What a miserable week it’s been for the weather! Here are the latest developments on NetHorus this week:
- Error messages – in particular, the flash messages, are now much prettier and will grey the background out to make the user aware something’s gone wrong.
- Configuration files – NetHorus will now check that a configuration file has been loaded, and raise an error if it hasn’t.
- Testing – we have some tests for the EventLog model, updated tests for the Ipv4Network models.
- Interface dependencies using the IF-MIB::ifStackTable are now working, although the table isn’t straightforward to parse. Credit to Brian Candler for explaining the acts_as_tree plugin to me.
- Model changes – the Ipv4Network model has been tidied up – testing proved that there were some cases where invalid data would be passed and cause errors.
- Credits – Martin Gleadow is now credited properly for keeping tabs on dependencies for the latest releases – something I should write up in the Wiki soon.
- Bugfixes – we destroy_all event logs for a device, rather than delete_all-ing them. This removes the data from the table, rather than breaking the device-to-eventlog relationship and leaving the data sitting stale.
- Interface layout – improvements to make things look prettier and simpler.
- Device inventorying now uses IF-MIB::ifHighSpeed if present to record the speed of an interface, since it appears generally more accurate than IF-MIB::ifSpeed.
So, that’s the past week. How did this week’s planned features go? Not too well…
- SNMPv3 support is still incomplete, I will be de-prioritizing this as it isn’t strictly required for any new functionality, but will be a very-nice-to-have.
- VRF support is lacking – the VRF Lite functionality on my Cisco 877W is slightly limited. I’m aware that full-fat VRF on bigger Cisco boxes works well, and I’m aiming to get started with VRF support this week.
- ifStackTable support is complete in the back-end database, however I want to come up with a way of displaying interface relationships visually.
And finally, here’s what I have planned for the coming weeks:
- ARP table polling – read in the ARP table from a device periodically and use it to track the Layer 2 addresses of devices on the network, and will also be useful for device discovery (incidentally, something I despite but I’m aware it’s a good way to get up and running).
- Layer 2 Forwarding table polling – used in combination with ARP table polling, will allow us to track devices throughout the network.
- Cisco CDP support – for displaying connected neighbour switches.
- ATM VC/VP information – for displaying details of virtual circuits and virtual paths on an ATM switch.
- Frame Relay PVC information – to display PVCs on an interface, their details, etc.
- Neighbour relationships – automatically detecting which devices share common subnets.
- Configuration generation – for Nagios primarily, so we can generate configurations based on the topology information stored in NetHorus. No need to set everything up once in NetHorus and again in Nagios!
Phew. That’s a lot of stuff, but it gives you an idea of what I have planned for the future.
As always, your feedback is important – please email me: firstname.lastname@example.org.