users can access Dell Networking OS applications using either ip1 or ip2. Return traffic for such end-user-
originated sessions destined to management port ip1 is handled using the EIS route lookup.
Handling of Transit Traffic (Traffic Separation)
This is forwarded traffic where destination IP is not an IP address configured in the switch.
• Packets received on the management port with destination on the front-end port is dropped.
• Packets received on the front-end port with destination on the management port is dropped.
• A separate drop counter is incremented for this case. This counter is viewed using the
netstat
command, like all other IP layer counters.
Consider a scenario in which ip1 is an address assigned to the management port and ip2 is an address
assigned to any of the front panel port of a switch. End users on the management and front panel port
networks are connected. In such an environment, traffic received in the management port destined on the
data port network is dropped and traffic received in the front-end port destined on the management network
is dropped.
Mapping of Management Applications and
Traffic Type
The following table summarizes the behavior of applications for various types of traffic when the
management egress interface selection feature is enabled.
Table 37. Mapping of Management Applications and Traffic Type
Traffic type /
Application
type
Switch initiated traffic
Switch-destined traffic
Transit Traffic
EIS
Management
Application
Management 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.
If source TCP/UDP port matches a
management application and source
IP address is management port IP
address, management port is the
preferred egress port selected based
on route lookup in EIS table. If
management port is down or route
lookup fails, packets are dropped
Traffic from
management port
to data port and
from data port to
management port is
blocked
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
Internet Group Management Protocol (IGMP)
446
Содержание S4048T
Страница 1: ...Dell Configuration Guide for the S4048T ON System 9 10 0 1 ...
Страница 98: ... saveenv 7 Reload the system uBoot mode reset Management 98 ...
Страница 113: ...Total CFM Pkts 10303 CCM Pkts 0 LBM Pkts 0 LTM Pkts 3 LBR Pkts 0 LTR Pkts 0 802 1ag 113 ...
Страница 411: ...mode transit no disable Force10 Resilient Ring Protocol FRRP 411 ...
Страница 590: ...Figure 67 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 590 ...
Страница 591: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 591 ...
Страница 594: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 594 ...
Страница 595: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 595 ...
Страница 646: ...Figure 87 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 646 ...
Страница 647: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 647 ...
Страница 648: ...Figure 89 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 648 ...
Страница 653: ...Figure 91 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 653 ...
Страница 654: ...Figure 92 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 654 ...
Страница 955: ...Figure 119 Single and Double Tag First byte TPID Match Service Provider Bridging 955 ...
Страница 1179: ...Figure 147 Create Hypervisor Figure 148 Edit Hypervisor Figure 149 Create Transport Connector Virtual Extensible LAN VXLAN 1179 ...