CISCO-MGC-MIB

All MIBs › CISCO-MGC-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2003-04-18

Category: Cisco Devices, Telephony and VoIP

Description:

Manages Media Gateway Controllers including call routing, signaling links, and trunk group statistics on Cisco MGX.

Imported Objects

cmgwIndex	OBJECT-TYPE
cmgwSignalProtocolIndex	OBJECT-TYPE

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-TC

CiscoPort

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TruthValue

What Is CISCO-MGC-MIB?

CISCO-MGC-MIB is a Cisco proprietary MIB for managing the Cisco Media Gateway Controller (MGC), a call-agent/softswitch platform providing call-control intelligence to voice gateways via signaling protocols such as SGCP and MGCP. It exposes configuration data for MGC and MGC-group associations per gateway, including domain names, IP addressing with multiple-IP support, and the resolution/protocol used, centered on the cMgcConfigTable and cMgcIpConfigTable. For monitoring, it lets an operator confirm the call-agent-to-gateway signaling relationship is correctly configured (which MGC controls which gateway, and via which IP addresses) and receive cMgcMibNotifications for related fault or state-change events, functioning more as a call-control configuration/fault MIB than a hardware sensor MIB. It is used alongside Cisco's voice gateway MIBs since the MGC/gateway relationship spans both the call agent (external) and the gateway device. Administrators often first inspect it with a CISCO-MGC-MIB MIB Browser session before scripting automated polling, and it is typically deployed in Cisco VoIP/PSTN gateway networks using MGCP/SGCP-controlled media gateways.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-MGC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

MGC domain name configuration
number of MGC groups per gateway
MGC IP address configuration
number of configured IP addresses
signaling resolution/protocol setting
MGC configuration/fault notifications

Supported Devices

Cisco Media Gateway Controller (MGC) platforms
Cisco voice gateways using SGCP/MGCP signaling

Monitoring Examples

cMgcConfigTable/cMgcConfigEntry, indexed by cMgcIndex, expose cMgcDomainName and cMgcNumMgcGroups so an admin can confirm which call-agent domain and how many MGC groups are configured for a given gateway. cMgcIpConfigTable/cMgcIpConfigEntry list the associated cMgcIpAddressType/cMgcIpAddress entries, letting an operator verify all expected call-agent IP addresses are registered (cMgcNumIP) - a mismatch here would indicate a misconfigured or unreachable call agent. cMgcResolution and cMgcMibNotifications round out the config/fault-notification picture for the gateway-to-MGC relationship.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoMgcMIB	1.3.6.1.4.1.9.9.321			This MIB is used to support MGC(call agent) and MGC Group configuration. The MGC or MGC group configuration is performed under a specific gateway(cmgwIndex). The call agent is an external element (outside of gateway) with call control intelligence to control call connection in gateway. The protocols used for communication between voice gateway and call agent included SGCP, MGCP, ... Multiple IP addresses can be associated with one call agent. An MGC group is a logical grouping of several MGCs into one group. MGC redundancy is used to support multi call agent for one gateway. With MGC redundancy, a voice gateway can send gateway-initiated-commands to the next MGC in the MGC group if it fails to receive response from any IP address(es) associated to the current MGC. To use MGC redundancy in gateway: Step 1: add individual entry (in any order) for profile MGC Step 2: make association between the entries 1 IP with MGC 2 MGC with MGC group 1/2 protocol with MGC group 3 MGC group with profile or MGC group with gateway Only if a MGC group at least is associated with one profile or gateway, then the MGC group can be used, otherwise the MGC group is useless. To delete the following entries, it is needed to do de-association first: profile MGC When do de-association, the order is opposite to that of association.
cMgcConfig	1.3.6.1.4.1.9.9.321.1.1
cMgcConfigEntry	1.3.6.1.4.1.9.9.321.1.1.1.1		not-accessible	Each entry represents a call agent(MGC). Each entry in this table should have a unique domain name representing a call agent. Adding/deleting entry in this table is controlled by 'cMediaGwDomainNameConfigTable' of CISCO-MEDIA-GATEWAY-MIB: 1. Entry creation An entry in this table is created when its associated entry in the 'cMediaGwDomainNameConfigTable' is created with the value of 'mgc(3)' in the cmgwConfigDomainNameEntity object. The 'cmgwConfigDomainName' of the associated entry in the 'cMediaGwDomainNameConfigTable' will be taken as 'cMgcDomainName' of the new entry. 2. Entry deletion An entry of this table is deleted when its associated entry in 'cMediaGwDomainNameConfigTable' is deleted.
cMgcConfigTable	1.3.6.1.4.1.9.9.321.1.1.1		not-accessible	This table is used for configuring MGC related parameters.
STR cMgcDomainName	1.3.6.1.4.1.9.9.321.1.1.1.1.2	SnmpAdminString	read-only	This object contains the same name as the one in the 'cMgcDomainName object' of the associated entry in 'cMediaGwDomainNameConfigTable'.
cMgcGroupConfig	1.3.6.1.4.1.9.9.321.1.2
U32 cMgcGrpAssociationInfo	1.3.6.1.4.1.9.9.321.1.2.1.1.3	Unsigned32	read-only	This object indicates the association between MGC group and profile/gateway with bitmap format. It is 1:N mapping, e.g., each profile or gateway can only have one MGC group, but one MGC group can be associated with multi profile and gateway. The possible bit positions used in the bitmap are listed as follows: Bit profile/gateway value --------------------------------------------------------------- 0 profile 1 0: the MGC group is not associated with it 1: the MGC group is associated with it 1 profile 2 0: the MGC group is not associated with it 1: the MGC group is associated with it 2 profile 3 0: the MGC group is not associated with it 1: the MGC group is associated with it 3 profile 4 0: the MGC group is not associated with it 1: the MGC group is associated with it ... ... 30 profile 31 0: the MGC group is not associated with it 1: the MGC group is associated with it 31 gateway 0: the MGC group is not associated with it 1: the MGC group is associated with it The value zero means the MGC Group is not associated with any profile or gateway.
cMgcGrpEntry	1.3.6.1.4.1.9.9.321.1.2.2.1		not-accessible	The entry is represented an association of a MGC with a MGC group.
cMgcGrpGroup	1.3.6.1.4.1.9.9.321.2.2.4			A collection of objects providing MGC (in MGC group) configuration information.
CMG cMgcGrpIndex	1.3.6.1.4.1.9.9.321.1.2.1.1.1	CMgcGroupIndex	not-accessible	A unique index to identify a MGC group.
I32 cMgcGrpMgcPreference	1.3.6.1.4.1.9.9.321.1.2.2.1.1	Integer32	read-create	The preference of the MGC in the MGC group. The lower the number the higher the preference. i.e. 1 will have higher preference than 2.
CIS cMgcGrpMgcUdpPort	1.3.6.1.4.1.9.9.321.1.2.2.1.2	CiscoPort	read-create	The UDP port of the MGC in the MGC group. The zero means there is no specific UDP port, the UDP port in the protocol table will be used.
I32 cMgcGrpNumMgc	1.3.6.1.4.1.9.9.321.1.2.1.1.2	Integer32	read-only	This object is used to indicate number of MGCs to be associated with this MGC Group. The value zero means there is no MGC in the MGC Group. When the entry create, this value is set to 0. Adding/deleting MGC to/from MGC group is through cMgcGrpTable. After a MGC added/deleted to/from this MGC group, the value of this object will be incremented/decremented by 1. If the value of this object is zero, it is not allowed to associate this MGC group with any profile or gateway.
I32 cMgcGrpNumProtocol	1.3.6.1.4.1.9.9.321.1.2.1.1.4	Integer32	read-only	This object is used to indicate number of protocols associated with this MGC group. The value zero means there is no protocol associated with this MGC group. When the entry create, this object is set to 0. The association between protocol and MGC group is configured via cMgcGrpProtocolTable. After a protocol is associated/de-associated with this MGC group, this object will be incremented/decremented by 1. If this object is zero, it is not allowed to associate the MGC group with any profile or gateway.
cMgcGrpParamEntry	1.3.6.1.4.1.9.9.321.1.2.1.1		not-accessible	Entry of cMgcGrpParamTable. Each entry includes the information shared by a group of MGC
cMgcGrpParamGroup	1.3.6.1.4.1.9.9.321.2.2.3			A collection of objects providing per MGC group configuration information.
cMgcGrpParamTable	1.3.6.1.4.1.9.9.321.1.2.1		not-accessible	This table containing information about MGC group related profile/protocol association and parameters.
cMgcGrpProtocolEntry	1.3.6.1.4.1.9.9.321.1.2.3.1		not-accessible	Entry of cMgcGrpProtocolTable.
cMgcGrpProtocolGroup	1.3.6.1.4.1.9.9.321.2.2.5			A collection of objects providing Protocol (in MGC group) configuration information.
I32 cMgcGrpProtocolPreference	1.3.6.1.4.1.9.9.321.1.2.3.1.1	Integer32	read-create	The preference of the Protocol in the MGC group. The lower the number the higher the preference. i.e. 1 will have higher preference than 2. When gateway does not know which protocol is used by a call agent the preference is used to make the decision. But if gateway knows which protocol used by a call agent, gateway will use that protocol (as long as the protocol is added to the MGC group, irrespective of the preference) to communicate with the call agent. For example: when gateway return a call agent message, gateway will use the protocol which used by the call agent to send the message.
ROW cMgcGrpProtocolRowStatus	1.3.6.1.4.1.9.9.321.1.2.3.1.2	RowStatus	read-create	This object is used to create a new row or modify or delete an existing row in this table. In order to add a protocol to MGC group, the following condition need to be met: Both the protocol and the MGC group should be existing After the protocol added to the MGC group, the related cMgcGrpNumProtocol will be incremented by 1. In order to delete a protocol from MGC group, the following condition need to be met: The protocol to be deleted should not be the only one in the MGC group when the MGC group is used by a gateway or a profile. This means if the value of cMgcGrpNumProtocol is equal to 1 and the value of cMgcGrpAssociationInfo is non-zero, this protocol is the only one associated with the MGC group which is still in use by gateways or some profiles. Therefore this protocol can not be deleted. After the protocol deleted from the MGC group, the related cMgcGrpNumProtocol will be decremented by 1.
cMgcGrpProtocolTable	1.3.6.1.4.1.9.9.321.1.2.3		not-accessible	cMgcGrpProtocolTable is used to add protocol to MGC group. This table is designed to support multi protocol for MGC group. The MGC group to protocol is N to N mapping.
ROW cMgcGrpRowStatus	1.3.6.1.4.1.9.9.321.1.2.2.1.3	RowStatus	read-create	This object is used to create a new row or modify or delete an existing row in this table. In order to add an MGC to a MGC group, the following conditions need to be met: 1. the MGC and the MGC group should be existing 2. at least one IP address is associated with the MGC if the MGC is configured for internal resolution. After the MGC added to the MGC group, the related cMgcGrpNumMgc will be incremented by 1. cMgcNumMgcGroups will be incremented by 1. In order to delete an MGC from MGC group, the following conditions need to be met: The MGC is not the only MGC associated with the MGC group if the MGC group is associated with gateway or one or more profiles. After the MGC added to the MGC group, the related cMgcGrpNumMgc will be decremented by 1. cMgcNumMgcGroups will be decremented by 1.
T/F cMgcGrpStateChangeNtfy	1.3.6.1.4.1.9.9.321.1.2.1.1.5	TruthValue	read-write	This object enables or disables sending gateway state change notifications to call agent.
cMgcGrpTable	1.3.6.1.4.1.9.9.321.1.2.2		not-accessible	This table represents the association of MGCs and MGC group. Each MGC group consists of one or more MGCs and each MGC can belong to one or more MGC groups. Therefore it is an N to N mapping.
I32 cMgcIndex	1.3.6.1.4.1.9.9.321.1.1.1.1.1	Integer32	not-accessible	A unique index to identify each MGC which will communicate with this media gateway.
IP cMgcIpAddress	1.3.6.1.4.1.9.9.321.1.1.2.1.3	InetAddress	read-create	This object represents the configured IP address. After adding the entry, this object can not be modified.
IPt cMgcIpAddressType	1.3.6.1.4.1.9.9.321.1.1.2.1.2	InetAddressType	read-create	This object is the IP address type for cMgcIpAddress.
cMgcIpConfigEntry	1.3.6.1.4.1.9.9.321.1.1.2.1		not-accessible	Each entry represents an IP address which is associated with the MGC(cMgcIndex). When cMgcResolution is configured to 'externalOnly', user cannot add/delete/modify any entry.
cMgcIpConfigTable	1.3.6.1.4.1.9.9.321.1.1.2		not-accessible	This table contains MGC related IP addresses. MGC index(cMgcIndex) is a part of index of this table, so IP address in this table is automatically associated with the MGC. Multiple IP addresses can be associated with the same MGC. Under the same MGC (cMgcIndex is same) all IP addresses are equivalent. all IP addresses will share the same domain name: 'cMgcDomainName' in cMgcConfigTable.
I32 cMgcIpIndex	1.3.6.1.4.1.9.9.321.1.1.2.1.1	Integer32	not-accessible	A unique index to identify the address of a specific MGC. The MGC is represented by cMgcIndex.
cMgcIpMIBGroup	1.3.6.1.4.1.9.9.321.2.2.2			A collection of objects providing IP (in MGC) configuration information.
I32 cMgcIpPreference	1.3.6.1.4.1.9.9.321.1.1.2.1.4	Integer32	read-create	This object represents preference of the cMgcIpAddress in the given MGC. The lower the number the higher the preference. i.e. 1 will have higher preference than 2. IF more than one IP have the same preference, gateway will select them one by one.
ROW cMgcIpRowStatus	1.3.6.1.4.1.9.9.321.1.1.2.1.5	RowStatus	read-create	This object is used to create/modify/delete entry. In order to delete an entry, following conditions need to be met: 1. The MGC to which this IP address is being added, should be existing. 2. The MGC's resolution (cMgcResolution) should be 'internal only'. 3. the mandatory object is cMgcIpAddress After the IP address added to the MGC the related 'cMgcNumIP' in MGC table will be incremented by 1. In order to delete an entry, following conditions need to be met: 1. The MGC's resolution (cMgcResolution) should be 'internal only'. 2. The IP address should not be the only one in the MGC while the MGC is associated with MGC group. This means if the value of 'cMgcNumIP' is equal to 1 and the value of 'cMgcNumMgcGroups' is non-zero, this IP address is the only one associated with the MGC and it is possible that this IP address is also the only one associated with MGC group. Therefore this IP address can not be deleted. After deleting the IP address from the MGC the related 'cMgcNumIP' in MGC table will be decremented by 1.
cMgcMIBCompliance	1.3.6.1.4.1.9.9.321.2.1.1			Compliance statement for CISCO-MGC-MIB.
cMgcMIBCompliances	1.3.6.1.4.1.9.9.321.2.1
cMgcMIBConformance	1.3.6.1.4.1.9.9.321.2
cMgcMIBGroup	1.3.6.1.4.1.9.9.321.2.2.1			A collection of objects providing per MGC basis configuration information.
cMgcMIBGroups	1.3.6.1.4.1.9.9.321.2.2
cMgcMibNotifications	1.3.6.1.4.1.9.9.321.0
cMgcMibObjects	1.3.6.1.4.1.9.9.321.1
I32 cMgcNumIP	1.3.6.1.4.1.9.9.321.1.1.1.1.4	Integer32	read-only	This object is used to indicate number of IP addresses are associated with this MGC. The value zero means there is no IP address associated with this MGC. The MGC can not be deleted if the value of this object is non-zero and cMgcResolution is configured to 'internalOnly'.
I32 cMgcNumMgcGroups	1.3.6.1.4.1.9.9.321.1.1.1.1.3	Integer32	read-only	This object is used to indicate number of MGC group with which this MGC associated. The value zero means this MGC is not associated with any MGC Group. If this value greater than zero, then the MGC entry can not be deleted.
INT cMgcResolution	1.3.6.1.4.1.9.9.321.1.1.1.1.5	INTEGER	read-write	This object determines the kind of resolution to be applied for this MGC. 'internalOnly' means that the gateway will not try to resolve the IP address for this domain name using external DNS name server. 'externalOnly' means the IP address for this domain name will be resolved externally using DNS name server. The request to change from 'internalOnly' to 'externalOnly' will be rejected if the DNS name server is not available for gateway. The IP addresses related to the same MGC should have the same cMgcResolution. The value of the MGC associated objects in the cMgcIpConfigTable can not be modified by NMS if the value of cMgcResolution for the MGC is 'externalOnly'. The following are the behavior of changing the value of this object. [1] changing the value from 'externalOnly' to 'internalOnly' 1) precondition MGC is not associated with any MGC group (value of cMgcNumMgcGroups is zero). 2) behavior If the value of this object is changed successfully, all existing IP addresses in cMgcIpConfigTable that are associated to the MGC will be removed automatically. Note that MGW can't communicate with MGC if NMS does not add static IP address into cMgcIpConfigTable for the MGC. [2] changing the value from 'internalOnly' to 'externalOnly' 1) precondition All MGC associated statically configured IP addresses must be removed from cMgcIpConfigTable by NMS before setting 'externalOnly' value to this object. An inconsistentValue error is generated for setting 'externalOnly' value if the MGC associated IP addresses are not removed. 2) behavior After successfully setting 'externalOnly' value to this object, the MGC domain name will be resolved by MGW software using external DNS name server and the resulting IP addresses will be added to cMgcIpConfigTable automatically.

OID symbolic	OID numeric	Type	Access	Description
ciscoMgcMIB	1.3.6.1.4.1.9.9.321			This MIB is used to support MGC(call agent) and MGC Group configuration. The MGC or MGC group configuration is performed under a specific gateway(cmgwIndex). The call agent is an external element (outside of gateway) with call control intelligence to control call connection in gateway. The protocols used for communication between voice gateway and call agent included SGCP, MGCP, ... Multiple IP addresses can be associated with one call agent. An MGC group is a logical grouping of several MGCs into one group. MGC redundancy is used to support multi call agent for one gateway. With MGC redundancy, a voice gateway can send gateway-initiated-commands to the next MGC in the MGC group if it fails to receive response from any IP address(es) associated to the current MGC. To use MGC redundancy in gateway: Step 1: add individual entry (in any order) for profile MGC Step 2: make association between the entries 1 IP with MGC 2 MGC with MGC group 1/2 protocol with MGC group 3 MGC group with profile or MGC group with gateway Only if a MGC group at least is associated with one profile or gateway, then the MGC group can be used, otherwise the MGC group is useless. To delete the following entries, it is needed to do de-association first: profile MGC When do de-association, the order is opposite to that of association.
cMgcMibNotifications	1.3.6.1.4.1.9.9.321.0
cMgcMibObjects	1.3.6.1.4.1.9.9.321.1
cMgcConfig	1.3.6.1.4.1.9.9.321.1.1
cMgcConfigTable	1.3.6.1.4.1.9.9.321.1.1.1		not-accessible	This table is used for configuring MGC related parameters.
cMgcConfigEntry	1.3.6.1.4.1.9.9.321.1.1.1.1		not-accessible	Each entry represents a call agent(MGC). Each entry in this table should have a unique domain name representing a call agent. Adding/deleting entry in this table is controlled by 'cMediaGwDomainNameConfigTable' of CISCO-MEDIA-GATEWAY-MIB: 1. Entry creation An entry in this table is created when its associated entry in the 'cMediaGwDomainNameConfigTable' is created with the value of 'mgc(3)' in the cmgwConfigDomainNameEntity object. The 'cmgwConfigDomainName' of the associated entry in the 'cMediaGwDomainNameConfigTable' will be taken as 'cMgcDomainName' of the new entry. 2. Entry deletion An entry of this table is deleted when its associated entry in 'cMediaGwDomainNameConfigTable' is deleted.
I32 cMgcIndex	1.3.6.1.4.1.9.9.321.1.1.1.1.1	Integer32	not-accessible	A unique index to identify each MGC which will communicate with this media gateway.
STR cMgcDomainName	1.3.6.1.4.1.9.9.321.1.1.1.1.2	SnmpAdminString	read-only	This object contains the same name as the one in the 'cMgcDomainName object' of the associated entry in 'cMediaGwDomainNameConfigTable'.
I32 cMgcNumMgcGroups	1.3.6.1.4.1.9.9.321.1.1.1.1.3	Integer32	read-only	This object is used to indicate number of MGC group with which this MGC associated. The value zero means this MGC is not associated with any MGC Group. If this value greater than zero, then the MGC entry can not be deleted.
I32 cMgcNumIP	1.3.6.1.4.1.9.9.321.1.1.1.1.4	Integer32	read-only	This object is used to indicate number of IP addresses are associated with this MGC. The value zero means there is no IP address associated with this MGC. The MGC can not be deleted if the value of this object is non-zero and cMgcResolution is configured to 'internalOnly'.
INT cMgcResolution	1.3.6.1.4.1.9.9.321.1.1.1.1.5	INTEGER	read-write	This object determines the kind of resolution to be applied for this MGC. 'internalOnly' means that the gateway will not try to resolve the IP address for this domain name using external DNS name server. 'externalOnly' means the IP address for this domain name will be resolved externally using DNS name server. The request to change from 'internalOnly' to 'externalOnly' will be rejected if the DNS name server is not available for gateway. The IP addresses related to the same MGC should have the same cMgcResolution. The value of the MGC associated objects in the cMgcIpConfigTable can not be modified by NMS if the value of cMgcResolution for the MGC is 'externalOnly'. The following are the behavior of changing the value of this object. [1] changing the value from 'externalOnly' to 'internalOnly' 1) precondition MGC is not associated with any MGC group (value of cMgcNumMgcGroups is zero). 2) behavior If the value of this object is changed successfully, all existing IP addresses in cMgcIpConfigTable that are associated to the MGC will be removed automatically. Note that MGW can't communicate with MGC if NMS does not add static IP address into cMgcIpConfigTable for the MGC. [2] changing the value from 'internalOnly' to 'externalOnly' 1) precondition All MGC associated statically configured IP addresses must be removed from cMgcIpConfigTable by NMS before setting 'externalOnly' value to this object. An inconsistentValue error is generated for setting 'externalOnly' value if the MGC associated IP addresses are not removed. 2) behavior After successfully setting 'externalOnly' value to this object, the MGC domain name will be resolved by MGW software using external DNS name server and the resulting IP addresses will be added to cMgcIpConfigTable automatically.
cMgcIpConfigTable	1.3.6.1.4.1.9.9.321.1.1.2		not-accessible	This table contains MGC related IP addresses. MGC index(cMgcIndex) is a part of index of this table, so IP address in this table is automatically associated with the MGC. Multiple IP addresses can be associated with the same MGC. Under the same MGC (cMgcIndex is same) all IP addresses are equivalent. all IP addresses will share the same domain name: 'cMgcDomainName' in cMgcConfigTable.
cMgcIpConfigEntry	1.3.6.1.4.1.9.9.321.1.1.2.1		not-accessible	Each entry represents an IP address which is associated with the MGC(cMgcIndex). When cMgcResolution is configured to 'externalOnly', user cannot add/delete/modify any entry.
I32 cMgcIpIndex	1.3.6.1.4.1.9.9.321.1.1.2.1.1	Integer32	not-accessible	A unique index to identify the address of a specific MGC. The MGC is represented by cMgcIndex.
IPt cMgcIpAddressType	1.3.6.1.4.1.9.9.321.1.1.2.1.2	InetAddressType	read-create	This object is the IP address type for cMgcIpAddress.
IP cMgcIpAddress	1.3.6.1.4.1.9.9.321.1.1.2.1.3	InetAddress	read-create	This object represents the configured IP address. After adding the entry, this object can not be modified.
I32 cMgcIpPreference	1.3.6.1.4.1.9.9.321.1.1.2.1.4	Integer32	read-create	This object represents preference of the cMgcIpAddress in the given MGC. The lower the number the higher the preference. i.e. 1 will have higher preference than 2. IF more than one IP have the same preference, gateway will select them one by one.
ROW cMgcIpRowStatus	1.3.6.1.4.1.9.9.321.1.1.2.1.5	RowStatus	read-create	This object is used to create/modify/delete entry. In order to delete an entry, following conditions need to be met: 1. The MGC to which this IP address is being added, should be existing. 2. The MGC's resolution (cMgcResolution) should be 'internal only'. 3. the mandatory object is cMgcIpAddress After the IP address added to the MGC the related 'cMgcNumIP' in MGC table will be incremented by 1. In order to delete an entry, following conditions need to be met: 1. The MGC's resolution (cMgcResolution) should be 'internal only'. 2. The IP address should not be the only one in the MGC while the MGC is associated with MGC group. This means if the value of 'cMgcNumIP' is equal to 1 and the value of 'cMgcNumMgcGroups' is non-zero, this IP address is the only one associated with the MGC and it is possible that this IP address is also the only one associated with MGC group. Therefore this IP address can not be deleted. After deleting the IP address from the MGC the related 'cMgcNumIP' in MGC table will be decremented by 1.
cMgcGroupConfig	1.3.6.1.4.1.9.9.321.1.2
cMgcGrpParamTable	1.3.6.1.4.1.9.9.321.1.2.1		not-accessible	This table containing information about MGC group related profile/protocol association and parameters.
cMgcGrpParamEntry	1.3.6.1.4.1.9.9.321.1.2.1.1		not-accessible	Entry of cMgcGrpParamTable. Each entry includes the information shared by a group of MGC
CMG cMgcGrpIndex	1.3.6.1.4.1.9.9.321.1.2.1.1.1	CMgcGroupIndex	not-accessible	A unique index to identify a MGC group.
I32 cMgcGrpNumMgc	1.3.6.1.4.1.9.9.321.1.2.1.1.2	Integer32	read-only	This object is used to indicate number of MGCs to be associated with this MGC Group. The value zero means there is no MGC in the MGC Group. When the entry create, this value is set to 0. Adding/deleting MGC to/from MGC group is through cMgcGrpTable. After a MGC added/deleted to/from this MGC group, the value of this object will be incremented/decremented by 1. If the value of this object is zero, it is not allowed to associate this MGC group with any profile or gateway.
U32 cMgcGrpAssociationInfo	1.3.6.1.4.1.9.9.321.1.2.1.1.3	Unsigned32	read-only	This object indicates the association between MGC group and profile/gateway with bitmap format. It is 1:N mapping, e.g., each profile or gateway can only have one MGC group, but one MGC group can be associated with multi profile and gateway. The possible bit positions used in the bitmap are listed as follows: Bit profile/gateway value --------------------------------------------------------------- 0 profile 1 0: the MGC group is not associated with it 1: the MGC group is associated with it 1 profile 2 0: the MGC group is not associated with it 1: the MGC group is associated with it 2 profile 3 0: the MGC group is not associated with it 1: the MGC group is associated with it 3 profile 4 0: the MGC group is not associated with it 1: the MGC group is associated with it ... ... 30 profile 31 0: the MGC group is not associated with it 1: the MGC group is associated with it 31 gateway 0: the MGC group is not associated with it 1: the MGC group is associated with it The value zero means the MGC Group is not associated with any profile or gateway.
I32 cMgcGrpNumProtocol	1.3.6.1.4.1.9.9.321.1.2.1.1.4	Integer32	read-only	This object is used to indicate number of protocols associated with this MGC group. The value zero means there is no protocol associated with this MGC group. When the entry create, this object is set to 0. The association between protocol and MGC group is configured via cMgcGrpProtocolTable. After a protocol is associated/de-associated with this MGC group, this object will be incremented/decremented by 1. If this object is zero, it is not allowed to associate the MGC group with any profile or gateway.
T/F cMgcGrpStateChangeNtfy	1.3.6.1.4.1.9.9.321.1.2.1.1.5	TruthValue	read-write	This object enables or disables sending gateway state change notifications to call agent.
cMgcGrpTable	1.3.6.1.4.1.9.9.321.1.2.2		not-accessible	This table represents the association of MGCs and MGC group. Each MGC group consists of one or more MGCs and each MGC can belong to one or more MGC groups. Therefore it is an N to N mapping.
cMgcGrpEntry	1.3.6.1.4.1.9.9.321.1.2.2.1		not-accessible	The entry is represented an association of a MGC with a MGC group.
I32 cMgcGrpMgcPreference	1.3.6.1.4.1.9.9.321.1.2.2.1.1	Integer32	read-create	The preference of the MGC in the MGC group. The lower the number the higher the preference. i.e. 1 will have higher preference than 2.
CIS cMgcGrpMgcUdpPort	1.3.6.1.4.1.9.9.321.1.2.2.1.2	CiscoPort	read-create	The UDP port of the MGC in the MGC group. The zero means there is no specific UDP port, the UDP port in the protocol table will be used.
ROW cMgcGrpRowStatus	1.3.6.1.4.1.9.9.321.1.2.2.1.3	RowStatus	read-create	This object is used to create a new row or modify or delete an existing row in this table. In order to add an MGC to a MGC group, the following conditions need to be met: 1. the MGC and the MGC group should be existing 2. at least one IP address is associated with the MGC if the MGC is configured for internal resolution. After the MGC added to the MGC group, the related cMgcGrpNumMgc will be incremented by 1. cMgcNumMgcGroups will be incremented by 1. In order to delete an MGC from MGC group, the following conditions need to be met: The MGC is not the only MGC associated with the MGC group if the MGC group is associated with gateway or one or more profiles. After the MGC added to the MGC group, the related cMgcGrpNumMgc will be decremented by 1. cMgcNumMgcGroups will be decremented by 1.
cMgcGrpProtocolTable	1.3.6.1.4.1.9.9.321.1.2.3		not-accessible	cMgcGrpProtocolTable is used to add protocol to MGC group. This table is designed to support multi protocol for MGC group. The MGC group to protocol is N to N mapping.
cMgcGrpProtocolEntry	1.3.6.1.4.1.9.9.321.1.2.3.1		not-accessible	Entry of cMgcGrpProtocolTable.
I32 cMgcGrpProtocolPreference	1.3.6.1.4.1.9.9.321.1.2.3.1.1	Integer32	read-create	The preference of the Protocol in the MGC group. The lower the number the higher the preference. i.e. 1 will have higher preference than 2. When gateway does not know which protocol is used by a call agent the preference is used to make the decision. But if gateway knows which protocol used by a call agent, gateway will use that protocol (as long as the protocol is added to the MGC group, irrespective of the preference) to communicate with the call agent. For example: when gateway return a call agent message, gateway will use the protocol which used by the call agent to send the message.
ROW cMgcGrpProtocolRowStatus	1.3.6.1.4.1.9.9.321.1.2.3.1.2	RowStatus	read-create	This object is used to create a new row or modify or delete an existing row in this table. In order to add a protocol to MGC group, the following condition need to be met: Both the protocol and the MGC group should be existing After the protocol added to the MGC group, the related cMgcGrpNumProtocol will be incremented by 1. In order to delete a protocol from MGC group, the following condition need to be met: The protocol to be deleted should not be the only one in the MGC group when the MGC group is used by a gateway or a profile. This means if the value of cMgcGrpNumProtocol is equal to 1 and the value of cMgcGrpAssociationInfo is non-zero, this protocol is the only one associated with the MGC group which is still in use by gateways or some profiles. Therefore this protocol can not be deleted. After the protocol deleted from the MGC group, the related cMgcGrpNumProtocol will be decremented by 1.
cMgcMIBConformance	1.3.6.1.4.1.9.9.321.2
cMgcMIBCompliances	1.3.6.1.4.1.9.9.321.2.1
cMgcMIBCompliance	1.3.6.1.4.1.9.9.321.2.1.1			Compliance statement for CISCO-MGC-MIB.
cMgcMIBGroups	1.3.6.1.4.1.9.9.321.2.2
cMgcMIBGroup	1.3.6.1.4.1.9.9.321.2.2.1			A collection of objects providing per MGC basis configuration information.
cMgcIpMIBGroup	1.3.6.1.4.1.9.9.321.2.2.2			A collection of objects providing IP (in MGC) configuration information.
cMgcGrpParamGroup	1.3.6.1.4.1.9.9.321.2.2.3			A collection of objects providing per MGC group configuration information.
cMgcGrpGroup	1.3.6.1.4.1.9.9.321.2.2.4			A collection of objects providing MGC (in MGC group) configuration information.
cMgcGrpProtocolGroup	1.3.6.1.4.1.9.9.321.2.2.5			A collection of objects providing Protocol (in MGC group) configuration information.

CiscoPort (1)
CIS cMgcGrpMgcUdpPort	1.3.6.1.4.1.9.9.321.1.2.2.1.2	CiscoPort	read-create	The UDP port of the MGC in the MGC group. The zero means there is no specific UDP port, the UDP port in the protocol table will be used.
CMgcGroupIndex (1)
CMG cMgcGrpIndex	1.3.6.1.4.1.9.9.321.1.2.1.1.1	CMgcGroupIndex	not-accessible	A unique index to identify a MGC group.
InetAddress (1)
IP cMgcIpAddress	1.3.6.1.4.1.9.9.321.1.1.2.1.3	InetAddress	read-create	This object represents the configured IP address. After adding the entry, this object can not be modified.
InetAddressType (1)
IPt cMgcIpAddressType	1.3.6.1.4.1.9.9.321.1.1.2.1.2	InetAddressType	read-create	This object is the IP address type for cMgcIpAddress.
INTEGER (1)
INT cMgcResolution	1.3.6.1.4.1.9.9.321.1.1.1.1.5	INTEGER	read-write	This object determines the kind of resolution to be applied for this MGC. 'internalOnly' means that the gateway will not try to resolve the IP address for this domain name using external DNS name server. 'externalOnly' means the IP address for this domain name will be resolved externally using DNS name server. The request to change from 'internalOnly' to 'externalOnly' will be rejected if the DNS name server is not available for gateway. The IP addresses related to the same MGC should have the same cMgcResolution. The value of the MGC associated objects in the cMgcIpConfigTable can not be modified by NMS if the value of cMgcResolution for the MGC is 'externalOnly'. The following are the behavior of changing the value of this object. [1] changing the value from 'externalOnly' to 'internalOnly' 1) precondition MGC is not associated with any MGC group (value of cMgcNumMgcGroups is zero). 2) behavior If the value of this object is changed successfully, all existing IP addresses in cMgcIpConfigTable that are associated to the MGC will be removed automatically. Note that MGW can't communicate with MGC if NMS does not add static IP address into cMgcIpConfigTable for the MGC. [2] changing the value from 'internalOnly' to 'externalOnly' 1) precondition All MGC associated statically configured IP addresses must be removed from cMgcIpConfigTable by NMS before setting 'externalOnly' value to this object. An inconsistentValue error is generated for setting 'externalOnly' value if the MGC associated IP addresses are not removed. 2) behavior After successfully setting 'externalOnly' value to this object, the MGC domain name will be resolved by MGW software using external DNS name server and the resulting IP addresses will be added to cMgcIpConfigTable automatically.
Integer32 (9)
I32 cMgcGrpMgcPreference	1.3.6.1.4.1.9.9.321.1.2.2.1.1	Integer32	read-create	The preference of the MGC in the MGC group. The lower the number the higher the preference. i.e. 1 will have higher preference than 2.
I32 cMgcGrpNumMgc	1.3.6.1.4.1.9.9.321.1.2.1.1.2	Integer32	read-only	This object is used to indicate number of MGCs to be associated with this MGC Group. The value zero means there is no MGC in the MGC Group. When the entry create, this value is set to 0. Adding/deleting MGC to/from MGC group is through cMgcGrpTable. After a MGC added/deleted to/from this MGC group, the value of this object will be incremented/decremented by 1. If the value of this object is zero, it is not allowed to associate this MGC group with any profile or gateway.
I32 cMgcGrpNumProtocol	1.3.6.1.4.1.9.9.321.1.2.1.1.4	Integer32	read-only	This object is used to indicate number of protocols associated with this MGC group. The value zero means there is no protocol associated with this MGC group. When the entry create, this object is set to 0. The association between protocol and MGC group is configured via cMgcGrpProtocolTable. After a protocol is associated/de-associated with this MGC group, this object will be incremented/decremented by 1. If this object is zero, it is not allowed to associate the MGC group with any profile or gateway.
I32 cMgcGrpProtocolPreference	1.3.6.1.4.1.9.9.321.1.2.3.1.1	Integer32	read-create	The preference of the Protocol in the MGC group. The lower the number the higher the preference. i.e. 1 will have higher preference than 2. When gateway does not know which protocol is used by a call agent the preference is used to make the decision. But if gateway knows which protocol used by a call agent, gateway will use that protocol (as long as the protocol is added to the MGC group, irrespective of the preference) to communicate with the call agent. For example: when gateway return a call agent message, gateway will use the protocol which used by the call agent to send the message.
I32 cMgcIndex	1.3.6.1.4.1.9.9.321.1.1.1.1.1	Integer32	not-accessible	A unique index to identify each MGC which will communicate with this media gateway.
I32 cMgcIpIndex	1.3.6.1.4.1.9.9.321.1.1.2.1.1	Integer32	not-accessible	A unique index to identify the address of a specific MGC. The MGC is represented by cMgcIndex.
I32 cMgcIpPreference	1.3.6.1.4.1.9.9.321.1.1.2.1.4	Integer32	read-create	This object represents preference of the cMgcIpAddress in the given MGC. The lower the number the higher the preference. i.e. 1 will have higher preference than 2. IF more than one IP have the same preference, gateway will select them one by one.
I32 cMgcNumIP	1.3.6.1.4.1.9.9.321.1.1.1.1.4	Integer32	read-only	This object is used to indicate number of IP addresses are associated with this MGC. The value zero means there is no IP address associated with this MGC. The MGC can not be deleted if the value of this object is non-zero and cMgcResolution is configured to 'internalOnly'.
I32 cMgcNumMgcGroups	1.3.6.1.4.1.9.9.321.1.1.1.1.3	Integer32	read-only	This object is used to indicate number of MGC group with which this MGC associated. The value zero means this MGC is not associated with any MGC Group. If this value greater than zero, then the MGC entry can not be deleted.
RowStatus (3)
ROW cMgcGrpProtocolRowStatus	1.3.6.1.4.1.9.9.321.1.2.3.1.2	RowStatus	read-create	This object is used to create a new row or modify or delete an existing row in this table. In order to add a protocol to MGC group, the following condition need to be met: Both the protocol and the MGC group should be existing After the protocol added to the MGC group, the related cMgcGrpNumProtocol will be incremented by 1. In order to delete a protocol from MGC group, the following condition need to be met: The protocol to be deleted should not be the only one in the MGC group when the MGC group is used by a gateway or a profile. This means if the value of cMgcGrpNumProtocol is equal to 1 and the value of cMgcGrpAssociationInfo is non-zero, this protocol is the only one associated with the MGC group which is still in use by gateways or some profiles. Therefore this protocol can not be deleted. After the protocol deleted from the MGC group, the related cMgcGrpNumProtocol will be decremented by 1.
ROW cMgcGrpRowStatus	1.3.6.1.4.1.9.9.321.1.2.2.1.3	RowStatus	read-create	This object is used to create a new row or modify or delete an existing row in this table. In order to add an MGC to a MGC group, the following conditions need to be met: 1. the MGC and the MGC group should be existing 2. at least one IP address is associated with the MGC if the MGC is configured for internal resolution. After the MGC added to the MGC group, the related cMgcGrpNumMgc will be incremented by 1. cMgcNumMgcGroups will be incremented by 1. In order to delete an MGC from MGC group, the following conditions need to be met: The MGC is not the only MGC associated with the MGC group if the MGC group is associated with gateway or one or more profiles. After the MGC added to the MGC group, the related cMgcGrpNumMgc will be decremented by 1. cMgcNumMgcGroups will be decremented by 1.
ROW cMgcIpRowStatus	1.3.6.1.4.1.9.9.321.1.1.2.1.5	RowStatus	read-create	This object is used to create/modify/delete entry. In order to delete an entry, following conditions need to be met: 1. The MGC to which this IP address is being added, should be existing. 2. The MGC's resolution (cMgcResolution) should be 'internal only'. 3. the mandatory object is cMgcIpAddress After the IP address added to the MGC the related 'cMgcNumIP' in MGC table will be incremented by 1. In order to delete an entry, following conditions need to be met: 1. The MGC's resolution (cMgcResolution) should be 'internal only'. 2. The IP address should not be the only one in the MGC while the MGC is associated with MGC group. This means if the value of 'cMgcNumIP' is equal to 1 and the value of 'cMgcNumMgcGroups' is non-zero, this IP address is the only one associated with the MGC and it is possible that this IP address is also the only one associated with MGC group. Therefore this IP address can not be deleted. After deleting the IP address from the MGC the related 'cMgcNumIP' in MGC table will be decremented by 1.
SnmpAdminString (1)
STR cMgcDomainName	1.3.6.1.4.1.9.9.321.1.1.1.1.2	SnmpAdminString	read-only	This object contains the same name as the one in the 'cMgcDomainName object' of the associated entry in 'cMediaGwDomainNameConfigTable'.
TruthValue (1)
T/F cMgcGrpStateChangeNtfy	1.3.6.1.4.1.9.9.321.1.2.1.1.5	TruthValue	read-write	This object enables or disables sending gateway state change notifications to call agent.
Unsigned32 (1)
U32 cMgcGrpAssociationInfo	1.3.6.1.4.1.9.9.321.1.2.1.1.3	Unsigned32	read-only	This object indicates the association between MGC group and profile/gateway with bitmap format. It is 1:N mapping, e.g., each profile or gateway can only have one MGC group, but one MGC group can be associated with multi profile and gateway. The possible bit positions used in the bitmap are listed as follows: Bit profile/gateway value --------------------------------------------------------------- 0 profile 1 0: the MGC group is not associated with it 1: the MGC group is associated with it 1 profile 2 0: the MGC group is not associated with it 1: the MGC group is associated with it 2 profile 3 0: the MGC group is not associated with it 1: the MGC group is associated with it 3 profile 4 0: the MGC group is not associated with it 1: the MGC group is associated with it ... ... 30 profile 31 0: the MGC group is not associated with it 1: the MGC group is associated with it 31 gateway 0: the MGC group is not associated with it 1: the MGC group is associated with it The value zero means the MGC Group is not associated with any profile or gateway.
No type (24)
ciscoMgcMIB	1.3.6.1.4.1.9.9.321			This MIB is used to support MGC(call agent) and MGC Group configuration. The MGC or MGC group configuration is performed under a specific gateway(cmgwIndex). The call agent is an external element (outside of gateway) with call control intelligence to control call connection in gateway. The protocols used for communication between voice gateway and call agent included SGCP, MGCP, ... Multiple IP addresses can be associated with one call agent. An MGC group is a logical grouping of several MGCs into one group. MGC redundancy is used to support multi call agent for one gateway. With MGC redundancy, a voice gateway can send gateway-initiated-commands to the next MGC in the MGC group if it fails to receive response from any IP address(es) associated to the current MGC. To use MGC redundancy in gateway: Step 1: add individual entry (in any order) for profile MGC Step 2: make association between the entries 1 IP with MGC 2 MGC with MGC group 1/2 protocol with MGC group 3 MGC group with profile or MGC group with gateway Only if a MGC group at least is associated with one profile or gateway, then the MGC group can be used, otherwise the MGC group is useless. To delete the following entries, it is needed to do de-association first: profile MGC When do de-association, the order is opposite to that of association.
cMgcConfig	1.3.6.1.4.1.9.9.321.1.1
cMgcConfigEntry	1.3.6.1.4.1.9.9.321.1.1.1.1		not-accessible	Each entry represents a call agent(MGC). Each entry in this table should have a unique domain name representing a call agent. Adding/deleting entry in this table is controlled by 'cMediaGwDomainNameConfigTable' of CISCO-MEDIA-GATEWAY-MIB: 1. Entry creation An entry in this table is created when its associated entry in the 'cMediaGwDomainNameConfigTable' is created with the value of 'mgc(3)' in the cmgwConfigDomainNameEntity object. The 'cmgwConfigDomainName' of the associated entry in the 'cMediaGwDomainNameConfigTable' will be taken as 'cMgcDomainName' of the new entry. 2. Entry deletion An entry of this table is deleted when its associated entry in 'cMediaGwDomainNameConfigTable' is deleted.
cMgcConfigTable	1.3.6.1.4.1.9.9.321.1.1.1		not-accessible	This table is used for configuring MGC related parameters.
cMgcGroupConfig	1.3.6.1.4.1.9.9.321.1.2
cMgcGrpEntry	1.3.6.1.4.1.9.9.321.1.2.2.1		not-accessible	The entry is represented an association of a MGC with a MGC group.
cMgcGrpGroup	1.3.6.1.4.1.9.9.321.2.2.4			A collection of objects providing MGC (in MGC group) configuration information.
cMgcGrpParamEntry	1.3.6.1.4.1.9.9.321.1.2.1.1		not-accessible	Entry of cMgcGrpParamTable. Each entry includes the information shared by a group of MGC
cMgcGrpParamGroup	1.3.6.1.4.1.9.9.321.2.2.3			A collection of objects providing per MGC group configuration information.
cMgcGrpParamTable	1.3.6.1.4.1.9.9.321.1.2.1		not-accessible	This table containing information about MGC group related profile/protocol association and parameters.
cMgcGrpProtocolEntry	1.3.6.1.4.1.9.9.321.1.2.3.1		not-accessible	Entry of cMgcGrpProtocolTable.
cMgcGrpProtocolGroup	1.3.6.1.4.1.9.9.321.2.2.5			A collection of objects providing Protocol (in MGC group) configuration information.
cMgcGrpProtocolTable	1.3.6.1.4.1.9.9.321.1.2.3		not-accessible	cMgcGrpProtocolTable is used to add protocol to MGC group. This table is designed to support multi protocol for MGC group. The MGC group to protocol is N to N mapping.
cMgcGrpTable	1.3.6.1.4.1.9.9.321.1.2.2		not-accessible	This table represents the association of MGCs and MGC group. Each MGC group consists of one or more MGCs and each MGC can belong to one or more MGC groups. Therefore it is an N to N mapping.
cMgcIpConfigEntry	1.3.6.1.4.1.9.9.321.1.1.2.1		not-accessible	Each entry represents an IP address which is associated with the MGC(cMgcIndex). When cMgcResolution is configured to 'externalOnly', user cannot add/delete/modify any entry.
cMgcIpConfigTable	1.3.6.1.4.1.9.9.321.1.1.2		not-accessible	This table contains MGC related IP addresses. MGC index(cMgcIndex) is a part of index of this table, so IP address in this table is automatically associated with the MGC. Multiple IP addresses can be associated with the same MGC. Under the same MGC (cMgcIndex is same) all IP addresses are equivalent. all IP addresses will share the same domain name: 'cMgcDomainName' in cMgcConfigTable.
cMgcIpMIBGroup	1.3.6.1.4.1.9.9.321.2.2.2			A collection of objects providing IP (in MGC) configuration information.
cMgcMIBCompliance	1.3.6.1.4.1.9.9.321.2.1.1			Compliance statement for CISCO-MGC-MIB.
cMgcMIBCompliances	1.3.6.1.4.1.9.9.321.2.1
cMgcMIBConformance	1.3.6.1.4.1.9.9.321.2
cMgcMIBGroup	1.3.6.1.4.1.9.9.321.2.2.1			A collection of objects providing per MGC basis configuration information.
cMgcMIBGroups	1.3.6.1.4.1.9.9.321.2.2
cMgcMibNotifications	1.3.6.1.4.1.9.9.321.0
cMgcMibObjects	1.3.6.1.4.1.9.9.321.1

RFC description

Cisco Media Gateway Controller vendor-private MIB for VoIP gateway management.

Start monitoring Cisco Media Gateway Controller (MGC) platforms (legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-MGC-MIB

This MIB depends on

Related MIBs

What Is CISCO-MGC-MIB?

What Can Be Monitored

Supported Devices

Monitoring Examples

RFC description