From: Cal Michael (cmichael@network-data.com)
Date: Fri Dec 12 2003 - 15:33:08 GMT-3
- All,
I have came across the following problem,
er feature with a favorite PPP feature,
multilink.
The virtual-template interface would
not go into an up/up state which appeared
to prevent frame-relay from being usable
until a shut/noshut was performed on the
ISDN interface which had become activated
(successfully) after a full device reload.
The lab configuartion was:
<<<Main Frame Relay Configuration>>>
ip cef
multilink virtual-template 1
policy-map FRTS-SHAPING
class MEDIA
priority 96
interface Serial0/0
bandwidth 256
no ip address
encapsulation frame-relay
frame-relay traffic-shaping
frame-relay lmi-type ansi
interface Serial0/0.121 point-to-point
frame-relay interface-dlci 121 ppp Virtual-Template1
class Voice-EPVC
interface Serial0/0.131 point-to-point
frame-relay interface-dlci 131 ppp Virtual-Template1
class Voice-EPVC
map-class frame-relay Voice-EPVC
frame-relay cir 128000
frame-relay bc 1280
frame-relay be 0
frame-relay mincir 128000
service-policy output FRTS-SHAPING
frame-relay fragment 160
interface Virtual-Template1
bandwidth 128
ip address 192.168.10.2 255.255.255.252
ip tcp header-compression iphc-format
load-interval 30
max-reserved-bandwidth 85
service-policy output FRTS-SHAPING
ppp multilink
ppp multilink fragment-delay 10
ppp multilink interleave
ip rtp header-compression iphc-format
<<<ISDN Configuration>>>
username changeme password changeme
interface BRI1/0
no ip address
encapsulation ppp
dialer pool-member 10
isdn switch-type basic-ni
isdn spid1 80055512120101 5551212
isdn spid2 80055512120102 5551212
no cdp enable
ppp authentication chap
ppp multilink
interface Dialer1
ip address 192.168.254.2 255.255.255.252
encapsulation ppp
dialer pool 10
dialer remote-name changeme
dialer idle-timeout 900
dialer string 8005554567
dialer load-threshold 80 outbound
dialer-group 1
ppp authentication chap
ppp multilink
I suspect that the ISDN interface is
attempting to utilize / bind to the
virtual-template interface for some
reason; but I would think that this
would again occur when the ISDN
interface was brought up again, which
it doesn't.
Is the use of multilink groups an
appropriate solution to this, and if
so, how should it be applied to the
configuration? Or is there another
way?
--- Thanks ---
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:39 GMT-3