cloudstack: No have Virtual Routers , secondary-vm and consoleproxy-vm agent state wrong

ISSUE TYPE
  • Other
COMPONENT NAME
 VR
CLOUDSTACK VERSION
4.15.0
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
STEPS TO REPRODUCE

I split six virtual machines from a single physical machine to install the highly available CloudStack,
The machine allocation is as follows
10.13.56.6 manager1
10.13.56.7 manager2
10.13.56.8 client1
10.13.56.9 client2
10.13.56.10 ha1
10.13.56.11 ha2

 /24 network
basic network model
single netCard 

I have a virtual IP 10.13.56.88 for cloudstack HA
I install cloudstack 4.15 

when I add client1 and client2 to cloudstack compute nodes successfully,
I saw system VMs agent state is wrong  and Virtual Routers not automatically created

so I login v-1-VM and s-2-VM, They can `Ping` each other
but they unable to `Ping` gateway (10.13.56.254) successfully

I don't know what happend , I have successfully run CloudStack and managed KVM on three physical machines using the tutorial
So what's wrong with me? Please help me, thanks
EXPECTED RESULTS
s-2-VM and s-2-VM agent state is up 
and Virtual Routers automatically create
ACTUAL RESULTS
system VMs agent state is wrong  and Virtual Routers not automatically created

image image image

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (9 by maintainers)

Most upvoted comments

@weizhouapache @rhtyd I found the reason, Incorrect network configuration on VMARE EXSI is causing the problem. The promiscuous mode and MAC address change pseudo transport in the VM Network configuration need to be set to accept image Thank you for your help, I will close the issue