| Par. No.
| Meaning
| Remarks
|
| (A)
| Command name
| |
| (B)
| Main execution result
| |
| (C)
| Result part type
| |
| (D)
| Result part number
| |
| (E)
| Continuation indicator
| |
| (1)
| Concentrator identity
| |
| (2)
| Hexadecimal network address of security block
| |
| (3)
| Security block type
| see SI 006 |
| (4)
| Security block type
| see SI 006 |
| (5)
| Security block type
| see SI 006 |
| (6)
| Security block type
| see SI 006 |
| (7)
| Security block type
| see SI 006 |
| (8)
| Security block type
| see SI 006 |
| (9)
| Security block type
| see SI 006 |
| (10)
| Security block type
| see SI 006 |
| (11)
| Header
| |
| CONV
| converter |
| RIT
| replaceable item |
| (12)
| Row identification
| |
| (13)
| Rack identification
| |
| (14)
| Shelf number
| |
| (15)
| Slot number
| |
| (16)
| Logical control element identity
| hexadecimal form |
| (17)
| Security block category
| |
| BBCON
| broadband control |
| BBNET
| broadband network |
| CE
| control element |
| NETWORK
| network |
| PERI
| peripheral |
| SYS
| system |
| TEL
| telephonic |
| (18)
| Control element function
| see SI 019 |
| (19)
| Application processor type
| see SI 210 |
| (20)
| Security block number which can be also the first one in a range
| |
| (21)
| Security block number which is the last one in the range
| |
| (22)
| Security block status
| see SI 017 |
| (23)
| Security block status
| see SI 017 |
| (24)
| Security block status
| see SI 017 |
| (25)
| Security block status
| see SI 017 |
| (26)
| Security block status
| see SI 017 |
| (27)
| Security block status
| see SI 017 |
| (28)
| Security block status
| see SI 017 |
| (29)
| Security block status
| see SI 017 |
| (30)
| RIT status
| |
| EQ
| equipped |
| EQALW
| equip allowed |
| NEQ
| not equipped |
| REPLACE
| replaced |
| (31)
| Display or translate option
| |
| (32)
| Display or translate option
| |
| (33)
| Display or translate option
| |
| (34)
| Display or translate option
| |
| (35)
| Indication in case of a request to display the full list of all SBLs
| |
| (36)
| Comments on execution result
| |
| (37)
| Replaceable item type
| see SI 010 |
| (38)
| Relation identity
| |
| (39)
| Database main status
| see SI 057 |
| (40)
| Database sub-status
| see SI 057 |
| (41)
| Error point referring to a specific point in the source listing as indication where the database failure occurred
| |
| (42)
| Item specification in case of error
| |
| (43)
| Result data header
| |
| (44)
| Result data sub-header
| |
| (45)
| Security block type
| see SI 006 |
| (46)
| Security block type
| see SI 006 |
| (47)
| Security block type
| see SI 006 |
| (48)
| Security block type
| see SI 006 |
| (49)
| Security block type
| see SI 006 |
| (50)
| Security block status
| see SI 017 |
| (51)
| Number of security blocks which are in the specified state for the given security block type
| |
| (52)
| Number of security blocks which are in the specified state for the given security block type
| |
| (53)
| Number of security blocks which are in the specified state for the given security block type
| |
| (54)
| Number of security blocks which are in the specified state for the given security block type
| |
| (55)
| Number of security blocks which are in the specified state for the given security block type
| |
| (56)
| Result data header
| |
| (57)
| Result data sub-header
| |
| (58)
| Result data sub-header
| |
| DEVT/CEF
| device type / control element
function |
| (59)
| Result data sub-header
| |
| LCE
| logical control element |
| (60)
| Result data sub-header
| |
| APT
| application processor |
| (61)
| Result data sub-header
| |
| COMING UP
| RTSU status |
| ISOLATED
| RTSU status |
| NO TONES
| RTSU status |
| NORMAL
| RTSU status |
| (63)
| Hexadecimal network address of security block
| |
| (64)
| Security block type
| see SI 006 |
| (65)
| Security block number
| can also be the first one in a
range |
| (66)
| Last security block number in the range
| |
| (68)
| Security block status
| see SI 017 |
| (69)
| Device type
| see SI 009 |
| (70)
| Control element function
| see SI 019 |
| (71)
| Logical control element identity
| hexadecimal form |
| (72)
| Application processor type
| see SI 210 |
| (73)
| Data header for cross-over
| |
| (74)
| Cross-over flag indication
| |
| EVEN SIDE
| even side |
| NORMAL SIDE
| normal side |
| ODD SIDE
| odd side |
| (75)
| Cross-over inhibit flag indication
| |
| FIXED EVEN SIDE
| fixed even side |
| FIXED NORMAL SIDE
| fixed normal side |
| FIXED ODD SIDE
| fixed odd side |
| FREE
| free |
| (76)
| Result data header
| |
| (77)
| Result data sub-header
| |
| (78)
| Replaceable item type
| see SI 010 |
| (79)
| Row identification
| |
| (80)
| Rack identification
| |
| (81)
| Shelf number
| |
| (82)
| Slot number
| |
| (83)
| Status of replaceable item
| |
| BUSY
| busy |
| EQ
| equipped |
| EQALW
| equip allowed |
| NEQ
| not equipped |
| REPLACE
| replaced |
| (84)
| Hot insertable / not hot insertable indication
| |
| N-A
| not applicable |
| NO
| not hot insertable |
| YES
| hot insertable |
| (85)
| Suspected / not suspected indication
| |
| NO
| not suspected |
| YES
| suspected |
| (86)
| Mandatory / not mandatory indication
| |
| NO
| not mandatory |
| YES
| mandatory |
| (87)
| Circuit breaker number
| |
| Key Parameter
| Contents / Meaning
| Action
|
| 1
| 2
| 3
|
|
|
| (36)
|
|
| BUILD OF DEPENDENT LIST FAILED . . . . . . . . . .
|
B
|
| (36)
|
|
| CANCELLED . . . . . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| CE IS NOT EQUIPPED . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| COMMAND HANDLER LIMIT REACHED . . . . . . . . . .
|
D
|
| (36)
|
|
| DATA BASE FAILURE . . . . . . . . . . . . . . . .
|
C
|
| (36)
|
|
| EXTERNAL EQUIPMENT . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| HIGHER LEVEL CHECK : STACK OVERFLOW . . . . . . .
|
C
|
| (36)
|
|
| NO ANSWER FROM O&M SACE . . . . . . . . . . . . .
|
B
|
| (36)
|
|
| NO APPLICATION PROCESS . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| NO IDENTITIES FOUND . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| NO RITS FOUND . . . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| NO SBLS MAPPED ON THIS RIT . . . . . . . . . . . .
|
A
|
| (36)
|
|
| NO TUNNEL CONTROLLING CE FOUND . . . . . . . . . .
|
A
|
| (36)
|
|
| NO TUNNELS IN ETHERNET SWITCH . . . . . . . . . .
|
A
|
| (36)
|
|
| RIT IS NOT EQUIPPED . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| RIT IS REPLACED . . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| SBL IS NOT EQUIPPED . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| SBL NBR OUT OF RANGE . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| TOO MANY RESULTS, BUFFER OVERFLOW . . . . . . . .
|
E
|
| (36)
|
|
| UNEXISTING CONVERTOR . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| UNEXISTING LCE . . . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| UNEXISTING RIT . . . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| UNEXISTING RTSU . . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| UNEXISTING SBL . . . . . . . . . . . . . . . . . .
|
A
|
| (36)
|
|
| UNEXISTING SBLTYPE . . . . . . . . . . . . . . . .
|
A
|
| Action
| Meaning
|
| A
| The result data is given as an error message when inconsistent data is detected during the check of the operation. Check input data. If applicable, refer to the Restrictions part of the corresponding MMC-command. If the input data is not correct, repeat the MMC-command with adapted data. If the input data is correct, the given result data can be taken as information only. Otherwise, it is quite possible that commands to be entered previously, are forgotten. In that case, enter the necessary MMC-commands first. |
| B
| Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. If any error point is given it refers to a specific point in the source listing as an indication where the database failure has occurred. |
| C
| Special fault clearing will be necessary. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. If any error point is given it refers to a specific point in the source listing as an indication where the database failure has occurred. |
| D
| Wait until the current request is finished and submit the MMC-command again. |
| E
| Split-up the translation or display request into a number of requests with more limited options. Repeat the MMC-command with adapted data. If the fault occurs again, special fault clearing will be necessary. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. |