[c-nsp] Cisco bug locator?

[Pete Lumbis]

I can't comment on the state of the new bug toolkit (vomit) but to Mikaels
point:

Yes, there are crappy bugs. I see them every day. They are written by
humans with the information available at the time. TAC needs to do a better
job of following up on bugs after they are resolved to ensure the
information in the bug reflects the actual problem and symptom that
customers can see. It's a work in progress and sadly will never be perfect
(since again, it's written by humans). I would say you should ALWAYS open a
TAC case to fix bugs that you worry you are hitting. TAC engineers have the
resources to find further details and update the bug so it's readable (yes,
this is a pain in the ass. why should you have to open a case to translate
a bug to English? Again, bugs written by humans, generally with limited
information at the time of writing). This won't always be an easy process
but it's doable.

Regards,
Pete


On Tue, Nov 19, 2013 at 9:40 PM, Mikael Abrahamsson <swmike at swm.pp.se>wrote:

> On Tue, 19 Nov 2013, Jay Hennigan wrote:
>
>  Does anyone have a current URL for the Cisco bug toolkit that works the
>> right way around?
>>
>> The link on their website now only allows you to enter a bug ID.  I am
>> looking for the original bug tool that is actually useful, where you
>> specify the IOS version, platform, and nature of the bug, and it then
>> gives you the bug ID.
>>
>> This one is kind of useless.
>>
>> https://tools.cisco.com/bugsearch
>>
>
> Cisco has over the past years made their public bug information more and
> more useless, mostly by not documenting their bugs publically in a useful
> manner. That they would then cripple the search function would be no
> surprise to me.
>
> I have numerous times had to ask people within Cisco who have access to
> their internal tools for clarification on bugs in order to actually gain
> useful knowledge about what the bug actually is. I also had to numerous
> times ask cisco to actually publish the bug at all, just to be able to
> evaluate if a SMU should be applied or not. Yes, they released SMUs without
> the bug ID the SMU fixed being publically available. This has happened
> several times.
>
> So complain to your account team and give feedback on their website. Only
> by customers complaining will we see improvement.
>
> --
> Mikael Abrahamsson    email: swmike at swm.pp.se
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>