hehheheh... Well, that's very much a true thing! Isolate, verify, fix! :)
The catchy part about this is the speed at which to do it. You have
LOTS of devices to work through, so an initial measurement of the skills
involved is to isolate which segment(s) of the network are likely to be
the place where the problem exists (and not to get distracted by other
log messages you may see from other problems).
But pick your area, run whatever appropriate show/debug commands to
verify that and then implement your solution to fix. Test/verify that
it works then move on to the next. Always verify though, just like in
the configuration part!
*Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider) #4713,
CCDE #2009::D, JNCIE-M #153, JNCIE-ER #102, CISSP, et al.
CCSI #21903, JNCI-M, JNCI-ER
swm_at_emanon.com
Knowledge is power.
Power corrupts.
Study hard and be Eeeeviiiil......
On 5/5/11 8:57 AM, imran ali wrote:
> not an expert yet but i suggest the following
>
> 1)identify the problem fist ...make sure what is being asked
> 2)check on what routers u need to configure
>
> 3)use sh run | in ...sh run | sec ....sh run | beg ...and other relavent
> show commans
>
> then comes resolution ...
>
>
>
> On Thu, May , 2011 at 2:51 PM, Paul Tim <paultim68_at_gmail.com> wrote:
>
>> Hi
>> Seeking for Experts point of view on "Strategy for Troubleshooting Section
>> "
>>
>> cheers
>> Paul
>>
>>
>> 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
Blogs and organic groups at http://www.ccie.net
Received on Thu May 05 2011 - 09:20:36 ART
This archive was generated by hypermail 2.2.0 : Wed Jun 01 2011 - 09:01:11 ART