Posts Tagged ‘ networking ’

For the Love of Networking or How I Learned to Stop Worrying and Love the Bomb

People usually tell you to do what you love. What they may not tell you is that you probably shouldn’t do something unless you love it.

There are obviously exceptions to this. If you need the work and can’t get anything else, you have to do what you have to do. However, with IT, the rule of “do what you love” seems particularly harsh.

I realize more and more that, with IT in general, if you don’t love what you do, you won’t get very far. You’ll probably work at a Tier I help desk for the rest of your life. While someone has to do it (and while it can be an art itself), I think most people aspire for more. Unfortunately, if you don’t love it, you won’t get any further.

As I study for my JNCIS, I have realized more and more that if I didn’t really want this, there’s no way I could pass it honestly. Sure, I could use a brain dump (read here for why not to) and pass, but that wouldn’t get me very far. I would either bomb every interview or get lucky, get hired, and then get fired within 30 days as my employer realizes I cheated on the test.

This stuff isn’t extremely simple. It’s not overly difficult, but you’re going to hate it if you don’t crave it. And if you hate it, how far do you realistically expect to get?

If you love it, don’t worry. It will all come with perseverance and dedication. Just study, ask questions, and delve deeper and deeper.


JNCIS-ENT Question of the Week #1 –


Aggregate Routes and Generated Routes are very similar. What is one of the biggest differences between the two?


Generated routes have a next-hop value of the first contributing route, whereas aggregate routes have a next-hop value of reject. Chris has it.

JNCIA Question of the Week #6 – Commit Requirements


With a clean Juniper router (one that is using the factory default configuration), what must be set before the router will allow you to commit configuration changes? How is this option set?


Chris got it right, of course. Root passwords are required to save configuration changes in Junos. The command to do so is:
set system root-authentication plain-text-password

If you’re reading this and preparing for JNCIA-Junos, be sure you know this. Even if it’s not on the exam, it’s a pretty basic skill. Don’t use Brain Dumps!

BGP, OSPF, Spans, and Bounces – Working for a Service Provider


First, I would like to say that in general, I like my job. Second, it should be mentioned that I am in a group that is often looked down upon. Third, I am good at my job.

It should also be mentioned that anything contained in this post is my own personal opinion and does not in any way reflect the views of the company I work for, my department, my bosses, my peers, or any other organizational unit or entity within my company.

Now that the disclaimer is out of the way…


Let’s get something straight. I consider my job to be vital to the continued operations and profitability of the company I work for. I do not resolve issues on my own, but instead escalate them to the support group responsible for a particular piece of equipment. This is usually DNOC IP or DNOC ATM, although sometimes it can include our server group or applications support.

I watch Netcool. For those of you not familiar, it basically collects SNMP traps from all of the network-facing equipment in our company. By network-facing, I mean network backbone and service equipment. Customer equipment and building equipment – such as a Cisco 2960 switch – is not included. Netcool tells me when something bad happens. This could be as simple as a single IMA T1 going down or as bad as an entire market losing connectivity to the rest of the network.

I’ll say it again: I don’t resolve issues. However, that being said, I can tell you why an iBGP peer dropped and then re-established. And I can do it pretty quickly. I can generally tell you why anything that I receive an alarm for happens. I’ve been doing this for less than a year now, but I feel very confident in my abilities to narrow something down. This is where the problem comes in.

The Problem

If a routing protocol bounces for a few seconds, it is generally held for 24 hours. If it stays clear, the ticket is closed.

This is simple. Why must I send the ticket to another group for something so simple? I think I’m capable of periodically checking on an interface to see if it has remained stable. If we monitored these ourselves and escalated if necessary, we could save time for the support groups. And saving the time of people that get paid more than we do means saving the company money.

When we receive traps, I can easily find a root or common cause. Not always, but often.

I hold a NOC position and title. Why, then, does it feel like I am not a member of the NOC?

The Solution

We need to raise the standard for our group. We need to be more consistent as a group and provide better information as a group. We need to increase our knowledge as a group. Everyone needs to be on the same page.

If we can accomplish those things, perception of the group should become a little more positive. Over time, it should get to the point of trust. At that time, we should be allowed to be integrated more fully into the NOC and better fulfill our entry-level position expectations.


Working for a service provider is not all that it’s cracked up to be. If I did not have such an excellent boss, I would have jumped ship longer ago in search of greener pastures. No place is perfect, but not troubleshooting is a nightmare. Do not apply for a service provider position expecting sunshine and rainbows. You may find that it is either more than you bargained for or nowhere near as challenging as what you expected. I’m not sure if there is a happy balance anywhere in there. Unless, maybe, you want to be customer-facing.