1.0, Expanding the horizon...

1.0.w has gone into the last iteration. I'm waiting for feedback to squish the last bugs and plan to move on with .x afterwards...

The new version will focus a great deal on improving CLI interaction. So far I've been messing about with my own approach, but now there are 2 very interesting projects out there, which could be integrated into NeDi:

• http://dis.sf.net/
• http://search.cpan.org/~oliver/Net-Appliance-Session-0.09/

Any help from perl programmers for developing and testing is welcome. I'll be around on IRC (irc://irc.freenode.net/nedi) to discuss future development of this and other topics...

Lets see what we can achieve next year! Y'all have great holdiays!

Net::Appliance::Session looks good. Support for SSH and device phrasebooks makes it flexible (as long as it works).

I have used Cisco Telnet 1.10 and had a few problems. I found if the commands got too complex then it lost track of the output and just hung.

A brief status report on the upcoming 1.0 release candidate:

New discovery features:

• Route based discovery
• Inline OUI discovery (it's not at the end anymore).

New GUI features:

• Weather/Error Map, geographical layout and SVG export!
• New editor to manage locations (assists in placing them on your background map).
• CPU, Mem, temperature, traffic and error Alerts in Monitoring Health (see revised screenshot in the gallery). Events are logged as well for long term investigation.
• Compare configs to any of the same device type (or just another device). This lets you quickly find discrepancies.

And Many bug fixes...

Todolist:

• Cleanup/finish leafdev,webdev handling
• Port security support for collection via CLI on IOS and SNMP.

Well I know someone will ask, so I suppose it might as well be me. Will this be soon or will it be awhile? I was never patient enough to wait an hour after eating to go swimming either. It always seemed like such a long time.

The route based discovery sounds good. Do you look at neighbours/next hops for different routing protocols?

The release candidate will be soon (couple weeks). And if things go better than in .w, the final relase shouldn't be too far (few months) out either.

It should include all next hops as far as I could test it...

Download RC1 for testing.

Among a bucket of bug-fixes I improved the GUI, some .defs (HP, Cisco 3560), discovery and it's message handling and last but not least the DB structure. A minor bugfix should make moni.pl more stable as well...

I couldn't work on port security support yet, but the webdev feature is working for my Cisco SCCP phones (SN# and Extension in Contact) (You'll need to install the perl-lwp module for it to work!)

If you want to mess with geographic maps, create map-bg.png in html/log. Then go to other-loced and place those locations of yours on it....

I strongly recommend to use the new nedi.conf and initialize the DB!

RC2 coming along...

Thanks to HP Switzerland I've got LLDP discovery working! It requires proper implementation on the devices (like HP does)...

I'll need to implement the new location scheme in the map and RC2 will be ready for testing (Hopefully before I leave for San Francisco in August).

Reworked Network Health

Added Vlan-List. This completes device based audits as you can list modules, interfaces and vlans now

You must be a BF2 player. I am MajorCatastrophe http://bf2s.com/player/43387766/.

I was wondering how long it would take until somebody mentions it

I completely overhauled the CLI library. It should be much more straight forward now. If anyone knows Net::Telnet(::Cisco) though, please get in touch as I've got some big questionmarks floating around here...

I could test it on IOS, CatOS (with and without radius), Cat1900, Ironware and Procurve. The latter needs "console terminal NONE" configured in order to work, unless you know of another way to disable those escape sequences. Also if anyone knows of how to get rid of that "Hit any key to continue" on newer HP switches please let me know

Also I've got some good and bad news:

Bad News
The location string requires a fixed pattern now. This is the only way I can provide support as it's impossible to reproduce other constellations and code accordingly. The separator can still be chosen:

Good News
I also overhauled the Device-Writer. It now allows you to substitute the 2nd search field and use the result as argument for the command field (1 command only). I added the region on 230 devices this way...

I have done some work with Net::Telnet::Cisco. I built a new machine on Fedora 7 and also have Net::Appliance::Session installed.

I have trouble with Catalyst 1900/2900 running TACACS. I can send the code I used to get them working. I haven't put it into NeDi though.

I can try some devices if you don't have access to them.

Looks like I'm not able to complete everything before my leave. Those who don't want to wait another 3 weeks can download RC2. Topology Map doesn't work properly in geographic mode, but the rest should be ok (needs testing though). As this is a major step (probably the last one for now), you should use the new nedi.conf as template and initialize the DB first.

Most new fields reveal hints when hovering over them with the mousepointer. It's brief and cryptic, but still better than nothing