NNCVS-MIB :: nncVSLOCSeconds

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NNCVS-MIB › nncVSLOCSeconds

nncVSLOCSeconds

Module: NNCVS-MIB

OID (symbolic): NNCVS-MIB::nncVSLOCSeconds

OID (numeric): 1.3.6.1.4.1.123.3.72.1.2.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This count gives the number seconds for which Loss of Continuity was declared.

What is nncVSLOCSeconds?

This counter tracks the cumulative number of seconds during which the voiceband services channel declared a Loss of Continuity (LOC) condition. A rising count signals sustained signal-continuity problems on the ATM voice channel, which an admin would investigate as a possible physical-layer or timing issue affecting call quality. For example, a channel reporting 340 LOC seconds over a day points to a persistent continuity fault worth escalating to the carrier or checking cabling for.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.123.3.72.1.2.1.1.1
snmpwalk -v2c -c public <target> NNCVS-MIB::nncVSLOCSeconds

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.123.3.72.1.2.1.1.1.1
snmpget -v2c -c public <target> NNCVS-MIB::nncVSLOCSeconds.1

Start monitoring Newbridge Networks voiceband services (VS) card in a multiservice switch with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NNCVS-MIB::nncVSLOCSeconds OID value, configure state conditions and alerts, and monitor any Newbridge Networks voiceband services (VS) card in a multiservice switch from a single console.

How to Use in IPNetwork Monitor

Select a Newbridge Networks voiceband services (VS) card in a multiservice switch 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 nncVSLOCSeconds 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. This count gives the number seconds for which Loss of Continuity was declared. 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.

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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.123newbridgeNNCGNI0001-SMI
1.3.6.1.4.1.123.3nncExtensionsNNCGNI0001-SMI
Numeric OIDNameModule
1.3.6.1.4.1.123.3.72nncVSNNCVS-MIB
1.3.6.1.4.1.123.3.72.1nncVSObjectsNNCVS-MIB
1.3.6.1.4.1.123.3.72.1.2nncVSStatisticsNNCVS-MIB
1.3.6.1.4.1.123.3.72.1.2.1nncVSStatisticsTableNNCVS-MIB
1.3.6.1.4.1.123.3.72.1.2.1.1nncVSStatisticsEntryNNCVS-MIB
1.3.6.1.4.1.123.3.72.1.2.1.1.1nncVSLOCSecondsNNCVS-MIB