Thanks Peter and everyone else that replied. I will share my procedure/experience once our head-upgrade is completed.
Darish.
From: Learmonth, Peter [mailto:Peter.Learmonth@netapp.com] Sent: October-24-07 1:38 PM To: Darish Rajanayagam Subject: RE: Head upgrade 3020 to 3040
IQNs will stay the same. LUN S/Ns will change. You should keep a copy of lun show -v from before the upgrade, then set them S/N back the way they were after the swap. lun offline <lun path> lun serial <lun path> <serial number> lun online (Do this before bringing servers back up)
This is especially important for VMware in order to avoid resignaturing VMFS and having to re-register VMs.
IP addresses will stay the same. Not sure about MAC addrs, but I don't think that matters.
Peter
________________________________ From: Darish Rajanayagam [mailto:darishr@softcom.biz] Sent: Wednesday, October 24, 2007 9:41 AM To: toasters@mathworks.com Subject: Head upgrade 3020 to 3040 Greeting Toasters,
We will soon be upgrading our FAS3020 filer to a FAS3040. The two main protocols the filer is used for is NFS and ISCSI. I am concerned of the implications this upgrade will have on the iscsi network. Has anyone done this type of migration and can share their experience with me? Will upgrading the head unit impact iscsi iqns, lun serial numbers etc?
Thanks, Darish.
FYI.
Our head migration was a success. The lun serials did change and that was pretty much the only issue we ran across during the upgrade. Below is a high level overview of what was done.
1. Bring the 3020 head to the same OnTap level as the 3040 prior to upgrade, best to give it a couple of weeks of OnTap running time before doing the head upgrade
2. Label all cables that will be re-plugged, makes things easier.
3. Perform an options autosupport and create a txt document with the appropriate serial number of all LUNs.
4. Halt the old filer
5. Disconnect fibre cables and network cables and reconnect appropriately.
6. Power on 3040 and Ctrl-C to enter special boot menu.
7. Option5 to boot into maintenance mode.
8. Disk reassign to assign disks to new head unit
9. Fcstat device_map to verify
10. Destroy mailbox mailbox destroy local
11. Reboot
12. Check aggr status and vol status and ensure all data is available
13. Upgrade OnTap to q build (64bit OS).
14. Install new licenses
15. Luns come up offline, change the lun serial as per step 3.
16. Bring luns online.
17. Verify connectivity via licensed protocols etc.
/dr
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Darish Rajanayagam Sent: October-25-07 8:20 AM To: Learmonth, Peter Cc: toasters@mathworks.com Subject: RE: RE: Head upgrade 3020 to 3040
Thanks Peter and everyone else that replied. I will share my procedure/experience once our head-upgrade is completed.
Darish.
From: Learmonth, Peter [mailto:Peter.Learmonth@netapp.com] Sent: October-24-07 1:38 PM To: Darish Rajanayagam Subject: RE: Head upgrade 3020 to 3040
IQNs will stay the same. LUN S/Ns will change. You should keep a copy of lun show -v from before the upgrade, then set them S/N back the way they were after the swap. lun offline <lun path> lun serial <lun path> <serial number> lun online (Do this before bringing servers back up)
This is especially important for VMware in order to avoid resignaturing VMFS and having to re-register VMs.
IP addresses will stay the same. Not sure about MAC addrs, but I don't think that matters.
Peter
________________________________ From: Darish Rajanayagam [mailto:darishr@softcom.biz] Sent: Wednesday, October 24, 2007 9:41 AM To: toasters@mathworks.com Subject: Head upgrade 3020 to 3040 Greeting Toasters,
We will soon be upgrading our FAS3020 filer to a FAS3040. The two main protocols the filer is used for is NFS and ISCSI. I am concerned of the implications this upgrade will have on the iscsi network. Has anyone done this type of migration and can share their experience with me? Will upgrading the head unit impact iscsi iqns, lun serial numbers etc?
Thanks, Darish.