Skip to main content

Amusing log messages

I give Cisco credit for fully documenting firewall log messages. In theory this gives users the ability to set up a system for catching interesting log messages and ignoring uninteresting messages. More vendors should be so bold as to actually acknowledge that their products log messages, and that those messages need to be documented.

This level of disclosure has an interesting side effect. I'm not sure what I'd do if one of our ASA's  logged this error:
Error Message    %ASA-2-716515:internal error in: function: OCCAM failed to 
allocate memory for AK47 instance
Explanation    The OCCAM failed to allocate memory for the AK47 instance.
Or this error:
Error Message    %ASA-2-716508: internal error in: function: Fiber scheduler is scheduling 
rotten fiber. Cannot continuing terminating
Explanation    The fiber scheduler is scheduling rotten fiber, so it cannot continue terminating. 

Fiber rot?

An AK47 instance?

No doubt those messages mean something to someone  at the TAC. For the rest of us, they are mostly just amusing.

Comments

  1. When I read those, I get nostalgic for the days when error code documentation would tell you something other than what the error message says. If I went to Cisco's site to find an explanation for an error code (and I sometimes do), I'd like to get a better explanation for an "ASA-2-716515:internal error in: function: OCCAM failed to allocate memory for AK47 instance" message than, "The OCCAM failed to allocate memory for the AK47 instance."

    Yeah, thanks for that. Makes me glad I took the time to look it up.

    ReplyDelete
  2. Oracle wizards amaze me sometimes. I was in Oracle training once and our instructor challenged us to give her an Oracle error message she didn't know.

    I think maybe two or three got her, out of 15 or 20.

    They're pretty easy to google, but this site is pretty fantastic

    ReplyDelete
  3. Never bring a razor to a semi-automatic assault rifle fight.

    ReplyDelete

Post a Comment

Popular posts from this blog

Cargo Cult System Administration

“imitate the superficial exterior of a process or system without having any understanding of the underlying substance” --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:Failing to understand the difference between necessary and sufficient. A daily backup is necessary, b…

Ad-Hoc Verses Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to …

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:
In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. The…