Timeline for answer to Cisco pause input causing drop by Zac67
Current License: CC BY-SA 4.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 13 at 21:00 | comment | added | JukEboX | so the client is producing the Pause frame when it can't handle everything at once or is buffering? | |
| Jan 13 at 20:53 | comment | added | Zac67♦ | You mean it generates pause frames? That wasn't clear - pause frames are generated on the ingress port when the (or a) destination port is too busy to forward the ingress frames. | |
| Jan 13 at 19:10 | comment | added | JukEboX | Not yet. I do see storm control for other ports on other devices when it does trigger. But not on this one for all the PAUSES. PAUSES is caused by overwhelming the port on the switch or the computer not reading fast enough? | |
| Jan 13 at 18:34 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 33 characters in body
|
| Jan 13 at 18:22 | comment | added | Zac67♦ |
storm-control triggering isn't really an error. Have you tried debugging it?
|
|
| Jan 13 at 17:42 | comment | added | JukEboX | Switch is not sending storm control events in the log. Wouldn't it be throwing an error? | |
| Jan 13 at 17:31 | history | answered | Zac67♦ | CC BY-SA 4.0 |