
Configuring and Troubleshooting Bay Dial VPN Services
8-8 303509-A Rev 00
Configuring Frame Relay on the CPE Router
If the CPE router is a Bay Networks platform, refer to Configuring Frame Relay
Services for details on configuring frame relay on an interface. Otherwise, see the
frame relay documentation appropriate to the CPE router on the home network for
detailed frame relay configuration information.
The rest of this section describes the most important Dial VPN considerations for
configuring the frame relay parameters.
• If you are using Site Manager, you can accept the default values for most
frame relay parameters. Do not change the Service Name parameter value that
the router assigns.
• Put all frame relay PVCs running virtual private network services (that is, Dial
VPN) in one service record. Do not mix them with other (routed) PVCs in the
same service record. See the frame relay documentation for a description of
service records and their use.
• Ensure that a permanent virtual circuit is configured between the gateway and
the CPE. Accept the default management type for the frame relay interface,
ANSI T1 617D.
• If you use the default service record for Dial VPN PVCs, you do not need to
configure the PVCs, because the gateway learns the DLCIs dynamically
through the Local Management Interface (LMI) protocol. If you are not using
the default service record for the Dial VPN PVCs, you must manually
configure the PVCs to a specific service record.
• You must configure two static routes from the CPE router: one to the
RADIUS client on the gateway and one to the remote node’s supernet that
services all the remote nodes in the same user community. In addition, for Bay
Networks routers, you must configure an adjacent host as the next hop for the
return messages.
Note:
For a frame relay connection, all Dial VPN circuits must be in the same
service record.
Comentarios a estos manuales