Book now with code EOY2025
Zartanasaurus wrote: » You aren't going to break anything just doing show commands. These should get you a nice little map to start working with:sh cdp neighbor sh lldp neighbor sh spanning-tree root sh vlan br sh int trunk sh etherchannel summarysh int status: List of transceiver types, duplex/speed negotiations.sh protocols: The fastest way I know to get IP/mask info for interfaces.sh ip protocols: Routing protocol info.sh ip int | i line|access_list: Determine if an access-list is applied to a port.sh ip int | i line|access_list|Internet: Same as previous plus adds IP/prefix length configurations. There's lots of good info under sh ip int like MTU, WCCP, CEF, ICMP that you can add to this command if you want.sh errdisable recovery is good to see if anyone enabled timers to recover from storm-control, bpdugard and such.
CodeBlox wrote: » I'm just in fear that if I run these commands, it may bog down the devices and crash them.. I learned that doing debug commands on production routers is not exactly a good thing to do
lantech wrote: » The only thing I might do before you undertake this is to ask for permission. Doing this might get a few people nervous that you are trying to hack into the network from the inside.
Use code EOY2025 to receive $250 off your 2025 certification boot camp!