![Dell S6000-ON Configuration Manual Download Page 370](http://html.mh-extra.com/html/dell/s6000-on/s6000-on_configuration-manual_84557370.webp)
• Whenever IP address is assigned to the management port, it is stored in a global variable in the IP
stack, which is used for comparison with the source IP address of the packet.
• Rest of the response traffic is handled as per existing behavior by doing route lookup in the default
routing table. So if the traffic is destined to the front-end port IP address, the response is sent out by
doing a route lookup in the default routing table, which is an existing behavior.
Consider a sample topology in which ip1 is an address assigned to the management port and ip2 is an
address assigned to any of the front panel port. A and B are end users on the management and front-
panel port networks. The OS-initiated traffic for management 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
traffic for such end-user-originated sessions destined to management port ip1 is handled using the EIS
route lookup.
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 34. 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
Traffic from
management port
to data port and
from data port to
management port
is blocked
370
Internet Group Management Protocol (IGMP)
Summary of Contents for S6000-ON
Page 1: ...Dell Configuration Guide for the S6000 ON System 9 9 0 0 ...
Page 557: ...Figure 80 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 557 ...
Page 562: ...Figure 83 MSDP Default Peer Scenario 1 562 Multicast Source Discovery Protocol MSDP ...
Page 563: ...Figure 84 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 563 ...
Page 564: ...Figure 85 MSDP Default Peer Scenario 3 564 Multicast Source Discovery Protocol MSDP ...
Page 665: ...Policy based Routing PBR 665 ...
Page 818: ...Figure 110 Single and Double Tag TPID Match 818 Service Provider Bridging ...
Page 819: ...Figure 111 Single and Double Tag First byte TPID Match Service Provider Bridging 819 ...
Page 995: ...Figure 140 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 995 ...