Use hinv to verify that the IRIS ATM board has been located by the operating system, as follows:

# /sbin/hinv
. . .

In a CHALLENGE or Onyx system (HIO board), the format of the hinv display is as follows:

ATM OC-3 unit unit#: slot slot#, adapter adapter#

The unit# option indicates the board's (port's) unit number, slot# indicates the slot in which the IO4 board resides, and adapter# (IO4 adapter) indicates the mezzanine position (5 indicates lower; 6 indicates upper) at which the ATM board resides.

---

Note: If the board is not listed, either (1) the system is running the wrong IRIX version, (2) the system has not been booted enough times, (3) the jumpers on the newly installed board have the same unit number as one of the listed ATM boards, or (4) the board is improperly installed. If no ATM board is listed, use the versions eoe1 command to verify the IRIX version number. If the version is incorrect, install the correct version, and reboot the system two times. If the version is correct or if other IRIS ATM boards are listed, reboot and watch the terminal for error messages. If the problem persists, reinstall the product (the board and all cables) making sure to set the IRIS ATM board's jumpers correctly and to set all the hardware firmly.

---

In an Origin2000 or Onyx2 system, the format of the hinv display is as follows:

ATM XIO 4 port OC-3c: module module#, slot slot#, unit unit# (ports: #-#)

The module# and slot# variables indicate the location (module and XIO slot) at which the board resides, unit# indicates the board's assigned unit number, and #-# indicates the range of numbers assigned to the four ports.

---

Note: If the board is not listed, either (1) the system is running the wrong IRIX version, (2) the IRIS ATM driver has not been built into the IRIX system by using the autoconfig command, or (3) the board is improperly installed. If no ATM board is listed, use the versions eoe and versions atm commands to verify the IRIX and IRIS ATM versions. If either image is incorrect or missing, install the correct version, and reboot the system. If the version is correct or if other IRIS ATM boards are listed, reboot and watch the terminal for error messages. If the problem persists, reinstall the product, making sure to set all the hardware firmly.

---

If the IRIS ATM board is listed, continue to the next step.

Use atmconfig as follows to verify that each port's MAC address is recognized:

# /usr/etc/atmconfig -i port# -m

MAC addr: ##:##:##:##:##:##

The port# indicates the port's identification number. For the HIO mezzanine board in a CHALLENGE or Onyx system, the port# is the same as the board's unit number.

If the MAC address is listed, continue to the next step.

---

Note: If the command was not located, the IRIS ATM software is not installed. If atmconfig displayed a message, look the message up in Chapter 5, “Troubleshooting and Error Messages”. If the display shows NULL for a MAC address, the IRIS ATM board is dysfunctional. Contact the Silicon Graphics Technical Assistance Center or the site's support engineer.

---

On a CHALLENGE or Onyx system, use atmstat as follows to verify that the board's rate queues are configured:

# /usr/etc/atmstat -i unit# -q

/hw/atm/#: interface HW state: UP
ATM interface rateq settings:
0: #### cells/s (#.## Mbps)
. . .

If the rates are listed and are correct, continue to the next step. The rates that are configured by default are listed in Table 3-5.

---

Note: If the command was not located, the IRIS ATM software is not installed. If atmstat displayed a message, look the message up in Table 3-5. If the displayed rates are not correct, reconfigure them as explained in Chapter 3, “IRIS ATM Configuration Reference”.

---

Use netstat as follows to verify that the IRIS ATM logical IP network interfaces are configured and enabled:

% /usr/etc/netstat -ina
. . .
atm0 9180 netaddress hostaddress . . .

If the IRIS ATM logical network interfaces are listed and enabled, continue to the next step.

---

Note: If no ATM logical network interface is listed, there is something wrong with the configuration of the software. Use the versions command to verify that the IRIS ATM software is installed, then use autoconfig and reboot one more time, in case you did not start using the newly built operating system that contains the IRIS ATM software. If an ATM interface is listed, but not configured correctly, verify your entries to the following files: /etc/hosts /etc/config/netif.options /etc/config/ifconfig-#.options /var/sysgen/master.d/if_atm If an interface that you expected is not listed, verify your entries in the /var/sysgen/master.d/if_atm file.

---

Use atmarp as follows to verify that the PVCs are loaded into the address resolution table. Entries for PVC connections have the flag PVC.

% /usr/etc/atmarp -a

IP address port VPI VCI flags
name         0    #  ##   PVC
name         0    #  ##   PVC NOSNAP

If there are no entries, follow the instructions in “Address Resolution for PVCs” in Chapter 3, to create and load entries.

Use ps as follows to verify that the ATM signaling and ILMI software are operating:

% /sbin/ps -ef | grep atm
root ... /usr/etc/atmsigd -d
root ... /usr/etc/atmilmid -p

If the two daemons are listed, continue to the next step.

---

Note: If the either or both daemons are not listed, one of the following problems might be the cause: (1) the missing module is not configured correctly or (2) the module was unable to contact the adjacent switch, so it terminated itself; this could indicate that the physical link is broken or missing, or that the switch is down. Solve the problem, then restart the daemons by following the instructions in “Stopping and Restarting IRIS ATM” in Chapter 3.

---

Use atmstat to verify that atmsigd and atmilmid each have opened their PVC for use in their own communications. The VPI/VCI values should match either the defaults (0/5 and 0/16) or the values given during the configuration process.

% /usr/etc/atmstat -i port# -V
VPI VCI rateQ/div/burst   flags
 0   16  B0 / 2 / 32     READ WRITE
 0    5  B0 / 2 / 32     READ WRITE
 <other VCs>
 number receive VCCs: 4   number forward VCCs: 4

Use ifatmconfig as follows to verify that the ATM addresses are known and that the LIS information is configured:

% /usr/etc/ifatmconfig atm#
atm#: (ATM addr: 0xATM_address)
port #

arpserver 0xATM_address
vcrate #bps bps
vctimeout #minutes minutes

If the all information is listed and correct, go to the next step.

---

Note: If an ATM address is not listed, use grep atm to search the SYSLOG file for atm error messages, then look them up in Chapter 5, “Troubleshooting and Error Messages”. Common causes for a missing ATM address include (1) the adjacent switch does not support address registration or (2) the /var/atm/ifatm.conf file could not be parsed during startup or did not contain an entry for the logical network interface.

---

Use atmarp to verify that the SVC to the ATMARP servers are open. Connections to ARP servers can be identified by the server's ATM address, as shown in the following example. The ATM address shown here should match the one displayed for arpserver in the previous step. The IP address for an ATMARP server is not necessarily known, and may not display.

% /usr/etc/atmarp -al
<IP address>   port VPI VCI    flags
IP_addr         #    #   ###   0x82 CONN
 ATM addr: 0xATM_address

The IRIS ATM configuration information appears to be complete and correct. You are finished with this verification procedure.

Perform the verification procedure described in “Verifying the Initial Configuration”.

If netstat lists some IRIS ATM network interfaces that are not configured or are disabled, this is only a problem if you expect these to be functional. The following tests can be performed on all enabled interfaces. If an interface that you want to test is configured with an IP address but has an asterisk after it, use ifconfig atm# up to enable it.

Verify that the system is physically connected to another ATM endpoint (for example, an ATM switch or another ATM network controller).

From the atmarp -a display, select one of the PVC destination IP addresses for a different ATM station. The network portion of the destination IP addresses must match the network portion of one of the local IP addresses (as displayed by the netaddress entry from the netstat display). Use the selected destination address in the following two verification procedures.

Use ping -r to contact the ATM station, as follows:

% /usr/etc/ping -r IPaddress
PING name (IPaddress): 56 data bytes
64 bytes from IPaddress: icmp_seq=0 ttl=254 time=2 ms
64 bytes from IPaddress: icmp_seq=1 ttl=254 time=3 ms
64 bytes from IPaddress: icmp_seq=2 ttl=254 time=5 ms
64 bytes from IPaddress: icmp_seq=3 ttl=254 time=2 ms
CNTL-C
----name PING Statistics----
4 packets transmitted, 4 packets recvd, 0% packet loss
round-trip min/avg/max = 2/3/5 ms

Use rcp (or rlogin) to verify that the basic, IP-based network utilities are functional, as follows:

% /usr/bsd/rcp guest@IPaddress:/path/filename .
% /sbin/ls
<filename should be listed>

Perform the verification procedure described in “Verifying the Initial Configuration”.

If netstat lists some IRIS ATM network interfaces that are not configured or are disabled, this is only a problem if you expect these to be functional. The following tests can be performed on all enabled interfaces. If an interface that you want to test is configured with an IP address but has an asterisk after it, use ifconfig.

Verify that the system is physically connected to an ATM switch.

Obtain the IP address or name of at least one other ATM station on the same subnetwork as the physical port you want to test. One method for doing this step is to list the destinations known to this system (as shown in the following), then select one of the addresses displayed:

% grep netaddress /etc/hosts

The netaddress variable specifies the nonmasked portion of the network address as displayed by the netstat command.

Use ping -r to contact the selected ATM station, as follows:

% /usr/etc/ping -r IPaddress

PING name (IPaddress): 56 data bytes
64 bytes from 150.166.76.26: icmp_seq=0 ttl=254 time=2 ms
64 bytes from 150.166.76.26: icmp_seq=1 ttl=254 time=3 ms
64 bytes from 150.166.76.26: icmp_seq=2 ttl=254 time=2 ms
64 bytes from 150.166.76.26: icmp_seq=3 ttl=254 time=2 ms

CNTL-C
----name PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2/2/3 ms

Use rcp (or rlogin) as follows to verify that the basic, IP-based network utilities are functional:

% /usr/bsd/rcp guest@IPaddress:/path/filename .
% /sbin/ls
<filename from other file system should be listed>

You can verify the creation of the SVC with the atmarp -aln command, which displays the address mappings for IP traffic. The single VC shown in the following example maps IP address 192.0.2.3 to ATM NSAP address 0x47.0005. The indicated VPI/VCI value was valid only for the first SVC to this address; subsequent SVCs to this address may use different VPI/VCI values.

% /usr/etc/atmarp -al
IP address   port VPI VCI flags
192.0.2.3     0    0  117 0x83 COMPL CONN
  ATM addr: 0x47.0005.80.ffe100.0000.f21a.024f.00204809006f.00