From: Danny Cox (dandermanuk@gmail.com)
Date: Sun Oct 15 2006 - 20:28:48 ART
I'm most of the way through a lab which uses virtual-templates over the
frame relay, so we have R1, R2, R5 with R5 as the hub in a hub and spoke
setup.
R5 has a circuit to each of R1 and R2 - DLCIs are 501 and 502 respectively.
In order to use a single IP address on R5, we need to use a single virtual
template for both the DLCIs, so something like:
interface Serial0/0
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial0/0.125 multipoint
frame-relay interface-dlci 501 ppp Virtual-Template1
frame-relay interface-dlci 502 ppp Virtual-Template1
virtual-template1
ip address a.b.c.5 255.255.255.0
But the routing tables on R5 do seem to get in a bit of a knot and one
route in particular comes up as
O E1 128.1.14.0/24 [110/21] via 128.1.125.1, 00:01:06, Virtual-Access2
[110/21] via 128.1.125.1, 00:01:06,
Virtual-Access1
I have NO idea why virtual-access2 (pointing to R2) gets involved, because
there's nothing out that way to advertise that route. it seems, I think, to
be an odditiy of using virtual-templates this way. it should be solidly out
R1. The routing table on R2 shows that R2 thinks this as well.
Any comments folks? I can bungle my way around it (and have done so) but
I'd like to understand this properly. All configs I've seen so far with
virtual-templates only have one DLCI per virtual-template per interface and
not this sort of setup. I'm slightly at a loss to know how to diagnose it
and would apreciate any pointers.
many thanks
Danny
This archive was generated by hypermail 2.1.4 : Wed Nov 01 2006 - 07:29:05 ART