[an error occurred while processing this directive][an error occurred while processing this directive]

Analyzer Input Table

The jnxAnalyzerInputTable, whose object identifier is {jnxAnalyzerMIBObjects 2}, contains information about analyzer sessions. In a typical analyzer session, several source ports can be associated with a single destination port, and a range or series of ports can be mirrored.

Each jnxAnalyzerInputEntry provides information about input source ports, and contains the objects listed in Table 1.

Table 1: jnxAnalyzerInputTable

Object

Object ID

Description

jnxAnalyzerInputValue

jnxAnalyzerInputEntry 1

Identifies an analyzer input source port. This object can contain a display string of not more than 255 characters.

  • If the value of jnxAnalyzerInputType is 1, then the value of jnxAnalyzerInputValue denotes the interface name of the input source.
  • If the value of jnxAnalyzerInputType is 2, then the value of jnxAnalyzerInputValue denotes the VLAN name of the input source.

jnxAnalyzerInputOption

jnxAnalyzerInputEntry 2

Denotes the type of traffic to be mirrored from the source port; that is, whether it is ingress traffic or egress traffic. This object uses the following integer values:

  • 1–Ingress traffic, where the analyzer monitors packets received by the source port.
  • 2–Egress traffic, where the analyzer monitors packets transmitted by the source port.

In both the cases, the number of packets mirrored to the destination port depends on the jnxMirroringRatio.

jnxAnalyzerInputType

jnxAnalyzerInputEntry 3

Denotes whether the mirroring source is an interface or a VLAN. This object uses integer values 1 (for interface) and 2 (for VLAN).

For interfaces, you can configure either ingress or egress mirroring, whereas for VLANS, you can configure only ingress mirroring.


Published: 2010-04-27

[an error occurred while processing this directive]