On Wed, Aug 12, 2009 at 02:21:43PM -0400, Rodney Dunn wrote: > If you are going to move go to the latest SRB rebuild on Cisco.com. > > There were a ton of fixes in the early SRB releases due to a huge > quality push on that throttle. > > SRC and SRD simply have less field exposure.
I can actually name quite a few major networks who are running SRC in very widespread deployment, including mine, and a couple of tier 1's. >From what I've seen this is actually the train with the most service provider field exposure, and amazingly enough (not trying to jinx it here) SRC4 has been solid for us so far. We did hit quite a few serious issues in the earlier builds, things like BGP announcements which stopped working until you deleted and readded the neighbor, rsvp that didn't actually reserve bandwidth, many SNMP counter issues, a runaway CPU loop in the BGP process, etc, but they've all been fixed in SRC4. The biggest issue we've encountered so far is that when you reload the router to upgrade to SRC4 the "switchport trunk allowed vlan" list on trunk ports tends to drop vlan IDs during the reboot (particularly on port-channels and port-channel members, causing port-channel desyncs). Comparing the before and after in rancid will save you a lot of grief, we've seen this happen at least a dozen times now so it definitely appears to be an SRC4 specific issue. -- Richard A Steenbergen <[email protected]> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
