All MIBs › CISCO-WAN-AXIPOP-MIB › portEqueueServiceRatio
portEqueueServiceRatio
Module: CISCO-WAN-AXIPOP-MIB
OID (symbolic): CISCO-WAN-AXIPOP-MIB::portEqueueServiceRatio
OID (numeric): 1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.7
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Number of times queue 1 is serviced for every time queue 2 is serviced. The value 0 is supported only by FRSM-VHS.
FRSM-VHS supports two different egress queue servicing algorithms depending on the Egress Qos Feature.
if EgrQosFeature is ENABLED, Weighted Fair queueing algorithm will be used to select one queue out of 4 data queues and this object will be set to a default value of 0 in this case and this value cannot be modified by user.
In case of EgrQosFeature being DISABLED, this object will be set to a default value of 1 and can be configured to user desired value. This value will be used to decide number of times High priority queue has to be serviced for every time low priority queue is serviced. For FRSM12 card: There is only one scheme of egress scheduling of COS queues within ports, which uses only two COS queues for user data. The scheduling scheme uses a pre-defined ratio to schedule these COS queues on a given port. This object will be used to decide number of times High priority queue has to be serviced for every time low priority queue is serviced.
What is portEqueueServiceRatio?
This read-write integer (0..15) sets how many times egress queue 1 is serviced for every one time queue 2 is serviced on the port, with the value 0 supported only on FRSM-VHS, where it instead signals that the FRSM-VHS-specific Weighted Fair Queueing algorithm is being used across four data queues in place of a fixed servicing ratio. An administrator tunes this ratio to bias egress scheduling toward higher-priority queue 1 traffic over queue 2 traffic. For example, on an FRSM-VHS port with the Egress Qos Feature enabled, portEqueueServiceRatio defaults to and stays at 0 because WFQ, rather than a fixed servicing ratio, is actively managing the four egress queues.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.7 snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::portEqueueServiceRatio
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.7.1 snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::portEqueueServiceRatio.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.7.1 i <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> portEqueueServiceRatio.1
Start monitoring Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-AXIPOP-MIB::portEqueueServiceRatio OID value, configure state conditions and alerts, and monitor any Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) from a single console.
OID Breakdown
Upper-level ancestors (12 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.351 | stratacom | CISCOWAN-SMI |
| 1.3.6.1.4.1.351.110 | basis | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5 | basisServices | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.1 | frameRelay | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.1.1 | frPort | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.1.1.1 | frPortCnf | BASIS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.351.110.5.1.1.1.1 | frPortCnfPortGrp | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.1.1.1.1.1 | frPortCnfPortGrpTable | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.1.1.1.1.1.1 | frPortCnfPortGrpEntry | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.7 | portEqueueServiceRatio | CISCO-WAN-AXIPOP-MIB |