CISCO-MMODAL-CONTACT-APPS-MIB
The CISCO-MMODAL-CONTACT-APPS-MIB provides SNMP instrumentation for the Cisco Unified Expert Advisor (CUEA) services within the Multi-Modal Contact Applications (MMCA) cluster, exposing runtime statistics for individual services and defining notification formats for the Intelligent Contact Management (ICM) environment. This module enables monitoring of service-specific performance counters and operational states across Runtime and Reporting nodes to facilitate troubleshooting of call routing, agent availability, and contact lifecycle management.
Imported Objects
Objects
306 total| Object Name |
|---|
ciscoMmodalContactAppsMIB MODULE-IDENTITY .1.3.6.1.4.1.9.9.664 |
ciscoMmodalContactAppsMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.664.0 |
cmmcaMIBEvent NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.664.0.1 |
ciscoMmodalContactAppsMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.664.1 |
cmmcaGeneralInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.664.1.1 |
cmmcaServerNamero InetAddressDNS (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.664.1.1.1 |
cmmcaDescriptionro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.2 |
cmmcaVersionro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.3 |
cmmcaStartTimero DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.664.1.1.4 |
cmmcaTimeZoneNamero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.5 |
cmmcaTimeZoneOffsetHoursro Integer32 (-12..12) UNITS "hours" .1.3.6.1.4.1.9.9.664.1.1.6 |
cmmcaTimeZoneOffsetMinutesro Integer32 (-59..59) UNITS "minutes" .1.3.6.1.4.1.9.9.664.1.1.7 |
cmmcaOpsConsoleURLro CiscoURLString (CISCO-TC) .1.3.6.1.4.1.9.9.664.1.1.8 |
cmmcaLocalDeviceTypero Enumeration .1.3.6.1.4.1.9.9.664.1.1.9 |
cmmcaEnableNotificationsrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.664.1.1.10 |
cmmcaSystemConditionStatusro CmmcaSystemConditionStatus .1.3.6.1.4.1.9.9.664.1.1.11 |
cmmcaSystemStatusro CmmcaServiceStatus .1.3.6.1.4.1.9.9.664.1.1.12 |
cmmcaClusterInfoTable SEQUENCE OF CmmcaClusterInfoEntry .1.3.6.1.4.1.9.9.664.1.1.13 |
cmmcaClusterInfoEntry CmmcaClusterInfoEntry .1.3.6.1.4.1.9.9.664.1.1.13.1 |
cmmcaDeviceIndex Integer32 .1.3.6.1.4.1.9.9.664.1.1.13.1.1 |
cmmcaDeviceNamero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.13.1.2 |
cmmcaDeviceDescriptionro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.13.1.3 |
cmmcaDeviceTypero Enumeration .1.3.6.1.4.1.9.9.664.1.1.13.1.4 |
cmmcaDeviceStatusro Enumeration .1.3.6.1.4.1.9.9.664.1.1.13.1.5 |
cmmcaDeviceInetAddressTypero InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.664.1.1.13.1.6 |
cmmcaDeviceInetAddressro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.664.1.1.13.1.7 |
cmmcaClusterIdro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.13.1.8 |
cmmcaNextNodeTable SEQUENCE OF CmmcaNextNodeEntry .1.3.6.1.4.1.9.9.664.1.1.14 |
cmmcaNextNodeEntry CmmcaNextNodeEntry .1.3.6.1.4.1.9.9.664.1.1.14.1 |
cmmcaNextNodeIndex Integer32 .1.3.6.1.4.1.9.9.664.1.1.14.1.1 |
cmmcaNextNodeNamero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.14.1.2 |
cmmcaNextNodeTypero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.14.1.3 |
cmmcaNextNodeIpAddrTypero InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.664.1.1.14.1.4 |
cmmcaNextNodeIpAddrro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.664.1.1.14.1.5 |
cmmcaNextNodeStatusro CmmcaNextNodeStatus .1.3.6.1.4.1.9.9.664.1.1.14.1.6 |
cmmcaSystemConditionTable SEQUENCE OF CmmcaSystemConditionEntry .1.3.6.1.4.1.9.9.664.1.1.15 |
cmmcaSystemConditionEntry CmmcaSystemConditionEntry .1.3.6.1.4.1.9.9.664.1.1.15.1 |
cmmcaSystemConditionIndex Integer32 .1.3.6.1.4.1.9.9.664.1.1.15.1.1 |
cmmcaSystemConditionIdro Integer32 .1.3.6.1.4.1.9.9.664.1.1.15.1.2 |
cmmcaSystemConditionSeverityro CmmcaConditionStatus .1.3.6.1.4.1.9.9.664.1.1.15.1.3 |
cmmcaSystemConditionDescriptionro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.15.1.4 |
cmmcaSystemConditionTimeStampro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.664.1.1.15.1.5 |
cmmcaSystemConditionMessagero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.1.15.1.6 |
cmmcaLicenseInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.664.1.2 |
cmmcaRtLicensesAvailablero Gauge32 UNITS "agents" .1.3.6.1.4.1.9.9.664.1.2.1 |
cmmcaTotalLicensesConfiguredro Gauge32 UNITS "agents" .1.3.6.1.4.1.9.9.664.1.2.2 |
cmmcaThreadPool OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.664.1.3 |
cmmcaTPoolRtIdleThreadsro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.3.1 |
cmmcaTPoolRtRunningThreadsro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.3.2 |
cmmcaTPoolRtCoreThreadsro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.3.3 |
cmmcaTPoolRtMaxThreadsAvailro Unsigned32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.3.4 |
cmmcaTPoolRtMaxThreadsUsedro Counter32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.3.5 |
cmmcaRuntimeInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.664.1.4 |
cmmcaEnvRtMaxMemUsedro CounterBasedGauge64 UNITS "bytes" .1.3.6.1.4.1.9.9.664.1.4.1 |
cmmcaEnvRtCurrMemUsedro CounterBasedGauge64 UNITS "bytes" .1.3.6.1.4.1.9.9.664.1.4.2 |
cmmcaEnvRtMaxMemAvailro CounterBasedGauge64 UNITS "bytes" .1.3.6.1.4.1.9.9.664.1.4.3 |
cmmcaEnvRtCurrMemAvailro CounterBasedGauge64 UNITS "bytes" .1.3.6.1.4.1.9.9.664.1.4.4 |
cmmcaEnvRtCurrThreadsInUsero Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.4.5 |
cmmcaEnvMaxThreadsUsedro Unsigned32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.4.6 |
cmmcaEnvRtUpTimero Counter64 UNITS "milliseconds" .1.3.6.1.4.1.9.9.664.1.4.7 |
cmmcaRtMsgQMemPercentUsagero Gauge32 UNITS "percentage" .1.3.6.1.4.1.9.9.664.1.4.8 |
cmmcaMaxMsgQMemAvailro CounterBasedGauge64 UNITS "bytes" .1.3.6.1.4.1.9.9.664.1.4.9 |
cmmcaRtCongestedro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.664.1.4.10 |
cmmcaServices OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.664.1.5 |
cmmcaServiceTable SEQUENCE OF CmmcaServiceEntry .1.3.6.1.4.1.9.9.664.1.5.1 |
cmmcaServiceEntry CmmcaServiceEntry .1.3.6.1.4.1.9.9.664.1.5.1.1 |
cmmcaServiceIndex CmmcaIndex .1.3.6.1.4.1.9.9.664.1.5.1.1.1 |
cmmcaServiceTypero CmmcaServiceType .1.3.6.1.4.1.9.9.664.1.5.1.1.2 |
cmmcaServiceNamero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.5.1.1.3 |
cmmcaServiceStatusro CmmcaServiceStatus .1.3.6.1.4.1.9.9.664.1.5.1.1.4 |
cmmcaServiceIntPeriodro Gauge32 .1.3.6.1.4.1.9.9.664.1.5.1.1.5 |
cmmcaRtRoutingDomainro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.5.1.1.6 |
cmmcaRtLogLevelro CmmcaSeverityLevel .1.3.6.1.4.1.9.9.664.1.5.1.1.7 |
cmmcaRtTraceMaskro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.664.1.5.1.1.8 |
cmmcaRtMessageThroughputro Gauge32 UNITS "messages per second" .1.3.6.1.4.1.9.9.664.1.5.1.1.9 |
cmmcaRtUptimero Counter64 UNITS "seconds" .1.3.6.1.4.1.9.9.664.1.5.1.1.10 |
cmmcaRtMsgReceivedro Counter64 UNITS "messages" .1.3.6.1.4.1.9.9.664.1.5.1.1.11 |
cmmcaMaxThreadsAvailablero Unsigned32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.5.1.1.12 |
cmmcaRtThreadsInUsero Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.664.1.5.1.1.13 |
cmmcaServiceInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.664.1.6 |
cmmcaRmTable SEQUENCE OF CmmcaRmEntry .1.3.6.1.4.1.9.9.664.1.6.1 |
cmmcaRmEntry CmmcaRmEntry .1.3.6.1.4.1.9.9.664.1.6.1.1 |
cmmcaRmRtAgentsLoggedInro Gauge32 UNITS "agents" .1.3.6.1.4.1.9.9.664.1.6.1.1.1 |
cmmcaRmRtAgentsOnCallsro Gauge32 UNITS "agents" .1.3.6.1.4.1.9.9.664.1.6.1.1.2 |
cmmcaRmRtAgentsReservedro Gauge32 UNITS "agents" .1.3.6.1.4.1.9.9.664.1.6.1.1.3 |
cmmcaRmRtAgentsWrapUpro Gauge32 UNITS "agents" .1.3.6.1.4.1.9.9.664.1.6.1.1.4 |
cmmcaRmRtAgentsReadyro Gauge32 UNITS "agents" .1.3.6.1.4.1.9.9.664.1.6.1.1.5 |
cmmcaRmRtAgentsNoQueuero Gauge32 UNITS "agents" .1.3.6.1.4.1.9.9.664.1.6.1.1.6 |
cmmcaRmAggNumOffersAcceptro Counter64 UNITS "offers" .1.3.6.1.4.1.9.9.664.1.6.1.1.7 |
cmmcaRmIntNumOffersAcceptro Gauge32 UNITS "offers" .1.3.6.1.4.1.9.9.664.1.6.1.1.8 |
cmmcaRmAggNumOffersRejectro Counter64 UNITS "offers" .1.3.6.1.4.1.9.9.664.1.6.1.1.9 |
cmmcaRmIntNumOffersRejectro Gauge32 UNITS "offers" .1.3.6.1.4.1.9.9.664.1.6.1.1.10 |
cmmcaRmAggNumOffersTimedOutro Counter64 UNITS "offers" .1.3.6.1.4.1.9.9.664.1.6.1.1.11 |
cmmcaRmIntNumOffersTimedOutro Gauge32 UNITS "offers" .1.3.6.1.4.1.9.9.664.1.6.1.1.12 |
cmmcaCmTable SEQUENCE OF CmmcaCmEntry .1.3.6.1.4.1.9.9.664.1.6.2 |
cmmcaCmEntry CmmcaCmEntry .1.3.6.1.4.1.9.9.664.1.6.2.1 |
cmmcaCmRtNumActiveCallsro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.664.1.6.2.1.1 |
cmmcaCmRtNumCallTryingro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.664.1.6.2.1.2 |
cmmcaCmRtNumCallRingBackro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.664.1.6.2.1.3 |
cmmcaCmRtNumCallConnectingro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.664.1.6.2.1.4 |
CISCO-MMODAL-CONTACT-APPS-MIB Technical Reference Overview
The CISCO-MMODAL-CONTACT-APPS-MIB SNMP MIB module published by Cisco defines 306 managed OID objects, including 266 scalar/column metrics, 13 SNMP tables, and 1 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.664. Key tabular structures include cmmcaRmTable, cmmcaCmTable, cmmcaRdaTable, cmmcaBreTable, cmmcaWaTable, cmmcaMpaTable. Monitored SNMP traps/notifications include cmmcaMIBEvent.
Key OID Definitions in CISCO-MMODAL-CONTACT-APPS-MIB
.1.3.6.1.4.1.9.9.664The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is a highly scalable, modular, extensible, open and secure platform for providing contact center applications. The Cisco Unified Expert Advisor (CUEA) is implemented on this platform. The Cisco Unified Expert Advisor application is deployed on multiple devices that form a cluster, where each device could be classified as 'Runtime' or 'Reporting'. Each device hosts a set of services and each service performs a specific task. Not all services will be running on every device. The CISCO-MMODAL-CONTACT-APPS-MIB defines the instrumentation of the services present in the Cisco Unified Expert Advisor. The MIB mainly consists of the run-time statistics of each service and also defines a Notification format. It also defines various groups of objects that are not specific to a service. DEFINITION OF TERMS AND ACRONYMS ACD Automatic Call Distributor ACMI Advanced Contact Management Interface. The interface used by the ICM to talk to generic peripherals. Also known as GED-188 Agent An Agent, also known as Expert Advisor, is a person in the enterprise who is capable of handling calls from CUEA AQ Assignment Queue Assignment Queue Assignment Queues allow Cisco Unified ICM to route call requests to groups of expert advisors. Various experts may qualify for various assignment queues based on the assignment queue membership rules, and they then log in or out of, as well as change their availability with respect to those assignment queues. An expert advisor who is available on a given assignment queue is able to be considered by the Work Assigner to receive calls according to the assignment queue's selection strategy. Attribute Definition Attributes Definitions are used by assignment queues and expert advisors. Attributes are defined by CUEA administrators and assigned to assignment queues and expert advisors. Expert advisors are routed call requests if the expert advisor's skills and attributes match those of the Assignment Queue. B2BUA Back to back user agent CM Contact Manager Contact A Contact is the internal object that represents an internal call. The Contact is created when the call arrives at CUEA, and does not terminate until the caller disconnects CTI Computer Telephony Integration CTI-OS Computer Telephony Integration - Object Server CUEA Cisco Unified Expert Advisor CUCM Cisco Unified Communications manager CUPS Cisco Unified Presence server CVP Customer Voice Portal DNIS Dialed Number Identification service ERS Enterprise Routing Services. The ERS Peripheral Gateway is a generic interface for the ICM to connect to an ACD. It exposes the ACMI protocol GED188 The ICM CTI Server/Client interface specification ICM Intelligent Contact Management ICMGW Intelligent Contact Management Gateway ICMPG ICM Peripheral Gateway IM Instant Messaging JVM Java Virtual Machine MMCA Multi Modal Contact Applications MPA Media Platform adapter MPI Media Platform Interface PG Peripheral Gateway. The Peripheral Gateway is how the ICM talks to any ACD. PIM Peripheral Information Manager. The PIM is a component of the ICM Peripheral Gateway that handles the ACD specific communication. RA Reporting Adapter RDA Resource Desktop adapter RDI Resource desktop interface RM Resource Manager RS Reporting subsystem Selection Strategy The strategy by which the Work Assigner should assign Expert Advisors to contacts. SIP Session Initiation Protocol Skills Skills are classifications for expert advisor abilities, general knowledge, and expertise. Skills may be defined by Expert Advisor administrators, and then assigned to individual experts. An expert may have multiple skills, and a competency level from 1 to 100 in each. SIMPLE SIP for Instant Messaging and Presence Leveraging Extensions WA Work Assigner.
.1.3.6.1.4.1.9.9.664.1.6.1This table describes the Resource Manager (RM) Service instances configured on this Device. The Resource Manager (RM) is responsible for maintaining the state of assignable resources, e.g. agents. The RM interfaces to the Work Assigner, Media Platform Interface, Resource Desktop Adapter and Business Rules Engine. Resource state is a function of information obtained from the actual resource and a rule set. Each RM only participates with in a single routing domain, and therefore only talks to a single Work Assigner. Each RM is also tied to a single MPA, and one or more RDAs that are dedicated to the RM. The BRE can be shared with other components (other RMs, and other CMs) This table has a sparse dependent relationship with the cmmcaServiceTable and hence uses the index of that table.
.1.3.6.1.4.1.9.9.664.1.6.2This table describes CM instances configured on this Device. The Contact Manager (CM) service is responsible for the handling of call requests and maintaining contact state. Instances may load share as well as support different types of contacts. This service is a critical funnel point to the rest of the system. CM uses BRE to help direct call flow decision making. The CM must be able to transparently scale and provide for fault tolerance. This is best modeled as the CM receiving work from a virtual queue. The CM only participates within a single routing domain, and therefore only talks to a single Work Assigner. Each CM is also tied to a single MPA. The BRE used by the CM can be shared among components (both CMs and RMs). This table has a sparse dependent relationship with the cmmcaServiceTable and hence uses its index.
.1.3.6.1.4.1.9.9.664.1.6.3This table lists all Resource Desktop Adapter services configured on this Device. The Resource Desktop Adapter (RDA) is used by the RM to communicate to the user interface of the Resource (or Agent). This component provides a normalized interface (RDI-Resource desktop interface) to the Resource Manager that removes the differences between communicating to different types of desktops (such as CTIOS, Presence, Web Based, etc) or Resources (such as occasional or traditional agents). This type of communication typically includes requests like: - Log In or Log Out a resource from the desktop - Set the presence state of the desktop to a particular state - Show a precall message to the resource - Offer a task to the resource and get a response Each RDA is tied to a single Resource Manager, but each Resource Manager may talk to many RDAs. This table has a sparse dependent relationship with cmmcaServiceTable and hence uses its index.
.1.3.6.1.4.1.9.9.664.1.6.4This table describes the Business Rules Engine (BRE) services configured on this Device. The Business Rules Engine in MMCA allows customers to define how the system will behave and then execute scripts or business rules at runtime. In Cisco Unified Expert Advisor application, a very limited Business Rules Engine will be needed. It will be required only to run pre-configured basic agent scripts and contact scripts (queue to a given skill group and then connect the call). The following features are required of the BRE: - Start a script - Select a single AQ for a contact to be queued to, or a multiple AQs for a resource to be made available. - Request Resource - Direct Call Control Requests to Client (CM) - Receive and Handle Call Events (leg terminated, etc.) - Receive and change individual agent availability This table has a sparse dependent relationship with Service Table and hence uses its index.
.1.3.6.1.4.1.9.9.664.1.6.5This table lists the Work Assigner(WA) Service instances configured on this Device. The Work Assigner is responsible for matching Contacts that need Resources with Resources that need Contacts. The scope of a single work assigner defines a Routing Domain. A Routing Domain is a set of Contacts and a set of Resources that can be assigned to each other. This means that the size of a routing domain is constrained by how scalable a Work Assigner can be. Because of this, the Work Assigner tries to be as streamlined as possible and delegate all logic that deals with the scope of an individual resource or individual contact to the RM or the CM. Work Assigner is not the only interface that is used to communicate between the RM and the CM, it merely provides the initial assignment between the two , much in the same manner as a SIP connects two endpoints, and then gets out of the call. The Work Assigner also includes the logic to execute advanced routing features (such as resume routing, spatial routing, etc). This table has a sparse dependent relationship with cmmcaServiceTable and hence is indexed by cmmcaServiceIndex.
.1.3.6.1.4.1.9.9.664.1.6.6This table describes MPA services configured on this Device. The Media Platform Adapter is a media platform for SIP calls: - SIP Back to Back User Agent (B2BUA), providing basic 3rd party call control and endpoint functions to its clients (RM, CM, RDA). - Used by both RM and CM for handling calls. A single Media Platform Interface(MPI) can support multiple clients (such as a RM, a CM and a RDA), SIP based MPIs will always be co-located with its clients. This table has a sparse dependent relationship with cmmcaServiceTable and hence uses its index.
.1.3.6.1.4.1.9.9.664.1.6.7This table describes Reporting Adapter (RA) services configured on this Device. Reporting adapters listen to event stream that are produced by runtime components. They then take those events, convert them as appropriate (for example, converting them to a particular version of a schema or applying a security policy of what data can be sent to the reporting database) and then send a new message to the Reporting Subsystem service. This message is sent using durability and persistence to ensure that the message will get to the Reporting Subsystem (RS). Reporting Adapters run on the same Device as the runtime components that they are monitoring. This is because the events that are being produced are delivered on a best-effort basis, and being on the same Device (and in the same JVM) ensures that the adapter will receive the event. This table has a sparse dependent relationship with cmmcaServiceTable and hence uses its index.
.1.3.6.1.4.1.9.9.664.1.6.8This table describes Reporting Subsystem(RS) services configured on this Device. Reporting Subsystem (RS) receives reporting messages from Reporting Adapter(s) (RA(s)) and writes historical data into the database. Configuration data will be replicated from run-time Devices to Reporting Database. End users are provided with a set of report templates to generate historical reports which consist of both historical data and configuration data. This table has a sparse dependent relationship with cmmcaServiceTable and hence uses its index.
.1.3.6.1.4.1.9.9.664.1.6.9This table describes ICM Gateway(ICMGW) services configured on this Device. The ICM Gateway talks to the ERS PG of ICM over the GED-188 (ACMI) protocol. It sends agent state information to the ICM so that the ICM knows whether or not to route calls to Cisco Unified Expert Advisor and if so to which skill groups, i.e. assignment queues. Another critical function is to allow translation routing of calls from ICM and getting call context information from those calls into CUEA. Unlike a conventional ACD, the ICM Gateway doesnt track individual calls and generate every call event to the PIM. Instead, it relays agent status events to the ERS PG, and the PG is then able to fabricate real-time agent/skill-group reports and sends to the ICM Central Controller. The ICM Gateway also forwards call termination details to the PG and based on those the modified OPC at the PG can create half-hour reports. This table has a sparse dependent relationship with cmmcaServiceTable and hence uses its index.
.1.3.6.1.4.1.9.9.664.1.5.1This table lists all functional services that make up Cisco Unified Expert Advisor (CUEA) application. Each service performs a specific task. The various services are Contact Manager(CM), Resource Manager (RM), Work Assigner (WA), Media Platform Adapter (MPA), Business Rules Engine (BRE), ICMGateway (ICMGW), Resource Desktop Adapter (RDA), Reporting Adapter(RA) and Reporting Subsystem (RS). Note that, not all services will be found on all Devices. There could be potentially multiple instances of each service (identified by CmmcaServiceType) running on the same Cisco Unified Expert Advisor Device. Each service is given a unique service index by the SNMP agent upon startup and this same index is used in other sparsely dependent tables, specifically cmmcaServiceInfo tables (viz; cmmcaRmTable, cmmcaCmTable, cmmcaRdaTable, cmmcaBreTable, cmmcaWaTable, cmmcaMpaTable, cmmcaRaTable, cmmcaRsTable and cmmcaIcmgwTable) based on cmmcaServiceType. For eg: All service entries with cmmcaServiceType 'cm' will have entries in cmmcaCmTable, and all service entries with cmmcaServiceType 'rm' will have entries in cmmcaRmTable and so on. This table is read-only for an NMS and is populated by SNMP agent upon startup. It cannot be modified during runtime.
.1.3.6.1.4.1.9.9.664.1.1.13CUEA can consist of multiple devices that form a cluster. This table gives the information related to the CUEA Cluster. Each entry denotes a Device within the Cluster.
.1.3.6.1.4.1.9.9.664.1.1.14This table gives the information related to the neighbouring nodes that are connected to the device. Each entry denotes a node connected to the device.
.1.3.6.1.4.1.9.9.664.1.1.15This table lists all the Raised System Conditions in the application. A service can be inService ,but could raise certain important System Conditions, which provide more information about the health of service.
.1.3.6.1.4.1.9.9.664.0.1An event is a notification that is sent by a functional service of the CUEA application. Notifications are sent by CUEA when unusual conditions occur that potentially, can affect the functioning of a service in CUEA. Each Notification describes the operation state information of a service when such service impacting conditions occur.
.1.3.6.1.4.1.9.9.664.1.7.1The event message ID is the unique notification message identifier that was assigned by the CUEA application. This identifier is unique for each different notification but consistent for each instance of the same notification.
.1.3.6.1.4.1.9.9.664.1.7.2The event host name object specifies the host name or the fully qualified domain name of the CUEA server from which this event originated.
.1.3.6.1.4.1.9.9.664.1.7.3The event application name object specifies the service-specific name of the functional service that generated this notification. This name will vary, both in content and in format, based on the service that generated the notification. For example, the name for the first CM service may be CUEA_CM1 while the third MPA service name may be CUEA_MPA3. By convention, the application version number shall appear in the application name as well, thus the second CM service application name for Cisco Unified Expert Advisor version 1.0 will be CUEA_1_0_CM2.
.1.3.6.1.4.1.9.9.664.1.7.4The event message name object specifies the service-specific name of the Expert Advisor service notification message. This name will vary, both in content and in format, based on the event itself. The object value is used to group and correlate similar notifications.
.1.3.6.1.4.1.9.9.664.1.7.5The event state object identifies the state (not to be confused with severity) of the notification and potentially the current state of the functional component that generated the notification. The possible states are: 'raise': A raise state identifies a notification received as a result of a health-impacting condition, such as a process failure. A subsequent clear state notification will follow when the error condition is resolved. 'clear': The clear state indicates that the condition which generated a previous raise notification has been resolved.
.1.3.6.1.4.1.9.9.664.1.7.6The event severity object indicates the severity level of this notification. The severity levels are: 'emergency': The notification indicates that a devastating failure has occurred; the system or service is unusable. Immediate operator intervention is required. 'alert': The notification indicates that a devastating failure is imminent that will render the system unusable. Immediate operator attention is necessary. 'critical': The notification indicates that a service impacting failure is likely to occur soon; an error has occurred that was not appropriately handled by the system. Operator attention is needed as soon as possible. 'error': The notification contains important operational state information and may indicate that the system has experienced a temporary impairment or an error that was appropriately handled by the system. An operator should review the notification soon to determine if action is needed. 'warning': The notification contains important operational state information that may be a precursor to an error occurrence. An operator should review the notification soon to determine if action is needed. 'notice': The notification contains health or operational state information that may be pertinent to the health of the system but does not require the attention of the administrator at this time. 'informational': The notification contains interesting system-level information that is valuable to an administrator, however, the event itself does not indicate a failure or impairment condition. 'debug': The notification provides supplemental information that may be beneficial toward diagnosing or resolving a problem but does not in itself provide operational health status.
.1.3.6.1.4.1.9.9.664.1.7.7The event time stamp object specifies the date and time that the notification was generated on the originating device.
.1.3.6.1.4.1.9.9.664.1.7.8The event text is the full text of the notification. This text includes a description of the event that was generated, component state information and potentially a brief description of administrative action that may be necessary to correct the condition that caused the event to occur.
.1.3.6.1.4.1.9.9.664.1.4.1The real-time maximum memory used object is a real-time snapshot metric indicating the peak memory usage by the application within the runtime environment since startup. The object value is expressed as a count of bytes and indicates the high water mark of memory used simultaneously within the environment.
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.
The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.
The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.
SNMP MIB module
The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.
The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.