User's Manual

Chapter 3 - Operation and Administration Using the CLI NPU Configuration
4Motion 286 System Manual
only with an IP service group. A VLAN CS service flow can be associated only with
a VPWS (Transparent/QinQ/Mapped) service group. Typically VLAN CS service
flows should be managed (created/modified/deleted) only by the AAA server.
However, to support special needs, it is possible to define VLAN CS service flows
for the Default Service Profile.
Up to 12 Service Flows can be defined for each Service Profile.
1 Enable the service flow configuration mode (refer to Section 3.3.11.15.3.3.1)
2 You can now execute any of the following tasks:
» Configure the parameters for this service flow (refer to
Section 3.3.11.15.3.3.2)
» Restore the default parameters for this service flow (refer to
Section 3.3.11.15.3.3.3)
» Configure uplink/downlink classification rule names (refer to
Section 3.3.11.15.3.3.4)
3 Terminate the service flow configuration mode (refer to
Section 3.3.11.15.3.3.6)
You can, at any time delete an existing service flow (refer to
Section 3.3.11.15.3.3.7).
3.3.11.15.3.3.1Enabling the Service Flow Configuration Mode\ Creating a New Service
Flow
To configure the parameters for a service flow, first enable the service flow
configuration mode. Run the following command to enable the service flow
configuration mode. You can also use this command to create a new service flow.
npu(config-srvcprfl)# flow [<flow-id (1-255)] [grp-alias
<srvc-grp-alias>] [if-alias <string>] [mcast-sfid <integer(0-65535)>
{[mcastipv4add <string(15)>]}] [<string>]
After enabling the service profile configuration mode, execute the following tasks to
configure service flows within this service profile:
NOTE
The mcast-sfid and mcastipv4add parameter are for future use with a DGW
profile (not supported in the current release). Do not use these parameters. In
the following sections these parameters will be ignored.