EtherHaul Operation, Administration and Maintenance Manual
Page 67
PVID is a VLAN ID which will be assigned to an untagged frame or a priorit y-tagged
frame, (the VID is set to 0 indicating that the frame does not belong to any VLAN and
only PCP field is relevant), which enters to the bridge through this port.
o Untagged frame entering the S1 component (or provider-nni) will be tagged
with S-VLAN ID 1 with P-Bit (prio) 0.
o Untagged frame entering a C component (or customer-uni) will be tagged
with C-VLAN ID 1 with P-Bit (prio) 0.
o Configuring C-VLAN PVID is available only on ports with Network Type of
customer-uni.
CLI
set bridge-port <component-id-list> <bridge-port> [pvid <value>] [prio
<value>] [admit <value>] [filter <value>]
<component-id-list> : list: | c1 | c2 | c3 | c4 | c5 | c6 | s1
<bridge-port> : host | eth0 | eth1 | eth2 | eth3 | eth4 | s1
| c1 | c2 | c3 | c4 | c5 | c6
Admit: This attribute controls what kinds of frames are allowed into the bridge. If it is
set to untagged then only untagged or priority tagged frames may enter. If it is set to
tagged then only tagged frames (i.e. those with VID different from zero) may enter. If
it is set to all, all kinds of frames may enter. By default it is set to all.
Filter: By default the VLAN configuration is essentially asymmetrical. Frames with any
VIDs may enter through any port but leave only though a port which is a member in the
egress set assigned to a particular VLAN. By setting filter to enabled symmetry is
introduced – in this case a frame can enter through a particular port only if it can leave
through this port as well. By default the attribute is set to disabled.
8.3.4 Configuration Examples
8.3.4.1 Single Cable Connection
When single Ethernet cable is used, both customer traffic and management (either
tagged or untagged) are running over the cable.
As a single port is connected, no meaning for traffic separation applies. For such a case,
the default transparent configuration can be used (no configuration changes in the
VLAN table).
8.3.4.2 Transparent Pipe for Customer Traffic + Separate Management
In case of a requirement to provide completely transparent (and isolated) “Pi pe” for
customer traffic, two Ethernet connections are used – one for customer traffic and
second for management (either tagged or untagged).
Example: management on Eth1, customer traffic on Eth2. You are required to provide
transparanet isolated connection between Eth2 ports across the link.
To Next Page
Loading...
