TN-LAG-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TN-LAG-MIB

Organization: Nokia

Last Updated: 2014-11-25

Category: Link Aggregation, Nokia Carrier Ethernet

Description: Manages Nokia carrier Ethernet link aggregation group membership and LACP configuration.

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

TN-LAG-MIB is a Nokia (formerly Alcatel-Lucent) proprietary MIB for the 7x50 family of carrier Ethernet/service routers, implementing management of IEEE 802.3ad Link Aggregation Groups (LAG/LACP). It exposes configuration and operational data per LAG such as LACP enable state and mode, admin key auto-generation, port count thresholds and threshold-crossing actions, dynamic cost adjustment, and a descriptive name for each aggregate. For monitoring, it lets an operator confirm a LAG's administrative and row status, whether LACP negotiation is enabled and in active/passive mode, and whether the number of active member ports has fallen below the configured tnLagPortThreshold — a condition that typically triggers the configured tnLagPortThresholdAction and signals reduced link redundancy/bandwidth rather than a single-interface fault. It is explicitly built on top of the IEEE 802.3ad Link Aggregation standard, layering Nokia-specific provisioning objects over that standard's LACP concepts. It is deployed on Nokia 7x50 (7750/7450/7250) service router platforms in carrier and large-enterprise WAN/Ethernet aggregation networks. Engineers can download the TN-LAG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TN-LAG-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 1830 PSS (Photonic Service Switch) optical transport platform

Monitoring Examples

An operator would poll tnLagConfigTable/tnLagConfigEntry, reading tnLagPortThreshold against the actual count of LACP-bundled member ports to detect when a LAG has dropped below its minimum bandwidth requirement. tnLagEnableLACP and tnLagLACPMode confirm whether a given LAG (indexed by tnLagIndex) is running active or passive LACP negotiation. If tnLagRowStatus shows the aggregate is active but fewer physical ports are up than tnLagPortThreshold requires, the configured tnLagPortThresholdAction (e.g., bringing the LAG down) would be expected to fire.

What Can Be Monitored

  • LAG operational/row status
  • LACP enable state and mode
  • active member port count vs. threshold
  • port threshold action
  • LAG description/dynamic costing
Imported Objects

From IEEE8023-LAG-MIB

dot3adAggPortEntryOBJECT-TYPE

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From TN-PORT-MIB

tnPortLagId
tnPortPortID

From TN-TC-MIB

TItemLongDescription
TNamedItemOrEmpty

From TROPIC-GLOBAL-REG

tnSRMIBModulesOBJECT-IDENTITY
tnSRNotifyPrefixOBJECT-IDENTITY
tnSRObjsOBJECT-IDENTITY

From TROPIC-SYSTEM-MIB

tnSysSwitchIdOBJECT-TYPE

How to Use in IPNetwork Monitor

Example using tnLagPortThresholdFalling OID:

Select a Nokia 7750/7450/7250 service router (802.3ad LAG admin/threshold 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 tnLagPortThresholdFalling 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. It reports counts the number of linkDown or dynamicCost events for the Link Aggregation Group caused by the number of physical ports being less than or equal to tnLagPortThreshold value. 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

Manages IEEE 802.3ad Link Aggregation Groups (LAG) on Nokia 7x50 service platforms for link bundling.

Start monitoring Nokia 7750/7450/7250 service router (802.3ad LAG admin/threshold 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-LAG-MIB