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.
This section contains the following topics:
Registering service VMs with Prime Network Services Controller ensures that Prime Network Services Controller recognizes and can communicate with the VMs.
For Cisco service VMs, see Registering Cisco VMs Deployed on VMware.
This procedure describes how to register VSM VMs that have been installed directly on the hypervisor. Cisco VMs that are instantiated on a hypervisor through Prime Network Services Controller are automatically registered with Prime Network Services Controller upon instantiation.
You do not need to register a VSG that is installed directly on the hypervisor. The deployment procedure automatically registers the VM with Prime Network Services Controller.
1. In the hypervisor, navigate to the VM to be registered with Prime Network Services Controller.
2. Open a console window for the VM.
3. In the CLI, register the VM as follows:
By default, Prime Network Services Controller includes a service path for use with the automatic instantiation of network services. This service path can cause issues if it is used by a port profile. As a result, we recommend that you remove the default service path from Prime Network Services Controller.
1. Choose Policy Management > Service Policies > root > Policies > Service Path.
2. In the General tab, choose the default service path and then click Delete.
The following topics can help troubleshoot issues that you might encounter with the Prime Network Services Controller Device Adapter and service VMs:
If you change the management IP address of Prime Network Services Controller, configure service VMs that were previously registered with Prime Network Services Controller so that they can continue to communicate with Prime Network Services Controller. See the following topics for more information:
After changing the Prime Network Services Controller management IP address, you must register service VMs with the new IP address as follows.
Confirm the following:
1. For each VSM registered with Prime Network Services Controller:
2. For each VSG registered with Prime Network Services Controller:
If you change the IP address of the Prime Network Services Controller server, you must update vsm-service as follows so that Prime Network Services Controller can maintain communications with Nexus 1000V switches.
Obtain the Prime Network Services Controller debug plugin nsc-dplug.3.4.n.x.bin. If you need assistance in locating this file, contact the Cisco Technical Assistance Center.
You can contact the TAC over the phone or via the Web:
Regional phone numbers are available at http://www.cisco.com/c/en/us/support/web/tsd-cisco-worldwide-contacts.html#numbers.
To use the Web, go to http://www.cisco.com/cisco/web/support/index.html.
1. Log in to Prime Network Services Controller via the console.
2. Stop the pmon services by entering the following commands:
3. Load the Prime Network Services Controller debug plugin:
4. Delete the database for the vsm-service:
5. Restart pmon services:
6. Use the Prime Network Services Controller XML API to identify and delete the stale extpolClient object for vsm-service.
Step 1 | Log in to Prime Network Services Controller via the console. |
Step 2 | Stop the pmon
services by entering the following commands:
# connect local-mgmt (local-mgmt)# service stop |
Step 3 | Load the
Prime Network Services Controller debug plugin:
(local-mgmt)# update bootflash:/nsc-dplug.3.4.n.x.bin
A $ prompt is displayed when the
update bootflash command is complete.
|
Step 4 | Delete the
database for the vsm-service:
$ sudo bash # rm /opt/cisco/vsm-service/db/flash/dme.db |
Step 5 | Restart pmon
services:
# connect local-mgmt (local-mgmt)# service start |
Step 6 | Use the
Prime Network Services Controller XML API to identify and delete the
stale extpolClient object for vsm-service.
For more information, see the Cisco Prime Network Services Controller XML API Guide. |
You can use to troubleshoot faults associated with managed devices and services.
1. Choose Resource Management > Managed Resources > root > tenant.
2. In the Network Services tab, choose the required service or device, and then click Edit.
3. In the General tab, review the Status area for any issues or states affecting reachability, configuration, or association.
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.