TCP dbx output sbappendaddr_failed_nospace

[Chris Ellam]

My sys_check TCP dbx output lists that sbappendaddr_failed_nospace has occured 366174 times during a 16 hour full load test period and I am trying figure out what this means. This is an ES80 and it has a gigabit network and the system get lots of broadcast info that is sent to 1 socket. There are no dropped packets on bcm0 so it looks as though the bcm driver is able to process all the incomming data. I am not sure though whether it is the driver that then does the socket work or whether it is another Tru64 process.

Can somebody explain how this works?
Here are the rest of the dbx output for sockets
====== somaxconn: 1024
====== sominconn: 0
====== sb_max: 20971520
====== sbcompress_threshold: 0
====== total_tcp_inpcbs: 171
====== tcbhashsize: 512
====== sobacklog_hiwat: 2
====== sobacklog_drops: 0
====== somaxconn_drops: 0
====== sbappendaddr_failed_addrtoolong: 0
====== sbappendaddr_failed_nombuf: 0
====== sbappendaddr_failed_nospace: 366174