VR IP Association Command

[ran huang <ra...@gmail.com>]

Greetings everyone,

When starting a new VR, the MAC address from "Start" and "IpAssoc" 
commands (which are received on host side) differs.

1. why is this the case?
2. what is the significance of IpAssocCommand?

I am using cloudstack v4.9.2 and centos7.



brief example:

"com.cloud.agent.api.StartCommand": {
...
"nics": [{
"deviceId" : 2
"ip" : "172.24.2.107"
"mac" : "06:b7:78:00:00:53"
...
"com.cloud.agent.api.routing.IpAssocCommand": {
...
"ipAddresses" : [{
"publicIp" : "172.24.2.107"
"vifMacAddress" : "06:24:7c:00:00:53"
"newNic" : false
...


best regards,
Ran Huang

Re: VR IP Association Command

[Rohit Yadav <ro...@shapeblue.com>]

The Start(Command) is the initial command that is sent to start a VM, the IpAssoc is used to associate a (new) nic/IP in a VR. On initial programming (say deploying a fresh VR, or a VR after restartNetwork with cleanup=true is called), the IpAssoc is sent that would configure all the necessary nics expected on the VR (for example, at least the link-local ip, the guest network nic/ip and the snat public nic/ip).



- Rohit

<https://cloudstack.apache.org>



________________________________
From: ran huang <ra...@gmail.com>
Sent: Tuesday, October 2, 2018 7:31:38 AM
To: users@cloudstack.apache.org
Subject: VR IP Association Command

Greetings everyone,

When starting a new VR, the MAC address from "Start" and "IpAssoc"
commands (which are received on host side) differs.

1. why is this the case?
2. what is the significance of IpAssocCommand?

I am using cloudstack v4.9.2 and centos7.



brief example:

"com.cloud.agent.api.StartCommand": {
...
"nics": [{
"deviceId" : 2
"ip" : "172.24.2.107"
"mac" : "06:b7:78:00:00:53"
...
"com.cloud.agent.api.routing.IpAssocCommand": {
...
"ipAddresses" : [{
"publicIp" : "172.24.2.107"
"vifMacAddress" : "06:24:7c:00:00:53"
"newNic" : false
...


best regards,
Ran Huang

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue