How to increase cores on F5 Viprion guests:

Pre-Activity-Analysis:

Verify a support Contract with the vendor and open proactive vendor ticket for the activity. Run the following commands and collect the details:

tmsh show /sys version
tmsh show /sys hardware
tmsh show /sys license
tmsh show /sys software
Interface/VLAN status,
Routes
netstat -nr
tmsh show /net route
tmsh list /sys management-route
tmsh show net interface
Take a UCS file backup :# cd /var/local/ucs
#tmsh save /sys ucs <Device-name_date>.ucs
Go to Local Traffic›› Network Map >> Show Map and take the output of virtual servers, pool etc.. status.

Implementation Plan:

1. Move Guests to Configured Mode

Go to vCMP ›› Guest List ›› Device-v02›› Requested State ›› Configured ›› Update

2. Allocate Cores

Go to vCMP ›› Guest List ›› Device-v02›› Cores Per Slot ›› 4 ›› Update

Ensure to be connected on the device console and monitor for any logs.

3. Ensure Guest is in Deployed Mode

Bring guest device to deploy state using below.

Go to vCMP ›› Guest List ›› < Guest > ›› Device-v02›› Deployed ›› Update.

4. Make sure that all VSs are up

5. Failover the traffic from Device-v01 to Device-v02 by running below command on Device-v01

 tmsh run /sys failover standby

6. Move Guests to Configured Mode

Go to vCMP ›› Guest List ›› Device-v01 ›› Requested State ›› Configured ›› Update

3. Allocate Cores

Go to vCMP ›› Guest List ›› Device-v01 ›› Cores Per Slot ›› 4 ›› Update

Ensure to be connected on the device console and monitor for any logs.

7. Ensure Guest is in Deployed Mode

Go to vCMP ›› Guest List ›› Device-v01 ›› Requested State ›› Deployed ›› Update.

8. Make sure that all virtual servers are up and then Fail over back to Device-v01

Fail over the traffic from Device-v02 to Device-v01 by running the below command on Device-v02

 tmsh run /sys failover standby

Post Activity Test Plan:

Verify the management connectivity like ping, snmp, SSH towards active and standby devices
Login to each device CLI and ensure the interface are marked up (Validate with pre-change stat) and routes/VLAN configs are present
Verify the status of virtual server and pool member. Ensure the up/down/not-monitored counts are as per the pre-change stat
Verify the ltm file in /var/log and ensure no abnormal errors are logged
Check the CPU & Memory usage and ensure they are normal
Go to Local Traffic›› Network Map >> Show Map and compare the output with the “Pre_change_Status” image

Published by Raghavendra Seshumurthy