User's Manual

Chapter 3 - Operation and Administration Using the CLI NPU Configuration
4Motion 247 System Manual
configured to support direct communication between MSs belonging to the
service group.
 VPWS-Transparent: This type of service group is used only for VLAN CS flows.
Once service group is configured as VPWS-Transparent type, IP allocation
configuration is not required. This type of service group is not associated with
any R3 service interface as vlan-tagged MS traffic is transferred transparently
on the on the R3 interface. A VPWS-Transparent service group can be
configured to support time based accounting.
 VPWS-QinQ: This type of service group is used only for VLAN CS flows. Once
service group is configured as type VPWS-QinQ type, IP allocation
configuration is not required. This type of service group is not associated with
any R3 service interface as double-tagged MS traffic is transferred
transparently on the on the R3 interface. The QinQ VLAN used by the MS
should be received from the AAA server in Access-Accept messages. A
VPWS-QinQ service group can be configured to support time based
accounting.
 VPWS-Mapped: This type of service interface is intended for special needs
were VLAN CS service flows from multiple MSs use the same VLAN ID. Once
service group is configured as VPWS- Mapped type, IP allocation configuration
is not required. This type of service group makes the mapping between a
unique MS flow VLAN ID used on R3 interface and a CVID. The CVID can be
missing. For this service group type a VLAN pool need to configured. The
ASNGW will uniquely allocate a VLAN from the configured pool to each MS
flow to be used on R3 interface. A VPWS-Mapped service group can be
configured to support time based accounting.
You can configure up to 10 service groups, where each of the IP Service Groups is:
 Associated with a separate service IP or VLAN service interface.