The PTP radio has changed wireless channel.
This has been caused by either
i) mandatory radar avoidance,
   a DFS impulsive interference event will also be
   detected,
or
ii) Dynamic Spectrum Optimization, (DSO)
    DSO improves link performance by selecting the
    most appropriate transmit and receive channels
    with the lowest level of interference.

Indicates if the unit is being installed. NB: a change 
of state may generate an SNMP trap and/or SMTP email 
alert

The unit is out of calibration

The master and slave units have incompatible region 
codes. NB: Both units must have compatible license keys

Spectrum Management was unable to locate a suitable 
wireless channel to operate on

The SNMP ifAdminStatus of the wireless interface has 
disabled wireless traffic

The SNMP ifAdminStatus of the Ethernet interface has 
disabled Ethernet traffic

If the fiber link is not OK, there are three possible 
causes: Either the fiber link has been installed but 
disabled (because the license key does not include fiber 
support), the link could not be established even though 
no LOS was detected (i.e. an optical carrier was 
detected, which could be due to a broken TX fiber, or 
because the link is disabled at the fiber link partner), 
or the link could not be established and LOS is detected 
(i.e. no optical carrier is detected). NB: a change of 
status may generate an SNMP trap and/or SMTP email alert

The detection of Ethernet fragments (runt packets) when 
the link is in full duplex is an indication of an 
auto-negotiation or forced configuration mismatch

DFS impulsive interference detected event

A non-zero value indicates that the master and slave 
ends of a link are different hardware products, or have 
different software versions. NB: It is very unusual to 
detect this, because incompatible units will normally 
fail to establish a wireless link. However, some 
combinations may establish a partial wireless link and 
detect this situation. NB: A non-zero value may generate 
an SNMP trap and/or SMTP email alert

If SNTP Sync fails then check the server settings in the 
Remote Management page, or disable SNTP

Not Synchronized indicates failure of the external 
timing system for a period greater than the holdover 
timer. TDD frame timing will have drifted, and this link 
may cause interference with other links in a synchronized 
network. Timing System Failure is an early warning, 
indicating that 80% of the holdover period has expired.

Current status of the out-of-band management link. NB: a 
change of state may generate an SNMP trap and/or SMTP 
email alert

The SNMP ifAdminStatus of the out-of-band management 
interface has disabled Ethernet traffic

The remote node of this link has been configured with a 
different link mode optimization

The detection of Ethernet fragments (runt packets) when 
the link is in full duplex is an indication of an 
auto-negotiation or forced configuration mismatch. This 
alarm is only raised if an Out-of-Band Management Mode 
has been configured.

Current status of the Ethernet link. NB: a change of 
state may generate an SNMP trap and/or SMTP email alert

The syslog service has been enabled or disabled

The syslog local log is nearly full (90%)

The syslog local log has wrapped

Enable or disable the syslog client

The secure mode (e.g. FIPS, UC-APL) state of the unit. 
The secure mode is not configured(1) state indicates that 
the unit is capable of secure mode operation, and one or 
more of the following security materials has not been 
configured: Key Of Keys, Private Key, Public Certificate, 
DRNG Entropy Status, Wireless Encryption Key. The secure 
mode mode is configured but not active(2) state indicates 
that the unit is capable of secure mode operation, and 
the security material has been configured, but the 
configuration of interfaces is not consistent with secure 
mode operation. The secure mode is not supported(3) state 
indicates that the unit is not capable of secure mode 
operation. The secure mode capability requires 
appropriate hardware compatibility, license key and 
software image.

Ethernet traffic bridging is disabled because the 
wireless link is not operating at the configured Lowest 
Ethernet Modulation Mode

Current status of telecoms channel A. NB: a change of 
state may generate an SNMP trap and/or SMTP email alert

Current status of telecoms channel B. NB: a change of 
state may generate an SNMP trap and/or SMTP email alert

The loopback status of telecoms channel A. This is 
intended for installation testing and should be set to 
'None' for normal operation. The wire connections to a 
unit can be tested by applying a 'Copper' loopback to the 
local unit. The wireless connection to the remote unit 
can be tested by applying a 'Wireless' loopback to the 
remote unit with no loopback on the local unit. NB: a 
change of state may generate an SNMP trap and/or SMTP 
email alert

The loopback status of telecoms channel B. This is 
intended for installation testing and should be set to 
'None' for normal operation. The wire connections to a 
unit can be tested by applying a 'Copper' loopback to the 
local unit. The wireless connection to the remote unit 
can be tested by applying a 'Wireless' loopback to the 
remote unit with no loopback on the local unit. NB: a 
change of state may generate an SNMP trap and/or SMTP 
email alert

The region code prohibits the wireless unit from 
operating outside the regulated limits. An invalid region 
code indicates a corrupted license key. NB: a change of 
state may generate an SNMP trap and/or SMTP email alert

A non-zero value indicates that signalling was received 
with the wrong MAC address or a mismatched link name. NB: 
It is very unusual to detect this, because units with 
mis-configured Target MAC Address will normally fail to 
establish a wireless link. However, rare circumstances 
may establish a partial wireless link and detect this 
situation. NB: A non-zero value on start-up, or a change 
of value during operation, may generate an SNMP trap 
and/or SMTP email alert