Сеть из 60 компов, нескольких свитчей (HP ProCurve Switch 2626/6108/2824/2650/2510-24)
При заходи на их IP открывается log alert.
Месяц назад начились ошибки на всех свитчах на разных портах. Они возникают когда пользователь включает компьютер или при подключении сетевого кабеля.
Петель в сети нет.
Пробовали подключать напрямую комп к свитчу, разные компы к одному порту, ошибки остаются.
High Collision or Drop Rate on port 1
Код: Description:
A large number of collisions or packet drops have occurred on port 1.
Possible causes:
The possible causes include an extremely high level of traffic on port 1, half/full duplex mismatch, a misconfigured or malfunctioning NIC or transceiver on a device connected to this port, or a topology loop in the network.
Actions:
Use a network monitoring device or application to determine the traffic levels on the affected segment. If needed, consider subdividing that segment with switches or bridges, or moving high-traffic devices to their own switch ports.
Check the directly-connected device for mismatches in half/full duplex operation (half duplex on the switch and full duplex on the connected device).
Check for a misconfigured NIC or transceiver (such as a transceiver configured for "loopback test" or "SQE test").
Also, verify that there are no topology loops in your network. If not enabled, you may also enable Spanning Tree.
При заходи на их IP открывается log alert.
Месяц назад начились ошибки на всех свитчах на разных портах. Они возникают когда пользователь включает компьютер или при подключении сетевого кабеля.
Петель в сети нет.
Пробовали подключать напрямую комп к свитчу, разные компы к одному порту, ошибки остаются.
High Collision or Drop Rate on port 1
Код: Description:
A large number of collisions or packet drops have occurred on port 1.
Possible causes:
The possible causes include an extremely high level of traffic on port 1, half/full duplex mismatch, a misconfigured or malfunctioning NIC or transceiver on a device connected to this port, or a topology loop in the network.
Actions:
Use a network monitoring device or application to determine the traffic levels on the affected segment. If needed, consider subdividing that segment with switches or bridges, or moving high-traffic devices to their own switch ports.
Check the directly-connected device for mismatches in half/full duplex operation (half duplex on the switch and full duplex on the connected device).
Check for a misconfigured NIC or transceiver (such as a transceiver configured for "loopback test" or "SQE test").
Also, verify that there are no topology loops in your network. If not enabled, you may also enable Spanning Tree.