SUMMARY - A1000 Firmware Upgrade
2007-12-24 19:24:00
responses are listed below:
In my situation the boot disks were not mounted on the A1000 so I did not
have to deal with that potential problem.
We are also running Veritas FirstWatch which introduced some additional
considerations.
The first response listed below formed the general game plan.
The steps followed were:
Stop all processes accessing disks. Run "fuser" to verify all processes are
stopped.
Un-mount file systems.
Using vxdiskadm, "deport" drive groups - option 9 from menu interface.
You will be prompted to offline the disks at the same time. Answer yes
to offline the disks.
If there are any installed disks that were not part of a disk group,
use option 11, to offline these disks as well.
Upgrade Firmware using Raid Manager GUI
Using vxdiskadm, "online" each disk. - option 10 from menu interface.
Using vxdiskadm, "import" each diskgroup. option 8 from menu interface.
NOTE: With FirstWatch diskgroups should be imported with a "-t" flag.
It may not be possible to set this flag when using vxdiskadm.
Use: vxdg -t import <disk_group>
instead
Start up each disk group.
vxvol -g <disk_group> startall
If new drive were added, they can be exposed to veritas without having to
reboot by using the command,
vxdctl enable (untested, dervived from newsgroup postings after the
fact)
-----Original Message-----
From: David Price [mailto:dprice at plugnpay.com]
Sent: 6 February 2001 14:34
To: codeprof at codeprof.com
Subject: A1000 Firmware Upgrade
After upgrading from Raid Manager 6.11 to 6.22 I am attempting to upgrade
the firmware of the A1000 controllers.
RM is not letting me do so as it reports that the drives are still receiving
IO and will therefore not permit an upgrade.
I have unmounted the drives, which I thought would be enough to prevent IO.
The systems is a 3500 running 2.6
It is also running Veritas Firstwatch & Veritas Volume Manager.
On my last attempt I did nothing with Volume Manager and that may be the
problem.
Any other suggestions would be appreciated.
Dave Price
***************************
Deport disk groups where LUNs are located.
run vxdiskadm and select option 11 for each LUN in the disk group
do firmware upgrade as documented.
run vxdiskadm and select option 10 for each LUN
import disk group
start vols manually using "vxvol -g <disk_group> startall"
*******
Some maintenance operations (such as updating firmware on A3500's)
require halting Veritas (simply idling file systems does not idle a
Veritas disk since File Manager puts stuff on every disk which it keeps
active).
Exporting and subsequently importing file systems works for non-rootdg
stuff, but if rootdg is involved, you must halt and subsequently restart
Veritas.
NOTE: if root stuff is mirrored, you should break the mirror before
starting this.
0) Edit vfstab so that / is mounting only the raw device. Most likely
you can use /etc/vfstab.prevm. But you need to make sure that this
mounts the correct disk and slice as root.
1) Comment out all entries with vx in them in /etc/system:
* vxvm_START (do not remove)
*forceload: drv/vxdmp
*forceload: drv/vxio
*forceload: drv/vxspec
*rootdev:/pseudo/vxio at 0:0
*set vxio:vol_rootdev_is_volume=1
* vxvm_END (do not remove)
2) #touch /etc/vx/reconfig.d/state.d/install-db
This prevents veritas from starting when rebooted.
3) #reboot
4) Do maintainence.
5) rm /etc/vx/reconfig.d/state.d/install-db
6) Uncomment entries in /etc/system
7) Put back correct /etc/vfstab, the one that uses veritas.
8) #reboot
******
Veritas may be talking to them.
If your A1000 is a complete disk group, then deport the DG, upgrade,
then import the DG again.
*****
If your controllers are setup active /active you will have to change them
and upgrade each separately
Comments
Got something to say?
You must be logged in to post a comment.
