Cisco CCNA Exam Tutorial And Case Study: VLANs and IP Connectivity
4784
Computers > Computer Certification
Mar 1, 2007
Chris Bryant
Cisco CCNA Exam Tutorial And Case Study: VLANs and IP Connectivity
In this CCNA case study, we'll take some basic switching and trunking theory and put it into action. We have two routers (R2 and R3) along with two switches (SW1 and SW2). R2 is connected to SW1 at fast 0/2, and R3 is connected to SW2 at fast 0/3. Both routers have IP addresses on the 172.12.23.0 /24 network.
For these routers to be able to ping each other, the switches must be able to communicate. These are two 2950 switches, and they're connected via two crossover cables. Before we worry about the router connectivity, let's make sure the trunk link is up between the switches with the "show interface trunk" command.
SW2#show interface trunk
Port Mode Encapsulation Status Native vlan
Fa0/11 desirable 802.1q trunking 1
Fa0/12 desirable 802.1q trunking 1
< output truncated for clarity >
The default mode of these switches is for the ports to run in dynamic desirable trunking mode, so we didn't even need to write a configuration to have the trunk form - it's already there!
R2 and R3?s Ethernet addresses have already been configured, the trunk line is operational, and both ports are in VLAN 1. We'll ping R2?s Ethernet interface from R3, and then R3?s Ethernet interface from R2 to verify IP connectivity.
R2#ping 172.23.23.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
R3#ping 172.23.23.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
With pings, exclamation points indicate IP connectivity, and periods indicate no connectivity.
So we've got connectivity! Now let's see if we still have that connectivity when the ports are placed into different VLANs. Cisco CCNA theory states that devices in different VLANs can't communicate without the intervention of a Layer 3 device, but let's see if that's true by placing R2 into VLAN 23. (VTP is already running on these switches.)
SW1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config)#int fast 0/2
SW1(config-if)#switchport mode access
SW1(config-if)#switchport access vlan 23
SW1(config-if)#^Z
Now that R2 and R3 are in separate VLANs, can they still send pings back and forth?
R2#ping 172.23.23.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R3#ping 172.23.23.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds:
.....
No, they can?t. The difference is that they?re now in separate VLANs, and devices in different VLANs can?t communicate unless routing is taking place somewhere. Here, no routing is taking place, so the pings don?t go through.
Put R3?s switch port into VLAN 23, and try the ping again.
SW2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
SW2(config)#interface fast0/3
SW2(config-if)#switchport mode access
SW2(config-if)#switchport access vlan 23
R3#ping 172.23.23.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
R2#ping 172.23.23.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds:
!!!!!
Now that R2 and R3 are in the same VLAN, pings can go through. This just proves the theory - that inter-VLAN communicate requires a Layer 3 device. Layer 3 switches are becoming more and more popular, but router-on-a-stick is still around - and we'll see how to configure that in our next tutorial!
For these routers to be able to ping each other, the switches must be able to communicate. These are two 2950 switches, and they're connected via two crossover cables. Before we worry about the router connectivity, let's make sure the trunk link is up between the switches with the "show interface trunk" command.
SW2#show interface trunk
Port Mode Encapsulation Status Native vlan
Fa0/11 desirable 802.1q trunking 1
Fa0/12 desirable 802.1q trunking 1
< output truncated for clarity >
The default mode of these switches is for the ports to run in dynamic desirable trunking mode, so we didn't even need to write a configuration to have the trunk form - it's already there!
R2 and R3?s Ethernet addresses have already been configured, the trunk line is operational, and both ports are in VLAN 1. We'll ping R2?s Ethernet interface from R3, and then R3?s Ethernet interface from R2 to verify IP connectivity.
R2#ping 172.23.23.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
R3#ping 172.23.23.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
With pings, exclamation points indicate IP connectivity, and periods indicate no connectivity.
So we've got connectivity! Now let's see if we still have that connectivity when the ports are placed into different VLANs. Cisco CCNA theory states that devices in different VLANs can't communicate without the intervention of a Layer 3 device, but let's see if that's true by placing R2 into VLAN 23. (VTP is already running on these switches.)
SW1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config)#int fast 0/2
SW1(config-if)#switchport mode access
SW1(config-if)#switchport access vlan 23
SW1(config-if)#^Z
Now that R2 and R3 are in separate VLANs, can they still send pings back and forth?
R2#ping 172.23.23.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R3#ping 172.23.23.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds:
.....
No, they can?t. The difference is that they?re now in separate VLANs, and devices in different VLANs can?t communicate unless routing is taking place somewhere. Here, no routing is taking place, so the pings don?t go through.
Put R3?s switch port into VLAN 23, and try the ping again.
SW2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
SW2(config)#interface fast0/3
SW2(config-if)#switchport mode access
SW2(config-if)#switchport access vlan 23
R3#ping 172.23.23.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
R2#ping 172.23.23.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds:
!!!!!
Now that R2 and R3 are in the same VLAN, pings can go through. This just proves the theory - that inter-VLAN communicate requires a Layer 3 device. Layer 3 switches are becoming more and more popular, but router-on-a-stick is still around - and we'll see how to configure that in our next tutorial!
Article Source: http://www.articlerich.com
Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage , home of free CCNA and CCNP tutorials! Pass the CCNA exam with Chris Bryant!
Write a Review
Add to My Favorite
Refer it to Friend
Report Article
Other links owned by this user
EIGRP is a major subject of the CCNA exam, and Cisco goes into even more detail with EIGRP on your CCNP exams. Part of that detail is the purpose and configuration of EIGRP stub routers. A problem with EIGRP comes in when a successor is
Category:
QoS is a big topic on your BCMSN and CCNP exams, and for good reason. As more and more traffic flows through today's networks, accurately plying QoS to both your routers and switches becomes more important. Note the phrase "accurately
Category:
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
Category:
The most common method of configuring ISDN is with dialer maps, but dial information can also be configured on a logical interface. To pass the CCNA exam, you must know how to configure and troubleshoot both dialer maps and dialer
Category:
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.
Category:
CCNA exam success deends artially on knowing the details of ISDN, and there are lenty of them! To hel you review for your CCNA exam, here are a few ISDN details that you must know on exam day. (They hel in the real world, too ? and there are still
Category:
Passing the CCNA is tough, and one of the toughest parts is keeping all the acronyms straight! Frame Relay has plenty of those, and today we're going to examine what DLCIs do and how they're mapped on a Cisco router. Frame Relay VCs use
Category:
To be truly prepared for your CCNA and CCNP exams, you need real hands-on experience with real Cisco routers and switches. However, a production network is a really bad place to practice your configurations, but an excellent way to get fired and/or
Category:
While routers accept and generate broadcasts, they do not forward them. This can be quite a problem when a broadcast needs to get to a device such as a DHCP or TFTP server that's on one side of a router with other subnets on the other side.
Category:
QoS - Quality o Service - is a huge topic on both the BCMSN exam and real-world networks. QoS is so big today that Cisco's created separate specialist certiications that cover nothing but QoS! It can be an overwhelming topic at irst, but master the
Category:
To pass the BSCI exam, you need to know the difference between IRDP and HSRP. While they have the same basic function, the operation and configuration of each are totally different. The aim of both is to allow hosts to quickly discover a
Category:
OSPF route ibution is an important topic on the BSCI exam, and it's a topic full of details and defaults that you need to know for the exam room and the job. To help you pass the BSCI exam, here's a quick review of some of the OSPF route
Category:
Ever since you picked up your first CCNA book, you've heard about multicasting, ten a fair idea of what it is, and you've memorized a couple of reserved multicasting addresses. Now as you prepare to pass the BCMSN exam and become a CCNP, you've
Category:
In this CCNA case study, we'll take some basic switching and trunking theory and put it into action. We have two routers (R2 and R3) along with two switches (SW1 and SW2). R2 is connected to SW1 at fast 0/2, and R3 is connected to SW2 at fast 0/3. Both
Category:
RIP isn't exactly the most complex routing protocol on the CCNA exam, but that makes it easy to overlook some of the important you must keep in mind in order to pass the exam! To help you review for the exam, here are just a few of those
Category:
To pass e CCNA exam, you've got to know how to work wi IGRP and EIGRP unequal-cost load balancing. You may not see much IGRP in production networks anymore, but you'll see a lot of EIGRP, and part of fine-tuning your EIGRP network is making sure
Category:
Your BSCI exam and CCNP certification success depend on mastering BGP, and a ig part of that is knowing how and when to use the many BGP attriutes. And for those of you with an eye on the CCIE, elieve me - you've got to know BGP attriutes like the
Category:
Multicasting is a vital topic on your BCMSN, CCNP, and CCIE exams, and it can also be very confusing when you first start studying it. Multicasting uses concepts that are unlike anything you've run into in your routing protocol studies, and that can
Category:
Other links at Computers > Computer Certification
To be truly prepared for your CCNA and CCNP exams, you need real hands-on experience with real Cisco routers and switches. However, a production network is a really bad place to practice your configurations, but an excellent way to get fired and/or
Category:
In this CCNA case study, we'll take some basic switching and trunking theory and put it into action. We have two routers (R2 and R3) along with two switches (SW1 and SW2). R2 is connected to SW1 at fast 0/2, and R3 is connected to SW2 at fast 0/3. Both
Category:
When you're studying for the BSCI exam on the way to earning your CCNP certification, it's safe to say that BGP is like nothing you?ve studied to this point. BGP is an external routing protocol used primarily by Internet Service Providers (ISPs).
Category:
One f the first things yu learned abut Frame is that the LMI als serves as a keepalive, r a heartbeat - and if three cnsecutive LMIs are missed, the line prtcl ges dwn. There's a limitatin t LMI as a keepalive, thugh. The LMI is exchanged
Category:
Dialer Watch is a vital part of your CCNA and CCNP studies, particularly for the BCRAN exam, but it's one of the most misunderstood technologies as well. To help you pass the CCNA and CCNP certification exams, here's a detailed look at Dialer
Category:
Site Sponsor
Directory Statistics
Articles: 68214
Categories: 501
Yahoo Entertainment
