routes. If SSH is specified as a management application, SSH links to and from an unknown destinationuses the management default route.Protocol SeparationWhen you configure the application application-type command to configure a set ofmanagement applications with TCP/UDP port numbers to the OS, the following table describes theassociation between applications and their port numbers.Table 14. Association Between Applications and Port NumbersApplication Name Port Number Client ServerSSH 22 Supported SupportedSflow-Collector 6343 SupportedSNMP 162 for SNMP Traps (client),161 for SNMP MIB response (server)SupportedNTP 123 SupportedDNS 53 SupportedFTP 20/21 Supported SupportedSyslog 514 SupportedTelnet 23 Supported SupportedTFTP 69 SupportedRadius 1812,1813 SupportedTacacs 49 SupportedHTTP 80 for httpd443 for secure httpd8008 HTTP server port for confd application8888 secure HTTP server port for confdapplicationSupportedIf you configure a source interface is for any EIS management application, EIS might not coexist with thatinterface and the behavior is undefined in such a case. You can configure the source interface for thefollowing 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 trapsbecause 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. YouInternet Group Management Protocol (IGMP) 307
