2    Configuring the ATM Software

After you install the DIGITAL DGLTA adapter and DIGITAL UNIX ATM subsets, you must configure the software in order to communicate on the ATM network to which the system is connected. This chapter describes the DIGITAL UNIX ATM network environment and how to configure the ATM subsystem. In addition, this chapter describes the commands for managing the ATM subsystem and contains a diagnostic map to help you isolate any problems that might occur.

2.1    ATM Environment

An ATM network consists of the following:

• Switch

  A specialized system that maintains a list of virtual channel identifiers (VCIs) and virtual path identifiers (VPIs), connects one end system to another, and forwards or switches ATM cells from one end system to another based on the VCI/VPI information contained in the cell

• End system

  A system physically connected to a switch that communicates with other end systems through the switch

In the DIGITAL UNIX ATM environment, the following configurations are possible:

• Classical Internet Protocol (CLIP)

• Local Area Network (LAN) emulation

• IP switching

The following sections describe each of these configurations and the roles of systems in each.

2.1.1    Classical IP Environment

The Classical IP environment, as described in RFC 1577, provides a basic means for carrying unicast IP traffic over ATM networks. In this environment, hosts that can communicate with each other are grouped into a Logical IP Subnetwork (LIS). An ATM network can contain multiple LISs. In a LIS, all hosts and routers have the following requirements:

• Have the same IP network/subnetwork number and mask.

• Are directly connected to the ATM network.

• Access members outside the LIS through a router.

• For switched virtual circuits (SVCs), use Address Resolution Protocol (ARP) to resolve IP protocol addresses to ATM hardware addresses. For SVCs and permanent virtual circuits (PVCs), use Inverse ARP to resolve ATM hardware addresses to IP protocol addresses.

• Can communicate with all other members in the same LIS (mesh topology).

Figure 2-1 shows an ATM network with two LISs. Host A and Host B are members of LIS 1; Host C, Host D, and Host E are members of LIS 2. The figure also shows a virtual circuit (VC) between Host A and the router and between Host E and the router. Although these hosts are connected to the same switch and might establish a VC for communications between each other, they cannot because all communications to a member of another LIS must go through a router.

Figure 2-1:  Classical IP over an ATM Network

2.1.2    LAN Emulation Environment

The LAN Emulation (LANE) environment, as defined by the ATM Forum, groups hosts into an entity called an emulated LAN. A LANE environment has the following characteristics:

• Identifies hosts through their 48-bit media access control (MAC) addresses

• Supports multicast and broadcast services either through point-to-multipoint connections or through a multicast server, unlike the Classical IP environment

• Supports any protocol that uses an IEEE broadcast LAN

Figure 2-2 shows an ATM network with two emulated LANs. Host A and Host B are LAN Emulation Clients (LECs) on ELAN1. Host C, Host D, and Host E are LECs on ELAN2. The LECS (LAN Emulation Configuration Server), the LES (LAN Emulation Server), and the BUS (Broadcast and Utility Server) are depicted as two separate systems, although these server functions are typically resident on an ATM switch.

Figure 2-2:  Emulated LAN over an ATM Network

2.1.3    IP Switching

The IP switching environment consists of one or more hosts connected to an IP switch. Each host is connected to the IP switch through a point-to-point physical connection, with each physical connection as a separate subnet. Communication between the host and the IP switch occurs over dynamically created PVCs.

The IP switch is a typical ATM switch with added IP controller software that performs IP routing and IP traffic classification functions. In this environment, a series of packets from one host to another with the same protocol type, type of service, and other characteristics indicated in the packet header is called a flow. When the IP controller identifies a flow that is of long duration, it instructs the ATM switch to make the appropriate hardware connections and to forward the ATM cells directly to the destination, bypassing the IP controller. This increases throughput at the switch and throughout the network.

The DIGITAL UNIX IP switching implementation is based on the Ipsilon Networks, Inc. reference model and has the following characteristics:

• Supports IP traffic only

• Supports multicast and broadcast services

• Does not require systems to function as ARP servers or multicast servers

• Uses the Ipsilon Flow Management Protocol (IFMP) to exchange control information with the IP switch

• Does not require that ATM Forum signaling (options UNI3X) be configured on the system

• Requires fewer configuration steps than Classical IP and LAN emulation

Figure 2-3 shows a simple ATM network with an IP switch, IP switch gateway, some hosts, and a legacy LAN network. Host A, Host B, and the IP gateway are on separate subnets. The IP switch gateway runs a routing protocol and advertises routes to other subnets to hosts on the legacy LAN.

Figure 2-3:  IP Switching over an ATM Network

For the IP switching subnetworks, DIGITAL recommends that you use a network mask length of 30 bits. This allows for two bits for each host address, one bit for the subnetwork address, and one bit for the broadcast address. Using large netmasks helps to conserve IP address space on subnetworks that have a few hosts attached.

2.2    ATM Planning

This section describes those tasks that you need to do before configuring the ATM software.

2.2.1    Verifying That the ATM Subsets Are Installed

Verify that the ATM subsets are installed by entering the following command:

# setld -i | grep ATM

If all of the subsets are not installed, install them by using the setld command. For more information on installing subsets, see setld(8), the Installation Guide, or the System Administration manual.

Note

You do not have to install the OSFATMBINOBJECT subset.

2.2.2    Configuring ATM into the Kernel

After you install the ATM subsets, verify that the ATM support you require is in the kernel by issuing the following command:

# sysconfig -q atm

If atm: is not displayed, log in as superuser and complete the following steps:

1. Build a new kernel by issuing the doconfig command. If you are unfamiliar with rebuilding the kernel, see the System Administration manual.

2. When prompted, select one or more of the kernel options in Table 2-1:

   Table 2-1:  ATM Kernel Options

   Option	Purpose
   options ATM	For base ATM support (required)
   options UNI3X	For ATM Forum signaling with either LANE or Classical IP
   options ATMILMI3X	For ATM Forum Integrated Layer Management Interface (ILMI) support
   options ATMIP	For Classical IP services
   options LANE	For ATM Forum LAN Emulation (LANE)
   options ATMIFMP	For IP switching

   Note

   If the ATM hardware is already installed, options ATM is automatically selected as a mandatory option.

3. Reboot your system with the new kernel by issuing the following command:

   # shutdown -r now
   

   This command immediately shuts down and automatically reboots the system.

2.2.3    Preparing for the Configuration

After you verify ATM support in the kernel, you configure ATM. ATM configuration can consist of the following parts:

• Configuring for Classical IP

• Configuring for LAN Emulation

• Configuring for IP switching

The type of information you need depends on the types of environment you want to set up and use.

2.2.3.1    Classical IP Information

Figure 2-4 shows Part A of the Configuration Worksheet. The following sections explain the information you need to record in Part A of the worksheet. If you are viewing this manual on line, you can use the print feature to print a copy of this part of the worksheet.

Figure 2-4:  Configuration Worksheet, Part A

Adapter name

The device names of the network interfaces. The lta network interface are supported for ATM.

ROM end system identifiers

The ROM end system identifier (ESI) addresses of the adapter that you want to register with the system and the local switch. If you want to register all of the adapter's ROM ESI addresses, leave this blank.

Depending on the number of address prefixes assigned by the switch, you can create one or more ATM addresses. The driver can control up to 64 ROM ESI addresses, though adapters generally have only a few ROM ESI addresses.

Additional ESIs

Additional ESI addresses that you want to register with the system and the local switch. An ESI address has twelve hexadecimal digits.

Synchronous Digital Hierarchy Mode

If you want to enable Synchronous Digital Hierarchy (SDH) mode on ATM adapters that support both Synchronous Optical Network (SONET) and SDH physical interfaces, check Yes; otherwise, check No.

Flow control

If you want to enable vendor-specific flow control on the adapter, check Yes; otherwise, check No. The adapter must support this type of flow control. DIGITAL adapters and switches support FLOWmaster vendor flow control.

Signaling and ILMI

If you want to enable signaling and the Integrated Layer Management Interface (ILMI) on the interface, check Yes; otherwise, check No. You must enable signaling and ILMI when using Classical IP over SVCs.

UNI version (signaling only)

The signaling version to use on the interface. If you want to use User-Network Interface (UNI) Version 3.0, check 3.0. If you want to use UNI Version 3.1, check 3.1. The default is 3.0.

VC accounting (signaling only)

If you want to enable logging of virtual circuit (VC) releases, check Yes; otherwise, check No.

LIS number

A Logical IP Subnet (LIS) interface number. You can create multiple LIS interfaces on an ATM driver.

ARP server

If you want your system to function as an ARP server, check Server; otherwise, check Client.

Server ATM address (ARP client only)

The ATM address of the ATM ARP server, either a host name or alias that appears in the /etc/atmhosts file or a 40-digit ATM End System Address (AESA) with selector byte. The ARP server must also be on the ATM network.

Note

The ATM Forum now calls an NSAP-style address an AESA.

Server IP address (ARP client only)

The IP address of the ATM ARP server machine.

2.2.3.2    LAN Emulation Information

Figure 2-5 shows Part B of the Configuration Worksheet. The following sections explain the information you need to record in Part B of the worksheet. If you are viewing this manual on line, you can use the print feature to print a copy of this part of the worksheet.

Figure 2-5:  Configuration Worksheet, Part B

Adapter name

The device names of the network interfaces. The lta network interfaces are supported for ATM.

ROM end system identifiers

The ROM end system identifier (ESI) addresses of the adapter that you want to register with the system and the local switch. If you want to register all of the adapter's ROM ESI addresses, leave this blank. You must enter at least one ESI for each emulated LAN (ELAN) you want to configure.

Depending on the number of address prefixes assigned by the switch, you can create one or more ATM addresses. The driver can control up to 64 ROM ESI addresses, though adapters generally have only a few ROM ESI addresses.

Additional ESIs

Additional ESI addresses that you want to register with the system and the local switch. An ESI address has twelve hexadecimal digits.

Synchronous Digital Hierarchy Mode

If you want to enable Synchronous Digital Hierarchy (SDH) mode on ATM adapters that support both Synchronous Optical Network (SONET) and SDH physical interfaces, check Yes; otherwise, check No.

Flow control

If you want to enable vendor-specific flow control on the adapter, check Yes; otherwise, check No. The adapter must support this type of flow control. DIGITAL adapters and switches support FLOWmaster vendor flow control.

Signaling and ILMI

If you want to enable signaling and the Integrated Layer Management Interface (ILMI) on the interface, check Yes; otherwise, check No. You must enable signaling and ILMI when using LAN Emulation.

UNI version (signaling only)

The signaling version to use on the interface. If you want to use User-Network Interface (UNI) Version 3.0, check 3.0. If you want to use UNI Version 3.1, check 3.1. The default is 3.0.

VC accounting (signaling only)

If you want to enable logging of virtual circuit (VC) releases, check YES; otherwise, check NO.

ELAN number

A LAN Emulation Client (LEC) interface unit number.

Virtual LAN name

The name of the emulated LAN to join. The emulated LAN name must already be configured on the ATM switch. If the name is not configured on the ATM switch, the LEC joins the default emulated LAN. Do not specify both a virtual LAN name and a LES address.

LES address

The ATM address of the LAN Emulation Server (LES), either a host name or alias that appears in the /etc/atmhosts file or a 40-digit ATM AESA address with selector byte. If you want the LEC to go directly to the LES and bypass the configuration phase, enter the LES address. Otherwise, the LEC contacts a LAN Emulation Configuration Server (LECS) to obtain a LES address. Do not specify both a virtual LAN name and a LES address.

MTU size

The maximum transmission unit (MTU) size. The following MTU sizes are supported: 1516, 4544, 9234, and 18190. When specified with a virtual LAN name, the emulated LAN must already be configured on the ATM switch to support the specified MTU size. If it is not configured for the specified MTU size, the request is ignored.

2.2.3.3    IP Switching Information

Figure 2-6 shows Part C of the Configuration Worksheet. The following sections explain the information you need to record in Part C of the worksheet. If you are viewing this manual on line, you can use the print feature to print a copy of this part of the worksheet.

Figure 2-6:  Configuration Worksheet, Part C

Adapter name

The device names of the network interfaces. The lta network interfaces are supported for ATM.

Interface

The IP switching (ips) interface number. If you are using multiple adapters, each adapter is assigned a separate interface number.

SNAP VCI

The Virtual Channel Identifier (VCI) number that Ipsilon Flow Management Protocol (IFMP) uses as the default Subnetwork Attachment Point (SNAP) VCI. The default VCI is 15. This number must match the VCI number that IFMP uses on the destination host or switch associated with the point-to-point interface.

Routing

The method you use to update your internal routing tables. If you use the gated daemon, check gated. If you use the routed daemon, check routed. If you use static routes, check static routes.

Destination (static routes only)

The IP address of the destination subnetwork.

Gateway (static routes only)

The IP address of the IP controller on the IP switch.

Netmask (static routes only)

The netmask for the destination subnetwork.

Host name

The names of hosts on the subnetwork to be added to the /etc/hosts file.

Internet address

The IP addresses of hosts on the subnetwork to be added to the /etc/hosts file.

Alias

The aliases, if any, of hosts on the subnetwork to be added to the /etc/hosts file.

2.3    Configuring ATM

After you complete the required ATM planning, you configure the ATM software. The following sections provide information on how to configure classical IP, LAN emulation, and IP switching.

2.3.1    Configuring Classical IP

Configuring Classical IP on your host consists of the following steps:

1. Creating PVC mappings on your ATM switch, if you are not going to use SVCs. You also use PVCs when directly connecting two hosts to each other without an ATM switch.

2. Editing the /etc/atmhosts file.

3. Adding hosts to the hosts database.

4. Running atmsetup.

5. Running netsetup (SVCs only).

6. Editing the /etc/atm.conf file (PVCs only).

7. Running atmconfig (PVCs only).

The first step depends on the type of ATM switch you are using. See your ATM switch documentation for this information. The following sections describe steps 2-7.

2.3.1.1    Editing the /etc/atmhosts File

You edit the /etc/atmhosts file to add the address of the ATM ARP server on your ATM network. The /etc/atmhosts file contains mappings of ATM host names to ATM hardware addresses. This file can also contain ATM ESIs and AESAs for specific services on the ATM network. Putting entries in this file enables you to specify the address or service by name instead of specifying a long hexadecimal string.

Entries in the /etc/atmhosts file can be one of the following:

• A comment, denoted by a pound sign (#) as the first character

• An address specification

The address specification is similar to that of IP addresses in the /etc/hosts file, and has the following format:

atm_addr hostname [ alias ... ]

The atm_addr parameter can consist of ESIs or AESAs.

The following table lists the address type and the number of hexadecimal address digits required for each type:

The hostname parameter can contain any printable character.

The following example shows entries in the /etc/atmhosts file:

08002b2fe740                            myhost.esi  [1]
47840f01020300002122313208002b2fe740    myhost   [2]
47840f01020300002122313208002b2fe7403a  myhost.ip  [3]

1. Specifies an ESI to use in registering myhost with the switch. [Return to example]

2. Specifies the AESA of myhost. This is the network prefix and the ESI, and is the address that the network knows. [Return to example]

3. Specifies the AESA with selector byte of a service on myhost for the DIGITAL UNIX implementation of RFC 1577, Classical IP and ARP over ATM. [Return to example]

Note

By default, the atmhosts file contains an entry for PVCs. Do not delete or modify this entry.

2.3.1.2    Adding Hosts to the hosts Database

You add the IP addresses for all ATM hosts that will be on any Logical IP Subnet (LIS) to which the host will connect to the hosts database. Make sure you have the IP addresses for the local host and the ATM ARP server. Depending on your environment, host names and addresses can be in the local /etc/hosts file or in one of the files distributed with the Berkeley Internet Name Domain (BIND) system or Network Information System (NIS).

You can enter these IP addresses in the /etc/hosts file either by editing the file itself or by running the Network Configuration application of the Common Desktop Environment (CDE) Application manager. See Network Administration for information on the Network Configuration application, BIND, and NIS.

2.3.1.3    Running atmsetup

To run the atmsetup script and to configure Classical IP on your system, log in as root and do the following:

1. Invoke the atmsetup script by entering the following command:

   # /usr/sbin/atmsetup
   

   The ATM Setup menu appears.

2. Enter the number of the adapter that you want to configure.

3. Enter 1 (configure) to configure the adapter for Classical IP.

4. Enter 1 (Driver) to configure the driver module.

5. Enter 1 (configure) to configure the driver.

6. Indicate whether you want the driver to come on line and initiate low-level communications with the ATM switch when the system is booted.

7. Indicate whether you want to register all of the driver's ESIs. If you answer y (the default), all of the adapter's ROM ESI addresses are registered. If you answer n, you are prompted to select the ESIs from a list and to enter the number of each, separated by commas. For example, 1,3,5.

8. Indicate whether you want to register any additional ESIs. If you answer y, you are prompted for the ESI address.

9. Indicate whether you want to enable SDH mode. If you do, enter y; otherwise, enter n.

10. Indicate whether you want to enable FLOWmaster vendor flow control. If you do, enter y; otherwise, enter n.

11. Enter 2 (Signaling) to configure the signaling module.

12. Enter 1 (configure) to configure signaling.

13. Indicate whether you want to enable signaling and ILMI on the interface.

    If you answer y (the default), enter the UNI version you want to use. Press Enter to accept the default (Version 3.0); otherwise, enter 3.1. Then, indicate whether you want to log VC activity.

14. Enter 3 (ATMIP) to configure the ATMIP (Classical IP) module.

15. Enter 1 (configure) to configure ATMIP.

16. Enter 1 to add a LIS.

17. Enter the number of the LIS you want to add.

18. Indicate whether your system is to act as an ARP client or an ARP server. Enter c for client or s for server.

19. If the system is to be an ARP client, enter the ARP server's ATM address or alias and press Enter. Then, enter the ARP server's IP address and press Enter.

20. To add another LIS, enter 1; otherwise, enter 6 to indicate that you do not want to add more LISs. Then, enter 5 to indicate that you are finished with the ATMIP module setup. Then, enter the last number displayed (done) to indicate that you are finished with the adapter setup.

21. If you want to start the ATM components immediately from the atmsetup script, enter y; otherwise, enter n. If you enter n, you must reboot the system to start the ATM components with the new values.

2.3.1.4    Running netsetup (SVCs only)

After you run the atmsetup script and start the ATM components (either from within the atmsetup script or by rebooting the system), you run the /sbin/netsetup script to configure the lis interfaces. See netsetup(8) for more information.

2.3.1.5    Editing the /etc/atm.conf File (PVCs only)

The basic Classical IP configuration process creates switched virtual circuits (SVCs). If you want to use permanent virtual circuits (PVCs), you must manually edit the /etc/atm.conf file after you run atmsetup. After you install the ATM subsets, the ATM configuration file contains the following sample PVC entries:

.
.
.
# print Waiting to join ATM Network... [1]
# wait state=up driver=lta0  [2]
# sleep 3 [3]
##
## **************************************************************************
## This sequence shows how to configure a Classical IP interface over a
## Permanent Virtual Circuit (PVC).
## **************************************************************************
##
## Create the Logical IP Subnet (LIS)
# print Configuring Classical IP interface lis0 on VPI=0 VCI=50 ... [4]
# run /usr/sbin/atmarp -c lis=0 driver=lta0 [5]
##
## Set the IP address for the LIS.  A PVC LIS cannot be configured through
## the netsetup command because it does not exist until the atmarp command
## above is executed.
# run ifconfig lis0 10.128.64.7 netmask 255.255.255.0 up [6]
#
## Set up the PVC. The same PVC must also have been configured on the switch.
## Note: The selector value will be different for each LIS (use "atmconfig
## bindlist" to see the bindings and selectors).
# +pvc driver=lta0 converge=atmip vpi=0 vci=50 selector=0 [7]
##
## If the remote host does not support RFC1577, the following additional
## commands are necessary.
##
## Create a permanent ATM ARP entry for the remote host's IP address
# atmarp -s PVC 10.128.64.xx permanent  [8]
##
## Associate the VPI/VCI specified above with the IP address
# atmarp -v +vc 0 50 10.128.64.xx  [9]
##

.
.
.

1. Remove the comment character (#) to enable printing of the message. [Return to example]

2. Waits for the driver to complete initialization with the switch, delaying startup until the interface is up.

   Remove the comment character (#) and edit this entry as needed. Add entries for each additional interface installed on the system, incrementing the interface number. For example, if another DGLTA adapter is installed on the system, the entry would be as follows:

   wait state=up driver=lta1
   

   [Return to example]

3. Suspends execution for three seconds to allow the driver to complete initialization.

   Remove the comment character (#) and edit this entry as needed. [Return to example]

4. Creates and attaches the LIS.

   Remove the comment character (#) and add entries for each LIS connected to the system, incrementing the LIS number. [Return to example]

5. Associates an IP address with the LIS.

   The LIS entry has the following format:

   run ifconfig lisn atmipaddr netmask ipnetmask up
   

   The n is the LIS number, atmipaddr is the IP address of the local machine on the ATM LIS, and ipnetmask is the LIS netmask to use.

   Remove the comment character (#) and edit this entry as needed. Add entries for each LIS connected to the system, incrementing the LIS number. [Return to example]

6. Sets up a PVC for a host on the LIS. Each entry has the following format:

   +pvc driver=driver converge=atmip vpi=vp_num vci=vc_num selector=num
   

   The driver option is the driver name associated with the LIS, the vp_num option is the VPI of the PVC, the vc_num option is the VCI of the PVC configured on the switch, and the num option is the LIS number. You must specify the selector parameter.

   Remove the comment character (#) and edit this entry as needed. Add entries for each additional PVC that you want to set up. [Return to example]

7. Depending on your network topology and the number and configuration of LISs in your network, you might need to add static routes to other hosts if either of the following conditions are true:

   • Your system is one hop away from another host (via a gateway) over an ATM connection

   • Your system is more than one hop away from another host on a network that supports multicast messages (for example, Ethernet, FDDI, Token Ring)

   To add a static route to the routing tables, add entries immediately after this comment line. These entries have the following format:

   run /usr/sbin/route add -net destination gateway -netmask mask
   

   The destination argument is the IP address of the destination network and the gateway argument is the address of the local LIS.

   Add entries for each additional host to which your system needs to communicate. See route(8) for more information. [Return to example]

8. Creates a permanent entry in the ATM ARP table. Each entry has the following format:

   /usr/sbin/atmarp -s atm_address ip_address permanent
   

   The atm_address argument specifies the ATM address (full 20-byte AESA or host name) for the entry and the ip_address argument specifies the IP address for the corresponding ATM address. The permanent argument means that the entry is not subject to the RFC 1577 aging rules. PVCs use the host name PVC.

   Remove the comment character (#) and edit this entry as needed. Add entries for each additional host that does not support RFC 1577. [Return to example]

9. Associates a VPI and VCI with a permanent IP address for a host that does not support RFC 1577. Each entry has the following format:

   /usr/sbin/atmarp -v +vc vpi_number vci_number hostname
   

   The vpi_number argument specifies the virtual path identifier (VPI) for the virtual circuit, the vci_number argument specifies the virtual channel identifier (VCI) for the virtual circuit, and hostname argument specifies the host name assigned to the ARP entry.

   Remove the comment character (#) and edit this entry as needed. Add entries for each additional host that does not suppor RFC 1577. [Return to example]

2.3.1.6    Running atmconfig (PVCs only)

After you are done editing the /etc/atm.conf file, enter the following command to start and configure the ATM subsystem:

# atmconfig source

If you have multiple configuration files, you can execute a specific file by entering the following command:

# atmconfig source file=file_name

See atmconfig(8) for more information.

Note

You must invoke the atmconfig command to process the commands in the /etc/atm.conf file each time the system is rebooted. You can do do this manually or by running a user-supplied script in the /etc/inin.d directory.

After the PVC is configured, verify the configuration by issuing the atmarp -a command. Output similar to the following appears if the PVC is configured:

# atmarp -a
Number of entries : 1
 
IP Address :   atm66 (16.142.128.66)
ATM Address :  PVC
Flags :        Complete Permanent 
VCs :          vpi    vci    VC Type
               ---    ---    -------
               0      999    PVC

2.3.2    Configuring LAN Emulation

Configuring LAN emulation on your host consists of the following steps:

1. Editing the /etc/atmhosts file

2. Adding hosts to the hosts database

3. Running atmsetup

4. Running netsetup

The following sections describe these steps.

2.3.2.1    Editing the /etc/atmhosts File

You edit the /etc/atmhosts file only if you want to specify a LAN Emulation Server (LES) address on your ATM network. The /etc/atmhosts file contains mappings of ATM host names to ATM hardware addresses. This file can also contain ATM ESIs and AESAs for specific services on the ATM network.

Entries in the /etc/atmhosts file can be one of the following:

• A comment, denoted by a pound sign (#) as the first character

• An address specification

The address specification is similar to that of IP addresses in the /etc/hosts file, and has the following format:

atm_addr hostname [ alias ... ]

The atm_addr parameter can consist of ESIs or AESAs.

The following example shows entries in the /etc/atmhosts file:

08002b2fe740                            myhost.esi  [1]
47840f01020300002122313208002b2fe740    myhost   [2]
47840f01020300002122313208002b2fe7403a  myhost.ip  [3]

1. Specifies an ESI to use in registering myhost with the switch. [Return to example]

2. Specifies the AESA of myhost. This is the network prefix and the ESI, and is the address that the network knows. [Return to example]

3. Specifies the AESA with selector byte of a service on myhost for the DIGITAL UNIX implementation of RFC 1577, Classical IP and ARP over ATM. [Return to example]

Note

By default, the atmhosts file contains and entry for PVCs. Do not delete or modify this entry.

2.3.2.2    Adding Hosts to the hosts Database

You add the IP addresses for all ATM hosts that will be on any emulated LAN (ELAN) to which the host will connect to the hosts database. Make sure you have the IP addresses for the local host. Depending on your environment, host names and addresses can be in the local /etc/hosts file or in one of the files distributed with the Berkeley Internet Name Domain (BIND) system or Network Information System (NIS).

You can enter these IP addresses in the /etc/hosts file either by editing the file itself or by running the Network Configuration application of the Common Desktop Environment (CDE) Application manager. See Network Administration for information on the Network Configuration application, BIND, and NIS.

2.3.2.3    Running atmsetup

To run the atmsetup script and to configure LAN emulation on your system, log in as root and do the following:

1. Invoke the atmsetup script by entering the following command:

   # /usr/sbin/atmsetup
   

   The ATM Setup menu appears.

2. Enter the number of the adapter that you want to configure.

3. Enter 1 (configure) to configure the adapter for LAN emulation.

4. Enter 1 (Driver) to configure the driver module.

5. Enter 1 (configure) to configure the driver.

6. Indicate whether you want the driver to come on line and initiate low-level communications with the ATM switch when the system is booted.

7. Indicate whether you want to register all of the driver's ESIs. If you answer y (the default), all of the adapter's ROM ESI addresses are registered. If you answer n, you are prompted to select the ESIs from a list and enter the number of each, separated by commas. For example, 1,3,5.

8. Indicate whether you want to register any additional ESIs. If you answer y, you are prompted for the ESI address.

9. Indicate whether you want to enable SDH mode. If you do, enter y; otherwise, enter n.

10. Indicate whether you want to enable FLOWmaster vendor flow control. If you do, enter y; otherwise, enter n.

11. Enter 2 (Signaling) to configure the signaling module.

12. Enter 1 (configure) to configure signaling.

13. Enter y to indicate that you want to enable signaling and ILMI on the interface. Then, enter the UNI version you want to use. Press Enter to accept the default (Version 3.0); otherwise, enter 3.1. Then, indicate whether you want to log VC activity.

14. Enter 4 (LANE) to configure the LANE (LAN Emulation) module.

15. Enter 1 (configure) to configure LANE.

16. Enter 1 to add an ELAN.

17. Indicate whether you want to join a specific emulated LAN. If you do, enter y. Then, enter the name of the emulated LAN you want to join and go to step 19.

    If you do not want to join a specific emulated LAN, enter n.

18. If you answered n to the previous question, indicate whether you want to specify a LAN Emulation Server (LES). If you answer y, enter the LES address. If you answer n, you will use the LAN Emulation Configuration Server (LECS) and join the default emulated LAN.

19. Indicate whether you want to specify an MTU size other than the default 1516. If you answer y, enter the MTU size.

20. To add another ELAN, enter 1; otherwise, enter 6 to indicate that you do not want to add more ELANs. Then, enter 5 to indicate that you are finished with the LANE module setup. Then, enter the last number displayed (done) to indicate that you are finished with the adapter setup.

    Note

    You can join an emulated LAN on a switch only once for each adapter; do not join the same ELAN multiple times from the same adapter. If you want to join the same ELAN on the same switch, you must install another adapter and join the ELAN from it.

21. If you want to start the ATM components immediately from the atmsetup script, enter y; otherwise, enter n. If you enter n, you must reboot the system to start the ATM components with the new values.

2.3.2.4    Running netsetup

After you run the atmsetup script and start the ATM components (either from within the atmsetup script or by rebooting the system), you run the /sbin/netsetup script to configure the elan interfaces. See netsetup(8) for more information.

2.3.3    Configuring IP Switching

Configuring IP switching on your host consists of the following steps:

1. Editing the /etc/hosts file

2. Running atmsetup

3. Editing the /etc/atm.conf file

4. Running atmconfig

The following sections describe these steps.

2.3.3.1    Editing the /etc/hosts File

You edit the /etc/hosts file to add the IP addresses for each IP switching subnetwork to which the host will connect. For each subnet, add a pair of IP addresses for each end of the point-to-point link (host side and IP controller side), the IP address of the subnet, and the broadcast address of the subnet. For example, an /etc/hosts file for the configuration in Figure 2-3 is as follows:

# IP Switching subnet A
16.1.1.4   atm4-net
16.1.1.5   hosta.corp.com              hosta             atm5
16.1.1.6   ipsctrlhosta.corp.com       ipsctrlhosta      atm6
16.1.1.7   atm7-broadcast
# IP Switching subnet B
16.1.1.0   atm0-net
16.1.1.1   ipsctrlhostb.corp.com       ipsctrlhostb      atm1
16.1.1.2   hostb.corp.com              hostb             atm2
16.1.1.4   atm4-broadcast
# IP Switching subnet C
16.1.1.8   atm8-net
16.1.1.9   ipsctrlhostc.corp.com       ipsctrlhostc      atm9
16.1.1.10  ipgwy.corp.com              ipgwy             atm10
16.1.1.11  atm11-broadcast

You can enter these IP addresses either by editing the /etc/hosts file or by running the Network Configuration application of the Common Desktop Environment (CDE) Application manager. See Network Administration for information on the Network Configuration application.

2.3.3.2    Running atmsetup

To run the atmsetup script and to configure the adapter or adapters on your system, log in as root and do the following:

1. Invoke the atmsetup script by entering the following command:

   # /usr/sbin/atmsetup
   

   The ATM Setup menu appears.

2. Enter the number of the adapter that you want to configure.

3. Enter 1 (configure) to configure the adapter.

4. Enter 1 (Driver) to configure the driver module.

5. Enter 1 (configure) to configure the driver.

6. Indicate whether you want the driver to come on line and initiate low-level communications with the ATM switch when the system is booted.

7. Enter y to indicate that you want to register all of the driver's ROM ESIs.

8. Enter n to indicate that you do not want to register any additional ESIs.

9. Enter n to indicate that you want to enable SONET mode.

10. Enter n to indicate that you do not want to enable vendor flow control.

11. Enter 5 to indicate that you are finished with the driver module setup. Then, enter the last number displayed (done) to indicate that you are finished with the adapter setup.

12. If you want to start the ATM components immediately from the atmsetup script, enter y; otherwise, enter n. If you enter n, you must reboot the system to start the ATM components with the new values.

2.3.3.3    Editing the /etc/atm.conf File

After you install the ATM subsets, the default ATM configuration file, /etc/atm.conf, contains entries for Classical IP over PVCs and for IP switching. Use the following entries for configuring IP switching:

.
.
.
# print Waiting to join ATM network ... [1]
# wait state=up driver=lta0 [2]
# sleep 3 [3]

.
.
.
##
## **************************************************************************
## This sequence shows how to configure an IP Switching interface
## **************************************************************************
##
## Create an ips0 interface.  Override default SNAP VCI to interoperate
## with the Gigaswitch Rev 2.x software.
# print Configuring IP Switching interface ips0 ...
# run /usr/sbin/atmifmp attach ips=0 driver=lta0 snapvci=32 [4]
## Set the IP address for the interface. An IP Switching interface cannot
## be configured through the netsetup command because it does not exist
## until the above atmifmp command is executed.
# run /usr/sbin/ifconfig ips0 up 10.142.128.133 10.142.128.134 netmask 255.255.255.252 [5]
##
## If not running a routing daemon (routed, etc) one or more static routes
## may be necessary.
# run /usr/sbin/route add -net 10.142.128.0 10.142.128.134 -netmask 255.255.255.0 [6]
exit

1. Remove the comment character (#) to enable printing of the message. [Return to example]

2. Waits for the driver to complete initialization with the switch, delaying startup until the interface is up.

   Remove the comment character (#) and edit this entry as needed. Add entries for each additional interface installed on the system, incrementing the interface number. For example, if another DGLTA adapter is installed on the system, add the following entry:

   wait state=up driver=lta1
   

   [Return to example]

3. Suspends execution for three seconds to allow the driver to complete initialization.

   Remove the comment character (#) and edit this entry as needed. [Return to example]

4. Creates and attaches the ips0 interface, and overrides the default SNAP VCI to interoperate with the DIGITAL GIGAswitch switch.

   Remove the comment character (#) and edit this entry as needed. Add entries for each ips interface, incrementing the ips number.

   Note

   The default SNAP VCI is 15. This number must match the VCI number that IFMP uses on the switch associated with the point-to-point interface.

   [Return to example]

5. Associates an IP address with the ips interface.

   The ips entry has the following format:

   run ifconfig ips0 atmipaddr addr netmask ipnetmask up
   

   The atmipaddr is the IP address of the local machine, addr is the IP address of the IP controller, and ipnetmask is the netmask to use.

   Remove the comment character (#) and edit this entry as needed. Add entries for each ips interface on the system, incrementing the ips number.

   If you were configuring IP switching on Host A in Figure 2-3, you would create the following entry:

   run /usr/sbin/ifconfig ips0 up 16.1.1.5 16.1.1.6 netmask 255.255.255.252
   

   [Return to example]

6. Adds a static route to the subnetwork 10.142.128.0.

   Depending on your network topology and the number of interfaces on your host, you might need to add static routes to other hosts if your system has multiple interfaces and the default route is to another gateway on another network.

   Remove the comment character (#) and edit this entry as needed. Add entries for each additional route to add to the routing tables. These entries have the following format:

   run /usr/sbin/route add -net destination gateway -netmask mask
   

   The destination argument is the IP address of the destination subnetwork, and the gateway argument is the address of the IP controller on the IP switch. See route(8) for additional information.

   If you were configuring IP switching on Host A in Figure 2-3 and you wanted to route all traffic on all 16.1.1 networks through the IP switch, you would create the following static route to the IP controller on the switch:

   run /usr/sbin/route add -net 16.1.1.0 16.1.1.6 -netmask 255.255.255.0
   

   Using the Class Inter-Domain Routing (CIDR) format, the entry would be as follows:

   run /usr/sbin/route add -net 16.1.1/24 16.1.1.6
   

   [Return to example]

2.3.3.4    Running atmconfig

After you are done editing the /etc/atm.conf file, enter the following command to start and configure the ATM subsystem:

# atmconfig source

If you have multiple configuration files, you can execute a specific file by entering the following command:

# atmconfig source file=file_name

See atmconfig(8) for more information.

2.4    Managing the ATM Environment

Managing the ATM environment consists of the following tasks:

• Managing ATM networking and displaying information about ATM networks

• Managing the signaling module

• Managing the Classical IP environment

• Managing the LAN Emulation environment

• Managing IP switching

The following sections describe each of these tasks.

2.4.1    Managing ATM Networking and Displaying Information About ATM Networks

To manage ATM networking and to display information about the ATM networks, you use the atmconfig command. The command controls only the base ATM modules and device drivers; it does not control specific convergence modules or signaling protocols. You can use the atmconfig command to do the following:

• Enable and disable device drivers

• Create and destroy PVCs

• Destroy SVCs

• Create and destroy ESIs

• Display the currently active VCs and driver status

• Process configuration batch files

See atmconfig(8) for more information.

2.4.2    Managing the Signaling Module

To manage ATM UNI signaling on the end system, you use the atmsig command. The atmsig command allows you to:

• Display state information about the signaling module

• Disable and enable the ILMI and signaling

• Read and modify the various timer values and statistics for Q.SAAL and Q.93B (2931)

The signaling module is associated with a specified interface at all times, which is identified by the driver name. If the interface is disabled, the signaling module is also disabled. The signaling module must be enabled again when the interface is brought back on line.

See atmsig(8) for more information.

2.4.3    Managing the Classical IP Environment

To manage Classical IP on an end system, you use the atmarp command. The atmarp command allows you to:

• Create a logical IP subnet (LIS) interface

• Create and delete entries in the ATM ARP table

• Display entries in the ATM ARP table

• Toggle the permanent flag for entries

• Display the local host's ATM configuration status

• Create and remove an association between an established VC and a remote IP entity that does not support Classical IP

See atmarp(8) for more information.

2.4.4    Managing the LAN Emulation Environment

Managing the LAN emulation environment consists of the following tasks:

• Managing LAN Emulation Clients (LECs)

• Displaying the LAN Emulation Address Resolution Protocol (LE-ARP) table

The following sections describe these tasks.

2.4.4.1    Managing LAN Emulation Clients

To manage LAN Emulation Clients (LECs), you use the atmelan command. The atmelan command allows you to:

• Create and configure LAN Emulation Clients (LEC) as network interfaces

• Display counters, parameters, and the state of each LEC

See atmelan(8) for more information.

2.4.4.2    Displaying the LE-ARP Table

To display the LE-ARP table for each elan interface, you use the learp command. The command displays the address mappings for the emulated LAN. Each entry consists of the Media Access Control (MAC) address, state, ATM address, and flags. See learp(8) for more information.

2.4.5    Managing IP Switching

To manage IP switching on an end system, you use the atmifmp command. The atmifmp command allows you to:

• Enable and disable IP switching

• Display IP switching configuration

• Display or clear IP switching statistics

• Display IP switching flow information

See atmifmp(8) for more information.

2.5    Solving Problems

This section contains a diagnostic map to help you solve problems that might occur when you use the ATM network services. Use this section, along with the appropriate DIGITAL documentation, to solve as many problems as possible at your level.

2.5.1    Using the Diagnostic Map

ATM network problems can occur for a number of reasons. The diagnostic map in this section should help you isolate the problem. The following figure explains how to use the diagnostic map:

After you isolate the problem, the map refers you to other sections for instructions on using the various problem-solving tools and utilities. The map also refers you to other manuals for complete diagnostic information for particular devices and software products.

You could experience problems that are not documented in this manual when you use ATM network software with other layered products. Each layered product has its own manual or set of manuals that might describe solutions not provided here.

2.5.2    Getting Started

Before you start problem solving, ensure that communications hardware is ready for use. Verify the following:

• The system's physical connections are properly installed. See the documentation for your system and communications hardware device.

• Event logging is enabled to monitor network events. See System Administration for information on starting event logging and for descriptions of event messages.

Also check the product release notes for up-to-date information on known problems.

2.5.3    Solving ATM Problems

# setld -i | grep OSFATM

OSFATMnnn installed ATM Commands
   (Network-Server/Communications)
OSFATMBINnnn installed ATM Kernel
   Modules (Kernel Build Environment)
OSFATMBINCOMnnn installed ATM Kernel
   Header and Common Files
   (Kernel Build Environment)
OSFATMBINOBJECTnnn installed ATM Kernel
   Objects (Kernel Software Environment)

# sysconfig -q atm

Name: lta0      Type: STS-3      State: UP
Driver ID: 1   ESIs: 8   PPAs: 9  VCs: 6

2.5.3.1    Solving CLIP Problems

# atmsig status driver=driver_name

# atmarp -h

# ifconfig lisx

lis0: flags=c23<UP,BROADCAST,NOTRAILERS,MULTICAST,SIMPLEX>
    inet 10.140.120.52 netmask ffffff00 broadcast 10.140.120.255
   ipmtu 1500

unknown host

host is unreachable

2.5.3.2    Solving LANE Problems

# atmsig status driver=driver_name

# atmelan show

.
.
.
control state: S_OPERATIONAL

.
.
.

# ifconfig elanx

elan0: flags=c23<UP,BROADCAST,NOTRAILERS,MULTICAST,SIMPLEX>
     inet 10.140.120.52 netmask ffffff00 broadcast 10.140.120.255
   ipmtu 1500

unknown host

host is unreachable

2.5.3.3    Solving IP Switching Problems

# atmifmp showips

ips0:
         Attached to driver lta0
         Default (SNAP) VC = 32
         IP Traffic VC = 1850 (Unused - peer does
                not support Flow Type 0)
         Min Tx VC = 1
         Max Tx VC = 2048
         Min Rx VC = 1
         Max Rx VC = 2048
         Driver Min Tx VC = 1
         Driver Max Tx VC = 2048
         Driver Min Rx VC = 1
         Driver Max Rx VC = 2048
         Peer does not support Flow Type 0

# ifconfig ipsx

ips0: flags=4d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>
   inet 16.142.128.129 
-->
16.142.128.130 netmask fffffffc  ipmtu 1500

unknown host

host is unreachable