VPN - Vanguard Networks
VPN - Vanguard Networks
VPN - Vanguard Networks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Tunnel Support for<br />
Bridge Traffic<br />
Figure 2-3 shows an example of packet flow between the bridge, tunnel, and LCON<br />
modules. The overall configuration guidelines of tunnel support for bridge traffic<br />
are:<br />
• Configure each tunnel with a unique Bridge Link Number. The Bridge Link<br />
can be Transparent, Source Routing or Translational Bridge Traffic.<br />
• All bridge packets intended for the remote side bridge, passing through the<br />
tunnel are encapsulated with encrypted GRE and IP headers, and then sent<br />
over the tunnel.<br />
• On the remote side tunnel, the IP and GRE Headers are removed after<br />
decryption and the original bridge packet is forwarded to the appropriate host.<br />
• Source Routing Bridge, Transparent Bridge, and Translational Bridge traffics<br />
can be tunneled.<br />
• The Protocol Type field in GRE Header has separate identifiers for:<br />
- Source Routing Bridge Packet<br />
- Spanning Tree Protocol Entity packet<br />
- Transparent Bridge packet (protocol type value = 6558)<br />
• Tunnels support the transport of BPDU between the remote bridges for<br />
spanning tree calculations.<br />
• For SR Bridge Traffic over a LAN Tunnel, the “Link Mode” must be<br />
configured as RFC1294 in the Bridge Link Configuration, corresponding to<br />
the Tunnel.<br />
(Normal) Bridge Link z<br />
Ethernet<br />
Packets<br />
Tunnel Bridge Link x<br />
Tunnel Bridge Link y<br />
LCON<br />
Module<br />
Packet<br />
Out<br />
Bridge<br />
Token Ring<br />
Packets<br />
Figure 2-3. Packet Flow between Bridge, Tunnel, and LCON Modules<br />
Tunneling 2-3<br />
T0103-10, Revision L Release 7.3