Hi all - I'm curious what others recommend doing before you start working on actual lab tasks. Obviously, the basic that everyone starts with is reading through the entire lab first to get a good idea of the overall picture. I'm finding that I have what could be a decently time consuming list of things go through in an attempt to root out and discover any planted misconfigurations. How many of these do you actively do at the beginning as opposed to going with the flow and using these for troubleshooting as issues arise?
1 – Read lab end to end 2 – Create L2 map labeling switches, devices, physical ports, vlans allowed, IP address, trunk, etherchannel 3 – Verify ports are in correct vlan for each device 4 – Verify trunks are correctly configured and permit vlans - "sh inter tru" 5 – Verify IP / subnet for switch SVI's - "sh run | be interface V" 6 – Verify etherchannels - "sh ether summ" 7 – Verify neighbors are on correct ports - "sh cdp neigh" 8 – Verify IP on AAP - "sh ip int brie" 9 – Verify WLC IP, subnet, vlan, port, ap manager - "sh inter det mana" 10 – Verify lwapp's aren't running autonomous code - "sh ver" 11 – Look through each switch config and look for any anomalies, such as "vlan dot1q tag native" or a shutdown vlan 12 – Ping each controller management IP from switch Thanks - Jay Killion, CCIE #17873
_______________________________________________ Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos :: iPexpert on YouTube: www.youtube.com/ipexpertinc
