NetXMS Support Forum

Hi,

I have the following procurve switches with "generic drivers". Its kind of weirg that almost all procurve switches have generic drivers. Netxms version I use is 1.2.6


System Description=ProCurve J4899B Switch 2650, revision H.10.83, ROM H.08.02 (/sw/code/build/fish(mkfs))
SNMP Object ID=.1.3.6.1.4.1.11.2.3.7.11.44
Driver=GENERIC

System Description=ProCurve J9147A 2910al-48G Switch, revision W.14.38, ROM W.14.04 (/sw/code/build/sbm(t4a))
SNMP Object ID=.1.3.6.1.4.1.11.2.3.7.11.87
Driver=GENERIC

System Description=ProCurve J4819A Switch 5308xl, revision E.11.21, ROM E.05.05 (/sw/code/build/alpmo(alp11))
SNMP Object ID=.1.3.6.1.4.1.11.2.3.7.11.17
Driver=GENERIC

System Description=ProCurve J4904A Switch 2848, revision I.10.77, ROM I.08.07 (/sw/code/build/mako(mkfs))
SNMP Object ID=.1.3.6.1.4.1.11.2.3.7.11.32
Driver=GENERIC

System Description=ProCurve J4899C Switch 2650, revision H.10.83, ROM H.08.05 (/sw/code/build/fish(mkfs))
SNMP Object ID=.1.3.6.1.4.1.11.2.3.7.11.83
Driver=GENERIC

System Description=ProCurve J9088A Switch 2610-48, revision R.11.07, ROM R.10.06 (/sw/code/build/nemo(ndx))
SNMP Object ID=.1.3.6.1.4.1.11.2.3.7.11.77
Driver=GENERIC

Hi!

Very strange. Procurve driver basically only checks for device OID to be started with .1.3.6.1.4.1.11.2.3.7.11. Can you check in server log that PROCURVE driver actually loaded at startup?

Best regards,
Victor

hi victor,

here's the log. it is also strange that when i move my other server (working procurve driver) to another server, i also encounter this problem.

[27-Mar-2013 09:42:34.843] Log file opened
[27-Mar-2013 09:42:35.077] Database driver "mysql.ddr" loaded and initialized successfully
[27-Mar-2013 09:42:38.921] GSM modem on COM1: initialized successfully. Hardware ID: "".
[27-Mar-2013 09:43:45.718] Listening for SNMP traps on UDP socket 0.0.0.0:162
[27-Mar-2013 09:43:45.733] NetXMS Server started
[27-Mar-2013 09:43:45.749] Listening for client connections on TCP socket 0.0.0.0:4701
[27-Mar-2013 09:43:45.749] Listening for mobile device connections on TCP socket 0.0.0.0:4747
[27-Mar-2013 09:43:45.749] Unable to create socket in function MobileDeviceListener
[27-Mar-2013 09:43:45.749] Unable to create socket in function ClientListener

----------------------------------------------------------
When polling one of my switch, it change the driver to GENERIC

03.2013 09:51:13] **** Poll request sent to server ****
[27.03.2013 09:51:13] Poll request accepted
[27.03.2013 09:51:13] Starting configuration poll for node XXXXX
[27.03.2013 09:51:13] Checking node's capabilities...
[27.03.2013 09:51:13]    Checking NetXMS agent...
[27.03.2013 09:51:14]    Checking SNMP...
[27.03.2013 09:51:14]    SNMP agent is active (version 2c)
[27.03.2013 09:51:14]    System description changed to ProCurve J9138A Switch 2520-24-PoE, revision S.14.30, ROM S.14.03 (/sw/code/build/elmo(S_t4b))
[27.03.2013 09:51:14]    New network device driver selected: GENERIC
[27.03.2013 09:51:14]    System name changed to XXXXX
[27.03.2013 09:51:15]    LLDP node ID changed to 4@80C16EBE0D40
[27.03.2013 09:51:23] Capability check finished
[27.03.2013 09:51:23] Checking interface configuration...
[27.03.2013 09:51:25] Checking node name
[27.03.2013 09:51:25] Node name is OK
[27.03.2013 09:51:25] Interface configuration check finished
[27.03.2013 09:51:25] Finished configuration poll for node XXXXX
[27.03.2013 09:51:25] Node configuration was changed after poll
[27.03.2013 09:51:25] **** Poll completed successfully ****

Hi!

That's strange - looks like no drivers loaded at all. Is there any files with extension .ndd? Also, try to run server with debug level 5 and send me messages shown at startup.

Best regards,
Victor

Hi Victor,

Maybe its a bug. I only encounter this when installing the netxms on the other drive. ex:

My new server (Windows 2003 Server), I install the netxms on D:\Programs\Netxms\ the procurve drivers was not working. I've re-install the netxms to the default netxms installation directory "C:\netxms\" folder and its works. I do the same on my other server which is procurve driver is not working and it works.

I was thinking that there might be a hard coded path somewhere in the registry or in the program itself. but i'm not sure.