Configuring the ETH PWE3 Mobile Bearer Service on the CBU-HUAWEI

Extranet VPN
Extranet VPN

*****************ETH PWE3 Mobile Bearer Service on the CBU  Configuration*****************

  • Configure the OLT.
    1. Create an SVLAN and add an upstream port to it.Create smart VLAN 800 and add upstream port 0/19/0 to it.
      OLT(config)#vlan 800 smart
      OLT(config)#port vlan 800 0/19 0
    2. Add an ONU on the OLT.The ONU is connected to the GPON port of the OLT through an optical fiber. You can perform the service configuration only after adding an ONU successfully on the OLT. To log in to the ONU through Telnet and configure the ONU from the OLT, you must configure the inband management VLANs and IP addresses of the OLT and the ONU on the OLT.
      1. Configure the inband management VLAN and IP address of the OLT.Create management VLAN 4000 and add upstream port 0/19/0 to it. Configure the inband management IP address to 192.168.0.1/24.

         NOTE:

        To manage the ONU through SNMP, you must configure the management VLAN, configure the management IP address, and create a management service port.
        OLT(config)#vlan 4000 smart
        OLT(config)#port vlan 4000 0/19 0
        OLT(config)#interface vlanif 4000
        OLT(config-if-vlanif4000)#ip address 192.168.50.1 24
        OLT(config-if-vlanif4000)#quit
      2. Add a DBA profile.Configure the profile name to ETH, profile type to Type1, Fixed bandwidth to 102400 Mbit/s.
        OLT(config)#dba-profile add profile-name ETH type1 fix 102400
      3. (Optional) Add an alarm profile.
        • The ID of the default GPON alarm profile is 1. The thresholds of all the alarm parameters in the default alarm profile are 0, which indicates that no alarm is generated.
        • In this example, the default alarm profile is used, and therefore the configuration of the alarm profile is not required.
        • Run the gpon alarm-profile add command to add an alarm profile, which is used for monitoring the performance of an activated ONU line.
      4. Add an ONU line profile.Add GPON MDU line profile 10 and bind T-CONT 1 to the DBA profile named ETH. In this way, the T-CONT can provide flexible DBA solutions based on different configurations in the DBA profile.
        OLT(config)#ont-lineprofile gpon profile-id 10
        OLT(config-gpon-lineprofile-10)#tcont 1 dba-profile-name ETH

        Add GEM port 0 for transmitting management traffic streams and GEM port 1 for transmitting ETH traffic streams. Bind GEM port 0 and GEM port 1 to T-CONT 1. Configure the QoS mode to priority-queue (default) and the queue priority to 6.

         NOTE:

        1. To change the QoS mode, run the qos-mode command to configure the QoS mode to gem-car or flow-car, and run the gem add command to configure the ID of the traffic profile bound to the GEM port.
        2. When the QoS mode is PQ, the default queue priority is 0; when the QoS is flow-car, traffic profile 6 is bound to the port by default (no rate limitation); when the QoS mode is gem-car, traffic profile 6 is bound to the port by default (no rate limitation).
        OLT(config-gpon-lineprofile-10)#gem add 0 eth tcont 1 priority-queue 6
        OLT(config-gpon-lineprofile-10)#gem add 1 eth tcont 1 priority-queue 6

        Configure the mapping mode from the GEM port to ONU-side service to VLAN (default), map the service port of management VLAN 4000 to GEM port 0, and map the service port of SVLAN 800 to GEM port 1.

        OLT(config-gpon-lineprofile-10)#mapping-mode vlan
        OLT(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 4000
        OLT(config-gpon-lineprofile-10)#gem mapping 1 1 vlan 800
        

        After the configuration is complete, run the commit command to make the configured parameters take effect.

        OLT(config-gpon-lineprofile-10)#commit
        OLT(config-gpon-lineprofile-10)#quit
      5. Add an ONU.Connect the ATN930 to GPON port 0/3/1. The ONU ID is 1, the SN is 48575443E6D8B541, the management mode is SNMP, and the bound line profile ID is 10.

         NOTE:

        • You can run the ont add command to add an ONU offline or run the ont confirm command to confirm an automatically discovered ONU.
        • Before running the ont confirm command to confirm the automatically discovered ONU, you must run the port ont-auto-find command in the GPON mode to enable the ONU automatic discovery function.
        • In this example, the method of confirming an automatically discovered ONU is used.
        OLT(config)#interface gpon 0/3
        OLT(config-if-gpon-0/3)#port 1 ont-auto-find enable
        OLT(config-if-gpon-0/3)#display ont autofind 1
                                                                                        
          Command:                                                                      
                  display ont autofind 1                                                
           ------------------------------------------------------------------------     
           Number    F/ S/ P         SN            Password                             
           ------------------------------------------------------------------------     
            1        0/ 3/ 1    48575443E6D8B541                                        
           ------------------------------------------------------------------------     
        OLT(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp 
        ont-lineprofile-id 10 desc ATN930_0/3/1/1_line10
          Number of ONTs that can be added: 1, success: 1                               
          PortID :1, ONTID :1                                                           
        

         NOTE:

        • After an ONU is added, it is recommended that you run the display ont info command or the display ont state command to query the ONU status. In this step, ensure that Config State and Config State of the ONU are normal and match respectively.
        • If the ONU state in the actual query result is different from the preceding description, run the display ont capability command to query the actual ONU capabilities, and then add a proper ONU profile based on the queried ONU capabilities. Then, add an ONU again.
      6. (Optional) Bind the alarm profile to the ONU.The default profile (profile 1) is used.
        OLT(config-if-gpon-0/3)#ont alarm-profile 1 1 profile-id 1
      7. Configure the inband management VLAN and IP address of the ONU.Configure the static IP address of the ATN930 to 192.168.50.2/24 and the management VLAN ID to 4000 (the same as the management VLAN of the OLT).
        OLT(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 4000
      8. Configure an inband management service port.Configure the management service port ID to 0, management VLAN ID to 4000, GEM port ID to 0, and CVLAN ID to 4000. The rate of the inband service port on the OLT is not limited. Therefore, use traffic profile 6 (default). To limit the rate of the service port, run the traffic table ip command to add a traffic profile and bind it to the service port.
        OLT(config-if-gpon-0/3)#quit
        OLT(config)#service-port 0 vlan 4000 gpon 0/3/1 ont 1 gemport 0 multi-service 
        user-vlan 4000 rx-cttr 6 tx-cttr 6

       NOTE:

      Now, the ONU is successfully added to the OLT, and the management channel between the OLT and the ONU is available. You can log in to the ATN930 by running the telnet 192.168.0.2 command on the OLT to configure the ATN930.

    3. Create service ports.

      Configure the management service port ID to 1, SVLAN ID to 800, GEM port ID to 1, and CVLAN ID to 800. Rate limitation for upstream and downstream packets is performed on the MDU instead of on the OLT. Therefore, use traffic profile 6 (default). To limit the rate of the service port, run the traffic table ip command to add a traffic profile and bind it to the service port.

       NOTE:

      The CVLAN must be the same as the upstream VLAN of the ATN930.
      OLT(config)#service-port 1 vlan 800 gpon 0/3/1 ont 1 multi-service
       user-vlan 800
    4. Configure queue scheduling.Use the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode, with the weights of 10, 10, 20, 20, and 40 respectively; queues 5-7 adopt the PQ mode. The priority of the TDM emulation service is 6, adopting the PQ scheduling.

       NOTE:

      Queue scheduling is a global configuration. You need to configure queue scheduling only once on the OLT, and then the configuration takes effect globally. In the subsequent phases, you need not configure queue scheduling repeatedly when configuring other services.
      OLT(config)#queue-scheduler wrr 10 10 20 20 40 0 0 0

      Configure the mapping between queues and 802.1p priorities. Priorities 0-7 map queues 0-7 respectively.

      OLT(config)#cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7
      

       NOTE:

      For the service board that supports only four queues, the mapping between 802.1p priorities and queue IDs is as follows: priorities 0 and 1 map queue 1; priorities 2 and 3 map queue 2; priorities 4 and 5 map queue 3; priorities 6 and 7 map queue 4.
    5. Save the data.
      OLT(config)#save
  • Configure the ONU.

    NOTE:

    Because the management VLAN and the management IP address have been configured, you can run the telnet 192.168.0.2 command on the OLT to log in to the ATN930 to perform the configuration. You can also log in to the ATN930 through a serial port to perform the configuration.
    1. Configure the IP address of the loopback interface.Configure the IP address of loopback interface 0 to 5.5.5.5/32.
      OLT(config)#interface loopback 0
      OLT(config-if-loopback0)#ip address 5.5.5.5 32
      OLT(config-if-loopback0)#quit
      
    2. Configure the MPLS LSR ID and enable the global MPLS and L2 VPN functions.
      OLT(config)#mpls lsr-id 5.5.5.5   //Set the local LSR ID to the IP address of loopback interface 0
      OLT(config)#mpls   //Enable global MPLS
      OLT(config-mpls)#mpls te   //Enable global MPLS TE
      OLT(config-mpls)#quit
      OLT(config)#mpls l2vpn   //Enable L2 VPN
      
    3. Enable the MPLS TE function for VLAN interface 800 and configure the IP address of VLAN interface 800.
      OLT(config)#vlan 800 smart  //Upstream VLAN
      OLT(config)#mpls vlan 800
      OLT(config)#port vlan 800 0/0 0
      OLT(config)#interface vlanif 800
      OLT(config-if-vlanif800)#ip address 10.50.50.50 24  //Configure the IP address of VLAN interface 500 to 10.50.50.50/24
      OLT(config-if-vlanif800)#mpls
      OLT(config-if-vlanif800)#mpls te
      OLT(config-if-vlanif800)#quit
      
    4. Create a service port for the Ethernet access service.Create an SVLAN for ETH emulation (the services of this SVLAN are terminated by the ETH PW termination device after ETH emulation of the services), and then create a service port and switch the CVLAN ID to the emulation SVLAN ID.
      OLT(config)#vlan 3001
      OLT(config)#service-port vlan 3001 eth 0/4/0 multi-service user-vlan 20 rx-cttr 6 tx-cttr 6
      
    5. Create an MPLS tunnel from the ATN930 to the PTN.Configure the tunnel ID to 10 and the link layer encapsulation protocol of the tunnel interface to MPLS.
      OLT(config)#interface tunnel 10
      OLT(config-if-tunnel10)#tunnel-protocol mpls te

      Configure the destination IP address of the tunnel to 30.30.30.30.

      OLT(config-if-tunnel10)#destination 30.30.30.30

      Configure the MPLS TE tunnel ID to 10. A tunnel ID and an LSR ID uniquely identifies an MPLS TE tunnel.

      OLT(config-if-tunnel10)#mpls te tunnel-id 10

      Configure the signaling protocol for creating the MPLS TE tunnel to static.

      OLT(config-if-tunnel10)#mpls te signal-protocol static

      Save the configuration and quit the MPLS TE configuration.

      OLT(config-if-tunnel10)#mpls te commit
      OLT(config-if-tunnel10)#quit
    6. Configure parameters of the ingress node of the static LSP.

      Configure the tunnel interface ID to 10, IP address of the egress node of the LSP to 30.30.30.30, next hop IP address (L3 interface IP address of the egress node in the same tunnel) to 10.60.60.60, and out-label to 8100 (which must be the same as the in-label of the downstream LSR).

       NOTE:

      A static MPLS TE tunnel can be used only after it is bound to a static LSP.
      OLT(config)#static-lsp ingress tunnel-interface tunnel 10 destination 30.30.30.30
       nexthop 10.60.60.60 out-label 8100
    7. Configure parameters of the egress node of the static LSP.Configure the name of the static LSP to ptn2atn930, bind the static LSP to VLAN interface 800 of the ingress node (The VLAN interface IP address is the next hop IP address of the ingress node. The communication between LSRs is available only when the ingress node and the egress node are added to the same MPLS VLAN), and configure the in-label to 8200 (which must be the same as the out-label of the upstream LSR).
      OLT(config)#static-lsp egress ptn2atn930 incoming-interface vlanif 800 in-lable 8200
    8. Configure the tunnel policy.

      Configure the policy name to mpls-static, bind the policy to tunnel 10, and configure the destination IP address of the tunnel to 30.30.30.30.

       NOTE:

      The destination IP address should be consistent with that configured in the MPLS TE tunnel.
      OLT(config)#tunnel-policy mpls-static
      Info: New tunnel-policy is configured.
      OLT(config-tunnel-policy-mpls-static)#tunnel binding destination 30.30.30.30 te tunnel 10
      OLT(config-tunnel-policy-mpls-static)#quit
    9. Create a PW profile and configure its attributes.
      1. Configure the PW name and type.Configure the PW name to cbu2ptn_eth, and type to nto1.
        OLT(config)#pw-template cbu2ptn_eth
        OLT(config-pw-template-cbu2ptn_eth)#pw-type ethernet tagged
        
      2. Configure the loopback interface IP address of the remote PTN device in the PW profile.Configure the loopback interface IP address to 30.30.30.30.
        OLT(config-pw-template-cbu2ptn_eth)#peer-address 30.30.30.30
        
      3. Configure the PW template to or not to support the control word.
        OLT(config-pw-template-cbu2ptn_eth)#control-word
        
      4. Configure the tunnel policy used by the PW template.Configure the tunnel policy name to mpls-static.
        OLT(config-pw-template-cbu2ptn_eth)#tnl-policy mpls-static
        OLT(config-pw-template-cbu2ptn_eth)#quit
      5. Reset the PW template.

         CAUTION:

        After modifying the attributes of a PW template, you must reset the PW. After that, the modified attributes take effect. After a PW is reset, the protocol starts negotiation again. In this case, the services are interrupted. Therefore, exercise caution when you run this command.
        OLT(config)#reset pw template cbu2ptn_eth
         Info: In operation, please wait...OK!
    10. Configure the system clock source.The system input/output clock source of ATN930 can be obtained from the GPON line clock. If the configuration is not performed, the ATN930 adopts the local oscillator as the system clock or output clock source.
      OLT(config)#clock source 0 0/0/0
      OLT(config)#clock priority system 0
      
      

       NOTE:

      After the configuration is completed, you can run the display clock source command to confirm that the configured system clock source is in the normal state.
    11. Bind the ETH to the PW.The static LSP encapsulation mode is adopted. Such a PW does not use the LDP signaling protocol for parameter negotiation. You can manually specify the related information by running the related command. The data of a static PW is transmitted between the provider edges (PEs) through tunnels. Configure the VLAN ID to 10, PW ID to 10, PW template cbu2ptn_eth, type to MPLS, transmit label to 8448, and receive label to 8449.
      OLT(config)#pw-ac-binding vlan 3001 pw 10 pw-template cbu2ptn_eth static
       transmit-label 8848 receive-label 8849
      

       NOTE:

      When you configure a static TDM PW, the PW transmit-label and receive-label configured on the ATN930 must be the same as the PW transmit-label and receive-label configured on the peer PE (the PTN in this example).
    12. Save the data.
      OLT(config)#save   
      
      

                                                    *************************END***********************

Be the first to comment

Leave a Reply

Your email address will not be published.


*


For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

I agree to these terms.