Posted on Thursday, 9th March 2006 by sean
It’s rare that I open a case with TAC, I’m usually able to figure things out with the help of the docs or by working at it. But this past week, I’ve been involved with several cases:
Upgrade problems – After swapping the flash in a 3660, we couldn’t store an image on the new flash via xmodem. The solution ended up being for us to copy the image to DRAM, boot to that, format the filesystem, then copy the image to flash
ATM problems – After the upgrade, ATM failed. Turns out there’s a bug in the version we were upgrading from that enabled ATM payload scrambling no matter what the config said. After the upgrade, it respected the config, turned scrambling off, which meant the router couldn’t talk to its peers. See: http://www.cisco.com/en/US/tech/tk39/tk49/technologies_tech_note09186a00800d73b7.shtml#knownissue_atm_scramble
CiscoWorks won’t sync archive – Even though my CW2K server could log in to all the devices, it couldn’t pull down the configs. I still don’t understand why, but after telling CW2K to use TFTP it worked. I still ran into a bug where many switches are shown as “partial failures” because of a bug in CW2K, even though it succeeded.
CiscoWorks Netconfig jobs don’t work on switches – Still going through this one with TAC. I can run a netconfig job on routers just fine, but not on switches
policy-map editing hangs the exec session – after the above upgrade, whenever I try to create or edit a policy-map, the exec session hangs. I just opened the case on this one.
I also noticed that the CPU on the router climbed about 10%, might need a case on that to help investigate.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
Posted in General | Comments (0)
