Discovering Devices CHAPTER

Transcription

1 CHAPTER 11 The Cisco Prime Collaboration Manager discovery process involves three phases: Access-level discovery Cisco Prime CM verifies the SNMP, HTTP, CLI, and JTAPI credentials on the devices. For endpoints (CTS), SNMP and CLI credentials are validated. For application manager (CTS-Manager) and multipoint switches (CTMS), SNMP and HTTP are validated. For call processors (Cisco Unified CM), SNMP, HTTP, and JTAPI credentials are validated. For network devices (routers and switches), SNMP is validated. Inventory discovery Cisco Prime CM polls MIB-II and other device MIBs to collect information on the device inventory, neighboring switches, and default gateway. It also verifies whether the polled device is supported in Cisco Prime CM. Topology discovery Cisco Prime CM verifies whether CDP is enabled on the device and discovers the topology, based on CDP. Cisco Prime CM discovers both layer 2 and layer 3 paths. The initial endpoint discovery ends at the layer 2 path discovery. In the layer 2 path discovery, Cisco Prime CM discovers the endpoints, switches and default gateway. The layer 3 path is discovered when a troubleshooting workflow is triggered either manually or automatically. For further details on the Troubleshooting workflow, see Troubleshooting the Sessions, page

2 Chapter 11 Figure 11-1 shows the device discovery life cycle. Figure 11-1 Device Discovery Life Cycle Discovery Ping failed Unknown Check credentials Incorrect credentials Accessible Device not supported Data Collection Inventory Collected Managed User changes device state Unreachable Inaccessible Unsupported Undiscoverable Suspended Check connectivity Enter correct credentials Check connectivity (SNMP/HTTP timeout) User performs the task Resume Management Transient device state Device States A device state indicates that Cisco Prime CM is able to access the device and collect the inventory. The device state is updated only after performing either a discovery or an update inventory task. Cisco Prime CM displays the following device states: Unknown This is the preliminary state, when the device is first added. Unreachable Cisco Prime CM is unable ping the device, using ICMP. If the ICMP is not enabled on the device, the device is moved to the Unreachable state. You must update the emsam.properties file to disable the ICMP ping verification. The emsam.properties file is available in the directory /opt/emms/emsam/conf. To edit the emsam.properties file: a. Log into the Cisco Prime CM server as cmuser. b. Navigate to /opt/emms/emsam/conf using the command cd /opt/emms/emsam/conf. c. Open the emsam.properties file, using any UNIX editor. d. Change the string, true to false in the line under ICMP Ping - Enable/Disable: com.cisco.nm.emms.discovery.icmp.ping = false e. Save the file. Start the discovery job again to discover the device. Unsupported Cisco Prime CM compares the device with the device catalog, if the device does not match or the SysObjectID is not known, the device is moved to this state. 11-2

3 Chapter 11 Sequence for Accessible Cisco Prime CM is able to access the device through all mandated credentials. This is part of the access-level discovery, which is an intermediate state during the device discovery. Inaccessible Cisco Prime CM is not able to access the device through any one of the mandated credentials (see Managing Credentials). You must check the credentials and discover the devices, again. Inventory Collected Cisco Prime CM is able to collect the required data, using the mandated data collectors. This is part of the inventory discovery, which is an intermediate state during device discovery. Undiscoverable Cisco Prime CM is not able to collect the required data, using the mandated data collectors. CTS-Manager Cisco Prime CM must collect the endpoints data from CTS-Manager. If it not collected, CTS-Manager is moved to Undiscovered state. There are no mandate data collection for Cisco Unified CM, CTS, CTMS, and other network devices. Connectivity issues can be caused by SNMP and/or HTTP (HTTPS) timeout. Also, if you use HTTP (HTTPS) to collect data, only one HTTP (HTTPS) user can log in at a time. If Cisco Prime CM faces any of these problems, the device state is moved to the Undiscoverable state. You must check the connectivity and discover the devices, again. Managed Cisco Prime CM has successfully imported the required device data to the inventory database. All session, endpoints, and inventory data are available for the device in this state. You can troubleshoot a device only if it is in this state. Suspended User has suspended the monitoring of the device. The session and endpoints data are not displayed for the devices in this state. The periodic polling is also not performed for the devices in this state. You cannot update inventory for these devices. To update inventory for this device, you need to perform Resume management. The device will be discovered again. See Suspending and Resuming Managed Devices, page 12-8 for details on suspended devices. Sequence for You must follow the following sequence to discover devices in Cisco Prime CM: 1. Enter the device credentials using the Manage Credentials page (Inventory > Device Inventory > Manage Credentials). You must enter credentials for all video collaboration devices that you plan to monitor, using Cisco Prime CM. That is, you must enter credentials for: Application manager (CTS-Manager) Call processors (Cisco Unified CM) Multipoint switches (CTMS) Endpoints (CTS) and Network devices (routers and switches). 11-3

4 Sequence for Chapter Discover the devices using the Inventory page (Inventory > Device Inventory > Discover Devices). You must first discover the Application manager (Example: CTS-Manager). The Cisco Unified CM, CTMS and CTS, default gateway, and switches are discovered along with CTS-Manager. Cisco Prime CM supports call processors clusters. You must ensure that the cluster IDs are unique. Cisco Prime CM must discover and manage only the call processor publisher to manage a cluster. All subscribers must be discovered only through the publisher. You must not discover the subscribers directly. Cisco Prime CM must manage the cluster publisher to monitor a cluster. The JTAPI must be configured on the cluster publisher and the computer telephony integration (CTI) service must be running on all subscribers. You must ensure that the device credentials that you have entered are correct. During the discovery process, based on the device that you want to discover, Cisco Prime CM connects to the device, using CLI, HTTP (HTTPS), or SNMP. CDP should also be enabled on the device. 11-4

5 Chapter 11 Sequence for Figure 11-2 shows the discovery life cycle for a Cisco TelePresence Manager (CTS-Manager). Figure 11-2 Discovery Life Cycle for a CTS-Manager User enters CTS-MAN to manage Discovery aborted NO Cisco Prime CM checks for access-level for CTS-MAN Yes Collects inventory: Discovers Cisco Unified CM CTMS and CTS Error logged NO Cisco Prime CM checks for access-level credentials for CTMS, CTS, and CUCM. Yes Collects inventory for CTS and/or CTMS. Discovers neighboring switch and default gateway Collects inventory for CUCM Discovers CTS Yes NO Error logged Cisco Prime CM checks for access-level credentials for neighboring switch and default gateway Yes Collects inventory for neighboring switch and default gateway Collects CDP link data for CTS and/or CTMS Cisco Prime CM checks for access-level credentials for CTS NO Error logged Collects CDP link data for neighboring switch and default gateway Discovery of CTS-MAN is completed and database is updated

6 Chapter 11 You have to perform the Discovery task when you want to add new devices to the Cisco Prime CM database. You can either discover devices immediately or schedule a discovery job. To discover devices: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Choose Inventory > Device Inventory. The Inventory page appears. Click Discover Devices. The Discovery Setup window appears. Enter the job name. Click True to enable the device accessibility verification while discovering devices. Cisco Prime CM verifies the device accessibility, using SNMP, CLI, HTTP (HTTPS), and JTAPI. Enter the IP address of the device. You can enter multiple IP address using one of the supported delimiters comma, colon, or blank space. To manage a cluster, enter only the IP address of the call processor publisher. All subscribers must be discovered only through publisher. You must not discover the subscribers directly. You can either schedule a periodic discovery job or run the discovery job, immediately. If you want to run the job immediately go to Step 8. Enter the scheduling details to schedule a discovery job. Start Date Enter the start date for the time period in the MM/DD/YYYY format, or click the drop-down list to select the start date from a calendar. Start Time Click the drop-down list to select the start time. The time displayed is the client browser time. The scheduled periodic job runs at this specified time. End Date Enter the end date for the time period in the MM/DD/YYYY format, or click the drop-down list to select the end date from a calendar. If you do not want to specify an end date, click No Date. 11-6

7 Chapter 11 Step 7 Step 8 Click either Daily or Weekly to specify whether you want the periodic job to run every day or once a week. Click Run Now to immediately run the discovery job or click Schedule to schedule the periodic discovery job at a later time. The discovery of devices may take a few minutes to appear on the Current Inventory table, based on the device that you have entered. You can check the status of the job, using the List Discovery Jobs button on the Inventory page. The Job Management page appears with the list of discovery jobs. After the discovery job is complete, you can verify the entered credentials in the Current Inventory table (Access Information), using Inventory > Device Inventory. If the credentials are not displayed, update the credential profile (see Updating Device Credentials, page 10-4) and run the discovery again. If you are discovering devices for the first time, after the discovery job has completed, you must import the sessions, using the Import Sessions link in the Sessions Monitoring (Monitoring > Session Monitoring) page. See Import Sessions from Application Manager and Multipoint Switches, page 13-4 for details. 11-7

8 Chapter