Cisco Features navigator

Hi,

Have you ever asked yourself the following question : how could i know if my Cisco device can support a certain specific feature ?

Let say it this way : if you are given a Cisco device that you are not familiar with, how will you know which features does it support ? OR, if you are about to deploy a certain IT solution, how would you know which Cisco device you should buy to accomplish your deployment tasks and more ?

Check out the following video to learn what you should use and how you should use it before ordering a Cisco device :

Main steps of troubleshooting network issues

The main steps of troubleshooting are :

• problem report (the first step is receiving the complaint from a user or from a monitoring tool (using a monitoring tool, we may detect a situation that could become a tshoot issue and resolve that situation before it impacts users : that is called proactive maintenance))
• diagnosis
•  resolve the problem

The first step toward resolving an issue after it's reported, is : clearly define the issue. Diagnosing the reported problem allows to clearly define it. Note that we have to diagnose because most often the end user's report may not have enough information to allow us to resolve the issue.

Right way to configure default route in a router

The process of sending a lot of ARP requests can consume a big percentage of  a router's CPU resources. 

One Configuration that cause a router to send a lot of ARP requests is having a default-route configured that points to an ethernet interface ((config)#ip route 0.0.0.0 0.0.0.0 f0/1) instead of the next hop address ((config)#ip route 0.0.0.0 0.0.0.0 20.1.1.1).

 When configured with an exit interface, the router instead of sending ARP request for MAC address of a next-hop address, it will send ARP request for the MAC address of the destination IP address
in each packet. That result in an excessive number of ARP requests which will cause a spike of the CPU.

Before jumping into a router and start troubleshooting it, we need to know that it's the router that is causing a poor network performance. Click here to read our blog post on how to detect the root cause of a network performance issues.

A router could be the root cause of your network performance. That is a fact. But we should not ignore that applications, servers, user's client can also be the root cause of our network performance. Click here to learn how to identify the source of your network performance.

_____________________________________

Detect the source of your network performace issues

A network performance might be operating at a level that is disturbing productivity and at a level
that is bellow its normal level of operation. As a network administrator, you need to determine
what is the origine of the performance issue or what is network component causing the the poor performance. It could be a switch, a router, the user's client, the server or the application.

How will you know the root cause of your network performace issue ? The answer is by using : WIRESHARK.

With WIRESHARK, you can look into what is really happeing in the wire.
With the help of WIRESHARK you can analyse protocols and identify exactly the root cause of you network performance issues. Don't hesitate to contact us, we offer training on how to set and use WIRESHARK and how to analyse prorocols  >> Here is our contacts if you wish to be part of our next WIRESHARK class

CCNP-TSHOOT teaches how to diagnose/troubleshoot Cisco routers and switches. Of course,  before jumping into your Cisco routers or switches, you should first of all know the root cause of the poor performance issues of your network.

>> Here is our contacts if you wish to be part of our next WIRESHARK class
>> Here is our contact if you wish to attend CCNP-tshoot class