User's Manual
ULP EMS Operator Guide Maintaining and Operating the ULP Network
On-Ramp Wireless Confidential and Proprietary 38 010-0045-00
2. A system administrator can control additional default parameters for the following
alarms through editing the /opt/onramp_apps/nms_config.properties file on the EMS
server. If editing the nms_config.properties file after starting the EMS, restart the EMS
backhaul to show the changes. Some alarms can be permanently disabled by setting
parameters in the nms_config.properties file. For detailed information about
permanently disabling alarms, call On-Ramp Wireless.
a. The following alarms have configuration parameters in the nms_config.properties
file:
GW Health Alarm Timeout
Node Missed Intervals
Node Frequent Rejoins
Sysmon Node Communications
b. To restart the EMS backhaul, the system administrator should log in to the EMS
server through a terminal and run:
/sbin/service onramp_EMS_backhaul stop
/sbin/service onramp_EMS_backhaul start
3.6.1.1 GW Process Health
This type of alarm indicates that the EMS and Gateway (GW) cannot maintain communication
through the network backhaul. The following conditions can cause a connectivity alarm:
1. The GW server and/or software process has died. To verify that the GW server and software
are running, complete these steps:
a. Log on to the physical GW server using a UNIX
®
/Linux
®
terminal shell. If the operator
cannot log in to the GW, they may need to verify the physical status of the GW.
b. Run the following command from the shell prompt:
/sbin/service ulp-gateway status
The output from this indicates if the GW is running.
c. Restart the GW with the following commands from the shell prompt:
/sbin/service ulp-gateway stop
/sbin/service ulp-gateway start
2. The network connectivity between the EMS and the GW is broken. An operator should use
the standard networking debugging tools to verify the availability of the backhaul
connectivity between the EMS and the GW. For example, the operator can ping the GW to
validate that it is available through the backhaul network. When re-establishing the
backhaul connectivity, the operator may need to contact the backhaul provider to help
diagnose the issue.