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
