NOKIA-RATESHAPE-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsNOKIA-RATESHAPE-MIB

Organization: Nokia

Last Updated: 2000-01-30

Category: QoS

Description: Manages Nokia interface rate shaping policies for outbound traffic bandwidth limiting.

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 NOKIA-RATESHAPE-MIB?

NOKIA-RATESHAPE-MIB is a vendor MIB from Nokia that defines rate-shaping controls for outbound interface traffic, letting an operator apply access lists and shaping rules to bound bandwidth usage per interface and direction. It exposes configuration data through rsAccessListTable (access list definitions bound to an interface and direction) and rsRuleTable (individual shaping rules tied to an access list). Its monitoring value is in software/policy configuration status: confirming the correct rate-shaping rules and access lists are applied and active on each interface, which explains observed bandwidth-limiting behavior on a link. It is rooted under the shared Nokia enterprise OID branch (nokia, nokiaProducts, ntcCommon), indicating it is part of a broader family of Nokia network-element MIBs sharing common conventions. It is deployed on Nokia (formerly Newbridge/Alcatel-lineage) network equipment where administrators need to enforce bandwidth caps on outbound traffic per interface. Engineers can download the NOKIA-RATESHAPE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in NOKIA-RATESHAPE-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

  • Nokia network element (router/switch)

Monitoring Examples

An operator would poll rsAccessListTable (indexed by rsAccessListIfIndex and rsAccessListIndex) to see which access list and direction (rsAccessListDirection) is applied to a given interface, then cross-reference rsRuleTable (via rsRuleIfIndex and rsRuleIndex) to inspect the specific shaping rule in effect; an interface missing an expected rsAccessListName binding would explain why traffic is not being shaped as intended, useful when diagnosing unexpected bandwidth consumption. rsAccessListRowStatus can confirm whether an access list entry is active or pending.

What Can Be Monitored

  • rate-shaping access list assignment per interface
  • shaping rule configuration
  • traffic direction (inbound/outbound) shaping
  • access list row/activation status
Imported Objects

From SNMPv2-CONF

OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
enterprises

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using rsAccessListStatPktsPassed OID:

Select a Nokia network element (router/switch, outbound rate shaping) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type rsAccessListStatPktsPassed into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. Gives the count of number of packets successfully exiting this access list. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Vendor-private MIB for Nokia rate-shaping and traffic control features; manages bandwidth limiting and traffic policing configuration.

Start monitoring Nokia network element (router/switch, outbound rate shaping) 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.

Download NOKIA-RATESHAPE-MIB