All MIBs › ASKEY-QOS-MIB
Organization: ASKEY Inc.
Last Updated: 2006-05-30
Category: DSL and Broadband, Quality of Service, Vendor: Askey
Description: Manages quality of service scheduling, queuing, and traffic marking on Askey DSLAM equipment.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is ASKEY-QOS-MIB?
This is a vendor-specific MIB from Askey defining quality-of-service scheduling, queuing, and traffic-marking configuration on Askey DSLAM/broadband access equipment. It exposes per-line QoS policy tables, DiffServ marking/mapping configuration, and traffic policing rules (rate limits and actions). It is primarily a configuration MIB for traffic management rather than hardware fault monitoring, but it lets an administrator confirm the software-configured QoS policy in effect on a line matches intent, which is important for diagnosing performance complaints. It explicitly depends on and extends the standard DiffServ MIB framework, referencing diffServAdminStatus, diffServMappingTable, and DSCP marking concepts. It is deployed on Askey DSL/broadband access multiplexers (DSLAMs) delivering managed, QoS-differentiated broadband service to subscribers. Engineers can download the ASKEY-QOS-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in ASKEY-QOS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Askey DSLAM/broadband access equipment
Monitoring Examples
An administrator would poll askeyQoSLineTable/askeyQoSLineEntry to confirm askeyQoSLineTrafficPolicing is enabled on a subscriber line, then check trafficPolicingTable/trafficPolicingEntry for the configured trafficPolicingCIR (committed information rate) and trafficPolicingAction to understand how excess traffic is handled. Cross-checking diffServMappingTable/diffServMappingEntry and diffServDSCP values confirms that inbound traffic is being classified and marked as expected, and a mismatch between the configured CIR and observed throughput on that line would point to a misapplied policing policy rather than a physical line fault.
What Can Be Monitored
- per-line QoS policy status
- DiffServ DSCP marking/mapping
- traffic policing CIR
- policing action on excess traffic
Imported Objects
From ASKEY-DSLAM-MIB
| ipDslam | OBJECT-IDENTITY |
From ASKEY-SYSTEM-MIB
| askeyCosQueueMapping8021p | OBJECT-TYPE |
From IF-MIB
| ifIndex | OBJECT-TYPE |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| RowStatus |
OIDs
RFC description
Provides QoS configuration for line ports and DiffServ traffic policing in ASKEY DSLam equipment.
Start monitoring Askey DSLAM broadband access equipment (legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.