dio 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.6.99.0.10
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.6.99.0.11
The unit is out of calibration
incompatibleRegionCodesTrap
.1.3.6.1.4.1.17713.6.99.0.14
and slave units have incompatible region
codes. NB: Both units must have compatible license keys
noWirelessChannelAvailableTrap
.1.3.6.1.4.1.17713.6.99.0.15
anagement was unable to locate a suitable
wireless channel to operate on
wirelessLinkDisabledWarningTrap
.1.3.6.1.4.1.17713.6.99.0.16
fAdminStatus of the wireless interface has
disabled wireless traffic
dataPortDisabledWarningTrap
.1.3.6.1.4.1.17713.6.99.0.17
fAdminStatus of the Ethernet interface has
disabled Ethernet traffic
dataPortFiberStatusTrap
.1.3.6.1.4.1.17713.6.99.0.18
er 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
dataPortConfigurationMismatchTrap
.1.3.6.1.4.1.17713.6.99.0.19
ion of Ethernet fragments (runt packets) when
the link is in full duplex is an indication of an
auto-negotiation or forced configuration mismatch
dfsImpulsiveInterferenceTrap
.1.3.6.1.4.1.17713.6.99.0.2
DFS impulsive interference detected event
incompatibleMasterAndSlaveTrap
.1.3.6.1.4.1.17713.6.99.0.20
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.6.99.0.21
nc fails then check the server settings in the
Remote Management page, or disable SNTP
tDDSynchronizationAlarmTrap
.1.3.6.1.4.1.17713.6.99.0.22
onized 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.
managementPortStatusTrap
.1.3.6.1.4.1.17713.6.99.0.23
atus of the out-of-band management link. NB: a
change of state may generate an SNMP trap and/or SMTP
email alert
managementPortDisabledWarningTrap
.1.3.6.1.4.1.17713.6.99.0.24
fAdminStatus of the out-of-band management
interface has disabled Ethernet traffic
linkModeOptimizationMismatchTrap
.1.3.6.1.4.1.17713.6.99.0.25
node of this link has been configured with a
different link mode optimization
managementPortConfigurationMismatchTrap
.1.3.6.1.4.1.17713.6.99.0.28
ion 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.
dataPortStatusTrap
.1.3.6.1.4.1.17713.6.99.0.3
atus of the 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.6.99.0.30
The syslog service has been enabled or disabled
syslogLocalNearlyFullTrap
.1.3.6.1.4.1.17713.6.99.0.31
The syslog local log is nearly full (90%)
syslogLocalWrappedTrap
.1.3.6.1.4.1.17713.6.99.0.32
The syslog local log has wrapped
syslogClientTrap
.1.3.6.1.4.1.17713.6.99.0.33
Enable or disable the syslog client
secureModeAlarmTrap
.1.3.6.1.4.1.17713.6.99.0.34
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.
ethernetBridgingStatusAlarmTrap
.1.3.6.1.4.1.17713.6.99.0.35
raffic bridging is disabled because the
wireless link is not operating at the configured Lowest
Ethernet Modulation Mode
telecomsChannelAStatusTrap
.1.3.6.1.4.1.17713.6.99.0.4
atus of telecoms channel A. NB: a change of
state may generate an SNMP trap and/or SMTP email alert
telecomsChannelBStatusTrap
.1.3.6.1.4.1.17713.6.99.0.5
atus of telecoms channel B. NB: a change of
state may generate an SNMP trap and/or SMTP email alert
channelALoopbackTrap
.1.3.6.1.4.1.17713.6.99.0.6
ck 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
channelBLoopbackTrap
.1.3.6.1.4.1.17713.6.99.0.7
ck 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
regionCodeTrap
.1.3.6.1.4.1.17713.6.99.0.8
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
installStatusTrap
.1.3.6.1.4.1.17713.6.99.0.9
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