How to enable the FC option on NX4 module?

08/08/2011
By

Well today I decided to see if i can access the backend storage on my Celerra NX4… Guess what! I couldn’t!

The reason for my decision was that I have upgraded the DART software on the Celerra Server from 5.6.x to 6.0.41.4 and to make sure that the FLARE version on the CLARiiON backend is also up-to-date!

Caution: Changing the SPs IP Addresses in a Proxy ARP implementation requires rebooting the backend storage array to change their network configuration. Only one SP will be rebooted at a time to make the process as non-disruptive as possible. While the SPs are rebooting, the backend storage array and Celerra system performance will be degraded. The estimated time for the upgrade is 15 minutes.

So, here is the steps below to enable this option on my Celerra NX4 Server.

1- I have connected to the Control Station using SSH.

2- I opened a HyperTerminal session and logged in with the user name "nasadmin" and password "nasadmin".

Connecting to 172.16.0.190:22…
Connection established.
Escape character is ‘^@]’.

A customized version of the Linux operating system is used on the     
EMC(R) Celerra(R) Control Station.  The operating system is     
copyrighted and licensed pursuant to the GNU General Public License     
("GPL"), a copy of which can be found in the accompanying     
documentation.  Please read the GPL carefully, because by using the     
Linux operating system on the EMC Celerra you agree to the terms     
and conditions listed therein.     
     
EXCEPT FOR ANY WARRANTIES WHICH MAY BE PROVIDED UNDER THE TERMS AND      
CONDITIONS OF THE APPLICABLE WRITTEN AGREEMENTS BETWEEN YOU AND EMC,      
THE SOFTWARE PROGRAMS ARE PROVIDED AND LICENSED "AS IS" WITHOUT      
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT      
NOT LIMITED TO, THE IMPLIED MERCHANTABILITY AND FITNESS FOR A      
PARTICULAR PURPOSE.  In no event will EMC Corporation be liable to      
you or any other person or entity for (a) incidental, indirect,      
special, exemplary or consequential damages or (b) any damages      
whatsoever resulting from the loss of use, data or profits,      
arising out of or in connection with the agreements between you      
and EMC, the GPL, or your use of this software, even if advised      
of the possibility of such damages.     
     
EMC and Celerra are registered trademarks or trademarks of     
EMC Corporation in the United States and/or other countries.  All     
other trademarks used herein are the property of their respective owners.

EMC Celerra Control Station Linux release 3.0 (NAS 6.0.41)     
WARNING! The remote SSH server rejected X11 forwarding request.
Last login: Mon Aug  8 09:51:49 2011 from 172.16.0.254
EMC Celerra Control Station Linux   Tue Apr 26 09:08:28 EDT 2011

    *** slot_0 primary control station ***

3- Changed to the root user with the command:

[nasadmin@NX4Demo ~]$ su root
Password:
[root@NX4Demo nasadmin]#

4- Run the following command to verify that the system is in a good state:

# /nas/bin/nas_checkup

Sample output:
[root@NX4Demo nasadmin]# /nas/bin/nas_checkup
Check Version:    6.0.41.4
Check Command:    /nas/bin/nas_checkup
Check Log    :    /nas/log/checkup-run.110808-111419.log

————————————-Checks————————————-
Control Station: Checking statistics groups database………………….. Pass
Control Station: Checking if file system usage is under limit………….. Pass
Control Station: Checking if NAS Storage API is installed correctly…….. Pass
Control Station: Checking if NAS Storage APIs match……………………  N/A
Control Station: Checking if NBS clients are started………………….. Pass
Control Station: Checking if NBS configuration exists…………………. Pass
Control Station: Checking if NBS devices are accessible……………….. Pass
Control Station: Checking if NBS service is started…………………… Pass
Control Station: Checking if PXE service is stopped…………………… Pass
Control Station: Checking if standby is up……………………………  N/A
Control Station: Checking integrity of NASDB…………………………. Pass
Control Station: Checking if primary is active……………………….. Pass
Control Station: Checking all callhome files delivered………………… Pass
Control Station: Checking resolv conf……………………………….. Pass
Control Station: Checking if NAS partitions are mounted……………….. Pass
Control Station: Checking ipmi connection……………………………. Pass
Control Station: Checking nas site eventlog configuration……………… Pass
Control Station: Checking nas sys mcd configuration…………………… Pass
Control Station: Checking nas sys eventlog configuration………………. Pass
Control Station: Checking logical volume status………………………. Pass
Control Station: Checking valid nasdb backup files……………………. Pass
Control Station: Checking root disk reserved region…………………… Pass
Control Station: Checking if RDF configuration is valid………………..  N/A
Control Station: Checking if fstab contains duplicate entries………….. Pass
Control Station: Checking if sufficient swap memory available………….. Pass
Control Station: Checking for IP and subnet configuration……………… Pass
Control Station: Checking auto transfer status……………………….. Pass
Control Station: Checking for invalid entries in etc hosts…………….. Pass
Control Station: Checking the hard drive in the control station………… Pass
Control Station: Checking if Symapi data is present…………………… Pass
Control Station: Checking if Symapi is synced with Storage System………. Pass
Blades         : Checking boot files………………………………… Pass
Blades         : Checking if primary is active……………………….. Pass
Blades         : Checking if root filesystem is too large……………… Pass
Blades         : Checking if root filesystem has enough free space……… Pass
Blades         : Checking if using standard DART image………………… Pass
Blades         : Checking network connectivity……………………….. Pass
Blades         : Checking status……………………………………. Pass
Blades         : Checking dart release compatibility………………….. Pass
Blades         : Checking dart version compatibility………………….. Pass
Blades         : Checking server name……………………………….. Pass
Blades         : Checking unique id…………………………………. Pass
Blades         : Checking CIFS file server configuration………………. Pass
Blades         : Checking domain controller connectivity and configuration. Pass
Blades         : Checking DNS connectivity and configuration…………… Pass
Blades         : Checking connectivity to WINS servers………………… Pass
Blades         : Checking I18N mode and unicode translation tables……… Pass
Blades         : Checking connectivity to NTP servers…………………. Warn
Blades         : Checking connectivity to NIS servers…………………. Pass
Blades         : Checking virus checker server configuration…………… Pass
Blades         : Checking if workpart is OK………………………….. Pass
Blades         : Checking if free full dump is available………………. Pass
Blades         : Checking if each primary Blade has standby……………. Pass
Blades         : Checking if Blade parameters use EMC default values……. Pass
Blades         : Checking VDM root filesystem space usage……………… Pass
Blades         : Checking if file system usage is under limit………….. Pass
Blades         : Checking for excessive memory utilization…………….. Pass
Blades         : Checking for REPV2 component configuration……………. Pass
Storage System : Checking disk emulation type………………………… Pass
Storage System : Checking disk high availability access……………….. Pass
Storage System : Checking disks read cache enabled……………………. Pass
Storage System : Checking disks and storage processors write cache enabled. Pass
Storage System : Checking if FLARE is committed………………………. Pass
Storage System : Checking if FLARE is supported………………………. Pass
Storage System : Checking array model……………………………….. Pass
Storage System : Checking if microcode is supported……………………  N/A
Storage System : Checking no disks or storage processors are failed over… Pass
Storage System : Checking that no disks or storage processors are faulted.. Pass
Storage System : Checking that no hot spares are in use……………….. Pass
Storage System : Checking that no hot spares are rebuilding……………. Pass
Storage System : Checking minimum control lun size……………………. Pass
Storage System : Checking maximum control lun size……………………. Pass
Storage System : Checking maximum lun address limit…………………… Pass
Storage System : Checking system lun configuration……………………. Pass
Storage System : Checking if storage processors are read cache enabled….. Pass
Storage System : Checking if auto assign are disabled for all luns……… Pass
Storage System : Checking if auto trespass are disabled for all luns……. Pass
Storage System : Checking storage processor connectivity………………. Pass
Storage System : Checking control lun ownership………………………. Pass
Storage System : Checking if Fibre Channel zone checker is set up……….  N/A
Storage System : Checking if Fibre Channel zoning is OK………………..  N/A
Storage System : Checking if proxy arp is setup……………………….  N/A
Storage System : Checking SPA SPB communication………………………. Pass
Storage System : Checking for unsupported storage profile……………… Pass
Storage System : Checking if Clariion security is enabled……………… Pass
Storage System : Checking if backend has mixed disk types……………… Pass
——————————————————————————–

One or more warnings have occurred. It is recommended that you follow the
instructions provided to correct the problem then try again.

————————————Warnings————————————

Blades : Check connectivity to NTP servers
Warning HC_DM_18800115743:
     * server_2: Only one NTP server is configured. It is recommended to
       define at least two different NTP servers for a high availability.
       If the clock of the Data Mover is not correct, potential errors
       during Kerberos authentication may happen (timeskew).
Action : Use the server_date command to define another NTP server on
     the Data Mover. Read the man pages for details and examples.

——————————————————————————–

Ok, the Celerra is in good state to start the process.

5- Verifing the Celerra model number before the process, by typing:

# /nas/sbin/model

Sample output:
[root@NX4Demo sbin]# /nas/sbin/model
NX4

6- Now I enabled the FC option by typing the following command:

# /nas/sbin/nas_hw_upgrade -fc_option -enable

Sample output:
[root@NX4Demo sbin]# /nas/sbin/nas_hw_upgrade -fc_option -enable
Checking if running as root…yes
Checking if FC option is enabled…no
Checking for integrated system…yes
Checking if model is supported…yes
Checking if backend is supported…yes
Model: NX4FC
Command succeeded

7- Recheck the Celerra model number after this process:

[root@NX4Demo sbin]# /nas/sbin/model
NX4FC

Great!

8- Then I wanted to know the public IP addresses for the SPA and SPB, so I typed:

# /nasmcd/sbin/clariion_mgmt -info

Sample output:
[root@NX4Demo nasadmin]# /nasmcd/sbin/clariion_mgmt -info
Error 12: Not configured

Haa! I don’t have public IP addresses for the SPA and SPB!

Okay, okay don’t panic, let’s just configure them.

heem, let’s look at the parameters and attributes of the command "clariion_mgmt":

[root@NX4Demo sbin]# ./clariion_mgmt
Error 255: clariion_mgmt
         -start [ -spa_ip <Public IP for SPA> ] [ -spb_ip <Public IP for SPB> ] [ -use_nat | -use_proxy_arp (default) | -use_proxy_nd ]
       | -modify [ -spa_ip <Public IP for SPA> ] [ -spb_ip <Public IP for SPB> ]
       | -recover [-o]
       | -stop [ -use_proxy_nd ]
       | -info [ -use_proxy_nd ]

OK, I found what I needed!

9- So, to give the SPA and SPB a new public IP addresses, I typed:

# /nasmcd/sbin/clariion_mgmt -start -spa_ip <new IP> -spb_ip <new IP> -use_proxy_arp
 
Sample output:
[root@NX4Demo sbin]# ./clariion_mgmt -start -spa_ip 172.16.0.189 -spb_ip 172.16.0.188 -use_proxy_arp
Checking if running as root…yes
Checking if model is supported…yes
Checking for integrated system…yes
Checking if interface eth3 is configured…yes
Checking if interface eth3:1 is configured…no
Checking if interface eth3:2 is configured…no
Checking if IP (172.16.0.189) is available…yes
Checking if IP (172.16.0.188) is available…yes
Checking if SP (128.221.252.200) is up…yes
Checking if SP (128.221.253.201) is up…yes
Checking if a gateway is setup for eth3…yes
Step 1/12 [28185788431]: Setting up Proxy ARP for SPA on Control Station
Adding host specific route for SPA
Adding rules to allow outbound traffic from SPA
Adding ARP entry for SPA
Updating /etc/hosts entry for SPA
Step 2/12 [28185788417]: Changing SPA IP address.
WARNING: This will require a reboot of the SP.
WARNING: Answering "No" below will abort the entire script.
WARNING: Please answer whether it is OK to continue [y] or [n]: y
Changing SPA IP from 128.221.252.200 to 172.16.0.189 (subnetmask 255.255.0.0, gateway 172.16.1.10)
Step 3/12 [28185788419]: Waiting for SPA to reboot.
Waiting for SPA to go down…done (68 secs)
Step 4/12 [28185788423]: Waiting for SPA to boot up.
Waiting for SPA to come back up………….done (59 secs)
Step 5/12 [28185788427]: Waiting for CLARiiON software to start on SPA.
Waiting for CLARiiON software to start on SPA….done (61 secs)
Waiting until SPB sees 172.16.0.189 in the domain…done (37 secs)
Step 6/12 [28185788429]: Updating NAS database with SPA IP address.
Updating SYMAPI database with new CLARiiON IP addresses…done (162 secs)
Step 7/12 [28185788432]: Setting up Proxy ARP for SPB on Control Station
Adding host specific route for SPB
Adding rules to allow outbound traffic from SPB
Adding ARP entry for SPB
Updating /etc/hosts entry for SPB
Step 8/12 [28185788418]: Changing SPB IP address.
WARNING: This will require a reboot of the SP.
WARNING: Answering "No" below will abort the entire script.
WARNING: Please answer whether it is OK to continue [y] or [n]: y
Changing SPB IP from 128.221.253.201 to 172.16.0.188 (subnetmask 255.255.0.0, gateway 172.16.1.10)
Step 9/12 [28185788420]: Waiting for SPB to reboot.
Waiting for SPB to go down…done (69 secs)
Step 10/12 [28185788424]: Waiting for SPB to boot up.
Waiting for SPB to come back up…………..done (66 secs)
Step 11/12 [28185788428]: Waiting for CLARiiON software to start on SPB.
Waiting for CLARiiON software to start on SPB….done (72 secs)
Waiting until SPA sees 172.16.0.188 in the domain…done (3 secs)
Step 12/12 [28185788430]: Updating NAS database with SPB IP address.
Updating SYMAPI database with new CLARiiON IP addresses…done (102 secs)
FINISH: Operation took a total time of 13 minutes 2 seconds to complete.

10- Nice, checked the new configured IP addresses:

[root@NX4Demo sbin]# ./clariion_mgmt -info
Public IP address for SPA: 172.16.0.189
Public IP address for SPB: 172.16.0.188
Start on boot            : yes
Current implementation   : Proxy-ARP
Status                   : Started

11- Then checked if the hosts file was updated with the new IP addresses:

[root@NX4Demo sbin]# cd /etc
[root@NX4Demo etc]# cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1        localhost.localdomain localhost
::1        localhost6.localdomain6 localhost6
# Internal DART Server Primary Network
128.221.252.1  server_1    #DART_data_mover_1
128.221.252.2  server_2    #DART_data_mover_2
128.221.252.3  server_3    #DART_data_mover_3
128.221.252.4  server_4    #DART_data_mover_4
128.221.252.5  server_5    #DART_data_mover_5
128.221.252.6  server_6    #DART_data_mover_6
128.221.252.7  server_7    #DART_data_mover_7
128.221.252.8  server_8    #DART_data_mover_8
128.221.252.9  server_9    #DART_data_mover_9
128.221.252.10  server_10    #DART_data_mover_10
128.221.252.11  server_11    #DART_data_mover_11
128.221.252.12  server_12    #DART_data_mover_12
128.221.252.13  server_13    #DART_data_mover_13
128.221.252.14  server_14    #DART_data_mover_14
128.221.252.15  server_15    #DART_data_mover_15
128.221.252.16  server_16    #DART_data_mover_16
# Internal Management Switch Primary Network
128.221.252.50  mgmt_2_3          #ENCLOSURE-0_MGMT_A
128.221.252.51  mgmt_4_5          #ENCLOSURE-1_MGMT_A
128.221.252.52  mgmt_6_7          #ENCLOSURE-2_MGMT_A
128.221.252.53  mgmt_8_9          #ENCLOSURE-3_MGMT_A
# Internal UPS Primary Network
128.221.252.90  emcnasUPS_i0      #UPS_0
128.221.252.101    emcnasotherCS_i0
# Internal DART Server Backup Network
128.221.253.1  server_1b    #DART_data_mover_1
128.221.253.2  server_2b    #DART_data_mover_2
128.221.253.3  server_3b    #DART_data_mover_3
128.221.253.4  server_4b    #DART_data_mover_4
128.221.253.5  server_5b    #DART_data_mover_5
128.221.253.6  server_6b    #DART_data_mover_6
128.221.253.7  server_7b    #DART_data_mover_7
128.221.253.8  server_8b    #DART_data_mover_8
128.221.253.9  server_9b    #DART_data_mover_9
128.221.253.10  server_10b    #DART_data_mover_10
128.221.253.11  server_11b    #DART_data_mover_11
128.221.253.12  server_12b    #DART_data_mover_12
128.221.253.13  server_13b    #DART_data_mover_13
128.221.253.14  server_14b    #DART_data_mover_14
128.221.253.15  server_15b    #DART_data_mover_15
128.221.253.16  server_16b    #DART_data_mover_16
# Internal Management Switch Backup Network
128.221.253.50  mgmt_2_3b         #ENCLOSURE-0_MGMT_B
128.221.253.51  mgmt_4_5b         #ENCLOSURE-1_MGMT_B
128.221.253.52  mgmt_6_7b         #ENCLOSURE-2_MGMT_B
128.221.253.53  mgmt_8_9b         #ENCLOSURE-3_MGMT_B
# Internal UPS Backup Network
128.221.253.90  emcnasUPS_i1      #UPS_1
128.221.253.101    emcnasotherCS_i1
128.221.252.100        emcnas_i0.localdomain emcnas_i0
128.221.253.100        emcnas_i1
128.221.254.100        emcnas_ipmi
128.221.254.101        emcnasotherIPMICS_i3
172.16.0.190    NX4Demo.demo.local    NX4Demo
172.16.0.189 A_SL7E9091900035 SPA # CLARiiON SP
172.16.0.188 B_SL7E9091900035 SPB # CLARiiON SP

12- At the end, I did a re-discover for the CLARiiON backend storage from the Celerra to see the new IP addresses:

# nas_storage -check -all

Sample output:
[root@NX4Demo etc]# nas_storage -check -all

Discovering storage (may take several minutes)

done

13- just checking to see if i can ping the new IP addresses:

C:\> ping 172.16.0.189

Pinging 172.16.0.189 with 32 bytes of data:
Reply from 172.16.0.189: bytes=32 time=318ms TTL=126
Reply from 172.16.0.189: bytes=32 time=1ms TTL=126
Reply from 172.16.0.189: bytes=32 time<1ms TTL=126
Reply from 172.16.0.189: bytes=32 time<1ms TTL=126

Ping statistics for 172.16.0.189:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 318ms, Average = 79ms

C:\> ping 172.16.0.188

Pinging 172.16.0.188 with 32 bytes of data:
Reply from 172.16.0.188: bytes=32 time=409ms TTL=126
Reply from 172.16.0.188: bytes=32 time<1ms TTL=126
Reply from 172.16.0.188: bytes=32 time<1ms TTL=126
Reply from 172.16.0.188: bytes=32 time<1ms TTL=126

Ping statistics for 172.16.0.188:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 409ms, Average = 102ms

14- Finally I can connect to the CLARiiON backend storage and check if there is any FLARE updates:

a. start “Unisphere Service Manager” and type in the IP address of SPA or SPB.

image

b. Name: “nasadmin”, Password: “nasadmin”.

image

c. And now, I can do all the necessary actions on the CLARiiON storage like “Registration”, “Add/Remove” Hardware, Software Updates and Diagnostics!

usm 

 

Voila! that was it. Now I have change my Celerra NX4 to Celerra NX4FC.

One Response to How to enable the FC option on NX4 module?

  1. Unexpected on 08/08/2011 at 15:30

    Excellent work! Now let’s get this baby hooked up to vSphere 5.0 😉