3 - C H A P T E R -

C H A P T E R 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.

Caution - 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 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:

TABLE 3-1 `/etc/opt/SUNWconn/atm/atmconfig` Field Descriptions
Field	Description
`Interface`	Physical interface, `ba`N.
`UNI/Framing`	Version of the UNI specification used for signalling, 3.0, 3.1, or 4.0; or, for entries with only two fields, the Framing Interface, SONET or SDH.
`CIP_Host`	Hostname used for Classical IP.
`LANE_Instance`	Instance number for a LAN Emulation interface; LAN Emulation interfaces will be called `lane`N where N is the LAN Emulation instance number. The LANE instance number must be between 0 and 999. Note: The LANE instance number is not necessarily the same as the physical instance number.
`LANE_Host`	Hostname used for LAN Emulation

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

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 ATM Addresses and Address Registration.

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-2 lists the flags, including configuration flags, and the options they provide.

TABLE 3-2 `/etc/opt/SUNWconn/atm/aarconfig` File Flag Descriptions
Flag	Description
`l`	Represents the ATM address of the local interface on ARP clients or systems not using an ARP server for ATM address resolution, and can be used to assign an ATM address to the host. Hostname should not appear; ATM Address should be provided if, and only if, SVCs are used. If you provide an s entry to use an ARP server (see below), you must also provide an ATM Address (a server is meaningful only in an SVC environment). See TABLE 3-3.
`L`	Represents the ATM address of the local interface on an ARP server. Hostname should not appear; ATM Address is required. See TABLE 3-3.
`s`	Specifies a connection to the ATM ARP server. Either ATM Address or VCI (in the case of a PVC connection) should appear, but not both. Hostname should not appear. The s entry is required on all clients that need to communicate with the server for ATM address resolution. See TABLE 3-3.
`t`	Represents an IP to ATM address/VCI entry. `aarsetup` adds these entries into the local table. Any t entries on the server must contain ATM Address and may also contain VCI if PVC communication between the server and client is desired. In addition, there are some cases when a t entry may be useful on an ARP client system. If a client wants to communicate with another system over PVCs, the PVC to be used is provided in a t entry containing VCI; or if a client wishes to cache frequently used addresses to avoid frequent ARP requests, a t entry containing ATM Address may be provided. See TABLE 3-3. Note: If your naming service (NIS+ or DNS) server is an ATM host, you must provide the hostname to IP address resolution for the hosts included in t entries, either by using the IP address in the Hostname field of the t entry, or by adding an entry to the local `/etc/hosts` file.
`t6`	Represents an IP to ATM address/VCI entry. `aarsetup` adds these entries to the address cache. Any VC indicates an IPv6 PVC. An ATM address indicates a statically configured IPv6 SVC. The t6 entry is the only way to configure destination hosts for communication over IPv6
`a`	Represents an address that may have access to this host. If no a entries appear in the `aarconfig` file, access to the host is unrestricted. Including a entries allows access to be restricted to known hosts. As an alternative to listing individual addresses, the ATM address field may contain a prefix, followed by the wildcard `$anymacsel`, which matches any 7-byte ESI/Selector combination following the given prefix. This allows access by any host connected to the switch that is specified by the given prefix. Hostname and VCI should not appear; ATM Address is required. See TABLE 3-3.
`m`	Notifies the system that the entire ATM address, including the network prefix, must be configured manually on this interface. If your interface is connected to a switch that does not support ILMI address registration, you must include this option in your `/etc/opt/SUNWconn/atm/aarconfig` file. Note that you may not use the variables `$myaddress`, `$prefix`, and `$localswitch_server` (which use the switch prefix obtained from the switch via ILMI) if ILMI address registration is disabled.

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

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

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

TABLE 3-3 /`etc/opt/SUNWconn/atm/aarconfig` File Flag Requirements and Options
Interface *	Host	ATM Address	VCI	Flags	*
required	illegal	SVC only	illegal	`l`	local information
required	illegal	required	illegal	`L`	local information on server
required	illegal	required	illegal	`a`	access list entry
required	required	or*	or*	`t`	permanent table entry
required	required	xor**	xor**	t6	IPv6 table entries PVC & SVC
required	illegal	xor**	xor**	`s`	server address/PVC
required	illegal	illegal	illegal	`m`	manual address registration
or - Means one or the other required, but using both is also legal. *xor - Means one or the other required, but using both is illegal.

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

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.

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

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

Interface   Host  ATM Address             VCI Flag

ba0          -    $myaddress               -   l

ba0          -    $localswitch_server      -   s

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

Interface Host ATM Address          VCI  Flag

ba0       -    $localswitch_server   -      L

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

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

Interface   Host       ATM Address   VCI  Flag

ba0         -          -               -     l

ba0         hostb      -             100     t

ba0         hostc      -             101     t

on hostb:

Interface     Host    ATM Address        VCI    Flag

ba0           -                 -          -       l

ba0           hosta             -        100       t

ba0           hostc             -        102       t

on hostc:

Interface  Host   ATM Address    VCI   Flag

ba0        -      -                -      l

ba0        hosta  -              101      t

ba0        hostb  -              102      t

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

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

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

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

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.

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

Interface     Host     ATM Address          VCI           Flag

ba0           -        $myaddress             -              l

ba0           -        $prefix:$sunmacsel0    -              s

/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

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

/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

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

TABLE 3-4 `/etc/opt/SUNWconn/atm/laneconfig` Entry Descriptions
Field	Description
Interf`ace`	Refers to the LAN Emulation interface, laneN.
`MAC Address/ELAN Name`	This field is for the 6-byte MAC address of the interface, or, in the case of an n entry, the name of the emulated LAN to join.
`ATM Address`	This field is for the 20-byte ATM address. The `$myaddres`s variable assigns the local switch prefix, local MAC address, and default selector.
`VCI`	The VCI field is a positive decimal integer identifying a Permanent Virtual Circuit. Place a dash in this field if VCI is not used.
`Flag`	This field identifies the type of entry. For a complete description of the `laneconfig` flags, see .

TABLE 3-5 describes the flags used in the /etc/opt/SUNWconn/atm/laneconfig file.

TABLE 3-5 `/etc/opt/SUNWconn/atm/laneconfig` Flag Descriptions
Flag	Description
`l`	This flag designates a local address entry. There must be an `l` entry for each interface running LAN Emulation. The interface and the ATM address must be included; the MAC address may be included (default is the MAC address assigned to the board).
`t`	This flag designates a table entry for the local MAC-ATM address resolution table. If you wish to avoid the address resolution process for a frequently accessed system, for instance, you may include a `t` entry for that system; you may also create PVCs with a `t` entry. The interface, MAC address, and either ATM address or VCI (for SVC or PVC connection, respectively) must be included.
`n`	This flag allows you to specify the name of an emulated LAN to join. By default, the SunATM implementation will use the name provided by the LECS. If you wish to specify a different name, or if your LECS requires that a user include a name in its requests, a name may be provided with this flag. Interface is required; the name should be entered in the second field.
`M`	Notifies the system that a larger MTU size will be used in the ELAN which this lane instance will join. The default MTU size is 1500 bytes. With the M flag, you can set the MTU size to be either 4 Kbytes (4528 bytes) or 9 Kbytes (9218 bytes).
`a`	Represents an address that may have access to this host. If no `a` entries appear in the `laneconfig` file, access to the host is unrestricted. Including a entries allows access to be restricted to known hosts. As an alternative to listing individual addresses, the ATM address field may contain a prefix, followed by the wildcard `$anymacsel`, which matches any 7-byte ESI/Selector combination following the given prefix. This allows access by any host connected to the switch specified by the given prefix. Mac Address and VCI should not appear; ATM Address is required. See .
`c`	This flag allows an alternate LECS address to be specified. By default, the SunATM software uses the well-known address specified in the LAN Emulation standard. If, however, your LECS has a different address, or you wish to connect to the LECS over a PVC, you may provide the alternate ATM address or VCI in a c entry. If you wish to make a PVC connection, the VCI must be 17, as required by the LAN Emulation standard. The interface and ATM address or VCI must be included.
`s`	This flag specifies the LES address or VCI, and instructs the system to contact the LES directly, and to use default subnet configuration information. This flag should be used if your subnet does not have an LECS. Without this entry, the system first connects to the LECS, which provides the LES address and configuration information.
`m`	Notifies the system that the entire ATM address, including the network prefix, must be configured manually on this interface. If your interface is connected to a switch that does not support ILMI address registration, you must include this option in your `/etc/opt/SUNWconn/atm/aarconfig` file. Note that the variables `$myaddress`, `$prefix` and `$localswitch_server` (which use the switch prefix obtained from the switch via ILMI) may not be used if ILMI address registration is disabled.

TABLE 3-6 describes the required, optional, and illegal fields for each flag type.

TABLE 3-6 `laneconfig` Flag Requirements and Options
Interface	MAC Address/ELAN Name	ATM Address	VCI	Flag
required	optional	required	illegal	`l`
required	required	xor¹	xor¹	`t`
required	Emulated LAN name	illegal	illegal	`n`
required	MTU Size in bytes	illegal	illegal	`M`
required	illegal	required	illegal	`a`
required	illegal	xor¹	xor	`c`
required	illegal	xor¹	xor	`s`
required	illegal	illegal	illegal	`m`
¹xor means that you can use either the ATM Address field or the VCI field, but not both.

Note - 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 . For a complete description of how to use these variables, see ATM Address Formats and Variables.

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

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

TABLE 3-7 Predefined SunATM Variables
Variable	Description
`prefix`	The 13-byte prefix associated with the local switch.
`mac`	The 6-byte MAC address associated with the local host or interface.
`sel`	The default 1-byte selector for the local interface.
`macsel`	The concatenation of `$mac:$sel`.
`myaddress`	The concatenation of `$prefix:$mac:$sel`, resulting in the default address for the local interface.
`anymac`	A wild card representing any 6-byte ESI. Should only be used in a entries.
`anymacsel`	A wild card representing any 7-byte ESI and Selector combination. Should only be used in `a` entries.
`?`	A wild card matching one or two hexadecimal digits within any colon-separated field. For example, `$prefix:$anymac:?` is equivalent to both `$prefix:$anymac:??` and `$prefix:$anymacsel`. However, it is not the same as `$prefix:$anymacsel:0?`, which requires that the first digit of the selector byte is a `0`. This wild card should only be used in `a` entries.

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.

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

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