Fibre-link problems 2

[LookDef]

Hi all,

We're having some troubles with the fibre/DS1 link to one of our EPNs. The alarm log is as follows. Does anyone have a link to an Avaya document that fully explains alarm / test codes etc.. The stuff I keep getting up on the Avaya site is pretty rudimentary.. Here's the alarm logs from the outage we had this morning.. The problem resolves itself, though the EPN reboots in the process (not good when your CEO happens to be on the phone on that EPN at the time).. Am I right in thinking it's a lose of signal somewhere external to the system that is causing this problem ? Cheers to all in advance.

Port Maintenance On Alt Alarm Svc Ack? Date Date
Name Brd? Name Type State 1 2 Alarmed Resolved

03B17 UDS1-BD n WARNING 09/13/09:45 00/00/00:00
03B0905 DIG-LINE n 1539 WARNING RDY 09/13/10:03 00/00/00:00
SYNC n WARNING 09/13/10:21 00/00/00:00
SYNC n WARNING 09/13/10:21 00/00/00:00
SYNC n WARNING 09/13/10:21 00/00/00:00
SYNC n WARNING 09/13/10:21 00/00/00:00
SYNC n WARNING 09/13/10:21 00/00/00:00
01E18 SN-CONF n MAJOR y 09/12/05:29 09/12/05:30
01E18 SN-CONF n MAJOR y 09/12/14:23 09/12/14:24
01E18 SN-CONF n MAJOR y 09/12/19:47 09/12/19:47
5 A-PNC FIBER-LK n MAJOR y 09/12/23:48 09/12/23:48
5 A-PNC FIBER-LK n MAJOR y 09/12/23:48 09/12/23:49
01E18 SN-CONF n MAJOR y 09/12/23:48 09/12/23:49
5 A-PNC FIBER-LK n MAJOR y 09/12/23:49 09/12/23:49
01E18 SN-CONF n MAJOR y 09/12/23:49 09/12/23:49
5 A-PNC FIBER-LK n MAJOR y 09/13/03:57 09/13/03:57
5 A-PNC FIBER-LK n MAJOR y 09/13/03:58 09/13/03:58
01E18 SN-CONF n MAJOR y 09/13/03:58 09/13/03:58
PN 04 EXP-PN n MAJOR y 09/13/03:58 09/13/03:58
PN 04 EXP-PN n MAJOR y 09/13/03:58 09/13/03:58
PN 04 EXP-PN n MAJOR y 09/13/03:58 09/13/03:58
5 A-PNC FIBER-LK n MAJOR y 09/13/09:43 09/13/09:43
PN 04 EXP-PN n MAJOR y 09/13/09:43 09/13/09:43
PN 04 EXP-PN n MAJOR y 09/13/09:43 09/13/09:43
03minor EXT-DEV n MINOR y 07/31/14:31 07/31/15:02
03A17 UDS1-BD y MINOR y 08/16/03:39 08/16/04:45
01A H-ADAPTR y MINOR IN y 09/06/22:09 09/06/22:09
01A H-ADAPTR y MINOR IN y 09/06/22:09 09/06/22:09

 

[lopes1211]

yes, your ds1 with the signalling prob went down. run reports on all circuits and on both ends.

list meas ds1-f log 1e21a
list meas ds1-f log 1e21b

etc, etc



-CL

 

[4merAvaya]

Below is the link to the Avaya maintenance manual for a G3rV11.

Kevin

http://support.avaya.com/elmodocs2/multivantage/233823_2/233117_5/233117_5.pdf

 

[LookDef]

Hey guys,

Thanks for the help here.. I didn't actually get a chance to look back here much yesterday as the system is still rebooting every couple of hours.. I did a list meas ds1-f log 1e21a and here is a sample of what came out

DS-1 FACILITY LINK PERFORMANCE MEASUREMENTS DETAILED LOG REPORT

Counted Since: 7:44 pm TUE SEP 11, 2007

Date Time ES BES SES UAS/FS CSS LOFC

09/14 06:43 0 0 0 0 N/A N/A
09/14 06:58 0 0 0 0 N/A N/A
09/14 07:13 0 0 0 0 N/A N/A
09/14 07:28 0 0 0 0 N/A N/A
09/14 07:43 0 0 0 0 N/A N/A
09/14 07:58 0 0 0 0 N/A N/A
09/14 08:13 0 0 0 0 N/A N/A
09/14 08:28 0 0 0 0 N/A N/A

The times here don't specifically corrolate to the times the system went down.. Sometimes there is a log and the system was fine, other times the system has gonne down around that time, but I feel that's just because these logs seem to come up evey 15 - 30 minutes anyway.

The strange thing about this problem is though that the DS1 link to the 3rd cabinet (the one we're having the problem on) is acutally to a remote cabinet. We have it going through an IPMUX and shoved down one of out data links. This system has been working for well over a year now, and every time the system has gone down there has always been logs in the IPMUXs showing a loss of sync.. Here though, when the system reboots, according to the MUXs the link remains up and operating!! Is it possible the 3rd cabinet is not rebooting at all and this error is just causing maybe some of the cards in the cabinet to reset while keeping the link up?

Really, thanks for everything you might be able to tell us in advance.. We've even go a local Avaya tech stumped on this one.

 

[lopes1211]

You need to run that report for each side of each circuit connecting the PPN and EPN. While these are technically ds1's connecting the remote EPN, there are several 64K channels dedicated for the synch/signalling. The synch/signalling is always on the A or B circuit of a DS1 remote (never the C or D). I wouldn't hesitate to send the C&D circuits though some kind of IP mux since delay,jitter,latency will only affect voice quality and not bring the whole cabinet down. I question what excess data traffic on you IP link would do to the signalling links on the 1st two circuits though. Your mux idea is clever but not a supported application. Not too surprising an Avaya tech would shrug their shoulders.

-CL