• To ensure that protocol separation is done only for switch initiated traffic where the application actsas client, only the destination TCP/UDP port is compared and not the source TCP/UDP port. Thesource TCP/UDP port becomes a known port number when the box acts as server.• TFTP is an exception to the preceding logic.• For TFTP, data transfer is initiated on port 69, but the data transfer ports are chosen independently bythe sender and receiver during initialization of the connection. The ports are chosen at randomaccording to the parameters of the networking stack, typically from the range of temporary ports.• If route lookup in EIS routing table succeeds, the application-specific packet count is incremented.This counter is viewed using the show management application pkt-cntr command. Thiscounter is cleared using clear management application pkt-cntr command.• If the route lookup in the EIS routing table fails or if management port is down, then packets aredropped. The application-specific count of the dropped packets is incremented and is viewed usingthe show management application pkt-drop-cntr command. This counter is cleared usingclear management application pkt-drop-cntr command.• Packets whose destination TCP/UDP port does not match a configured management application, takethe regular route lookup flow in the IP stack.• In the ARP layer, for all ARP packets received through the management interface, a double routelookup is done, one in the default routing table and another in the management EIS routing table. Thisis because in the ARP layer, we do not have TCP/UDP port information to decide the table in whichthe route lookup should be done.• The show arp command is enhanced to show the routing table type for the ARP entry.• For the clear arp-cache command, upon receiving the ARP delete request, the routecorresponding to the destination IP is identified. The ARP entries learned in the management EISrouting table are also cleared.• Therefore, a separate control over clearing the ARP entries learned via routes in the EIS table is notpresent. If the ARP entry for a destination is cleared in the default routing table, then if an ARP entryfor the destination exists in the EIS table, that entry is also cleared.• Because fallback support is removed, if the management port is down or the route lookup in EIS tablefails packets are dropped. Therefore, switch-initiated traffic sessions that used to work previously viafallback may not work now.Handling of Switch-Destined Traffic• The switch processes all traffic received on the management port destined to the management portIP address or the front-end port destined to the front-end IP address.• If the source TCP/UDP port number matches a configured EIS or non-EIS management applicationand the source IP address is a management Port IP address, then the EIS route lookup is done for theresponse traffic and hence is sent out of the management port. In this case, the source IP address is amanagement port IP address only if the traffic was originally destined to the management port IP.• ICMP-based applications like ping and traceroute are exceptions to the preceding logic since we donot have TCP/UDP port number. So if source IP address of the packet matches the management portIP address EIS route lookup is done.• Management application packet counter is incremented if EIS route lookup succeeds and packet issent out of the management port.• If route lookup in the EIS routing table fails or if the management port is down, then packets aredropped. The management application drop counter is incremented.Internet Group Management Protocol (IGMP) 369
