Re: Reachibility Issue.

don't go beyond the speed , duplex , vlans...I don't think they would go for
media types...they have much better tricks to slow you down than this one

also show cdp details can be helpful..

----- Original Message -----
From: "sajid mavani" <sajidmavani_at_gmail.com>
To: "Mark Matters" <markccie_at_gmail.com>; "Ryan West" <rwest_at_zyedge.com>
Cc: <ccielab_at_groupstudy.com>
Sent: Saturday, September 12, 2009 8:51 PM
Subject: Re: Reachibility Issue.

> Hi Ryan/Mark
>
> Thanks a lot for the useful suggestion I would follow as per the
> guidelines
> suggested.
> I would make sure that i take care when redistributing routes at layer
> three & step wise check my configuration.
>
> In regards to the back bone reachibility during the initial testing if i
> am
> not able to ping the backbone (BB1 or BB2) it would be a good idea as
> suggested to create a SVI and ping the interface.
>
> Is it possible if the interface media type is configured incorrectly which
> could prevent you to ping the back bone interface ?? I tried a lot to
> check
> on the site to get any command that could change the media Ethernet
> media
> type .. but did not come across.. I am not sure how to go about with it.
>
> Please as per convenience please reply.
>
> Have a pleasant day!!
>
> Regards
>
> Sajid
>
>
>
>
>
> On Sat, Sep 12, 2009 at 9:12 PM, Mark Matters <markccie_at_gmail.com> wrote:
>
>> 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>

--------------------------------------------------------------------------------

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.93/2365 - Release Date: 09/12/09
06:37:00

Blogs and organic groups at http://www.ccie.net
Received on Sat Sep 12 2009 - 21:58:25 ART