There are generally a few things you need to do to make this work: 1) Enable "frame-relay switching" on one end 2) set the frame-relay interface-type to DCE on one end, usually the side acting as the frame switch 3) Make sure you use the same DLCI on both sides.
On Fri, Mar 5, 2010 at 3:35 PM, Di Bias, Steve <[email protected]>wrote: > This would work and satisfy the requirement as far as I can see, however > there is obviously more commands involved with this approach. > > Everyone else agree? > > Steve > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Frank > Sent: Friday, March 05, 2010 12:28 PM > To: [email protected] > Subject: [OSL | CCIE_RS] Version Vol1. Lab 6 R6<->R9 links > > > Hi, > > I came up with a different solution for the missing LMI and keep-alive > on the interlinks between R6 and R9. > Instead of using "no keepalive", you can also make one side of the links > a FR switch. > > For example, if I do: > > interface MFR1 > no ip address > frame-relay intf-type dce <========= > ! > interface MFR1.69 point-to-point > ip address 150.100.69.9 255.255.255.0 > frame-relay interface-dlci 69 > ! > interface MFR1.96 point-to-point > ip address 150.100.96.9 255.255.255.0 > frame-relay interface-dlci 96 > > then R9 will act as the FR switch, and R6 and R9 will exchange LMI > status messages; and you do not have the problem that the PVC's don't > become active: > > R6# sh frame pvc | i ACTIVE.*MFR > DLCI = 69, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = MFR1.69 > DLCI = 96, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = MFR1.96 > > R9#sh frame pvc | i ACT > DLCI = 69, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = MFR1.69 > DLCI = 96, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = MFR1.96 > R9#sh frame map > MFR1.96 (up): point-to-point dlci, dlci 96(0x60,0x1800), broadcast > status defined, active > MFR1.69 (up): point-to-point dlci, dlci 69(0x45,0x1050), broadcast > status defined, active > > Questions: > > 1) Would this be an acceptable solution (it does not seem to violate any > requirements)? > > 2) Are there any drawbacks to this approach that I'm overlooking? > > Regards, > > Farnk > > > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > > UHS Confidentiality Notice: This e-mail message, including any > attachments, is for the sole use of the intended recipient (s) and may > contain confidential and privileged information. Any unauthorized review, > use, disclosure or distribution of this information is prohibited. If this > was sent to you in error, please notify the sender by reply e-mail and > destroy all copies of the original message. > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > -- Regards, Joe Astorino CCIE #24347 (R&S) Sr. Technical Instructor - IPexpert Mailto: [email protected] Telephone: +1.810.326.1444 Live Assistance, Please visit: www.ipexpert.com/chat eFax: +1.810.454.0130 IPexpert is a premier provider of Classroom and Self-Study Cisco CCNA (R&S, Voice & Security), CCNP, CCVP, CCSP and CCIE (R&S, Voice, Security & Service Provider) Certification Training with locations throughout the United States, Europe and Australia. Be sure to check out our online communities at www.ipexpert.com/communities and our public website at www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
