Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Netapp: toasters

6030A - 6040A HEAD SWAP. SOME DOUBTS

 

 

Netapp toasters RSS feed   Index | Next | Previous | View Threaded


G.Milazzo at sinergy

Jan 12, 2010, 6:27 AM

Post #1 of 2 (1284 views)
Permalink
6030A - 6040A HEAD SWAP. SOME DOUBTS

Hi all,

I'm going to do a swap of a 6030 cluster appliances with a 6040 ones. I've some doubt regarding LUN id and serials and disk ownership (6000 series perform the software ownership I know).

For which concern the LUNs both systems host a series of FC LUNs (Windows, VMware) and I remember (maybe wrong) that could be some issues on LUN serials changes and so on...is this correct?

The big concern regards the disk ownership. Times ago I've replaced a fault 3140 head on a cluster and once restarted I have had to reassign all the ownership to the disk yet pointing to the old sysid/name. I'm concerned that changing the head from 6030 to the new 6040 the disk ownership remain to the old 6030 and system will not start (missing mailbox disk and so on)...

There are some step to perform to be sure of successful hw upgrade?

Last: do you suggest me to upgrade to 7.3.2 (now is 7.2.x) before OR after the hw upgrade?

Thank you in advance


romeotheriault at gmail

Jan 12, 2010, 9:07 AM

Post #2 of 2 (1214 views)
Permalink
Re: 6030A - 6040A HEAD SWAP. SOME DOUBTS [In reply to]

Hi Milazzo, I have performed a similiar upgrade from a 3050 cluster to a
3170 cluster. There are a lot more details to the upgrade than I've listed
below but these are some big points that you'll need to cover.

1. Yes, the lun serials will change and you'll need to revert them back to
the originals before you try to reconnect you clients. There are two scripts
that I know of on the netapp communities page that help automate this.
One for windows (vbs): http://communities.netapp.com/docs/DOC-1754
One for unix (or win too I guess, perl. I wrote this one):
http://communities.netapp.com/docs/DOC-2369

2. You'll need to update your /etc/rc file ahead of time to deal with any
network card name changes that may occur.

3. Yes, you'll need to reassign the disks to the new head. You do this in
maintenance mode and with the "disk reassign" command.

4. You'll need to clear out the old mailboxes in maint mode also.
mailbox destroy local
mailbox destroy partner

5. You'll also want to make sure that your iscsi and fcp target nodenames
are the same after the upgrade. You can do this with the "iscsi nodename"
and "fcp nodename" commands.

6. You'll also want to make sure that the hardware model you are upgrading
to uses the same version of OnTap that you are running on your current head,
otherwise you'll need to upgrade that too.

If you'd like email me privately and I can get you a copy of my upgrade
guide I used for my own upgrade.

Romeo

Netapp toasters RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.