Configuring routing between a PE and a CE
You can configure IPv6 static routing, RIPng, OSPFv3, IPv6 IS-IS, EBGP, or IBGP between a PE and a CE.
Configuring IPv6 static routing between a PE and a CE
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Configure an IPv6 static route for a VPN instance. | ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length { interface-type interface-number [ next-hop-address ] | nexthop-address [ public ] | vpn-instance d-vpn-instance-name nexthop-address } [ permanent ] [ preference preference-value ] [ tag tag-value ] [ description description-text ] | By default, no IPv6 static route is configured for a VPN instance. Perform this configuration on the PE. On the CE, configure a common IPv6 static route. For more information about IPv6 static routing, see Layer 3—IP Routing Configuration Guide. |
Configuring RIPng between a PE and a CE
A RIPng process belongs to the public network or a single VPN instance. If you create a RIPng process without binding it to a VPN instance, the process belongs to the public network.
For more information about RIPng, see Layer 3—IP Routing Configuration Guide.
To configure RIPng between a PE and a CE:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a RIPng process for a VPN instance and enter RIPng view. | ripng [ process-id ] vpn-instance vpn-instance-name | Perform this configuration on the PE. On the CE, create a common RIPng process. |
3. Return to system view. | quit | N/A |
4. Enter interface view. | interface interface-type interface-number | N/A |
5. Enable RIPng on the interface. | ripng process-id enable | By default, RIPng is disabled on an interface. |
Configuring OSPFv3 between a PE and a CE
An OSPFv3 process belongs to the public network or a single VPN instance. If you create an OSPF process without binding it to a VPN instance, the process belongs to the public network.
For more information about OSPFv3, see Layer 3—IP Routing Configuration Guide.
To configure OSPFv3 between a PE and a CE:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create an OSPFv3 process for a VPN instance and enter OSPFv3 view. | ospfv3 [ process-id ] vpn-instance vpn-instance-name | Perform this configuration on the PE. On the CE, create a common OSPF process. Deleting a VPN instance also deletes all related OSPFv3 processes. |
3. Set the router ID. | router-id router-id | N/A |
4. (Optional.) Configure an OSPFv3 domain ID. | domain-id { domain-id [ secondary ] | null } | The default domain ID is 0. Perform this configuration on the PE. When you redistribute OSPFv3 routes into BGP, BGP adds the primary domain ID to the redistributed BGP VPNv6 routes as a BGP extended community attribute. You can configure the same domain ID for different OSPFv3 processes. All OSPF processes of the same VPN must be configured with the same OSPF domain ID to ensure correct route advertisement. This command is available in Release 2311P04 and later versions. |
5. (Optional.) Configure the type code of an OSPFv3 extended community attribute. | ext-community-type { domain-id type-code1 | route-type type-code2 | router-id type-code3 } | By default, the type codes for domain ID, route type, and router ID are hexadecimal numbers 0005, 0306, and 0107, respectively. Perform this configuration on the PE. This command is available in Release 2311P04 and later versions. |
6. (Optional.) Configure an external route tag for redistributed VPN routes. | route-tag tag-value | By default, if BGP runs within an MPLS backbone, and the BGP AS number is not greater than 65535, the first two octets of the external route tag are 0xD000. The last two octets are the local BGP AS number. If the AS number is greater than 65535, the external route tag is 0. Perform this configuration on the PE. This command is available in Release 2311P04 and later versions. |
7. (Optional.) Disable setting the DN bit in OSPFv3 LSAs. | disable-dn-bit-set | By default, when a PE redistributes BGP routes into OSPFv3 and creates OSPFv3 LSAs, it sets the DN bit for the LSAs. Before using this command, make sure it does not cause any routing loops. Perform this configuration on the PE. This command is available in Release 2311P04 and later versions. |
8. (Optional.) Ignore the DN bit in OSPFv3 LSAs. | disable-dn-bit-check | By default, the PE checks the DN bit in OSPFv3 LSAs. Before using this command, make sure it does not cause any routing loops. Perform this configuration on the PE. This command is available in Release 2311P04 and later versions. |
9. (Optional.) Enable the external route check function for OSPFv3 LSAs. | route-tag-check enable | By default, the PE checks the DN bit in OSPFv3 LSAs to avoid routing loops. This command is compatible with the old protocol (RFC 4577). HP recommends not using this command in the current software version. Perform this configuration on the PE. This command is available in Release 2311P04 and later versions. |
10. Return to system view. | quit | N/A |
11. Enter interface view. | interface interface-type interface-number | N/A |
12. Enable OSPFv3 on the interface. | ospfv3 process-id area area-id [ instance instance-id ] | By default, OSPFv3 is disabled on an interface. Perform this configuration on the PE. |
Configuring IPv6 IS-IS between a PE and a CE
An IPv6 IS-IS process belongs to the public network or a single VPN instance. If you create an IPv6 IS-IS process without binding it to a VPN instance, the process belongs to the public network.
For more information about IPv6 IS-IS, see Layer 3—IP Routing Configuration Guide.
To configure IPv6 IS-IS between a PE and a CE:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create an IPv6 IS-IS process for a VPN instance and enter IS-IS view. | isis [ process-id ] vpn-instance vpn-instance-name | Perform this configuration on the PE. On the CE, create a common IPv6 IS-IS process. |
3. Configure a network entity title for the IS-IS process. | network-entity net | By default, no NET is configured. |
4. Enable IPv6 for the IS-IS process. | ipv6 enable | IPv6 is disabled by default. |
5. Return to system view. | quit | N/A |
6. Enter interface view. | interface interface-type interface-number | N/A |
7. Enable IPv6 for the IS-IS process on the interface. | isis ipv6 enable [ process-id ] | IPv6 is disabled on an interface by default. |
Configuring EBGP between a PE and a CE
Configure the PE:
Step
Command
Remarks
1. Enter system view.
system-view
N/A
2. Enable BGP and enter BGP view.
bgp as-number
N/A
3. Enter BGP-VPN instance view.
ip vpn-instance vpn-instance-name
N/A
4. Configure the CE as the VPN EBGP peer.
peer { group-name | ipv6-address } as-number as-number
By default, no BGP peer is configured.
5. Create the BGP-VPN IPv6 unicast address family and enter its view.
address-family ipv6 [ unicast ]
By default, the BGP-VPN IPv6 unicast address family is not created.
Configuration commands in BGP-VPN IPv6 unicast address family view are the same as those in BGP IPv6 unicast address family view. For details, see Layer 3—IP Routing Configuration Guide.
6. Enable IPv6 unicast route exchange with the specified peer or peer group.
peer { group-name | ip-address } enable
By default, BGP does not exchange IPv6 unicast routes with any peer.
7. Redistribute the routes of the local CE.
import-route protocol [ process-id [ med med-value | route-policy route-policy-name ] * ]
A PE must redistribute the routes of the local CE into its VPN routing table so that it can advertise them to the peer PE.
8. (Optional.) Configure filtering of advertised routes.
filter-policy { acl6-number | prefix-list ipv6-prefix-name } export [ protocol process-id ]
By default, BGP does not filter advertised routes.
9. (Optional.) Configure filtering of received routes.
filter-policy { acl6-number | prefix-list ipv6-prefix-name } import
By default, the PE does not filter received routes.
Configure the CE:
Step
Command
Remarks
1. Enter system view.
system-view
N/A
2. Enter BGP view.
bgp as-number
N/A
3. Configure the PE as an EBGP peer.
peer { group-name | ipv6-address } as-number as-number
By default, no BGP peer is configured.
4. Create the BGP IPv6 unicast address family and enter its view.
address-family ipv6 [ unicast ]
By default, the BGP IPv6 unicast address family is not created.
5. Enable IPv6 unicast route exchange with the specified peer or peer group.
peer { group-name | ip-address } enable
By default, BGP does not exchange IPv6 unicast routes with any peer.
6. (Optional.) Configure route redistribution.
import-route protocol [ process-id [ med med-value | route-policy route-policy-name ] * ]
A CE must advertise its VPN routes to the connected PE so that the PE can advertise them to the peer CE.
Configuring IBGP between a PE and a CE
Use IBGP between PE and CE only in a basic IPv6 MPLS L3VPN network. In networks such as inter-AS VPN and carrier's carrier, you cannot configure IBGP between PE and CE.
Configure the PE:
Step
Command
Remarks
1. Enter system view.
system-view
N/A
2. Enter BGP view.
bgp as-number
N/A
3. Enter BGP-VPN instance view.
ip vpn-instance vpn-instance-name
Configuration commands in BGP-VPN instance view are the same as those in BGP view. For details, see Layer 3—IP Routing Configuration Guide.
4. Configure the CE as the VPN IBGP peer.
peer { group-name | ipv6-address } as-number as-number
By default, no BGP peer is created.
5. Create the BGP-VPN IPv6 unicast family and enter its view.
address-family ipv6 [ unicast ]
By default, the BGP-VPN IPv6 unicast family is not created.
6. Enable IPv6 unicast route exchange with the specified peer.
peer { group-name | ipv6-address } enable
By default, BGP does not exchange IPv6 unicast routes with any peer.
7. Configure the CE as a client of the RR.
peer { group-name | ipv6-address } reflect-client
By default, no RR or RR client is configured, and the PE does not advertise routes learned from the IBGP peer CE to other IBGP peers, including VPNv6 IBGP peers. The PE advertises routes learned from the CE to other IBGP peers only when you configure the IBGP peer CE as a client of the RR.
Configuring an RR does not change the next hop of a route. To change the next hop of a route, configure an inbound policy on the receiving side.
8. (Optional.) Enable route reflection between clients.
reflect between-clients
By default, route reflection between clients is enabled.
9. (Optional.) Configure the cluster ID for the RR.
reflector cluster-id { cluster-id | ip-address }
By default, the RR uses its own router ID as the cluster ID.
If multiple RRs exist in a cluster, use this command to configure the same cluster ID for all RRs in the cluster to avoid routing loops.
Configure the CE:
Step
Command
Remarks
1. Enter system view.
system-view
N/A
2. Enter BGP view.
bgp as-number
N/A
3. Configure the PE as an IBGP peer.
peer { group-name | ipv6-address } as-number as-number
By default, no BGP peer is created.
4. Create the BGP IPv6 unicast family and enter its view.
address-family ipv6 [ unicast ]
By default, the BGP IPv6 unicast family is not created.
5. Enable IPv6 unicast route exchange with the specified peer or peer group.
peer { group-name | ipv6-address } enable
By default, BGP does not exchange IPv6 unicast routes with any peer.
6. (Optional.) Configure route redistribution.
import-route protocol [ process-id [ med med-value | route-policy route-policy-name ] * ]
A CE must redistribute its routes to the PE so the PE can advertise them to the peer CE.