vismCPUUtilization - vism CPU Utilization - CISCO-VISM-MODULE-MIB

MIBs list

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

vismCPUUtilization

vism CPU Utilization
1.3.6.1.4.1.351.110.3.25.1

This is the percentage of time CPU is in non-idle state. DEFVAL { 0 } ::= { vismSystemPerfStats 1 } SYNTAX Integer32 (0..100) MAX-ACCESS read-only STATUS current DESCRIPTION This is the percentage of memory in use by VISM. DEFVAL { 0 } ::= { vismSystemPerfStats 2 } SYNTAX INTEGER { noaction (1), clear (2) } MAX-ACCESS read-write STATUS current DESCRIPTION This variable is used to clear all the CPU and Memory Utilization statistics. 'noaction(1)': The value return on a GET operation. 'clear(2)' : Clear alarm. ::= { vismSystemPerfStats 3 } -- -- VISM Call statistics -- SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION Total number of calls made in VISM. DEFVAL { 0 } ::= { vismCallStats 1 } SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION Total number successful calls made in VISM. DEFVAL { 0 } ::= { vismCallStats 2 } SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION Total number failed calls made in VISM. DEFVAL { 0 } ::= { vismCallStats 3 } SYNTAX INTEGER { noaction (1), clear (2) } MAX-ACCESS read-write STATUS current DESCRIPTION This variable is used to clear all the VISM call statistics. 'noaction': The value return on a GET operation 'clear': Clear all alarm ::= { vismCallStats 4 } -- -- vismIpGrp group -- -- SYNTAX IpAddress MAX-ACCESS read-write STATUS current DESCRIPTION This object identifies the IP address of VISM card. Each VISM card has its own IP address. IP address for each VISM card is required to communicate with the call agent. This object is applicable if the object vismMode is in VoIP(Voice Over IP) or Switched mode. ::= { vismIpGrp 1 } SYNTAX IpAddress MAX-ACCESS read-write STATUS current DESCRIPTION SUB-NETMASK of the VISM IP interface. This object is applicable if the object vismMode is in VoIP or Switched mode. ::= { vismIpGrp 2 } SYNTAX Integer32 (0..255) MAX-ACCESS read-write STATUS current DESCRIPTION This object is used to provision the bitmask used for the TOS (Type Of Service) octet for cells carrying the control xGCP(Gateway Control Protocol) traffic. Default value 96 = 0x60 => Precedence = 3 and TOS nibble = 0 The bitmask can be only a byte value. DEFVAL { 96 } ::= { vismIpGrp 3 } SYNTAX IpAddress MAX-ACCESS read-write STATUS current DESCRIPTION The bearer IP address of VISM card. This is an optional second IP address of the VISM card. If this bearer IP address is defined, the vismIpAddress automatically becomes the control IP address. ::= { vismIpGrp 4 } SYNTAX IpAddress MAX-ACCESS read-write STATUS current DESCRIPTION Bearer SUB-NETMASK of the VISM IP interface. This optional bearer subnet mask must be provided when vismBearerIpAddress is provided. ::= { vismIpGrp 5 } -- -- vismVoIPGrp group -- -- SYNTAX Integer32 (0..255) MAX-ACCESS read-write STATUS current DESCRIPTION This object is used to provision the bitmask used for the TOS octet for cells carrying VoIP bearer RTP(Real-time Transport Protocol) traffic. Default value 160 = 0xA0 => Precedence = 5 and TOS nibble = 0 The bitmask can be only a byte value. DEFVAL { 160 } ::= { vismVoIpGrp 1 } SYNTAX Integer32 (500..15000) UNITS "milliseconds This attribute defines the RTCP(Real-time Transport Control Protocol) report interval (defined in RFC 1889). This indicates the interval at which the RTCP reports should be sent to the participating members. The RTCP reports are not sent at a fixed rate at this interval. Rather, this value is used as a base value to arrive at a random number between 0.5 and 1.5 times this value. This interval timer also serves the purpose of RTP packets receive timer. At every vismRtcpRecvMultiplier times this interval, where vismRtcpRecvMultiplier is specified in the MIB object below, a check is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. Currently, this interval timer is a card-specific value, which means the value is configurable on a per card basis and not on a per call basis. This value is applicable for VoIP adaptation only. DEFVAL { 5000 } ::= { vismVoIpGrp 2 } SYNTAX INTEGER { disable (1), enable (2) } MAX-ACCESS read-write STATUS current DESCRIPTION This object defines whether the RTP packets receive timer on the VISM needs to be enabled or not. For some VoIP applications if a connection is in send-recv mode or recv-only mode, after the bearer cut-through is done, the RTP stream should be monitored for RTP packets. If there are no packets received within a time interval specified by 5 seconds, then a Gateway initiated DLCX (Delete connection) should be sent on that connection. If this object is set to enable, the RTP stream is monitored. Otherwise, it is not monitored. This value is applicable for VoIP adaptation only. DEFVAL { disable } ::= { vismVoIpGrp 3 } -- This object is deprecated as we have a seperate per codec -- packetization period table SYNTAX INTEGER { tenms (10), twentyms (20), thirtyms (30), fourtyms (40) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION This object is used to provision the packetization period to be applied and is applicable for VoIP only. For VoAAL2 adaptations, the packetization period is derived from the profile table entry. For VoAAL1 adaptation, it is fixed at 5.875 ms.

Back to CISCO-VISM-MODULE-MIB MIB page.

IPHost Network monitor allows you to monitor vismCPUUtilization 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 vismCPUUtilization with IPHost tools

MIBs list