CISCO-WAN-MG-MIB: View SNMP OID List / Download MIB

The MIB module for managing Media Gateways (MGs). Terms used: MG: Media Gateway MGC: Media Gateway Controller MGCP: Media Gateway Control Protocol NE: Notified Entity RSIP: Restart In Progress (MGCP standard message)

Denotes name of the MG, as it is identified by media gateway controllers. This corresponds to a domain name under which the Media Gateway could also be registered in a DNS.

This object indicates the current admin state of the Media Gateway. The possible admin states are: 'inService' - The MG is ready to provide service. In this state, the MG will respond to connection control requests, emit autonomous messages to MGCs as applicable, etc. 'commandedOutOfService' - The MG does not provide service and all resources have been released. In this state, the MG will not respond to any connection control requests or emit autonomous messages. 'pendingOutOfService' - This is a transitional state prior to going 'commandedOutOfService'. In this state the MG provides service but does not accept new service requests (i.e. creation of connections) will transition to 'commandedOutOfService' according to 'mgShutdownGraceTime'. Enumeration: 'commandedOutOfService': 2, 'pendingOutOfService': 3, 'inService': 1.

This control object is used to change the service state of the MG from 'inService' to 'commandedOutOfService' and from 'commandedOutOfService' to 'inService'. The resulting service state of the gateway is represented by 'mgAdministrativeState'. If set, this object triggers the following: 'inService': Transition 'mgAdministrativeState' to 'inService'. In the course, the MG's MGCs may get notified of this transition, e.g. in the case of MGCP through emission of RSIPs to registered call agents according to policy. 'forcefulOutOfService': Take the gateway out-of-service forcefully. This releases any resources at the MG. In the course, the MGCs may get notified of this transition, e.g. in the case of MGCP through emission of RSIPs to registered call agents according to policy. 'gracefulOutOfService': Take the gateway out-of-service gracefully. If there are no resources existing, 'mgAdministrative' transitions to 'commandedOutOfService' immediately. If resources exist, 'mgAdministrativeState' transitions to 'pendingOutOfService' thus initiating a graceful shutdown. In the course, the MGs MGCs may get notified of this transition, e.g. in the case of MGCP through emission of RSIPs to registered call agents according to policy. Enumeration: 'gracefulOutOfService': 3, 'forcefulOutOfService': 2, 'inService': 1.

This object indicates the time in seconds after which an MG will transition from 'gracefulOutOfService' to 'forcefulOutOfService'. A value of -1 indicates that the MG allows for draining, i.e. will automatically transition after the last resource in use has been released. Otherwise, it essentially indicates the amount of time an MGC has to perform any cleanup, e.g. deletion of connections etc.

This is a table which identifies the protocols, along with their revisions that the media gateway supports for purposes of communication with an MGC. The table is created by the agent at system startup and cannot changed.

Represents an individual table entry in mgSupportedProtocolTable.

Serves as index to this table.

A control protocol and its revision supported by the call gateway. For example: 'MGCP 0.1 11/9/99' The protocol can be one of the control protocols like MGCP or it can be a signaling backhaul protocol or it can be resource co-ordination protocol like SRCP.

This is a table which contains information about the individual MGCs.

Represents an individual table entry in mgcTable.

Serves as index to this table.

Denotes the name of the media gateway controller. This corresponds to a domain name under which the MGC could also be registered in a DNS. Once the row has become active, this value may not be modified.

Indicates how the MG resolves the IP address of the MGC. 'true(1)' - the resolution is done using an external DNS server. 'false(2)' - the resolution is done using mgcResolutionTable.

Represents the state of the association between the MG and the MGC. The possible values are: 'mgcUnassociated' : MG and MGC are not associated. For example, in the case where MGCP is the coordination protocol, it means no subscription to autonomous messages such as RSIP but control requests would be answered. 'mgcAssociated' : MG and MGC are associated. E.g. in the case where MGC is the coordination protocol, it means MGC is subscribed to autonomous messages such as RSIP. 'mgcAssociatedCommLoss' : Associated but MGC unreachable. This object is being moved to the mgcRedundancyGrpParamTable. This object is deprecated because the association state is defined per MGC redundancy group, rather than per MGC. Enumeration: 'mgcAssociated': 2, 'mgcAssociatedCommLoss': 3, 'mgcUnassociated': 1.

Used to control the association state, as represented by mgcAssociationState. The possible value for a set operation on this object are: 'mgcUnassociate': Transition from any state to 'mgcUnassociated'. If registered, MG will initiate deregistration. 'mgcAssociate' : Transition to 'mgcAssociated'. If applicable, MG will register with MGC. If MGCP is the coordination protocol, MG will send RSIP. If MG cannot establish communication, it will subsequently transition into 'mgcAssociatedCommLoss' for the 'mgcAssociationState' object. If MG is already associated with MGC, no transition will take place and mgcAssociationState shall not change. 'mgcClear' : No action will be taken. This means that the Media Gateway will not initiate any association/unassociation. This object is being moved to the mgcRedundancyGrpParamTable. This object is deprecated because the association state control is defined per MGC redundancy group, rather than per MGC. Enumeration: 'mgcUnassociate': 1, 'mgcClear': 3, 'mgcAssociate': 2.

Indicates what MG will do when mgcAssociationState transitions to unassociated. 'mgcNoAction' : indicates that MG will take no further action. In particular, no resources will be released nor connections be flushed. 'mgcRelease' : indicates that upon unassociation, the MG will release all resources and flush all connections. This object may not always be configurable, i.e. be read only in some agent implementations. In these cases, mgcNoAction shall be supported as the default value. Enumeration: 'mgcRelease': 2, 'mgcNoAction': 1.

Indicates how long, in seconds, upon detection of a communication loss, subscriptions to autonomous notifications (such as notification requests and RSIPs in the case of MGCP) remain valid and communications will be reattempted for an MGC in 'mgcAssociatedCommLoss' state. A value of -1 indicates that the MGC may remain in 'mgcAssociatedCommLoss' state indefinitely. A value of 0 indicates that the MGC transitions into 'mgcUnassociated' state immediately. This object may not always be configurable, i.e. be read only in some agent implementations. An MG implementation may not support differentiation of the timeout between associations. In such an event, any modification to the value for one MGC will take effect globally.

Controls the creation and deletion of a table entry. 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 the row, a value for mgcName must be provided. This mgcName should be already added in mgDomainName table and at least 1 IP should associated to this mgcName. To all other objects, defaults defined by the agent implementation may apply. Deletion of a row with mgcAssociationState other than unassociated shall be rejected.

This table contains information about which protocols are being used in a particular association between the gateway and the MGCs. Because there may be a number of different protocols in use for a particular control association between the gateway and an MGC, this information is kept in a separate table rather than being included in mgcTable. In effect, it constitutes a relationship between mgcTable and mgSupportedProtocolTable. With support for multiple MGC redundancy groups, the protocols will be defined per MGC redundancy group rather than per MGC. A new table mgcRedundancyGrpProtocolTable is introduced.

Represents an individual table entry in mgcProtocolTable. mgcNumber references the media gateway controller, constituting a foreign key into mgcTable and adapting the value of mgcNumber of that MGC. mgProtocolNumber references the protocol, reflecting the mgProtocolNumber from the mgSupportedProtocolTable. When active, it is expected that mgcNumber and mgcProtocolNumber contain valid values that maintain referential integrity, i.e. constitute valid foreign keys into mgcTable and mgSupportedProtocolTable respectively. The attempt to create a row that would violate referential integrity shall be rejected. With support for multiple MGC redundancy groups, the protocols will be defined per MGC redundancy group rather than per MGC.

Controls the creation and deletion of a table entry. 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. With support for multiple MGC redundancy groups, the protocols will be defined per MGC redundancy group rather than per MGC.

This object identifies the maximum number of MGCs the MG can have.

This table contains information about the individual endpoints.

Represents an individual table entry in mgEndpointTable.

Identifies endpoint as it is known by the NE. The endpoint number is unique for the entire MG and ranges from 1 to the maximum number of endpoints that the MG can support.

Identifies the DS1 line. Generally, this will correspond to the ifIndex of the physical interface terminating the line. Once the row has become active, this value may not be changed.

Identifies endpoint as it is known by the MGC. If MG and MGC use a mutually agreed upon convention, this may be supplied by the agent, i.e. be read-only.

Indicates the endpoint's bandwidth, in Kbps. Typically, this will be 64 times the number of channels terminated by the endpoint.

Indicates the state of the endpoint. 'mgEndpointActive' - the endpoint is in service and operational. 'mgEndpointFailed' - the endpoint is in service but not operational, e.g. because a line that the endpoint belongs to is in a state of service affecting alarm. 'mgEndpointDegraded' - the endpoint is in service but not fully operational, e.g. in cases with endpoints with channels on multiple lines, when one of the lines is in a state of service affecting alarm If MGCP is used as the control protocol, the following transitions will generally trigger an RSIP command: from 'mgEndpointActive'/'mgEndpointDegraded' to 'mgEndpointFailed' or from 'mgEndpointFailed' to 'mgEndpointDegraded'/'mgEndpointActive'. Transitions between 'mgEndpointActive' and 'mgEndpointDegraded' will generally not trigger emission of RSIP. Enumeration: 'mgEndpointFailed': 2, 'mgEndpointActive': 1, 'mgEndpointDegraded': 3.

Bit map of DS0s used by the endpoint. Bit positions set to '1' represent DS0s used by the endpoint. The Bit position corresponds to the DS0 number. Once the row has become active, this value may not be changed.

Controls the creation and deletion of a table entry. 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 thereby creating an endpoint. An endpoint may be deleted by setting the RowStatus to 'destroy'. Other options such as `createAndWait', 'notInService', 'notReady' will not be used. On creation, values for mgEndpointLineNumber and mgEndpointChannelMap have to be supplied.

Identifies whether the MG creates endpoints for connections involving single channels (e.g. DS0s) dynamically upon receipt of a create connection request in the control protocol, or whether the endpoints have to be configured statically. This does not apply for endpoints involving several channels (such as nx64) which will in general be configured statically. 'dynamic': Endpoint created dynamically if not already existing. 'strictDynamic': Endpoint created dynamically; connection requests must not refer to preexisting endpoint. 'static': Endpoint statically provisioned. This object will in general not be configurable, i.e. be read only in most agent implementations. Enumeration: 'static': 3, 'dynamic': 1, 'strictDynamic': 2.

This table extends the mgEndpointTable. Objects that do not directly describe the endpoint but extend the rules to configure the mgEndpointTable can be added to this table. Each table entry describes an instance of an endpoint on a media gateway.

Each entry represents a media gateway endpoint interface.

This object is used to create multiple rows in the mgEndpointTable as specified in the SNMP PDU, starting from the row specified by the index of the instance for the number of rows specified in this object. The repetition operation will start from the mgEndpointNumber, mgEndpointLineNumber and mgEndpointChannelMap that is specified in the PDU and will add rows for the number specified in this object. If for a given mgEndpointLineNumber all the endpoints channels are exhausted, it will proceed to the next mgEndpointLineNumber. This will continue until the number of repetitions specified in this object is exhausted or the number of DS1s and endpoints is exhausted, whichever comes first. The agent will need to be able to populate the objects in the mgEndpointTable with the appropriate values as new rows are created.

This table contains information about each line in the media gateway.

Represents an individual table entry in lineAssignmentTable.

Identifies the DS1 line. Generally, this will correspond to the ifIndex of the physical interface terminating the line.

Each bit that is set represents that the corresponding DS0 is in use, either because it has been assigned to an endpoint or because it constitutes a signaling channel that is not available for assignment to an endpoint.

Line name as identified by the MGC, if applicable. The default line name is 'LINE'. If MG uses a common convention, this may be supplied by the agent, i.e. be read-only.

This table provides the name to IP address mapping for each of the MGCs, external DNS server, tftp server and announcement server. It also stores the IP addresses of external resolved domain name. Several addresses may be associated with a single name.

Represents an individual table entry in mgcResolutionTable.

Serves as index to this table. The table will be divided into two, index 1 to 88 will be used by the user and index 89 to 176 will be used by the VDNS to fill in the externally resolved IP address.

Denotes the name of the entity (MGC and/or NE) whose address is to be resolved. Once the row has become active, this value may not be changed.

Denotes the IP address of the entity. Once the row has become active, this value may not be changed. To change the IP address, an entry will have to be removed and a new entry will have to be added.

Indicates whether the address is the one currently applied for communications with the system of that name. 'csActive' - name resolves to that IP address 'csInactive' - IP address currently not in use On creation of the row, this value will be 'csInactive', although it may transition immediately to active, triggering the notification of 'mgcCommStateActive' specified in CISCO-VISM-TRAPS-MIB. Enumeration: 'csActive': 1, 'csInactive': 2.

This object can be used by the MG in the selection of an IP address if multiple IP addresses are available for the same name. This object cannot be modified after this entry is created. It has to be unique among various IP addresses of a same domain name. In which case the IP address associated with mgcResolutionPreference 1 would be selected over the IP address associated with mgcResolutionPreference 2.

Controls the creation and deletion of a table entry. An entry may be created using the 'createAndGo' option. mgcResolutionIndex, mgcResolutionName, mgcResolutionIpAddress, and mgcResolutionPreference should be provided when creating an entry. mgcResolutionIndex can be 1 - 88. Entries with index 89 - 176 will be implicitly added when VDNS resolves IP addresses of domain servers. Usually maximum 8 IP addresses can be added to one mgcName. For external DNS server only 3 IP addresses with the highest will be used. Before creating an entry in this table one entry should already been created in mgDomainNameTable with the same name as mgcResolutionName. 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'. Only mgcResolutionIndex should be provided to delete an entry. The last IP within 1 - 88 should not be deleted if the mgcResolutionName is still configured for MGC, tftp server, external DNS server, PRI backhaul session group or announcement server and there is no external resolved IP (entry 89 - 176) for this domain name. Other options such as `createAndWait', 'notInService', 'notReady' will not be used.

All entries statically configured by the customer (i.e. all entries in the top half of the table) will have the flag set to 'internal'. All IP addresses obtained due to external resolution of the domain name (that is, entries in the bottom half of the table) will have this flag set to 'external'. Enumeration: 'internal': 1, 'external': 2.

This table provides the domain names that are configured by users. The domain names could refer to Call Agents, tftp server for CAS file download, external DNS server or announcement server.

Represents an individual table entry in mgDomainNameTable.

This object serves as index to this table.

This object denotes the domain name of MGCs, tftp server, external DNS server or announcement server. Once the row has become active, this value may not be changed.

This object determines the kind of DNS resolution to be applied for a particular domain name. 'internalOnly' means that the gateway will not try to resolve the IP address for this domain name using external DNS. The IP address/es for this domain name will be obtained from the first half of mgcResolutionTable, which are added by the user. 'externalOnly' means the IP address for this domain name will be resolved externally using external DNS. 'internalFirst' means the first preference will be given to statically provisioned IP address/es, followed the IP address/es resolved using external DNS. 'externalFirst' means the first preference will be given to IP addresses resolved using external DNS followed by statically provisioned IP addresses. This object can be modified when mgDomainNameRowStatus is active except that if the mgDomainName refers to external DNS server then this object cannot be changed. The request to change from 'internalOnly' to other types will be rejected if external DNS server is 'NULL'. The external DNS server can be set to 'NULL' through the object vismExtDnsServerDn in CISCO-VISM-MODULE-MIB. When user change this object to 'internalOnly' then all the externally resolved IP addresses should be implicitly deleted from mgcResolutionTable. Enumeration: 'internalFirst': 3, 'externalFirst': 4, 'internalOnly': 1, 'externalOnly': 2.

Controls the creation and deletion and of a table entry. An entry may be created using the 'createAndGo' option. User can only set mgDnsResolutionType to 'internalOnly'. The request to set an entry with mgDnsResolutionType of 'externalOnly', 'internalFirst' or 'externalFirst' would be rejected if the external DNS server is 'NULL'. 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'. The deletion of an entry will be rejected if there is still reference to this domain name. For example, it cannot be deleted if it is configured as MGC, tftp server, external DNS server or announcement server. Also user added IPs should already been deleted. After delete the domain name externally resolved IPs are purged implicitly. The request to change from 'internalOnly' to other types will be rejected if external DNS server is 'NULL'. Other options such as `createAndWait', 'notInService', 'notReady' will not be used.

The compliance statement for the SNMP entities which implement MGMIB.

The compliance statement for the SNMP entities which implement MGMIB.

The compliance statement for the SNMP entities which implement MGMIB.

The compliance statement for the SNMP entities which implement MGMIB.

This group contains objects that apply to the media gateway as a whole, such as global parameters and state.

This group contains objects that describe the Media Gateway Controllers with which the Media gateway communicates.

This group contains objects describing the media gateway's endpoints.

This group contains objects which relate lines to endpoints. These objects complement the information contained in a line MIB.

This group contains information to resolve names to IP addresses in the absence of DNS support.

This group contains objects that describe the MGCs with which the MG communicates.

This group contains information to resolve names to IP addresses both in the absence of DNS support and with DNS support.

This group contains domain names and information about how these domain names will be resolved.

This group contains objects that describe the Media Gateway Controllers with which the Media gateway communicates.

This group contains repetition objects describing the media gateway's endpoints as defined in the mgEndpointExtTable.