Recent changes to bugs

#26 SNMP uptime collaps at 496 days

R. Begemann — Mon, 10 Aug 2020 09:42:10 -0000

Hi Pete,

thanks for your explanation. I am confused about the uptime of the switch. The webinterface shows more than 4 years and the max I can find in switchmap is 496days. Hope the 2 screenshots as attachment shows the difference.

Best regards
Ralf

SNMP uptime collaps at 496 days

Anonymous — Mon, 03 Aug 2020 09:32:15 -0000

Hi volks,
I wrote a small shell script, that collects the uptime value from the network switches in one html page. Going down the row, I noticed that there are no values higher than 496 days. If you look on the switch by cli you see the correct value. I'd like to request a change to display the correct value for the snmp uptime.
Best regards
Ralf

#24 Error in Switch.pm: No snmpv3 for SNMP::Info

Pete Siemsen — Tue, 22 Nov 2016 08:32:08 -0000

as the subject explains: #24 Error in Switch.pm: No snmpv3 for SNMP::Info
;)

#25 port information intermittently displayed incorrectly.

Pete Siemsen — Mon, 12 Sep 2016 02:11:22 -0000

Ok, from looking at the logic in the SetState function, I'm guessing that the port "type" is undefined. If you want to do some hacking, you can modify that function slightly and see what happens. In PopulatePorts.pm, in the SetState function, comment-out the line that says

if (defined $Port->{Type}) {

and comment-out the line that has the matching right-bracket, 8 lines below.

I wonder what the effect will be :-)

#25 port information intermittently displayed incorrectly.

Pete Siemsen — Mon, 12 Sep 2016 00:34:56 -0000

Hi Pete,

Yep have tried debug, when it fails it says something like "populatePorts::SetState: returning with state set to unknown". (see log below from a successful and failed run of switchmap)

I also run a packet sniff and it looks like the switches are returning the same SNMP info each time. My thought was that somehow switchmap was not parsing the returned data correctly somehow, but I'm not brainy enough to debug the perl in more depth.

We have a 6807 with Sup6T which also occasionally fails to get any info from. This has the latest firmware and everything so can't update that.

Thanks for you help. We really like switchmap.

Cheers, Simon

Successful
2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 2016/09/05 10:01:16 SwitchUtils::GetSnmpTable: returning hash with 35 values
PopulatePorts::SetStatesAndDaysInactive: called
PopulatePorts::SetState: called for port StackSub-St1-2
PopulatePorts::SetState: returning with State set to "Inactive"
PopulatePorts::SetDaysInactive: called
PopulatePorts::SetDaysInactive: returning
PopulatePorts::SetState: called for port Gi1/0/5
PopulatePorts::SetState: returning with State set to "Active"
PopulatePorts::SetDaysInactive: called
PopulatePorts::SetDaysInactive: returning
PopulatePorts::SetState: called for port Gi1/0/6
PopulatePorts::SetState: returning with State set to "Active"
PopulatePorts::SetDaysInactive: called
PopulatePorts::SetDaysInactive: returning
PopulatePorts::SetState: called for port Gi1/1/4
PopulatePorts::SetState: returning with State set to "Disabled"
PopulatePorts::SetDaysInactive: called
PopulatePorts::SetDaysInactive: returning
PopulatePorts::SetState: called for port Gi1/0/3
PopulatePorts::SetState: returning with State set to "Active"
PopulatePorts::SetDaysInactive: called
PopulatePorts::SetDaysInactive: returning
PopulatePorts::SetState: called for port Gi1/0/9
PopulatePorts::SetState: returning with State set to "Disabled"
PopulatePorts::SetDaysInactive: called
PopulatePorts::SetDaysInactive: returning
PopulatePorts::SetState: called for port Gi1/0/2
PopulatePorts::SetState: returning with State set to "Active"

Failed:
2016/08/30 12:28:19 SwitchUtils::GetSnmpTable: returning hash with 35 values
2016/08/30 12:28:19 PopulatePorts::SetStatesAndDaysInactive: called
2016/08/30 12:28:19 PopulatePorts::SetState: called for port Gi1/0/24
2016/08/30 12:28:19 PopulatePorts::SetState: returning with State set to "Disabled"
2016/08/30 12:28:19 PopulatePorts::SetDaysInactive: called
2016/08/30 12:28:19 PopulatePorts::SetDaysInactive: returning
2016/08/30 12:28:19 PopulatePorts::SetState: called for port Gi1/1/4
2016/08/30 12:28:19 PopulatePorts::SetState: returning with State set to "Disabled"
2016/08/30 12:28:19 PopulatePorts::SetDaysInactive: called
2016/08/30 12:28:19 PopulatePorts::SetDaysInactive: returning
2016/08/30 12:28:19 PopulatePorts::SetState: called for port Gi1/0/14
2016/08/30 12:28:19 PopulatePorts::SetState: returning with State set to "Disabled"
2016/08/30 12:28:19 PopulatePorts::SetDaysInactive: called
2016/08/30 12:28:19 PopulatePorts::SetDaysInactive: returning
2016/08/30 12:28:19 PopulatePorts::SetState: called for port Gi1/0/2
2016/08/30 12:28:19 PopulatePorts::SetState: returning with State set to "Unknown"

From: Pete Siemsen [mailto:siemsen@users.sf.net]
Sent: Monday, 12 September 2016 9:49 a.m.
To: [switchmap:bugs] 25@bugs.switchmap.p.re.sf.net
Subject: [switchmap:bugs] #25 port information intermittently displayed incorrectly.

Hmm. We have about 110 Cisco switches of various kinds, 2 of which are 3650s running version 03.07.03.E. The SwitchMap-produced web pages for those two switches look good - there are no ports that have state "Unknown".

It's weird that it's intermittent. I think that when it fails, SwitchMap isn't getting some of the MIB data from the switches. I can't explain why. It might help to run with debugging turned on, and hope to catch it when it fails. Try running with the "-d 4 -f" command-line options. It'll create a file named SwitchMap.log. Note that you can also put a single switch name on the end of the command line to make SwitchMap run on only one switch. The only downside is that SwitchMap will erase the webpages for all the other switches, so if others rely on the SwitchMap pages (as they do at my site) you'll want to announce that you're debugging.

Also, upgrading the code in the switches may help.

[bugs:#25]https://sourceforge.net/p/switchmap/bugs/25/ port information intermittently displayed incorrectly.

Status: open
Group: v1.0_(example)
Created: Tue Aug 30, 2016 11:00 PM UTC by sossie07
Last Updated: Tue Aug 30, 2016 11:00 PM UTC
Owner: Pete Siemsen

HiPete
We have about 100 cisco switchs of all models and ages and SwitchMap has been running well.

Recently we have installed some new Cisco 3650 switches running IOS-XE 3.03.05. and we are finding that port information on these switches in intermittantly displayed in SM incorrectly.

Intermitiantly the interface state (and other items are incorrecly reported) e.g on interfaces that are UP is displayed as "Unknown"
Information that is incorrectly collected for these ports and this includes:
state, days inactive, speed and all information about what the port is connected to.
Information that is correctly collected for these ports and this includes:
port,vlan, duplex, description

This issue is intermittant, ie. sometimes all the information for the port is corrected retreived, and othertimes not. If it gets it wrong for one port on the switch all ports are wrong.

We are running SM 13.1 but have also tried SM 14 with the same issue. We are running SM on windows 2012r2

SNMP seems fine, I'm wondering if its an issue parsing the SNMP response but I don't know why that woudl change.

Does anyone have any suggestions as to how I can troubleshoot this. I am familiar with running SM in debug mode and have done that but cant see anything obvious.

Thanks, Simon

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/switchmap/bugs/25/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

#25 port information intermittently displayed incorrectly.

Pete Siemsen — Sun, 11 Sep 2016 21:49:08 -0000

Also, upgrading the code in the switches may help.

port information intermittently displayed incorrectly.

sossie07 — Tue, 30 Aug 2016 23:00:21 -0000

HiPete
We have about 100 cisco switchs of all models and ages and SwitchMap has been running well.

Recently we have installed some new Cisco 3650 switches running IOS-XE 3.03.05. and we are finding that port information on these switches in intermittantly displayed in SM incorrectly.

This issue is intermittant, ie. sometimes all the information for the port is corrected retreived, and othertimes not. If it gets it wrong for one port on the switch all ports are wrong.

We are running SM 13.1 but have also tried SM 14 with the same issue. We are running SM on windows 2012r2

SNMP seems fine, I'm wondering if its an issue parsing the SNMP response but I don't know why that woudl change.

Does anyone have any suggestions as to how I can troubleshoot this. I am familiar with running SM in debug mode and have done that but cant see anything obvious.

Thanks, Simon

#24 Error in Switch.pm: No snmpv3 for SNMP::Info

Pete Siemsen — Wed, 24 Feb 2016 16:22:37 -0000

Line 261 in what file?

Error in Switch.pm: No snmpv3 for SNMP::Info

Anonymous — Wed, 24 Feb 2016 14:57:56 -0000

The code from line 261ff is cousing trouble with snmpv3. It is not implemented here and causing a die! (which breaks the whole program).
I am not sure, when this code is needed, but it was the case with our HP Switches.

#15 Trunk vlan overrides access vlan on older Cisco switches.

Pete Siemsen — Thu, 20 Nov 2014 01:00:25 -0000

Hi All, just adding an up vote to this request... we have a similar issue in our Cisco environment. Certain Network Engineers like flushing out configs with trunk settings ( just-in-case a port ever got flipped to trunk mode ), but indeed SwitchMap does display the Trunk Vlan rather then the Access Vlan. Likewise, the resultant html pages (e.g. Vlans) don't show all the ports actually on a vlan.

I haven't tried Petr's patch yet, was hoping that if it had been successful it would have been rolled into code trunk by now; i.e. 13.1

Pete any thoughts? And always, extreme thanks for this useful product!