Steps to upgrade a vCMP host.
According to this article, the steps to upgrade a vCMP host are: Re-activate the host license. Shutdown the guests one at a time by setting the requested state to Configured. Proceed with the upgrade. Is this correct? I've also read (and been told) that you should set the guests to Provision before upgrading. So is it Configured or Provision?
Renaming VLANs on a Viprion chassis and vCMP Guests
I'm in the unenviable position of having to rename a dozen+ VLANs on a Vipreon chassis and vCMP guests. The reason stems from having to combine guests from 2 pairs of chassis where one pair is being decommissioned. Unfortunately the original admin who set up the chassis did not use the same VLAN naming convention for both sets of chassis, and the same VLAN tags exist in both places. This results in guests that are brought over from the old chassis not being able to access the network as the VLAN names do not match up. The destination is 2 chassis where the LTMs are in an active-standby pair with the members of the pair being split between the 2 chassis. (Same situation on the chassis I'm migrating from.) Can I get a sanity check on what I'd like to do here? Force the guests offline on the secondary chassis. Shut down the guests. Rename the VLANs on the Vipreon by editing bigip.conf and bigip_base.conf load sys config verify load sys config (or just reboot the chassis to be thorough) Bring up one guest offline, repeat the same procedure on the guest. Failover during a maintenance window and test. Repeat for other guests. If everything works there, repeat the same procedure on the primary chassis. Resync the configs once all changes are made and tested. At this point the guests that are migrated over should be able to access the newly renamed VLANs as well. Am I missing anything here?Sharing same VLAN between vCMP guest
Hello, This question is regarding to sharing same VLAN between vCMP guest for F5 viprion platform. lets say, I have a VLAN 10 which is tagged to interface 1.1 at vCMP host level and propagated to Guest A in common partition. -For the guest B can I use same VLAN? -What would be the recommend way to share VLANs between guests? -Can we tag VLAN 10 to 1.2 interface at vCMP host level and share it with Guest B?
Moving vCMP guests to newer blade - upgrade resources at same time?
Hi all - I'm working on replacing my old B2100 blades with new B2150 blades. I'm running vCMP with the LTM guests at v12.1.2. Some of these guests have been challenged resource-wise and, since the 2150s have twice the CPU/RAM as the 2100s, I want to add resources to them. I'm planning on using the method here: https://support.f5.com/csp/article/K63705154 (Migrating a BIG-IP configuration to new Viprion blades using ConfigSync) and have a spare chassis where I have built the target host cluster. So the big question is, can I go from, say, two CPUs in an existing guest to four CPUs in the target guest? I don't see anything referring to the CPU/RAM resources in the document, but may have missed something in my first reading. Has anyone done this? I will need to add resources to them eventually and thought this might be a good opportunity to kill two birds with one stone. The first upgrade will be to the standby systems - with the active systems held as-is in reserve in case any issues pop up in production with the new configuration. I appreciate any feedback.
Device Service Clustering (vCMP guests not failing over when physical vCMP host interface fails)
Hello, Today we have the following physical setup for two 5250v F5s that we are using as vCMP host for 5 vCMP guests in each of them. These vCMP guest are configured in an HA pair using Device Service Clustering with load aware. They are homogeneous. Last week we had failover tests in the Data Center and brought down manually the physical interfaces from the switch side that are members of Port-Channel107 shown in the picture and the fail-over did not occur. While in the vCMP host we noticed the the port status changed to down in the physical interface, this was not passed over to the vCMP guests and that is what I am assuming was the cause of the failing over not happening. We did see all the VIPs, Nodes, Pools going down on the active unit but the failover was not triggered and cause all the applications to fail. Questions: -Is the expected behavior not to pass the status of the physical interfaces in the vCMP host to the vCMP guests? -Is there something that I am missing in my current configuration that is causing these vCMP guests not to fail-over when the physical interfaces in the vCMP host fail? -Do I need to use HA groups to monitor the trunks instead of load aware for the fail-over to be triggered?
