Bridging Configuration on PPP/MLPPP/FR/MLFR/HDLC/GigE Interface
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
429
Alcatel-Lucent
Beta Beta
OmniAccess 5740 Unified Services Gateway CLI Configuration Guide
BRIDGING CONFIGURATION COMMANDS
TO ENABLE/DISABLE BCP ON THE INTERFACE
Command (in ICM) Description
vlan {<2-4094>...
[native]|range <2-4094> <2-
4094>}
This command is entered in the Interface
Configuration Mode.
This command is used to enable VLAN
802.1Q trunk on the interface. When first
VLAN is configured, BCP is
automatically enabled.
Once BCP is enabled and is in ‘open’
state, the interface can receive/transmit
tagged packets.
(BCP state can be seen in “show
interfaces <interface-name>” command).
When ‘native’ is configured, untagged
packets are bridged based on the native
configuration.
This command can also be used to
configure multiple VLANs and a range of
VLANs on the interface.
When multiple VLANs are configured
and ‘native’ keyword is used, the last
VLAN is the native VLAN (that is, the last
VLAN is considered for bridging the
untagged packets.)
no vlan {<2-4094>...
|native|range <2-4094> <2-
4094>}
This command is used to disable BCP if
all VLANs are removed from the
interface configuration.
Use ‘Native’ keyword to disable bridging
of untagged packets. Native VLAN is no
more native though VLAN is still
configured on the interface.
BCP will be disabled if the last VLAN
configuration is removed.
This command is also used to delete
range of VLANs configured on the
interface.
To Next Page
Loading...
