| mgName |
.1.3.6.1.4.1.351.150.10.1.1.1 |
|
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.
|
| mgAdministrativeState |
.1.3.6.1.4.1.351.150.10.1.1.2 |
|
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'.
|
| mgAdministrativeStateControl |
.1.3.6.1.4.1.351.150.10.1.1.3 |
|
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.
|
| mgShutdownGraceTime |
.1.3.6.1.4.1.351.150.10.1.1.4 |
|
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.
|
| mgSupportedProtocolEntry |
.1.3.6.1.4.1.351.150.10.1.1.7.1 |
|
Represents an individual table entry in
mgSupportedProtocolTable.
|
| maxConcurrentMgcs |
.1.3.6.1.4.1.351.150.10.1.2.3 |
|
This object identifies the maximum number of MGCs
the MG can have.
|
| mgcEntry |
.1.3.6.1.4.1.351.150.10.1.2.1.1 |
|
Represents an individual table entry in
mgcTable.
|
| mgcProtocolEntry |
.1.3.6.1.4.1.351.150.10.1.2.2.1 |
|
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.
|
| mgEndpointCreationPolicy |
.1.3.6.1.4.1.351.150.10.1.3.2 |
|
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.
|
| mgEndpointEntry |
.1.3.6.1.4.1.351.150.10.1.3.1.1 |
|
Represents an individual table entry in
mgEndpointTable.
|
| lineAssignmentEntry |
.1.3.6.1.4.1.351.150.10.1.4.1.1 |
|
Represents an individual table entry in
lineAssignmentTable.
|
| mgcResolutionEntry |
.1.3.6.1.4.1.351.150.10.1.5.1.1 |
|
Represents an individual table entry in
mgcResolutionTable.
|
| mgDomainNameEntry |
.1.3.6.1.4.1.351.150.10.1.6.1.1 |
|
Represents an individual table entry in mgDomainNameTable.
|
| mgProtocolNumber |
.1.3.6.1.4.1.351.150.10.1.1.7.1.1 |
|
Serves as index to this table.
|
| mgProtocolName |
.1.3.6.1.4.1.351.150.10.1.1.7.1.2 |
|
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 signalling backhaul protocol or
it can be resource co-ordination protocol like SRCP.
|
| mgcNumber |
.1.3.6.1.4.1.351.150.10.1.2.1.1.1 |
|
Serves as index to this table.
|
| mgcName |
.1.3.6.1.4.1.351.150.10.1.2.1.1.2 |
|
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.
|
| mgcDnsResolution |
.1.3.6.1.4.1.351.150.10.1.2.1.1.3 |
|
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.
|
| mgcAssociationState |
.1.3.6.1.4.1.351.150.10.1.2.1.1.4 |
|
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.
|
| mgcAssociationStateControl |
.1.3.6.1.4.1.351.150.10.1.2.1.1.5 |
|
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 unregistration.
'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.
|
| mgcUnassociationPolicy |
.1.3.6.1.4.1.351.150.10.1.2.1.1.6 |
|
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.
|
| mgcCommLossUnassociationTimeout |
.1.3.6.1.4.1.351.150.10.1.2.1.1.7 |
|
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.
|
| mgcRowStatus |
.1.3.6.1.4.1.351.150.10.1.2.1.1.8 |
|
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.
|
| mgcProtocolRowStatus |
.1.3.6.1.4.1.351.150.10.1.2.2.1.1 |
|
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.
|
| mgEndpointNumber |
.1.3.6.1.4.1.351.150.10.1.3.1.1.1 |
|
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.
|
| mgEndpointLineNumber |
.1.3.6.1.4.1.351.150.10.1.3.1.1.2 |
|
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.
|
| mgEndpointName |
.1.3.6.1.4.1.351.150.10.1.3.1.1.3 |
|
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.
|
| mgEndpointSpeed |
.1.3.6.1.4.1.351.150.10.1.3.1.1.4 |
|
Indicates the endpoint's bandwidth, in Kbps. Typically,
this will be 64 times the number of channels terminated
by the endpoint.
|
| mgEndpointState |
.1.3.6.1.4.1.351.150.10.1.3.1.1.5 |
|
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.
|
| mgEndpointChannelMap |
.1.3.6.1.4.1.351.150.10.1.3.1.1.6 |
|
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.
|
| mgEndpointRowStatus |
.1.3.6.1.4.1.351.150.10.1.3.1.1.7 |
|
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.
|
| lineNumber |
.1.3.6.1.4.1.351.150.10.1.4.1.1.1 |
|
Identifies the DS1 line. Generally, this will
correspond to the ifIndex of the physical interface
terminating the line.
|
| channelAssignment |
.1.3.6.1.4.1.351.150.10.1.4.1.1.2 |
|
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.
|
| lineName |
.1.3.6.1.4.1.351.150.10.1.4.1.1.3 |
|
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.
|
| mgcResolutionIndex |
.1.3.6.1.4.1.351.150.10.1.5.1.1.1 |
|
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.
|
| mgcResolutionName |
.1.3.6.1.4.1.351.150.10.1.5.1.1.2 |
|
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.
|
| mgcResolutionIpAddress |
.1.3.6.1.4.1.351.150.10.1.5.1.1.3 |
|
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.
|
| mgcResolutionCommState |
.1.3.6.1.4.1.351.150.10.1.5.1.1.4 |
|
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.
|
| mgcResolutionPreference |
.1.3.6.1.4.1.351.150.10.1.5.1.1.5 |
|
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.
|
| mgcResolutionRowStatus |
.1.3.6.1.4.1.351.150.10.1.5.1.1.6 |
|
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.
|
| mgcDnsResolutionFlag |
.1.3.6.1.4.1.351.150.10.1.5.1.1.7 |
|
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'.
|
| mgDomainNameIndex |
.1.3.6.1.4.1.351.150.10.1.6.1.1.1 |
|
This object serves as index to this table.
|
| mgDomainName |
.1.3.6.1.4.1.351.150.10.1.6.1.1.2 |
|
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.
|
| mgDnsResolutionType |
.1.3.6.1.4.1.351.150.10.1.6.1.1.3 |
|
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.
|
| mgDomainNameRowStatus |
.1.3.6.1.4.1.351.150.10.1.6.1.1.4 |
|
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.
|
