Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Network Event Log errors, but CSU Stats are clean

Status
Not open for further replies.

Roshan2

MIS
Joined
Nov 3, 2003
Messages
9
Location
US
I have a 0x32 running MICS 6.0. I put in two PRIs, a local and an LD, about a month ago. The local has been fine, but the LD bounces at random intervals of several hours to about 10 days. All calls on it drop and these errors are recorded in the Network Event Log:

EVT325-00 (S5) Errored Second
EVT328-00 (S5) Line Code Violation
EVT330-00 (S5) Loss of Frame
EVT323-00 (S5) Degraded Minute

However, the CSU stats show no errors when the line bounce occurs (or at any other time). On a couple of occasions I have had the line vendor check the card at the HDSL card at the MPOE and they have reported that it showed no errors.

I have had my PBX support vendor replace both PRI cards (the replacement for the LD line is a brand-new card); he also replaced the NVRAM cartridge with a newer-version card as the one I had was running a buggy version. However, the problem is still occurring.

My PBX vendor is considering replacing the KSU itself, and is also working with Nortel support on the issue. Does anyone have any ideas on this issue?

Thank you very much,
Roshan
 
I'd check the cable/ connectors (or change it) between the MPOE and the system
 
At one point, we had 2 E&M lines, each going over a T1 to remote locations, with 6 channels for voice & the rest data.

The second remote location, all of a sudden, appeared to lose its T1 -- it would bounce from up to down continually.

After working with Telco, our Norstar vendor, and a third party, it was determined that it was a clocking issue -- I believe that both the Norstar & our Adtran were trying to each do the clocking. Shutting clocking off on the Adtran resolved it.

Perhaps your issue is clocking?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top