Upgrading 4036, media full

Hi,

I’m presently stuck in an upgrade cycle of a 4036. Image 2.1 at the moment and 3.0 is failing due the lack of media space. The manual do not specify any way of displaying flash, ram or whatever media the image is stored on. There are no CF card inside, from what I have seen. delete, format or any other command of media seem to be missing as well.

Can anyone shed light on this?

Magnus

Hi ,

Upgrade to version 3.6.2, since you have version 2.1.

If you are having issues upgrading because the file system has reached 100% then perform the following steps:

Enter to the switch via CLI with user:root and password:br6000

  1. rm /dev/nul

  2. Re-run the upgrade.

  3. Factory default the unit to clear any corrupted configuration files.

To update the software to version 3.9.1, you need to first update to version 3.6.2 and then to

3.9.1.

To update 4036 software to 3.6.2:

  1. Extract the provided upgrade_all.tgz:

In Linux, run: tar –zxvf upgrade_all.tgz

The extracted files are: upgrade.tgz, firmware.tar and versions.txt files

  1. Create a symbolic link to the software file upgrade.tgz, to upgrade_2036_4036.tgz as

follows:

ln -s upgrade.tgz upgrade_2036_4036.tgz

For V2.0.x: Run the update software CLI command

For V2.1.x: Run the update software chassis CLI command.

To update the software to version 3.9.1 :

Please follow the regular update steps described in Section 5.1, “Update to Software Version 3.9.1" in the User Manual

Hi!

  1. You must configure 4036’s ip address, subnet mask, gateway.

  2. You must configure tftp server’s ip address, too.

then…

If you in U-Boot console, you can find tftp boot command by help+enter

Before boot from tftp, you must check current environment, too!

Okay!

I’ll find the rebuild flash all batch command and capture it for you…

It’s not a command, only batch file that was consist of some commands.

What version software are you running?

no point of upgrading firmware alone. Nothing stored in the location you indicate. I image it’s text files at that location anyways, like on Cisco. Virtually takes up no space at all. Firmware errors like before as nothing has changed.

Is there a procedure for complete flash of disk and restore from TFTPBOOT? Does anyone know the syntax to TFTPBOOT? Works well on Cisco. Here manual specifies no instruction for the commands in U-Boot, that I have seen.

Thanks!

That’s a good news…:)

I’m struggled migration of Exchange Server 2003 to 2013 last week.

I’m also experienced some problem that update 4036 firmware 2.x to 3.0.

That’s a final mountain for latest firmware.

I’m so sorry that I wasn’t help your problems.

See you again.

Hi,

Thanks, I took that to mean FTP server. I know the TFTP process is manual, why I asked for the syntax to point the TFTPBOOT to the TFTP server. I have tried everything I can think of regarding the syntax in the U-Boot. I’m very familiar with this from Cisco, however have no clue about eh syntax. Question mark gives no hints and manual states nothing.

Magnus

Mmmm… That’s very curious.

This is my switch’s status

Can you try it below?

If there is any image in flash you can delete with “flash delete FLASH_NAME” command.

And… RETRY firmware update.

If you can’t update from firmware 2.1 to firmware 3.0, you also try firmware and software separately.

hi Rian,

Could you be so kind to clarify, where to link these symbolic files? I guess, basically we need to know where the file should go. We only find traces of upgrade files pertaining to firmware upgrades.

Deleting the /dev/nul only freed 1,7mb, so no luck there.

Much appreciated

Magnus

i hope this helps:

2036/4036 version 3.0.0 requires a special upgrade procedure.

If you are running version 2.1 please refer to the

following steps before downloading the version.

To update the software to 3.0.0:

  1. Extract the provided upgrade_all.tgz:In Linux – run

tar –zxvf upgrade_all.tgz

You will get : upgrade.tgz, firmware.tar and versions.txt files

  1. Create symbolic link to the software file upgrade.tgz, to upgrade_2036_4036.tgz as follows:

ln -s upgrade.tgz upgrade_2036_4036.tgz

Run the update software chassis CLI command

  1. 4036/2036 firmware 7.3.0 is a basic requirement for software V3.0.0.

When updating from previous software versions the chassis firmware should be

updated as instructed in the “Firmware Update”

  1. Did you check your flash area?

  2. If you have a console cable then you will be able to initialize

via build_flash command in U-Boot console menu.

It delete any temporary files and configuration on your flash then

rebuild all boot flash area include second boot area.

Then you can acquire more space for firmware update.

Good luck…:)

  • If you don’t have a console cable don’t try this process.

Hi inbusiness,

Thank you for your help in the matter. The U-Boot, do not contain the build_flash command unfortunately. The best I could find there was the tftpboot, however I could not figure out the correct syntax. Manual and help menu don’t mention ether.

Yes, I have console cable and I figured the 38400 speed out myself, so +1 there.

Magnus

Ok,

I see. That would be perfect if you could find that. greatly appreciated.

Magnus

Hi~ again…

When I was using build_all_flash batch command my 4036 switch’s firmware version was 3.9.1.

Because I was experienced abnormal boot process and finally I was clear that situation via this command.

You said previously below…


I’m presently stuck in an upgrade cycle of a 4036. Image 2.1 at the moment and 3.0 is failing due the lack of media space. The manual do not specify any way of displaying flash, ram or whatever media the image is stored on. There are no CF card inside, from what I have seen. delete, format or any other command of media seem to be missing as well.

Can anyone shed light on this?


What’s your exact current software version?

(* You can find version show command)

4036 software fastest upgrade path is 1.0 → 2.0 → 3.1.2 → 3.6.2 → 3.9.1

  • You can update software 2.x.x to software 3.1.2

** But software 3.1.2 require firmware 7.3.100

If your 4036 is normal condition, you can update firmware then also update software separately.

Can you try below?

  1. unzip the downloaded firmware with 7zip.

you can find upgrade.tgz and firmware.tar

  1. upload “firmware.tar” file to your ftp server.

  2. in you 4036’s CLI with admin account

4036-xxxx# update firmware chassis (in firmware 3.9.1, if you type “?” then you will find your exact command)

  1. reboot your 4036 switch

  2. retry original work.

4036-xxxx# update firmware chassis

Good luck~

Hi inbusiness,

As the text you just quoted, we have image 2.1 and try to upgrade to 3.0. I’m aware of the above steps that you outline, but since the available space is inadequate (above image) for where it inflates the tar file, this is where I get the error message from the (first image). Obviously since it cant inflate the packages, it is a corrupt file. You can see why this is an issue, as the image we upgrade to is 97M in size and the presumed disk location only is 100M. Inflation then isn’t possible. Had it used the 256M partition, it would have been flying. Update firmware Chassis, gives me no control over the location, to place the files. It has its own logic.

Magnus

Hi inbusiness,

The syntax was wrong and I never figured it out. I have a Master degree in networking, but thanks for your advice in having IP addresses on both ends of the layer 2 link….

I solved the problem with a workaround in Linux. Only from 2.1 it was a problem. Rest was just the normal procedure.

Thank you for all your effort.

Magnus

4036’s U-Boot systex is very unique.

If you want set up some parameter don’t use “=”

If you setup server ip you must type below.

server ip 192.168.0.1

(NOT server ip = 192.168.0.1)

If you use “=” that mean delete that parameter.

That’s all.

And may I have a question?

This is my firmware upgrade test screenshot.

Why your upgrade file name is upgrade.tgz?

Normally upgrade_all.tgz has all firmware and software.

In what order?

tftpboot server ip 10.0.21.15 ? Don’t work… can you check your syntax?

tftpboot server ip 10.0.21.15 comes close, but dont start transfer but gives this output: tftpboot- boot image via network using TFTP protocol… then what?

What FTP client are you using? I’m on Filezilla. I’m wiretapping the transfer and have no errors or retransmissions.

4036 has a built-in FTP client.

My FTP Server is QNAP NAS.

TFTP boot is capable on U-Boot and that process is manual.

My 4036’s current firmware is Firmware.3.9.1-985

Do you have firmware 3.1.2?

That file include procedure from 2.x to 3.1.2.

There is some information update procedure for your case.

Can you pass me your eMail address?

I’ll pass you file link on my NAS.