Behavior Of Various Applications For Switch-Initiated Traffic - Dell S4820T Configuration Manual

Hide thumbs Also See for S4820T:

Table of Contents

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.

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

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

Sflow-collector

Snmp (SNMP Mib response and

icmp (ping and traceroute)

Behavior when EIS is Enabled

EIS Behavior

EIS Behavior for ICMP

Behavior when EIS is Disabled

Default Behavior

Internet Group Management Protocol (IGMP)