TN-SERV-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsTN-SERV-MIB

Organization: Nokia

Last Updated: 2016-03-15

Category: Nokia Carrier Ethernet, Service Management

Description: Manages Nokia carrier Ethernet L2VPN and VPLS service instances, SAPs, and SDP bindings.

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

TN-SERV-MIB is a Nokia (formerly Alcatel-Lucent) proprietary MIB used to manage and provision carrier Ethernet services—including Layer 2 VPN (L2VPN) and VPLS service instances, Service Access Points (SAPs), and Service Distribution Point (SDP) bindings—on the Nokia 7x50 SR system. It exposes customer and service inventory data via tnCustInfoTable (customer records with contact/phone details) and tnSvcBaseInfoTable (base service instance attributes), along with row-status and last-management-change tracking for configuration auditing. Its monitoring value lies in service-level operational/software status—confirming a service or customer record's tnCustRowStatus/tnSvcRowStatus is active, and using tnCustLastMgmtChange to detect unexpected configuration changes—rather than physical hardware sensors, making it central to carrier Ethernet service assurance. It is part of the broader Timetra/Nokia SR MIB family and depends on shared textual conventions (e.g., ALCATEL-IND1-TIMETRA-TC-MIB) as well as underlying port/interface MIBs like TIMETRA-PORT-MIB for the physical resources services ride on. It is deployed by service providers operating Nokia 7x50 SR routers to provision and monitor customer-facing L2VPN/VPLS services. The TN-SERV-MIB OID branch itself sits under the broader Nokia Timetra enterprise tree, alongside the sibling port and textual-convention modules it depends on.

IPNetwork Monitor allows you to monitor SNMP objects defined in TN-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 router platforms, entire product line (customer/service inventory status)

Monitoring Examples

An operator would poll tnCustInfoTable/tnCustInfoEntry indexed by tnCustId to verify tnCustRowStatus is active and tnCustContact/tnCustPhone details are current for a customer record. The tnSvcBaseInfoTable/tnSvcBaseInfoEntry rows, keyed by tnSvcId, would be checked to confirm a VPLS or L2VPN service instance's tnSvcRowStatus remains active and hasn't unexpectedly transitioned to notInService. Tracking tnCustLastMgmtChange helps audit when a customer's service configuration was last modified, flagging possibly unauthorized changes.

What Can Be Monitored

  • customer record status
  • service instance (L2VPN/VPLS) row status
  • SAP/SDP binding configuration
  • last management change timestamp
  • customer contact information
Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-SMI

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

From SNMPv2-TC

DisplayString
MacAddress
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From TN-TC-MIB

SdpBindId
ServObjDesc
ServiceAdminStatus
ServiceOperStatus
TNamedItem
TNamedItemOrEmpty
TmnxActionType
TmnxCustId
TmnxEnabledDisabled
TmnxEncapVal
TmnxPortID
TmnxServId
TmnxVRtrIDOrZero

From TROPIC-GLOBAL-REG

tnSRMIBModulesOBJECT-IDENTITY
tnSRNotifyPrefixOBJECT-IDENTITY
tnSRObjsOBJECT-IDENTITY

From TROPIC-SYSTEM-MIB

tnSysSwitchIdOBJECT-TYPE
OIDs

FAQ

How would I use TN-SERV-MIB to confirm a customer's L2VPN or VPLS service is actually up on a Nokia 7x50 SR router?
TN-SERV-MIB tracks service instances via tnSvcBaseInfoTable, with tnSvcRowStatus indicating whether that service entry is active, provisioned, or mid-change. A service provider troubleshooting a customer complaint about a VPLS circuit can check this row status directly, rather than digging through raw port counters, to confirm the service object itself is in the expected active state.

Can TN-SERV-MIB flag unexpected configuration changes to a customer record on a Nokia SR router?
Yes — tnCustInfoTable stores customer records (including contact/phone details) alongside tnCustLastMgmtChange, a timestamp that updates whenever that customer's configuration is touched. An operator can poll this timestamp to detect an unplanned or unauthorized change to a customer's service setup, which is useful for configuration-change auditing in a carrier Ethernet environment.

RFC description

Vendor-specific MIB for TN service management; defines service status, configuration, and operational objects for TN service infrastructure.

Start monitoring Nokia 7x50 SR-series service router platforms, entire product line (customer/service inventory 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 TN-SERV-MIB