
Configuring ATM Services
1-18
308612-14.00 Rev 00
Configuring multiple PVCs per service record uses network addressing most
efficiently. Although you need to configure each PVC manually, you need only
define and associate protocols with the ATM network service record. All the
PVCs that you configure for a given ATM service record carry the protocols that
you select and configure to run on that service record.
A configuration using multiple PVCs per service record works best in either fully
meshed environments or in nonmeshed environments where systems not directly
connected to each other have no need to communicate. You can configure multiple
PVCs per service record as long as you do not need to separate protocols by PVC
(that is, all PVCs accept the same protocols).
There are, however, ways to configure upper-layer protocols, such as IP or
Internetwork Packet Exchange (IPX), to allow systems in nonmeshed networks to
fully communicate. See the documentation for these protocols for more
information.
One PVC
A configuration using one PVC per service record works the same way as one
using multiple PVCs per service record. When you define only one PVC per
service record, upper-layer protocols treat the ATM network as a series of direct
point-to-point connections, viewing each PVC as an individual network interface.
You can configure each PVC with different protocols and parameter settings. This
allows you to connect to different network sites using, for example, different types
of data encapsulation (Figure 1-7
).
Note:
When you configure multiple PVCs per service record, all PVCs use the
data encapsulation type that you set for the ATM service record. See “Data
Encapsulation Methods” on page 1-13 for more information.
Comentarios a estos manuales