STN-ATM-VPN-MIB :: stnAtmVpnTrunkInVpnIdIfaceInvalid

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › STN-ATM-VPN-MIB › stnAtmVpnTrunkInVpnIdIfaceInvalid

stnAtmVpnTrunkInVpnIdIfaceInvalid

Module: STN-ATM-VPN-MIB

OID (symbolic): STN-ATM-VPN-MIB::stnAtmVpnTrunkInVpnIdIfaceInvalid

OID (numeric): 1.3.6.1.4.1.3551.2.7.1.7.1.1.1.1.8

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The number packets received with a Vpn-Id that was known, but the entry in the FIB refered to an invalid or non-existant interface. This can indicate an invalid configuration.

What is stnAtmVpnTrunkInVpnIdIfaceInvalid?

Counts packets received with a known VPN ID whose forwarding table entry pointed to an invalid or non-existent interface, which can indicate a configuration error. A nonzero count here is a direct signal to check the trunk's VPN forwarding configuration for a stale or broken interface reference.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3551.2.7.1.7.1.1.1.1.8
snmpwalk -v2c -c public <target> STN-ATM-VPN-MIB::stnAtmVpnTrunkInVpnIdIfaceInvalid

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3551.2.7.1.7.1.1.1.1.8.1
snmpget -v2c -c public <target> STN-ATM-VPN-MIB::stnAtmVpnTrunkInVpnIdIfaceInvalid.1

Start monitoring Spring Tide Networks (Lucent) multiservice ATM switch (ATM VPN interface config) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the STN-ATM-VPN-MIB::stnAtmVpnTrunkInVpnIdIfaceInvalid OID value, configure state conditions and alerts, and monitor any Spring Tide Networks (Lucent) multiservice ATM switch (ATM VPN interface config) from a single console.

How to Use in IPNetwork Monitor

Select a Spring Tide Networks (Lucent) multiservice ATM switch (ATM VPN interface config) 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 stnAtmVpnTrunkInVpnIdIfaceInvalid 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 packets received with a Vpn-Id that was known, but the entry in the FIB refered to an invalid or non-existant 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (11 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.3551springtidenetSPRING-TIDE-NETWORKS-SMI
1.3.6.1.4.1.3551.2stnSystemsSPRING-TIDE-NETWORKS-SMI
1.3.6.1.4.1.3551.2.7stnRouterSTN-ROUTER-MIB
1.3.6.1.4.1.3551.2.7.1stnRouterObjectsSTN-ROUTER-MIB
1.3.6.1.4.1.3551.2.7.1.7stnRouterAtmVpnSTN-ROUTER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.3551.2.7.1.7.1stnAtmVpnSTN-ATM-VPN-MIB
1.3.6.1.4.1.3551.2.7.1.7.1.1stnAtmVpnTrunkObjectsSTN-ATM-VPN-MIB
1.3.6.1.4.1.3551.2.7.1.7.1.1.1stnAtmVpnTrunkTableSTN-ATM-VPN-MIB
1.3.6.1.4.1.3551.2.7.1.7.1.1.1.1stnAtmVpnTrunkEntrySTN-ATM-VPN-MIB
1.3.6.1.4.1.3551.2.7.1.7.1.1.1.1.8stnAtmVpnTrunkInVpnIdIfaceInvalidSTN-ATM-VPN-MIB