Administrator Guide

Handling of Transit Traffic (Traffic Separation)
This is forwarded traffic where destination IP is not an IP address configured in the switch.
● Packets received on the management port with destination on the front-end port is dropped.
● Packets received on the front-end port with destination on the management port is dropped.
● A separate drop counter is incremented for this case. This counter is viewed using the netstat command, like all other IP
layer counters.
Consider a scenario in which ip1 is an address assigned to the management port and ip2 is an address assigned to any of
the front panel port of a switch. End users on the management and front panel port networks are connected. In such an
environment, traffic received in the management port destined on the data port network is dropped and traffic received in the
front-end port destined on the management network is dropped.
Mapping of Management Applications and Traffic Type
The following table summarizes the behavior of applications for various types of traffic when the management egress interface
selection feature is enabled.
Table 37. Mapping of Management Applications and Traffic Type
Traffic type /
Application type
Switch initiated traffic Switch-destined traffic Transit Traffic
EIS Management
Application
Management is the preferred
egress port selected based on
route lookup in EIS table. If the
management port is down or the
route lookup fails, packets are
dropped.
If source TCP/UDP port matches a
management application and source IP
address is management port IP address,
management port is the preferred egress
port selected based on route lookup in EIS
table. If management port is down or route
lookup fails, packets are dropped
Traffic from
management port
to data port and
from data port to
management port is
blocked
Non-EIS
management
application
Front-end default route will
take higher precedence over
management default route and
SSH session to an unknown
destination uses the front-end
default route only. No change in
the existing behavior.
If source TCP/UDP port matches a
management application and the source IP
address is a management port IP address,
the management port is the preferred egress
port selected based on route lookup in EIS
table. If the management port is down or the
route lookup fails, packets are dropped
Traffic from
management port
to data port and
from data port to
management port is
blocked
● EIS is enabled implies that EIS feature is enabled and the application might or might not be configured as a management
application
● EIS is disabled implies that either EIS feature itself is disabled or that the application is not configured as a management
application
Transit Traffic
This phenomenon occurs where traffic is transiting the switch. Traffic has not originated from the switch and is not terminating
on the switch.
● Drop the packets that are received on the front-end data port with destination on the management port.
● Drop the packets that received on the management port with destination as the front-end data port.
Switch-Destined Traffic
This phenomenon occurs where traffic is terminated on the switch. Traffic has not originated from the switch and is not
transiting the switch.
The switch accepts all traffic destined to the switch, which is received on management or front-end data port. Response traffic
with management port IP address as source IP address is handled in the same manner as switch originated traffic.
Switch-Originated Traffic
364
Internet Group Management Protocol (IGMP)