The table describes the commands used in this activity.
Baseline QoS Measurement Lab Commands
Command Description
show ip interface [brief] [type] [number]
Lists a summary of an interface IP information and status
clear counters Clears the interface counters
show interfaces [interface-
id]
Displays the administrative and operational status of all interfaces or a specified interface
shutdown Disables an interface
copy running-config startup- config
Saves your entries in the configuration file
Job Aid
This job aid is available to help you complete the lab activity:
Your assigned workgroup pod number provided by the instructor
Task 1: Baseline Measurement of Network Traffic
You will clear interface counters on Cisco routers and switches.
Activity Procedure
Complete these steps:
Step 1 Verify that the S0/0 and S0/1 interfaces on both of your workgroup routers (WGxR1 and WGxR2) are administratively enabled.
Step 2 Clear the interface counters on both of your workgroup routers using the clear
Note At this time, your instructor has not yet started the Pagent and Callgen router traffic generations.
Activity Verification
You have completed this task when you attain this result:
You have cleared interface counters on Cisco routers and switches.
Task 2: Identify Interface Statistics
You will identify interface statistics.
Activity Procedure
Complete these steps:
Step 1 From the WGxR1 workgroup router, perform an extended ping to the WGxR2 router serial 0/0 interface, then record the ping response time in the table at the end of the lab. For the extended ping, use a repeat count of 100 and a datagram size of 160.
WGxR1#ping Protocol [ip]: Target IP address: 10.2.x.2 Repeat count [5]: 100 Datagram size [100]: 160 Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort.
Sending 100, 160-byte ICMP Echos to 10.2.x.2, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 8/8/13 ms
Step 2 Repeat the extended ping two more times and record your results in the table at the end of this lab.
Step 3 Repeat Step 1 and Step 2, but ping from the WGxR2 to WGxR1 serial 0/0 interface and record the response time results in the table at the end of this lab.
Step 4 From both of your workgroup routers, issue the show interfaces serial 0/0 command and record the highlighted stats below in the table at the end of the lab.
WGxR1#show interfaces serial0/0 Serial0/0 is up, line protocol is up Hardware is PowerQUICC Serial Description: to WGxR2
Internet address is 10.2.3.1/24
MTU 1500 bytes, BW 384 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, LCP Open
Open: CDPCP, IPCP, loopback not set
Last input 00:00:03, output 00:00:01, output hang never Last clearing of "show interface" counters 00:00:12
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queuing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/21/32 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 288 kilobits/sec
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 3 packets output, 184 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
Step 5 Clear the interface counters on both of your workgroup routers using the clear
counters command.
Step 6 Notify your instructor when you are done with the prior steps. Your instructor will start both Pagent and Callgen traffic generators. Your instructor will advise you when all traffic streams are operational.
Activity Verification
You have completed this task when you attain this result:
You have identified interface statistics.
Task 3: Use Commands and Tools to Gather Network Response
Time Data After Both Pagent and Callgen Traffic Generators
Are Sending Traffic
You will use Cisco IOS monitoring commands and network connectivity tools (ping) to gather network response time data.
Activity Procedure
Complete these steps:
Step 1 From the WGxR1 workgroup router, perform an extended ping to the WGxR2 router serial 0/0 interface, then record the ping response time in the table at the end of the lab. For the extended ping, use a repeat count of 100 and a datagram size of 160.
Caution Before initiating the extended ping command, wait for the Pagent and Callgen traffic to run for at least one minute so that the traffic generation can stabilize.
WGxR1#ping Protocol [ip]: Target IP address: 10.2.x.2 Repeat count [5]: 100 Datagram size [100]: 160 Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort.
Sending 100, 160-byte ICMP Echos to 10.2.x.2, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 12/62/220 ms
Caution After the Pagent traffic generation has been started, it is important that the Pagent routers not be used for network measurements using ping and traceroute commands, because the Pagent routers maintain a very high CPU load in generating the traffic demands for the QoS course labs.
Step 2 Repeat the extended ping command two more times and record your results in the table at the end of this lab.
Step 3 Repeat Step 1 and Step 2 but ping from the WGxR2 to WGxR1 serial 0/0 interface and record the response time results in the table at the end of this lab.
Step 4 From both of your workgroup routers, issue the show interfaces serial 0/0 command and record the highlighted statistics below in the table at the end of the lab.
WGxR1#show interfaces serial 0/0 Hardware is PowerQUICC Serial Description: to wgxr1
Internet address is 10.2.x.1/24
MTU 1500 bytes, BW 384 Kbit, DLY 20000 usec,
reliability 255/255, txload 130/255, rxload 37/255 Encapsulation PPP, LCP Open
Open: CDPCP, IPCP, loopback not set
Last input 00:00:02, output 00:00:00, output hang never Last clearing of "show interface" counters 00:01:20
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1023 Queueing strategy: weighted fair
Output queue: 0/1000/64/1023 (size/max total/threshold/drops) Conversations 0/32/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 288 kilobits/sec
5 minute input rate 57000 bits/sec, 116 packets/sec 5 minute output rate 196000 bits/sec, 211 packets/sec 6595 packets input, 800344 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 9418 packets output, 826272 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
Note The traffic sent between Pagent-1 and Pagent-2 is set up so that the traffic rate varies constantly and will be different between Pagent-1 and Pagent-2. When the traffic rate from Pagent-1 to Pagent-2 is high and increasing, the traffic rate from Pagent-2 to Pagent-1 will be low and decreasing, and vice versa. As a result, the drop rate on your workgroup router serial 0/0 interface may be different between your workgroup R1 and R2 routers.
Note For Callgen, both Callgen routers will generate VoIP calls at a constant rate.
Step 5 Compare the resulting statistics with and without the Pagent and Callgen traffic generations enabled.
You should notice that many of the pings would have a longer response time in the event of congestion on the low bandwidth 384-kbps PPP serial link.