Traffic type /
Application type
Switch initiated traffic
Switch-destined traffic
Transit Traffic
only. No change in the existing
behavior.
port is down or the route lookup fails, packets
are dropped
•
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.
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.
312
Internet Group Management Protocol (IGMP)
Summary of Contents for S3048-ON
Page 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Page 137: ...0 Gi 1 1 Gi 1 2 rx Flow N A N A 0 0 No N A N A yes Access Control Lists ACLs 137 ...
Page 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Page 241: ...Dell Control Plane Policing CoPP 241 ...
Page 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Page 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Page 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Page 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Page 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Page 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Page 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Page 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...