Configuring Service Profiles

• About Service Profiles, on page 1

• How to Configure Service Profiles, on page 7

About Service Profiles

A Gigabit passive optical network (GPON) topology consists of an optical line termination (OLT) device that
is connected to multiple optical network terminals (ONTs) through an optical splitter.
Downstream traffic is the traffic flowing from an OLT to a specific ONT. The OLT receives and transmits
the Ethernet services to the GPON Encapsulation Method (GEM) ports. Each GEM port is identified by a
unique ID called port ID. The GEM ports encapsulate the Ethernet services into GEM frames, add the port
ID, and broadcast the GEM frames to all the connected ONTs. The ONT then filters the GEM frames based
on the port ID, decapsulates the GEM frames to Ethernet services, and transmits the services to end users.
Upstream traffic is the traffic flowing from all the ONTs to the OLT. Because all the ONTs share the same
transmission channel, only one ONT is allocated the bandwidth to transmit data at a given point in time.
Bandwidth allocation is based on the type of transmission container (T-CONT). A T-CONT is a buffer for
transmitting the upstream service flow in the GPON system, and is identified by an allocation ID. The ONT
encapsulates the Ethernet services to the GEM frames, and buffers the GEM frames into the T-CONT that is
waiting for the uplink data forwarding time. Multiple GEM ports are multiplexed into a T-CONT. The OLT
receives the GEM frames through the GEM ports, decapsulates the GEM frames to Ethernet services, and
transmits the services to the access layer device.
Service profile deployment allows you to configure various profile templates. The following table lists the
various profile templates that you can configure.

Table 1: Service Profile Operation

Configuration Task Type of Traffic Required or Optional

VLAN profiles Upstream and downstream traffic Required

DBA profiles Upstream traffic only Required

Uplink traffic profiles Upstream traffic only Optional

Downlink traffic profile Downstream traffic only Optional

Line profiles Upstream traffic only Required

Configuring Service Profiles

1
 Configuring Service Profiles
About VLAN Profiles

Configuration Task Type of Traffic Required or Optional

Rule profiles Upstream traffic only Required

Unique profiles Upstream traffic only Optional

You can specify a default service profile and bind multiple service profiles to a rule. The device type
configuration in multiple service profiles vary. After an ONT is registered, the OLT checks the service profiles
based on the device type reported by the ONT. If the device type in the service profile matches the device
type reported by the ONT, the OLT sends the service profile to the ONT. If the device type does not match,
the OLT checks whether the default service profile exists and sends the default service profile to the ONT.

About VLAN Profiles

You can configure VLAN application modes to the traffic flow between the OLT and the ONT. The OLT
supports both the N:1 and 1:1 VLAN application modes for flexible and variable VLAN service applications.
The OLT implements GEM port-based VLAN transformation rules through the VLAN profile template
configuration. A VLAN profile template can be configured with the following transformation rules:
• Add rule: This rule is used to configure VLAN stacking rules. After a rule is configured and applied, in
the upstream direction, the OLT adds an outer-VLAN tag to the inner-VLAN tag of the service flow
originating from the ONT and carried by the corresponding GEM port. In the downstream direction, the
OLT strips the ingress traffic outer-VLAN tag from the uplink device and forwards it to the ONT through
the corresponding GEM port. Each VLAN profile template can be configured with 32 VLAN stacking
rules, but the inner-VLAN tag (a combination of VLAN ID and priority) should be unique in each rule.
After the template is configured, it is referenced by the GEM port configured in the line profile template
or unique profile template.
• Add default rule: This rule is used to configure VLAN tagging rules. After a rule is configured and
applied, in the upstream direction, the OLT adds a default VLAN tag to the untagged service flow
originating from the ONT and carried by the corresponding GEM port. In the downstream direction, the
OLT strips the default VLAN of the service flow from the uplink port and forwards it to the ONT through
the corresponding GEM port. Only one default VLAN tag rule can be configured for each VLAN profile
template. After the template is configured, it is referenced by the GEM port configured in the line profile
template or unique profile template.
• Translate rule: This rule is used to configure VLAN translation rules. After a rule is configured and
applied, in the upstream direction, the OLT converts the old-VLAN tag to the new-VLAN tag of the
service flow originating from the ONT and carried by the corresponding GEM port. In the downstream
direction, the OLT converts the new-VLAN tag of the service flow to the old-VLAN tag and forwards
it to the ONT through the corresponding GEM port. Each VLAN template can be configured with 32
VLAN conversion rules, but the old-VLAN tag (a combination of VLAN ID and priority) should be
unique in each rule. After the template is configured, it is referenced by the GEM port configured in the
line profile template or unique profile template.

After the VLAN template is referenced, the VLAN translation and the stacking rules are compared for an
upstream packet with a VLAN tag. The VLAN tag rule is compared for an upstream packet without a VLAN
tag from an ONT GEM port. The packet is discarded if there is no corresponding matching rule.

Configuring Service Profiles

2
 Configuring Service Profiles
About DBA Profiles

About DBA Profiles

For upstream traffic, only one ONT is allowed to transmit data at a given point in time because all the ONTs
share the same transmission channel. The upstream traffic is handled by scheduling a dynamic bandwidth
assignment (DBA) profile.
Bandwidth allocation is based on the configured T-CONT for transmitting upstream traffic. Each T-CONT
type provides a certain Quality of Service (QoS).
The following table lists the different types of T-CONT, the relationship between each type of T-CONT, and
bandwidth allocation and service application for each T-CONT type

Table 2: T-CONT Type Summary

T-CONT Type Traffic Descriptor Component Description

Type 1 Fixed bandwidth Provides only fixed bandwidth.

Configured for carrying traffic that
is sensitive to delay or jitter, for
example, VoIP services.

Type 2 Assured bandwidth Provides only assured bandwidth.

Configured for carrying on or off
type traffic without strict delay and
jitter requirements, for example,
IPTV multicast services.

Type 3 Assured bandwidth Provides both assured bandwidth

as well as nonassured bandwidth.
Maximum bandwidth
Configured for carrying
variable-rate burst traffic.

Type 4 Maximum bandwidth Provides best-effort bandwidth.

Configured for carrying
variable-rate burst traffic that does
not exhibit delay sensitivity, for
example, internet data services.

Type 5 Fixed bandwidth Provides a combination of fixed,

assured, and best-effort bandwidth.
Assured bandwidth
Configured for carrying general
Maximum bandwidth traffic.

The following are the characteristics of aDBA profile:

• In all types of T_CONT, bandwidth allocation is prioritized in the following order:
1. Fixed bandwidth
2. Assured bandwidth
3. Nonassured bandwidth
4. Best-effort bandwidth

Configuring Service Profiles

3
 Configuring Service Profiles
About Uplink Traffic Profiles

• Fixed bandwidth assured bandwidth together comprise the basic bandwidth. The sum of the fixed
bandwidth and the assured bandwidth of all T-CONT configurations under the same PON port cannot
exceed the total uplink bandwidth of the corresponding PON port.
• Nonassured and best-effort bandwidth together comprise the additional bandwidth.

About Uplink Traffic Profiles

Uplink traffic flow is scheduled based on the GEM port. The following are the two types of scheduling modes:
• Flow control mode: The flow is controlled by the GEM port rate limitation configured on the GEM port.
• Priority queue scheduling mode: The flow is controlled by the GEM port priority.

The uplink traffic profile configuration is applied only if the ONT supports it. After the uplink traffic profile
template is applied, it is referenced based on the GEM port in the line profile template or unique profile
template. The GEM port traffic is scheduled by the ONT based on the uplink traffic profile configuration.

About Downlink Traffic Profiles

Downlink traffic flow is scheduled using the flow control mode.
Only one downstream traffic flow schedule can be configured in a GEM port. After the downlink traffic profile
template is applied, it is referenced based on the GEM port in the line profile template or unique profile
template.

About Line Profiles

A line profile allows you to map the ONT service flow to the OLT. The following are the parameters required
to create a line profile:
1. Device type
Define a device type. Each connected ONT must have its own specific device type name. When the ONT
is registered to go online, the OLT delivers a specific line profile template configuration according to the
device type reported. In the line profile configuration, the device type must be configured first. The device
type cannot be modified after the line profile is configured. The entire line profile configuration must be
removed when the device type is deleted or modified.
2. T-CONT
Create a T-CONT and configure the binding relationship between the T-CONT and the DBA profile
template.
3. GEM port
Create a GEM port and configure the GEM port parameters, as detailed below:
a. Configure a GEM port and map it to the T-CONT.
b. Map the GEM port to the VLAN profile configuration. The OLT must support the GEM port-based
VLAN translate rule.
c. Map the GEM port to the uplink traffic profile. The upstream traffic scheduling parameters are
configured in the upstream traffic profile.

Configuring Service Profiles

4
Configuring Service Profiles
About Line Profiles

d. Map the GEM port to the downlink traffic profile. The downlink bandwidth rate limit configured in
the downlink traffic profile is implemented by the OLT ACL resources.

4. Mapping rule
Configure mapping rules between the GEM port and user interface data flows, as detailed below:
a. A mapping mode is required to configure mapping between the GEM port and the data flowing from
the user interface. The following are the various mapping modes available:
• Port
• VLAN ID
• 802.1P priority
• Port + VLAN ID
• Port + 802.1P priority
• VLAN ID+802.1P priority
• Port+VLAN ID+802.1P priority

Note Only one mapping mode can be configured for the same service profile. The default mapping mode is based
on VLAN ID mapping.

b. A mapping table establishes the mapping relationship between the GEM port and the upstream data
flowing into the ONT user interface. After the mapping relationship is established, the corresponding
GEM port can be used to carry the service.

Note The parameters of the mapping mode must be the same as those configured in the mapping table configuration.

5. Flow rule
Configure flow rules, as detailed below:
a. Service flows are distinguished by the ONT based on the packet Ethernet type and the port the packets
are received into.
Packets that receive ports are classified into the following types:
• Ethernet interface (Eth): The Ethernet interface refers to the LAN port of the ONT.
• Virtual Ethernet interface (VEIP): The virtual Ethernet interface refers to the WAN interface of
the ONT.
• Voice IP interface (IPhost): The voice IP interface is applicable to ONTs that supports voice
service.

b. The VLAN tag processing policy of the ONT flow. Based on the flow rules configured, the ONT
applies the VLAN processing rule on the service flow. The following are the VLAN tag processes:

Configuring Service Profiles

5
 Configuring Service Profiles
About Unique Profiles

• Transparent
• Default
• Keep
• Translate
• Add

6. Rule profile
Configure a rule profile. Configure a rule profile, as detailed below:
a. Configure the ONT authentication rule and bind the line profile to the related ONTs. An OLT supports
the following authentication modes:
• Serial number authentication
• Password authentication
• Combination of serial number and password authentication
• Logical ONT ID (LOID) authentication
• LOID password authentication
• Combination of LOID and LOID password authentication.

Serial number authentication, password authentication, and a combination of serial number and
password authentication are ITU-defined ONT authentication methods.
b. Configure the ONT discovery mode. This can be configured with password authentication mode, a
combination of serial number and password authentication mode, and all LOID related authentication
modes. There are two types of ONT discovery modes:
• Always-on mode: This mode indicates that even after the ONT passes the authentication, if the
serial number changes, the ONT goes online. By default, the ONT discovery mode is in always-on
mode.
• Once-on mode: This mode indicates that the ONT must be authenticated and registered within
the specified time after the configuration of the profile is completed. If ONT authentication
succeeds, the serial number cannot be modified. The specified time can be set either by no aging
time and aging time. A no-aging time means that the timeout period is not set and the ONT can
always be authenticated.

After the ONT authentication rule is configured, the service profile is applied to the ONT.

About Unique Profiles

Each ONT is configured differently based on the service flow attribute and each of its service flow application.
For example, for voice service flow, the flow attribute is a telephone number. You can configure a line profile
and a unique profile on an OLT, based on the ONT service application. The following are the conditions for
configuring line profile and unique profile as well as the advantages and disadvantages of each method.

Configuring Service Profiles

6
 Configuring Service Profiles
How to Configure Service Profiles

• If the ONT service flow attributes are not distinguished, different line profiles are directly configured
for each ONT. Although this method allows for clear configurations, a large number of line profiles can
occupy space in the configuration file.
• If the ONT service flow attributes are distinguished, the common service flow attributes are configured
as a line profile, and the different service flow attributes are configured as a unique profile. Although
this method allows for simpler configuration, it is difficult to modify the ONT configurations because
they are unclear.

Perform the following configuration steps to create a unique profile:

1. Configure the ONT description. This description can be used to describe the geographic location of the
terminal according to the user. If a terminal fails, its location can be located quickly for troubleshooting
nased on its description.
2. Bind the traffic profile and VLAN profile to the ONT GEM port using the GEM port profile. The ONT
GEM port can only be created in the line profile. The ONT GEM port binding relationship to the traffic
profile and VLAN profile can be configured either in the line profile or the unique profile.

Note If there is a GEM port profile binding configuration in both the line profile and the unique profile, the unique
profile configuration takes precedence.

3. Configure the ONT SIP service, including the SIP proxy attributes, SIP interface attributes, SIP number
attributes, and digitmap attributes.

How to Configure Service Profiles

The following sections provide information on how to configure various service profiles.

Configure a VLAN Profile

To configure a VLAN profile, perform the following procedures.

Configure an Add Rule

Modifying and activating the VLAN template causes the ONT that references the template to go online again.
To configure add rule, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Configuring Service Profiles

7
 Configuring Service Profiles
Configure a Default Rule

Command or Action Purpose

Step 2 configure terminal Enters global configuration mode.
Example:
Device# configure terminal

Step 3 deploy profile vlan Enters VLAN profile configuration mode.

Example:
Device(config)# deploy profile vlan

Step 4 aim {index_num [name name] | name name} Creates VLAN aim.
Example: • index_num: The index of the template. The range is
Device(deploy-profile-vlan)# aim 5 from 0 to m, where m is the maximum number of
ONTs supported.
• name: The name of the template in string format. The
string length is from 1 to 128.

Step 5 [no] add inner-vlan vid {priority } {outer-vlan {vid Configures the VLAN stacking rule.
[priority] } }
• vid: The VLAN ID. The range is from 0 to 4094.
Example:
• priority: The 802.1 priority. The range is from 0 to 7.
Device(deploy-profile-vlan-5)#

Use the no add inner-vlan vid [priority] command to delete

the VLAN stacking rule.

Step 6 active Activates the VLAN rule.

Example:
Device(deploy-profile-vlan-5)# active

Step 7 exit Exits to VLAN profile configuration mode.

Example:
Device(deploy-profile-vlan-5)# exit

Step 8 delete aim {index_list | name name} (Optional) Deletes the VLAN aim.
Example: • index_list: The index number combination.
Device(deploy-profile-vlan)# delete aim 5
• name: The name of the template in string.

Step 9 exit Exits to global configuration mode.

Example:
Device(deploy-profile-vlan)# exit

Configure a Default Rule

Modifying and activating the VLAN template causes the ONT that references the template to go online again.
To configure a default rule, perform this procedure.

Configuring Service Profiles

8
 Configuring Service Profiles
Configure a Default Rule

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile vlan Enters VLAN profile configuration mode.

Example:
Device(config)# deploy profile vlan

Step 4 aim {index_num [name name] | name name} Creates VLAN aim.
Example: • index_num: The index of the template. The range is
Device(deploy-profile-vlan)# aim 5 from 0 to m, where m is the maximum number of
ONTs supported.
• name: The name of the template, in string format. The
string length is from 1 to 128.

Step 5 [no] default vlan vid [priority] Configures a VLAN tagging rule.
Example: • vid: The VLAN ID. The range is from 0 to 4094.
Device(deploy-profile-vlan-5)# default vlan 5 5
• priority: The 802.1 priority. The range is from 0 to 7.

Use the no default vlan command to delete the VLAN

tagging rule.

Step 6 active Activates the VLAN rule.

Example:
Device(deploy-profile-vlan-5)# active

Step 7 exit Exits to VLAN profile configuration mode.

Example:
Device(deploy-profile-vlan-5)# exit

Step 8 delete aim {index_list | name name} (Optional) Deletes the VLAN aim.
Example: • index_list: The index number combination.
Device(deploy-profile-vlan)# delete aim 5
• name: The name of the template in string.

Step 9 exit Exits to global configuration mode.

Example:
Device(deploy-profile-vlan)# exit

Configuring Service Profiles

9
 Configuring Service Profiles
Configure a Translate Rule

Configure a Translate Rule

Modifying and activating the VLAN template causes the ONT that references the template to go online again.
To configure a translate rule, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile vlan Enters VLAN profile configuration mode.

Example:
Device(config)# deploy profile vlan

Step 4 aim {index_num [name name] | name name} Creates VLAN aim.
Example: • index_num: The index of the template. The range is
Device(deploy-profile-vlan)# aim 5 from 0 to m, where m is the maximum number of
ONTs supported.
• name: The name of the template, in string format. The
string length is from 1 to 128.

Step 5 [no] translate old-vlan vid {priority | new-vlan {vid Configures the VLAN translate rule.
[priority] } }
• vid: The VLAN ID. The range is from 0 to 4094.
Example:
• priority: The 802.1 priority. The range is from 0 to 7.
Device(config)#

Use the no translate old-vlan vid [priority] to delete the

VLAN translate rule.

Step 6 active Activates the VLAN rule.

Example:
Device(config)#

Step 7 exit Exits to VLAN profile configuration mode.

Example:
Device(deploy-profile-vlan-5)# exit

Step 8 delete aim {index_list | name name} (Optional) Deletes the VLAN aim.
Example: • index_list: The index number combination.
Device(deploy-profile-vlan)# delete aim 5
• name: The name of the template in string.

Configuring Service Profiles

10
 Configuring Service Profiles
Configure a DBA Profile

Command or Action Purpose

Step 9 exit Exits to global configuration mode.
Example:
Device(deploy-profile-vlan)# exit

Configure a DBA Profile

Modifying and activating the DBA profile causes the ONT that references the template to go online again.
To configure a DBA profile, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile dba Enters DBA profile configuration mode.

Example:
Device(config)# deploy profile dba

Step 4 aim {index_num [name name] | name name} Creates the DBA aim.
Example: • index_num: The index of the template. The range is
Device(deploy-profile-dba)# from 0 to m, where m is the maximum number of
ONTs supported.
• name: The name of the template, in string format.
The string length is from 1 to 128.

Step 5 type 1 fix fixed_bandwidth Configures Type 1 DBA.

Example: fixed_bandwidth: The fixed bandwidth, in kbps. The range
Device(deploy-profile-dba-5)# type 1 fix 1024 is from 256 to 800000.

Step 6 type 2 assured assured_bandwidth Configures Type 2 DBA.

Example: assured_bandwidth: The assured bandwidth, in kbps. The
Device(deploy-profile-dba-5)# type 2 assured 1024 range is from 0 to 800000.

Step 7 type 3 assured assured_bandwidth max max_bandwidth Configures Type 3 DBA.

Example: • assured_bandwidth: The assured bandwidth, in kbps.
The range is from 0 to 800000.

Configuring Service Profiles

11
 Configuring Service Profiles
Configure an Uplink Traffic Profile

Command or Action Purpose

Device(deploy-profile-dba-5)# type 3 assured 256 • max_bandwidth: The maximum bandwidth, in kbps.
max 1024 The range is from 256 to 1200000.

Step 8 type 4 max max_bandwidth Configures Type 4 DBA.

Example: • max_bandwidth: The maximum bandwidth, in kbps.
Device(deploy-profile-dba-5)# type 4 max 256 The range is from 256 to 1200000.

Step 9 type 5 fix fixed_bandwidth assured assured_bandwidth Configures Type 5 DBA.

max max_bandwidth
• fixed_bandwidth: The fixed bandwidth, in kbps. The
Example: range is from 256 to 800000.
Device(deploy-profile-dba-5)# type 5 fix 1024
assured 256 max 256
• assured_bandwidth: The assured bandwidth, in kbps.
The range is from 0 to 800000.
• max_bandwidth: The maximum bandwidth, in kbps.
The range is from 256 to 1200000.

Step 10 active Activates the DBA aim.

Example:
Device(deploy-profile-dba-5)# active

Step 11 exit Exits to VLAN profile configuration mode.

Example:
Device(deploy-profile-dba-5)# exit

Step 12 delete aim { index_list | name name} (Optional) Deletes the DBA aim.
Example: • index_list: The index number combination.
Device(deploy-profile-dba)#
• name: The name of the template in string.

Step 13 exit Exits to global configuration mode.

Example:
Device(deploy-profile-dba)# exit

Configure an Uplink Traffic Profile

Modifying and activating the uplink traffic profile causes the ONT that references the template to go online.
To configure an uplink traffic profile, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.

Configuring Service Profiles

12
 Configuring Service Profiles
Configure an Uplink Traffic Profile

Command or Action Purpose

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile us-traffic Enter uplink traffic profile configuration mode.
Example:
Device(config)# deploy profile us-traffic

Step 4 aim {index_num [name name] | name name} Creates uplink traffic profile aim.
Example: • index_num: The index of the template. The range is
Device(deploy-profile-us-traffic)# aim 5 from 0 to m, where m is the maximum number of
ONTs supported.
• name: The name of the template, in string format.
The string length is from 1 to 128.

Step 5 us queue queue_id (Optional) Configures GEM port queue priority.

Example: queue_id: GEM port priority queue in T-CONT. The range
Device(deploy-profile-us-traffic-5)# us queue 5 is from 0 to 7, where, 0 is the lowest priority and 7 is the
highest priority.

Step 6 us car cir cir cbs cbs pir pir pbs pbs (Optional) Configures GEM port traffic control.
Example: • cir: The committed information rate, in kbps. The
Device(deploy-profile-us-traffic-5)# us car cir range is from 64 to 800000.
256 cbs 23 pir 1024 pbs 5
• cbs: The committed burst size, in KB. The range is
from 2 to 25000.
• pir: The peak information rate, in kbps. The range is
from 64 to 1024000. The peak information rate
requirement is greater than or equal to committed
information rate.
• pbs: The peak burst size, in KB. The range is from 2
to 25000.

Step 7 active Activates the uplink traffic profile aim.

Example:
Device(deploy-profile-us-traffic-5)# active

Step 8 exit Exits to VLAN profile configuration mode.

Example:
Device(deploy-profile-us-traffic-5)# exit

Step 9 delete aim {index_list | name name} (Optional) Deletes the uplink traffic profile aim.

Configuring Service Profiles

13
 Configuring Service Profiles
Configure a Downlink Traffic Profile

Command or Action Purpose

Example: • index_list: The index number combination.
Device(deploy-profile-us-traffic)# delete aim 5
• name: The name of the template in string.

Step 10 exit Exits to global configuration mode.

Example:
Device(deploy-profile-us-traffic)# exit

Configure a Downlink Traffic Profile

Modifying and activating the downlink traffic profile causes the ONT that references the template to go online.
To configure a downlink traffic profile, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile ds-traffic Enters downlink traffic profile configuration mode.
Example:
Device(deploy-profile-ds-traffic)#

Step 4 aim {index_num [name name] | name name} Creates downlink traffic profile aim.
Example: • index_num: The index of the template. The range is
Device(deploy-profile-ds-traffic)# aim 5 from 0 to m, where m is the maximum number of
ONTs supported.
• name: The name of the template, in string format. The
string length is from 1 to 128.

Step 5 ds car bandwidth bandwidth (Optional) Configures GEM port committed access rate
(CAR).
Example:
Device(deploy-profile-ds-traffic-5)# bandwidth: The downstream bandwidth, in kbps. The value
range is from 64 to 2608832.

Step 6 active Activates the downlink traffic profile aim.

Example:
Device(deploy-profile-ds-traffic-5)#

Configuring Service Profiles

14
 Configuring Service Profiles
Configure a Line Profile

Command or Action Purpose

Step 7 exit Exits to VLAN profile configuration mode.
Example:
Device(deploy-profile-ds-traffic-5)# exit

Step 8 delete aim {index_list | name name} (Optional) Deletes the downlink traffic profile aim.
Example: • index_list: The index number combination.
Device(deploy-profile-ds-traffic)# delete aim 5
• name: The name of the template, in string format.

Step 9 exit Exits to global configuration mode.

Example:
Device(deploy-profile-ds-traffic)# exit

Configure a Line Profile

To configure a line profile, perform the following procedures.

Configure a Device Type

Modifying and activating the line profile causes the ONT that references the template to go online.
To configure a device type, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile line Enter line profile configuration mode.

Example:
Device(config)# deploy profile line

Step 4 aim {index_number [name name] | name name} Creates line profile aim.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string format.

Configuring Service Profiles

15
 Configuring Service Profiles
Configure a T-CONT

Command or Action Purpose

Step 5 device type type Configures the device type.
Example: type: The ONT device type name. The name of the ONT
Device(deploy-profile-line-5)# device type c40-100 device type should conform to the GPON Terminal Naming
Specification.

Step 6 active Activates the line profile.

Example:
Device(deploy-profile-line-5)# active

Step 7 exit Exits to line profile configuration mode.

Example:
Device(deploy-profile-line-5)# exit

Step 8 delete aim {index_list | name name} (Optional) Deletes the aim.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# delete aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
w
• name: The profile name in string

Step 9 exit Exits to global configuration mode.

Example:
Device(deploy-profile-line)# exit

Configure a T-CONT
Modifying and activating the line profile causes the ONT that references the template to go online.
To configure a T-CONT, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile line Enters line profile configuration mode.

Example:
Device(config)# deploy profile line

Configuring Service Profiles

16
 Configuring Service Profiles
Configure a GEM Port

Command or Action Purpose

Step 4 aim {index_number [name name] | name name} Creates line profile aim.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string.

Step 5 [no ] tcont tcont_id profile dba {index_num |name name} Creates T-CONT.
Example: • tcont_id: The T-CONT ID. The value range is from 1
Device(deploy-profile-line-5)# tcont 2 profile dba to 8.
5
• index_number: The index of the template. The range
is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string.

Step 6 active Activates the line profile.

Example:
Device(deploy-profile-line-5)# active

Step 7 exit Exits to line profile configuration mode.

Example:
Device(deploy-profile-line-5)# exit

Step 8 delete aim {index_list | name name} (Optional) Deletes the line profile.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# delete aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string.

Step 9 exit (Optional) Exits to global configuration mode.

Example:
Device(deploy-profile-line)# exit

Configure a GEM Port

Modifying and activating the line profile causes the ONT that references the template to go online.
To configure GEM port, perform this procedure.

Before you begin

T-CONT must be configured before configuring a GEM port. The GEM port must also be bound to the VLAN
profile. The upstream and downstream traffic profiles are optional.

Configuring Service Profiles

17
 Configuring Service Profiles
Configure a GEM Port

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile line Enters line profile configuration mode.

Example:
Device(config)# deploy profile line

Step 4 aim {index_number [name name] | name name} Creates line profile aim.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string.

Step 5 gemport traffic-mode {car | queue} Configures the GEM port traffic mode.
Example:
Device(deploy-profile-line-5)# gemport
traffic-mode car

Step 6 [no] gemport gem_index tcont tcont_id [encrypt | Creates GEM port and configure the parameters.
vlan-profile | us-traffic-profile | ds-traffic-profile ]
• gem_index: The GEM port index number. The ranges
{index_number | name name}
is from 1 to 1024. Currently, at most 24 GEM Ports
Example: can be created in each line profile.
Device(deploy-profile-line-5)# gemport 2 tcont 2
vlan-profile 2
• index_number: The index of the template. The range
is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The name of the template, in string format.
The string length range is from 1 to 128.

Use the no gemport gem_index to delete the GEM port.

Step 7 active Activates the line profile.

Example:
Device(deploy-profile-line-5)# active

Step 8 exit Exits to line profile configuration mode.

Example:
Device(deploy-profile-line-5)# exit

Configuring Service Profiles

18
 Configuring Service Profiles
Configure a Mapping Rule

Command or Action Purpose

Step 9 delete aim {index_number | name name} (Optional) Deletes the line profile.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# delete aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string.

Step 10 exit Exits to global configuration mode.

Example:
Device(deploy-profile-line)# exit

Configure a Mapping Rule

Modifying and activating the line profile causes the ONT that references the template to go online.
To configure a mapping rule, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile line Enters line profile configuration mode.

Example:
Device(config)# deploy profile line

Step 4 aim {index_number [name name] | name name} Creates line profile aim.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string.

Step 5 mapping mode {port | port-priority | port-vlan | Configures the GEM port mapping mode configuration.
port-vlan-priority | priority | vlan | vlan-priority}
Example:
Device(deploy-profile-line-5)# mapping mode port

Configuring Service Profiles

19
 Configuring Service Profiles
Configure a Flow Rule

Command or Action Purpose

Step 6 [no] mapping index_number { vlan vlan_id | priority Creates GEM port mapping.
priority | port {eth port_id | veip | iphost } } gemport
• index_number: Mapping index number. The value
gem_index
range is from 0 to 47.
Example:
• vlan_id: The VLAN ID. The value range is from 1 to
Device(deploy-profile-line-5)# mapping 2 port eth
2 gemport 2
4094.
• priority: The 802.1P. The value range is from 0 to 7.
• eth: The ONT Ethernet interface. Optional for SFU.
• veip: The ONT WAN interface. Optional for HGU.
• iphost: The ONT voice IP interface.
• port_id: The ONT Ethernet interface. The value range
is from 1 to 24 depending on the number of ONTs.
• gem_index: The GEM port index number. The range
is from 1 to 1024. Currently, a maximum of 24 GEM
ports can be created in each line profile.

Use the no mapping index_num to delete GEM port

mapping.

Step 7 active Activates the line profile.

Example:
Device(deploy-profile-line-5)# active

Step 8 exit Exits to line profile configuration mode.

Example:
Device(deploy-profile-line-5)# exit

Step 9 delete aim {index_number | name name} (Optional) Deletes the line profile.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# delete aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string.

Step 10 exit Exits to global configuration mode.

Example:
Device(deploy-profile-line)# exit

Configure a Flow Rule

Modifying and activating the line profile causes the ONT that references the template to go online.
To configure a flow rule, perform this procedure.

Configuring Service Profiles

20
 Configuring Service Profiles
Configure a Flow Rule

Before you begin

The ONT should support flow rules. This is applicable for SFU type ONT.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile line Enters line profile configuration mode.

Example:
Device(config)# deploy profile line

Step 4 aim {index_num [name name] | name name} Creates line profile aim.
Example: • index_number: The index of the template. The range
Device(deploy-profile-line)# aim 5 is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string

Step 5 flow flow_id port {eth port_id | veip | iphost } {etype { Creates the transparent flow rule.
ipoe | pppoe | arp}} transparent
• flow_id: The flow ID. The value range is from 0 to
Example: 63.
Device(deploy-profile-line-5)# flow 2 port iphost
etype arp transparent
• port_id: The ONT Ethernet interface ID. The value
range is from 1 to 24.
• ipoe: Ethernet Type 0x0800 packet
• pppoe: Ethernet Type 0x8863 or 0x8864 packet
• arp: Ethernet Type 0x0806 packet

Step 6 flow flow_id port {eth port_id | veip | iphost } {etype { Creates the default VLAN flow rule.
ipoe | pppoe | arp} } default vlan vid [priority]
• flow_id: The flow ID. The value range is from 0 to
Example: 63.
Device(deploy-profile-line-5)# flow 2 port iphost
etype arp default vlan 3
• port_id: The ONT Ethernet interface ID. The value
range is from 1 to 24.
• ipoe: Ethernet Type 0x0800 packet
• pppoe: Ethernet Type 0x8863 or 0x8864 packet
• arp: Ethernet Type 0x0806 packet

Configuring Service Profiles

21
 Configuring Service Profiles
Configure a Flow Rule

Command or Action Purpose

• vlan_id: The VLAN ID. The value range is from 1 to
4094.
• priority: The 802.1P. The value range is from 0 to 7.

Step 7 flow flow_id port {eth port_id | veip | iphost } [etype Creates the keep flow rule.
{ipoe | pppoe | arp} ] vlan vlan_id [priority] keep
• flow_id: The flow ID. The value range is from 0 to
Example: 63.
Device(deploy-profile-line-5)# flow 2 port iphost
etype arp vlan 3 keep
• port_id: The ONT Ethernet interface ID. The value
range is from 1 to 24.
• ipoe: Ethernet Type 0x0800 packet
• pppoe: Ethernet Type 0x8863 or 0x8864 packet
• arp: Ethernet Type 0x0806 packet
• vlan_id: The VLAN ID. The value range is from 1 to
4094.
• priority: The 802.1P. The value range is from 0 to 7.

Step 8 [no] flow flow_id port {eth port_id | veip | iphost } [etype Creates the translate flow rule.
{ipoe | pppoe | arp} ] vlan vid [priority] translate vlan
• flow_id: The flow ID. The value range is from 0 to
vid [priority]
63.
Example:
• port_id: The ONT Ethernet interface ID. The value
Device(deploy-profile-line-5)# flow 2 port iphost
etype arp vlan 3 translate vlan 3
range is from 1 to 24.
• ipoe: Ethernet Type 0x0800 packet
• pppoe: Ethernet Type 0x8863 or 0x8864 packet
• arp: Ethernet Type 0x0806 packet
• vlan_id: The VLAN ID. The value range is from 1 to
4094.
• priority: The 802.1P. The value range is from 0 to 7.

Step 9 active Activates the line profile.

Example:
Device(deploy-profile-line-5)# active

Step 10 exit Exits to line profile configuration mode.

Example:
Device(deploy-profile-line-5)# exit

Step 11 delete aim {index_number | name name} (Optional) Deletes the line profile.
Example:

Configuring Service Profiles

22
 Configuring Service Profiles
Configure a Rule Profile

Command or Action Purpose

Device(deploy-profile-line)# delete aim 5 • index_number: The index of the template. The range
is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name in string.

Configure a Rule Profile

To configure a rule profile, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile rule Enters rule profile configuration mode.

Example:
Device(config)# deploy profile rule

Step 4 aim slot-num/pon-num/ont-num [name name] Creates rule profile aim.

Example: • slot-num/pon-num/ont-num : The ONT ID.
Device(deploy-profile-rule)# aim 0/1/1 • slot-num: The slot number. The value is 0.
• pon-num: The PON number. The range is from
1 to 8.
• ont-num: The ONT number. The range is from
1 to 128.

• name: The profile name, in string format.

Step 5 permit sn {string-hex string_serial_number | hex Creates the serial number permit profile.
hex_serial_number } line {profile_line_list | name name}
• hex_serial_number: The ONT serial number, in hex
default line {index_number | name name}
format.
Example:
• string_serial_number: The ONT serial number, in
Device(deploy-profile-rule-0/1/1)# permit sn
string-hex GPON-1790032e line 1 default line
string format.
1
• index_number: The index of the template. The range
is from 0 to m, where m is the maximum number of
ONTs supported.

Configuring Service Profiles

23
 Configuring Service Profiles
Configure a Rule Profile

Command or Action Purpose

• profile_line_list : The profile line list number.
• name: The profile name, in string format. The string
length is from 1 to 128.

Step 6 permit pw {string string_password | hex hex_password} (Optional) Creates the password permit profile.
line {profile_line_list | name name} {default line
• string_password: The ONT password, in string
{index_num | name name} |once-on {no-aging |
format.
aging-time time} }
Example: • hex_password: The ONT password, in hex format.
Device(deploy-profile-rule-0/1/1)# permit pw • index_number: The index of the template. The range
string-hex GPON-1790032e line 1 default line 1 is from 0 to m, where m is the maximum number of
ONTs supported.
• profile_line_list : The profile line list number.
• name: The profile name, in string format. The string
length is from 1 to 128.

Step 7 permit sn-pw {string-hex string_serial_number | hex (Optional) Creates the serial number and password permit
hex_serial_number} {string string_password | hex profile.
hex_password} line { profile_line_list | name name}
• hex_serial_number: The ONT serial number, in hex
default line {index_num | name name}
format.
Example:
• string_serial_number: The ONT serial number, in
Device(deploy-profile-rule-0/1/1)# permit sn-pw
string-hex GPON-1790032e line 1 default line 1
string format.
• string_password: The ONT password in string format.
• hex_password: The ONT password in hex format.
• index_number: The index of the template. The range
is from 0 to m, where m is the maximum number of
ONTs supported.
• profile_line_list : The profile line list number.
• name: The profile name, in string format. The string
length is from 1 to 128.

Step 8 permit loid loid line {profile_line_list | name name} (Optional) Creates the LOID permit profile.
default line {index_num | name name} |once-on
• loid: The ONT logical ID, in string format. The string
{no-aging | aging-time time} }
length is from 1 to 24.
Example:
• profile_line_list : The profile line list number.
Device(deploy-profile-rule-0/1/1)# permit loid 2
line 4 default line 3 once-on aging 3 • name: The profile name, in string format. The string
length is from 1 to 128.

Configuring Service Profiles

24
 Configuring Service Profiles
Configure a Rule Profile

Command or Action Purpose

• index_number: The index of the template. The range
is from 0 to m, where m is the maximum number of
ONTs supported.
• no-aging : Configures no timeout for discovery mode.
• aging-time time: Configures timeout for discovery
mode, in hours. The range is from 1 to 168.

Step 9 permit lopw logical_password line {profile_line_list | (Optional) Creates the LOID password permit profile.
name name} [default line {index_number | name name}
• logical_password: The ONT password.
|once-on {no-aging | aging-time time} ]
Example: • profile_line_list : The profile line list number.
Device(deploy-profile-rule-0/1/1)# permit lopw • name: The profile name, in string format. The string
password line 4 default line 3 once-on aging 3 length is from 1 to 128.
• index_number: The index of the template. The range
is from 0 to m, where m is the maximum number of
ONTs supported.
• no-aging : Configures no timeout for discovery mode.
• aging-time time: Configures timeout for discovery
mode, in hours. The range is from 1 to 168.

Step 10 permit loid-lopw loid logical_password line (Optional) Creates the LOID and LOID Password permit
{profile_line_list | name name} [default line profile.
{index_number | name name} |once-on {no-aging |
• loid: The ONT logical ID, in string format. The string
aging-time time} ]
length is from 1 to 24.
Example:
• logical_password: The ONT logical password, in
Device(deploy-profile-rule-0/1/1)# permit
loid-lopw 2 password line 4 default line 3 once-on
string format. The string length is from 1 to 12.
aging 3
• profile_line_list: The profile line list number.
• index_number: The index of the template. The range
is from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name, in string format. The string
length is 1 to 128.
• time: The discovery mode timeout time, in hours. The
value range is from 1 to 168.

Step 11 active Activates the rule profile.

Example:
Device(deploy-profile-rule-0/1/1)# active

Configuring Service Profiles

25
 Configuring Service Profiles
Configure a Unique Profile

Command or Action Purpose

Step 12 exit Exits to rule profile configuration mode.
Example:
Device(deploy-profile-rule-0/1/1)# exit

Step 13 delete aim { ont_id_list | name name } (Optional) Deletes the rule profile aim.
Example: • slot-num/pon-num/ont-num: The ONT ID.
Device(deploy-profile-rule)# delete aim 0/1/1 • slot-num: The slot number. The value is 0.
• pon-num: The PON number. The range is from
1 to 8.
• ont-num: The ONT number. The range is from
1 to 128.

• name: The profile name, in string format.

Configure a Unique Profile

To configure a unique profile, perform the following procedures.

Configure an ONT Description

Modifying and activating the unique profile causes the ONT that references the profile to go offline and then
online.
To configure an ONT description, perform this procedure.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile unique Enters unique profile configuration mode.

Example:
Device(config)# deploy profile unique

Step 4 aim slot-num/pon-num/ont-num [name name] Creates unique profile aim.

Example: • slot-num/pon-num/ont-num: The ONT ID.
Device(deploy-profile-unique)# aim 0/1/1 • slot-num: The slot number. The value is 0.

Configuring Service Profiles

26
 Configuring Service Profiles
Configure a GEM Port Profile

Command or Action Purpose

• pon-num: The PON number. The range is from
1 to 8.
• ont-num: The ONT number. The range is from 1
to 128.

• name: The profile name, in string format.

Step 5 [no] description description Configures the ONT description

Example: description: ONT description. The length of the description
Device(deploy-profile-unique-0/1/1)# description is from 1 to 128.
cisco
Use the no description command to delete the ONT
description.

Step 6 ip-config mode{dhcp vlan vlan_id {vlan_priority | host Configures the IP configuration as static or DHCP.
} | static ip_address}
Note This command is applicable to an ONT device
Example: that operates in the Single Family Unit (SFU)
Device(deploy-profile-unique-0/1/1)# ip-config mode mode.
dhcp vlan 4093 host 2

Step 7 active Activates the unique profile

Example:
Device(deploy-profile-unique-0/1/1)# active

Step 8 exit Exits to line profile configuration mode.

Example:
Device(deploy-profile-unique-0/1/1)# exit

Step 9 delete aim { ont_id_list | name name } (Optional) Deletes the unique profile.
Example: • slot-num/pon-num/ont-num: The ONT ID.
Device(deploy-profile-unique)# delete aim 0/1/1 • slot-num: The slot number. The value is 0.
• pon-num: The PON number. The range is from
1 to 8.
• ont-num: The ONT number. The range is from 1
to 128.

• name: The profile name, in string format.

Configure a GEM Port Profile

Modifying and activating the unique profile causes the ONT that references the profile to go offline and then
online.
To configure a GEM port profile, perform this procedure.

Configuring Service Profiles

27
 Configuring Service Profiles
Configure a GEM Port Profile

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile unique Enters unique profile configuration mode.

Example:
Device(config)# deploy profile unique

Step 4 aim slot-num/pon-num/ont-num [name name] Creates unique profile aim.

Example: • slot-num/pon-num/ont-num: The ONT ID.
Device(deploy-profile-unique)# aim 0/1/1 • slot-num: The slot number. The value is 0.
• pon-num: The PON number. The range is from
1 to 8.
• ont-num: The ONT number. The range is from 1
to 128.

• name: The profile name, in string format.

Step 5 [no] gemport gem_index {vlan-profile |us-traffic-profile Configures the GEM port profile.
| ds-traffice-profile } { index_num | name name }
• gem_index: The GEM port index. The range is from
Example: 1 to 1024.
Device(deploy-profile-unique-0/1/1))# gemport 2
vlan-profile 2
• index_num: The index of the template. The range is
from 0 to m, where m is the maximum number of
ONTs supported.
• name: The profile name, in string format. The string
length is from 1 to 128.

Use the no gemport gem_index to delete the GEM port

profile.

Step 6 active Activates the unique profile.

Example:
Device(deploy-profile-unique-0/1/1))# active

Step 7 exit Exits to line profile configuration mode.

Example:
Device(deploy-profile-unique-0/1/1)# exit

Configuring Service Profiles

28
 Configuring Service Profiles
Configure a SIP

Command or Action Purpose

Step 8 delete aim {slot-num/pon-num/ont-num | name name} (Optional) Deletes the unique profile.
Example: • slot-num/pon-num/ont-num: The ONT ID.
Device(deploy-profile-unique))# delete aim 0/1/1 • slot-num: The slot number. The value is 0.
• pon-num: The PON number. The range is from
1 to 8.
• ont-num: The ONT number. The range is from 1
to 128.

• name: The profile name, in string format.

Configure a SIP
Modifying and activating the unique profile causes the ONT that references the profile to go offline and then
online.
To configure a SIP, perform this procedure.

Before you begin

The ONT should support SIP settings. This is applicable for SFU type ONT.

Procedure

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: Enter your password, if prompted.
Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:
Device# configure terminal

Step 3 deploy profile unique Enters unique profile configuration mode.

Example:
Device(config)# deploy profile unique

Step 4 aim slot-num/pon-num/ont-num [name name] Creates unique profile aim.

Example: • slot-num/pon-num/ont-num: The ONT ID.
Device(deploy-profile-unique)# aim 0/1/1 • slot-num: The slot number. The value is 0.
• pon-num: The PON number. The range is from
1 to 8.
• ont-num: The ONT number. The range is from
1 to 128.

Configuring Service Profiles

29
 Configuring Service Profiles
Configure a SIP

Command or Action Purpose

• name: The profile name, in string format.

Step 5 [no] sip agent proxy-server uri {outbound-proxy Configures the SIP proxy server.
|registrar-server |signal-port }proxy_server_uri]
proxy-server uri: The proxy server universal resource
Example: identifier (UNI). The length is from 1 to 64.
Device(deploy-profile-unique-0/1/1)# sip agent Use the no sip agent command to delete the SIP agent.
proxy-server 2

Step 6 [no] sip user mode {static ip-address ip mask ip_mask Configures the SIP interface.
gateway ip primary-dns ip secondary-dns ip|dhcp vlan
• ip: The IP address
vlan_idpriority host host_id}
Example: • ip_mask: The IP network mask
Device(deploy-profile-unique-0/1/1)# sip usr mode • vlan_id: The VLAN ID. The value range is from 1 to
dhcp vlan 2 4 host 1 4094.
• priority: The value range is from 0 to 7.
• host_id: The IP host ID. The value is 1.

Use the no sip user mode command to delete the SIP

interface.

Step 7 [no] sip user pots_number{name username password Configures the SIP user.
password |telno phone_num}
• pots_number: The ONT POTS port number. The
Example: value range is from 1 to 2
Device(deploy-profile-unique-0/1/1)# sip user 2
name user 1 password 123
• username: The SIP username., The username length
is from 1 to 25.
• password: The SIP username. The password length
is from 1 to 25
• phone_num: The ONT local phone number. The digit
length is from 1 to 25.

Use the no sip user user_id command to delete the SIP

user.

Step 8 sip digitmap dial-plan-id dial_plan_id dial-plan-token Configures the SIP digit map.
token
• dial_plan_id: The digit map index. The range is from
Example: 1 to 10.
Device(deploy-profile-unique-0/1/1)# sip digitmap
dial-plan-id 2 dial-plan-token 3
• token: The digit map content.

Use the no sip digitmap dial-plan-id id command to

delete the SIP digit map.

Step 9 active Activates the unique profile.

Example:
Device(deploy-profile-unique-0/1/1)# active

Configuring Service Profiles

30
 Configuring Service Profiles
Configure a SIP

Command or Action Purpose

Step 10 exit Exits to line profile configuration mode.
Example:
Device(deploy-profile-unique-0/1/1)# exit

Step 11 delete aim {slot-num/pon-num/ont-num | name name} (Optional) Deletes the unique profile.
Example: • slot-num/pon-num/ont-num: The ONT ID.
Device(deploy-profile-unique)# delete aim 0/1/1 • slot-num: The slot number. The value is 0.
• pon-num: The PON number. The range is from
1 to 8.
• ont-num: The ONT number. The range is from
1 to 128.

• name: The profile name, in string format.

Configuring Service Profiles

31
 Configuring Service Profiles
Configure a SIP

Configuring Service Profiles

32