Narbik Labs: Frame Relay notes

Lab 1: Hub and Spoke using Frame-Relay Map Statements

• On a multipoint interface, the router can’t ping itself unless you add a frame-relay map statement pointing the interface IP to one of the DLCI’s.
• When configuring frame-relay maps on the spokes, don’t use the broadcast keyword for mappings to other spokes.  Otherwise, the hub will get redundant routing information (broadcasts/multicasts).
• The keepalive command controls the LMI Status inquiry interval, and the frame-relay lmi-n391dte command controls the complete status enquiry interval.
• Status inquiries are LMI type 1 inquiries, full status inquiries are LMI type 0 inquiries.

Lab 2: Hub and Spoke using Point-to-Point Subinterfaces

• No need to manually disable inverse-arp when using subinterfaces.
• On a point-to-point interface, the router can reach all IP addresses (including itself) without a mapping, as long as the IP is in the routing table with a valid next hop.

Lab 3: Mixture of Point-to-Point and Multipoint Frame Relay

No notes.

Lab 4: Multipoint Frame Relay without Frame Relay Mapping

Using PPP between spoke and hub to distribute layer 3 information

! Hub
int serial1/0
  encap frame
  no ip address
  frame-relay interface-dlci 102 ppp Virtual-Template 1
  frame-relay interface-dlci 103 ppp Virtual-Template 1
  frame-relay interface-dlci 104 ppp Virtual-Template 1
!
int virtual-template 1
  ip address 150.0.0.1 255.255.255.0
!

! Spoke 2
int serial1/0
  encap frame-relay
  no ip address
  frame-relay interface-dlci 201 ppp Virtual-Template 2
!
int Virtual-Template 2
  ip address 150.0.0.2 255.255.255.0
!

• The virtual template ID must be different on each spoke, even though it’s the same on all DLCIs on the hub.

Lab 5:  Frame Relay and Authentication

• Yeah, I need to deep-dive on PPP authentication.  Very, very weak here.

Lab 6:  Frame Relay End-to-End Keepalive

map-class frame-relay FREEK12
 frame-relay end-to-end keepalive mode bidirectional
!
int ser1/0.12 point-to-point
 frame-relay interface-dlci 102
  class FREEK12
!

Timers that can be used to adjust FREEK:

frame-relay end-to-end keepalive [send|receive]

• timer
• error-threshold — how many failures must occur before the interface goes down
• success-events — how many successes must occur before the interface comes up
• event-window — how many recent events to consider when testing error-threshold or success-events