Egress Interface Selection (EIS) for HTTP and IGMPApplicationsYou can use the Egress Interface Selection (EIS) feature to isolate the management and front-end port domains for HTTP and IGMPtraffic. Also, EIS enables you to configure the responses to switch-destined traffic by using the management port IP address as the sourceIP address. This information is sent out of the switch through the management port instead of the front-end port.The management EIS feature is applicable only for the out-of-band (OOB) management port. References in this section to themanagement default route or static route denote the routes configured using the management route command. The managementdefault route can be either configured statically or returned dynamically by the DHCP client. A static route points to the managementinterface or a forwarding router.Transit traffic (destination IP not configured in the switch) that is received on the front-end port with destination on the management portis dropped and received in the management port with destination on the front-end port is dropped.Switch-destined traffic (destination IP configured in the switch) is:• Received in the front-end port with destination IP equal to management port IP address or management port subnet broadcast addressis dropped.• Received in the management port with destination IP not equal to management IP address or management subnet broadcast address isdropped.Traffic (switch initiated management traffic or responses to switch-destined traffic with management port IP address as the source IPaddress) for user-specified management protocols must exit out of the management port. In this chapter, all the references to trafficindicate switch-initiated traffic and responses to switch-destined traffic with management port IP address as the source IP address.In customer deployment topologies, it might be required that the traffic for certain management applications needs to exit out of themanagement port only. You can use EIS to control and the traffic can exit out of any port based on the route lookup in the IP stack.One typical example is an SSH session to an unknown destination or an SSH connection that is destined to the management port IPaddress. The management default route can coexist with front-end default routes. If SSH is specified as a management application, SSHlinks to and from an unknown destination uses the management default route.Protocol SeparationWhen you configure the application application-type command to configure a set of management applications with TCP/UDPport numbers to the OS, the following table describes the association between applications and their port numbers.Table 33. Association Between Applications and Port NumbersApplication Name Port Number Client ServerSSH 22 Supported SupportedSflow-Collector 6343 SupportedSNMP 162 for SNMP Traps (client),161 for SNMP MIB response (server)SupportedNTP 123 SupportedDNS 53 Supported364 Internet Group Management Protocol (IGMP)
