Configuring a Level 1 Carrier CE to Access Level 1 Carrier PEs

When Level 1 and Level 2 carriers are in different ASs, the Level 2 carrier functions as the VPN user of the Level 1 carrier, the scenario of which is the same as that the CE's access to the PE in the basic BGP/MPLS IP VPN.

Procedure

Create a VPN instance on the Level 1 carrier PE.
1. Run system-view
  The system view is displayed.
2. Run ip vpn-instance vpn-instance-name
  A VPN instance is created, and the VPN instance view is displayed.
3. Run ipv4-family
  The VPN instance IPv4 address family is enabled, and the view of this address family is displayed.
4. Run route-distinguisher route-distinguisher
  An RD is set for the VPN instance IPv4 address family.
5. Run apply-label per-route
  The label distribution mode is set to per-route per-label.
6. Run vpn-target vpn-target & <1-8> [ both | export-extcommunity | import-extcommunity ]
  A VPN target is configured for the VPN instance IPv4 address family.
7. Run quit
  Return to the system view.
8. Run interface interface-type interface-number
  The view of the interface connected to the Level 1 carrier CE is displayed.
9. Run ip binding vpn-instance vpn-instance-name
  The interface is associated with the VPN instance.
10. Run ip address ip-address { mask | mask-length }
  The IP address is configured for the interface.
11. Run mpls
  MPLS is enabled on the interface.
12. Run commit
  The configuration is committed.
Configure labeled BGP on the Level 1 carrier PE.
1. Run system-view
  The system view is displayed.
2. Run bgp { as-number-plain1 | as-number-dot1 }
  The BGP view is displayed.
3. Run vpn-instance vpn-instance-name
  A BGP-VPN instance is created and the BGP-VPN instance view is displayed.
4. Run peer ipv4-address as-number { as-number-plain2 | as-number-dot2 }
  The Level 1 carrier CE is configured as an EBGP peer in the BGP-VPN instance view.
5. Run quit
  Return to the BGP view.
6. Run ipv4-family vpn-instance vpn-instance-name
  The BGP-VPN instance IPv4 address family view is displayed.
7. Run import-rib vpn-instance vpn-instance-name labeled-unicast [ valid-route ] { route-policy route-policy-name | route-filter route-filter-name }
  Labeled BGP VPN routes are imported to the BGP VPN routing table.
8. Run quit
  Return to the BGP view.
9. Run ipv4-labeled-unicast vpn-instance vpn-instance-name
  The BGP-labeled-VPN instance IPv4 address family view is displayed.
10. Run peer ipv4-address enable
  The BGP peer relationship is enabled in the BGP-labeled-VPN instance IPv4 address family view so that the Level 1 carrier PE and the Level 1 carrier CE can exchange labeled BGP routes.
11. Run import-rib vpn-instance vpn-instance-name include-label-route [ valid-route ] [ route-policy route-policy-name | route-filter route-filter-name ]
  The device is enabled to import the labeled BGP routes that are imported from the VPN instance to the routing table of the BGP-labeled-VPN instance IPv4 address family.
12. Run commit
  The configuration is committed.
Configure labeled BGP on the Level 1 carrier CE between it and the Level 1 carrier PE.
1. Run system-view
  The system view is displayed.
2. Run interface interface-type interface-number
  The view of the interface connected to the Level 1 carrier PE is displayed.
3. Run ip address ip-address { mask | mask-length }
  The IP address is configured for the interface.
4. Run mpls
  MPLS is enabled on the interface.
5. Run quit
  Return to the system view.
6. Run bgp { as-number-plain2 | as-number-dot2 }
  The BGP view is displayed.
7. Run peer ipv4-address as-number { as-number-plain1 | as-number-dot1 }
  The Level 1 carrier PE is configured as an EBGP peer of the Level 1 carrier CE.
8. Run ipv4-family labeled-unicast
  The BGP-labeled address family view is displayed.
9. Run peer ipv4-address enable
  The BGP peer relationship is enabled in the BGP-labeled address family view so that the Level 1 carrier CE and the Level 1 carrier PE can exchange labeled BGP routes.
10. (Optional) Run peer ip-address allow-as-loop [ number ]
  Routing loops are allowed.
  
  Perform this step if the Level 1 carrier and Level 2 carriers belong to different ASs and Level 2 carriers belong to the same AS.
11. Run quit
  Return to the BGP view.
12. Run import-rib public labeled-unicast [ valid-route ] { route-policy route-policy-name }
  BGP VPN labeled routes are imported to the BGP public network routing table.
13. Run commit
  The configuration is committed.