VMware Enable SSH (vSphere ESX)

 

VMware Enable SSH KB ID 0000299 

Problem

Should you wish to get SSH (remote secure console) access to your ESX  hosts, you need to do the following.

ESX Version 8 and Newer

ESX Version 6.5 and Newer

ESX version 5 and Newer

ESX version 4.1.0

ESX version 4.0.0 and earlier

ESX version 4.0.0 and earlier

Solution

VMware Enable SSH ESX 8.0

Directly on an ESX Host: If you have a stand-alone ESX Server running version 8.x, Log in via the web console >  Select ‘Host’ > Actions > Services > Enable Secure Shell (SSH).

Via vSphere/vCenter: If you want to enable SSH on an ESX host through the vCenter Web client then, from the ‘hosts and datacentres’ view > Select the Host  > Configure > Services > Locate SSH > Start.

Enable SSH Permanently: Some people don’t want this enabled for security reasons, and in production that makes sense, but on my test network I always have SSH enabled. from the same screen as above with SSH selected > Edit Start-up Policy > Select ‘Start an stop with host” > OK.

VMware Enable SSH 6.5

If you have a stand-alone ESX Server running version 6.5, it’s a lot easier to enable ESX access. Select ‘Host’ > Actions > Service > Enable Secure Shell (SSH). Note: You can also enable the direct console access here.

If you want to enable SSH on an ESX host through the vCenter Web client then, from the ‘hosts and datacenters’ view > Select the Host  > Configure > Security Profile > Scroll down to ‘Services’ > Edit.

Locate ‘SSH > Start > OK.

Once enabled you will see the following warning on the hosts summary page, however, in version 6.5 you can suppress this error.

VMware Enable SSH ESX 5

ESX 5 has a built in firewall, which can have SSH opened in the VI clients, or just as with version 4.1.0 you can enable SSH Locally from the console from troubleshooting options.

Enable Remotely

1. Log into the host with the VI client > Select the host > Configuration > Security Profile > Properties.

2. Locate SSH Server > Tick it > Options > You can either manually start it or set it to start automatically.

3. You will see the following warning to “retrieve” the firewall settings (because you have just changed them) > Select Yes.

Note: Having it running will still cause the “Configuration Issues – SSH for the host has been enabled” nag screen on the summary tab of the host.

VMware Enable SSH ESX 4.0.1

Starting with version 4.0.1 you can enable SSH access from the server console.

1. Go to the normal ESX console > Press F2 > Log in >Troubleshooting Options.

2. Select “Enable Remote Tech support” toggle on and off with {enter} if you want to SSH in the server remotely using PuTTy for example > If you want to log on directly at the console choose “Enable Local Tech Support”.

3. Note: Having it running will still cause the “Configuration Issues – Remote Tech support Mode (SSH) for the host {hostname} has been enabled” nag screen on the summary tab of the host.

Grant SSH Access to ESX 4.0.0 and earlier

1. Go to the normal ESXi console.

2. Press ALT+F1 > the screen will change > Type unsupported {enter} > Note: Nothing will appear on the screen till you hit {enter} > Type in the root password and press {enter}.

3. You now need to edit a config file, the only editor we have is vi (sorry) issue the following command,

[box]vi /etc/inetd.conf[/box]

4. The vi editor will open the file, use the arrow keys to move down to the line that says,

[box]#ssh stream tcp nowait root…[/box]

Press I on the keyboard (that puts the vi editor into insert mode) and delete the hash “#” mark from the beginning of the line.

5 Then, to save the changes press {Esc} > type in :wq {Enter} (that’s write the changes and quit if you’re interested).

6. Enter the following command.

[box]

cat /var/run/inetd.pid

[/box]

It will provide you with a number, (in the example below its 4983, yours will be different).

7. Issue the following command.

[box]

kill -HUP {the number you got from above}

[/box]

8. To get back to the usual ESXi screen and exit command line press ALT+F2.

9. You can now connect with an SSH client like Putty.

 

Related Articles, References, Credits, or External Links

Original Article written: 07/12/11

ESX4 – Grant Root User SSH Access

Thanks to Dave Corrasa for the feedback.

Updating the AnyConnect client for Deployment from the Cisco ASA 5500

KB ID 0000704 

Problem

Your ASA will (by default) update your AnyConnect clients to the latest client software when they connect. However you need to supply the ASA with the updated packages first.

Solution

1. Download the latest AnyConnect client package, from Cisco. The one you want will have a file extension of .pkg

AnyConnect 4

AnyConnect 3

2. Connect to the ASDM > Configuration > Remote Access VPN > Network (Client) access > AnyConnect Client Software > Add.

 

Note: On older versions of the ASDM you will find the option under > Network (Client) access > Advanced > SSL VPN > Client Settings > Add.

3. Select Upload > Browse to the software you downloaded > Select.

 

4. The file should upload to flash memory.

 

5. And it will tell you if it has been successful.

 

6. Select the new software and, using the ‘up arrow’ move it to the top of the list > Apply.

Note: At this point I also delete the old software packages.

7. Don’t forget to upload the packages for Linus and MacOS of you may see the following error;

The AnyConnect package on the secure gateway could not be located.

 

 

8. Remember to save the changes. File > Save running configuration to flash.

Related Articles, References, Credits, or External Links

Cisco ASA5500 AnyConnect SSL VPN 

Original article written: 02/11/12

Device Boots to ROMMON (Cisco ASA)

KB ID 0001199 

Problem

After recently picking up some second hand ASA5512-X firewalls, I went to run them up, and make sure they were ok, however on boot up they went straight to ROMMON like so;

[box]

Use ? for help.
rommon #0>

[/box]

Now I know what ROMMON is, it’s the base operating system of the device, its job is a bit like the BIOS on a PC, it locates and loads the operating system. The only time you should ever see a rommon prompt is

  • If you ‘force’ a device into rommon mode as it boots.
  • The devices config register is incorrectly set.
  • The operating system is missing/corrupt.
  • The flash memory of the device is broken, (or needs reformatting).

Chances are, the firm who ‘re-sold’ them simply did some password recovery, and forgot to set the config register back again.

Solution

I’ve recovered enough passwords and booted form the network enough times to know that if the OS is present on the device, I can load it manually with the ‘boot’ command.

[box]

rommon #0> boot
Launching BootLoader...
Boot configuration file contains 2 entries.


Loading disk0:/asa923-smp-k8.bin...

[/box]

Once loaded up and logged in, lets have a look at the config register, (it should look like 0x1).

[box]

ciscoasa# show ver | incl register
Configuration register is 0x40 << Aha!!
ciscoasa#

[/box]

The easiest way to rectify this is to delete the config register, and it will then reset to the default.

[box]

ciscoasa# configure terminal
ciscoasa(config)# no config-register
ciscoasa(config)# exit
ciscoasa#
ciscoasa# show ver | incl register
Configuration register is 0x40 (will be 0x1 at next reload)
ciscoasa#

[/box]

Reload/reboot the firewall and if it boot properly, then you know you have rectified the problem, but you can re-check..

[box]

ciscoasa# show ver | incl register
Configuration register is 0x1 << Boom!
ciscoasa#

[/box]

Related Articles, References, Credits, or External Links

NA

Deploying Applications with VMware ThinApp

KB ID 0000612

Problem

ThinApp is an “Odd” VMware product, insofar as it’s got nothing to do with virtual machines or virtual technology. It’s a product that turns applications into “Stand alone” thin applications, that can be sent to a user and ran without the need for that user to have administrative access, or the need to install anything.

ThinApp was a product called Thinstall that VMware purchased and “re-badged”, you get a free copy with VMware View 5 (Premier Edition). And it ships with a copy of VMware workstation. (Not because it needs a copy, but VMware recommends you use a clean virtual machine to create your ThinApps on).

If you’ve ever used sysdiff in the past or Novell Zenworks for Desktops, you will be familiar with the process, take a ‘scan’ of a clean machine, then install application(s), then carry out another ‘scan’. The software then works out the ‘difference’ and uses that information to build a software package.

In the example below I’m going to create a stand alone version of Google Chrome, that is pre configured, and has Java already installed, and finally deploy that as a single executable file.

Solution

1. It’s recommended that you create your ThinApp on the oldest operating system that it might be deployed on, so here I’m creating a virtual machine in VMware workstation that’s running Windows XP.

2. When built remove any hardware that will not be needed, like the floppy drive, and the USB Controller (Edit > Settings).

3. Installing ThinApp is pretty straightforward, simply run the executable and follow the on screen prompts the only thing to note is; when you enter your licence key, be aware the name you enter will display on the “splash screen” as your ThinApp loads (as shown).

4. Once your reference machine is setup, take a snapshot of it, so you can roll back to this point to create further ThinApps on this clean machine (VM > Snapshot > Take Snapshot).

5. Run the ThinApp Setup Capture > Next > Prescan > This will take a few minutes > When finished simply minimise the window you are finished with it for now. Note: Don’t worry if the application you are installing requires a reboot, ThinApp is clever enough to cope with that.

6. Now install and configure the application you require, in this case Google Chrome. I’m also installing Java, and setting the default homepage to the Google search page.

7. When the application is installed to your liking, maximise (or open the capture if you’ve rebooted) and select ‘Postscan’ > OK.

Note: Before running Postscan make sure you delete any installer files downloaded, any icons from the desktop you do not want deployed in the ThinApp, and empty the recycle bin (you don’t want all that stuff captured, when creating your ThinApp).

8. Make sure only the executable you require is ticked as an entry point > Next > At the Horizon App Manage Page > Next.

9. In a domain environment you can restrict ThinApp access to particular users or groups > Next.

10. Set the isolation mode as required, for most cases it will be ‘Full’ > Next.

11. Select the option to store the sandbox in the user profile > Next > Select whether you want to provide statistics to VMware > Next.

12. You will see this screen ONLY of you are capturing a browser. This is used if you have a particular website that will only run in IE6, or Firefox etc. So that only when URL’s enters listed here are accessed (either directly or from a hyper link) the ThinApp browser will open them, all other URL’s will be opened by the default browser. It’s a cool feature but not one I’m using > Next.

13. Give your ThinApp a name > Next.

14. I’m choosing the option to embed everything into my executable, selecting this may cause a warning about icons, but I ignored and deployed with no problems > Save.

Note: You can use this page to create an MSI file to deploy via group policy if you wish.

15. After ThinApp generates the files it needs > Build.

16. Finish

17. Heres my ThinApp executable file.

18. To test I’ve copied it to a Windows 7 machine.

19. While it’s loading this is what you will see.

20. And here is my ThinApp version of Google Chrome running and pre configured.

Related Articles, References, Credits, or External Links

NA

Creating and Deploying USB Portable Applications with VMware ThinApp

KB ID 0000616 

Problem

The last time I wrote about deploying applications with ThinApp, it was geared towards getting standalone applications onto client PC’s for non admins to run, or putting them in a network share. But if you have a portable application the advantage is you can run it from portable media (Like a USB drive).

Like before I’ll convert Google Chrome to a ThinApp, but the difference is I will set the applications ‘sandbox’ to live in the same location (on the USB). Then I’ll try it out on a different machine.

Solution

1.  It’s recommended that you create your ThinApp on the oldest operating system that it might be deployed on, so here I’m creating a virtual machine in VMware workstation that’s running Windows XP.

2.  When built remove any hardware that will not be needed, like the floppy drive, and the USB Controller (Edit > Settings).

3. Installing ThinApp is pretty straightforward, simply run the executable and follow the on screen prompts the only thing to note is; when you enter your licence key, be aware that the name you enter will display on the “splash screen” as your ThinApp loads.

4. Once your reference machine is setup, take a snapshot of it, so you can roll back to this point to create further ThinApps on this clean machine (VM > Snapshot > Take Snapshot).

5. Run the ThinApp Setup Capture > Next.

6. Prescan > This will take a few minutes > When finished simply minimise the window you are finished with it for now. Note: Don’t worry if the application you are installing requires a reboot, ThinApp is clever enough to cope with that.

7. Now install and configure the application you require, in this case Google Chrome. I’m also installing Java, and setting the default homepage to the Google search page.

8. When the application is installed to your liking, maximise (or open the capture if you’ve rebooted) and select ‘Postscan’ > OK.

Note: Before running Postscan make sure you delete any installer files downloaded, any icons from the desktop you do not want deployed in the ThinApp, and empty the recycle bin (you don’t want all that stuff captured, when creating your ThinApp).

9. Make sure only the executable you require is ticked as an entry point > Next.

10. At the Horizon App Manage Page > Next.

11. In a domain environment you can restrict ThinApp access to particular users or groups > Next.

12. Set the isolation mode as required, for most cases it will be ‘Full’ > Next.

13. As you are storing the App on USB I’d suggest (though you don’t have to) set the application to save its sandbox in the same directory.

14. Select whether you want to provide statistics to VMware > Next.

15. You will see this screen ONLY if you are capturing a browser. This is used if you have a particular website that will only run in IE6, or Firefox etc. So that only when URL’s entered, listed here, are accessed (either directly or from a hyper link) the ThinApp browser will open them, all other URL’s will be opened by the default browser. It’s a cool feature but not one I’m using > Next.

16. Give your ThinApp a name > Next.

17. I’m choosing the option to embed everything into my executable, selecting this may cause a warning about icons, but I ignored and deployed with no problems > Save.

18. After ThinApp generates the files it needs > Build.

19. Finish.

20. Heres my ThinApp executable file.

21. Which I’ve copied to my USB Drive.

22. So when use the drive in another machine.

23. You can simply run the executable.

24. While the app loads it will show a splash screen like this.

25. And should load pre-configured.

 

Related Articles, References, Credits, or External Links

NA

Ubuntu – Initial Setup, Restricted Extras, Screenlets and Cairo Dock

KB ID 0000407

Problem

You have taken the plunge and installed Ubuntu, what are you going to do next? Here’s some stuff to make your experience a little bit better.

Solution

Restricted Extras installs flash, Java, Some Codec Packs and the Microsoft core font pack. Screenlets are a collection of desktop Gadgets/Widgets. And Cairo dock is a customisable screen dock/launch pad for your applications.

Related Articles, References, Credits, or External Links

NA

Windows Server 2012 – Install Error

KB ID 0000618 

Problem

I thought I’d spin up Server 2012 today, and as usual with all new OS’s I run them up in VMware Workstation to take a look (I’m running Workstation 8.0.3 build-703057).

As soon as it started up I was greeted by this.

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005D
Parameters:
0x000000000FEBFBFF
0×0000000020000800
0×0000000000000000
0×0000000000000000

Below is information for VMware Workstation and ESXi 5

Solution

For VMware Workstation

1. In my case it was simply a BIOS setting that needed to be enabled. Enter your system BIOS and locate a feature called Data Execution Prevention, (or No Execute Memory Protection).

2. Enable that setting, then ensure you shut the machine down then manually power it back on again.

Additional Points to Note when installing Server 2012

Make sure on the properties of the VM > Hardware > Processors > Tick Virtualize Intel VT-x/EPT or V/RVI (Note: Virtual support should also be enabled in the host machines BIOS).

VMware Workstation – Error – “Virtualized Intel VT-x/EPT is disabled”

VMware Workstation likes to automatically install VMware Tools, Sometimes Server 2012 does not like this and sits with a black screen that will flash blue when you click on it. So to Stop it Installing VMware Tools, Options Tab > VMware Tools > Select Manual. Note: you can always snapshot it and then manually install it later it you want to test. This has been a problem since the early releases of Windows 8.

Solution For ESXi5

1. Here’s the same problem on an ESXi 5 host.

2. Before you do anything you need to be at ESXi 5.0 U1 for Server 2012 to be supported (That’s build number 623860 or better).

3. However in this case the problem is the same as above, The server in question was an HP Proliant ML 350 G5. Boot the server and press F9 to enter the RBSU > Advanced Options.

4. Processor Options

5. Enable ‘No-Execute Memory Protection” > Exit and save settings.

6. And now we are good to go.

Follow up

04/07/12 Email from Simon Reindl:

I had to update my Bios as InsydeH2O does not offer any tweaking options, It is using Compal Bios (previous 9, now 10 – downloaded from Compal.com. It is using InsydeH20 BIOS on a Compal motherboard. It is a custom build.

 

Related Articles, References, Credits, or External Links

NA

GNS3 – Can’t Save ASA Config – ‘%Error copying system:/running-config (Not enough space on device)’

KB ID 0000987

Problem

I love GNS3, it is a brilliant piece of software, I use it for bench testing and proof of concept work. Yes is can be a bit clunky sometimes, but it’s FREE! I had a project open with about four ASA’s on it, and it would not save the config on just one of them.

[box]

HostName(config)# copy running-config startup-config

Source filename [running-config]?
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
HostName(config)#

[/box]

[box]

HostName(config)# write mem
Building configuration...
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
Error executing command
[FAILED]
HostName(config)# 

[/box]

[box]

HostName(config)# copy running-config disk0:

Source filename [running-config]?

Destination filename [running-config]?
Cryptochecksum: fdf42190 76959bba 05a6a3d6 3f900005

%Error copying system:/running-config (Not enough space on device)
HostName(config)# 

[/box]

Solution

At first I simply deleted the ASA and added a new one, which annoyingly did the same. Then I read a post that said, do the following;

1. Open the configuration for the affected ASA.

2. Change the NIC Model to pcnet > Apply > OK > Stop the firewall > Start the Firewall.

HOWEVER, in my case the problem persisted, I eventually fixed it by formatting the virtual ASA’s flash drive.

3. Execute the following command;

[box]

HostName# format flash 

 

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

Format operation will destroy all data in "flash:". Continue? [confirm]{Enter}
Initializing partition - hda: hda1
done!
mkdosfs 2.11 (12 Mar 2005)

System tables written to disk

Format of disk0 complete
HostName# 

[/box]

4. Power off, then power on the firewall, problem fixed.

Related Articles, References, Credits, or External Links

NA

Cisco Catalyst – Upgrading ‘Stacked’ Switches

KB ID 0001002

Problem

The following procedure was carried out on two Cisco Catalyst 3750 switches.

Solution

1. We can see (above) that we have two switches, but if your connected remotely, best make sure.

[box]

Petes-Stack#show switch
Switch/Stack Mac Address : 0018.7347.a000
                                           H/W   Current
Switch#  Role   Mac Address     Priority Version  State
----------------------------------------------------------
*1       Master 0018.7347.a000     1      0       Ready
 2       Member 0024.f79b.9b00     1      0       Ready

[/box]

2. Lets see what IOS files are in the flash memory on both switches.

[box]

Petes-Stack#dir flash1:
Directory of flash:/

    2  -rwx        5514  Sep 25 2014 14:28:06 +01:00  private-config.text
    3  drwx         192   Mar 1 1993 00:10:57 +00:00  c3750-ipservicesk9-mz.122-55.SE8
   84  -rwx         856  Sep 23 2014 13:24:52 +01:00  vlan.dat
   85  -rwx       15354  Sep 25 2014 14:28:06 +01:00  config.text
   87  -rwx        3096  Sep 25 2014 14:28:06 +01:00  multiple-fs

15998976 bytes total (2406400 bytes free)
Petes-Stack#dir flash2:
Directory of flash2:/

    2  -rwx        5514  Sep 25 2014 14:28:06 +01:00  private-config.text
    3  drwx         192   Mar 1 1993 00:23:02 +00:00  c3750-ipservicesk9-mz.122-55.SE8
   84  -rwx       15354  Sep 25 2014 14:28:06 +01:00  config.text
   85  -rwx        3096   Mar 1 1993 00:04:19 +00:00  multiple-fs
   86  -rwx         856  Sep 23 2014 13:24:52 +01:00  vlan.dat

15998976 bytes total (2406400 bytes free)
Petes-Stack#

[/box]

3. Well there’s only one IOS file in there but let’s make sure anyway, by seeing what version is loaded.

[box]

Petes-Stack#show version
----output ommitted for the sake of brevity----
Switch Ports Model              SW Version            SW Image
------ ----- -----              ----------            ----------
*    1 52    WS-C3750-48P       12.2(55)SE8           C3750-IPSERVICESK9-M
     2 52    WS-C3750-48P       12.2(55)SE8           C3750-IPSERVICESK9-M
----output ommitted for the sake of brevity----

[/box]

4. Lets delete the IOS file from flash1, and make sure it’s gone.

[box]

Petes-Stack#delete /f /r flash1:c3750-ipservicesk9-mz.122-55.SE8
Petes-Stack#dir flash1:
Directory of flash:/

    2  -rwx        5514  Sep 25 2014 14:28:06 +01:00  private-config.text
   84  -rwx         856  Sep 23 2014 13:24:52 +01:00  vlan.dat
   85  -rwx       15354  Sep 25 2014 14:28:06 +01:00  config.text
   87  -rwx        3096  Sep 25 2014 14:28:06 +01:00  multiple-fs

15998976 bytes total (15972352 bytes free)
Petes-Stack#

[/box]

5. Now I’ve setup my TFTP server and downloaded the new IOS file. I need to copy it into the flash1 memory.

[box]

Petes-Stack#copy tftp flash1:
Address or name of remote host? 192.168.1.38
Source filename? c3750-ipservicesk9-mz.122-55.SE9.bin
Destination filename? c3750-ipservicesk9-mz.122-55.SE9.bin
Accessing tftp://192.168.1.38/c3750-ipservicesk9-mz.122-55.SE9.bin...
Loading c3750-ipservicesk9-mz.122-55.SE9.bin from 192.168.1.38 (via Vlan1): !!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 13009047 bytes]

13009047 bytes copied in 214.044 secs (60777 bytes/sec)
Petes-Stack#

[/box]

6. Repeat the process of deleting the IOS, and copying the new one onto flash2. It will remember your answers from earlier so just hit enter.

[box]

Petes-Stack#delete /f /r flash2:c3750-ipservicesk9-mz.122-55.SE8
Petes-Stack#show flash2:

Directory of flash2:/

    2  -rwx        5514  Sep 25 2014 14:28:06 +01:00  private-config.text
   84  -rwx       15354  Sep 25 2014 14:28:06 +01:00  config.text
   85  -rwx        3096   Mar 1 1993 00:04:19 +00:00  multiple-fs
   86  -rwx         856  Sep 23 2014 13:24:52 +01:00  vlan.dat

15998976 bytes total (15972352 bytes free)
Petes-Stack#copy tftp flash2:
Address or name of remote host [192.168.1.38]? {Enter}
Source filename [c3750-ipservicesk9-mz.122-55.SE9.bin]? {Enter}
Destination filename [c3750-ipservicesk9-mz.122-55.SE9.bin]? {Enter}
Accessing tftp://192.168.1.38/c3750-ipservicesk9-mz.122-55.SE9.bin...
Loading c3750-ipservicesk9-mz.122-55.SE9.bin from 192.168.1.38 (via Vlan1): !!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 13009047 bytes]

13009047 bytes copied in 245.945 secs (52894 bytes/sec)
Petes-Stack#

[/box]

7. Now let’s make sure the new file is in both switches flash memory.

[box]

Petes-Stack#show flash1:

Directory of flash:/

    2  -rwx        5514  Sep 25 2014 14:28:06 +01:00  private-config.text
    3  -rwx    13009047  Sep 26 2014 15:46:10 +01:00  c3750-ipservicesk9-mz.122-55.SE9.bin
   84  -rwx         856  Sep 23 2014 13:24:52 +01:00  vlan.dat
   85  -rwx       15354  Sep 25 2014 14:28:06 +01:00  config.text
   87  -rwx        3096  Sep 25 2014 14:28:06 +01:00  multiple-fs

15998976 bytes total (2962944 bytes free)
Petes-Stack#show flash2:

Directory of flash2:/

    2  -rwx        5514  Sep 25 2014 14:28:06 +01:00  private-config.text
    3  -rwx    13009047  Sep 26 2014 15:52:03 +01:00  c3750-ipservicesk9-mz.122-55.SE9.bin
   84  -rwx       15354  Sep 25 2014 14:28:06 +01:00  config.text
   85  -rwx        3096   Mar 1 1993 00:04:19 +00:00  multiple-fs
   86  -rwx         856  Sep 23 2014 13:24:52 +01:00  vlan.dat

15998976 bytes total (2962944 bytes free)
Petes-Stack#

[/box]

8. Even though it’s been deleted, the boot variable will be set to the OLD version of the IOS, to demonstrate issue the following command.

[box]

Petes-Stack#show boot
BOOT path-list      : flash:/c3750-ipservicesk9-mz.122-55.SE8
Config file         : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break        : no
Manual Boot         : no
HELPER path-list    :
Auto upgrade        : yes
Auto upgrade path   :
NVRAM/Config file
      buffer size:   524288
Timeout for Config
          Download:    0 seconds
Config Download
       via DHCP:       disabled (next boot: disabled)
-------------------
Switch 2
-------------------
BOOT path-list      : flash:/c3750-ipservicesk9-mz.122-55.SE8
Config file         : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break        : no
Manual Boot         : no
HELPER path-list    :
Auto upgrade        : no
Auto upgrade path   :
Petes-Stack#

[/box]

9. So change the boot variable to the new one, and check again.

[box]

Petes-Stack# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Petes-Stack(config)# boot system switch all flash:c3750-ipservicesk9-mz.122-55.SE9.bin

Petes-Stack#show boot
BOOT path-list      : flash:c3750-ipservicesk9-mz.122-55.SE9.bin
Config file         : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break        : no
Manual Boot         : no
HELPER path-list    :
Auto upgrade        : yes
Auto upgrade path   :
NVRAM/Config file
      buffer size:   524288
Timeout for Config
          Download:    0 seconds
Config Download
       via DHCP:       disabled (next boot: disabled)
-------------------
Switch 2
-------------------
BOOT path-list      : flash:c3750-ipservicesk9-mz.122-55.SE9.bin
Config file         : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break        : no
Manual Boot         : no
HELPER path-list    :

Auto upgrade        : no
Auto upgrade path   :
Petes-Stack#

[/box]

10. Save the changes, and reload the switch.

[box]

Petes-Stack#write mem
Building configuration...
[OK]
Petes-Stack#reload
Proceed with reload? [confirm] {Enter}
Switch 2 reloading...

[/box]

11. Post reboot, log in and check that the stack is running the new code.

[box]

Petes-Stack#show version
Cisco IOS Software, C3750 Software (C3750-IPSERVICESK9-M), Version 12.2(55)SE9, RELEASE SOFTWARE
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Mon 03-Mar-14 22:45 by prod_rel_team
Image text-base: 0x01000000, data-base: 0x02F00000

ROM: Bootstrap program is C3750 boot loader
BOOTLDR: C3750 Boot Loader (C3750-HBOOT-M) Version 12.2(44)SE5, RELEASE SOFTWARE (fc1)

Petes-Stack uptime is 5 minutes
System returned to ROM by power-on
System image file is "flash:c3750-ipservicesk9-mz.122-55.SE9.bin"

[/box]

Option 2

You can also carry out the following procedure on the switch ‘stack master’ that will automate the entire procedure for you. Note: This requires the IOS in .tar format not .bin (as above);

[box]archive download-sw /safe /allow-feature-upgrade /reload tftp:{ip-of-TFTP-Server}/{IOS-File-Name.tar}[/box]

Related Articles, References, Credits, or External Links

NA

Cisco Catalyst – %Error Deleting flash:/{name} (Is a directory)

KB ID 0001070 

Problem

Today I was upgrading a Cisco 3750 switch, and needed to free up some space in the flash memory to upload the new system image to. But when I tried to delete the current system file I got this error.

[box]

Petes-3750# dir
Directory of flash:/

2 -rwx 796 Mar 7 1993 01:15:49 +00:00 vlan.dat
3 drwx 192 Mar 1 1993 00:17:13 +00:00 c3750-ipservicesk9-mz.122-55.SE5
4 -rwx 5504 May 27 2015 10:23:47 +00:00 private-config.text
85 -rwx 3096 May 27 2015 10:23:47 +00:00 multiple-fs
86 -rwx 2544 Mar 1 1993 00:01:40 +00:00 config.backup
88 -rwx 4020 May 27 2015 10:23:47 +00:00 config.text

15998976 bytes total (2421248 bytes free)
Petes-3750(config-if)#exit

Petes-3750#delete flash:/c3750-ipservicesk9-mz.122-55.SE5
Delete filename [c3750-ipservicesk9-mz.122-55.SE5]?
Delete flash:/c3750-ipservicesk9-mz.122-55.SE5? [confirm]
%Error deleting flash:/c3750-ipservicesk9-mz.122-55.SE5 (Is a directory)

[/box]

Solution

Well the fact that the file name didn’t have ‘.bin’ on the end of it should have been a clue. Anyway to delete the folder you need to use the force and recursive switches in your delete command, (or you can use rmdir).</p?

[box]

Petes-3750#delete /force /recursive flash:/c3750-ipservicesk9-mz.122-55.SE5
Petes-3750#dir
Directory of flash:/

2 -rwx 796 Mar 7 1993 01:15:49 +00:00 vlan.dat
4 -rwx 5504 May 27 2015 10:23:47 +00:00 private-config.text
85 -rwx 3096 May 27 2015 10:23:47 +00:00 multiple-fs
86 -rwx 2544 Mar 1 1993 00:01:40 +00:00 config.backup
88 -rwx 4020 May 27 2015 10:23:47 +00:00 config.text

15998976 bytes total (15981056 bytes free)
Petes-3750#

[/box]

Related Articles, References, Credits, or External Links

NA