Profile Name
|
Name of the credential profiles.
For example:
|
Device Type
|
(Optional) The credential fields (such as SNMP, HTTP, CLI) are displayed, based on the device type that you have selected.
To reduce rediscovery time, we recommend that you select the device type when you create the credential profiles.
The default device type is "Any", if you do not select a device type while creating a credential profile.
See cisco.com for the list of device types.
For EX series, MX series, SX series, bare Codec devices, and all profiles with Codec, select the device type as TC_CE.
While managing coresident PLM, you should provide both CLI and HTTP credentials.
|
Device Type
|
For Cisco Prime Collaboration Release 12.1 and later
While managing co-resident PLM, you should provide both CLI and HTTP credentials.
Ensure the following conditions are met for the Router to be identified as a Cisco Unified Border Element (CUBE):
-
CLI credentials (CLI Login Username and CLI Login Password) for the Device Type - Router is mandatory.
-
Enabling SSH version 2 or later on Port 22 of the Router is mandatory.
-
If Enable Password is set on the Router then provide the password in CLI Enable Password field.
For Cisco Prime Collaboration Release 11.6 and later
For EX series, MX series, SX series, DX series with CE image, bare Codec devices, and all profiles with Codec, select the
device type as Codec.
For MSE devices, select Cisco MCU as the device type.
For Cisco Prime Collaboration Release 11.5 and later
For Cisco Virtualized Voice Browser devices, select Virtualized Voice Browser device type.
You can enter any credentials (SNMP, HTTP, CLI , MSI) to create an "Any" credential profile. You must create an "Any" credential profile to run auto-discovery (Ping Sweep and CDP discovery). However, you can run logical discovery also.
If your network has multiple subnets, then create an "Any" profile for each subnet.
|
IP Version
|
The IP address is version 4 or version 6.
|
IP Address Pattern
|
IP address of the devices for which the credentials are provided. You must:
-
Separate multiple IP addresses by the delimiter pipe (|).
-
Not use 0.0.0.0 or 255.255.255.255.
-
Not use question mark (?).
We recommend that you:
-
Enter the exact IP address for Cisco Unified CM, and Cisco TMS.
-
Enter the exact IP address for either CTS or network devices.
-
Do not use many wildcard expressions in the address patterns.
For example:
Avoid using patterns such as 150.*.*.*, 192.78.22.1?, 150.5.*.*/24.
If you are unable to find a common pattern for the devices, enter *.*.*.*.
Minimize the use of wildcard character (*), while defining the IP address patterns in the credential profiles .
For Cisco Prime Collaboration Release 11.5 and later
Use of wildcard character may increase the discovery time.
See SNMPv2C to understand how the patterns are used.
|
General SNMP Options
|
SNMP Timeout - The default is 10 seconds.
|
SNMP Retries - The default is 2.
|
SNMP Version - Selecting an SNMP version is mandatory.
|
SNMPv2C
Used to discover and manage the device.
|
SNMP Read Community String
You can provide either SNMPv1 or SNMPv2C credentials. We recommend that you use different SNMP credentials for Cisco TelePresence
systems and network devices.
Cisco Prime Collaboration Assurance searches the credential profiles, based on the IP address pattern. Cisco Prime Collaboration
Assurance then chooses a profile for which the SNMP credentials match. There can be multiple matching profiles, that is, profiles
with the same SNMP credentials. In such cases, Cisco Prime Collaboration Assurance chooses the profile that matches first.
For Cisco Prime Collaboration Release 11.1 and earlier
Note
|
If multiple profiles have the same SNMP credentials but different CLI credentials, Cisco Prime Collaboration Assurance might
chose a profile that contains the correct SNMP credentials but incorrect CLI credentials for the device. If this occurs, the
troubleshooting workflow might not work.
|
|
SNMP Write Community String
|
SNMPv3
Used to discover and manage the device.
|
SNMP Security Name - Enter a security name.
|
SNMP Authentication Protocol - You can choose either MD5 or SHA.
|
SNMP Authentication Passphrase - Enter a passphrase.
|
SNMP Privacy Protocol - You can choose either AES, AES128, or DES.
For Cisco Prime Collaboration Release 11.5 and later
SNMP Privacy Protocol - You can choose either AES128, or DES.
|
CLI
Used to access the device through CLI to discover media path for troubleshooting.
|
CLI Login Username and Password
The CLI credentials are used during the troubleshooting workflow. If the credentials are not entered or if the entered credentials
are incorrect, the troubleshooting workflow feature may not work.
For Cisco Prime Collaboration Release 11.5 and later
The CLI credentials are used to manage video test call and analyze call signaling through SIP Call Flow Analyzer.
For Cisco Prime Collaboration Release 12.1 and later
Ensure the following conditions are met for the Router to be identified as a Cisco Unified Border Element (CUBE):
-
CLI credentials (CLI Login Username and CLI Login Password) for the Device Type - Router is mandatory.
-
Enabling SSH version 2 or later on Port 22 of the Router is mandatory.
-
If Enable Password is set on the Router then provide the password in CLI Enable Password field.
|
HTTP
Used to access the device through HTTP to poll system status and meeting information.
|
HTTP Username and Password
Cisco Prime Collaboration Assurance first checks the access for HTTP. If the access attempt fails, then Cisco Prime Collaboration
Assurance checks the access for HTTPS.
If you log in to Cisco TMS using the <domain/username> format, then ensure that you add the same <domain/username> value
in the HTTPS Username field.
|
JTAPI
Used to retrieve the session status information from the Cisco Unified CM.
|
(Optional) JTAPI Username and Password.
Note
|
Password must not contain a semicolon (;) or equals (=).
|
|
|
For Cisco Prime Collaboration Release 11.5 and later
Used to retrieve the session status information from the Cisco Unified CM.
For Cisco Prime Collaboration Release 12.1 SP1
A new set of JTAPI specific parameters are introduced to secure the JTAPI (TLS v1.2) connection.
Following are a set of JTAPI specific parameters.
-
Secure Connection check box
-
Check the check box - Checking this option enables you to have a secure TLS connection to Cisco Unified Communications Manager.
A warning message appears indicating you to "Ensure that “Standard CTI Secure Connection” role is associated with this JTAPI
user, along with other required roles". Click OK to return to Cisco Prime Collaboration Assurance.
-
Uncheck the check box - If the check box is not checked, JTAPI cannot make a secure connection.
A warning message appears indicating you to "Ensure that “Standard CTI Secure Connection” role associated with this JTAPI
user is removed. To continue to Monitor Conferences, ensure that the required roles are configured". Click OK to return to
Cisco Prime Collaboration Assurance.
For more information, see Setting up Devices for Cisco Prime Collaboration Assurance.
The check box enables you to enter the parameters in (enable or disable) the new Secure JTAPI fields.
|
|
2. TFTP Server IP Address - Specify the IP address of the TFTP Server.
Note
|
The value must be one of the nodes on the CUCM cluster. Make sure that the TFTP service is running on that node.
|
3. TFTP Server Port - The TFTP Server Port defaults to 69.
Note
|
Do not change the default value unless the System Administrator recommends.
|
4. CAPF Server IP Address - Specify the IP address of the CAPF Server.
Note
|
-
For more information on the certificate authority proxy function, see the Chapter on “Certificate Authority Proxy Function” in the “Security Guide for Cisco Unified Communications Manager”.
- Ensure to select RSA Only from the Key Order drop-down list while creating the CAPF profile on CUCM.
-
You must always provide the CUCM Publisher IP Address.
|
5. CAPF Server Port - The CAPF Server Port number defaults to 3804.
Note
|
Ensure that the value entered matches with the value that is configured in Cisco Unified Communication Manager.
|
7. Instance ID for Publisher - This field specifies the application instance identifier configured in CAPF Settings section of Application or End User
CAPF profile configuration page in the Cisco Unified Communication Manager cluster.
8. Secure Authentication String – Enter the Authentication String configured in CAPF Settings section of Application or End User CAPF profile configuration
page in the respective Communication Manager Publisher.
Note
|
The section on Troubleshooting Secure JTAPI Connections lists the details of troubleshooting the possible errors and recommended actions "with setup of CUCM for Secure JTAPI and
Sessions not coming up on Conference Diagnostics" resepctively.
|
|