. While I was with the State of Montana, I saved our department (and the tax payers of Montana) thousands of dollars in Cisco equipment costs by performing due diligence measures.
While at Qwest, I promoted a remote computer support model, which ultimately saved the company money in travel (and travel related expenses). I have volunteered as a guest instructor at the University of Montana, college of technology, in Helena and Missoula Montana (2010 via WebEx). I am a former member of the 2003, 2004 University of Montana (COT) IT curriculum advisory committee. I was a member of the HCMC technology review committee (. TRC), solutions engineering group, and the CIRT Team (security incident response).
I believe my engineering, teaching, mentoring, leadership experience, broad corporate IT security exposure, and seasoned people skills will be an instant asset to Northwestern College. I believe my teaming ability, previous employment experiences, coupled with strong technology and security skills will pave the way to another solid and successful outcome. My present career goal is to continue in network/security architecture and engineering. I possess vast experience in multiple IT verticals and have driven successful outcomes in each of them. Summary - I am experienced in successes and will not settle for anything less. Senior VP of Information Technology, utilizing extensive knowledge of information technology and security to meet customer and corporate business objectives. Team Lead, Network Systems/Security Engineering, 01/2013 to Current Northwestern College – Blaine, Minnesota.
I bring Executive Leadership and mid-level management experience, coupled with strong network engineering/integration, security, and administration skills to the position. My management skill set includes, executive level strategic planning, IT department planning, project management, change management, risk assessment & management, budgeting, and staff development. My engineering experience includes principal/senior level; network/systems architecture, network management, IT infrastructure, network operations/security (including audit & incident response). In my current position, I have driven IT department change on multiple fronts (from my lead engineering role). I generated a 'state of the network' document (my first week on the job) for the IT Infrastructure Manager, IT Director, and the COO, which addressed infrastructure FTE needs, enhanced change management, required core infrastructure upgrades, and technology/security direction. All of my recommendations have been adopted.
We are currently working on security risk assessment/management and network segmentation (securing the datacenter). I recently finished architecting and implementing a new Security Intrusion Prevention System based on Cisco Firepower (Sourcefire) services (October - 2015) and was part of a team that architected and implemented a new Co-Lo datacenter in Las Vegas (December -2015). In my previous executive leadership role, I was the Vice President of Information Technology at Missoula Federal Credit Union. During my tenure, I participated in strategic planning, IT department planning (tied to strategic initiatives), and daily operation of the IT department (manager of staff, technology life cycle, operational efficiencies, disaster recovery, business continuity, IT governance, budgeting, and managing operational risk).
2006 Technology focus included enhanced operational security measures (Cisco ASA, CSC Anti-X, IOS IPS), Cisco wireless network pilot project, Microsoft Active Directory rollout planning, Nortel telephony system redundancy, VoIP initiatives, and standardized on Cisco's layer2 and layer3 technologies (I also architected and re-engineered the Cisco core switched network). I have driven multiple successful technology project outcomes at HCMC and Corporate Technology Group (Cisco Partner). As the Network Manager/Analyst at Blue Cross Blue Shield of Montana, I initiated infrastructure projects (including RFP work) to replace the datacenter Cisco core network switch fabric and frame-relay based WAN (with Cisco 6500 switches in the core and a VPN based wide-area network). I also planned and executed the first network 'off-site' disaster recovery test to IBM, Boulder, CO. I was a member of the security incident response team and heavily involved with HIPAA compliance related initiatives and audit response.
Supervisor, Senior Network Engineer, 02/2011 to 12/2012 Capella University – Minneapolis, Minnesota. Design, analysis, troubleshooting, proactive maintenance and monitoring of network components to maintain and enhance the corporate local and wireless network infrastructure. Provide technical and operational support on the network infrastructure hardware, including Cisco network routers, switches, ASA firewalls, intrusion prevention systems, F5 load balancers, network access controls, monitoring and supporting systems. Perform oversight and management of network hardware configurations, security credentials, installations and repairs. Provide hardware and software upgrade services, maintain infrastructure operational documentation, and follow approved change management administrative policies and procedures.
Provide strategic and technical assistance in the planning, implementation, upgrade, capacity, and support of the networking applications and infrastructure environments. Provide guidance and oversight of internal and external vulnerability, penetration, PCI, and technology audit testing and procedures. Manage, administer, and configure DNS/DHCP settings. Team Lead, Principal Network Engineer,. OSI Model advocate. Strong Cisco switching, routing, and security experience: Layer2 = ARP, CDP, VLANs (VTP), Spanning Tree Protocol, 802.1Q trunking, ether channel/port channel. Layer3 = IPSec, ARP, HSRP, EIGRP, IP routing, eBGP, iBGP.
Layer4 = TCP, UDP, ICMP, GRE, ESP. Security = Cisco PIX & ASA Firewalls, IOS IPS, IOS SLA, ACLS-route-maps, IPSec remote access and site-to-site VPNs. Hardware exposure includes: Cisco 2900, 3750, 3560, 6500 (catOS & IOS), 3800 ISR routers, asa5540, asa5520, cisco3030 vpn, wireless (WCS), F5 Load-balancers (3600 LTM), Mitel VoIP. Network Management system and protocol analysis tools include = Wild Packets, Wire Shark protocol analyzers, Fluke Optiview toolset, HP OpenView, CiscoWorks, Kiwi syslogger, MRTG.
DNS, DHCP, QoS (cos and DiffServ). Member of the Technology Review Committee (TRC), Solutions Engineering group, and the CIRT Team (Security Incident Response). CCNA 640-801 (925). 640-802 (active). Senior Network Engineer,. Security design, implementation, and support. Conducting and managing network assessments, assisting other engineers when needed.
Experience with consulting, design, implementation, and support of network projects. Expert abilities in Security, LAN, and WAN networking. Proven project management experience. Professional image and mannerisms. Proven experience designing and implementing Cisco IP network and security solutions.
Ability to work closely in a collaborative team environment. Ability to construct accurate and descriptive professional documentation related to customer projects.
Assists with VoIP implementations (Mitel, Cisco Call Manager). Hardware exposure includes: Cisco ISR routers 1800, 2800, 3800, ASA5510, Pix 515, 525, Cisco 3750, 3560, 2950 switches.
eBGP, iBGP, EIGRP, OSPF, DHCP, DNS, Solarwinds, HP Openview, QoS (DiffServ), Policy-based routing, route-maps, ACLs, CCNA 640-801 (925). Director of I,. T - Directs I/T operations including computer operations, technical support, systems analysis and programming.
May also direct database management, telecommunications, I/T training and microcomputer technology. Establishes technical priorities, standards, and procedures. Ensures sufficient systems capacity for organizational needs.
This is an Executive level position reporting to the Chief Operating Officer. Also performs Principal Network Analyst and Network Security/Analyst functions.
Network Manager/Senior Cisco Engineer, Network Security. Currently administer BCBSMT's Sniffer, Wild Packets, and Fluke Optiview protocol analyzers, Cisco PIX Firewalls, Cisco Switch/Router fabric, IP backbone network infrastructure and remote frame-relay/VPN network, DNS/DHCP/WINS, Microsoft Windows 2000, 2003 Server, Microsoft Workstations, ISS Security scanner, and VPN (client and site-to-site). GRE, IPSec, QoS utilized for VPN site-to-site tunnels. HP Openview NNM Administrator. CCNA 640-801 (925) - 100% in troubleshooting section. 1st line Manager,. Operational support of all Distributed Computing systems for Helena, Montana.
Isolate trouble, repair, resolve and/or coordinate resolution with network, vendor, and or application developers. Maintain system hardware and software including PCs, LANS, IWS, DMP, UNIX, Microsoft and miscellaneous file servers and communication servers, X-terminals and Microsoft workstations (600+). Install, load, backup, document, and track system and application software. Assist users and on-site support personnel when required. Manage and maintain trouble reporting data, configurations, backup media, and user profiles and directories.
Maintain inventory of components, parts and spares. Data Communications Systems: Network Planning & Design Alternatives, Network Management, Administration, Trends in Data Communications, Network Diagnostic & Monitoring Considerations, Network Topology & Optimization, Functional Network Subsystem Relationships, Common Carrier Offerings, The Communications Industry, Value Added Services, Tariffs. University of Montana, College of Technology (Helena, MT): Member of the 2003, 2004 Curriculum Advisory Committee. Provided overview of IBM's Tivoli Network Management System (Netview for AIX) to University Information Technology students. University of Montana, College of Technology (Missoula, MT): Provided a Network Career path overview via WebEx to 1st year networking students (2010). Provided seminar on Information Technology (OSI Model) to the Missoula County School District I/T Professionals. Formed Cisco Systems User Group in Helena.
Cisco Networkers (2001, 2002, 2004, 2007, 2011, 2015) SANs Institute 2003 (http://www.sans.org/). Degrees. MBA Certificate Program: Professional, 11/2006 Professional, 6/1985 Data Communications Systems: Network Planning & Design Alternatives, Network Management, Administration, Trends in Data Communications, Network Diagnostic & Monitoring Considerations, Network Topology & Optimization, Functional Network Subsystem Relationships, Common Carrier Offerings, The Communications Industry, Value Added Services, Tariffs.
1/1983 - 1/2008, Personal Training Plan, Missoula, MT.Professional (1000+ hours).Principals of Management, Project Management Skills, Human Relations in Business, Cisco CCNA, 640-801(925), 640-802, CCNP classes (QoS, switching/routing), IBM Certified AIX/Unix System Administrator, Building Cisco Multi-Layered Switched Networks: Management Information Systems, 6/1979.
This is done with the following command: copy usbflash0:c3750e-universalk9-mz.122-58.SE2.bin flash: This will copy the.bin file on the USB into the flash memory of the switch. If you do a 'sh flash:' on the switch, you will see both of them listed in there.
Directory of flash:/ 2 -rwx 7728 Jan 16 2014 14:22:00 -06:00 vlan.dat 3 -rwx 2072 Feb 13 2014 07:58:36 -06:00 multiple-fs 461 -rwx 57686 Feb 13 2014 07:58:36 -06:00 config.text 4 -rwx 5309 Feb 13 2014 07:58:36 -06:00 private-config.text 6 drwx 512 Feb 28 1993 18:10:34 -06:00 c3750e-universalk9-mz.122-55.SE2 6 drwx 512 Feb 12 2014 18:10:34 -06:00 c3750e-universalk9-mz.122-58.SE2. Very straightforward tutorial.
Cisco has good documentation, but sometimes it is 'too much' and we all know we don't have time for that. One point of note, Step 4 seems to be missing some text in the command, at least for the 3650. You have: switch#(config)boot system c3750e-universalk9-mz.122-58.SE2.bin It should be: switch#(config)boot system flash:c3750e-universalk9-mz.122-58.SE2.bin Without specifying the flash: directory you will get a 'File system with suffix not allowed error: Thanks again!
My colleagues and I are using this method to swap out the OS on about nine hundred 3850s in the span of a week. While the method itself works, we've been having hit or miss luck with the flash drive hanging up during the copy process and getting errors upon plugging the flash drive into the USB port, switch wants to run fcsk on it each time. I was curious - can anyone can recommend a brand/size of flash drive that works reliably without failures or errors upon plugging in to the USB port? We've had some success with PNY, but just say no to SanDisk when it comes to this type of work - the 16/32GB Cruzer Glides have been worthless - you get what you pay for I guess.
Thanks for your feedback!
This document describes the procedure to upgrade the software image on the Cisco Catalyst switch Layer 3 (L3) modules. Cisco recommends that you have knowledge of these topics:. TFTP and how to transfer files with this protocol. An understanding of how to set up a computer to be an TFTP server.
The Cisco IOS ® Software image downloaded onto the workstation that acts as the TFTP server prior to actual image installation. This document is not restricted to specific software and hardware versions. Refer to for more information on document conventions.
This document describes these L3 modules:. Catalyst 4500/4000 4232-L3 module. Catalyst 5500/5000 Route Switch Module (RSM). Catalyst 6500/6000 Multilayer Switch Module (MSM). Catalyst 6500/6000 Mutilayer Switch Feature Card (MSFC). Catalyst 6500/6000 Mutilayer Switch Feature Card 2 (MSFC2) Note: Each of these modules is similar with respect to the upgrade procedure. The same upgrade procedure is generally applicable.
This document uses examples from the upgrade of the MSFC2 on the Catalyst 6500/6000. If there are differences in procedure, each subsection of the upgrade describes the differences. This document does not describe the upgrade of the Catalyst 5500/5000 Route Switch Feature Card (RSFC). For information on Catalyst 5500/5000 RSFC upgrades, refer to the section of the document.
There are multiple ways to achieve the upgrade. The procedure in this document discusses the TFTP upgrade only. On certain platforms, such as the Catalyst 6500/6000 MSFC, there are other ways to upgrade, including the use of Flash PC Cards. For those options, refer to the appropriate configuration guide from this list:.
Catalyst 4500/4000 4232-L3 Module—. Catalyst 5500/5000 RSM—. Catalyst 6500/6000 MSM— Install a TFTP server on a TCP/IP-ready workstation or PC. Once the application is installed, perform a minimal level of configuration. Follow this procedure:.
Configure the TFTP application to operate as a TFTP server (not a TFTP client). Specify the outbound file directory. This is the directory that stores the Cisco software images. (See.) Most TFTP applications provide a setup routine to assist in these configuration tasks.
Cisco 3750 Software Upgrade
Note: You can use TFTP to transfer software image files from a PC to the device. This document uses output from the Cisco TFTP Server application. Cisco has discontinued this application and no longer supports it. If you do not have a TFTP server, obtain any third-party TFTP server application from another source. If the Cisco TFTP server is used, disable the logging function to prevent excessive logs that can disrupt the TFTP process. To disable logging on the Cisco TFTP server, choose View Menu Options, uncheck Enable Logging, and click OK.
Les chroniques de spiderwick telecharger. A valid Cisco IOS Software image for the router is necessary. Make sure that the image supports the hardware and software features, and that the router has enough memory to run it. To determine hardware and software features, refer to the specific platform release notes:. Catalyst 4500/4000 4232-L3 Module—. Catalyst 5500/5000 RSM—. Catalyst 6500/6000 MSM—. Catalyst 6500/6000 MSFC— If you do not yet have a Cisco IOS Software image, refer to these documents for specific platform images:.
Catalyst 4500/4000 4232-L3 images— ( customers only). Catalyst 5500/5000 RSM images— ( customers only). Catalyst 6500/6000 MSM/MSFC images— ( customers only) Now a TFTP server is installed, and there is a valid Cisco IOS Software image. When the image in any device is upgraded, have a console connection into the device so that access to the device is possible if a problem develops. A console connection is different than a Telnet session.
A console connection provides information upon system boot. Telnet is a TCP/IP method, but a console connection is a physical connection. (A console connection can also be virtual, through the backplane on the Catalyst 6500/6000 series.) For each platform, there are different methods to console into the L3 module. On this platform, physically plug a console cable into the 4232-L3 module.
For more information, refer to the section of. For details on how to connect to the console port on the RSM, refer to the section of. On this platform, there is a console port on the module.
For more details on the console connection, refer to. The Catalyst 6500/6000 MSFC is different than the other physical modules because the MSFC resides on a daughter card within the Supervisor Engine. The MSFC is similar to the Catalyst 5500/5000 RSFC, which also resides on the Supervisor Engine.
The best method to use is to physically connect your terminal to the console port of the Supervisor Engine. Next, gain executive mode (enable) access. Afterward,you can go into the virtual console mode if the switch console command is issued. For more information on this command, refer to.
For more information on console ports and cables in general, refer to. Follow this procedure to upgrade the L3 module:.
Provide TCP/IP connectivity to the L3 module. Copy the image into the L3 module through the TFTP. Set boot statements to load the new image upon startup. Reboot the L3 module to load the new image. Note: For each L3 module, the procedure is similar and, generally, the same procedure applies. When differences or specifics apply to each L3 module, there are notes after each step.
The L3 module has the ability to receive new Cisco IOS images through the TFTP. To use TFTP with the image, you must ensure that the TFTP server (the computer that runs TFTP server software) can reach the L3 engine through TCP/IP. If you are able to ping the computer from the command-line interface (CLI) of the L3 module, you have successfully completed this step. Setup of the L3 engine for IP connectivity is beyond the scope of this document. To configure IP connectivity for each specific L3 module, refer to:. Catalyst 4500/4000 4232-L3 module— For specific notes on how to gain IP connectivity for upgrades, refer to the and sections of the document.
Catalyst 5500/5000 RSM—. Catalyst 6500/6000 MSFC—. Verify Free Space on the Bootflash At this point, you need to verify that you have enough space in the bootflash to copy the new image. If there is not enough room, you have to delete some files to make space. In some situations, if the image is very large, you must delete the current image in the bootflash. On the MSFC, this deletion can be made safely if you also have the boot image in the bootflash.
You use the boot image if the main image is corrupt or not available. Note: The main image is the full feature set Cisco IOS image, whereas the boot image is essentially a scaled-down version of the main image. The boot image has limited sub-IP functionality with the intent to provide TFTP capabilities. To determine the amount of free space and whether there is a boot image in the bootflash, issue the command.
Example: In this example, the bootflash has 1,265,440 bytes free, and there is a boot image present (c6msfc2- boot-mz.121-6.E1). The word 'boot' in the file name indicates a boot image. C-MSFC15# dir bootflash: Directory of bootflash:/ 1 -rw- 1667488 Apr 20 2001 20:56:41 c6msfc2-boot-mz.121-6.E1 2 -rw- 12269412 Feb 05 2002 18:08:32 c6msfc2-jsv-mz.121-8a.E2 15204352 bytes total ( 1265440 bytes free) Note: The Catalyst 4500/4000 4232-L3 module does not have boot image functionality. However, you are likely to find adequate space on the bootflash for the image. Also, as long as you do not reload the device, the module continues to function correctly. The module continues to work because the image is loaded into the DRAM upon boot and does not rely on the bootflash image once the system is up.
If you find that there is not enough space, you can delete the file. The command deletes the file. Example: c-MSFC15# delete bootflash:c6msfc2-jsv-mz.121-8a.E2 Delete filename c6msfc2-jsv-mz.121-8a.E2?
C6msfc2-jsv-mz.121-8a.E2 Delete bootflash:c6msfc2-jsv-mz.121-8a.E2? confirm y c-MSFC15# The file is removed once it is deleted and squeezed. Note: If the image size is more than the memory size of the bootflash, you can use an external flash drive (Disk0). Copy the Image into Bootflash At this stage, you have IP connectivity and can ping between the computer that acts as a TFTP server and the L3 module. Now, copy the image into the bootflash. If you cannot ping between devices, see the section of this document.
Step 1 provides appropriate links for IP connectivity. At the enable prompt, issue this command to copy from the TFTP server to your bootflash: c-MSFC15# copy tftp bootflash You see a prompt with this information: Address or name of remote host ? 172.16.84.119 Address or name of remote host is the IP address of the TFTP server. The ping test in confirms the IP.
Source filename ? C6msfc2-jsv-mz.121-8a.E5 Source filename is the image file name. The file must be in your TFTP directory path so that the TFTP server can locate the file. Note: The file name must be spelled exactly the same, which includes any capitalization.
Destination filename flash? C6msfc2-jsv-mz.121-8a.E5 Destination filename is the file name of the image that you intend to save onto the bootflash. Use of the same file name as the source name ensures that, in the future, you can correctly identify the software features and version run. If you do not have enough space in the bootflash, Cisco IOS Software asks if you want to delete the current image to make room for the new image. The transfer can take some time, which depends on the speed of the connection and the size of the image. During the transfer, you see exclamation marks ('!'
) for good packets. The appearance of periods ('.' ) indicates that the link has taken some hits.
Investigate the problem afterward. A successful TFTP transfer reports an OK, along with the number of bytes transferred. If you do not receive an OK, investigate IP connectivity and possible TFTP server issues. Example: c-MSFC15# copy tftp bootflash Address or name of remote host ? 172.16.84.119 Source filename ? C6msfc2-jsv-mz.121-8a.E5 Destination filename flash? C6msfc2-jsv-mz.121-8a.E5 Accessing tftp://172.16.84.119/c6msfc2-jsv-mz.121-8a.E5.
Loading c6msfc2-jsv-mz.121-8a.E5 from 172.16.84.119 (via Vlan1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!- Output suppressed. OK - 1228112 bytes 12269412 bytes copied in 523.852 secs (23459 bytes/sec) c-MSFC15# After you have successfully transferred the file, verify that the file is in the bootflash: Issue the dir device: command to show files that are currently in the bootflash. Example: c-MSFC15# dir bootflash: Directory of bootflash:/ 1 -rw- 1667488 Apr 20 2001 20:56:41 c6msfc2-boot-mz.121-6.E1 2 -rw- 12269412 Feb 05 2002 18:08:32 c6msfc2-jsv-mz.121-8a.E5 Verify that the name and the file size are correct.
After you copy the image through TFTP, you must provide the L3 module with the name of the image to load upon boot. Check Current Boot Statements The image is now in the bootflash. You must set the L3 module to boot the new image. By default, the L3 module boots the first available image. (An absence of boot commands in the configuration enables the default.) There is a possibility that you have a previous boot statement defined.
There are two ways to determine the current boot parameter settings. Method 1 is to issue the command: Example: c-MSFC15# show config Building configuration. Current configuration: 1625 bytes! Version 12.1 service timestamps debug datetime msec localtime! Hostname c-MSFC15! Boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4 boot bootldr bootflash:c6msfc2-boot-mz.121-6.E1!
Ip subnet-zero! -More- Check to see if the configuration has any commands. The commands appear toward the top of the configuration. How to install bve 4 for windows 7. Method 2 is to issue the command: Example: c-MSFC15# show boot BOOT variable = bootflash:c6msfc2-jsv-mz.121-8a.E4,1 CONFIGFILE variable = BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-6.E1 Configuration register is 0x102 Check to see if the boot statements appear under the parameter BOOT variable.
If you have boot entries, you must remove them from the configuration. For more information on the removal of boot entries, see the Remove Previous Boot Statements section of this document. Remove Previous Boot Statements To remove the statements, enter into configuration terminal mode. From the configuration mode, you can negate any command with the issue of no in front of each boot statement. This example illustrates the removal of a boot statement: Example: c-MSFC15# show config Building configuration. Current configuration: 1625 bytes! Version 12.1 service timestamps debug datetime msec localtime!
Hostname c-MSFC15! Boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4 boot bootldr bootflash:c6msfc2-boot-mz.121-6.E1! Ip subnet-zero! -More- At this point, you have the boot statement that you want to remove. The statement to remove is boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4. C-MSFC15# configure terminal Enter configuration commands, one per line.
End with CNTL/Z. C-MSFC15(config)# no boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4 c-MSFC15(config)# ^Z c-MSFC15# Verify that you have removed the command: Example: c-MSFC15# show config Building configuration. Current configuration: 1625 bytes! Version 12.1 service timestamps debug datetime msec localtime!
Hostname c-MSFC15! Boot bootldr bootflash:c6msfc2-boot-mz.121-6.E1!- Note: Now the boot statement no longer appears in the configuration.! Ip subnet-zero! -More- Once the commands are removed, you can issue the command or the command to save the configuration to NVRAM.
Example: c-MSFC15# write memory 3d01h:%SYS-5-CONFIGI: Configured from console by vty0 (127.0.0.11) Building configuration. C-MSFC15# Set the New Boot Statement You must add the boot statement to indicate which image the L3 module needs to load.
Issue this command to set the boot parameter:. Note: In this command, imagename is the name of the new Cisco IOS image.
Example: c-MSFC15# configure terminal Enter configuration commands, one per line. End with CNTL/Z. C-MSFC15(config)# boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E5 c-MSFC15(config)# ^Z c-MSFC15# write memory 3d01h:%SYS-5-CONFIGI: Configured from console by vty0 (127.0.0.11) Building configuration.
C-MSFC15# Be sure to verify that the config-register value is set to 0x2102 with the issue of the show boot command. If config-register is set to a different value, you can change it with the issue of this command in configuration mode:. config-register 0x value Example: c-MSFC15# configure terminal Enter configuration commands, one per line. End with CNTL/Z. C-MSFC15(config)# config-register 0x2102 c-MSFC15(config)# ^Z c-MSFC15# write memory Verify the boot parameters with the issue of the show boot command: c-MSFC15# show boot BOOT variable = bootflash:c6msfc2-jsv-mz.121-8a.E5,1 CONFIGFILE variable = BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-6.E1 Configuration register is 0x102 ( will be 0x2102 at next reload) c-MSFC15# After you change the config-register, the change takes place at the next reload, as the example shows. For the L3 module to run the new Cisco IOS image, you must reload the module.
Make sure that you have saved the configuration. Issue the copy run start command or the write memory to save the configuration. Example: c-MSFC15# write memory 3d01h:%SYS-5-CONFIGI: Configured from console by vty0 (127.0.0.11) Building configuration. C-MSFC15# Issue the reload command to soft reset the L3 module, as this example shows: Example: c-MSFC15# reload Proceed with reload?
confirm 00:00:40:%SYS-5-RELOAD: Reload requested System Bootstrap, Version 12.1(2r)E, RELEASE SOFTWARE (fc1) Copyright (c) 20 0 0 by cisco Systems, Inc. Cat6k-MSFC2 platform with 131072 Kbytes of main memory Self decompressing the image: ######################################################### OK%SYS-6-BOOTMESSAGES: Messages above this line are from the boot loader. Self decompressing the image: ################################################################################### OK Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. Cisco Systems, Inc. 170 West Tasman Drive San Jose, California Cisco Internetwork Operating System Software IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY DEPLOYMENT RELEASE SOFTWARE (fc2) TAC Support: Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 22-Oct-01 21:51 by eaarmas Image text-base: 0x40008980, data-base: 0x418D2000 cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory. Processor board ID SAD042106RN R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache Last reset from power-on Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software. 509K bytes of non-volatile configuration memory. 16384K bytes of Flash internal SIMM (Sector size 512K).
Press RETURN to get started! 00:00:02: Currently running ROMMON from S (Gold) region 00:00:04:%SYS-5-CONFIGI: Configured from memory by console 00:00:04:%SYS-5-RESTART: System restarted - Cisco Internetwork Operating System Software IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY DEPLOYMENT RELEASE SOFTWARE (fc2) TAC Support: Copyright (c) 1986-2001 by cisco Systems, Inc. Compiled Mon 22-Oct-01 21:51 by eaarmas 00:00:06:%SCP-5-ONLINE: Module online 00:00:09:%LINK-3-UPDOWN: Interface Vlan1, changed state to up 00:00:10:%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up c-MSFC15 After the L3 module comes up, make sure that you run the new version of code.
Issue the command to check. Example: c-MSFC15# show version Cisco Internetwork Operating System Software IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY DEPLOYMENT RELEASE SOFTWARE (fc2)!- Note: Now the MSFC runs the new software image. TAC Support: Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 22-Oct-01 21:51 by eaarmas Image text-base: 0x40008980, data-base: 0x418D2000 ROM: System Bootstrap, Version 12.1(2r)E, RELEASE SOFTWARE (fc1) BOOTFLASH: MSFC2 Software (C6MSFC2-BOOT-M), Version 12.1(6)E1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) c-MSFC15 uptime is 0 minutes System returned to ROM by power-on Running default software cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory. Processor board ID SAD042106RN R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache Last reset from power-on Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software.
4 Virtual Ethernet/IEEE 802.3 interface(s) 509K bytes of non-volatile configuration memory. 16384K bytes of Flash internal SIMM (Sector size 512K). Configuration register is 0x2102 c-MSFC15# Verify that the version ( 12.1(8a)E5) is correct and that the config-register is set ( 0x2102). The upgrade is complete. Note: If you have dual MSFCs, you must download the image onto the second MSFC bootflash: device. The image does not automatically download to the second MSFC. This requirement is also applies to config-sync mode and Single Router Mode (SRM).
In config-sync mode and SRM, changes in the boot variables automatically propagate to the nondesignated or standby MSFC. To copy an image from bootflash to the bootflash of a nondesignated or standby MSFC, issue the command.
When you run Catalyst OS (CatOS) software on the Supervisor Engine, you can choose to boot the MSFC from an image in the Supervisor Engine slot0 Flash PC Card slot. Your boot system statement refers to the Flash device as sup-slot0. Although there is support for such a boot process, avoid use of it. Use this boot process only as a temporary step, such as when you test an image. Be aware of Cisco bug ID ( customers only). You cannot issue commands such as the dir sup-slot0: command or the show sup-slot0: commands from the MSFC because the MSFC does not consider slot0 to be a local file system.
If you specify sup-slot0 as the source of the operating system image, the switch transfers the file through TFTP across the internal switching bus between the sc0 interface on the Supervisor Engine and a special loopback IP address on the MSFC. From the MSFC CLI, you can issue this command: FIRE-MSFC1# copy tftp?