cccaEventOriginatingNode

CISCO-CONTACT-CENTER-APPS-MIB · .1.3.6.1.4.1.9.9.473.1.4.4

Object

scalar SNMP-FRAMEWORK-MIBSnmpAdminString

The event originating node objects specifies the application-
defined name of the enterprise contact center application
functional component that generated this notification.  This
name will vary, both in content and in format, based on the
component that generated the notification.  For example, the
name for a router component may be 'RouterA', a combination of
the component identification and the 'side' identifier, while
the name 'PG1A' is a combination of the peripheral gateway
acronym followed by the peripheral gateway number and the
'side' identifier.

Context

MIB: CISCO-CONTACT-CENTER-APPS-MIB
OID: .1.3.6.1.4.1.9.9.473.1.4.4
Type: scalar
Access: notifyonly
Status: current
Parent: cccaNotificationInfo
Groups: 1

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'CISCO-CONTACT-CENTER-APPS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-CONTACT-CENTER-APPS-MIB::cccaEventOriginatingNode.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-CONTACT-CENTER-APPS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-CONTACT-CENTER-APPS-MIB::cccaEventOriginatingNode'

Syntax

SNMP-FRAMEWORK-MIBSnmpAdminString

Source: SNMP-FRAMEWORK-MIBSnmpAdminString
Base type: OctetString

Values & Constraints

Type Constraints

range: 0..255