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.
You need to configure device credentials for all devices that are managed using Cisco Prime Collaboration. Device credentials are required for discovering devices and updating inventory. If the credentials vary for different devices, create separate credentials profiles; that is, if you want to manage two Cisco Unified Communications Managers with different credentials in Cisco Prime Collaboration, you must create two separate credentials profiles.
The following are some of the requirements while creating credentials profiles:
HTTP and SNMP credentials are mandatory for the endpoints to get into Managed state.
For Cisco Prime Collaboration Release 11.1 and earlier
CLI credentials are required to troubleshoot sessions involving endpoints and network devices.
For Cisco Prime Collaboration Release 11.5 and later
CLI credentials are required to manage video test call and analyzing call signaling through SIP Call Flow Analyzer.
JTAPI credentials are mandatory for Unified CM for conference monitoring. This credential is not required for endpoints.
Create an Enterprise License Manager profile by selecting Enterprise License Manager as the device type for Prime License Manager.
Define HTTP and SNMP credentials for Unified Contact Center devices such as Cisco Unified Intelligence Center (CUIC), Cisco Voice Portal (CVP), Cisco Finesse, Cisco SocialMiner, Cisco Unified Contact Center Enterprise (Unified CCE), Cisco Unified Contact Center Express (Unified CCX), Cisco MediaSense.
For Cisco Prime Collaboration Release 11.5 and later
Define HTTP and SNMP credentials for Unified Contact Center devices such as Cisco Unified Intelligence Center (CUIC), Cisco Voice Portal (CVP), Cisco Finesse, Cisco SocialMiner, Cisco Unified Contact Center Enterprise (Unified CCE), Cisco Unified Contact Center Express (Unified CCX), Cisco Virtualized Voice Browser.
Enter HTTP credentials for Contact Center Enterprise in the following format: domain\administrator. For example hcsdc2\administrator.
Enter HTTP credentials for Cisco Unified Customer Voice Portal (CVP) which have the ServiceabilityAdministrationUserRole privileges. The default username wsmadmin has this privilege.
JTAPI credentials are not required for Cisco Prime Collaboration Assurance Standard mode .
Credentials are not required for the phones, Cisco Cius, Cisco Jabber, and Cisco Jabber Video for TelePresence (Movi) endpoints. These endpoints are discovered with the discovery of the call processor with which they are registered.
Select VCS/ EXPRESSWAY in the Device type drop-down list to create credentials for Cisco Expressway-Core, Cisco Expressway-Edge or a Cisco VCS with Cisco Collaboration Edge or Core.
You must review the Setting up Devices for Prime Collaboration Assurance document to understand the required protocols to manage devices in Cisco Prime Collaboration 11.0.
You must review the Configure Devices for Prime Collaboration Assurance document to understand the required protocols to manage devices in Cisco Prime Collaboration 11.5.
You must review the Configure Devices for Prime Collaboration Assurance document to understand the required protocols to manage devices in Cisco Prime Collaboration 11.6.
Step 1 | In the
Cisco
Prime Collaboration page, choose
from the Toggle
Navigation pane.
For Cisco Prime Collaboration Release 11.5 and later In the Cisco Prime Collaboration page, choose from the Toggle Navigation pane. The Inventory Management page is displayed. |
Step 2 | In the Credentials Profile page, click Add and enter the necessary information described in the Credential Profiles Field Descriptions table. |
Step 3 | Click Save. In your network, you may have configured the same SNMP credentials for all devices. In such cases, first create a new profile and later clone the existing profile. To clone, in the Credentials Profile page, select an existing profile and click Clone and after the required updates click Add/Update. |
After the devices are discovered, you can check the current Inventory table to verify that the credentials have been updated in the Cisco Prime Collaboration database.
The following table describes the fields on the Credential Profiles page.
For Cisco Prime Collaboration Release 11.5 and later
CISCO INTERACTION MANAGER is renamed as WEB/EMAIL INTERACTION MANAGER
CUIC is renamed as INTELLIGENCE CENTER
CTS is renamed as CTS/IX ENDPOINT
CISCO UNIFIED COMMUNICATIONS MANAGER is renamed as COMMUNICATIONS MANAGER
C_SERIES CODEC is renamed as TC/CE ENDPOINT
E20 is renamed as E20 ENDPOINT
ISDN is renamed as ISDN GATEWAY
MCU is renamed as MULTIPOINT CONTROLLER
MXP is renamed as MXP ENDPOINT
ROUTER is renamed as ROUTER/VOICEGATEWAY
TPS is renamed as TELEPRESENCE SERVER
TELEPRESENCE CONDUCTOR is renamed as TELEPRESENCE CONDUCTOR
Note | You do not need to add credentials for Cisco Device, Polycom, Cisco Unified Communications Manager Express (Cisco Unified CME), and UC500 Series devices in Credential Profiles page. |
For Cisco Prime Collaboration Release 11.1 and earlier
In Cisco Prime Collaboration, when a device is added, the SSL certificates are exchanged for credential validation by accessing a protected resource using HTTPS. During exchange, the SSL certificate is not stored in Cisco Prime Collaboration trust-store and communication with the device fails, at a later point of time. It is recommended that you manually import the SSL certificate to Cisco Prime Collaboration trust-store to access the device.
Cisco Prime Collaboration enables you to check the authenticity of the SSL certificate during its communication with the devices or applications over HTTPS. However, this is not mandatory as you can still continue to discover the devices without authenticating the certificate.
By default, Cisco Prime Collaboration does not validate the certificates from the devices or applications it communicates.
To enable the SSL certificate authentication:
Step 1 | Choose The . Certificate Management page is displayed. |
Step 2 | In the Device Certificate Management tab, check the Enable SSL certificate authentication for device discovery check box. |
Step 3 | Click the Import Certificates button. |
Step 4 | Restart the
Cisco Prime Collaboration server for the changes in trust manager to take
effect.
cm/admin# application stop cpcm cm/admin# show application status cpcm cm/admin# application start cpcm |
If you have modified credentials for the devices that you are currently managing in the Cisco Prime Collaboration application, you must modify the relevant credential profiles in the Cisco Prime Collaboration database.
If the credentials are incorrect, a major event— Device is inaccessible is triggered from Cisco Prime Collaboration ( ).
Step 1 | Choose
.
For Cisco Prime Collaboration Release 11.5 and later Choose |
Step 2 | From the Inventory Management page, select a device and click Modify Credentials. |
Step 3 | Update the credentials and
click
Rediscover.
Cisco Prime Collaboration takes a few minutes to update its database with the modified credentials. After the credentials are updated, an informational event, Device is accessible from Collaboration Manager, is triggered. Cisco Prime Collaboration uses the updated credentials in the next polling job. |
For Cisco Prime Collaboration Release 11.5 and later
If device discovery fails because of incorrect credentials, you can test the credentials for the failed devices and rediscover those devices. Choose
for a list of devices that were not discovered.Note | Do not run this task when a discovery job is in progress. |
Step 1 |
For Cisco Prime Collaboration Release 11.5 and later Choose The . Inventory Management page is displayed. | ||
Step 2 | From the Credential Profiles page, select the profile name to use for testing the credentials, and click Verify. | ||
Step 3 | Enter a valid device IP address to test the credentials. You can verify only one device at a time, and you cannot enter expressions such as *.*.*.*, 192.2.*.*, and so on. | ||
Step 4 | Click
Test. You can see
an inprogress moving icon next to the test button till the task completes. The
test results are displayed under the Test Credential Result pane.
If the verification fails, see the possible reasons listed in .
|
The credential verification error messages are tabulated below.
Either the device response time is slow or the device is unreachable. |
||||
Either the device response time is slow or the device is unreachable. |
Increase the SNMP Timeout and Retries values in the credential profile. |
|||
The configured SNMPv3 security level is not supported on the device. |
Device does not support the configured SNMPv3 security level. |
Change the SNMPv3 security level to the supported security level in the credential profile. |
||
The SNMPv3 response was not received within the stipulated time. |
Either the device response time is slow or the device is unreachable. |
|||
Enter the correct SNMPv3 engine ID in the credential profile. |
||||
Verify that the correct SNMPv3 authentication algorithm is entered in the credential profile. |
||||
The configured SNMPv3 context in the credential profile does not exist on the device. |
Verify that the configured SNMPv3 context is correct in the credential profile. |
|||
Either the SNMPv3 username is incorrect in the credential profile or the SNMPv3 username is not configured on the device. |
Verify that the correct SNMPv3 username is set in the credential profile and on the device. |
|||
Verify and reenter the device CLI credentials in the credential profile. |
||||
Either SSH or Telnet service may not be running on the device. |
||||
Either the HTTP service is not running or the URL is invalid. |
||||
Verify whether the HTTP or HTTPS service is running on the device. |
||||
Incorrect HTTP credentials entered in the credential profile. |
Verify and reenter the device HTTP credentials in the credential profile. |
|||
Incorrect JTAPI credentials entered in the credential profile. |
Verify and reenter the device JTAPI credentials in the credential profile.
|
|||
For Cisco Prime Collaboration Release 11.1 and earlier |
||||
Incorrect MSI credentials entered in the credential profile. |
Verify and reenter the device MSI credentials in the credential profile. |
You can delete only unused credential profiles. We recommend that you do not delete the credential profile of a device that is being managed in the Cisco Prime Collaboration application.