
In customer deployment topologies, it might be required that the traffic for certain management applications needs to exit out of the
management port only. You can use EIS to control and the traffic can exit out of any port based on the route lookup in the IP stack.
One typical example is an SSH session to an unknown destination or an SSH connection that is destined to the management port IP
address. The management default route can coexist with front-end default routes. If SSH is specified as a management application,
SSH links to and from an unknown destination uses the management default route.
Protocol Separation
When you configure the
application
application-type
command to configure a set of management applications with
TCP/UDP port numbers to the OS, the following table describes the association between applications and their port numbers.
Table 36. Association Between Applications and Port Numbers
Application Name
Port Number
Client
Server
SSH
22
Supported
Supported
Sflow-Collector
6343
Supported
SNMP
162 for SNMP Traps (client),
161 for SNMP MIB response (server)
Supported
NTP
123
Supported
DNS
53
Supported
FTP
20/21
Supported
Supported
Syslog
514
Supported
Telnet
23
Supported
Supported
TFTP
69
Supported
Radius
1812,1813
Supported
Tacacs
49
Supported
HTTP
80 for httpd
443 for secure httpd
8008 HTTP server port for confd application
8888 secure HTTP server port for confd
application
Supported
If you configure a source interface is for any EIS management application, EIS might not coexist with that interface and the behavior
is undefined in such a case. You can configure the source interface for the following applications: FTP, ICMP (ping and traceroute
utilities), NTP, RADIUS, TACACS, Telnet, TFTP, syslog, and SNMP traps. Out of these applications, EIS can coexist with only syslog
and SNMP traps because these applications do not require a response after a packet is sent.
The switch also processes user-specified port numbers for applications such as RADIUS, TACACS, SSH, and sFlow. The OS
maintains a list of configured management applications and their port numbers. You can configure two default routes, one configured
on the management port and the other on the front-end port.
Internet Group Management Protocol (IGMP)
359
Содержание 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 ...