TEKNOMANIA ONLINE Teknomania Online Information News
Whether you’re on the road to the CCNA, CCNP, MCSE, or you’re on any other computer certification track, the odds are that sooner or later, you’re going to fail an exam. It’s happened to almost all of us, yours truly included. What you have to keep in mind in these times is that success is not a straight line. You’ve probably seen charts showing the growth of an industry or a business — you know, the ones that go from left to right, and look kind of jagged. The line goes up for a while, then down a bit, then up some more, then down a little.
The key? While every business has its setbacks, the net result is that the line goes up and progress is made. That’s how you want your certification pursuit and your career to go as well – upward!
I’m not asking you to be happy about failing an exam. You’re allowed to get mad for a few minutes, vow to never take another exam again, and be disappointed. What you’re not allowed to do is stay that way.
If you put your books away in a fit of anger, get them out. If you took some time off, it’s time to get back to work. Again, there’s nothing wrong with being unhappy about failing an exam. It’s how you handle that failure that counts. No inventor, executive, or entrepreneur has ever been right 100% of the time. Learn something from your failure. Was your study time quality study time? Did you get some hands-on practice with the technology you’re studying? Asking yourself these questions can be tough, but it can be highly valuable in making sure you don’t fail the next time. And there must be a next time – because the one thing you cannot do is quit.
Besides, take it from someone who’s been there – your temporary failure makes your eventual success that much sweeter.
CCNA Certification Exam Tutorial: Cisco Switching Modes
To pass the CCNA exam and earn this important certification, you’ve got to know switching inside and out. While you’re learning all the basic switching theory, make sure to spend some time with the one of three switching modes Cisco routers can use.
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.
Learning the similarities and differences between these modes is an often-overlooked part of CCNA studies. Spend some time studying this important CCNA topic – you’ll be glad you did!
CCNP / BCMSN Exam Tutorial: VLAN Trunking Protocol (VTP)
Passing the BCMSN exam and getting one step closer to the CCNP certification means learning and noticing details that you were not presented with in your CCNA studies. (Yes, I know – you had more than enough details then, right?) One protocol you’ve got to learn more details about is VTP, which seemed simple enough in your CCNA studies! Part of learning the details is mastering the fundamentals, so in this tutorial we’ll review the basics of VTP.
In show vtp status readouts, the “VTP Operating Mode” is set to “Server” by default. The more familiar term for VTP Operating Mode is simply VTP Mode, and Server is the default. It’s through the usage of VTP modes that we can place limits on which switches can delete and create VLANs.
In Server mode, a VTP switch can be used to create, modify, and delete VLANs. This means that a VTP deployment has to have at least one switch in Server mode, or VLAN creation will not be possible. Again, this is the default setting for Cisco switches.
Switches running in Client mode cannot be used to create, modify, or delete VLANs. Clients do listen for VTP advertisements and act accordingly when VTP advertisements notify the Client of VLAN changes.
VTP Transparent mode actually means that the switch isn’t participating in the VTP domain as Servers and Clients do. (Bear with me here.) Transparent VTP switches don’t synchronize their VTP databases with other VTP speakers. They don’t even advertise their own VLAN information! Therefore, any VLANs created on a Transparent VTP switch will not be advertised to other VTP speakers in the domain, making them locally significant only. (I know you remember that phrase from your CCNA studies!)
Devices running VTP Transparent mode do have a little something to do with the other switches in the VTP domain, though. When a switch running in Transparent mode receives a VTP advertisement, that switch will forward that advertisement to other switches in that VTP domain.
Configuring switches as VTP Clients is a great way to “tie down” VLAN creation capabilities to switches that are under your physical control. However, this occasionally leads to a situation where only the VTP clients will have ports that belong to a given VLAN, but the VLAN still has to be created on the VTP server. (VLANs can be created and deleted in transparent mode, but those changes aren’t advertised to other switches in the VTP domain.)
In the next BCMSN tutorial, we’ll take a look at the details of VTP.
CCNP / BSCI Exam Tutorial: Route Summarization And The OSPF Null Interface
CCNP exam success, particularly on the BSCI exam, demands you understand the details of route summarization. This skill not only requires that you have a comfort level with binary conversions, but you have to know how and where to apply route summarization with each individual protocol.
You also have to know the “side effects” of route summarization. With OSPF, there will actually be an extra interface created at the point of summarization, and this catches a lot of CCNP candidates by surprise. Let’s take a look at the null0 interface and how it relates to OSPF summarization.
On R1, the following networks are redistributed into OSPF, and then summarized.
interface Loopback16
ip address 16.16.16.16 255.0.0.0
interface Loopback17
ip address 17.17.17.17 255.0.0.0
interface Loopback18
ip address 18.18.18.18 255.0.0.0
interface Loopback19
ip address 19.19.19.19 255.0.0.0
R1(config)#router ospf 1
R1(config-router)#redistribute connected subnets
R1(config-router)#summary-address 16.0.0.0 252.0.0.0
The summary address appears on R2, a downstream router.
R2#show ip route ospf
O E2 16.0.0.0/6 [110/20] via 172.12.123.1, 00:00:05, Serial0
Let’s go back to R1 and look at its OSPF table.
R1#show ip route ospf
O 16.0.0.0/6 is a summary, 00:01:51, Null0
Where did the null0 interface come from, and why is it there? Packets sent to the null interface are dropped, and in this case, that’s a good thing.
When you configure summary routes in OSPF, a route to null0 will be installed into the OSPF routing table. This helps to prevent routing loops. Any packets destined for the routes that have been summarized will have a longer match in the routing table, as shown below…
C 17.0.0.0/8 is directly connected, Loopback17
C 16.0.0.0/8 is directly connected, Loopback16
C 19.0.0.0/8 is directly connected, Loopback19
C 18.0.0.0/8 is directly connected, Loopback18
O 16.0.0.0/6 is a summary, 00:01:51, Null0
.. and packets that do not match one of the summarized routes but do match the summary route will be dropped.
Preventing routing loops when performing route redistribution and summarization is vital. OSPF gives us a little help in that regard in this situation, and as you study more complex redistribution scenarios on your way to the CCNP and CCIE, you’ll realize that we’ll take all the help we can get!
CCNP Certification / BCMSN Exam Tutorial: Getting Started With HSRP
Defined in RFC 2281, HSRP is a Cisco-proprietary protocol in which routers are put into an HSRP router group. Along with dynamic routing protocols and STP, HSRP is considered a high-availability network service, since all three have an almost immediate cutover to a secondary path when the primary path is unavailable.
One of the routers will be selected as the primary (“Active”, in HSRP terminology), and that primary will handle the routing while the other routers are in standby, ready to handle the load if the primary router becomes unavailable. In this fashion, HSRP ensures a high network uptime, since it routes IP traffic without relying on a single router.
The hosts using HSRP as a gateway don’t know the actual IP or MAC addresses of the routers in the group. They’re communicating with a pseudorouter, a “virtual router” created by the HSRP configuration. This virtual router will have a virtual MAC and IP adddress as well.
The standby routers aren’t just going to be sitting there, though! By configuring multiple HSRP groups on a single interface, HSRP load balancing can be achieved.
Before we get to the more advanced HSRP configuration, we better get a basic one started! We’ll be using a two-router topology here, and keep in mind that one or both of these routers could be multilayer switches as well. For ease of reading, I’m going to refer to them only as routers.
R2 and R3 will both be configured to be in standby group 5. The virtual router will have an IP address of 172.12.23.10 /24. All hosts in VLAN 100 should use this address as their default gateway.
R2(config)#interface ethernet0
R2(config-if)#standby 5 ip 172.12.23.10
R3(config)#interface ethernet0
R3(config-if)#standby 5 ip 172.12.23.10
The show command for HSRP is show standby, and it’s the first command you should run while configuring and troubleshooting HSRP. Let’s run it on both routers and compare results.
R2#show standby
Ethernet0 – Group 5
Local state is Standby, priority 100
Hellotime 3 sec, holdtime 10 sec
Next hello sent in 0.776
Virtual IP address is 172.12.23.10 configured
Active router is 172.12.23.3, priority 100 expires in 9.568
Standby router is local
1 state changes, last state change 00:00:22
R3#show standby
Ethernet0 – Group 5
Local state is Active, priority 100
Hellotime 3 sec, holdtime 10 sec
Next hello sent in 2.592
Virtual IP address is 172.12.23.10 configured
Active router is local
Standby router is 172.12.23.2 expires in 8.020
Virtual mac address is 0000.0c07.ac05
2 state changes, last state change 00:02:08
We can see that R3 has been selected as the Active router (“local state is Active”), the virtual router’s IP is 172.12.23.10, and R2 is the standby router.
There are some HSRP values that you’ll need to change from time to time. What if we want R2 to be the Active router instead? Can we change the MAC address of the virtual router? I’ll answer those questions in the next part of this HSRP tutorial!
CCNP Certification / BCMSN Exam Tutorial: HSRP MAC Addresses And Timers
To earn your CCNP certification and pass the BCMSN exam, you’ve got to know what HSRP does and the many configurable options. While the operation of HSRP is quite simple (and covered in a previous tutorial), you also need to know how HSRP arrives at the MAC address for the virtual router – as well as how to configure a new MAC for this virtual router. This puts us in the unusual position of creating a physical address for a router that doesn’t exist!
The output of show standby for a two-router HSRP configuration is shown below.
R2#show standby
Ethernet0 – Group 5
Local state is Standby, priority 100
Hellotime 3 sec, holdtime 10 sec
Next hello sent in 0.776
Virtual IP address is 172.12.23.10 configured
Active router is 172.12.23.3, priority 100 expires in 9.568
Standby router is local
1 state changes, last state change 00:00:22
R3#show standby
Ethernet0 – Group 5
Local state is Active, priority 100
Hellotime 3 sec, holdtime 10 sec
Next hello sent in 2.592
Virtual IP address is 172.12.23.10 configured
Active router is local
Standby router is 172.12.23.2 expires in 8.020
Virtual mac address is 0000.0c07.ac05
2 state changes, last state change 00:02:08
R3 is in Active state, while R2 is in Standby. The hosts are using the 172.12.123.10 address as their gateway, but R3 is actually handling the workload. R2 will take over if R3 becomes unavailable.
An IP address was assigned to the virtual router during the HSRP configuration process, but not a MAC address. However, there is a MAC address under the show standby output on R3, the active router. How did the HSRP process arrive at a MAC of 00-00-0c-07-ac-05?
Well, most of the work is already done before the configuration is even begun. The MAC address 00-00-0c-07-ac-xx is reserved for HSRP, and xx is the group number in hexadecimal. That’s a good skill to have for the exam, so make sure you’re comfortable with hex conversions. The group number is 5, which is expressed as 05 with a two-bit hex character. If the group number had been 17, we’d see 11 at the end of the MAC address – one unit of 16, one unit of 1.
The output of the show standby command also tells us that the HSRP speakers are sending Hellos every 3 seconds, with a 10-second holdtime. These values can be changed with the standby command, but HSRP speakers in the same group should have the same timers. You can even tie down the hello time to the millisecond, but it’s doubtful you’ll ever need to do that.
R3(config-if)#standby 5 timers ?
<1-254> Hello interval in seconds
msec Specify hello interval in milliseconds
R3(config-if)#standby 5 timers 4 ?
<5-255> Hold time in seconds
R3(config-if)#standby 5 timers 4 12
Another important HSRP skill is knowing how to change the Active router assignment. I’ll show you how to do that, and how to configure HSRP interface tracking, in the next part of my CCNP / BCMSN exam tutorial!