Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual page 4256

Complete Software Guide for Junos
Table 553: Logical Operators for the monitor traffic Command (continued)
Logical Operator (Highest to Lowest Precedence)
&&
||
( )
4152
®
OS for EX Series Ethernet Switches, Release 10.4
Description
Logical AND. If the first condition matches, the next condition is
evaluated. If the first condition does not match, the next condition is
skipped.
Logical OR. If the first condition matches, the next condition is skipped.
If the first condition does not match, the next condition is evaluated.
Group operators to override default precedence order. Parentheses are
special characters, each of which must be preceded by a backslash
(
\
You can use relational operators to compare arithmetic expressions composed of integer
constants, binary operators, a length operator, and special packet data accessors. The
arithmetic expression matching condition uses the following syntax:
monitor traffic matching "ether[0] & 1 != 0""arithmetic_expression relational_operator
arithmetic_expression"
The packet data accessor uses the following syntax:
protocol [byte-offset <size>]
The optional size field represents the number of bytes examined in the packet header.
The available values are
1, 2,
multicast traffic:
user@host> monitor traffic matching "ether[0] & 1 != 0"
To specify match conditions that have a numeric value, use the arithmetic and relational
operators listed in Table 554 on page 4153.
NOTE: Because the Packet Forwarding Engine removes Layer 2 header
information before sending packets to the Routing Engine:
The
monitor traffic
traffic.
The
monitor traffic interface
for Layer 3 and Layer 4 packet data, resulting in the
match ) for this command for Layer 3 and Layer 4 packets not working
either. Therefore, ensure that you specify match conditions as described
in this command summary. For more information about match conditions,
see Table 552 on page 4150.
The 802.1Q VLAN tag information included in the Layer 2 header is removed
from all inbound traffic packets. As the
command for aggregated Ethernet interfaces (such as
inbound traffic data, the command does not show VLAN tag information
in the output.
).
or bytes.The following sample command captures all
4
command cannot apply match conditions to inbound
command also cannot apply match conditions
pipe option (
match
monitor traffic interface ae[x]
ae0 ) only shows
Copyright © 2010, Juniper Networks, Inc.
|