Rodney and All,
Stay away from 12.3 go right to 12.4
We lost a customer because of that firmware rev. and because of Cisco's
tech support
incompetence, which had me on a wild goose chase with problems on a 1700,
and
boy was I pissed off about that one.
Bugs involved CSCeh95427, and CSCsa86946 and I finally figured this out
when
working on a problem with a completely different customer and a different
router.
Fortunately the Cisco tech that helped with -that- one knew what he was
doing.
Still not repaired in 12.3 IS repaired in 12.2 and 12.4
Ted
Message
>From: cisco-nsp-bounces (AT) puck (DOT) nether.net
>[mailto:cisco-nsp-bounces (AT) puck (DOT) nether.net] Behalf Rodney Dunn
>Sent: Wednesday, November 30, 2005 6:39 PM
>To: noc ops
>Cc: cisco-nsp (AT) puck (DOT) nether.net
>Subject: Re: [c-nsp] PPP Multilink
>
>
>Should be. I really perfer seeing people run the latest 12.3 mainline
>code for MLPPP as I remember we fixed a lot of bugs mid 12.3 for
>mlppp. 12.2(31) for basic MLPPP shold be ok but I can't remember
>if we support QS with it there though.
>
Wed, Nov 30, 2005 at 01:55:08PM -0800, noc ops wrote:
>in-line:
>>
>Rodney Dunn wrote:
>Wed, Nov 30, 2005 at 01:36:29PM -0800, noc ops wrote:
>>
>>>We are currently rolling out mlppp (6 x T1) on a 7206vxr w/ npe-400
>>>engine. Was wondering if anyone can provide insight to on
>the following
>>>questions.
>>>
>>>Is it recommended to disable fragmentation on ppp multilink?
>>
>>
>Yes. Fragmentation really isn't needed on T1 speed links.
>
>that's what i thoughtthanks.
>>
>>
>>
>>
>>
>>>Why would you want to disable cef on mlppp bundle? Can't
>remember where
>>>I saw this reference but thought that I run this by the group for
>>>confirmation.
>>
>>
>as a short term workaround to a switching patch bug but it
>should be reenabled as soon as the fix is identified.
>
>is it safe to leave it enabled on 12.2(31)?
>>
>>
>>
>regards,
>/virendra
>>
>>
>>
>>
>>>
>>>appreciate any feedback.
>>>
>>>
>>>regards,
>>>/virendra
>>>
>>>cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net
>>>
>>>archive at
>>
>>
>
>cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net
>
>archive at
>

>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.362 / Virus Database: 267.13.10/190 - Release
>Date: 12/1/2005
>
cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net
archive at

Fri, 2 Dec 2005, Ted Mittelstaedt wrote:

Rodney and All,

Stay away from 12.3 go right to 12.4

We lost a customer because of that firmware rev. and because of Cisco's
tech support incompetence, which had me on a wild goose chase with
problems on a 1700, and boy was I pissed off about that one.

Bugs involved CSCeh95427, and CSCsa86946 and I finally figured this out
when working on a problem with a completely different customer and a
different router. Fortunately the Cisco tech that helped with -that- one
knew what he was doing.

You scared me for a minute as I just upgraded two customer 1700s to
12.3.17 to get working QoS service-policies and cef. Fortunately, both
are very simple configs (one has multilink) with no NAT. Both those bug
ids are NAT issues. Did you encounter any non-NAT show stoppers with 12.3
on the 1700 series?

BTW, 12.2.latest on the 1720 accepts service-policy commands, but doesn't
appear willing to actually apply them to interfaces.

Jon Lewis | I route
Senior Network Engineer | therefore you are
Atlantic Net |
http://www.lewis.org/~jlewis/pgp for PGP public key

cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net

archive at