“Just because you are a
"Just because you are a character doesn't mean that you have character." - The Wolf (Pulf Fiction)
I'm still in the office... multicast video streams at MPEG1 compression (about 1 Mbps) are all good but some subscription MPEG4 at one of the buildings on our MAN is choppy. My friend is prepping the network for some live subscription coming up so corporate peops can watch TV on their desktops for this internal presentation. They asked me to look into what's wrong. Unfortunately, I'm the cleaner. It's like calling Mr. Wolfe in Pulp Fiction. When it gets down to the wire and they are out of answers, they come to me. I would like to shoot the individual that gave me that reputation. I am not Mr. Wizard. I'm just an ordinary guy like everybody else and, contrary to popular belief, I am not the magic eight ball with the answers to all their problems. However, it is my job to find the answers... wherever they might be hiding, so that's what I do... find answers. Often, if I'm lucky, I can blow some dust off some atrophied corner of my brain and get what I need without a lot of research or looking too far... but sometimes it's work... digging and testing and troubleshooting and lions and tigers and bears... oh my! Part of the new responsibilities I took on this morning were knowledge deficiency items that I have been meaning to brush up on for some time now and could never find the free clock cycles to accomplish that task, so I will carry a heavier burden for a while until I get up to speed, but it is something that will make me a better network engineer in the long run and thus more valuable to my employer (whomever that may be). Plus, it may spur some motivation to carry through with my plans to achieve a second CCIE this year. We'll see... it's not likely, but it's a nice goal to have. Ahhhh yes, back to the subject at hand... so, I get asked to help with this multicast performance issue this afternoon. I'm convinced that it is isolated to systems at that location that have some common element that is thus far unknown to me and not a problem with the network system performance or bandwidth. It is definitely not bandwidth. Most of these folks are only bottlenecked at the fast ethernet NIC... the rest is gigabit fiber through and through. The bottom line is this: for me to do any further troubleshooting, I must drive to that location. Fudge. I was planning on going home... umm... now. It doesn't look like that is going to happen any time soon. So, off I go... work work work. I miss EL.
...no, I really miss her.
I'm still in the office... multicast video streams at MPEG1 compression (about 1 Mbps) are all good but some subscription MPEG4 at one of the buildings on our MAN is choppy. My friend is prepping the network for some live subscription coming up so corporate peops can watch TV on their desktops for this internal presentation. They asked me to look into what's wrong. Unfortunately, I'm the cleaner. It's like calling Mr. Wolfe in Pulp Fiction. When it gets down to the wire and they are out of answers, they come to me. I would like to shoot the individual that gave me that reputation. I am not Mr. Wizard. I'm just an ordinary guy like everybody else and, contrary to popular belief, I am not the magic eight ball with the answers to all their problems. However, it is my job to find the answers... wherever they might be hiding, so that's what I do... find answers. Often, if I'm lucky, I can blow some dust off some atrophied corner of my brain and get what I need without a lot of research or looking too far... but sometimes it's work... digging and testing and troubleshooting and lions and tigers and bears... oh my! Part of the new responsibilities I took on this morning were knowledge deficiency items that I have been meaning to brush up on for some time now and could never find the free clock cycles to accomplish that task, so I will carry a heavier burden for a while until I get up to speed, but it is something that will make me a better network engineer in the long run and thus more valuable to my employer (whomever that may be). Plus, it may spur some motivation to carry through with my plans to achieve a second CCIE this year. We'll see... it's not likely, but it's a nice goal to have. Ahhhh yes, back to the subject at hand... so, I get asked to help with this multicast performance issue this afternoon. I'm convinced that it is isolated to systems at that location that have some common element that is thus far unknown to me and not a problem with the network system performance or bandwidth. It is definitely not bandwidth. Most of these folks are only bottlenecked at the fast ethernet NIC... the rest is gigabit fiber through and through. The bottom line is this: for me to do any further troubleshooting, I must drive to that location. Fudge. I was planning on going home... umm... now. It doesn't look like that is going to happen any time soon. So, off I go... work work work. I miss EL.
 |
...no, I really miss her.
Whoah...scary dude. Look at my latest post. I swear I came here to read yours AFTER I posted mine.
Here’s to the cleaners, firemen and other fine folks who get shit done.
it must have been all of that smellin-each-others-farts-in-the-baby-ward action back in ‘71… we’ve mind melded and didn’t even know it…
btw, for those that didn’t know it, theSpaceMonkey and I were (actually) born 3 days apart in the same hospital and farted a lot in the same infant ward… we be crazy like that
Post a comment