Agreed, and just asking for all the bugs on the platform(if you got
it) would likely give a deluge of mostly useless / incomprehensible
info. What you want to do is frame it something like this. I will be
deploying this box, to this place in my network, to offer these
services, with this code train. What are the currently known /
outstanding issues for this box in this scenario?
-Ben
On Jan 18, 2011, at 5:16 PM, Łukasz Bromirski wrote:
On 2011-01-18 22:36, Matlock, Kenneth L wrote:
I'd say the 'best' way is to go through your account team. Cisco
doesn't post all the bugs to their website. They only show the bugs
which other customers have reported, and not ones found internally.
Your account team will have access to ALL the bugs for a particular
platform/code train.
Account team job is not in any way to provide bug scrub information.
The only source of Cisco-backed-up of bug information and software
recommendation (which may, or may not depend on the other services) is
to ask Cisco Services (and pay for it) to do it.
There's a lot going on, and checking bug toolkit is just scratching
the
surface.
--
"There's no sense in being precise when | Łukasz
Bromirski
don't know what you're talking about." |
jid:[email protected]
John von Neumann | http://
lukasz.bromirski.net
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
