IPexpert, Inc
  • CartCart
  • Client Login
  • About IPexpert
  • Contact Us
 
Call 1-866-225-8064 | Chat with a Training Advisor 
 
  • CCIE R&S
    • Lab Workbooks
    • Video on Demand
    • Audio on Demand
    • Online vRack Rental
    • Blended Learning Self-Study Bundle
    • Courses / Boot Camps
    • Complete End-to-End Solution
    • Free Online CCIE R&S Training
  • CCIE Voice
    • Lab Workbooks
    • Video on Demand
    • Audio on Demand
    • Online vRack Rental
    • Blended Learning Self-Study Bundle
    • Courses / Boot Camps
    • Complete End-to-End Solution
    • Free Online CCIE Voice Training
  • CCIE Wireless
    • Lab Workbooks
    • Video on Demand
    • Audio on Demand
    • Online vRack Rental
    • Blended Learning Self-Study Bundle
    • Courses / Boot Camps
    • Complete End-to-End Solutions
    • Free Online CCIE Wireless Training
  • CCIE Security
    • Lab Workbooks
    • Video on Demand
    • Audio on Demand
    • Online vRack Rental
    • Blended Learning Self-Study Bundle
    • Courses / Boot Camps
    • Complete End-to-End Solution
    • Free Online CCIE Security Training
 
  • IPexpert Around the Web

    • Follow us on Twitter
    • Join us on Facebook
    • Connect at LinkedIn
    • Stay up to date with RSS

  • Search


  • Technical Blogs by Track

    * CCIE R&S Technical Blogs

    * CCIE Voice Technical Blogs

    * CCIE Wireless Technical Blogs

    * CCIE Security Technical Blogs

    * General Technical Blogs

    * All CCIE Tracks vLecture Videos


  • 5 Day CCNA Bootcamp!

    CCNA 5 Day Bootcamp

    CCNA Instructor Led Bootcamp is delivered by CCIEx2 #8918 (R&S,Sec) Senior Technical Instructor Rahim Raoufi. Register and get Free CCNA Self Study Tools, Exam Voucher and $1000 Credit towards CCNP Training.


  • Join Our Free Online Study List


  • View CCIE Job Opportunities


  • Cisco Certification Training


  • Tags

    CCIE ccie exam CCIE Job CCIE Jobs ccie lab CCIE lab training CCIE R&S CCIE R&S Lab CCIE R&S Training ccie r&s written CCIE Routing & Switching CCIE Security CCIE Security 3.0 ccie security training CCIE Service Provider CCIE Success CCIE Success Stories CCIE Training ccie voice ccie voice jobs ccie voice lab CCIE Voice Training CCIE Wireless CCIE Wireless Training ccna ccnp Cisco exam free ccie training free ccie voice training ipexpert IPv6 lab MPLS multicast OSPF practice r&s Security Strategy study training Troubleshooting Voice Written

  • Quick Links

    CCIE Training

    CCIE Lab Training

    CCIE Written Training

    CCNP Training

    CCNA Training

    CCIE Training in India


Spot the Differences Troubleshooting

VN:F [1.9.6_1107]
Rating: 5.0/5 (1 vote cast)
By Anthony Sequeira on September 8th, 2011
Tweet

“One of these things is not like the other!” This popular children’s exercise can certainly come into play with our various troubleshooting approaches!

When you engage in the The Spot the Differences approach to troubleshooting, you attempt to compare functioning to malfunctioning devices or processes and spot the differences. This might even allow you to implement a solution or a workaround to a problem without even understanding the underlying cause.

By comparing configurations, software versions, hardware or link properties between working and nonworking situations and spotting significant differences between them, you might be able to resolve the problem by changing the nonoperational situation to be consistent with the working situation.

As alluded to above, the biggest disadvantage with this method is that it can lead to a working situation, but not to an understanding of the root cause of the problem.

You should notice that the effectiveness of this method depends on how easy it is to compare working and nonworking devices, situations, or processes. Having a good baseline of what constitutes normal behavior on the network makes it easier to spot abnormal behavior. Also, the use of consistent configuration templates makes it easier to spot the significant differences between functioning and malfunctioning devices. As a result of all of these factors, the effectiveness of this method does typically depend on the quality of the overall network maintenance process.

Finally, you should also take note that like the follow-the-path method, this approach is best used as a supporting method in combination with other methods such as top-down or bottom-up troubleshooting.

Anthony Sequeira CCIE, CCSI
Twitter: @compsolv
Facebook: http://www.facebook.com/compsolv

 

Print FriendlyPrint Friendly

Tags: CCIE, ccie exam, CCIE Training, ccie troubleshooting, Cisco, exam, training, Troubleshooting
No Comments

Follow the Path Troubleshooting

VN:F [1.9.6_1107]
Rating: 4.5/5 (2 votes cast)
By Anthony Sequeira on September 7th, 2011
Tweet

Another important and basic troubleshooting technique that you should be aware of is called Follow the Path. This method is typically used in conjunction with another of the troubleshooting techniques that we have discussed in previous posts. For example, following the path might be used in conjunction with the top down or bottom up troubleshooting approaches.

What do we do when we engage in follow the path troubleshooting? We engage in tracing the path of packets through the network in order to eliminate irrelevant links and devices from the troubleshooting process. Notice that the objective of this method of troubleshooting is to isolate the problem by eliminating potential problem areas from the scope of the troubleshooting process. When you analyze and verify the path that packets take through the network as they travel from a source to a destination, you can reduce the scope of your troubleshooting to just those links and devices that are actually in the forwarding path.

Anthony Sequeira CCIE, CCSI
Twitter: @compsolv
Facebook: http://www.facebook.com/compsolv

 

Print FriendlyPrint Friendly

Tags: CCIE, ccie exam, ccie lab, ccie strategy, CCIE Tips, CCIE Training, exam, lab, Strategy, training, Troubleshooting
1 Comment

The Divide and Conquer Troubleshooting Approach

VN:F [1.9.6_1107]
Rating: 0.0/5 (0 votes cast)
By Anthony Sequeira on September 6th, 2011
Tweet

Are you looking for the most efficient method possible when it comes to using the OSI model as a guide for your Troubleshooting approach? Well then you have arrived at the correct place.

This method has you do your fact gathering (as usual), and then based on the information you have gathered, it has you dive right into to the most likely layer of the OSI model.

Divide and Conquer

Please keep in mind that you might be dead wrong, of course. Be very ready to move up or down in the OSI model with your troubleshooting based on the information you gather at the particular layer that you started at.

Ready for an example? Let’s say you are working with a Trouble Ticket that states you are not receiving a particular prefix from your RIP peer. This certainly sounds like you are receiving other prefixes for RIP from the device. A great idea would be do dive right into the Network layer and check for any filtering mechanisms that might be in place. You could also start with a debug ip rip as well at this Network layer. Based on what you discover, you might be moving up or down in the OSI.

Anthony Sequeira CCIE, CCSI
Twitter: @compsolv
Facebook: http://www.facebook.com/compsolv

Print FriendlyPrint Friendly

Tags: ccie exam, ccie lab, CCIE Practice, CCIE Tips, Cisco, Troubleshooting, TSHOOT
No Comments

The Bottom-Up Troubleshooting Approach

VN:F [1.9.6_1107]
Rating: 1.3/5 (3 votes cast)
By Anthony Sequeira on September 4th, 2011
Tweet

Did you read the previous post in this series regarding the Top-Down Troubleshooting approach? If you did, then you already have a great understanding for this Troubleshooting approach. Once again, we are going to rely on the OSI model as a guide as we troubleshoot. This time, however, we are going to start that physical layer and work our way up the layers. Hey, do you need a review of what those layers are? Here you go:

  • Application
  • Presentation
  • Session
  • Transport
  • Network
  • Data Link
  • Physical

When you engage in the Bottom-Up Troubleshooting approach, you are eliminating more and more potential problems as you move up each layer. It is fun! I rely on this Troubleshooting approach when in doubt, that is for sure.


Read Full Entry »

Print FriendlyPrint Friendly

Tags: CCIE, ccie exam, CCIE lab training, ccie strategy, CCIE Tips, CCIE Training
No Comments

The Top-Down Troubleshooting Approach

VN:F [1.9.6_1107]
Rating: 0.0/5 (0 votes cast)
By Anthony Sequeira on August 31st, 2011
Tweet

When you engage in the Top Down troubleshooting approach, you are using the OSI reference model as a guide, and you are hoping that the problem is one of the higher layers! You are beginning your troubleshooting in the higher layers, trying to find the highest layer that is working. You see, the way the OSI reference model works, if we can determine that a particular layer works, then it is a pretty safe assumption that all the layers below it are functional. Notice I say “pretty” safe. There might indeed be problems at a lower layer that are so specific, they are not showing up in your initial evidence collection.

What is an example of a Trouble Ticket where we might immediately latch on to the Top-Down Troubleshooting approach? Well, how about this…

TROUBLE TICKET 4

Users in Subnet 101 are reporting that they can access Web content from Subnet 201, but they are unable to transfer files to or from an FTP server in that subnet.

Here we can see that a Top Down Troubleshooting approach certainly makes sense. Especially when we balance this against starting with a Bottom Up approach (covered in the next blog post). It is quite clear that we do not have a physical layer issue, since the Web connectivity would not work.


Read Full Entry »

Print FriendlyPrint Friendly

Tags: CCIE, ccie exam, ccie lab, CCIE Practice, ccie strategy, CCIE Tips, ccie troubleshooting
No Comments

« Older Entries
Newer Entries »
 
Avatars by Sterling Adventures
  • Terms & Conditions
  • Sitemap
  • Communities
  • Client Testimonials
  • Blog
© 2000-2010 IPexpert Inc. All rights reserved