Solved

HP Procurve Connectivity issues

Posted on 2013-06-04
13
1,530 Views
Last Modified: 2013-06-25
Hi

Need some help with 3 HP Procurves 1810 - 24G switches, which we have been having some issues with lately.
All 3 using firmware P.2.10
No VLAN configured.

These 3 switches sits on a floor in our building and let users connect their computers to our LAN. Switch nr.1 and nr.2 is connected to switch nr.3 which is connected to a switch in the floor below, a HP V1810-48G using firmware P.1.15.

Every morning lately, about 1-6 users lose their connection. It varies how many of these users that loses their connection.
The rest of the users can connect fine, and don't notice anything.
The management interface for the 3 switches goes down, and cannot be pinged.
No issues on any other equipment.

The temporary solution has been to reboot them, only then can we reach the management interface again and the users who lost their connection are able to connect again. After the reboot, there are no issues until next morning.

Regards.
0
Comment
Question by:Lenblock
  • 7
  • 5
13 Comments
 
LVL 15

Expert Comment

by:Perarduaadastra
ID: 39218318
Sounds like a developing hardware fault.

I assume that the switches are stacked, so try designating a different member as the master. If the failure occurs again but you can still access the management interface, then it's likely that the demoted switch is the culprit.
0
 

Author Comment

by:Lenblock
ID: 39218346
The switches are not stacked, I don't believe that's an option on the 1810 - 24G.

We replaced switch nr. 3 thinking that it might be that one causing the issues with the others, but that did not resolve the issue.
0
 
LVL 18

Expert Comment

by:fgasimzade
ID: 39219777
May be a loop somewhere?
0
 

Author Comment

by:Lenblock
ID: 39221309
Loop protection is set on every port to: "Log and Shutdown Port", except from the ports which are connected to the other switches where it is set to: "log".

If it was a loop, had it a couple times earlier on these switches, the port which is creating the loop has been blocked and the management interface has still been accessible.
Also after a reboot with the same computers/equipment connected everything works fine until next morning.

Loop protection settings on switches:
Transmission time: 5
Shutdown time: 180
Ports where computers connected: "Log and shutdown port"
Ports where connected to other switches: "log"
0
 
LVL 15

Expert Comment

by:Perarduaadastra
ID: 39221322
Are the ports affected different every time, and on different switches?

As you now have a fourth switch, try substituting it for each the remaining two in turn; if one of these latter switches is generating the fault, replacing it with the new one should make the problem go away.
0
 

Author Comment

by:Lenblock
ID: 39221340
Will try to replace the other two.

Is it also possible it could be some sort of glitch in the config, and that a reset to factory and manually configure the switch(not from config backup) might do the trick ?
0
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 
LVL 15

Expert Comment

by:Perarduaadastra
ID: 39221348
It's worth a try, especially if the configs aren't complex and thus time-consuming to rebuild.

It may help to re-apply the current firmware as well, in case something has gone awry there; this has worked at least once for me in the past when an oddball issue couldn't be pinned down.
0
 

Author Comment

by:Lenblock
ID: 39243825
Did a reset to factory, applied the firmware again, manually set the config.

One of the three switches seems to be fine. The other two is still quite funky, but it's only the management interface that has issues now. Connecting to the switches seems to be fine.
0
 
LVL 15

Expert Comment

by:Perarduaadastra
ID: 39243980
"The other two is still quite funky" - erm, I'm not sure I catch your meaning here.

It seems that the connectivity issue has gone, but if the management interface is not working properly then that's a different issue, and should be resolved - limited or no access to switch management is most apparent when you really, really need to change something but can't.

Does each switch have to be accessed separately, or can they all be managed from a single interface? Is it web-based management, or are you working from the CLI via the console port?
0
 

Accepted Solution

by:
Lenblock earned 0 total points
ID: 39262124
They have to be managed separately, and only through the web-based interface.

It seems the issue might have been with the Firmware, 2.10. Set the previous version of the firmware 2.2 as the Active Image. Not experienced any troubles, so far.

I upgraded a fourth switch to firmware 2.10 which sits at a different location and experienced the same issue.

Will wait until tomorrow if the issue returns, or if it is resolved.
0
 
LVL 15

Expert Comment

by:Perarduaadastra
ID: 39264285
Unless I'm misunderstanding HP's firmware numbering, version 2.2 would seem more recent than version 2.1...

In any case, mixing firmware revisions between the same pieces of equipment is often a fruitful source of hard-to-identify problems, and is best avoided.

If a newer firmware causes problems then roll back to a previous version; reliability is more important than any extra bells and whistles that come with a later release.

It does seem a little odd to me that you have to manage each switch separately, as having three of them to deal with is a lot more hassle than managing them as a single stack. I suspect that this is a situation that you've inherited rather than made for yourself.
0
 

Author Comment

by:Lenblock
ID: 39265091
2.10 is the latest firmware. Weird numbering, I know. Firmware site: HP Procurve 1810-24G Firmware

Been careful to only have the same firmware on the same switches.

1810-24G cannot be stacked, it's a limitation. You have to buy the next one in the series to do that I believe.

Anyways, it seems to have been solved with the downgrade in Firmware P.2.2.

Regards.
0
 

Author Closing Comment

by:Lenblock
ID: 39274220
Downgrading the firmware to P.2.2 was the solution. Didn't really find out why it failed on Firmware P.2.10.
0

Featured Post

Network it in WD Red

There's an industry-leading WD Red drive for every compatible NAS system to help fulfill your data storage needs. With drives up to 8TB, WD Red offers a wide array of solutions for customers looking to build the biggest, best-performing NAS storage solution.  

Join & Write a Comment

If you’re like me and you like peace and quiet, saving money, and pretty lights, then this article is for you. For financial reasons, I buy all the Cisco equipment for my home lab second-hand. The first thing to wear out is usually one of the coo…
Before I go to far, let's explain HA (High Availability) and why you should consider it.  High availability is the mechanism used to provide redundancy to any service at the same site and appears as a single service to the users of that service.  As…
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now