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

Imported Objects

ciscoMgmtCISCO-SMI
SnmpAdminStringSNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUPSNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32, Counter32, Gauge32, Integer32SNMPv2-SMI
TEXTUAL-CONVENTION, DateAndTime, TruthValueSNMPv2-TC

Type Definitions (2)

Name Base Type Values/Constraints
CldIndexUnsigned32range: 1..4294967295
CldSeverityEnumerationemergency(1), alert(2), critical(3), error(4), warning(5), notice(6), informational(7), debug(8)

Objects

ciscoLivedataMIB .1.3.6.1.4.1.9.9.814
ciscoLivedataMIBNotifs .1.3.6.1.4.1.9.9.814.0
ciscoLivedataMIBObjects .1.3.6.1.4.1.9.9.814.1
cldGeneral .1.3.6.1.4.1.9.9.814.1.1
cldServerName
.1.3.6.1.4.1.9.9.814.1.1.1
cldDescription
.1.3.6.1.4.1.9.9.814.1.1.2
cldVersion
.1.3.6.1.4.1.9.9.814.1.1.3
cldStartTime
.1.3.6.1.4.1.9.9.814.1.1.4
cldTimeZoneName
.1.3.6.1.4.1.9.9.814.1.1.5
cldTimeZoneOffset .1.3.6.1.4.1.9.9.814.1.1.6
cldEventNotifEnable
.1.3.6.1.4.1.9.9.814.1.1.7
cldCluster .1.3.6.1.4.1.9.9.814.1.2
cldClusterID
.1.3.6.1.4.1.9.9.814.1.2.1
cldClusterStatus .1.3.6.1.4.1.9.9.814.1.2.2
cldClusterAddress
.1.3.6.1.4.1.9.9.814.1.2.3
cldServices .1.3.6.1.4.1.9.9.814.1.3
cldServiceTable .1.3.6.1.4.1.9.9.814.1.3.1
cldServiceEntry .1.3.6.1.4.1.9.9.814.1.3.1.1
cldServiceIndex .1.3.6.1.4.1.9.9.814.1.3.1.1.1
cldServiceName
.1.3.6.1.4.1.9.9.814.1.3.1.1.2
cldServiceState .1.3.6.1.4.1.9.9.814.1.3.1.1.3
cldServiceUpTime
.1.3.6.1.4.1.9.9.814.1.3.1.1.4
cldReportingConnections .1.3.6.1.4.1.9.9.814.1.4
cldReportingConnectionTable .1.3.6.1.4.1.9.9.814.1.4.1
cldReportingConnectionEntry .1.3.6.1.4.1.9.9.814.1.4.1.1
cldRptConnIndex .1.3.6.1.4.1.9.9.814.1.4.1.1.1
cldRptConnMessagesDiscarded
.1.3.6.1.4.1.9.9.814.1.4.1.1.10
cldRptConnDSCP .1.3.6.1.4.1.9.9.814.1.4.1.1.11
cldRptConnServerID
.1.3.6.1.4.1.9.9.814.1.4.1.1.2
cldRptConnServerAddress
.1.3.6.1.4.1.9.9.814.1.4.1.1.3
cldRptConnState .1.3.6.1.4.1.9.9.814.1.4.1.1.4
cldRptConnStateTime
.1.3.6.1.4.1.9.9.814.1.4.1.1.5
cldRptConnEventRate
.1.3.6.1.4.1.9.9.814.1.4.1.1.6
cldRptConnHeartbeatRTT
.1.3.6.1.4.1.9.9.814.1.4.1.1.7
cldRptConnSocketConnects
.1.3.6.1.4.1.9.9.814.1.4.1.1.8
cldRptConnSocketDisconnects
.1.3.6.1.4.1.9.9.814.1.4.1.1.9
cldEvents .1.3.6.1.4.1.9.9.814.1.5
cldEventTable .1.3.6.1.4.1.9.9.814.1.5.1
cldEventEntry .1.3.6.1.4.1.9.9.814.1.5.1.1
cldEventIndex .1.3.6.1.4.1.9.9.814.1.5.1.1.1
cldEventID .1.3.6.1.4.1.9.9.814.1.5.1.1.2
cldEventAppName
.1.3.6.1.4.1.9.9.814.1.5.1.1.3
cldEventName
.1.3.6.1.4.1.9.9.814.1.5.1.1.4
cldEventState .1.3.6.1.4.1.9.9.814.1.5.1.1.5
cldEventSeverity .1.3.6.1.4.1.9.9.814.1.5.1.1.6
cldEventTimestamp
.1.3.6.1.4.1.9.9.814.1.5.1.1.7
cldEventText
.1.3.6.1.4.1.9.9.814.1.5.1.1.8
ciscoLivedataMIBConform .1.3.6.1.4.1.9.9.814.2
ciscoLivedataMIBCompliances .1.3.6.1.4.1.9.9.814.2.1
ciscoLivedataMIBGroups .1.3.6.1.4.1.9.9.814.2.2

Notifications/Traps

NameOIDDescription
cldEventNotif








.1.3.6.1.4.1.9.9.814.0.1
ntity 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.