VCMP Terminology question
Hi all, Just trying to get a better understanding of VCMP resource allocation (specifically memory) but could someone confirm the following please? In the following F5 article -vcmp-for-viprion-systems-administration-14-0-0 - I keep coming across sentences that seem to use 'slot' and 'blade' seemingly at random and I think that 'slot' means the same as 'blade' and that one can be swapped with the other without any change in the meaning. The following picture from further down the same article (under heading 'Example of blade removal and memory use') would suggest that this is the case but just wondering if I am missing some subtle distinction between the two. Furthermore regarding the above - it says 'Guest - 4GB memory allocation' but based on the 2GB per vCPU figures and the memory use numbers I think this means 4GB of memory allocated per slot\blade so in total there is 16GB allocated? That would make sense to me but again it isn't 100% clear at the minute. Also can someone clarify the second part of the sentence as follows: 'You should specify enough cores to satisfy the combined memory requirements of all BIG-IP modules that you provision within the guest. When you deploy the guest, the host allocates this number of cores to every slot on which the guest runs, regardless of the number of slots you have assigned to the guest.' Is this related to the maximum and minimum number of slots allocated values? That is the only thing I can possibly tie into the above that makes any sort of sense. Any clarification on the above would be much appreciated.
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?
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?
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.
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?
