notes: PPP over Frame-Relay (PPPoFR)

- Frame-relay does not natively support features such as authentication, link quality monitoring, or reliable transmission.
- By implementing PPPoFR, authentication of frame-relay PVCs can be implement, or multiple PVCs could be binded together using MLP.
- PPPoFR is configured through the use of a virtual-template interfaces.
- A virtual-template is a PPP encapsulated interface that is designed to spawn a “template” of configuration down to multiple member interfaces.
- When using a virtual-template interface it’s important to understand that a virtual-access “member” interface is cloned from the virtual-template interface when the PPP connection comes up, therefore the virtual-template interface itself will always be in the down/down state. This can affect certain network designs such as using the backup interface command
on a virtual-template.


note: the oly way to do authentication over FR is through PPP.

CONFIG-SET: PPP over frame-relay (PPPoFR) example
+---------------------------------------------------

STEP1: Create the virtual-template interface
- Configures all the logical options like a IP address
- Authentication is optional
NOTE: "encapsulation ppp" not needed as virtual-templates always runs PPP

interface virtual-template1
ip address 192.1.7.6 255.255.255.0
ppp chap hostname ROUTER6
ppp chap password 0 CISCO


STEP2: Configure the physical frame-relay interface and bind the virtual-template to the frame-relay PVC
Note that the order that these steps are performed are important

interface Serial0/0
encapsulation frame-relay
frame interface-dlci 201 ppp virtual-template1


verification:

sh ip interface brief | include 192.1.7.6
virtual-access1 192.1.7.6 YES TFTP up up
virtual-template1 192.1.7.6 YES manual down down