vlan problem in Essex Release
+I have problem with vlan . The compute node doesn't get metadata from metadata_server.
different switch result in different performance:
test A: 2 compute nodes + normal switch = get metadata ok.
test B: 2 compute nodes + some switch (just like cisco 3750, cisco 2950) = metadata get failed.
failed error like this:
cloud-setup: failed to read iid from metadata. tried 30
WARN: /etc/rc3.
Starting dropbear sshd: generating rsa key... generating dsa key... OK
===== cloud-final: system completely up in 40.61 seconds ====
wget: can't connect to remote host (169.254.169.254): Network is unreachable
wget: can't connect to remote host (169.254.169.254): Network is unreachable
wget: can't connect to remote host (169.254.169.254): Network is unreachable
+there are 2 compute node (172.16.200.1, 172.16.200.2), 1 vlan(172.
and dnsmasq from nova-network is ok:
nobody 1508 0.0 0.0 27708 1000 ? S 14:22 0:00 dnsmasq --strict-order --bind-interfaces --pid-file=
nobody 2416 0.0 0.0 29140 1148 ? S 14:22 0:00 dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=
root 2417 0.0 0.0 29140 492 ? S 14:22 0:00 dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=
+I run nova from source script, which version is 2012.1(Essex Release)
+ the network between instance and compute node is unreachable in Test B, although `curl 169.254.169.254` run well in compute node.
thx a lot for any reply!
compute node nova.conf:
[DEFAULT]
verbose=True
auth_strategy=
allow_resize_
state_path=
lock_path=
compute_
dhcpbridge_
fixed_range=
s3_host=
s3_port=3333
connection_
network_
osapi_compute_
my_ip=172.16.200.1
vlan_interface=eth0
sql_connection=
libvirt_type=kvm
instance_
logdir=
libvirt_
resume_
reclaim_
novncproxy_
xvpvncproxy_
vncserver_
vncserver_
api_paste_
image_service=
ec2_dmz_
rabbit_
rabbit_
glance_
force_dhcp_
instances_
compute interface :
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,
link/ether 00:1e:67:09:ab:dc brd ff:ff:ff:ff:ff:ff
inet 172.16.200.2/16 brd 172.16.255.255 scope global eth0
inet6 fe80::21e:
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,
link/ether 00:1e:67:09:ab:dd brd ff:ff:ff:ff:ff:ff
inet 192.168.176.200/24 brd 192.168.176.255 scope global eth1
inet6 fe80::21e:
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,
link/ether 00:15:1a:6e:0b:08 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,
link/ether 00:15:1a:6e:0b:09 brd ff:ff:ff:ff:ff:ff
6: virbr0: <BROADCAST,
link/ether de:ce:f9:c2:5a:e4 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
8: vlan100@eth0: <BROADCAST,
link/ether 00:1e:67:09:ab:dc brd ff:ff:ff:ff:ff:ff
inet6 fe80::21e:
valid_lft forever preferred_lft forever
9: br100: <BROADCAST,
link/ether 00:1e:67:09:ab:dc brd ff:ff:ff:ff:ff:ff
inet6 fe80::2095:
valid_lft forever preferred_lft forever
10: vnet0: <BROADCAST,
link/ether fe:16:3e:32:1b:6d brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:
valid_lft forever preferred_lft forever
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- zzfancy
- Solved:
- Last query:
- Last reply: