HP MSR2000 Configuration Manual page 202

Step
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.
Configuring EBGP between a PE and a CE
1. Configure the PE:
Step
1. Enter system view.
2. Enable BGP and enter BGP
view.
3. Enter BGP-VPN instance view.
4. Configure the CE as the VPN
EBGP peer.
5. Create
unicast family and enter its
view.
6. Enable
exchange with the specified
peer or peer group.
7. Redistribute the routes of the
local CE.
Command
isis [ process-id ] vpn-instance
vpn-instance-name
network-entity net
quit
interface interface-type
interface-number
isis enable [ process-id ]
the BGP-VPN IPv4
IPv4 unicast route
Command
system-view
bgp as-number
ip vpn-instance vpn-instance-name
peer { group-name | ip-address }
as-number as-number
address-family ipv4 [ unicast ]
peer { group-name | ip-address }
enable
import-route protocol [ { process-id
| all-processes } [ allow-direct |
med med-value | route-policy
route-policy-name ] * ]
193
Remarks
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
view. For more information,
see Layer 3—IP Routing
Configuration Guide.
By default, no BGP peer is
configured.
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.