TCP/IP Stack flow error on AP8853

[DCIM_Support]

tcp/ip stack flow error - AP8853 on about 10 PDU's out of 50 Firmware 6.1

01/15/2016         05:39:41               System TCP/IP stack failure. Module: tvSheapFree-assertion error line 580, file(.\treck\source\trsheap.c)

(CID:105462217)

[DCIM_Support · Accepted solution]

Hi Steven Johnstone,

This issue is resolved in AOS v6.1.3 or higher.  Each Network Management Card has an AOS and application file and they cannot be updated independently. Please check http://www.apc.com/tools/download/index.cfm to verify the latest versions available for your device.
For users that are unable to upgrade or if your application does not have AOS 6.1.3 or higher bundled yet, the following options are available:

• Pursue caching the MX Record for your selected SMTP server on the DNS server (or use a DNS server that has the record cached)  
• Consider downgrading to v5.1.X firmware for your application while reviewing the information and support for downgrading in knowledge base article FA167693, titled Things To Consider When Upgrading or Downgrading a Network Management Card 2 (NMC2) Device between v5.X.X and v6.X.X.

 Check the below knowledge base link.

http://www.apc.com/site/support/us/en/faq/?page=content&country=ITB〈=en&locale=en_US&id=FA177701&red...

Regards,

Rana Ajmal

(CID:105462224)

[DCIM_Support]

Hi Rana, Thanks for your reply I guessed it might be firmware related but they are all on AOS 6.1.3. Any ideas maybe upgrade to higner version? Thanks

(CID:105462228)

[DCIM_Support]

Hi Steven, Try to upgrade on Firmware Revision 6.4.0

(CID:105462232)

[DCIM_Support]

Thanks will try 6.40

(CID:105462491)

[DCIM_Support]

FYI s.johnstone & Rana Ajmal - that knowledge base covers a very specific TCP/IP stack failure, not all of them. Note the specific error in the log for that issue would be "TCP/IP stack failure. Module: tfDnsGetMailHost-assertion error line 1266, file(.\treck\source\trresolv.c)" and the message Steven posted is different. I do agree, the best course of action, if possible, is to upgrade to 6.4.0 and see if the issue still exists. That is our newest firmware and is a few revisions newer than AOS 6.1.3/rpdu2g APP 6.0.9/6.1.0. It also has enhanced debugging capability for issues like this. If the issue still exists in 6.4.0, then we need the .tar file from a few of the PDUs exhibiting the problem to review. Instructions on downloading the .tar file are here -> http://www.schneider-electric.us/en/faqs/FA156131

(CID:105462272)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.