Cisco Cisco Prime Network Services Controller 3.2 Installation Guide
4
The administrator deploys a new Device Adapter VM (Adapter2) with a management IP address that is different from the
management IP address for Adapter1.
management IP address for Adapter1.
5
Prime Network Services Controller does not recognize Adapter2 as a replacement for Adapter1 and instead considers it a new
instance of the Device Adapter.
instance of the Device Adapter.
6
All services (lb1, lb2, and lb3) that were managed by Adapter1 continue to run, but in headless mode; that is, any attempt by
Prime Network Services Controller to change the configuration for those services fails.
Prime Network Services Controller to change the configuration for those services fails.
7
Additional deployments, such as lb4, might be assigned to Adapter1 for management and will therefore fail to complete deployment.
If you delete the managed-endpoint for the Device Adapter before replacing the Device Adapter VM,
Prime Network Services Controller will not recognize the new Device Adapter VM as a replacement for
the original Device Adapter VM. Instead, you will encounter the behavior described in this scenario.
Prime Network Services Controller will not recognize the new Device Adapter VM as a replacement for
the original Device Adapter VM. Instead, you will encounter the behavior described in this scenario.
Note
Troubleshooting Devices and Services
You can use Prime Network Services Controller to troubleshoot faults associated with managed devices and services.
Procedure
Step 1
Choose Resource Management > Managed Resources > root > tenant.
Step 2
In the Network Services tab, choose the required service or device, and then click Edit.
Step 3
In the General tab, review the Status area for any issues or states affecting reachability, configuration, or association.
Step 4
In the Faults tab, review the displayed faults. To view additional information about a fault, double-click the entry, or choose
the entry and then click Properties.
the entry and then click Properties.
Upgrading Prime Network Services Controller
Upgrading Overview
Prime Network Services Controller 3.2.2 does not support InterCloud functionality. If you upgrade from
a previous version of Prime Network Services Controller with InterCloud objects, the upgrade procedure
will detect those objects and stop the upgrade process. You must delete all InterCloud objects before you
can upgrade to 3.2.2.
a previous version of Prime Network Services Controller with InterCloud objects, the upgrade procedure
will detect those objects and stop the upgrade process. You must delete all InterCloud objects before you
can upgrade to 3.2.2.
Note
Use the following procedure to upgrade to a newer Prime Network Services Controller version. For Prime Network Services Controller
3.2.2, the only supported upgrade paths are from Prime Network Services Controller 3.0.2 or 3.2 as shown in the following table.
3.2.2, the only supported upgrade paths are from Prime Network Services Controller 3.0.2 or 3.2 as shown in the following table.
55