RRN 00198 HANDLE N7 ROUTESET (UNSUCCESSFUL)

PLGND926

Message Triggering Condition

Response in case of not successful result of the execution, on operator request, of one of the following MMC-commands:
CRN 00247 EXTEND-N7RTES
CRN 00248 REDUCE-N7RTES
CRN 00249 MODIFY-N7RTES
CRN 00250 DISPLAY-N7RTES

Report Layout

 SWA-ORJ-MTP
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        LOGNET: (1)............
        OPERATOR INPUT: (2)
          RTESID   = (3).............
          REFRTES  = (4).............
          CLSNAME  = (5).....
          (6)....... (7).....
          (8)....... (9)
          RTEPRIO  = (10)
          MANDISTR = (11)............
          COMBLKS  = (12)....
          NMMSG    = (13)...
          RTESFUNC = (14)..
          RTEFUNC  = (15)..
          ALTRTES  = (16)............
          SI       = (17)&(18)&(19)
          SLSRCT   = (20)
          ALL(21)
          RTSPONLY = (22)
          DETAIL   = (23)....
          CONTROL  = (24).... & (25) & (26) & (27) & (28)
          MEMBER   = (29)
        -----------------------------------------------------------------------
        RESULT :(30)
          (31)........................................................
          (32)........................................................
          (33)........................................................
          IN PARAM: (34).... (35)..
  REPORT REFERENCE NUMBER = 0198

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
(D) Result part number
(E) Continuation indicator
(1) Network indication of own node
(2) Operator Input Heading
(3) Parameter name existing routeset name
(4) Parameter name name of the reference routeset
(5) Combined Linkset Name For ANSI combined linkset
(6) LKSETx = title for title purpose
(7) "route specification by LKSET1= Linkset identity
(8) COSTx = title for title purpose
(9) Route cost route cost to be assigned to
route 1 (see LKSET1)
(10) Route priority route priority to be assigned
(11) Manual distribution When manual distribution is
specified, the ORJ fills up the
routing distribution according to
the specification given by the
operator in this parameter
(12) Combined linkset applicability indication indicates whether the routes
specified form a combined route
having the same priority
specified by RTEPRIO or as
seprate routes with different
priority
APPLIC combined linkset applicable
NOTAPPL combined linkset not applicable
(13) Network management messages applicability can have ON or OFF values for a
Routeset
OFF combined linkset not applicable
ON combined linkset applicable
(14) Routeset function indicates wether the routeset
must be activated or not
(default=activate)
ACTIVATE activate routeset upon creation
DEACT deactivate routeset
REMCIRTG remove circular routing
REMXLIST remove circular routing
(15) Route function indicates wether the route must
be activated or not
(default=activate), see parameter
18
ACTIVATE activate route upon creation
DEACT deactivate route
FRCDEACT forced deactivate route (in case
of the deactivation of the last
active route of the routeset)
PUTTFA put traffic allowed for the
route(s)
(16) Alternative Routeset Alternative Routeset to be used
in case of routing on SI
(17) Service Indicator Indicate if there are alternative
routing (default=0).
(18) Service Indicator Indicate if there are alternative
routing (default=0).
(19) Service Indicator Indicate if there are alternative
routing (default=0).
(20) SLS for RCT States the Signalling link
Selection of the link on which to
send the routeset congestion test
message
(21) Indication given depending on operator input indicates to display for all
values of Routeset
(22) Route type is for STP or orignating traffic can have either ORG or STP values
(23) Detailed display request specifies the type of display for
one or all Routeset
ABNRTG routesets with abnormal routing
AVDEST all available routeset
destinations
DEFAULT default report
MTPOVW message transfer part overview
NORMRTG routesets with normal routing
NOTIFY notify destinations
RTESTATL routeset state-long
RTESTATS routeset state-short
TRAFFIC traffic info
UNAVDEST all unavailable routeset
destinations
XLIST display all xlist connected to
that destination
(24) Command control type CANCEL ongoing display or
SCHEDULE
CANCEL cancelled
SCHED scheduled
(25) Start month for the scheduled request: MONTH 1 to 12
(26) day for the scheduled request: DAY 1 to 31
(27) hour for the scheduled request: HOUR 1 to 24
(28) minute for the scheduled request: 0 to 59
MINUTE
(29) Member of cluster routeset can have values 0:255
(30) Result of the request Old or new data
(31) Error reason see Evaluation
(32) Error reason see Evaluation
(33) Error reason see Evaluation
(34) Faulty parameter mnemonic indicates mnemonic for Faulty
parameter
ALL display all routesets in CA and
NCA
ALTRTES alternative routeset name
CLSNAME combined linkset NAME
COMBLKS create combined linkset
CONTROL command control
COST route cost
DETAIL detail
LKSET linkset specifying the 4 routes
MANDISTR manual route distribution
NMMSG network management messages
REFRTES reference routeset
RTEFUNC route function
RTEPRIO route priority
RTESFUNC routes function
RTESID routeset identity
SI service indicator
SLSRCT SLS for RCT
(35) Faulty parameter value indicates the value for Faulty
Parameter

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(31) COMMAND ABORTED . . . . . . . . . . . . . . . . . A
(32) NO RESPONSE FROM ACCOUNTING MODULE . . . . . . . . A
(32) REDUCE NOT ALW: LAST ROUTE USED BY ISUP/TUP . . . A
(32) REDUCE NOT ALW: LAST ROUTE USED BY SCCP . . . . . A
(32) REDUCE NOT ALW: ROUTESET IN USE BY ACCOUNTING . . A
(32) SYSTEM ERROR OCCURED IN ACCOUNTING MODULE . . . . A
(33) GIVEN ROUTE IS NOT PART OF ROUTESET . . . . . . . A
(33) NO ROUTESET DEFINED FOR DEST . . . . . . . . . . . A
(33) NO ROUTESET MATCHING OPERATOR INPUT FOUND . . . . A
(33) ROUTING ON SI EXISTS ALREADY FOR RTESID . . . . . A
(33) RTESID SPECIFIED IN PARAM ALTRTES ALREADY EXISTS . A
(33) USE FRCDEACT TO DEACT LAST ACTIVE RTE IN RTESET . A

Action Description

Action Meaning
A The result data is given as an error message, when an inconsistent data is detected during the check of the operation, which is specified by the specific input parameters, whether is valid and in conflict with the existing data.

Check input data:

to Extend N7 Routeset:

  • route priority may be 1, 2, 3 or 4
  • a routeset cannot contain more then 4 different routes
  • a reference routeset (REFRTES) may only be specified when the

routeset to be extended does not yet contain any routes, i.e. the routeset to be extended must be an empty routeset.

  • all specified routes must already exist and be valid for the

same network(s) as the routeset destination

  • the destination of each specified route must be adjacent and

the corresponding N7 signalling exchange must be defined as STPSP

  • no specified route may already be used in the routeset
  • the priority of the direct route must always be 1 and there

can only exist one direct route in a routeset

  • a routeset for the non-concerned area can only have one route

of each priority (no combined linksets to a non-concerned area) . for routesets to the non-concerned area combined linksets are not allowed because TFP / TFA is not supported for the non-concerned area. to Reduce N7 Routeset:

  • the command must leave a valid routeset configuration if this

is the last available route (R_N74RS_SP / DY) in the routeset, then no user may be defined for DEST, i.e: . no TUP/ISUP users may use the specified routeset(s) . no TAX users may use the specific routeset . the destination may not exist as SCCP destination to modify N7 Routeset:

  • in case of concerned area (NCANAME not specified), the last

active route of the routeset cannot be deactivated by IRTEFUNC = DEACT. Use FRCDEACT.

  • if at least 1 route is specified (ADJEXCHx/LKSETx is

mentioned):

  • the route priority is derived from the RTEPRIO parameter,

i.e.: the route via ADJEXCH1/LKSET1 will receive priority as defined by parameter RTEPRIO, the route via ADJEXCH2/LKSET2 will receive priority RTEPRIO + 1 and so on. to Display N7 Routeset:

  • if DETAIL is equal to ABNRTG, NORMRTG, AVDEST or UNAVDEST,

then either DEST=ALL, NCANAME=ALL or ALL parameter must be specified

  • the ALL option for the network indicator is only valid using

exchange name input for parameter DEST

  • if DETAIL is equal to MTPOVW, ABNRTG, NORMRTG, AVDEST or

UNAVDEST the link related data of the route in use is displayed. It consists of : . the adjacent destination (EXCHNAME / SPLIT_PC & SSF), . the external linset number (LKSET), . the linktype, . the signalling link code (SLC), . the traffic- and level 3 status.

  • if DETAIL = DESTNCA and one destination (point code & SSF) is

specified, the corresponding non-concerned area name is displayed,

  • if DETAIL = DESTNCA and a non-concerned area (NCANAME = ALL)

is specified, all destinations in the requested non-concerned area are given,

  • if DETAIL = DESTNCA and all non-concerned areas (NCANAME =

ALL) is specified, all non-concerned area names are displayed.

Correct the input data and enter the MMC-command again. If applicable, see also the invalid parameter identity (parameter 18).

If the input data is correct, the given result data can be taken as an information only and it is quite possible that, commands to be entered previous to the command, are forgotten. In that case, enter the necessary MMC-commands first.