Managing Inventory CHAPTER. Viewing Inventory Details

Transcription

1 CHAPTER 14 Viewing Inventory Details Cisco Prime Collaboration Manager maintains continuous, real-time discovery of device inventory. The Prime CM inventory automatically reflects every addition, deletion, and modification that occurs in the video collaboration network. In Prime CM, devices are grouped based on the device type.the Device Group pane is available in the Device Inventory, Session Monitoring (as a filter), Endpoint Monitoring, Alarms, and Events pages. You can select devices/ endpoints from the groups you are interested in, to check inventory details, monitor sessions, endpoints, alarms, and events. Prime CM supports on-demand inventory update for the managed devices. It updates the device state, based on the inventory collection. You can export the inventory for all managed devices. You can suspend and resume the management of the device. The inventory is not updated for devices in the Suspended state. Each device that is managed by Prime CM is modeled to display the physical inventory of a device (interface and peripherals). To view the inventory details for a device, click on a row in the Current Inventory pane. Table 14-1 Current Inventory Endpoint Name Host Name Device Type Device Model Software Type Software Version State Last Discovered Name assigned to the endpoint for ease of identification. Name assigned to the device for ease of identification. Device type with the manufacturer s name, such as Switch, CTS. Device model, such as Catalyst3506G48PS. IP address used for managing the device. Click on the IP address to log into the device. For routers and switches, you must associate a terminal client application, such as Putty to log into the device. Software running on the device, such as IOS, CatOS. Software version running on the device. Prime CM managed device status. Date and time the device was last discovered. 14-1

2 Table 14-1 Current Inventory (continued) Mediatrace Role Unsupported Device does not support Cisco Mediatrace. Transparent Device supports Cisco Mediatrace but profile is not configured. Responder Cisco Mediatrace responder profile is enabled on the device. You should enable this profile if you want to monitor and collect information on Cisco Mediatrace. Initiator Cisco Mediatrace initiator profile is enabled on the device. You should enable this profile if you want to initiate Cisco Mediatrace sessions or polls. Initiator/Responder Cisco Mediatrace initiator and responder profiles are enabled on the device. IP SLA Role Unsupported Device does not support Video IP SLA Not Configured Device supports the Video IP SLA but it is not configured. Responder IP SLA Responder profile is configured on the device. The device that is configured with this profile, processes measurement packets and provides detailed timestamp information. The responder can send information about the destination device s processing delay, back to the source Cisco router. Performance Monitor Unsupported Device does not support Cisco Performance Monitor. Not Configured Device supports Cisco Performance Monitor but it is not configured. Configured Cisco Performance Monitor is enabled to allow you to monitor the flow of packets in your network and become aware of any issues that might impact the flow. Visibility Not Applicable- The realtime visibility feature is not supported for this device. Limited or Full visibility This status is displayed only for endpoints, based on the visibility settings. See Realtime Visibility of an Endpoint, page for details. System Information The System Information pane contains the following details for all devices except the TelePresence Server: Object ID Up Time Contact Location System Object ID of the endpoint. Duration for which the device has been running. Contact details of the endpoint. System location of the endpoint. 14-2

3 Access Information The Access Information pane contains the following details for all devices: Credential Profile Name SNMP Access Level SNMP Version CLI Access Level HTTP Access Level JTAPI Access Level Credential profile used for the selected device while discovery. Read Only is displayed, if you have defined the SNMP credentials in the Credential Profiles. Defined SNMP version in the Credential Profiles. If you have defined the CLI credentials, Prime CM checks whether the access level is Read Only or Read Write. The appropriate value is displayed, based on the verification. This field is not displayed if the credential is not mandatory for Prime CM. Read Only is displayed, if you have defined the HTTP credentials in the Credential Profiles. This field is not displayed if the credential is not mandatory for Prime CM. Read Only is displayed, if you have defined the JTAPI credentials in the Credential Profiles. This field is not displayed if the credential is not mandatory for Prime CM. Interface Information The Interface Information pane contains the following details for CTS, Cisco Codec, CTMS, MCU, MSE, Cisco TelePresence Server, and network devices. Physical Address Name Type MTU Speed CDP Operational Status Admin Physical address of the device. Name of the device. Type of the device. Maximum transmission unit. Maximum packet size, in bytes, that this interface can handle. Speed of the device in Mbps. Whether the CDP is enabled (True) or disabled (False.) Operational state of the device. Administrative status of the interface. Event Settings The Event Settings pane contains the following details for endpoints and infrastructure devices. 14-3

4 Sessions Name Minor Threshold Major Threshold Critical Threshold Enabled Automatic Troubleshooting Endpoints Category Alarm Condition Enabled Severity Packet loss, jitter, and/or latency for which the threshold values are set. Displays threshold values for minor alarms. Displays threshold values for major alarms. Displays threshold values for critical alarms. Event enabled or disabled. If enabled, displays event severity. Categories such as endpoint and service infrastructure. Condition defined for the alarm to trigger. Event enabled or disabled. Displays the severity: Critical, Major, or Minor. Device-specific Inventory Details The default threshold values are set for Rx packet loss, jitter, and/or latency for all endpoints. See Default Event Settings for details. To customize the default values, see Enabling Automatic Troubleshooting, page You can further customize these settings for a single endpoint or a set of endpoints using Customize Events in the current inventory table. The following tables describe the additional inventory details for: CTS, Cisco Codec, MX, E20, MXP, and Polycom Cisco TelePresence Movi Cisco Unified IP Phone 8900 and 9900 Series, and Cisco Cius CTMS CTS-Manager and TMS Cisco Unified CM MCU and MSE Cisco VCS Cisco TelePresence Conductor 14-4

5 CTS, Cisco Codec, MX, E20, MXP, and Polycom TelePresence Endpoint Data is displayed based on the endpoint type (CTS, Cisco Codec, MX, E20, MXP, or Polycom) that you have selected. Endpoint Name Directory Number Call Controller CUCM Address CUCM Cluster ID VCS Address VCS Cluster ID Registration Status Name assigned to the endpoint for ease of identification. IP phone details as defined in the endpoint. Hostname or IP address of the Cisco Unified CM server, where the endpoint is registered. Identification of the Cisco Unified CM cluster, where the Cisco Unified CM server is registered. Hostname or IP address of the VCS server where the endpoint is registered. Identification of the VCS cluster, where the VCS server is registered. Registration status of the endpoint with call processor (Cisco Unified CM or VCS). If Cisco Unified CM or VCS is not managed, the information displayed is N/A. H.323 ID configured on the Cisco Codec device. E164 number configured on the Cisco Codec device. H323 ID E164 No H323 Gatekeeper Address Network address of the gatekeeper to which the Cisco Codec is registered. SIP URI Registered SIP URI on the Cisco Codec device. SIP Proxy Address SIP proxy address that is configured manually on the Cisco Codec device. Application Manager CTSMAN Hostname or IP address of the application manager, where the CTS is integrated. TMS Hostname or IP address of the application manager, where the Cisco Codec is integrated. Switch Details Connected To Switch Details of the switch to which the endpoint is connected. Port Connected Details of the switch port to which the endpoint is connected. Peripherals Name Peripheral type, such as uplink, phone, camera, display, touch screen monitor, microphone. Position MAC Address Software Version Model Serial Make Firmware Version Hardware Version Midlet Version Note CTS systems support the TelePresence Touch Screen monitoring. Position of the peripheral, such as front_center for a microphone. MAC address of the peripheral. Software version running on the peripheral. Model of the peripheral. Serial number of the peripheral. Manufacturer s details for the peripheral. Firmware version of the peripheral. Hardware version of the peripheral. Midlet version running on the peripheral. 14-5

6 Note Prime CM does not support Peripherals details for Cisco TelePresence 150 MXP. Cisco TelePresence Movi Movi Endpoint Name Name assigned to the endpoint for ease of identification. SIP URI Registered SIP URI on the Cisco TelePresence Movi endpoint. VCS Address Hostname or IP address of the VCS, where the endpoint is registered. VCS Cluster ID Identification of the VCS cluster, where the VCS is registered. Cisco Unified IP Phone 8900 and 9900 Series, and Cisco Cius CUCM Endpoint Endpoint Name Name assigned to the endpoint for ease of identification. Model Model of the endpoint, such as CP-8945 or CP Directory Number IP phone details as defined in the endpoint. Serial Number Serial number of the endpoint. of the endpoint as defined in the call processor. Call Controller CUCM Address Hostname or IP address of the Cisco Unified CM server where the endpoint is registered. CUCM Cluster ID Identification of the Cisco Unified CM cluster where the Cisco Unified CM server is registered. Registration Status Registration status of the endpoint with call processor (Cisco Unified CM). If Cisco Unified CM is not managed, the information displayed is N/A. Network Configuration Data is displayed only for Cisco Cius endpoint. Switch Details Connected To Switch Port Connected Wi-Fi Details Status Default Router Access Point Name Ethernet Details Status Default Router Details of the switch to which the endpoint is connected. Details of the switch port to which the endpoint is connected. Displays the status of the wi-fi connection, such as connected or not connected. IP address used to manage the endpoint when connected using a wi-fi network. IP address of the default router to which the endpoint is connected. Name of the access point to which the endpoint is connected. Displays the status of the Ethernet connection, such as connected or not connected. IP address used to manage the endpoint when connected using Ethernet. IP address of the default router to which the endpoint is connected. 14-6

7 Note For discovery of Cisco Cius and Cisco Unified IP Phone 8900 and 9900 series, you must enable the HTTP interface. If the HTTP interface is not enabled, these devices will not appear in inventory table. CTMS Multipoint Switch Timezone Time zone configured on the multipoint switch. SKU Hardware Model Model number of the media convergence server on which the multipoint switch is running. Software Version Version of multipoint switch administration software currently installed. OS Version Operating System (OS) version. Hostname Hostname configured for the multipoint switch. IP address used to manage the multipoint switch. Subnet Mask Subnet mask used on the IP address. MAC Address MAC address of the media convergence server on which the multipoint switch software is running. This MAC address belongs to Ethernet interface 0 (the eth0 network interface card [NIC]). With failover, this MAC address persists, although another Ethernet interface becomes active. Switch Details Connected To Switch Port Connected Ad hoc Segments Maximum Segments Schedulable Details of the switch to which the multipoint switch is connected. Details of the switch port to which the multipoint switch is connected. Maximum number of segments that are available for impromptu meetings. The maximum number is 48. Total number of segments (individual video displays) that this multipoint switch can handle. The maximum number is 48. Number of segments available at any one time for scheduled meetings. The multipoint switch automatically derives this value by subtracting the defined number of Ad Hoc Segments from the defined number of Maximum Segments. 14-7

8 CTS-Manager and TMS Application Manager System Connectivity (see Note below) SKU Hardware Model Model number of the server on which the application manager is running. Software Version Version of administration software currently installed. OS Version Operating System (OS) version. Hostname Hostname configured for the application manager. IP address used to manage the application manager. Subnet Mask Subnet mask used on the IP address. MAC Address MAC address number supplied for the application manager. Exchange Server: These details are displayed only if the Calendaring service (Scheduling API mode) is configured in the CTS-Manager. Status Whether the exchange server is running or down. IP address assigned to the exchange server. Software Version Version of software currently installed on the exchange server. LDAP Server: These details are displayed only if the active directory is configured in the CTS-Manager. Status Software Version Whether the LDAP server is running or down. IP address assigned to the LDAP server. Version of software currently installed on the LDAP server. Note For CTS-Manager, the System Connectivity pane is visible only for CTS-Manager 1.7 and 1.8. Also, the CTS-Manager user configured in the Prime CM application must have administrative privilege in the CTS-Manager. Cisco Unified CM Call Processor Cluster ID Parameter that provides a unique identifier for the cluster. This parameter is used in call detail records (CDR), so collections of CDR records from multiple clusters can be traced to the sources. The default is StandAloneCluster. Publisher Hostname Hostname configured for the cluster publisher. Registered CTS Endpoints Number of registered endpoints on the call processor. Total CTS Endpoints Total number of endpoints. 14-8

9 MCU and MSE MCU or MSE Details Data is displayed based on the conferencing device (MCU or MSE) that you have selected. MSE Blades Data is displayed only for MSE. Hardware Model Model number of the media convergence server on which the multipoint switch is running. Serial Number Serial Number of the MCU Software Version Version of multipoint switch administration software currently installed. MCU Type/Device Type Type of the MCU/ Device. Build Version Build version of installed software. Manufacturer Manufacturer s name. Hostname Host name configured in the device (MCU or MSE). Local IP address of the MCU or MSE network interface used to access the MCU or MSE web user interface. Subnet Mask Subnet mask used on the IP address. MAC Address Fixed hardware MAC address of the ethernet port. Connected To Router IP address of the router to which the MCU or MSE is connected. Cluster Type Whether the cluster is a master or slave. If the cluster is configured, Not Configured is displayed. Total Video Ports Number of video ports configured in MCU. This is displayed only for MCU devices. Total Audio Ports Number of audio ports configured in MCU. This is displayed only for MCU devices. SIP (This is displayed only for MCU devices.) Status Whether the SIP registration is enabled or disabled. Proxy Network address of the SIP proxy. Domain Network address of the SIP registrar to which the MCU has registered. H323 (This is displayed only for MCU devices.) Status Whether the H.323 gatekeeper registration is enabled or disabled. Gatekeeper ID Identifier used by the MCU to register with the H.323 gatekeeper. Gatekeeper Address Network address of the gatekeeper to which the MCU has registered. Type Type of the blade. Slot Slot number. Slot 1 is MSE Supervisor, 2-10 are blades. Software Version Version of the software used. Status Status of the blade, OK or absent. Port A IP address of Port A. Port B IP address of Port B. 14-9

10 Cisco VCS Call Processor Cluster ID Cluster Name, which is used to identify one cluster of VCSs from another. Master Name of the VCS peer, which is configured as the cluster master. Registered Endpoints Number of endpoints registered to the VCS. Peers Number of VCS peers configured within the cluster. VCS Configuration Timezone Time zone that has been configured on the VCS. Maximum Traversal Calls Number of traversal call licenses available on the VCS. Maximum Non-Traversal Number of non-traversal call licenses available on the VCS. Calls Maximum Registrations Number of endpoints that can be registered with the VCS. Expressway Whether the VCS expressway is configured. Interworking Whether the VCS is configured to allow H.323 systems to connect to SIP systems. Encryption Whether the AES encryption is available in the software build. Find Me Whether the FindMe is enabled or disabled. Device Provisioning Whether the provisioning server is enabled on the VCS. Dual Network Interface Whether the LAN 2 interface on the VCS Expressway is enabled. Starter Pack Whether the Starter Pack option key is installed. Cisco TelePresence Conductor TelePresence Conductor Name Software Version Cluster Master Cluster Peers Total Registered MCUs Software ID Hardware Serial Number Hostname configured for the conductor. IP address of the conductor. Version of software currently installed. Name of the conductor peer, which is configured as the cluster master. Number of conductor peers configured within the cluster. Number of MCUs registered to the conductor. Identification of the software on the conductor. Serial number of the conductor hardware

11 Updating Inventory Registered MCUs Name Name of the MCU registered to the conductor. IP address of the MCU registered to the conductor. Type Type of the MCU registered to the conductor. Pool MCU pool to which the MCU belongs. Blacklisted Listed MCUs are not used by the conductor. Blacklisted Reason Reason why the MCUs are not used by the conductor. Media Load: Allocated/In Media load allocated, in use, and the maximum available. Use/ Max Available Signalled Load: Allocated/In Use/ Max Available Signalled load allocated, in use, and the maximum available. Note Only Cisco TelePresence Conductor controlled MCU cascading is supported. Updating Inventory The Update Inventory task helps you to synchronize the Prime CM inventory database with the network. During this task, the accessibility verification is not performed (see Figure 14-1). The Update Inventory task is performed for all devices managed in Prime CM. You cannot update the inventory for only a few selected devices. Perform the Update Inventory task, when there are any changes in the network devices interfaces. Perform the Discovery task, when there are any changes in the device configuration, such as software image update, changes in the first hop router configuration, and so forth. If there are any updates in the device credentials, you must run the discovery for that device after updating the Credentials profile. See Discovering Devices, page 12-1 to schedule a discovery job. Figure 14-1 Update Inventory Life Cycle Data Collection Managed Update inventory Unreachable Undiscoverable Check device connectivity (ICMP ping) Check device connectivity (SNMP/HTTP timeout)

12 Suspending and Resuming Managed Devices Chapter 14 We recommend that you define a periodic update inventory job to keep the Prime CM database up-to-date. To update inventory: Step 1 Step 2 Step 3 Step 4 Step 5 Choose Inventory > Device Inventory. The Device Inventory page appears. Click Update Inventory. The Refresh Inventory page appears. You can either schedule a periodic update inventory job or run the job immediately. If you want to run the job immediately, go to Step 5. Enter the job name. Enter the scheduling details: Start Time Select Start Time to enter the start date and time in the yyyy/mm/dd and hh:mm AM/PM format, respectively. Alternatively, you can click the date picker if you want to select the start date and time from the calendar. The time displayed is the client browser time. The scheduled periodic job runs at this specified time. Recurrence Select None, Hourly, Daily, Weekly, or Monthly to specify the job period. Settings Specify the details of the job period. End Time If you do not want to specify an end date/time, click No End Date/Time. Click End at to enter the end date and time in the yyyy/mm/dd and hh:mm AM/PM format, respectively. Click Run Now to immediately run the update inventory job, or click Schedule to schedule the periodic update inventory job at a later time. 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. Suspending and Resuming Managed Devices You can suspend a device that is in the Managed state. After the device is moved to the Suspended state, Prime CM does not monitor this device. That is, session, endpoint, and inventory details are not updated for the device in this state and alarms are not triggered for these devices. The following are behaviors for a device in the Suspended state: If a device is in the Suspended state, Prime CM does not poll the devices. If a suspended endpoint joins a new session, the endpoint is shown as Unknown in the Session Topology pane. If a suspended endpoint is already in an in-progress session, the endpoint icon (in the Session Topology pane) changes to Unknown, immediately after the endpoint state is changed to Suspended. If CTS-Manager is suspended, the new session data are not imported. The CTS-Manager polling is not performed. The existing session data (last polled data) is displayed in the Prime CM server. If Cisco Unified CM publisher is suspended, Prime CM does not poll the registered endpoints that belong to that corresponding Cisco Unified CM cluster

13 Managing Clusters If there are any active alarms, they are not cleared immediately. You can either manually clear the alarms or alarms will be automatically cleared, after it expires. By default it is 24 hours. No new alarms are triggered for a suspended device. If a suspended endpoint is already in a troubleshooting job, you cannot troubleshoot from the suspended endpoint. However, you can troubleshoot to the suspended endpoint. If a device is in a suspended state, the Endpoint Utilization report does not contain any data for this device. To suspend managed devices: Step 1 Step 2 Step 3 Step 4 Choose Inventory > Device Inventory. The Inventory page appears. Choose devices that are in the Managed state from the Current Inventory table. Click Suspend Management. A message appears, Selected devices suspended successfully. Click OK. The Current Inventory table refreshes with the updated device status. To resume managing a suspended device: Step 1 Step 2 Step 3 Choose the devices in the Suspended state from the Current Inventory table. Click Resume Management. A message appears, Selected devices resumed successfully. Click OK. The Current Inventory table refreshes with the updated device status. Managing Clusters Prime CM manages clusters or multiple servers for CTS-Manager or Cisco TMS only, to enable uninterrupted monitoring of the sessions, in case there is a failover in the CTS-Manager or Cisco TMS setup. A primary and secondary configuration is set up for the servers, so that if one instance goes down, another picks up. You must manually configure the primary, secondary, hot standby, and the load-balancer configuration. Prime CM manages multiple CTS-Manager or Cisco TMS, but imports sessions only from the primary CTS-Manager or Cisco TMS as per the configuration in the Manage Clusters page. Prime CM monitors only the application servers. It does not monitor the database instances. Health polling is performed for all the CTS-Manager or Cisco TMS application servers in the clusters. To manage clusters: Step 1 Choose Inventory > Device Inventory. The Device Inventory page appears

14 Exporting Inventory Chapter 14 Step 2 Step 3 Step 4 Step 5 Click Manage Clusters. The Manage Clusters window appears. Enter the Cluster Name and select the Cluster Type from the drop down menu. Enter the IP address of the Primary, Secondary, Hot Standby, and the Load-Balancer servers. The Primary Server IP address is mandatory. Click Add. New cluster is added. Click Update, if you change make changes to the existing cluster settings. To reset the cluster settings, click Add button on top of the Manage Clusters page. 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. Exporting Inventory You can export inventory details for endpoints and infrastructure devices (CTS-Manager, Cisco Unified CM, CTMS, Cisco TMS, and so on) using the Export Inventory button in the Inventory page. This exported data contains all endpoints and infrastructure devices in all device states (Managed, Unmanaged, and so on.) The exported data is available in the CSV format. See Viewing Inventory Details, page 14-1 to understand the exported inventory data details. The exported data does not include the device credentials details (Access Information). Deleting Devices You can delete devices that are in the Unknown, Unreachable, Inaccessible, Undiscoverable, Suspended, and Unsupported states. Devices in the Managed state cannot be deleted. After a device is deleted, it is not listed in the Current Inventory table, but the details are available in the Cisco Prime CM server. See Rediscovering Deleted Devices, page 12-9, to rediscover a deleted device. You can access the deleted device s details as part of the past session data. To delete a device: Step 1 Step 2 Step 3 Step 4 Choose Inventory > Device Inventory. The Device Inventory page appears. Choose the devices from the Current Inventory table. You can use the quick filter to get the list of devices in the desired state. Click Delete. A message appears, Selected devices deleted successfully. Click OK

15 Deleting Devices The Current Inventory table refreshes without the deleted devices

16 Deleting Devices Chapter