Notification Center in Cisco Catalyst Center 2.3.7.6

[Dominic Stalder]

Hi guys

I just upgraded to Cisco Catalyst Center 2.3.7.6 and saw this "new" notification center. I can see a lot of error / warning / information events corresponding to the upgrade time yesterday day evening:

Now I have two questions:

1. Are those errors "still" true or is this an historical event notification? I don't think, that they are active, otherwise the Catalyst Center would not running "normally" like it does.

2. How can I dismiss or clear those historical events from the notification center?

Thanks and best regards

Dominic

[Dominic Stalder]

Hi Eric

sorry for my late response... But as you already noted and referenced the feedback from Cisco, this Cisco DNAC version of 2.3.7.6 is pretty buggy and I am not really happy, that I have upgraded to this version.

But because we don't use it that excessively or in a critical fashion; it does not hit us that hard and I can wait for the next, hopefully less buggy version.

Regards

Dominic

, 

[Eric R. Jones]

Thank you for the reply. This provides more information when someone asks why we haven't addressed this particular CVE issue. Usually we just point out the documentation in the release notes but having a few testimonials addressing the issues at hand is always helpful.

[JEFFREY SESSLER]

I'm seeing similar things, but the errors just come back. It's as if the check fails and then recovers. Health check is clean but I've opened a TAC case just in case. I'm regretting upgrading to 2.3.6.7, and I keep seeing that there is a 2.3.6.9 referenced as fixing some stuff but I've yet to see that show up in release notes or for download.  

[maflesch]

I don't know what you mean by 2.3.6.7 and 2.3.6.9. Fixes to the notification center should be in 2.3.7.7 or at the very least 2.3.7.9. Neither of these versions are out yet which is why you don't see them in the release notes.

[JEFFREY SESSLER]

@maflesch Meaning that when I run across a bug that I may be hitting, it's often the case that 2.3.7.9 is the identified "first fixed."  Do you have an ETA on 2.3.7.7 or 2.3.7.9?  Has any thought been given to adopting more rapid/targeted releases (package level) in the same fashion that we have SMUs and APSP on the switch/wireless side? The SMU's and APSP's are great in that they target specific defects without the need to wait for the normal point releases and/or TAC special builds. 

[maflesch]

2.3.7.7 should be out by the end of the next week or two, unless something pushes the release back further. 2.3.7.9 is currently slated to be released by the end of January but will most likely be closer to March. It's all fluid.

As for the SMUs, this already exists in Catalyst Center. It was previously referred to as hot fixes, but is now officially SMUs. The first one was released on 2.3.5.6. The only problem with SMUs is that by deploying them, this can prevent you from upgrading to the next release as the SMU will have a higher package version than the next release will. 

Also, SMUs (and hot fixes) are meant for critical issues. The notification center is not a critical issue (albeit a very annoying one).

[JEFFREY SESSLER]

@maflesch As a customer, there is nothing more annoying than updating every four months, only to find out that while a couple of the bugs you were hitting are fixed, there a bunch of other new bugs that you have to live with for another 3-4 months until the next point release.   The SMUs are a viable fix for that, including for "annoying" bugs like notifications, as it helps to improve the reputation of the product.  I can showcase all the things that I like about the product (AI stuff), but at the same time, I pray at the alter each upgrade cycle hopeful that a function that has been working continues to do so.  For example, with the move to 2.3.6.x, my site analytics that worked well in 2.3.5, just don't function.

It's just weird to me that this product is built around containers and packages, yet it's always a monolithic update rather than releasing packages independently, and more frequently i.e., here is the new package the resolves the notifications bug.  If the use of SMUs breaks future updating, that feels like something the product development should address.

Sorry for the rant, but it's incredibly frustrating to be back to what feels like "Prime 1.0" days, when the modern architecture of CatCenter should allow for more frequent and targeted upgrading.  

[Will Pettit]

Has anyone managed to fix this? Upgraded yesterday and have all the same errors