MPLS-FTN-MIB :: mplsFTNPerfMatchedPackets

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MPLS-FTN-MIB › mplsFTNPerfMatchedPackets

mplsFTNPerfMatchedPackets

Module: MPLS-FTN-MIB

OID (symbolic): MPLS-FTN-MIB::mplsFTNPerfMatchedPackets

OID (numeric): 1.3.6.1.2.1.10.9999.5.1.6.1.3

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Number of packets that matched the specified FTN entry if it is applied/mapped to the specified interface. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsFTNDiscontinuityTime.

What is mplsFTNPerfMatchedPackets?

Counts packets on this interface that matched the associated FTN rule, i.e. how much traffic that redirect/steering rule has actually processed; watch mplsFTNPerfDiscontinuityTime for resets that would make raw counter deltas misleading.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.9999.5.1.6.1.3
snmpwalk -v2c -c public <target> MPLS-FTN-MIB::mplsFTNPerfMatchedPackets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.9999.5.1.6.1.3.1
snmpget -v2c -c public <target> MPLS-FTN-MIB::mplsFTNPerfMatchedPackets.1

Start monitoring MPLS provider-edge and label-switching routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MPLS-FTN-MIB::mplsFTNPerfMatchedPackets OID value, configure state conditions and alerts, and monitor any MPLS provider-edge and label-switching routers from a single console.

How to Use in IPNetwork Monitor

Select an MPLS provider-edge and label-switching router 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 mplsFTNPerfMatchedPackets 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 the number of packets that matched the specified FTN entry if it is applied/mapped to the specified interface. 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.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.10transmissionCHECKPOINT-MIB-2
1.3.6.1.2.1.10.9999mplsMIBMPLS-TC-MIB
Numeric OIDNameModule
1.3.6.1.2.1.10.9999.5mplsFTNMIBMPLS-FTN-MIB
1.3.6.1.2.1.10.9999.5.1mplsFTNObjectsMPLS-FTN-MIB
1.3.6.1.2.1.10.9999.5.1.6mplsFTNPerfTableMPLS-FTN-MIB
1.3.6.1.2.1.10.9999.5.1.6.1mplsFTNPerfEntryMPLS-FTN-MIB
1.3.6.1.2.1.10.9999.5.1.6.1.3mplsFTNPerfMatchedPacketsMPLS-FTN-MIB