User guide

Overview of Switch Login Components Logging Into the Switch
page 2-4 OmniSwitch AOS Release 7 Switch Management Guide March 2015
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.
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 aaa authentication command.
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 Chapter 8, “Managing 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, see “Configuring the Console Port” on page 2-6.
• EMP Port—The Ethernet Management Port (EMP) allows you to bypass the Network Interface (NI)
modules and remotely manage the switch directly through the CMM., see “Setting the EMP Port’s IP
Address” on page 2-7
• 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 “Using Telnet” on page 2-8.
• Secure Shell—Any standard Secure Shell client may be used for remote login to the switch. See
“Using Secure Shell” on page 2-9.
OmniSwitch
Switch Login Components
remote user
local user
local user
database
Login via Secure Shell, Telnet,
HTTP, or SNMP
Login via the console port.
Authentication
Server