No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ISIS/4/IS_RECV_ERR_PKT

ISIS/4/IS_RECV_ERR_PKT

Message

ISIS/4/IS_RECV_ERR_PKT:ISIS-INFO: Dropped an error packet. (PktType=[PktType], ProcessId=[ProcessId], ErrReason=[ErrReason], ErrCount=[ErrCount], InterfaceName=[InterfaceName])

Description

ISIS drop the error packets received.

Statistics about received error packets are collected based on the packet type, and statistics about the five types of error packets that are received most within 15 minutes are displayed. Each module collects error packet statistics and generates logs independently.

Upon reception of the first error packet, each module generates a log and starts to collect statistics at an interval of 15 minutes. If no other error packets are received within 15 minutes, the module stops statistics collection and continues the collection when it receives another error packet.

Parameters

Parameter Name Parameter Meaning

PktType

Type of error packets

ProcessId

ID of the IS-IS process that receives error packets

ErrReason

Reason why the packet is an error packet:
  • 1. The length of the fixed header parsed from the Hello packet header is incorrect, or the length of the Hello packet is less than that of the fixed header.
  • 2. The value of the Reserved/Circuit Type field in the Hello packet is incorrect.
  • 3. The Source ID field in the Hello packet is the same as the local system ID.
  • 4. The Circuit Type field in the Hello packet does not match the packet type.
  • 5. The length of the Hello packet is greater than the value of lsp-length originate.
  • 6. The value of the ID length field in the Hello packet is not 0 or 6.
  • 7. The Protocol TLV field in the Hello packet does not match the local protocol.
  • 8. The level of the Hello packet does not match the local level.
  • 9. The value of the Version/Protocol ID Extension field in the Hello packet is incorrect.
  • 10. The value of the Version field in the Hello packet is incorrect.
  • 11. The value of the Maximum Area Address field in the Hello packet does not match the local counterpart.
  • 12. The TLV parsed from the Hello packet is incorrect.
  • 13. The Hello packet carries no area address TLV.
  • 14. The area address in the area address TLV of the Hello packet is too long.
  • 15. The area address in the Level-1 Hello packet does not match the local counterpart.
  • 16. The neighbor IP address in the Hello packet is on a different network segment.
  • 17. The SNPA address in the Hello packet received on a broadcast network conflicts with the local counterpart.
  • 18. The Hello packet carries an invalid authentication field.
  • 19. The Hello packet carries superfluous authentication TLVs.
  • 20. The three-way handshake information in the Hello packet is incorrect.
  • 21. The IPv6 address in the Hello packet is invalid.
  • 22. The Hello packet carries superfluous area TLVs.
  • 23. The area TLV in the Hello packet is incorrect.
  • 24. The Hello packet carries superfluous IP address TLVs.
  • 25. The IP address TLV in the Hello packet is incorrect.
  • 26. The number of neighbors in the Hello packet exceeds the maximum number (128) of neighbors supported on an interface.
  • 27. The value of the Holding Time field in the Hello packet is 0.
  • 28. The IP address in the Hello packet conflicts with the IP address of the local interface.
  • 29. The Hello packet carries superfluous IPv6 address TLVs.
  • 30. The IPv6 address in the Hello packet conflicts with the IPv6 address of the local interface.
  • 51. The LSP header is shorter than a fixed header length.
  • 52. The level of the LSP does not match the local level.
  • 53. The system ID in the LSP is invalid.
  • 54. The sequence number of the LSP is 0.
  • 55. The IS type of the LSP is invalid.
  • 56. The value of the Maximum Area Address field in the LSP does not match the local counterpart.
  • 57. The checksum of the LSP is 0.
  • 58. The checksum of the LSP is incorrect.
  • 59. The authentication field of the LSP is incorrect.
  • 60. The TLV length of the LSP is incorrect.
  • 61. The LSP carries more than one protocol TLV.
  • 62. The LSP is too long.
  • 63. The Nbr TLV field in the LSP is incorrect.
  • 64. The Extended IS TLV field in the LSP is incorrect.
  • 65. The Reach TLV field in the LSP is incorrect.
  • 66. The Area TLV field in the LSP is incorrect.
  • 67. The SRLG TLV field in the LSP is incorrect.
  • 68. The IPV6 Reach TLV field in the LSP is incorrect.
  • 69 The LSP is received from an unknown adjacency.
  • 70. The Extended Reach TLV field in the LSP is incorrect.
  • 71. The TE Router ID TLV field in the LSP is incorrect.
  • 72. The MT IS Reach TLV field in the LSP is incorrect.
  • 73. The MT ID TLV field in the LSP is incorrect.
  • 74. The MT IPv6 Prefix TLV field in the LSP is incorrect.
  • 75. The value of the Remain Life Time field in the LSP is 0.
  • 76. The LSP carries superfluous authentication TLVs.
  • 77. The IP address TLV field in the LSP is incorrect.
  • 78. The Alias TLV field in the LSP is incorrect.

ErrCount

Number of received error packets

InterfaceName

Name of interface

Possible Causes

  • Message errors occurred during transmission on the network.
  • The messages were rewritten by a device during uploading or downloading.

Procedure

  • Collect the log information, and then contact technical support personnel technical personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 137841

Downloads: 90

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next