Behavior Of Various Applications For Switch-Initiated Traffic - Dell S4048–ON Configuration Manual

S-series 10gbe switches
Hide thumbs Also See for S4048–ON:
Table of Contents

Advertisement

Traffic type /
Switch initiated traffic
Application type
Non-EIS
Front-end default route will take
management
higher precedence over
application
management default route and
SSH session to an unknown
destination uses the front-end
default route only. No change in
the existing behavior.
EIS is enabled implies that EIS feature is enabled and the application might or might not be configured as a management
application
EIS is disabled implies that either EIS feature itself is disabled or that the application is not configured as a management
application
Transit Traffic
This phenomenon occurs where traffic is transiting the switch. Traffic has not originated from the switch and is not terminating on
the switch.
Drop the packets that are received on the front-end data port with destination on the management port.
Drop the packets that received on the management port with destination as the front-end data port.
Switch-Destined Traffic
This phenomenon occurs where traffic is terminated on the switch. Traffic has not originated from the switch and is not transiting
the switch.
The switch accepts all traffic destined to the switch, which is received on management or front-end data port. Response traffic with
management port IP address as source IP address is handled in the same manner as switch originated traffic.
Switch-Originated Traffic
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.
Switch-destined traffic
management port is down or route lookup
fails, packets are dropped
If source TCP/UDP port matches a
management application and the source IP
address is a management port IP address, the
management port is the preferred egress port
selected based on route lookup in EIS table. If
the management port is down or the route
lookup fails, packets are dropped
Internet Group Management Protocol (IGMP)
Transit Traffic
Traffic from
management port to
data port and from data
port to management
port is blocked
363

Advertisement

Table of Contents
loading

Table of Contents