Login
- Table of Contents
-
- H3C S9500 Operation Manual-Release2132[V2.03]-03 IP Routing Volume
- 00-1Cover
- 01-IP Routing Overview
- 02-BGP Configuration
- 03-IS-IS Configuration
- 04-OSPF Configuration
- 05-RIP Configuration
- 06-Routing Policy Configuration
- 07-Static Routing Configuration
- 08-IPv6 BGP Configuration
- 09-IPv6 IS-IS Configuration
- 10-IPv6 OSPFv3 Configuration
- 11-IPv6 RIPng Configuration
- 12-IPv6 Static Routing Configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 10-IPv6 OSPFv3 Configuration | 187.07 KB |
Table of Contents
Chapter 1 IPv6 OSPFv3 Configuration
1.1.5 OSPFv3 Features Supported
1.2 IPv6 OSPFv3 Configuration Task List
1.3 Configuring OSPFv3 Basic Functions
1.3.2 Configuring OSPFv3 Basic Functions
1.4 Configuring OSPFv3 Area Parameters
1.4.2 Configuring an OSPFv3 Stub Area
1.4.3 Configuring OSPFv3 Virtual Links
1.5 Configuring OSPFv3 Routing Information Management
1.5.2 Configuring OSPFv3 Route Summarization
1.5.3 Configuring OSPFv3 Inbound Route Filtering
1.5.4 Configuring Link Costs for OSPFv3 Interfaces
1.5.5 Configuring the Maximum Number of OSPFv3 Load-balanced Routes
1.5.6 Configuring a Priority for OSPFv3
1.5.7 Configuring OSPFv3 Route Redistribution
1.6 Tuning and Optimizing an OSPFv3 Network
1.6.2 Configuring OSPFv3 Timers
1.6.3 Configuring the DR Priority for an Interface
1.6.4 Ignoring MTU Check for DD Packets
1.6.5 Disable Interfaces from Sending OSPFv3 Packets
1.6.6 Enable the Logging on Neighbor State Changes
1.7 Displaying and Maintaining OSPFv3
1.8 OSPFv3 Configuration Examples
1.8.1 Configuring OSPFv3 Areas
1.8.2 Configuring OSPFv3 DR Election
1.9 Troubleshooting OSPFv3 Configuration
1.9.1 No OSPFv3 Neighbor Relationship Established
1.9.2 Incorrect Routing Information
Chapter 1 IPv6 OSPFv3 Configuration
& Note:
The term “router” refers to a router in a generic sense or an Ethernet switch running routing protocols in this document.
When configuring OSPF, go to these sections for information you are interested in:
l IPv6 OSPFv3 Configuration Task List
l Configuring OSPFv3 Basic Functions
l Configuring OSPFv3 Area Parameters
l Configuring OSPFv3 Routing Information Management
l Tuning and Optimizing an OSPFv3 Network
l Displaying and Maintaining OSPFv3
l OSPFv3 Configuration Examples
l Troubleshooting OSPFv3 Configuration
1.1 Introduction to OSPFv3
1.1.1 OSPFv3 Overview
OSPFv3 is OSPF (Open Shortest Path First) version 3 for short, supporting IPv6 and compliant with RFC2740 (OSPF for IPv6).
Identical parts between OSPFv3 and OSPFv2:
l 32 bits router ID and area ID
l Packets: Hello, DD (Data Description), LSR (Link State Request), LSU (Link State Update), LSAck (Link State Acknowledgment)
l Mechanisms for finding neighbors and establishing adjacencies
l Mechanisms for LSA flooding and aging
Differences between OSPFv3 and OSPFv2:
l OSPFv3 now runs on a per-link basis, instead of on a per-IP-subnet basis.
l OSPFv3 supports multiple instances per link.
l OSPFv3 identifies neighbors by Router ID, while OSPFv2 by IP address.
1.1.2 OSPFv3 Packets
OSPFv3 has also five types of packets: hello, DD, LSR, LSU, and LSAck.
The five packets have the same packet header, which different from the OSPFv2 packet header is only 16 bytes in length, has no authentication field, but is added with an Instance ID field to support multi-instance per link.
Figure 1-1 gives the OSPFv3 packet header.
Figure 1-1 OSPFv3 packet header
l Version #: Version of OSPF, which is 3 for OSPFv3.
l Type: Type of OSPF packet, from 1 to 5 are hello, DD, LSR, LSU, and LSAck respectively.
l Packet Length: Packet length in bytes, including header.
l Instance ID: Instance ID for a link.
l 0: Reserved, which must be 0.
1.1.3 OSPFv3 LSA Types
OSPFv3 sends routing information in LSAs, which as defined in RFC2740 have the following types:
l Router-LSAs: Originated by all routers. This LSA describes the collected states of the router's interfaces to an area. Flooded throughout a single area only.
l Network-LSAs: Originated for broadcast and NBMA networks by the Designated Router. This LSA contains the list of routers connected to the network. Flooded throughout a single area only.
l Inter-Area-Prefix-LSAs: Similar to Type 3 LSA of OSPFv2, originated by ABRs (Area Border Routers), and flooded throughout the LSA's associated area. Each Inter-Area-Prefix-LSA describes a route with IPv6 address prefix to a destination outside the area, yet still inside the AS (an inter-area route).
l Inter-Area-Router-LSAs: Similar to Type 4 LSA of OSPFv2, originated by ABRs and flooded throughout the LSA's associated area. Each Inter-Area-Router-LSA describes a route to ASBR (Autonomous System Boundary Router).
l AS-external-LSAs: Originated by ASBRs, and flooded throughout the AS (except Stub and NSSA areas). Each AS-external-LSA describes a route to another Autonomous System. A default route can be described by an AS external LSA.
l Link-LSAs: A router originates a separate Link-LSA for each attached link. Link-LSAs have link-local flooding scope. Each Link-LSA describes the IPv6 address prefix of the link and Link-local address of the router.
l Intra-Area-Prefix-LSAs: Each Intra-Area-Prefix-LSA contains IPv6 prefix information on a router, stub area or transit area information, and has area flooding scope. It was introduced because Router-LSAs and Network-LSAs contain no address information now.
1.1.4 Timers of OSPFv3
Timers in OSPFv3 include:
l OSPFv3 packet timer
l LSA delay timer
l SPF timer
I. OSPFv3 packet timer
Hello packets are sent periodically between neighboring routers for finding and maintaining neighbor relationships, or for DR/BDR election. The hello interval must be identical on neighboring interfaces. The smaller the hello interval, the faster the network convergence speed and the bigger the network load.
If a router receives no hello packet from a neighbor after a period, it will declare the peer is down. The period is called dead interval.
After sending an LSA to its adjacency, a router waits for an acknowledgment from the adjacency. If no response is received after retransmission interval elapses, the router will send again the LSA. The retransmission interval must be longer than the round-trip time of the LSA in between.
II. LSA delay time
Each LSA has an age in the local LSDB (incremented by 1 per second), but an LSA is not aged on transmission. You need to add an LSA delay time into the age time before transmission, which is important for low speed networks.
III. SPF timer
Whenever LSDB changes, SPF recalculation happens. If recalculations become so frequent, a large amount of resources will be occupied, reducing operation efficiency of routers. You can adjust SPF calculation interval and delay time to protect networks from being overloaded due to frequent changes.
1.1.5 OSPFv3 Features Supported
l Basic features defined in RFC2740
l OSPFv3 stub area
l OSPFv3 multi-process, which enable a router to run multiple OSPFv3 processes
1.1.6 Related RFCs
l RFC2740: OSPF for IPv6
l RFC2328: OSPF Version 2
1.2 IPv6 OSPFv3 Configuration Task List
Complete the following tasks to configure OSPFv3:
|
Task |
Remarks |
|
|
Required |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Configuring the Maximum Number of OSPFv3 Load-balanced Routes |
Optional |
|
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
1.3 Configuring OSPFv3 Basic Functions
1.3.1 Prerequisites
l Make neighboring nodes accessible with each other at network layer.
l Enable IPv6 packet forwarding
1.3.2 Configuring OSPFv3 Basic Functions
Follow these steps to configure OSPFv3 basic functions:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enable OSPFv3 and enter its view |
ospfv3 [ process-id ] |
Required |
|
Specify a router ID |
router-id router-id |
Required |
|
Enter interface view |
interface interface-type interface-number |
— |
|
Enable OSPFv3 on the interface |
ospfv3 process-id area area-id [ instance instance-id ] |
Required Not enabled by default |
& Note:
l Configure an OSPFv3 process ID when enabling OSPFv3. The process ID takes effect locally, without affecting packet exchange between routers.
l When configuring a router ID, make sure each router has a unique ID. If a router runs multiple OSPFv3 processes, you need to specify a router ID for each process.
1.4 Configuring OSPFv3 Area Parameters
The stub area and virtual link support of OSPFv3 has the same principle and application environments with OSPFv2.
Splitting an OSPFv3 AS into multiple areas reduces the number of LSAs on networks and extends OSPFv3 application. For those non-backbone areas residing on the AS boundary, you can configure them as Stub areas to further reduce the size of routing tables on routers in these areas and the number of LSAs.
Non-backbone areas exchange routing information via the backbone area. Therefore, the backbone and non-backbone areas, including the backbone itself must maintain connectivity. In practice, necessary physical links may not be available for connectivity. You can configure virtual links to address it.
1.4.1 Prerequisites
l Enable IPv6 packet forwarding
l Configure OSPFv3 basic functions
1.4.2 Configuring an OSPFv3 Stub Area
Follow these steps to configure an OSPFv3 stub area:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Enter OSPFv3 area view |
area area-id |
— |
|
Configure the area as a stub area |
stub [ no-summary ] |
Required Not configured by default |
|
Configure the default route cost of sending a packet to the stub area |
default-cost value |
Optional Defaults to 1 |
& Note:
l Configurations on routers attached to the same area should be compatible to avoid information exchange failures, information block and routing loops.
l You cannot delete an OSPFv3 area directly. Only when you remove all configurations in area view and all interfaces attached to the area become down, can the area be removed automatically.
l All routers attached to a stub area must be configured with the stub command. The keyword no-summary is only available on the ABR.
l If you use the stub command with the keyword no-summary on an ABR, the ABR distributes a default summary LSA into the area rather than generating an AS-external-LSA or Inter-Area-Prefix-LSA. The stub area of this kind is also known as totally stub area.
1.4.3 Configuring OSPFv3 Virtual Links
You can configure virtual links to maintain connectivity between non-backbone areas and the backbone, or in the backbone itself.
Follow these steps to configure a virtual link:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Enter OSPFv3 area view |
area area-id |
— |
|
Create and configure a virtual link |
vlink-peer router-id [ hello seconds | retransmit seconds | trans-delay seconds | dead seconds | instance instance-id ] * |
Required |
& Note:
Both ends of a virtual link are ABRs that are configured with the vlink-peer command.
1.5 Configuring OSPFv3 Routing Information Management
This section is to configure management of OSPF routing information advertisement and reception, and route redistribution from other protocols.
1.5.1 Prerequisites
l Enable IPv6 packet forwarding
l Configure OSPFv3 basic functions
1.5.2 Configuring OSPFv3 Route Summarization
Follow these steps to configure route summarization between areas:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Enter OSPFv3 area view |
area area-id |
— |
|
Configure a summary route |
abr-summary ipv6-address prefix-length [ not-advertise ] |
Required |
& Note:
The abr-summary command is available on ABRs only. If contiguous network segments are available in an area, you can use the command to summarize them into one network segment on the ABR. The ABR will advertise only the summary route. Any LSA falling into the specified network segment will not be advertised, reducing the LSDB size in other areas.
1.5.3 Configuring OSPFv3 Inbound Route Filtering
You can configure OSPFv3 to filter routes that are computed from received LSAs according to some rules.
Follow these steps to configure inbound route filtering:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Configure inbound route filtering |
filter-policy { acl-number | ipv6-prefix ipv6-prefix-name } import |
Required Not configured by default |
& Note:
Use of the filter-policy import command can only filter routes computed by OSPFv3. Only routes not filtered can be added into the local routing table.
1.5.4 Configuring Link Costs for OSPFv3 Interfaces
You can configure OSPFv3 link costs for interfaces to adjust routing calculation.
Follow these steps to configure the link cost for an OSPFv3 interface:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter interface view |
Interface interface-type interface-number |
— |
|
Configure the cost for the interface |
ospfv3 cost value [ instance instance-id ] |
Optional By default, OSPFv3 computes an interface’s cost according to the bandwidth on it. The cost value defaults to 1 for VLAN interfaces of switches. |
1.5.5 Configuring the Maximum Number of OSPFv3 Load-balanced Routes
If multiple routes to a destination are available, using load balancing to send IPv6 packets on these routes in turn can improve link utility.
Follow these steps to configure the maximum number of load-balanced routes:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Specify the maximum number of equal-cost routes for load-balancing |
maximum load-balancing maximum |
Optional 8 by default |
1.5.6 Configuring a Priority for OSPFv3
A routing device may run multiple routing protocols. The system assigns a priority for each protocol. When these routing protocols find the same route, the route found by the protocol with the highest priority is selected.
Follow these steps to configure a priority for OSPFv3:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Configure a priority for OSPFv3 |
preference [ ase ] [ route-policy route-policy-name ] preference |
Optional By default, the priority of OSPFv3 interval routes is 10, and priority of OSPFv3 external routes is 150. |
1.5.7 Configuring OSPFv3 Route Redistribution
Follow these steps to configure OSPFv3 route redistribution:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Specify a default cost for redistributed routes |
default cost value |
Optional Defaults to 1 |
|
Redistribute routes from another protocol or from another OSPFv3 process |
import-route { isisv6 process-id | ospfv3 process-id | ripng process-id | bgp4+ [ allow-ibgp ] | direct | static } [ cost value | type { 1 | 2 } | tag value | route-policy route-policy-name ] * |
Optional |
|
Configure the filtering of redistributed routes |
filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } export [ isisv6 process-id | ospfv3 process-id | ripng process-id | bgp4+ | direct | static ] |
Optional Not configured by default |
& Note:
l Using the import-route command on a router makes the router become an ASBR.
l Since OSPFv3 is a link state based routing protocol, it cannot directly filter LSAs to be advertised. Therefore, you need to configure filtering redistributed routes before advertising routes that are not filtered in LSAs into the routing domain.
l Use of the filter-policy export command takes effect only on the local router. However, if the import-route command is not configured, executing the filter-policy export command does not take effect.
1.6 Tuning and Optimizing an OSPFv3 Network
This section describes configurations of OSPFv3 timers, interface DR priority, MTU check ignorance for DD packets, disabling interfaces from sending OSPFv3 packets.
OSPFv3 timers:
l Packet timer: Specified to adjust topology convergence speed and network load
l LSA delay timer: Specified especially for low speed links
l SPF timer: Specified to protect networks from being over consumed due to frequent network changes.
For a broadcast network, you can configure DR priorities for interfaces to affect DR/BDR election.
By disabling an interface from sending OSPFv3 packets, you can make other routers on the network obtain no information from the interface.
1.6.1 Prerequisites
l Enable IPv6 packet forwarding
l Configure OSPFv3 basic functions
1.6.2 Configuring OSPFv3 Timers
Follow these steps to configure OSPFv3 timers:
|
Use the command… |
Remarks |
|
|
Enter system view |
system-view |
— |
|
Enter interface view |
interface interface-type interface-number |
— |
|
Configure the hello interval |
ospfv3 timer hello seconds [ instance instance-id ] |
Optional Defaults to 10 seconds on P2P, broadcast interfaces |
|
Configure the dead interval |
ospfv3 timer dead seconds [ instance instance-id ] |
Optional Defaults to 40 seconds on P2P, broadcast interfaces |
|
Configure the LSA retransmission interval |
ospfv3 timer retransmit interval [ instance instance-id ] |
Optional Defaults to 5 seconds |
|
Configure the LSA transmission delay |
ospfv3 trans-delay seconds [ instance instance-id ] |
Optional Defaults to 1 second |
|
Return to system view |
quit |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Configure the SPF timer |
spf timers delay-interval hold-interval |
Optional By default, delay-interval is 5 seconds, and hold-interval is 10 seconds |
& Note:
l The dead interval set on neighboring interfaces cannot be so small. Otherwise, a neighbor is so easy to be considered as down.
l The LSA retransmission interval cannot be so small to avoid unnecessary retransmissions.
1.6.3 Configuring the DR Priority for an Interface
Follow these steps to configure the DR priority for an interface:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter interface view |
interface interface-type interface-number |
— |
|
Configure the DR priority |
ospfv3 dr-priority priority [ instance instance-id ] |
Optional Defaults to 1 |
& Note:
The DR priority of an interface determines the interface’s qualification in DR election. Interfaces having the priority 0 cannot become a DR or BDR.
1.6.4 Ignoring MTU Check for DD Packets
When LSAs are few in DD packets, it is unnecessary to check MTU in DD packets in order to improve efficiency.
Follow these steps to ignore MTU check for DD packets:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter interface view |
interface interface-type interface-number |
— |
|
Ignore MTU check for DD packets |
ospfv3 mtu-ignore [ instance instance-id ] |
Required After this command is configured, the interface will not check the MTU field of incoming DD packets. |
1.6.5 Disable Interfaces from Sending OSPFv3 Packets
Follow these steps to disable interfaces from sending OSPFv3 packets:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Disable interfaces from sending OSPFv3 packets |
silent-interface { interface-type interface-number | all } |
Required Not disabled by default |
& Note:
l Multiple processes can disable the same interface from sending OSPFv3 packets. Using the silent-interface command disables only the interfaces associated with the current process rather than interfaces associated with other processes.
l After an OSPF interface is set to silent, direct routes of the interface can still be advertised in Intra-Area-Prefix-LSAs via other interfaces, but other OSPFv3 packets cannot be advertised. Therefore, no neighboring relationship can be established on the interface. This feature can enhance the adaptability of OSPFv3 networking.
1.6.6 Enable the Logging on Neighbor State Changes
Follow these steps to enable the logging on neighbor state changes:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OSPFv3 view |
ospfv3 [ process-id ] |
— |
|
Enable the logging on neighbor state changes |
log-peer-change |
Required Enabled by default |
1.7 Displaying and Maintaining OSPFv3
|
To do… |
Use the command… |
Remarks |
|
Display OSPFv3 debugging state information |
display debugging ospfv3 |
Available in any view |
|
Display OSPFv3 process brief information |
display ospfv3 [ process-id ] |
|
|
Display OSPFv3 interface information |
display ospfv3 interface [ interface-type interface-number | statistic ] |
|
|
Display OSPFv3 LSDB information |
display ospfv3 lsdb [ [ external | inter-prefix | inter-router | intra-prefix | link | network | router ] [ link-state-id ] [ originate-router ip-address ] | statistic | total ] display ospfv3 process-id lsdb [ [ external | inter-prefix | inter-router | intra-prefix | link | network | router ] [ link-state-id ] [ originate-router ip-address ] | total ] |
|
|
Display OSPFv3 neighbor information |
display ospfv3 [ process-id ] [ area area-id ] peer [ statistic | [ interface-type interface-number ] [ verbose ] | peer-router-id ] |
|
|
Display OSPFv3 neighbor statistics |
display ospfv3 peer statistic |
|
|
Display OSPFv3 routing table information |
display ospfv3 [ process-id ] routing [ ipv6-address prefix-length | ipv6-address/prefix-length | abr-routes | asbr-routes | all | statistics ] |
|
|
Display OSPFv3 area topology information |
display ospfv3 [ process-id ] topology [ area area-id ] |
|
|
Display OSPFv3 virtual link information |
display ospfv3 [ process-id ] vlink |
|
|
Display OSPFv3 next hop information |
display ospfv3 [ process-id ] next-hop |
|
|
Display OSPFv3 link state request list information |
display ospfv3 [ process-id ] request-list [ statistics ] |
|
|
Display OSPFv3 link state retransmission list information |
display ospfv3 [ process-id ] retrans-list [ statistics ] |
|
|
Display OSPFv3 statistics |
display ospfv3 statistic |
1.8 OSPFv3 Configuration Examples
1.8.1 Configuring OSPFv3 Areas
I. Network requirements
In the following figure, all switches run OSPFv3. The AS is split into three areas, in which, Switch B and Switch C act as ABRs to forward routing information between areas.
It is required to configure Area 2 as a stub area, reducing LSAs into the area without affecting route reachability.
II. Network diagram
Figure 1-2 Network diagram for OSPFv3 area configuration
III. Configuration procedure
1) Configure IPv6 addresses for interfaces (omitted).
2) Configure OSPFv3 basic functions.
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ipv6
[SwitchA] ospfv3
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 300
[SwitchA-Vlan-interface300] ospfv3 1 area 1
[SwitchA-Vlan-interface300] quit
[SwitchA] interface vlan-interface 200
[SwitchA-Vlan-interface200] ospfv3 1 area 1
[SwitchA-Vlan-interface200] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ipv6
[SwitchB] ospfv3
[SwitchB-ospf-1] router-id 2.2.2.2
[SwitchB-ospf-1] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ospfv3 1 area 0
[SwitchB-Vlan-interface100] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ospfv3 1 area 1
[SwitchB-Vlan-interface200] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ipv6
[SwitchC] ospfv3
[SwitchC-ospfv3-1] router-id 3.3.3.3
[SwitchC-ospfv3-1] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] ospfv3 1 area 0
[SwitchC-Vlan-interface100] quit
[SwitchC] interface vlan-interface 400
[SwitchC-Vlan-interface400] ospfv3 1 area 2
[SwitchC-Vlan-interface400] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] ipv6
[SwitchD] ospfv3
[SwitchD-ospfv3-1] router-id 4.4.4.4
[SwitchD-ospfv3-1] quit
[SwitchD] interface Vlan-interface 400
[SwitchD-Vlan-interface400] ospfv3 1 area 2
[SwitchD-Vlan-interface400] quit
# Display OSPFv3 neighbor information on Switch B.
[SwitchB] display ospfv3 peer
OSPFv3 Area ID 0.0.0.0 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
3.3.3.3 1 Full/DR 00:00:39 Vlan100 0
OSPFv3 Area ID 0.0.0.1 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
1.1.1.1 1 Full/Backup 00:00:38 Vlan200 0
# Display OSPFv3 neighbor information on Switch C.
[SwitchC] display ospfv3 peer
OSPFv3 Area ID 0.0.0.0 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
2.2.2.2 1 Full/Backup 00:00:39 Vlan100 0
OSPFv3 Area ID 0.0.0.2 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
4.4.4.4 1 Full/DR 00:00:38 Vlan400 0
# Display OSPFv3 routing table information on Switch D.
[SwitchD] display ospfv3 routing
E1 - Type 1 external route, IA - Inter area route, I - Intra area route
E2 - Type 2 external route, * - Selected route
OSPFv3 Router with ID (4.4.4.4) (Process 1)
------------------------------------------------------------------------
*Destination: 2001::/64
Type : IA Cost : 2
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
*Destination: 2001:1::/64
Type : IA Cost : 3
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
*Destination: 2001:2::/64
Type : I Cost : 1
NextHop : directly-connected Interface: Vlan400
*Destination: 2001:3::/64
Type : IA Cost : 4
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
3) Configure Area 2 as a stub area.
# Configure Switch D.
[SwitchD] ospfv3
[SwitchD-ospfv3-1] area 2
[SwitchD-ospfv3-1-area-0.0.0.2] stub
# Configure Switch C, and specify the cost of the default route sent to the stub area as 10.
[SwitchC] ospfv3
[SwitchC-ospfv3-1] area 2
[SwitchC-ospfv3-1-area-0.0.0.2] stub
[SwitchC-ospfv3-1-area-0.0.0.2] default-cost 10
# Display OSPFv3 routing table information on Switch D. You can find a default route is added, whose cost is the cost of a directly connected route plus the configured cost.
[SwitchD] display ospfv3 routing
E1 - Type 1 external route, IA - Inter area route, I - Intra area route
E2 - Type 2 external route, * - Selected route
OSPFv3 Router with ID (4.4.4.4) (Process 1)
------------------------------------------------------------------------
*Destination: ::/0
Type : IA Cost : 11
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
*Destination: 2001::/64
Type : IA Cost : 2
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
*Destination: 2001:1::/64
Type : IA Cost : 3
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
*Destination: 2001:2::/64
Type : I Cost : 1
NextHop : directly-connected Interface: Vlan400
*Destination: 2001:3::/64
Type : IA Cost : 4
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
4) Configure Area 2 as a totally stub area
# Configure Switch C, the ABR, to make Area 2 as a totally stub area.
[SwitchC-ospfv3-1-area-0.0.0.2] stub no-summary
# Display OSPFv3 routing table information on Switch D. You can find route entries are reduced. All non direct routes are removed except the default route.
[SwitchD] display ospfv3 routing
E1 - Type 1 external route, IA - Inter area route, I - Intra area route
E2 - Type 2 external route, * - Selected route
OSPFv3 Router with ID (4.4.4.4) (Process 1)
------------------------------------------------------------------------
*Destination: ::/0
Type : IA Cost : 11
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
*Destination: 2001:2::/64
Type : I Cost : 1
NextHop : directly-connected Interface: Vlan400
1.8.2 Configuring OSPFv3 DR Election
I. Network requirements
In the following figure:
l The priority of Switch A is 100, the highest priority on the network, so it will be the DR.
l The priority of Switch C is 2, the second highest priority on the network, so it will be the BDR.
l The priority of Switch B is 0, so it cannot become the DR.
l RouterD has the default priority 1.
& Note:
Tunnels must be created between switches to configure OSPFv3 and form OSPFv3 neighbor relationships. For related information, refer to Tunneling Configuration.
II. Network diagram
Figure 1-3 Network diagram for OSPFv3 DR election configuration
III. Configuration procedure
1) Configure IPv6 addresses for interfaces (omitted)
2) Configure OSPFv3 basic functions
# Configure Switch A
<SwitchA> system-view
[SwitchA] ipv6
[SwitchA] ospfv3
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ospfv3 1 area 0
[SwitchA-Vlan-interface100] quit
# Configure Switch B
<SwitchB> system-view
[SwitchB] ipv6
[SwitchB] ospfv3
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ospfv3 1 area 0
[SwitchB-Vlan-interface200] quit
# Configure Switch C
<SwitchC> system-view
[SwitchC] ipv6
[SwitchC] ospfv3
[SwitchC-ospfv3-1] router-id 3.3.3.3
[SwitchC-ospfv3-1] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] ospfv3 1 area 0
[SwitchC-Vlan-interface100] quit
# Configure Switch D
<SwitchD> system-view
[SwitchD] ipv6
[SwitchD] ospfv3
[SwitchD-ospfv3-1] router-id 4.4.4.4
[SwitchD-ospfv3-1] quit
[SwitchD] interface vlan-interface 200
[SwitchD-Vlan-interface200] ospfv3 1 area 0
[SwitchD-Vlan-interface200] quit
# Display neighbor information on Switch A. You can find the switches have the same default DR priority 1. In this case, the switch with the highest Router ID is elected as the DR. Therefore, Switch D is the DR, and Switch C is the BDR.
[SwitchA] display ospfv3 peer
OSPFv3 Area ID 0.0.0.0 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
2.2.2.2 1 2-Way/DROther 00:00:36 Vlan200 0
3.3.3.3 1 Full/Backup 00:00:35 Vlan100 0
4.4.4.4 1 Full/DR 00:00:33 Vlan200 0
# Display neighbor information on Switch D. You can find the neighbor states between Switch D and other switches are all full.
[SwitchD] display ospfv3 peer
OSPFv3 Area ID 0.0.0.0 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
1.1.1.1 1 Full/DROther 00:00:30 Vlan100 0
2.2.2.2 1 Full/DROther 00:00:37 Vlan200 0
3.3.3.3 1 Full/Backup 00:00:31 Vlan100 0
3) Configure DR priorities for interfaces.
# Configure the DR priority of Vlan-interface100 as 100 on Switch A.
[SwitchA] interface Vlan-interface 100
[SwitchA-Vlan-interface100] ospfv3 dr-priority 100
[SwitchA-Vlan-interface100] quit
# Configure the DR priority of Vlan-interface 200 as 0 on Switch B.
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ospfv3 dr-priority 0
[SwitchB-Vlan-interface200] quit
#Configure the DR priority of Switch C as 2.
[SwitchC] interface Vlan-interface 100
[SwitchC-Vlan-interface100] ospfv3 dr-priority 2
[SwitchC-Vlan-interface100] quit
# Display neighbor information on Switch A. You can find DR priorities have been updated, but DR and BDR are not changed.
[SwitchA] display ospfv3 peer
OSPFv3 Area ID 0.0.0.0 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
2.2.2.2 0 2-Way/DROther 00:00:38 Vlan200 0
3.3.3.3 2 Full/Backup 00:00:32 Vlan100 0
4.4.4.4 1 Full/DR 00:00:36 Vlan200 0
# Display neighbor information on Switch D. You can find Switch D is still the DR.
[SwitchD] display ospfv3 peer
OSPFv3 Area ID 0.0.0.0 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
1.1.1.1 100 Full/DROther 00:00:33 Vlan100 0
2.2.2.2 0 Full/DROther 00:00:36 Vlan200 0
3.3.3.3 2 Full/Backup 00:00:40 Vlan100 0
4) Restart DR/BDR election
# Use the shutdown and undo shutdown commands on interfaces to restart DR/BDR election (omitted).
# Display neighbor information on Switch A. You can find Switch C becomes the BDR.
[SwitchA] display ospfv3 peer
OSPFv3 Area ID 0.0.0.0 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
2.2.2.2 0 Full/DROther 00:00:31 Vlan200 0
3.3.3.3 2 Full/Backup 00:00:39 Vlan100 0
4.4.4.4 1 Full/DROther 00:00:37 Vlan200 0
# Display neighbor information on Switch D. You can find Switch A becomes the DR.
[SwitchD] display ospfv3 peer
OSPFv3 Area ID 0.0.0.0 (Process 1)
----------------------------------------------------------------------
Neighbor ID Pri State Dead Time Interface Instance ID
1.1.1.1 100 Full/DR 00:00:34 Vlan100 0
2.2.2.2 0 2-Way/DROther 00:00:34 Vlan200 0
3.3.3.3 2 Full/Backup 00:00:32 Vlan100 0
1.9 Troubleshooting OSPFv3 Configuration
1.9.1 No OSPFv3 Neighbor Relationship Established
I. Symptom
No OSPF neighbor relationship can be established.
II. Analysis
If the physical link and lower protocol work well, check OSPF parameters configured on interfaces. The two neighboring interfaces must have the same parameters, such as the area ID, network segment and mask, network type. If the network type is broadcast, at least one interface must have a DR priority higher than 0.
III. Process steps
1) Display neighbor information using the display ospfv3 peer command.
2) Display OSPFv3 interface information using the display ospfv3 interface command.
3) Ping the neighbor router’s IP address to check connectivity.
4) Check OSPF timers. The dead interval on an interface must be at least four times the hello interval.
5) On a broadcast network, at least one interface must have a DR priority higher than 0.
1.9.2 Incorrect Routing Information
I. Symptom
OSPFv3 cannot find routes to other areas.
II. Analysis
The backbone area must maintain connectivity to all other areas. If a router connects to more than one area, at least one area must be connected to the backbone. The backbone cannot be configured as a Stub area.
In a Stub area, all routers cannot receive external routes, and all interfaces connected to the Stub area must be associated with the Stub area.
III. Solution
1) Use the display ospfv3 peer command to display OSPFv3 neighbors.
2) Use the display ospfv3 interface command to display OSPFv3 interface information.
3) Use the display ospfv3 lsdb command to display Link State Database information to check integrity.
4) Display information about area configuration using the display current-configuration configuration command. If more than two areas are configured, at least one area is connected to the backbone.
5) In a Stub area, all routers are configured with the stub command.
6) If a virtual link is configured, use the display ospf vlink command to check the neighbor state.
