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>

Reminder

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

upgrade

FAQ-What Does an Exceptional Assertion Occurring to the NE40 Mean

Publication Date:  2012-07-27 Views:  47 Downloads:  0
Issue Description
What does an exceptional assertion occurring to the NE40 mean?
The exceptional assertion occurring to the NE40 is as follows:
display lpu assertq 1 1
Start to display Assert queue board 01…
There are 4 items in queue of slot 1:
11-30 14:02:04 Ticks 0x53df15ea DEC 240626 slot 1 ASSERT(0)fails! TaskIndex
0xe,../../Source//nps_8011/pts/np_d6_buf.c,279d6_get_buf err: size=15064 too big
1 Layer:0x377760
2 Layer:0x5cb2a0
3 Layer:0x5cb578
4 Layer:0x68f57c
5 Layer:0x6cea18
6 Layer:0x6cf618
7 Layer:0x807c8c
11-30 14:03:05 Ticks 0x53df1dda DEC 219013 slot 1 ASSERT(0)fails! TaskIndex
0xe,../../Source//nps_8011/pts/np_d6_buf.c,279d6_get_buf err: size=15064 too
big
1 Layer:0x377760
2 Layer:0x5cb2a0
3 Layer:0x5cb578
4 Layer:0x68f57c
5 Layer:0x6cea18
6 Layer:0x6cf618
7 Layer:0x807c8c 
Alarm Information
 Null 
Handling Process
The assertion is caused by too large a data packet (0xe,../../Source//nps_8011/pts/np_d6_buf.c,279d6_get_buf err: size=15064 too big) received by the NE40. It is an error packet or other cause on the network and will have no effect on the operation of the NE40.
The NE40 usually may receive two types of packets during operation. One type is the packets that the NE40 needs to forward. Most packets are of this type. No matter how large these packets are, the NE40 fragments them according to the MTU. Therefore, these packets have no effect on the NE40.
The other type is packets that are sent to the NE40, including ping packets and protocol packets. Packets of this type need to be sent to the main control board and the size of these packets cannot exceed 15000 bytes. If the size exceeds 15000 bytes, the above assertion occurs.
Usually, there are no such large ping packets or protocol packets and the assertion is caused by error packets.
Therefore, you do not need to worry about how many times the assertion occurs. 
Root Cause
 Null 
Suggestions
 Null 

END