atmarp(1M)atmarp(1M)NAMEatmarp - display or manage IP address to virtual circuit mappings for
TCP/IP over ATM.
SYNOPSISatmarp-a [ -nl ]
atmarp-f pvcfile [ -e default-bps ]
atmarp-d host (SPANS entries ONLY)
atmarp-p (SPANS entries ONLY)
atmarp-s host interface aal vpi vci (SPANS entries ONLY)
DESCRIPTIONatmarp-a displays the current ATM ARP table. Each interface can be
configured to use standard UNI signaling or SPANS (Simple Protocol for
ATM Network Signaling), but not both. SPANS is a signaling protocol that
was designed at FORE Systems prior to the existance of standard ATM
signaling protocols (Note: The SPANS options are only available on Origin
and Onyx2). When the ATM ARP table is displayed, the entries for the UNI
signaling interfaces will be displayed separately from the entries for
the SPANS signaling interfaces. The UNI entries are displayed first,
followed by the SPANS entries. The ATM ARP table contains IP address to
ATM address translations and IP address to virtual circuit translations
for TCP/IP over ATM. The ATM ARP table can contain both pre-configured
permanent translations (permanent virtual circuits) and dynamically
created translations (switched virtual circuits). The -l option tells
atmarp to print out ATM addresses associated with each entry in the ARP
table. The -l option only applies to the UNI entries and does nothing
for the SPANS entries. The -n option tells atmarp to print the IP
addresses in standard dot-notation instead of attempting to resolve the
IP address to a qualified host name.
For the UNI entries, each entry displayed by atmarp-a can have the
following information: an IP address, a virtual circuit (identified by
port, VPI, and VCI), an ATM address (if using the -l option), and these
flags indicating the state of the entry:
COMPL The IP address has been resolved to either an ATM
address or a permanent virtual circuit.
CONN The entry has an associated virtual circuit
(identified by port, VPI, VCI).
PEND The system is in the process of connecting to the
destination represented by the entry.
PVC The entry resolves the IP address to a permanent
virtual circuit (PVC).
VALIDATE The entry is in the process of being validated via
Inverse ATM ARP.
Page 1
atmarp(1M)atmarp(1M)
NAK The ATM ARP server has NAK'ed this IP address. It is
unreachable.
NOSNAP The associated virtual circuit is not using 802.2 LLC
SNAPs for encapsulating IP.
For the SPANS entries, each entry displayed by atmarp-a can have the
following information: an IP address, an interface name, the AAL, a
virtual circuit (identified by VPI, and VCI), and these flags indicating
the state of the entry:
SPANS The entry is infact a SPANS entry.
Pending Address resolution has begun but has not yet
completed.
Complete Address resolution is completed and the virtual
circuit has been established.
When atmarp is invoked with the -f option, it becomes a daemon that
manages permanent virtual circuits (PVCs) for TCP/IP traffic over ATM.
When atmarp-f is used to manage PVCs, it is usually invoked by the ATM
start-up script, /etc/init.d/atm, using the file /var/atm/pvc.conf as the
PVC table.
The pvcfile contains one mapping per line. Blank lines are ignored and
any characters to the right of a # character are ignored to allow
comments in the file. Each line has the following format:
IP-address port VPI VCI flags
IP-address
This is an IP address or a hostname that can be resolved to an IP
address.
port This decimal integer is the unit number of the actual ATM interface
over which the virtual circuit to this destination is established.
Note that virtual circuits to the same sub-net can go across
different interfaces and that each port can support multiple sub-
nets.
VPI VCI
These two integers are the VPI/VCI pair of the virtual circuit for
this destination. The values can be either in decimal or
hexadecimal (preceded with 0x).
flags
Currently, the only flag is n which, if set, inhibits sending of
802.2 SNAP LLC headers on IP packets sent on that VC.
Page 2
atmarp(1M)atmarp(1M)
When the -f option is used, atmarp forks off a daemon process to create
the virtual circuits for each valid line in pvcfile. The daemon process
then sleeps until it is killed. When the process is killed, the virtual
circuits will be closed and the mappings deleted.
If the daemon process is sent a SIGHUP signal, it will read the pvcfile
again, incorporate any additional mappings, and delete any removed
mappings. This allows an administrator to modify the pvcfile and have
the changes take effect by invoking killall -HUP atmarp. The -f option
applies only to UNI signaling interfaces and does nothing for the SPANS
entries.
The -d option tells atmarp to delete an entry from the table of SPANS
entries. The host entry can be specified as a hostname or IP address (in
dot-notation). The -d option applies only to SPANS entries and does
nothing for the UNI entries.
The -p option tells atmarp to purge all the entries from the table of
SPANS entries. The -p option applies only to SPANS entries and does
nothing for the UNI entries.
The -s option tells atmarp to set a PVC entry into the table of SPANS
entries. The host (remote host) can be specified as a hostname or IP
address (in dot-notation). The interface is the physical interface the
PVC is to use and is specified as the interface name as it appears in the
"netstat -i" output display. (ie. atm0) The aal is the AAL type of the
connection and must be specified as 5. The vpi is the Virtual Path
Identifier of the connection and must be specified as 0. The vci is the
Virtual Circuit Identifier of the connection and must be specified as a
number between 33 and 255. The -s option applies only to SPANS
interfaces and does nothing for the UNI entries.
EXAMPLES
Here is an example pvcfile showing three hosts:
#
#
# hostname port VPI VCI flags
# -----------------------
atm-host1 0 0 201
atm-host2 0 0 0x34
atm-host3 1 16 203 n
FILES
/etc/init.d/atm
/var/atm/pvc.conf
SEE ALSOatm(7M), if_atm(7M), if_atmarp(7M), atmconfig(1M), atmstat(1M),
ifatmconfig(1M), spansd(1m), killall(1M)
Page 3
