No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

Honeywell Alarm System Going Offline

Publication Date:  2019-07-15  |   Views:  302  |   Downloads:  0  |   Document ID:  EKB1000079801

Contents

Issue Description

After a user logs in to the OMU portal of the server and accesses the External System tab page, the user finds that the added Honeywell alarm system is in offline state, as shown in Figure 9-8. The message Check extern system heart failed is repeatedly displayed in debug logs of the DCG.
Figure 9-7 Honeywell alarm system in offline state

Handling Process

Step 1 Check whether the registration parameters of the Honeywell alarm system are correctly set.
1. Log in to the OMU portal of the server and access the External System tab page.
2. In the System Domains panel, select the Honeywell alarm system.
3. Check whether the registration parameters for connecting to the Honeywell alarm system are correctly set.
 If no, correct the settings based on the site requirements and check whether the fault is rectified.
If the fault is rectified, no further action is required. If the fault persists, go to Step 2.
 If yes, go to the next step.
Step 2 Run the ping command to check whether the Honeywell alarm system is properly connected to the eSpace IVS platform.
 If the network is abnormal, locate and rectify the network fault and check whether the fault is rectified.
If the fault is rectified, no further action is required. If the fault persists, go to Step 3.
 If the network is properly connected, go to the next step.
Step 3 Check whether no alarm has been triggered by the Honeywell alarm system.
1. Trigger an alarm on the Honeywell alarm system.
2. Refresh the OMU portal page and check whether the Honeywell alarm system goes online.
If the Honeywell alarm system goes online, the fault is rectified, and no further action is required. If the fault persists, go to the next step.
Step 4 Check whether alarms sent by the Honeywell alarm system are blocked by the server firewall.
1. On the OMU portal, enable the debug log function for the DCG.
2. Log in to the server as the root user and run the tcpdump -i ethx host alarmSysIP -s0 -vv -w /home/systodcg.pcap command.

 ethx indicates the service network adapter in use, for example, eth0. If you do not know the specific network adapter, you can enter any, indicating that packets of all network adapters are captured. However, this will result in a too large size of captured packets.
 host alarmSysIP indicates that only communication packets between the server and the alarm system whose IP address is the value of alarmSysIP are captured.
 /home/systodcg.pcap indicates the directory where captured packets are stored.
3. Trigger alarms of the same type on the Honeywell alarm system. About 2 minutes later, press Ctrl+C to stop capturing packets.
4. Go to the /home directory and obtain the file storing captured packets (systodcg.pcap). Go to the /home/ivs_dcg/log/debug directory and obtain all debug logs within the packet capturing period.

To minimize disk usage, run the rm /home/systodcg.pcap command to delete systodcg.pcap from the server after obtaining it.
5. Use WireShark to open systodcg.pcap and check whether alarms shown in Figure 9-9 exist.

Obtain the Wireshark installation package from http://www.wireshark.org/.
Figure 9-8 Packets from the Honeywell alarm system to the eSpace IVS platform



 If no, contact Huawei technical support engineers.
 If yes, go to the next step.
6. Check whether Receive HoneyWell msg exists in the debug logs obtained in Step 4.4.
 If yes, contact Huawei technical support engineers.
 If no, go to the next step.
7. Run the rcSuSEfirewall2 status command to check status of the server firewall.
 If the firewall is not enabled, contact Huawei technical support engineers.
 If the firewall is enabled, run the rcSuSEfirewall2 stop command to disable the firewall and go to the next step.
Step 5 Check whether the fault is rectified.
If the fault is rectified, no further action is required. If the fault persists, contact Huawei technical support engineers.

Root Cause

 Registration parameters of the Honeywell alarm system are incorrectly set.
 The network between the Honeywell alarm system and the eSpace IVS platform is abnormal.
 No alarm has been triggered by the Honeywell alarm system.
 Alarms sent by the Honeywell alarm system are intercepted by the server firewall.

NOTE:
After the Honeywell alarm system is added to the OMU portal, an alarm must be triggered on the Honeywell alarm system and sent to the eSpace IVS platform. Otherwise, the Honeywell alarm system will not go online.