JUNIPER-ANALYZER-MIB :: jnxAnalyzerOutputType

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › JUNIPER-ANALYZER-MIB › jnxAnalyzerOutputType

jnxAnalyzerOutputType

Module: JUNIPER-ANALYZER-MIB

OID (symbolic): JUNIPER-ANALYZER-MIB::jnxAnalyzerOutputType

OID (numeric): 1.3.6.1.4.1.2636.3.40.1.1.1.1.3.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The destination port can be on the same switch or on a different switch(Remote Analyzer).

Value 1 specifies that the destination interface is on the same switch and it receives a copy of traffic from the source ports. The port does not transmit any traffic except that required for the analyzer session.

The traffic for each Remote Analyzer session is carried over a user-specified Remote Analyzer VLAN that is dedicated for that Remote Analyzer session in all participating switches. A special vlan is confgiured exclusively for remote mirroring by marking it as analyzer vlan. Intermediate switches will have a few ports (minimum of 2 ports )as members of the analyzer vlan. These are the trunk ports which act as the link between the switches. The analyzer ports on the destination switch are also added to the Analyzer VLAN.

Value 2 specifies that the traffic from all the source ports is copied into the Remote Analyzer vlan specified by the vlan name.

In the source switch the analyzer session destination is given as the analyzer vlan. In the intermediate switches the analyzer sessions have the source and the destination as the analyzer vlan. The packet will reach the destination ports as it will be a part of the analyzer vlan.

What is jnxAnalyzerOutputType?

This read-only INTEGER object reports whether an analyzer session's destination is a local interface(1) on the same switch or a remote Analyzer VLAN(2) used to carry mirrored traffic to a switch elsewhere in the network. It tells an admin how mirrored traffic reaches its destination: directly out a dedicated monitor port, or tunneled across intermediate switches over a special analyzer VLAN carried on trunk ports. For example, a value of vlanname(2) indicates the session is a Remote Analyzer setup where mirrored packets travel across the network tagged with the configured analyzer VLAN before reaching the monitoring station.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.40.1.1.1.1.3.1.2
snmpwalk -v2c -c public <target> JUNIPER-ANALYZER-MIB::jnxAnalyzerOutputType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.40.1.1.1.1.3.1.2.1
snmpget -v2c -c public <target> JUNIPER-ANALYZER-MIB::jnxAnalyzerOutputType.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> jnxAnalyzerOutputType.1

Start monitoring Juniper Networks EX/QFX switch (Analyzer port-mirroring feature) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-ANALYZER-MIB::jnxAnalyzerOutputType OID value, configure state conditions and alerts, and monitor any Juniper Networks EX/QFX switch (Analyzer port-mirroring feature) from a single console.

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.2636juniperMIBJUNIPER-SMI
1.3.6.1.4.1.2636.3jnxMibsJUNIPER-SMI
1.3.6.1.4.1.2636.3.40jnxExMibRootJUNIPER-SMI
1.3.6.1.4.1.2636.3.40.1jnxExSwitchingJUNIPER-EX-SMI
1.3.6.1.4.1.2636.3.40.1.1jnxExAnalyzerJUNIPER-EX-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.40.1.1.1jnxAnalyzerMIBJUNIPER-ANALYZER-MIB
1.3.6.1.4.1.2636.3.40.1.1.1.1jnxAnalyzerMIBObjectsJUNIPER-ANALYZER-MIB
1.3.6.1.4.1.2636.3.40.1.1.1.1.3jnxAnalyzerOutputTableJUNIPER-ANALYZER-MIB
1.3.6.1.4.1.2636.3.40.1.1.1.1.3.1jnxAnalyzerOutputEntryJUNIPER-ANALYZER-MIB
1.3.6.1.4.1.2636.3.40.1.1.1.1.3.1.2jnxAnalyzerOutputTypeJUNIPER-ANALYZER-MIB