Re: say hello to vtn-dev.

Home Messages Hashtags Subgroups

This group is locked. No changes can be made to the group while it is locked.

Hideyuki Tai <h-tai@...> #3 Hi, Thank you for reading the documents! Yes, your understanding is quite right. VTN is a solution which isolate physical network to many virtual tenant network. You can create interfaces (virtual ports) in a vBridge, and configure a port map for a interface of the vBridge. On configuring a port map, you can specify physical switch ID, physical port ID, and also VLAN Tag information, like the following: VTN vbridge interface \| physical switch ID port ID VLAN Tag vtn1 vbr1 1 \| physical sw 1 5 untag vtn1 vbr1 2 \| physical sw 2 4 untag vtn1 vbr1 3 \| physical sw 3 3 VLAN ID 10 vtn2 vbr1 1 \| physical sw 1 9 untag vtn2 vbr1 2 \| physical sw 2 9 untag vtn2 vbr1 3 \| physical sw 3 3 VLAN ID 20 Regards, Hideyuki Tai (2013/06/20 23:38), 黄登辉 wrote: toggle quoted message Show quoted text I am a new to vtn, i already read NEC_VTN_Demo_0606.pdf and NEC_VTN_Implementation_0606.pdf. I have a feeling, VTN is a solution which isolate physical network to many virtual tenant networks, vbridge is a logical concept, it can be considered as port mapping to physical switch. for example, a vbridge may have a port mapping, like the following: vbridge port no physical switch ID port no vbr1 1 physical sw 1 5 vbr1 2 physical sw 2 4 vbr1 3 physical sw 3 3 Is my understanding right? _______________________________________________ vtn-dev mailing list vtn-dev@... https://lists.opendaylight.org/mailman/listinfo/vtn-dev

Join {z.archive.vtn-dev@lists.opendaylight.org to automatically receive all group messages.