Cisco Prime Collaboration Device Management Guide, 9.0
Managing Inventory
Downloads: This chapterpdf (PDF - 338.0KB) The complete bookPDF (PDF - 1.85MB) | Feedback

Managing Inventory

Table Of Contents

Managing Inventory

Viewing Inventory Details

Device-specific Inventory Details

Updating and Collecting Inventory Details

Updating Inventory

Collecting Inventory Details

IP Phone Discovery Schedule

IP Phone XML Discovery Schedule

Phone Lines Report

Exporting Device Inventory

Suspending and Resuming Managed Devices

Deleting Devices


Managing Inventory


Cisco Prime Collaboration maintains continuous, real-time discovery of device inventory. You need to periodically update the inventory so that you have up-to-date information of your network.

When you update inventory, the inventory synchronizes with the Prime Collaboration database. The Prime Collaboration inventory reflects every addition, deletion, and modification that occurs in the collaboration network after update. You can schedule how often you want to update inventory.

Viewing Inventory Details

In Prime Collaboration, devices are grouped based on the device type. The Device Group pane is available in the Device Work Center, Session Diagnostics (as a filter), Endpoint Diagnostics, 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.

Other than the inventory table, the Device Work Center page contains System Information, Access Information, Interface Information, and Event Settings panes that appear below the inventory table. All these panes are populated based on the last polled data. The device must be in Managed state at least once so that these details are displayed.

Inventory Table

You can view the Inventory table on the Device Work Center page (Choose Operate > Device Work Center).

Each device that is managed by Prime Collaboration 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.

To select multiple devices (first 500 entries), use the check box available on the top left corner of the Current Inventory pane.

You can change the event settings of the devices using the Customize Events option.

You can change the visibility settings of the devices using the Edit option. This is enabled only for endpoints, predefined groups and userdefined groups. The visibility settings of the device can be changed only if the device is in the Managed state. Any change in visibility settings appear in the Session Diagnostics page. For more information, see the Cisco Prime Collaboration Network Monitoring, Reporting and Diagnostics Guide. You can suspend and resume the management of the device using Suspend and Resume. Inventory is not updated for devices in the Suspended state.

You can use the show drop-down list on the inventory table to filter devices based on the device type and state.

For example, if you want to rediscover all deleted devices in your network, select Deleted from the show drop-down list. The inventory table will list all deleted devices. Perform rediscovery to discover these devices.

There are options such as Quick Filters, Advanced Filters to filter devices based on the device criteria. See Managing Device Groups.

The Total field in the upper right corner of the inventory table displays the device count. To view the number of devices in a group, select the group.

For example, to view the number of phone endpoints, select the Endpoints group in Device Group. The number of endpoints will be updated in the Total field. For more information on the device count, see Assurance Inventory Summary.

Table 6-1 describes all the fields on the Inventory table.

Table 6-1 Current Inventory Table 

Field
Description

Endpoint Name

Name assigned to the endpoint for ease of identification.

Host Name

Name assigned to the device for ease of identification.

Device Type

Device type with the manufacturer's name, such as Switch, CTS.

Device Model

Device model, such as Catalyst3506G48PS.

IP Address

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 Type

Software running on the device, such as IOS, CatOS.

Software Version

Software version running on the device.

State

Prime Collaboration managed device status.

Last Discovered

Date and time the device was last discovered.

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.

For more information see the Cisco Prime Collaboration 9.0 Network Monitoring, Reporting, and Diagnostics Guide.

Customized Events

Green check mark displayed—Indicates event settings is customized for the device using Customize Events tab.

Green check mark not displayed—Indicates event settings is not customized for the device. The device uses global settings.

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.


System Information

The System Information pane contains the credential details for all devices except the TelePresence Server:

Field
Description

Object ID

System Object ID of the endpoint.

Up Time

Duration for which the device has been running.

Contact

Contact details of the endpoint.

Location

System location of the endpoint.

Primary Capability

Primary service running on the device.

Capabilities

All other services (other than primary service) running on the device.


Detailed Device View

Detailed Device View opens a detailed view of the device (as a popup window). This is available as a link in the System Information pane.

In the Detailed Device View, you can do the following:

View hardware and software information on system, environment, connectivity, and interface

components

View hardware and software information on subcomponents of aggregate devices

View application status for Cisco Unified CM, Voice Services, Work Flow, and Synthetic Tests and so on.

Suspend or resume management of a device or a device component so the device is no longer polled, or polling is resumed.

Launch other tools such as performance graphs, Diagnostic View, and so on.

Diagnostic View

You can view the important statistics and details of this and other network management applications that are installed on your network management server, on a single page instead of navigating through several pages to view the required data.

In the Device Work Center page, the Detailed Device View and Diagnostic View links are available only for the voice network devices such as Cisco Unified CM, Cisco Unity Connection, Cisco Unified Presence, Voice Gateway, and so on. These views are not available for video network devices (such as Cisco VCS, TelePresence and so on) and phone endpoints.

For more information, see the Cisco Prime Collaboration 9.0 Network Monitoring, Reporting, and Diagnostics Guide.

Access Information

The Access Information pane contains the following details for all devices:

Field
Description

Credential Profile Name

Credential profile used for the selected device while discovery.

SNMP Access Level

Read Only is displayed, if you have defined the SNMP credentials in the Credential Profiles.

SNMP Version

Defined SNMP version in the Credential Profiles.

CLI Access Level

If you have defined the CLI credentials, Prime Collaboration 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 Collaboration.

HTTP Access Level

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 Collaboration.

JTAPI Access Level

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 Collaboration.


Interface Information

The Interface Information pane contains the following details for CTS, Cisco Codec, CTMS, Cisco MCU, Cisco MSE, and Cisco TelePresence Server.

Field
Description

Physical Address

Physical address of the device.

Name

Name of the device.

Type

Type of the device.

MTU

Maximum transmission unit. Maximum packet size, in bytes, that this interface can handle.

Speed

Speed of the device in Mbps.

CDP

Whether the CDP is enabled (True) or disabled (False.)

Operational Status

Operational state of the device.

Admin

Administrative status of the interface.


Event Settings

The Event Settings pane contains the following details for endpoints and infrastructure devices.

Field
Description
Sessions

Name

Packet loss, jitter, and/or latency for which the threshold values are set.

Minor Threshold

Displays threshold values for minor alarms.

Major Threshold

Displays threshold values for major alarms.

Critical Threshold

Displays threshold values for critical alarms.

Enabled

Event enabled or disabled.

Automatic Troubleshooting

If enabled, displays event severity.

Endpoints

Category

Categories such as endpoint and service infrastructure.

Alarm Condition

Condition defined for the alarm to trigger.

Enabled

Event enabled or disabled.

Severity

Displays the severity: Critical, Major, or Minor.


The default threshold values are set for Rx packet loss, jitter, and/or latency for all endpoints. To view Default Event Settings and to customize values, see the Cisco Prime Collaboration Fault Management Guide.

You can further customize these settings for a single endpoint or a set of endpoints using Customize Events in the current inventory table. See the Cisco Prime Collaboration 9.0 Fault Management Guide.

Assurance Inventory Summary

Inventory Summary lists the count of devices based on the device state. The total column displays the total number of devices in a particular state. The device count is available as a cross-launch to the Inventory table in Device Work Center. When you click on any count, you will be directed to the Inventory table where you can see all the devices in that particular state.

Inventory Summary is available as a slider at the bottom of your UI browser. You can view the details when you scroll over.

The count for Unknown IP Phones is provided separately. Unknown IP Phones include the total number of phones that are not registered with Cisco Unified CM for more than 24 hours, or yet to be registered by Cisco Unified CM.

The Mass endpoints column excludes the phone count.


Note Although, the total count column is the sum of Infrastructure devices, Mass endpoints and Telepresence endpoints columns put together for each device state, you may see some inconsistency in the number of devices in the total count column. This is because, the computation of the total count column may also include Unknown device types from the inventory.


Inventory Summary is refreshed after every 30 seconds to display the most current data.

Device-specific Inventory Details

The following tables describe the additional inventory details for:

CTS, Cisco Codec, MX, E20, MXP, and Polycom

Cisco Jabber for TelePresence Video (Movi)

Cisco Unified IP Phone 8900 and 9900 Series, and Cisco Cius

CTMS

CTS-Manager and Cisco TMS

Cisco Unified CM

Cisco MCU and MSE

Cisco VCS

Cisco TelePresence Conductor

CTS, Cisco Codec, MX, E20, MXP, and Polycom

Field
Description
TelePresence Endpoint

Data is displayed based on the endpoint type (CTS, Cisco Codec, MX, E20, MXP, or Polycom) that you have selected.

Endpoint Name

Name assigned to the endpoint for ease of identification.

Directory Number

IP phone details as defined in the endpoint.

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.

VCS Address

Hostname or IP address of the VCS server where the endpoint is registered.

VCS Cluster ID

Identification of the VCS cluster, where the VCS server is registered.

Registration Status

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.

H323 ID

H.323 ID configured on the Cisco Codec device.

E164 No

E164 number configured on the Cisco Codec device.

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.

Note CTS systems support the TelePresence Touch Screen monitoring.

Position

Position of the peripheral, such as front_center for a microphone.

MAC Address

MAC address of the peripheral.

Software Version

Software version running on the peripheral.

Model

Model of the peripheral.

Serial

Serial number of the peripheral.

Make

Manufacturer's details for the peripheral.

Firmware Version

Firmware version of the peripheral.

Hardware Version

Hardware version of the peripheral.

Midlet Version

Midlet version running on the peripheral.



Note Prime Collaboration does not support Peripheral details for Cisco TelePresence 150 MXP.


Cisco Jabber for TelePresence Video (Movi)

Field
Description
Movi

Endpoint Name

Name assigned to the endpoint for ease of identification.

SIP URI

Registered SIP URI on the Cisco Jabber for TelePresence Video (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

Field
Description
CUCM Endpoint

Endpoint Name

Name assigned to the endpoint for ease of identification.

Model

Model of the endpoint, such as CP-8945 or CP-9971.

Directory Number

IP phone details as defined in the endpoint.

Serial Number

Serial number of the endpoint.

Description

Description 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.

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.

Network Configuration

Data is displayed only for Cisco Cius endpoint.

Wi-Fi Details

Status

Displays the status of the wi-fi connection, such as connected or not connected.

IP Address

IP address used to manage the endpoint when connected using a wi-fi network.

Default Router

IP address of the default router to which the endpoint is connected.

Access Point Name

Name of the access point to which the endpoint is connected.

Ethernet Details

Status

Displays the status of the Ethernet connection, such as connected or not connected.

IP Address

IP address used to manage the endpoint when connected using Ethernet.

Default Router

IP address of the default router to which the endpoint is connected.



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 the inventory table.


For Cisco Cius devices, the standard phone description available in the inventory is SEP and MAC address.

CTMS

Field
Description
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

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

Details of the switch to which the multipoint switch is connected.

Port Connected

Details of the switch port to which the multipoint switch is connected.

Ad hoc Segments

Maximum number of segments that are available for impromptu meetings. The maximum number is 48.

Maximum Segments

Total number of segments (individual video displays) that this multipoint switch can handle. The maximum number is 48.

Schedulable

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.


CTS-Manager and Cisco TMS

Field
Description
Application Manager

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

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.

System Connectivity (see Note below)
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

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

Whether the LDAP server is running or down.

IP Address

IP address assigned to the LDAP server.

Software Version

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 Collaboration application must have administrative privilege in the CTS-Manager.


Cisco Unified CM

Field
Description
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.


Cisco MCU and MSE

Field
Description
MCU or MSE Details

Data is displayed based on the conferencing device (MCU or MSE) that you have selected.

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).

IP Address

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.

H.323 (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.

MSE Blades

Data is displayed only for MSE.

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

IP address of Port A.

Port B IP Address

IP address of Port B.


Cisco VCS

Field
Description
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 Calls

Number of non-traversal call licenses available on the VCS.

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.



Note Prime Collaboration manages both Cisco VCS application and appliance.


Cisco TelePresence Conductor

Field
Description
TelePresence Conductor

Name

Hostname configured for the conductor.

IP Address

IP address of the conductor.

Software Version

Version of software currently installed.

Cluster Master

Name of the conductor peer, which is configured as the cluster master.

Cluster Peers

Number of conductor peers configured within the cluster.

Total Registered MCUs

Number of MCUs registered to the conductor.

Software ID

Identification of the software on the conductor.

Hardware Serial Number

Serial number of the conductor hardware.

Registered MCUs

Name

Name of the MCU registered to the conductor.

IP Address

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 Use/ Max Available

Media load allocated, in use, and the maximum 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 and Collecting Inventory Details

Updating and collecting inventory details depend on the type of network deployed—voice, video or both. Also, depends on the data you want to collect at a given point. Table 6-2 recommends when to update inventory based on your network.

Table 6-2 Recommendation for Updating Inventory 

Description
Task

If you have both voice and video endpoints deployed in your network, and want to collection data on both

Perform Update Inventory (Choose Operate > Device Work Center > Update Inventory). For more information, see Updating Inventory.

If you have both voice and video endpoints deployed in your network, and you want to collect data on video endpoints only

Perform Update Inventory (Choose Operate > Device Work Center > Update Inventory). For more information, see Updating Inventory.

If you have both voice and video endpoints, and you want to collect data on voice endpoints only

Perform IP Phone Inventory Collection and Cluster Data Discovery (Choose Administration > System Setup > Assurance Setup). For more information, see Collecting Inventory Details.

If you have only voice network

Perform IP Phone Inventory Collection and Cluster Data Discovery (Choose Administration > System Setup > Assurance Setup). For more information, see Collecting Inventory Details.

If you have only video network

Perform Update Inventory (Choose Operate > Device Work Center > Update Inventory). For more information, see Updating Inventory.


Updating Inventory

The Update Inventory task helps you to synchronize the Prime Collaboration inventory database with the network. During this task, the accessibility verification is not performed (see Figure 6-1).

Perform the Update Inventory task, when:

You want to synchronize database for all devices managed in your network. You cannot update the inventory for only a few selected devices.

You want to define a periodic update inventory job to keep the Prime Collaboration database up-to-date

There are any changes in the network devices interfaces.


Note Any new devices added to the network will not be identified.


Figure 6-1 Update Inventory Life Cycle

We recommend that you define a periodic update inventory job to keep the Prime Collaboration database up-to-date.

To update inventory:


Step 1 Choose Operate > Device Work Center..

Step 2 In the Device Work Center page, click Update Inventory.

The Update Inventory window appears.

Step 3 If you want to update inventory based on the device status, check the Update devices based on device criteria check box.

Device status—You can rediscover devices that are in Inaccessible, Unreachable, Undiscoverable, Unknown, Deleted, and Unsupported states.

If you choose to update the inventory based on device status, then accessibility information check is performed. If you do not, then inventory gets updated with all devices in Managed state. Device accessibility is not checked.

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.

Step 4 Enter the job name and 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.

Step 5 Click Run Now to immediately run the update inventory job, or click Schedule to schedule the periodic update inventory job at a later time.

If you click Run Now, the job in progress window appears. You can check the status of your job by clicking progress details.

You can check the status of the job using the Discovery Jobs button on the Device Work Center page. The Job Management page appears with the list of discovery jobs. For more information, see Verifying Discovery Status.


Collecting Inventory Details

Prime Collaboration supports on-demand inventory update for the managed devices. It collects data from managed devices and updates the information about the devices themselves and the phones registered with managed devices.

Eveyr addition, deletion, and modification of phones, XML phones and clusters are reflected in the inventory.

There are separate inventory collection schedules for phones and clusters. For details on cluster discovery, see Cluster Data Discovery Settings.

You cannot create additional schedules. You can only edit the existing schedule. For phones, you can create multiple inventory collection schedules.


Note You can schedule periodic discovery of only Cisco Unified CM clusters. Only phones registered with these clusters are discovered. For more information, see Cluster Data Discovery Settings.


As Prime Collaboration performs inventory collection of phones and Cisco Unified CM clusters, they pass through various device states until they are fully recognized by Prime Collaboration (see Device States for details).

You can specify how often to collect information about the phone and clusters that are managed in Inventory Collection.

To schedule Inventory Collection, choose Administration > System Setup > Assurance Setup. For an overview of the inventory collection tasks, see Table 6-3.

Table 6-3 Inventory Collection Overview

Task
Description

Schedule inventory collection of IP Phones

In the IP Phone Discovery Schedule page (Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings), you can add, edit, or delete the IP phone discovery schedules. (See IP Phone Discovery Schedule.)

Schedule inventory collection of Phone XML

In the IP Phone XML Discovery Schedule page (Administration > System Setup > Assurance Setup  > IP Phone XML Inventory Collection Settings), you can schedule phone XML discovery. See IP Phone XML Discovery Schedule.)

Schedule inventory collection of cluster devices

In the Cluster Data Discovery page (Administration > System Setup > Assurance Setup  > Cluster Data Discovery Settings), you can add, edit, or delete the cluster device discovery schedules. (See Cluster Data Discovery Settings.


IP Phone Discovery Schedule

When you choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings, you can perform the following tasks:

Viewing IP Phone Collection Status

Adding an IP Phone Discovery Schedule

Editing an IP Phone Discovery Schedule

Deleting an IP Phone Discovery Schedule

Viewing IP Phone Collection Status

To view the IP Phone collection status, choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings.

The IP Phone Discovery Schedule page appears.

The IP Phone Collection Status pane displays the following:

Collection Status—Displays the status of the discovery process. The status could be any one of the following:

In progress—When you start PIFServer for the first time or restart it, discovery takes place automatically and the status appears as In Progress.

Complete—The discovery process is complete.

Not available. Try after some time—Appears when you start PIFServer for the first time, or restart it, and the discovery process has not yet begun.

Last Collection Start Time—Displays the start time of the last discovery.

Last Collection End Time—Displays the end time of the last discovery.

Adding an IP Phone Discovery Schedule

Prime Collaboration provides six default schedules for phone discovery. You can update or delete them; you can also add up to 10 phone discovery schedules.

To add an IP Phone schedule:


Step 1 Choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings.

The IP Phone Discovery Schedule page appears.

Step 2 Click Add.

The Add Schedule dialog box appears.

Step 3 Enter the following:

Name for the discovery schedule

Day of the week when you want discovery to occur

Time of the day when you want discovery to occur

Step 4 Click OK.


Editing an IP Phone Discovery Schedule

To edit an IP Phone discovery schedule:


Step 1 Choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings.

Step 2 In the IP Phone Discovery page, select the phone discovery schedule that you want to edit.

Step 3 Click Edit.

Step 4 In the Edit Discovery Schedule dialog box, you can change the following:

Name of the discovery schedule

Day of the week when you want discovery to occur

Time of the day when you want discovery to occur

Step 5 Click OK.

Step 6 After all your changes are done, click Apply.


Deleting an IP Phone Discovery Schedule

To delete an IP Phone discovery schedule:


Step 1 Choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings.

The IP Phone Discovery Schedule page appears.

Step 2 Click Delete. In the confirmation box, click Yes to confirm.


IP Phone XML Discovery Schedule

To schedule when phone discovery should take place, you can use the Phone XML Collection page. The default scheduled start for phone XML discovery is daily at 3 p.m. Phone XML discovery collects serial number, load ID, and App ID for each phone.

To view and schedule an Phone XML discovery status:


Step 1 Choose Administration > System Setup > Assurance Setup  > IP Phone XML Inventory Collection Settings.

The Phone XML Collection page appears. See Table 6-4.

Step 2 Click Apply to accept any scheduling changes.

Step 3 In the confirmation box, click OK.


Table 6-4 Phone XML Field Description

Field
Description

Collection Status

Status of current collection process. States include: complete, pending, and scheduled.

Last Collection Start Time

Date and time when the last performed phone discovery started.

Last Collection End Time

Date and time when the last performed phone discovery stopped.

Phone XML Collection Schedule

Enables you to change the default 3 p.m. data collection.


Table 6-4 describes Phone XML fields.

Phone Lines Report

Phone Lines display a consolidated list of voice and video endpoints in your network (choose Operate > Device Work Center > Phone Lines). This report is updated based on the IP Phone discovery. To schedule IP Phone discovery choose Administration > System Setup > Assurance Setup  > IP Phone Inventory Collection Settings. For more information, see IP Phone Discovery Schedule.

By default, Phone Lines display: Extension, Phone Description, IP Address, MAC Address, Model, Regd., CM/CME Address, Switch Address, Port, Device Pool, Partition Name, and Status Reason Code. You can hide any of the default columns and select other columns of data to be displayed using the Column Filter option.

For individual reports, that is, for a report on voice phones/lines choose Report > Interactive Reports > Inventory Reports > Audio Phones/Lines. For a report on video phones and lines choose Report > Interactive Reports > Inventory Reports > Audio Phones/Lines. For more information on phone reports, see the Cisco Prime Collaboration 9.0 Network Monitoring, Reporting, and Diagnostics Guide.

Exporting Device 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 option on the Device Work Center page. This exported data contains details such as MAC address, Software version, devices in all device states (Managed, Unmanaged, and so on. This file will not contain any credential information.

The exported data is available in the CSV format.

See Viewing Inventory Details to understand the exported inventory details. The exported data does not include the device credential profiles.

To export device information to a file:


Step 1 Choose Operate > Device Work Center > Export.

The Export dialog box appears. You have options to export device list and credentials, and device inventory.

Step 2 Select Device Inventory, and enter a name for the output file.

Only CSV file format is supported.

Step 3 Click Export.

Save the .csv file on your local system.


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 Collaboration 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 Collaboration 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 Collaboration server.

If Cisco Unified CM publisher is suspended, Prime Collaboration does not poll the registered endpoints that belong to that corresponding Cisco Unified CM cluster.

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 Choose Operate > Device Work Center.

Step 2 From the Current Inventory table, select devices that are in the Managed state.

Step 3 Click Suspend.

A message appears, Selected devices suspended successfully.

Step 4 Click OK. The Current Inventory table refreshes with the updated device status.


To resume managing a suspended device:


Step 1 Choose the devices in the Suspended state from the Current Inventory table.

Step 2 Click Resume.

A message appears, Selected devices resumed successfully.

Step 3 Click OK. The Current Inventory table refreshes with the updated device status.


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 Prime Collaboration server.

See Rediscovering Devices, 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 Choose Operate > Device Work Center.

Step 2 From the Current Inventory table, select devices you want to delete.

You can use the quick filter to get the list of devices in the desired state.

Step 3 Click Deleted.

A message appears, Selected devices deleted successfully.

Step 4 Click OK. The Current Inventory table refreshes without the deleted devices.



Note You cannot delete phones directly from the inventory using the delete option. Phones are deleted automatically when the clusters with which they are registered are deleted. The inventory gets updated only after a rediscovery is performed.