Today was my last day at the office, and I start a new job and adventure on Monday.  What does that mean for the blog?

The biggest impact is the fact that I won’t have access to a CSM or FSWM any more.  These are two pretty unique devices, and I get quite a few questions on these guys.  I’ll try my best to recount what I know, but I’ll have to get information from buddies at the old job if research is needed.  The CSM has been a backbone of this blog for a while, so I’ll need to find another area with a similar demand for examples and configuration help.  The FWSM doesn’t measure to the same scale, but the old company casino online australia is the only one I know that runs those things, so the world may be that much poorer in FWSM information.

It’s pretty widely known that I hate Cisco 3750 switches. We’ve had so many hardware and software failures with them that I’ve got a seriously bad taste in my mouth. Since I’m leaving for a new company, I thought I’d publish some statistics while I still have access to the numbers.

Total TAC cases online casino usa european roulette opened related to 3750s: 21 Number of 3750G-12S-S replaced: 21 Number of 3750G-24TS replaced: 7 Total number of RMAs issued: 28 Total number of 3750s in the company: ~120 Failure rate: 23.3%

After several months of semi-serious job searching, I’ve landed a new position with a local company. I don’t know how much I should reveal about them, but I’m really excited to be joining their team. I’ll pass on more details as I get a feel for what Pokies is appropriate, but I’ll say that the position involves Nexus 7ks, ASR 1000s, and supporting private cloud technologies. It should be really fun and quite a new adventure for me.

I noticed a few weeks back that my blog article titles were showing up in my RSS feed as ads for cheap prescriptions. Not good. I changed all my passwords, made sure I was at the latest version of Wordpress (I was), and disabled all my unneeded plugins. The RSS feed cleared up, but my Google search results still showed I was a pharmacy; the big problem is that all the pages appeared normal when browsing over to them, so I never really noticed the bigger problem.

Are you sensing a theme lately?  Since we covered the basics of the main IGPs (I’m an enterprise guy, so no IS-IS comments, please.), I thought I’d try to describe the basics of advertising IPv6 routes over BGP.  Yet again, we’re not going to do any route manipulation or change any of the 948284928 BGP attributes.  We’re just trying to get routes exchanged.

Configuration

There’s no new version of BGP for IPv6 here.  It’s the standard BGP version 4 that we’ve all been using for years, but we’re going to take advantage of the multiprotocol support (MPBGP, RFC 2858 RFC 4760).  We’ll get to the differences in a second, but the first thing to do is to set up the BGP process as normal.  

I passed the IIUC yesterday, so now I’m a CCNA Voice.  It’s kind of belittling to get a CCNA-level certification at this point in my career, but I didn’t want to be completely left behind, so I figured I should move into some voice stuff before I’m left in the dust.

The exam was probably the best Cisco exam I’ve ever taken.  Of all the exams I’ve taken in the last few years, this is the only one that didn’t have questions with huge misspellings or grammatical errors.  I was really taken aback at that since a good portion of the questions from some of my recent CCNP exams were plain unreadable.  I think I remember leaving a comment on one IIUC question about the word “an” being left out of a description, but that was no big deal.  I’m not that obesessive-compulsive.

A few hours ago, the last of the IPv4 addresses were allocated by IANA.  Now’s the time to learn more about IPv6!  Yesterday, I posted about EIGRP for IPv6, so I think I’ll continue the trend by introducing OSPFv3, which is the IPv6 implementation of OSPF.  As always, I’m using Cisco routers here.  Just as yesterday, this is just a guide to the absolutely basics; if you want to do some funky OSPF magic, you won’t find it here - perhaps in time, though.

I’m not going to go all out like Jeremy over at Packetlife.net has, but I’m going to start to discuss a few IPv6 topics.  In time (like in September when APNIC runs out of IPv4 addresses), I’m sure I’ll ramp up the IPv6 talk, but let’s start easy and get EIGRP for IPv6 up and running.  

Configuration

There are quite a few differences between EIGRP for IPv6 (yes, that’s an official name) and the IPv4 version.  First of all, all IPv6 routing is disabled by default on a Cisco router, so, if you’re doing any routing in IPv6, you’ll want to enable it or risk smashing your head into the desk trying to figure out what’s going on.

RichardF commented on an article I wrote last November and mentioned the prompt command in the ASA.  I never set aside any time to research it, but I finally took the time today while waiting for a maintenance window.

This is one of those little things in life that make me happy.  Since the active ASA always has the same hostname and IP address, I find it hard to keep track of to which firewall I’m actually connected.  That “configurtions are no long in sync” message you get when you conf t on the standby firewall really irks me.  With the prompt command, I can see which firewall I’m on and in what state it is.