JUNIPER-ANALYZER-MIB: View SNMP OID List / Download MIB

VENDOR: JUNIPER


 Home MIB: JUNIPER-ANALYZER-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 jnxAnalyzerMIB 1.3.6.1.4.1.2636.3.40.1.1.1
This is Juniper Networks' implementation of enterprise specific MIB for Analyzer and Remote Analyzer. Port mirroring is widely used in enterprise switches to send a copy of all or sampled packets seen on a port to an anlyzer on the same or different switch.
     jnxAnalyzerMIBObjects 1.3.6.1.4.1.2636.3.40.1.1.1.1
         jnxAnalyzerTable 1.3.6.1.4.1.2636.3.40.1.1.1.1.1 no-access
Network traffic passing through ports is analyzed by sending a copy of the traffic to another port on the same or different switch. This table contains the analyzer parameters.
             jnxAnalyzerEntry 1.3.6.1.4.1.2636.3.40.1.1.1.1.1.1 no-access
A row instance contains the Analyzer Name, Analyzer Status, Mirroring Ratio, Loss Priority.
                 jnxAnalyzerName 1.3.6.1.4.1.2636.3.40.1.1.1.1.1.1.1 displaystring no-access
This object identifies a unique Analyzer configured on the switch.
                 jnxAnalyzerStatus 1.3.6.1.4.1.2636.3.40.1.1.1.1.1.1.2 truthvalue read-only
This object identifies whether the mirroring associated with a particular analyzer is enabled or disabled.
                 jnxMirroringRatio 1.3.6.1.4.1.2636.3.40.1.1.1.1.1.1.3 unsigned32 read-only
This object will specify the mirroring ratio. User can configure the analyzer to mirror only one out of X packets [1:X packets] in the ingress/egress side based on whether the port is configured for ingress or egress mirroring. The configuration supports a range from 1: X [0 <= X <= 2047].Default value is 1.
                 jnxLossPriority 1.3.6.1.4.1.2636.3.40.1.1.1.1.1.1.4 integer read-only
The analyzer port may be congested when the number of packets exceeds the bandwidth of the analyzer port. So the loss-priority parameter is enabled. The switched packets will not get affected by this. The value 0 corresponds to low priority.The value 1 corresponds to high loss priority. Enumeration: 'high': 1, 'low': 0.
         jnxAnalyzerInputTable 1.3.6.1.4.1.2636.3.40.1.1.1.1.2 no-access
An analyzer Session is an association of several source ports to a destination port.A range or series of ports can be mirrored in a session.
             jnxAnalyzerInputEntry 1.3.6.1.4.1.2636.3.40.1.1.1.1.2.1 no-access
An Entry is created for each Input Source port.
                 jnxAnalyzerInputValue 1.3.6.1.4.1.2636.3.40.1.1.1.1.2.1.1 displaystring no-access
This identifies each different analyzer input source. If the value of jnxAnalyzerInputType is 1 then jnxAnalyzerInputValue refers to the input source Interface Name. If the value of jnxAnalyzerInputType is 2 then jnxAnalyzerInputValue refers to the input source vlan name.
                 jnxAnalyzerInputOption 1.3.6.1.4.1.2636.3.40.1.1.1.1.2.1.2 integer read-only
A source port is a switch port that is been mirrored. It can be mirrored based either on Ingress(received) traffic or egress (transmitted) traffic. The goal of receive (or ingress) Analyzer is to monitor as much as possible all the packets received by the source interface. The amount of received packets mirrored to the destination port depends on the mirroring ratio. A series or range of ingress ports can be mirrored in an analyzer session. The goal of transmit (or egress) analyzer is to monitor as much as possible all the packets sent by the source interface. The amount of egress packets mirrored to the destination port depends on the mirroring ratio.The copy is provided after the packet is modified. A range of egress ports can be mirrored in an analyzer session. The value 1 corresponds to mirroring ingress traffic. The value 2 corresponds to mirroring egress traffic. Enumeration: 'ingress': 1, 'egress': 2.
                 jnxAnalyzerInputType 1.3.6.1.4.1.2636.3.40.1.1.1.1.2.1.3 integer read-only
This specifies whether interfaces or VLANs is mirrored. Mirroring can be done on the basis of the interface name.All packets received on a port configured for ingress mirroring is sent to the analyzer port.All packets sent out on a port configured for egress mirroring is sent to the analyzer port.Any number of network ports can be configured for ingress or egress mirroring.The value one of jnxAnalayzerInputType corresponds to mirroring the interface traffic. On a particular switch, the user can choose to monitor all the ports that belong to a particular VLAN. It is needed in order to analyze the network traffic in one or more VLANs.Mirroring can be configured in ingress direction only for VLAN. Mirroring can be done on the basis of VLAN name (supported only in ingress). All packets received on a particular VLAN are sent out to the analyzer.The value two of jnxAnalyzerInputType corresponds to mirroring vlan traffic. Enumeration: 'interface': 1, 'vlanname': 2.
         jnxAnalyzerOutputTable 1.3.6.1.4.1.2636.3.40.1.1.1.1.3 no-access
This table describes the destination port to which the traffic from the source ports are copied.
             jnxAnalyzerOutputEntry 1.3.6.1.4.1.2636.3.40.1.1.1.1.3.1 no-access
An Entry is created for each destination port or destination vlan.
                 jnxAnalyzerOutputValue 1.3.6.1.4.1.2636.3.40.1.1.1.1.3.1.1 displaystring no-access
This object identifies each different destination port or destination vlan. If the value of jnxAnalyzerOutputType is 1 then jnxAnalyzerOutputValue gives the destination interface name. If the value of jnxAnalyzerOutputType is 2 then jnxAnalyzerOutputValue gives the destination vlan name.
                 jnxAnalyzerOutputType 1.3.6.1.4.1.2636.3.40.1.1.1.1.3.1.2 integer read-only
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. Enumeration: 'interface': 1, 'vlanname': 2.
         jnxExAnalyzerInputTable 1.3.6.1.4.1.2636.3.40.1.1.1.1.4 no-access
An analyzer Session is an association of several source ports to a destination port.A range or series of ports can be mirrored in a session.
             jnxExAnalyzerInputEntry 1.3.6.1.4.1.2636.3.40.1.1.1.1.4.1 no-access
An Entry is created for each Input Source port.
                 jnxExAnalyzerInputOption 1.3.6.1.4.1.2636.3.40.1.1.1.1.4.1.1 integer no-access
A source port is a switch port that is been mirrored. It can be mirrored based either on Ingress(received) traffic or egress (transmitted) traffic. The goal of receive (or ingress) Analyzer is to monitor as much as possible all the packets received by the source interface. The amount of received packets mirrored to the destination port depends on the mirroring ratio. A series or range of ingress ports can be mirrored in an analyzer session. The goal of transmit (or egress) analyzer is to monitor as much as possible all the packets sent by the source interface. The amount of egress packets mirrored to the destination port depends on the mirroring ratio.The copy is provided after the packet is modified. A range of egress ports can be mirrored in an analyzer session. The value 1 corresponds to mirroring ingress traffic. The value 2 corresponds to mirroring egress traffic. The value 3 corresponds to mirroring vlan ingress traffic. The value 4 corresponds to mirroring vlan egress traffic. Enumeration: 'ingress': 1, 'egress': 2, 'egress-vlan': 4, 'vlan': 3.
                 jnxExAnalyzerInputValue 1.3.6.1.4.1.2636.3.40.1.1.1.1.4.1.2 displaystring no-access
This identifies each different analyzer input source. If the value of jnxExAnalyzerInputType is 1 then jnxExAnalyzerInputValue refers to the input source Interface Name. If the value of jnxExAnalyzerInputType is 2 then jnxExAnalyzerInputValue refers to the input source vlan name.
                 jnxExAnalyzerInputType 1.3.6.1.4.1.2636.3.40.1.1.1.1.4.1.3 integer read-only
This specifies whether interfaces or VLANs is mirrored. Mirroring can be done on the basis of the interface name.All packets received on a port configured for ingress mirroring is sent to the analyzer port.All packets sent out on a port configured for egress mirroring is sent to the analyzer port.Any number of network ports can be configured for ingress or egress mirroring.The value one of jnxAnalyzerInputType corresponds to mirroring the interface traffic. On a particular switch, the user can choose to monitor all the ports that belong to a particular VLAN. It is needed in order to analyze the network traffic in one or more VLANs.Mirroring can be configured in ingress direction only for VLAN. Mirroring can be done on the basis of VLAN name (supported only in ingress). All packets received on a particular VLAN are sent out to the analyzer.The value two of jnxExAnalyzerInputType corresponds to mirroring vlan traffic. Enumeration: 'interface': 1, 'vlanname': 2.