On to IP Services (IEWB1)

Started IP Services of IEWB1, I was originally going to do Security, but skimming through that section it uses a Common Config based in IP Services. No Breakdowns for this section either but it's pretty straight forward. One of those things where you have to do Steps A-Z to get something to work, not anything that really needs explanation or has much deviation.

That was fast... (done with IEWB1 IPv6)

Didn't take more than 45 mins to finish IPv6. It's a little disappointing, as it took longer to set up the topology then to execute the configurations. Also, the section is very sparse, touching only on the very basics like configuring the different types of IPv6 addresses and IPv6 on Frame.

What should it have had? Oh maybe configurations of RIPng, OSPFv3, etc? Considering that on a real/mock lab they'll probably ask you to configure some routing.

I'm trying not to let the lack of info in the workbook frustrate me. :)

Back on Track!

So after some uncertainty with what direction I should be going and losing motivation, I'm back on track. I'm still pursuing IEWB1, specifically IPV6, and I plan on finishing the workbook out.

Sometimes, you need to step away and not do anything related to the CCIE, I did just that yesterday. It helps you keep in touch with reality and is actually rejuvenating.

I did watch this older video, its of Carl Honore, speaking about the benfits of Slowing Down...

So Long to Mike Down from IPExpert...

Word on the street is that Mike Down, training adviser and friend, has left IPExpert. Great guy who's been a big help for me.

Check out the post at:
http://mdownipexpert.blogspot.com/

Questions?

So I pose this question to you.

If you were financially able to quit your job in order to dedicate your time to studying for the CCIE lab, would you? Has any one weighed the pros and cons of doing this? What factors did you consider in making your choice?

Feel free to respond in the comments. I'd really like to see other peoples perspectives.

Reviewing the Fundamentals.

So after some loss in motivation and feeling overwhelmed with work and getting into more advanced labs in class. I'm going to focus on some fundamentals. Reason being, I can't know everything that IOS is capable of but what I know for a fact is that routing protocols should be known like the back of my hand (in order to be at least some what successful on the lab). I think once I'm confident with the fundamentals, to the point of being able to see the config in my head, I'll have the confidence to move forward and learn other things or at least learn where I can find "other things" in the DocCD.

I'm no longer searching for materials, I think I have too much materials in fact (thats a good problem to have, I guess). I'm going to deep dive into the things I do have.

Reviewing Class Labs.

Decided to stray away from Multicast, at least for today. I'm going over some of the class labs, taking my time to evaluate my thought process.

I'll be re-starting multicast next week.

Completed QOS (IEWB1)

Well... sort of. I did all the labs minus the last 3 and that's because the configs were one liners.

Most of the QOS stuff, especially the early labs in the section, was stuff I already knew. As before, the end of the section was disappointing due to the fact that there were no breakdowns. I think it's important for tech labs to end with a breakdown of the features of a particular technology, it's a good way to summarize what you had just executed. The alternative is to turn to the Doc CD and I guess that equally important.

So what's next? I think I'll tackle Multicast and then I may put away this workbook and look at some of the other material I have. Still undecided.

Frame Relay Traffic Shaping (notes)

There are some things I didn't know about Legacy Frame Relay Traffic Shaping (FRTS).

For instance you could apply a map-class to a specific dlci and you can also create a priority queue by calling a priority list within a map class and then subsequently apply the Map class to an interface or specific dlci.

Configlet:


!
interface Serial1/0
ip address 159.1.0.1 255.255.255.0
encapsulation frame-relay
ip ospf network broadcast
serial restart-delay 0
no dce-terminal-timing-enable
no fair-queue
frame-relay traffic-shaping
frame-relay map ip 159.1.0.2 102 broadcast
frame-relay interface-dlci 102
class SHAPE
no frame-relay inverse-arp
!
!
map-class frame-relay SHAPE
frame-relay cir 56000
frame-relay bc 560
frame-relay be 80
frame-relay priority-group 1
priority-list 1 protocol ip high udp 16000
!


Here some advanced configurations that incorporate MQC, per DLCI shaping, priority queueing.

!
!
class-map match-all VOICE
match ip rtp 16384 16383
!
!
policy-map PER_VC_POLICY
class VOICE
priority 32 4000
class class-default
fair-queue
!
!
!
interface Serial1/0
ip address 155.1.0.4 255.255.255.0
encapsulation frame-relay
ip ospf network broadcast
serial restart-delay 0
no dce-terminal-timing-enable
frame-relay traffic-shaping
frame-relay map ip 155.1.0.5 405 broadcast
frame-relay interface-dlci 405
class SHAPE
no frame-relay inverse-arp
!

!
map-class frame-relay SHAPE
frame-relay adaptive-shaping interface-congestion 1
frame-relay cir 64000
frame-relay bc 640
frame-relay be 0
frame-relay mincir 56000
service-policy output PER_VC_POLICY
frame-relay fragment 80



@ some point I'll post equations to derive things like Bc and Be.

QoS (notes)

So I originally went through Narbik's GAP book and took notes when doing the QoS section (QoS Post)

Here are some additional notes:

Legacy Custom Queue: creates a bandwidth reservation in the output queue of an interface. First create a queue-list to define traffic type to a queue number. Once the queues are defined, reserve bandwidth for each of the queues created, this is done by determining a byte-count. The byte-count is a ratio of the bytes in a particular queue to the entire byte-count of all queues. (Custom Queueing supports 16 queues, 15 usable/configurable queues)

Configlet:

queue-list 1 protocol ip 1 tcp www
queue-list 1 protocol ip 2 tcp smtp
queue-list 1 default 3

queue-list 1 queue 1 byte-count 5000
queue-list 1 queue 2 byte-count 2000
queue-list 1 queue 3 byte-count 3000

Apply this to an interface (and it's only out-bound queueing)

(config)# interface fas0/0
(config-if)# custom-queue-list 1


Legacy Priority Queueing: uses 4 queues, High, Medium, Normal and Low. Priority queueing uses a round robin sequencing to service the queues, it checks to see if there are any packets in the High queueing, then moves on to Medium and so on. The issue with Priority queueing is that there is the potential of starving the lower queues if there are packets constantly in a higher queue. Configuring Priority Queueing is very simlar to Custom Queueing.

Configlet:

priority-list 1 protocol ip high tcp telnet
priority-list 1 protocal ip medium tcp ftp
priority-list 1 protocol ip normal
priority-list 1 default low

Apply the list to an interface:

priority-group 1

QoS (IEWB1) and IPExpert's VoD.

Last night, I watched Scott (VoD from IPExpert) talk for about 30 mins (I cut it short because it was getting late) on Tips and Strategy. I found that from the first 30 mins, I believe he'll keep your attention which is critical when having to hear someone lecture/teach. I'm glad his personality plays a part in the lesson otherwise, if it were straight tech talk, I'd lose interest fairly quickly.

I've decided to continue on with IEWB1 mainly because I'm more then 60% done with the book. I know if I stop now, I'll wonder what it's in the other 40%. So I've started QoS and they've re-introduced the breakdowns, I may start losing interesting once they take those away.

misc...

So it's here! The interface is slick! I'm liking the quality of the videos too! The labs are online in member's section and are pretty well secured.

On another note, I spent the morning at Cisco's office to sit in on a presentation on Wide Area Application Services or WAAS. It waas interesting (pretty lame joke.)

So I've got more then enough material to go through and it should keep me busy for the next few months.

Mike Down @ IPExpert - Great offers!

Just saw Mike's twitters and I surfed on over to his blog (which can be found on the right) to find some really great deals!

Lab vRack rentals BOGO! Buy one, get one free! Plus if you buy 10 or more sessions you get the Labs eBook free! All you have to do is contact Mike @ mdown@proctorlabs.com and in the subject field include "I READ YOUR BLOG - I WANT THE DEAL!"

On a related note...

I actually decided to opt in and get the Blended Learning Solution from IPExpert, I wasn't too excited with the materials I was using and I figured having a lot of different material would be beneficial anyway. Plus I've heard great things about the BLS! I can't wait to get and go through it! I'll post more on it once it arrives.

Terry's Class Lab 1 (Class)

Yesterday was Terry's second class. We spent the morning reviewing and doing a walk through of Lab1.

Some things to remember:

- There are 2 ways to edit/create VLANs Vlan data base and in global config mode. The major difference is that for 29xx, 35xx, and 37xx you can use the Vlan database mode because these switches don't have SUP modules. Since the 65xx and 45xx switches have multiple SUPs they need to synchronize their configs, ie, there vlans. In order to support sync, you should configure these switches using global config mode, vlan database doesn't automatically sync.

- Routers have line vty 0 4 while switches have line vty 0 15. So when configuring telnet passwords, you should get all 16 on switches or you may lose points.

- ip default-gateway is used when a switch is acting as a layer 2 device only. Once you enable ip routing then you need a default route and ip default-gateway will no longer be sufficient.

- When asked to configure the "best" authentication, this means MD5.

- Summarising can happen at many different points in a network, read carefully to determine where the task is asking for summarising.

- Filters block the propagation of routes, it doesn't necessarily mean that the destination is unreachable. You can have routes blocked but if you have a default route, traffic can still exit a router and find a path known my the next hop to destination you just route filtered out.

- Aliases, I need to start using Terry's aliases, they save time but more importantly he doesn't help you if he can't use his aliases.

In the afternoon we started Lab2. We were able to complete this lab in the allotted time but when I asked how long it should take to complete, it should only take 2.5 hours.