Corporate Customer's Services via MBH

Huawei Solution

Page 1 of 9
C2 General
 Table of Contents

1.Introduction........................................................................................................................................ 3
1.1 High Level Design........................................................................................................................... 3
1.2 Low Level Design............................................................................................................................ 3
1.2.1 Omniswitch.................................................................................................................................. 4
1.2.2 M/W equipment............................................................................................................................ 4
1.2.3 Huawei nodes.............................................................................................................................. 4
2.Configuration...................................................................................................................................... 5
2.1 Omniswich configuration................................................................................................................. 5
2.2 PtP link configuration...................................................................................................................... 6
2.3 Huawei nodes configuration............................................................................................................ 6
2.3.1 POC1 LAG master node.............................................................................................................. 6
2.3.2 POC1 LAG backup node.............................................................................................................. 7
2.3.3 POC2/3 node............................................................................................................................... 7

Page 2 of 9
C2 General
 1.Introduction

This document describes the topology and configuration for providing services to Corporate Customers using
the Mobile Back Hauling (MBH) solution, having Huawei as the IP/MPLS nodes. The solution/configuration in
this document is applicable in customers having M/W equipment as access means or fiber in case of FTTS
implementation. It also applies if a corporate customer is connected with a MW link to the FTTS node.

1.1 High Level Design

In the customer's premises a L2 switch (Omni-switch 6250/6450) shall be installed in order to provide traffic
policing, p-bit manipulation and vlan tagging, so as to differentiate the data streams originating from the
customer's equipment.

In the connecting site (POC2/3) a modular IDU shall act as the aggregation point, delivering all incoming traffic
from all customers that have the same end-point to the Huawei IP/MPLS node. From there all the streams shall
traverse the IP/MPLS network and be delivered to the Nokia ME network and afterwards the packets will be
forwarded to the appropriate network according to the service

Figure 1-1 MBH solution topology (HLD)

1.2 Low Level Design

Figure 1-2 MBH solution topology (LLD)

Page 3 of 9
C2 General
 1.2.1 Omni switch
The Omni-Switch (OS) installed at the customer's premises shall receive traffic from customer's equipment and
manipulate it. In particular, the OS shall receive each packet stream in different ports, one per service. It will
then (for each service) police the traffic in order to match the one agreed in the SLA and change the p-bit again
according to the service. That way the service shall be treated with the appropriate priority in the network.

Lastly it will translate all incoming vlans to C-vlans. These C-vlans are to be provided by victus (one for each
service) plus one more for NTU_management. All outgoing frames from OS shall be in 802.1q format and all the
incoming frames in the ME network shall be in 802.1ad format.

The frame's conversion from .1q to QinQ can take place in the M/W or in the Huawei node, according to the
M/W chain used to reach the connecting site (POC2/3) and thus the Huawei node. The outer Vlan used shall be
unique per POC/FTTS node and shall be provided by Victus. In this way the inner Vlans can be repeated per
POC.

1.2.2 M/W equipment

The M/W link shall change the frames' format to QinQ if the m/w path consists RTN links or leave it as 802.1q if
a FP exists in the M/W chain. It will classify the traffic according to the frame's p-bit.

1.2.3 Huawei nodes

The Huawei node shall receive the frames from the aggregating m/w IDU (convert them to QinQ if necessary)
and shall map the traffic to a DSCP bit/que. It will then deliver the traffic to the NNI connection with the Nokia
ME network. For this solution an MC-LAG is being implemented between Huawei and ME nodes in order to
provide resilience (see attached Visio file).

Corporate
customers over Huaw ei MBH.vsdx

Page 4 of 9
C2 General
 2.Configuration

2.1 Omniswich configuration

For this example, we will configure one Onenet service and one Internet feed (ILM) which represent the most
commonly asked services. Onenet is to be configured in port 1/1 and ILM in port 1/2.

The first thing to do is to denote the S-vlans that the services will use. These are the vlans that will be delivered
to the m/w equipment.

Figure 2-1 Denote Svlans

Afterwards we denote the above vlans will traverse port 1/9 (figure 2-2), which is the port that is connected to
the m/w equipment and then we create the sap profiles that we will use per service (figure 2-3). In the sap
profiles is where the policing, remarking and vlan translation takes place.

Figure 2-2 Vlan though b/h port

Figure 2-3 sap-profiles

Next we create the service and bind it to a sap. Inside the sap we state what is the UNI port, what profile we'll
use and what will be the vlan sent by the customer (Figures 2-4, 2-5)

Figure 2-4 Onenet Service

Figure 2-5 Internet Feed service

Page 5 of 9
C2 General
 2.2 PtP link configuration
The detailed configuration is described in Vodafone GR IP MW RTN900/300 Configuration Reference
paragraphs 3.4 & 3.5

2.3 Huawei nodes configuration

2.3.1 POC1 LAG master node

lacp e-trunk system-id 0000-0000-0020
#For the system-id usually the MAC address of the master LAG node is used
lacp e-trunk priority 10
#A smaller value indicates a higher LACP E-Trunk system priority.

e-trunk 1
peer-address <Backup LAG node loopback IP address> source-address <Master LAG node loopback IP address>
revert disable
timer revert delay 5
e-trunk bfd enable
e-trunk bfd min-tx-interval 100 min-rx-interval 100

interface Eth-Trunk0
description LAG_MASTER
qinq protocol 88a8
mode lacp-static
lacp timeout fast
e-trunk 1
lacp e-trunk priority 300
# A smaller value indicates a higher LACP E-Trunk system priority.
statistic enable
#
interface Eth-Trunk0.<VLAN-ID>
vlan-type dot1q <VLAN-ID>
description <Description text>
statistic enable
mpls l2vc <Remote router loopback IP address> <VC-ID> tunnel-policy TNLP-POLICY no-control-word
#PWE3 configuration, VC-ID must be the same on the PWE3 configured on the remote router

interface GigabitEthernet3/0/0
negotiation auto
description <Description text, interface connected to 7750 ME master node>
undo shutdown
eth-trunk 0
dcn

Page 6 of 9
C2 General
 2.3.2 POC1 LAG backup node
lacp e-trunk system-id 0000-0000-0020
#For the system-id usually the MAC address of the master LAG node is used
lacp e-trunk priority 10
#A smaller value indicates a higher LACP E-Trunk system priority.

e-trunk 1
priority 200
#The default E-Trunk priority is 100.The smaller the value, the higher the priority.
peer-address <Master LAG node loopback IP address> source-address <Backup LAG node loopback IP address>
revert disable
timer revert delay 5
e-trunk bfd enable
e-trunk bfd min-tx-interval 100 min-rx-interval 100

interface Eth-Trunk0
description LAG_BACKUP
qinq protocol 88a8
mode lacp-static
lacp timeout fast
e-trunk 1
lacp e-trunk priority 300
# A smaller value indicates a higher LACP E-Trunk system priority.
statistic enable

interface Eth-Trunk0.<VLAN-ID>
#Sub-interface VLAN-ID on which the PWE3s are terminated
vlan-type dot1q <VLAN-ID>
description <Description text>
statistic enable
mpls l2vc <Remote router loopback IP address> <VC-ID> tunnel-policy TNLP-POLICY no-control-word
#PWE3 configuration, VC-ID must be the same on the PWE3 configured on the remote router

interface GigabitEthernet3/0/0
#Example of interface connected to the 7750 ME node
negotiation auto
description <Description text, interface connected to 7750 ME backup node>
undo shutdown
eth-trunk 0
dcn

Page 7 of 9
C2 General
 2.3.3 POC2/3 node
interface GigabitEthernet0/1/7
#Example of interface connected to the OMNI SWITCH customer premises equipment
description <Description text, interface connected to OMNI SWITCH customer premises node>
undo shutdown
qinq protocol 88a8
dcn
#
interface GigabitEthernet0/1/7.<VLAN-ID>
vlan-type dot1q <VLAN-ID>
description <Description text>
statistic enable
mpls l2vc <Master LAG Huawei node loopback IP address> 200003 tunnel-policy TNLP-POLICY no-control-word
#Example of PWE3 circuit to the master LAG Huawei node, see attached visio file for reference
mpls l2vc <Backup LAG Huawei node loopback IP address> 200010 tunnel-policy TNLP-POLICY no-control-word
secondary
#Example of PWE3 circuit to the master LAG Huawei node, see attached visio file for reference
mpls l2vpn redundancy independent
mpls l2vpn stream-dual-receiving

2.3.4 FTTS node

interface GigabitEthernet0/2/26
#Example of interface connected to the OMNI SWITCH customer premises equipment
description <Description text, interface connected to OMNI SWITCH customer premises node>
undo shutdown
undo dcn
#
interface GigabitEthernet0/2/26. <VLAN-ID>
description <Description text, interface connected to OMNI SWITCH customer premises node>
statistic enable
qinq stacking vid 450
#OMNI-switch service VLAN
qinq stacking vid 1000 to 1010
#OMNI-switch service VLAN
qinq stacking pe-vid 3000
#Outer-VLAN between OMNI-switch and Huawei FTTS node
mpls l2vc <ABR-1 Huawei node loopback IP address> 200004 tunnel-policy TNLP-POLICY no-control-word
#Example of PWE3 circuit to the ABR-1 LAG Huawei node, see attached visio file for reference
mpls l2vc <ABR-2 Huawei node loopback IP address> 200002 tunnel-policy TNLP-POLICY no-control-word
secondary
mpls l2vpn redundancy independent
mpls l2vpn stream-dual-receiving

Page 8 of 9
C2 General
 2.3.5 ABR-1 node
mpls switch-l2vc <Master LAG node loopback IP address> 200006 tunnel-policy TNLP-POLICY between <FTTS
node loopback IP address> 200004 tunnel-policy TNLP-POLICY encapsulation vlan control-word-transparent
#Refer to the visio diagram for the VC-ID examples

2.3.6 ABR-2 node

mpls switch-l2vc <Backup LAG node loopback IP address> 200008 tunnel-policy TNLP-POLICY between <FTTS
node loopback IP address> 200002 tunnel-policy TNLP-POLICY encapsulation vlan control-word-transparent
#Refer to the visio diagram for the VC-ID examples

2.3.7 General configuration

1. Between the nodes on which the PWE3 is configured the following LDP peer command needs to be
configured

mpls ldp
remote-peer pwe3
#
ipv4-family
#
mpls ldp remote-peer <remote node name description>
remote-ip <Remote node loopback IP address>

2. If the ABR nodes are Infinera nodes, the PWE3 stitching is not possible on the INM. In this case an LSP
from the FTTS node all the way to the LAG Huawei nodes needs to be created as well as the ldp peers
described in point 1 above.

Page 9 of 9
C2 General