User's Manual

ULP EMS Operator Guide Maintaining and Operating the ULP Network
On-Ramp Wireless Confidential and Proprietary 40 010-0045-00
The operator can attempt to clear the alarm by rebooting the AP generating this alarm. If this
clears the alarm, call On-Ramp Wireless.
If rebooting the AP does not clear the alarm, move the AP to an offline state in the EMS, and call
On-Ramp Wireless.
3.6.1.5 Overload Adjustment
The overload adjustment alarm is not likely to be cleared without a service call to On-Ramp
Wireless. If this alarm is detected, call On-Ramp Wireless. On-Ramp Wireless may schedule a
service call to perform an AP forced rescan to fix this issue.
3.6.1.6 Software Asserts
The On-Ramp Wireless AP, GW, and Node software automatically detects various error
conditions. When an error is detected, the software may generate an assert alarm.
The assert alarm generates a log message with a reason code, including a line of code and the
file responsible for the alarm. If there is an AP, GW, or Node assert alarm, it is typically expected
that the assert will result in an automatic restart of the GW, AP, or Node that generated the
assert condition.
In the event of an assert alarm, the following situations may exist:
1. The underlying cause of the software alert is due to an unforeseen system issue, such as an
assert that is being generated repeatedly. This indicates that there is a system failure, and
the operator must call On-Ramp Wireless.
2. The underlying cause of the software alert is due to an unforeseen event that happens very
infrequently. This assert is not likely to be seen again, and the system is again operating as
expected. Notify On-Ramp Wireless of this assert alarm.
3.6.1.7 Node Frequent Rejoin
If an end device is frequently rejoining, it can indicate an error in many different aspects of the
system.
The operator should schedule a service call. The appropriate On-Ramp Wireless personnel may
come on site to get additional information from the EMS system. The On-Ramp Wireless
personnel may also direct an EMS operator to enable additional debugging aspects of the device
through the EMS console.
To clear the problem, try to reboot the GW and/or AP. This may not resolve the problem.
3.6.1.8 Node Missed Intervals
This alarm indicates that an end device missed a configurable number of scheduled update
intervals.
The system uses the following defaults for missed intervals:
 Three missed intervals trigger a minor alarm.