Network configuration in compute node

asked 2012-12-17 09:31:55 -0600

tgsasi gravatar image

HI All,

I am facing Network routing issue. I am unable to login to the instance which created in the compute node.

In cloud controller br100 ip is 192.168.20.33 ( we assigned IP range for VM is 192.168.20.X and 192.168.20.33 is assigned for this br100. )

In compute node : its taking the eth1 ip for br100 (due to this i am unable to connect the instance )

Below is my controller & node network settings. Please give you suggestion for fixing this issue.

Network Settings below :

Cloudserver :

root@cloudserver:~# ifconfig br100 Link encap:Ethernet HWaddr 00:1a:64:c5:8d:fa inet addr:192.168.20.33 Bcast:192.168.20.63 Mask:255.255.255.224 inet6 addr: fe80::a08b:5eff:fe9a:b679/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:474 errors:0 dropped:0 overruns:0 frame:0 TX packets:1585 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:58255 (58.2 KB) TX bytes:160050 (160.0 KB)

eth0 Link encap:Ethernet HWaddr 00:1a:64:c5:8d:f8 inet addr:192.168.10.6 Bcast:192.168.10.31 Mask:255.255.255.224 inet6 addr: fe80::21a:64ff:fec5:8df8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:876113 errors:0 dropped:0 overruns:0 frame:0 TX packets:513749 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:263861137 (263.8 MB) TX bytes:282799476 (282.7 MB) Interrupt:16 Memory:ce000000-ce012800

eth1 Link encap:Ethernet HWaddr 00:1a:64:c5:8d:fa inet6 addr: fe80::21a:64ff:fec5:8dfa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1248 errors:0 dropped:0 overruns:0 frame:0 TX packets:2514 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:112890 (112.8 KB) TX bytes:195372 (195.3 KB) Interrupt:17 Memory:ca000000-ca012800

virbr0 Link encap:Ethernet HWaddr 42:da:6b:2f:23:48 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B

vnet0 Link encap:Ethernet HWaddr fe:16:3e:0f:c6:e3 inet6 addr: fe80::fc16:3eff:fe0f:c6e3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:87 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:5868 (5.8 KB) TX bytes:12121 (12.1 KB)

Compute Node :

br100 Link encap:Ethernet HWaddr 9c:8e:99:fb:6f:4c inet addr:192.168.4.2 Bcast:192.168.4.63 Mask ... (more)

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2012-12-18 13:34:36 -0600

open4job gravatar image

what't your nova configuration?

edit flag offensive delete link more
0

answered 2012-12-20 13:17:21 -0600

aji-zqfan gravatar image

br100 will get ip automatically and usually will bridge on a private nic (also can bridge on public nic, but instance will get a floating ip in the host's network). so on compute node, if you do not assign an ip to the br100 manually, the problem will be that you have defined a wrong fixed_ip_range when create a private network please check your instance's network since i notice vnet0 are created on the two nodes.

any detail will help us to locate the problem, especially the output of shell>nova-manage network list or content of /etc/nova/nova.conf

edit flag offensive delete link more
0

answered 2012-12-26 06:54:56 -0600

tgsasi gravatar image

Hi ,

Thanks for looking this issue , Output of # nova-manage network list is below id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid 2 192.168.20.32/27 None 192.168.20.34 8.8.4.4 None None None 65fa4c9a-312b-45e3-9712-48e6194deca1

/etc/nova/nova.conf details below

--allow_admin_api=true --use_deprecated_auth=false --scheduler_driver=nova.scheduler.simple.SimpleScheduler --s3_host=192.168.10.6 --ec2_host=192.168.10.6

RabbitMQ

--rabbit_host=192.168.10.6

--nova_url=http://192.168.10.6:8774/v1.1/ --routing_source_ip=192.168.10.6 --iscsi_ip_prefix=192.168.21 --ec2_url=http://192.168.10.6:8773/services/Cloud --keystone_ec2_url=http://192.168.10.6:5000/v2.0/ec2tokens --api_paste_config=/etc/nova/api-paste.ini

############ Nova Compute ########### --connection_type=libvirt --libvirt_type=kvm #-libvirt_type=qemu --libvirt_use_virtio_for_bridges=true --libvirt_cpu_mode=host-model --use_cow_images=True --snapshot_image_format=qcow2

######### Nova Volume ############# --start_guests_on_host_boot=true --resume_guests_state_on_host_boot=true --iscsi_helper=tgtadm --ec2_private_dns_show_ip

####### Glance ######### --glance_api_servers=192.168.10.6:9292 --image_service=nova.image.glance.GlanceImageService

############ MYSQL ############ --sql_connection=mysql://novadbadmin:global@192.168.10.6/nova

######## nova API ########## --auth_strategy = keystone --cc_host=192.168.10.6

########## vnc specific configuration ######## #--novnc_enabled=true #--novncproxy_base_url=http://192.168.10.6:6080/vnc_auto.html #--vncserver_proxyclient_address=192.168.10.6 #--vncserver_listen=192.168.10.6

######### Nova Network ################ --network_manager=nova.network.manager.FlatDHCPManager --public_interface=eth0 --flat_interface=eth1 --flat_network_bridge=br100 --fixed_range=192.168.20.0/27 --floating_range=192.168.4.0/26 --public_interface=vlan100 ##--auto_assign_floating_ip=True --network_size=32 --flat_network_dhcp_start=192.168.20.33 --flat_injected=false --force_dhcp_release --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --force_dhcp_release ######### MISC ########## --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --root_helper=sudo nova-rootwrap --verbose


T.G.Sasikumar

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-12-17 09:31:55 -0600

Seen: 156 times

Last updated: Dec 26 '12