KB.15.15

Example 147 show ipv6 ospf3 interface command for a specific VLAN with passive

configured on an interface

HP Switch(config)# show ipv6 ospf3 interface 75 detail

OSPFv3 configuration and statistics for VLAN 75

Interface : vlan-75 Status : Enabled

Area ID : 0.0.0.3 State : WAIT

Priority : 1 Cost : 1

Type : BCAST Passive : Yes

Hello Interval : 10 Dead Interval : 40

Transit Delay : 1 Retransmit Interval : 5

Events : 0 Designated Router : 15.1.1.2

Neighbors : 1 Backup Designated Router : 15.1.4.4

Troubleshooting: Logging neighbor adjacency change events

In the default configuration, the routing switch generates event log messages to indicate neighbor

adjacency changes during initialization and normal operation. This enables OSPFv3

misconfiguration troubleshooting, while producing a lower volume of event log messages than is

seen with the debug troubleshooting option. Both a standard (default) mode and an optional detail

mode are provided. Using the optional debug destination command, the logging output can

be directed to a syslog server or a terminal. For more information on debug, see the

"Troubleshooting" appendix in the latest Management and Configuration Guide for your routing

switch.

Syntax:

logging neighbor-adjacency [ detail ]

Used in the ospf3 context to enable logging of standard or detailed adjacency

changes. In the default configuration, logs OSPFv3 neighbor changes into or out

of the full adjacency state.

detail

Generates event log messages for all OSPFv3 neighbor adjacency state changes.

no logging neighbor-adjacency

Disables logging neighbor adjacency on the routing switch.

no logging neighbor-adjacency detail

Cancels detailed neighbor adjacency change logging and returns the routing

switch to logging only neighbor changes into our out of full adjacency.

Default: Standard full adjacency change logging enabled.

The neighbor-adjacency event log messages are described in the latest Event Log Reference Guide

for your routing switch. In the event log output, neighbors are identified by router ID.

Configuring a virtual link 227