I started on a frame relay lab but got side tracked with the “broadcast” keyword.

gotchas:

1. PVC deleted means that frame switch does not have the dlci configured
2. PVC inactive means you have a typo in your config
3. use debug frame packet
4. point-to-point <> physical use map statements with the broadcast keyword. Broadcast enables the dlci to forward both broadcast and multicast traffic. (think RIP, OSPF, mcast, etc..)
5. set the DE bit on packets greater then 1024 bytes on dlci 502 = (global) frame-relay de-list 1 protocol ip gt 1024 (int) frame-relay de-group  1 502
6. chap = ppp over frame-relay. (virtual int, ppp authen chap, (global) username R1 password xx) ( don’t forget to remove the pertinent frame config from the serial interface and move it to the virtual-template along with the ip address!).
7. req: send full status updates of dlci’s every 180 seconds solution: doc cd = frame-relay lmi-n391dte 18
8. I went the wrong way the last question. The solution was to search the doc cd with the keywords in the question ” bytes per second & packets per second” frame-relay broadcast-queue 50 36000 90
9. DO NOT mix DR and NON-DR network types. Even though you can tweak the hello’s to form an adjacency the neighbors will not be functioning. ie sho ip route ospf = nothing
10. Ospf is not running right – check your frame-relay map statements and add broadcast where needed.
11. If your lab scenerio forbids you from using the broadcast keyword you will have to use ip ospf net non-broadcast or ip ospf net point-to-multi non-broadcast.
12. IOS will not permit OSPF neighbor statements for network types broadcast or point-to-point – only for non-broadcast and for point-to-multipoint

Broadcast keyword

Physical / multipoint interfaces = add the broadcast keyword

hub to spoke = add the broadcast keyword

spoke to hub = add the broadcast keyword

spoke to spoke = do not add the broadcast keyword

ip ospf net non-broadcast – sends unicast. You need the neighbor command.  Adding the broadcast keyword is not necessary.

side note: make sure your timers match for different ip ospf network types.

Here network types work together:

Broadcast to Broadcast
Non-Broadcast to Non-Broadcast
Point-to-Point to Point-to-Point
Point-to-Multipoint to Point-to-Multipoint
Broadcast to Non-Broadcast (adjust hello/dead timers)
Point-to-Point to Point-to-Multipoint (adjust hello/dead timers)

broadcast = 10 hello 40 dead

non-broadcast = 30 hello 120 dead

You can tweak the hello/dead with ip ospf hello-interval or ip ospf dead commands.
* An adjacency will be formed with routers running OSPF, as long as the authentication is the same, the stub flag is the same, the area is the same, and the timers are the same.

* If you mix and match network types we might need to modify the timers so we can form an adjacency. This is done with the ip ospf hello-interval and ip ospf dead-interval commands.

* You can mix and match network types as long as the network types involved have the same DR relationship. You can’t mix network types that require a DR with those that don’t require a DR.

Dont Need a DR:
Point-to-Point and Point-to-Multipoint (if you adjust timers)
Point-to-Point and Point-to-Multipoint non-broadcast (if you adjust timers)
Point-to-Multipoint and Point-to-Multipoint non-broadcast

Need a DR:
Broadcast and Non-Broadcast (if you adjust timers)

Frame relay interfaces..

1- broadcast network: no need for neighbor command, if given under the frame relay interface Broadcast keyword should be enabled on the frame relay map statements

2- non broadcast network u have to specify the neighbors statically under the ospf process… on frame relay mapping it doesn’t cares about the broadcast keyword (because the updates are going as unicast)

but it is mostly used if in frame relay due to a restriction u r not allowed to use the the broadcast keyword

3- p2mp: this network type is specially used for NBMA networks, so this is best suitable for the hub and spoke networks on frame relay…

u don’t have to give the neighbor command in ospf process, for the neighbor to come up…

u NEED BROADCAST keyword on the frame relay map statements for this to work

4- p2mp non broadcast (cisco propriety)  u need to specify the neighbor command in ospf process and on frame relay mappings u don’t need broadcast keyword.

Frame-relay

config fr to use 2 pipes and 1 ip address on both r1 and r2.

int mult 12
ip address 10.1.1.1 255.255.255.0

int virtual-template 12
ppp multi group 12

int s1/0
en frame
frame-relay interface-dlci 102 ppp virtual-template 12
no shut

int s1/1
en frame
frame-relay interface-dlci 201 virtual-template 12
no shut

sho ppp multilink
——————————————————–

no frame switch

int s1/1
ip add 10.1.1.1 255.255.255.0
no keepalives <—————— on both sides
clock rate 64000 <————— on DCE
frame-relay map ip 10.1.1.3 113

sh frame lmi <——there are no LMI’s since keepalives are disabled.
——————————————————–

usefull commands
clear frame-relay in
sh frame map
sh frame pvc
sh frame lmi
debug ip packet
debug frame-relay packet
debug fram lmi
—————————–

to config a router as a frame switch
(DCE)
conf t
frame switching
int s1/0
clock rate 64000
frame-relay intf-type dce

frame-relay intf-type

To configure a Frame Relay switch type, use the frame-relay intf-type

command in interface configuration mode. To disable the switch, use the

no form of this command.

frame-relay intf-type [dce | dte | nni]

no frame-relay intf-type [dce | dte | nni]
Syntax Description

dce
(Optional) Router or access server functions as a switch connected to a

router.

dte
(Optional) Router or access server is connected to a Frame Relay network.

nni

(Optional) Router or access server functions as a switch connected to a

switch—supports Network-to-Network Interface (NNI) connections.

Usage Guidelines
This command can be used only if Frame Relay switching has previously

been enabled globally by means of the frame-relay switching command.
————-  ——————

when routing OSPF over frame-relay physical/multi

int s1/0
frame-relay map ip 150.1.100.1 401 broadcast < —— make sure you add

the BROADCAST keyword.
———————————-

config the router so the LMI status messages (keepalives) are sent every

5 seconds and Full status LMUI requests are send every 4 cycles instead

of 6

int s1/0
keepalive 5
frame-relay lmi-n391dte 4
———————————

frame-relay lmi-n391dte

To set a full status polling interval, use the frame-relay lmi-n391dte

command in interface configuration mode. To restore the default interval

value, assuming that a Local Management Interface (LMI) has been

configured, use the no form of this command.

frame-relay lmi-n391dte keep-exchanges

no frame-relay lmi-n391dte keep-exchanges

Syntax Description
keep-exchanges = Number of keep exchanges to be done before requesting a

full status message. Acceptable value is a positive integer in the range

from 1 to 255.

Usage Guidelines
Use this command when the interface is configured as data terminal

equipment (DTE) or a Network-to-Network Interface (NNI) as a means of

setting the full status message polling interval.
Examples

In the following example, one out of every four status inquiries

generated will request a full status response from the switch. The other

three status inquiries will request keepalive exchanges only.

interface serial 0
frame-relay intf-type DTE
frame-relay lmi-n391dte 4

————————–
frame-relay lmi-n392dce

To set the DCE and the Network-to-Network Interface (NNI) error

threshold, use the frame-relay lmi-n392dce command in interface

configuration mode. To remove the current setting, use the no form of

this command.

frame-relay lmi-n392dce threshold

no frame-relay lmi-n392dce threshold
Syntax Description
threshold= Error threshold value. Acceptable value is a positive integer

in the range from 1 to 10.

Usage Guidelines

In Cisco’s implementation, N392 errors must occur within the number

defined by the N393 event count in order for the link to be declared

down. Therefore, the threshold value for this command must be less than

the count value defined in the frame-relay lmi-n393dce command.
Examples

The following example sets the LMI failure threshold to 3. The router

acts as a Frame Relay DCE or NNI switch.

interface serial 0
frame-relay intf-type DCE
frame-relay lmi-n392dce 3
———————————

frame-relay lmi-n392dte

To set the error threshold on a DTE or network-to-network interface (NNI)

interface, use the frame-relay lmi-n392dte command in interface

configuration mode. To remove the current setting, use the no form of

this command.

frame-relay lmi-n392dte threshold
no frame-relay lmi-n392dte threshold

Syntax Description
threshold =
Error threshold value. Acceptable value is a positive integer in the

range from 1 to 10.

Examples

The following example sets the Local Management Interface (LMI) failure

threshold to 3. The router acts as a Frame Relay DTE or NNI switch.

interface serial 0
frame-relay intf-type DTE
frame-relay lmi-n392dte 3
——————————-

frame-relay lmi-n393dce

To set the DCE and Network-to-Network Interface (NNI) monitored events

count, use the frame-relay lmi-n393dce command in interface configuration

mode. To remove the current setting, use the no form of this command.

frame-relay lmi-n393dce events
no frame-relay lmi-n393dce events

Syntax Description
events =
Value of monitored events count. Acceptable value is a positive integer

in the range from 1 to 10.

Defaults
2 events

Usage Guidelines
This command and the frame-relay lmi-n392dce command define the condition

that causes the link to be declared down. In Cisco’s implementation, N392

errors must occur within the events argument count in order for the link

to be declared down. Therefore, the events value defined in this command

must be greater than the threshold value defined in the frame-relay lmi-

n392dce command.

Examples
The following example sets the Local Management Interface (LMI) monitored

events count to 3. The router acts as a Frame Relay DCE or NNI switch.

interface serial 0
frame-relay intf-type DCE
frame-relay lmi-n393dce 3
——————————-

frame-relay lmi-n393dte

To set the monitored event count on a DTE or Network-to-Network Interface

(NNI) interface, use the frame-relay lmi-n393dte command in interface

configuration mode. To remove the current setting, use the no form of

this command.

frame-relay lmi-n393dte events
no frame-relay lmi-n393dte events

Syntax Description
events =Value of monitored events count. Acceptable value is a positive

integer in the range from 1 to 10.

Defaults
4 events

Examples
The following example sets the Local Management Interface (LMI) monitored

events count to 3. The router acts as a Frame Relay DTE or NNI switch.

interface serial 0
frame-relay intf-type DTE
frame-relay lmi-n393dte 3
—————————–

frame-relay lmi-t392dce

To set the polling verification timer on a DCE or Network-to-Network

Interface (NNI) interface, use the frame-relay lmi-t392dce command in

interface configuration mode. To remove the current setting, use the no

form of this command.

frame-relay lmi-t392dce seconds
no frame-relay lmi-t392dce seconds

Syntax Description

seconds    =Polling verification timer value from 5 to 30 seconds.

Defaults
15 seconds

Usage Guidelines
The value for the timer must be greater than the DTE or NNI keepalive

timer.

Examples
The following example indicates a polling verification timer on a DCE or

NNI interface set to 20 seconds:

interface serial 3
frame-relay intf-type DCE
frame-relay lmi-t392dce 20
————————-

frame-erlay point-to point
note: no need for no frame-relay inverse -arp since the interface is

point to point ( only 1 other router connects to our interface) .

int s1/0
encap frame
no shut
int s1/0.21 point-to-point
ip add 175.1.1.1 255.255.255.0
frame-relay interface-dlci 102
note: frame-relay map ip x.x.x.x 102 will kick back an error – you can

not use the frame-relay map command.
——————————————

frame-relay over multipoint and point-to- point
r1

int s1/0
en frame
no frame-relay inverse-arp
no shut

int s1/0.123 multipoint
ip add 123.1.1.1 255.255.255.0
frame-relay map ip 123.1.1.1 102
frame-relay map ip 123.1.1.2 102
frame-relay map ip 123.1.1.3 103

r2
interface Serial1/0
no ip address
encapsulation frame-relay
no dce-terminal-timing-enable

interface Serial1/0.21 point-to-point
ip address 150.1.123.2 255.255.255.0
frame-relay interface-dlci 201

r3
interface Serial1/0
ip address 150.1.123.3 255.255.255.0
encapsulation frame-relay
no dce-terminal-timing-enable
frame-relay map ip 123.1.1.1 301
frame-relay map ip 123.1.1.2 301
frame-relay map ip 123.1.1.3 301
no frame-relay inverse-arp

——————————————-

frame-relay without frame-relay mapping

int s1/0
encap frame
frame-relay interface-dlco 102 ppp virtual-template 1

int virtual-template 1
ip address 10.1.1.1 255.255.255.0
———————————————–

frame-relay and authentication
r1 and r2:
r1 should send a challenge when it’s called by r2. see ****
r2 should NOT authenticate when it’s called.
pass cisco
this authentication should be successfull even if the router’s name is

changed. see @@@@

r1
username r2 pass 0 cisco
int s1/0.12
no ip add
frame-rel interface-dlci 102 ppp virtual-template 12

int virtual-template 12
ip add 10.1.10.1 255.255.255.0
ppp authen chap callin                ****
ppp chap hostname R1                  @@@@

r2
username r1 pass 0 cisco

int s1/0.21
no ip add
frame-re interface-dl 201 ppp virtual-template 21

int virtual-template 21
ip add 10.1.10.2 255.255.255.0
ppp chap hostname R2                   @@@@
————————————–

frame-relay and authentication
R1 <> R3
r1 should not authenticate when called.
r3 should use PAP authentication when its called by R1
pass cisco13
hostname SHOULD be used for this authentication

r1
int s1/0.13
no ip add
frame-re interface-dl 103 ppp virtual-template 13

int virtual-template 13
ip address 10.1.13.1 255.255.255.0
ppp pap sent-username r1 pass 0 cisco13

r3
username r1 pass 0 cisco13
inte s1/0.31
no ip add
frame-relay interface-dlci 301 ppp virtual-template 31

int virtual-template 31
ip add 10.1.13.3 255.255.255.0
ppp authentication pap callin
================================

r1<>r4
r1 should send a challenge when its called by r4 SEE ****
r4 should use pap authenticaton when its called by r1 SEE @@@@
pass for CHAP is ciscoCHAP  SEE #####
for PAP = ciscoPAP & the hostname should be configured R1-PAP. SEE %%%%

NOTE: don’t forget to add the username!!

r1
username r4 pass ciscoCHAP                       ####
int s1/0.14
no ip add
frame-relay interface-dlci 104 ppp virtual-template 14

int virtual-template 14
ip add 10.1.14.1 255.255.255.0
ppp authentication chap callin                   ****
ppp pap sent-username R1-PAP password 0 ciscoPAP %%%%

r4
username R1-PAP password 0 ciscoPAP              %%%%
username r1 password 0 ciscoCHAP                 ####

int s1/0.14
no ip add
frame-relay interface-dlci 401 ppp virtual 41

int virtual-template 41
ip add 10.1.14.4 255.255.255.0
ppp authen pap callin                            @@@@
———————————————————

Frame-relay end to end keepalives
–configure on both ends

conf t
map-class frame-relay EEK
frame-relay end-to-end keepalive mode bidirectional

int s1/0.12
frame-relay interface-dlci 102
class EEK

To verify: sho frame end-to keep inter s1/0.12
——————————-

config EEK between R1<>R4 for 3 errors in 5 events teh subinterface

should transition to a down state. After 4 sucessfules events in a row

the interface should come back up. Keepalives should be exchanged every

20 seconds.

r1
map-class frame-realy EEK14
frame-relay end keep mode bidirectonal
frame-relay end keep error-threshold recv 3
frame-relay end keep error-threshold send 3
frame-relay end keep event-windows recv 5
frame-relay end keep event-windows send 5
frame-relay end keep success-events recv 4
frame-relay end keep success-events send 4
frame-relay end keep timers recv 20
frame-relay end keep timers send 20
int s1/0.14
frame-relay interface-dlci 104
class EEK14
————————————–

Frame-relay unnumbered

r1(config-if)#frame-relay interface-dlci 102 ppp virtual-Template 1
%vtemplate error; failed to set up PPP-FR circuit <—- this is because I

had parts of an old config where I deleted Virtual-Template1 by doing no

Virtual-Template1 but Virtual-Access1 was left behind in the config. The

SOLUTION is to either create Virtual-Template1 first or create a

differnet Virtual-Template like Virtual-Template10.

R1 (hub)

int loop0
ip add 1.1.1.1 255.0.0.0

int s1/0
en frame
frame interface-dl 102 ppp virtual-template1
frame interface-dl 103 ppp virtual-template1
frame interface-dl 104 ppp virtual-template1

int virtual-template 1
ip unnumbered

r2 (spoke)

int loop0
ip add 2.2.2.2 255.0.0.0

int s1/0
en frame
frame interface-dl 201 ppp virtual-template2

int virtual-template 2
ip unnumbered

NOTE: PPP created a host route. sho ip route 2.0.0.0/32 <– to disable

this use NO PEER NEIGHBOR-ROUTE

Problem: the hub can ping the spokes. But the spokes can only ping the

hub and not any of the spokes.
solutuon: PBR

ip local policy route-map PINGSPOKES
route-map PINGSPOKES per 10
set ip next-hop 1.1.1.1
route-map PINGSPOKES per 20

—————————————————–