During an attempt to start up (build its stack), the signaling software encountered a problem and aborted the build. When this message follows a message indicating that a device file could not be opened or a PVC could not be bound, this means that the error occurred during initial startup of the IRIS ATM subsystem (for example, atmconfig -u).

As requested by sigtest, the driver attempted to accept an incoming VC request, but the accept failed. That is, the ioctl() command ATMIOC_ACCEPT failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

The driver was unable to add a party to the multipoint VC, as requested by sigtest. The ioctl() command ATMIOC_ADDPARTY failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the man page for intro(2):

The native-E.164 address that was entered does not have a valid count of digits. A digit is any of the following characters: 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9. The address must contain at least 1 digit and no more than 15.

The ATM NSAP address that was entered contained an invalid count ( length of user's entry) of hexadecimal characters. The address must be exactly 40 hexadecimal characters.

The ATM NSAP address that was entered contained an invalid character. Valid hexadecimal characters are the following: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, A, b, B, c, C, d, D, e, E, f, and F.

As the contents of the file specified on the atmarp -f command line were parsed, an invalid board unit ( unit) was encountered.

Change the entry at the line indicated (linenumber) to an installed IRIS ATM board. The /sbin/hinv command displays the unit numbers associated with the currently installed boards.

When attempting to open a virtual circuit for one of the entries in the IP-to-PVC mapping file, atmarp was unable to create the channel. The ioctl() command ATMIOC_CREATEPVC failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

When attempting to display the current IP-to-ATM address resolution table, atmarp was unable to complete the task. The ioctl() command ATMIOC_GETARPTAB failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

When attempting to open a virtual circuit for one of the entries in the IP-to-ATM mapping file, atmarp was unable to map an IP address to the VPI/VCI address for the VC. The ioctl() command ATMIOC_SETARP failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

The device file (for example, /hw/atm/2) for a hardware unit (for example, port 2) mentioned in the IP-to-PVC address resolution (AR) table could not be opened. This may indicate that the board was not located during the last power on, that the board is not active (UP), or that the IRIS ATM software was not installed correctly. The systemmessage (a standard system errno) provided in the message indicates the problem. Some system messages are described below; others are described in the man page for the open() system call.

To remedy ENODEV or ENXIO, do either of the following:

The file specified on the atmarp -f command line could not be opened for reading. Verify that the file allows read-access and that it is a simple ASCII text file.

As the contents of the file specified on the atmarp -f command line were parsed, a name was encountered that could not be mapped to an IP address.

Add the name (name) to the network information database (for example, the local /etc/hosts file or the NIS server) or edit the entry on the line indicated so that it matches an entry from the database.

While attempting to process a received ATMARP packet, the driver encountered an unknown command. This indicates that the sender of the packet uses ARP commands that are not implemented in this version of the IRIS ATM driver. There is no problem with the IRIS ATM product.

As the contents of the file specified on the atmarp -f command line were parsed, an invalid entry was encountered in the VPI column.

Change the entry at the line indicated (linenumber) to a valid entry. Valid entries range from 0 to 65535 digital or 0x0000 to 0xFFFF hexadecimal, inclusive.

As the contents of the file specified on the atmarp -f command line were parsed, an invalid entry was encountered in the VPI column. Valid entries range from 0 to 255 digital or 0x00 to 0xFF hexadecimal.

Change the entry at the line indicated (linenumber) to a valid entry, inclusive.

As the contents of the file specified on the atmarp -f command line were parsed, an error was encountered at the line indicated.

Edit the file as explained in “Mapping IP Interfaces to the ATM Subsystem” in Chapter 3.

While reading the IP-over-PVC configuration file (/var/atm/pvc.conf ), atmarp encountered an invalid entry ( flag) in the flags position of the line specified ( number#). To resolve this, edit the file as explained in “Address Resolution for PVCs” in Chapter 3.

While attempting to download new firmware, atmconfig was unable to start the EEPROM write (“burn”) program. The ioctl() command ATMIOC_EXEC failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to reconfigure the board, an error occurred. The ioctl() command ATMIOC_SETCONF failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

When atmconfig attempted to open the device file for the hardware (/hw/atm/#), it did not find the file. This may indicate that the hardware unit was not located during the last power on, that the board is not active (UP), or that the IRIS ATM software was not installed correctly. The systemmessage (a standard system errno) indicates more exactly what the problem is; explanation for the systemmessage is available in the intro(2) and open(2)man pages.

While attempting to reconfigure the hardware with the indicated unit number (#), atmconfig -X or atmconfig -R was unable to complete the task. A prior error message should indicate more detail about the problem.

When starting the process of downloading new firmware from the specified file (filename) to the hardware with the indicated unit number (#), atmconfig -l could not read the file containing the new program for burning the EEPROM. A prior message should clarify the reason.

The firmware currently on the hardware is the correct version for compatibility with the driver that is currently running. No new firmware has been downloaded to the hardware with the indicated unit number (#). When installing new IRIS ATM software, you do not need to download new firmware. The driver does this automatically as it starts running, whenever it discovers that the firmware on the board is incompatible.

When trying to put the indicated hardware unit (#) into the UP state, ifconfig -u discovered that the board was already UP.

Before starting to download new firmware to the hardware unit ( #), atmconfig -l discovered that the device was not in the DOWN state. Use atmconfig -d to put to hardware into the DOWN state, before continuing. For more information on the use of the -d option, see “Changing the State of a Port” in Chapter 3, for Origin2000 or Onyx 2 systems, or “Changing the State of a Board” in Chapter 3, for Challenge or Onyx systems.

Before starting to reconfigure the hardware unit (#), atmconfig -X or atmconfig -R discovered that the device was not in the DOWN state. Use atmconfig -d to reset and put the hardware into the DOWN state, before reconfiguring it. For more information on the use of the -d option, see “Changing the State of a Port” in Chapter 3, for Origin2000 or Onyx 2 systems, or “Changing the State of a Board” in Chapter 3, for Challenge or Onyx systems.

When trying to put the hardware unit (#) into the UP state, ifconfig -u discovered that the device was not in the DOWN state. Use atmconfig -d to put the hardware into the DOWN state before invoking this command again. For more information on the use of these options, see “Changing the State of a Port” in Chapter 3, for Origin2000 or Onyx 2 systems, or “Changing the State of a Board” in Chapter 3, for Challenge or Onyx systems.

While downloading the new firmware to hardware unit (# ), atmconfig -l encountered a problem. A prior error message should clarify the reason.

While attempting to configure the board from its configuration file (filename), atmconfig was unable to do so. The ioctl() command ATMIOC_SETCONF failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While configuring the board from its configuration file ( filename), atmconfig found that one of the sizes specified for buffers is not a multiple of 8. Edit the file and try the command again.

While configuring the board from its configuration file ( filename), atmconfig found that the size specified for the small buffers is larger than that specified for the large buffers. Edit the file and try the command again.

While configuring the board from its configuration file ( filename), atmconfig found that the sum total of all the specified buffer sizes is more than the board can accommodate (which is 1,966,080 bytes). Edit the file and try the command again.

While configuring the board from its configuration file ( filename), atmconfig found that the indicated line (number) could not be parsed. The problematic entry is for the indicated buffers: XLBUF =large transmit, XSBUF=small transmit, RLBUF= large receive, or RSBUF=small receive buffers. Edit the file and try the command again.

While attempting to reconfigure the rate queues on the IRIS ATM board from the configuration file (filename), the command encountered an unrecognized character in the position where it expected to read the rate queue's rate. Edit the file, as explained in “ATM-OC3c HIO Board Transmission Rate Configuration” in Chapter 3, then invoke the command again.

While attempting to reconfigure the rate queues on the IRIS ATM board from the configuration file (filename), the command's ioctl() call to the board (ATMIOC_SETRATEQ) failed with the error indicated in the systemmessage (a standard system errno); additional explanation for the systemmessage is available in the intro(2) man page. Verify that the rate specified on the problematic line in the file is supported by the hardware.

While configuring the board from its configuration file, atmconfig found that the communication path to the board is not working. Specifically, the ATMIOC_GETCONF ioctl() call failed. This probably indicates that the board is not responding. The systemmessage (a standard system errno) for the failure indicates what the problem is, as explained below. Additional explanation for the systemmessage is available in the intro (2) man page.

While attempting to reconfigure the IRIS ATM board, the command could not open the indicated configuration file (filename) for reading. It could be that the file does not exist or that its access modes do not allow reading. The systemmessage (a standard system errno) indicates more exactly what the problem is; additional explanation for the systemmessage is available in the intro(2)man page.

While attempting to reconfigure the IRIS ATM board, the command discovered that the board is not in the UP or DOWN state. Invoke atmconfig -u to bring the board UP. If this fails, use atmconfig -d followed by atmconfig -u. If this also fails, invoke atmconfig -r, atmconfig -d , and atmconfig -u. If this does not work, power cycle the machine. For more information on the use of these options, see “Changing the State of a Port” in Chapter 3, for Origin2000 or Onyx 2 systems, or “Changing the State of a Board” in Chapter 3, for Challenge or Onyx systems.

While configuring the board's buffer sizes from the configuration file, atmconfig found that the board was not in the correct state for reconfiguration. The board must be in the DOWN state. Use the atmconfig -d command to change the board's state, then invoke the command again. For more information on the use of the -d option, see “Changing the State of a Port” in Chapter 3, for Origin2000 or Onyx 2 systems, or “Changing the State of a Board” in Chapter 3, for Challenge or Onyx systems.

While attempting to reconfigure the IRIS ATM board, the command could not interpret something on the indicated line (linenumber). Edit the file, as explained in “ATM-OC3c HIO Board Transmission Rate Configuration” in Chapter 3, then invoke the command again.

While attempting to reconfigure the rate queues on the IRIS ATM board from the configuration file (filename), the command encountered an unrecognized string in the position of the specified line where it expected to read the rate queue's identification value. Edit the file, as explained in “ATM-OC3c HIO Board Transmission Rate Configuration” in Chapter 3, then invoke the command again.

While attempting to reconfigure the allocation of onboard memory, atmconfig -X or atmconfig -R discovered that the newly specified configuration is invalid. For example, the total byte count for all buffers (receive and transmit) may exceed the allowed maximum, or the specified size for large-sized buffers may be larger than the small-sized buffers, or one of the sizes may not be a multiple of 8.

When starting the process of downloading new firmware, atmconfig -l encountered a problem. The ioctl() command ATMIOC_VERS failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

When attempting to set up a virtual circuit for the test, atmtest was unable to create the VC. The ioctl() command ATMIOC_CREATEPVC failed. The systemmessage (a standard system errno) indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to retrieve the options on the board, atmtest -O encountered a problem. The ioctl() command ATMIOC_GETOPT failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to retrieve the rate queue settings from the board, atmconfig -q encountered a problem. The ioctl() command ATMIOC_GETRATEQ failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to retrieve status information from the board, atmstat encountered a problem. The ioctl() command ATMIOC_GETSTAT failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to retrieve the virtual circuit table from the board, atmconfig -V encountered a problem. The ioctl() command ATMIOC_GETVCTAB failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to set the options on the board, atmtest -o encountered a problem. The ioctl() command ATMIOC_SETOPT failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to reconfigure the rate for the indicated rate queue (number), the driver encountered an error. The error (errornumber ) supplied by the board indicates the problem.

While attempting to retrieve the firmware version from the board, atmtest -V encountered a problem. The ioctl() command ATMIOC_VERS failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to retrieve the options on the board, atmstat -o encountered a problem. The ioctl() command ATMIOC_GETOPT failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to place a message on the IRIS ATM signaling software's queue, an error occurred because the message is not a known (recognized) type. This indicates incompatible IRIS ATM software modules. Use the inst utility to remove and reinstall all the IRIS ATM software.

The string specified with the -B option could not be resolved into an IP address. This could mean that the provided host name does not exist in the /etc/hosts file.

While performing the checksum on received data, atmtest discovered an error. The error is located at the indicated offset position.

While comparing the incoming data to the transmitted data, atmtest -Xrw -C discovered a difference (that is, an error). The hexnumeral specifies the problematic buffer.

While attempting to allocate memory to handle the outgoing data, atmtest's mpin() call failed. This indicates a problem with the operating system or the system. For example, the memory is totally occupied by other processes. Additional explanation for the systemmessage is available in the intro (2) man page. There is nothing wrong with the IRIS ATM software.

The -N option of atmtest expected an accompanying -Xwo or -Xrw. The -N option cannot be used for a VC opened for receiving (reading) only.

The argument for -N must be a multiple of 48.

While attempting to read the incoming data (that is, the data that was transmitted by atmtest -Xw), atmtest -Xr encountered an EINTR error caused by dropped (lost) packets on the VC and hardware unit (#) that are specified in the message. Use the atmstat command to discover the exact nature of the problem.

The -X option of atmtest expects one of the following arguments: ro (read-only VC), wo (write-only VC), or rw (read-write VC).

While attempting to download new firmware, atmconfig -l could not open the indicated file for reading. To resolve this, reinstall the IRIS ATM software.

While attempting to download new firmware, atmconfig -l could not read the header on the indicated file. To resolve this, reinstall the IRIS ATM software.

While attempting to download new firmware, atmconfig -l found that it could not read the indicated section (number) of the file containing the firmware. To resolve this, reinstall the IRIS ATM software.

While attempting to download new firmware, atmconfig -l could not skip the compiler's header on the indicated file containing executable firmware. To resolve this, reinstall the IRIS ATM software.

The setup call was rejected at the other endpoint or along the ATM network for the cause specified in the error message. ATM rejection causes are summarized in Table A-1, and Table A-2.

On the system running the SNMP browser application, verify that the ATM MIB and the standard MIB2 definition files (atmf_ilmi.mib and mib2) are installed in the appropriate directory for the MIB viewing application that you are using. When IRIS ATM is installed with inst, the ATM MIB file is automatically placed in the /usr/lib/netvis/mibs directory on the system running the IRIS ATM software. You can copy the definition file from the IRIS ATM station to the system running the browser application. The appropriate location for all MIB definition files for the NetVisualyzer and IRIXPro Browser applications is the /usr/lib/netvis/mibs directory. To perform this verification for the NetVisualyzer or IRIXPro applications, use the command below:

If the files are not listed (that is, it do not exist), copy them to the directory. If the files exist, verify that atmilmid is registered in the browser application system's /etc/snmpd.remote.conf file as a subagent to the main SNMP agent. The atm-ilmi entry in the snmpd.remote.conf file should be similar to the one shown below:

% grep atm-ilmi /etc/snmpd.remote.conf
1.3.6.1.4.1.353.2 IPaddress 23849 4 atm-ilmi

---

Note: This verification step must be done on the system where the SNMP viewing application (browser) is running. The IPaddress must identify the logical network interface on the system where the IRIS ATM ILMI software is running.

---

If this line exists, verify that the UDP socket (port) indicated in the snmpd.remote.conf entry matches the one specified in the /etc/config/atmilmid.options file, as explained in “Optional atmilmid Configuration” in Chapter 3, and that the IPaddress identifies the IRIS ATM logical network interface for the UNI in question.

If everything seems fine, kill and restart snmpd. If the problem persists, reinstall the IRIS ATM software and, if necessary, copy the ATM MIB file again to the system running the browser application. If the problem still persists, there is probably a problem with the SNMP MIB viewing application. Contact your support person for that application.

When atmconfig attempted to retrieve the current status for the board, an error occurred. The ioctl() command ATMIOC_GETSTAT failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to reconfigure the board with new operational options, atmconfig -o encountered a problem. The ioctl() command ATMIOC_SETOPT failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

When attempting to open a virtual circuit for one of the entries in the IP-to-ATM mapping file, atmconfig -Q was unable to configure a timer (rate queue). The ioctl() command ATMIOC_SETRATEQ failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

When ifatmconfig was attempting to bind the LIS (that is, the logical IP network interface) to the port specified on the command line, it encountered a problem. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to display information about an LIS, the ifatmconfig command could not retrieve the address of the ATMARP server. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

While attempting to display information about an LIS, the ifatmconfig command could not retrieve the ATM address assigned to the LIS. The ATMIOC_GETATMADDR ioctl() call failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to reconfigure the allocation of onboard memory, atmconfig -X or atmconfig -R, could not retrieve the current configuration from the board because the ATMIOC_GETCONF ioctl() call failed. This may indicate that the board is not responding. The systemmessage (a standard system errno) for the failure indicates what the problem is, as explained below. Additional explanation for the systemmessage is available in the intro(2) man page.

While attempting to display information about an LIS, the ifatmconfig command could not retrieve the cell rate used for traffic to that LIS. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

While attempting to display information about an LIS, the ifatmconfig command could not retrieve the port assigned to the LIS. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

While attempting to display information about an LIS, the ifatmconfig command could not retrieve the timeout for inactive VCs to that LIS. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

After assigning the requested VC timeout for an LIS, the driver was unable to read it back. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While trying to retrieve the current configuration from the board, atmconfig -s encountered an error. The ioctl() command ATMIOC_GETCONF failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to retrieve I/O driver statistics, atmconfig -d encountered a problem. The ioctl() command ATMIOC_GETIOSTAT failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2)man page. For more information on the use of the -d option, see “Changing the State of a Port” in Chapter 3, for Origin2000 or Onyx 2 systems, or “Changing the State of a Board” in Chapter 3, for Challenge or Onyx systems.

When atmstat attempted to open the device file for the indicated hardware unit (#), it did not find the file. This may indicate that the board was not located during the last power on, that the board is not active (UP), or that the IRIS ATM software was not installed correctly. The systemmessage (a standard system errno) provided in the message indicates the problem. Some system messages are described below; others are described in the man page for the open(2) system call.

When atmtest attempted to open the device file, it failed. This may indicate that the board was not located during the last power on, that the board is not active (UP), or that the IRIS ATM software was not installed correctly. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) and open(2) man pages.

While attempting to read the incoming data (that is, the same data that was transmitted by atmtest -Xw), atmtest -Xr encountered an error. The systemmessage (a standard errno) specifies the reason. Further explanation is available in the intro(2) and read(2) man pages.

When atmtest -Xro attempted to read incoming data, it failed. The systemmessage (a standard errno) specifies the reason. Further explanation is available in the intro(2) and read(2)man pages.

When ifatmconfig was attempting to assign the ATM ARP server for the LIS (that is, the logical IP network interface), it found that the interface was already configured and enabled. Use ifconfig down to disable it before trying again.

The driver was unable to assign the requested VC transmission rate to this logical network interface. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

The driver was unable to assign the requested VC timeout for an LIS. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

While attempting to write the transmit data to the ATM subsystem, atmtest -Xw encountered an error. The systemmessage (a standard errno) specifies the reason. Further explanation is available in the intro(2) and write(2) man pages.

When atmtest -Xwo attempted to write outgoing data, it failed. The systemmessage (a standard errno) specifies the reason. Further explanation is available in the intro(2) and write(2) man pages.

The attempt to download the indicated number of words ( count) to EEPROM address (08hexnumeral) did not succeed. The reason is provided in an adjacent error message.

The native-E.164 address that was entered contained invalid characters. Each entry must be a digit. A digit is any of the following characters: 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9.

The signaling software was unable to open a PVC on the hardware unit (port) indicated (#). The ATMIOC_CREATEPVC ioctl() call to the IRIS ATM driver failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

The signaling software was unable to open a PVC on the hardware unit indicated (#). The ATMIOC_CREATEPVC ioctl() call to the IRIS ATM driver failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

During an attempt to start up and build its stack, the signaling software encountered a problem and aborted the build. The problem is that the signaling software was unable to open a PVC on the hardware unit indicated ( #). The ATMIOC_CREATEPVC ioctl() call to the IRIS ATM driver failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

As the signaling software attempted to read incoming data on the indicated hardware unit (that is, device file dev/atm#) an error occurred, as described by the systemmessage. Additional explanation for the systemmessage is available in the intro(2) man page.

As the signaling software attempted to write outgoing data to the indicated hardware unit (that is, device file /hw/atm/#) an error occurred, as described by the systemmessage. Additional explanation for the systemmessage is available in the intro(2) man page.

While attempting to allocate memory to handle the outgoing data, the signaling software's mpin() call failed. This indicates a problem with the operating system or the system. For example, the memory is totally occupied by other processes. Additional explanation for the systemmessage is available in the intro (2) man page. There is nothing wrong with the IRIS ATM software.

The signaling software was unable to open a device file for the hardware unit indicated (#). The reason for the failure is provided in the systemmessage, for which additional explanation is available in the intro(2) man page.

During an attempt to start up and build its stack, the signaling software encountered a problem and aborted the build. The problem is that the device file for the indicated hardware unit (#) could not be opened due to the error indicated by the systemmessage . Additional explanation for the systemmessage is available in the intro(2) man page.

As the signaling software attempted to read incoming data on the indicated hardware unit (that is, device file /hw/atm/#) an error occurred, as described by the systemmessage. Additional explanation for the systemmessage is available in the intro(2) man page.

As the signaling software attempted to write outgoing data to the indicated hardware unit (that is, device file /hw/atm/#) an error occurred, as described by the systemmessage. Additional explanation for the systemmessage is available in the intro(2) man page.

While attempting to allocate memory to handle the outgoing data, the signaling software's mpin() call failed. This indicates a problem with the operating system or the system. For example, the memory is totally occupied by other processes. Additional explanation for the systemmessage is available in the intro (2) man page. There is nothing wrong with the IRIS ATM software.

The signaling software was unable to open a device file for the hardware unit indicated (that is, device file /hw/atm/#). The reason for the failure is provided in the systemmessage, for which additional explanation is available in the intro(2) man page.

This message does not necessarily indicate any error. This informational message is printed once for every 1000 transmitted packets. The xmit value indicates the number of packets transmitted, total indicates the number of packets atmtest has been asked to transmit and receive, and count indicates the number of packets that have been lost (transmitted but not received), so far.

When ifatmconfig was attempting to parse the ATM address for the LIS's ATMARP server, it discovered that the address is not valid. Follow the description of valid entries provided in Table 3-9, before trying again.

While processing a command line entry, the ifatmconfig command was unable to bind to a raw socket. This indicates a problem with the operating system (for example, it is overloaded). Nothing is wrong with the IRIS ATM software. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

While processing a command line entry, the ifatmconfig command was unable to open a raw socket. This indicates a problem with the operating system (for example, it is overloaded). Nothing is wrong with the IRIS ATM software. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

The ifatmconfig command could not open the specified filename that it believes is the LIS configuration file. Before trying again, verify that the file exists. The default name for this file is /var/atm/ifatm.conf. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

While processing the specified entry (linenumber) in the LIS configuration file (filename), the ifatmconfig command was unable to bind to a raw socket. This indicates a problem with the operating system (for example, it is overloaded). Nothing is wrong with the IRIS ATM software. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

While processing the specified entry (linenumber) in the LIS configuration file (filename), the ifatmconfig command was unable to open a raw socket. This indicates a problem with the operating system (for example, it is overloaded). Nothing is wrong with the IRIS ATM software. The systemmessage (a standard system errno) for the failure indicates what the problem is. Additional explanation is available in the intro(2) man page.

While processing the LIS configuration file (filename), the ifatmconfig command was unable to process an entry on the specified line (linenumber). It is probable that a value provided after one of the key words is invalid. To resolve the problem, edit the file as explained in “Address Resolution for SVCs” in Chapter 3.

While reading the LIS configuration file (filename), the ifatmconfig command encountered an illegal entry at the start of the specified line (linenumber). The first entry on each line must be the name of an IRIS ATM logical network interface (for example, atm0 or atm1). To correct the problem, edit the file as explained in “Address Resolution for SVCs” in Chapter 3.

While processing the LIS configuration file (filename), the ifatmconfig command encountered an illegal entry on the specified line (linenumber). To resolve the problem, edit the file as explained in “Address Resolution for SVCs” in Chapter 3.

The indicated command line entry (userentry) is not a valid entry.

While attempting to download new firmware, atmconfig -l found that the indicated section (number) of the file containing the firmware (filename) has an invalid address. To resolve this, reinstall the IRIS ATM software and restart the driver.

The driver was unable to associate itself with (“listen on”) an incoming VC, as requested by sigtest. The ioctl() command ATMIOC_LISTEN failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

The setup call was rejected at the location specified in the error message. ATM rejection locations are summarized in Table A-3.

This is not an error message. The message is only meant to warn you not to interrupt this process until the “Finished” message appears, since an interruption could cause corruption of the data on the board's EEPROM.

The driver was unable to set up the multipoint VC, as requested by sigtest. The ioctl() command ATMIOC_MPSETUP failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to display information about an LIS, the ifatmconfig command retrieved a null address for the ATMARP server. This probably indicates that the logical network interface specified on the command line has not been configured (in the /var/atm/ifatm.conf file) with an ATMARP server.

While attempting to display information about an LIS, the ifatmconfig command discovered that the ATM address is null. This means that the LIS does not have an assigned ATM address. If the adjacent switch supports address registration, this message indicates that there is a problem with the connection to the switch or with the switch itself. If the switch does not support address registration, configure this address by as explained in “Required atmilmid Configuration” in Chapter 3.

There are no IRIS ATM network interfaces available (that is, configured and enabled). Since the atmarp utility binds lower-layer services (virtual circuits) to the upper-layers (that is, the IP protocol stack), it requires an operational IRIS ATM network interface.

Use netstat -in to display the current configuration of network interfaces. If no IRIS ATM network interface (atm0, atm1, etc.) is configured and enabled, follow the instructions in “IP Network Interface Configuration” in Chapter 3, to remedy this condition. If no IRIS ATM network interface is listed, use versions to verify that the IRIS ATM software is installed, use autoconfig to build the driver into the operating system, then reboot to start using the new operating system.

While attempting to create a write-only VC for transmission, the open() call for a file descriptor to the IRIS ATM subsystem failed. This probably indicates a configuration or hardware availability problem. The reason for the failure is provided in the systemmessage, for which additional explanation is available in the intro(2) man page. There is nothing wrong with IRIS ATM.

The driver's attempt to start accepting data on an open, activated VC failed. That is, it could not open a new file descriptor to the device. The reason for the failure is provided in the systemmessage, for which additional explanation is available in the intro(2) man page.

When processing an interrupt from the board, the driver discovered a serious problem with its communication mechanism to the board. The command from the board (0xhexnumber) is not a recognized one. This may indicate a mismatch between the driver and board firmware versions. Follow the instructions in “Stopping and Restarting IRIS ATM” in Chapter 3, to reset the indicated board (unit) and then restart the driver. Restarting the driver with atmconfig causes the versions to be compared and a firmware update to be done if necessary.

When processing an interrupt from the board, the driver discovered a serious problem with its communication mechanism to the board. The driver expected the commands on the two communication queues to match (xcmd = b2h), however they did not. The actual commands encountered are displayed as hexadecimal numbers. Follow the instructions in “Stopping and Restarting IRIS ATM” in Chapter 3, to reset the indicated board (unit). If the problem persists, contact the Silicon Graphics Technical Assistance Center or the site's support engineer.

During startup, the driver was unable to allocate memory for use in maintaining status information for the indicated board (number ). This may indicate a problem with system memory. This does not indicate any problem with the IRIS ATM board or software.

The driver was unable to allocate memory for the IRIS ATM interface indicated (number). This indicates a problem with the operating system.

During startup, the driver was unable to allocate memory for use in managing information about the indicated board (number). This may indicate a problem with system memory. This does not indicate any problem with the IRIS ATM board or software.

During startup, the driver was unable to allocate memory for use in managing the communication interface to the indicated board ( number). This may indicate a problem with system memory. This does not indicate any problem with the IRIS ATM board or software.

During startup, the driver was unable to allocate memory for use in managing the communication interface to the indicated board ( number). This may indicate a problem with system memory. This does not indicate any problem with the IRIS ATM board or software.

During startup, the driver was unable to allocate memory for use in managing the communication interface to the indicated board ( number). This may indicate a problem with system memory. This does not indicate any problem with the IRIS ATM board or software.

When attempting to read a buffer containing incoming (received) data, the driver encountered an unknown buffer size (or type). The displayed number indicates the type of buffer encountered. This may indicate a mismatch between the versions of board firmware and operating system driver.

To remedy this, reinstall the IRIS ATM software, rebuild the operating system to include the new driver, and reboot the machine. The new driver may download new firmware onto the board during the reboot. If the problem persists, contact the Silicon Graphics Technical Assistance Center or the site's support engineer.

While attempting to display information about an LIS, the ifatmconfig command could not retrieve the port assigned to the LIS. This may indicate that the logical network interface specified on the command line has not been configured (in the /var/atm/ifatm.conf file) with a port.

When attempting to download firmware onto the board's EEPROM, atmconfig was unable to complete the task. The ioctl() command ATMIOC_STO failed. The pound sign ( #) indicates whether the error occurred on the first or second instance of this call. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to download new firmware, atmconfig -l could not read the indicated section (number) in the file containing the firmware. To resolve this, reinstall the IRIS ATM software.

The driver was unable to register to receive incoming VC requests, as requested by sigtest. The ioctl() command ATMIOC_REGISTER failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

An attempt to release an SVC failed. The hexadecimal number displayed indicates the local (software internal) identification number for that VC.

While attempting to download new firmware, atmconfig -l could not locate the indicated section (number) in the file containing the firmware. To resolve this, reinstall the IRIS ATM software.

While attempting to download new firmware, atmconfig -l found that the indicated section (number) of the file containing the firmware (filename) was larger than allowed (maxsize). To resolve this, reinstall the IRIS ATM software.

The driver was unable to set up the VC, as requested by sigtest . The ioctl() command ATMIOC_SETUP failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While preparing to send data, sigtest was unable to allocate (memalign) memory for its outgoing data. This indicates a problem with the operating system. For example, all memory is occupied by other processes. The reason for the failure is provided in the systemmessage, for which additional explanation is available in the intro(2) man page. There is nothing wrong with IRIS ATM.

While preparing to send data, sigtest was unable to lock down (mpin) enough memory to handle its outgoing data. This probably indicates that sigtest has exceeded its allowable limit for locked memory. The reason for the failure is provided in the systemmessage, for which additional explanation is available in the intro(2) man page. There is nothing wrong with IRIS ATM.

While attempting to read the MAC address from the board, atmconfig -m discovered the board does not have one. IRIS ATM cannot operate without a MAC address. Contact the Silicon Graphics Technical Assistance Center or the site's support engineer.

While attempting to download new firmware, atmconfig -l found that the indicated file has the indicated number of sections ( number), which exceeds the maximum number allowed. To resolve this, reinstall the IRIS ATM software.

While trying to initialize the board into the DOWN state, atmconfig -d encountered an error. The ioctl() command ATMIOC_CONTROL for initializing the board failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page. For more information on the use of the -d option, see “Changing the State of a Port” in Chapter 3, for Origin2000 or Onyx 2 systems, or “Changing the State of a Board” in Chapter 3, for Challenge or Onyx systems.

After downloading new firmware and resetting the board, atmconfig -d could not initialize the board. The ioctl() command ATMIOC_CONTROL for initialization failed.The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.For more information about the use of the -d option, see “Resetting a Port” in Chapter 3.

After downloading new firmware, atmconfig -d attempted to reset the board and encountered a problem. The ioctl() command ATMIOC_CONTROL for reset failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page. For more information about the use of the -d option, see “Resetting a Port” in Chapter 3.

While attempting to reset the board, atmconfig -r encountered a problem. The ioctl() command ATMIOC_CONTROL for reset failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to bring the board to the DOWN state, atmconfig -d found that the board was not in the pre-initialized state, so it attempted to reset the board. The ioctl() command ATMIOC_CONTROL for reset failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page. For more information about the use of the -d option, see “Resetting a Port” in Chapter 3.

When trying to put the board into the UP state, ifconfig -u encountered a problem. The ioctl() command ATMIOC_CONTROL for up failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to read the MAC address from the board, atmconfig -m encountered a problem. The ioctl() command ATMIOC_GETMACADDR failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

While attempting to retrieve the firmware version from the board, atmconfig -V encountered a problem. The ioctl() command ATMIOC_VERS failed. The systemmessage (a standard system errno) for the failure indicates what the problem is, as summarized in the following list. Additional explanation is available in the intro(2) man page.

The userentry is invalid. Use only digits displayed on the menu.

The userentry that was used for selecting a type of cellrate is not valid. Use only the digits displayed in the menu.

While attempting to write a MAC address into the board's FLASH EPROM, the command could not parse the indicated userentry that was supplied on the command line. The user entry must consist of 12 hexadecimal characters (0-9, a-f, or A-F) with or without separating colons and no blank spaces between the characters. For example, 09C8715AF983 and 09:c8:71:5a:f9:83 are both valid.

The user supplied an invalid userentry. The entry must be a digit (number): 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9.

The specified userentry is not an acceptable (valid) entry for the line. Use only the values described in the menu.

While attempting to read its configuration file, the signaling software was unable to parse an entry located on the indicated line ( linenumber). The message describes the nature of the problem. Due to this problem, the signaling software was not able to configure itself and start. To resolve this problem, edit the /var/tmp/atmsigd.tcl file as described in “Required atmsigd Configuration” in Chapter 3, then restart the IRIS ATM signaling software as described in Table 3-12.

While attempting to add or update an entry in the local ATMARP table, the driver encountered an error due to the table being already full. If the system is configured to perform as the ATMARP server for one or more LISs, it is possible that there are too many hosts. In this case, select a different system to be ATMARP server for a number of the LISs in order to remove the overload from this system. If the system is not an ATMARP server, ifconfig one or more logical network interfaces down or remove some entries from the IP-over-PVC address configuration file (/var/atm/pvc.conf ), in order to free space in the table.

While attempting to add an entry (IP address) for an ATMARP server to the local ATMARP table, the driver encountered an error due to the table being already full. If the system is configured to perform as the ATMARP server for one or more LISs, it is possible that there are too many hosts. In this case, select a different system to be the ATMARP server for a number of the LISs in order to remove the overload from this system. If the system is not an ATMARP server, ifconfig one or more logical network interfaces down or remove some entries from the IP-over-PVC address configuration file (/var/atm/pvc.conf), in order to free space in the table.

The IRIS ATM software received an ATMARP request for resolution of an IP-to-ATM address, however, this system is not configured as the ATMARP server for the LIS indicated (atm#). This probably indicates that some endpoint has been configured to use this station as its server. There is nothing wrong with the IRIS ATM subsystem.

The IRIS ATM software received an Inverse ATMARP request for resolution of an ATM-to-IP address, however, this system is not configured as the ATMARP server for the LIS indicated (atm#). This probably indicates that some endpoint has been configured to use this station as its server. There is nothing wrong with the IRIS ATM subsystem.

While attempting to add the results from an address resolution request to the local ATMARP table, the driver encountered an error due to the table being already full. If the system is configured to perform as the ATMARP server for one or more LISs, it is possible that there are too many hosts. In this case, select a different system to be ATMARP server for a number of the LISs in order to remove the overload from this system. If the system is not an ATMARP server, ifconfig one or more logical network interfaces down or remove some entries from the IP-over-PVC address configuration file (/var/atm/pvc.conf), in order to free space in the table.

While closing a transmit virtual channel, a problem occurred at the board level, and the VC could not be dismantled. The error ( number) supplied by the board indicates the nature of the problem. This message may indicate that an upper-layer control program asked the driver to tear down a VC that did not exist or that was only open for receiving (not for sending).

While closing a receive virtual channel, a problem occurred at the board level, and the VC could not be dismantled. This message may indicate that an upper-layer control program asked the driver to tear down a VC that did not exist or that was only open for transmitting (not for receiving).

During power up, two IRIS ATM boards were encountered that have the same unit number. This error can only occur when the following two conditions are true:

To remedy this problem do either one of the following: (1) edit the /var/sysgen/master.d/atm file to ignore the settings on the jumpers and reboot, or (2) remove one of the boards indicated in the error message and reconfigure its unit jumper setto a unique setting, as described in the hardware's installation instructions.

While processing an interrupt from the board, the driver discovered it could not clear the interrupt. This may indicate a problem with the board's GIO Interrupt Register. Use atmconfig to reset the board. If the problem persists, contact the Silicon Graphics Technical Assistance Center or the site's support engineer.

The board transmitted the final frame for a virtual circuit that the upper-layer control program has asked the driver to tear down. The driver's request for the board to free up the resources for that VC failed. The error (number) indicates the reason.

While waiting for the indicated board (number) to process a driver-to-board command, the driver waited long enough to believe that something is wrong with the board. The board did not process the command and a relatively long period of time passed. In many instances, subsequent error messages indicate more about the problem. The board may have encountered a problem that caused it to freeze or it may be dysfunctional.

Use the atmconfig command to transition the board from its current state to DOWN, and then to UP. If the problem persists, use atmconfig to reset the board. If this message is displayed again, shut down the system and turn off the power; then, power it on. If this message is displayed again, contact the Silicon Graphics Technical Assistance Center or the site's support engineer.

An error occurred during a transmission on the indicated board ( unitnumber). The error (errornumber) provides further details.

While attempting to bring the indicated board (number) to the initialized (DOWN) state, the driver was not able to initialize it. The board may have encountered a problem that caused it to freeze or it may be dysfunctional.

Invoke atmconfig -r to reset the board, then use atmconfig -d to manually put the board into the DOWN state. If this does not work, shut down the system and turn off the power; then, power it on. If this message is displayed again, contact the Silicon Graphics Technical Assistance Center or the site's support engineer. For more information on the use of these options, see “Changing the State of a Port” in Chapter 3, for Origin2000 or Onyx 2 systems, or “Changing the State of a Board” in Chapter 3, for Challenge or Onyx systems.

While passing new large-sized buffers to the board, a problem occurred and the buffers were not accepted by the board. The error supplied by the board (errornumber) indicates the problem.

While passing new medium-sized buffers to the board, a problem occurred and the buffers were not accepted by the board. The error supplied by the board (errornumber) indicates the problem.

While passing new small-sized buffers to the board, a problem occurred and the buffers were not accepted by the indicated board (digit ). The error supplied by the board (errornumber ) indicates the problem.

During startup, the driver failed to contact the DANG device on the ATM-OC3c board. This indicates a hardware problem. Contact the Silicon Graphics Technical Assistance Center or the site's support engineer.

While the driver was attempting to place a message on the IRIS ATM signaling software's queue, an error occurred. The affected packet is an IP packet. The specific message is S2D_REGRESPONSE. When status is a nonzero value, the message has failed to complete successfully. This may indicate a problem with atmsigd.

This is not an error message. The message is only meant to warn you not to interrupt this process since an interruption could cause corruption of the data on the board's EEPROM.

When sigtest wrote the outgoing data to its file descriptor, the call failed. The reason for the failure is provided in the systemmessage, for which additional explanation is available in the intro(2) man page. There is nothing wrong with IRIS ATM.