We have about 25 PM3s deployed, in a mix of PRI and CT-1 environments.
Many of them have been service for just about as long as Livingston has
been shipping PM3s. Running 3.9b22 at present, but I've observed this
with previous ComOS releases as well.
To date I've seen about five instances where the T-1 line interfaces
will go into a mode where telco sees massive errors. Line levels look
good, some errors seen on the receive end at the PM3.
This condition persists until the PM3 is powered off and back up. Rebooting
does not fix it. I have not verified if physically unplugging the T-1
lines and reconnecting fixes it.
It has happened infrequently enough as to not be the kind of thing one
can easily open a trouble case with Lucent over, and isn't repeatable
(at least not without months of waiting.)
Anyone else ever experience this? What's the fix?
-- Jay Hennigan - Network Administration - jay@west.net NetLojix Communications, Inc. NASDAQ: NETX - http://www.netlojix.com/ WestNet: Connecting you to the planet. 805 884-6323
- 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/>