Forum Discussion
VCMP Hosts and Guests
Hi community!!
Recently I asked refered to HA betwen Guests, and Hosts, about sync... And actually due to the answer recieved I'm realizing the HA process between Guests (Active / Passive), and for Hosts (A & B) in Standalone Mode.
But now this configuration implies a little problem (or I think so), I'm defining VLANS on HOST A (trunk with 80 VLANS), and parsing to guests differents groups of vlans (20 VLANS to each guest), the problem i'm facing off is the need to recreate all the vlans in the other HOST again (to parse to STANDBY GUESTS), is this the correct way to proceed or I'm confused about this process?
Isn't better stablish a ACTIVE/ACTIVE relationship between HOST to solve this issue?
If finally I have to create the vlans again I will use CLI of course.
Thanks in advance!
Hi,
You have to create the vlans again. But as long as you already configured those vlans on the first host, you can copy the vlan config in bigip_base.conf file from the first host and paste this configuration to the second host on the same file.
You should copy all vlan information like below :
net vlan /Common/vlan_external { interfaces { 1.2 { } } tag 4093 }
Once copied to the second host, you save the bigip_base.conf file and execute a
to apply your changes.tmsh load sys config
bigip_base.conf is located under /config
- Yann_Desmarest_
Nacreous
Hi,
You have to create the vlans again. But as long as you already configured those vlans on the first host, you can copy the vlan config in bigip_base.conf file from the first host and paste this configuration to the second host on the same file.
You should copy all vlan information like below :
net vlan /Common/vlan_external { interfaces { 1.2 { } } tag 4093 }
Once copied to the second host, you save the bigip_base.conf file and execute a
to apply your changes.tmsh load sys config
bigip_base.conf is located under /config
- nanukanu_263047
Nimbostratus
Perfect! I supose it, so, its the correct way of proceed, correct? And related with this -I only see 2 Interfaces on Guests (on Host aggregate of 4) it's correct? -I can use the same IP on ACTIVE/STANDBY vlan Interface? or its imperative play with floating IP? Thanks! - Yann_Desmarest_
Nacreous
The procedure above works for vlan replication on the host only, I already noticed that the guest is not displaying correct interfaces, speed, etc. but the important is that you have your vlans propagated on the guest. Regarding the Active/Standby, you will need to share a floating Self IP for outgoing traffic to peers (snat automap feature). You cannot assign the same physical Self IP to multiples Guests - Yann_Desmarest_
Nacreous
The procedure above works for vlan replication on the host only, I already noticed that the guest is not displaying correct interfaces, speed, etc. but the important is that you have your vlans propagated on the guest. Regarding the Active/Standby, you will need to share a floating Self IP for outgoing traffic to peers (snat automap feature). You cannot assign the same physical Self IP to multiples Guests
Hi,
You have to create the vlans again. But as long as you already configured those vlans on the first host, you can copy the vlan config in bigip_base.conf file from the first host and paste this configuration to the second host on the same file.
You should copy all vlan information like below :
net vlan /Common/vlan_external { interfaces { 1.2 { } } tag 4093 }
Once copied to the second host, you save the bigip_base.conf file and execute a
to apply your changes.tmsh load sys config
bigip_base.conf is located under /config
- nanukanu_263047
Nimbostratus
Perfect! I supose it, so, its the correct way of proceed, correct? And related with this -I only see 2 Interfaces on Guests (on Host aggregate of 4) it's correct? -I can use the same IP on ACTIVE/STANDBY vlan Interface? or its imperative play with floating IP? Thanks! - The procedure above works for vlan replication on the host only, I already noticed that the guest is not displaying correct interfaces, speed, etc. but the important is that you have your vlans propagated on the guest. Regarding the Active/Standby, you will need to share a floating Self IP for outgoing traffic to peers (snat automap feature). You cannot assign the same physical Self IP to multiples Guests
- The procedure above works for vlan replication on the host only, I already noticed that the guest is not displaying correct interfaces, speed, etc. but the important is that you have your vlans propagated on the guest. Regarding the Active/Standby, you will need to share a floating Self IP for outgoing traffic to peers (snat automap feature). You cannot assign the same physical Self IP to multiples Guests
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com