Ask Your Question
0

Local vlan id range is less

asked 2012-10-29 02:27:46 -0500

Hello, i am a new quantum fun. I have a question about provision local vlan of ovs plugin. Plugin ovs agent can provide 4094 local vlan for local vlan mapping on integration bridge 'br-int'. But each physical network can have a vlan range, it may be 1-4094. If compute node has two physical network. Each physical network vlan range is 1 - 4094. The node supports 4094 * 2 network. Now plugin agent of this node can only provide 4094 local vlan id for mapping physical network segmentation id(physical vlan id). If i create other network more than 4094, it will log error "No local VLAN availabel for net-id=xxxx" . Is it right?

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2012-10-30 06:58:59 -0500

Thanks Robert Kukura, that solved my question.

edit flag offensive delete link more
0

answered 2012-10-29 15:50:35 -0500

rkukura gravatar image

The local VLAN IDs only get allocated when a port on that node needs access to a network. Local VLAN IDs are not allocated for networks that are not used on that node. Therefore, the openvswitch plugin should be able to support simultaneous access to up to 4094 different virtual networks from a single node, but these can be distributed over any number of physical networks (and/or GRE tunnels).

-Bob

edit flag offensive delete link more
0

answered 2012-10-29 10:14:35 -0500

gongysh gravatar image

Yes, I think OVS agent Code in quantum is working this way.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-10-29 02:27:46 -0500

Seen: 50 times

Last updated: Oct 30 '12