following is my procedure for adding new disks in a cluster. it might be overkill, but i'd rather have that than disk kill :)

once i tried to do the disk_fw_upgrade and had the partner take over halfway through the disk_fw_upgrade. it wasn't pretty.

btw, i have heard that in in 6.X disk_fw_upgrade is going to be automagic by the filers.

---cut--here---8<--------8<---cut--here---8<--------8<---cut--here---8<-------

attaching a new shelf to clustered filers A and B ------------------------------------------------- get disk setup and physically installed

have B takeover A

attach cable to A loop of A

have B giveback A

have A takeover B

attach cable to B loop of B

if any downrev disks, do a disk_firmware_upgrade

have A giveback B

firmware update only -------------------- on A, takeover B

on A, do the disk_firmware_update

on A, giveback B

---cut--here---8<--------8<---cut--here---8<--------8<---cut--here---8<-------

-- email: lance_bailey@pmc-sierra.com box: Lance R. Bailey, unix Administrator vox: +1 604 415 6646 PMC-Sierra, Inc fax: +1 604 415 6151 105-8555 Baxter Place http://www.lydia.org/~zaphod Burnaby BC, V5A 4V7 Did you hear about the new corduroy pillows? They're making headlines - Binkley

Hi,

...

I have a 840 cluster. Whenever I add new disks, the cluster starts throwing 'doenrev disk firmware' error messages. NetApps suggests doing a disk_fw_update on the disk and strictly says "NO need to Halt a filer'. Reality is totally different. The command specifically asks you wether the cluster partner is on Halt-OK prompt or not?

The workaround I am doing, intitiate a takeover and do the disk_fw_update. However, this still needs to do a takeover/giveback and 2 minutes of downtime...Adding/replacing bad disks is a regular activity...

Any suggestions..?

Can't you just 'cf disable' on each Filer whilst you upgrade the firmware?

-- Regards,

Jay Tribick Senior Systems Engineer Carrier1 Voice: +44 207 531 3874 Mobile: +44 7801 526 638