Cisco 4500 Compressed Config Question

Started by Ironman, February 12, 2015, 09:26:03 PM

Previous topic - Next topic

Ironman


Quote from: wintermute000 on February 13, 2015, 02:55:19 PM
This is what TAC exists for

Geesh, maybe I'm having a bad week. I thought this site was to gather a "community" of networking folks who could bounce ideas and issues off each other. The whole point of posting an issue is to see if someone else in the "community" came across this similar issue. TAC is generally a last resort. I usually like to do some digging of my own and ask my peers if they've seen this before I go running to TAC.


deanwebb

It is a community, but I think we're all feeling a little punchy today. Nothing personal, Ironman... take it as a general "Dang, we haven't seen stuff like that" when you get ribbing like this.

Honestly, what you're experiencing makes sense in the light of the failed hardware. Let us know what happened when you have more information.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

Ironman

Thanks Dean. I guess your right. Happy Valentines Weekend everyone!

wintermute000

Ironman, I was just being brief, as you've discovered its looking more and more like a HW issue.... I just couldn't be arsed typing 'looks strongly like buggy behaviour and I'd log a TAC case regardless of whatever other research I was doing'.

icecream-guy

Quote from: Ironman on February 13, 2015, 03:44:18 PM

Quote from: wintermute000 on February 13, 2015, 02:55:19 PM
This is what TAC exists for

I usually like to do some digging of my own and ask my peers if they've seen this before I go running to TAC.

this is a waste of a whole crapload of money,  an crap, no matter how lowly, open a TAC case first, your company is paying a lot money for SmartNet,  not to use it, or to use it as a last resort is just not smart.  open first than you can go to the community. and if we resolve it before TAC does, good for us.

we have Advanced Services at work, it costs a bank, we'll open TAC cases at the drop of a hat. just cause something doesnt' look right, something reloads in the middle of the night. We open proactive cases, when we reload gear to make sure hardware is available at the local depot, in case a device take a crap.

make use of the services, man.
:professorcat:

My Moral Fibers have been cut.


Ironman

So. . . .at the end of the day it wound up being a H/W bug. I popped out the secondary sup and waited a few mins and popped it back in and BAM! It works like a charm now.

LynK

Nice. hardware bug or IOS bug? I would look at upgrading either way... just to make sure it doesn't happen again.
Sys Admin: "You have a stuck route"
            Me: "You have an incorrect Default Gateway"

Ironman

Quote from: LynK on February 24, 2015, 02:33:57 PM
Nice. hardware bug or IOS bug? I would look at upgrading either way... just to make sure it doesn't happen again.

Looks like a Hardware bug. TAC said they have seen this before and have been replacing the sups. Its a flash problem on the supervisor itself. If it happens again we will just replace it.