I initially started this blog to post labs I had created for myself during my studies. I’ve noticed that I don’t get a lot of comments on the actual lab posts I make though. I’m hoping to change that, so I’ll be starting to create my own solutions to those labs in order to initiate some discussion.
I’m going to hit them at random though, so be aware :) In future I’ll post a lab, leave it for a week, and then provide my solution to it. That way you get to figure it out for yourself first. If you really are stuck the solution will be up in a week. Remember though that there is always more than 1 way to do a lab, so don’t take my solutions as gospel.
I’ll start one later and will do more whenever I have a bit of free time :)
Now that my CCIP has been completed, I’d like to dive a bit into Juniper. We have a few Junipers in our network and I’d like to learn more about them. The few times I’ve used JunOS already I’ve been impressed.
I might do either the JNCIA-ER or the JNCIS-ER. I’ll see how much time I have.
Juniper do a great job of giving LOTS of free study material on their site, so I suggest you take a look as well.
I’ve gone and configured myself a Juniper Olive (google it) for actual labbing and so on. I might just put up a couple of Juniper labs!
I’ll put up a few things here and there as I go along.
I nailed the MPLS exam this morning so that completes my CCIP!
I’d like to finish the MPLS Fundamentals book I’m reading as there is a lot of stuff in there that’s not in the exam.
After that I’d like to do my JNCIA and then start reading LOTS of books so I can eventually do my CCIE written.
The diagram is the same as my last VPN Lab. Also it uses my MPLs topology found over here: http://mellowd.co.uk/ccie/?p=522
This is the topology for this lab (click for a bigger image):
- Customer1 and Customer 2 both have MPLS vpn’s through the ISP core.
- Customer1 is using OSPF and Customer2 is using EIGRP
- Customers should have no access to each others networks
- Customers should be able to reach all their sites from all their sites
- The ISP wants to monitor the CPE routers via their monitoring server. Create another loopback on each CPE router and give them all a /32 loopback in the 172.16.1.1/24 range – i.e. 172.16.1.1/32 for CPE1, 172.16.1.2/32 for CPE2 and so on
- Ensure the monitoring router can get to all these /32 routes (and ONLY these /32 routes) – It should not know about any customer routes – CPE routers should only see their OWN loopbacks in the routing table
- Now enable CPE3 and CPE6 to see each others subnets. All other CPE routers should see no change in their routing tables