
Starting ATM
117374-A Rev. A 1-7
Things to Remember
When enabling protocols on a service record, keep the following in mind:
• A PVC service record requires that you add at least one PVC for the service
record to operate.
• Each ATM service record globally controls
-- All protocols for any standard PVCs and SVCs that it contains.
-- All nonbridging protocols for any hybrid PVCs that it contains.
• When you select either NULL or LLC/SNAP data encapsulation to run on an
SVC, you automatically select the technology defined in RFC 1577, Classical
IP and ARP over ATM. This technology allows you to set up logical IP
subnets within your ATM network, and provides the ability to use an address
resolution protocol to obtain information and receive that information from a
designated asynchronous transfer mode Address Resolution Protocol
(ATMARP) server. For additional information about RFC 1577 and how to
configure logical IP subnets on an ATM network, refer to Cha
pter 3.
• After you add protocols to an LLC/SNAP, NULL, or LANE switched virtual
circuit, Site Manager adds an SVC button to the ATM Service Records List
window. Clicking on the SVC button opens the SVC window. From this
window, you can view and delete individual SVCs from the service record
(dynamic mode only).
• Selecting LANE to run on an SVC service record defines that service record
as belonging to an emulated LAN. This means that any protocols on that
service record operate as if they were running over a traditional Ethernet or
token ring LAN.
Source Routing XNS
SR Spanning Tree RIP (XNS)
Translate/LB AppleTalk
XNS LLC2
RIP (XNS) DLSw
AppleTalk
Table 1-2. Protocols Supported for Standard PVCs and SVCs
(continued)
PVC Using LLC/SNAP,
NLPID, or NULL
SVC Using LLC/SNAP
or NULL (RFC 1577) SVC Using LANE 802.3 SVC Using LANE 802.5
Comentários a estes Manuais