Gateway Up/Down Notifications HSNM administration backend general discussion

[humzakhan]

Dear Team,

What is the latency to which gateway is consider to be down. We are getting too much unnecessary notifications/alerts. Can we manually configure notifications/alerts parameters ?

[HSNMSupport]

Hi Humzan
HSNM receives datas (CPU load, latency to google, latency to HSNM, etc) from the GW every minutes.
If it doesn't receive datas for 2 minutes, the GW will be labeled as CRITICAL and you will see it in orange
If it doesn't receive datas for 5 minutes, the GW will be labeled as DOWN and you will see it in red

GatewayList.jpg

Best regards

[humzakhan]

i) We are getting down/up notifications only from HSNM frequently. However same gateways are being monitored by other NMS, If any of the node/gateway goes down we should have notification from NMS too, but it is not happening and the Uptime on the mikrotik is also not showing any downtime (refer image). We are only getting notifications from HSNM server.
ii) We are having multiple gateways in same IP pool, for instance if we consider network to be unreachable from HSNM appliance then we must have notifications from other gateways on the same pool too. Which is not happening.

[HSNMSupport]

Hi Humzan
For HSNM the GW is down if it doesn't received any data from it.
Inside the GW there is a script HWMonitor that, every 1 minutes, send CPU load, latency to google, latency to HSNM, network bandwidth to HSNM,etc. You should check, inside the Mikrotik GW, the value "P: ....." on Data variable in order to understand if HSNM is reachable from GW: you should have something like this P:192.168.0.254,1,10 where 192.168.0.254 is the HSNM IP, 1 means that the HSNM is reachable and 10 is the latency.

DataVariable.jpg

In addition to that you can check, on the GW's dashboard, the "latency to gotspot manager"; if you see latency to 1500 means that GW was not able to reach HSNM

GWDashboard.jpg

Best regards