BERR Errors

[NY105]

Good Morning,

I have a CS1000M rls 5 and receiving BERR 300 and BERR 600 errors on my DCH's. I get them on both shelf (0 & 1) depending on which CPU is active. I already swapped out the CNI cards for both and still have same problem. I also checked all the cables on both MSDL cards and 3PE cards. Once in awile it will actually take down the DCH that is on that shelf with the active CPU. I am starting to wonder if one or both 3PE cards are bad or need to be reseated. If that is the case, what is the procedure for doing this task.

Thanks

 

[Firebird Scrambler]

I found this below for two references that may give you a clue?.

Had a site that produced FIJI005 and BERR300/600 failures leading to Per Sig cards going disabled
Also Firmware Audit messages ( FHW000 & FHW002 ) were seen for hardware associated with the Per Sig cards.

Doing a SSCK on the Active of Standby Clocks in LD 60 showed a VCXO AGING error as below :-
>LD 60
DTI000
.SSCK 0
ENBL
CLOCK ACTIVE
GROUP 1
SIDE 0
CLOCK CONTROLLER - TRACK ON LOOP 4
PREF - 4
SREF - 48
AUTO SWREF CLK - ENBL
VCXO AGING

From the NTP's The LD 60 SSCK command the VCXO AGING states
VCXO AGING ERROR = the timing crystal is faulty, replace the clock.
For both Clock Controllers to give this error is unusual.

It was found that the BT Main exchange was using the DWSS system to supply Timing & Syncronization to the Meridian.
There was a fault with the DWSS that corrupted the clock but didn't mark it as faulty.
So the Meridian still thought it had a good clocking source and didn't switch to the standby clock, but as this clock source was corrupt we got the FIJI / FHW000 / Per Sig errors.

Below is a typical listing for the event.
----------------------------------------------


FIJI005 RING 0

FIJI101 1 0

FIJI300 1 0 FROM: ENBL TO: SYS DSBL - SELF TESTING
TIME: 13:20:10

FIJI005 RING 0

BERR600 NCB 0 1: Check Device 'IGS 3' at address 0xe162 in Group 1
Check IO device, network device, or PS card

BERR600 NCB 0 1: Check Device 'IGS 0' at address 0xe00c in Group 1
Check IO device, network device, or PS card

FIJI005 RING 0

FIJI300 1 0 FROM: SYS DSBL - SELF TESTING TO: SYS DSBL - SELFTESTS PASSED
TIME: 13:20:48

>LD 60
DTI000
.SSCK 0
ENBL
CLOCK ACTIVE
GROUP 1
SIDE 0
CLOCK CONTROLLER - TRACK ON LOOP 4
PREF - 4
SREF - 48
AUTO SWREF CLK - ENBL
VCXO AGING

The VCXO AGING states
8. VCXO AGING ERROR = the timing crystal is faulty, replace the clock.


FHW000 32 LOOP RESPONSE TIME OUT

FHW000 33 LOOP RESPONSE TIME OUT

FHW000 34 LOOP RESPONSE TIME OUT

FHW000 35 LOOP RESPONSE TIME OUT

XMI000 44 : PLL UNLOCK EVENT

FHW000 33 LOOP RESPONSE TIME OUT

FHW000 33 LOOP RESPONSE TIME OUT

FHW000 33 LOOP RESPONSE TIME OUT

FHW000 33 LOOP RESPONSE TIME OUT

FHW000 33 LOOP RESPONSE TIME OUT

FHW000 33 LOOP RESPONSE TIME OUT

FHW000 48 LOOP RESPONSE TIME OUT

FHW000 50 LOOP RESPONSE TIME OUT

ERR4500 315 48 00013981

ERR5340 48

FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
ERR4500 330 48 310664053

FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW000 48 LOOP RESPONSE TIME OUT

FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW000 48 LOOP RESPONSE TIME OUT

FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT

FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT

FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT
FHW002 48 EXPANDED SDI DEVICE RESPONSE TIMEOUT

###########################################################

ANALYSIS
Nortel has completed its investigation of a potential problem with QPC441F (3PE) Version C cards that could cause system problems during insertion.
The problem investigated is related to a marginality issue with batches of CMOS PROMs used on Version C cards. The suspect PROMS may not enable properly during insertion and may generate system error messages and prevent cards from enabling initially.
One or more of the following symptoms could be seen if a faulty Version C card is inserted in system :
1. BERR300 and BERR600 messages generated to TTY
2. Cannot enable XCT (NT8D17) and PS (QPC43R) cards during installation. A disable and enable attempt or rebooting the system will bring cards into proper working service.
3. System may INI during the initial insertion of QPC441F Version C card.
4. Could cause issues with enabling other cards in the network shelf (including FIJI's, PRI cards, XNET etc)
Note : This issue is seen upon insertion. Cards with a good PROM will not exhibit this issue.

Faulty version C cards should be replaced with version D - see Nortel Technical Bulletin 2006007039 for full details



All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[NY105]

Below is what I am getting on the TTY. I checked both 3PE cards and here are the numbers.

QPC441F B NNTM1832C93V



000000000000000000
FHW001 15 SDI DEVICE RESPONSE TIMEOUT

BERR300 CNIP 37655856 0 0: Address=0x4208c3c9, BERZ=0x0

BERR300 CNIP 37655856 0 0: Address=0x4208c3c9, BERZ=0x0

BERR600 NCB 1 0: Check Device "SDI 15" at address 0x30f2 in Group 0
Check IO device, network device, or PS card

MSDL307 GROUP 0 MSDL 15 0000DEAD 0000A522 000000C0 00000000 0000001E 0000000E 0
0000038
00000000

0000001E 00000000 00000000 00000000 00000000 00000000 00000040 0000000
0
00000000 00000000 00000000 00000000 0000001E 00000000 00000000 0000001
0
00002578 00000010 00001080 0000008F 00007DB8 00000000 00000000 0000008
F
00007DC8 0000008F 00007D00 0000008F 000075F0 00000082 0000C4C4 0000008
F
00007D00 00000000 00003704 00000080 00000000 00000000 00000001 0000000
0
00000000 00000000 00000001 000047D3 00008FB3 00003000 00000081 0000162
8
0000B008 00000E6C 00000155 00000200 00000008 00000010 000025B5 0000001
0
000025B5 0000008F 00002801 00001032 00008A01 00000081 00001630 0000008
1
DCH: 13 DISABLED (MSDL 15 SYS DSBL)
MSDL101 GROUP 0 MSDL 15

MSDL300 FROM: ENBL TO: SYS DSBL - SELFTESTS FAILED
TIME: 11:20:25 REASON: 68020 BUS ERROR

MSDL112 GROUP 0 MSDL 15

MSDL300 FROM: SYS DSBL - SELFTESTS FAILED TO: SYS DSBL - SELF TESTING
TIME: 11:20:57

MSDL300 FROM: SYS DSBL - SELF TESTING TO: SYS DSBL - SELFTESTS PASSED
TIME: 11:21:29

MSDL300 FROM: SYS DSBL - SELFTESTS PASSED TO: ENBL
TIME: 11:21:29

DCH: 13 EST CONFIRM TIME: 11:21:31 13/02/2012

 

[NY105]

I am also having issues with this still. I could not find the referenced Tech Bulletin mentioned above. I need some direction on this, my DCH's keeping cycling and every few days I have to INI the PBX to get them going again because it will spit out errors and I can not get into the TTY.

 

[NY105]

If anyone is interested in the fix here goes. The DCH daughterbaords on the NT5D12's where bad. I removed them and installed an external MSDL card for my DCH's and when I turned them back on evertything was working like it should. No more hardware faults on either DCH or MSDL. The only thing left I have to figure out is why am I getting "000000" on all my TTY's. Last mystery to solve on this one.