
Traffic type /
Application type
Switch initiated traffic
Switch-destined traffic
Transit Traffic
management port is down or route lookup
fails, packets are dropped
Non-EIS
management
application
Front-end default route will take
higher precedence over
management default route and
SSH session to an unknown
destination uses the front-end
default route only. No change in
the existing behavior.
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
Traffic from
management port to
data port and from data
port to management
port is blocked
•
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.
Internet Group Management Protocol (IGMP)
363
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...