HP 6125XLG R2306-HP 6125XLG Blade Switch MCE Configuration Guide - Page 33

Configuring IPv6 IS-IS between an IPv6 MCE and a VPN site

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 33 highlights

For more information about OSPFv3, see Layer 3-IP Routing Configuration Guide. To configure OSPFv3 between IPv6 MCE and VPN site: Step 1. Enter system view. Command system-view 2. Create an OSPFv3 process for a VPN instance and enter ospfv3 [ process-id ] vpn-instance OSPFv3 view. vpn-instance-name 3. Set the router ID. router-id router-id import-route protocol [ process-id 4. Redistribute remote site routes | allow-ibgp ] [ cost value | advertised by the PE.. route-policy route-policy-name | type type ] * 5. Return to system view. quit 6. Enter interface view. interface interface-type interface-number 7. Enable OSPFv3 on the interface. ospfv3 process-id area area-id [ instance instance-id ] Remarks N/A Perform this configuration on the IPv6 MCE. On the VPN site, configure normal OSPFv3. N/A By default, no route of any other routing protocol is redistributed into OSPFv3. N/A N/A By default, OSPFv3 is disabled on an interface. NOTE: Deleting a VPN instance also deletes all related OSPFv3 processes. Configuring IPv6 IS-IS between an IPv6 MCE and a VPN site An IPv6 IS-IS process belongs to the public network or a single IPv6 VPN instance. If you create an IPv6 IS-IS process without binding it to an IPv6 VPN instance, the process belongs to the public network. By configuring IPv6 IS-IS process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of different IPv6 VPNs to be exchanged between the IPv6 MCE and the sites through different IPv6 IS-IS processes, ensuring the separation and security of IPv6 VPN routes. For more information about IPv6 IS-IS, see Layer 3-IP Routing Configuration Guide. To configure IPv6 IS-IS between IPv6 MCE and VPN site: Step 1. Enter system view. 2. Create an IPv6 IS-IS process for a VPN instance and enter IS-IS view. 3. Configure a network entity title for the IS-IS process. 4. Enable the IPv6 capacity for the IPv6 IS-IS process. Command system-view isis [ process-id ] vpn-instance vpn-instance-name network-entity net ipv6 enable Remarks N/A Perform this configuration on the IPv6 MCE. On a VPN site, configure normal IPv6 IS-IS. By default, no NET is configured. By default, IPv6 is disabled. 30

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
30
For more information about OSPFv3, see
Layer 3—IP Routing Configuration Guide
.
To configure OSPFv3 between IPv6 MCE and VPN site:
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
IPv6 MCE. On the VPN site,
configure normal OSPFv3.
3.
Set the router ID.
router-id
router-id
N/A
4.
Redistribute remote site routes
advertised by the PE..
import-route
protocol
[
process-id
|
allow-ibgp
] [
cost
value
|
route-policy
route-policy-name
|
type
type
] *
By default, no route of any other
routing protocol is redistributed
into OSPFv3.
5.
Return to system view.
quit
N/A
6.
Enter interface view.
interface
interface-type
interface-number
N/A
7.
Enable OSPFv3 on the
interface.
ospfv3
process-id
area
area-id
[
instance
instance-id
]
By default, OSPFv3 is disabled on
an interface.
NOTE:
Deleting a VPN instance also deletes all related OSPFv3 processes.
Configuring IPv6 IS-IS between an IPv6 MCE and a VPN site
An IPv6 IS-IS process belongs to the public network or a single IPv6 VPN instance. If you create an IPv6
IS-IS process without binding it to an IPv6 VPN instance, the process belongs to the public network.
By configuring IPv6 IS-IS process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of
different IPv6 VPNs to be exchanged between the IPv6 MCE and the sites through different IPv6 IS-IS
processes, ensuring the separation and security of IPv6 VPN routes.
For more information about IPv6 IS-IS, see
Layer 3—IP Routing Configuration Guide
.
To configure IPv6 IS-IS between IPv6 MCE and VPN site:
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
IPv6 MCE. On a VPN site,
configure normal IPv6 IS-IS.
3.
Configure a network entity
title for the IS-IS process.
network-entity
net
By default, no NET is configured.
4.
Enable the IPv6 capacity for
the IPv6 IS-IS process.
ipv6 enable
By default, IPv6 is disabled.