CISCO-LIVEDATA-MIB

        Cisco LiveData is the next generation reporting product for
Cisco Unified Contact Center Enterprise (CCE).  Cisco
LiveData provides a horizontally scalable, highly available
architecture to support systems with large numbers of
reporting users.  LiveData enables fast refresh rates on
real-time data (3 seconds or less).  A LiveData node consumes
real-time data streams from one or more sources, processes
the data and publishes the resulting data to solution
consumers.  Consumers may be database management systems,
applications or reporting engines.
        
Cisco LiveData aggregates and publishes real-time data and
metrics pushed to it (e.g. from the CCE router and/or
peripheral gateway components) to a message bus; Cisco
Unified Intelligence Center (CUIC) and the CCE Administrator
Workstation (AW) subscribe to this message bus to receive
real-time data updates.  CUIC users then build reports using
this real-time data; other CCE clients may also query this
real-time data from the CCE AW database.
        
A LiveData cluster consists of one or more nodes; one is
designated as the master with additional worker nodes as
needed.  A LiveData cluster may have a remote peer cluster
that works cooperatively in a fault-tolerant model.  LiveData
cluster peers communicate with one another to negotiate who
is the 'active' cluster and who is on 'standby' (only one
cluster will be active at a time).  If the active cluster
fails, the standby cluster will transition to active and
begin consuming the data streams previously consumed by the
peer cluster.
        
In small deployments, a LiveData cluster will be collocated
with CUIC in the same server virtual machine; in larger
deployments, a LiveData cluster may include several nodes
that may or may not be collocated with CUIC.
        
A single node in a LiveData cluster will have multiple
services running in the guest virtual machine that are
critical to the successful function of that node.  Services
may be distributed across the nodes of a cluster to balance
the workload.  Each node will establish and maintain
connections to data sources in the solution.
        
CISCO-LIVEDATA-MIB defines instrumentation unique to the
LiveData servers (virtual machines). The instrumentation
includes objects of:
    1) a general nature - attributes of the device and
       application,
    2) cluster status* and identity,
    3) service status and identity and
    4) connection status and attributes (including metrics).
    5) events
        
* It is important to note that cluster status is shared
across all nodes of a cluster; cluster status is not
device-specific unless there is only one node in the cluster.
        
The MIB also defines a single notification type; all nodes in
all clusters may emit notifications.
        
Service and connection instrumentation is exposed as tables.
The number of entries within each table may change over time,
adapting to changes within the cluster. 
        
Glossary:
---------
AW         Administrator Workstation component of a Cisco
           Unified Contact Center Enterprise deployment.  The
           AW collects and serves real-time and configuration
           data to the CCE solution.
CCE        (Cisco Unified) Contact Center Enterprise; CCE
           delivers intelligent contact routing, call
           treatment, network-to-desktop computer telephony
           integration, and multichannel contact management
           over an IP infrastructure.
CUIC       Cisco Unified Intelligence Center; CUIC is a web-
           based reporting application that provides real-
           time and historical reporting in an easy-to-use,
           wizard-based application for Cisco Contact Center
           products.
UCCE       Unified Contact Center Enterprise; see 'CCE'.
    
Source file
CISCO-LIVEDATA-MIB
Last revised
Identity
ciscoLivedataMIB
Base OID
1.3.6.1.4.1.9.9.814
Imported Objects
CISCO-SMI ciscoMgmt
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Gauge32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DateAndTime TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-LIVEDATA-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LIVEDATA-MIB::ciscoLivedataMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LIVEDATA-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LIVEDATA-MIB::ciscoLivedataMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (50)
.1.3.6.1.4.1.9.9.814
.1.3.6.1.4.1.9.9.814.0
.1.3.6.1.4.1.9.9.814.1
.1.3.6.1.4.1.9.9.814.1.1
.1.3.6.1.4.1.9.9.814.1.1.1
.1.3.6.1.4.1.9.9.814.1.1.2
.1.3.6.1.4.1.9.9.814.1.1.3
.1.3.6.1.4.1.9.9.814.1.1.4
.1.3.6.1.4.1.9.9.814.1.1.5
.1.3.6.1.4.1.9.9.814.1.1.6
.1.3.6.1.4.1.9.9.814.1.1.7
.1.3.6.1.4.1.9.9.814.1.2
.1.3.6.1.4.1.9.9.814.1.2.1
Enumeration
.1.3.6.1.4.1.9.9.814.1.2.2
.1.3.6.1.4.1.9.9.814.1.2.3
.1.3.6.1.4.1.9.9.814.1.3
.1.3.6.1.4.1.9.9.814.1.3.1
.1.3.6.1.4.1.9.9.814.1.3.1.1
.1.3.6.1.4.1.9.9.814.1.3.1.1.1
.1.3.6.1.4.1.9.9.814.1.3.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.814.1.3.1.1.3
.1.3.6.1.4.1.9.9.814.1.3.1.1.4
.1.3.6.1.4.1.9.9.814.1.4
.1.3.6.1.4.1.9.9.814.1.4.1
.1.3.6.1.4.1.9.9.814.1.4.1.1
.1.3.6.1.4.1.9.9.814.1.4.1.1.1
.1.3.6.1.4.1.9.9.814.1.4.1.1.10
.1.3.6.1.4.1.9.9.814.1.4.1.1.11
.1.3.6.1.4.1.9.9.814.1.4.1.1.2
.1.3.6.1.4.1.9.9.814.1.4.1.1.3
Enumeration
.1.3.6.1.4.1.9.9.814.1.4.1.1.4
.1.3.6.1.4.1.9.9.814.1.4.1.1.5
.1.3.6.1.4.1.9.9.814.1.4.1.1.6
millisecondsSNMPv2-SMIGauge32
.1.3.6.1.4.1.9.9.814.1.4.1.1.7
.1.3.6.1.4.1.9.9.814.1.4.1.1.8
.1.3.6.1.4.1.9.9.814.1.4.1.1.9
.1.3.6.1.4.1.9.9.814.1.5
.1.3.6.1.4.1.9.9.814.1.5.1
.1.3.6.1.4.1.9.9.814.1.5.1.1
.1.3.6.1.4.1.9.9.814.1.5.1.1.1
.1.3.6.1.4.1.9.9.814.1.5.1.1.2
.1.3.6.1.4.1.9.9.814.1.5.1.1.3
.1.3.6.1.4.1.9.9.814.1.5.1.1.4
Enumeration
.1.3.6.1.4.1.9.9.814.1.5.1.1.5
.1.3.6.1.4.1.9.9.814.1.5.1.1.6
.1.3.6.1.4.1.9.9.814.1.5.1.1.7
.1.3.6.1.4.1.9.9.814.1.5.1.1.8
.1.3.6.1.4.1.9.9.814.2
.1.3.6.1.4.1.9.9.814.2.1
.1.3.6.1.4.1.9.9.814.2.2
Dependencies (5) 5 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-CONFrfc
  4. SNMPv2-TCrfc
  5. SNMP-FRAMEWORK-MIBrfc
  6. CISCO-LIVEDATA-MIBciscoselected
Type Definitions (2)
Unsigned32 range: 1..4294967295
Enumeration
emergency(1)
alert(2)
critical(3)
error(4)
warning(5)
notice(6)
informational(7)
debug(8)
Conformance Groups (6)
The general group defines the general Cisco LiveData
objects. All servers will populate these objects.
.1.3.6.1.4.1.9.9.814.2.2.1
The cluster group defines the Cisco LiveData objects related
to the cluster of LiveData servers. All servers will populate
these objects.
.1.3.6.1.4.1.9.9.814.2.2.2
The services group defines the Cisco LiveData service table
objects. All servers will populate these objects, however,
the number of entries in the table will vary across servers
and the types of services will vary as well.
.1.3.6.1.4.1.9.9.814.2.2.3
The reporting connections group defines the Cisco LiveData
connection table objects. All servers will populate these
objects, however, the number of entries in the table will
vary across servers.
.1.3.6.1.4.1.9.9.814.2.2.4
The events group defines the Cisco LiveData event table
objects. All servers will populate these objects, however,
the number of entries in the table will vary across servers.
.1.3.6.1.4.1.9.9.814.2.2.5
This group defines the notification types defined in this
MIB.
.1.3.6.1.4.1.9.9.814.2.2.6
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.814.2.1.1
This object is the compliance statement for entities which
implement the Cisco LiveData MIB.
Required groups
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.9.814.0.1
The SNMP entity generates cldEventNotif when an unusual
condition has occurred that can potentially affect the
functioning of the Cisco LiveData server. This notification
type describes operational state information of the service
generating the notification when such service-impacting
conditions occur. A notification is sent by a functional
service of the Cisco LiveData server.
The notification type includes the following objects:

'cldEventID': The unique numeric event message
identifier for this event.

'cldServerName': The fully-qualified domain name of the
Cisco LiveData server that generated the
notification.

'cldEventAppName': The name of the Cisco LiveData
functional service that generated this
event.

'cldEventName': The service-specific name of the Cisco
LiveData event message.

'cldEventState': The state of the event, either 'raise'
or 'clear'. A 'raise' state event is
generated when an unusual or service-
impacting condition occurs while a
'clear' state event is generated when
a prior condition has been resolved.

'cldEventSeverity': The severity level of this event; an
integer value from 1 (emergency) to 8
(debug).

'cldEventTimestamp': The date and time that the event was
generated.

'cldEventText': The full text of the event.