Enabling OSPFv3 in a VRF
To enable OSPFv3 for a default Virtual Routing and Forwarding (VRF), enter a command such as the following.
device(config-ospf6-router)# ipv6 router ospf vrf red
Syntax: [no] ipv6 router ospf vrf vrf-name
The vrf-name parameter species the name of the VRF in which OSPFv3 is being initiated.
Disabling OSPFv3 in a VRF
To disable OSPFv3 for a default Virtual Routing and Forwarding (VRF), enter a command such as the following.
device
(cong-ospf6-router)# no ipv6 router ospf vrf red
Syntax: [no] ipv6 router ospf vrf vrf-name
The vrf-name parameter species the name of the VRF in which OSPFv3 is being initiated.
If you disable OSPFv3, the device removes all the conguration information for the disabled protocol from the running-conguration le.
Moreover, when you save the conguration to the startup-cong le after disabling one of these protocols, all the conguration
information for the disabled protocol is removed from the startup-cong le.
When you disable OSPFv3, the following warning message is displayed on the console.
device(config-ospf6-router)# no ipv6 router ospf
ipv6 router ospf mode now disabled. All ospf config data will be lost when writing to flash!
If you have disabled the protocol but have not yet saved the conguration to the startup-cong le and reloaded the software, you can
restore the conguration information by re-entering the command to enable the protocol (for example, ipv6 router ospf). If you have
already saved the conguration to the startup-cong le and reloaded the software, the conguration information is gone. If you are
testing an OSPF conguration and are likely to disable and re-enable the protocol, you should make a backup copy of the startup-cong
le containing the protocol conguration information. This way, if you remove the conguration information by saving the conguration
after disabling the protocol, you can restore the conguration by copying the backup copy of the startup-cong le onto the ash
memory.
NOTE
All the conguration examples below are applicable for OSPFv3 conguration mode in VRFs as
well.
Assigning OSPFv3 areas
After OSPFv3 is enabled, you can assign OSPFv3 areas. You can assign an IPv4 address or a number as the area ID for each area. The
area ID is representative of all IPv4 addresses (subnets) on a device interface. Each device interface can support one area.
An area can be normal, a stub, or a Not-So-Stubby Area (NSSA) :
• Normal - OSPFv3 devices within a normal area can send and receive External Link State Advertisements (LSAs).
• Stub - OSPFv3 devices within a stub area cannot send or receive External LSAs. In addition, OSPF devices in a stub area must
use a default route to the area’s Area Border Router (ABR) or Autonomous System Boundary Router (ASBR) to send trac out
of the area.
• NSSA - The ASBR of an NSSA can import external route information into the area.
– ASBRs redistribute (import) external routes into the NSSA as type 7 LSAs. Type-7 External LSAs are a special type of LSA
generated only by ASBRs within an NSSA, and are ooded to all the routers within only that NSSA.
Conguring OSPFv3
FastIron Ethernet Switch Layer 3 Routing
53-1003627-04 293
To Next Page
Loading...
Need help?
General
