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:
If you do not configure these items with NTP, they will not register with Prime Network Services Controller.
Note | NTP service does not come up on the terminal when PNSC is upgraded from the previous releases to Release 3.4.1d or later. To access the NTP service, you need to re-login into the same terminal or start a new terminal. |
For information on configuring NTP, see the following topics:
Configure NTP on VMs by using the information in the following table.
For this VM: | Do this: |
---|---|
VSG |
Configure the NTP server in the Prime Network Services Controller GUI as described in the Prime Network Services Controller User Guide, section "Configuring NTP." |
VSM |
Enter the following CLI command from the VSM console, where x.x.x.x is the NTP server IP address: clock timezone zone-name offset-hours offset-minutes clock summer-time zone-name start-week start-day start-month start-time end-week end-day end-month end-time offset-minutes ntp server x.x.x.x |
Use this procedure to configure NTP in Prime Network Services Controller.
1. In your browser, enter https://ip-address where ip-address is the Prime Network Services Controller IP address.
2. In the Prime Network Services Controller login window, enter the username admin and the admin user password. This is the password that you set when installing Prime Network Services Controller.
3. Set the time zone by doing the following:
4. Add an external NTP server as the time source, as follows:
Establish connectivity between and VMware vCenter by performing the following tasks:
Note | You need to export and Register the VMware vCenter Extension plugin for VMware vCenter releases 5.5 and 6.0. For VMware vCenter release 6.5 onward, plugin registration is automated and you need to enter VMware vCenter Administrator Credentials while adding VM Manager. |
The first step in configuring connectivity with VMware vCenter is exporting the vCenter extension file.
1. In , choose Resource Management > VM Managers > VM Managers.
2. In the VM Managers pane, click Export vCenter Extension.
3. Save the vCenter extension file in a directory that the vSphere Client can access because you will need to register the vCenter extension plug-in from within the vSphere Client (see Registering the vCenter Extension Plugin in vCenter).
4. Open the XML extension file to confirm that the content is available.
Step 1 | In , choose Resource Management > VM Managers > VM Managers. |
Step 2 | In the VM Managers pane, click Export vCenter Extension. |
Step 3 | Save the vCenter extension file in a directory that the vSphere Client can access because you will need to register the vCenter extension plug-in from within the vSphere Client (see Registering the vCenter Extension Plugin in vCenter). |
Step 4 | Open the XML extension file to confirm that the content is available. |
Registering the vCenter extension plug-in enables you to create a VM Manager in Prime Network Services Controller and communicate with the vCenter VMM and the VMs that Prime Network Services Controller manages.
1. From the VMware vSphere Client, log in to the vCenter server that you want to manage by using Prime Network Services Controller.
2. In the vSphere Client, choose Plug-ins > Manage Plug-ins.
3. Right-click the window background and choose New Plug-in.
4. Browse to the Prime Network Services Controller vCenter extension file that you previously exported and click Register Plug-in.
5. In the security warning message box, click Ignore.
6. When the success message is displayed, click OK, and then click Close.
Step 1 | From the VMware vSphere Client, log in to the vCenter server that you want to manage by using Prime Network Services Controller. | ||
Step 2 | In the vSphere Client, choose Plug-ins > Manage Plug-ins. | ||
Step 3 | Right-click the
window background and choose
New
Plug-in.
| ||
Step 4 | Browse to the Prime Network Services Controller vCenter extension file that you previously exported and click Register Plug-in.
The vCenter Register Plug-in window appears, displaying a security warning. | ||
Step 5 | In the security
warning message box, click
Ignore.
A progress indicator shows the task status. | ||
Step 6 | When the success message is displayed, click OK, and then click Close. |
1. Choose Resource Management > VM Managers > VM Managers, and then click Add VM Manager.
2. In the Add VM Manager dialog box, enter the following information and then click OK:
Step 1 | Choose Resource Management > VM Managers > VM Managers, and then click Add VM Manager. |
Step 2 | In the Add VM
Manager dialog box, enter the following information and then click
OK:
|
By default, Prime Network Services Controller discovers all VMs on Nexus 1000V switches whether or not a tenant or another organization is configured on the VM vNIC. This procedure describes how to configure Prime Network Services Controller so that it discovers only those VMs with a tenant or another organization configured on a vNIC.
Note | If you enable this option, VMs that are protected but powered off will not be managed by Prime Network Services Controller. |
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. Install the Prime Network Services Controller debug plugin and access the root shell.
2. In the root shell, do the following:
3. Using a vi editor, open /opt/cisco/sam.config for editing.
4. In the custom section of the file, add the following entry:
5. Save the file and exit the editor.
6. Enter exit and then enter service restart.
Step 1 | Install the
Prime Network Services Controller debug plugin and access the root
shell.
For information on installing the debug plugin, contact the Cisco TAC. |
Step 2 | In the root
shell, do the following:
|
Step 3 | Using a vi editor, open /opt/cisco/sam.config for editing. |
Step 4 | In the custom
section of the file, add the following entry:
skipNonTenantVms=true |
Step 5 | Save the file and exit the editor. |
Step 6 | Enter exit and then enter service restart. |