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


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


Log Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document supports all the logs of device, including the parameters, meaning, possible causes and solution.

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).



SOCKET/6/LSTNASYNQUEINFO:The verbose information about the current asynchronous queue in listening state was displayed. (Read=[ULONG], Write=[ULONG], Connect=[ULONG], Close=[ULONG], PeerClose=[ULONG], Accept=[ULONG], KeepAliveDown=[ULONG], Crammed at: [ULONG]:[ULONG]:[ULONG](Hour:Minute:Seconds), LostMessage=[ULONG], MessageType=[ULONG])


The detailed information about the asynchronous message queue in the listening status was described in the log.


Parameter Name Parameter Meaning
Read indicates the number of Read messages.
Write indicates the number of Write messages.
Connect indicates the number of Connect messages.
Close indicates the number of Close messages.
PeerClose indicates the number of PeerClose messages.
Accept indicates the number of Accept messages.
KeepAliveDown indicates the number of Keep Alive Down messages.
Crammed at indicates the time when the asynchronous message queue becomes full. The format is HH:MM:SS.
LostMessage indicates the number of lost messages.
MessageType indicates the type of lost messages. The types of lost messages are shown as follows

1. Read

2. Write

3. Connect

4. Close

5. Accept

6. PeerClose

7. KeepAliveDown

Possible Causes

The TCP listening socket was closed for a certain cause, and then the information about the asynchronous message queue at the closed TCP listening socket was recorded.


  1. This log message indicates a normal situation, and no action is required.
Updated: 2019-05-29

Document ID: EDOC1000097209

Views: 136071

Downloads: 189

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next