[c-nsp] Crash bug in SXH3
Charles Spurgeon
c.spurgeon at mail.utexas.edu
Wed Sep 3 15:07:50 EDT 2008
To which I will add another warning: there is also a fatal crash bug
in SXH3 that is triggered by removing a route-map.
The CSCsk21935 buginfo heading is: "Crash in ipfib_policy_forward
after remove policy route-map" This bug is internally viewable only
and we got the heading info from the TAC. It's apparently related to
this publicly viewable bug: CSCsm75286
This bug in combination with an apparent hardware error on a Sup720
left one of our core routers equipped with dual sup720s crashed and
sitting in rommon.
We are informed that SXF code also has the route-map bug, but we have
more confidence in that code (having removed route-maps in it many
times without problems) so we have reverted to SXF6 while awaiting a
new SXH build.
-Charles
Charles E. Spurgeon / UTnet
UT Austin ITS / Networking
c.spurgeon at its.utexas.edu / 512.475.9265
On Thu, Aug 07, 2008 at 10:59:40PM +0100, Phil Mayers wrote:
> All,
>
> Just a warning, there is a fatal crash bug in SXH3 related to using SCP.
> Considering the release notes claim fixes in that very area, this is
> highly amusing (note: issue may not actually be amusing)
>
> Does anyone else think the 6500 software train is becoming a bad joke?
> SRC claims *today* ISSU using dual sups / SSO, a much larger chunk of
> (33) features e.g. 6vpe etc. and one presumes a faster rate of ports
> from mainline IOS because they don't need to modularise everything.
>
> SXH on the other hand has... erm... buggy modularity. And... buggy
> monolithic too.
>
> I haven't got a TAC case open because we've rolled back to SXH2a (which
> has its own set of crash bugs, but less frequent ones...) and it's late
> - a task for tomorrow I feel.
> _______________________________________________
> 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/
More information about the cisco-nsp
mailing list