Prerequisites for OSPFv3 Multiarea Adjacency
- Ensure that Open Shortest Path First version 3 (OSPFv3) is configured on the primary interface.
- Ensure that the primary interface type is point-to-point.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The OSPFv3 Multiarea Adjacency feature allows you to configure a link that multiple Open Shortest Path First version 3 (OSPFv3) areas can share to enable optimized routing. You can add more than one area to an existing OSPFv3 primary interface.
Open Shortest Path First version 3 (OSPFv3) allows a single physical link to be shared by multiple areas. This creates an intra-area path in each of the corresponding areas sharing the same link. All areas have an interface on which you can configure OSPFv3. One of these interfaces is designated as the primary interface and others as secondary interfaces.
The OSPFv3 Multiarea Adjacency feature allows you to configure a link on the primary interface to enable optimized routing in multiple areas. Each multiarea interface is announced as a point-to-point unnumbered link. The multiarea interface exists as a logical construct over an existing primary interface. The neighbor state on the primary interface is independent of the neighbor state of the multiarea interface. The multiarea interface establishes a neighbor relationship with the corresponding multiarea interface on the neighboring device. You can only configure multiarea adjacency on an interface that has two OSPFv3 speakers.
Use the ospfv3 multi-area command to configure multiarea adjacency on the primary OSPFv3 interface.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example:
|
|
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
|
Step 3 |
interface type number Example:
|
Specifies the interface type and number. |
|
Step 4 |
ipv6 enable Example:
|
Enables IPv6 processing on an interface that has not been configured with an explicit IPv6 address. |
|
Step 5 |
ospfv3 multi-area multi-area-id Example:
|
|
|
Step 6 |
ospfv3 multi-area multi-area-id cost interface-cost Example:
|
(Optional) Specifies the cost of sending a packet on an OSPFv3 multiarea interface. Use this command to specify the cost only if you want the cost of the multiarea interface to be different than the cost of the primary interface. |
|
Step 7 |
ospfv3 process-id ipv6 area area-id Example:
|
|
|
Step 8 |
serial restart-delay count Example:
|
Sets the amount of time that the router waits before trying to bring up a serial interface when it goes down. The count argument specifies the frequency (in seconds) at which that hardware is reset. The range is from 0 to 900. |
|
Step 9 |
end Example:
|
Returns to privileged EXEC mode. |
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example:
|
|
|
Step 2 |
show ospfv3 interface brief Example:
|
Displays brief information about Open Shortest Path First version 3 (OSPFv3) interfaces. |
|
Step 3 |
show ospfv3 multi-area Example:
|
Displays information about OSPFv3 multiarea interfaces. |
|
Step 4 |
show ospfv3 interface Example:
|
Displays information about OSPFv3 interfaces. |
Device> enable
Device# configure terminal
Device(config)# interface serial 2/0
Device(config-if)# ipv6 enable
Device(config-if)# ospfv3 multi-area 100
Device(config-if)# ospfv3 multi-area 100 cost 512
Device(config-if)# ospfv3 1 ipv6 area 0
Device(config-if)# serial restart-delay 0
Device(config-if)# end
Device# show ospfv3 interface brief
Interface PID Area AF Cost State Nbrs F/C
Se2/0 1 0 ipv6 64 P2P 1/1
MA2 1 1 100 ipv6 512 P2P 1/1
Device# show ospfv3 multi-area
OSPFV3_MA2 is up, line protocol is up
Primary Interface Serial2/0, Area 100
Interface ID 10
MTU is 1500 bytes
Neighbor Count is 1To display information about OSPFv3 interfaces, use the show ospfv3 interface command in privileged EXEC mode.
Device# show ospfv3 interface
Serial2/0 is up, line protocol is up
Link Local Address 2001:DB8:0:FFFF::1, Interface ID 10
Area 0, Process ID 1, Instance ID 0, Router ID 10.0.0.12
Network Type POINT_TO_POINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:07
Graceful restart helper support enabled
Index 1/1/1, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.0.0.22
Suppress hello for 0 neighbor(s)
Multi-area interface Count is 1
OSPFV3_MA2 interface exists in area 100 Neighbor Count is 1
OSPFV3_MA2 is up, line protocol is up
Link Local Address 2001:DB8:0:FFFF::1, Interface ID 10
Area 100, Process ID 1, Instance ID 0, Router ID 10.0.0.12
Network Type POINT_TO_POINT, Cost: 512
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:08
Graceful restart helper support enabled
Index 1/1/2, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.0.0.22
|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands |
|
|
IPv6 commands |
|
Description |
Link |
|---|---|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to https://cfnng.cisco.com/. An account on Cisco.com is not required.