Service Deployment
Multi-Services Bearer
NE20E supports various types of bearer techniques, such as VLL, PWE3, VPLS, L3VPN, and multicast VPN, which meets FMC bearing network requirements, as shown in Figure 5-1.
Leased Line Service
After leased line services are transmitted using E2E HVPLS, VLL, or MPLS L3VPN. NE20E supports a variety of L2VPN and L3VPN techniques so that leased line services can be provisioned in a large scale.
Configuration Item | Description |
---|---|
Configure the LDP signaling protocol. | Establish an LDP session between PEs. For example, the loopback address of the local end of an LDP session is 192.168.3.2, and that of the remote end is 192.168.3.3.
|
Enable the L2VPN function. | Enable the L2VPN function on both PEs. # mpls l2vpn # |
Establish an LDP or TE tunnel. | Establish an LDP or TE tunnel between the PEs. For configuration details, see Constructing an Infrastructure Network. |
Configure a VSI. | Configure a VSI. # vsi a2 //Configure a VSI. pwsignal ldp //Configure LDP as a signaling protocol for the VSI. vsi-id 2 //Configure a VSI ID. peer 3.3.3.9 //Specify the IP address of the VSI peer. # |
Configure AC interfaces. | The following inbound VLAN and QinQ interfaces on the NE20E support VPLS:
|
Bind each AC interface to the VSI. | Bind each AC interface to the VSI. In the following example,
a GE sub-interface is bound to the VSI.
# interface gigabitethernet 0/1/0.1 vlan-type dot1q 100 l2 binding vsi a2 //Bind the AC interface to the VSI. # |
Configuration Item | Description |
---|---|
Configure the LDP signaling protocol. | For configuration details, see Table 5-1. |
Enable the L2VPN function. | Enable the L2VPN function on both PEs. # mpls l2vpn # |
Establish an LDP or TE tunnel. | Establish an LDP or TE tunnel between the PEs. For configuration details, see Constructing an Infrastructure Network. |
Configure AC interfaces. | For configuration details, see Table 5-1. |
Configure a VC connection. | Configure a VC on each AC interface.
|
Configuration Item | Description |
---|---|
LDP or TE tunnel. | Establish an LDP or TE tunnel between the PEs. For configuration details, see Constructing an Infrastructure Network. |
BGP VPNv4 peer relationship | For configuration details, see the step "Configure an MP-IBGP peer relationship between PEs to exchange VPNv4 routing information" in Initial Configuration. |
VPN instance | # ip vpn-instance vpna //Configure a VPN instance. In this example, the VPN instance is established over an LDP LSP. ipv4-family route-distinguisher 1:1 //Configure the RD value. vpn-target 1:1 export-extcommunity //Configure the export RT. vpn-target 1:1 import-extcommunity //Configure the import RT. # |
Bind an AC interface to a VPN instance. | In the following example, a GE interface is bound to a VPN
instance.
# interface gigabitethernet 0/1/0 ip binding vpn-instance vpna //Bind the AC interface to the VPN instance. ip address 10.1.1.1 255.255.255.252 # |
Configure the PE and CE to exchange routing information. | For configuration details, see the step "Configure a PE and a CE to exchange L3VPN routing information" in Initial Configuration. |
Inter-City L3VPN Service
Inter-City Layer 3 services can be transmitted using L2VPN accessing L3VPN, or the End-to-end L3VPN. Using seamless MPLS to establish an E2E L3VPN tunnel is recommended.
For configuration details on a seamless MPLS L3VPN, see Seamless MPLS Configuration.
For configuration details on L2VPN accessing an L3VPN, see L2VPN Accessing L3VPN Configuration.
Inter-City L2VPN Service
Inter-City L2VPN leased line services can be implemented using either of the following methods:
- If the bearer network contains a single IGP area, establish a single-hop PW or configure the basic VPLS functions. For configuration details, see Table 5-1 and Table 5-2.
- If each of the bearing network is defined at a specific IS-IS
level or in a specific OSPF area, establish a multi-hop PW (MS-PW)
or configure HVPLS.Figure 5-4 Inter-city P2P (MS-PW) service
NOTE:
NE20E functions as a UPE on an MS-PW. The MS-PW configuration is similar to the single-hop PW configuration. For configuration details, see Table 5-2.
Figure 5-5 Inter-city P2MP (HVPLS) serviceNOTE:
NE20E functions as a UPE on an HVPLS network. The HVPLS configuration is similar to the common VPLS configuration. For configuration details, see Table 5-1.