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

redistribute VPN 2's routes from RIPng process 20 into the OSPFv3 routing table of the MCE.

Page 44 highlights

Destination: 30::2/128 NextHop : ::1 Interface : InLoop0 Protocol : Direct Preference: 0 Cost : 0 Destination: 2012:1::/64 NextHop : FE80::202:FF:FE02:2 Interface : Vlan30 Protocol : OSPFv3 Preference: 150 Cost : 1 Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost : 0 The output shows that PE 1 has learned the private route of VPN 1 through OSPFv3. Use similar procedures to configure OSPFv3 process 20 between the MCE and PE 1 and redistribute VPN 2's routes from RIPng process 20 into the OSPFv3 routing table of the MCE. # On PE 1, display the routing table of VPN 2. [PE1] display ipv6 routing-table vpn-instance vpn2 Routing Table : vpn2 Destinations : 5 Routes : 5 Destination: ::1/128 NextHop : ::1 Interface : InLoop0 Protocol : Direct Preference: 0 Cost : 0 Destination: 40::/64 NextHop : 40::2 Interface : Vlan40 Protocol : Direct Preference: 0 Cost : 0 Destination: 40::2/128 NextHop : ::1 Interface : InLoop0 Protocol : Direct Preference: 0 Cost : 0 Destination: 2012::/64 NextHop : FE80::200:FF:FE0F:5 Interface : Vlan40 Protocol : OSPFv3 Preference: 150 Cost : 1 Destination: FE80::/10 NextHop : :: Interface : NULL0 Protocol : Direct Preference: 0 Cost : 0 The output shows that PE 1 has learned the private route of VPN 2 through OSPFv3. Now, the routing information for the two VPNs has been added into the routing tables on PE 1. 41

  • 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

41
Destination: 30::2/128
Protocol
: Direct
NextHop
: ::1
Preference: 0
Interface
: InLoop0
Cost
: 0
Destination: 2012:1::/64
Protocol
: OSPFv3
NextHop
: FE80::202:FF:FE02:2
Preference: 150
Interface
: Vlan30
Cost
: 1
Destination: FE80::/10
Protocol
: Direct
NextHop
: ::
Preference: 0
Interface
: NULL0
Cost
: 0
The output shows that PE 1 has learned the private route of VPN 1 through OSPFv3.
Use similar procedures to configure OSPFv3 process 20 between the MCE and PE 1 and
redistribute VPN 2's routes from RIPng process 20 into the OSPFv3 routing table of the MCE.
# On PE 1, display the routing table of VPN 2.
[PE1] display ipv6 routing-table vpn-instance vpn2
Routing Table : vpn2
Destinations : 5
Routes : 5
Destination: ::1/128
Protocol
: Direct
NextHop
: ::1
Preference: 0
Interface
: InLoop0
Cost
: 0
Destination: 40::/64
Protocol
: Direct
NextHop
: 40::2
Preference: 0
Interface
: Vlan40
Cost
: 0
Destination: 40::2/128
Protocol
: Direct
NextHop
: ::1
Preference: 0
Interface
: InLoop0
Cost
: 0
Destination: 2012::/64
Protocol
: OSPFv3
NextHop
: FE80::200:FF:FE0F:5
Preference: 150
Interface
: Vlan40
Cost
: 1
Destination: FE80::/10
Protocol
: Direct
NextHop
: ::
Preference: 0
Interface
: NULL0
Cost
: 0
The output shows that PE 1 has learned the private route of VPN 2 through OSPFv3.
Now, the routing information for the two VPNs has been added into the routing tables on PE 1.