BelAir100SN User Guide
Using Layer 2 Tunnels
May 31, 2010
Confidential
Document Number BDTM11001-A01 Released
If you specify a DSCP value, then it appears in the DSCP/TOS bits of any L2TP
or PPP control packets.
Configuring Layer 2
Extended Tunnels
/protocol/te-<eng>/set tunnel-x <index (1-5)>
source <if-VLAN> [backup-source <if_VLAN>]
lns <ip_addr> [backup-lns <ip_addr>]
name <host name> [backup-name <host name>]
[switch {non-revertive | revertive}]
/protocol/te-<eng>/delete tunnel <index>
The
set tunnel-x
command allows you to configure an extended tunnel that has
two VLAN interfaces to provide redundancy in case one VLAN interface
becomes unreachable.
First you must configure the tunnel engine to be in extended mode. See
“Setting Tunnel Engine Parameters” on page 154
. Then, you configure the
extended tunnel with the
set tunnel-x
command.
The <index> parameter is used for easy reference when using other
commands. It can be displayed with the
/protocol/te-<eng>/show config
command.
The
source
and
backup-source
parameters specify the primary and backup
VLAN interfaces. The
lns
and
backup-lns
parameters specify the IP addresses of
the LNS for each of the VLAN interfaces. The
name
and
backup-name
parameters specify the host names for each of the VLAN interfaces.
The <host name> parameter can be any series of 18 alphanumeric ASCII
characters. It is analogous to the <stn_name> parameter when configuring a
simple tunnel. See
“Configuring Layer 2 Tunnels” on page 153
.
The
switch
parameter controls whether the use of a backup VLAN is revertive
or not. Once the BelAir unit starts to use a tunnel through a backup VLAN:
• If
switch
is set to
non-revertive
, then the BelAir unit uses the tunnel through
the backup VLAN until it fails. Only then does the BelAir unit switches back
to the tunnel using the main VLAN. This is the default setting.
• If
switch
is set to
revertive
, then the BelAir unit uses the tunnel through the
backup VLAN only while the main tunnel is unavailable. The BelAir unit
switches back to the tunnel using the main VLAN as soon as it becomes
available again.
The
delete tunnel
command removes the specified tunnel. After using this
command, user data mapped to this tunnel is dropped instead of forwarded.