Simulating Wide Area Network Connections

The other major part of modeling the internetwork consists of WAN connections. At this point in the design, you are concerned only with ISO Layer 1. You will continue to model the internetwork from Layer 1 on up because this is the most logical way to build any network. First, you will build all the physical connections to all your devices, and then you will configure all LAN interfaces, WAN interfaces, and finally your different networks together with routing protocols. Constructing a network in a layered approach allows for future growth and adaptation by upgrading or replacing a single layer at a time, while leaving the remaining layers unchanged. With this in mind, we will focus on physical aspects, such as cable types and pinouts. Part III, "Connecting LANs with Wide Area Networks (WANs)," focuses on ISO Layer 2 protocols.

You can model WAN connections in three primary ways, and you can simulate a WAN in one way in a Cisco environment:

• You can model WANs by using a special crossover cable for routers with WAN Interface Cards (WICs) or external CSU/DSUs.

• You can model WANs by using V.35 DTE cable to a V.35 DCE cable, or any serial cable in a DTE-to-DCE configuration.

• You can simulate WANs by using loopback plugs on CSU/DSUs.

• You can model WANs by using a Cisco router as a Frame Relay or X.25 switch.


Of course, no book on networking would be complete without mentioning the OSI model; Appendix B, "The 'Abridged' OSI Reference Model," presents a brief overview of the OSI model.

Modeling WANs by Using Special Crossover Cable Routers with Built-In or External CSU/DSUs

Two routers with built-in or external CSU/DSUs can be connected in a "back-to-back" mode. This functions as the Layer 1 for many WAN protocols, including PPP, HDLC, and others. This is done by utilizing a special crossover cable made from pinning out specific pins of a four-pair Category 5 cable. It is important to note that the crossover cable needed differs slightly from a T1 to a 56-kbps DSU. You must connect a router with a T1 service unit or CSU/DSU to another router with a T1 service unit or CSU/DSU. The same is true for a 56-kbps service unit. Figures 1-3 and 1-4 illustrate what pinouts you need to make a crossover cable, from a Category 5 cable for a T1 CSU/DSU and a 56-kbps CSU/DSU.

Figure 1-3. Pinouts for a Crossover Cable for T1 Service Module or


Figure 1-4. Pinouts for a Crossover Cable for 56-kbps Service Module or CSU/DSU

Figure 1-4. Pinouts for a Crossover Cable for 56-kbps Service Module or CSU/DSU

Modeling WANs by Using a V.35 DTE Cable to a V.35 DCE Cable

The most common way to provide Layer 1 connectivity between routers is to connect a female V.35 DCE cable to a male V.35 DTE cable. The key factor in any back-to-back configuration is ensuring that one side of the link sets clocking. This is always the DCE side of the link. To configure the clock rate for an interface, simply add the command clock rate [value]. Example 1-3 demonstrates how to set the clocking on a serial interface to 64,000 bps.

Example 1-3 Configuring the Clockrate on a DCE Interface frame_relay_switch(config)#int serial 5 frame_relay_switch(config-if)#clockrate 64000 frame_relay_switch(config-if)#AZ frame_relay_switch#

It is important to ensure that the cable is truly a V.35 DTE cable connecting to a V.35 DCE cable. The sex of the DCE or DTE cable is not relevant; however, you must connect a DCE side to a DTE side, and set the clock rate, as demonstrated in Example 1-3. Figure 1-5 illustrates many of the standard Cisco cable connectors, ranging from the common V.35 and

RS-232 interfaces to EIA613-HSSI interfaces.

Figure 1-5. Common Cable Interfaces for Cisco Routers

Figure 1-5. Common Cable Interfaces for Cisco Routers

Interfaces V35 232 X21 Hssi

These cables can be ordered from Cisco Systems, part number CAB-V35MT for the V.35 male DTE cable, and CAB-V35FC for the female DCE cable. Several companies also make serial and crossover cables at reasonable prices.

At times when the cables are connected in a back-to-back mode, it might be hard to tell which one is the DCE cable. You might be in the field or working remotely, and you might not have physical access to your lab—how, then, can you tell which cable is the DCE cable? The show controller command shows the cable type and shows whether the cable is DCE or DTE. Example 1-4 shows two interfaces on a Cisco 2501 router. Using the show controller command, you can tell what the interface type is.

Example 1-4 Example of the show controllers Command

Router#show controller serial 0

HD unit 0, idb = 0xCED94, driver structure at 0xD3B18 buffer size 1524 HD unit 0, V.35 DTE cable cpb = 0xE2, eda = 0x4140, cda = 0x4000 RX ring with 16 entries at 0xE24000

00 bd_ptr=0x4000 pak=0x0D66F0 ds=0xE2DDB0 status=80 pak_size=0 ***text omitted***

Router#show controller serial 1

HD unit 1, idb = 0xD7788, driver structure at 0xDC508 buffer size 1524 HD unit 1, RS-232 DCE cable cpb = 0xE3, eda = 0x2140, cda = 0x2000 RX ring with 16 entries at 0xE32000

00 bd_ptr=0x2000 pak=0x0DF0E4 ds=0xE3C468 status=00 pak_size=0 ***text omitted***

Interface Serial 0 is a V.35 DTE cable, and interface Serial 1 is an RS-232 DCE cable. Other

serial cables, such as RS-232, are used for back-to-back connections, as long as a DCE cable is connected to DTE cable. It is important to note that each different cable type has certain speed restrictions. For example, it is not possible to simulate T1 speeds on RS-232 cables. For the most flexibility in lab environments, use V.35 cables whenever possible.

Sometimes, you might want to switch your lab environment rather rapidly. You might want a serial connection attached to one router one day, whereas the next day you might want that same connection to go to another router. In these situations, it is best to use a patch panel of some sort. A V.35 patch panel is a common sight at large labs. The V.35 patch panel is simple to work with. Most V.35 patch panels have a female DTE port located on top, in the rear, and a V.35 male DCE port located in the middle, in the rear. The routers plug into these ports, the DTE cable to the DTE port, and the DCE cable to the DCE port. On the front of the patch panel are small patch ports, with one port in front of each DTE and DCE port. A black patch cable then enables you to patch one DTE port to one DCE port, thereby connecting one router to another router.

To change the configuration, simply move the patch cable to another patch port. Using a patch panel in this manner allows for quick and rapid physical configuration of many serial links. Patch panels should be labeled on the front to designate which is the DCE and DTE port —this can be key when troubleshooting physical layer issues. Figure 1-6 illustrates a V.35 Patch panel.

Figure 1-6. V.35 Patch Panels

- Monitor port

Proprietary patch cable i>-<11

Most patch panels also have a bottom port, right below the DCE port. This port is used for attaching a line monitor or data scope.

Simulating WANs by Using HDLC and Loopback Plugs on CSU/DSUs

Yet another way to use WAN interfaces in your model is to deploy loopback plugs on your CSU/DSUs combined with running HDLC protocol. In addition, by putting a Layer 3 address, such as an IP or IPX address, on the interface, the interface will respond to pings and will show up in routing tables. The Layer 2 encapsulation must also be set to HDLC when using loopback plugs. Routers with built-in CSU/DSUs or WAN interface cards (WICs), and even on routers with external CSU/DSUs, can have a loopback plug installed into the RJ-45 jack, thus spoofing the WAN interface as up. Example 1-5 illustrates output from the show interface command on a Cisco 2524, with a T1 WIC and a loopback plug installed.

Figure 1-6. V.35 Patch Panels

Example 1-5 The show interface Command of a Cisco 2524 with a T1 Loopback Plug Installed in Its WIC

router# show interfaces serial 1

Serial1 is up, line protocol is up (looped) Hardware is HD64570 with FT1 CSU/DSU

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation HDLC, loopback not set, keepalive set (10 sec)

Last input 00:00:02, output 00:00:02, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0 (size/max/drops); Total output drops: 0

Queueing strategy: weighted fair

Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 2537 packets input, 148733 bytes, 0 no buffer Received 2537 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 2537 packets output, 148733 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets

0 output buffer failures, 0 output buffers swapped out

1 carrier transitions

DCD=up DSR=up DTR=up RTS=up CTS=up router#


Loopback plugs can be useful in the field. Whenever a CSU/DSU or WIC is suspected to be malfunctioning, installing a loopback plug can quickly test the physical layer to the CSU/DSU. When the loopback plug is installed, the show interface command should show the interface as line up, protocol up and (looped).

A loopback plug can be easy to make. You can use a simple cable kit to construct these plugs, or you can order them from most cable vendors, if they are supplied with the diagrams in Figures 1-7 and 1-8. Figure 1-7 demonstrates the pinouts required for an RJ-45 56-kbps loopback plug, while Figure 1-8 illustrates the pinouts required for an RJ-45 T1 or 1.544-Mbps loopback plug.

Figure 1-7. Pinouts for an RJ-45 56-kbps Loopback Plug

Figure 1-7. Pinouts for an RJ-45 56-kbps Loopback Plug

0 0

Post a comment