C H A P T E R  6

SunATM and Solaris Networking Features

This chapter discusses the SunATM and Solaris Networking features.

This chapter contains the following sections:


ATM and SNMP

Two of the ATM standards supported by the SunATM software (the User Network Interface (UNI) and LAN Emulation (LANE) specifications) include definitions of SNMP-style Management Information Bases (MIBs) relevant to those standards. These MIBs are referred to as the ATM Forum (ATMF) and LAN Emulation (LANE) MIBs, respectively.

The ATM SNMP daemon (atmsnmpd) handles requests for information in both MIBs, as well as the system MIBs, from SNMP-based network management systems (such as the SunNet Manager program), and from ilmid, when it is required, for SNMP requests coming from the switch.

atmsnmpd can be used as a forwarding agent. If you configure it as a forwarding agent, atmsnmpd will forward SNMP requests for unknown MIBs to the port specified with the forward option, -f. This allows a system to have two SNMP agents respond to requests received over the SNMP port. FIGURE 6-1 illustrates the required configuration. To set up this example configuration, atmsnmpd must be started with the parameter -f 1000 and other_snmpd must be started so that it listens on port 1000.

FIGURE 6-1 Using atmsnmpd as a Forwarding Agent

Diagram of the required configuration for using atmsnmpd as a forwarding agent.[ D ]

Note - If you do not specify a forwarding port for unknown requests, atmsnmpd will respond with a "No Such Name" error to requests for MIBs that it does not support. If you do specify a forwarding port, atmsnmpd instead forwards the request to that port. Responses received from the agent running on the forwarding port are sent to the requesting SNMP manager with no modification. If the agent does not respond, then atmsnmpd does not send a response back.



SNMP and Solaris

The ATM SNMP agent in SunATM supports a framework for SNMP agents; however, this means that its setup depends on the version of the Solaris operating environment in which it is running. This section discusses those differences, which are mostly transparent to the user.

Solaris 2.6 Through Solaris 9 Compatible Software

The Solaris 2.6 through 9 operating environments include a bundled SNMP agent that is designed to run as a master agent, binding by default to UDP port 161. Configure other agents to listen to other UDP ports and act as subagents, then configure the master agent to forward particular requests to those subagents. This framework provides a single agent at port 161 with the combined capabilities of the master agent and all the additional subagents.

The SunATM software has been designed to take advantage of this framework if it is installed on a system running Solaris 2.6, 7, or 8. The files necessary for the ATM SNMP agent to be recognized by the master agent (atm.reg and atm.rsrc) are copied under /etc/snmp/conf by the S00sunatm startup script if it detects that the system is running Solaris 2.6, 7, or 8. SNMP requests pertaining to the ATM Forum subtree (atmForum) are forwarded to the atmsnmpd from the master agent. In addition, atmsnmpd binds, by default, to port 1000, rather than 161, under Solaris 2.6 or later. The UDP port may still be changed using atmadmin, but the default will be 1000 in Solaris 2.6, 7, or 8.


ATM and Logical Interfaces

The SunATM software supports logical interfaces in the LAN Emulation environment. Logical interfaces allow you to assign multiple IP addresses to a single Emulated LAN interface. A logical interface name consists of three parts: the device name (in the case of SunATM LAN Emulation, lane); the major number, which corresponds to the lane instance number; and the minor number, which distinguishes the logical interfaces on a single physical interface. The format of a LAN Emulation logical interface name is laneN:X, where N is the major number and X is the minor number.

Each logical interface will be associated with a unique IP hostname and address. All logical interfaces on a given physical interface will be associated with the same ATM and MAC addresses. Configure logical interfaces by placing multiple entries for a given interface in the /etc/opt/SUNWconn/atm/atmconfig file.

Consider the following rules when you use logical interfaces with the SunATM software:

The following examples show the atmconfig and laneconfig files and the ifconfig -a output for a system with one physical interface, ba0. That interface runs both Classical IP and LAN Emulation under UNI 3.1, and has 4 different IP addresses. Configure the hostnames, cip0, atm0, atm1, and atm2, appropriately in /etc/hosts.

The example /etc/opt/SUNWconn/atm/atmconfig file:

Interface   UNI  CIP Hostname  LANE Instance   LANE Hostname
ba0         3.1          cip0            0              atm0
ba0          -              -            0:1            atm1
ba0          -              -            0:2            atm2

The corresponding example /etc/opt/SUNWconn/atm/laneconfig file:

Interface   MAC Address/     ATM Address  VCI   Flag
            ELAN Name
lane0           -            $myaddress    -     l

The resulting ifconfig -a output:

# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000 
ba0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 9180 index 3
        inet 192.29.235.36 netmask ffffff00 broadcast 192.29.235.255
        ether 8:0:20:7a:37:af 
lane0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
        inet 192.29.240.36 netmask ffffff00 broadcast 192.29.240.255
        ether 8:0:20:8b:6d:d0 
lane0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4        inet 192.29.241.36 netmask ffffff00 broadcast 192.29.241.255lane0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4        inet 192.29.242.36 netmask ffffff00 broadcast 192.29.242.255


Supporting Multiple Emulated LANs on a Single Interface

The SunATM software allows a single ATM interface to join up to sixteen emulated local area networks (ELANs), provided this is allowed by the switch and LAN Emulation (LANE) services. Each ELAN joined will be represented by a unique lane instance (for example, lane0 or lane1).



Note - A requirement for supporting this feature is that the adapter card be assigned multiple MAC addresses, which is supported in the SunATM/S 2.1 and SunATM/P 3.0 adapters. This feature does not work with the older SunATM/S 2.0 adapters. You can find the number of MAC addresses assigned to your SunATM adapter by using the atmgetmac(1M) command with the count option.



Configure multiple ELANs by placing multiple entries in the
/etc/opt/SUNWconn/atm/atmconfig and /etc/opt/SUNWconn/atm/laneconfig files. Each lane instance will have a unique hostname and IP address, ATM address, and MAC address associated with it. In addition, assign an ELAN name to the instance if any ELAN other than the default is to be joined. Provide this information, with the exception of the MAC address, which is retrieved from the board itself, in the /etc/opt/SUNWconn/atm/atmconfig and /etc/opt/SUNWconn/atm/laneconfig configuration files.



Note - Only one signalling protocol (for example, UNI 3.0 or 3.1) and one Classical IP instance are supported per physical interface. Specify the UNI version in the first
/etc/opt/SUNWconn/atm/atmconfig
entry for a given interface; the Classical IP instance may be specified in any entry.



The following example shows the /etc/opt/SUNWconn/atm/atmconfig and
/etc/opt/SUNWconn/atm/laneconfig files and the ifconfig -a output for a system with one SunATM interface, ba0. The interface uses UNI 3.0 for signalling, and does not run Classical IP. It joins 4 emulated LANs: the default, elan1, elan2, and elan3.

The example /etc/opt/SUNWconn/atm/atmconfig file:

Interface    UNI  CIP Hostname   LANE Instance LANE Hostname
ba0          3.0      -               0             atm0
ba0           -       -               1             atm1
ba0           -       -               2             atm2
ba0           -       -               3             atm3

The corresponding example /etc/opt/SUNWconn/atm/laneconfig file:

Interface   MAC Address/    ATM Address   VCI Flag
            ELAN Name
lane0           -            $myaddress     -    l
lane1           -            $myaddress     -    l
lane1         elan1               -         -    n
lane2           -            $myaddress     -    l
lane2         elan2               -         -    n
lane3           -            $myaddress     -    l
lane3         elan3               -         -    n

The resulting ifconfig -a output:

lo0:  flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
      inet 127.0.0.1 netmask ff000000 
lane0:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
      inet 192.29.240.36 netmask ffffff00 broadcast 192.29.240.255
      ether 8:0:20:7a:37:af 
lane1:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
      inet 192.29.241.36 netmask ffffff00 broadcast 192.29.241.255
      ether 8:0:20:7a:37:b0 
lane2:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
      inet 192.29.242.36 netmask ffffff00 broadcast 192.29.242.255
      ether 8:0:20:7a:37:b1 
lane3:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
      inet 192.29.243.36 netmask ffffff00 broadcast 192.29.243.255
      ether 8:0:20:7a:37:b2


ATM and IP Multipathing

The SunATM software supports IP Multipathing in the LAN Emulation environment. IP Multipathing allows you to create interface groups which provide stand-by interfaces which IP may failover to in the event of hardware failure between an interface and its network equipment. In addition, it allows increased network throughput by spreading traffic across the group member interfaces

Consider the following rules when you use IP Multipathing with the SunATM software: