![]() ![]() (obviously copy the config to notepad so you can re-apply it) If it does resolve the problem you can then look at how you can change that feature to make the ticket work. What this means is if you isolate a problem to what you think might be being caused by a feature simply remove that feature and see if it fixes the ticket. ![]() Do not be afraid to remove any feature to prove if it is causing a problem.I am not going to blog here today about everything I learnt as this will come in the next few weeks with some more specific posts on different technologies, but I will list a few points below ![]() ![]() Mixed in with Brians humour and views and insight into the future of networking this was for me and I am sure everyone else that attended an invaluable week in preparation for the troubleshooting section of ccie r&S lab. If you have never been to a ccie bootcamp I would highly recommend it – they are not cheap but totally worth it. This has certainly been a drinking from the fire hose week where there wasn’t a moment where you were not learning something new. If you want to see the style of the teaching there some videos from INE here The next 4 days took the format of reviewing the previous evenings tickets through the day, taking at least 45 minutes per ticket and not just going through the solution but exploring all possible solutions. Well after 5 days of CCIE Troubleshooting tickets with 20 other students and Brian Dennis in London this week, I am back home and just trying to process what I have learnt!ĭay 1 – full write up here – was an introduction to troubleshooting, basic strategy and some technology basics, and then attempting to build the entire 30 router topology and starting at 6pm the first 10 tickets. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |