Users Guide

applications takes a preference for ip1 as source IP and uses the management network to reach the destination. If the management
port is down or the route lookup in EIS routing table fails, ip2 is the source IP and the front-panel port is used to reach the
destination. The fallback route between the management and data networks is used in such a case. At any given time, end users can
access Dell Networking OS applications using either ip1 or ip2. Return trac for such end-user-originated sessions destined to
management port ip1 is handled using the EIS route lookup.
Handling of Transit Trac (Trac Separation)
This is forwarded trac where destination IP is not an IP address congured 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, trac
received in the management port destined on the data port network is dropped and trac received in the front-end port destined on
the management network is dropped.
Mapping of Management Applications and Trac Type
The following table summarizes the behavior of applications for various types of trac when the management egress interface
selection feature is enabled.
Table 34. Mapping of Management Applications and Trac Type
Trac type /
Application type
Switch initiated trac Switch-destined trac Transit Trac
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
Trac 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
Trac 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 congured as a management
application
• EIS is disabled implies that either EIS feature itself is disabled or that the application is not congured as a management
application
Transit Trac
This phenomenon occurs where trac is transiting the switch. Trac 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.
376
Internet Group Management Protocol (IGMP)