CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB - persistentXgcpEventsTable

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

persistentXgcpEventsTable

persistent Xgcp Events Table
1.3.6.1.4.1.351.150.18.1.1.1

The persistentXgcpEventsTable contains configuration information about xGCP events which involve a persistent notification request. ::= { persistentXgcpEvents 1 } SYNTAX PersistentXgcpEventsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION An entry in the persistentXgcpEventsTable. Each entry consists of persistentXgcpEventNum - Index to the persistentXgcpEventsTable. persistentXgcpEventName - Name of the xGCP event that needs persistent notification to the call agent for example 't/hd'. persistentXgcpEventRowStatus -This indicates whether an xGCP event is added in this entry or not. This table is not created implicitly. The user can add xGCP event or delete an xGCP event. INDEX { persistentXgcpEventNum } ::= { persistentXgcpEventsTable 1 } PersistentXgcpEventsEntry ::= SEQUENCE { persistentXgcpEventNum Integer32, persistentXgcpEventName SnmpAdminString, persistentXgcpEventRowStatus RowStatus } SYNTAX Integer32 (1..16) MAX-ACCESS not-accessible STATUS current DESCRIPTION This object is a index to persistentXgcpEventsTable. ::= { persistentXgcpEventsEntry 1 } SYNTAX SnmpAdminString (SIZE(0..64)) MAX-ACCESS read-write STATUS current DESCRIPTION This object holds the name of the event for example 't/hd' or 't/hu'. ::= { persistentXgcpEventsEntry 2 } SYNTAX RowStatus MAX-ACCESS read-write STATUS current DESCRIPTION This object allows to add or delete an entry. Modifying an entry is not allowed. An entry may be created using the 'createAndGo' option. When the row is successfully created, the RowStatus would be set to 'active' by the agent. An entry may be deleted by setting the RowStatus to 'destroy'. Other options such as `CreateAndWait', 'notInService', 'notReady' will not be used. For creating an entry the persistentXgcpEventNum and persistentXgcpEventName must be provided. This object tells call control whether or not a particular xGCP event is added or not, based on this the call control module will decide whether or not to notify (NTFY) call agent when a particular xGCP event is received, without waiting for CA to request for that event. ::= { persistentXgcpEventsEntry 3 } -- -- ********************************************************************** -- Conformance -- ********************************************************************** -- -- conformance information -- persistentXgcpEventsMIBConformance OBJECT IDENTIFIER ::= { ciscoWanPersistentXgcpEventsMIB 2 } persistentXgcpEventsMIBCompliances OBJECT IDENTIFIER ::= { persistentXgcpEventsMIBConformance 1 } persistentXgcpEventsMIBGroups OBJECT IDENTIFIER ::= { persistentXgcpEventsMIBConformance 2 } -- -- Conformance and compliance statements statements -- persistentXgcpEventsMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION The complaince statement for persistent Xgcp events which implement persistentXgcpEvents MIB.

Back to CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB MIB page.

IPHost Network monitor allows you to monitor persistentXgcpEventsTable on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco multiplexers right now.

MIBs list