Chapter 2. Initial Configuration and Verification

This chapter explains the procedures that should be used to configure and verify IRIS ATM the first time it is started on a system. For subsequent configuration changes and for details of the procedures explained in this chapter, see the instructions in Chapter 3, “IRIS ATM Configuration Reference”.

The configuration steps in this chapter configure the product with default settings that allow it to be tested with the verification procedures described at the end of the chapter. The configuration that results from these procedures is a default. In many environments, the site's network administrator will need to alter the settings after the product has been verified.

Order for Performing Installation Steps

It is highly recommended that you use the following order to install and configure the IRIS ATM product:

  1. Use inst to install the new IRIS ATM software; the software image is named atm. Use of inst is explained in the IRIS ATM Release Notes and the IRIS Insight document Software Installation Administrator's Guide.

  2. Configure IRIS ATM, as explained in “Configuring IRIS ATM”.

  3. If not already done during the configuration steps, invoke the /etc/autoconfig command to build the IRIS ATM driver into the operating system.

  4. Power down the system and install the IRIS ATM hardware, as explained in the IRIS ATM\x15 OC3c Board for CHALLENGE and Onyx Installation Instructions or IRIS 4Port ATM\x15 OC3c XIO Board Installation Instructions.

  5. Power on the system.

  6. Verify the IRIS ATM subsystem, as explained in “Verifying IRIS ATM Functionality”.


Note: Failure to follow this order of installation steps will require additional reboots of the system. The hardware cannot be verified until the software is installed, configured, booted twice (or autoconfigured by using autoconfig, and booted).


Before You Begin Configuration

Before you begin the configuration, you should perform the following steps:

  1. Determine which functionalities your system needs to support.

  2. Collect configuration information.

  3. Review required configuration tasks.

The following sections offer guidelines for performing these steps.

Determining System Functionalities

This product can be configured to support any or all of the functionalities listed in this section. Before you begin the configuration, you should determine which of the following functionalities your system needs to support:

  • IP applications over switched virtual circuits (SVCs) in compliance with RFC 1577

  • Non-IP applications (developed by the customer) over SVCs

  • IP applications over permanent virtual circuits (PVCs)

  • Non-IP applications (developed by the customer) over PVCs

Collecting Configuration Information

Before starting the installation and configuration, collect the following information that is required during the configuration procedures. Space is provided in this section for you to record the information.

After you have collected the configuration information, follow the steps in “Configuring IRIS ATM”, to configure the IRIS ATM subsystem.

  1. Will this system use the IP (also called TCP/IP) protocol over any of its ATM ports? If yes, determine how many IP-over-ATM logical network interfaces (atm#) are needed and obtain an IP address for each one. For IP-over-ATM, it is possible to configure multiple interfaces per physical port; specifically, there can be one interface for each logical IP subnetwork (LIS). The ATM subsystem can support up to 64 logical network interfaces.

    atm0______________________________________

    atm______________________________________

    atm______________________________________

    atm______________________________________

  2. Will this system use PVCs? If it will, obtain the IP address and a VPI/VCI value for one or more ATM endpoints with which this system will be communicating. Also determine which port number (as displayed by the hinv command) will support each of these channels.

    ____________________________ / ______port__

    ____________________________ / ______port__

    ____________________________ / ______port__

    ____________________________ / ______port__

    If any of these PVCs needs LLC/SNAP encapsulation disabled, mark that PVC's line with an n. In compliance with RFC 1577, IRIS ATM does LLC/SNAP encapsulation and Inverse ARP responses by default. IRIS ATM does not generate Inverse ARP requests.

  3. Will this system use SVCs? If it will, obtain the following information:

    • For each IP-over-ATM logical network interface (atm#) that will use SVCs, obtain the ATM address (either ATM NSAP or native E.164) of the ATM address resolution server:

      atm______________________________________

      atm______________________________________

      atm______________________________________

      atm______________________________________

    • For each physical port (number displayed by hinv), find out which version of the ATM UNI (3.0 or 3.1) the attached switch supports for service specific convergence protocol (SSCOP) and Q.2931:

      port0SSCOP=____Q.2931=____

      port1SSCOP=____Q.2931=____

      port2SSCOP=____Q.2931=____

      port3SSCOP=____Q.2931=____

    • For each port, does the adjacent switch perform ILMI address registration, or will you need to assign the system its ATM address on that port? (There should be one switch for each IRIS ATM physical port.) If all the switches do address registration, skip to the next step. For ports that you need to assign the ATM address, obtain either a native E.164 or an ATM NSAP address.

      port0_________________________________________

      port1_________________________________________

      port2_________________________________________

      port3_________________________________________


      Note: If no switch is attached to a port, follow the instructions in “Enabling an ATM Port to Function in a Configuration without a Switch” in Chapter 3.


Reviewing Required Configuration Tasks

Table 2-1, lists the configuration tasks that must be performed after the new IRIS ATM software has been installed, but before IRIS ATM is started for the first time and its functionality verified. The IRIS ATM subsystem cannot function until these tasks have been completed. Brief instructions for all of these tasks are provided in “Configuring IRIS ATM”.

Table 2-1. Required Configuration Tasks

 

Item to configure

Section where complete instructions are located

For IP traffic over ATM:

 

 

 

IP addresses and names

“Mapping Names to IP Addresses: The /etc/hosts File” in Chapter 3

 

Network interface to IP address mappings

“Mapping IP Addresses to Network Interfaces: The netif.options File” in Chapter 3

 

ATM-to-IP address mappings (address resolution)

“Mapping IP Interfaces to the ATM Subsystem” in Chapter 3

For SVCs only:

 

 

 

ATM UNI and signaling

“Required atmsigd Configuration” in Chapter 3

 

ILMI module

“Required atmilmid Configuration” in Chapter 3

After these required configuration tasks have been performed, the IRIS ATM subsystem operates with default settings, some of which may not be suitable for your purposes. After performing the verification tests, if you need to alter the default parameters, follow the more complete instructions provided in Chapter 3, “IRIS ATM Configuration Reference”, to configure the system with different settings.

Configuring IRIS ATM

Follow the procedures in this section to configure the IRIS ATM product the first time it is installed and before it is run. The product is not operational until it is configured as described in this section.

  1. Locate the inst image for the new version of IRIS ATM. Then, use inst to install it, as illustrated in the following command lines:

    # inst
    Inst> from location_of_image
    Inst> install atm
    Inst> go

  2. For systems requiring more than four IP-over-ATM network interfaces, edit the /var/sysgen/master.d/if_atm file to configure the number of ATM logical network interfaces needed. As shown in the following example, change the ifatm_n_ifnets= line to replace the default value (4) with a decimal number to indicate the number of interfaces your system requires. Complete instructions are provided in “IRIS ATM IP Driver Configuration” in Chapter 3.

    Change from this:

    ifatm_n_ifnets=4

    To this:

    ifatm_n_ifnets=decimal_number

  3. For systems requiring IP-over-ATM, edit the /etc/hosts file to configure an IP address and name for each ATM logical network interface. Complete instructions are provided in “Mapping Names to IP Addresses: The /etc/hosts File” in Chapter 3.

  4. For systems requiring IP-over-ATM, edit the /etc/config/netif.options file to map each network interface (including atm0) to an IP address. Complete instructions are provided in “Mapping IP Addresses to Network Interfaces: The netif.options File” in Chapter 3.

  5. For CHALLENGE or Onyx systems (only) exchanging constant bit rate (CBR) traffic, if any particular rates need to be always available, edit the /var/atm/atmhw.conf file to configure these permanent rates. Complete instructions are provided in “Changing the Runtime Rates on Transmission Queues” in Chapter 3.

  6. For systems using IP-over-PVCs, edit the /var/atm/pvc.conf file to map each remote endpoint (IP address) to an ATM virtual channel address and an ATM port. If the channel does not use LLC/SNAP encapsulation, place an n in the flags column. Each entry should have the following format. Complete instructions are provided in “Address Resolution for PVCs” in Chapter 3.

    Format:

    IPaddress  port#   vpi   vci   fflags

    Example:

    223.16.8.1  0  1  35


    Note: You do not need to add the PVCs used by ATM signaling and ILMI. The IRIS ATM software does this automatically.


  7. For systems using IP-over-SVCs, edit or create a /var/atm/ifatm.conf file to map each IP-over-SVC logical network interface to an ATM port and an ATM address resolution server. Each entry should have the following format. Complete instructions are provided in “Address Resolution for SVCs” in Chapter 3.

    Format:

    atm# port # arpserver NSAP_address

    Example:

    atm0 port 0 arpserver 0x390840001122334455667788990d000122003300


    Note: To make this station operate as the ATMARP server for the LIS in which atm# is a member, add the first two items in the line but do not specify arpserver. After completing the configuration and rebooting the system, edit this file again to add the arpserver portion of the line, as described in “Address Resolution for SVCs” in Chapter 3.


  8. For systems using SVCs, edit the /var/atm/atmsigd.tcl file to configure the UNI versions used on each port. The versions (for SSCOP and Q.2931 signaling) must match those used by the adjacent switch. For each port, remove the pound sign (#) from one line in the file or create new lines, as shown in the following example. Complete instructions are provided in “Required atmsigd Configuration” in Chapter 3.

    Format:

    buildstack identification# /hw/atm/# version_SSCOP version_Q.2931

    Change from this:

    buildstack 1 /hw/atm/0 AF30 AF30
    # buildstack 1 /hw/atm/0 AF30 AF31
    # buildstack 1 /hw/atm/0 AF31 AF31
    
    # buildstack 2 /hw/atm/1 AF30 AF30
    # buildstack 2 /hw/atm/1 AF30 AF31
    # buildstack 2 /hw/atm/1 AF31 AF31
    
    # buildstack 3 /hw/atm/2 AF30 AF30
    # buildstack 3 /hw/atm/2 AF30 AF31
    # buildstack 3 /hw/atm/2 AF31 AF31

    To something like this:

    buildstack 1 atm0 AF30 AF30
    # buildstack 1 atm0 AF30 AF31
    # buildstack 1 atm0 AF31 AF31
    
    # buildstack 2 atm1 AF30 AF30
    buildstack 2 atm1 AF30 AF31
    # buildstack 2 atm1 AF31 AF31
    
    buildstack 3 atm2 AF30 AF30
    # buildstack 3 atm2 AF30 AF31
    # buildstack 3 atm2 AF31 AF31
    
    # buildstack 4atm3 AF30 AF30
    # buildstack 4atm3 AF30 AF31
    buildstack 4atm3 AF31 AF31

  9. For systems using SVCs, edit the /var/atm/atmilmid.conf file to configure the ILMI module for each physical port (that is, each ATM-OC3c board). For any port attached to a switch that does not register ATM addresses, also add an ATMADDRESS line to assign the system its ATM address. Complete instructions are provided in “Required atmilmid Configuration” in Chapter 3.

    Format:

    ATMPORT port_index  devname  VPI  VCI
    
    ATMADDRESS port_index  ATM_address

    Example:

    ATMPORT  1  /hw/atm/0  0 16
    ATMPORT  2  /hw/atm/1  0  16
    ATMPORT  3  /hw/atm/2  0  16
    ATMPORT  4  /hw/atm/3  0  16
    ATMADDRESS 1 47000580ffe1000000f115098d080069042a4f00

  10. Invoke the /etc/autoconfig -f command to build the IRIS ATM driver into the operating system that will be loaded at the next startup.

The system is now ready to shut down and install the hardware. If the hardware is already installed, reboot the system now. Once the hardware is installed and the system is powered on, follow the instructions in “Verifying IRIS ATM Functionality” to verify that the ATM subsystem is functional.

Verifying IRIS ATM Functionality

The following sections describe procedures for verifying the functionality and configuration of an IRIS ATM subsystem. Do all of the procedures described in each section that are appropriate for your configuration, as described in the introductory paragraph for each set of verification steps.

Verifying the Initial Configuration

This procedure verifies that the basic configuration information about the IRIS ATM subsystem is correct. Do these steps immediately after the initial installation, configuration, and startup. Skip any steps intended for a configuration that does not apply.

  1. Log on to the system and become super user (root).

Verify the Board Configuration

  1. 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.

  2. 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.


  3. 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”.


Verify IP Configuration

  1. 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.


Verify IP-over-PVC Configuration

  1. 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.

Verify IP-over-SVC Configuration

  1. 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.


  2. 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

  3. 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.


  4. 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

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

Verifying the ATM Signaling Protocol Stack with sigtest

The sigtest utility verifies that the IRIS ATM signaling software is functional. Do these steps immediately after the initial installation, configuration, and startup. This test requires that the system be connected to an ATM switch. For complete information about the parameters used during this test, see Table 2-2.

  1. Before starting this verification procedure, complete the verification procedure described in “Verifying the Initial Configuration”.

  2. Open two shell windows and become super user (root).

  3. Disable each ATM logical network interface that is serviced by the port you want to test, using the following command line:

    # /usr/etc/ifconfig atm# down

    The atm# variable is replaced with each enabled logical network interface.

  4. In one window, make the ATM subsystem register with the switch for receiving SVC setup requests, using the following command lines to specify the traffic contract:

    # /usr/lib/atm/bin/sigtest /hw/atm/port#
    [0] Quit
    [1] Register to accept incoming calls
    [2] Attempt to setup a point-to-point call
    [3] Attempt to setup a point-to-multipoint call
    Enter choice: 1
    
    Enter fwdMaxCSDU size: 9180
    
    Enter bwdMaxCSDU size: 8192
    
    Enter blliCode: 1

    The registration is successful when the following message appears:

    Registering for BLLI=1, fwd/bwdMaxCSDU=9180/8192
    Registration successful.


    Note: If the registration fails, look up the cause number in Table A-1, or Table A-2, or the error message in the alphabetical listing in Chapter 5, “Troubleshooting and Error Messages”.


  5. In the other window, use the values shown in the following command lines to run a test that verifies the atmsigd command's ability to transmit and receive over a point-to-point SVC for best-effort traffic with the specified traffic contract. In the following example, values shown in italics are values that you need to create, values in bold should be entered exactly as illustrated, and text within <angle brackets> is displayed by sigtest.

    # /usr/lib/atm/bin/sigtest   /hw/atm/port#
    [0] Quit
    [1] Register to accept incoming calls
    [2] Attempt to setup a point-to-point call
    [3] Attempt to setup a point-to-multipoint call
    Enter choice: 2
    Using calling address: address type = <type>
        Address =  <local ATM address is displayed>
    Enter called address:
        Address type [1 for E164, or 2 for NSAP]: type_from_above
        Enter a string of exactly 40 hex characters:
                  ATMaddress_copied_from_line_above
    Enter fwdMaxCSDU size: 12280
    Enter bwdMaxCSDU size: 2048
    Enter number of BLLIs to offer [valid range 0-3]: 1
    Enter blli 1: 3
    Enter bearerClass: 3
    Enter Forward Cell Rate
      Enter Cellrate type: 7
      Enter Peak Cell Rate for CLP 0+1: 357142
    Enter Backward Cell Rate
      Enter Cellrate type: 7
      Enter Peak Cell Rate for CLP 0+1: 178571
    Enter forwardQoS [0 - 4]: 0
    
    Enter backwardQoS [0 - 4]: 0
  6. Verify that the test succeeded by comparing your terminal display with the following examples, which illustrate the wording that appears in each window when the test is successful. In the transmitting window, you see the following lines:

    Setup successful, negotiated fwd/bwdCSDU = 9180/2048
    (1) Wrote 9180 bytes
    (2) Wrote 9180 bytes
    . . .
    (9) Wrote 9180 bytes
    (10) Wrote 9180 bytes

    In the receiving window, you see these lines. Notice that the receiver's transmission cell rate matches the value you entered for the backward (returning VC) cell rate. In contrast, the convergence sublayer data units (CSDU) values are expressed from the transmitter's point of view.

    Listen successful:
      userHandle = 0x#, callHandle = #
      fwdMaxCSDU = 9180, bwdMaxCSDU = 2048
      BLLI = 3
      Xmit Cell Rate : cellrate spec. type = BEST EFFORT
      Peak Cell Rate for CLP 0+1 = 178571
      Caller Address : address type = NSAP
      Address = 47000580ffe1000000f115098d080069042aca00
    Accepted connection!!
      Received 9180 bytes
      Received 9180 bytes
       . . .
       Received 9180 bytes
       Received 9180 bytes
    Read 10 CSDUs for a total of 91800 bytes
  7. In the receive window, again make the ATM subsystem register with the switch for receiving SVC setup requests, using the following command lines:

    Enter choice: 1
    Enter fwdMaxCSDU size: 12280
    Enter bwdMaxCSDU size: 4096
    Enter blliCode: 1

    The registration is successful when this message appears:

    Registering for BLLI=1, fwd/bwdMaxCSDU=12280/4096
    Registration successful.
  8. In the transmit window, run another test, using the values shown below, to verify the atmsigd command's ability to transmit and receive over a point-to-point VC for constant bit rate (CBR) traffic.

    Enter choice: 2
    Using calling address: address type = <type>
      Address =  <local ATM address is displayed>
    Enter called address:
       Address type [1 for E164, or 2 for NSAP]: type_from_above
       Enter a string of exactly 40 hex characters:
            ATMaddress_copied_from_line_above
    Enter fwdMaxCSDU size: 12280
    Enter bwdMaxCSDU size: 512
    Enter number of BLLIs to offer [valid range 0-3]: 0
    Enter bearerClass:  4
    Enter Forward Cell Rate
       Enter Cellrate type:  3
       Enter Peak Cell Rate for CLP 0+1: 14534
    Enter Backward Cell Rate
       Enter Cellrate type:  3
       Enter Peak Cell Rate for CLP 0+1: 9259
    Enter forwardQoS [0 - 4]:  1
    Enter backwardQoS [0 - 4]: 1

    Note: On a CHALLENGE or Onyx system, the cell rate values used in this test assume that the IRIS ATM board is configured with default settings. If the high-priority transmission rate queues have been configured with different settings, replace the cell rates used in the test with values that are currently configured, as reported by atmstat -q.


  9. Verify that the test succeeded. When the test is successful, you see the following displays in the two windows. In the transmitting window:

    Setup successful, negotiated fwd/bwdCSDU = 12280/512
    (1) Wrote 12280 bytes
    (2) Wrote 12280 bytes
    . . .
    (9) Wrote 12280 bytes
    (10) Wrote 12280 bytes

    In the receiving window:

    Listen successful:
     userHandle = 0x#, callHandle = #
      fwdMaxCSDU = 12280, bwdMaxCSDU = 512
      BLLI = 0
      Xmit Cell Rate : cellrate spec. type = PEAK AGGREGATE
      Peak Cell Rate for CLP 0+1 = 9259
      Caller Address : address type = NSAP
      Address = 47000580ffe1000000f115098d080069042aca00
    Accepted connection!!
      Received 12280 bytes
      Received 12280 bytes
      . . .
      Received 12280 bytes
      Received 12280 bytes
    Read 10 CSDUs for a total of 122800 bytes
  10. If you wish, you may perform additional verification by selecting other sigtest menu options and testing with other values. Table 2-2, summarizes the meanings and IRIS ATM support for the various parameters. Be aware that not all switches support the full range of options that this test makes available.

    Table 2-2. Variables for the sigtest Utility

    Item in sigtest prompt

    Value

    Description

    Supported for use with sigtest

    maxCSDU:

     

    Maximum byte size for ATM AAL5 convergence sublayer data units, represented in decimal format. Supported range is 0 through 65,535.

    Y

    BLLI:

     

    Broadband low-layer information for verification of protocol stack match at OSI layers 2 and 3 between endpoints.

     

     

    0

    Null.

    Y

     

    1

    Accept any. Only valid for receiving VC.

    Y

     

    2

    Level 2 LLC (SNAP).

    N[a]

     

    3

    LAN Emulation control.

    Y

     

    4

    LAN Emulation 802.3 data.

    Y

     

    5

    LAN Emulation 802.3 multicast.

    Y

     

    6

    LAN Emulation 802.5 data.

    Y

     

    7

    LAN Emulation 802.5 multicast.

    Y

    Cellrate type:

     

     

     

     

    0

    Null.

    N

     

    1

    Peak.

    N

     

    2

    Peak Tagged.

    N

     

    3

    Peak Aggregate.

    Y

     

    4

    PSB(peak cellrate, sustainable cellrate, maximum burst size).

    N

     

    5

    PSB Tagged.

    N

     

    6

    PSB Aggregate (peak cellrate, sustainable cellrate, maximum burst size).

    Y

     

    7

    Best Effort.

    Y

    peak cellrate:

     

    Cells per second represented in decimal format for the peak transmission rate. For CBR, if the high-priority rate queues are configure with non-default values, the forward peak rate must exactly match a configured rate queue as displayed by atmstat -q.

    Y

    sustainable cellrate:

     

    Cells per second represented in decimal format for the sustained (average) transmission rate. The value must be less than the peak cell rate defined for this VC. Software rounds up the entry to the next supported rate.

     

    burst size:

     

    Cell count represented in decimal format for the maximum size of a transmission burst (that is, a tightly packed sequence of cells). Must be between 32 and 2048. Value entered is rounded up to a multiple of 32.

     

    bearerClass:

     

     

     

     

    1

    Bearer class A (BCOB-A).

    Y

     

    2

    Bearer class C (BCOB-C).

    Y

     

    3

    Bearer class X (BCOB-X) with unspecified, best-effort traffic type.

    Y

     

    4

    Bearer class X (BCOB-X) with CBR traffic type.

    Y

     

    5

    Bearer class X (BCOB-X) with VBR traffic type.

    N

    QoS:

     

     

     

     

    0

    Quality of service class 0; unspecified, best effort.

    Y

     

    1

    Quality of service class 1; Service Class A / CBR.

    Y

     

    2

    Quality of service class 2: Service Class B / VBR.

    Y

     

    3

    Quality of service class 3; Service Class C / Connection-oriented data.

    Y

     

    4

    Quality of service class 4: Service Class D / Connectionless data.

    Y

    [a] Level 2 LLC requires that each CSDU (packet) contain a valid SNAP header. The IRIS ATM driver creates these when servicing IP traffic, but does not support this for sigtest.


Verifying IP over ATM Functionality

This section describes procedures for verifying that the IRIS ATM subsystem is servicing IP-based upper-layer applications. Separate instructions are provided for IP-over-PVC and IP-over-SVC. Follow both procedures if your system uses both PVCs and SVCs; otherwise, follow the set of procedures that is appropriate. At a minimum, the following configuration procedures must be performed before this verification procedure is tried:


Note: The procedures described in the following sections do not troubleshoot the IRIS ATM board. Hardware verification is explained in the IRIS ATM\x15 OC3c Board for CHALLENGE and Onyx Installation Instructions and in “Verifying the IRIS ATM Hardware using atmtest”.


Verify IP-over-PVCs

Perform the following steps to verify that IP-over-PVC applications can transmit and receive through the IRIS ATM subsystem.

  1. 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.

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

  3. 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.

  4. 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
  5. 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>

Verify IP-over-SVCs

Perform the following steps to verify that IP applications can transmit and receive through the IRIS ATM signaling subsystem.

  1. 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.

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

  3. 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.

  4. 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
  5. 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>
  6. 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

Verifying the IRIS ATM Hardware using atmtest

The atmtest utility verifies that the IRIS ATM port is functional. Perform this test when you suspect something is wrong with the hardware.

This test requires that the problematic port be physically connected to any of the following:

  • To a switch. The local port's PVC to the switch (default address is VPI=0, VCI=201) must be mapped, at the switch, to an outgoing PVC that returns to the same local port.

  • Directly to another IRIS ATM port, on the same or a different system. No switch exists between the two systems. The port must be reconfigured via the atmconfig command so that it recovers the clock from its own transmit clock signal:

    # atmconfig -i /hw/atm/port# -du
    # atmconfig -i /hw/atm/port# -o 0

    For more information about the use of the -du option, see “Changing the State of a Board” in Chapter 3.

  • To itself with a low-loss loopback test connector (sold as an FDDI station testing device). The type of connector must be appropriate for the port you are testing (for example, MIC or dual-SC). Figure 2-1, shows an example of this type of device. The port must be reconfigured with the atmconfig command so that it generates the transmit clock from its own clock signal:

    # atmconfig -i /hw/atm/port# -du
    # atmconfig -i /hw/atm/port# -o 0

  • On a CHALLENGE or Onyx system only, to itself with a loopback cable assembly that consists of a MIC-to-ST dual fiber optic cable with an adapter for connecting the two ST connectors to each other, as shown in Figure 2-2. The port must be reconfigured with the atmconfig command so that it generates the transmit clock from its own clock signal:

    # atmconfig -i /hw/atm/port# -du
    # atmconfig -i   /hw/atm/unit# -o 0


    Caution: Use the following command to reconfigure the port back to normal once the loopback cable is removed. Failure to do this causes the board to malfunction for normal switch use.


    # atmconfig -i /hw/atm/port# -o 1

    Figure 2-1. Loopback or Test Cable Assembly for Dual-SC Connector

    Loopback or Test Cable Assembly for Dual-SC Connector

    Figure 2-2. Loopback Cable Assembly and Adapter for MIC Connector

    Loopback Cable Assembly and Adapter for MIC Connector

To verify that the IRIS ATM port is functional, follow these steps:

  1. Make sure that the port is physically connected by one of the loopback methods explained previously.

  2. As super user, use the following command line to invoke atmtest to transmit and receive through one IRIS ATM port using default settings for VPI/VCI and rate. Invoke this command once for each port.

    # /usr/etc/atmtest -i /hw/atm/port# -Xrw &

    The port# variable indicates the port's assigned number or, on a CHALLENGE or Onyx system, the board's unit number.

    The resulting display should indicate success with wording similar to the following example. You can terminate the test at any time by pressing Ctrl-C.

    atmtest: /hw/atm/port#:
    vpi/vci = 0 201 xmit-rate: 68.57 Mbps
    - 1000/10000 frames transmitted, total 0 lost
    . . .
    --- 10000 frames transmitted, 0 lost ---

  3. Invoke atmtest to test a number of different transmission rates, using the following command lines. On a CHALLENGE or Onyx system, you can test each of the transmission rates configured on the board's rate queues; use the atmstat command to display the rates. (See “Rates on the ATM-OC3c HIO Board for CHALLENGE and Onyx Platforms” in Chapter 1, for detailed information on rate queues.) On an Origin or Onyx2 system, you may test any rate you want. With each invocation of atmtest, you specify a different rate in bits per second. As the test precedes, it displays its progress. You can kill each test, at any time, by simultaneously pressing the Ctrl and c keys. Use this format:

    # /usr/etc/atmtest -i /hw/atm/port# -ebitspersecond &

    Each entry has the following meaning:

    • The port# variable specifies a port number displayed by /sbin/hinv for an IRIS ATM board. On a CHALLENGE or Onyx system, use the board's unit number as the port number.

    • The bitspersecond variable specifies a decimal number indicating the speed in user payload bits per second at which the data is to be transmitted. On a CHALLENGE or Onyx system, this must match one of the rates supported by the board; use the atmstat -i port# -q command to list the currently configured rates.

    For example:

    # /usr/etc/atmtest -i /hw/atm/0 -Xrw -e10000000
    atmtest: /hw/atm/0:
    vpi/vci = 0 201 xmit-rate: 10.00 Mbps Best Eff
    - 1000/10000 frames transmitted, total 0 lost
    ...
    # /usr/etc/atmtest -i /hw/atm/port# -Xrw -e30000000
    # /usr/etc/atmtest -i /hw/atm/port# -Xrw -e68000000
    # /usr/etc/atmtest -i /hw/atm/port# -Xrw -e135991460

  4. When you are finished testing and ready to reattach the system to its switch, use this command to reconfigure the port back to normal:

    # atmconfig -i /hw/atm/port# -o 1