1-- *****************************************************************
2-- CISCO-LIVEDATA-MIB.my
3-- Cisco (Unified) LiveData MIB file.
4-- Copyright (c) 2005-2006, 2013 by Cisco Systems Inc.
5-- All rights reserved.
6-- *****************************************************************
7
8CISCO-LIVEDATA-MIB DEFINITIONS ::= BEGIN
9
10IMPORTS
11    MODULE-IDENTITY,
12    OBJECT-TYPE,
13    NOTIFICATION-TYPE,
14    Unsigned32,
15    Counter32,
16    Gauge32,
17    Integer32
18        FROM SNMPv2-SMI
19    MODULE-COMPLIANCE,
20    NOTIFICATION-GROUP,
21    OBJECT-GROUP
22        FROM SNMPv2-CONF
23    TEXTUAL-CONVENTION,
24    DateAndTime,
25    TruthValue
26        FROM SNMPv2-TC
27    SnmpAdminString
28        FROM SNMP-FRAMEWORK-MIB
29    ciscoMgmt
30        FROM CISCO-SMI;
31
32
33ciscoLivedataMIB MODULE-IDENTITY
34    LAST-UPDATED    "201308290000Z"
35    ORGANIZATION    "Cisco Systems, Inc."
36    CONTACT-INFO
37            "Cisco Systems
38            Customer Service
39
40            Postal: 170 W Tasman Drive
41            San Jose, CA  95134
42            USA
43
44            Tel: +1 800 553-NETS
45
46            E-mail: cs-snmp@cisco.com"
47    DESCRIPTION
48        "Cisco LiveData is the next generation reporting product for
49        Cisco Unified Contact Center Enterprise (CCE).  Cisco
50        LiveData provides a horizontally scalable, highly available
51        architecture to support systems with large numbers of
52        reporting users.  LiveData enables fast refresh rates on
53        real-time data (3 seconds or less).  A LiveData node consumes
54        real-time data streams from one or more sources, processes
55        the data and publishes the resulting data to solution
56        consumers.  Consumers may be database management systems,
57        applications or reporting engines.
58
59        Cisco LiveData aggregates and publishes real-time data and
60        metrics pushed to it (e.g. from the CCE router and/or
61        peripheral gateway components) to a message bus; Cisco
62        Unified Intelligence Center (CUIC) and the CCE Administrator
63        Workstation (AW) subscribe to this message bus to receive
64        real-time data updates.  CUIC users then build reports using
65        this real-time data; other CCE clients may also query this
66        real-time data from the CCE AW database.
67
68        A LiveData cluster consists of one or more nodes; one is
69        designated as the master with additional worker nodes as
70        needed.  A LiveData cluster may have a remote peer cluster
71        that works cooperatively in a fault-tolerant model.  LiveData
72        cluster peers communicate with one another to negotiate who
73        is the 'active' cluster and who is on 'standby' (only one
74        cluster will be active at a time).  If the active cluster
75        fails, the standby cluster will transition to active and
76        begin consuming the data streams previously consumed by the
77        peer cluster.
78
79        In small deployments, a LiveData cluster will be collocated
80        with CUIC in the same server virtual machine; in larger
81        deployments, a LiveData cluster may include several nodes
82        that may or may not be collocated with CUIC.
83
84        A single node in a LiveData cluster will have multiple
85        services running in the guest virtual machine that are
86        critical to the successful function of that node.  Services
87        may be distributed across the nodes of a cluster to balance
88        the workload.  Each node will establish and maintain
89        connections to data sources in the solution.
90
91        CISCO-LIVEDATA-MIB defines instrumentation unique to the
92        LiveData servers (virtual machines). The instrumentation
93        includes objects of:
94            1) a general nature - attributes of the device and
95               application,
96            2) cluster status* and identity,
97            3) service status and identity and
98            4) connection status and attributes (including metrics).
99            5) events
100
101        * It is important to note that cluster status is shared
102        across all nodes of a cluster; cluster status is not
103        device-specific unless there is only one node in the cluster.
104
105        The MIB also defines a single notification type; all nodes in
106        all clusters may emit notifications.
107
108        Service and connection instrumentation is exposed as tables.
109        The number of entries within each table may change over time,
110        adapting to changes within the cluster.
111
112        Glossary:
113        ---------
114        AW         Administrator Workstation component of a Cisco
115                   Unified Contact Center Enterprise deployment.  The
116                   AW collects and serves real-time and configuration
117                   data to the CCE solution.
118        CCE        (Cisco Unified) Contact Center Enterprise; CCE
119                   delivers intelligent contact routing, call
120                   treatment, network-to-desktop computer telephony
121                   integration, and multichannel contact management
122                   over an IP infrastructure.
123        CUIC       Cisco Unified Intelligence Center; CUIC is a web-
124                   based reporting application that provides real-
125                   time and historical reporting in an easy-to-use,
126                   wizard-based application for Cisco Contact Center
127                   products.
128        UCCE       Unified Contact Center Enterprise; see 'CCE'."
129    REVISION        "201305230000Z"
130    DESCRIPTION
131        "Initial version of this MIB."
132    ::= { ciscoMgmt 814 }
133
134
135
136-- ******************************************************************
137-- TEXTUAL CONVENTIONS SECTION
138-- ******************************************************************
139
140CldIndex ::= TEXTUAL-CONVENTION
141    DISPLAY-HINT    "d"
142    STATUS          current
143    DESCRIPTION
144        "This textual convention represents the index value of an
145        entry in a table.  In this MIB, table entries are sorted
146        within a table in an ascending order based on its index
147        value.  Indexes for table entries are assigned by the SNMP
148        agent."
149    SYNTAX          Unsigned32 (1..4294967295)
150
151CldSeverity ::= TEXTUAL-CONVENTION
152    STATUS          current
153    DESCRIPTION
154        "This textual convention indicates the severity level of a
155        notification or a logged event (or trace) message.  The
156        severity levels are:
157
158        'emergency':      Events of this severity indicate that a
159                          devastating failure has occurred; the
160                          system or service is unusable.  Immediate
161                          operator intervention is required.
162
163        'alert':          Events of this severity indicate that a
164                          devastating failure is imminent that will
165                          render the system unusable.  Immediate
166                          operator attention is necessary.
167
168        'critical':       Events of this severity indicate that a
169                          service-impacting failure is likely to
170                          occur soon which is the result of an error
171                          that was not appropriately handled by the
172                          system. Operator attention is needed as
173                          soon as possible.
174
175        'error':          Events of this severity contain important
176                          operational state information and may
177                          indicate that the system has experienced a
178                          temporary impairment or an error that was
179                          appropriately handled by the system.  An
180                          operator should review the notification
181                          soon as possible to determine if additional
182                          action is needed.
183
184        'warning':        Events of this severity contain important
185                          operational state information that may be a
186                          precursor to an error occurrence.  An
187                          operator should review the event soon to
188                          determine if additional action is needed.
189
190        'notice':         Events of this severity contain health or
191                          operational state information that may be
192                          pertinent to the health of the system but
193                          do not require the immediate attention of
194                          the administrator.
195
196        'informational':  Events of this severity contain interesting
197                          system-level information that is valuable
198                          to an administrator in time, however, the
199                          event itself does not indicate a fault or
200                          an impairment condition.
201
202        'debug':          Events of this severity provide supplemental
203                          information that may be beneficial toward
204                          diagnosing or resolving a problem but do not
205                          necessarily provide operational health
206                          status."
207    SYNTAX          INTEGER  {
208                        emergency(1),
209                        alert(2),
210                        critical(3),
211                        error(4),
212                        warning(5),
213                        notice(6),
214                        informational(7),
215                        debug(8)
216                    }
217-- ******************************************************************
218
219ciscoLivedataMIBNotifs  OBJECT IDENTIFIER
220    ::= { ciscoLivedataMIB 0 }
221
222ciscoLivedataMIBObjects  OBJECT IDENTIFIER
223    ::= { ciscoLivedataMIB 1 }
224
225cldGeneral  OBJECT IDENTIFIER
226    ::= { ciscoLivedataMIBObjects 1 }
227
228cldCluster  OBJECT IDENTIFIER
229    ::= { ciscoLivedataMIBObjects 2 }
230
231cldServices  OBJECT IDENTIFIER
232    ::= { ciscoLivedataMIBObjects 3 }
233
234cldReportingConnections  OBJECT IDENTIFIER
235    ::= { ciscoLivedataMIBObjects 4 }
236
237cldEvents  OBJECT IDENTIFIER
238    ::= { ciscoLivedataMIBObjects 5 }
239
240ciscoLivedataMIBConform  OBJECT IDENTIFIER
241    ::= { ciscoLivedataMIB 2 }
242
243ciscoLivedataMIBCompliances  OBJECT IDENTIFIER
244    ::= { ciscoLivedataMIBConform 1 }
245
246ciscoLivedataMIBGroups  OBJECT IDENTIFIER
247    ::= { ciscoLivedataMIBConform 2 }
248
249
250-- ******************************************************************
251-- GENERAL OBJECTS SECTION
252-- ******************************************************************
253
254cldServerName OBJECT-TYPE
255    SYNTAX          SnmpAdminString
256    MAX-ACCESS      read-only
257    STATUS          current
258    DESCRIPTION
259        "This object indicates the fully-qualified domain name of the
260        Cisco LiveData server."
261    ::= { cldGeneral 1 }
262
263cldDescription OBJECT-TYPE
264    SYNTAX          SnmpAdminString
265    MAX-ACCESS      read-only
266    STATUS          current
267    DESCRIPTION
268        "This object indicates a textual description of the Cisco
269        LiveData software installed on this server.  This is
270        typically the full name of the application."
271    ::= { cldGeneral 2 }
272
273cldVersion OBJECT-TYPE
274    SYNTAX          SnmpAdminString
275    MAX-ACCESS      read-only
276    STATUS          current
277    DESCRIPTION
278        "This object indicates the version number of the Cisco
279        LiveData software that is installed on this server."
280    ::= { cldGeneral 3 }
281
282cldStartTime OBJECT-TYPE
283    SYNTAX          DateAndTime
284    MAX-ACCESS      read-only
285    STATUS          current
286    DESCRIPTION
287        "This object indicates the date and time that the Cisco
288        LiveData software (the primary application service) was
289        started on this server."
290    ::= { cldGeneral 4 }
291
292cldTimeZoneName OBJECT-TYPE
293    SYNTAX          SnmpAdminString
294    MAX-ACCESS      read-only
295    STATUS          current
296    DESCRIPTION
297        "This object indicates the textual name of the time zone
298        where the Cisco LiveData server (host) is physically
299        located."
300    ::= { cldGeneral 5 }
301
302cldTimeZoneOffset OBJECT-TYPE
303    SYNTAX          Integer32
304    UNITS           "minutes"
305    MAX-ACCESS      read-only
306    STATUS          current
307    DESCRIPTION
308        "This object indicates the number of minutes that the local
309        time, in the time zone where the Cisco LiveData server (host)
310        is physically located, differs from Greenwich Mean Time
311        (GMT)."
312    ::= { cldGeneral 6 }
313
314cldEventNotifEnable OBJECT-TYPE
315    SYNTAX          TruthValue
316    MAX-ACCESS      read-write
317    STATUS          current
318    DESCRIPTION
319        "This object specifies whether event generation is enabled in
320        the SNMP entity.  This object allows a management station to
321        disable, during run time, all outgoing Cisco LiveData
322        notifications.  This is typically done during a maintenance
323        window when many application components are frequently
324        stopped, reconfigured and restarted, which can generate
325        periodic floods of notifications that are not desirable
326        during a maintenance period.  Please note that this setting
327        is persistent even after a restart of the agent; the
328        management station must explicitly reset this object value
329        back to 'true' to re-enable outgoing application
330        notifications from this device.
331
332        When the value of this object is 'true', notifications will
333        be sent to configured management stations.  When the value is
334        set to 'false' by a management station, notifications will
335        not be sent to configured management stations.  The default
336        value of this object is 'true'.
337
338        The value of this object does not alter the normal table
339        management behavior of the event table, i.e., generated
340        events will be stored in the event table regardless of the
341        value of this object."
342    DEFVAL          { true }
343    ::= { cldGeneral 7 }
344
345-- ******************************************************************
346-- CLUSTER OBJECTS SECTION
347-- ******************************************************************
348
349cldClusterID OBJECT-TYPE
350    SYNTAX          SnmpAdminString
351    MAX-ACCESS      read-only
352    STATUS          current
353    DESCRIPTION
354        "This object indicates a cluster- unique textual identifier
355        for this cluster (e.g. 'sideA')."
356    ::= { cldCluster 1 }
357
358cldClusterStatus OBJECT-TYPE
359    SYNTAX          INTEGER  {
360                        pairedActive(1),
361                        pairedStandby(2),
362                        isolatedActive(3),
363                        isolatedStandby(4),
364                        testing(5),
365                        outOfService(6)
366                    }
367    MAX-ACCESS      read-only
368    STATUS          current
369    DESCRIPTION
370        "This object indicates the current status of this cluster of
371        Cisco LiveData servers.  A cluster is a group of one or more
372        Cisco LiveData servers that work cooperatively to consume and
373        process inbound real-time data from one or more data sources.
374        Work is distributed between worker nodes within the cluster
375        by the master node.  A cluster may have a peer cluster in a
376        fault-tolerant deployment model that will assume data
377        processing duties in the event where its active peer cluster
378        fails.
379
380        'pairedActive':      The cluster is actively processing data
381                             and is communicating with its remote
382                             peer cluster.
383
384        'pairedStandby':     The cluster is standing by (waiting to
385                             process data if necessary) and is
386                             communicating with its remote peer
387                             cluster.
388
389        'isolatedActive':    The cluster is  is actively processing
390                             data but has lost peer-to-peer
391                             communication with it's remote peer
392                             cluster.
393
394        'isolatedStandby':   The cluster is standing by (waiting to
395                             process data if necessary) but has lost
396                             peer-to-peer communication with its
397                             remote peer cluster.
398
399        'testing':           The cluster is unable to communicate
400                             with the remote peer cluster via the
401                             peer-to-peer connection and it is
402                             invoking the 'test-other-side' procedure
403                             to decide whether to become active or to
404                             go into a standby state.
405
406        'outOfService':      The cluster is out of service."
407    ::= { cldCluster 2 }
408
409cldClusterAddress OBJECT-TYPE
410    SYNTAX          SnmpAdminString
411    MAX-ACCESS      read-only
412    STATUS          current
413    DESCRIPTION
414        "This object indicates the hostname or the IP address of the
415        remote peer cluster for peer-to-peer communication with the
416        remote cluster."
417    ::= { cldCluster 3 }
418-- ******************************************************************
419-- SERVICE TABLE SECTION
420-- ******************************************************************
421
422cldServiceTable OBJECT-TYPE
423    SYNTAX          SEQUENCE OF CldServiceEntry
424    MAX-ACCESS      not-accessible
425    STATUS          current
426    DESCRIPTION
427        "The service table is a list of Cisco LiveData services.  A
428        service in this context is one or more executable processes
429        that have been configured to run on this server.
430
431        Service table objects include both the service name and the
432        current run state of that service.  A single LiveData server
433        will have multiple running services, each of a different
434        type, that encompass the LiveData solution on a particular
435        server.  Some of these services work cooperatively with
436        similar or dependent services on other server nodes in the
437        cluster.
438
439        The SNMP agent constructs the service table at startup; the
440        agent refreshes this table periodically during runtime to
441        offer a near real-time status of configured services.
442        Service table entries cannot be added to or deleted from the
443        table by the management station.  All objects in this table
444        are read-only."
445    ::= { cldServices 1 }
446
447cldServiceEntry OBJECT-TYPE
448    SYNTAX          CldServiceEntry
449    MAX-ACCESS      not-accessible
450    STATUS          current
451    DESCRIPTION
452        "Each service entry represents a Cisco LiveData service.
453        The LiveData application software includes a collection of
454        related services, each of which perform a specific,
455        necessary function of the application."
456    INDEX           { cldServiceIndex }
457    ::= { cldServiceTable 1 }
458
459CldServiceEntry ::= SEQUENCE {
460        cldServiceIndex     CldIndex,
461        cldServiceName      SnmpAdminString,
462        cldServiceState     INTEGER,
463        cldServiceUpTime    DateAndTime
464}
465
466cldServiceIndex OBJECT-TYPE
467    SYNTAX          CldIndex
468    MAX-ACCESS      not-accessible
469    STATUS          current
470    DESCRIPTION
471        "The service index is a value that uniquely identifies an
472        entry in the services table.  This value is arbitrarily
473        assigned by the SNMP agent."
474    ::= { cldServiceEntry 1 }
475
476cldServiceName OBJECT-TYPE
477    SYNTAX          SnmpAdminString
478    MAX-ACCESS      read-only
479    STATUS          current
480    DESCRIPTION
481        "This object indicates a user-intuitive textual name for the
482        Cisco LiveData service."
483    ::= { cldServiceEntry 2 }
484
485cldServiceState OBJECT-TYPE
486    SYNTAX          INTEGER  {
487                        unknown(1),
488                        disabled(2),
489                        starting(3),
490                        started(4),
491                        active(5),
492                        stopping(6),
493                        stopped(7)
494                    }
495    MAX-ACCESS      read-only
496    STATUS          current
497    DESCRIPTION
498        "This object indicates the last known state of the Cisco
499        LiveData service.  The object value identifies the run
500        status of a configured service installed on the Cisco
501        LiveData server.  The possible service states are:
502
503        'unknown':       The status of the service cannot be
504                         determined.
505
506        'disabled':      The service has been explicitly disabled by
507                         an administrator.
508
509        'starting':      The service is currently starting up but has
510                         not yet completed its startup procedure.
511
512        'started':       The service has completed its startup
513                         procedure and is currently running.
514
515        'active':        The service has been started, is currently
516                         running and is actively processing data.
517
518        'stopping':      The service is stopping and is in the midst
519                         of its shutdown procedure.
520
521        'stopped':       The service is stopped.  The service may be
522                         dysfunctional or impaired, or it has been
523                         explicitly stopped by an administrator."
524    ::= { cldServiceEntry 3 }
525
526cldServiceUpTime OBJECT-TYPE
527    SYNTAX          DateAndTime
528    MAX-ACCESS      read-only
529    STATUS          current
530    DESCRIPTION
531        "This object indicates the date and time that this service
532        started."
533    ::= { cldServiceEntry 4 }
534
535
536-- ******************************************************************
537-- REPORTING CONNECTION TABLE SECTION
538-- ******************************************************************
539
540cldReportingConnectionTable OBJECT-TYPE
541    SYNTAX          SEQUENCE OF CldReportingConnectionEntry
542    MAX-ACCESS      not-accessible
543    STATUS          current
544    DESCRIPTION
545        "The reporting connection table is a list of Cisco LiveData
546        server reporting connections. A LiveData server maintains a
547        number of active connections to data sources; most often,
548        these are contact center solution nodes that generate real-
549        time data that is ultimately used for creating reports.
550
551        Reporting connection table objects include objects that
552        identify the reporting connection, the current state of that
553        connection and a set of metrics and attributes that offer an
554        indication of the connection health and performance.  A
555        single LiveData server may have multiple reporting
556        connections, each to a different peer node and/or to multiple
557        data sources from a single node.
558
559        The SNMP agent constructs the reporting connection table at
560        startup; the agent refreshes this table periodically during
561        runtime when each LiveData service reports connection states.
562
563        Reporting connection table entries cannot be added to or
564        deleted from the table by the management station.  All
565        objects in this table are read-only."
566    ::= { cldReportingConnections 1 }
567
568cldReportingConnectionEntry OBJECT-TYPE
569    SYNTAX          CldReportingConnectionEntry
570    MAX-ACCESS      not-accessible
571    STATUS          current
572    DESCRIPTION
573        "Each reporting connection entry represents a Cisco LiveData
574        reporting connection.  The LiveData application connects to a
575        number of data sources, each of which sends real-time data
576        as a stream to the LiveData server."
577    INDEX           { cldRptConnIndex }
578    ::= { cldReportingConnectionTable 1 }
579
580CldReportingConnectionEntry ::= SEQUENCE {
581        cldRptConnIndex             CldIndex,
582        cldRptConnServerID          SnmpAdminString,
583        cldRptConnServerAddress     SnmpAdminString,
584        cldRptConnState             INTEGER,
585        cldRptConnStateTime         DateAndTime,
586        cldRptConnEventRate         Gauge32,
587        cldRptConnHeartbeatRTT      Gauge32,
588        cldRptConnSocketConnects    Counter32,
589        cldRptConnSocketDisconnects Counter32,
590        cldRptConnMessagesDiscarded Counter32,
591        cldRptConnDSCP              Integer32
592}
593
594cldRptConnIndex OBJECT-TYPE
595    SYNTAX          CldIndex
596    MAX-ACCESS      not-accessible
597    STATUS          current
598    DESCRIPTION
599        "The reporting connection index is a value that uniquely
600        identifies an entry in the reporting connection table.
601        This value is arbitrarily assigned by the SNMP agent."
602    ::= { cldReportingConnectionEntry 1 }
603
604cldRptConnServerID OBJECT-TYPE
605    SYNTAX          SnmpAdminString
606    MAX-ACCESS      read-only
607    STATUS          current
608    DESCRIPTION
609        "This object indicates a user-intuitive textual
610        identification for the Cisco LiveData connection; this is
611        indicative of the source of the real-time data streamed via
612        this reporting connection."
613    ::= { cldReportingConnectionEntry 2 }
614
615cldRptConnServerAddress OBJECT-TYPE
616    SYNTAX          SnmpAdminString
617    MAX-ACCESS      read-only
618    STATUS          current
619    DESCRIPTION
620        "This object indicates the hostname or IP address of the peer
621        node in this reporting connection."
622    ::= { cldReportingConnectionEntry 3 }
623
624cldRptConnState OBJECT-TYPE
625    SYNTAX          INTEGER  {
626                        inactive(1),
627                        active(2)
628                    }
629    MAX-ACCESS      read-only
630    STATUS          current
631    DESCRIPTION
632        "This object indicates the current state of this reporting
633        connection; it is either active or inactive."
634    ::= { cldReportingConnectionEntry 4 }
635
636cldRptConnStateTime OBJECT-TYPE
637    SYNTAX          DateAndTime
638    MAX-ACCESS      read-only
639    STATUS          current
640    DESCRIPTION
641        "This object indicates the date and time that this reporting
642        connection transitioned into its current state."
643    ::= { cldReportingConnectionEntry 5 }
644
645cldRptConnEventRate OBJECT-TYPE
646    SYNTAX          Gauge32
647    UNITS           "events"
648    MAX-ACCESS      read-only
649    STATUS          current
650    DESCRIPTION
651        "This object indicates the number of events that are arriving
652        via this connection per second."
653    ::= { cldReportingConnectionEntry 6 }
654
655cldRptConnHeartbeatRTT OBJECT-TYPE
656    SYNTAX          Gauge32
657    UNITS           "milliseconds"
658    MAX-ACCESS      read-only
659    STATUS          current
660    DESCRIPTION
661        "This object indicates the time, in milliseconds, for
662        heartbeat requests to be returned from the peer node in this
663        reporting connection."
664    ::= { cldReportingConnectionEntry 7 }
665
666cldRptConnSocketConnects OBJECT-TYPE
667    SYNTAX          Counter32
668    MAX-ACCESS      read-only
669    STATUS          current
670    DESCRIPTION
671        "This object indicates the number of successful socket
672        connections made to the peer node in this reporting
673        connection."
674    ::= { cldReportingConnectionEntry 8 }
675
676cldRptConnSocketDisconnects OBJECT-TYPE
677    SYNTAX          Counter32
678    MAX-ACCESS      read-only
679    STATUS          current
680    DESCRIPTION
681        "This object indicates the number of socket disconnects with
682        the peer node in this reporting connection.  This is used in
683        conjunction with cldConnSocketConnects to identify unstable
684        connections to a particular endpoint."
685    ::= { cldReportingConnectionEntry 9 }
686
687cldRptConnMessagesDiscarded OBJECT-TYPE
688    SYNTAX          Counter32
689    UNITS           "messages"
690    MAX-ACCESS      read-only
691    STATUS          current
692    DESCRIPTION
693        "This object indicates the number of messages sent by the
694        peer node in this reporting connection that have been
695        discarded."
696    ::= { cldReportingConnectionEntry 10 }
697
698cldRptConnDSCP OBJECT-TYPE
699    SYNTAX          Integer32
700    MAX-ACCESS      read-only
701    STATUS          current
702    DESCRIPTION
703        "This object indicates the Differentiated Services (DS) value
704        currently used by this reporting connection for Quality of
705        Service (QoS) marking."
706    ::= { cldReportingConnectionEntry 11 }
707
708
709-- ******************************************************************
710-- EVENT TABLE
711-- ******************************************************************
712
713cldEventTable OBJECT-TYPE
714    SYNTAX          SEQUENCE OF CldEventEntry
715    MAX-ACCESS      not-accessible
716    STATUS          current
717    DESCRIPTION
718        "The event table is a list of active Cisco LiveData events.
719        The SNMP agent constructs the event table at startup and it
720        fills the table as events are generated.
721
722        Events with the same cldEventID value will overwrite existing
723        events in the table with the same EventID (i.e. only the most
724        recent will persist).
725
726        Event table entries cannot be added to or deleted from the
727        table by the management station.  All objects in this table
728        are read-only."
729    ::= { cldEvents 1 }
730
731cldEventEntry OBJECT-TYPE
732    SYNTAX          CldEventEntry
733    MAX-ACCESS      not-accessible
734    STATUS          current
735    DESCRIPTION
736        "Each event entry represents a Cisco LiveData event.  The
737        LiveData application software generates events when an
738        unusual condition has occurred that can potentially affect
739        the functioning of the Cisco LiveData server."
740    INDEX           { cldEventIndex }
741    ::= { cldEventTable 1 }
742
743CldEventEntry ::= SEQUENCE {
744        cldEventIndex     CldIndex,
745        cldEventID        Unsigned32,
746        cldEventAppName   SnmpAdminString,
747        cldEventName      SnmpAdminString,
748        cldEventState     INTEGER,
749        cldEventSeverity  CldSeverity,
750        cldEventTimestamp DateAndTime,
751        cldEventText      SnmpAdminString
752}
753
754cldEventIndex OBJECT-TYPE
755    SYNTAX          CldIndex
756    MAX-ACCESS      not-accessible
757    STATUS          current
758    DESCRIPTION
759        "The event index is a value that uniquely identifies an entry
760        in the event table.  This value is arbitrarily assigned by
761        the SNMP agent."
762    ::= { cldEventEntry 1 }
763
764cldEventID OBJECT-TYPE
765    SYNTAX          Unsigned32
766    MAX-ACCESS      read-only
767    STATUS          current
768    DESCRIPTION
769        "This object indicates the unique numeric event message
770        identifier that is assigned by the LiveData server to this
771        event.  This identifier is unique for each different event.
772        The event ID can be used to correlate 'clear' state events
773                to 'raise' state events."
774    ::= { cldEventEntry 2 }
775
776cldEventAppName OBJECT-TYPE
777    SYNTAX          SnmpAdminString
778    MAX-ACCESS      read-only
779    STATUS          current
780    DESCRIPTION
781        "This object indicates the service- specific name of the
782        Cisco LiveData functional service that generated this event."
783    ::= { cldEventEntry 3 }
784
785cldEventName OBJECT-TYPE
786    SYNTAX          SnmpAdminString
787    MAX-ACCESS      read-only
788    STATUS          current
789    DESCRIPTION
790        "This object indicates the service-specific name of the Cisco
791        LiveData event message.  The object value is used to group
792        similar events."
793    ::= { cldEventEntry 4 }
794
795cldEventState OBJECT-TYPE
796    SYNTAX          INTEGER  {
797                        raise(1),
798                        clear(2)
799                    }
800    MAX-ACCESS      read-only
801    STATUS          current
802    DESCRIPTION
803        "This object indicates the state (not to be confused with
804        severity) of the event and potentially the current status of
805        the functional component that generated the event.  The
806        possible states are:
807
808        'raise':    A raise state identifies an event received as a
809                    result of a health-impacting condition, such as a
810                    process failure.  A subsequent clear state event
811                    will follow when the error condition is resolved.
812                    A node which generates a 'raise' state event may
813                    be impaired and likely requires the attention of
814                    an administrator.
815
816        'clear':    The clear state indicates that the condition
817                    which generated a previous raise notification has
818                    been resolved.  This may occur automatically with
819                    fault-tolerant deployments or may be the result
820                    of administrator intervention."
821    ::= { cldEventEntry 5 }
822
823cldEventSeverity OBJECT-TYPE
824    SYNTAX          CldSeverity
825    MAX-ACCESS      read-only
826    STATUS          current
827    DESCRIPTION
828        "This object indicates the severity level of this event."
829    ::= { cldEventEntry 6 }
830
831cldEventTimestamp OBJECT-TYPE
832    SYNTAX          DateAndTime
833    MAX-ACCESS      read-only
834    STATUS          current
835    DESCRIPTION
836        "This object indicates the date and time that the event was
837        generated on the originating device."
838    ::= { cldEventEntry 7 }
839
840cldEventText OBJECT-TYPE
841    SYNTAX          SnmpAdminString
842    MAX-ACCESS      read-only
843    STATUS          current
844    DESCRIPTION
845        "This object indicates the full text of the event which
846        includes a description of the event that was generated,
847        component state information and potentially a brief
848        description of administrative action that may be necessary
849        to correct the condition that caused the event to occur."
850    ::= { cldEventEntry 8 }
851
852
853
854-- ******************************************************************
855-- NOTIFICATION OBJECT SECTION
856-- ******************************************************************
857
858cldEventNotif NOTIFICATION-TYPE
859    OBJECTS         {
860                        cldEventID,
861                        cldServerName,
862                        cldEventAppName,
863                        cldEventName,
864                        cldEventState,
865                        cldEventSeverity,
866                        cldEventTimestamp,
867                        cldEventText
868                    }
869    STATUS          current
870    DESCRIPTION
871        "The SNMP entity generates cldEventNotif when an unusual
872        condition has occurred that can potentially affect the
873        functioning of the Cisco LiveData server.  This notification
874        type describes operational state information of the service
875        generating the notification when such service-impacting
876        conditions occur.  A notification is sent by a functional
877        service of the Cisco LiveData server.
878        The notification type includes the following objects:
879
880        'cldEventID':        The unique numeric event message
881                             identifier for this event.
882
883        'cldServerName':     The fully-qualified domain name of the
884                             Cisco LiveData server that generated the
885                             notification.
886
887        'cldEventAppName':   The name of the Cisco LiveData
888                             functional service that generated this
889                             event.
890
891        'cldEventName':      The service-specific name of the Cisco
892                             LiveData event message.
893
894        'cldEventState':     The state of the event, either 'raise'
895                             or 'clear'.  A 'raise' state event is
896                             generated when an unusual or service-
897                             impacting condition occurs while a
898                             'clear' state event is generated when
899                             a prior condition has been resolved.
900
901        'cldEventSeverity':  The severity level of this event; an
902                             integer value from 1 (emergency) to 8
903                             (debug).
904
905        'cldEventTimestamp': The date and time that the event was
906                             generated.
907
908        'cldEventText':      The full text of the event."
909   ::= { ciscoLivedataMIBNotifs 1 }
910
911-- ******************************************************************
912-- COMPLIANCE SECTION
913-- ******************************************************************
914
915ciscoLivedataMIBCompliance MODULE-COMPLIANCE
916    STATUS          current
917    DESCRIPTION
918        "This object is the compliance statement for entities which
919        implement the Cisco LiveData MIB."
920    MODULE          CISCO-LIVEDATA-MIB
921    MANDATORY-GROUPS {
922                        cldGeneralGroup,
923                        cldClusterGroup,
924                        cldServicesGroup,
925                        cldRptConnectionsGroup,
926                        cldEventsGroup,
927                        cldMIBEventGroup
928                    }
929    ::= { ciscoLivedataMIBCompliances 1 }
930
931cldGeneralGroup OBJECT-GROUP
932    OBJECTS         {
933                        cldServerName,
934                        cldDescription,
935                        cldVersion,
936                        cldStartTime,
937                        cldTimeZoneName,
938                        cldTimeZoneOffset,
939                        cldEventNotifEnable
940                    }
941    STATUS          current
942    DESCRIPTION
943        "The general group defines the general Cisco LiveData
944        objects.  All servers will populate these objects."
945    ::= { ciscoLivedataMIBGroups 1 }
946
947cldClusterGroup OBJECT-GROUP
948    OBJECTS         {
949                        cldClusterID,
950                        cldClusterStatus,
951                        cldClusterAddress
952                    }
953    STATUS          current
954    DESCRIPTION
955        "The cluster group defines the Cisco LiveData objects related
956        to the cluster of LiveData servers. All servers will populate
957        these objects."
958    ::= { ciscoLivedataMIBGroups 2 }
959
960cldServicesGroup OBJECT-GROUP
961    OBJECTS         {
962                        cldServiceName,
963                        cldServiceState,
964                        cldServiceUpTime
965                    }
966    STATUS          current
967    DESCRIPTION
968        "The services group defines the Cisco LiveData service table
969        objects.  All servers will populate these objects, however,
970        the number of entries in the table will vary across servers
971        and the types of services will vary as well."
972    ::= { ciscoLivedataMIBGroups 3 }
973
974cldRptConnectionsGroup OBJECT-GROUP
975    OBJECTS         {
976                        cldRptConnServerID,
977                        cldRptConnServerAddress,
978                        cldRptConnState,
979                        cldRptConnStateTime,
980                        cldRptConnEventRate,
981                        cldRptConnHeartbeatRTT,
982                        cldRptConnSocketConnects,
983                        cldRptConnSocketDisconnects,
984                        cldRptConnMessagesDiscarded,
985                        cldRptConnDSCP
986                    }
987    STATUS          current
988    DESCRIPTION
989        "The reporting connections group defines the Cisco LiveData
990        connection table objects.  All servers will populate these
991        objects, however, the number of entries in the table will
992        vary across servers."
993    ::= { ciscoLivedataMIBGroups 4 }
994
995cldEventsGroup OBJECT-GROUP
996    OBJECTS         {
997                        cldEventID,
998                        cldEventAppName,
999                        cldEventName,
1000                        cldEventState,
1001                        cldEventSeverity,
1002                        cldEventTimestamp,
1003                        cldEventText
1004                    }
1005    STATUS          current
1006    DESCRIPTION
1007        "The events group defines the Cisco LiveData event table
1008        objects.  All servers will populate these objects, however,
1009        the number of entries in the table will vary across servers."
1010    ::= { ciscoLivedataMIBGroups 5 }
1011
1012cldMIBEventGroup NOTIFICATION-GROUP
1013   NOTIFICATIONS    { cldEventNotif }
1014    STATUS          current
1015    DESCRIPTION
1016        "This group defines the notification types defined in this
1017        MIB."
1018    ::= { ciscoLivedataMIBGroups 6 }
1019
1020END
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032