OOBM and switch applications
The table below shows the switch applications that are supported on the OOBM interface as well as on the data interfaces. In this list, some applications are client-only, some are server-only, and some are both.
Application |
Inbound OOBM (server) |
Outbound OOBM (client) |
Inbound data plane (server) |
Outbound data plane (client) |
|---|---|---|---|---|
Telnet |
yes |
yes |
yes |
yes |
SSH |
yes |
N/A | yes |
N/A1 |
SNMP |
yes |
yes |
yes |
yes |
TFTP |
yes |
yes |
yes |
yes |
HTTP |
yes |
N/A1 | yes |
N/A1 |
SNTP |
N/A1 | yes |
N/A1 | yes |
TIMEP |
N/A1 | yes |
N/A1 | yes |
RADIUS |
N/A1 | yes |
N/A1 | yes |
TACACS |
N/A1 | yes |
N/A1 | yes |
DNS |
N/A1 | yes |
N/A1 | yes |
Syslog |
N/A1 | yes |
N/A1 | yes |
Ping |
yes |
yes |
yes44 |
yes |
Traceroute |
yes44 |
yes |
yes44 |
yes |
not applicable
Ping and Traceroute do not have explicit servers. Ping and Traceroute responses are sent by the host stack.
For applications that have servers,
oobm/data/both options have been added to listen mode. There is now a
listen keyword in the CLI commands to allow selection of those options. Default
value is
both for all servers.