[2.21.2-28] vRouter does not send ARP request without Gateway
Bug #1551105 reported by
Daisuke Nakajima
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Naveen N | |||
R2.21.x |
Fix Committed
|
High
|
Naveen N | |||
R2.22.x |
Fix Committed
|
High
|
Naveen N | |||
R3.0 |
Fix Committed
|
High
|
Naveen N | |||
Trunk |
Fix Committed
|
High
|
Naveen N |
Bug Description
Live-migration and preferred VM selection are not working in case of without Gateway.
The cause of issue is that vRouter does not send ARP request to AAP address if there is no Gateway in Virtual-network.
vRouter needs to send ARP request from DNS-server-address.
Changed in juniperopenstack: | |
assignee: | nobody → Naveen N (naveenn) |
milestone: | none → r3.1.0.0-fcs |
importance: | Undecided → High |
Changed in juniperopenstack: | |
status: | New → Fix Committed |
information type: | Proprietary → Public |
To post a comment you must log in.
Virtual network does not have both 'default_gateway' and 'dns_server_ address' in some cases like below; address' as '0.0.0.0'.
When VM uses Global IP address without both default gateway and dhcp, customer aims to use all of Global IP address for VM. Because each Global IP address is not wealth. Hence, customer wants to set both 'default_gateway' and 'dns_server_
However, if both attributes are set '0.0.0.0', there is no Interface of pkt0 for sending APR packet from vRouter. As a result, nova live-migration will not work well. address' are set "0.0.0.0". If vrouter sends ARP request to VM, use "0.0.0.0" for Sender IP address in ARP packet. linux.die. net/man/ 8/arping
To avoid this issue, I'd like to propose two solutions below.
1) At least one Pkt0 interface will be allocated to each virtual-network even if both 'default_gateway' and 'dns_server_
see DAD mode http://
2) Allow dummy IP address to 'dns_server_ address' such as '169.254.169.1' when Customer does not want to consume any IP address for Contrail internal use. address' after fixing this bug. network" : {
"display_ name": "test1",
"flood_ unknown_ unicast" : false,
"default- domain" ,
"admin" , 172.27. 113.202: 8082/virtual- network/ 02cf8444- 8fdd-4451- 91b5-967b7e6faf 35",
"created" : "2016-03- 03T00:55: 47.726224" ,
"creator" : null,
"descripti on": null,
"enable" : true,
"last_ modified" : "2016-03- 03T00:55: 47.841816" ,
"permissio ns": {
"group" : "admin",
"group_ access" : 7,
"other_ access" : 7,
"owner" : "admin",
"owner_ access" : 7
"user_ visible" : true,
"uuid_ lslong" : 104994635634305 71829,
"uuid_ mslong" : 202525938261247057
"is_shared" : false,
"network_ ipam_refs" : [
"attr" : {
" ipam_subnets" : [
{
"addr_from_ start": true,
"allocation_ pools": [],
"default_ gateway" : "169.254.169.1",
"dhcp_option_ list": {
"dhcp_ option" : [
{
"dhcp_ option_ name": "6",
"dhcp_ option_ value": "0.0.0.0"
}
]
},
"dns_server_ address" : "0.0.0.0",
"enable_ dhcp": false,
"host_routes" : {
"route" : []
},
...
As per my test, nova live-migration with AAP worked well when I configured '169.254.169.1' to 'default_gateway'. I think dummy address will work in 'dns_server_
This is the JSON which I tested.
{
"virtual-
"fq_name": [
"test1"
],
"href": "http://
"id_perms": {
},
"uuid": {
}
},
"name": "test1",
{