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
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.
a. The /etc/opt/SUNWconn/atm/aarconfig file on a client:
Interface | Host | ATM Address | VCI Flag | |
ba0 | - | $myaddress | - | l |
ba0 | - | $localswitch_server | - | s |
|
|
|
|
|
50 SunATM 3U CompactPCI Adapter Installation and User’s Guide • February 2001
