CISCO-XGCP-MIB :: cXgcpMgcConfigMgcGrpNum

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-XGCP-MIBcXgcpMgcConfigMgcGrpNum

cXgcpMgcConfigMgcGrpNum

Module: CISCO-XGCP-MIB

OID (symbolic): CISCO-XGCP-MIB::cXgcpMgcConfigMgcGrpNum

OID (numeric): 1.3.6.1.4.1.9.9.318.1.1.1.1.1

Node type: OBJECT-TYPE

Type: CMgcGroupIndexOrZero

Access: read-write

Description: This object specifies which MGC Redundant Group will be used in XGCP. The value of this object refers to the object cMgcGrpIndex from MGC Redundant Group Table, cMgcGrpParamTable.

There are two conditions to associate a MGC group: 1. At least one MGC is associated with the MGC group 2. At least one protocol is associated with the MGC group

If the value of the object is non-zero, it means the media gateway has a MGC Redundant Group. In the call setup, the parameters of call agents within the MGC Redundant Group will be sequentially tried according to its preference.

This object cXgcpMgcConfigMgcGrpNum and object cXgcpMgcConfigAddress are mutually exclusive. The object cXgcpMgcConfigAddress can be set only when the object cXgcpMgcConfigMgcGrpNum is equal to 0.

If the value of the object is 0, which means there is no MGC Redundant Group associated with the media gateway. It has only one call agent (in media gateway level) to communicate with. This call agent is indicated by cXgcpMgcConfigAddress and will be used in call setup (if call set-up on media gateway level).

What is cXgcpMgcConfigMgcGrpNum?

This read-write CMgcGroupIndexOrZero object specifies which MGC Redundant Group, referencing cMgcGrpIndex in the MGC Redundant Group Table, the gateway uses for XGCP signaling, valid only when at least one MGC and one protocol are already associated with that group. A non-zero value tells the admin the gateway has been configured for redundant MGC coverage rather than a single fixed controller. For example, an admin building resilience into a gateway's call-agent connectivity would point this object at a pre-configured redundant group instead of leaving it at zero.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.318.1.1.1.1.1
snmpwalk -v2c -c public <target> CISCO-XGCP-MIB::cXgcpMgcConfigMgcGrpNum

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.318.1.1.1.1.1.1
snmpget -v2c -c public <target> CISCO-XGCP-MIB::cXgcpMgcConfigMgcGrpNum.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.9.9.318.1.1.1.1.1.1 s <value>

Start monitoring Cisco VoIP/VoATM media gateway / Media Gateway Controller (MGC) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-XGCP-MIB::cXgcpMgcConfigMgcGrpNum OID value, configure state conditions and alerts, and monitor any Cisco VoIP/VoATM media gateway / Media Gateway Controller (MGC) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.318ciscoXgcpMIBCISCO-XGCP-MIB
1.3.6.1.4.1.9.9.318.1cXgcpObjectsCISCO-XGCP-MIB
1.3.6.1.4.1.9.9.318.1.1cXgcpMgcCfgCISCO-XGCP-MIB
1.3.6.1.4.1.9.9.318.1.1.1cXgcpMgcConfigTableCISCO-XGCP-MIB
1.3.6.1.4.1.9.9.318.1.1.1.1cXgcpMgcConfigEntryCISCO-XGCP-MIB
1.3.6.1.4.1.9.9.318.1.1.1.1.1cXgcpMgcConfigMgcGrpNumCISCO-XGCP-MIB