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.

...

We are now going to manually run the commands highlighted in bold text:

*** Some of the scripts use a configuration files located in file called /usr/lib64/nagios/plugins/dbupdates/conf/config.inc

cd /usr/lib64/nagios/plugins/dbupdates/scripts/

...

ssh -n -i "/usr/lib64/nagios/plugins/dbupdates/.sshkeys/monitor_dsa" -oPasswordAuthentication=no -oStrictHostKeyChecking=no -oPreferredAuthentications=publickey -oConnectionAttempts=1 -oConnectTimeout=10 -oUserKnownHostsFile=/usr/lib64/nagios/plugins/dbupdates/.sshkeys/monitor_known_hosts Monit0r@mx1.ath2dub.grie.geant.net

The scripts may print out an error/warning such as:

...

Pseudo-terminal will not be allocated because stdin is not a terminal.
Warning: Permanently added the RSA host key for IP address '62.40.96.3' to the list of known hosts.
----------------------------------------------------------------

...

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>');