TIMETRA-SAS-SERV-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTIMETRA-SAS-SERV-MIB

Organization: Alcatel

Last Updated: 2009-07-07

Description: TIMETRA-SAS-SERV-MIB module

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

This is an Alcatel-Lucent (Nokia) proprietary MIB, part of the TIMETRA family, for managing and provisioning services on the Alcatel 7x50 SR (Service Router) system, with this particular module (SAS - Service Aggregation Switch) extending service access point (SAP) statistics. It exposes extended per-SAP statistics such as QoS classifier and meter usage counts, and ingress/egress forwarded and dropped packet/octet counters, including drops due to extra VLAN tags. Its monitoring value is centered on service-level performance and fault detection: tracking ingress/egress forwarded traffic versus dropped traffic (including tag-related drops) on a given SAP reveals whether a customer service is experiencing packet loss, QoS policy misconfiguration, or VLAN tagging mismatches. As a TIMETRA-family module it depends on and extends the base SAP statistics model shared across other Alcatel-Lucent 7x50 SR service MIBs. It is deployed on Alcatel-Lucent (Nokia) 7x50 Service Router systems delivering carrier Ethernet/aggregation services. Engineers can download the TIMETRA-SAS-SERV-MIB file directly to load it into their MIB browser.

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

  • Alcatel-Lucent (Nokia) 7x50 Service Router

Monitoring Examples

An administrator would poll sapBaseStatsExtnTable/sapBaseStatsExtnEntry to compare sapBaseStatsIngressForwardedPackets/Octets against sapBaseStatsIngressDroppedPackets/Octets for a given SAP, and check sapBaseStatsIngressExtraTagDroppedPackets to see if drops are specifically caused by unexpected VLAN tagging. A high ratio of dropped-to-forwarded packets combined with a high sapBaseStatsQosMetersUsed count would suggest the SAP's QoS policy is over-restrictive for the offered traffic load, prompting a review of its classifier/meter configuration.

What Can Be Monitored

  • ingress/egress forwarded packets and octets per SAP
  • ingress/egress dropped packets and octets per SAP
  • extra-tag dropped packets/octets
  • QoS classifiers and meters in use per SAP
Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Gauge32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
MacAddress
RowPointer
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From TIMETRA-SAP-MIB

sapBaseInfoEntryOBJECT-TYPE
sapBaseStatsEntryOBJECT-TYPE
sapEgrQosQueueStatsEntryOBJECT-TYPE
sapEncapValueOBJECT-TYPE
sapIngQosQueueInfoEntryOBJECT-TYPE
sapIngQosQueueStatsEntryOBJECT-TYPE
sapPortIdOBJECT-TYPE

From TIMETRA-SAS-GLOBAL-MIB

timetraSASConfsOBJECT-IDENTITY
timetraSASModulesOBJECT-IDENTITY
timetraSASNotifyPrefixOBJECT-IDENTITY
timetraSASObjsOBJECT-IDENTITY

From TIMETRA-SAS-QOS-MIB

TIngressBurstSize
TIngressCIRRate
TIngressPIRRate
TMeterMode
TMeterRateMode

From TIMETRA-SERV-MIB

iesIfIndexOBJECT-TYPE
svcBaseInfoEntryOBJECT-TYPE
svcIdOBJECT-TYPE

From TIMETRA-TC-MIB

TAdaptationRule
TLevelOrDefault
TNamedItem
TSapIngressMeterId
TWeight
TmnxServId

How to Use in IPNetwork Monitor

Example using sapBaseStatsIngressForwardedPackets OID:

Select an Alcatel-Lucent (Nokia) 7x50 Service Router (extended SAP ingress/egress traffic/drop-counter status) 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 sapBaseStatsIngressForwardedPackets 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

Vendor-private MIB for Alcatel-Lucent/Nokia 7210 SAS service management and provisioning.

Start monitoring Alcatel-Lucent (Nokia) 7x50 Service Router (extended SAP ingress/egress traffic/drop-counter 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.

Download TIMETRA-SAS-SERV-MIB