Page History

...

The physical file on the server is: /usr/lib64/nagios/plugins/dbupdates/conf/routers_community.conf (Should you wish to be naughty and update the file directly on the server!!!)

*** Because the Operations team has commissioned a new router, we want to Dashboard to be able to raise critical alarms should a fault arise. In order for this to happen, we need to run some of the PHP and BASH Shell scripts detailed in the CRONTAB.

Log into prod-newdboard01.geant.net using your dante.surname credentials.

...

Once you have fixed the monitor_known_hosts file, you we need to rerun the get-bgp-v4-peers-on-router.sh, get-bgp-v6-peers-on-router.sh and populate_router_ix_public_peer_table.php scripts.

The router's details also need to be added manually to the juniper_servers table in the alarms database.

1. Log into the alarms database using the newdashboardBizuser
2. execute the follow statement INSERT INTO juniper_servers VALUES ('<ip_address>', '<router project>');