Jump to content
Sadikhov IT Certification forums

moekad

Members
  • Content Count

    254
  • Joined

  • Last visited

  • Days Won

    1

moekad last won the day on June 19 2013

moekad had the most liked content!

Community Reputation

2 Neutral

About moekad

  • Rank
    Advanced Member
  1. moekad

    CCIE Lab Scoring

    hey friends, i got a question!! how much do we need to pass CCIE R&S Lab ? is't correct we must need for TS: 80% and Config 80% ?? or TS + Config (overall) 80% and above? Thanks in advance
  2. moekad

    Help with Policy

    hey, i have little question!! i have configured: policy rate 128000 I know IOS Default Bc = 128000/32= 4000 Byte when i start to download, the rate kept 2KB/s or 1KB/s why? if i raise the Tc for ex: 128000/10 = 12800 Byte so the config would be: policy rate 128000 12800 the download rate would go thru 16KB/s so !! what's happening with me? Does this mean we should always tune the Bc ? thanks
  3. moekad

    egress queue

    i found that trick i did some research ==) assume assume we have link 100mbps and: srr-queue bandwidth shape 10 0 0 0 srr-queue bandwidth share 0 40 30 30 Queue1: 1/10 x 100Mbps = 10Mbps 100 - 10 = 90Mbps are shared among queue 2,3,4 then for Queue 2: 90Mbps x 40 /(40+30+30)= 36Mbps For queue3 : 27Mbps for queue 4: 27Mbps So Queue1 + Queue 2 and queue 3 and Queue4 10 + 36 + 27 + 27 =100Mbps as Total Port Bandwidth cool =) and so one =) regards =)
  4. moekad

    srr-queue QOS

    just for information, i have spend hours/ days reading about srr and i found this: hxxp://www.cisco.com/en/US/products/hw/switches/ps5023/products_tech_note09186a0080883f9e.shtml they said about "priority queue-out" => Enabling Priority Queue: When you configure this command, the SRR weight and queue size ratios are affected because there is one fewer queue participating in SRR. This means that weight1 in the srr-queue bandwidth shape or the srr-queue bandwidth share command is ignored (not used in the ratio calculation). All four queues participate in the SRR unless the priority queue is enabled, in which case the first bandwidth weight is ignored and is not used in the ratio calculation. Priority queue is serviced until empty before the other queues are serviced. You enable the priority queue by using the priority-queue out interface configuration command. So regardless SRR or WRR will end up with starvation if we didn't control that Queue administratively...
  5. moekad

    egress queue

    if yes, then this may end with starvation because i found at: hxxp://blog.internetworkexpert.com/2008/03/03/bridging-the-gap-between-3550-and-3560-qos-part-i/ they said: "Finally, SRR provides support for priority queue but this queue is not subject to SRR shaping limits as well. The weight assigned to the priority queue is simply ignored for SRR calculations." Thanks
  6. moekad

    egress queue

    hey i just want to ask i'm stuck with this : assume we have link 100mbps and: srr-queue bandwidth shape 10 0 0 0 srr-queue bandwidth share 0 40 30 30 Queue 1 : 1/10 = 10Mbps => priority Queue 1 Queue 2 : 40 /100 = 40 Mbps Queue 3 : 30 /100 = 30Mbps Queue4 : 30/100 = 30Mbps we we know, Share Queue are the remaining bandwidth of the Shape so if we add them: 10 + 40 + 30 + 30 = will be 110 why ? i mean the remaining bandwidth must be: 100 - 10 = 90Mbps but Queue 2,3,4 = 100Mbps Please, also i need to know if i enable " priority-queue out" , does this mean Queue1 weight will be ignored regardless shape / share mode? Thanks
  7. moekad

    srr-queue QOS

    ya correct, few minutes ago i read about that, if i didn't control Priority Queue 4 correct, i might end of starvation for the remaining queue also i read at:hxxp://www.cisco.com/en/US/tech/tk389/tk813/technologies_tech_note09186a00801558cb.shtml for ex if i have: wrr-queue bandwidth 4 6 5 5 and priority Queue is enabled for Queue 4 : wrr will be implement in 2 ways: 1) either WRR per packets mean: 4 out of 15 packets from Queue 1 will be send 2) per bandwidth: or 26% of bandwidth from Queue 1 will be send at least that what i understand =)
  8. moekad

    srr-queue QOS

    Thanks =) that's why i love wrr more thanks again for your time ... =)
  9. moekad

    srr-queue QOS

    Thanks well QoS for the switch is confusing my last question, i did alot research now i think i understand this ex: wrr-queue bandwidth 4 6 5 5 wrr-queue cos-map 1 6 7 so CoS 6,7 at Queue 1 : 4 /20 x 100 = 20% now my question, Does this mean: it will take 20 packets from Queue 1 ? or it will utilize up to 20% of link bandwidth? Thanks i just want to clear my mind regard this =)
  10. moekad

    srr-queue QOS

    thanks =) but i just need to make sure, In production we use share and shape mode at the same time ? as this config: Switch(config-if)# srr-queue bandwidth shape 25 0 0 0 Switch(config-if)# srr-queue bandwidth share 30 20 25 25 1) what's the advantage if queue 1 is the priority queue which we shape it at : 25% and we config it at share mode up to 30% ? if we use both Share/shape mode at the same time? 2) at egress we use Shape to hard limit Priority queue to prevent any starvation... at the ingress queue, we use Priority queue but there's no shape at the ingress queue!! The "priority-q bandwidth" will prevent PQ from using all bandwidth to prevent starvation!! am i right?
  11. moekad

    srr-queue QOS

    Thankss alot my last question... what's the advantage of configure: Shape and Share mode at the same time under the same interface ex: Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# srr-queue bandwidth shape 25 0 0 0 Switch(config-if)# srr-queue bandwidth share 30 20 25 25 as i read, the share will take advantage and can go above it's limit while shape is a hard limit Always priority Queue at egress = Queue1 right? in Read production network, we will configure both Share/Shape mode at the same time?
  12. moekad

    srr-queue QOS

    Thanks for your reply... yeah it's very confusing =) what i understand from your, is in the following: mls qos srr-queue input bandwidth 90 10 mls qos srr-queue input priority-queue 2 bandwidth 20 Queue2 is the priority queue, if there's no packets arrived to Queue1 , it will send up to 20% only as hard limit ? while Queue1 can take the advantage and use the "unused bandwidth" from Queue2 + it's bandwidth if there's no packets arrived to Queue2? Thanks alot
  13. moekad

    srr-queue QOS

    hey!! i have a question... I'm stuck with this.. if i have: Distribution1(config)#mls qos srr-queue input bandwidth 90 10 Distribution1(config)#mls qos srr-queue input priority-queue 2 bandwidth 20 Does this mean: Queue 2 has bandwidth of: 20 + 10%? and Queue2 guarantee minimum 30% and can go up to 100% of bandwidth if Queue1 has no packets ? Thanks alot
  14. moekad

    AF QOs

    Thanks for your help in everything =)
  15. moekad

    AF QOs

    i have found this site: hxxp://routing-bits.com/2009/07/21/qos-priority-levels/ in it they wrote: But if you had AF33 & AF21, AF33 is a more important class, therefor AF21 will be dropped first. I may consider this is wrong right? i mean what if i set for AF21 WRED min threshold 24 and max threshold 30 while AF33 WRED min threshold 20 and max threshold 30 This mean: AF33 will be drop first right? i mean we can't consider AF33 is more important than AF21 , they all may result based on the WRED configuration!! am i right? thanks
×