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

   > @weizhouapache I recreate a new vpc : test and add tier: 10.28.29.0/24. 
The redundant router are r-30932-VM and r-30933-VM. The r-30932-VM eth2 
IP:10.28.29.42 ,the r-30933-VM eth2 IP:10.28.29.229 The two virtual routers can 
ping each other using eth2, But a few minitues the two virtual routers can not 
ping each other using eth2.
   > 
   > 
![image](https://user-images.githubusercontent.com/4197714/260650532-ea927a3d-f0a0-467b-9dcc-221930c7e050.png)
   > 
   > and the r-30932-VM IP become
   > 
   > ```
   > 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
   >     link/ether 02:00:0f:b9:00:02 brd ff:ff:ff:ff:ff:ff
   >     altname enp0s9
   >     altname ens9
   >     inet 10.28.29.42/24 brd 10.28.29.255 scope global eth2
   >        valid_lft forever preferred_lft forever
   >     inet 10.28.29.254/24 brd 10.28.29.255 scope global secondary eth2
   >        valid_lft forever preferred_lft forever
   > ```
   > 
   > and the r-30933-VM IP become
   > 
   > ```
   > 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
   >     link/ether 02:00:1c:39:00:03 brd ff:ff:ff:ff:ff:ff
   >     altname enp0s9
   >     altname ens9
   >     inet 10.28.29.229/24 brd 10.28.29.255 scope global eth2
   >        valid_lft forever preferred_lft forever
   >     inet 10.28.29.254/24 brd 10.28.29.255 scope global secondary eth2
   >        valid_lft forever preferred_lft forever
   > ```
   > 
   > could you please give some advices?
   
   @xuanyuanaosheng 
   it seems both VRs become PRIMARY, right ?
   If you migrate the VRs to same host, everything will work as expected.
   
   I have experienced a similar issue before, which was caused by mlag settings 
on upstream routers.
   how many routers do you use ?
   


-- 
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