From: Timur.Mirza@xxxxxxxxxxxxxxxxxx
Date: Wed Sep 06 2000 - 14:26:01 GMT-3
in the following cfg, r1<----3 serial links--->r2....one of my colleagues had a
question: if an "r3" is connected to r1 w/ a couple of serial links & you want
to run pppml, how would r1 differentiate the 3 t1s to r2 from the two new t1s t
o
r3, since there is nothing in the cfg that binds s3/5,6 & 7 to virtual-template
1? also, cisco tac said that virtual-template 1 in a down/down state when you
issue a "sh ip in br" is normal?
!on r1:
multilink virtual-template 1
!
interface Serial3/5
no ip address
encapsulation ppp
ppp multilink
!
!
interface Serial3/6
no ip address
encapsulation ppp
ppp multilink
!
interface Serial3/7
no ip address
encapsulation ppp
ppp multilink
!
interface Virtual-Template1
ip address 10.1.250.17 255.255.255.252
ppp multilink
!on r2:
multilink virtual-template 1
!
interface Serial1/0
no ip address
encapsulation ppp
ppp multilink
!
!
interface Serial1/1
no ip address
encapsulation ppp
ppp multilink
!
interface Serial1/2
no ip address
encapsulation ppp
ppp multilink
!
interface Virtual-Template1
ip address 10.1.250.18 255.255.255.252
ppp multilink
!note the following output on r1:
r1#sh ip in br
Interface IP-Address OK? Method Status Protoco
l
Serial3/5 unassigned YES unset up up
Serial3/6 unassigned YES unset up up
Serial3/7 unassigned YES unset up up
Virtual-Access1 10.1.250.17 YES TFTP up up
Virtual-Template1 10.1.250.17 YES NVRAM down down
!cisco confirmed that the virtual-template 1 is not really an interface & it
will always register as down/down (this is ok); the virtual-access interface
must be in up/up mode & its across this interface where traffic flows, includin
g
the formation of adjacencies in link state relationships, such as in ospf:
r1#sh ip o n
Neighbor ID Pri State Dead Time Address Interface
1.1.1.2 1 FULL/ - 00:00:33 10.1.250.18
Virtual-Access1
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:53 GMT-3