![]() You canĪlso see this NIC in the brctl output, or you can find it by The packet transfers to the main NIC of the compute node. To see which bridge the packet will use, run the command: Run VlanManager, one bridge exists for each VLAN. If you run FlatDHCPManager, one bridge is on the compute node. The /etc/libvirt/qemu/instance-xxxxxxxx.xml file.įrom the vnet NIC, the packet transfers to a bridge on the compute You can find out what vnet NIC is being used by looking at The packet transfers to the virtual NIC of the compute host, such as, Interface Card (NIC) inside the instance, such as eth0. The instance generates a packet and places it on the virtual Network If you are logged in to an instance and ping an external host, forĮxample, Google, the ping packet takes the route shown in Visualizing nova-network Traffic in the Cloud ¶ ![]() ![]() ![]() You can safely ignore the state of virbr0, which is a default bridgeĬreated by libvirt and not used by OpenStack. 1: lo: mtu 16436 qdisc noqueue state UNKNOWN 2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 3: eth1: mtu 1500 qdisc pfifo_fast master br100 state UP qlen 1000 4: virbr0: mtu 1500 qdisc noqueue state DOWN 5: br100: mtu 1500 qdisc noqueue state UP ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |