ccie,java,安全,教程,文集,资料,工具书
CCIE-LAB
rate-limit input access-group 180 800000 150000 200000 conform-action set-prec-transmit 5 exceed-action set-prec-transmit 1
access-list 180 permit tcp any any eq telnet access-list 190 permit udp any any eq domain
7.0 Multicast STEP 1 (2 points)
1. Allow Multicast traffic to traverse CK13's ATM 2/0 interface. However, ensure that the multicast address 225.13.13.13 does not go in or out of the ATM 2/0 interface. To get the multicast traffic to pass across the ATM cloud, we are going to specify the PIM mode for the interface. We then want to limit which multicast groups traffic can pass across the link. We want all of the multicast traffic to go across except the 225.13.13.13 group. We are going to accomplish this with the ip multicast boundary command. We are going to create an access list that denies the specified group and permits all others, and then apply the access list to the multicast boundary so that only those groups specified in the access list are denied. The multicast boundary will stop the specified multicast groups both inbound and outbound.
CK13:
interface ATM2/0
ip pim dense-mode
ip multicast boundary 50
access-list 50 deny 225.13.13.13 access-list 50 permit any
8.0 CBWFQ STEP 1 (4 points)
1. Translate the following Custom Queue list into a CBWFQ and apply it outbound to CK13's Serial 1/0 interface. Don't use access lists to identify the traffic.
Study Guide From
IT认证部落 CCIE-LAB
2. 3. 4.
queue-list 1 protocol ip 1 udp 53 queue-list 1 protocol ip 2 tcp 23 queue-list 1 protocol ip 3 udp 123
5. 6. 7. 8. 9. 10.
queue-list 1 protocol ip 4 queue-list 1 default 5 queue-list 1 queue 1 byte-count 2000 queue-list 1 queue 2 byte-count 2000 queue-list 1 queue 4 byte-count 2500 queue-list 1 queue 5 byte-count 2000
Here, we are going to translate this Custom Queue list into a CBWFQ. When doing this, there are a couple of important things to remember. It states that we cannot use access lists to accomplish this. We need to know what protocols the port numbers given to us correspond to. UDP 53 is DNS; TCP 23 is TELNET; and UDP 123 is NTP. We also need to know that the default byte-count of a queue is 1500. There is no byte-count listed for queue 3, NTP, so it will have the default byte-count of 1500. To figure out what percentages of bandwidth each of these queues are going to have for the CBWFQ, we are going to add up the total byte count of all the queues and treat that as 100% of the bandwidth. Once we have our 100%, we are going to divide the individual queues to find our percentages.
We have 2000, 2000, 1500, 2500, and 2000. Adding those together, we get 10000 as our total bandwidth. If we divide each of the queues by 10000, we will come out
with:
DNS = 20% of the bandwidth Telnet = 20% of the bandwidth NTP = 15% of the bandwidth IP = 25% of the bandwidth Default = 20% of the bandw