PDF(102.5 KB) View with Adobe Reader on a variety of devices
ePub(171.3 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(135.4 KB) View on Kindle device or Kindle app on multiple devices
Updated:February 25, 2019
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Replication status indicates the health of communication of the sync between PAN and other nodes in a deployment. Primary Admin nodes sync config changes and updates to all other nodes in a deployment in the form of replication messages. For connectivity or communication issues, if a node goes out of sync or is unreachable, it will no longer receive or consume updates from the admin node and will need to be recovered.
Hovering over the Target next to the Node Status under Administration > Deployment will show you the current status of the node's replication and if it is in sync, how many messages are pending to be synced. If replication has failed, you will see a message indicating you need to perform a manual sync if the node is still reachable but out of sync.
If the node is not reachable however, in instances where it may have powered off or in case of connectivity issues, it will indicate a different status. Ultimately, the action to take is the same, ensure reachability and perform a manual resync.
To perform a manual sync:
Navigate to Administration > Deployment and select the Node that is in need of a manual synchronization with the checkbox next to it:
Performing a manual sync will involve a reload of the target node but not the Primary Admin node.
There might be situations where if the node has been out of sync for a long time, it may not be possible to recover via a manual sync. In these conditions, the quickest way to recover is to Deregister the node from the deployment, perform an application reset-config via CLI. Once the config has been reset, you can register the node back to the deployment.