Deployment Guide

Table Of Contents
This 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
not reachable through the management port (next hop ARP is not resolved, and so on), and if the destination is reachable
through a data port, 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 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 Traffic
This 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 and the 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 and traceroute) using the source ip option, the management port IP address should be specified as the source IP address.
If management port is 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 39. Behavior of Various Applications for Switch-Initiated Traffic
Protocol Behavior when EIS is Enabled Behavior when EIS is Disabled
dns EIS Behavior Default Behavior
ftp EIS Behavior Default Behavior
ntp EIS Behavior Default Behavior
radius EIS Behavior Default Behavior
Sflow-collector Default Behavior
Snmp (SNMP Mib response and SNMP
Traps)
EIS Behavior Default Behavior
ssh EIS Behavior Default Behavior
syslog EIS Behavior Default Behavior
tacacs EIS Behavior Default Behavior
telnet EIS Behavior Default Behavior
tftp EIS Behavior Default Behavior
icmp (ping and traceroute) EIS Behavior for ICMP Default Behavior
Behavior of Various Applications for Switch-Destined Traffic
This section describes the different system behaviors that occur when traffic is terminated on the switch. Traffic has not
originated from the switch and is not transiting the switch. Switch-destined traffic is applicable only for applications which act
as server for the TCP session and also for ICMP-based applications like ping and traceroute. FTP, SSH, and Telnet are the
applications that can function as servers for the TCP session.
354
Internet Group Management Protocol (IGMP)