pm3-1 error: port S37 stopped too long - flushing packet queue
The answer given was:
>*sigh*
>
>Anyway, the port was flow controlled for too long, the buffer filled,
>and was flushed.
Well, I have 4 PM3s connected to CT1s that are in a single trunk group so
the calls get spread evenly across the 4 boxes. The syslog contains many
of the above message for the first three PM3s but not the fourth unit.
The boxes are:
>pm3-1> ver
>Livingston PortMaster PM-3 ComOS 3.7.2c3
>System uptime is 27 days 6 hours 33 minutes
>pm3-1>
Is this a problem with the boxes? If not, why does it only happen on 3 of
the 4 boxes?
Is it possible that this problem is caused by something that the user does
or their configuration?
Any suggestions are welcome.
Butch
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>