Did we loose support for older Cisco switches?, (2900 and 2424 generation)

[tristanbob]

I am testing out Nedi version 1.0.w-rc1. I did a successful device write, but I noticed that it could not write to my older switches, Catalyst 2900 and 2924.

The error is "No login for" and the name of the device.

I then looked at the Device List and found out that all of my 2900 and 2924 switches were labeled with type "Other". In previous versions of Nedi, these devices were correctly identified, and I think Device Write worked with them.

Any idea what happened? Perhaps Cisco stopped including these older switches in their SNMP MIB file, and this new version of Nedi uses that file?

I can perform troubleshooting and debugging steps as necessary.

Thanks,

Tristan

[rickli]

Do a -d discovery on those particular switches. check whether this .obj file exists in the sysobj folder afterwards. If not you'll need to create them. Take this one as a template:

1.3.6.1.4.1.9.1.220.def:Type Cat2924MXL

[tristanbob]

Thanks Remo for walking me through this.

I will explain what happened so that other people can solve this problem and contribute to the development of NeDi.

1. Every type of device that Nedi connects to needs a .def file in the sysobj directory. This file includes details about how and where to get information from the device. By default, Nedi already comes with .def files for many popular device types. However, it may not include the type of device you have on your network.

2. My device types (Cisco Catalyst 2924XLv and 2924CXLv) did not have a .def file, so they were detected as "Other", and Nedi only collected basic information from them.

3. First, I needed to find the OID of my devices. To do this, I searched the "CISCO-PRODUCTS-MIB.oid" file in the sysobj directory for the names of my devices. Here is what I found.

"catalyst2924XLv" "1.3.6.1.4.1.9.1.217"
"catalyst2924CXLv" "1.3.6.1.4.1.9.1.218"

4. After that I needed to find a similar device that already has a .def file. In this case, it was "1.3.6.1.4.1.9.1.220.def" which was for the 2924MXL.

5. I copied the file "1.3.6.1.4.1.9.1.220.def" twice and re-named the files to "1.3.6.1.4.1.9.1.217.def" and "1.3.6.1.4.1.9.1.218.def".

6. Since the devices are so similar, the only field I had to change was the "Type" of device. I used the names that I got from the Cisco file.

7. After these files have been created, run a discovery and then look at the devices in the web-interface. They should no longer be labeled as "other", and Nedi will gather much more information from them.

8. Lastly, and most important, is to post your new .def files to the Nedi forum so others can benefit from your work.

Thanks,

Tristan Rhodes