When I add a Catalyst 6509 GSW I get the following errors in getDeviceData.log:

.... Mar 14 16:44:22 2005 xxx-gsw_06 OID_TESTER-6-DO_TEST Got results from xxx-gsw, length: 0 (reqGetnext: true, vl: @30) Mar 14 16:44:22 2005 xxx-gsw_06 OID_TESTER-6-DO_TEST Got timeout exception testing oidkey ucd_cpuIdle with netbox: 128.39.xxx.xxx (vl: @1002)

.... Mar 14 16:52:22 2005 xxx-gsw_06 OID_TESTER-6-DO_TEST Got results from xxx-gsw, length: 0 (reqGetnext: true, vl: @30) Mar 14 16:52:22 2005 xxx-gsw_06 OID_TESTER-6-DO_TEST Got timeout exception testing oidkey cMenuPortType with netbox: 128.39.xxx.xxx (vl: @1002)

.... Mar 14 16:55:23 2005 xxx-gsw_06 OID_TESTER-6-DO_TEST Got results from xxx-gsw, length: 0 (reqGetnext: true, vl: @30) Mar 14 16:55:23 2005 xxx-gsw_06 OID_TESTER-6-DO_TEST Got timeout exception testing oidkey hpHwVer with netbox: 128.39.xxx.xxx (vl: @1002)

etc.

Any ideas on why these messages occur? Is it because of a misconfiguration on the GSW?

Regards, Fredrik Holmberg

From kreide at online.no Mon Mar 14 17:10:14 2005

From: kreide at online.no (Kristian Eide) Date: Mon Mar 14 17:10:17 2005 Subject: [Nav-users] snmp timeout when adding a 6509 GSW Message-ID: 4236C142@epostleser.online.no

When I add a Catalyst 6509 GSW I get the following errors in getDeviceData.log: Mar 14 16:44:22 2005 xxx-gsw_06 OID_TESTER-6-DO_TEST Got results from xxx-gsw, length: 0 (reqGetnext: true, vl: @30) Mar 14 16:44:22 2005 xxx-gsw_06 OID_TESTER-6-DO_TEST Got timeout exception testing oidkey ucd_cpuIdle with netbox: 128.39.xxx.xxx (vl: @1002)

Any ideas on why these messages occur? Is it because of a misconfiguration on the GSW?

No. This is normal as the device does not reply to SNMP requests on a VLAN it does not recognize (1002 in this case). Since NAV does not know which VLANs are valid for a given device it will try several, some of which might not be valid, and this can result in the above message. It should be safe to ignore in this case, however.

-- Kristian