Today I’ve created a nice path selection challenge for everybody.
Let’s start with the topology:
IP addressing is simple. The subnets used are 10.0.xx.y/24 where xx are the numbers of the two routers on the link (lowest router first). Y is the router number.
The situation is as follows:
R2 has an eBGP peering with R1. It receives tge default route from R1. R2 advertises this default route to R3 R2 and R3 also form an OSPF network with area 0 R2 forms an OSPF NSSA area 50 with R4 R2 redistributes the connected route to R1 into OSPF R3 forms an OSPF NSSA area 50 with R5 R4 redistributes OSPF NSSA 50 into BGP (including NSSA external routes) R5 redistributes (i)BGP routes into OSPF So the questions are:
When you look at the blueprint for the CCIE lab exam you’ll notice a lot of separate items. These often appear as disparate things. When you study them you think you understand them and are able to apply them during a test. However, they don’t test your ability to configure separate technologies in isolated environments. They will test whether you understand the technologies and are able to combine them to make a solution work.
One of the seemingly complicated things to do in BGP is conditional advertisements. This can be used to apply policy to routes and only advertise specific routes when you (don’t) have another route. For example, you only advertise a default route when you have specific routes from a peer.
Another example is when you’re connected to two ISPs, but you prefer data to traverse just one of the two links. Maybe because one link is more expensive than the other or less reliable.
Cisco has released the newest ACI version, version 4.0. Again this version includes many new features and continues implementing the ACI Anywhere strategy. This new release also comes with it’s share of new hardware.
New Hardware ACI 4.0 introduces two new switches, a spine and a leaf:
Nexus 9332C This new spine switch is a smaller version of the Nexus 9364C spine switch. It supports 32 40/100G ports and is a more interesting option for smaller fabrics.
The tasks below are the first tasks that should be performed for the lab files I’ve included in my earlier post
One of the issues I’m running into now I’ve failed my lab while studying for my second attempt is that I have used most of the resources available out there. Of course I can still learn from those resources, but it will largely be repeating stuff I’ve already done. It will help me to increase my speed and will help reinforce my knowledge, but I still wanted to have some other resources.
Yesterday was my first attempt at the CCIE RS lab. I would have liked to write here that it would also be my only attempt, but unfortunately I failed. I already knew as I was walking out of the Cisco Brussels office that I did not pass, but the e-mail I received this morning removed all (if any) hope I had left. Pass, Pass, Fail, that was my verdict. I knew I was going to fail, but a pass, pass, pass, fail would have been a little bettter.
CCIE blueprint: 2.4.a Implement and troubleshoot RIPv2
When looking at the blueprint for CCIE RIPng is not listed as a subject. However, it is good practice to have some knowledge of this routing protocol.
This post is part of a multipost series about RIP. Other posts in this series are:
RIP RIP configuration part 1 RIP configuration part 2 RIP authentication RIP summarization Miscelanious RIP commands Since IPv6 contains much longer addresses it is more difficult to use the old syntax that is used for RIP.
CCIE blueprint: 3.4.a Implement and troubleshoot RIPv2
This post is part of a multipost series about RIP. Other posts in this series are:
RIP RIP configuration part 1 RIP configuration part 2 RIP authentication Miscelanious RIP commands RIPng Because RIP is a distance vector routing protocol summarization can be applied everywhere in the topology. This makes it easy to apply policy using summarization.
For this post I’m using a very simple network shown in the diagram below.
Three weeks ago Cisco released ACI version 3.2. This is the new long-lived release version of ACI and therefore the recommended version to deploy in new deployments or when upgrading. (Versions 2.1 and 2.2 are also long-lived releases and can still be used).
Most of the really new features were introduced in the 3.0 release, but 3.2 also boasts some interesting features. The release notes list them all, but I would like to zoom in on a few of them in this post.