Concept Guide

Enabling and Disabling Management Egress Interface Selection
You can enable or disable egress-interface-selection using the management egress-interface-selection command.
NOTE: Egress Interface Selection (EIS) works only with IPv4 routing.
When the feature is enabled using the management egress-interface-selection command, the following events are performed:
• The CLI prompt changes to the EIS mode.
• In this mode, you can run the application and no application commands
• Applications can be congured or uncongured as management applications using the application or no application
command. All congured applications are considered as management applications and the rest of them as non-management
applications.
• All the management routes (connected, static and default) are duplicated and added to the management EIS routing table.
• Any new management route added is installed to both the EIS routing table and default routing table.
• For management applications, route lookup is preferentially done in the management EIS routing table for all trac. management port is
the preferred egress port. For example, if SSH is a management application, an SSH session to a front-panel port IP on the peer box is
initiated via management port only, if the management port is UP and management route is available.
• If SSH request is received on the management port destined to the management port IP address, the response to the request is sent
out of the management port by performing a route lookup in the EIS routing table
• If the SSH request is received on the front-end port destined for the front-end IP address, the response trac is sent by doing a route
lookup in the default routing table only.
• If the management port is down or route lookup fails in the management EIS routing table, packets are dropped.
• For all non-management applications, trac exits out of either front-end data port or management port based on route lookup in
default routing table.
• Ping and traceroute are always non-management applications and route lookup for these applications is done in the default routing table
only.
• For ping and traceroute utilities that are initiated from the switch, if reachability needs to be tested through routes in the management
EIS routing table, you must congure ICMP as a management application.
• If ping and traceroute are destined to the management port IP address, the response trac for these packets is sent by doing route
lookup in the EIS routing table.
When the feature is disabled using the no management egress-interface-selection command, the following operations are
performed:
• All management application conguration is removed.
• All routes installed in the management EIS routing table are removed.
Handling of Management Route Conguration
When the EIS feature is enabled, the following processing occurs:
• All existing management routes (connected, static and default) are duplicated and added to the management EIS routing table.
• Any management static route newly added using the management route CLI is installed to both the management EIS routing table
and default routing table.
400
Internet Group Management Protocol (IGMP)