Cisco Cisco Prime Network Services Controller 3.2 Guía De Instalación
Network Services Controller and the Device Adapter have not been able to communicate with each other for an extended period of
time. If Prime Network Services Controller and the Device Adapter can resume communication with each other, they will recover
from the lost-visibility state.
time. If Prime Network Services Controller and the Device Adapter can resume communication with each other, they will recover
from the lost-visibility state.
If communication with the endpoint cannot be reestablished, you can remove the managed endpoints that are in lost-visibility state.
However, do not remove the managed endpoint for the Device Adapter. Instead, replace the Device Adapter VM by using the
same host information (hostname, access credentials, and management IP address) as the Device Adapter VM that is in lost-visibility
state.
However, do not remove the managed endpoint for the Device Adapter. Instead, replace the Device Adapter VM by using the
same host information (hostname, access credentials, and management IP address) as the Device Adapter VM that is in lost-visibility
state.
By removing the existing VM and recreating the Device Adapter VM with the same host information, Prime Network Services
Controller will recognize the new Device Adapter VM as a replacement for the previous Device Adapter VM. In addition, the new
Device Adapter VM will assume management of any third-party devices that the previous Device Adapter VM managed.
Controller will recognize the new Device Adapter VM as a replacement for the previous Device Adapter VM. In addition, the new
Device Adapter VM will assume management of any third-party devices that the previous Device Adapter VM managed.
Scenario 1
In this scenario, Prime Network Services Controller is deployed with the Device Adapter.
1
Prime Network Services Controller deploys three load balancers (lb1, lb2, and lb3) that are managed by Adapter1.
2
Adapter 1 becomes unavailable.
3
The administrator does not remove the managed-endpoint for Adapter1.
4
The administrator removes the Adapter1 VM and recreates it by using the same host information as that for the original Device
Adapter.
Adapter.
5
Prime Network Services Controller recovers connectivity and recognizes the new Device Adapter VM as a replacement for the
previous Adapter1.
previous Adapter1.
6
The new Adapter1 assumes management of the existing service nodes. In addition, Prime Network Services Controller will deploy
new service nodes (such as lb4) that are assigned to the new Adapter1.
new service nodes (such as lb4) that are assigned to the new Adapter1.
The new Adapter1 might attempt to reapply the configuration to the existing service nodes (lb1, lb2, and
lb3). If this occurs, Prime Network Services Controller might update the configuration state for these
service nodes to failed-to-apply. If this occurs, reboot the service nodes to display the correct configuration
state.
lb3). If this occurs, Prime Network Services Controller might update the configuration state for these
service nodes to failed-to-apply. If this occurs, reboot the service nodes to display the correct configuration
state.
Note
Scenario 2
In this scenario, the new Device Adapter has different host information than the original Device Adapter.
If the new Device Adapter VM has different host information, such as a different management IP address or hostname, Prime Network
Services Controller might not recognize it as a replacement for the existing VM. All existing service nodes that were managed by
the original Device Adapter VM will continue to run, but in headless mode. Any additional configuration changes that are made to
those service nodes by using Prime Network Services Controller will not be applied. In addition, because Prime Network Services
Controller does not recognize the new Device Adapter VM as the replacement for the previous Device Adapter VM, subsequent
deployments will fail because they cannot be assigned to the original Device Adapter.
Services Controller might not recognize it as a replacement for the existing VM. All existing service nodes that were managed by
the original Device Adapter VM will continue to run, but in headless mode. Any additional configuration changes that are made to
those service nodes by using Prime Network Services Controller will not be applied. In addition, because Prime Network Services
Controller does not recognize the new Device Adapter VM as the replacement for the previous Device Adapter VM, subsequent
deployments will fail because they cannot be assigned to the original Device Adapter.
As in the previous scenario, Prime Network Services Controller is deployed with Device Adapter (Adapater1).
1
Prime Network Services Controller deploys three load balancers (lb1, lb2, and lb3).
2
Adapter1 enters lost-visibility state.
3
The administrator does not remove the managed-endpoint for Adapter1.
54