• This lesson continues from the multi-area topology built in Configuration: R1 and R2 in Area 0, R2 and R3 in Area 1, all adjacencies FULL.

    OSPFv3 multi-area topology showing Area 0 backbone connected to Area 1 with IPv6 prefixes

    Figure 1 - multi-area topology

    You can also configure a in .

    OSPFv3 passive interface on R1 G0/1 blocking Hellos toward the 2001:db8:10::/64 LAN segment

    Figure 2 -

    If you remember the concept, a suppresses Hello messages on a specific interface.

    This means:

    • The interface still advertises its network

    • But it does not form neighbor adjacencies

    Configure a Passive Interface (Per Interface)

    You can configure a directly under the process.

    On R1:

    R1# conf t
    Enter configuration commands, one per line.  End with CNTL/Z.
    R1(config)# router ospfv3 1
    R1(config-router)# passive-interface g0/1

    Now verify:

    R1# show ospfv3 interface g0/1
    GigabitEthernet0/1 is up, line protocol is up 
      Link Local Address FE80::52CA:C4FF:FE00:1201, Interface ID 3
      Area 0, Process ID 1, Instance ID 0, Router ID 1.1.1.1
      Network Type BROADCAST, Cost: 1
      Transmit Delay is 1 sec, State WAITING, Priority 1
      No designated router on this network
      No backup designated router on this network
      Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
        No Hellos (Passive interface) 
        Wait time before Designated router selection 00:00:09
      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 0, maximum is 0
      Last flood scan time is 0 msec, maximum is 1 msec
      Neighbor Count is 0, Adjacent neighbor count is 0 
      Suppress hello for 0 neighbor(s)

    This confirms:

    • The interface is no longer sending Hello packets

    • No can form on this interface

    The network is still advertised, but no neighbors are allowed.

    Configure Passive by Default

    You can also make all interfaces passive by default, then selectively enable the ones that must form adjacencies.

    On R3:

    R3# conf t
    Enter configuration commands, one per line.  End with CNTL/Z.
    R3(config)# router ospfv3 1
    R3(config-router)# passive-interface default 
    %OSPFv3-5-ADJCHG: Process 1, IPv6, Nbr 2.2.2.2 on GigabitEthernet0/0 from FULL to DOWN, Neighbor Down: Interface down or detached

    Immediately, the drops!

    This happens because the interface is now passive and stops sending Hellos.
    Now re-enable on the required interface:

    R3(config-router)# no passive-interface g0/0
    %OSPFv3-5-ADJCHG: Process 1, IPv6, Nbr 2.2.2.2 on GigabitEthernet0/0 from LOADING to FULL, Loading Done

    The returns to FULL.

    You should use:

    • Passive interfaces on LAN segments where no neighbors exist

    • Passive-interface default in larger designs to reduce risk of unwanted adjacencies

    This is a common CCNP-level best practice for security and control.

    Answer the question below

    When an interface is configured as passive, what type of packets are no longer sent?

    Answer the question below

    Three neighbors, passive-interface default, then no passive-interface on two ports: how many stay FULL?