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

The MIB module for managing SRCP(Simple Resource Coordination Protocol) implementations. SRCP is a resource coordination protocol used between a MGC(Media Gateway Controller) and a MG(Media Gateway). SRCP MIB is applicable to both controllers (SRCP clients) and gateways (SRCP servers). MGMIB: This is the short name used for CISCO-WAN-MG-MIB in this MIB.

The name of the SRCP protocol version for exmaple SRCP 1.0.2. If MGMIB is supported, this name corresponds to mgProtocolName (defined in CISCO-WAN-MG-MIB MIB) in an entry to mgSupportedProtocolTable.

This object is used to configure the UDP port used for SRCP on the system (local UDP port). It is configurable only if the system is in a locked or disabled state (i.e If MGMIB Is supported, mgAdministrativeState(defined in CISCO-WAN-MG-MIB MIB) should be 'locked' before the UDP port can be configured).

This is a table which is used to provision peer-specific SRCP configuration and administration information. Each table entry corresponds to an SRCP peer as identified by its domain name(srcpPeerName).

Represents an individual table entry in srcpPeerTable. Each row corresponds to an SRCP peer and is identified by its domain name (srcpPeerName). Entries in this table are implicitly created by the agent. If the agent supports MGMIB, this occurs as follows: An entry shall be created when an entry is created in the mgcRedundancyGrpProtocolTable(defined in CISCO-WAN-MGC-REDUN-MIB MIB) and when mgProtocolNumber (defined in CISCO-WAN-MG-MIB MIB) refers to SRCP as supported protocol. An entry will be made for all MGC(Media Gateway Controller) in that MGC Redundancy Group. Accordingly, an entry shall be deleted if the corresponding entry in the mgcRedundancyGrpProtocolTable is deleted. If the agent does not support MGMIB, entry creation might occur when the first SRCP communication with an IP address/domain name occurs. if MGC Redundacy feature is supported the following objects: srcpPeerHeartbeatInterval, srcpPeerTimeSinceHeartbeat rcpPeerMaxPduSize are not meaningful here. These objects are defined per MGC Redundancy Group rather than per MGC.

This object identifies the SRCP peer and serves as index to this table. If MGMIB is supported, this is the same as the mgcNumber(defined in CISCO-WAN-MG-MIB MIB) from the mgcTable.

This object identifies the name of the SRCP peer. If MGMIB is supported, this is the same as the mgcName from the mgcTable.

This object is used to configure the UDP port of the SRCP peer.

This object is used to configure the length of the heartbeat interval, in milliseconds. The heartbeat interval indicate when the GW(Gateway) is expected to receive a heartbeat from a specific peer or MGC group. If value is 0, heartbeat for this peer is not monitored. The heartbeat interval less than 100 is not allowed (except 0). If MGC Redundancy is supported, this object is not effective. Instead, the user should use srcpPeerGrpHeartbeatInterval.

The time since the last heartbeat was received, in milliseconds. This represents the difference between the current time and the last time an SRCP command was received. A value of 0 shall be returned if the heartbeat is not monitored. Even if the heartbeat is monitored, a value of 0 shall be returned if any of the following is true: i) The system is locked or disabled (as indicated by mgAdministrativeState). ii) The srcpPeer is unassociated as indicated by mgcAssociationState(defined in CISCO-WAN-MG-MIB MIB). If MGC Redundancy is supported, this object is not effective. Instead, the user should use srcpPeerGrpTimeSinceHeartbeat.

This object is used to configure the maximum UDP PDU(Protocol Data Unit) size, in octets, that may be used for SRCP communications with the peer. This value may not be configurable for all agents. If MGC Redundancy is supported, this object is not effective. Instead, the user should use srcpPeerGrpMaxPduSize.

This table is used to provision SRCP parameters for an MGC Redundancy group. MGCs can be configured as part of MGC Redundancy groups. This feature allows for redundant call agents. Each table entry corresponds to an SRCP peer entry that is identified by the MGC Redundancy group number.

Represents an individual table entry in the srcpPeerGrpParamTable. Each row corresponds to an MGC Redundancy Group and is identified by the MGC Redundancy Group Number. Entries are implicitly created when the SRCP protocol is added for an MGC Redundancy Group. The entry will be removed if the SRCP protocol is removed for an MGC Redundancy Group.

This object is used to configure the length of the heartbeat interval, in milliseconds. If 0, heartbeat for this peer Group is not monitored. The heartbeat interval less than 100 is not allowed (except 0).

The time since the last heartbeat was received, in milliseconds. This represents the difference between the current time and the last time an SRCP command was received. A value of 0 shall be returned if the heartbeat is not monitored. Even if the heartbeat is monitored, a value of 0 shall be returned if any of the following is true: i) The system is locked or disabled (as indicated by mgAdministrativeState). ii) The stateChangeNtfy flag is disabled for the srcpPeer Group (as indicated by mgcRedundancyGrpStateChangeNtfy of CISCO-WAN-MGC-REDUN-MIB).

This object is used to configure the maximum UDP PDU size, in octets, that may be used for SRCP communications with the peer. This value may not be configurable for all agents.

This table contains SRCP statistics information since reset. SRCP statistics are kept in this table, with each table entry containing the statistics of SRCP messages that communicated with a peer at a specific IP address of the peer. It differs from the SRCP peer table which maintains information on a per call agent basis as identified by their domain names.

The row of the srcpPeerStatsTable contains information about SRCP message statistics per IP address of the MGC. An entry is implicitly created and deleted by the agent. There can be two cases: 1. Case of Internal address resolution : In this case IP addresses of all SRCP peers are resolved internally. If the agent supports the MGMIB, the following referential integrity rules apply: When an entry is added to mgcResolutionTable defined in CISCO-WAN-MG-MIB with a specific IP address, an entry is created in this srcpPeerStatsTable for that IP address. When an entry is deleted from mgcResolutionTable, the row with the corresponding IP address in this table will be deleted. 2. Case of External address resolution : If there is at least one Call agent whose IP address is resolved externally, an entry is created whenever SRCP communication occurs with a new IP address. Table entries are never deleted, but must be nonpersistent in agent implementations, i.e. must be purged in case of a system shutdown/restart.

This object specifies the IP address of the SRCP peer and serves as index to the table.

Denotes the name of the SRCP peer. This is the same as the mgcName from the mgcTable. It is provided here as a read-only parameter as a convinience feature.

The number of packets that were received and discarded. The packets may get discarded because of indecipherable PDUs like bad protocol version, bad command verb etc, or because of unknown transaction IDs (in case of SRCP clients).

The total number of AUGW(Audit Gateway) commands received from the peer on this IP address.

The total number of AULN(Audit Line) commands received from or sent to the peer on this IP address.

The total number of RQNT(Notification Request) commands received from or sent to the peer on this IP address.

The total number of NTFY(Notify) commands received from or sent to the peer on this IP address.

For MG : The total number of AUGW commands received that were responded to with a failure return code. For MGC : The total number of AUGW commands sent which were timed out without a response or for which a response with failure return code was received.

Media gateway : The total number of AULN commands received that were responded to with a failure return code. Media gateway controller : The total number of AULN commands sent which were timed out without a response or For which a response with failure return code was received.

Media gateway : The total number of RQNT commands received that were responded to with a failure return code. Media gateway controller : The total number of RQNT commands sent which were timed out without a response or for which a response with failure return code was received.

Media gateway : The total number of NTFY commands sent which were timed out without a response or for which a response with failure return code was received. Media gateway controller: The total number of NTFY commands received that were responded to with a failure return code.

This object specifies the minimum timeout value. This value along with srcpRequestMaxTimeout and srcpRequestRetries is used to determine the exponential retry interval for retransmitting unacknowledged SRCP messages. It is the responsibility of the requesting entity to provide suitable timeouts for all outstanding commands, and to retry commands when timeouts exceeded. The default value of this object is 500 milliseconds. When the value of this object changes srcpAdminObjects group changed trap will be sent as specify by vismConfigChangeTypeBitMap in CISCO-VISM-MODULE-MIB.

This object specifies the number of retries for a SRCP request that exceeds timeout. It is the responsibility of the requesting entity to provide suitable timeouts for all outstanding commands, and to retry when times out. The default value of this object is 3. When the value of this object changes srcpAdminObjects group changed trap will be sent as specify by vismConfigChangeTypeBitMap in CISCO-VISM-MODULE-MIB.

This object specifies the maximum timeout value. This timer value is used along with srcpRequestTimeOut and srcpRequestRetries to determine the exponential retry interval for retransmitting unacknowledged SRCP messages. The value of this timer has to be greater than or equal to srcpRequestTimeOut. The default value of this object is 500 milliseconds. When the value of this object changes srcpAdminObjects group changed trap will be sent as specify by vismConfigChangeTypeBitMap in CISCO-VISM-MODULE-MIB.

The compliance statement for the SNMPv2 entities which implement SRCP MIB.

The compliance statement for the SNMPv2 entities which implement SRCP MIB.

The compliance statement for the SNMPv2 entities which implement SRCP MIB.

This group contains objects related to configuration of SRCP. Min Access of read only is permissible for system providing only a fixed SRCP port.

This group contains the statistics per SRCP peer.

This group contains objects related to configuration of SRCP. Min Access of read only is permissible for system providing only a fixed SRCP port.

This group contains the statistics per SRCP peer.

This group contains objects related to configuration of SRCP. Min Access of read only is permissible for system providing only a fixed SRCP port.