beautypg.com

Using variables in the aarconfigfile, Using variables in the, Aarconfig – Sun Microsystems 3U User Manual

Page 69: Table 5-3, Using variables in the aarconfig file

background image

Chapter 5

Editing SunATM Configuration Files

47

TABLE 5-3

describes the required, optional, and illegal fields for each flag type. If a

field is unused, it is represented by a hyphen.

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

ba

1 entries, etc.

Using Variables in the

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.

Note –

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

.

TABLE 5-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

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.