Installing AVR

I can't speak specifically about adding AVR so maybe someone else can be more specific, but I've never had one not reboot when changing modules in resource provisioning.

Don't you have a failover cluster?

One thing to be aware of is that AVR isn't something that needs to be installed, all the necessary software is already there. Provisioning a module will simply start/restart appropriate daemons. And restarting deamons will have an impact, Virtual Servers will not be reachable for a few seconds. As Renato suggests, do it on the standby unit and do a failover when and then do the other.

Hi

We did provisioning of AVR last week first on 5200v pair with test and production vCMP guests. First on the test vCMP unit pair to see how it goes and to see the impact and after it on the production vCMP units. Provisioning was AVR "Nominal".

AVR provisioning was done first on an active test unit in an active-standby vCMP pair. The provisioning did an automatic failover to standby, then restarted tmm and probably some other daemons. Took about a minute or less on 5200 vCMP guest and no hiccups at all. Repeated it on the other vCMP test unit.

Being satisfied with the test units, we did the provisioning on the production units, this time first on the standby vCMP guest. After provisioning we forced a failover to get the other vCMP guest standby for provisioning. Finally forced the initial active unit back to active state. No problems at all.

Total elapsed time was less than 10 minutes for the two pairs and production impact was two failovers. So connections with no mirroring were impacted. Of course this was done in a planned maintenance window.

--thi

Thank you for the responses. They helped out with my planning on how much of an outage window I will need.

When making changes to resource provisioning, we don't need to go through the dossier/license process again? I just want to make sure that is really only related to code base upgrades.