Just recently migrated from a 6509 core with typical 3500 distribution and access switchs to a 6807 core with FEXes replacing all our other switches. Today we just got hit several (4) times by bug CSCup70579, each time this forced a reload of the system. This brought our entire company down, core, FEXes, phones, Wi-Fi, Internet, all of it. With all the FEXes (15) these reloads took perhaps a bit more than 20 minutes each time. This made it extremely difficult to troubleshoot and hit both the Sups (active and standby in the system). This was absolutely crushing to the company, and a loss of faith in our networking staff. I've never had such a negative experience with a Cisco product prior to this...the previous 6509 ran absolutely flawless and continuously for many years.
We were not made aware of the bug prior to getting hit with it. The TAC staff had a very difficult time pinpointing the problem (until it was pushed to engineering). Cisco is aware that we own this product and being on SmartNet shouldn't we receive some kind of notice via email that a critical, reload causing, issue potentially exists in our system? The bug notice was released late September and we've been sitting on that timebomb till it hit us. Is the normal procedure to search through all the bugs on Cisco's site and determine if our hardware/software is potentially affected by each one? Perhaps we've just become used to the way RedHat, Microsoft, and EMC notify their customers of critical issues and we're beginning to expect the same from Cisco...
Cisco is aware that we own this product and being on SmartNet shouldn't we receive some kind of notice via email that a critical, reload causing, issue potentially exists in our system?
Yes you can. Have you heard of Cisco Notification Service?