HP StorageWorks 2000fc HP StorageWorks 2312fc and 2324fc Modular Smart Array u - Page 26

If you cannot your access your system for at least three minutes, after changing the IP, address

Get HP StorageWorks 2000fc - G2 Modular Smart Array PDF manuals and user guides View all HP StorageWorks 2000fc manuals
Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

6. At the prompt, type the following command to set the values you obtained in Step 1 for each Ethernet management port, first for controller A and then for controller B: set network-parameters ip address netmask netmask gateway gateway controller a|b where: • address is the IP address of the controller • netmask is the subnet mask • gateway is the IP address of the subnet router • 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 193.168.0.1 controller b 7. Type the following command to verify the new IP addresses: show network-parameters Network parameters, including the IP address, subnet mask, and gateway address are displayed for each controller. a. From the CLI you can use the PING command to verify network connectivity For example: # ping 16.125.12.1 Info: Pinging 16.125.12.1 with 4 packets. Success: Command completed successfully. The remote computer responded with 4 packets. 8. Disconnect from the CLI and exit the emulator. 9. In the host computer's command window, type the following command to verify Ethernet connectivity, first for controller A and then for controller B: ping IP-address If you cannot your access your system for at least three minutes after changing the IP address, your network might require you to restart the management controller using the serial CLI. When you restart a management controller, communication with it is temporarily lost until it successfully restarts. Type the following command to restart the management controller on both controllers: restart mc both 26 Installing the enclosures

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
26
Installing the enclosures
6.
At the prompt, type the following command to set the values you obtained in Step 1 for each Ethernet
management port, first for controller A and then for controller B:
set network-parameters ip
address
netmask
netmask
gateway
gateway
controller a|b
where:
•
address is the IP address of the controller
•
netmask is the subnet mask
•
gateway is the IP address of the subnet router
•
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
193.168.0.1 controller b
7.
Type the following command to verify the new IP addresses:
show network-parameters
Network parameters, including the IP address, subnet mask, and gateway address are displayed for
each controller.
a.
From the CLI you can use the PING command to verify network connectivity
For example:
# ping 16.125.12.1
Info: Pinging 16.125.12.1 with 4 packets.
Success: Command completed successfully. The remote computer responded with 4 packets.
8.
Disconnect from the CLI and exit the emulator.
9.
In the host computer's command window, type the following command to verify Ethernet connectivity,
first for controller A and then for controller B:
ping
IP-address
If you cannot your access your system for at least three minutes
after changing the IP
address
, your network might require you to restart the management controller using the serial CLI. When
you restart a management controller, communication with it is temporarily lost until it successfully restarts.
Type the following command to restart the management controller on both controllers:
restart mc both