Forum Discussion
jessica_2018_36
Nimbostratus
NimbostratusNew LACP on VCMP enabled f5 pair
Hello All
I have got pair of F5 (connecting to 2 HP switches - Note the F5 dont connect to each other directly ( F51>>>2HP-SW<<<
Currently the trunk port has 4 gig links and i am planning to take them down/disable and move to the 2 of the 10 gig ports and create new trunk(lacp)
Below is my plan, login to the vcmp host (SECONDARY) and then
1) Delete the old Trunk and disable the 4 gig ports
2) Create new Trunk and add the 2 available 10gig interfaces and then go to each of the VLAN (there are about 30 vlans) and assign the new trunk created.
Because the upstream HP SWs are already 10gig ports , I just need to change the speed from 1gb to 10gb and once the LACP is up , hopefully both the F5 should see each other.
Once its done, i would like to move to the Primary VCMP host and Force it to Standby and do the above steps.
Hope this is OK? Do I have to do anything else or am I missing anything else, do i have to change anything on the guest because I am changing to different ports and moving vlans to the new trunk (10gb LACP)?
KR Jessica
I can't comment on the HP side of it as I haven't worked with any of the HP switches in years, but I would create the new LACP trunk side by side the old one, then move over the VLANs to the new trunk. If you don't, you'll need to disassociate the VLANs from the current 1Gb links, delete the 4x1Gb trunk, then go back in and associate them with the new 10Gb trunk. If things go awry, your backout is a bit tougher too.
If you were switching from access to trunk ports, you'd have another hoop to jump through, but this should be pretty simple.
You shouldn't have any issues with the guests. In their eyes it's like they uplink for the switch they're on is unplugged for a few minutes. They're just bridged to the interfaces. Basically they'll have no connection while you migrate them (whichever way you choose) but once they're reconnected on the host, they won't care what they're connected to on the host. You can do all sorts of things with the guest's vlans, rename them, etc. As long as the tag in the host matches the guest, you should be OK.
Either way you choose to do it, put together the tmsh commands so you can just copy/paste it into the CLI and make sure to do a save sys config at the end. It's a bit of extra prep work, but a lot better than clicking through 30 VLANs to move them around.
i.e.
create net trunk my10gbTrunk { lacp enabled lacp-mode active interfaces replace-all-with { 2.1 2.2 } } tmsh modify net vlan vlan28 { interfaces replace-all-with { my10gbTrunk } } tmsh modify net vlan vlan29 { interfaces replace-all-with { my10gbTrunk } } tmsh save sys configand backout of
tmsh modify net vlan vlan28 { interfaces replace-all-with { my4x1gbTrunk } } tmsh modify net vlan vlan29 { interfaces replace-all-with { my4x1gbTrunk } } tmsh save sys configGood luck!
Dave_McCauley_3Cirrostratus
I can't comment on the HP side of it as I haven't worked with any of the HP switches in years, but I would create the new LACP trunk side by side the old one, then move over the VLANs to the new trunk. If you don't, you'll need to disassociate the VLANs from the current 1Gb links, delete the 4x1Gb trunk, then go back in and associate them with the new 10Gb trunk. If things go awry, your backout is a bit tougher too.
If you were switching from access to trunk ports, you'd have another hoop to jump through, but this should be pretty simple.
You shouldn't have any issues with the guests. In their eyes it's like they uplink for the switch they're on is unplugged for a few minutes. They're just bridged to the interfaces. Basically they'll have no connection while you migrate them (whichever way you choose) but once they're reconnected on the host, they won't care what they're connected to on the host. You can do all sorts of things with the guest's vlans, rename them, etc. As long as the tag in the host matches the guest, you should be OK.
Either way you choose to do it, put together the tmsh commands so you can just copy/paste it into the CLI and make sure to do a save sys config at the end. It's a bit of extra prep work, but a lot better than clicking through 30 VLANs to move them around.
i.e.
create net trunk my10gbTrunk { lacp enabled lacp-mode active interfaces replace-all-with { 2.1 2.2 } } tmsh modify net vlan vlan28 { interfaces replace-all-with { my10gbTrunk } } tmsh modify net vlan vlan29 { interfaces replace-all-with { my10gbTrunk } } tmsh save sys configand backout of
tmsh modify net vlan vlan28 { interfaces replace-all-with { my4x1gbTrunk } } tmsh modify net vlan vlan29 { interfaces replace-all-with { my4x1gbTrunk } } tmsh save sys configGood luck!
jessica_2018_36Thanks Dave for your detailed answer :) I will go with your plan and let you know how it goes
- jessica_2018_36
Hi Dave,
Can I ask you one more question, if I were to move to different ports on the HP switch with new trunks/LACP, can I keep the vlan on F5 to be associated with old and the new trunk.
Example VLAN 28 - my10gbTrunk VLAN 28 - my4x1gbTrunk
vlan28 to be associated with my4x1gbTrunk and my10gbTrunk, this is to avoid any loss of management to the box (if I disassociate from old trunk and associate all the VLANs to the new trunk).
KR Jessica