3.3.2 OSPFv3 [SL-L3A]

1

OSPFv3 SENT <source address> (<interface name>) -> <destination address>: <error string>.

Warning (local device)

An attempt to send an OSPFv3 packet failed.

[Explanation of message variables]

<source address>: Source IPv6 address

<interface name>: Interface name

<destination address>: Destination IPv6 address

<error string>: Error cause

[Action]

If this error frequently occurs, determine the cause of the error.

2

OSPFv3:

Helper to adjacency <router id> [(VRF <vrf id>)] failed because network topology is changed.

Warning (local device or network)

The helper router operations stopped because the topology was changed.

[Explanation of message variables]

<router id>: Adjacent router's router ID

<vrf id> VRF ID

[Action]

None.

3

OSPFv3:

Helper to adjacency <router id> [(VRF <vrf id>)] failed because restart time is up.

Information (remote device)

The helper router operations stopped because the waiting time for restart elapsed.

[Explanation of message variables]

<router id>: Adjacent router's router ID

<vrf id> VRF ID

[Action]

Check if the adjacent router has stopped the restart operation. If it has not stopped, adjust the restart time of the adjacent router.

4

OSPFv3 RECV [Area <area id>]

RouterID <source id> [(<interface name>)] -> <destination address>: <log type>.

Warning (local device or remote device)

A received OSPFv3 packet was invalid.

However, multicast packets received from broadcast-type interfaces that have not been set as OSPFv3 interfaces are discarded without log acquisition.

[Explanation of message variables]

<area id>: Area ID

<source id>: Source router ID

<interface name>: Interface name

<destination address>: Destination IPv6 address

<log type>: One of the following log types:

• IP: received my own packet

• bad packet type

• bad version

• bad checksum

• packet too small

• packet size > ip length

• unknown neighbor

• area mismatch

• bad virtual link

• interface down

• HELLO: hello timer mismatch

• HELLO: dead timer mismatch

• HELLO: extern option mismatch

• DD: extern option mismatch

• HELLO: router id confusion

• DD: router id confusion

• DD: MTU mismatch

• LS ACK: Unknown LSA type

• LS REQ: empty request

• LS REQ: bad request

• LS UPD: LSA checksum bad

• LS UPD: Unknown LSA type

[Action]

The action to be taken depends on the type of the log.

• IP: received my own packet

• bad packet type

• bad version

• bad checksum

• packet too small

• packet size > ip length

  An adjacent router is sending an invalid packet. Check the unicast routing program (OSPFv3) of the adjacent router.

• unknown neighbor

  Non-Hello packets were received from an adjacent router that is not recognized by Hello, but no action is required.

• area mismatch

• bad virtual link

  If packets are received from the new adjacent router, modify the area settings.

  In other cases, no action is required.

• interface down

  None.

• HELLO: hello timer mismatch

• HELLO: dead timer mismatch

  Modify the OSPFv3 interface settings.

• HELLO: extern option mismatch

• DD: extern option mismatch

  Modify the stub area settings.

• HELLO: router id confusion

• DD: router id confusion

  Modify the router ID settings.

• DD: MTU mismatch

  An attempt to exchange routing information might fail because the MTU length does not match the adjacent router. Match the MTU length.

• LS ACK: Unknown LSA type

• LS REQ: empty request

• LS REQ: bad request

• LS UPD: LSA checksum bad

• LS UPD: Unknown LSA type

  An adjacent router is sending an invalid packet. Check the unicast routing program (OSPFv3) of the adjacent router.

5

OSPFv3:

Conflict between LSDB <lsid> and route <prefix> /<prefixlen> - Export to OSPFASE Bypassed.

Error (local device)

There is a conflict between LSDB <lsid> and the route. The unicast routing program automatically restarts.

[Explanation of message variables]

<lsid>: LSID of LSA

<prefix>: Routing information destination address

<prefixlen >: Prefix length of the routing information

[Action]

Take appropriate action by following the rtm aborted log.

6

OSPFv3:

Lost adjacency <router id> with interfaceID <id> (<interface name>) because no Hello received recently.

Warning (remote device or network)

Adjacency was terminated because Hello packets that should be sent periodically from the adjacent router were not received during a given interval. This error occurs when a neighboring router stops operation or when there is a communication error between the Switch and the neighboring router.

[Explanation of message variables]

<router id>: Adjacent router's router ID

<id>: ID of the interface of the adjacent router

<interface name>: Interface name

[Action]

If this warning occurs frequently, shorten the interval for sending Hello packets (hellointerval) or extend the maximum interval for receiving Hello packets (routerdeadinterval).

7

OSPFv3:

Lost adjacency <router id> with interfaceID <id> (<interface name>) because neighbor didn't receive my Hello recently.

Warning (remote device or network)

Adjacency was terminated because the adjacent router no longer recognizes the Switch. This occurs when the adjacent router is restarted or Hello packets sent by the Switch are not properly received by the adjacent router.

[Explanation of message variables]

<router id>: Adjacent router's router ID

<id>: ID of the interface of the adjacent router

<interface name>: Interface name

[Action]

If this warning occurs frequently, extend the interval for sending Hello packets (hellointerval) and the maximum interval for receiving Hello packets (routerdeadinterval).

8

OSPFv3:

Lost adjacency <router id1> with interfaceID <id> (<interface name>) due to bad LS Request (<lsid> <router id2> <ls type>).

Error (remote device)

An adjacent router was lost due to an invalid LS request.

[Explanation of message variables]

<router id1>: Adjacent router's router ID

<id>: ID of the interface of the adjacent router

<interface name>: Interface name

<lsid>: LSID of LSA

<router id2>: LSA advertising router ID

<ls type>: LSA LS type code

[Action]

Check the unicast routing program (OSPFv3) of the adjacent router.

9

OSPFv3:

Lost adjacency <router id> with interfaceID <id> (<interface name>) due to sequence mismatch (<sequence1> versus <sequence2>).

Warning (local device or remote device)

An adjacent router was lost due to a sequence (or option) mismatch.

[Explanation of message variables]

<router id>: Adjacent router's router ID

<id>: ID of the interface of the adjacent router

<interface name>: Interface name

<sequence1>: Sequence number in control data

<sequence2>: Sequence number in the DD message

[Action]

If this warning occurs frequently, extend the interval for retransmitting OSPFv3 packets (retransmitinterval).

10

OSPFv3:

Adjacency <router id> interface <interface name> is established.

Information (local or remote device)

A connection with the OSPFv3 adjacent router was successfully established.

[Explanation of message variables]

<router id>: Adjacent router's router ID

<interface name>: Interface name

[Action]

None.

11

OSPFv3:

Checksum failed at LSA type <ls type> ID <lsid> adv-router <router id> in this system's LSDB that belongs to Area <area id>, Domain <domain id> [on VRF <vrf id>].

Error (local device)

LSDB checksum is invalid. The unicast routing program automatically restarts.

[Explanation of message variables]

<ls type>: LSA LS type code

<lsid>: LSID of LSA

<router id>: LSA advertising router ID

<area id>: LSA area ID

<domain id>: LSA domain ID

<vrf id> VRF ID

[Action]

Take appropriate action by following the rtm aborted log.

12

OSPFv3:

Recovered from stub router (in [(VRF <vrf id>)] domain <domain id>).

Information (local device)

The stub router operation will now end.

[Explanation of message variables]

<vrf id> VRF ID

<domain id>: OSPFv3 domain ID

[Action]

None.

13

OSPFv3:

Graceful restart failed (in [(VRF <vrf id>)] domain <domain id>) because adjacency <router id> doesn't help me.

Warning (remote device or network)

Graceful restart failed because the neighboring router is not acting as a helper router.

[Explanation of message variables]

<vrf id> VRF ID

< domain id> OSPFv3 domain ID

<router id>: Adjacent router's router ID

[Action]

Check the configuration of the graceful restart of the neighboring router.

14

OSPFv3:

Graceful restart failed (in [(VRF <vrf id>)] domain <domain id>) because adjacency <router id> gives up me.

Warning (remote device or network)

Graceful restart failed because the neighboring router stopped helper router operation.

[Explanation of message variables]

<vrf id> VRF ID

< domain id> OSPFv3 domain ID

<router id>: Adjacent router's router ID

[Action]

If this error occurs frequently, check OSPF status of the neighboring router and the cause of stopping the helper function.

15

OSPFv3:

Graceful restart failed (in [(VRF <vrf id>)] domain <domain id>) because restart time is up.

Warning (local device)

The graceful restart failed because reconnection and LSA synchronization with all the neighboring routers that were connected prior to the restart could not be performed within the restart period.

[Explanation of message variables]

<vrf id> VRF ID

< domain id> OSPFv3 domain ID

[Action]

Check the restart time configuration.

16

OSPFv3:

Graceful restart finished successfully (in [(VRF <vrf id>)] domain <domain id>).

Information (local device)

Graceful restart was successful.

[Explanation of message variables]

<vrf id> VRF ID

< domain id> OSPFv3 domain ID

[Action]

None.