Cisco Cisco Unified Contact Center Enterprise 9.0(1)
Serviceability Best Practices Guide for Unified ICM/Unified CCE & Unified CCH
©2012 Cisco Systems, Inc.
38
The CISCO-CONTACT-CENTER-APPS-MIB is structured as follows:
Figure 13: CISCO-CONTACT-CENTER-APPS-MIB Structure
The Instance table is indexed by the instance number – a value ranging from 1 to 25.
The Component table is indexed by Instance, and Component number that is arbitrarily assigned
by the agent; the value of the Component number could change from one run period to another.
by the agent; the value of the Component number could change from one run period to another.
The Component Element table is indexed by Instance, Component number, and Component
Element number, which is arbitrarily assigned by the agent; the value of the Component Element
number could change from one run period to another.
Element number, which is arbitrarily assigned by the agent; the value of the Component Element
number could change from one run period to another.
Each component-specific table of instrumentation is indexed by Component number.
From an inventory standpoint (a network management station taking inventory of the server
itself), the Network Management Station (NMS) first polls the Instance table. Typically, for the
Unified CCE, there is only one instance. From that, the NMS polls all components that are part of
this instance. Now the NMS knows what is installed on this server and can see what is running.
For example, this is a Unified CCE central controller and the NMS wants to know what the
inbound call rate is. With the Component entry for the Router, using the Component index of that
entry, the NMS then polls the cccaRouterCallsPerSec object within the Router table (indexed by
Instance number and Component index).
itself), the Network Management Station (NMS) first polls the Instance table. Typically, for the
Unified CCE, there is only one instance. From that, the NMS polls all components that are part of
this instance. Now the NMS knows what is installed on this server and can see what is running.
For example, this is a Unified CCE central controller and the NMS wants to know what the
inbound call rate is. With the Component entry for the Router, using the Component index of that
entry, the NMS then polls the cccaRouterCallsPerSec object within the Router table (indexed by
Instance number and Component index).
Additional inventory can be accomplished by drilling a little deeper. For example, assume the
NMS wants to list what PIMs are installed on PG4A. Again, poll the Instance table to get the
instance number. Using that, get all components for that instance. Find PG4A and using the
component index for PG4A, get the PG table objects for PG4A. Then get the PIM table for PG4A
that returns a list of PIMs installed.
NMS wants to list what PIMs are installed on PG4A. Again, poll the Instance table to get the
instance number. Using that, get all components for that instance. Find PG4A and using the
component index for PG4A, get the PG table objects for PG4A. Then get the PIM table for PG4A
that returns a list of PIMs installed.
Instance
Component
Component Element
Base Objects
Router
NIC
Logger
DistAW
PG
PIM
CG
CTI OS
CampaignMgr
Dialer