NEC Neax 2400 Imx System Operations And Maintenance Manual

							CHAPTER 3 NDA-24238
Page 224
Revision 3.0
SYSTEM MESSAGES
This message is issued when the connection error related to external LAN Interface equipment occurs in the
system.
➀~➃ IP Address for external equipment in which error has been detected. (Hex.)
➄, ➅ Port No. (Client Port No.) (Hex.)
➆ Socket No. (Used Socket No.) (Hex.)
➇ Error Code (TCP/IP Error Code) (Hex.) See Ta b l e  3 - 2. TCP/IP Part Application Part
1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX
➀ ➁ ➂ ➃ ➄ ➅ ➆ ➇ ➈ ➉
4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000
7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
Default Alarm:
SUP26-VLAN Interface Error ReportDefault Grade: Grade Modified: Lamp Modified:
1112131415161718192021222324 
						

							NDA-24238 CHAPTER 3
Page 225
Revision 3.0
SYSTEM MESSAGES
Table 3-2  Error Code
Output Data 
(Hex.)DefinitionOutput Data 
(Hex.)Definition
BSD SOCKET ERROR 58 Address family not supported
10 User parameter error PROTOCOL FAMILY
11 Host not reachable 59 Address already in use
12 Timeout 60 Can’t assign requested address
14 Protocol error 61 Network is down
15 No buffer space *//62 Network is unreachable
16 Connection block invalid 63 Network dropped connection
17 Invalid pointer argument RESET
18 Operation would block 65 Connection reset by peer
19 Message too long 67 Socket is already connected
20 Protocol not available 68 Socket is not connected
50 Destination address required 69 Can’t send after socket shutdown
52 Protocol wrong type for socket 72 Connection refused
54 Protocol not supported 73 Host is down
55 Socket type not supported  76 Operation already in progress
56 Operation not supported on socket 77 Operation now in progress
57 Protocol family not supported 
						

							CHAPTER 3 NDA-24238
Page 226
Revision 3.0
SYSTEM MESSAGES
➈ Application Type
[When  =03 (SMDR) / 04 (MCI) ]
➉ Device Number of Error detected client PC
 Kind of Error
 Details on Detected Error 
~ Not used
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b0-b7 : (Hex)
01=SUPER SERVER
02=MAT
03=SMDR
04=MCI
05=OAI
06=PMS
07=MIS
9
b0-b7: (Hex)
Device Number of error detected Client PC. 
If the Machine Number is not determined, “FF”
is output.
b0-b7: (Hex)
01=SEND Execution Error
02=RECEIVE Execution Error
03=SEND Execution Count Over
04=RECEIVE Execution Count Over
05=System Data is not assigned
06=Time Over
07=Parity Error
08=Connection Error
09=Connection Port Capacity Over
0A=Detection of B-level Infinite Loop
0B~FF=Not Used
11
12
-When 01/02 is output at 
b0-b7: Cause of error (Hex)
-When 05 is output at 
b0-b7: 01=Data (Data Output via LAN) not assigned
02=Device No. not assigned
-When 07 is output at 
b0-b7: 00H=No Parity is set
01H=Odd Parity is set
02H=Even Parity is set
-When 08 is output at 
b0-b7: Cause of error (Hex)11
11
11
11
1324 
						

							NDA-24238 CHAPTER 3
Page 227
Revision 3.0
SYSTEM MESSAGES
[When =05 (OAI) / 07 (MIS) ]
➉ Faulty Logical Port No. (Hex)
 Error Kind (ERRK)
~ Not used b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
Table 3-3  Error Kind (ERRK)
Output Data Error Situation Required Check
01H SEND Execution Error
TCP/IP connection is down because the text is not transmit-
ted continuously.[1] Check the TCP/IP Transmission 
capacity on the UAP side is proper 
or not.
[2] Check the operation status on the UAP 
side is normal.
02H RECEIVE Execution Error
Incorrect text format is received.[1] Check the software operation on the 
MIS or Host side.
[2] Check the LAN cable connection 
status.
03H TCP/IP Connection Error
TCP/IP connection is released due to the TCP port discon-
nection order from the MIS or Host.Re-start the MIS or HOST computer.
04H Connection Error (B-level Infinite Loop, etc.) 
TCP port is released due to the detection of abnormal state in 
the MIS or HOST operation.Re-check the operation status of MIS or 
Host.
05H TCP/IP Port Capacity Over
TCP/IP connection cannot be established due to the connec-
tion port capacity over.The number of allowed ports for applica-
tion use via TCP/IP must be 16 or less. Ad-
just the used application number not to 
exceed “16” in total.
9
11b0-b7 : Error Kind (Hex)
Refer to Table 3-3:
1224 
						

							CHAPTER 3 NDA-24238
Page 228
Revision 3.0
SYSTEM MESSAGES
This message displays when the LAN Interface Connection Failure, detected in Message [26-V], recovers. The
message displays when the LAN Interface Connection Failure is restored. The first data is normally sent/re-
ceived by the recovered application equipment.
➀-➃ IP Address for external equipment in which error has been detected. (Hex.)
➄, ➅ Port No. (Client Port No.) (Hex.)
➆ Socket No. (Used Socket No.) (Hex.)
➇ Error Code (TCP/IP Error Code) (Hex.) See Ta b l e  3 - 2. TCP/IP Part Application Part
1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX
➀ ➁ ➂ ➃ ➄ ➅ ➆ ➇ ➈ ➉
4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000
7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
Default Alarm:
NON26-WLAN Interface Release ReportDefault Grade: Grade Modified: Lamp Modified:
1112131415161718192021222324 
						

							NDA-24238 CHAPTER 3
Page 229
Revision 3.0
SYSTEM MESSAGES
➈ Application Type
 
[When ➈
➈➈ ➈=03 (SMDR) / 04 (MCI) ]
➉ Device Number of recovered client PC
 Recovery Information
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b7 b6 b5 b4 b3 b2 b1 b0
b0-b7: (Hex)
01=SUPER SERVER
02=MAT
03=SMDR
04=MCI
05=OAI
06=PMS
07=MIS
b0-b7: (Hex)
Device Number of recovered Client PC 
for external LAN Interface.
b0-b7: (Hex)
01=Recovered
02~FF=Not defined
11 
						

							CHAPTER 3 NDA-24238
Page 230
Revision 3.0
SYSTEM MESSAGES
This message displays when the MUX (PH-PC36) card, whose clock function was detected as faulty, is recov-
ered.
➀ Unit, MG number for MUX card, 
which recovered from a clock 
failure
➁ RLS Data
1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000
➀ ➁
4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000
7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000
b7 b4 b3 b2 b1 b0
b7 b3 b2 b1 b0
Default Alarm:
NON33-AMUX Clock RestoreDefault Grade:
3Grade Modified: Lamp Modified:
b0-b1: Unit number for the recovered MUX card
b2: MG number for the recovered MUX card
b3: 0/1 = fault recovery in the MUX No. 0 system / fault recovery in 
MUX No. 1 system
b4: 0/1 = faulty MUX is in ACT/
Faulty MUX is in STBY
RLS Data:Clock alarm information on the recovered MUX card
b1: 0/1 = -/FH failure for 2M PCM Highway
b2: 0/1 = -/CLK failure for 2M PCM Highway
b3: 0/1 = -/4M CLK failure for PM 
						

							NDA-24238 CHAPTER 3
Page 231
Revision 3.0
SYSTEM MESSAGES
This message displays when an abnormal state is detected temporarily on the SDT (PA-SDTA/B) card.
➀ MG (Module Group)
➁ Details on alarm
Note:Alarm-detected HW is specified in ➂ (next page).
1: X0XX 00XX XXXX XX00 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000
➀ ➁ ➂
4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000
7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000
b7 b0
b7 b4 b3 b2 b1 b0
Default Alarm:
NON33-BSDT Alarm WarningDefault Grade:
2Grade Modified: Lamp Modified:
b7: 0/1 = Even-number MG/Odd-number MG
b4, b3 b2-b0
0 0 0 0 0
0 0 0 0 1 Hardware Failure
0 0 0 1 0 Optical Line Failure
0 0 0 1 1 Onboard Power Alarm
0 1 0 0 0
0 1 0 0 1 PCM Loss
0 1 0 1 0 Frame Alignment Loss
0 1 0 1 1 Receiving Section Failure
0 1 1 0 0 Mistake Rate Degradation
0 1 1 0 1 Sending Section Failure
0 1 1 1 0 Mistake Detection
1 0 0 0 0
1 0 0 0 1 Receiving Path Failure
1 0 0 1 0 Pointer Failure
1 0 0 1 1 Sending Path Failure
1 0 1 0 0 Receiving Path Error
1 0 1 0 1 Sending Path Error
b7: SDT Card Status
0/1=No. 0 System/No.1 System
SDT Card
Trouble
52M Interface
Alarm
VC-11 Path
Trouble
Note 
						

							CHAPTER 3 NDA-24238
Page 232
Revision 3.0
SYSTEM MESSAGES
➂ Alarm-detected HW
Note:This data displays only when b4 is “1” and b3 is “0” in data ➁.
Repair Procedure
Basically, fault repair work is not required by the display of this message. However, if the message is created
frequently, it is recommended that the repair work be performed as shown in the message [33-C] SDT Alarm
Trouble. b7 b6 b5 b4 b3 b2 b1 b0
The data here specifies the HW, on which any of the VC-11 Path 
Trouble was detected in data 
➁ (see Note). Refer to the table below:
b7 b6 b5 b4 b3 b2 b1 b0
- - - - 28 27 26 25
24 23 22 21 20 19 18 17
16 15 14 13 12 11 10 9
87654321
0/1=-/VC-11 Path Trouble 
						

							NDA-24238 CHAPTER 3
Page 233
Revision 3.0
SYSTEM MESSAGES
This message displays when a grave failure occurs on the SDT (PA-SDTA/B) card. If this is issued, remember
the ACT/STBY change of the SDT card may be followed, as a result of fault detection in the optical fiber line
(see [33-E] message).
➀ MG (Module Group)
➁ Details on alarm
Note:Fault repair procedure on each alarm is shown on the next page.
1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000
➀ ➁
4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000
7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000
b7 b0
b7 b4 b3 b2 b1 b0
Default Alarm:
MN33-CSDT Alarm TroubleDefault Grade:
3Grade Modified: Lamp Modified:
b7: 0/1 = Even-number MG/Odd-number MG
b4, b3 b2-b0
0 0 0 0 0
0 0 0 0 1 Hardware Failure
0 0 0 1 0 Optical Line Failure
0 0 0 1 1 Onboard Power Alarm
0 0 1 0 0 Abnormal MB Key Operation
0 1 0 0 0
0 1 0 0 1 PCM Loss
0 1 0 1 0 Frame Alignment Loss
0 1 0 1 1 Receiving Section Failure
0 1 1 0 0 Mistake Rate Degradation
0 1 1 0 1 Sending Section Failure
0 1 1 1 0 Mistake Detection
1 0 0 0 0
1 0 0 0 1 Receiving Path Failure
1 0 0 1 0 Pointer Failure
1 0 0 1 1 Sending Path Failure
1 0 1 0 0 Receiving Path Error
1 0 1 0 1 Sending Path Error
b7: SDT Card Status
0/1=No. 0 System/No.1 System
SDT Card
Trouble
52M Interface
Alarm
VC-11 Path
Trouble
Note