09-18-2002 04:06 PM - edited 03-02-2019 01:27 AM
I want to disable the ability to Telnet directly into the NAM. Sessioning in from the CAT is the only avenue I want available, or a way to use TACACs for NAM console logins.
Solved! Go to Solution.
09-18-2002 04:14 PM
Session into the NAM and then use the command 'exsession off' which will disbale external telnet access to the NAM. However, you can setup TACACS for login to the NAM Web Interface.
Here are the command details:
exsession [on | off]
Controls whether external Telnet sessions are accepted by the NAM from outside the switch. The default is set to off. If the exsession command is set to off, you can only Telnet to the NAM from the supervisor engine on the switch. If the exsession command is set to on, new Telnet requests from any valid IP address are accepted. This command will not drop any open sessions. This command can be used by the root account only.
09-18-2002 04:14 PM
Session into the NAM and then use the command 'exsession off' which will disbale external telnet access to the NAM. However, you can setup TACACS for login to the NAM Web Interface.
Here are the command details:
exsession [on | off]
Controls whether external Telnet sessions are accepted by the NAM from outside the switch. The default is set to off. If the exsession command is set to off, you can only Telnet to the NAM from the supervisor engine on the switch. If the exsession command is set to on, new Telnet requests from any valid IP address are accepted. This command will not drop any open sessions. This command can be used by the root account only.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide