Anyone having a problem with the MLP not coming up after a router restart. Had to bounce the interface last night when I started the lab. Using 12.4(22)YB. Will switch to the official T version tonight or tomorrow night. Seem to remember someone else having this issue.
From: Aamir Panjwani [mailto:[email protected]] Sent: Friday, June 26, 2009 12:59 AM To: Michael Ciarfello; OSL Group Subject: RE: [OSL | CCIE_Voice] FRTS and MLP issue yep auto qos is good for FRF12 and MLP but what about class based shaping and VATS we can't do auto qos right? Also, do you enable auto qos on all 3 routers or only on HQ? Thanks From: Michael Ciarfello [mailto:[email protected]] Sent: Friday, 26 June 2009 1:35 PM To: Aamir Panjwani; OSL Group Subject: RE: [OSL | CCIE_Voice] FRTS and MLP issue I've heard you might need to do both sides. SO prepare for that. If you do the autoqos (which I usually do) it will take care of that for you. Autoqos, copy, paste to notepad, edit, paste back in. I don't remember running into having to shut / no shut interfaces, but a good reminder. Thanks. ________________________________ From: Aamir Panjwani [[email protected]] Sent: Thursday, June 25, 2009 9:38 AM To: Michael Ciarfello; OSL Group Subject: RE: [OSL | CCIE_Voice] FRTS and MLP issue I only bounced HQ serial interface and it came good! Took me ages to figure this out... From: Michael Ciarfello [mailto:[email protected]] Sent: Thursday, 25 June 2009 11:33 PM To: Aamir Panjwani; OSL Group Subject: RE: [OSL | CCIE_Voice] FRTS and MLP issue I've heard of that with virtual-templates. Did you have to do both sides of the connection? From: [email protected] [mailto:[email protected]] On Behalf Of Aamir Panjwani Sent: Thursday, June 25, 2009 3:33 AM To: OSL Group Subject: Re: [OSL | CCIE_Voice] FRTS and MLP issue Nevermind guys, I had to bounce the physical serial interface to get the WAN going From: [email protected] [mailto:[email protected]] On Behalf Of Aamir Panjwani Sent: Thursday, 25 June 2009 12:59 PM To: OSL Group Subject: [OSL | CCIE_Voice] FRTS and MLP issue I have just configured MLP between HQ and BR2 and now my WAN link is not coming back up. I have pretty much followed the WAN QOS exercise video by Vik. Any help would be much appreciated HQ config ***************** class-map match-any media match ip dscp ef class-map match-any signal match ip dscp cs3 match ip dscp af31 policy-map wan-edge class media priority percent 33 class signal bandwidth percent 5 class class-default fair-queue interface serial0/2/0 frame-relay traffic-shaping interface serial0/2/0.2 point-to-point frame-relay interface-dlci 202 ppp virtual-template100 class FRTS interface virtual-template100 bandwidth 768 ip address 142.212.65.1 255.255.255.252 ip ospf mtu-ignore ip pim dense-mode ppp multilink ppp multilink interleave ppp multilink fragment-delay 10 service-policy output wan-edge map-class frame-relay FRTS frame-relay cir 768000 frame-relay mincir 768000 frame-relay bc 7680 frame-relay be 0 BR2 config **************** class-map match-any media match ip dscp ef class-map match-any signal match ip dscp cs3 match ip dscp af31 policy-map wan-edge class media priority percent 33 class signal bandwidth percent 5 class class-default fair-queue interface serial0/2/0 frame-relay traffic-shaping interface serial0/2/0.1 point-to-point frame-relay interface-dlci 102 ppp virtual-template200 class FRTS interface virtual-template200 bandwidth 768 ip address 142.212.65.2 255.255.255.252 ip ospf mtu-ignore ip pim dense-mode ppp multilink ppp multilink interleave ppp multilink fragment-delay 10 service-policy output wan-edge map-class frame-relay FRTS frame-relay cir 768000 frame-relay mincir 768000 frame-relay bc 7680 frame-relay be 0 ************************** Sh ip int brie Virtual-Access1 unassigned YES unset down down Virtual-Access2 unassigned YES TFTP down down Virtual-Access3 142.212.65.1 YES TFTP up down Virtual-Access4 unassigned YES TFTP down down Virtual-Template100 142.212.65.1 YES manual down down ************ Sh frame-relay pvc 202 PVC Statistics for interface Serial0/2/0 (Frame Relay DTE) DLCI = 202, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/2/0.2 input pkts 16 output pkts 225 in bytes 5536 out bytes 12320 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 0 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts 0 in DE pkts 0 out DE pkts 0 out bcast pkts 19 out bcast bytes 6346 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 00:16:54, last time pvc status changed 00:16:54 Bound to Virtual-Access3 (down, cloned from Virtual-Template100) cir 768000 bc 7680 be 0 byte limit 960 interval 10 mincir 768000 byte increment 960 Adaptive Shaping none pkts 225 bytes 12320 pkts delayed 0 bytes delayed 0 shaping inactive traffic shaping drops 0 Queueing strategy: fifo Output queue 0/40, 0 drop, 0 dequeued ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
