ONTAP Hardware

Head Swap FAS6080 to FAS6280?

henrypan1
5,158 Views

Dear NetApp Gurus,

Plan to swap head from FAS6080 to FAS6280.

Any checklist, best practice even cheat sheets to share?

Thanks in advance & looking forward to hear from you.

Good w/e

Henry

1 ACCEPTED SOLUTION

scottgelb
5,158 Views

The NOW site has a guide for both cluster and single node upgrades.

Upgrading a   FAS60xx     system in an HA pair to a  FAS62xx   system in an HA pair

http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/cs_migration/FAS6xxx/60xx_to_62xx_HA-pair/frameset.html

Upgrading a single-controller FAS60xx system to a single-controller FAS62xx system

http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/cs_migration/FAS6xxx/60xx_to_62xx_single-controller/frameset.html

I have my own templates we use for professional serives...after more head swaps than I can remember..and we don't follow the exact steps in the guides, but we have a lot of experience doing swaps and have peer review and support to check add another pair of eyes.  Make sure you boot the 6280s without disk and skip the boot (ctrl-c to break boot before special boot option)... then run "printenv" and make sure you don't have systems with the "bootarg.init" variables set  (search communities for that issue or the tsb)... if you see this issue with those init variables that only were set on some 32/6200 systems prior to being fixed in manufacturing a month or two ago, run "set-defaults" then "bye".  Pre-create a head-swap plan and open a case to run it by support as well.  Also, if you have never done one, I would engage professional services to assist. Key things are matching ONTAP (match 6080 to 6280 prior to swap, or tftp boot to 6280)... in maint mode, disk reassign, mailbox destroy local/partner, set fcp initiator/target as needed, modify /etc/rc and /etc/hosts as needed if interfaces change, map initiators and targets to ports on the 6280.  If fibre channel san, and if fcp target ports are NOT the same after swap, then make sure to modify the wwpn after swap to match what it was prior... if you use the SAME fcp target port (1c to 1c for example) then the wwpns will stay the same.. if the ports change, you can use "fcp portname set portname wwpn" or you can also swap ports...make sure you don't have duplicate portnames (the swap command makes that easier).

View solution in original post

4 REPLIES 4

scottgelb
5,159 Views

The NOW site has a guide for both cluster and single node upgrades.

Upgrading a   FAS60xx     system in an HA pair to a  FAS62xx   system in an HA pair

http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/cs_migration/FAS6xxx/60xx_to_62xx_HA-pair/frameset.html

Upgrading a single-controller FAS60xx system to a single-controller FAS62xx system

http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/cs_migration/FAS6xxx/60xx_to_62xx_single-controller/frameset.html

I have my own templates we use for professional serives...after more head swaps than I can remember..and we don't follow the exact steps in the guides, but we have a lot of experience doing swaps and have peer review and support to check add another pair of eyes.  Make sure you boot the 6280s without disk and skip the boot (ctrl-c to break boot before special boot option)... then run "printenv" and make sure you don't have systems with the "bootarg.init" variables set  (search communities for that issue or the tsb)... if you see this issue with those init variables that only were set on some 32/6200 systems prior to being fixed in manufacturing a month or two ago, run "set-defaults" then "bye".  Pre-create a head-swap plan and open a case to run it by support as well.  Also, if you have never done one, I would engage professional services to assist. Key things are matching ONTAP (match 6080 to 6280 prior to swap, or tftp boot to 6280)... in maint mode, disk reassign, mailbox destroy local/partner, set fcp initiator/target as needed, modify /etc/rc and /etc/hosts as needed if interfaces change, map initiators and targets to ports on the 6280.  If fibre channel san, and if fcp target ports are NOT the same after swap, then make sure to modify the wwpn after swap to match what it was prior... if you use the SAME fcp target port (1c to 1c for example) then the wwpns will stay the same.. if the ports change, you can use "fcp portname set portname wwpn" or you can also swap ports...make sure you don't have duplicate portnames (the swap command makes that easier).

henrypan1
5,158 Views

Salute to Scott!

radek_kubka
5,158 Views

Hi Bhola,

The documents have been moved apparently.

The easiest way to find them now, is to start at the Hardware Upgrade Procedures landing page:

http://support.netapp.com/documentation/bytype/index.html?subtypeID=61045

Regards,
Radek

Public