Tuesday, December 22, 2009
I saw the routes in the CE routers for the remote CE but wasn't able to ping. I even sourced my pings from a loopback that was being advertised in the CE-PE routing protocol. Weird.
Other than that, this was an interesting one, the 2 routers that join the 2 BGP ASes, were configured as eBGP peers and configured to send-label. Then the the eBGP VPNv4 relationship was farther spread apart, it was actually a peering of the PE to PE across 2 BGP ASes.
All in all, a good lab, but I'm troubled by why I can't seem to ping from CE to CE in either VRF.
On to the next one.
UPDATE------------ Issue resolved.
The problem was something so silly, I didn't have MPLS IP configured on R4, R5, and R6 in my ISIS domain. A good lesson, if your control plane looks good (ie your routing table) then the problem has to be in your forwarding plane. Thanks to Vignesh for his help.
Monday, December 14, 2009
Anyhow, this lab was the same setup as the last one, back to back VRFs, but uses MP-BGP to leak routes between BGP domains. The thing to note on this lab is BGP automatically filters route-targets that it doesn't need to know of (meaning it doesn't have a link configured for). So in order to exchange VPN routes it needs to stop this filtering by...
'no bgp default route-target filter' under the BGP process. That way, it can know the VRF routes and leak them between it's MP-eBGP peer of the other network.
I'm afraid my progress will continue to slow, I hope once things settle down I'll be able to return more aggressively to my studies.
Thursday, November 19, 2009
Monday, November 9, 2009
Tuesday, November 3, 2009
Router1(config-if)# area 1 sham-link 10.2.1.1 10.2.1.2 cost 40
show ip ospf sham-links
Tuesday, October 27, 2009
Monday, October 26, 2009
Thursday, October 22, 2009
Monday, October 19, 2009
Friday, October 16, 2009
Monday, October 12, 2009
Wednesday, October 7, 2009
Friday, October 2, 2009
Thursday, October 1, 2009
Wednesday, September 30, 2009
Tuesday, September 29, 2009
Thursday, September 24, 2009
Wednesday, September 23, 2009
Tuesday, September 22, 2009
Monday, September 21, 2009
Wednesday, September 16, 2009
Finished Lab 14 - HSRP/VRRP, pretty basic and easy, nothing challenging.
I have to skip 15 which is L2 VPN which requires some switch configurations and I don't have my rack up and running...
Moving on to Lab 16 - MP-BGP :)
I feel like I'm picking up some pace and now that the WB is half over or so, I feel a bit more motivated to finish it up.
Tuesday, September 15, 2009
Thursday, September 3, 2009
Monday, August 24, 2009
I figure I'll finish up lab 10, re-read RSVP and TE and then do lab 11.
Someone in the blogosphere had mentioned a CiscoPress book for MPLS/Service Provider that dealt with configurations... anyone recall what that book is? I'm thinking I would like to see some more configs.
Tuesday, August 4, 2009
Tuesday, July 28, 2009
This is how I keep it straight or understand it in my head:
- Address-family VPNV4 is used for PE to PE, to exchange VPN routes - implying that multiple VRFs will cross these peerings.
- Address-family IPV4 VRF XXX is used for PE to CE, to exchange IPV4 routes with the "customer" - implying that the interface connecting to the CE is in VRF XXX.
If this isn't right, I hope someone corrects me :)
Monday, July 27, 2009
I have to say, I'm much happier with IPX Vol 1 then I was with INE Vol 1. None the less, it doesn't hurt to study off of multiple vendors and I plan on doing so. What does "hurt" is the order, which I had done IPX V1 first. Lesson learned.
Thursday, July 23, 2009
Task 6.1- General ISIS config
- when configuring ISIS, start by using the NET command and then assign interfaces to the ISIS process with ip router isis command under the interface
- the NET command includes the area, system ID, and selector-byte, ie, net 51.0001.000.c800.0001.00
- to prevent loopback interfaces from forming adjacencies use the passive-interface command under the router process
Task 6.3 - ISIS Link auth
- ISIS Link authentication - under the interface use the command isis password xxx level 2. Specifying level 2 when the link is between 2 different areas
Task 6.4- ISIS Area auth
- SNP authentication/Area authentication is done under the router process area-password xxx authenticate snp validate
Task 6.5 - TLVs
- New metric style is wide. Using "transition" will allow the router to accept the old metric style too. Under the router process, metric-style wide transition
Task 6.6 - timers
- adjust timers like Hello interval and multiplier under the interface.
Task 6.7 & 6.8 Redistribution
- when redistributing connected interfaces, create a route map to be as specific as possible, then redistribute, redistribute connected route-map NAME level-1-2, the "level-1-2" specifies that it will be advertised through both level 1 and 2 routers.
- when redistributing static routes, create a route map to be as specific as possible, and you can set a metric on a specific route in order for it to be NOT advertised. Set the metric to the maximum to accomplish this in the route-map.
So ISIS is new to me and this lab was my first exposure to ISIS. Therefor, writing notes will help keep thing straight in my mind and for future reference.
Monday, July 20, 2009
Oh well, I can always re do the lab to solidify what I'm reading.
Wednesday, July 15, 2009
Lab 1 was Frame Relay - nothing new to learn, just some good re-enforcement of things I knew.
Lab 2 was ATM - all new to me!
Lab 3 and 4 I may have to skip for now, until I get access to some switches (my R&S rack is at my 'rents house, powered down).
Off to work on Lab 5 - OSPF, hopefully I'll have the same experience as Lab 1.
Monday, July 13, 2009
I have experience with IPX (in regards to R&S) so my expectation is set, I'm sure they did an excellent job in SP as they've done in R&S.
... I feel like the monkey has gotten off my back... for now.
Friday, July 10, 2009
I'm still not happy with INE Vol1's lack of explanation and I'm looking forward to finishing and moving on to something more thorough. I'm about a quarter finished... I sure am dragging my feet. :)
Tuesday, June 23, 2009
Tuesday, June 16, 2009
Where are the explanations in the answer guide?!?!?! If Vol 1 is supposed to be the beginning of the prep for CCIE SP, I would think they would give you at least some verbiage on the solution. Nope, nothing but configuration and verification.
I find that without reiteration of what everything means, I don't learn but I end up memorizing which isn't going to help me in the long run.
waa waa waa... just crying is all.
Thursday, June 4, 2009
60 questions, passing is 70%. Multiple guess and was pretty easy. I understand about getting the word out about Juniper networking products and can see why it would be beneficial to have Juniper certified people out there in the industry, but do you have to make the test THAT easy?
I get that making it hard would be discourage people, they'll think "why study for this when I can use my time to study for CCNA or something else?" but there's got to be a better solution then making it easy to the point where you question whether it has any merit at all...
I like JUNOS, I like J-WEB, and I liked using the Netscreens in the past and I think competition is a great thing. I would've liked to come out of the test feeling like I accomplished something challenging, but that's just my opinion.
Back on track to Service Provider.
Monday, June 1, 2009
Tuesday, May 26, 2009
So I posted a rough method of what I plan on doing and in what order. Next is to determine the amount of time and the number of repetitions I'll need to do.
I'm also thinking it's probably a good idea to attend a class or bootcamp, I know for R&S it definitely helped pull everything together.
For now, I'm working on INE vol 1 :)
Monday, May 18, 2009
You would think a weight would be lifted because step 1 has been fulfilled... Nah, instead I'm already feeling the drive/pressure/pseudo anxiety from knowing that the Lab is waiting for me. :)
Well, now on to organizing my plan of attack, will post it once I figure it out!
Monday, May 11, 2009
Still, I'm feeling good that it's starting again. :)
Monday, April 27, 2009
off topic - if your employer "helped" to get you your CCIE, ie, paid for training, paid for the exam, gave you time at work to study...
What do you owe them in return? If anything?
Friday, April 17, 2009
Work has gotten a bit busy with a new project and I'm squeezing in reading time whenever I can.
Can't wait to get the written over with and start doing some labs.
Monday, April 13, 2009
Thursday, April 9, 2009
Tuesday, April 7, 2009
MPLS is an incredible technology, very intelligent, can be complex or simple, but very powerful none the less. I can see the benefits to both the Service Provider and the Customers.
An interesting miss-conception that I had about WHY you should go with MPLS, the thought that it's a "faster" network because it doesn't have to look up destination IPs instead it simply looks at the label appended to a packet, was blown out of the water. And it should've been obvious too... Routers are getting so much faster and smarter so the resources used to do an IP look up now is nominal AND its not "slow" by any means. There are more COMPELLING reasons why MPLS is the WAN technology to go with.
I think I made a good choice in pursuing SP, I work for an SP and so I can kind of relate to it better, making it that much more interesting. Although the argument can be made that it's not valuable in the "real world" meaning outside of the SP realm but it's good to know both the enterprise side and the service provider side. The only disadvantage I can see is opportunity cost :) Not being able to study VOICE or SECURITY or more importantly have a life :)
Sunday, April 5, 2009
Surprisingly, it's starting off as a quick read, I'll let you know more once I'm done and if I still feel that way :)