Case 2 - Firmware malfunction

Firmware malfunction is the primary focus of this troubleshooting section. This cause of failure is characterized by proper operation of the NION followed by occurrence of an HF2 error. Subsequent power cycling of the NION can return the device to proper operation. Although the root cause is a firmware problem, there are network related issues that can stimulate the problem and steps that can be taken to mitigate it.

The CM-1 firmware, up to and including version 2.9.16, contains a bug. This bug will allow a stack overflow to occur during times of excessive network traffic that will render the CM-1 inoperative. This problem can occur in any CM-1 module installed in a NION, CAB or Mainframe.

Upgrading the firmware will fix this problem. If you are using a revision F or earlier CM-1 card, upgrade to 2.9.16.3 or later. If you are using a revision J CM-1 card, upgrade to 2.21.17 or later. For information, see Supported CobraNet firmware in the NION CobraNet Hardware Manual.

Note: The CAB 4n is available with both CM-1 and CM-2 modules. Only CM-1 modules are affected.

Verification of the problem - all conditions will be present

• The CM-1 will initially work properly.
• The CM-1 will become unresponsive. This can be indicated by an inability to change bundles.
• An HF2 related error will be logged.
• All audio bundles in and out of the CM-1 will stop.
• The CobraNet interface will not show active in CobraNet Discovery.
• The LED indicators on the CobraNet RJ-45 Ethernet connectors will most likely be static and in a random state. They will not be blinking in the normal pattern that indicates CobraNet activity. In some cases, the lights will blink in a repeatable pattern of 7,6,2.
• A hardware reset will correct the problem.