I start at the closest router and see if I can ping. If I can not then I
look at the switches. If everything looks fine I slap a SVI on the switch
the router/bb is connected to and see if I can ping to the SVI. Can I ping
from the switch to the router. etc... When in doubt I diagram to see the
path.
I have found this occurs when I misconfigure something, ip address, access
vlan, trunk ports, did I filter something and I forgot to add all the
necessary info. . I use the same approach as Ryan does. Config, verify and
move on.
Check out INE's blog....troubleshooting articles
On Sat, Sep 12, 2009 at 3:37 AM, sajid mavani <sajidmavani_at_gmail.com> wrote:
> Hello Seniors,
>
> I had a query if in case you are not able to ping any of your routers or
> Backbone interfaces what is the best possible troubleshooting steps.
>
> As per my understanding I would follow the following steps.
>
> 1) sh ip int b -- check the line protocol
> 2) check duplex settings
> 3) trace route check .
> 4) check for any access-list configured that would block ping reachibility.
> 5) check proper access vlan passed in the given interface
> 6) ?
> 7) ?
> 8) ?
> 9) ?
>
> Also if possible let me know what would be the best approach to
> troubleshoot any layer 2 & Layer 3 related problems if possible.
>
> Please let me know what would be the best approach, kindly reply to my
> query
> as per your convenience
>
> Have a pleasant day!!!
>
> Regards
>
> Sajid .
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Sat Sep 12 2009 - 11:42:04 ART
This archive was generated by hypermail 2.2.0 : Sun Oct 04 2009 - 07:42:03 ART