
When implementing [OSPF](/ospf) so that [OSPFv3](/ospfv2-and-ospfv3-comparison) is used, it is necessary to implement the `router ospfv3 [proccesID]` command in order to enable the OSPF process, even if no additional commands are issued under that configuration mode.

Even though OSPFv3 configurations are applied to the interface rather than the OSFPv3 process, the `router ospfv3 [proccesID]` command must still be applied to activate the OSPFv3 process.

## Links

https://networklessons.com/ospf/ospfv3-for-ipv4-configuration/

OSPFv3 - router ospfv3 command

OSPF Prefix Suppression Considerations

OSPF Route Filtering

OSPF Routing Bit

OSPF SPF Scheduling and throttling timers

OSPF Stub Area vs Totally Stub Area

OSPF Stub areas allowed LSAs

OSPF Summarization Restrictions Within an Area

OSPF TTL Security Check

OSPF Troubleshooting

OSPF Type 3 LSA

OSPF Type 4 LSA

OSPF Type 5 LSA

OSPF Type 7 LSA

OSPF Understanding LSA Aging and Refreshing

OSPF Virtual Link Network Type Considerations

OSPF Why it is not suitable for use on the Internet

OSPF advertising loopback network

OSPF area inactive

OSPF area notation

OSPF area type mismatch

OSPF backbone area 0

OSPF default metric values

OSPF design - when to create a new area

OSPF does not redistribute default route

OSPF downheap LSA

OSPF duplicate router IDs

OSPF extent of reconvergence process

OSPF immediate hello packet

OSPF in a GRE multipoint environment

OSPF loop prevention

OSPF message options field

OSPF metric sum of outgoing interface costs

OSPF modifying the router ID

OSPF network command

OSPF network types

OSPF non directly connected neighbor adjacencies

OSPF packet types

OSPF point to point network type for Ethernet

OSPF requirements for forming adjacency

OSPF router ID in an IPv6 environment

OSPF router ID

OSPF sham-link cost

OSPF sham-link

OSPF virtual link and ABRs

OSPF where do you configure a virtual link

OSPF why is a backbone area 0 necessary

OSPF within what area is an OSPF router considered to be

OSPF

OSPFv2 and OSPFv3 comparison

OSPFv3 Prefix Information Separation

OSPFv3 communication between routers and next hop addresses

OSPFv3 instance ID

Offset-list

PAT (overloading) maximum number of translations per inside global address

PAgP

PBR - Policy Based Routing

PBR - Transport Layer port number

PBR - load balancing

PBR - matching prefix lists

PBR - route-map and ACL deny statements not supported

PBR - set interface command

PBR next hop recursive

PBR next hop verify availability

PBR next-hop and default next-hop

PPPoE

PSTN

PTP - Best Master Clock Algorithm

PTP - Clock Types

PTP - Interface Roles

PTP - Offset and Delay times

Passive interface

Physical layer - Copper medium

Physical layer - Optical fiber medium

Physical layer - Wireless medium

Physical layer - encoding

Physical layer - media

Physical layer - modem

Physical layer - modulation

Physical layer Carrier Wave

Ping - Specify ToS

Ping - common reasons for failure

Ping - debug commands

Ping - extended feature

Ping - possible ping responses

Ping - specifying size

Ping - sweep range of sizes

Ping - troubleshooting concepts

Ping

PoE - Understanding Maximum Power

PoE Passive

PoE Standards-based

PoE over Gigabit Ethernet

PoE power sourcing equipment (PSE)

PoE powered device (PD)

PoE what is it

Point-to-Point Protocol (PPP)

Policy Based Routing acts on incoming traffic

Prefix Lists - Operators

Prefix Lists