HPE FlexFabric 5950 Series Configuration Manual page 212

Step
1. Enter system view.
2. Create an IS-IS process for a
VPN instance and enter
IS-IS view.
3. Configure a network entity
title for the IS-IS process.
4. Return to system view.
5. Enter interface view.
6. Enable the IS-IS process on
the interface.
C onfiguring EBGP between a PE and a CE
4 7 0 B
1. Configure the PE:
Step
1. Enter system view.
2. Enter BGP instance view.
3. Enter BGP-VPN instance
view.
4. Configure the CE as the
VPN EBGP peer.
5. Create the BGP-VPN IPv4
unicast family and enter its
view.
6. Enable IPv4 unicast route
exchange with the
specified peer or peer
group.
7. Redistribute the routes of
the local CE.
8. (Optional.) Allow the local
AS number to appear in the
AS_PATH attribute of a
received route, and set the
maximum number of
repetitions.
Command
system-view
isis [ process-id ] vpn-instance
vpn-instance-name
network-entity net
quit
interface interface-type
interface-number
isis enable [ process-id ]
Command
system-view
bgp as-number [ instance
instance-name ]
[ multi-session-thread ]
ip vpn-instance
vpn-instance-name
peer { group-name | ip-address
[ mask-length ] } as-number
as-number
address-family ipv4 [ unicast ]
peer { group-name | ip-address
[ mask-length ] } enable
import-route protocol
[ { process-id | all-processes }
[ allow-direct | med med-value
| route-policy
route-policy-name ] * ]
peer { group-name | ip-address
[ mask-length ] } allow-as-loop
[ number ]
204
Remarks
N/A
Perform this configuration on the
PE. On the CE, configure
common IS-IS.
By default, no NET is configured.
N/A
N/A
By default, no IS-IS process is
enabled on the interface.
Remarks
N/A
N/A
Configuration commands in
BGP-VPN instance view are the
same as those in BGP instance
view. For more information, see
Layer 3—IP Routing
Configuration Guide.
By default, no BGP peers exist.
For more information about
BGP peers and peer groups,
see Layer 3—IP Routing
Configuration Guide.
By default, the BGP-VPN IPv4
unicast family is not created.
By default, BGP does not
exchange IPv4 unicast routes
with any peer.
A PE must redistribute the
routes of the local CE into its
VPN routing table so it can
advertise them to the peer PE.
By default, BGP discards
incoming route updates that
contain the local AS number.
BGP detects routing loops by
examining AS numbers. In a
hub-spoke network where
EBGP is running between a PE
and a CE, the routing
information the PE advertises to