JUNIPER-ANALYZER-MIB

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

This object identifies a unique Analyzer configured on the switch.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object identifies whether the mirroring associated with a particular analyzer is enabled or disabled.

Unsigned32

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.

INTEGER0 = low1 = high · Integer32

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.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

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.

INTEGER1 = ingress2 = egress · Integer32

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.

INTEGER1 = interface2 = vlanname · Integer32

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.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

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.

INTEGER1 = interface2 = vlanname · Integer32

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.

INTEGER1 = ingress2 = egress3 = vlan4 = egress-vlan · Integer32

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.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

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.

INTEGER1 = interface2 = vlanname · Integer32

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.