• Tidak ada hasil yang ditemukan

1 - 4 Semester 6: Remote Access v2.0 - Lab 8.3.1 Copyright  2001, Cisco Systems, Inc.

Lab 8.3.1: Frame Relay Subinterfaces and Traffic Shaping

S0/0.18 192.168.192.1/24 S0/0.17 192.168.193.1/24

Adtran Atlas

2 - 4 Semester 6: Remote Access v2.0 - Lab 8.3.1 Copyright  2001, Cisco Systems, Inc.

Frame Relay switch. If you are using the Atlas 550, be sure to connect the routers’ serial interfaces to the correct port on the Atlas (labeled in the diagram) using a V.35 cable.

Step 2

Configure the router basic information such as router name and passwords as well as the LAN interfaces. In this lab, use Cisco Frame Relay encapsulation. You may explicitly configure the LMI-type as ANSI, or you can allow the router to autosense the LMI type.

Use the basic frame relay information below to configure the routers.

Note: Each PVC exists as a point-to-point network on its own logical IP subnet. A partial configuration for SanJose1 is shown here:

On SanJose1:

SanJose1(config)#interface serial 0/0.17 point-to-point SanJose1(config-subif)#ip address 192.168.193.1 255.255.255.0 SanJose1(config-subif)#frame-relay interface-dlci 17

SanJose1(config-fr-dlci)#exit

SanJose1(config-subif)#interface serial 0/0.18 point-to-point SanJose1(config-subif)#ip address 192.168.192.1 255.255.255.0 SanJose1(config-subif)#frame-relay interface-dlci 18

On London:

London(config)#interface serial 0/0.16 point-to-point London(config-subif)#ip address 192.168.192.2 255.255.255.0 London(config-subif)#frame-relay interface-dlci 16

London(config-fr-dlci)#exit

On Singapore:

Singapore(config)#interface serial 0/0.16 point-to-point Singapore(config-subif)#ip address 192.168.193.2 255.255.255.0 Singapore(config-subif)#frame-relay interface-dlci 16

Singapore(config-fr-dlci)#exit

Step 3

Test connectivity with extended pings between LANs at different regional sites. From SanJose1, use extended ping to test connectivity with London. Send several large packets (over 1000-byte datagram size) to measure throughput, and note the round-trip times in milliseconds.

SanJose1#ping Protocol [ip]:

Target IP address: 192.168.200.1 Repeat count [5]: 55

Datagram size [100]: 1111 Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: 192.168.0.1 Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 55, 1111-byte ICMP Echoes to 192.168.200.1, timeout is 2 seconds:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

3 - 4 Semester 6: Remote Access v2.0 - Lab 8.3.1 Copyright  2001, Cisco Systems, Inc.

Success rate is 100 percent (55/55), round-trip min/avg/max = 176/179/192 ms

Issue extended pings, using the same parameters, to record round-trip times between regional LANs: From SanJose1 to Singapore and from Singapore to London.

Round-trip times will vary, primarily due to the WAN interface card in your router. The router probably contains either a WIC-2A/S supporting up to 128 kbps or a WIC-2T

supporting up to 2.048 mbps. For the purposes of this lab, either WIC is fine. The round-trip times will become relevant when compared to the results of later tests.

Step 4

On Singapore and SanJose1, create a map-class in global configuration mode defining the CIR. A logical name must be assigned to uniquely identify each map-class. Use CIR as the name.

Singapore(config)#map-class frame-relay CIR

Singapore(config-map-class)#frame-relay traffic-rate 19200

SanJose1(config)#map-class frame-relay CIR

SanJose1(config-map-class)#frame-relay traffic-rate 19200

A Frame Relay map-class can be used by any Frame Relay interface. In this case, you will apply the map-class to Singapore’s subinterface, as shown below. Since the map- class specifies rate enforcement, you must enable Frame Relay traffic-shaping on the major interface.

Singapore(config)#interface serial 0/0

Singapore(config-if)#frame-relay traffic-shaping

Singapore(config-if)#interface serial 0/0.16 point-to-point Singapore(config-subif)#frame-relay class CIR

Configure the other end of this PVC, on SanJose1, using the same commands:

SanJose1(config)#interface serial 0/0

SanJose1(config-if)#frame-relay traffic-shaping

SanJose1(config-if)#interface serial 0/0.17 point-to-point SanJose1(config-subif)#frame-relay class CIR

Step 5

Test connectivity and throughput with extended pings as before, recording round-trip times. The average and round-trip times should have increased as traffic was buffered due to slow WAN links. Here are some sample results:

SanJose1#ping

<output omitted>

Sending 55, 1111-byte ICMP Echoes to 192.168.232.1, timeout is 2 seconds:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Success rate is 100 percent (55/55), round-trip min/avg/max = 184/460/520 ms

London#ping

<output omitted>

Sending 55, 1111-byte ICMP Echoes to 192.168.232.1, timeout is 2 seconds:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Success rate is 100 percent (55/55), round-trip min/avg/max = 356/464/540 ms

4 - 4 Semester 6: Remote Access v2.0 - Lab 8.3.1 Copyright  2001, Cisco Systems, Inc.

1. How are these ping results different from the first set of pings run in Step 3?

Step 6

To observe detailed traffic shaping statistics, issue show frame-relay pvc 17 on SanJose1. Although traffic-shaping is enabled, it is only active if traffic is buffered. For this reason, you might see “shaping inactive” in the output of this command, as shown here:

SanJose1#show frame-relay pvc 17

PVC Statistics for interface Serial0/0 (Frame Relay DTE)

DLCI = 17, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.18

input pkts 82 output pkts 80 in bytes 14127 out bytes 13930 dropped pkts 1 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts

0

in DE pkts 0 out DE pkts 0

out bcast pkts 66 out bcast bytes 12983

pvc create time 00:39:54, last time pvc status changed 00:03:00 cir 19200 bc 19200 be 0 limit 300 interval

125

mincir 9600 byte increment 300 BECN response no pkts 17 bytes 2828 pkts delayed 0 bytes

delayed 0 shaping inactive

traffic shaping drops 0

Serial0/0.18 dlci 18 is first come first serve default queuing Output queue 0/40, 0 drop, 0 dequeued

1. According to the output of this command, what is the CIR of this PVC?

1 - 6 Semester 6: Remote Access v2.0 - Lab 8.3.2 Copyright  2001, Cisco Systems, Inc.

Lab 8.3.2: On-Demand Routing

1/1

1/2