Configuring a Level 1 Carrier CE to Access Level 1 Carrier PEs
When the Level 1 carrier and Level 2 carrier are in different ASs, the Level 1 carrier takes the Level 2 carrier as its VPN user.
Procedure
- Create a VPN instance on the Level 1 carrier PE.
- Run system-view
The system view is displayed.
- Run ip vpn-instance vpn-instance-name
A VPN instance is created, and the VPN instance view is displayed.
- Run ipv4-family
The VPN instance IPv4 address family is enabled, and the view of this address family is displayed.
- Run route-distinguisher route-distinguisher
An RD is set for the VPN instance IPv4 address family.
- Run apply-label per-route
The label distribution mode is set to per-route per-label.
- Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ]
A VPN target is configured for the VPN instance IPv4 address family.
- Run quit
Return to the system view.
- Run interface interface-type interface-number
The view of the interface connected to the Level 1 carrier CE is displayed.
- Run ip binding vpn-instance vpn-instance-name
The interface is associated with the VPN instance.
- Run ip address ip-address { mask | mask-length }
The IP address is configured for the interface.
- Run mpls
MPLS is enabled on the interface.
- Run commit
The configuration is committed.
- Run system-view
- Configure labeled BGP on the Level 1 carrier PE.
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain1 | as-number-dot1 }
The BGP view is displayed.
- Run vpn-instance vpn-instance-name
A BGP-VPN instance is created and the BGP-VPN instance view is displayed.
- 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.
- Run quit
Return to the BGP view.
- Run ipv4-family vpn-instance vpn-instance-name
The BGP-VPN instance IPv4 address family view is displayed.
- 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.
- Run quit
Return to the BGP view.
- Run ipv4-labeled-unicast vpn-instance vpn-instance-name
The BGP-labeled-VPN instance IPv4 address family view is displayed.
- 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.
- 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.
- Run commit
The configuration is committed.
- Run system-view
- Configure labeled BGP on the Level 1 carrier CE between it and the Level 1 carrier PE.
- Run system-view
The system view is displayed.
- Run interface interface-type interface-number
The view of the interface connected to the Level 1 carrier PE is displayed.
- Run ip address ip-address { mask | mask-length }
The IP address is configured for the interface.
- Run mpls
MPLS is enabled on the interface.
- Run quit
Return to the system view.
- Run bgp { as-number-plain2 | as-number-dot2 }
The BGP view is displayed.
- 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.
- Run ipv4-family labeled-unicast
The BGP-labeled address family view is displayed.
- 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.
- (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.
- Run quit
Return to the BGP view.
- 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.
- Run commit
The configuration is committed.
- Run system-view
- Configure labeled BGP on the Level 1 carrier CE between it and the Level 2 carrier PE.
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain2 | as-number-dot2 }
The BGP view is displayed.
- Run peer ipv4-address as-number { as-number-plain2 | as-number-dot2 }
The Level 2 carrier PE is configured as an IBGP peer of the Level 2 carrier PE.
- Run peer ipv4-address connect-interface loopback interface-number
The interface for setting up a TCP connection is specified.
- Run ipv4-family labeled-unicast
The BGP-labeled address family view is displayed.
- 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 2 carrier PE can exchange labeled BGP routes.
- Run import-route protocol [ process-id ]
Routes of the Level 2 carrier's network are imported.
- Run commit
The configuration is committed.
- Run system-view
- Configure labeled BGP on the Level 2 carrier PE.
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain2 | as-number-dot2 }
The BGP view is displayed.
- Run peer ipv4-address as-number { as-number-plain2 | as-number-dot2 }
The Level 1 carrier CE is configured as an IBGP peer of the Level 2 carrier PE.
- Run peer ipv4-address connect-interface loopback interface-number
The interface for setting up a TCP connection is specified.
- Run ipv4-family labeled-unicast
The BGP-labeled address family view is displayed.
- Run peer ipv4-address enable
The BGP peer relationship is enabled in the BGP-labeled address family view so that the Level 2 carrier PE and the Level 1 carrier CE can exchange labeled BGP routes.
- Run commit
The configuration is committed.
- Run system-view