JUNOS and IOS comparisons

I've not done a blog since I passed the CCNP (had a couple of weeks of busyness at work among other things), however I thought I'd put up some info about Juniper, mainly because I'm currently in the process of studying for the JNCIA-Junos.

Currently where I work, the only Juniper devices are some firewalls over in the States, and I'm not in the security team so I've never logged on to them. I have been working with some Olives though, so I'm getting an idea for how they work (as you can see from previous blog posts).

TSHOOT Pass....CCNP get

Well, it looks like I wasn't talking out of my arse in the TSHOOT topology build, I passed it with flying colours! The pass mark was 790, I got 931.

In terms of how difficult the exam was, to be honest I didn't find it very hard at all. Once you have done a couple of tickets and get the confidence, all of it seems to fall in place. If you've passed the BSCI/ROUTE and SWITCH/BCMSN, you won't need much more to troubleshoot the topology as long as you labbed up enough when you did both exams.

TSHOOT soon...

Well, on Monday I am taking the TSHOOT exam, which I am definitely looking forward to. The topology was fun to put together, and the practice questions on Cisco's site made me confident about this one (plus all the technologies I have covered extensively in labbing scenarios already).

My blog on the TSHOOT topology seems to have been quite popular, and I'm glad people are finding it useful. My only slight reservation is that I haven't passed yet, so I don't know if I'm leading people up the garden path yet!

Links from the World Of Tomorrow

Okay, maybe I do watch too much Futurama, but sod it, it's great :D

I've seen a lot of new and good content appear recently, so I thought I'd do a little blog to get it out there, to all 5 of you reading this.

EIGRP Myths Debunked - When this guy has something to say, listen. Ivan is a genius. Also, he can articulate the reasons why I've been arguing that EIGRP isn't a "hybrid" protocol with people. Good show.

TSHOOT - How to do the topology with only minor bastardizations

So here we go, after a few days of having a life again, I'm going to go through what I did to achieve my topology that is pretty much the TSHOOT topology. I dont have all the gear to hand, and I had to bodge a couple of things round to do it with what I had available, but overall everything works as describe. This pleases me greatly :D

Current state of being

Thought I'd do a little update on whats going on now I've passed the BCMSN. As mentioned in the previous post, I feel a lot better off now that I've passed the BSCI and BCMSN, like a huge weight has lifted off my shoulders. This has meant I can now get back to a bit of a wider focus than deep on one technology.

BCMSN over

Finally, the BCMSN is done, and a huge weight off my mind is gone. The worry I had with it all was the deadline on it, but I did it with 8 days to spare, so that makes me a happy camper.

In terms of my mistakes on the first attempt which I sorted by my second, a lot of it came from topics which I'm still not sure should be on the exams. Voice I can kind of deal with to a point, as you need to know things like PoE and some QoS, but Wireless has almost nothing to do with switching other than using access ports and trunk ports, so why there is such a large emphasis on it I dont know.

Story of the first attempt

Well, as you may be able to tell by how long it has taken me to update this page, I didn't pass the BCMSN. I wasn't too far away (708, pass mark of 804), but far enough to question a few things.

More IPv6 wonderment

Okay, it isn't strictly a Cisco/Juniper blog, but I thought it was interesting enough to raise. I know, I should be studying harder for the BCMSN as its on Wednesday, but I've got another 6 hours before UFC 116 starts, so I think I've got time tonight to study...

So anyway, I've been playing with a tunnel I've had from Hurricane Electric for a LONG time. I was happy in that I could get IPv6 connectivity, however I never got round to trying to get traffic from other machines on my network to route via my Linux server for IPv6. I good half hour with RADVD though changed all that.

How to kill a switch version 407

Want to know how to kill a switch in no time whatsoever?

Do this (as long as you aren't using extended vlans, this should cover all of them): -

Switch(config)#no spanning-tree vlan 1-1024

Do that on a few in a topology with some redundant links.

Wanna see the results?

Andromeda-2950-24#sh proc cpu 
CPU utilization for five seconds: 99%/54%; one minute: 96%; five minutes: 50%

Pegasus-2950-12#sh proc cpu
CPU utilization for five seconds: 99%/52%; one minute: 97%; five minutes: 51%

Hydra2950-12#sh proc cpu
Syndicate content