TN-SAS-SERV-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TN-SAS-SERV-MIB

Organization: Nokia

Last Updated: 2015--0-4-

Category: Nokia Carrier Ethernet, Service Management

Description: Manages Nokia SAS L2VPN and VPLS service instance configuration and status.

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 TN-SAS-SERV-MIB?

This Nokia MIB manages service instances (L2VPN, VPLS, and related SAS services) on the 7x50 SR-series routers, extending the base service statistics with per-SAP counters. It exposes extended SAP base statistics including ingress/egress forwarded packet and octet counts, dropped-packet counts, and QoS classifier/meter usage per service access point. It supports monitoring of service-level performance and fault status by tracking forwarded versus dropped packet/octet counts, which directly reveal congestion, misconfiguration, or QoS policy issues causing traffic loss on a given service. It is part of Nokia's SROS service-management MIB family and depends on the base SAP/service objects (e.g., SAP index) defined elsewhere in that family. It is typically deployed on Nokia 7x50 SR routers providing carrier Ethernet L2VPN/VPLS services where per-service traffic accounting and QoS resource usage need close tracking. Engineers can download the TN-SAS-SERV-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TN-SAS-SERV-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 7x50 SR-series service routers

Monitoring Examples

An operator would poll the tnSapBaseStatsExtnTable (tnSapBaseStatsExtnEntry) for a service SAP to compare tnSapBaseStatsIngressForwardedPackets/Octets against tnSapBaseStatsIngressDroppedPackets/Octets, where a rising drop count indicates congestion or a QoS policer discarding traffic. tnSapBaseStatsIngressExtraTagDroppedPackets specifically flags packets dropped due to unexpected extra VLAN tags. tnSapBaseStatsQosClassifiersUsed and tnSapBaseStatsQosMetersUsed show how much of the hardware's QoS resource budget that SAP is consuming, useful when approaching platform scaling limits.

What Can Be Monitored

  • ingress/egress forwarded packets and octets
  • ingress dropped packets and octets
  • extra-tag dropped traffic
  • QoS classifier and meter resource usage
Imported Objects

From SNMPv2-SMI

Counter64
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

From TN-SAP-MIB

tnSapBaseInfoEntryOBJECT-TYPE
tnSapBaseStatsEntryOBJECT-TYPE

From TN-SERV-MIB

tnSvcBaseInfoEntryOBJECT-TYPE

From TROPIC-GLOBAL-REG

tnSASModulesOBJECT-IDENTITY
tnSASObjsOBJECT-IDENTITY

How to Use in IPNetwork Monitor

Example using tnSapBaseStatsIngressForwardedPackets OID:

Select a Nokia 7x50 SR-series service router (extended SAP traffic/QoS-classifier statistics) 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 tnSapBaseStatsIngressForwardedPackets 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. The number of sap ingress forwarded packets. 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 Counter64-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

Manages services, SAPs and configuration on Nokia 7x50 SR carrier routing systems with comprehensive statistics.

Start monitoring Nokia 7x50 SR-series service routers (extended SAP traffic/QoS-classifier statistics) 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 TN-SAS-SERV-MIB