Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1775
  • Last Modified:

HP Procurve Connectivity issues

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
Lenblock
Asked:
Lenblock
  • 7
  • 5
1 Solution
 
PerarduaadastraCommented:
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
 
LenblockAuthor Commented:
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
 
fgasimzadeCommented:
May be a loop somewhere?
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
LenblockAuthor Commented:
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
 
PerarduaadastraCommented:
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
 
LenblockAuthor Commented:
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
 
PerarduaadastraCommented:
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
 
LenblockAuthor Commented:
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
 
PerarduaadastraCommented:
"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
 
LenblockAuthor Commented:
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
 
PerarduaadastraCommented:
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
 
LenblockAuthor Commented:
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
 
LenblockAuthor Commented:
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

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now