This phenomenon occurs where traffic is transiting the switch. Traffic has not originated from the switchand is not terminating on the switch.• Drop the packets that are received on the front-end data port with destination on the managementport.• 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 theswitch and is not transiting the switch.The switch accepts all traffic destined to the switch, which is received on management or front-end dataport. Response traffic with management port IP address as source IP address is handled in the samemanner 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 isdown or the destination is not reachable through the management port (next hop ARP is notresolved, and so on), and if the destination is reachable through a data port, then the managementapplication 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 asdefined by this feature):Non-management application traffic exits out of either front-end data port or management portbased on routing table. If there is a default 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 theswitch:EIS Behavior: If the destination TCP/UDP port matches a configured management application, a routelookup is done in the EIS table and the management port gets selected as the egress port. If managementport 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 and traceroute) using the source ip option, the management port IP addressshould be specified as the source IP address. If management port is down or route lookup fails, packetsare dropped.Default Behavior: Route lookup is done in the default routing table and appropriate egress port isselected.312 Internet Group Management Protocol (IGMP)
