
Configuring ATM Services
1-32
303514-A Rev. 00
Configuring an ATM Service Record for ATMARP
When configuring a service record to act as an ATMARP client or server:
• Define a classical IP service record.
-- Specify SVC as the virtual circuit type for the service record. All network
devices on a LIS must connect over SVCs.
-- Specify LLC/SNAP or NULL as the encapsulation type for the service
record. RFC 1577 defines LLC/SNAP as the encapsulation type for
ATMARP.
For more information about how to create an SVC service record to run
classical IP, see Chapter 2
, “Starting ATM, ATM MPOA Server, and ATM
Router Redundancy.”
• Add IP and IP routing protocols to the circuit.
• Configure ATMARP Mode as either a client or a server.
For a description of the ATM-specific IP parameters necessary for classical IP
ATMARP operation over ATM, see “ATMARP Parameter
s” on page A-74.
For full compatibility with RFC 1577, you may have to specify a maximum
transmission unit (MTU) size of 9188 bytes. See “Defining the Interface MTU
”
on page 3-3 (for the BCC) or the Site Manager Interface MTU parameter
description on page A-4 for additional information about setting the MTU size.
When configuring the router as a client, you must define the server switch
address. The client sends ATMARP requests to the server switch address.
Note:
If you remove and replace a link module that is configured as an
ATMARP client, the client loses connectivity until the ATMARP server
registration refresh interval for that client expires (900-second default). This
loss of connectivity occurs only when the client is configured to autogenerate
the ATM address user part (see Disabling and Reenabling User Part
Autogeneration” on page 6-4 for additional information about autogenerating
ATM addresses).
Kommentare zu diesen Handbüchern