Issues with Catalyst 3750's since 2.2.5, and issue with Cisco 891 since always.
-
Hi,
I had a look at several C891s we have. One didn't provide the FDB via SNMP, the others did. I don't think that's a NetXMS issue, as all four devices poll ok via SNMP. One of them simply didn't have any data in the table. Could be a firmware issue. The one that didn't work was running a 15.0 firmware, the others were all on different versions of 15.2.
Regarding the switch topology, do you have CDP and/or LLDP enabled on the router and switches?Cheers
-
Hi,
do you mean that you select driver manually and it's not working anymore, or that automatic driver selection was changed from Catalyst to generic driver?
Best regards,
Victor -
@victor said in Issues with Catalyst 3750's since 2.2.5, and issue with Cisco 891 since always.:
Hi,
do you mean that you select driver manually and it's not working anymore, or that automatic driver selection was changed from Catalyst to generic driver?
Best regards,
VictorI had manually set snmp.driver to CATALYST-GENERIC in the past, but when I updated to 2.2.5 the driver shows as GENERIC when viewing object details. I looked in the logs and saw that CATALYST-GENERIC no longer loads on startup. I do see a "catalyst.ndd" file in /usr/lib/x86_64-linux-gnu/netxms/ndd and tried to set snmp.driver to it, but it doesn't get loaded either. These are the drivers loading for me at startup:
"TB" loaded successfully
"MIKROTIK" loaded successfully
"H3C" loaded successfully
"QTECH-OLT" loaded successfully
"AIRESPACE" loaded successfully
"PROCURVE" loaded successfully
"UBNT" loaded successfully
"CISCO-SB" loaded successfully
"JUNIPER" loaded successfully
"NETSCREEN" loaded successfully
"HPSW" loaded successfully
"AT" loaded successfully
"RITTAL" loaded successfully
"DLINK" loaded successfully
"NTWS" loaded successfully
"NETONIX" loaded successfully
"IGNITENET" loaded successfully
"SYMBOL-WS" loaded successfully
"PING3" loaded successfully
"NET-SNMP" loaded successfully
"DELL-PWC" loaded successfully
"EXTREME" loaded successfully
"CISCO-ESW" loaded successfullyThanks Victor, I really appreciate the help. From looking through the forum, I am impressed with your responsiveness and dedication to helping people get the most out of NetXMS.
Thanks again,
Mike -
@tursiops said in Issues with Catalyst 3750's since 2.2.5, and issue with Cisco 891 since always.:
Hi,
I had a look at several C891s we have. One didn't provide the FDB via SNMP, the others did. I don't think that's a NetXMS issue, as all four devices poll ok via SNMP. One of them simply didn't have any data in the table. Could be a firmware issue. The one that didn't work was running a 15.0 firmware, the others were all on different versions of 15.2.
Regarding the switch topology, do you have CDP and/or LLDP enabled on the router and switches?Cheers
Thanks for the reply and checking this out for me! I'm running 15.7(3)M on my 891, so perhaps there is an SNMP issue there somewhere. "sho mac-address-table" from ios shows a good table, but when looking at the "Interfaces" tab in NetXMS shows no peer nodes or peer MACS, aside from switch. It is showing the port alias, mac addresses of the ports, etc., just nothing in Peer Node, Peer MAC, and Peer IP.
I do have CDP and LLDP running on all my Cisco devices. I've triple checked both on everything out of my determination to fix this.
Two questions, if you don't mind. Are you running NetXMS 2.2.5, and what driver does your 891's use? Mine comes up as GENERIC, although I tried CISCO-SB and got the same results.
Thanks again,
Mike -
Hi,
driver list seems incomplete. Did you install server from sources or from deb package?
Best regards,
Victor -
-
The driver used for our Cisco routers is "GENERIC". Haven't seen any exception to that.
Cisco-SB is showing up on some Cisco small business switches (e.g. SG-300), while CATALYST-GENERIC and in one case CATALYST-2900XL are in use for Catalyst switches.We were running 2.2.4 up until yesterday, it's 2.2.5 now (so the data above is from 2.2.5).
Cheers
-
Victor, I reinstalled NetXMS Server and now all the drivers are back. I appreciate the help.
Tursiops, thanks for the information. I'll stick with Generic on the little router. I can still do what I need to do, just not as automated with regards to mapping.
I'm really impressed with NetXMS. I can't believe it's not more well known. It should be!
-
Maybe, there is generall problem with drivers. My windows installation after update 2.2.4-->2.2.5 cannot load some drivers
*I* Network device driver "AIRESPACE" loaded successfully
*I* Network device driver "AT" loaded successfully
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\baystack.ndd"
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\cat2900xl.ndd"
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\catalyst.ndd"
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\cisco-esw.ndd"
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\cisco-sb.ndd"
*I* Network device driver "DELL-PWC" loaded successfully
*I* Network device driver "DLINK" loaded successfully
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\ers8000.ndd"
*I* Network device driver "EXTREME" loaded successfully
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\h3c.ndd"
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\hpsw.ndd"
*I* Network device driver "IGNITENET" loaded successfully
*I* Network device driver "JUNIPER" loaded successfully
*I* Network device driver "NETSCREEN" loaded successfully
*I* Network device driver "MIKROTIK" loaded successfully
*I* Network device driver "NETONIX" loaded successfully
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\netscreen.ndd"
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\ntws.ndd"
*I* Network device driver "PING3" loaded successfully
*E* Unable to find entry point in network device driver "F:\NetXMS\lib\ndd\procurve.ndd"
*I* Network device driver "QTECH-OLT" loaded successfully
*I* Network device driver "SYMBOL-WS" loaded successfully
*I* Network device driver "TB" loaded successfully
*I* Network device driver "UBNT" loaded successfullyMartin
-
Hi,
seems to be Windows installer issue - old modules kept in place and some new modules missing. Will check that.
Best regards,
Victor -
The problematic modules have different timestamp (20.3.2018).
05/14/2018 07:11 PM 29,776 airespace.ndd
05/14/2018 07:11 PM 29,264 at.ndd
03/20/2018 04:49 PM 28,240 avaya-ers.dll
03/20/2018 04:49 PM 26,192 baystack.ndd
03/20/2018 04:49 PM 23,632 cat2900xl.ndd
03/20/2018 04:49 PM 24,144 catalyst.ndd
03/20/2018 04:49 PM 23,120 cisco-esw.ndd
03/20/2018 04:49 PM 23,632 cisco-sb.ndd
03/20/2018 04:49 PM 28,240 cisco.dll
05/14/2018 07:11 PM 24,144 dell-pwc.ndd
05/14/2018 07:11 PM 24,144 dlink.ndd
03/20/2018 04:49 PM 24,144 ers8000.ndd
05/14/2018 07:11 PM 24,144 extreme.ndd
03/20/2018 04:49 PM 24,144 h3c.ndd
03/20/2018 04:49 PM 23,120 hpsw.ndd
05/14/2018 07:11 PM 24,656 ignitenet.ndd
05/14/2018 07:11 PM 30,288 juniper.ndd
05/14/2018 07:11 PM 28,240 mikrotik.ndd
05/14/2018 07:11 PM 23,120 netonix.ndd
03/20/2018 04:49 PM 25,680 netscreen.ndd
03/20/2018 04:49 PM 30,288 ntws.ndd
05/14/2018 07:11 PM 26,192 ping3.ndd
03/20/2018 04:49 PM 24,144 procurve.ndd
05/14/2018 07:11 PM 26,192 qtech-olt.ndd
05/14/2018 07:11 PM 30,288 symbol-ws.ndd
05/14/2018 07:11 PM 28,752 tb.ndd
05/14/2018 07:11 PM 28,752 ubnt.ndd -
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login