Mailing List Archive: Cisco: NSP

how not to write a release note

Index | Next | Previous | View Threaded

jared at puck

Nov 16, 2009, 3:11 PM

Post #1 of 9 (1034 views)
Permalink

how not to write a release note

Seems cisco is getting lazy.. SXI3 is out and this has to be
one of the worst release notes ever:

CSCta14457 - A Cisco device may report alignment errors
"%ALIGN-3-TRACE" error messages accompanied with a traceback may be reported.

Does not say anything about what may trigger it, eg: mtu,
packet fragmentation, etc..

- Jared

--
Jared Mauch | pgp key available via finger from jared [at] puck
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

reuben-cisco-nsp at reub

Nov 16, 2009, 3:27 PM

Post #2 of 9 (1000 views)
Permalink

Re: how not to write a release note [In reply to]

Well there's always this one, for a laugh:

CSCso05336
Symptoms: A Cisco 1811 router reloads when trying to connect to irc.freenode.net
during the first 36 hours following a reload.
Conditions: The symptom is observed only in the first 36 hours following a
reload. Workaround: Do not connect to irc.freenode.net the first 36 hours
following a reload.

I thought that was a joke, but it's not..

Reuben

On 17/11/2009 10:11 AM, Jared Mauch wrote:
> Seems cisco is getting lazy.. SXI3 is out and this has to be
> one of the worst release notes ever:
>
> CSCta14457 - A Cisco device may report alignment errors
> "%ALIGN-3-TRACE" error messages accompanied with a traceback may be reported.
>
> Does not say anything about what may trigger it, eg: mtu,
> packet fragmentation, etc..
>
> - Jared
>

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

ras at e-gerbil

Nov 16, 2009, 3:34 PM

Post #3 of 9 (998 views)
Permalink

Re: how not to write a release note [In reply to]

On Mon, Nov 16, 2009 at 06:11:09PM -0500, Jared Mauch wrote:
>
> Seems cisco is getting lazy.. SXI3 is out and this has to be
> one of the worst release notes ever:
>
> CSCta14457 - A Cisco device may report alignment errors
> "%ALIGN-3-TRACE" error messages accompanied with a traceback may be reported.
>
> Does not say anything about what may trigger it, eg: mtu,
> packet fragmentation, etc..

Still not as funny as this one:

CSCso05336

Symptoms: A Cisco 1811 router reloads when trying to connect to
irc.freenode.net during the first 36 hours following a reload.

Conditions: The symptom is observed only in the first 36 hours
following a reload.

Workaround: Do not connect to irc.freenode.net the first 36 hours
following a reload.

We really need a wall of shame website where people can submit the true
gems. :)

--
Richard A Steenbergen <ras [at] e-gerbil> http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

newton at atdot

Nov 16, 2009, 5:52 PM

Post #4 of 9 (996 views)
Permalink

Re: how not to write a release note [In reply to]

On 17/11/2009, at 10:04 AM, Richard A Steenbergen wrote:

> On Mon, Nov 16, 2009 at 06:11:09PM -0500, Jared Mauch wrote:
>> CSCta14457 - A Cisco device may report alignment errors
>> "%ALIGN-3-TRACE" error messages accompanied with a traceback may be reported.
>>
>> Does not say anything about what may trigger it, eg: mtu,
>> packet fragmentation, etc..
>
> Still not as funny as this one:
>
> CSCso05336

My favourite is this, from the (disastrous) 7401ASR platform:

CSCdy18641

Symptoms A router may reload unexpectedly when a Layer 2 Tunneling Protocol (L2TP) connection is established.

Conditions This symptom is observed on a Cisco 7401ASR router that is used as a Layer 2 Tunneling Protocol (L2TP) network server (LNS).

Workaround There is no workaround.

This one was particularly notable because when Cisco originally started
pimping the 7401 they said that one of the specific roles it had been
designed for was "Broadband aggregation" with "Intelligent L2TP
tunneling support."
http://www.cisco.com/en/US/products/hw/routers/ps354/products_quick_reference_guide09186a0080091fd1.html

I don't think they were ever actually useful for any role at all. The
only way I ever managed to get them to work reliably was to turn off PXF,
which totally killed their performance. Worst platform ever.

- mark

--------------------------------------------------------------------
I tried an internal modem, newton [at] atdot
but it hurt when I walked. Mark Newton
----- Voice: +61-4-1620-2223 ------------- Fax: +61-8-82231777 -----

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

avayner at cisco

Nov 17, 2009, 12:11 AM

Post #5 of 9 (975 views)
Permalink

Re: how not to write a release note [In reply to]

Jared,

I took a quick look and this has to do with QOS.
I have sent an internal query for more info. Will advise.

Arie

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of Jared Mauch
Sent: Tuesday, November 17, 2009 01:11
To: cisco-nsp [at] puck
Subject: [c-nsp] how not to write a release note

Seems cisco is getting lazy.. SXI3 is out and this has to be
one of the worst release notes ever:

CSCta14457 - A Cisco device may report alignment errors
"%ALIGN-3-TRACE" error messages accompanied with a traceback may be
reported.

Does not say anything about what may trigger it, eg: mtu,
packet fragmentation, etc..

- Jared

--
Jared Mauch | pgp key available via finger from jared [at] puck
clue++; | http://puck.nether.net/~jared/ My statements are only
mine.
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

asturluismi at gmail

Nov 17, 2009, 1:58 AM

Post #6 of 9 (977 views)
Permalink

Re: how not to write a release note [In reply to]

I can't believe it, I need to check it.

> Still not as funny as this one:
>
> CSCso05336
>
> Symptoms: A Cisco 1811 router reloads when trying to connect to
> irc.freenode.net during the first 36 hours following a reload.
>
> Conditions: The symptom is observed only in the first 36 hours
> following a reload.
>
> Workaround: Do not connect to irc.freenode.net the first 36 hours
> following a reload.
>
> We really need a wall of shame website where people can submit the true
> gems. :)
>

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

kgraham at industrial-marshmallow

Nov 17, 2009, 11:45 AM

Post #7 of 9 (964 views)
Permalink

Re: how not to write a release note [In reply to]

> Does not say anything about what may trigger it, eg: mtu,
> packet fragmentation, etc..

Though that one is higher profile, still not as bad as:

http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.2.x/release/notes/ol_6897.html#wp274407

...listed as a "Limitation and Restriction" (as opposed to "Open
Caveat") with no bug citation.

At least there's some good bug release-note authors out there,
as evidenced byCSCse14048:

Cisco X2-10GB-LR transceiver modules with a
version
identification number lower than V03 might show
intermittent
frame check sequence (FCS) errors or be
ejected from the switch during
periods of operational
shock greater than 50g. There is no workaround.

(still waiting to be able to recommend that as a possible
problem to a c-nsp poster...)
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

avayner at cisco

Nov 17, 2009, 12:57 PM

Post #8 of 9 (965 views)
Permalink

Re: how not to write a release note [In reply to]

Well, as feedback for the issue raised, the bug you flagged is not
causing anything other than a traceback message...

Arie

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of Arie Vayner
(avayner)
Sent: Tuesday, November 17, 2009 10:11
To: Jared Mauch; cisco-nsp [at] puck
Subject: Re: [c-nsp] how not to write a release note

Jared,

I took a quick look and this has to do with QOS.
I have sent an internal query for more info. Will advise.

Arie

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of Jared Mauch
Sent: Tuesday, November 17, 2009 01:11
To: cisco-nsp [at] puck
Subject: [c-nsp] how not to write a release note

Seems cisco is getting lazy.. SXI3 is out and this has to be
one of the worst release notes ever:

CSCta14457 - A Cisco device may report alignment errors
"%ALIGN-3-TRACE" error messages accompanied with a traceback may be
reported.

Does not say anything about what may trigger it, eg: mtu,
packet fragmentation, etc..

- Jared

--
Jared Mauch | pgp key available via finger from jared [at] puck
clue++; | http://puck.nether.net/~jared/ My statements are only
mine.
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

eninja at gmail

Nov 17, 2009, 4:48 PM

Post #9 of 9 (975 views)
Permalink

Re: how not to write a release note [In reply to]

That is not true. Alignment corrections are very CPU intensive
activity that may easily overwhelm a device if it occurs frequently.

Thus, per thread, users need to know (via properly written release
notes) the causes of software defects so they can take steps to
workaround or rectify them.

Eninja

On Nov 17, 2009, at 9:57 PM, "Arie Vayner (avayner)"
<avayner [at] cisco> wrote:

> Well, as feedback for the issue raised, the bug you flagged is not
> causing anything other than a traceback message...
>
> Arie
>
> -----Original Message-----
> From: cisco-nsp-bounces [at] puck
> [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Arie Vayner
> (avayner)
> Sent: Tuesday, November 17, 2009 10:11
> To: Jared Mauch; cisco-nsp [at] puck
> Subject: Re: [c-nsp] how not to write a release note
>
> Jared,
>
> I took a quick look and this has to do with QOS.
> I have sent an internal query for more info. Will advise.
>
> Arie
>
> -----Original Message-----
> From: cisco-nsp-bounces [at] puck
> [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Jared Mauch
> Sent: Tuesday, November 17, 2009 01:11
> To: cisco-nsp [at] puck
> Subject: [c-nsp] how not to write a release note
>
>
> Seems cisco is getting lazy.. SXI3 is out and this has to be
> one of the worst release notes ever:
>
> CSCta14457 - A Cisco device may report alignment errors
> "%ALIGN-3-TRACE" error messages accompanied with a traceback may be
> reported.
>
> Does not say anything about what may trigger it, eg: mtu,
> packet fragmentation, etc..
>
> - Jared
>
> --
> Jared Mauch | pgp key available via finger from jared [at] puck
> clue++; | http://puck.nether.net/~jared/ My statements are only
> mine.
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads