Clariion storage processor IP address change

We recently spinned off to a new company from the parent one. As a result a major infrastructure change had to be performed on all our equipments. We had a few Clariions for which the storage processors IP address had to change, as were assigned a new block of IP address.

Their are a few things that had to be taken care before undergoing an IP address change of he storage processor IP address.

1. If the Clariion is master node of the global domain, then someone else had to be promoted to be domain master before changing the IP address. That is it has to be demoted as a master domain node.
2. Then the clarrion has to be removed from the domain. That is the domain security has to be reset
3. The storage processor has to be rebooted

Briefly, the steps are as follows:

1. Promote some other Clariion to be the master node of the domain. (This can be achieved through the Navisphere web based console).
2. Remove the Clariion from the domain. (This can be done through the Navisphere web console)
3. Reset the domain security principles. (http://SPA-IP/setup; Click Reset domain security)
4. Wait for it to come up
5. Repeat the same for the other node
6. Go to (http://SPA-IP/setup and change the IP address, ensure the peer IP address remains the same not the new one). The SP A will reboot. Wait for it to come up.
7. Repeart the same for the other SP node, ensuring the new IP address is reflected in the peer IP field. The SP B will be rebooted. Wait for it to come up.
8. Change the peer IP address field for the SP A. The SP A will be rebooted.

The new changes are in effect now. Join the Clariion back into domain and promote it as a master node (if previously)

Comments

Post a Comment

Popular posts from this blog

zpool and power path partial compatibility

Is power path fully supported with zpools, no. It's partial. You can have the pseudo devices assigned to a pool but it uses the native ctd disk only. Recently I lost 2 paths from the vnx array to m9000 server running Solaris 11.1. When I ran the zpool status -x command some of the pools were online while some of them were un available. Power path was reporting 2 paths only but it was active. So ideally the zpools should be online. But it's not. I enabled the remaining 2 paths and all became online. Internally the pools were pointing to one of the ctd devices that belonged to dead path and it was not coming online. Also few of the emcpower devices were renamed, so I had to do zpool import -d with the alternate disk. It seems power path is not completely supported now but may become in future.
Read more

NFS common problems

Have you come across very silly problem while mounting NFS share. It just comes out of no where and refuses to go. Hours of efforts are wasted when we find the exact issue and seems like banging our head on the doors. I have summarized some of them, I hope you might be having your set of goodies as well. If you are getting an error like permission denied on the client server (90% of the issue falls here), then check in sequence what has to be done: 1. If the server has multiple IP address, it can no surprises. Do a traceroute from the server to the client and see which interface is being used to connect. Of course please check first whether the client is pinging or not. Once you have the interface detail, this IP will be used on the clients to map the network share. 2. See if you can resolve the client IP address using DNS, if you can then use dns name in the share access list on the NFS server. 3. If the client has multiple interface, then do a traceroute to the IP found in 1...
Read more