On 8 March 2016 at 07:49, Gert Doering <[email protected]> wrote: > Hi, > > I'm not exactly sure how that relates to patch ordering and SMUs, tbh - > this is just a bug (and an annoying one, and testing should have caught > it before it was ever shipped) - but "slapping on 4.3.4SP10, instead > of patching" would have brought it as well, no?
Well bit a rant from me there, sorry ;) This issue didn't show up in lab testing and we haven't been able to replicate it (nor have TAC). It seems to be something about the ordering of patching and that was the point I wanted to highlight but poorly eluded to. A fresh 4.3.4 install then add SP10 and it "just works". This box was 4.3.4 default, then some SMUs, then SP6 and then SP10 (each upgrade was suggested by TAC because of a different issue ocuring over the lifecycle of the box). We shall have to wait an see what XR 6 brings. Cheers, James. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
