Have aVCS. reading the AX_Series_2_6_1-GR1_RelNote-120311.pdf
Page 119.
Step 1 - Backup - check
Step 2 - Copy off the ax device - check
Step 3 - disable VCS on the blade (NOT the master) - check
Step 4 - going into one partition called "Internal" changing vrrp-a vrid default to priority 150 (the other ones has 100) - check
VRRP-A fails over to the vBLADE - FAIL!
--------------vBlade-----------
vrid default
Unit State Priority
2 (Local) Standby 150 \*
1 (Peer) Active 100
and
sh vrrp-a config
vrrp-a device-id 2
vrrp-a set-id 1
vrrp-a enable
vrrp-a vrid default
preempt-mode disable
tracking-options
interface ethernet 3 priority-cost 15
vlan 10 timeout 10 priority-cost 15
---------------
------vMaster------
vrid default
Unit State Priority
1 (Local) Active 100
2 (Peer) Standby 150 \*
vrid that is running: default
and
sh vrrp-a config
vrrp-a device-id 1
vrrp-a set-id 1
vrrp-a enable
vrrp-a vrid default
priority 100
preempt-mode disable
tracking-options
interface ethernet 3 priority-cost 15
vlan 10 timeout 10 priority-cost 15
-----------
Suggestions ?! - force failover?!?!?
/Christian
OK.
Did on the vMaster:
vrrp-a force-self-standby vrid default device 1
It did fail over :)
Moving on to the shared partition now...
/C
OK...
BIG misstake..
The internal one just worked.. Missed one ping..
The shared one - just went down and our VIPs was more or less dead…
So I did NO vrrp-a forced backup thinggy.... and still the vBlade was master....
did vrrp-a force-standby all partitions on vBlade and our sites are back online...
Phew… Scary!!!
Plan B anyone?
Day 2…
Went at this from an different perspective than the readme files… Went MUCH BETTER…
This is how I did with success.. aVCS and VRRP-A configuration ( two physical AX boxes)..
Step 1 – Backup – check
Step 2 – Copy off the ax device – check
Step 3 – disable VCS on the blade (NOT the master) – check
Step 4- - on vMASTER go to config mode and enter: vrrp force-self-standby all-partitions device [insert the local device ID] (Mine is device 1)
Step 5 - verify on vBLADE that vrrp is has moved to the vBlade and device 2. Also verify that all services are working… 
Step 6 - enter configuration mode on vBlade and device 2. Change all vrrp priorities according to the readme PDF
Step 7 - Upgrade the vMaster (device 1). if getting question to save conig- say NO!!!
Step 8 - Reboot the vMaster
( Step 8.5 - verify that you are actually running the right software )
Step 9 - Verify that vrrp still has the vBlade as Active Now, due to higher priority and not the force-self-standby on device 1
Step 10 - Repeat step 4 but now on the vBlade (ie my device 2) but since vcs is not running skip the device part of the command… Thus: vrrp force-self-standby all-partitions
Step 11 - verify that vrrp is has moved to the vMaster and device 1. Also verify that all services are working…
Step 12 - upgrade the vBlade. if getting question to save conig- say NO!!!
Step 13 - Reboot vBlade - and let the vcs do its magic..
Step 14 - Get coffe!!
/Christian