CISCO-VISM-CONN-MIB :: vismChanUserMaxPCRBandwidth

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-VISM-CONN-MIBvismChanUserMaxPCRBandwidth

vismChanUserMaxPCRBandwidth

Module: CISCO-VISM-CONN-MIB

OID (symbolic): CISCO-VISM-CONN-MIB::vismChanUserMaxPCRBandwidth

OID (numeric): 1.3.6.1.4.1.351.110.5.5.3.1.1.1.51

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-write

Description: This indicates a user configured bandwidth (Peak Cell Rate) in cells per second from the local end i.e in the ingress direction of the PVC. For a VoIP bearer PVC, the max value is 75600 cps. For a VoIP control PVC, the max value is 24400 cps. For AAL2 PVCs, the PCR to be specified has to be computed based on: a) The no. of channels multiplexed on an AAL2 PVC b) The Codec (Compression Algorithm) used. c) The VAD factor d) Partial fill factor.

For a AAL2 bearer PVC, the max value is 60,000 cps on E1 card and 50,000 cps on T1 card. For a signaling PVC, the max value is 400 cps.

This parameter can not be changed when there are calls active on the PVC.

For a VOIP bearer PVC the max allowed value is 80000. For a VOIP control PVC the max allowed value is 20000. increased as we will allow 248 endpoints.

For Aal2 the values remain the same 50000/60000. For vbr connections the minimum value of PCR is 15.

What is vismChanUserMaxPCRBandwidth?

This read-write Unsigned32 object (1-100000), in cells-per-second, indicates a user-configured maximum bandwidth (Peak Cell Rate) from the local end in the ingress direction of the PVC, with max values of 75600 cps for a VoIP bearer PVC and 24400 cps for a VoIP control PVC, and AAL2 PVC values needing to be computed from channel count, codec, and VAD factor. This object gives the user an explicit ceiling on bandwidth distinct from the automatically-derived vismConnPCR, useful when the admin wants to cap bandwidth below what the connection could technically use. An engineer wanting to cap a VoIP bearer PVC's bandwidth below the hardware maximum of 75600 cps would set this object to their desired ceiling rather than relying on the default PCR calculation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.51
snmpwalk -v2c -c public <target> CISCO-VISM-CONN-MIB::vismChanUserMaxPCRBandwidth

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.51.1
snmpget -v2c -c public <target> CISCO-VISM-CONN-MIB::vismChanUserMaxPCRBandwidth.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.51.1 i <value>

Start monitoring Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-VISM-CONN-MIB::vismChanUserMaxPCRBandwidth OID value, configure state conditions and alerts, and monitor any Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) from a single console.

OID Breakdown

Upper-level ancestors (12 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.110basisBASIS-MIB
1.3.6.1.4.1.351.110.5basisServicesBASIS-MIB
1.3.6.1.4.1.351.110.5.5voiceBASIS-MIB
1.3.6.1.4.1.351.110.5.5.3vismChanGrpBASIS-MIB
1.3.6.1.4.1.351.110.5.5.3.1vismChanCnfGrpBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.5.3.1.1vismChanCnfGrpTableCISCO-VISM-CONN-MIB
1.3.6.1.4.1.351.110.5.5.3.1.1.1vismChanCnfGrpEntryCISCO-VISM-CONN-MIB
1.3.6.1.4.1.351.110.5.5.3.1.1.1.51vismChanUserMaxPCRBandwidthCISCO-VISM-CONN-MIB