| CRN 07603 | DISPLAY-N7-ALMPARS |
SWA-SUBSEC MTP
(A)....................... (B).................
(C)........................... (D) (E)
-----------------------------------------------------------------
OPERATOR INPUT:
LOGNET = (1)..............
CONTROL = (2)... & (3) & (4) & (5) & (6) & (7) & (8)
----------------------------------------------------------------------
RESULT: (9)....
GENERAL PARAMETERS:
-------------------
LKOOSTIM : (10) & (11)
LSOOSTIM : (12) & (13)
RTOOSTIM : (14) & (15)
LKALMGAP : (16) & (17)
REPGAP : (18) & (19)
OOSOCC : (20) / HOUR
LOGNET: (22)............
REPORT PARAMETERS:
------------------
LKSTCHRP : (23).
COSTCHRP : (24).
LSSTCHRP : (25).
SREJREP : (26).
SFAILREP : (27).
SEXCSTRP : (28).
TFCREP : (29).
MSUDSCRP : (30).
UPUSCRP : (31).
DSTCHRP : (32).
ALARMTRIGGERS:
--------------
LINK RELATED TRIGGERS:
----------------------
EXTFLT : (33)..
ORJDIS : (34)..
HWFLT : (35)..
MAIDIS : (36)..
SLOALM1 : (37)..
SLOALM2 : (38)..
CONG1ALM : (39)..
CONG2ALM : (40)..
CONG3ALM : (41)..
SCREENING RELATED TRIGGER:
--------------------------
SREJALM : (42)..
RDD RELATED TRIGGERS:
---------------------
RTGERALM : (43)..
DISCRALM : (44)..
DISTRALM : (45)..
RSUNAALM : (46)..
ROUTESET RELATED TRIGGERS:
--------------------------
INACCTFP : (47)..
INACCLSF : (48)..
INALSTFP : (49)..
CRTGALM : (50)..
LINK OCCUPANCY THRESHOLDS:
--------------------------
THRSLO1 : (51)
THRSLO2 : (52)
SCREENING THRESHOLDS:
---------------------
THRSREJ : (53).
THRSMSG : (54).
RDD THRESHOLDS:
---------------
THRRTGER : (55).
THRDISCR : (56).
THRDISTR : (57).
THRRSUNA : (58).
REPORT REFERENCE NUMBER = 4320
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | Command name | |
| (B) | Main execution result | |
| (C) | Result part type | |
| (D) | Result part number | |
| (E) | Continuation indicator | |
| (1) | Input logical network name | max. 16 characters via R_N7LNMNEM |
| (2) | Command control | can be CANCEL or SCHED |
| CANCEL | cancel request | |
| SCHED | schedule request | |
| (3) | Start date for the scheduled request | month |
| (4) | Start date for the scheduled request | day |
| (5) | Start time for the scheduled request | hour |
| (6) | Start time for the scheduled request | minute |
| (7) | Period for the scheduled request | number of hours |
| (8) | Period for the scheduled request | number of minutes |
| (9) | Information about execution result | see EVALUATION |
| (10) | Link out of service time | time duration that a link must be
out of service before giving an alarm (minutes) |
| (11) | Link out of service time | (seconds) |
| (12) | Linkset out of service time | time duration that a linkset must
be out of service before giving an alarm (minutes) |
| (13) | Linkset out of service time | (seconds) |
| (14) | Routeset out of service time | time duration that a routeset
must be out of service before giving an alarm (minutes) |
| (15) | Routeset out of service time | (seconds) |
| (16) | Link alarm gap | minimum time between two link
alarms (minutes) |
| (17) | Link alarm gap | (seconds) |
| (18) | Report gap | minimum time between two reports
(minutes) |
| (19) | Report gap | (seconds) |
| (20) | Out of service occurrence | number of times that a link must
go out of service in an hour before giving an alarm |
| (22) | Logical network name of which the alarm parameters are displayed | max.16 characters via R_N7LNMNEM |
| (23) | Indication whether the link status change report is required | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (24) | Indication whether the congestion status change report is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (25) | Indication whether the linkset status change report is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (26) | Indication whether the screening rejection report is is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (27) | Indication whether the screening failures report is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (28) | Indication whether the screening excess traffic is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (29) | Indication whether the transfer control status change report is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (30) | Indication whether the message signalling unit (MSU) discarded report is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (31) | Indication whether the user part unavailable (UPU) report is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (32) | Indication whether the routeset status change report is needed | can have values FALSE or TRUE |
| FALSE | report is not needed | |
| TRUE | report is needed | |
| (33) | Alarmtype used for link OOS due to external faults | it specifies the type of alarm |
| NOALM | no alarm | |
| NONURG | non urgent alarm | |
| SURG | semi-urgent alarm | |
| URG | urgent alarm | |
| (34) | Alarmtype used for link OOS due to
ORJ command see param (33) | see param (33) |
| (35) | Alarmtype used for link OOS due to
HW faults see param (33) | see param (33) |
| (36) | Alarmtype used for link OOS due to maintenance
see param (33) | see param (33) |
| (37) | Alarmtype to be issued for signalling link occupancy level 1
see param (33) | see param (33) |
| (38) | Alarmtype to be issued for signalling link occupancy level 2
see param (33) | see param (33) |
| (39) | Alarmtype to be issued for congestion level 1 alarm
see param (33) | see param (33) |
| (40) | Alarmtype to be issued for congestion level 2 alarm
see param (33) | see param (33) |
| (41) | Alarmtype to be issued for congestion level 3 alarm
see param (33) | see param (33) |
| (42) | Alarmtype to be issued for screening rejection errors
see param (33) | see param (33) |
| (43) | Alarmtype to be issued for routing errors
see param (33) | see param (33) |
| (44) | Alarmtype to be issued for discrimination errors
see param (33) | see param (33) |
| (45) | Alarmtype to be issued for distribution errors
see param (33) | see param (33) |
| (46) | Alarmtype to be issued for routeset unavailable errors
see param (33) | see param (33) |
| (47) | Alarmtype for routeset alarm if non-adjacent destination is inaccessible due to TFP
see param (33) | see param (33) |
| (48) | Alarmtype for routeset alarm if adjacent destination is inaccessible due to linkset failure
see param (33) | see param (33) |
| (49) | Alarmtype for routeset alarm if non-adjacent destination is inaccessible due to linkset failure
see param (33) | see param (33) |
| (50) | Alarmtype for routeset alarm if non-adjacent destination is inaccessible due to circular routing
see param (33) | see param (33) |
| (51) | Alarm threshold value for signalling link occupancy 1 | in % load |
| (52) | Alarm threshold value for signalling link occupancy 2 | in % load |
| (53) | Alarm threshold value for screening rejection errors | Range 0-32000 (default=100) |
| (54) | Alarm threshold value for screening messages | Range 0-999999 (4 bytes,
default=0) |
| (55) | Alarm threshold value for routing errors | an integer (default=0) |
| (56) | Alarm threshold value for discrimination errors | an integer (default=0) |
| (57) | Alarm threshold value for distribution errors | an integer (default=0) |
| (58) | Alarm threshold value for routeset unavailable errors | an integer (default=0) |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (9) | NO VALID LOGNET EXISTS . . . . . . . . . . . . . . | AC | ||
| (9) | NOT SUCCESSFUL DUT END . . . . . . . . . . . . . . | BC | ||
| (9) | NOT SUCCESSFUL DUT START . . . . . . . . . . . . . | BC | ||
| Action | Meaning |
|---|---|
| AC | Check input data:
Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. |
| BC | Repeat the command after some time. If the result is still unsuccessful, special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. |