Part of your CCNA / CCNP education is deciding what network topology to use when you’re putting together your home lab. Some of you are starting with one or two routers or switches, while others are starting with more. A customer recently sent me a list of his Cisco routers and switches that he has available for a home lab and asked for my help in coming up with the best way to use them.

There is no “right” or “wrong” answer to this question; again, part of the learning process is configuring and reconfiguring the physical topology of your lab. Let’s look at the routers and switches he has available, including the interfaces on each, and come up with one possible CCNA / CCNP home lab setup.

The equipment list:

Two 3620 routers. Each has 1 serial port and 2 ethernet ports.

One 3640 router. This has two ethernet cards, each with two ports, and two AUI ports.

Three 2503s, my personal favorite for home labs! These have 1 AUI port, 2 serial interfaces, and one BRI interface apiece.

One 2524 router. This has one serial port, 1 ethernet port, and one BRI interface.

One 4500 router. This has eight BRI ports, 2 ethernet ports, and more importantly, four serial ports.

He also has a 5200 access server, an ISDN simulator, one 2924 switch, and one 1924 switch.

Now, if you don’t have this much equipment to work with, don’t panic! Most CCNA / CCNP candidates don’t; this is more of an exercise in looking at what you do have and using it to the utmost.

As I’ve mentioned in many of my CCNA / CCNP home lab articles, an access server is a great thing to have. All he needs is an octal cable to connect his AS to the other devices we choose to use, and he’s all set. (If you need an access server sample configuration, there is one on my website in the Home Lab section.)
Read the full story

I know from experience that part of the excitement and anxiety of putting together your own CCNA / CCNP home lab is deciding what to buy! While you can make a workable home lab out of almost any combination of Cisco routers and switches, some routers are better suited for home lab work than others because they can fill multiple roles.

My personal favorite is the Cisco 2520. This router has four serial interfaces, making it an ideal frame relay switch. Don’t forget that just because you’re using a router as a frame switch, you can still use its routing capabilities. One setup I use is to use three of the four serial interfaces for frame switching and the fourth interface as a point-to-point network with another router. All you need is some DTE/DCE cables and you’re all set.
Read the full story

I know from experience that part of the excitement and anxiety of putting together your own CCNA / CCNP home lab is deciding what to buy! While you can make a workable home lab out of almost any combination of Cisco routers and switches, some routers are better suited for home lab work than others because they can fill multiple roles.

When you buy CCNA or CCNP “lab kits” – bundles of routers and switches – you can get a little confused about whether you’re getting a good deal. One router I get asked about quite a bit is the 2503.

2503 routers are fantastic for CCNA and CCNP home labs. They come with two serial interfaces, allowing you to connect one interface directly to another router (you’ll need a DTE/DCE cable for that, too) while connecting another to a frame relay switch if you like. If you don’t have a frame relay switch, you can connect a 2503 directly to two other routers via the serial interfaces.
Read the full story

A prime topic of your CCNA and CCNP CIT exams will be connecting Cisco routers directly via their Serial interfaces, and while the configuration is straightforward, there are some vital details and show commands you must know in order to pass the exams and configure this successfully in production and home lab networks. Let’s take a look at a sample configuration.

Connecting Cisco routers directly via their Serial interfaces works really well once you get it running – and getting such a connection up and running is easy enough. You can use show controller serial x to find out which endpoint is acting as the DCE, and it’s the DCE that must be configured with the clockrate command.

R3#show controller serial 1

HD unit 1, idb = 0×11B4DC, driver structure at 0×121868

buffer size 1524 HD unit 1, V.35 DCE cable

R3(config)#int serial1

R3(config-if)#ip address 172.12.13.3 255.255.255.0

R3(config-if)#clockrate 56000

R3(config-if)#no shut

Failure to configure the clockrate has some interesting effects regarding the physical and logical state of the interfaces. Let’s remove the clockrate from R3 and see what happens.

R3(config)#int s1

R3(config-if)#no clockrate 56000

R3(config-if)#

18:02:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down

The line protocol doesn’t drop immediately, but it does drop. Let’s run show interface serial1 to compare the physical and logical interface states.

R3#show int serial1

Serial1 is up, line protocol is down

Physically, the interface is fine, so the physical interface is up. It’s only the logical part of the interface – the line protocol – that is down. It’s the same situation on R1.

R1#show inter serial1

Serial1 is up, line protocol is down

While a router misconfiguration is the most likely cause of a serial connection issue, that’s not the only reason for clocking issues. Cisco’s website documentation mentions CSU/DSU misconfiguration, out-of-spec cables, bad patch panel connections, and connecting too many cables together as other reasons for clocking problems. Still, the number one reason for clocking problems in my experience is simply forgetting to configure the clockrate command!

When you’re studying to pass the Cisco CCNA and CCNP certification exams, you quickly learn that there’s always something else to learn. (You’ll really pick up on this in your CCIE studies, trust me!) Today we’ll take a look at an often-overlooked topic in Frame Relay, the encapsulation type. You don’t exactly change this on a daily basis in production networks (not if you want to stay employed, anyway!), but it’s an important exam topic that you must be familiar with.

The DCE and DTE must agree on the LMI type, but there’s another value that must be agreed upon by the two DTEs serving as the endpoints of the VC. The Frame encapsulation can be left at the default of Cisco (which is Cisco-proprietary), or it can be changed to the industry-standard IETF, as shown below. If a non-Cisco router is the remote endpoint, IETF encapsulation must be used. Note that the default of Cisco isn’t listed as an option by IOS Help, so you better know that one by heart!

R1(config)#int s0

R1(config-if)#encap frame ?

ietf Use RFC1490/RFC2427 encapsulation

R1(config-if)#encap frame ietf

What if a physical interface is in use and some remote hosts require Cisco encapsulation and others require IETF? The encapsulation type can be configured on a per-PVC basis as well. One encap type can be used on the interface, and any map statements that require a different encap type can have that specified in the appropriate map statement. In the following example, all PVCs will use the default Cisco encapsulation type except for PVC 115. The frame map statement using that PVC has ietf specified.

R1(config)#int s0/0

R1(config-if)#encap frame

R1(config-if)#frame map ip 172.12.123.3 123 broadcast

R1(config-if)#frame map ip 172.12.123.2 122 ietf broadcast

show frame map shows us that the mapping to DLCI 123 is using Cisco encapsulation, and DLCI 122 is using IETF.

R1#show frame map

Serial0 (up): ip 172.12.123.3 dlci 123(0×7B,0×1CB0), static

broadcast, CISCO, status defined, active

Serial0 (up): ip 172.12.123.2 dlci 122(0×7B,0×1CB0), static

broadcast, ietf, status defined, active

Just remember that Cisco is the default, and all PVCs will use Cisco unless you specify IETF in the frame map statement itself. You could also change the entire interface to use IETF for all mappings with the frame-relay encapsulation IETF command. For Cisco exams, as well as work on production networks, it’s always a good idea to know more than one way to do something!

More CCNA and CCNP candidates than ever before are putting together their own home labs, and there’s no better way to learn about Cisco technologies than working with the real thing. Getting the routers and switches is just part of putting together a great CCNA / CCNP home lab, though. You’ve got to get the right cables to connect the devices, and this is an important part of your education as well. After all, without the right cables, client networks are going to have a hard time working!

For your Cisco home lab, one important cable is the DTE/DCE cable. These cables have two major uses in a home lab. To practice directly connecting Cisco routers via Serial interfaces (an important CCNA skill), you’ll need to connect them with a DTE/DCE cable. Second, if you plan on having a Cisco router act as a frame relay switch in your lab, you’ll need multiple DTE/DCE cables to do so. (Visit my website’s Home Lab Help section for a sample Frame Relay switch configuration.)

If you have multiple switches in your lab, that’s great, because you’ll be able to get a lot of spanning tree protocol (STP) work in as well as creating Etherchannels. To connect your switches, you’ll need crossover cables.

You’ll need some straight-through cables as well to connect your routers to the switches.

Finally, if you’re lucky enough to have an access server as part of your lab, you’ll need an octal cable to connect your AS to the other routers and switches in your lab. The octal cable has one large connector on one end and eight numbered RJ-45 connectors on the other end. The large connector should be attached to the async port on your AS, and the numbered RJ-45 connectors will be connected to the console ports on your other routers and switches.

Choosing and connecting the right cables for your Cisco CCNA / CCNP home lab is a great learning experience, and it’s also an important part of your Cisco education. After all, all great networks and home labs all begin at Layer One of the OSI model!