HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Web and Unmanaged
cancel
Showing results for 
Search instead for 
Did you mean: 

Think I have a problem with 1910-48G switches

 
bestseany
Occasional Visitor

Think I have a problem with 1910-48G switches

Hello,

 

I'm wondering if anyone could shed any light on this problem I have...

 

We have two 1910-48G swtiches which we use for a Hyper-V cluster with an iSCSI SAN. The switches are linked together by 6 ports in a LAG, and port 48 on each switch is used as an uplink to our existing infrastructure.

 

The Hyper-V cluster servers use network teaming and iSCSI MPIO so that everything is split evenly across both switches for fault tolerance.

 

The problem we have is that the uplink in port 48 in the first switch seems to go down if you so much as blow on it, which takes down our entire cluster! Its like the brief downtime in the uplink is taking the switches down, even though they carry on running fine. The only event in the syslogs just shows the uplink port going down and up.

 

I thought that the uplink in the second switch would take over instead through STP, or the Hyper-V hosts should still at least see each other and the SAN even with no uplink working to the rest of the LAN.

 

This does appear to be an issue with the switches themselves. This was all configured before I started working here, but I've been through the configuration and haven't noticed any issues. Could this be an STP problem? Or a bug maybe?