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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

E1 ISDN link generating many Far end alarms in log 2

Status
Not open for further replies.

UCXaus

Technical User
Dec 5, 2011
46
0
0
AU
I've recently installed a Mitel 3300 (CXi, MCD 5.0SP1) at a customers site which has a new ISDN10 connection.

The ISDN trunks work - you can call in and call out on them, no problem. However, the maintenance log is filling up with entries like the following:

Call Control - Maintenance - MC269CA Universal E1 at location 03 1 02 01 Type of diagnostics : Background Scope of report : Hybrid Reason(s) for report: - Far end alarm : Absent

ISDN VDsu-1 Mod 1 Port 1 - All alerts are CLEARED

Call Control - Maintenance - MC269CA Universal E1 at location 03 1 02 01 Type of diagnostics : Background Scope of report : Hybrid Reason(s) for report: - Far end alarm : Present

ISDN VDsu-1 Mod 1 Port 1 - Layer 1 YELLOW alarm ACTIVE


Being that it says 'Far end alarm', is this something going screwy at the carrier's end? Or is it something I need to configure on the trunks?

:code.poet:
 
far end alarm normally indicates an error at the exchange end. Are you experiencing any issue with service.
 
What does this maintenance command say?

dtstats read 3 1 2 1 last 24

**********************************************
What's most important is that you realise ... There is no spoon.
 
@bobcheese - No issues have been reported to me regarding loss of service, dropouts, etc. I found this when I did my weekly maintenance log download and check.

@kwbMitel - output is as follows:

Code:
Universal E1          3 1  2  1                                                 
Link is Available                                                               
         duty                             bit                                   
         cycle       framing              error                                 
Time     (%)         losses     slips     rate                                  
------------------------------------------------                                
 9:05    100            0           0         0                                 
 9:00    100            0           0         0                                 
 8:00    100            0           0         0                                 
 7:00    100            0           0         0                                 
 6:00    100            0           0         0                                 
 5:00    100            0           0         0                                 
 4:00    100            0           0         0                                 
 3:00    100            0           0         0                                 
 2:00    100            0           0         0                                 
 1:00    100            0           0         0                                 
 0:00    100            0           0         0                                 
23:00    100            0           0         0                                 
22:00    100            0           0         0                                 
21:00    100            0           0         0                                 
20:00    100            0           0         0                                 
19:00    100            0           0         0                                 
18:00    100            0           0         0                                 
17:00    100            0           0         0                                 
16:00    100            0           0         0                                 
15:00    100            0           0         0                                 
14:00    100            0           0         0                                 
13:00    100            0           0         0                                 
12:00    100            0           0         0                                 
11:00    100            0           0         0                                 
10:00    100            0           0         0                                 
------------------------------------------------


:code.poet:
 
Thanks, danramierz. First clock source was empty, but since I specified the E1 link I haven't seen any more alerts in the logs.

:code.poet:
 
@ UCXaus, when you don't specify a clock source it would normally generate an alarm stating 'NENSYNC' was this not the case? Also, out of curiosity what is ISDN10? Is it just E1 with max 10 channels? We dont have this in UK just ISDN2 and ISDN30.
 
@ bobcheese, yes it is just 10 active channels of an ISDN30. In Australia we have 10, 20, 30.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top