2014年7月29日星期二

Configuring IPv6 Services in the FTTH (Bridging ONT) Scenario

This section describes the methods for configuring IPv6 services in the FTTH (bridging ONT) scenario.

Now, our supplier - Hunetwork can provide the devices which support the FTTH solution, such as: HG8245, HG8010, MA5683T...  and provides the technology of the FTTH solution,  also provides remote testing of the products in our laboratory for that you can understand the function of our product clearly.

Application Scenarios
The FTTH (bridging ONT) supports multiple IPv6 HSI and IPTV service schemes.

FTTH (Bridging ONT) Application Scenario
As shown in Figure 1, the FTTH (bridging ONT) works with upper-layer devices to support
DS+NAT+PPPoE/DS+NAT+IPoE HSI and DS+IPoE or DS+PPPoE IPTV services in the
Huawei fixed network IPv6 solution.
  •  For the voice service: An ONT with a bulit-in voice module can directly provide VoIP services for users. The ONT still processes VoIP services using IPv4.
  • Internet service: The PC and BRAS support the IPv4/IPv6 dual-stack, and can be connected through the PPPoE or IPoE dial-up. The OLT and ONT perform Layer 2 forwarding for both IPv4 and IPv6 user services, which can be configured almost in the same way. The only difference is that commands for configuring the ACL and security (DHCP option and anti-IP spoofing) features are different.
  •  IPTV service: STBs support IPv4/IPv6 dual-stack and carry IPTV services using either IPv4 or IPv6.
– When STBs use IPoE and the OLT functions as the multicast duplication point, the process for configuring IPv6 and IPv4 multicast services is the same, but commands
are different. The ONTs perform Layer 2 forwarding for only IPTV services, and the
configurations for IPv6 and IPv4 multicast services are the same on the ONT side.

– When STBs use the PPPoE dial-up, they directly connect to the BRAS by PPPoE. The
OLT and ONTs only forward PPPoE services instead of processing multicast services.
This solution is not recommended.

Figure 1 FTTH (bridging ONT) service networking
 fttb solution 1

FTTH (Bridging ONT) Configuration Procedure
After IPv6 is introduced to the FTTH (bridging ONT) scenario, the service configuration
procedure is as shown in the following figure. When IPv6 is introduced, the configurations for security features and BTV multicast services on the OLT side are different from those of IPv4. Other configurations do not change.
 fttb solution 2
NOTE
Texts in blue show the configuration difference between IPv6 and IPv4.

Procedure

Step 1 Configure LAG for upstream ports.
Configure upstream ports 0/19/0 and 0/19/1 into an aggregation group. Each member port in the aggregation group allocates packets based on the source MAC address. The working mode is LACP static aggregation.
huawei(config)#link-aggregation 0/19 0-1 ingress workmode lacp-static

Step 2 Configure GPON ONT profiles.
  1. Configure a DBA profile.
Create the same DBA profile for different types of services. Set the profile name to
ftth_dba, profile type to type3, assured bandwidth to 8 Mbit/s, and maximum bandwidth
to 20 Mbit/s.
huawei(config)#dba-profile add profile-name ftth_dba type3 assure 8192 max 20480

2. Configure an ONT line profile.
Create a GPON ONT line profile, named ftth, and bind it to the DBA profile ftth_dba.
huawei(config)#ont-lineprofile gpon profile-name ftth
huawei(config-gpon-lineprofile-1)#tcont 4 dba-profile-name ftth_dba
huawei(config-gpon-lineprofile-1)#gem add 11 eth tcont 4
huawei(config-gpon-lineprofile-1)#gem add 12 eth tcont 4
huawei(config-gpon-lineprofile-1)#gem add 13 eth tcont 4
huawei(config-gpon-lineprofile-1)#gem add 14 eth tcont 4
huawei(config-gpon-lineprofile-1)#commit
huawei(config-gpon-lineprofile-1)#quit

3. Configure an ONT service profile.
Create a GPON ONT service profile, named ftth. Configure the capability set of the ETH
port and POTS port to adaptive. Then the system automatically adapts to the ONT
according to the actual capability of the online ONT.
huawei(config)#ont-srvprofile gpon profile-name ftth
huawei(config-gpon-srvprofile-1)#ont-port eth adaptive pots adaptive
huawei(config-gpon-srvprofile-1)#commit
huawei(config-gpon-srvprofile-1)#quit

4. (Optional) Add an alarm profile. In this example, the default alarm profile is used, and
therefore the configuration of the alarm profile is not required.

Step 3 Add ONTs.
Connect two ONTs to GPON port 0/1/0. Set the ONT IDs to 1 and 2, SNs to
32303131D659FD40 and 6877687714852901, passwords to 0100000001 and 0100000002, discovery mode for password authentication to once-on, and management mode to OMCI. Bind the two ONTs to ONT line profile ftth and ONT service profile ftth.
There are two methods of adding an ONT: add an ONT offline and confirm an automatically discovered ONT.

  •  Add ONTs offline.
If the password of an ONT is known, run the ont add command to add an ONT offline.
huawei(config)#interface gpon 0/1
huawei(config-if-gpon-0/1)#ont add 0 1 password-auth 0100000001 once-on no-aging
omci ont-lineprofile-name
ftth ont-srvprofile-name ftth
huawei(config-if-gpon-0/1)#ont add 0 2 password-auth 0100000002 once-on no-aging
omci ont-lineprofile-name
ftth ont-srvprofile-name ftth

  •  Confirm automatically discovered ONTs
If the password or SN of an ONT is unknown, run the port portid ont-auto-find command
in GPON mode to enable the ONT auto-discovery function of the GPON port. Then, run the ont confirm command to confirm the ONT.
huawei(config)#interface gpon 0/1
huawei(config-if-gpon-0/1)#port 0 ont-auto-find enable
huawei(config-if-gpon-0/1)#display ont autofind 0
//After this command is executed, the information about all ONTs connected to
the GPON port through optical splitters is displayed.
huawei(config-if-gpon-0/1)#ont confirm 0 ontid 1 sn-auth 32303131D659FD40 omci
ont-lineprofile-name
ftth ont-srvprofile-name ftth

huawei(config-if-gpon-0/1)#ont confirm 0 ontid 2 sn-auth 6877687714852901 omci
ont-lineprofile-name
ftth ont-srvprofile-name ftth

NOTE
If multiple ONTs of the same type bound to the same line profile or service profile are connected to the same port, you can bulk add ONTs by bulk confirming automatically discovered ONTs to make configuration easier and more efficient. To do so, the preceding command can be modified as follows:
huawei(config-if-gpon-0/1)#ont confirm 0 all sn-auth omci ont-lineprofile-name
ftth ont-srvprofile-name ftth

  • (Optional) Bind the alarm profile to the ONT.
The default profile 1 is used in this example.
huawei(config-if-gpon-0/1)#ont alarm-profile 0 1 profile-id 1
huawei(config-if-gpon-0/1)#ont alarm-profile 0 2 profile-id 1

Step 4 Check ONT status.
After an ONT is added, run the display ont info command to query the current status of the ONT. Ensure that Config flag of the ONT is active, Run State is online, Config state is normal, and Match state is match.
huawei(config-if-gpon-0/1)#display ont info 0 1
---------------------------------------------------------------------
F/S/P : 0/1/0
ONT-ID : 1
Control flag : active //Indicates that the ONT is
activated.
Run state : online //Indicates that the ONT goes online
successfully.
Config state : normal //Indicates that the configuration state of the
ONT is normal.
Match state : match //Indicates that the capability profile bound to
the ONT is consistent with the actual capability of the ONT.
...//The rest of the response information is omitted.
When Config state is failed, Run state is offline, or Match state is mismatch:
  • If Control flag is deactive, run the ont active command in GPON mode to activate the ONU.
  • If Run state is offline, a physical line may be broken or the optical module may be damaged.

Check the line and the optical module.
  • If Config state is failed, the configured ONU capability exceeds the actual ONU capability.
In this case, run the display ont failed-configuration command in the diagnose mode to
check the failed configuration item and the failure cause. Then, rectify the fault accordingly.
  •   If the ONU does not match, that is, Match state is mismatch, the port types and number of ports undermatch the actual port types and number of ports supported by the ONU. In this case, run the display ont capability command to query the actual capability of the ONU, and then select one of the following modes to modify the ONU configuration:
– Create a proper ONU profile according to the actual capability of the ONU, and then run
the ont modify command to modify the configuration data of the ONU.

– Modify the ONU profile according to the actual capability of the ONU and save the
modification. Then, the ONU automatically recovers the configuration successfully.

Step 5 Configure the traffic profile for the HSI service.
huawei(config)#traffic table ip name ftth_hsi cir 4096 priority 0 priority-policy
local-setting

Step 6 Configure the service port for the HSI service.
Table 1  Scenario plan
 fttb solution 3

  • Scenario 1:
Configure the mapping between a GEM port and a VLAN. The service flow of C-VLAN
1001 is mapped to GEM port 14 in the ONT line profile.
huawei(config)#ont-lineprofile gpon profile-name ftth
huawei(config-gpon-lineprofile-1)#gem mapping 14 0 vlan 1001
huawei(config-gpon-lineprofile-1)#commit
huawei(config-gpon-lineprofile-1)#quit
Configure the VLAN of the Ethernet port on the ONT. If the ONT is connected to the PC
through Ethernet port 1, add Ethernet port 1 to VLAN 1001 in the ONT service profile.
huawei(config)#ont-srvprofile gpon profile-name ftth
huawei(config-gpon-srvprofile-1)#port vlan eth 1 1001
huawei(config-gpon-srvprofile-1)#commit
huawei(config-gpon-srvprofile-1)#quit
Configure the native VLAN of the ONT port. Set the native VLAN ID of Ethernet port 1 to 1001.

huawei(config)#interface gpon 0/1
huawei(config-if-gpon-0/1)#ont port native-vlan 0 1 eth 1 vlan 1001
huawei(config-if-gpon-0/1)#ont port native-vlan 0 2 eth 1 vlan 1001
huawei(config-if-gpon-0/1)#quit
Create an Internet access service VLAN and add an upstream port to it. Add upstream port 0/19/0 to VLAN 100.
huawei(config)#vlan 100 smart
huawei(config)#vlan attrib 100 stacking
huawei(config)#port vlan 100 0/19 0
Create service flows. Set the service VLAN to 100, GEM port ID to 14, and user VLAN to
1001. Use traffic profile ftth_hsi.

huawei(config)#service-port vlan 100 gpon 0/1/0 ont 1 gemport 14 multi-service
user-vlan 1001 tag-transform translate-and-add inner-vlan 1010 inbound traffic- table name ftth_hsi outbound traffic-table name ftth_hsi

huawei(config)#service-port vlan 100 gpon 0/1/0 ont 2 gemport 14 multi-service
user-vlan 1001 tag-transform translate-and-add inner-vlan 1011 inbound traffictable
name ftth_hsi outbound traffic-table name ftth_hsi

  • Scenario 2:
Configure the mapping between a GEM port and an Ethernet port on the ONT. Map the
service flow of Ethernet port 1 to GEM port 14 in the ONT line profile.
huawei(config)#ont-lineprofile gpon profile-name ftth
huawei(config-gpon-lineprofile-1)#mapping mode port
huawei(config-gpon-lineprofile-1)#gem mapping 14 0 eth 1
huawei(config-gpon-lineprofile-1)#commit
huawei(config-gpon-lineprofile-1)#quit
Configure the ONT packet processing mode. If the ONT is connected to the PC through
Ethernet port 1, In the ONT service profile, set the packet transmission mode to TAG
transparent transmission for Ethernet port 1.

huawei(config)#ont-srvprofile gpon profile-name ftth
huawei(config-gpon-srvprofile-1)#port vlan eth 1 transparent
huawei(config-gpon-srvprofile-1)#commit
huawei(config-gpon-srvprofile-1)#quit
Create an Internet access service VLAN and add an upstream port to it. Add upstream port 0/19/0 to VLAN 100.
huawei(config)#vlan 100 smart
huawei(config)#vlan attrib 100 stacking
huawei(config)#port vlan 100 0/19 0
Create service flows. Set S-VLAN ID to 100 and GEM port ID to 14. Use traffic profile
ftth_hsi.

huawei(config)#service-port vlan 100 gpon 0/1/0 ont 1 gemport 14 multi-service
user-vlan untagged tag-transform add-double inner-vlan 1001 inbound traffictable
name ftth_hsi outbound traffic-table name ftth_hsi
huawei(config)#service-port vlan 100 gpon 0/1/0 ont 2 gemport 14 multi-service
user-vlan untagged tag-transform add-double inner-vlan 1002 inbound traffictable
name ftth_hsi outbound traffic-table name ftth_hsi

Step 7 Configure the traffic profile for the voice service.
huawei(config)#traffic table ip name ftth_voip cir off priority 5 priority-policy
local-setting

Step 8 Configure the VLAN translation policy and service flows for the voice service.
1. Perform this step in the bridging ONT (single VLAN tag) scenario.
Table 2  Data plan
 fttb solution 4

Configure the mapping relationship between a GEM port and a VLAN. The service flow
of user VLAN 300 is mapped to GEM port 12 in the ONT line profile.

huawei(config)#ont-lineprofile gpon profile-name ftth
huawei(config-gpon-lineprofile-1)#gem mapping 12 2 vlan 300
huawei(config-gpon-lineprofile-1)#commit
huawei(config-gpon-lineprofile-1)#quit
Create a service VLAN and add an upstream port to it. Add upstream port 0/19/0 to VLAN
300.

huawei(config)#vlan 300 smart
huawei(config)#port vlan 300 0/19 0
Create service flows. Set the service VLAN to 300, GEM port ID to 12, and user VLAN
to 300, and use traffic profile ftth_voip.
huawei(config)#service-port vlan 300 gpon 0/1/0 ont 1 gemport 12 multi-service
user-vlan 300 inbound traffic-table name ftth_voip outbound traffic-table
name ftth_voip

huawei(config)#service-port vlan 300 gpon 0/1/0 ont 2 gemport 12 multi-service
user-vlan 300 inbound traffic-table name ftth_voip outbound traffic-table
name ftth_voip

2. Perform this step in the bridging ONT (double VLAN tags) scenario.
Table 3 Data plan
 fttb solution 5

Configure the mapping relationship between a GEM port and a VLAN. The service flow
of user VLAN 3001 is mapped to GEM port 12 in the ONT line profile.
huawei(config)#ont-lineprofile gpon profile-name ftth
huawei(config-gpon-lineprofile-1)#gem mapping 12 2 vlan 3001
huawei(config-gpon-lineprofile-1)#commit
huawei(config-gpon-lineprofile-1)#quit
Create a service VLAN and add an upstream port to it. Add upstream port 0/19/0 to VLAN
300.

huawei(config)#vlan 300 smart
huawei(config)#vlan attrib 300 stacking
huawei(config)#port vlan 300 0/19 0
Create service flows. Set the service VLAN to 300, GEM port ID to 12, and user VLAN
to 3001, and use traffic profile ftth_voip.
huawei(config)#service-port vlan 300 gpon 0/1/0 ont 1 gemport 12 multiservice
user-vlan 3001 tag-transform default inbound traffic-table name ftth_voip
outbound traffic-table name ftth_voip

huawei(config)#service-port vlan 300 gpon 0/1/0 ont 2 gemport 12 multiservice
user-vlan 3001 tag-transform default inbound traffic-table name ftth_voip
outbound traffic-table name ftth_voip

Step 9 Configure ONT voice service profiles.
ONT voice service profiles include the interface common profile, MGC interface profile, and POTS port profile.
  •  Interface common profile: saves common attributes of an ONT voice interface, including the fax mode, fax/modem negotiation mode, and priority of the coding and decoding mode.
  • MGC interface profile: saves the IP address or domain name of the MGC, protocol port ID of the MGC transport layer to which the MG interface belongs, and DSCP priority of media packets.
  • POTS port profile: saves physical attributes of a POTS port on an ONT, including the
impedance, transmitting gain, receiving gain, and signaling type of the POTS port.

1. Configure an interface common profile.
Run the display ont-mg-attribute-profile command to query the existing interface
common profile in the system. If the existing interface common profile in the system does
not meet the requirements, run the ont-mg-attribute-profile add command to add an
interface common profile.

In this example, the default interface common profile, namely interface common profile 1
is used.

2. Configure an MGC interface profile.
Run the display ont-mgc-profile command to query the existing MGC interface profile in
the system. If the existing MGC interface profile in the system does not meet the
requirements, run the ont-mgc-profile add command to add an MGC interface profile.
Create MGC interface profile 2, set the IP address of the MGC to 200.200.200.200, and
use default values for other parameters.

huawei(config)#ont-mgc-profile add profile-id 2 primary-mgc 200.200.200.200

3. Configure a POTS port profile.
Run the display ont-pots-profile command to query the existing POTS port profile in the
system. If the existing POTS port profile in the system does not meet the requirements, run the ont-pots-profile add command to add a POTS port profile.

In this example, the default POTS port profile, namely POTS port profile 1 is used.

Step 10 Configure the IP addresses of ONT H.248 users.
For ONT 1 and ONT 2, configure the IP address obtaining mode to the dhcp mode, set the
management VLAN to VLAN 20, and use default values for other parameters.
huawei(config)#interface gpon 0/1
huawei(config-if-gpon-0/1)#ont ipconfig 0 1 dhcp vlan 20
huawei(config-if-gpon-0/1)#ont ipconfig 0 2 dhcp vlan 20

Step 11 Configure H.248 PSTN users.
1. Add an H.248 interface and apply an MGC interface profile to the interface.
For ONT 1 and ONT 2, set the MG ID to 1, apply MGC interface profile 2 to ONT 1 and
ONT 2, and use default values for other parameters.

If parameters of an MGC interface profile are changed, the MGC interface profile must be
reapplied to the ONT so that the changed parameters can take effect.
huawei(config-if-gpon-0/1)#if-h248 add 0 1 1 mgc-profile profile-id 2
huawei(config-if-gpon-0/1)#if-h248 add 0 2 1 mgc-profile profile-id 2

  1. Add PSTN users.

For ONT 1 and ONT 2, create a PSTN user, set the MG ID to 1 (identical to the MG ID of
the H.248 interface), and set the physical terminal port ID to A0 and A1.
huawei(config-if-gpon-0/1)#mgpstnuser add 0 1 1 mgid 1 terminalid A0
huawei(config-if-gpon-0/1)#mgpstnuser add 0 2 1 mgid 1 terminalid A1

Run the display mgpstnuser attribute command to check whether the configuration of
the PSTN user is properly set.
huawei(config-if-gpon-0/1)#display mgpstnuser attribute 0 1 1
------------------------------------------------------------------------------
F/S/P : 0/1/0
ONT ID : 1
Port ID : 1
MG ID : 1
Terminal ID : A0
...//The rest of the response information is omitted.
huawei(config-if-gpon-0/1)#display mgpstnuser attribute 0 2 1
------------------------------------------------------------------------------
F/S/P : 0/1/0
ONT ID : 2
Port ID : 1
MG ID : 1
Terminal ID : A1
...//The rest of the response information is omitted.

Step 12 Apply ONT voice service profiles
After ONT voice service profiles are applied, if parameters in those profiles are changed, those profiles must be reapplied so that the changed parameters can take effect.

1. Apply an interface common profile.
Run the if-h248 attribute command to apply an interface common profile to an H.248
interface or configure the interface customized parameters, or run the ont-if-h248 batapply command to bulk apply the interface common profiles to H.248 interfaces. If you
use these two commands to apply the interface common profiles or configure the interface
customized parameters repeatedly, the last configurations take effect.
In this example, the default interface common profile, namely interface common profile 1
is used.

2. Apply a POTS port profile.
Run the pstnport electric command to apply a POTS port profile to an H.248 interface or
configure the interface customized parameters, or run the ont-pstnport electric batapply
command to bulk apply the POTS port profiles to H.248 interfaces. If you use these
two commands to apply the POTS port profiles or configure the interface customized
parameters repeatedly, the last configurations take effect.

In this example, the default POTS port profile, namely POTS port profile 1 is used.

Step 13 (Optional) Configure the H.248 user codec.
Run the mgpstnuser codec command to configure the H.248 user codec. The H.248 user codec will not be configured independently in this example.

Step 14 Configure the traffic profile for the IPTV service.
huawei(config)#traffic table ip index 8 cir off priority 4 priority-policy
local-setting

Step 15 Configure the VLAN translation policy and service port for the multicast service.

Configure the mapping relationship between a GEM port and an Ethernet port on the ONT. If the ONT is connected to the STB through Ethernet port 2, map the service flow of Ethernet port 2 to GEM port 13 in the ONT line profile.
huawei(config)#ont-lineprofile gpon profile-name ftth
huawei(config-gpon-lineprofile-1)#mapping mode port
huawei(config-gpon-lineprofile-1)#gem mapping 13 1 eth 2
huawei(config-gpon-lineprofile-1)#commit
huawei(config-gpon-lineprofile-1)#quit

Configure the VLAN of the Ethernet port on the ONT. If the ONT is connected to the STB
through Ethernet port 2, add Ethernet port 2 to VLAN 1000.
huawei(config)#ont-srvprofile gpon profile-name ftth
huawei(config-gpon-srvprofile-1)#port vlan eth 2 1000
huawei(config-gpon-srvprofile-1)#multicast-forward untag
huawei(config-gpon-srvprofile-1)#commit
huawei(config-gpon-srvprofile-1)#quit

Configure the native VLAN of the ONT port. If the ONT is connected to the STB through
Ethernet port 2, the native VLAN ID is 1000.
huawei(config)#interface gpon 0/1
huawei(config-if-gpon-0/1)#ont port native-vlan 0 1 eth 2 vlan 1000
huawei(config-if-gpon-0/1)#ont port native-vlan 0 2 eth 2 vlan 1000
huawei(config-if-gpon-0/1)#quit

Create a service VLAN and add an upstream port to it. Add upstream port 0/19/0 to VLAN 1000.
huawei(config)#vlan 1000 smart
huawei(config)#port vlan 1000 0/19 0

Create service flows. Set the service VLAN to 1000, GEM port ID to 13, and user VLAN to
untagged, and use traffic profile 8.
huawei(config)#service-port 1 vlan 1000 gpon 0/1/0 ont 1 gemport 13 multi-service
user-vlan untagged rx-cttr 8 tx-cttr 8
huawei(config)#service-port 2 vlan 1000 gpon 0/1/0 ont 2 gemport 13 multi-service
user-vlan untagged rx-cttr 8 tx-cttr 8

Step 16 Create an MVLAN and configure the IGMP version.
Set the IGMP version for the MVLAN to IGMP IPv6 v2.
huawei(config)#multicast-vlan 1000
huawei(config-mvlan1000)#igmp ipv6 version v2

This operation will delete all IPv6 programs with source IP addresses in the
current multicast VLAN

Are you sure to change current IGMP IPv6 version? (y/n)[n]:y
Command is being executed. Please wait...
Command has been executed successfully

Step 17 Configure a program library.
Set the mode for obtaining multicast programs to dynamic.

NOTE
You can set the mode for obtaining multicast programs to dynamic only when the IGMP mode is off.

huawei(config-mvlan1000)#igmp ipv6 mode off
Are you sure to close IGMP IPv6? (y/n)[n]:y
Command is being executed. Please wait...
Command has been executed successfully
huawei(config-mvlan1000)#igmp ipv6 match mode disable
Command has been executed successfully


(Optional) Set the address range for the dynamic programs. If you need to limit the address range of dynamic programs, perform this operation. For example, set the address range of dynamic programs to ff15::-ff15::ffff.
huawei(config-mvlan1000)#igmp ipv6 match group ipv6 ff15:: to-ipv6 ff15::ffff

Step 18 Set the IGMP IPv6 mode.
Select the IGMP IPv6 proxy mode.
huawei(config-mvlan1000)#igmp ipv6 mode proxy
Are you sure to change IGMP IPv6 mode? (y/n)[n]:y
Command is being executed. Please wait...
Command has been executed successfully

Step 19 Configure the IGMP upstream port.
Set the IGMP upstream port ID to 0/19/0 and working mode to default. Protocol packets are transmitted to all the IGMP upstream ports in the multicast VLAN.
huawei(config-mvlan1000)#igmp uplink-port 0/19/0
huawei(config-mvlan1000)#btv
huawei(config-btv)#igmp uplink-port-mode default
Are you sure to change the uplink port mode?(y/n)[n]:y

Step 20 Configure multicast users.
Add service ports 1 and 2 as multicast users.
huawei(config-btv)#igmp policy service-port 1 normal
huawei(config-btv)#igmp policy service-port 2 normal
huawei(config-btv)#igmp user add service-port 1
huawei(config-btv)#igmp user add service-port 2
huawei(config-btv)#multicast-vlan 1000
huawei(config-mvlan1000)#igmp multicast-vlan member service-port 1
huawei(config-mvlan1000)#igmp multicast-vlan member service-port 2
huawei(config-mvlan1000)#quit

Step 21 Configure the traffic profile for the VoD service.
huawei(config)#traffic table ip index 8 cir off priority 4 priority-policy
local-setting

Step 22 Configure the VLAN translation policy and service port for the VoD service.

Configure the mapping relationship between a GEM port and a VLAN. The service flow of user VLAN 1100 is mapped to GEM port 13 in the ONT line profile.
huawei(config)#ont-lineprofile gpon profile-name ftth
huawei(config-gpon-lineprofile-1)#gem mapping 13 4 vlan 1100
huawei(config-gpon-lineprofile-1)#commit
huawei(config-gpon-lineprofile-1)#quit

Configure the VLAN of the Ethernet port on the ONT. If the ONT is connected to the STB
through Ethernet port 2, add Ethernet port 2 to VLAN 1100.
huawei(config)#ont-srvprofile gpon profile-name ftth
huawei(config-gpon-srvprofile-1)#port vlan eth 2 1100
huawei(config-gpon-srvprofile-1)#commit
huawei(config-gpon-srvprofile-1)#quit

Configure the native VLAN of the ONT port. If the ONT is connected to the STB through
Ethernet port 2, the native VLAN ID is 1100.
huawei(config-if-gpon-0/1)#ont port native-vlan 0 1 eth 2 vlan 1100
huawei(config-if-gpon-0/1)#ont port native-vlan 0 2 eth 2 vlan 1100
huawei(config-if-gpon-0/1)#quit

Create a service VLAN and add an upstream port to it. Add upstream port 0/19/0 to VLAN 1100.
huawei(config)#vlan 1100 smart
huawei(config)#port vlan 1100 0/19 0

Create service flows. Set the service VLAN to 1100, GEM port ID to 13, and VLAN translation mode to transparent transmission, and use traffic profile 8.
huawei(config)#service-port 3 vlan 1100 gpon 0/1/0 ont 1 gemport 13 rx-cttr 8 txcttr
8 tag-transform transparent
huawei(config)#service-port 4 vlan 1100 gpon 0/1/0 ont 2 gemport 13 rx-cttr 8 txcttr
8 tag-transform transparent

Step 23 (Optional) Configure the PITP function for PPPoE.
huawei(config)#raio-mode common pitp-pmode
huawei(config)#pitp enable pmode

Step 24 (Optional) Configure the DHCP option function for IPoE.
huawei(config)#raio-mode common dhcp-option82 //For DHCPv4 packets
huawei(config)#dhcp option82 enable //For DHCPv4 packets
huawei(config)#raio-mode common dhcpv6-option //For DHCPv6 packets
huawei(config)#dhcpv6 option enable //For DHCPv6 packets

Step 25 Save the configuration on the OLT side.
huawei(config)#save
----End

More related:
How to Configure IPv6 Services in the FTTB+HGW Scenario
How to Configure IPv6 Services in the FTTB/C (No HGWs) Scenario
Configuration Difference Between IPv6 and IPv4
How to Add and Delete ONT on the OLT Device
ADSL2+ Dependency Feature and Limitation of MA5600T and MA5603T
MA5600T&5603T ADSL2+ Service Board Specifications
MA5680T Vs MA5683T : A Distinct Comparison

2014年7月28日星期一

Error 676 Occasionally Occurs in PPPoE Dialup



How to troubleshoot the fault when error 676 occasionally occurs in Point-to-Point Protocol over Ethernet (PPPoE) dialup. Here is the solution:

Fault Description

Network topology: ONU -> optical line terminal (Huawei OLT) -> switch -> broadband remote access server (BRAS)
An ONU user occasionally encounters error 676 in PPPoE dialup. In addition, the fault duration varies.

Possible Causes
  • An ONU user forges the MAC address of the BRAS.
  • An OLT user forges the MAC address of the BRAS.
  • The configuration of the BRAS or remote authentication dial in user service (RADIUS) is incorrect.
  • A VLAN conflict occurs.
Procedure
  1. Run the security mac-filter command to configure MAC address filtering on the ONU, which prevents the MAC address of the BRAS from being forged. The fault persists.
  2. Run the security mac-filter command to configure MAC address filtering on the OLT. The fault persists.
  3. Check the configurations of the BRAS and RADIUS. The configurations are correct. Check the VLAN configurations on the upper-layer aggregation switch and OLT. The VLAN configurations are correct.
  4. When an ONU user in VLAN A encounters error 676, another user in the same VLAN is already online on the BRAS. Therefore, it is determined that a VLAN conflict occurs on the BRAS. The maximum number of concurrent online users configured on the BRAS is 1 in PPPoE dialup. Therefore, if a user is online in the VLAN with conflicts, error 676 occurs with other users of the same VLAN in PPPoE dialup.
  5. Query the configurations of all ONUs connected to the OLT. It is found that VLANs have the same outer VLAN tags and the same inner VLAN tags. Modify the VLAN settings so that they have different outer tags and different inner tags. Then, the fault is rectified.
Suggestions and Summary

Properly plan VLANs for the PON ports on an OLT. It is suggested to configure an outer VLAN tag for each PON port. In such a manner, the fault location scope is minimized even when an inner VLAN conflict occurs.

The more information about technical support you can consult with our technician - Bill, and his e-mail address is as below:  

More related topics

2014年7月25日星期五

How to Troubleshoot Internet Access Failures



How to troubleshoot Internet access failures encountered by some Point-to-Point Protocol over Ethernet (PPPoE) users connected to an optical network unit (ONU). The fault is caused by subscriber line interference.

Fault Description
Error 678 occasionally occurs when PPPoE users connected to an ONU perform dialup for Internet access. The service can be temporarily restored after the user ports or the ONU is reset. However, the fault recurs after the device runs for a period of time.
No control board fault, reset, or loss of signal (LoS) alarms are generated on the ONU.

NOTE:
Card-type ONU devices, such as the MA5616 and the MA5612, support EIUA and EIUC service boards to provide fast Ethernet (FE) user ports.

Alarm Information
FE ports report port up and port down alarms.

Possible Causes
  • The control board is faulty.
  • The uplink port is faulty.
  • The upstream optical fiber is disconnected.
  • The EIUA board is faulty.
  • The subscriber line is faulty.
Procedure
  1. Log in to the ONU remotely to check the running status of the device. It is found that the ONU is running properly without having reset repeatedly. This indicates that the control board, uplink port, and upstream optical fiber on the device work properly.
  2. Replace the EIUA board with another one delivered in the same batch. It is found that the fault persists, indicating that the fault is not caused by EIUA board problems.
  3. Run the display port statistics portid command to query the port statistics. It is found that the FE ports have received and transmitted a large number of cyclic redundancy check (CRC) error frames and conflict errors. This indicates that there is a subscriber line interference source around the device.
  4. Remove all network cables connected to the ONU and connect only one port to a PC to perform a test. It is found that the Internet access service is restored, indicating that the fault is caused by a subscriber line interference.
  5. Use a multimeter to measure the voltages between the device shell and lines 1, 2, 3, and 6 in the network cable. The measured voltages are all 100 V. Check the subscriber lines. It is found that the power cable of the device is bundled with the network cable. Remove lines 4, 5, 7, and 8 from the network cable because these lines produce strong electrical interference to the device. It is found that the service is restored.
Suggestions and Summary
  • In this case, removing lines 4, 5, 7, and 8 from the network cable prevents the device from being affected by strong electrical interferences.
  • The anti-interference abilities of EIUA boards manufactured after 2012 are improved a lot. When similar subscriber line problems occur, you are advised to replace the original board with one manufactured after 2012 to enhance the anti-interference ability of the device.

More related topics

2014年7月23日星期三

How to Troubleshoot the Fault When the Cascaded Switch Fails to Telnet



LAN access service
Fault Description
Network topology: Layer 2 switch -> MA5620 -> MA5600T (V800R006C02)
The GPON service of the MA5600T uses the solution of binding GEM ports to priorities. That is, the priority bound to traffic streams of the MA5620 is 0 and the priority bound to traffic streams of the management address of the MA5620 is 3. Users can remotely ping the management IP address of the Layer 2 switch but cannot telnet it.
Cause Analysis
  • The Layer 2 switch filters out telnet packets by ACL rules configured.
  • The MA5600T uses the solution of binding GEM ports to priorities. The priority of traffic streams for managing the Layer 2 switch must be 0. Otherwise, the MA5600T drops packets.
Procedure
  1. Check configurations of the Layer 2 switch. It is found that telnet for the port is not blocked.
  2. Capture packets on the Layer 2 switch. It is found that the priority of the telnet response packet of the Layer 2 switch is 6. The priority of the packets of the Layer 2 switch cannot be changed.
  3. Check the configurations of the MA5620. It is found that the transparent LAN service (TLS) streams are configured, but the attributes of such streams cannot be changed.
  4. Configure a traffic stream on the MA5620 using the management IP address of the Layer 2 switch and configure the stream with the following attributes using the traffic profile: the priority of the stream is 0, the local attributes are used. Then, the Layer 2 switch can be telneted remotely. Then, it is found that the fault is rectified.
Suggestion and Conclusion
If the GPON service of the MA5600T uses the solution of binding GEM ports to priorities, the priority of the traffic stream transmitted to the GPON device needs to be checked.

More related topics


2014年7月17日星期四

How to Configure NQA for Static IPv4 Routes



Applicability
This example applies to all versions and Huawei wireless routers.

Networking Requirements
NQA for static IPv4 routes can quickly detect network faults and control advertisement of static routes. As shown in Figure 1, RouterA connects to RouterB through GE2/0/0 and connects to RouterC through GE1/0/0. Two links are available from RouterA to RouterD: RouterA-->RouterB-->RouterD (primary link) and RouterA-->RouterC-->RouterD (backup link).Configure an NQA ICMP test intance on RouterA to detect the active link. When the active link becomes faulty, packets sent from RouterA to RouterD are switched to the standby link.
Figure 1 Networking diagram of configuring NQA for static IPv4 routes 

Procedure
1. Configure RouterA.
#
 sysname RouterA
#
interface GigabitEthernet1/0/0
 ip address 192.168.1.1 255.255.255.0
#
interface GigabitEthernet2/0/0
 ip address 192.168.4.1 255.255.255.0
#
interface GigabitEthernet3/0/0
 ip address 192.168.6.1 255.255.255.0
#
ip route-static 192.168.2.0 255.255.255.0 192.168.1.2
ip route-static 192.168.3.0 255.255.255.0 192.168.4.2
ip route-static 192.168.5.0 255.255.255.0 192.168.1.2 preference 100  //Set the preference of static routes to 100 so that the static routes can be used as backup routes.
ip route-static 192.168.5.0 255.255.255.0 GigabitEthernet2/0/0 192.168.4.2 track nqa admin icmp  //Configure a static route to associate it with an NQA test instance.
#
nqa test-instance admin icmp  //Configure an NQA test instance named admin icmp.
 test-type icmp  //Set the test type to ICMP.
 destination-address ipv4 192.168.3.1  //Set the destination address of the NQA test instance to 192.168.3.1.
 frequency 10  //Set the interval between two NQA tests to 10s.
 probe-count 2  //Set the number of test probes of an NQA test instance to 2.
 start now  //Start the NQA test instance immediately.
#

2. Configure RouterB.
#
 sysname RouterB
#
interface GigabitEthernet1/0/0
 ip address 192.168.3.2 255.255.255.0
#
interface GigabitEthernet2/0/0
 ip address 192.168.4.2 255.255.255.0
#
ip route-static 192.168.5.0 255.255.255.0 192.168.3.1
ip route-static 192.168.6.0 255.255.255.0 192.168.4.1
#

3. Configure RouterC.
#
 sysname RouterC
#
interface GigabitEthernet1/0/0
 ip address 192.168.1.2 255.255.255.0
#
interface GigabitEthernet2/0/0
 ip address 192.168.2.1 255.255.255.0
#
ip route-static 192.168.5.0 255.255.255.0 192.168.2.2
ip route-static 192.168.6.0 255.255.255.0 192.168.1.1

4. Configure RouterD.
#
 sysname RouterD
#
interface GigabitEthernet1/0/0
ip address 192.168.3.1 255.255.255.0
#
interface GigabitEthernet2/0/0
ip address 192.168.2.2 255.255.255.0
#
interface GigabitEthernet3/0/0
ip address 192.168.5.1 255.255.255.0
#
ip route-static 192.168.1.0 255.255.255.0 192.168.2.1
ip route-static 192.168.4.0 255.255.255.0 192.168.3.2
ip route-static 192.168.6.0 255.255.255.0 192.168.3.2
ip route-static 192.168.6.0 255.255.255.0 192.168.2.1
#

5. Verify the configuration.
Run the display nqa results test-instance admin icmp command on RouterA to view the NQA test result. The command output displays "Lost packet ratio: 0 %", indicating that the link status is normal. Run the display ip routing-table command on RouterA to view the IP routing table. The routing table contains the static route with destination network segment 192.168.5.0/24 and next-hop address 192.168.4.2. There is no static route with preference 100 in the routing table.
Run the shutdown command in the view of GE1/0/0 or GE2/0/0 on RouterB to simulate a link failure. Run the display nqa results test-instance admin icmp command on RouterA to view the NQA test result. The command output displays "Completion:failed" and "Lost packet ratio: 100 %, indicating that a link failure has been detected. Then run the display ip routing-table command on RouterA to view the IP routing table. The routing table contains the static route with preference 100. There is no static route with destination network segment 192.168.5.0/24 and next-hop address 192.168.4.2. 

Configuration Notes
  • The static route associated with an NQA test instance is deleted from the routing table only when the NQA test fails. You can run the display nqa results command to view the NQA test result.
  • Before modifying the configuration of an NQA test instance, stop the NQA test instance.
  • If the static route associated with one NQA test instance is associated with another NQA test instance, the association between the static route and the former NQA test instance is removed.
  • Only the NQA ping test instance is used so that RouterA switches services based on the test result. There is no requirement for the peer device configuration.

The more information about technical support you can consult with our technician - Bill, and his e-mail address is as below:  
bill@huanetwork.com


More relate: