srcpVersion - srcp Version - CISCO-WAN-SRCP-MIB

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

srcpVersion

srcp Version
1.3.6.1.4.1.351.150.11.1.1.1

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. ::= { srcpAdminObjects 1 } SYNTAX Integer32 (1025..65535) MAX-ACCESS read-write STATUS current DESCRIPTION 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). DEFVAL { 2428 } ::= { srcpAdminObjects 2 } -- ************************************************************************** -- SRCP Peer Table -- ************************************************************************** SYNTAX SEQUENCE OF SrcpPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION 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). ::= { srcpAdminObjects 3 } SYNTAX SrcpPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION 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. INDEX { srcpPeerId } ::= { srcpPeerTable 1 } SrcpPeerEntry ::= SEQUENCE { srcpPeerId Integer32, srcpPeerName DisplayString, srcpPeerPortNumber Integer32, srcpPeerHeartbeatInterval Integer32, srcpPeerTimeSinceHeartbeat Integer32, srcpPeerMaxPduSize Integer32 } SYNTAX Integer32(1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION 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. ::= { srcpPeerEntry 1 } SYNTAX DisplayString (SIZE (1..64)) MAX-ACCESS read-only STATUS current DESCRIPTION This object identifies the name of the SRCP peer. If MGMIB is supported, this is the same as the mgcName from the mgcTable. ::= { srcpPeerEntry 2 } SYNTAX Integer32 (1025..65535) MAX-ACCESS read-write STATUS current DESCRIPTION This object is used to configure the UDP port of the SRCP peer. DEFVAL { 2428 } ::= { srcpPeerEntry 3 } SYNTAX Integer32 (0..65535) UNITS "milliseconds 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. DEFVAL { 0 } ::= { srcpPeerEntry 4 } SYNTAX Integer32 (0..2147483647) UNITS "milliseconds 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. ::= { srcpPeerEntry 5 } SYNTAX Integer32 (4095..65535) UNITS "octets 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. DEFVAL { 16384 } ::= { srcpPeerEntry 6 } -- ************************************************************************** -- SRCP Peer Group Table -- ************************************************************************** SYNTAX SEQUENCE OF SrcpPeerGrpParamEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION 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. ::= { srcpAdminObjects 4 } SYNTAX SrcpPeerGrpParamEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION 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. INDEX { mgcRedundancyGrpNum } ::= {srcpPeerGrpParamTable 1 } SrcpPeerGrpParamEntry ::= SEQUENCE { srcpPeerGrpHeartbeatInterval Integer32, srcpPeerGrpTimeSinceHeartbeat Integer32, srcpPeerGrpMaxPduSize Integer32 } SYNTAX Integer32 (0..65535) UNITS "milliseconds 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). DEFVAL { 0 } ::= { srcpPeerGrpParamEntry 1 } SYNTAX Integer32 (0..2147483647) UNITS "milliseconds 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). DEFVAL { 0 } ::= { srcpPeerGrpParamEntry 2 } SYNTAX Integer32 (4095..65535) UNITS "octets 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. DEFVAL { 16384 } ::= { srcpPeerGrpParamEntry 3 } -- ********************************************************************* -- The SRCP administration Retry Group -- ********************************************************************* SYNTAX Integer32 (1..10000) UNITS "milliseconds 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. ::= { srcpAdminRetyObjects 1 } SYNTAX Integer32 (0..10) MAX-ACCESS read-write STATUS current DESCRIPTION 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. ::= { srcpAdminRetyObjects 2 } SYNTAX Integer32 (1..10000) UNITS "milliseconds 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. ::= { srcpAdminRetyObjects 3 } -- ***************************************************************** -- The SRCP Statistics table -- ***************************************************************** SYNTAX SEQUENCE OF SrcpPeerStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION 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. ::= { srcpStatsObjects 1 } SYNTAX SrcpPeerStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION 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. INDEX { srcpStatsPeerIpAddress } ::= { srcpPeerStatsTable 1 } SrcpPeerStatsEntry ::= SEQUENCE { srcpStatsPeerIpAddress IpAddress, srcpStatsPeerName DisplayString, packetsDiscardedCnts Counter32, augwCnts Counter32, augwFailCnts Counter32, aulnCnts Counter32, aulnFailCnts Counter32, ntfyCnts Counter32, ntfyFailCnts Counter32, rqntCnts Counter32, rqntFailCnts Counter32 } SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION This object specifies the IP address of the SRCP peer and serves as index to the table. ::= { srcpPeerStatsEntry 1 } SYNTAX DisplayString (SIZE (1..64)) MAX-ACCESS read-only STATUS current DESCRIPTION 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. ::= { srcpPeerStatsEntry 2 } SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION 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). ::= { srcpPeerStatsEntry 3 } SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION The total number of AUGW(Audit Gateway) commands received from the peer on this IP address.

Back to CISCO-WAN-SRCP-MIB MIB page.

IPHost Network monitor allows you to monitor srcpVersion on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco mobile switches right now.

Easy monitoring of srcpVersion with IPHost tools

MIBs list