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.
installArmStateTrap
.1.3.6.1.4.1.17713.7.99.0.10
Indicates if the unit is being installed. NB: a change
of state may generate an SNMP trap and/or SMTP email
alert
unitOutOfCalibrationTrap
.1.3.6.1.4.1.17713.7.99.0.11
The unit is out of calibration
auxPortPowerOverEthernetOutputStatusTrap
.1.3.6.1.4.1.17713.7.99.0.12
Current status of the Power Over Ethernet (PoE) output
of the Aux port
incompatibleRegulatoryBandsTrap
.1.3.6.1.4.1.17713.7.99.0.14
The master and slave units have incompatible regulatory
bands. NB: Both units must have compatible license keys
noWirelessChannelAvailableTrap
.1.3.6.1.4.1.17713.7.99.0.15
Spectrum Management was unable to locate a suitable
wireless channel to operate on
wirelessLinkDisabledWarningTrap
.1.3.6.1.4.1.17713.7.99.0.16
The SNMP ifAdminStatus of the wireless interface has
disabled wireless traffic
auxPortConfigurationMismatchTrap
.1.3.6.1.4.1.17713.7.99.0.17
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.
sFPErrorTrap
.1.3.6.1.4.1.17713.7.99.0.18
If the SFP link is not OK, there are five possible
causes: Either a SFP has been installed but the license
key does not include SFP fiber support, a fiber 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), a fiber link could not be
established and LOS is detected (i.e. no optical carrier
is detected), the installed SFP is not supported or the
installed SFP failed to initialize correctly. NB: a
change of status may generate an SNMP trap and/or SMTP
email alert
sFPPortStatusTrap
.1.3.6.1.4.1.17713.7.99.0.19
Current status of the SFP Ethernet link. NB: a change of
state may generate an SNMP trap and/or SMTP email alert
dfsImpulsiveInterferenceTrap
.1.3.6.1.4.1.17713.7.99.0.2
DFS impulsive interference detected event
incompatibleMasterAndSlaveTrap
.1.3.6.1.4.1.17713.7.99.0.20
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
sNTPSyncTrap
.1.3.6.1.4.1.17713.7.99.0.21
If SNTP Sync fails then check the server settings in the
Remote Management page, or disable SNTP
tDDSynchronizationAlarmTrap
.1.3.6.1.4.1.17713.7.99.0.22
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.
sFPPortDisabledWarningTrap
.1.3.6.1.4.1.17713.7.99.0.23
The SNMP ifAdminStatus of the interface has disabled
Ethernet traffic
sFPPortConfigurationMismatchTrap
.1.3.6.1.4.1.17713.7.99.0.24
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.
linkModeOptimizationMismatchTrap
.1.3.6.1.4.1.17713.7.99.0.25
The remote node of this link has been configured with a
different link mode optimization
tDMInterfaceStatusTrap
.1.3.6.1.4.1.17713.7.99.0.26
@Current status of the connection to the TDM Box. A
state of 'Up' on a green background indicates that the
TDM Box is connected OK. When connecting a TDM Box only
the Main Ethernet port should be used
tDMChannelStatusTrap
.1.3.6.1.4.1.17713.7.99.0.27
Current status of the TDM channels. A value of 0
indicates that a TDM channel is established
tDMChannelLoopbackTrap
.1.3.6.1.4.1.17713.7.99.0.28
The loopback status of TDM channels. 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
nIDULanPortStatusTrap
.1.3.6.1.4.1.17713.7.99.0.29
Current status of the NIDU LAN Ethernet link. NB: a
change of state may generate an SNMP trap and/or SMTP
email alert
mainPSUPortStatusTrap
.1.3.6.1.4.1.17713.7.99.0.3
Current status of the Main PSU Ethernet link. NB: a
change of state may generate an SNMP trap and/or SMTP
email alert
syslogStateTrap
.1.3.6.1.4.1.17713.7.99.0.30
The syslog service has been enabled or disabled
syslogLocalNearlyFullTrap
.1.3.6.1.4.1.17713.7.99.0.31
The syslog local log is nearly full (90%)
syslogLocalWrappedTrap
.1.3.6.1.4.1.17713.7.99.0.32
The syslog local log has wrapped
syslogClientTrap
.1.3.6.1.4.1.17713.7.99.0.33
Enable or disable the syslog client
secureModeAlarmTrap
.1.3.6.1.4.1.17713.7.99.0.34
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.
dataBridgingStatusAlarmTrap
.1.3.6.1.4.1.17713.7.99.0.35
Ethernet Data traffic bridging is disabled because the
wireless link is not operating at the configured Lowest
Data Modulation Mode
licenseRemainingTrialPeriodAlarmTrap
.1.3.6.1.4.1.17713.7.99.0.36
If the full capability trial license period is about to
expire then purchase a license upgrade from your
reseller.
capacityVariantMismatchTrap
.1.3.6.1.4.1.17713.7.99.0.37
The remote node of this link has a lower link capacity.
Operating with a reduced effective link capacity.
maxLinkRangeExceededTrap
.1.3.6.1.4.1.17713.7.99.0.38
The measured link range is greater than the maximum
allowed by the license key. The link will operate at a
reduced capacity while this condition applies. This alarm
is only raised if the license specifies a maximum link
range and the trial license is not active.
tDMConfigurationMismatchTrap
.1.3.6.1.4.1.17713.7.99.0.39
Current status of the configuration of the TDM Box. A
state of 'Ok' on a green background indicates that the
TDM Box configuration is matched OK with the remote end.
mainPSUPortDisabledWarningTrap
.1.3.6.1.4.1.17713.7.99.0.4
The SNMP ifAdminStatus of the interface has disabled
Ethernet traffic
nIDULanPortDisabledWarningTrap
.1.3.6.1.4.1.17713.7.99.0.40
The SNMP ifAdminStatus of the interface has disabled
Ethernet traffic
nIDULanPortConfigurationMismatchTrap
.1.3.6.1.4.1.17713.7.99.0.41
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.
secondDataBridgingStatusAlarmTrap
.1.3.6.1.4.1.17713.7.99.0.42
Bridging of Ethernet traffic from Second Data Service
has been disabled because the wireless link is not
operating at the configured Lowest Second Data Modulation
Mode
transparentClockSourcePortAlarmTrap
.1.3.6.1.4.1.17713.7.99.0.43
Transparent Clock will not function properly because
SFP, the selected clock source port is not FIBER
portAllocationMismatchTrap
.1.3.6.1.4.1.17713.7.99.0.44
The local and remote ODUs have different services
configured.
mainPSUPortConfigurationMismatchTrap
.1.3.6.1.4.1.17713.7.99.0.5
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
auxPortStatusTrap
.1.3.6.1.4.1.17713.7.99.0.6
Current status of the Aux Ethernet link. NB: a change of
state may generate an SNMP trap and/or SMTP email alert
auxPortDisabledWarningTrap
.1.3.6.1.4.1.17713.7.99.0.7
The SNMP ifAdminStatus of the interface has disabled
Ethernet traffic
regulatoryBandTrap
.1.3.6.1.4.1.17713.7.99.0.8
The Regulatory Band prohibits the wireless unit from
operating outside the regulated limits. An invalid
Regulatory Band may be caused by a missing or incorrect
License Key, a corrupt MAC Address or an attempt to
configure a Regulatory Band not allowed by the License
Key. NB: a change of state may generate an SNMP trap
and/or SMTP email alert.
installStatusTrap
.1.3.6.1.4.1.17713.7.99.0.9
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