weizhouapache commented on issue #7364:
URL: https://github.com/apache/cloudstack/issues/7364#issuecomment-1484768562

   > @weizhouapache
   > 
   > Thank you for the response. My apologies for my late response.
   > 
   > Currently the system running the management server and the first host is 
connected to the switch via two ethernet interfaces `A (10.4.1.1/16)` and `B 
(10.6.1.1/16)`. **Note**: Both interface A and interface B is connected to an 
untagged port on the switch (we are using 802.1q VLAN on the switch and it only 
has options for tagged and untagged ports). The ethernet interface A is used 
for creating `cloudbr0` and the ethernet interface B is being used to created 
`cloudbr1`. `cloudbr0` is being used by the Management Network which is using 
isolation of type VLAN `cloudbr1` is being used by the Guest and Public Network 
whose isolation type is what we are discussing about.
   > 
   > Provided the scenario, correct me if I am wrong, based on my understanding 
if I used VLAN as my isolation type for the Public and Guest, I am assuming, I 
will need to connect `ethernet interface B` associated to `cloudbr1` to a trunk 
or tagged port on the switch. I already tried isolation of type VLAN for the 
Public and Guest Network and had the same issue where VM on the second host 
couldn't communicate virtual router on the first host. So I am assuming 
`interface B` being connected to an untagged port on the switch was the issue.
   > 
   > However, if I use isolation type of VXLAN, which uses layer 3 UDP packets, 
`ethernet interface B` associated to `cloudbr1` can be connected to an untagged 
to access port.
   > 
   > Correct me if I am wrong, provided, my assumptions are correct, I am 
assuming VXLAN is more likely to work with the existing switch configuration 
(`interface A` and `interface B` being connected to untagged switch ports)
   > 
   > Additionally, I am wondering, is there any additional configuration I have 
to do the system running the management server and the host or install any 
additional software on it. As I did try isolation type of VXLAN for the Public 
and the Guest Network with VLAN isolation type for the Management Network. It 
seemed like, I was having internet connectivity issues on the VMs (regardless 
of the host they are on). I tried installing Ubuntu 20.04 server, however, the 
process for fetching updates from the server and downloading was very slow and 
would eventually crash. I am really confused as to why I was getting such 
behavior. I checked, the management server log, however, I didnt notice any 
error messages.
   
   @Atiqul-Islam 
   from what I understand (maybe wrong),
   - if the isolated method is VLAN, switch port needs to be configured as 
trunk mode. otherwise, the traffic (with vlan tag) from a guest vm on a host 
cannot be sent to vms on hosts.
   - if the isolated method is VXLAN, it is not required to configure trunk 
switch port for traffic between guest vms. However, you still need to configure 
the switch port for public traffic (from guest vm or virtual router to the 
Internet). What's the vlan/vxlan tag of your public ip ranges ?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to