Mellanox MLNX-OS® User Manualfor SX1018HP Ethernet Managed Blade Switch

Rev 1.6.9
Mellanox Technologies
82
Mellanox Technologies Confidential
There is no limitation on the number of the source interfaces mapped to a mirroring session.
LAG
The source interface can be a physical interface or a LAG.
Port mirroring can be configured on a LAG interface but not on a LAG member. When a port is
added to a mirror
ed LAG it inherits the LAG’s mirror configuration. However, if port mirroring
configuration is set on a port, that configuration must be removed prior to adding the port to a
LAG interface.
When a port is removed from a LAG, the mirror property is switched of
f for that port.
Control Protocols
All control protocols captured on the mirror port are
forwarded to the analyzer port in addition to
their normal treatment. For example LACP, STP, and LLDP are forwarded to the analyzer port in
addition to their normal treatment by the CPU.
Exceptions to the behavior above a
re the packets that are being handled by the MAC layer, such
as pause frames.
5.10.1.2 Destination Interface
The destination interface is an analyzer port is one to whic
h mirrored traffic is sent. The mirrored
packets, are duplicated, optionally modified and sent to the analyzer port. The SwitchX® plat-
form supports up to 7 analyzer ports where any mirror port can be mapped to any analyzer port
and more than a single
mirror port can be mapped to a single analyzer port.
Packets can be forwarded to any destination using the command
destination interface .
The analyzer port supports status and statistics as any other port.
LAG
The destination interface cannot be a member of LAG when
the header format is local.
Control Protocols
The destination interface may also operate in part a
s a standard port, receiving and sending out
non-mirrored traffic. When the header format is configured as a local port, ingress control proto-
col packets that are received by the local analyzer port get discarded.
Advanced MTU Considerations
The analyzer port, like its counterparts, is subject
to MTU configuration. It does not send packets
longer than configured.
When the analyzer port sends encapsulated traf
fic, the analyzer traffic has additional headers and
therefore longer frame. The MTU must be configured to support the additional length, otherwise,
the packet is truncated to the configured MTU.
Ingress and egress traffic flows of a specific source interface can be mapped to two dif-
ferent sessions.