5.1 Complete, no issues
5.2 Complete, no issues
5.3 Complete, no issues
5.4 Wow, what a task. I now see why this lab gets an 8. For 2 bullet points, there is a heck of a lot of assumptions that have to be made, tons of redistribution, and a bunch of vrfs to keep track of. I actually made my way through this pretty well, but it certainly took some time. An excellent exercise to validate understanding of the big picture.
5.5, piece of cake after making it through the last task.
Monday, March 2, 2009
Sunday, March 1, 2009
IE Vol 2 SP Lab 3
Here we go with lab 3, right on schedule. Again, I'll be spending a full week on this one, taking my time to research and experiment with anything I'm not confident on. This lab moves up to a difficulty rating of 8, so I'm assuming there will be some curve balls thrown in this time.
1.1 Complete, no issues
1.2 Complete, even in transparent mode, dynamips doesn't seem to allow extended vlans on the ethernet modules.
1.3 Complete, no issues
1.4 Complete, no issues
1.5 Complete, had to change the label protocol to tdp.
2.1 Complete, no issues--no DR? use p2p or p2mp
2.2 Complete, no issues--no area authen? put it on the interface
2.3 Complete, stupid mistake. I couldn't get the isis adjacency up across the frame-relay interface. I thought there may have been some trick here since the frame-relay map had to support clns. Turns out I missed configuring isis on the interface to begin with. A dumb mistake that would have cost me valuable time in the lab.
2.4 Wrong. I used the isis password command. However, this exchanges the passwords in plain text. To do md5, an authentication key-chain must be used ala rip and eigrp.
3.1 complete, no issues
3.2 complete, no issues
3.3 complete, no issues. I'm probably splitting hairs a bit here, but the maximum prefix drops the connection when the limit is exceeded. Since the requirements specify that if the table "continues to grow to 12,000", to me this means at 12,000 the connection should be reset, meaning maximum-prefixes is 11,999. I'd hope the lab wouldn't be quite this particular, but who knows.
4.1 Complete, no issues. Here's where the tdp requirement from earlier gets specified.
4.2 Complete, no issues.
Well so far this lab is laughable. I'm assuming it's gonna it rough here shortly, because the difficulty is nowhere near an 8 so far.
1.1 Complete, no issues
1.2 Complete, even in transparent mode, dynamips doesn't seem to allow extended vlans on the ethernet modules.
1.3 Complete, no issues
1.4 Complete, no issues
1.5 Complete, had to change the label protocol to tdp.
2.1 Complete, no issues--no DR? use p2p or p2mp
2.2 Complete, no issues--no area authen? put it on the interface
2.3 Complete, stupid mistake. I couldn't get the isis adjacency up across the frame-relay interface. I thought there may have been some trick here since the frame-relay map had to support clns. Turns out I missed configuring isis on the interface to begin with. A dumb mistake that would have cost me valuable time in the lab.
2.4 Wrong. I used the isis password command. However, this exchanges the passwords in plain text. To do md5, an authentication key-chain must be used ala rip and eigrp.
3.1 complete, no issues
3.2 complete, no issues
3.3 complete, no issues. I'm probably splitting hairs a bit here, but the maximum prefix drops the connection when the limit is exceeded. Since the requirements specify that if the table "continues to grow to 12,000", to me this means at 12,000 the connection should be reset, meaning maximum-prefixes is 11,999. I'd hope the lab wouldn't be quite this particular, but who knows.
4.1 Complete, no issues. Here's where the tdp requirement from earlier gets specified.
4.2 Complete, no issues.
Well so far this lab is laughable. I'm assuming it's gonna it rough here shortly, because the difficulty is nowhere near an 8 so far.
IE Vol2 Lab 2 Complete
Well, I'm on schedule, barely, and ready to do lab 3 next week. There really wasn't anything too substantially scary in this lab. The VPN config was pretty basic and there wasn't any TE. PPPoE was new, but I felt pretty comfortable with it and know how to get to the docs. I'm also getting more comfortable with MPLS QoS. So, aside from a few knobs I think I did ok.
IE Vol 2 Section 10 Complete
10.1 Gotta love those knobs. mpls ldp tcp pak-priority. Now I never would have found this one. Guess I gotta get better at looking over the command-line options.
10.2 Pretty basic netflow setup. I'm not sure if netflow was covered in R&S, but I've worked with it enough where it wasn't an issue.
10.2 Pretty basic netflow setup. I'm not sure if netflow was covered in R&S, but I've worked with it enough where it wasn't an issue.
IE Vol 2 Section 9 Complete
9.1 Complete, no issues--just like R&S
9.2 Complete, no issues--just like R&S
9.3 Complete, no issues--just like R&S
9.2 Complete, no issues--just like R&S
9.3 Complete, no issues--just like R&S
IE Vol 2 Section 8
8.1 Complete. No issues, standard R&S stuff here. The nice part about logging denies, is I find out quickly that ospf has to be permitted in the access list.
8.2 Complete. Maximum routes in the vrf controls the size of the routing table.
8.2 Complete. Maximum routes in the vrf controls the size of the routing table.
IE Vol 2 Section 7
7.1 Complete. No issues, straight R&S stuff.
7.2 Complete. I need to remember not to use the nbar ftp, but to use an access-list of ftp, ftp-data, and gt 1023 to match ftp traffic.
7.3 Complete. I disagree with the solutions guide here. The requirements specify traffic should not be dropped "unless there is congestion in the transit path". To me this means setting DE, but the answers say to use queueing. In the lab a question to the proctor would be in order.
7.4 Complete, Qos-groups again. The key to keep in mind is that when traffic comes in an mpls interface, the only thing to match on is the mpls exp bits. Then on its way out of the router, if the tag is stripped, the exp bits are gone. So it's only possible to match on the packet itself. The other alternative is to use the Qos-group, with which the router associates an incoming packet internally, to remember to apply policies on egress.
7.2 Complete. I need to remember not to use the nbar ftp, but to use an access-list of ftp, ftp-data, and gt 1023 to match ftp traffic.
7.3 Complete. I disagree with the solutions guide here. The requirements specify traffic should not be dropped "unless there is congestion in the transit path". To me this means setting DE, but the answers say to use queueing. In the lab a question to the proctor would be in order.
7.4 Complete, Qos-groups again. The key to keep in mind is that when traffic comes in an mpls interface, the only thing to match on is the mpls exp bits. Then on its way out of the router, if the tag is stripped, the exp bits are gone. So it's only possible to match on the packet itself. The other alternative is to use the Qos-group, with which the router associates an incoming packet internally, to remember to apply policies on egress.
Subscribe to:
Posts (Atom)
Posts
