Chapter 3 Editing SunATM Configuration Files

This chapter describes how to configure SunATM interfaces by editing the configuration files.

You are not required to edit these configuration files by hand. You can use the atmadmin configuration program, described in "Using the atmadmin Configuration Program", to configure the SunATM files. From the program's command-line interface, you can change most of the SunATM parameters.

When it saves configuration information, atmadmin overwrites the existing SunATM configuration files in the /etc/opt/SUNWconn/atm/ directory. Therefore, any comments or other changes you manually made to the files will be lost.

This chapter contains the following sections:

• "Basic ATM Interface Plumbing"

  "Configuring a Classical Internet Protocol Interface"

• "Configuring a LAN Emulation Interface"

Basic ATM Interface Plumbing

ATM interfaces must be plumbed prior to configuration for LANE or Classical IP. This plumbing configuration is specified in the /etc/opt/SUNWconn/atm/atmconfig file. For a detailed description of plumbing and unplumbing ATM interfaces, see "Plumbing and Unplumbing Individual ATM Interfaces".

Editing the /etc/opt/SUNWconn/atm/atmconfig File

The /etc/opt/SUNWconn/atm/atmconfig file is a generic file that must appear on every SunATM system. It provides general configuration information used by the SunATM setup utilities to bring up ATM interfaces at boot time.

The file consists of one or more entries per interface. An entry contains the following fields described in Table 3-1:

The Interface and UNI fields are required for all interfaces. The CIP_Host field is required for interfaces that run Classical IP, and the LANE_Instance and LANE_Host fields are required for interfaces that run LAN Emulation. If a field is not used, it is represented by a hyphen.

Modifications to individual interfaces will take effect when the interface is plumbed. This will happen either at boot time or when you use the atmifconfig utility to plumb interfaces. If you modify an existing (already running) interface, you must first unplumb it with the atmifconfig utility. Refer to the atmifconfig(1m) man page or "Plumbing and Unplumbing Individual ATM Interfaces" for more information.

Changing the Framing Interface in the /etc/opt/SUNWconn/atm/atmconfig File

The framing interface defines the encapsulation method used for ATM cells as they are sent onto the wire. The default framing interface is SONET, but the SunATM software also supports the SDH interface. Your switch product information should indicate which interface your switch uses.

Previous versions of the SunATM software allowed you to choose a framing interface for the entire system (by setting a variable in the /etc/system file). In the SunATM software, the system variable can be used to allow backwards compatibility, but the preferred method is to select the framing interface for each interface and to add an entry in the /etc/opt/SUNWconn/atm/atmconfig file. An entry in /etc/opt/SUNWconn/atm/atmconfig overrides a variable set in /etc/system for a particular interface. If there is no value in either /etc/system or /etc/opt/SUNWconn/atm/atmconfig, the default framing interface is SONET.

Framing entries in /etc/opt/SUNWconn/atm/atmconfig should appear on individual lines, with two fields. The first field indicates the interface, baN, where N is the instance number (for example: ba0). The second is either SDH or SONET, depending on the desired setting.

Example of an /etc/opt/SUNWconn/atm/atmconfig File

The following sample atmconfig file creates this configuration:

• A LAN Emulation interface lane0, supporting UNI 3.1, on the ba0 interface.

• An interface that supports both Classical IP and LAN Emulation on ba1, using UNI 4.0. The LAN Emulation interface name is lane1.

• A Classical IP interface, supporting UNI 3.0, on ba2, which uses the SDH framing interface.

  #Interface UNI/Framing CIP_Host LANE_Instance LANE_Host #-------------------------------------------------------------- ba0 3.1 - 0 atm0 ba1 4.0 atm1 1 atm2 ba2 3.0 atm3 - - ba2 SDH

Using Variables in the  /etc/opt/SUNWconn/atm/aarconfig File

Because the prefix portion of an ATM address specifies the ATM switch, a number of hosts specified in an aarconfig file can have ATM addresses that share the same prefix. To simplify setting up the aarconfig file, you can define variables that contain part of an ATM address.

A variable's name is an identifier consisting of a collection of no more than 32 letters, digits, and underscores. The value associated with the variable is denoted by a dollar sign followed immediately by the variable name.

Use variables in the ATM address field only. They are not valid in any of the other fields in an entry.

You can use a colon to concatenate multiple variables to represent a single ATM address expression. Thus, if one variable, v1, is set to 11:22 and another variable, v2, is set to 33:44, the sequence $v1:$v2 represents 11:22:33:44. You can include hexadecimal numbers with variables in the expression. The expression 45:$v1:$v2 would have the value 45:11:22:33:44.

Use the following format to define variables in the aarconfig file:

set VARIABLE = EXPRESSION

where VARIABLE is the name of a variable and EXPRESSION is an expression concatenating one or two-digit hexadecimal numbers or the values of variables that have been previously defined. The equal sign is optional, but separate the variable and expression either by white space (spaces or tabs), an equal sign, or both.

Several predefined variables are built into the SunATM software. These variables are summarized in Table 3-2.

You can not use the $prefix variable or any other variables that use it (including $myaddress and $localswitch_server) on interfaces that are not running ILMI.

In most network configurations, the ATM address assigned to the local interface is $myaddress; using this variable in the l entry makes it possible to use identical aarconfig files on all Classical IP clients using a given server.

The sunmacselN variables can be used in conjunction with a prefix, as well as with known server addresses that are not bound to a particular system. As an example, consider the case where a server that supports 50 clients fails. If the ATM address of the server is specific to that particular server, you must change the s entry on all 50 clients to switch to a backup server. However, if the ATM address used for that server is $prefix:$sunmacsel3, this address is not only guaranteed to be unique, since it uses reserved medium access control (MAC) addresses, you can also simply assign that address to the backup server on the same switch by changing the l entry to an s entry on one system and bringing up a new server with no changes to the clients.

The sunmacselN variables do not include a prefix since a client and server may be on different switches and thus have different local prefix values.

In the case of a single-switch network, you can use localswitch_server as a well-known server address that includes the prefix associated with the local switch and a MAC address. It will restrict server access to clients on the local switch and provide a unique ATM address among all ATM clients connected to that switch. Thus, any host with a network prefix other than that of the local switch will be refused a connection to the ARP server if the ARP server's address is $localswitch_server.

Several rules apply to the use of variables in the aarconfig file:

• Two variables cannot follow each other in an expression without an intervening colon. Thus $v1:$v2 is legal while $v1$v2 is not.

• Fields in each line in the aarconfig file are separated by white space. Therefore, variables should not be separated from the rest of an ATM address with white space. For example, $v1: $v2 is illegal.

• Once a variable is defined by a set command, it may not be redefined later in the same configuration file.

• The reserved variable names cannot be set. These names include prefix, mac, sel, macsel, myaddress, anymac, anymacsel, sunmacselN (where N is a number between 0 and 199), and localswitch_server.

  ---

  Note -

  The ESI portion of localswitch_server and the sunmacselN variables is a reserved MAC address. The hexadecimal values of the reserved addresses are: localswitch_server 08:00:20:75:48:08 sunmacselN base 08:00:20:75:48:10 To calculate the ESI portion for a sunmacselN address, simply add the value of N (converted to a hexadecimal number) to the sunmacselN base address. For example, the ESI portion of sunmacsel20 would be 08:00:20:75:48:10 + 0x14 = 08:00:20:75:48:24.

  ---

Sample Classical IP Configurations

The following examples demonstrate entries in the /etc/opt/SUNWconn/atm/aarconfig file for several typical network configurations.

Although some of the examples show only one sample aarconfig file, similarly configured files must appear on each system. Example 2 shows the files for each of the three systems in the configuration.

1. SVC-only: Clients use the default address and access to the ARP server is restricted to clients on the local switch only.

   1. The /etc/opt/SUNWconn/atm/aarconfig file on a client:

      Interface Host ATM Address VCI Flag ba0 - $myaddress - l ba0 - $localswitch_server - s

   2. The /etc/opt/SUNWconn/atm/aarconfig file on the server:

      Interface Host ATM Address VCI  Flag ba0 - $localswitch_server -    L

2. PVC-only: hosta is connected to hostb and hostc over PVCs. There is no ARP server.

   1. /etc/opt/SUNWconn/atm/aarconfig on hosta:

      Interface Host      ATM Address VCI Flag ba0         -   -      - l ba0 hostb -     100     t ba0 hostc -     101     t

   2. on hostb:

      Interface     Host    ATM Address      VCI  Flag ba0 -         - -       l ba0  hosta         -        100       t ba0   hostc        -        102       t

   3. on hostc:

      Interface Host ATM Address VCI Flag ba0        -      -                -      l ba0        hosta  -              101      t ba0        hostb  -              102      t

3. SVC with no ARP server: hosta uses SVCs to connect to hostb and hostc. All hosts are connected to the same switch; there is no ARP server.

   Interface   Host   ATM Address VCI Flag ba0 - $myaddress                       - l ba0 hostb $prefix:08:00:20:d5:08:a8:00     - t ba0 hostc $prefix:08:00:20:21:20:c3:00     -     t

4. PVC/SVC mix: hosta uses an SVC to connect to hostb, and a PVC to connect to hostc. hostb is not on the local switch; there is no ARP server.

   Interface  Host  ATM Address                                           VCI  Flag ba0        -     $myaddress -     l ba0       hostb 45:00:00:00:00:00:00:00:0f:00:0:08:00:20:d5:08:a8:00   -     t ba0       hostc  -                                                       100   t

5. IPv6 PVC/SVC mix: hosta uses an SVC to connect to hostb, and a PVC to connect to hostc.

   Interface Host ATM Address VCI Flagba0 - $myaddress - lba0 hostb-v6 $prefix:08:00:20:d5:08:a8:00 - t6ba0 hostc-v6 - 100 t6

6. IPv4/IPv6 mix: hosta uses a static IPv4 SVC to connect to hostb and a static IPv6 SVC to connect to hostc.

   Interface Host ATM Address VCI Flagba0 - $myaddress - lba0 hostb $prefix:08:00:20:d5:08:a8:00 - tba0 hostc-v6 $prefix:08:00:20:21:20:c3:00 - t6

7. ARP server with Access Restrictions: Hosts are connected to an ATM ARP server that resolves addresses. Access is restricted to the local switch subnet and one additional switch subnet.

   1. /etc/opt/SUNWconn/atm/aarconfig on hosta:

      Interface     Host     ATM Address          VCI           Flag ba0           -        $myaddress             -              l ba0           -        $prefix:$sunmacsel0    -              s

   2. /etc/opt/SUNWconn/atm/aarconfig on server:

      Interface Host ATM Address      VCI    Flag ba0 - $prefix:$sunmacsel0       -       L ba0 - $prefix:$anymacsel       -       a ba0         - 45:00:00:00:00:00:00:00:0f:00:00:00:00:$anymacsel   -       a

8. Manual address configuration: Hosts are connected to a switch that does not support ILMI.

   1. /etc/opt/SUNWconn/atm/aarconfig on server:

      set prfx = 45:00:00:00:00:00:00:00:0f:00:00:00:00 Interface  Host  ATM Address        VCI        Flag ba0        -     $prfx:$sunmacsel0    -           L ba0        -     -                    -           m

   2. /etc/opt/SUNWconn/atm/aarconfig on client:

      set prfx = 45:00:00:00:00:00:00:00:0f:00:00:00:00 Interface  Host  ATM Address        VCI         Flag ba0        -     $prfx:$macsel        -            l ba0        -     $prfx:$sunmacsel0    -            s ba0        -      -                   -            m

Configuring a Classical Internet Protocol Interface

Classical Internet Protocol (Classical IP), specified by RFC 1577, is one way of supporting the TCP/IP and UDP/IP protocols in an ATM environment. In Classical IP, an ATM ARP server is used to resolve IP addresses to ATM addresses, replacing the traditional ARP protocol. In this configuration, each host must register with the ARP server when the ATM interface is brought up. For more information on the Classical IP protocols, see "Classical Internet Protocol" on page 47.

ATM ARP is used instead of the traditional ARP because ATM does not support broadcast (a network capability providing transmission from one point to all points on a network). Because Classical IP over ATM does not support broadcast, you cannot use the ypbind UNIX command with the -broadcast option to automatically locate the NIS server (ypserver) on a Classical IP ATM subnet.

If you are planning to run NIS over your ATM network, use the ypinit -c command to specify the list of NIS servers (ypservers). See the ypinit(1M) man page for details of setting up the ypserver. Be sure that the IP addresses of the ypservers are listed in the /etc/hosts file.

The Routing Information Protocol (RIP) also uses the broadcast feature of IP, so it is not supported under the Classical IP environment. In the Solaris operating environment, RIP is implemented by the daemon in.routed.

If you are using Classical IP only, you must explicitly add the routes to the routers in the ATM subnet. You can also specify one router as the default router to provide connectivity outside of the ATM subnet. See the route(1M) man page for information on using the route command to add specific router entries and to add a default router.

Editing the /etc/opt/SUNWconn/atm/aarconfig File

The /etc/opt/SUNWconn/atm/aarconfig file contains the required configuration information for each interface that uses Classical IP. One entry is required for each SunATM interface. It allows you to specify IP to ATM address translation, permanent virtual circuits (PVCs) to destinations, and the address of the ATM ARP server. The environment allows for a mix of PVCs and switched virtual circuits (SVCs).

Each time the /etc/opt/SUNWconn/atm/aarconfig file is modified, run the ATM ARP setup program, aarsetup, which is in the /etc/opt/SUNWconn/bin directory.

Every node, or client, has both an IP address and either an ATM address or a virtual circuit identifier (VCI). See "ATM Address Resolution", for ATM addressing scheme information.

In the IP-ATM address table shown in the /etc/opt/SUNWconn/atm/aarconfig file:

• Interface is the last part of the device name (ba0, for example).

• Hostname is either an IP address in "dot" notation or the name of a host that should be locally available unless a non-ATM network connection also exists.

• ATM Address consists of 20 octets with each octet represented by a one- or two-digit hexadecimal number and separated by colons.

• The VCI field is a positive decimal integer.

• An unused field is denoted by a hyphen.

Table 3-3 lists the flags, including configuration flags, and the options they provide.

Although SunATM supports PVC connections to a server for ARP traffic, RFC 1577 does not specify this case. For interoperability with other implementations, connections to the server should use SVCs.

For two hosts to communicate over PVCs, corresponding PVC connections must also be established in the ATM switch fabric.

Table 3-4 describes the required, optional, and illegal fields for each flag type. If a field is unused, it is represented by a hyphen.

Group entries in the aarconfig file in a designated order: the local (l or L) entry first, followed by any other flags in any order. You only need to maintain the ordering within entries for each physical interface; for example, all of the ba0 entries can appear first, and then all of the ba1 entries, etc.

Configuring a LAN Emulation Interface

LAN Emulation, standardized by the ATM Forum's LAN Emulation 1.0 specification, is another way of providing TCP/IP and UDP/IP support over an ATM interface. Address resolution information is provided by a series of LAN Emulation services. When a LAN Emulation interface is brought up, it must "join the LAN," that is, it must register with these services. This process, and the address resolution process is described in "LAN Emulation".

Unlike Classical IP, the LAN Emulation protocol provides a broadcast service to the upper layer protocols. Therefore, the multicast and broadcast limitations described in "Classical IP Parameter Group", do not affect LAN Emulation interfaces. With this broadcast service, address resolution is supported through the standard means, ARP for an IPv4 environment and Neighbor Discovery for an IPv6 environment. thus IPv6 works transparently over LANs.

Editing the /etc/opt/SUNWconn/atm/laneconfig File

The /etc/opt/SUNWconn/atm/laneconfig file contains the required configuration information for each interface that uses LAN Emulation. One entry is required for each SunATM interface.

Each time you modify the /etc/opt/SUNWconn/atm/laneconfig file, run the LAN Emulation setup program (lanesetup). lanesetup is in the /etc/opt/SUNWconn/atm/bin directory.

Each /etc/opt/SUNWconn/atm/laneconfig entry follows this format:

Interface         MAC Address/      ATM Address  VCI  Flag
                  ELAN Name

These entry fields are described in Table 3-5.

Table 3-6 describes the flags used in the /etc/opt/SUNWconn/atm/laneconfig file.

Table 3-7 describes the required, optional, and illegal fields for each flag type.

Designate unused fields in the /etc/opt/SUNWconn/atm/laneconfig file with a dash.

Using Variables in the /etc/opt/SUNWconn/atm/laneconfig File

You can use some of the predefined variables from /etc/opt/SUNWconn/atm/aarconfig file in the /etc/opt/SUNWconn/atm/laneconfig. These variables are listed in Table 3-8. For a complete description of how to use these variables, see "Using Variables in the  /etc/opt/SUNWconn/atm/aarconfig File".

Using predefined or user-defined variables in the MAC address field of local (`l') entries is not supported. Variables may be used in the MAC address field of other entry types, such as in table (`t') entries.

You can not use the $prefix variable or any other variables that use it (including $myaddress), on interfaces that are not running ILMI.

Sample LAN Emulation Configurations

The following examples demonstrate entries in the /etc/opt/SUNWconn/atm/laneconfig file for several common configurations.

Although some of the examples show only one sample laneconfig file, similarly configured files must appear on each LAN Emulation client.

1. Basic LAN Emulation client. The ATM and MAC address of a frequently used server is provided. The LECS provides the name of the Emulated LAN.

   set srvr_mac = 08:00:20:01:02:03 Interface MAC_Address/ ATM_Address VCI Flag ELAN Name lane0 - $myaddress - l lane0 $srvr_mac $prefix:$srvr_mac:00 - t

2. LAN Emulation client. The LECS requires that the client send the Emulated LAN name in its messages.

   Interface MAC_Address/ ATM_Address VCI Flag ELAN Name lane0 - $myaddress - l lane0 elan1 - - n