Free Guides

Language Tutorials

Cisco Articles

Cabling Your Home Lab

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!

Cisco Switching Modes

Store-and-Forward is exactly what it sounds like. The entire frame will be stored before it is forwarded. This mode allows for the greatest amount of error checking, since a CRC (Cyclical Redundancy Check) is run against the frame before it is forwarded. If the frame contains an error, it is discarded. If there's no problem with the frame, the frame is then forwarded to its proper destination.

While store-and-forward does perform error checking, the delay in processing the frame while this error check is run results in higher latency than the other modes you're about to read about. The latency time can also vary, since not all frames are the same size.

Cut-through switching copies only the destination MAC address into its memory before beginning to forward the frame. Since the frame is being forwarded as soon as the destination MAC is read, there is less latency than store-and-forward. The drawback is that there is no error checking.

There is a middle ground, fragment-free switching. Only part of the frame is copied to memory before it is forwarded, but it's the first 64 bytes of the frame, not just the destination MAC. (Why? Because if there is a problem with the frame, it's most likely in the first 64 bytes.) There is a little more error checking than cut-through, but not as much latency as with store-and-forward.
Note that the latency of both cut-through and fragment-free is fixed; these modes always look at the first six or 64 bytes, respectively. Store-and-forward's latency depends on the size of the frame.
 

Configuring And Troubleshooting VTP

VTP allows switches to advertise VLAN information between other members of the same VTP domain. VTP allows a consistent view of the switched network across all switches. When a VLAN is created on one switch in a VTP server, all other VTP devices in the domain are notified of that VLAN�s existence. VTP servers will know about every VLAN, even VLANs that have no members on that switch.

Switches run VTP in one of three modes. In server mode, VLANs can be created, modified, and deleted on a VTP server. When these actions are taken, the changes are advertised to all switches in the VTP domain. VTP Servers keep VLAN configuration information upon reboot.

In client mode, the switch cannot modify, create, or delete VLANs. VTP clients cannot retain VLAN configuration information upon reboot; they have to obtain this information from a VTP server.

In real-world networks, this is generally done to centralize the creation and deletion of VLANs. An interesting side effect of the server/client methodology is that if a VLAN is only to have ports on the VTP client switch, the VLAN must still first be created on the VTP server. The VTP client will learn about the VLAN from the VTP server, and ports can then be placed into that VLAN.

The third VTP mode is transparent mode. VTP switches in this mode ignore VTP messages. They do forward the VTP advertisements received from other switches. VLANs can be created, deleted, and modified on a transparent server, but those changes are not advertised to the other switches in the VTP domain.

For switches running VTP to successfully exchange VLAN information, three things have to happen. I've listed them for you in the order that you'll see them in the real world.

The VTP domain name must match. This is case-sensitive. "CISCO" and "cisco" are two different domains.

To distribute information about a newly-created VLAN, the switch upon which that VLAN is created must be in Server mode.
 

Configuring CGMP On Routers & Switches

If a Layer Two switch doesn't have the capabilities to run IGMP Snooping, it will be able to run CGMP - Cisco Group Membership Protocol. CGMP allows the multicast router to work with the Layer Two switch to eliminate unnecessary multicast forwarding.

CGMP will be enabled on both the multicast router and the switch, but the router's going to do all the work. The router will be sending Join and Leave messages to the switch as needed. PIM must be running on the router interface facing the switch before enabling CGMP, as you can see:

R1(config)#int e0

R1(config-if)#ip cgmp

WARNING: CGMP requires PIM enabled on interface

R1(config-if)#ip pim sparse

R1(config-if)#ip cgmp
When CGMP is first enabled on both the multicast router and switch, the router will send a CGMP Join message, informing the switch that a multicast router is now connected to it. This particular CGMP Join will contain a Group Destination Address (GDA) of 0000.0000.0000 and the MAC address of the sending interface. The GDA is used to identify the multicast group, so when this is set to all zeroes, the switch knows this is an introductory CGMP Join, letting the switch know that the multicast router is online.

The switch makes an entry in its MAC table that this router can be found off the port that the CGMP Join came in on. The router will send a CGMP Join to the switch every minute to serve as a keepalive.

A workstation connected to the switch on port 0/5 now wishes to join multicast group 225.1.1.1. The Join message is sent to the multicast router, but first it will pass through the switch. The switch will do what you'd expect it to do - read the source MAC address and make an entry for it in the MAC address table as being off port fast 0/5 if there's not an entry already there. (Don't forget that the MAC address table is also referred to as the CAM table or the bridging table.)

The router will then receive the Join request, and send a CGMP Join back to the switch. This CGMP Join will contain both the multicast group's MAC address and the requesting host's MAC address. Now the switch knows about the multicast group 225.1.1.1 and that a member of that group is found off port fast 0/5. In the future, when the switch receives frames destined for that multicast group, the switch will not flood the frame as it would an unknown multicast. Instead, the switch will forward a copy of the frame to each port that it knows leads to a member of the multicast group.

Two major benefits of CGMP are the explicit Join and Leave Group messages. In the next part of this BCMSN exam tutorial, we will take a look at the Leave Group messages.