Cisco Cisco Unified Contact Center Enterprise 9.0(1)
Serviceability Best Practices Guide for Unified ICM/Unified CCE & Unified CCH
©2012 Cisco Systems, Inc.
37
3.3.2
CISCO-CONTACT-CENTER-APPS-MIB Structure
At the base, tables in the CISCO-CONTACT-CENTER-APPS-MIB are indexed by the Unified
CCE instance (the instance name is a unique textual identifier that relates components that are
part of the same Unified CCE system); most are secondarily indexed by the Component index. In
a hosted deployment, there may be up to 25 instances of a particular component installed on a
single server (such as a router – one for each customer instance in a service provider solution).
This is why the Unified CCE instance is the primary index – it is the only way to distinguish one
router from another. However, in a typical Unified CCE deployment, there is only a single
instance.
CCE instance (the instance name is a unique textual identifier that relates components that are
part of the same Unified CCE system); most are secondarily indexed by the Component index. In
a hosted deployment, there may be up to 25 instances of a particular component installed on a
single server (such as a router – one for each customer instance in a service provider solution).
This is why the Unified CCE instance is the primary index – it is the only way to distinguish one
router from another. However, in a typical Unified CCE deployment, there is only a single
instance.
Thus, to inventory a particular server, the NMS should query the Instance table first; then query
the Component table to assign components to an instance. Lastly, query the Component Elmt
table for the processes associated with each component.
the Component table to assign components to an instance. Lastly, query the Component Elmt
table for the processes associated with each component.
Using the Instance and Component indexes, the NMS can then drill down further using it to query
the component-specific instrumentation for each component installed.
the component-specific instrumentation for each component installed.
The component-specific table of instrumentation provides (where possible) links to dependent
components that are distributed within the solution (for example, which Router a peripheral
gateway communicates with or which Logger is the primary for a particular Administration
Server and Real-time Data Server).
components that are distributed within the solution (for example, which Router a peripheral
gateway communicates with or which Logger is the primary for a particular Administration
Server and Real-time Data Server).