These log messages refer to the OSPF category.
2.34.1. [ID: 848] Unable to send ACK
- Log Categories
- OSPF
- Log Message
- Unable to send ACK.
- Default Log Severity
- Critical
- Parameters
- recviface, rule
- Explanation
- Unable to send acknowledgment.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.2. [ID: 870] Failed to add route
- Log Categories
- OSPF
- Log Message
- Failed to add route.
- Default Log Severity
- Critical
- Parameters
- iprange, rule
- Explanation
- The OSPF process could not create a new route with range iprange. This is probably a result of not having enough free memory.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- Check memory consumption.
2.34.3. [ID: 861] Bad area
- Log Categories
- OSPF
- Log Message
- Bad area.
- Default Log Severity
- Warning
- Parameters
- area, iface, rule
- Explanation
- The received OSPF data was from a neighboring router within an area which does not match the area of the receive iface.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Make sure all locally attached OSPF routers are in the same area as the attaching interfaces.
2.34.4. [ID: 867] Authentication failed due to bad crypto digest
- Log Categories
- OSPF
- Log Message
- Authentication failed due to bad crypto digest.
- Default Log Severity
- Warning
- Parameters
- neighborid, iface, rule
- Explanation
- Authentication failed due to bad crypto digest.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Verify that the neighbor OSPF router neighborid connected on interface iface share the same crypto digest.
2.34.5. [ID: 851] Authentication failed due to bad crypto key[...]
- Log Categories
- OSPF
- Log Message
- Authentication failed due to bad crypto key ids.
- Default Log Severity
- Warning
- Parameters
- id, recvid, neighborid, iface, rule
- Explanation
- Authentication failed due to bad crypto key ids. The crypto id id, used by interface iface does not match the received crypto id recvid from neighbor neighborid.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Verify that the neighboring OSPF router share the same crypto key id.
2.34.6. [ID: 824] Bad authentication password
- Log Categories
- OSPF
- Log Message
- Bad authentication password.
- Default Log Severity
- Warning
- Parameters
- neighborid, iface, rule
- Explanation
- Authentication failed due to bad password. The authentication password used by interface iface does not match the password from neighbor neighborid.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Verify that the neighboring OSPF router share the same password.
2.34.7. [ID: 814] Authentication failed since received crypto[...]
- Log Categories
- OSPF
- Log Message
- Authentication failed since received crypto sequence number too low.
- Default Log Severity
- Warning
- Parameters
- seqno, recvseqno, neighborid, recviface, rule
- Explanation
- Authentication failed since the received crypto sequence number is too low.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.34.8. [ID: 854] Authentication type mismatch with neighbor[...]
- Log Categories
- OSPF
- Log Message
- Authentication type mismatch with neighbor router.
- Default Log Severity
- Warning
- Parameters
- auth, recvauth, neighborid, recviface, rule
- Explanation
- The authentication type on this and the neighboring OSPF router does not match.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Verify that the neighboring OSPF router have the same authentication type.
2.34.9. [ID: 855] Received OSPF packet with bad length
- Log Categories
- OSPF
- Log Message
- Received OSPF packet with bad length.
- Default Log Severity
- Warning
- Parameters
- len, iplen, type, rule
- Explanation
- The received OSPF packet had a bad length. The OSPF packet type was type, the packet IP length was iplen and the OSPF data length was len.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Verify that neighboring routers are correctly configured.
2.34.10. [ID: 868] Checksum error
- Log Categories
- OSPF
- Log Message
- Checksum error.
- Default Log Severity
- Warning
- Parameters
- chksum, recvchksum, neighborid, recviface, rule
- Explanation
- The received OSPF data had a bad checksum.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Check network equipment for problems.
2.34.11. [ID: 836] Neighbor implied AS-EXT on stub area
- Log Categories
- OSPF
- Log Message
- Neighbor implied AS-EXT on stub area.
- Default Log Severity
- Warning
- Parameters
- neighborid, rule
- Explanation
- A neighbor illegally implied AS-EXT on a stub area.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- Check the configuration on the neighboring OSPF router.
2.34.12. [ID: 856] Received LSA with bad max-age value
- Log Categories
- OSPF
- Log Message
- Received LSA with bad max-age value.
- Default Log Severity
- Warning
- Parameters
- neighborid, maxage, recvmaxage, rule
- Explanation
- Received LSA with bad max-age value.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- Check the configuration on the neighboring OSPF router.
2.34.13. [ID: 876] Received LSA with bad sequence number
- Log Categories
- OSPF
- Log Message
- Received LSA with bad sequence number.
- Default Log Severity
- Warning
- Parameters
- neighborid, seqno, rule
- Explanation
- The received LSA had a bad sequence number.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- None
2.34.14. [ID: 826] Neighbor replied with unexpected sequence[...]
- Log Categories
- OSPF
- Log Message
- Neighbor replied with unexpected sequence number.
- Default Log Severity
- Warning
- Parameters
- neighborid, recviface, rule
- Explanation
- The system received a DD exchange packet with an unexpected sequence number.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- None
2.34.15. [ID: 837] Neighbor DD packet has too high MTU
- Log Categories
- OSPF
- Log Message
- Neighbor DD packet has too high MTU.
- Default Log Severity
- Warning
- Parameters
- neighborid, mtu, recvmtu, recviface, rule
- Explanation
- The MTU in the received DD packet was too high. The MTU recvmtu in the data received on interface recviface from neighbor neighborid is higher than the MTU on the receive interface.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Lower the MTU on the neighboring OSPF router.
2.34.16. [ID: 825] Neighbor sent non-duplicate in wrong state
- Log Categories
- OSPF
- Log Message
- Neighbor sent non-duplicate in wrong state.
- Default Log Severity
- Warning
- Parameters
- neighborid, recviface, rule
- Explanation
- The system received a non-duplicate DD from a neighbor in a higher state than exchange.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- None
2.34.17. [ID: 871] Neighbor changed options during exchange phase
- Log Categories
- OSPF
- Log Message
- Neighbor changed options during exchange phase.
- Default Log Severity
- Warning
- Parameters
- neighborid, rule
- Explanation
- The system received a DD exchange packet indicating that the neighbor had changed options during the exchange.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- None
2.34.18. [ID: 815] Unknown LSA type
- Log Categories
- OSPF
- Log Message
- Unknown LSA type.
- Default Log Severity
- Warning
- Parameters
- neighborid, type, rule
- Explanation
- A neighbor described an unknown LSA type.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- Check the configuration on the neighboring OSPF router.
2.34.19. [ID: 835] Neighbor misused the I-flag
- Log Categories
- OSPF
- Log Message
- Neighbor misused the I-flag.
- Default Log Severity
- Warning
- Parameters
- neighborid, recviface, rule
- Explanation
- The system received a DD exchange packet in which the I-flag was set.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- None
2.34.20. [ID: 845] Neighbor M-MS mismatch
- Log Categories
- OSPF
- Log Message
- Neighbor M-MS mismatch.
- Default Log Severity
- Warning
- Parameters
- neighborid, recviface, rule
- Explanation
- The system received a DD exchange packet indicating that the neighbor got the M/MS (master/slave) role wrong.
- Gateway Action
- Abort
- Action Description
- The current DD exchange is aborted and restarted
- Proposed Action
- None
2.34.21. [ID: 853] Generic event
- Log Categories
- OSPF
- Log Message
- Generic event.
- Default Log Severity
- Debug
- Parameters
- type, loglevel, reason, rule
- Explanation
- A DDesc debug log event of level loglevel occurred. The event is described in the parameter reason. This log event can be enabled/disabled by configuring the OSPF process config object.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.22. [ID: 830] Generic event
- Log Categories
- OSPF
- Log Message
- Generic event.
- Default Log Severity
- Debug
- Parameters
- type, loglevel, reason, rule
- Explanation
- A EXCHANGE debug log event of level loglevel occurred. The event is described in the parameter reason. This log event can be enabled/disabled by configuring the OSPF process config object.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.23. [ID: 874] Cannot map PTP neighbor to local IP
- Log Categories
- OSPF
- Log Message
- Cannot map PTP neighbor to local IP.
- Default Log Severity
- Warning
- Parameters
- neighborid, ip, iface, rule
- Explanation
- Unable to map a configured PTP neighbor to the local IP at HA fail over.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- Check OSPF interface configuration.
2.34.24. [ID: 823] Generic event
- Log Categories
- OSPF
- Log Message
- Generic event.
- Default Log Severity
- Debug
- Parameters
- type, loglevel, reason, rule
- Explanation
- A HELLO debug log event of level loglevel occurred. The event is described in the parameter reason. This log event can be enabled/disabled by configuring the OSPF process config object.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.25. [ID: 817] Hello packet E-flag mismatch
- Log Categories
- OSPF
- Log Message
- Hello packet E-flag mismatch.
- Default Log Severity
- Warning
- Parameters
- flag, recvflag, iface, rule
- Explanation
- Received a HELLO packet on interface iface, which had a mismatching E-flag configuration. The system uses E-flag value flag which does not match the received flag recvflag. The E-Flag describes how AS-external-LSAs are flooded.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Check that all locally attached OSPF routers share the same E-flag configuration.
2.34.26. [ID: 832] Hello packet N-flag and E-flags are both set[...]
- Log Categories
- OSPF
- Log Message
- Hello packet N-flag and E-flags are both set which is illegal.
- Default Log Severity
- Warning
- Parameters
- iface, rule
- Explanation
- Received a HELLO packet on interface iface which has both the N and E flags set. This is illegal.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Change the configuration on the neighboring router.
2.34.27. [ID: 872] Hello packet interval mismatch
- Log Categories
- OSPF
- Log Message
- Hello packet interval mismatch.
- Default Log Severity
- Warning
- Parameters
- interval, recvinterval, iface, rule
- Explanation
- The HELLO interval property in the received HELLO packet, recvinterval does not match the HELLO interval configured on iface.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Check that all locally attached OSPF routers have the same hello interval.
2.34.28. [ID: 834] Hello packet N-flag mismatch
- Log Categories
- OSPF
- Log Message
- Hello packet N-flag mismatch.
- Default Log Severity
- Warning
- Parameters
- flag, recvflag, iface, rule
- Explanation
- Received a HELLO packet on interface iface, which had a mismatching N-flag configuration. The N-flag describes NSSA details.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Check that all locally attached OSPF routers share the same N-flag configuration.
2.34.29. [ID: 839] Hello packet netmask mismatch
- Log Categories
- OSPF
- Log Message
- Hello packet netmask mismatch.
- Default Log Severity
- Warning
- Parameters
- netmask, recvnetmask, iface, rule
- Explanation
- A OSPF data packet from a neighboring router had a network netmask recvnetmask, that differed from the netmask on the receive iface.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Verify that locally attached OSPF routers have the same netmask as the attaching interfaces.
2.34.30. [ID: 875] Hello packet router dead interval mismatch
- Log Categories
- OSPF
- Log Message
- Hello packet router dead interval mismatch.
- Default Log Severity
- Warning
- Parameters
- interval, recvinterval, iface, rule
- Explanation
- Received a HELLO packet which had a mismatching router dead interval. The interval configured on interface iface does not match the received interval, recvinterval.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Check that all locally attached OSPF routers have the same router dead interval.
2.34.31. [ID: 852] LSA internal checksum error
- Log Categories
- OSPF
- Log Message
- LSA internal checksum error.
- Default Log Severity
- Critical
- Parameters
- rule
- Explanation
- Internal LSA checksum error.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- Restart the OSPF subsystem.
2.34.32. [ID: 865] Got ACK for mismatched LSA
- Log Categories
- OSPF
- Log Message
- Got ACK for mismatched LSA.
- Default Log Severity
- Warning
- Parameters
- type, lsaid, lsartr, rule
- Explanation
- Received acknowledge for mismatched LSA.
- Gateway Action
- Ignore
- Action Description
- The acknowledgment is ignored
- Proposed Action
- None
2.34.33. [ID: 864] Received AS-EXT LSA on stub
- Log Categories
- OSPF
- Log Message
- Received AS-EXT LSA on stub.
- Default Log Severity
- Warning
- Parameters
- neighborid, rule
- Explanation
- An AS external LSA was received which is illegal on a stub area.
- Gateway Action
- Discard
- Action Description
- The LSA was discarded
- Proposed Action
- None
2.34.34. [ID: 843] Received LSA with bad checksum
- Log Categories
- OSPF
- Log Message
- Received LSA with bad checksum.
- Default Log Severity
- Warning
- Parameters
- neighborid, rule
- Explanation
- The received LSA had an incorrect checksum.
- Gateway Action
- Discard
- Action Description
- The LSA was discarded
- Proposed Action
- Check network equipment for problems.
2.34.35. [ID: 840] Bad LSA sequence number
- Log Categories
- OSPF
- Log Message
- Bad LSA sequence number.
- Default Log Severity
- Warning
- Parameters
- neighborid, maxage, recvmaxage, rule
- Explanation
- A LSA with a bad max age was received.
- Gateway Action
- Discard
- Action Description
- The LSA was discarded
- Proposed Action
- None
2.34.36. [ID: 846] Bad LSA sequence number
- Log Categories
- OSPF
- Log Message
- Bad LSA sequence number.
- Default Log Severity
- Warning
- Parameters
- neighborid, seqno, rule
- Explanation
- The received LSA had a bad sequence number.
- Gateway Action
- Discard
- Action Description
- The LSA was discarded
- Proposed Action
- None
2.34.37. [ID: 819] Generic event
- Log Categories
- OSPF
- Log Message
- Generic event.
- Default Log Severity
- Debug
- Parameters
- type, loglevel, reason, rule
- Explanation
- A LSA debug log event of level loglevel occurred. The event is described in the parameter reason. This log event can be enabled/disabled by configuring the OSPF process config object.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.38. [ID: 857] Failed to prepare replacement LSA
- Log Categories
- OSPF
- Log Message
- Failed to prepare replacement LSA.
- Default Log Severity
- Critical
- Parameters
- type, lsaid, lsartr, rule
- Explanation
- Failed to create the LSA replacement for the existing LSA with id lsaid, type type and originating router lsartr.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.39. [ID: 863] Received LSA is older then DB copy
- Log Categories
- OSPF
- Log Message
- Received LSA is older then DB copy.
- Default Log Severity
- Warning
- Parameters
- type, lsaid, lsartr, rule
- Explanation
- The received LSA is older than the copy already in the database.
- Gateway Action
- Discard
- Action Description
- The received LSA will be discarded
- Proposed Action
- None
2.34.40. [ID: 827] REQ packet LSA size mismatch
- Log Categories
- OSPF
- Log Message
- REQ packet LSA size mismatch.
- Default Log Severity
- Warning
- Parameters
- rule
- Explanation
- The received OSPF REQ packet had a mismatching LSA size.
- Gateway Action
- Abort
- Action Description
- Parsing aborted
- Proposed Action
- None
2.34.41. [ID: 842] ACK packet LSA size mismatch
- Log Categories
- OSPF
- Log Message
- ACK packet LSA size mismatch.
- Default Log Severity
- Warning
- Parameters
- recviface, rule
- Explanation
- ACK packet LSA size mismatch.
- Gateway Action
- Abort
- Action Description
- Parsing aborted
- Proposed Action
- None
2.34.42. [ID: 821] Requested LSA size too large
- Log Categories
- OSPF
- Log Message
- Requested LSA size too large.
- Default Log Severity
- Warning
- Parameters
- size, rule
- Explanation
- Unable to create LSA since the size is too large.
- Gateway Action
- Abort
- Action Description
- Unable to create LSA
- Proposed Action
- None
2.34.43. [ID: 828] Received selforiginated LSA for unknown type
- Log Categories
- OSPF
- Log Message
- Received selforiginated LSA for unknown type.
- Default Log Severity
- Warning
- Parameters
- type, rule
- Explanation
- Received selforiginated LSA of unknown type.
- Gateway Action
- Drop
- Action Description
- The LSA will be flushed
- Proposed Action
- None
2.34.44. [ID: 858] UPD packet LSA size mismatch
- Log Categories
- OSPF
- Log Message
- UPD packet LSA size mismatch.
- Default Log Severity
- Warning
- Parameters
- rule
- Explanation
- The received OSPF UPD packet had a mismatching LSA size.
- Gateway Action
- Abort
- Action Description
- Parsing aborted
- Proposed Action
- None
2.34.45. [ID: 1442] Received malformed packet
- Log Categories
- OSPF
- Log Message
- Received malformed packet.
- Default Log Severity
- Warning
- Parameters
- neighborid, type, rule
- Explanation
- Received malformed OSPF packet. The OSPF packet was received from neighborid and were of the type type.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- Verify that neighboring routers are correctly configured.
2.34.46. [ID: 822] Unable to find VLINK transport area
- Log Categories
- OSPF
- Log Message
- Unable to find VLINK transport area.
- Default Log Severity
- Warning
- Parameters
- area, vlink, rule
- Explanation
- Unable to find transport area for the VLINK.
- Gateway Action
- Skip
- Action Description
- Interface is not included in router LSA
- Proposed Action
- Verify the configuration of the OSPF area.
2.34.47. [ID: 831] Neighbor died
- Log Categories
- OSPF
- Log Message
- Neighbor died.
- Default Log Severity
- Warning
- Parameters
- neighborid, iface, rule
- Explanation
- Lost connectivity with neighbor router.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- Check neighbor status and connectivity.
2.34.48. [ID: 820] AS disabled due to failed memory allocation
- Log Categories
- OSPF
- Log Message
- AS disabled due to failed memory allocation.
- Default Log Severity
- Critical
- Parameters
- rule
- Explanation
- An OSPF AS has been disabled due to memory allocation failure.
- Gateway Action
- Disable
- Action Description
- None
- Proposed Action
- Check memory consumption.
2.34.49. [ID: 850] Unable to allocate memory for LSA
- Log Categories
- OSPF
- Log Message
- Unable to allocate memory for LSA.
- Default Log Severity
- Critical
- Parameters
- rule
- Explanation
- The OSPF subsystem was unable to allocate additional memory needed for storing LSA information. The internal states of the
OSPF process might now not correspond to what the neighboring routers expect.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- The OSPF subsystem is out of memory. Try increasing the amount of memory used by OSPF and/or modify the network topology surrounding
this OSPF router.
2.34.50. [ID: 866] Unable to allocate memory for LSA link states
- Log Categories
- OSPF
- Log Message
- Unable to allocate memory for LSA link states.
- Default Log Severity
- Critical
- Parameters
- rule
- Explanation
- The OSPF subsystem was unable to allocate additional memory needed for storing LSA information. The internal states of the
OSPF process might now not correspond to what the neighboring routers expect.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- The OSPF subsystem is out of memory. Try increasing the amount of memory used by OSPF and/or modify the network topology surrounding
this OSPF router.
2.34.51. [ID: 841] Unable to allocate memory for LSA shell states
- Log Categories
- OSPF
- Log Message
- Unable to allocate memory for LSA shell states.
- Default Log Severity
- Critical
- Parameters
- rule
- Explanation
- The OSPF subsystem was unable to allocate additional memory needed for storing LSA information. The internal states of the
OSPF process might now not correspond to what the neighboring routers expect.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- The OSPF subsystem is out of memory. Try increasing the amount of memory used by OSPF and/or modify the network topology surrounding
this OSPF router.
2.34.52. [ID: 873] Unable to allocate memory for router neighbor[...]
- Log Categories
- OSPF
- Log Message
- Unable to allocate memory for router neighbor states.
- Default Log Severity
- Critical
- Parameters
- rule
- Explanation
- The OSPF subsystem was unable to allocate additional memory needed for storing neighbor information. The internal states of
the OSPF process might now not correspond to the what the neighboring routers expect.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- The OSPF subsystem is out of memory. Try increasing the amount of memory used by OSPF and/or modify the network topology surrounding
this OSPF router.
2.34.53. [ID: 829] Unable to allocate memory for SPF vertex[...]
- Log Categories
- OSPF
- Log Message
- Unable to allocate memory for SPF vertex states.
- Default Log Severity
- Critical
- Parameters
- rule
- Explanation
- The OSPF subsystem was unable to allocate additional memory needed for storing SPF vertex information. The internal states
of the OSPF process might now not correspond to the what the neighboring routers expect.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- The OSPF subsystem is out of memory. Try increasing the amount of memory used by OSPF and/or modify the network topology surrounding
this OSPF router.
2.34.54. [ID: 818] Generic event
- Log Categories
- OSPF
- Log Message
- Generic event.
- Default Log Severity
- Debug
- Parameters
- type, loglevel, reason, rule
- Explanation
- A packet debug log event of level loglevel occurred. The event is described in the parameter reason. This log event can be enabled/disabled by configuring the OSPF process config object.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.55. [ID: 859] Generic event
- Log Categories
- OSPF
- Log Message
- Generic event.
- Default Log Severity
- Debug
- Parameters
- type, loglevel, reason, rule
- Explanation
- A route debug log event of level loglevel occurred. The event is described in the parameter reason. This log event can be enabled/disabled by configuring the OSPF process config object.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.56. [ID: 1053] Received Router LSA which contains mismatched[...]
- Log Categories
- OSPF
- Log Message
- Received Router LSA which contains mismatched Link State ID and Advertising Router.
- Default Log Severity
- Warning
- Parameters
- lsaid, lsartr, rule
- Explanation
- None
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.34.57. [ID: 838] Generic event
- Log Categories
- OSPF
- Log Message
- Generic event.
- Default Log Severity
- Debug
- Parameters
- type, loglevel, reason, rule
- Explanation
- A SPF debug log event of level loglevel occurred. The event is described in the parameter reason. This log event can be enabled/disabled by configuring the OSPF process config object.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- None
2.34.58. [ID: 833] Unable to send data on interface
- Log Categories
- OSPF
- Log Message
- Unable to send data on interface.
- Default Log Severity
- Warning
- Parameters
- destip, iface, rule
- Explanation
- The interface iface could not send data to the specified address destip.
- Gateway Action
- None
- Action Description
-
- Proposed Action
- Verify that the interface is up and running and that is has link.
2.34.59. [ID: 849] Sender source IP not in interface range
- Log Categories
- OSPF
- Log Message
- Sender source IP not in interface range.
- Default Log Severity
- Warning
- Parameters
- srcip, iprange, iface, rule
- Explanation
- The source IP (srcip) on the received OSPF data is not within the receive interface iface range iprange.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Verify that all locally attached OSPF routes are on the same network.
2.34.60. [ID: 869] Too many neighbors on interface
- Log Categories
- OSPF
- Log Message
- Too many neighbors on interface.
- Default Log Severity
- Warning
- Parameters
- iface, rule
- Explanation
- There are too many OSPF routers on a directly connected network. Unable to maintain 2-way with all of them(hello packet).
- Gateway Action
- Skip
- Action Description
- Some neighbors are skipped and are not described in outgoing HELLO packets
- Proposed Action
- Reduce the number of OSPF routers on the network.
2.34.61. [ID: 862] Unknown LSA type
- Log Categories
- OSPF
- Log Message
- Unknown LSA type.
- Default Log Severity
- Warning
- Parameters
- neighborid, type, rule
- Explanation
- The received LSA was of unknown type.
- Gateway Action
- Discard
- Action Description
- The LSA was discarded
- Proposed Action
- Check the configuration on the neighboring OSPF router.
2.34.62. [ID: 860] Unknown neighbor
- Log Categories
- OSPF
- Log Message
- Unknown neighbor.
- Default Log Severity
- Warning
- Parameters
- neighborid, neighborip, iface, rule
- Explanation
- Unknown neighbor seen on PTP based interface.
- Gateway Action
- None
- Action Description
- None
- Proposed Action
- Verify the configuration on the neighboring OSPF router.
2.34.63. [ID: 816] Unknown OSPF packet type
- Log Categories
- OSPF
- Log Message
- Unknown OSPF packet type.
- Default Log Severity
- Warning
- Parameters
- type, recviface, rule
- Explanation
- The received OSPF data was of an unknown type.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Check the configuration on the neighboring router.
2.34.64. [ID: 847] Packet version is not OSPFv2
- Log Categories
- OSPF
- Log Message
- Packet version is not OSPFv2.
- Default Log Severity
- Warning
- Parameters
- version, rule
- Explanation
- Packet version is not OSPFv2.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None