Cisco provide a gargantuan amount of documentation for their products, and a lot are available as straight PDF’s direct from Cisco.
In these guides are some useful commands for general maintenance, monitoring on Cisco switches.
packetlife.net is a great site to follow with regular hints, tips on improving your network layout, as well as maintaining and keeping your Cisco systems up and running.
There are two acceptable methods for connecting to a Cisco Switch, either through SSH (if enabled on the switch) or directly through the console port.
When connecting your terminal software make sure to rotate through terminal speeds starting with at minimum 9600.The default terminal speed configuration of a Cisco Router is probably 9600 8N1 but other configurations may have been set such as: 115200 8N1.
The console command-line uses two prompts, the
* ">" is the user-level prompt, and * "#" is the admin user prompt.
Admin access is always available using ’enable’ from the terminal/console connection (or after connecting with a valid ssh user/password.)
> > enable #
’enable’ behaves similarly to su root in Unix. Without it, you’re privileges are mostly limited to a subset “show” commands.
The Cisco switch holds two configurations, the running-config and the startup-config. The running-config is the (potentially unsaved) config currently running, and the startup-config is the persistent configuration that the device starts with.
# show running-config # show startup-config
You can make the current configuration persistent by copying the running-config to the startup-config:
# copy running-config startup-config
The Cisco Switch Configuration text files are simply ascii command-line instructions to recreate a configuration. An example manual configuration of the console/terminal connection is shown below
# config terminal (config)# line con 0 (config)# exec-timeout 60 0 (config)# no modem enable (config)# length 100 (config)# transport preferred none (config)# speed 115200 # end # copy running-config startup-config # show running-config
After configuring the device with an IP address, it is convenient to edit the configuration locally on your desktop, and copy it accross to the switch every so often as you work:
Copy the running config to an sshd host
copy running-config scp:
Copy the edited / text from a http host
config replace http://10.0.0.2:9000/cisco01-config
Runtime monitoring with the ‘show’ command, some interesting options
* ver - hardware and software version, summary interfaces, and why the router was last started (or crashed) * proc - note: >70% utilisation is asking for trouble * mem - memory utilisation * running-config | run - Running Configuration * startup-config | conf - Startup Configuration * int <strong>interface-name</strong> - Interface details * ip route - Without any parameters, this will show you all routes in the IP routing table. * ip route <strong>x.y.z.q</strong> - Shows routing information on one or more of the most specific routes that contain that IP address - however, if you enter an IP address for which no route but the default route (0.0.0.0) exists, the default route will not be shown. * ip route <strong>x.y.z.q netmask longer-prefixes</strong> - Shows a list of routes that are within the IP range specified by x.y.z.q as a starting point and netmask as a length. The longer-prefixes keyword tells it to find all routes that fall in that range - of all specificities (prefix length = specificity). * ip bgp - Without any parameters, this will show you all routes heard via BGP. * ip bgp <strong>x.y.z.q</strong> - Shows routing information on one or more of the most specific BGP routes that contain that IP address - if you enter an IP address for which no route but the default route (0.0.0.0) exists, the default route will not be shown. * ip bgp <strong>x.y.z.q netmask longer-prefixes</strong> - Shows a list of BGP routes that are within the IP range specified by x.y.z.q as a starting point and netmask as a length. The longer-prefixes keyword tells it to find all BGP routes that fall in that range - of all specificities (prefix length = specificity). * ip bgp reg <strong>regexp</strong> - This shows you all BGP routes matching the regular expression regexp. For example, sho ip bgp reg _1_ shows you all BBN routes. * ip bgp ? - You may want to explore the other sho ip bgp commands. Typing sho ip bgp ? will get you a list of them. You can't do any harm with a sho command... * ip bgp summ
# config term (config)# enter configuration commands ... ... (config)# end
Revert to the startup configuration using router replace.
# router replace nvram:startup-config