Logging Into the Switch
Overview of Switch Login Components
Switch access components include access methods (or interfaces) and user accounts stored on the local
user database in the switch and/or on external authentication servers. Each access method, except the
console port, must be enabled or "unlocked" on the switch before users can access the switch through that
interface.
Authentication
Server
Management Interfaces
Logging into the switch may be done locally or remotely. Remote connections may be secure or insecure,
depending on the method. Management interfaces are enabled using the
This command also requires specifying the external servers and/or local user database that will be used to
authenticate users. The process of authenticating users to manage the switch is called Authenticated
Switch Access (ASA). Authenticated Switch Access is described in detail in
Switch Security."
An overview of management methods is listed here:
Logging Into the CLI
•
Console port—A direct connection to the switch through the console port. The console port is always
enabled for the default user account. For more information about connecting to the console port, see
your OmniSwitch Hardware Users Guide.
•
Telnet—Any standard Telnet client may be used for remote login to the switch. This method is not
secure. For more information about using Telnet to access the switch, see
•
FTP—Any standard FTP client may be used for remote login to the switch. This method is not secure.
See
"Using FTP" on page
•
Secure Shell—Any standard Secure Shell client may be used for remote login to the switch. See
"Using Secure Shell" on page
OmniSwitch AOS Release 6 Switch Management Guide
OmniSwitch
local user
database
Switch Login Components
2-9.
2-11.
Overview of Switch Login Components
Login via Secure Shell, Telnet,
FTP, HTTP, or SNMP
local user
Login via the console port.
aaa authentication
July 2010
remote user
command.
Chapter 11, "Managing
"Using Telnet" on page
2-7.
page 2-5