Users complaining about network slowness and dropped connections

[HeywoodKenobi]

I have a handful of users who are complaining about their apps becoming unresponsive and slow. I looked at their PCs, a couple of them show Event ID's in the event log that say the NIC lost connection to the network. So I log into the switches, 2

HP V1910-48G

connected with a Gbic, and I see these errors in the syslog. Any idea why this is happening and how to fix it or is it normal?

 

Mar 14 08:49:06:039 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/7 link status is DOWN.
Mar 14 08:41:55:306 2014 MSTP Information MSTP_FORWARDING Instance 0's port GigabitEthernet1/0/7 has been set to forwarding state.
Mar 14 08:41:55:295 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/7 link status is UP.
Mar 14 08:41:44:955 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/7 link status is DOWN.
Mar 14 08:37:41:826 2014 MSTP Information MSTP_FORWARDING Instance 0's port GigabitEthernet1/0/11 has been set to forwarding state.
Mar 14 08:37:41:814 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/11 link status is UP.
Mar 14 08:37:39:420 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/11 link status is DOWN.
Mar 14 08:37:21:678 2014 MSTP Information MSTP_FORWARDING Instance 0's port GigabitEthernet1/0/11 has been set to forwarding state.
Mar 14 08:37:21:667 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/11 link status is UP.
Mar 14 08:26:53:043 2014 MSTP Information MSTP_FORWARDING Instance 0's port GigabitEthernet1/0/24 has been set to forwarding state.
Mar 14 08:26:53:030 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/24 link status is UP.
Mar 14 08:26:49:114 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/24 link status is DOWN.
Mar 13 18:52:27:206 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/9 link status is DOWN.
Mar 13 18:23:41:949 2014 MSTP Information MSTP_FORWARDING Instance 0's port GigabitEthernet1/0/4 has been set to forwarding state.
Mar 13 18:23:41:937 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/4 link status is UP.
Mar 13 18:23:40:213 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/4 link status is DOWN.
Mar 13 18:23:20:696 2014 MSTP Information MSTP_FORWARDING Instance 0's port GigabitEthernet1/0/4 has been set to forwarding state.
Mar 13 18:23:20:685 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/4 link status is UP.
Mar 13 18:23:18:314 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/4 link status is DOWN.
Mar 13 18:14:17:082 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/11 link status is DOWN.
Mar 13 17:00:44:224 2014 MSTP Information MSTP_FORWARDING Instance 0's port GigabitEthernet1/0/24 has been set to forwarding state.
Mar 13 17:00:44:212 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/24 link status is UP.
Mar 13 17:00:42:526 2014 IFNET Error LINK_UPDOWN GigabitEthernet1/0/24 link status is DOWN.

P.S. This thread has been moevd from ProCurve / ProVision-Based to Web and Unmanaged. - Hp forum moderator

[Richard Brodie_1]

Links shouldn't be bouncing up and down like that (assuming you aren't rebooting the PCs). I've seen a NIC driver problem cause that sort of symptom. I would collect some details on the clients hardware/software and look for an update from the manufacturer, if they have a similar config.

If you have some cheap desktop hubs knocking around, you could hang some of the affected users off them, see if that makes the problem go away. And it's probably worth grabbing the  firmware for the 1910's, just in case.

[HeywoodKenobi]

I found more about this I stuck wireshark on the network and found tons of checksum errors related to STP.

No.     Time           Source                Destination           Protocol Length Frame      Info
    576 1077.946920000 HewlettP_34:04:11     Spanning-tree-(for-bridges)_00 STP      64     Yes        RST. Root = 32768/0/cc:3e:5f:34:04:09  Cost = 0  Port = 0x8007 [ETHERNET FRAME CHECK SEQUENCE INCORRECT]

Frame 576: 64 bytes on wire (512 bits), 64 bytes captured (512 bits) on interface 0
IEEE 802.3 Ethernet
    Destination: Spanning-tree-(for-bridges)_00 (01:80:c2:00:00:00)
        Address: Spanning-tree-(for-bridges)_00 (01:80:c2:00:00:00)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast)
    Source: HewlettP_34:04:11 (cc:3e:5f:34:04:11)
        Address: HewlettP_34:04:11 (cc:3e:5f:34:04:11)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Length: 39
    Padding: 00000000000000
    Frame check sequence: 0x00000000 [incorrect, should be 0x78577e0b]
Logical-Link Control
Spanning Tree Protocol

and

No.     Time           Source                Destination           Protocol Length Frame      Info
    577 1079.946820000 HewlettP_34:04:11     Spanning-tree-(for-bridges)_00 STP      64     Yes        RST. Root = 32768/0/cc:3e:5f:34:04:09  Cost = 0  Port = 0x8007 [ETHERNET FRAME CHECK SEQUENCE INCORRECT]

Frame 577: 64 bytes on wire (512 bits), 64 bytes captured (512 bits) on interface 0
IEEE 802.3 Ethernet
    Destination: Spanning-tree-(for-bridges)_00 (01:80:c2:00:00:00)
        Address: Spanning-tree-(for-bridges)_00 (01:80:c2:00:00:00)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast)
    Source: HewlettP_34:04:11 (cc:3e:5f:34:04:11)
        Address: HewlettP_34:04:11 (cc:3e:5f:34:04:11)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Length: 39
    Padding: 00000000000000
    Frame check sequence: 0x00000000 [incorrect, should be 0x78577e0b]
Logical-Link Control
Spanning Tree Protocol

340240  908.527334000   HewlettP_34:04:1f          LLDP_Multicast LLDP      332         Chassis Id = cc:3e:5f:34:04:09 Port Id = GigabitEthernet1/0/21 TTL = 120

The MAC address cc:3e:5f:34:04:09 is the first switch in the group(of two switches) and so far it is the only one that shows these errors.  It is connected to another v1910 via a mini gbic.

[byjup]

Did you find a solution for this.

We also have a similar situation.

Thank you.

[Howiedoit]

I also have these same errors. I have not put wireshark on the net as yet. My switches are H5500 series (core) and v1910 (edge).

Both series of switches have these errors. And it does look like some type of STP issue.

I have RSTP enable on all switches as per HP Network guy I was talking to when first configured.

I also see in the logs: MSTP notice of topology changes for various ports and also "set to forwarding state"

Would be nice to see some resolution to this or what we can do to mitigate these??

Please HP??

[Ph-MASSA]

I've got same error :

Jan 12 11:20:43:659 2015 MSTP Information MSTP_FORWARDING -Slot=2; Instance 0's port Ethernet2/0/33 has been set to forwarding state.

Jan 12 11:20:43:570 2015 IFNET Error LINK_UPDOWN Ethernet2/0/33 link status is UP.

Jan 12 11:20:41:743 2015 IFNET Error LINK_UPDOWN Ethernet2/0/33 link status is DOWN.

on HP 3600 V2 version 5.20.99, Release 2108P07

the solution ?

[HPhouse]

I am receiving this error as well after finishing our upgrade to a fiber LAN.  The users that are affected are reporting slowness.  HP?

Jan  5 16:39:33:574 2015 MSTP Information MSTP_FORWARDING Instance 0's port GigabitEthernet1/0/7 has been set to forwarding state.

Jan  5 16:39:33:557 2015 IFNET Error LINK_UPDOWN GigabitEthernet1/0/7 link status is UP.

Jan  5 16:39:30:675 2015 IFNET Error LINK_UPDOWN GigabitEthernet1/0/7 link status is DOWN.

[dionizio]

Estou com o mesmo problema, alguém encontrou uma solução?

Eu verifiquei os logs do dispositivo conectado na porta, mas nele não existe nenhum alerta de perda de conexão.