CLI Reference Guide-R04

Chapter 1 | Initial Switch Configuration
Configuring the Switch for Remote Management
– 54 –
Username: admin
Password:
CLI session with the ECS4120-28Fv2-I* is opened.
To end the CLI session, enter [Exit].
Console#configure
Console(config)#username guest password 0 [password]
Console(config)#username admin password 0 [password]
Console(config)#
* This manual covers the ECS4120-28Fv2 and ECS4120-28Fv2-I Gigabit Ethernet
switches. There are no significant differences between the switches, therefore
most of the screen display examples are based on the ECS4120-28Fv2-I.
Remote Connections
(Network Interface)
Prior to accessing the switch’s onboard agent via a network connection, you must
first configure the switch’s network interface with a valid IPv4 or IPv6 address.
The default network interface is VLAN 1 which includes ports 1-28. When
configuring the network interface, the IP address, subnet mask, and default
gateway may all be set using a console connection, or DHCP protocol as described
in the following sections.
An IPv4 address for the primary network interface is obtained via DHCP by default.
To manually configure this address or enable dynamic address assignment via
DHCP, see “Setting an IP Address” on page 55.
After configuring the switch’s IP parameters, you can access the onboard
configuration program from anywhere within the attached network. The onboard
configuration program can be accessed using Telnet or SSH from any computer
attached to the network. The switch can also be managed by any computer using a
web browser (Internet Explorer 11, Mozilla Firefox 52, or Google Chrome 57, or
more recent versions).
Note: This switch supports eight Telnet sessions or SSH sessions.
The onboard program only provides access to basic configuration functions. To
access the full range of SNMP management functions, you must use SNMP-based
network management software.
Configuring the Switch for Remote Management
The switch can be managed through the operational network, known as in-band
management. Because in-band management traffic is mixed in with operational
network traffic, it is subject to all of the filtering rules usually applied to a standard
network ports such as ACLs and VLAN tagging. In-band network management can
be accessed via a connection to any network port (1-28).