packet_tracer
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
packet_tracer [2021/07/06 12:39] richard [Updating 2960 switch] |
packet_tracer [2023/03/10 00:34] (current) richard [Updating 2960 switch] |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| - check for connectivity (do some pings) | - check for connectivity (do some pings) | ||
| - copy file from TFTP server | - copy file from TFTP server | ||
| - | * issue ''copy tftp: flash:'' command. You'll be asked for TFTP server IP address, then the file you want to copy. You can just paste the filename ''c2960-lanbasek9-mz.150-2.SE4.bin'' when asked for it rather than type it. (when viewing the server in the "Services" tab you can find the file you want and hit Ctrl+C) After file has completed copying, command ''show flash:'' will list the files in flash memory. Your copied file should show. | + | * issue ''copy tftp: flash:'' command. You'll be asked for TFTP server IP address, then the file you want to copy. You can just paste the filename ''c2960-lanbasek9-mz.150-2.SE4.bin'' when asked for it rather than type it. (you can also find that file name when viewing the server in the "Services" tab you can find the file you want and hit Ctrl+C) After file has completed copying, command ''show flash:'' will list the files in flash memory. Your copied file should show. |
| - issue boot system command to boot from new file, save config | - issue boot system command to boot from new file, save config | ||
| * In global config mode, issue ''boot system flash:c2960-lanbasek9-mz.150-2.SE4.bin'' | * In global config mode, issue ''boot system flash:c2960-lanbasek9-mz.150-2.SE4.bin'' | ||
| Line 40: | Line 40: | ||
| * ''show version'' | * ''show version'' | ||
| + | \\ | ||
| + | Bundle and install mode: | ||
| + | https://www.lookingpoint.com/blog/ios-xe-catalyst-switches\\ | ||
| + | https://content.cisco.com/chapter.sjs?uri=/searchable/chapter/c/en/us/td/docs/switches/lan/Denali_16-1/ConfigExamples_Technotes/Config_Examples/Misc/qos/m_install_vs_bundle.html.xml | ||
| ==== Updating 2811 router ==== | ==== Updating 2811 router ==== | ||
| Line 56: | Line 59: | ||
| * in enable mode, issue ''copy tftp: flash:''. You'll be asked for the tftp server IP address and the file you want to copy. | * in enable mode, issue ''copy tftp: flash:''. You'll be asked for the tftp server IP address and the file you want to copy. | ||
| * Once file has copied you can issue ''show flash:'' to confirm new file is there. | * Once file has copied you can issue ''show flash:'' to confirm new file is there. | ||
| - | - issue boot system command to boot from new file, (delete tftp boot), save config | + | - issue boot system command to boot from new file, (delete any accidental tftp boot), save config |
| * issue ''boot system flash:c2800nm-advipservicesk9-mz.151-4.M4.bin'' | * issue ''boot system flash:c2800nm-advipservicesk9-mz.151-4.M4.bin'' | ||
| - | * somehow a ''boot system tftp'' command may have found its way into the config (i don't know why this happens?? you may see this in running-config (''show running-config'')), delete this with a ''no boot system tftp'' command | + | * somehow a ''boot system tftp'' command may have found its way into the config (possible if you accidentally forgot to declare "flash" in the boot command). You will see this in running-config (''show running-config''), delete this with a ''no boot system tftp'' command |
| * issue ''write'' to save config | * issue ''write'' to save config | ||
| - reboot ''reload'' | - reboot ''reload'' | ||
| Line 88: | Line 91: | ||
| ===== Basic Routing ===== | ===== Basic Routing ===== | ||
| + | ==== Basic Routing with Layer 3 switches ==== | ||
| + | |||
| + | Simple labs to demonstrate use of Layer 3 switches. These can be more efficient than Layer 2 switches as some ethernet frames broadcasts flooding a broadcast domain are prevented. I used RIP and EIGRP in these labs so the devices will share routes between the subnets with each other. It was much easier than having to declare static routes. \\ | ||
| + | \\ | ||
| + | Linking subnets together\\ | ||
| + | {{:packet_tracer:pt_layer_3_linking_subnets.png?400|}}\\ | ||
| + | \\ | ||
| + | Adding more devices\\ | ||
| + | {{:packet_tracer:pt_layer_3_linking_subnets_more_devices.png?400|}}\\ | ||
| + | \\ | ||
| + | Using Layer 3 switch's Switch Virtual Interfaces (SVI) to act as a gateway\\ | ||
| + | {{:undefined:pt_layer_3_linking_subnets_svi_gateway.png?400|}}\\ | ||
| + | \\ | ||
| + | {{ :packet_tracer:layer_3_switching_basic.zip |}} | ||
| ===== Loopback Interfaces ===== | ===== Loopback Interfaces ===== | ||
| Line 206: | Line 223: | ||
| ===== Cisco IOS Device Security ===== | ===== Cisco IOS Device Security ===== | ||
| + | ==== Console security ==== | ||
| + | To set up a new router or switch you will need to console into the device with a rollover cable a computer. \\ | ||
| + | A new router or switch will not have any security to protect its configuration.\\ | ||
| + | They'll be no password required to access the device.\\ | ||
| + | In most environments you will probably want to set a password to stop the casual user from going into the router and viewing or changing config. | ||
| + | ==== Telnet and SSH access ==== | ||
| + | When you get a brand new router or switch, you will need to console into the device with your laptop and a rollover cable to set it up. However long term you probably don't want to use the rollover cable all the time. You will want to set up remote access via Telnet and/or SSH. This means as long as you have IP access to the device, you can check and update configurations from a remote telnet/SSH terminal rather than having to be next to the device with your rollover cable. | ||
| ===== AAA ===== | ===== AAA ===== | ||
packet_tracer.1625575172.txt.gz · Last modified: 2021/07/06 12:39 by richard
Page Tools
