Conversion on Supervisor Engine 32

This section uses this terminology:

   *

     Switch Processor (SP)—Refers to the switch component of the system or Supervisor Engine.
   *

     Route Processor (RP)—Refers to the router component of the system or MSFC2A.

Note: The images that this document uses are for example purposes only. Replace the images with the images that you use in your switch environment. Make sure to refer to the Catalyst 6500 Series Release Notes for memory and ROMmon requirements.

Step 1

Establish a console connection to the SP.

Log your console session as a best practice. The log enables you to capture a record of the session and compare the log to the steps in this document, if you need to troubleshoot. For example, in HyperTerminal, choose Transfer > Capture Text in order to log a console session. Refer to Connecting a Terminal to the Console Port on Catalyst Switches for more information.

Step 2

Back up the CatOS configuration from the Supervisor Engine and the Cisco IOS Software configuration from the MSFC2A.

You need to reconfigure the switch after you convert to Cisco IOS Software as the system software because the conversion process loses the configuration. If you back up the files, they can serve as a reference after the conversion or as a backup if you decide to convert back to CatOS. Issue the copy config tftp command on the Supervisor Engine and the copy start tftp command on the MSFC2A in order to back up the configurations.

Refer to Managing Software Images and Working with Configuration Files on Catalyst Switches for more information on how to use the copy config tftp and copy start tftp commands to back up configuration files.

Step 3

Verify that the Cisco IOS Software image (s3223*) is available on the SP bootdisk or a CompactFlash card in disk0.

Issue the dir command in order to verify the location of the Cisco IOS Software image (s3223*).

   Console> (enable) dir bootdisk:
   -#- -length- -----date/time------ name
     1 13389508 Oct 11 2005 15:46:45 s3223-adventerprisek9_wan-mz.122-18.SXF.bin

   !--- This is the SP bootdisk and the location for the current
   !--- CatOS software version that runs on the SP.
       
   245784576 bytes available (47114308 bytes used)

   Console> (enable) dir disk0:
     2   -rw-  47114308   Oct 11 2005 14:33:05 s3223-adventerprisek9_wan-mz.122-18.SXF.bin

   !--- This is the CompactFlash Type II device called disk0:.
   !--- This is the Cisco IOS Software image (s3223*) release for this conversion.

   95641600 bytes available (47114308 bytes used)
   Console> (enable)

If the Cisco IOS Software image (s3223*) is missing from either bootdisk: or disk0:, download the image. Step 4 provides this procedure. If the image is present, go to Step 5. Step 4 (Optional)

Complete this step only if the Cisco IOS Software image (s3223*) is missing from either the SP bootdisk or the PC card in slot0. See Step 3 in order to determine if you need to complete this step.

Issue the copy tftp bootdisk: command or the copy tftp disk0: command in order to download the image to either the SP bootdisk or to one of the flash cards.

Note: You might need to format the CompactFlash if it has never been used before or if it was formatted with the Cisco IOS Software algorithm. Issue the format disk0: command in order to format CompactFlash on a Supervisor Engine 32.

Note: You can free up space as necessary on either of these devices. Issue the delete bootdisk: command or the delete disk0:filename command in order to delete the file. You do not need to issue a command in order to erase deleted files from the device.

   Console> (enable) copy tftp disk0:
   IP address or name of remote host []? 10.1.1.2
   Name of file to copy from []?s3223-adventerprisek9_wan-mz.122-18.SXF.bin
   128626688 bytes available on device disk0, proceed (y/n) [n]? y
   /
   File has been copied successfully.
   Console> (enable)

   !--- Verify the image location.

   Console> (enable) dir disk0:
         2   -rw-  32983632    Oct 04 2005 19:33:05 s3223-adventerprisek9_wan-mz.122-18.SXF.
    bin
   95641600 bytes available (32985088 bytes used)
   Console> (enable)

Step 5

Issue either the switch console or the session module command in order to access the RP.

   Console> (enable) switch console
   Trying Router-15...
   Connected to Router-15.
   Type ^C^C^C to switch back...
   Router>

   !--- Issue the enable command in order to enter privileged EXEC mode.

   Router>enable
   Router#

Step 6

Change the configuration register setting in order to put the switch into ROMmon on reload.

Issue the show bootvar command in order to check the current configuration register setting.

   Router#show bootvar
   BOOT variable = bootflash: c6msfc2a-adventerprisek9_wan-mz.122-18.SXF.bin,1
   CONFIG_FILE variable does not exist
   BOOTLDR variable does not exist
   Configuration register is 0x2102

   !--- This is the current configuration register value.

   Router#
   Router#configure terminal
   Enter configuration commands, one per line. End with CNTL/Z.
   Router(config)#config-register 0x0

   !--- This changes the configuration register value of the RP.

   Router(config)#end
   Router#

Verify the new configuration register setting.

   Router#show bootvar
   BOOT variable = bootflash: c6msfc2a-adventerprisek9_wan-mz.122-18.SXF.bin,1
   CONFIG_FILE variable does not exist
   BOOTLDR variable does not exist
   Configuration register is 0x2102(will be 0x0 at next reload)
   Router#

Then, reload the router.

   Router#reload

   !--- Press Enter or Return.
   !--- This reloads the router.

   System configuration has been modified. Save? [yes/no]: no

   !--- Press Enter or Return.

   Proceed with reload? [confirm]

   !--- Press Enter or Return.

   System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE (fc1)
   Technical Support: http://www.cisco.com/techsupport
   Copyright (c) 2004 by cisco Systems, Inc.
   Cat6k-MSFC2A platform with 524288 Kbytes of main memory

   !--- After this step is complete, the switch enters into RP ROMmon.

   rommon 1 >

Step 7

Erase NVRAM for the CatOS system software region in order to prevent any corrupted files from passing during this conversion. Then, change the configuration register back to the default.

   rommon 1 > priv

   !--- Press Enter or Return.
   !--- You enter ROMmon privileged mode.
   !--- This output displays:

   You now have access to the full set of monitor commands.
   Warning: some commands allow you to destroy your
   configuration and/or system images and could render
   the machine unbootable.

   !--- Issue the fill command from ROMmon privileged mode.

   rommon 2 > fill

   !--- Press Enter or Return.
   !--- Be sure to enter these parameters exactly as they appear here:

   Enter in hex the start address [0x0]: be000000

   !--- Press Enter or Return.

   Enter in hex the test size or length in bytes [0x0]: 80000

   !--- Press Enter or Return.

   Enter in hex the pattern to be written [0x0]: ffff

   !--- Press Enter or Return.

   Enter the operation size 'l'ong, 'w'ord, or 'b'yte []: l

   !--- Press Enter or Return.
   !--- After the NVRAM erase is complete, issue the reset command.

   rommon 3 > reset

   !--- Press Enter or Return.

   rommon 1 > confreg 0x2102

   !--- Press Enter or Return.

Step 8

In order to go back to the SP, press Ctrl-C three times:

Note: If you issued the session module command in order to access the RP, you must issue the exit command instead of Ctrl-C.

   !--- Press Ctrl-C three times.

   rommon 2 > ^C
   rommon 2 > ^C
   rommon 2 > ^C
   Console> (enable)

   !--- This is the SP console prompt.
    

Step 9

Change the configuration register setting on the SP so that the switch does not boot the CatOS image and goes to ROMmon.

   Console> (enable) set boot config-register 0x0
   Configuration register is 0x0
   ignore-config: disabled
   auto-config: non-recurring, overwrite, sync disabled
   console baud: 9600
   boot: the ROM monitor
   Console> (enable)

   !--- Verify the settings.

   Console> (enable) show boot
   BOOT variable = bootdisk:cat6000-sup32pfc3k8.8-5-1.bin,1;
   CONFIG_FILE variable = bootdisk:switch.cfg

   Configuration register is 0x0
   ignore-config: disabled
   auto-config: non-recurring, overwrite, sync disabled
   ROMmon console baud: 9600
   boot: image specified by the boot system commands

   Image auto sync is enabled
   Image auto sync timer is 120 seconds

Step 10

Reset the switch so that it goes into ROMmon:

   Console> (enable) reset
   This command will reset the system.
   Do you want to continue (y/n) [n]? y
   2005 Oct 14 17:21:18 %SYS-5-SYS_RESET:System reset from Console//
   Powering OFF all existing linecards
   2005 Oct 14 17:21:18 %ETHC-5-PORTFROMSTP:Port 2/1 left bridge port 2/1
   Console> (enable)
   System Bootstrap, Version 12.2(18r)SX2

   !--- This is the SP ROMmon image release.

   Copyright (c) 2004 by cisco Systems, Inc.
   Cat6k-Sup32 platform with 1048576 Kbytes of main memory

   !--- After this message, the router goes to SP ROMmon.

   rommon 1 >

Step 11

Boot the switch with the Cisco IOS Software image (s3223*).

Issue the dir bootdisk: command or the dir disk0: command. The command you use depends on the device to which you previously downloaded the Cisco IOS Software image (s3223*). Then, issue the boot bootdisk: command or the boot disk0:filename command in order to start the bootup sequence.

   rommon 1 > dir disk0:
   Directory of disk0:
       2      47114308  -rw-     s3223-adventerprisek9_wan-mz.122-18.SXF.bin

   !--- The Cisco IOS Software image (s3223*) is on disk0: in this case.
   !--- This is the device from which the image boots in this procedure.

   rommon 2 > boot disk0:s3223-adventerprisek9_wan-mz.122-18.SXF.bin
   Self decompressing the image : 
   ##################################################################################
   ##################################################################################
   ######################################################### [OK]

   !--- Output suppressed.

   System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE (fc1)
   Technical Support: http://www.cisco.com/techsupport
   Copyright (c) 2004 by cisco Systems, Inc.
   Cat6k-MSFC2A platform with 524288 Kbytes of main memory
   Download Start
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   Download Completed! Booting the image.
   Self decompressing the image : 
   ######################################################################
   #################################################### [OK]

   !--- Output suppressed.

   Press RETURN to get started!

   !--- Output suppressed.

   Router>

Step 12

At this point, the Cisco IOS Software image (3223*) has successfully booted, but the Supervisor Engine Flash devices are still formatted with the previous CatOS algorithm. Therefore, Cisco IOS Software cannot correctly write to sup-bootdisk: or disk0:. You need to reformat these Flash devices and replace the images that are on the Flash devices.

Issue the format command in order to format the Flash devices.

   Router#format sup-bootdisk:
   Format operation may take a while. Continue? [confirm]

   !--- Press Enter or Return.

   Format operation will destroy all data in "sup-bootdisk:".  Continue? [confirm]

   !--- Press Enter or Return.

   Format of sup-bootflash complete
   Router#

   Router#format disk0:

   !--- Format the CompactFlash card in disk1: as well, if you have one.

   Format operation may take a while. Continue? [confirm]

   !--- Press Enter or Return.

   Format operation will destroy all data in "disk0:".  Continue? [confirm]

   !--- Press Enter or Return.

   Format: Drive communication & 1st Sector Write OK...
   Writing Monlib sectors...................
   ...........................................................................
   Monlib write complete
   Format: All system sectors written. OK...
   Format: Total sectors in formatted partition: 251616
   Format: Total bytes in formatted partition: 128827392
   Format: Operation completed successfully.
   Format of disk0 complete
   Router#

Step 13

When you formatted the Supervisor Engine Flash devices in Step 12, the Cisco IOS Software image (s3223*) used to boot the Supervisor Engine, as well as all data on the device, is erased. You need to recopy the Cisco IOS Software image (s3223*).

Note: Remember that the conversion lost the configuration. You need to configure an IP address and possibly a static or dynamic routing in order to reestablish connectivity to your TFTP server. Verify that you can ping your TFTP server from the switch.

Issue the copy tftp command in order to copy the Cisco IOS Software image (s3223*) to either the sup-bootdisk: or the disk0: Flash devices.

   Router#copy tftp sup-bootdisk:

   !--- The Cisco IOS Software image (s3223*) copies to SP bootflash (sup-bootdisk:) 
   !--- in this case.

   Address or name of remote host []? 10.1.1.2
   Source filename []?s3223-adventerprisek9_wan-mz.122-18.SXF.bin
   Destination filename [s3223-adventerprisek9_wan-mz.122-18.SXF.bin]?
   Accessing tftp://10.1.1.2/s3223-adventerprisek9_wan-mz.122-18.SXF.bin...
   Loading s3223-adventerprisek9_wan-mz.122-18.SXF.bin (via FastEthernet3/1): !!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

   !--- Output suppressed.

   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   [OK - 32983632 bytes]
   32983632 bytes copied in 382.524 secs (86226 bytes/sec)
   Verifying compressed IOS image checksum...
   Verified compressed IOS image checksum for sup-bootdisk:/s3223-adventerprisek9_wan-mz.
    122-18.SXF.bin 
   Router#

   !--- Verify the image location in SP bootflash.

   Router#dir sup-bootdisk:
   Directory of sup-bootdisk:/
    
       1  -rw-    47114308  Sep 30 2005 00:58:36 +00:00  s3223-adventerprisek9_wan-mz.
    122-18.SXF.bin
    
   255954944 bytes total (208837504 bytes free)
   Router#
   Router#

Step 14

Set the boot variable to boot from the Cisco IOS Software image (s3223*) in either sup-bootdisk: or disk0:.

   !--- Check the current boot variable settings.

   Router#show bootvar
   BOOT variable = bootflash: c6msfc2a-adventerprisek9_wan-mz.122-18.SXF.bin,1

   !--- The BOOT variable incorrectly points to an old MSFC2A image.

   CONFIG_FILE variable does not exist
   BOOTLDR variable does not exist
   Configuration register is 0x2102
   Standby is not up.
   Router#

   !--- Set the boot variable to boot the Cisco IOS Software image (s3223*).

   Router#configure terminal
   Enter configuration commands, one per line.  End with CNTL/Z.
   Router(config)#boot system flash sup-bootdisk: s3223-adventerprisek9_wan-mz.
    122-18.SXF.bin

   !--- This command should be on one line.

   Router(config)#end

   !--- Save the changes.

   Router#write memory
   Building configuration...
   [OK]
   Router#

Step 15

Change the configuration register of the SP from 0x0 to 0x2102. Otherwise, upon reload, the router ends up in SP ROMmon. Issue the show bootvar command again.

   Router#show bootvar
   BOOT variable = sup-bootdisk: s3223-adventerprisek9_wan-mz.122-18.SXF.bin,1
   CONFIG_FILE variable does not exist
   BOOTLDR variable =
   Configuration register is 0x2102

This output seems to show that all the variables are set and that you can automatically boot the switch. However, if you reload the router at this point, you end up in SP ROMmon because the configuration register value for the SP that you set in Step 9 is still 0x0. Issue the remote command switch show bootvar command in order to verify this statement. The command displays the current environment variable settings on the SP.

   Router# #remote command switch show bootvar
   BOOT variable =
   CONFIG_FILE variable does not exist
   BOOTLDR variable does not exist
   Configuration register is 0x0

Issue this set of commands on the RP in order to change the configuration register settings on the SP:

   !--- Set the configuration register.

   Router#configure terminal
   Enter configuration commands, one per line.  End with CNTL/Z.
   Router(config)#config-register 0x2102
   Router(config)#end

   !--- Save the changes.

   Router#write memory
   Building configuration...
   [OK]

   !--- Verify the settings on the SP.

   Router# #remote command switch show bootvar
   BOOT variable = 
   CONFIG_FILE variable =
   BOOTLDR variable =
   Configuration register is 0x0 (will be 0x2102 at next reload)

Step 16

Reload the switch.

   Router#reload
   Proceed with reload? [confirm]

   !--- Output suppressed.

Troubleshoot System Software Conversion

This section describes how to troubleshoot common issues that occur during the system software conversion. Unable to Boot with Cisco IOS Software when User Converts from CatOS to Cisco IOS

If you try to boot Cisco IOS Software from disk0 or slot0 during the conversion process, you can receive an error message similar to this:

• • • TLB (Store) Exception ***

Access address = 0x10000403 PC = 0x8000fd60, Cause = 0xc, Status Reg = 0x30419003

monitor: command "boot" aborted due to exception

This error message can be hardware or software related, and can result in a boot loop or the switch getting stuck in ROM Monitor (ROMmon) mode.

Complete these steps in order to resolve this issue:

  1.

This issue can be caused by a software image with a bad checksum. Download again the Cisco IOS Software image from the TFTP server.

  2.

If the download does not resolve the issue, format the Flash card, and download again the Cisco IOS Software image.

Refer to PCMCIA Filesystem Compatibility Matrix and Filesystem Information for information on how to erase the Flash.

  3.

This issue can also be due to a hardware fault, but the error message does not indicate which hardware component causes the problem. Try to boot the Cisco IOS Software from another Flash card.

Standby Supervisor Engine Module Is Not On Line or Status Indicates unknown

This section outlines common reasons that the standby Supervisor Engine module does not come online and how to solve each problem. You can determine that the Supervisor Engine module does not come online in one of these ways:

   *

The output of the show module command shows the status as other or faulty.

   *

The Status LED glows amber in color.

Common Reasons/Solutions

   *

Console in to the standby Supervisor Engine in order to determine if it is in ROMmon mode or in continuous reboot. If the Supervisor Engine is in one of these states, refer to Recovering a Catalyst 6500/6000 Running Cisco IOS System Software from a Corrupted or Missing Boot Loader Image or ROMmon Mode.

Note: If the active and standby Supervisor Engines do not run the same Cisco IOS Software release, the standby can fail to come online. For example, a Supervisor Engine can fail to come online in a situation in which:

         o

The active Supervisor Engine runs Route Processor Redundancy Plus (RPR+) mode. RPR+ mode is available in Cisco IOS Software Release 12.1[11]EX and later.

         o

The standby Supervisor Engine runs a software version where RPR/RPR+ mode is not available, such as Cisco IOS Software Release 12.1[8b]E9.

In this case, the second Supervisor Engine fails to come online because the redundancy mode is enhanced high system availability (EHSA) by default. The standby Supervisor Engine fails to negotiate with the active Supervisor Engine. Make sure both Supervisor Engines run the same Cisco IOS Software level.

This output shows the Supervisor Engine in slot 2 in ROMmon mode. You must console in to the standby Supervisor Engine in order to recover it. Refer to Recovering a Catalyst 6500/6000 Running Cisco IOS System Software from a Corrupted or Missing Boot Loader Image or ROMmon Mode for information on the recovery procedures.

         6513_01#show module
         Mod Ports Card Type                              Model              Serial No.
         --- ----- -------------------------------------- ------------------ -----------
           1    2  Catalyst 6000 supervisor 2 (Active)    WS-X6K-S2U-MSFC2   SAD0628035C
           2    0  Supervisor-Other                       unknown            unknown
           3   16  Pure SFM-mode 16 port 1000mb GBIC      WS-X6816-GBIC      SAL061218K3
           4   16  Pure SFM-mode 16 port 1000mb GBIC      WS-X6816-GBIC      SAL061218K8
           5    0  Switching Fabric Module-136 (Active)   WS-X6500-SFM2      SAD061701YC
           6    1  1 port 10-Gigabit Ethernet Module      WS-X6502-10GE      SAD062003CM

         Mod MAC addresses                       Hw    Fw           Sw           Status
         --- ---------------------------------- ------ ------------ ------------ -------
           1  0001.6416.0342 to 0001.6416.0343   3.9   6.1(3)       7.5(0.6)HUB9 Ok      
           2  0000.0000.0000 to 0000.0000.0000   0.0   Unknown      Unknown      Unknown 
           3  0005.7485.9518 to 0005.7485.9527   1.3   12.1(5r)E1   12.1(13)E3,  Ok      
           4  0005.7485.9548 to 0005.7485.9557   1.3   12.1(5r)E1   12.1(13)E3,  Ok      
           5  0001.0002.0003 to 0001.0002.0003   1.2   6.1(3)       7.5(0.6)HUB9 Ok      
           6  0002.7ec2.95f2 to 0002.7ec2.95f2   1.0   6.3(1)       7.5(0.6)HUB9 Ok      

         Mod Sub-Module                  Model           Serial           Hw     Status 
         --- --------------------------- --------------- --------------- ------- -------
           1 Policy Feature Card 2       WS-F6K-PFC2     SAD062802AV      3.2    Ok     
           1 Cat6k MSFC 2 daughterboard  WS-F6K-MSFC2    SAD062803TX      2.5    Ok     
           3 Distributed Forwarding Card WS-F6K-DFC      SAL06121A19      2.1    Ok     
           4 Distributed Forwarding Card WS-F6K-DFC      SAL06121A46      2.1    Ok     
           6 Distributed Forwarding Card WS-F6K-DFC      SAL06261R0A      2.3    Ok     
           6 10GBASE-LR Serial 1310nm lo WS-G6488        SAD062201BN      1.1    Ok

   *

Make sure that the Supervisor Engine module is properly seated in the backplane connector. Also, make sure that the Supervisor Engine installation screw is completely tightened. Refer to Catalyst 6500 Series Switch Module Installation Note for more information.

   *

In order to identify if the standby Supervisor Engine is faulty, issue the redundancy reload peer command from the active Supervisor Engine. In order to identify any hardware failures, observe the boot sequence through the console to the standby Supervisor Engine.

If the standby Supervisor Engine still does not come online, create a service request with Cisco Technical Support in order to further troubleshoot. When you create the service request, provide the switch output log that you collected and the troubleshooting steps that you performed.

Error: Compressed image checksum is incorrect

If you try to boot Cisco IOS Software during the conversion process, you can receive an error message similar to this:

   Error : compressed image checksum is incorrect 0x64479A4B
           Expected a checksum of 0x72A42935

   *** System received a Software forced crash ***
   signal= 0x17, code= 0x5, context= 0x800267c0
   PC = 0x800200d4, Cause = 0x20, Status Reg = 0x3041c003

This error message can be hardware or software related and can result in a boot loop or the switch getting stuck in ROM Monitor (ROMmon) mode.

  Complete these steps in order to resolve this issue:

1. This issue can be caused by a software image with a bad checksum. Download again the Cisco IOS Software image from the TFTP server.

2.If the download does not resolve the issue, format the Flash card, and download again the Cisco IOS Software image.

Refer to PCMCIA Filesystem Compatibility Matrix and Filesystem Information for information on how to erase the Flash.

3. This issue can also be due to a hardware fault, but the error message does not indicate which hardware component causes the problem. Try to boot the Cisco IOS Software from another Flash card.

Unable to Save Configuration After System Software Coversion

Error messages similar to these can occur soon after the conversion when the write memory command is issued:

   Warning: Attempting to overwrite an NVRAM configuration previously written
   by a different version of the system image.
   Overwrite the previous NVRAM configuration?[confirm]
   startup-config file open failed (Bad device info block)

or

   Warning: Attempting to overwrite an NVRAM configuration previously written
   by a different version of the system image.
   Overwrite the previous NVRAM configuration?[confirm]
   startup-config file open failed (No such device)

In order to resolve the issue, try these options:

   *

     Execute the erase nvram: command, and try to save the configuration.
   *

     Execute the boot config nvram:startup-config command, and try to save the configuration.