This phenomenon occurs where traffic is transiting the switch. Traffic has not originated from the switch and is not terminating on theswitch.• 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 TrafficThis phenomenon occurs where traffic is terminated on the switch. Traffic has not originated from the switch and is not transiting theswitch.The switch accepts all traffic destined to the switch, which is received on management or front-end data port. Response traffic withmanagement port IP address as source IP address is handled in the same manner as switch originated traffic.Switch-Originated TrafficThis phenomenon occurs where traffic is originating from the switch.1 Management Applications (Applications that are configured as management applications):The management port is an egress port for management applications. If the management port is down or the destination is notreachable through the management port (next hop ARP is not resolved, and so on), and if the destination is reachable through a dataport, then the management application traffic is sent out through the front-end data port. This fallback mechanism is required.2 Non-Management Applications (Applications that are not configured as management applications as defined by this feature):Non-management application traffic exits out of either front-end data port or management port based on routing table. If there is adefault route on both the management and front-end data port, the default for the data port is preferred route.Behavior of Various Applications for Switch-Initiated TrafficThis section describes the different system behaviors that occur when traffic is originating from the switch:EIS Behavior: If the destination TCP/UDP port matches a configured management application, a route lookup is done in the EIS table andthe management port gets selected as the egress port. If management port is down or the route lookup fails, packets are dropped.EIS Behavior for ICMP: ICMP packets do not have TCP/UDP ports. To do an EIS route lookup for ICMP-based applications (ping andtraceroute) using the source ip option, the management port IP address should be specified as the source IP address. If management portis down or route lookup fails, packets are dropped.Default Behavior: Route lookup is done in the default routing table and appropriate egress port is selected.Table 35. Behavior of Various Applications for Switch-Initiated TrafficProtocol Behavior when EIS is Enabled Behavior when EIS is Disableddns EIS Behavior Default Behaviorftp EIS Behavior Default Behaviorntp EIS Behavior Default Behaviorradius EIS Behavior Default BehaviorSflow-collector Default BehaviorInternet Group Management Protocol (IGMP) 369
