Celerra Setup problems

if your ever stuck trying to use /nascmd/sbin/clariion_mgmt and the command just won’t go through, try this option   -skip_rules

Change Celerra IP address

So I read a lot of Scott Lowe’s blog, and again he has the answer, but I needed just a bit more detail to make this work.  Since i’m using his blog as a starting point i’ll reference it here.  I also used this here from EMC

My Summary:

first, change the IP of the Celerra Manger, also known as the “control station”

Then change the IP of the SP’s with this command

/nasmcd/sbin/clariion_mgmt -start -spa_ip 128.221.ххх.ххх -spb_ip 128.221.ххх.ххх -use_proxy_arp

So a few things i’ll add

1) when using the clariion_mgmt tool, make sure to ssh as nasadmin, then su to root, if you ssh directly as root, the command might fail for you as it did for me with a “NAS_DB environment variable is not defined” message.

2) default passwords for nasadmin and root are “nasadmin”

3) when you setup a PPP connection to the Celerra or Clariion, do it this way:

Use the special EMC serial cable and the maintenance port on the back of the SP. Create a PPP dial up connection on your Windows laptop 115200 baud, HW flow control. Point a web browser to http://192.168.1.1/setup .

Username: clariion
Password: clariion!

I love when a question becomes a standard

When VMW says that vCenter needs a static IP

They mean it.

vSphere 4.1 upgrade gotchas

For any of you thinking about building a new vCenter on a 64 bit OS so you can upgrade to 4.1, you should just export your database and import it on another machines. This is especially true if you use vDS's (vNetwork Distributed Switch), remember that these are stored on the vCenter and will continue to work on the ESX hosts, but will be difficult to modify/import/recreate on your new vCenter 4.1 server. To compound this difficult situation, if you are using iSCSI to reach your shared storage you will be in more deep stuff.

If you find yourself in this scenario, and you know what you named your previous vDS's, PortGroups, etc.. you may be able to recreate it without much difficulty. It gets more difficult when your using 8+ nic's per ESX Host. If you just need to start from scratch, it'll take a reboot or two of your ESX hosts (especially if you use EVC CPU masking) to get everything ripped out so you can start over again.

Remove Non-Present Devices from Device Manager

After you P2V something, there are alot of old hardware devices that no longer exist, but you can’t see them by default, this article tells you how to see them so you can remove them.

http://support.microsoft.com/kb/315539

Upgrade iLo on a whole HP chassis

log into HP OBA with SSH

run

update ilo all tftp://x.x.x.x/ilo2_200.bin

wait 10 minutes