Alcatel-Lucent OmniSwitch 9000 Quick Setup Guide

22

Your First Login Session

Access to the EMP. By default, only devices in the same 
subnet as the EMP will be able to manage the switch 
through that port. For information on allowing devices in 
other subnets to manage the switch via the EMP, refer to 
the OmniSwitch 9000 Series Hardware Users Guide.

Save these changes to the switch’s running memory by 

entering commit system at the boot prompt:

Boot > commit system

This will immediately enable your changes and allow 

users to ping the EMP. However, note that these changes 

have not yet been saved to the switch’s boot.params file 

and will be lost if the switch is rebooted.

To permanently save these changes to the 

boot.params file, enter commit file at the boot prompt:

Boot > commit file

Changes will be preserved following a switch reboot.

Return to the CLI prompt by entering exit at the boot 

prompt.

Important. Although you have configured the EMP with 
valid IP address information, you will not be able to 
access the switch through this port for Telnet, FTP, 
WebView, or SNMP sessions until you have unlocked 
these remote session types. See 

 for more information.

Security is a key feature on OmniSwitch 9000 switches. As a 
result, when you access the switch for the first time, you must 
use a direct console port connection. All other session types 
(Telnet, FTP, WebView, and SNMP) are “locked out” until 
they are manually unlocked by the user.

The CLI command used to unlock session types is 

Note. When you unlock session types, you are granting 
switch access to non-local sessions (e.g., Telnet). As a 
result, users who know the correct user login and pass-
word will have remote access to the switch. For more 
information on switch security, refer to the Switch 
Management Guide.

To unlock all session types, enter the following command 
syntax at the CLI prompt:

-> aaa authentication default local