Lab Exercise: Navigating Your Hands-On Lab


In this lab, you will construct and become familiar with the VoIP lab topology to be used in subsequent labs. The lab topology contains a total of three Cisco routers. However, some of the labs can be adapted to only two routers.

Following is a list of required lab equipment:

  • Three Cisco routers running Cisco IOS Software Release 12.3(1) or later. (The IOS should support the H.323 Gateway and AutoQoS features.)

    - Router R1 should contain one serial interface and one FXS port.

    - Router R2 should contain two serial interfaces.

    - Router R3 should contain one serial interface and one FXS port.

Note

To identify an appropriate IOS image for your routers, visit Cisco's Feature Navigator, at www.cisco.com/go/fn, where you can specify the features you require for your specific router platform.


  • Two DTE-to-DCE serial cables (with the appropriate serial connectors for your routers).

  • Two analog telephones.

Figure 2-50 illustrates the lab's physical topology and IP addressing.

Figure 2-50. Lab Topology


Task 1: Physical Connectivity

In this task, you will interconnect the lab routers.

Complete these steps:

1.

Adapting the topology shown in Figure 2-50 to your own router interfaces, interconnect routers R1 and R2 using a DTE-to-DCE serial cable. The DTE end of the cable should be connected to router R1, and the DCE end of the cable should be connected to router R2.

2.

Interconnect routers R2 and R3 using a DTE-to-DCE serial cable. The DTE end of the cable should be connected to router R2, and the DCE end of the cable should be connected to router R3.

3.

Connect an analog telephone to the FXS port in router R1.

4.

Connect an analog telephone to the FXS port in router R3.

Task 2: Initial Configuration

In this task, you will configure the routers in the lab topology for Layer 3 connectivity.

Complete these steps:

1.

Adapting the topology shown in Figure 2-50 to your own router interface, assign an IP address to the serial interface on router R1 and configure the interface for PPP encapsulation. Set the bandwidth of the interface connecting to R2 to 128 kbps, using the bandwidth 128 command. Administratively bring up the interface.

2.

Assign IP addresses to the two serial interfaces on router R2 and configure the interfaces for PPP encapsulation. Set the bandwidth of the interface connecting to router R1 to 128 kbps, using the bandwidth 128 command. Set the clock rate on the interface connecting to router R1 to 128 kbps with the clock rate 128000 command. Set the bandwidth of the interface connecting to router R3 to 2 Mbps, using the bandwidth 2000 command. Administratively bring up the interfaces.

3.

Assign an IP address to the serial interface router R3, and configure the interface for PPP encapsulation. Set the clock rate on the serial interface to 2 Mbps with the clock rate 2000000 command and indicate the interface bandwidth as 2 Mbps with the bandwidth 2000 command. Administratively bring up the interface.

4.

Configure a routing protocol of your choice on the routers such that all routers can see the networks associated with each of the serial interfaces in the topology.

Task 3: Exercise Verification

In this task, you will verify Layer 3 connectivity across your pod of routers.

Complete these steps:

1.

Issue the show ip route command on R1, R2, and R3 to verify that the following networks are visible to each router:

  • 10.1.1.0/24

  • 10.7.7.0/24

2.

From a console connection to the R1 router, ping the 10.7.7.2 interface (that is, R3's serial interface) to verify Layer 3 connectivity across the pod.

Suggested Solution

Although your physical hardware and selection of a routing protocol might differ, the following examples offer one solution. Example 2-1 shows a possible configuration for router R1.

Example 2-1. Router R1's Configuration

 interface Serial0  bandwidth 128 ip address 10.1.1.2 255.255.255.0  encapsulation ppp ! router eigrp 100  network 10.0.0.0 

Example 2-2 shows a possible configuration for router R2.

Example 2-2. Router R2's Configuration

 interface Serial0/0 bandwidth 128  ip address 10.1.1.1 255.255.255.0  encapsulation ppp  clockrate 128000 ! interface Serial0/1  bandwidth 2000  ip address 10.7.7.1 255.255.255.0  encapsulation ppp ! router eigrp 100 network 10.0.0.0 

Example 2-3 shows a possible configuration for R3.

Example 2-3. Router R3's Configuration

 interface Serial0  bandwidth 2000 ip address 10.7.7.2 255.255.255.0  encapsulation ppp  clock rate 2000000 ! router eigrp 100  network 10.0.0.0 

The results of the show ip route command, issued on all routers, should be similar to the output shown in the following examples.

Example 2-4 shows the show ip route command output for router R1

Example 2-4. Router R1's show ip route Output

 R1#show ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP        D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area        N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2        E1 - OSPF external type 1, E2 - OSPF external type 2        i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2        ia - IS-IS inter area, * - candidate default, U - per-user static route        o - ODR, P - periodic downloaded static route Gateway of last resort is not set      10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks D       10.7.7.2/32 [90/21024000] via 10.1.1.1, 00:14:05, Serial0 D       10.7.7.0/24 [90/21024000] via 10.1.1.1, 00:14:05, Serial0 C       10.1.1.0/24 is directly connected, Serial0 C       10.1.1.1/32 is directly connected, Serial0 C    192.168.0.0/24 is directly connected, Ethernet0 

Example 2-5 shows the show ip route command output for router R2.

Example 2-5. Router R2's show ip route Output

 R2#show ip route Codes:  C - connected, S - static, R - RIP, M - mobile, B - BGP         D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area         N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2         E1 - OSPF external type 1, E2 - OSPF external type 2         i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2         ia - IS-IS inter area, * - candidate default, U - per-user static route         o - ODR, P - periodic downloaded static route  Gateway of last resort is not set       10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks C        10.7.7.2/32 is directly connected, Serial0/1 C        10.1.1.2/32 is directly connected, Serial0/0 C        10.7.7.0/24 is directly connected, Serial0/1 C        10.1.1.0/24 is directly connected, Serial0/0 

Example 2-6 shows the show ip route command output for router R3.

Example 2-6. Router R3's show ip route Output

 R3#show ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP        D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area        N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2        E1 - OSPF external type 1, E2 - OSPF external type 2        i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2        ia - IS-IS inter area, * - candidate default, U - per-user static route        o - ODR, P - periodic downloaded static route  Gateway of last resort is not set       10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks D        10.1.1.2/32 [90/21024000] via 10.7.7.1, 00:15:22, Serial0 C        10.7.7.0/24 is directly connected, Serial0 D        10.1.1.0/24 [90/21024000] via 10.7.7.1, 00:15:22, Serial0 C        10.7.7.1/32 is directly connected, Serial0 

The result of the ping 10.7.7.2 command, issued on router R1, should be similar to the output shown in Example 2-7.

Example 2-7. Router R1's ping 10.7.7.2 Output

 R1#ping 10.7.7.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.7.7.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 16/19/24 ms 




Cisco Voice over IP Cvoice (c) Authorized Self-study Guide
Cisco Voice over IP (CVoice) (Authorized Self-Study Guide) (2nd Edition)
ISBN: 1587052628
EAN: 2147483647
Year: 2006
Pages: 111
Authors: Kevin Wallace

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net