• Whenever IP address is assigned to the management port, it is stored in a global variable in the IPstack, 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 defaultrouting table. So if the traffic is destined to the front-end port IP address, the response is sent out bydoing 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 anaddress 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 assource IP and uses the management network to reach the destination. If the management port is downor the route lookup in EIS routing table fails, ip2 is the source IP and the front-panel port is used to reachthe destination. The fallback route between the management and data networks is used in such a case. Atany given time, end users can access Dell Networking OS applications using either ip1 or ip2. Returntraffic for such end-user-originated sessions destined to management port ip1 is handled using the EISroute 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 netstatcommand, like all other IP layer counters.Consider a scenario in which ip1 is an address assigned to the management port and ip2 is an addressassigned to any of the front panel port of a switch. End users on the management and front panel portnetworks are connected. In such an environment, traffic received in the management port destined onthe data port network is dropped and traffic received in the front-end port destined on the managementnetwork is dropped.Mapping of Management Applications and Traffic TypeThe following table summarizes the behavior of applications for various types of traffic when themanagement egress interface selection feature is enabled.Table 34. Mapping of Management Applications and Traffic TypeTraffic type /ApplicationtypeSwitch initiated traffic Switch-destined traffic Transit TrafficEISManagementApplicationManagement is thepreferred egress portselected based on routelookup in EIS table. If themanagement port is downor the route lookup fails,packets are dropped.If source TCP/UDP port matches amanagement application and sourceIP address is management port IPaddress, management port is thepreferred egress port selected basedon route lookup in EIS table. IfTraffic frommanagement portto data port andfrom data port tomanagement portis blocked370 Internet Group Management Protocol (IGMP)
