Chapter 108 SWAN (ServerNet Wide Area Network) Concentrator Messages

Table of Contents

pSOS Specific Traps
pNA Specific Traps
SMT Specific Traps
TFTP Specific Traps
Listener Specific Traps
SNMP Specific Traps
WANEXPLAPB Specific Traps
WANEXPLABX Specific Traps
WANSWIFT Specific Traps
WANGFDX Specific Traps
WANMPSB Specific Traps
WANBSCTR Specific Traps
WANBSCSP Specific Traps
WANENVBSC Specific Traps
WANENVASC Specific Traps
WANADCCP Specific Traps
WANSNAX Specific Traps

The SWAN concentrator generates TRAPMUX message 6 through the WAN subsystem trap multiplexer process. The subsystem ID displayed by this message includes TRAPMUX as the subsystem name.

A general explanation of the trap message is provided, followed by the specific details for each type of SWAN concentrator trap event message; they are organized as follows:

SWAN concentrator firmware generated traps:
SWAN concentrator data link control (DLC) task generated traps:

Enterprise Specific Trap SNMP-Trap-Multiplexer - trap-multiplexer-process-name, Version: version-number, Community: community-string, Enterprise:enterprise-identifier, Network addr: ip-address, Generic trap: 6, Specific trap: specific-trap-value, Time ticks: <9>, (varbind n OID=varbind-object-identifier, type=varbind-data-type, value=varbind-value)

trap-multiplexer-process-name

is the name of the Trap Multiplexer process that received the trap.

version-number

is the number in the version field of the trap PDU.

community-string

is the community name associated with the trap originator, from the community field of the trap PDU. For SWAN concentrator trap events, the value is Tandem_Computers_EMS.

enterprise-identifier

is the SWAN concentrator object identifier (OID), which is illustrated in Figure 108-1.

Figure 108-1 SWAN Concentrator Object Identifier (OID) Tree

ip-address

is the SWAN concentrator PATH IP address.

specific-trap-value

contains a decimal number that uniquely identifies the trap. These are the SWAN concentrator components that can generate a trap event:

“pSOS Specific Traps”: numbers 1 through 3874
“pNA Specific Traps”: numbers 20484 through 24334
“SMT Specific Traps”: numbers 1179649 through 1245195
“TFTP Specific Traps”: numbers 2228224 through 2228239
“Listener Specific Traps”: numbers 4194305 through 4194307
“SNMP Specific Traps”: number 450001
“WANEXPLAPB Specific Traps”: numbers 11665459 through 11731024
“WANEXPLABX Specific Traps”: numbers 12714035 through 12779600
“WANSWIFT Specific Traps”: numbers 13828096 through 13828143
“WANGFDX Specific Traps”: numbers 14811181 through 14876722
“WANMPSB Specific Traps”: numbers 15925248 through 15925294
“WANBSCTR Specific Traps”: numbers 16973824 through 16973873
“WANBSCSP Specific Traps”: numbers 18022400 through 18022448
“WANADCCP Specific Traps”: numbers 22020101 through 22216744
“WANSNAX Specific Traps”: numbers 23265281 through 23265292

time-stamp

is the elapsed time value of the time-stamp field of the trap PDU.

The remaining optional field in the trap message is the varbind field. If there is not information for this field, (no varbinds) is displayed. Otherwise, the following fields are displayed one or more times.

n

indicates the number of varbinds.

varbind-object-identifier

is the SWAN concentrator object identifier (OID) of the varbind, which is illustrated in Figure 108-1.

varbind-data-type

indicates the data type of the varbind and is one of the following:

Value	Meaning
NULL	no data
INTEGER	data is in integer notation
OCTETSTRING	data is in octal notation
OID	data is an object identifier (OID)
IPADDR	data is an IP address
COUNTER	data is a counter
GAUGE	data is a gauge
TIMETICKS	data is a timestamp
SMI-OPAQUE	data is opaque
DISPLAYSTRING	Is a text message providing additional information about the trap.

varbind-value

is the value of the varbind.

Figure 108-2 shows three fields in a sample trap message that identify the trap as a SWAN concentrator trap.

Figure 108-2 Sample SWAN Concentrator Trap Message

pSOS Specific Traps

Table 108-1 describes the traps issued by pSOS. The recovery action is described in Table 108-2

Table 108-1 pSOS Specific Traps

Specific Trap	Description	Recovery Action
1	Timed out; returned only if timeout was requested	1
2	Unimplemented system service	1
3	Illegal system service function number	1
4	Node specifier out of range	1
5	Object identifier (OID) is incorrect; failed validity check	1
6	Object identifier (OID) is incorrect; failed validity check	1
7	Incorrect object type	1
8	Node’s object table full	1
9	Named object not found	1
13	Informative; files may be corrupted on restart	2
14	Exceeds node’s maximum number of tasks	1
15	No stack space	1
16	Stack too small	1
17	Priority out of range	1
18	Task already started	1
19	Cannot restart; this task never was started	1
20	Task already suspended	1
21	The task was not suspended	1
22	Cannot change priority; new priority out of range	1
23	Register number out of range	1
24	pHILE+ resource in use	1
25	pREPC+ resource in use	1
26	pNA+ resource in use	1
27	Starting address not on long word boundary	1
28	Illegal unit_size - must be power of 2 and >= 16	1
29	Length too large (for given unit_size)	1
30	Cannot create; region length too small to hold RNB	1
31	Cannot delete; one or more segments still in use	1
32	Cannot getseg; request size of zero is illegal	1
33	Cannot getseg; request size is too big for region	1
34	No free segment; only if RN_NOWAIT attribute used	1
35	Segment does not belong to this region	1
36	Incorrect segment starting address	1
37	Segment is already unallocated	1
38	Cannot getseg; region deleted while waiting	1
40	Starting address not on long word boundary	1
41	Buffer size not power of 2, or less than 4 bytes	1
42	Length too small to hold PTCB	1
43	Cannot delete; one or more buffers still in use	1
44	Cannot allocate; partition out of free buffers	1
45	Incorrect buffer starting address	1
47	Buffer is already unallocated	1
48	Message length exceeds KI maximum packet buffer length	1
49	Message length exceeds maximum message	1
50	Buffer too small to receive message	1
51	Cannot create QCB exceeds node’s max num	1
52	Cannot allocate private buffers; too few available	1
53	Message queue at length limit	1
54	Queue deleted while task waiting	1
58	Queue is variable size	1
60	Queue is not variable size	1
60	Selected events not pending	1
62	Illegal, not called from an ASR	1
63	Task has no valid ASR	1
65	Exceeds node’s maximum number of semaphores	1
66	Not semaphore; this error code returns only if SM_NOWAIT was selected	1
67	Semaphore deleted while task waiting	1
71	System time and date not yet set	1
72	Date input out of range	1
73	Time of day input out of range	1
74	Ticks input out of range	1
75	Exceeds maximum number of configured timers	1
76	timid invalid	1
77	Timer not armed or already expired	1
78	Too late; date and time input already in the past	1
83	Object not created from this node	1
84	Cannot wait; the remote node is out of Agents	1
90	PADDR not page-aligned	1
91	LADDR not on section boundary	1
92	Logical address is not mapped	1
93	Cannot affect supervisor map	1
94	Copy length too long; past section end	1
95	Section is already mapped	1
96	No more unused section available	1
97	Cannot map to zero memory	1
98	Length greater than section	1
99	Illegal task mode switch	1
101	Object does not exist any more	1
102	Remote node no longer is service	1
103	Cannot terminate master node	1
257	Illegal device (major) number	1
258	No driver provided	1
259	Illegal I/O function number	1
1284	Interrupted system call	1
1285	I/O error	1
1286	No such address	1
1289	The socket descriptor is invalid	1
3840	Region 0 must be aligned on a long word boundary	1
3841	Region 0 overflow while making system data area	1
3842	Region 0 overflow while making object table	1
3843	Region 0 overflow while making device data area table	1
3844	Region 0 overflow while making task structures	1
3845	Region 0 overflow while making queue structures	1
3846	Region 0 overflow while making semaphore structures	1
3847	Region 0 overflow while making timer structures	1
3848	Region 0 overflow while making partition structures	1
3849	Region 0 overflow while making RSC structures	1
3850	Region 0 overflow while making region structures	1
3851	Region 0 overflow while making MMU structures	1
3852	Cannot create root task	1
3854	Checksum error	2
3855	Wrong processor type	1
3856	MMU already enabled with bad setting	1
3857	Region 0 unit size must match MMU	1
3858	Illegal packet type in the received packet	1
3859	Multiprocessor configuration mismatch at system verify	1
3860	Global object received cannot be entered in this code	1
3861	Node # = 0 in Multi-processor configuration table	1
3862	Total # of nodes = 0 or > 2 ** 14 in mpct	1
3863	Region 0 overflow while making roster and seq.# tables	1
3864	KI_MAXBUF entry is smaller than required	1
3865	Asynchronous call error - no user call out	1
3867	Error while initializing a device	1
3872	Slave node joined too soon!	1
3874	Join request was sent to slave node	1

Table 108-2 pSOS Recovery Actions

#	Severity	Description
1	Minor	This is a SWAN kernel problem.If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable. If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), be prepared to supply your system number and the numbers and versions of products related to the error.
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.

pNA Specific Traps

Table 108-3 describes the traps issued by pNA. The recovery action is described in Table 108-4

Table 108-3 pNA Specific Traps

Specific Trap	Description	Recovery Action
20484	Interrupted system call	1
20485	I/O error	1
20486	No such address	1
20489	The socket descriptor is invalid	1
20492	Not enough memory	1
20493	Permission denied	1
20497	Entry exists	1
20502	An argument is invalid	1
20503	An internal table has run out of space	1
20512	The connection is broken	3
20515	This operation would block and the socket is non-blocking	1
20516	The socket is non-blocking and the connection cannot be complete	1
20517	The socket is non-blocking and a previous connection attempt has not yet been complete	1
20518	Socket operation on a socket	1
20519	The destination address is invalid	1
20520	Message too long	1
20521	Protocol wrong type for socket	1
20522	Protocol not available for socket	1
20523	Protocol not supported	1
20524	Socket type not supported	1
20525	Operation not supported on socket	1
20526	Protocol family not supported	1
20527	Address family not supported	1
20528	Address is already in use	1
20529	Address not available	1
20530	Network is down	3
20531	Network is unreachable	3
20532	Network dropped on reset	3
20533	The connection has been aborted by the peer	4
20534	The connection has been reset by the peer	4
20535	An internal buffer is required, but cannot be allocated	1
20536	The socket is already connected	1
20537	The socket is not connected	1
20538	Can’t sent after socket shutdown	1
20539	Too many references: can’t splice	1
20540	Connection timed out	4
20541	The attempt to connect was refused	4
20544	Host is down	4
20545	The destination node could not be reached from this node	1
20546	Directory not empty	1
20550	NT_INIT returned -1	1
20551	The MTU is invalid	1
20552	The hardware length is invalid	1
20553	The specified route cannot be found	1
20554	Collision is select call; these conditions have already been selected by another task	1
20555	The task id is invalid	1
24321	Insufficient memory allocated by NC_DATASIZE or region 0 too small	1
24322	The number of initial routing table entries specified exceeds NC	1
24323	The number of initial NI table entries specified exceeds NC_NNI	1
24324	Invalid NI address	1
24325	Invalid MTU for NI	1
24326	pNA+ memory error	2
24327	PNAD task creation error	1
24328	pNA+ initialization error	1
24329	NI initialization error	1
24330	Routing table initialization error	1
24331	ARP table initialization error	1
24332	PNAD timer initialization error	1
24333	PNAD event error	1
24334	pNA+ checksum error	2

Table 108-4 pNA Recovery Actions

#	Severity	Description
1	Minor	This is a SWAN kernel problem.If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), be prepared to supply your system number and the numbers and versions of products related to the error.
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
3	Critical	Cause: This event can be a result of the following causes: The Ethernet cables on the SWAN concentrator are reversed. Both PATHs to the SWAN concentrator are connected to the same Ethernet segment. In this case, a different WANBoot process issues the ZWAN-EVT-BOOTP-REQUIN-OK event. Effect: If the SWAN concentrator Ethernet cables are reversed, the SWAN concentrator is unusable. If the SWAN concentrator Ethernet ports are connected to the same Ethernet segment, the SWAN concentrator is still usable, but performance may be degraded, and a problem with the one Ethernet segment can cause both paths to the SWAN concentrator to be unusable.Recovery: If the SWAN concentrator Ethernet ports are connected to the same Ethernet segment, reverse the cables. If the SWAN concentrator Ethernet ports are connected to the same Ethernet segment, connected them to different Ethernet segments.
4	Critical	Determine if the corresponding IOP is running in the system processors.

SMT Specific Traps

Table 108-5 describes the traps issued by SMT. The recovery action is described in Table 108-5 and in Table 108-7

Table 108-5 SMT Specific Traps

Specific Trap	Description	SMT Action	Recovery Action
1179649	The “activate path” (down load) request from the IOP preempts the previous one (that is now in-process) from this IOP	Discard the previous “active path” request (the clip code file eventually will be downloaded) and process the current one instead	0
1179650	The indicated DLC task is stopped. This may be caused by user’s request to abort the DLC task, or as a result of error encountered by the DLC reported in some previous trap	None	0
1179652	The indicated DLC task is started	None	0
1179653	The clip code with the indicated file name is deleted from flash or the clip code of the indicated active DLC task is deleted from the flash	None	0
1179654	Unable to get memory space to process the current request	None	Retry the request later by using SCF command. If problem persists, take action #1
1179656	The clip code with the indicated file name is not found in flash	None	Re-enter the “delete task code” request with the correct file name. If problem persists, take action #1
1179657	Unable to copy the clip code of the indicated DLC task to flash because of space problem	None	Remove unused clip code saved in flash to free up the space. This is automated within the CLIP.
1179658	The indicated DLC task is configured (its CLIP code has been added to the FLASH memory) but is not started	None	0
1179661	SWAN kernel hardware related message	SWAN kernel continues to run	1) Look at the error text in the trap message, if it is a hardware related error (for example, FAN BAD or -5 volt supply is bad), take action #5; if it is not a hardware related error, take action #12) If POST is executed and detected an error, it will display the POST results.3) If POST is not executed, the following message is displayed:“ERROR: POST WAS NOT RUN“The SWAN concentrator kernel will automatically initiate the FIRMUP process, which updates the essential and non-essential FLASH memory.If the FIRMUP process is successful, no further recovery action should be necessary.If the FIRMUP process fails, replace the SWAN concentrator.
1179660	Warning message; SWAN kernel coding bug	SNMP trap message is sent to the TRAPMUX	This may be a transient error, if it happens very often, take action #1
1179662	SWAN kernel warning message/informational message	SWAN kernel continues to run	0
1245195	Indicates fatal errors issued by SMT or DUMP task and by error exception handler or Watchdog Timer handler.	SWAN kernel takes a dump of CLIP memory and resets itself	1

Example 108-1 Example of Specific Trap 1245195 for POST FIR Block Error

TANDEM.TRAPMUX.D20    000006 Enterprise
Specific Trap - SNMP-Trap-Multiplexer
$ZTMX, Version: 0, Community:
Tandem_Computers_EMS, Enterprise:
1.3.6.1.4.1.169.7.1, Network addr:
172.16.35.34, Generic trap: 6, Specific
trap: 1245195, Time ticks: 0, (varbind 1
OID=1.3.6.1.4.1.169.7.1.7,
type=OCTET-STRING,
value=TRACK SWAN28 CLIP 2 TASK SMT  POST
RESULTS : SYS FLG VER 5c00,
POST BITS VER 0053, SYSTEM FLGS
00000000, POST RUN BITS 4400000e00000000
                           POST FAIL_BITS
4400001c00000000)

Example 108-2 Example of Specific Trap 1245195 for SMT FIR Block Error

TANDEM.TRAPMUX.D20    000006 Enterprise
Specific Trap - SNMP-Trap-Multiplexer
$ZTMX, Version: 0, Community:
Tandem_Computers_EMS, Enterprise:
1.3.6.1.4.1.169.7.1, Network addr:
172.16.35.34, Generic trap: 6, Specific
trap: 1245195, Time ticks: 0, (varbind 1
OID=1.3.6.1.4.1.169.7.1.7,
type=OCTET-STRING,
value=TRACK SWAN28 CLIP 2 TASK SMT  FIR
Error REC (1) =  DATA TYPE 7 DATA LEN 6
TOKEN ID 3ED ERR_SOURCE pSOS SOURCE_LOC
STEP_21 ERROR 0)

Table 108-6 SMT Specific Trap 1245195 Description

SOURCE_LOC	ERR_ SOURCE	Error Description	Recovery Action
1	pNA+	ioctl call on PNA socket has failed in bootpc procedure.Operation attempted: SIOCGIFADDR	1
2	pNA+	ioctl call on PNA socket has failed in bootpc procedure.Operation attempted: SIOCSIFADDR	1
3	pSOS	q_send on SMT_BOOTPC0_EVENTQ has failed in bootpc procedure.	1
4	pSOS	ev_send to SMT TASK has failed in bootpc procedure.	1
5	pSOS	Couldn't create BOOTPC0_IN_Q in bootpc_start procedure.Operation attempted: q_create	1
6	pSOS	Couldn't create BOOTPC0_FREE_Q in bootpc_start procedure.Operation attempted: q_create	1
7	pSOS	Couldn't create BOOTPC1_IN_Q in bootpc_start procedure.Operation attempted: q_create	1
8	pSOS	Couldn't create BOOTPC1_FREE_Q in bootpc_start procedure.Operation attempted: q_create	1
9	pSOS	Couldn't allocate memory for boopc segment address from RN #0 in bootpc_start procedure.Operation attempted: rn_getseg	1
10	pSOS	Couldn't send message to bpc_free_qid in bootpc_start procedure.Operation attempted: q_send	1
11	SMT	SMT internal error in initializing LANPORT_A in bootpc_start procedure.Operation attempted: add_niNote: PC_COUNTER is stored.	1
12	SMT	SMT internal error in initializing LANPORT_B in bootpc_start procedure.Operation attempted: add_niNote: PC_COUNTER is stored.	1
13	pSOS	Couldn't create task name BOOTPC0_NAME in bootpc_start procedure.Operation attempted: t_create	1
14	pSOS	Couldn't start task name BOOTPC0_NAME in bootpc_start procedure.Operation attempted: t_start	1
15	pSOS	Couldn't create task name BOOTPC1_NAME in bootpc_start procedure.Operation attempted: t_create	1
16	pSOS	Couldn't start task name BOOTPC1_NAME in bootpc_start procedure.Operation attempted: t_start	1
17	pSOS	Couldn't send message to bpc_free_qid in bootpc_server procedure.Operation attempted: q_send	1
18	pSOS	Couldn't create task name SNMP_NAME in bootpc_server procedure.Operation attempted: t_create	1
19	pSOS	Couldn't start task name SNMP_NAME in bootpc_server procedure.Operation attempted: t_start	1
20	pSOS	Couldn't deallocate memory in proc_snmp_dnld_reply procedure.Operation attempted: rn_retseg	1
21	pSOS	Couldn't create SMT input MsgQ for BOOTPD in swanmgr_start procedure.Operation attempted: q_create	1
22	pSOS	Couldn't create SMT input MsgQ for SNMP Agent in swanmgr_start procedure.Operation attempted: q_create	1
23	pSOS	Couldn't create SMT input MsgQ for TFTP client in swanmgr_start procedure.Operation attempted: q_create	1
24	pSOS	Couldn't create SMT input MsgQ for BOOTPC0 in swanmgr_start procedure.Operation attempted: q_create	1
25	pSOS	Couldn't create SMT input MsgQ for BOOTPC1 in swanmgr_start procedure.Operation attempted: q_create	1
26	pSOS	Couldn't create SMT input MsgQ for DIAG task in swanmgr_start procedure.Operation attempted: q_create	1
27	pSOS	Couldn't create SMT input MsgQ for DLC task in swanmgr_start procedure.Operation attempted: q_create	1
28	pSOS	Couldn't create or start TIMER task and queue in swanmgr_start procedure.Operation attempted: q_create, t_create, t_start	1
29	pSOS	Couldn't create or start SMT task in swanmgr_start procedure.Operation attempted: t_create, t_start	1
30	pSOS	Operation could not be completed since SMT (Dump thread) detected a problem. The error that follows is defined by SMT.	1
31	pNA+	Operation related to dump thread is uncompleted since the call to pSOS or pNA+ failed. The error that follows should be decoded with respect to pSOS or pNA+.	1

Table 108-7 SMT Recovery Actions

#	Severity	Description
0	None	Informational only. No recovery is required.
1	Minor	This is a SWAN kernel problem.If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), be prepared to supply your system number and the numbers and versions of products related to the error.
5	Major	Hardware error. Replace the SWAN concentrator.

TFTP Specific Traps

Table 108-8 describes the traps issued by TFTP. The recovery action is described in Table 108-8 and in Table 108-9.

Table 108-8 TFTP Specific Traps

Specific Trap	Description	SMT Action	Recovery Action
2228224	Error message; Invalid Error no	SNMP trap message is sent to the TRAPMUX	1
2228225	Error message; Server: Bad file	SNMP trap message is sent to the TRAPMUX	The TFTP Server in the host has returned an error that the program file to be downloaded is not found. Check that the program file exists. If the problem persists, take action #1.
2228226	Error message; Server: Access Err	SNMP trap message is sent to the TRAPMUX	The TFTP server in the host has returned an access violation error . The TFTP process is not configured with the subvolume where the downloadable file exists. Correct the problem, then retry the action. If the problem persists take action #1.
2228227	Error message; Server: No Space	SNMP trap message is sent to the TRAPMUX	The TFTP server in the host has returned a "No space or full disk error." Restart the TFTP process, then try the operation, if the problem persists, take action #1.
2228228	Error message; Server: Bad TFTP	SNMP trap message is sent to the TRAPMUX	1
2228229	Error message; Server: Bad TX Id	SNMP trap message is sent to the TRAPMUX	1
2228230	Error message; Server: File already Exists	SNMP trap message is sent to the TRAPMUX	1
2228231	Error message; Server: No User	SNMP trap message is sent to the TRAPMUX	1
2228232	Error message; Client: Bad TFTP operation	SNMP trap message is sent to the TRAPMUX	2
2228233	Error message; Client sendto Fail	SNMP trap message is sent to the TRAPMUX	2
2228234	Error message; No Response from TFTP Server	SNMP trap message is sent to the TRAPMUX	Check if the TFTP Server is up. If it is not up then bring it up. If the problem still exists take action #1.
2228235	Error message; Client: Unknown pkt	SNMP trap message is sent to the TRAPMUX	2
22282236	Error message; Client: Out of Seq	SNMP trap message is sent to the TRAPMUX	2
2228237	Error message; Client: Big Packet	SNMP trap message is sent to the TRAPMUX	Determine if the corresponding DLC Microcode file Cxxxxp0x id correct, or if there is more than one TFTP server on the processor. Correct these problems and try again. If the problem persists take action #2.
22282238	Error message; Client: No Socket	SNMP trap message is sent to the TRAPMUX	2
2228239	Error message; Client: No Input	SNMP trap message is sent to the TRAPMUX	2

Table 108-9 TFTP Recovery Actions

#	Severity	Description
1	Minor	This is a TFTP server problem.If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), be prepared to supply your system number and the numbers and versions of products related to the error.
2	Minor	This is a SWAN kernel problem.If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), be prepared to supply your system number and the numbers and versions of products related to the error.
3	Critical	Cause: This event can be a result of the following causes: The Ethernet cables on the SWAN concentrator are reversed. Both PATHs to the SWAN concentrator are connected to the same Ethernet segment. In this case, a different WANBoot process issues the ZWAN-EVT-BOOTP-REQUIN-OK event. Effect: If the SWAN concentrator Ethernet cables are reversed, the SWAN concentrator is unusable. If the SWAN concentrator Ethernet ports are connected to the same Ethernet segment, the SWAN concentrator is still usable, but performance may be degraded, and a problem with the one Ethernet segment can cause both paths to the SWAN concentrator to be unusable.Recovery: If the SWAN concentrator Ethernet ports are connected to the same Ethernet segment, reverse the cables. If the SWAN concentrator Ethernet ports are connected to the same Ethernet segment, connected them to different Ethernet segments.

Listener Specific Traps

Table 108-10 describes the traps issued by Listener. The recovery action is described in Table 108-11

Table 108-10 Listener Specific Traps

Specific Trap	Description	SMT Action	Recovery Action
4194305	Warning message; no socket available	SNMP trap message is sent to the TRAPMUX	1
4194306	Warning message; cannot sent socket option	SNMP trap message is sent to the TRAPMUX	1
4194307	Warning message; unable to listen on socket	SNMP trap message is sent to the TRAPMUX	1

Table 108-11 Listener Recovery Actions

#	Severity	Recovery Action
1	Minor	This is a SWAN kernel problem.If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable. If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), be prepared to supply your system number and the numbers and versions of products related to the error.

SNMP Specific Traps

Table 108-12 describes the traps issued by SNMP. The recovery action is described in Table 108-13

Table 108-12 SNMP Specific Traps

Specific Trap	Description	SMT Action	Recovery Action
450001	Warning message; internal error	SNMP trap message is sent to the TRAPMUX	1

Table 108-13 SNMP Recovery Actions

#	Severity	Recovery Action
1	Minor	This is a SWAN kernel problem.If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable. If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), be prepared to supply your system number and the numbers and versions of products related to the error.

WANEXPLAPB Specific Traps

Table 108-14 describes the traps issued by WANEXPLAPB. The recovery action is described in Table 108-15

Table 108-14 WANEXPLAPB Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
11665459	FAILURE_FETCH_STATS_SIG	Cannot get signal status from bit driver	5
11665476	FAILURE_CONFIG_ERROR	Bad configuration record used for open command	8
11665485	FAILURE_SEND_RESPONSE_ CLB	Unable to send CLB (CAP/CLIP) frame	6
11730944	INIT_BEGINNING	DLC task initialization levels and trap failure codes for initialization	2
11730945	PNA_Q_CREATE_LEVEL	DLC task initialization levels and trap failure codes for initialization	2
11730946	DRIVER_INSTALLED_LEVEL	DLC task initialization levels and trap failure codes for initialization	2
11730947	CAP_CLIP_INIT_LEVEL	DLC task initialization levels and trap failure codes for initialization; cannot initialize CAP/CLIP interface	2
11730948	ALLOCATE_DCB_LEVEL	DLC task initialization levels and trap failure codes for initialization; pSOS failure; out of memory	2
11730949	INIT_PORT_LEVEL	DLC task initialization levels and trap failure codes for initialization, cannot initialize I/O port	2
11730950	RUNNING_LEVEL	DLC task initialization levels and trap failure codes for initialization	6
11730976	FAILURE_GETSEG	Critical failure; pSOS cannot obtain a memory segment	6
11730977	FAILURE_RETSEG	pSOS failure; cannot return memory segment	6
11730978	FAILURE_FRAMELIST	Memory error; linked list of frames corrupt	7
11730979	FAILURE_SENDSTATE	CAP/CLIP window state is bad	7
11730980	FAILURE_PRI_BAD_STATE	LAPB primary state machine encounter a bad state	7
11730981	FAILURE_PRI_BAD_EVENT	LAPB primary state machine encounter a bad event	7
11730982	FAILURE_SEC_BAD_STATE	LAPB secondary state machine encounter a bad state	7
11730983	FAILURE_SEC_BAD_EVENT	LAPB secondary state machine encounter a bad event	7
11730984	FAILURE_LOST_SOCKET	This might be caused by the operating system closing the socket connection	7
11730985	FAILURE_Q_CREATE	pSOS failure; cannot create pSOS queue	6
11730986	FAILURE_Q_SEND	pSOS failure; cannot send message to pSOS queue	6
11730987	FAILURE_EVENT_SEND	pSOS failure; cannot send event message	6
11730994	FAILURE_FETCH_CONFIG	pSOS failure; cannot return memory segment	6
11730996	FAILURE_FETCH_STATS	pSOS failure; cannot return memory segment	6
11730997	FAILURE_SENDTEXT	pSOS failure; cannot return memory segment	6
11730998	FAILURE_SENDTEXT2	pSOS failure; cannot return memory segment	6
11730999	FAILURE_RELAY_ON	Unable to turn relay on	6
11731000	FAILURE_RELAY_OFF	Unable to turn relay off	6
11731001	FAILURE_GET_BAUD_RATE	pSOS failure; cannot return memory segment	6
11731002	FAILURE_RESPOND_ERROR	pSOS failure; cannot return memory segment	6
11731003	FAILURE_COMMAND_ RESPONSE	pSOS failure; cannot return memory segment	6
11731004	FAILURE_COMPLETE_REQ	pSOS failure; cannot return memory segment	6
11731005	FAILURE_COMPLETE_REQ1	pSOS failure; cannot return memory segment	6
11731006	FAILURE_FRAME_WRITE	Bit driver failed to write frame to I/O port	2
11731007	FAILURE_FRAME_READ	Bit driver failed to read frame from I/O port	2
11731008	FAILURE_REQUEUE_FRAME_CNTRL	Bit driver failed to requeue frame on I/O port	2
11731009	FAILURE_REQUEUE_FRAME_READ	Bit driver failed to requeue frame on I/O port	2
11731010	FAILURE_OPEN_LINE	Unable to open I/O port	2
11731013	FAILURE_START_GETSEG	pSOS failure; cannot get memory segment	6
11731014	FAILURE_START_RCV_BUF	Cannot initialize memory buffer	6
11731015	FAILURE_STOP_CLEAR_BUF	Cannot clear memory buffer	6
11731016	FAILURE_STOP_RCVD	Unable to stop I/O port	5
11731017	FAILURE_STOP_DEQUEUE	pSOS failure; cannot return memory segment	6
11731018	FAILURE_STOP_CLOSE	Unable to close I/O port	5
11731019	FAILURE_SEND_RLS	pSOS failure; cannot return memory segment	6
11731020	FAILURE_SEND_RESP_GET_ MEM	pSOS failure; cannot get memory segment	6
11731022	FAILURE_PUT_RES_Q_SEND	pSOS failure; cannot send message to pSOS queue	2
11731023	FAILURE_PUT_RES_EV_SEND	pSOS failure; cannot send event message	2
11731024	FAILURE_ADD_Q	pSOS failure; cannot get memory segment	6

Table 108-15 WANEXPLAPB Recovery Actions

#	Severity	Recovery Action
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
5	Major	Hardware error. Replace the SWAN concentrator.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	Expand DLC protocol error. The DLC task should kill itself then come back online.
8	Major	Check the line parameters of the corresponding Expand line-handler process (IOP).

WANEXPLABX Specific Traps

Table 108-16 describes the traps issued by WANEXPLAPBX. The recovery action is described in Table 108-17

Table 108-16 WANEXPLAPBX Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
12714035	FAILURE_FETCH_STATS_SIG	Cannot get signal status from bit driver	5
12714052	FAILURE_CONFIG_ERROR	Bad configuration record used for open command	8
12714061	FAILURE_SEND_RESPONSE_ CLB	Unable to send CLB (CAP/CLIP) frame	6
12779520	INIT_BEGINNING	DLC task initialization levels and trap failure codes for initialization	2
12779521	PNA_Q_CREATE_LEVEL	DLC task initialization levels and trap failure codes for initialization	2
12779522	DRIVER_INSTALLED_LEVEL	DLC task initialization levels and trap failure codes for initialization	2
12779523	CAP_CLIP_INIT_LEVEL	DLC task initialization levels and trap failure codes for initialization, cannot initialize CAP/CLIP interface	2
12779524	ALLOCATE_DCB_LEVEL	DLC task initialization levels and trap failure codes for initialization, pSOS failure; out of memory	2
12779525	INIT_PORT_LEVEL	DLC task initialization levels and trap failure codes for initialization, cannot initialize I/O port	2
12779526	RUNNING_LEVEL	DLC task initialization levels and trap failure codes for initialization	6
12779552	FAILURE_GETSEG	Critical failure; pSOS cannot obtain a memory segment	6
12779553	FAILURE_RETSEG	pSOS failure; cannot return memory segment	6
12779554	FAILURE_FRAMELIST	Memory error, linked list of frames corrupt	7
12779555	FAILURE_SENDSTATE	CAP/CLIP window state is bad	7
12779556	FAILURE_PRI_BAD_STATE	LAPB primary state machine encounter a bad state	7
12779557	FAILURE_PRI_BAD_EVENT	LAPB primary state machine encounter a bad event	7
12779558	FAILURE_SEC_BAD_STATE	LAPB secondary state machine encounter a bad state	7
12779559	FAILURE_SEC_BAD_EVENT	LAPB secondary state machine encounter a bad event	7
12779560	FAILURE_LOST_SOCKET	This might be caused by the operating system closing the socket connection	7
12779561	FAILURE_Q_CREATE	pSOS failure; cannot create pSOS queue	6
12779562	FAILURE_Q_SEND	pSOS failure; cannot send message to pSOS queue	6
12779563	FAILURE_EVENT_SEND	pSOS failure; cannot send event message	6
12779570	FAILURE_FETCH_CONFIG	pSOS failure; cannot return memory segment	6
12779572	FAILURE_FETCH_STATS	pSOS failure; cannot return memory segment	6
12779573	FAILURE_SENDTEXT	pSOS failure; cannot return memory segment	6
12779574	FAILURE_SENDTEXT2	pSOS failure; cannot return memory segment	6
12779575	FAILURE_RELAY_ON	Unable to turn relay on	6
12779576	FAILURE_RELAY_OFF	Unable to turn relay off	6
12779577	FAILURE_GET_BAUD_RATE	pSOS failure; cannot return memory segment	6
12779578	FAILURE_RESPOND_ERROR	pSOS failure; cannot return memory segment	6
12779579	FAILURE_COMMAND_ RESPONSE	pSOS failure; cannot return memory segment	6
12779580	FAILURE_COMPLETE_REQ	pSOS failure; cannot return memory segment	6
12779581	FAILURE_COMPLETE_REQ1	pSOS failure; cannot return memory segment	6
12779582	FAILURE_FRAME_WRITE	Bit driver failed to write frame to I/O port	2
12779583	FAILURE_FRAME_READ	Bit driver failed to read frame from I/O port	2
12779584	FAILURE_REQUEUE_FRAME_CNTRL	Bit driver failed to requeue frame on I/O port	2
12779585	FAILURE_REQUEUE_FRAME_READ	Bit driver failed to requeue frame on I/O port	2
12779586	FAILURE_OPEN_LINE	Unable to open I/O port	2
12779589	FAILURE_START_GETSEG	pSOS failure; cannot get memory segment	6
12779590	FAILURE_START_RCV_BUF	Cannot initialize memory buffer	6
12779591	FAILURE_STOP_CLEAR_BUF	Cannot clear memory buffer	6
12779592	FAILURE_STOP_RCVD	Unable to stop I/O port	5
12779593	FAILURE_STOP_DEQUEUE	pSOS failure; cannot return memory segment	6
12779594	FAILURE_STOP_CLOSE	Unable to close I/O port	5
12779595	FAILURE_SEND_RLS	pSOS failure; cannot return memory segment	6
12779596	FAILURE_SEND_RESP_GET_ MEM	pSOS failure; cannot get memory segment	6
12779598	FAILURE_PUT_RES_Q_SEND	pSOS failure; cannot send message to pSOS queue	2
12779599	FAILURE_PUT_RES_EV_SEND	pSOS failure; cannot send event message	2
12779600	FAILURE_ADD_Q	pSOS failure; cannot get memory segment	6

Table 108-17 WANEXPLAPBX Recovery Actions

#	Severity	Recovery Action
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
5	Major	Hardware error. Replace the SWAN concentrator.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	Expand DLC protocol error. The DLC task should kill itself then come back online.
8	Major	Check the line parameters of the corresponding Expand line-handler process (IOP).

WANSWIFT Specific Traps

Table 108-18 describes the traps issued by WANSWIFT. The recovery action is described in Table 108-19.

Table 108-18 WANSWIFT Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
13828096	INIT_Q_CREATE	Task initialization error, cannot create a message queue to communicate with SMT	2
13828097	INIT_IDENT	Task initialization error, pSOS failure; cannot obtain the task identifier	2
13828098	INIT_CAP_CLIP	Task initialization error, cannot initialize CAP/CLIP interface	2
13828099	INIT_ALLOC_MEM	Task initialization error; pSOS failure; unable to allocate memory for control blocks	2
13828100	INIT_DRIVER_INIT	Task initialization error; pSOS failure; unable to initialize the driver	2
13828128	FAILURE_GETSEG	pSOS failure; cannot get memory segment for read buffer	6
13828129	FAILURE_RETSEG	pSOS failure; cannot return memory segment for read buffer	6
13828130	FAILURE_OPEN_PORT	pSOS failure; cannot open the I/O port	2
13828131	FAILURE_CLOSE_PORT	pSOS failure; cannot close the I/O port	2
13828132	FAILURE_RCV_CLB	Unable to receive CLB (CAP/CLIP) frame	6
13828133	FAILURE_SEND_CLB	Unable to send a CLB (CAP/CLIP) frame	6
13828134	FAILURE_FLUSH_EV_SEND	pSOS failure; cannot send a FLUSH event message	2
13828135	FAILURE_EV_SEND	pSOS failure; cannot send a FLUSH event message	2
13828136	FAILURE_TM_CANCEL	pSOS failure; cannot stop timer	6
13828137	FAILURE_TM_EVAFTER	pSOS failure; cannot start timer	6
13828138	FAILURE_SM2_BAD_STATE	SWIFT level 2 state machine encountered a bad state	7
13828139	FAILURE_SM2_BAD_EVENT	SWIFT level 2 state machine encountered a bad event	7
13828140	FAILURE_SM3_BAD_STATE	SWIFT level 3 state machine encountered a bad state	7
13828141	FAILURE_SM3_BAD_EVENT	SWIFT level 3 state machine encountered a bad event	7
13828142	FAILURE_INVALID_FRAME	SWIFT invalid frame pointer	7
13828143	FAILURE_DRIVER	pSOS failure; de read or write failed	6

Table 108-19 WANSWIFT Recovery Actions

#	Severity	Recovery Action
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	Expand DLC protocol error. The DLC task should kill itself then come back online.

WANGFDX Specific Traps

Table 108-20 describes the traps issued by WANGFDX. The recovery action is described in Table 108-21

Table 108-20 WANGFDX Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
14811181	FAILURE_FLUSH_EV_SEND	pSOS failure; cannot send a FLUSH event message	2
14811187	FAILURE_M2_BAD_EVENT	GFDX modem level 2 state machine encountered a bad event	7
14876672	INIT_Q_CREATE	Task initialization error; cannot create a message queue to communicate with SMT	2
14876673	INIT_IDENT	Task initialization error; pSOS failure; cannot obtain the task identifier	2
14876674	INIT_CAP_CLIP	Task initialization error; cannot initialize CAP/CLIP interface	2
14876675	INIT_REQUEST	Task initialization error; pSOS failure; unable to allocate memory for request message	2
14876676	INIT_DCB	Task initialization error; pSOS failure; unable to allocate memory for device control block	2
14876677	INIT_TRACE_CB	Task initialization error; pSOS failure; unable to allocate memory for trace control block	2
14876678	INIT_CONFIG_CB	Task initialization error; pSOS failure; unable to allocate memory for configuration control block	2
14876679	INIT_CCB	Task initialization error; pSOS failure; unable to allocate memory for channel control block	2
14876680	INIT_STAT_CB	Task initialization error; pSOS failure; unable to allocate memory for statistics control block	2
14876681	INIT_DRIVER_INIT	Task initialization error; pSOS failure; unable to initialize the driver	2
14876704	FAILURE_READ_GETSEG	pSOS failure; cannot get memory segment for read buffer	6
14876705	FAILURE_READ_RETSEG	pSOS failure; cannot return memory segment for read buffer	6
14876706	FAILURE_WRITE_GETSEG	pSOS failure; cannot get memory segment for write buffer	6
14876707	FAILURE_WRITE_RETSEG	pSOS failure; cannot return memory segment for write buffer	6
14876708	FAILURE_OPEN_PORT	pSOS failure; cannot open the I/O port	2
14876709	FAILURE_CLOSE_PORT	pSOS failure; cannot close the I/O port	2
14876710	FAILURE_RCV_CLB	Unable to receive CLB (CAP/CLIP) frame	6
14876711	FAILURE_SEND_CLB	Unable to send a CLB (CAP/CLIP) frame	6
14876712	FAILURE_MCB	pSOS failure; unable to allocate memory for the message control block	2
14876713	FAILURE_MCB_AVAIL	Maximum number of message control blocks reached; unable to process CLB messages	2
14876714	FAILURE_BLOCK_DATA	pSOS failure; unable to allocate memory for blocked data	2
14876715	FAILURE_RESPONSE	pSOS failure; unable to allocate memory for response message	2
14876716	FAILURE_FREE_BLOCK	pSOS failure; unable to allocate memory for special control block	2
14876718	FAILURE_SM2_BAD_STATE	GFDX level 2 state machine encountered a bad state	7
14876719	FAILURE_SM2_BAD_EVENT	GFDX level 2 state machine encountered a bad event	7
14876720	FAILURE_SM3_BAD_STATE	GFDX level 3 state machine encountered a bad state	7
14876721	FAILURE_SM3_BAD_EVENT	GFDX level 3 state machine encountered a bad event	7
14876722	FAILURE_M2_BAD_STATE	GFDX modem level 2state machine encountered a bad state	7

Table 108-21 WANGFDX Recovery Actions

#	Severity	Recovery Action
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	Expand DLC protocol error. The DLC task should kill itself then come back online.

WANMPSB Specific Traps

Table 108-22 describes the traps issued by WANMPSB. The recovery action is described in Table 108-23

Table 108-22 WANMPSB Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
15925248	INIT_Q_CREATE	Task initialization error; cannot create a message queue to communicate with SMT	2
15925249	INIT_IDENT	Task initialization error; pSOS failure; cannot obtain the task identifier	2
15925250	INIT_CAP_CLIP	Task initialization error; cannot initialize CAP/CLIP interface	2
15925251	INIT_ALLOC_MEM	Task initialization error; pSOS failure; unable to allocate memory for control blocks	2
15925252	INIT_DRIVER_INIT	Task initialization error; pSOS failure; unable to initialize the driver	2
15925280	FAILURE_GETSEG	pSOS failure; cannot get memory segment for read buffer	6
15925281	FAILURE_RETSEG	pSOS failure; cannot return memory segment for read buffer	6
15925282	FAILURE_OPEN_PORT	pSOS failure; cannot open the I/O port	2
15925283	FAILURE_CLOSE_PORT	pSOS failure; cannot close the I/O port	2
15925284	FAILURE_RCV_CLB	Unable to receive CLB (CAP/CLIP) frame	6
15925285	FAILURE_SEND_CLB	Unable to send a CLB (CAP/CLIP) frame	6
15925286	FAILURE_FLUSH_EV_SEND	pSOS failure; cannot send a FLUSH event message	2
15925287	FAILURE_EV_SEND	pSOS failure; cannot send a FLUSH event message	2
15925288	FAILURE_TM_CANCEL	pSOS failure; cannot stop timer	6
15925289	FAILURE_TM_EVAFTER	pSOS failure; cannot start timer	6
15925290	FAILURE_SM2_BAD_STATE	MPSB level 2 state machine encountered a bad state	7
15925291	FAILURE_SM2_BAD_EVENT	MPSB level 2 state machine encountered a bad event	7
15925292	FAILURE_SM3_BAD_STATE	MPSB level 3 state machine encountered a bad state	7
15925293	FAILURE_SM3_BAD_EVENT	MPSB level 3 state machine encountered a bad event	7
15925294	FAILURE_DRIVER	pSOS failure; de read or write failed	6

Table 108-23 WANMPSB Recovery Actions

#	Severity	Recovery Action
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	Expand DLC protocol error. The DLC task should kill itself then come back online.

WANBSCTR Specific Traps

Table 108-24 describes the traps issued by WANBSCTR. The recovery action is described in Table 108-25

Table 108-24 WANBSCTR Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
16973824	INIT_Q_CREATE	Task initialization error; cannot create a message queue to communicate with SMT	2
16973825	INIT_IDENT	Task initialization error; pSOS failure; cannot obtain the task identifier	2
16973826	INIT_CAP_CLIP	Task initialization error; cannot initialize CAP/CLIP interface	2
16973827	INIT_REQUEST	Task initialization error; pSOS failure; unable to allocate memory for request message	2
16973828	INIT_DCB	Task initialization error; pSOS failure; unable to allocate memory for device control block	2
16973829	INIT_TRACE_CB	Task initialization error; pSOS failure; unable to allocate memory for trace control block	2
16973830	INIT_CONFIG_CB	Task initialization error; pSOS failure; unable to allocate memory for configuration control block	2
16973831	INIT_CCB	Task initialization error; pSOS failure; unable to allocate memory for channel control block	2
16973832	INIT_STAT_CB	Task initialization error; pSOS failure; unable to allocate memory for statistics control block	2
16973833	INIT_DRIVER_INIT	Task initialization error; pSOS failure; unable to initialize the driver	2
16973856	FAILURE_READ_GETSEG	pSOS failure; cannot get memory segment for read buffer	6
16973857	FAILURE_READ_RETSEG	pSOS failure; cannot return memory segment for read buffer	6
16973858	FAILURE_WRITE_GETSEG	pSOS failure; cannot get memory segment for write buffer	6
16973859	FAILURE_WRITE_RETSEG	pSOS failure; cannot return memory segment for write buffer	6
16973860	FAILURE_OPEN_PORT	pSOS failure; cannot open the I/O port	2
16973861	FAILURE_CLOSE_PORT	pSOS failure; cannot close the I/O port	2
16973862	FAILURE_RCV_CLB	Unable to receive CLB (CAP/CLIP) frame	6
16973863	FAILURE_SEND_CLB	Unable to send a CLB (CAP/CLIP) frame	6
16973864	FAILURE_MCB	pSOS failure; unable to allocate memory for the message control block	2
16973865	FAILURE_MCB_AVAIL	Max number of MCB's reached; unable to process CLB messages	2
16973866	FAILURE_BLOCK_DATA	pSOS failure; unable to allocate memory for blocked data	2
16973867	FAILURE_RESPONSE	pSOS failure; unable to allocate memory for response message	2
16973868	FAILURE_FREE_BLOCK	pSOS failure; Unable to allocate memory for special control block	2
16973869	FAILURE_FLUSH_EV_SEND	pSOS failure; cannot send a FLUSH event message	2
16973870	FAILURE_SM2_BAD_STATE	WANBSCTR level 2 state machine encountered a bad state	7
16973871	FAILURE_SM2_BAD_EVENT	WANBSCTR level 2 state machine encountered a bad event	7
16973872	FAILURE_SM3_BAD_STATE	WANBSCT level 3 state machine encountered a bad state	7
16973873	FAILURE_SM3_BAD_EVENT	WANBSCTR level 3 state machine encountered a bad event	7

Table 108-25 WANBSCTR Recovery Actions

#	Severity	Recovery Action
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	Expand DLC protocol error. The DLC task should kill itself then come back online.
8	Major	Check the line parameters of the corresponding Expand line-handler process (IOP).

WANBSCSP Specific Traps

Table 108-26 describes the traps issued by WANBSCSP. The recovery action is described in Table 108-27.

Table 108-26 WANBSCSP Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
18022400	INIT_Q_CREATE	Task initialization error; cannot create a message queue to communicate with SMT	2
18022401	INIT_IDENT	Task initialization error; pSOS failure; cannot obtain the task identifier	2
18022402	INIT_CAP_CLIP	Task initialization error; cannot initialize CAP/CLIP interface	2
18022403	INIT_REQUEST	Task initialization error; pSOS failure; unable to allocate memory for request message	2
18022404	INIT_DCB	Task initialization error; pSOS failure; unable to allocate memory for device control block	2
18022405	INIT_TRACE_CB	Task initialization error; pSOS failure; unable to allocate memory for trace control block	2
18022406	INIT_CONFIG_CB	Task initialization error; pSOS failure; unable to allocate memory for configuration control block	2
18022407	INIT_CCB	Task initialization error; pSOS failure; unable to allocate memory for channel control block	2
18022408	INIT_STAT_CB	Task initialization error; pSOS failure; unable to allocate memory for statistics control block	2
18022409	INIT_DRIVER_INIT	Task initialization error; pSOS failure; unable to initialize the driver	2
18022432	FAILURE_READ_GETSEG	pSOS failure; cannot get memory segment for read buffer	6
18022433	FAILURE_READ_RETSEG	pSOS failure; cannot return memory segment for read buffer	6
18022434	FAILURE_WRITE_GETSEG	pSOS failure; cannot get memory segment for write buffer	6
18022435	FAILURE_WRITE_RETSEG	pSOS failure; cannot return memory segment for write buffer	6
18022436	PEN_PORT	pSOS failure; cannot open the I/O port	2
18022437	FAILURE_CLOSE_PORT	pSOS failure; cannot close the I/O port	2
18022438	FAILURE_RCV_CLB	Unable to receive CLB (CAP/CLIP) frame	6
18022439	FAILURE_SEND_CLB	Unable to send a CLB (CAP/CLIP) frame	6
18022440	FAILURE_MCB	pSOS failure; unable to allocate memory for the message control block	2
18022441	FAILURE_MCB_AVAIL	Maximum number of MCBs reached; unable to process CLB messages	2
18022442	FAILURE_BLOCK_DATA	pSOS failure; unable to allocate memory for blocked data	2
18022443	FAILURE_RESPONSE	pSOS failure; unable to allocate memory for response message	2
18022444	FAILURE_FREE_BLOCK	pSOS failure; unable to allocate memory for special control block	2
18022445	FAILURE_SM2_BAD_STATE	WANBSCSP level 2 state machine encountered a bad state	7
18022446	FAILURE_SM2_BAD_EVENT	WANBSCSP level 2 state machine encountered a bad event	7
18022447	FAILURE_SM3_BAD_STATE	WANBSCSP level 3 state machine encountered a bad state	7
18022448	FAILURE_SM3_BAD_EVENT	WANBSCSP level 3 state machine encountered a bad event	7

Table 108-27 WANBSCSP Recovery Actions

#	Severity	Recovery Action
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	Expand DLC protocol error. The DLC task should kill itself then come back online.

WANENVBSC Specific Traps

Table 108-32 describes the trap events issued by WANENVBSC. The recovery action is described in Table 108-32

Table 108-28 WANENVBSC Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
19988512	FAILURE_GETSEG	pSOS failure; cannot get memory segment	6
19988513	FAILURE_RETSEG	pSOS failure; cannot return memory segment	6
20054144	FAILURE_INVALID_ FUNCTION	Invalid function received from host	7
20054145	FAILURE_REQUEST_ PENDING	A new request has been received, while the previous request is still pending	7
20054148	FAILURE_INVALID_ QUAL	Byte driver did not initiate I/O, as the qualifier is invalid	7
20054149	FAILURE_DISCONNECT_STATE	Byte driver did not initiate I/O, as the driver is in DISCONNECT state	7
20054150	FAILURE_EMPTY_POLL_LIST	Poll list is empty	7
20054151	FAILURE_CORRUPT_ POLL_LIST	Poll list is corrupt - not terminated with ENQ	7
20119553	FAILURE_CAPCLIP_INIT	Cannot initialize CAP/CLIP interface	2
20119616	FAILURE_SEND_CLB_ FRAME	Unable to send CLB frame	6
20119617	FAILURE_SOCKET_ LOST	Socket connection lost	8
20119682	FAILURE_CONFIG_ ERROR	Byte driver OPEN failed	8
20119683	FAILURE_INVALID_ SUBTYPE	Subtype is invalid	8

Table 108-29 WANENVBSC Recovery Actions

#	Severity	Recovery Action
2	Major	If the problem persists, reset or replace the SWAN concentrator. Before resetting or replacing the SWAN concentrator, make sure the other CLIPs on the SWAN concentrator are not in use.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	WANENVBSC DLC protocol error. The DLC task should kill itself then come back online.
8	Major	Check the line parameters of the corresponding WANENVBSC line-handler process (IOP).

WANENVASC Specific Traps

Table 108-30 describes the trap events issued by WANENVASC. The recovery action is described in Table 108-31

Table 108-30 WANENVASC Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
21037088	FAILURE_GETSEG	pSOS failure; cannot get memory segment	6
21037089	FAILURE_RETSEG	pSOS failure; cannot return memory segment	6
21102720	FAILURE_INVALID_ FUNCTION	Invalid function received from host	7
21102721	FAILURE_REQUEST_ PENDING	A new request has been received, while the previous request is still pending	7
21102724	FAILURE_INVALID_ QUAL	Byte driver did not initiate I/O, as the qualifier is invalid	7
21168129	FAILURE_CAPCLIP_INIT	Cannot initialize CAP/CLIP interface	1
21168192	FAILURE_SEND_CLB_ FRAME	Unable to send CLB frame	6
21168193	FAILURE_SOCKET_ LOST	Socket connection lost	8
21168258	FAILURE_CONFIG_ ERROR	Async driver OPEN failed	8
21168259	FAILURE_INVALID_ SUBTYPE	Subtype is invalid	8

Table 108-31 WANENVASC Recovery Actions

#	Severity	Recovery Action
1	Critical	This is a SWAN kernel problem.If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), be prepared to supply your system number and the numbers and versions of products related to the error.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	WANENVASC DLC protocol error. The DLC task should kill itself then come back online.
8	Major	Check the line parameters of the corresponding WANENVASC line-handler process (IOP).

WANADCCP Specific Traps

Table 108-32 describes the traps issued by WANADCCP. The recovery action is described in Table 108-33

Table 108-32 WANADCCP Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
22020101	ERR_OBJDEL	Object has been deleted	6
22020102	ERR_OBJID	Object identifier (OID) is incorrect; failed validity check	6
22216731	ERR_RNADDR	pSOS failure for rn_retseg; starting address not on long word boundary	6
22216736	ERR_ZERO	pSOS failure; cannot getseg; request size of zero is illegal	6
22216737	ERR_TOOBIG	pSOS failure; cannot getseg; request size of too big for region	6
22216738	ERR_NOSEG	pSOS failure; no free segment available	6
22216739	ERR_NOTINRN	pSOS failure.; segment does not belong to this region	6
22216740	ERR_SEGADDR	pSOS failure for rn_retseg; incorrect segment starting address	6
22216741	ERR_SEGADDR	pSOS failure for rn_retseg; segment is already deallocated	6
22216742	ERR_NOQCB	pSOS failure; cannot create QCB; exceeds node's maximum number of active queues	6
22216743	ERR_IODN	Driver error; illegal device number specified	6
22216744	ERR_NODR	Driver error; no driver provided	5

Table 108-33 WANADCCP Recovery Actions

#	Severity	Recovery Action
5	Major	Hardware error. Replace the SWAN concentrator.
6	Major or critical	This is a major error if the download is successful after this trap error. The system recovered successfully.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.

WANSNAX Specific Traps

Table 108-34 describes the traps issued by WANSNAX. The recovery action is described in Table 108-35.

Table 108-34 WANSNAX Specific Traps

Specific Trap	Failed Procedure	Description	Recovery Action
23265281	TRAP_SMT_STOP	Received a directive from SMT to stop	0
23265282	TRAP_Q_CREATE	Cannot create a needed pSOS queue	6
23265283	TRAP_CAP_CLIP	CAP/CLIP interface failure	6
23265284	TRAP_NO_MEMORY	Cannot acquire needed memory block	6
23265285	TRAP_FREE_MEMORY	Cannot return a memory block to pSOS	6
23265286	TRAP_NO_TIMER	No pSOS timers available	6
23265287	TRAP_LIST_CORRUPTION	Corrupted link list detected	7
23265288	TRAP_DRIVER	BitSync driver failure	6
23265289	TRAP_MEMORY_CORRUPTION	Corrupted memory block detected	7
23265290	TRAP_PSOS_ERROR	Failure in a pSOS service routine	6
23265291	TRAP_LOSS_CONNECTION	Lost communication with IOP	4
23265292	TRAP_LOGIC_ERROR	Internal logical error detected	7

Table 108-35 WANSNAX Recovery Actions

#	Severity	Recovery Action
0	None	Informational only. No recovery is required.
4	Critical	Check if the corresponding IOP is running.
6	Major or critical	This is a major error if the download is successful after this trap error.This is a critical error if a download failure occurs after this trap error. In this case, the SWAN concentrator must be reset.
7	None	Expand DLC protocol error. The DLC task should kill itself then come back online.