Example for Configuring a VLL Connection in Martini Mode

Networking Requirements

The MPLS network of an ISP provides the L2VPN service for many users. The users connect to the MPLS network through PE1 and PE2, and users on the PEs change frequently. A proper VPN solution is required to provide secure VPN services for users and to simplify configuration when new users connect to the network.

A Martini VLL connection can be set up between CE1 and CE2 to meet these requirements, as shown in Figure 1.

By default, LNP is enabled globally on the device. If a VLANIF interface is used as an AC-side interface for L2VPN, the configuration conflicts with LNP. In this case, run the lnp disable command in the system view to disable LNP.

The lnp disable command has no impact on services before the device restarts. After the device restarts, the device can only forward packets from the VLANs specified by the port default vlan command at Layer 2. The port default vlan 1 command is configured by default, so only packets of VLAN 1 can be forwarded at Layer 2.

Figure 1 Martini VLL

Configuration Roadmap

Users on the PEs change frequently, so manual configuration is inefficient and may cause configuration errors. Here, the two PEs can set up a remote LDP connection and use the LDP protocol to synchronize user information (VC IDs). This implementation is the Martini mode.

The configuration roadmap is as follows:

Configure an IGP on the PE and P devices on the backbone network to ensure reachability between them, and enable MPLS.
This example uses the default tunnel policy to set up an LSP tunnel. The LSP tunnel is used as a dedicated tunnel to transmit private network data on the public network.
Set up a remote LDP session between the PEs to exchange VC labels between the PEs.
Enable MPLS L2VPN and create VC connections on the PEs. Enabling MPLS L2VPN is the prerequisite for VLL configuration.

Procedure

Configure VLANs for interfaces and addresses for VLANIF interfaces on the CE, PE and P devices according to Figure 1.

# Configure CE1. The configuration on CE2, PE1, P and PE2 is similar to the configuration on CE1 and is not mentioned here.

<HUAWEI> system-view
[HUAWEI] sysname CE1
[CE1] vlan batch 10
[CE1] interface vlanif 10
[CE1-Vlanif10] ip address 192.168.1.1 255.255.255.0
[CE1-Vlanif10] quit
[CE1] interface gigabitethernet 0/0/1
[CE1-GigabitEthernet0/0/1] port link-type trunk
[CE1-GigabitEthernet0/0/1] port trunk allow-pass vlan 10
[CE1-GigabitEthernet0/0/1] quit

Configure IGP on the MPLS backbone network. (In this example, OSPF is used.)
When configuring OSPF, advertise the 32-bit addresses of loopback interfaces on PEs and P. The loopback interface addresses are the LSR IDs.

# Configure PE1. The configuration on P and PE2 is similar to the configuration on CE1 and is not mentioned here.
```
[PE1] interface loopback 1
[PE1-LoopBack1] ip address 1.1.1.9 32
[PE1-LoopBack1] quit
[PE1] ospf 1
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
```

Configure the basic MPLS capabilities and MPLS LDP on the MPLS network.

# Configure PE1.

[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1] interface vlanif 20
[PE1-Vlanif20] mpls
[PE1-Vlanif20] mpls ldp
[PE1-Vlanif20] quit

# Configure the P.

[P] mpls lsr-id 2.2.2.9
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P] interface vlanif 20
[P-Vlanif20] mpls
[P-Vlanif20] mpls ldp
[P-Vlanif20] quit
[P] interface vlanif 30
[P-Vlanif30] mpls
[P-Vlanif30] mpls ldp
[P-Vlanif30] quit

# Configure PE2.

[PE2] mpls lsr-id 3.3.3.9
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2] interface vlanif 30
[PE2-Vlanif30] mpls
[PE2-Vlanif30] mpls ldp
[PE2-Vlanif30] quit

Set up a remote LDP session between PEs.

# Configure PE1.

[PE1] mpls ldp remote-peer 3.3.3.9
[PE1-mpls-ldp-remote-3.3.3.9] remote-ip 3.3.3.9
[PE1-mpls-ldp-remote-3.3.3.9] quit

# Configure PE2.

[PE2] mpls ldp remote-peer 1.1.1.9
[PE2-mpls-ldp-remote-1.1.1.9] remote-ip 1.1.1.9
[PE2-mpls-ldp-remote-1.1.1.9] quit

After the configuration is complete, run the display mpls ldp session command on PE1 to view the establishment of the LDP session. You can find that an LDP session is set up between PE1 and PE2.

The command output of PE1 is used as an example.

[PE1] display mpls ldp session

 LDP Session(s) in Public Network
 Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
 A '*' before a session means the session is being deleted.
 ------------------------------------------------------------------------------
 PeerID             Status      LAM  SsnRole  SsnAge      KASent/Rcv
 ------------------------------------------------------------------------------
 2.2.2.9:0          Operational DU   Passive  0000:00:09  40/40
 3.3.3.9:0          Operational DU   Passive  0000:00:09  37/37
 ------------------------------------------------------------------------------
 TOTAL: 2 session(s) Found.

Enable MPLS L2VPN and create VCs on the PEs.
# Configure PE1: Create a VC on VLANIF10, which is connected to CE1.In this example, a VLANIF interface is used as the AC-side interface, so you need to run the lnp disable command in the system view before performing the following steps. If you cannot disable LNP on the live network, do not use a VLANIF interface as the AC-side interface.
```
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1] interface vlanif 10
[PE1-Vlanif10] mpls l2vc 3.3.3.9 101
[PE1-Vlanif10] quit
```
# Configure PE2: Create a VC on VLANIF40, which is connected to CE2.In this example, a VLANIF interface is used as the AC-side interface, so you need to run the lnp disable command in the system view before performing the following steps. If you cannot disable LNP on the live network, do not use a VLANIF interface as the AC-side interface.
```
[PE2] mpls l2vpn
[PE2-l2vpn] quit
[PE2] interface vlanif 40
[PE2-Vlanif40] mpls l2vc 1.1.1.9 101
[PE2-Vlanif40] quit
```

Verify the configuration.

View the L2VPN connection information on the PEs, and you can see that an L2VC is set up and is in Up state.

The command output of PE1 is used as an example.

[PE1] display mpls l2vc interface vlanif 10
 *client interface       : Vlanif10 is up
  Administrator PW       : no
  session state          : up
  AC status              : up
  Ignore AC state        : disable
  VC state               : up
  Label state            : 0
  Token state            : 0
  VC ID                  : 101
  VC type                : VLAN
  destination            : 3.3.3.9
  local group ID         : 0            remote group ID      : 0
  local VC label         : 8195        remote VC label      : 8195
  local AC OAM State     : up
  local PSN OAM State    : up
  local forwarding state : forwarding
  local status code      : 0x0
  remote AC OAM state    : up
  remote PSN OAM state   : up
  remote forwarding state: forwarding
  remote status code     : 0x0
  ignore standby state   : no
  BFD for PW             : unavailable
  VCCV State             : up
  manual fault           : not set
  active state           : active
  forwarding entry       : exist
  link state             : up
  local VC MTU           : 1500         remote VC MTU        : 1500
  local VCCV             : alert ttl lsp-ping bfd
  remote VCCV            : alert ttl lsp-ping bfd
  local control word     : disable      remote control word  : disable
  tunnel policy name     : --
  PW template name       : --
  primary or secondary   : primary
  load balance type      : flow                                        
  Access-port            : false                                       
  Switchover Flag        : false                                       
  VC tunnel/token info   : 1 tunnels/tokens
    NO.0  TNL type       : lsp   , TNL ID : 0x10031
    Backup TNL type      : lsp   , TNL ID : 0x0
  create time            : 0 days, 0 hours, 8 minutes, 42 seconds      
  up time                : 0 days, 0 hours, 7 minutes, 44 seconds      
  last change time       : 0 days, 0 hours, 7 minutes, 44 seconds      
  VC last up time        : 2013/08/29 20:01:50                         
  VC total up time       : 0 days, 0 hours, 7 minutes, 44 seconds
  CKey                   : 6                                           
  NKey                   : 5                                           
  PW redundancy mode     : frr                                         
  AdminPw interface      : --                                          
  AdminPw link state     : --                                          
  Diffserv Mode          : uniform                                     
  Service Class          : be                                          
  Color                  : --                                          
  DomainId               : --                                          
  Domain Name            : --

CE1 and CE2 can ping each other.

The command output of CE1 is used as an example.

[CE1] ping 192.168.1.2
  PING 192.168.1.2: 56  data bytes, press CTRL_C to break
    Reply from 192.168.1.2: bytes=56 Sequence=1 ttl=255 time=31 ms
    Reply from 192.168.1.2: bytes=56 Sequence=2 ttl=255 time=10 ms
    Reply from 192.168.1.2: bytes=56 Sequence=3 ttl=255 time=5 ms
    Reply from 192.168.1.2: bytes=56 Sequence=4 ttl=255 time=2 ms
    Reply from 192.168.1.2: bytes=56 Sequence=5 ttl=255 time=28 ms

  --- 192.168.1.2 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 2/15/31 ms

Configuration Files

CE1 configuration file

#
sysname CE1
#
vlan batch 10
#
interface Vlanif10
 ip address 192.168.1.1 255.255.255.0
#
interface GigabitEthernet0/0/1
 port link-type trunk
 port trunk allow-pass vlan 10
#
return

PE1 configuration file

#
sysname PE1
#
vlan batch 10 20
#
lnp disable #mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
mpls ldp remote-peer 3.3.3.9
 remote-ip 3.3.3.9
#
interface Vlanif10
 mpls l2vc 3.3.3.9 101
#
interface Vlanif20
 ip address 10.1.1.1 255.255.255.0
 mpls
 mpls ldp
#
interface GigabitEthernet0/0/1
 port link-type trunk
 port trunk allow-pass vlan 10
#
interface GigabitEthernet0/0/2
 port link-type trunk
 port trunk allow-pass vlan 20
#
interface LoopBack1
 ip address 1.1.1.9 255.255.255.255
#
ospf 1
 area 0.0.0.0
  network 1.1.1.9 0.0.0.0
  network 10.1.1.0 0.0.0.255
#
return

P configuration file

#
sysname P
#
vlan batch 20 30
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Vlanif20
 ip address 10.1.1.2 255.255.255.0
 mpls
 mpls ldp
#
interface Vlanif30
 ip address 10.2.2.2 255.255.255.0
 mpls
 mpls ldp
#
interface GigabitEthernet0/0/1
 port link-type trunk
 port trunk allow-pass vlan 30
#
interface GigabitEthernet0/0/2
 port link-type trunk
 port trunk allow-pass vlan 20
#
interface LoopBack1
 ip address 2.2.2.9 255.255.255.255
#
ospf 1
 area 0.0.0.0
  network 2.2.2.9 0.0.0.0
  network 10.1.1.0 0.0.0.255
  network 10.2.2.0 0.0.0.255
#
return

PE2 configuration file

#
sysname PE2
#
vlan batch 30 40
#
lnp disable #mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls ldp
#
mpls ldp remote-peer 1.1.1.9
 remote-ip 1.1.1.9
#
interface Vlanif30
 ip address 10.2.2.1 255.255.255.0
 mpls
 mpls ldp
#
interface Vlanif40
 mpls l2vc 1.1.1.9 101
#
interface GigabitEthernet0/0/1
 port link-type trunk
 port trunk allow-pass vlan 30
#
interface GigabitEthernet0/0/2
 port link-type trunk
 port trunk allow-pass vlan 40
#
interface LoopBack1
 ip address 3.3.3.9 255.255.255.255
#
ospf 1
 area 0.0.0.0
  network 3.3.3.9 0.0.0.0
  network 10.2.2.0 0.0.0.255
#
return

CE2 configuration file

#
sysname CE2
#
vlan batch 40
#
interface Vlanif40
 ip address 192.168.1.2 255.255.255.0
#
interface GigabitEthernet0/0/1
 port link-type trunk
 port trunk allow-pass vlan 40
#
return