Page History

...

1. Open one or more of the following RabbitMQ management consoles.  (Credentials are in the "GÉANT Dashboard v3" LastPass folder)
   • http://net-alarms01.geant.org:15672/
   • http://net-alarms02.geant.org:15672/
   • http://prodnet-dashboard-storage01alarms03.geant.org:15672/
2. Scroll down to the "Nodes" section
3. There should be 3 rows in the table and all status icons should be green (currently - there is a red bar showing a deprecated node - this will be removed when possible).  The expected node hostnames are:
   • prod-noc-alarms01.geant.org
   • prod-noc-alarms02.geant.org
   • prod-dashboardnoc-storage01alarms03.geant.org

Solution

1. If one of the 3 nodes is failing or missing from the list, log into the failing server via ssh and restart the RabbitMQ service:

   • sudo systemctl restart rabbitmq-server

2. After a minute or two the management consoles should show the cluster is restored.

...

1. On each of the following servers:
   • net-alarms01.geant.org
   • net-alarms02.geant.org
   • net-alarms03.geant.org
2. Log in via ssh and execute the following command:

   • sudo systemctl restart trap_collector

...

1. Open https://net-alarms-monitoring.geant.org/d/hESYQotZz/correlation-services?orgId=1
2. Scroll down to the "Collectors" panel
3. Check that the graph shows one of the lead collector processes processing a non-zero rate of traps.note that it is normal for only one of the collectors to be processing traps, the other line should remain at zero  The leader can be identified by the FORWARDER with Raft state 2 in the Raft States panel.

Solution

1. On each of the following servers:
   • net-alarms01.geant.org
   • net-alarms02.geant.org
   • net-alarms03.geant.org
2. Log in via ssh and execute the following command:

   • sudo systemctl restart trap_correlator

...