l
To log in to the system for the first time, enter username
setup
and follow the on-screen directions to create a
user account. After doing so, the
setup
user will expire, and you will be logged in as the user just created.
l
To log in thereafter, use valid system user credentials.
7. At the prompt, type the following command to set the values you obtained in step 1 on page 44 for each network
port, first for controller A and then for controller B:
set network-parameters ip
address
netmask
netmask
gateway
gateway
controller a|b
where:
l
address
is the IP address of the controller
l
netmask
is the subnet mask
l
gateway
is the IP address of the subnet router
l
a|b
specifies the controller whose network parameters you are setting
For example:
# set network-parameters ip 192.168.0.10 netmask 255.255.255.0 gateway 192.168.0.1
controller a
# set network-parameters ip 192.168.0.11 netmask 255.255.255.0 gateway 192.168.0.1
controller b
NOTE See the CLI Reference Guide for information about IPv6, and the commands used to add IPv6 addresses and
set IPv6 network parameters. The
ipv6
term is included within each relevant command name.
8. Type the following command to verify the new IP address:
l
For IPv4, enter the
show network-parameters
CLI command.
l
For IPv6, enter the
show ipv6-network-parameters
CLI command.
Network parameters, including the IP address, subnet mask, and gateway address are displayed for each controller.
9. Use the ping command to verify network connectivity.
For example, to ping the gateway in the examples above:
# ping 192.168.0.0
Info: Pinging 192.168.0.1 with 4 packets.
Success: Command completed successfully. - The remote computer responded with 4
packets.
10. In the host computer's command window, type the following command to verify connectivity, first for controller A
and then for controller B:
ping
controller-IP-address
If you cannot access your system for at least three minutes after changing the IP address, your network might require
you to restart the Management Controller(s) using the CLI port. When you restart a Management Controller,
communication with the MC is temporarily lost until it successfully restarts.
Type the following command to restart the management controller on both controllers:
restart mc both
11. When you are done using the CLI, exit the emulator.
12. Retain the new IP addresses to access and manage the controllers, using either the SMU or the CLI.
44
Chapter 5
Connecting to the controller CLI port