Showing posts with label 642-642. Show all posts
Showing posts with label 642-642. Show all posts
Tuesday, March 23, 2010
Passed Qos 642-642
Well I cleared the exam today. I'm not going to sit here and say it was easy either. It was a good hard test. I did get hit with some off-the-wall stuff, but for the most part if you knew your QoS you will be fine. Finished with about 15 minutes to spare, and an 869 score. I was a bit shocked looking at my report though, one category was in the 50%, and two in the 75'ish area. I did pretty strong in the others areas though, and I think that pulled my score up. Thanks guys, onward to BGP!
Thursday, March 18, 2010
Shaping--Part 2
Just following up a bit after my last post. Remember I ended up shaping to the average with 64000 bps as my shaping rate? I ended up with a policy that looked like this:
Now I went in a did a bit of reconfiguration. Heres what I did:
Now look at the output of a show policy-map interface:
So here you can probably see some differences from above. Right off the bat you should notice that the target rate is double what we had originally configured! Our bucket of tokens now is Bc + Be, instead of just Bc in our previous example. We get our target shaping rate from the following formula:
Rate = configured rate(1 + Be/Bc) or 64000 (1+(8000/8000)) or 64000(2)....128
So essentially this guy is configured to send up to 2000 bytes (8000 bits x 2) each 125ms interval (if the bucket(s) have that many tokens of course!). But also notice the increment bytes in this example. They are double what they were in the previous example. This is because when you shape to the peak, Bc + Be are going to be replenished each Tc.
Now I went in a did a bit of reconfiguration. Heres what I did:
R2(config)#policy-map shape_all
R2(config-pmap)#class class-default
R2(config-pmap-c)#no shape average 64000
R2(config-pmap-c)#shape peak 64000
Now look at the output of a show policy-map interface:
So here you can probably see some differences from above. Right off the bat you should notice that the target rate is double what we had originally configured! Our bucket of tokens now is Bc + Be, instead of just Bc in our previous example. We get our target shaping rate from the following formula:
Rate = configured rate(1 + Be/Bc) or 64000 (1+(8000/8000)) or 64000(2)....128
So essentially this guy is configured to send up to 2000 bytes (8000 bits x 2) each 125ms interval (if the bucket(s) have that many tokens of course!). But also notice the increment bytes in this example. They are double what they were in the previous example. This is because when you shape to the peak, Bc + Be are going to be replenished each Tc.
Wednesday, March 10, 2010
QoS 642-642 Progress
So, I finished the QoS book by Odom....awesome read! I need to go through and make some notes for the chapters though...sort of a second "glance through." I also picked up the nugget monthly streaming subscription; and am a pretty good way through them now. Good progress, I need some lab reinforcement and I should be good. Anyone know any good QoS labs (I have the ONT portfolio....).
Subscribe to:
Posts (Atom)

