Chapter 130 WANMGR Messages

Cause  The WAN manager process failed when executing an operation on the specified PROCESS object. This is a major error message. A configuration or system error has prevented the operation. The causes are described in procedure-name.

Effect  The identified operation cannot be performed.

Recovery  Correct the problem reported in file-system-error. Try to restart the process using the WAN subsystem SCF STOP PROCESS and START PROCESS commands.

Cause  This is an informational message. The message was generated because the indicated WAN subsystem SCF command was successfully executed on the specified ADAPTER object.

Effect  The effect of each command on the specified ADAPTER object is:

Recovery  No recovery action is required.

Cause  This is an informational message. The message was generated because the indicated WAN subsystem SCF command was successfully executed on the specified SERVER object.

Effect  The effect of each command on the specified SERVER object is:

Recovery  No recovery action is required.

Cause  This is an informational message. The message was generated because the indicated WAN subsystem SCF command was successfully executed on the specified PATH object.

Effect  The effect of each command on the specified PATH object is:

Recovery  No recovery action is required.

Cause  This is an informational message. The message was generated because the indicated WAN subsystem SCF command was successfully executed on the specified TASK object.

Effect  The effect of each command on the specified TASK object is:

Recovery  No recovery action is required.

Cause  This is an informational message. The message was generated because the indicated WAN subsystem SCF command was successfully executed on the specified PROCESS object.

Effect  The effect of each command on the specified PROCESS object is:

Recovery  No recovery action is required.

Cause  This is an informational message. The message was generated because the indicated WAN subsystem SCF command was successfully executed on the specified DEVICE object.

Effect  The effect of each command on the specified DEVICE object is listed below:

Recovery  No recovery action is required.

Cause  This is a critical error message. An internal error occurred within the WAN manager process.

Effect  The operation of the WAN manager process may be affected.

Recovery  Contact your server provider and provide all relevant information as follows:

Cause  This is a major error message. An error occurred when the WAN manager process attempted to start a process with the PROCESS_LAUNCH_IT_ procedure. Incorrect object configuration or a system error has prevented starting the object.

Effect  The specified PROCESS object was not started.

Recovery  The error reason reported in the message must be analyzed and corrected.

Cause  This is a warning message. Configured values for the specified DEVICE or PROCESS object have been changed and the next time the object is started, it will be started with the new values. The configuration parameters for a PROCESS or a DEVICE do not match those found in the configuration database.

Effect  The IOP representing the specified PROCESS or DEVICE object does not match the database configuration.

Recovery  The PROCESS or DEVICE object should be stopped and then re-started so that it can be synchronized with the configuration database.

Cause  This is a warning message. An error occurred when the WAN manager process attempted to access the configuration database record for the specified object. This operator message was reported because an error was returned from the procedure identified in procedure-name.

Effect  The WAN manager process was unable to either create the specified process object using the PROCESS_LAUNCH_IT_ procedure, or to stop the specified process using the DSC_STOP_DEVICE_ procedure.

Recovery  The error and error detail reported in the message must be analyzed and corrected.

When the error value is 1 with error-detail 6005, it indicates that the CONFIG database is already locked by a subsystem and WAN manager is unable to acquire the lock. As a result, the WAN manager will be unable to execute the sensitive commands (ADD/ALTER/ABORT/START/STOP/DELETE) on the WAN subsystem objects.

In this scenario, configure the WAN manager to retry for a maximum of 30 seconds to acquire the lock. This is achieved using the STARTUP parameters RETRYMAX and DELAY (applicable from G06.27 and subsequent G-series RVUs). These parameters can be configured as follows:

SCF>ABORT PROCESS $ZZKRN. #ZZWAN
SCF>ALTER PROCESS $ZZKRN.#ZZWAN, & STARTUPMSG "RETRYMAX no. of retries;DELAY delay in centiseconds" 
SCF>START PROCESS $ZZKRN.#ZZWAN 

RETRYMAX can be set with the values from 5 to 30 and DELAY with the values from 0 to 100. The default values for RETRYMAX and DELAY are 5 and 0, respectively. The WAN manager retries to acquire the lock for RETRYMAX times with the specified DELAY in centiseconds. For example, if RETRYMAX is set to 30 with DELAY of 100, it indicates that WAN manager retries 30 times at an interval of 100 centiseconds delay to obtain the CONFIG database lock.

	NOTE: Configure the Startup parameters carefully because the default timeout value of SCF commands is 80 Seconds (configurable value). When SCF timeout is less than WAN manager’s retry time, the SCF Command times out but WAN manager continues to process the request.

Cause  This is an informational message. The concentrator manager (ConMgr) process is stopping. The concentrator manager (ConMgr) process has detected an error condition that it considers fatal and cannot continue to run in the processor.

Effect  No SWAN concentrator can be managed for the processor where the concentrator manager (ConMgr) process generated this message.

Recovery  No recovery action is required.

Cause  This is an informational message. The concentrator manager (ConMgr) process received an activate path request from an IOP. The IOP is trying to start the WAN line by asking the concentrator manager (ConMgr) process to download the microcode to the SWAN concentrator.

Effect  If the download is successful, the IOP can then start WAN traffic on the WAN line. If the download is not successful, the IOP cannot start WAN traffic on the WAN line.

Recovery  If the download is successful, no action is necessary. If the download is not successful, take the necessary steps as defined by error-recovery described above.

Cause  This is an informational message. The concentrator manager (ConMgr) process has completed the stop request from the specified IOP. The IOP has requested the DLC task to be stopped because the LINE was stopped.

Effect  The DLC task has been stopped, now the IOP can terminate if requested.

Recovery  The error reason reported in the message must be analyzed and corrected.

Cause  This is an informational message. This message occurred due to a configuration or system error. The concentrator manager (ConMgr) process detected an error when issuing an SNMP SET command to the specified SWAN concentrator.

Effect  The SWAN concentrator TASK was not successfully started. The ACTIVATE PATH operation will attempt to recover by issuing the SET request to another PATH. An ACTIVATE PATH request from an IOP or a WAN subsystem SCF command will not be able to use the specified PATH. The ACTIVATE PATH operation will try to recover by issuing the SET request to another PATH.

Recovery  The error reason reported in set-error must be analyzed and corrected.

Cause  This is a major error message. The concentrator manager (ConMgr) process has received a TRAP message in response to an SNMP SET command to the SWAN concentrator that indicates a failure of the Set operation or that the SNMP process failed to receive a TRAP message when one is required.

Effect  An ACTIVATE PATH request from an IOP or a WAN subsystem SCF command will not be able to use the specified PATH. The ACTIVATE PATH operation will try to recover by issuing the SET request to another PATH.

Recovery  The error reason reported in the message must be analyzed and corrected.

cmgr_track_id	identifies the SWAN concentrator track identity.
cmgr_concname.clip_number	identifies the adapter name and the CLIP number.
zwan_tkn_path_name	identifies the Ethernet path name. This token will be present only if the status is “successful.”
program	specifies the object file to be downloaded to the CLIP. It has the following format: \system.$volume.subvol.filename This is present only if the command was an add task.
status	identifies whether the command succeeded or failed. If the command succeeded on an alternate path but failed on the requested path, a warning message with error messages on that path is issued. Otherwise, no message is given.
component	identifies the component that has caused the error. There is no path error message. The possible values are: Message text Explanation “CLIP Kernel” The Kernel running in the CLIP. “WANMgr” The WANMgr process. “SNMP Agent” The SNMP agent task running in the CLIP. “TCP/IP” The NonStop TCP/IP process running.
cmgr_err	identifies the reason for the failure of the add task or status task command. No path error message will be given.
swan_path_a/swan_path_b	identifies the reason for the failure on the specific path, if nonzero. The possible values are: Message text Explanation “TCPIP - CLIP Unreachable” No route to the host configured. “TCPIP - Network Unreachable” Network is unreachable. “TCPIP Process Error” TCP/IP process-related error. TCPIP Process Down” TCP/IP process is down. “Invalid Value” ConMgr received an unexpected value. “SNMP Memory Shortage” No Memory available to receive SNMP packet. “No Trap Resp from CLIP” ConMgr did not receive Trap from CLIP. “No Response from CLIP” CLIP did not respond to requests from ConMgr. “TFTP File Not Found” TFTP could not find the file to download. “TFTP Access Violation” TFTP server doesn’t have permission to download the file. “TFTP No Space/Disk Full” TFTP client doesn’t have enough space to store the file. “TFTP Bad Operation” TFTP packet is corrupted. “TFTP Bad Tx ID” TFTP bad transmission ID. “TFTP File Already Exists” A file by that name already exists in the adapter. “TFTP Bad User” The user is not allowed to download the file. “Bad TFTP Operation” Unsupported TFTP operation attempted. “TFTP sendto Failed” A sendto to the TFTP process failed. “No Resp from the TFTP Server” TFTP server is not responding. “TFTP Unknown Packet” Unrecognized TFTP packet. “TFTP Out of Sequence” An out of sequence packet was received. “TFTP Too Big Packet” The packet received by TFTP is too big. “TFTP No Socket” TFTP process could not obtain sockets. “TFTP No Input” No input for TFTP. “Error in SNMP Trap” Trap response from CLIP reported an error. “TCPIP Bind Error” Error encountered while binding to a TCP/IP socket. “Timeout on TCPIP Bind” Timeout while binding to TCP/IP socket. “TCPIP version unknown” TCPIP version unknown. “TCPIP Socket Error” TCP/IP socket error. “Path Stopped” The path is stopped. “Path Not Configured” The path is not configured. “No Timers” Could not allocate a timer from Timer list. “No Memory” Not memory available. “Timeout on TCPIP Socket” Timeout on TCP/IP socket. “Bad SNMP Struct” SNMP data received has invalid format. “SNMP Memory Shortage” No enough memory to store the SNMP message. “DCT Not Found” No entry for the TCP/IP process corresponding to the current path.
swan_err_detail_a | swan_err_detail_b	identify the reason for the failure if non-zero. The possible values are: Message text Explanation “File Read Error” Unable to read the program file for obtaining binder timestamp. “Encode SNMP Error” Error in encoding the SNMP request packet to be sent to CLIP. “Invalid Value” A request to ConMgr contained invalid value or an internal call has resulted in an invalid value. “Invalid SNMP Status” The SNMP reply from the CLIP contained an invalid value for error status. “No Trap Resp from CLIP” CLIP has not responded with Trap for a SET request from host. “No Response from CLIP” CLIP is not responding to requests from ConMgr. “Error in SNMP Trap” Trap response indicates an error from CLIP for previous request from ConMgr. “TCPIP Bind Error” Binding to the socket has failed. “Timeout on TCPIP Bind” Operation of binding to a socket has timed out. “Adapter TYPE invalid” Adapter has been invalidated by WanMgr. “Adapter configured with wrong TYPE” Adapter is configured with the wrong type. “DEVICE Stopped” Device is stopped. “SERVER Stopped” Server down. “TASK stopped” Task is stopped. “Timeout on WanMgr Read” A request to WanMgr has timed out. “Version Incompatible” Incompatible WanMgr. “Mismatch of PROG file with adapter’s TYPE” The adapter’s type is not matching the type obtained from the program file. “Bad Program Filename” Program file name is not proper. “Bad Command” The command is not supported. “Error in WanMgr Read” Error in reading data from WanMgr. “Bad IP Address” Routing address provided by WanMgr is wrong. “Wrong filename convention” The file name is wrong according to SWAN or SWAN 2. “TCPIP - CLIP Unreachable” No route to the host is configured. “TCPIP - Network Unreachable” Network is unreachable. “TCPIP Process Error” TCP/IP process related error. “TCPIP Process Down” TCP/IP process is down. “Invalid Value” ConMgr received an unexpected value. “SNMP Memory Shortage” No memory available to receive SNMP packet. “No Trap Resp from CLIP” ConMgr did not receive Trap from CLIP. “No Response from CLIP” CLIP did not respond to requests from ConMgr. “TFTP File Not Found” TFTP could not find the file to download. “TFTP Access Violation” TFTP server doesn’t have permission to download the file. “TFTP No Space/Disk Full” TFTP client doesn’t have enough space to store the file. “TFTP Bad Operation” TFTP packet is corrupted. “TFTP Bad Tx ID” TFTP bad transmission ID. “TFTP File Already Exists” A file by that name already exists in the adapter. “TFTP Bad User” The user is not allowed to download the file. “TFTP Bad Operation” Unsupported TFTP operation attempted. “TFTP sendto Failed” A sendto to the TFTP process failed. “No Resp from TFTP Server” TFTP server is not responding. “TFTP Unknown Packet” Unrecognized TFTP packet. “TFTP Out of Sequence” An out of sequence packet was received. “TFTP Too Big Packet” The packet received by TFTP is too big. “TFTP No Socket” TFTP process could not obtain sockets. “TFTP No Input” No input for TFTP. “Error in SNMP Trap” Trap response from CLIP reported an error. “TCPIP Bind Error” Error encountered while binding to a TCP/IP socket. “Timeout on TCPIP Bind” Timeout while binding to TCP/IP socket. “TCPIP version unknown” TCPIP version unknown. “TCPIP Socket Error” TCP/IP socket error. “PATH Stopped” The path is stopped. “PATH Not Configured” The path is not configured. “No Timers” Could not allocate a timer from Timer list entry (TLE). “No Memory” No memory is available. “Timeout on TCPIP Socket” Timeout on TCP/IP socket. “Bad SNMP Struct” SNMP data received has invalid format. “SNMP Memory Shortage” Not enough memory to store the SNMP message. “DCT Not Found” No entry for the TCP/IP process corresponding to the current path.

Cause  This is an informative message. It is issued whenever an add task command or a status task command is issued either from SCF, OSM, or TSM. This message indicates the outcome of these commands (successful or failure).

Effect  The add task helps in downloading the diagnostic task and DLC tasks running in a CLIP. This message has no effect on the CLIP.

Recovery  If the add and status tasks return “successful,” no action is necessary. If the tasks return “failure,” take necessary steps as recommended by the message returned. The message returned can be one of the following:

Cause  This is an informational message. The WAN shared driver has successfully connected to the data link control (DLC) task in the SWAN concentrator. A new socket connection was requested by the IOP and was established.

Effect  The IOP can start WAN traffic on the WAN line.

Recovery  No recovery action is required.

Cause  This is a major error message. The WAN shared driver has failed to connect to the data link control (DLC) task in the SWAN concentrator. A new socket connection was requested by the IOP but failed and a connection was not established.

Effect  The IOP cannot start WAN traffic on the WAN line.

Recovery  The socket error reported in socket-error must be analyzed and corrected.

Cause  This is a major error message. The WAN shared driver failed on a socket receive operation because the NonStop TCP/IP process detected an error on the socket connection.

Effect  The socket connection is lost.

Recovery  The socket error reported in socket-error must be analyzed and corrected. If the message displayed is file-system error 179 there may be a problem handling data frames or a corrupted data frame was received. To resolve this problem, contact your service provider with the EMS message.

Cause  This is a major error message. The WAN shared driver failed on a socket send operation because the NonStop TCP/IP process detected an error on the socket connection.

Effect  The status of the socket connection is described in connection-status.

Recovery  The socket error reported in socket-error must be analyzed and corrected.

Cause  This is a major error message. The WAN shared driver failed during initialization because of the error reported in error-number.

Effect  The WAN Shared Driver is not initialized and the WAN Shared Driver cannot be used. The IOP that the WAN shared driver is bound with stops running.

Recovery  The initialization error reason reported in the message must be analyzed and corrected. If the message displayed is file-system error 179 there may be a problem reading the database. To resolve this problem, contact your service provider with the EMS message.

Cause  This is an informational message. When serving a START DEVICE request WAN Shared Driver checks the integrity of the existing PROFILE and the IOPOBJECT specified.

Effect  If the specified PROFILE is not supported by IOPOBJECT (that is, if the version between these two object does not match), WAN Shared Driver will generate a warning event.

Recovery  The DEVICE needs to be deleted and re-added with the correct PROFILE and IOPOBJECT combination.

Cause  This is an informational message. The WANBoot process failed on a file open procedure to the WAN manager process because the WAN manager process was not accessible.

Effect  The WANBoot process and/or the WAN manager processes have terminated. No information about the WAN manager process configuration database record is available.

Recovery  The WAN manager process must be started. When the WAN manager process restarts, it will in turn restart the WANBoot process if it is also failed.

Cause  This is a major error message. The ADD PROCESS command for the WANBoot process did not specify a NonStop TCP/IP process name in the STARTUP attribute.

Effect  The WANBoot process stops running and the SWAN concentrator cannot obtain its configuration information.

Recovery  Reissue the ADD PROCESS command for the WANBoot process with a valid NonStop TCP/IP process name specified in the STARTUP attribute.

Cause  This is an informational message. The WANBoot process successfully sent a BOOTP reply back to the BOOTP client in the specified CLIP on the specified SWAN concentrator. This occurred because the SWAN concentrator was powered on, or the power on self test (POST) was executed on the CLIP, or a software failure caused the CLIP to restart its Kernel code (the firmware object code of the microcode file that runs in the essential part of the CLIP FLASH memory).

Effect  The SWAN concentrator has successfully established its configuration parameters. A firmup may have been initiated.

Recovery  No recovery action is required.

Cause  This is an error message. The WAN manager process failed to return the configuration record for the specified WANBoot process. The WAN manager process cannot be accessed from the WANBoot process to select configuration database information. The WAN manager process may have stopped running.

Effect  No BOOTP reply will be sent to the CLIP issuing the BOOTP request.

Recovery  Restart the WAN manager process, or correct the problem when the WAN manager process may have while accessing the configuration database information.

Cause  This is a major error message. The WANBoot could not reply successfully to a BOOTP request received from a SWAN concentrator CLIP. This may be because the ADAPTER, SERVER, or PATH object was not configured, or because NonStop TCP/IP process access to the ADAPTER failed.

Effect  The SWAN concentrator CLIP will not be accessible from the system.

Recovery  Either configure the ADAPTER, SERVER, or PATH correctly, or correct the problem with the NonStop TCP/IP process or with the ServerNet LAN Systems Access (SLSA) subsystem.

Cause  This is an informational message.The WANBoot process successfully sent a BOOTP request message to the specified SWAN concentrator and received the expected BOOTP reply. The SOCKET used access to the NonStop TCP/IP process has been restarted, or an ADAPTER, or a PATH configuration has been ADDED or ALTERed.

Effect  The PATH configuration has been re-synchronized.

Recovery  No recovery action is required.

Cause  This is a warning message. The WANBoot process failed to send a BOOTP request message to the specified SWAN concentrator. Failure to exchange BOOTP requests may be caused by the SWAN concentrator being powered off or not connected to the configured Ethernet segment. It may also be caused by the NonStop TCP/IP process or the ServerNet LAN Systems Access (SLSA) LIF object not being accessible.

Effect  The CLIP will not be accessible using the specified PATH. OSM or TSM cannot perform a LOAD request.

Recovery  Correct the problem identified by the file-system error. Recovery timers will bring the path into use if necessary.

Cause  This is an informational message. The WANBoot successfully performed a FIRMUP to the SWAN concentrator. The firmware in the SWAN concentrator was out of date and required updating.

Effect  The SWAN concentrator firmware was updated.

Recovery  No recovery action is required.

Cause  This is a major error message. The WANBoot process failed to perform a firmup to the SWAN concentrator. The firmware in the SWAN concentrator is out of date and requires updating.

Effect  The SWAN concentrator firmware was not updated.

Recovery  Correct the problem identified by the file-system error. Recovery timers will bring the path into use if necessary

Cause  This is a warning message. The WANBoot process received a BOOTP request from a PATH that is not configured on the NonStop TCP/IP process assigned to the specified WANBoot process. This could have occurred because of the following causes:

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, connect them to different Ethernet segments.

Cause  This is a major error message. The WANBoot process encountered a configuration or system error when attempting to create a socket to access its configured NonStop TCP/IP process.

Effect  The specified NonStop TCP/IP process cannot be accessed from the specified WANBoot process.

Recovery  The error reason reported in the message must be analyzed and corrected.

Cause  This is a major error message. The WANBoot successfully received a dump image from the specified CLIP. The firmware in the SWAN concentrator failed and a dump image was sent to the server and saved in the file indicated in disk-file-name.

Effect  The SWAN concentrator firmware image is archived for diagnosis.

Recovery  No recovery action is required. If necessary, the SWAN concentrator KERNELCODE will restart automatically.

Cause  This is a major error message. The WANBoot process was unable to receive a dump image from the specified CLIP. The firmware in the SWAN concentrator failed, however the dump image could not be sent to the host. If file-system-error reports a value of -1, or if file-name and error-number report a socket create error -1, then the WANBoot process might not have a running NonStop TCP/IP process.

Effect  The SWAN concentrator firmware dump image is lost.

Recovery  If file-system-error reports a value of -1, or if file-name and error-number report a socket create error -1, make sure that the WANBoot process has a running NonStop TCP/IP process. For all other errors, no recovery action is required. If necessary, the SWAN concentrator KERNELCODE will restart automatically. The dump image can be made available only by correcting the problem reported, and then reproducing the failure in the CLIP so the dump can be taken again.

Cause  This is an informational message. The WANBoot was able to successfully exchange a status probe on the specified CLIP PATH. Prior to exchanging the status probe, the CLIP PATH had been inaccessible. The CLIP PATH was restored to service either by powering on the SWAN concentrator, connecting the SWAN concentrator to the configured Ethernet segment, or by starting the NonStop TCP/IP process and SUBNET object and the associated ServerNet LAN Systems Access (SLSA) subsystem LIF object.

Effect  The PATH can now be used to access a LINE on the SWAN concentrator CLIP.

Recovery  No recovery action is required.

Cause  This is a major error message. The WANBoot process is no longer able to exchange status probe messages with the specified CLIP PATH. Failure to exchange status probe messages may be caused by the SWAN concentrator being powered off or not connected to the configured Ethernet segment. The problem may also be caused by the NonStop TCP/IP process or by the ServerNet LAN Systems Access (SLSA) LIF object not being accessible.

Effect  The specified PATH cannot be used to access lines on the CLIP. If the other PATH to the CLIP is also not available, the CLIP will be inaccessible.

Recovery  Correct the problem identified by the file-system error. Recovery timers will bring the path into use if necessary.

task-obj-spec	identifies that a TASK object is the subject of this operator message and is in the following format: $ZZWAN.#conc-name.clip-num.dlc-task
configuration-track-id	identifies the configuration-track-id. It is in the form ZZWAN.#conc-name.clip-num.dlc-task.
swan-kernel-microde-file-name	identifies the disk file that contains the KERNELCODE used for the firmup operation.
step-number	identifies the step in the firmup sequence that failed. The possible values are: Value Explanation 0 Initial BOOTP.
error-recovery	identifies the recovery mechanism to be taken up. The possible values are: Value Explanation 1 Auto-retrying on other PATH.

Cause  This is a warning message. The WANBoot process failed to perform a firmup on the specified path of the SWAN concentrator after the initial BOOTP.

Effect  The SWAN concentrator firmware was not updated from the specified path.

Recovery  No recovery action is needed. WANBoot will automatically retry on the other path.

Cause  This general purpose event provides informational messages.

Effect  This event has no effect.

Recovery  No recovery action is required.

process-obj-spec	identifies that a PROCESS object is the subject of this operator message and has the following format: $ZZKRN.#proc-name
error-number	identifies the file-system error number. File-system errors are described in the Guardian Procedure Errors and Messages Manual. You can also display the message text of a file-system error by typing the word “error” followed by the error number at the TACL prompt. To display file-system error information, enter “error -1.”

Cause  This is a dummy event.

Effect  This event has no effect.

Recovery  No recovery action is required.

task-obj-spec	identifies that a TASK object is the subject of this operator message and has the following format: $ZZWAN.#conc-name.clip-num.dlc-task
configuration-track-id	identifies the configuration track id and has the following format: ZZWANl.#conc-name.clip-num.dlc-task
clip-number	identifies the CLIP number.
progress%	percent of FIRMUP completed.

Cause  The status of firmup progress will be made available to the user at the place of initiation of FIRMUP (OSM/TSM). The status will include the percentage of work completed.

process-obj-spec	identifies that a PROCESS object is the subject of this operator message. It has the following format: $ZZKRN.#proc-name
step-number	identifies the step in which the process configuration failed. The possible values are: Value Explanation 0 Read CONFIG file. 1 ADD Process. 2 ALTER Process. 3 START Process.
status	identifies whether the configuration is an ERROR or WARNING.
ip-address	identifies the IP address.
ERROR msg	The possible errors are: Value Explanation 0 WANBoot/TFTP process configured without HOSTIP. 1 No Adapters configured for the given HOSTIP. 2 Another PROCESS configured for the given HOSTIP. 3 SNMP TMUX process configured without HOST/TCPIP. 4 HOSTIP already bound to different TCPIP.

Cause  During WANMgr startup, or when a PROCESS is added, WANMgr checks for the integrity of the process’s HOSTIP and TCPIP attributes.

Effect  Occurs if a WANBoot /TFTP/SNMPTMUX process is misconfigured. The possible errors are:

adapter-obj-spec	Indicates that an adapter object is the subject of this operator message. It is in the following form: $ZZKRN.#conc-name
step-number	identifies the step in which the adapter configuration failed. The possible values are: Value Explanation 0 Read CONFIG file. 1 Add adapter. 2 Alter adapter. 3 Start adapter. 4 Start device.

ERROR msg

identifies the error message number. Possible values are:

Cause  During WANMgr startup, or when an adapter is added, WANMgr checks for the integrity of the adapter’s HOSTIP and TCP/IP attributes.

Effect  During WANMgr startup, when HOSTIP/TCPIP combination mismatches for an adapter, the same adapter’s TYPE still be made invalid. Subsequently, ACTIVATE PATH and STATUS TASK requests will never succeed in this adapter. When an adapter is added, the following errors can be generated:

Recovery  To make an adapter’s TYPE valid, delete and re-add the adapter.

Cause  This is an informational message. The concentrator manager (ConMgr) process received a hardware status request from WANMgr. The WANMgr is trying to get the status of the hardware components of the SWAN concentrator.

Effect  If the request is successful ConMgr obtains the status of the hardware components from the CLIP and returns the name to WANMgr.

Recovery  If the request is successful no action is necessary. If the download is not successful, take the necessary steps as defined by error-recovery described under error-recovery (above).

adapter-obj-spec	identifies that an ADAPTER object is the subject of this operator message. The format is: $ZZWAN.#conc-name
clip-number	identifies the CLIP number.
path-name	identifies the PATH name for the received BOOTP request.
conf-type	Is the configured TYPE of the adapter.
det-type	Is the REAL type of the adapter.

Cause  WANBoot received a BOOTP request from the CLIP. WANBoot checks whether the adapter’s real TYPE matches the configured TYPE.

Effect  If the adapter’s real TYPE does not match the adapter’s configured TYPE, WANBoot generates this error event.

Recovery  Delete the adapter and re-add it with the proper TYPE.

Cause  This is an informational message. The ConMgr process received an ADD TASK or ACTIVATE PATH request. ConMgr is checking the validity of the PROGRAM file to be downloaded to the CLIP.

Effect  If the specified PROGRAM file is valid, ConMgr downloads the file to the CLIP; if the PROGRAM is invalid, ConMgr attempts to get the file from the given location. If this action also fails, ConMgr cancels the request.

Recovery  If the request is successful, no action is required. If the request failed, retry the request by specifying the proper PROGRAM file.

Cause  This is a warning message which indicates that the auto-configured Primary and Backup CPU values for the PROCESS object have been changed, and the object will be started with the new values. See the reason-msg for the reason for the change in the auto-configured parameters for a PROCESS.

Effect  The auto-configured process is added and started with the new values.

Recovery  No recovery action is required since the process is autoconfigured using the changed values.

Cause  This is a severe error message caused by the malfunction of another subsystem manager process. An error occurred when the WAN manager process attempted to access the configuration database record and found the configuration file locked by the process-obj-spec for more than five seconds.

Effect  The WAN manager process cannot complete the database operation. This EMS message occurs along with EMS message 11 (see this message for details about the procedure that failed).

Recovery  Check the status of the process that has locked the configuration file and correct it. Repeat the operation that resulted in this message.