APS-MIB-JUNI :: junidApsStatusCurrent

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › APS-MIB-JUNI › junidApsStatusCurrent

junidApsStatusCurrent

Module: APS-MIB-JUNI

OID (symbolic): APS-MIB-JUNI::junidApsStatusCurrent

OID (numeric): 1.3.6.1.4.1.4874.3.2.2.1.1.2.1.3

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: The current status of the APS group.

modeMismatch

Modes other than 1+1 unidirectional monitor protection line K2 bit 5, which indicates the architecture and K2 bits 6-8, which indicate if the mode is unidirectional or bidirectional. A conflict between the current local mode and the received K2 mode information constitutes a mode mismatch.

channelMismatch

This bit indicates a mismatch between the transmitted K1 channel and the received K2 channel has been detected.

psbf

This bit indicates a Protection Switch Byte Failure (PSBF) is in effect. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames.

feplf

Modes other than 1+1 unidirectional monitor the K1 byte for Far-End Protection-Line failures. A Far-End Protection-Line defect is declared based on receiving SF on the protection line.

extraTraffic

This bit indicates whether extra traffic is currently being accepted on the protection line.

What is junidApsStatusCurrent?

This read-only BITS field indicates current APS group status. Network engineers monitor this for mode mismatches, channel mismatches, or active switching. Multiple bits can be set simultaneously.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.3.2.2.1.1.2.1.3
snmpwalk -v2c -c public <target> APS-MIB-JUNI::junidApsStatusCurrent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.3.2.2.1.1.2.1.3.1
snmpget -v2c -c public <target> APS-MIB-JUNI::junidApsStatusCurrent.1

Start monitoring Juniper Networks SONET-interface routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the APS-MIB-JUNI::junidApsStatusCurrent OID value, configure state conditions and alerts, and monitor any Juniper Networks SONET-interface routers from a single console.

OID Breakdown

Upper-level ancestors (10 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.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.3juniperUniExperimentJuniper-UNI-SMI
1.3.6.1.4.1.4874.3.2juniExperimentJuniper-Experiment
1.3.6.1.4.1.4874.3.2.2juniSonetApsExperimentJuniper-Experiment
Numeric OIDNameModule
1.3.6.1.4.1.4874.3.2.2.1junidApsMIBAPS-MIB-JUNI
1.3.6.1.4.1.4874.3.2.2.1.1junidApsMIBObjectsAPS-MIB-JUNI
1.3.6.1.4.1.4874.3.2.2.1.1.2junidApsStatusTableAPS-MIB-JUNI
1.3.6.1.4.1.4874.3.2.2.1.1.2.1junidApsStatusEntryAPS-MIB-JUNI
1.3.6.1.4.1.4874.3.2.2.1.1.2.1.3junidApsStatusCurrentAPS-MIB-JUNI