CTWUG Committee have noted several problems creeping into the our wug and many of these can be avoided with a little housekeeping. We are talking about things like:
[ul]
[li]OSPF routers not having hostnames[/li]
[li]OSPF routers not having relevant logins[/li]
[li]OSPF routers not having the right WMS scripts etc.[/li]
[/ul]
These issues make it a hassle to manage the CTWUG and means we can do less of the fun stuff.
We are doing a little housekeeping with Project Spring Clean. Rather than having silly manual processes to follow up on this I’ve created a script to to check many of these issues and email the WIND node admins to notify them of issues. These should be sent later today. And will continue to be sent. This process is not perfect as many ips are fairly difficult to link to a wind node, but hopefully this process will actually result in this being cleaned up as well. Another benefit.
I actually envisage this to be a continual maintenance process but to get it rolling will be a little bit of a push. This will automate the nagging process and make it much more convenient for everyone.
This script check OSPF routers things like:
[ul]
[li]Does it have a IP address/hostname on wind? [Fix this by adding an ip address on the wind node.][/li]
[li]Does it have more than one? 
[Fix this by deleting duplicate ip address entries on the wind node. If you want to keep the duplicate name add it as a CNAME.][/li]
[li]Is the ctwug/ctwug read-only login enabled?[/li]
[li]Is the router being managed properly by wms.[/li]
[li]Are the scripts loaded?[/li]
[li]What RouterOS version is running? [Try and keep it to 6.0 or later.][/li]
[li]What version of the WMS scripts are running?[/li]
[/ul]
You may notice logins on the CTWUG read-only user. This script is not changing anything, though, with the node’s permission we may enable that (with a proper login though).
Most of these issues can be fixed by installing wms scripts. Or alternatively removing OSPF on routers that don’t really need it. If you do remove the rb from ospf it will be deleted by my script after two week.
Some useful resources on this and WIND issues:
[ul]
[li]http://wiki.ctwug.za.net/WMS[/li]
[li]http://wiki.ctwug.za.net/Node_Update[/li]
[/ul]
The deadline for most of these fixes is 1 Nov 2014. We hope to get everything in ship shape by then. If new issues emerge later you would usually get about 30 days to sort those out before we will review these and see what further action is needed.
Plan is once the routers are all in ship shape to load them into a network monitoring tool and properly monitor traffic etc. on these. Once we are there we can start monitoring links alerting on crap links etc. as well.
I may also expand the tool to ensure more of our wind data is up to date. Check active IPs for reverse dns entries. Check subnet ranges on node for consistency etc. Heck if this is managed well we could have a very clear idea of all the ip ranges on the wug without looking at our wiki pages.
I hope everyone will see this as a postive development to make sure our 630 active backbone OSPF routers are all in tip top shape. If those are running smoothly sure the CTWUG will be running smoothly.
An example of a positive impact this has had already is that I have noticed an issue in the WMS scripts and fixed it. You would have seen v24 rolling out last night.
Also see the homeless routers below. Closed the other thread.
