Peavey MediaMatrix Nion Hardware Manual page 71

The causes of HF2 errors
HF2 related errors could have two basic causes:

A hardware error. The physical hardware is at fault.

The firmware running on the CM-1 has malfunctioned and cannot respond to the NION.
Case 1 - Hardware error
In this case the interface between the CM-1 and NION has failed due to a chronic hardware
problem. This condition can be identified by persistence of the error through multiple power
cycles of the NION. A hardware fault can only be remedied by repair or replacement of the
failed component. Please consult your dealer for further information regarding repair or
replacement of hardware.
A hardware error can also be caused by a NION operating at elevated temperature. Address
cooling and ventilation issues when this cause is suspected.
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. A fix is not currently available, but is being worked on. This problem can occur in
any CM-1 module installed in a NION, CAB or Mainframe.
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.
The causes of firmware malfunction
Presence of excessive network traffic, also known as a data storm, can cause a stack overflow
to occur. A data storm can be caused by the presence of a loop in the network. Loop problems
can be more acute in larger networks and in networks that contain gigabit Ethernet links. A
data storm can also be caused by malfunctioning equipment in rare cases.
June 11, 2012 Version 1.6.4b.1
NION Hardware Manual
67