You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2022/08/10 09:36:24 UTC

[GitHub] [cloudstack] xuanyuanaosheng opened a new issue, #6624: The Cloudstack Multi VLAN, But one of the Virtual Routers can not work

xuanyuanaosheng opened a new issue, #6624:
URL: https://github.com/apache/cloudstack/issues/6624

   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   
   ##### CLOUDSTACK VERSION
   1.  CloudStack:4.15.2.0
   2.  ceph version:15.2.16
   3.  cloudstack agent os version: Oracle Linux Server 8.3
   
   
   The cloudstack env is **using the Ceph RBD and  local storage as cloudstack cluster primary storage.**
   
   
   The cloudstack cluster TEST work node is  eno49 and eno50 to bond0.
   ```
    - bond0  --->  bond0.1935 ---> cloudbr0
    
   
   
                            -------> VLAN 1115
    - bond0  ---> cloudbr1 -
                            -------> VLAN 1118
    
   ```
   
   The details config:
   
   1.  ifcfg-eno49
   ```
   TYPE=Ethernet
   BOOTPROTO=none
   NAME=bond0-slave
   MASTER=bond0
   SLAVE=yes
   DEVICE=eno49
   ONBOOT=yes
   HOTPLUG=no
   DELAY=0
   STP=no
   ```
   
   2. ifcfg-eno50
   ```
   TYPE=Ethernet
   BOOTPROTO=none
   NAME=bond0-slave
   MASTER=bond0
   SLAVE=yes
   DEVICE=eno50
   ONBOOT=yes
   ```
   
   3. ifcfg-bond0
   ```
   DEVICE=bond0
   NAME=bond0
   TYPE=Bond
   BONDING_MASTER=yes
   ONBOOT=yes
   HOTPLUG=no
   BOOTPROTO=none
   BRIDGE=cloudbr1
   BONDING_OPTS="mode=1 miimon=100"
   ```
   
   4. ifcfg-bond.1935
   ```
   DEVICE=bond0.1935
   NAME=bond0.1935
   ONBOOT=yes
   HOTPLUG=no
   BOOTPROTO=none
   VLAN=yes
   BRIDGE=cloudbr0
   ```
   
   5.  ifcfg-cloudbr0
   ```
   DEVICE=cloudbr0
   NAME=cloudbr0
   TYPE=Bridge
   BOOTPROTO=none
   ONBOOT=yes
   IPV6INIT=no
   IPV6_AUTOCONF=no
   IPADDR=10.26.246.11
   GATEWAY=10.26.246.254
   NETMASK=255.255.255.0
   DELAY=5
   STP=yes
   ```
   
   6.  ifcfg-cloudbr1
   ```
   DEVICE=cloudbr1
   NAME=cloudbr1
   TYPE=Bridge
   ONBOOT=yes
   BOOTPROTO=none
   IPV6INIT=no
   IPV6_AUTOCONF=no
   DELAY=5
   STP=yes
   ```
   
   The network command:
   ```
   # nmcli d
   DEVICE        TYPE      STATE                   CONNECTION   
   cloudbr0      bridge    connected               cloudbr0     
   cloud0        bridge    connected (externally)  cloud0       
   brbond0-1115  bridge    connected (externally)  brbond0-1115 
   brbond0-1118  bridge    connected (externally)  brbond0-1118 
   cloudbr1      bridge    connected               cloudbr1     
   bond0         bond      connected               bond0        
   eno49         ethernet  connected               bond0-slave  
   eno50         ethernet  connected               bond0-slave  
   vnet0         tun       connected (externally)  vnet0        
   vnet10        tun       connected (externally)  vnet10       
   vnet11        tun       connected (externally)  vnet11       
   vnet12        tun       connected (externally)  vnet12       
   vnet16        tun       connected (externally)  vnet16       
   vnet17        tun       connected (externally)  vnet17       
   vnet18        tun       connected (externally)  vnet18       
   vnet2         tun       connected (externally)  vnet2        
   vnet21        tun       connected (externally)  vnet21       
   vnet22        tun       connected (externally)  vnet22       
   vnet23        tun       connected (externally)  vnet23       
   vnet4         tun       connected (externally)  vnet4        
   bond0.1115    vlan      connected (externally)  bond0.1115   
   bond0.1118    vlan      connected (externally)  bond0.1118   
   bond0.1935    vlan      connected               bond0.1935   
   lo            loopback  unmanaged               --   
   
   
   # nmcli c
   NAME          UUID                                  TYPE      DEVICE       
   cloudbr0      d4b789ba-7321-548d-dabd-5c4150da0266  bridge    cloudbr0     
   cloud0        4d28dc6a-dcd4-456d-b6d7-65907a6b2963  bridge    cloud0       
   brbond0-1115  ee9a06a6-c856-478a-9d68-ff7125c45ae6  bridge    brbond0-1115 
   brbond0-1118  d8548bd2-9a02-4f5d-9f19-669e7b46e483  bridge    brbond0-1118 
   cloudbr1      6df8d4a7-7ee1-528a-dcf9-20d35734f675  bridge    cloudbr1     
   bond0         ad33d8b0-1f7b-cab9-9447-ba07f855b143  bond      bond0        
   bond0.1115    58e5fbc3-3571-4c3b-a82f-6e8722fb9b46  vlan      bond0.1115   
   bond0.1118    614180b3-92e1-46e3-8693-e74289807831  vlan      bond0.1118   
   bond0.1935    79f54c00-8b72-f4d7-9ae6-74ea2b65af0a  vlan      bond0.1935   
   bond0-slave   31fc52de-447b-46f6-33cf-1d4dbbcddef5  ethernet  eno49        
   bond0-slave   12e7087a-5ced-5405-d350-7726d3570bae  ethernet  eno50        
   vnet0         3b8c138f-a27d-4aee-b6c6-b80e307e652d  tun       vnet0        
   vnet10        631f7272-a06c-4521-b03e-f4b13643ac3c  tun       vnet10       
   vnet11        c0e6aebd-53d3-4214-a6ed-12c224136ba5  tun       vnet11       
   vnet12        061633df-d815-4b91-9373-1098c231e4ec  tun       vnet12       
   vnet16        aeee6eba-0da0-49e0-a10d-39a15f0a5d70  tun       vnet16       
   vnet17        13a77f1c-3235-414d-90c9-3be38aadbbfb  tun       vnet17       
   vnet18        245fafbc-f80e-46dd-8c92-30daac5989de  tun       vnet18       
   vnet2         832d0870-7325-487a-b2c8-10420bddec92  tun       vnet2        
   vnet21        169f8145-7d96-4e38-afcc-6b4398b11513  tun       vnet21       
   vnet22        26b7676b-ec89-4d18-b944-39d4d7ba9244  tun       vnet22       
   vnet23        5ee8c080-21b2-4894-8d08-034609ddcb4b  tun       vnet23       
   vnet4         d4108da5-276e-4b37-82d4-ef7411b5d893  tun       vnet4
   ```
   
   The work node (10.26.246.11) can ping gateway: 10.26.18.254 ( VLAN 1118 ) and 10.26.15.254 ( VLAN 1115 ).
   
   For system vm (VLAN 1115 and VLAN 1118 ) can ping gateway: 10.26.18.254 ( VLAN 1118 ) and 10.26.15.254 ( VLAN 1115 ).
   
   For Virtual route (VLAN 1115) can ping gateway: 10.26.18.254 ( VLAN 1118 ) and 10.26.15.254 ( VLAN 1115 )
   
   But,  For Virtual route (VLAN 1118) can not  ping gateway: 10.26.18.254 ( VLAN 1118 ) and 10.26.15.254 ( VLAN 1115 ). The VLAN 1115 works fine, But the VLAN 1118 can not work.  Could you please give some advices?
   
   ![image](https://user-images.githubusercontent.com/4197714/183866381-984211c1-e9fa-45df-9d01-fbdd8170439d.png)
   
   


-- 
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: commits-unsubscribe@cloudstack.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [cloudstack] xuanyuanaosheng closed issue #6624: The Cloudstack Multi VLAN, But one of the Virtual Routers can not work

Posted by GitBox <gi...@apache.org>.
xuanyuanaosheng closed issue #6624: The Cloudstack Multi VLAN, But one of the Virtual Routers can not work
URL: https://github.com/apache/cloudstack/issues/6624


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [cloudstack] xuanyuanaosheng commented on issue #6624: The Cloudstack Multi VLAN, But one of the Virtual Routers can not work

Posted by GitBox <gi...@apache.org>.
xuanyuanaosheng commented on issue #6624:
URL: https://github.com/apache/cloudstack/issues/6624#issuecomment-1229722471

   I reinstall it,it works fine.  I will close this issue.


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org