Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ARN image upgrade
- Thread starter kondzio
- Start date
Here is the text excerpt from some documentationt hat I typed up:
===========================================================
NOTE: For major revisions of code, such as from 14 to 15, you will have to create a new config file locally, then transfer it to the router via FTP.
If you are transferring a new config to the router, name it something other than “config” prior to the transfer so as to not overwrite the current config file. When you reboot the router, you will perform a named boot. This will ensure that if, for some reason, the new config file does not work correctly, you will still have the old config to fall back on with a simple power off/on.
So now that is out of the way, here is how to upgrade code:
Ensure that the directory on your PC that you are copying files from, has only files destined for the router, or you could encounter problems in steps 7 and 8.
1.) Open up Router Files Manager (within Site Manager) for the router in question.
2.) Click to highlight all files that you want to delete (all but config and ti_notice.txt when applicable), then click on Command, then choose Delete. Click Yes to confirm.
3.) Compact the flash card. This can either be done by clicking Command, Compact, or by telnetting to the router and issuing a compact command from the TI.
4.) Open a COMMAND prompt. Change to the directory that you have the new files for the router. This can be done, for example, by typing c: <enter>, cd temp <enter>, etc. This will, of course, vary by where you have the files at.
5.) Once there, type "ftp <router name>". When prompted, log in with the proper telnet username and password.
6.) After you are logged in, type "bin" to enter binary mode. You can enter hash if you like, but that is optional.
7.) Type "mput *.*"
8.) When prompted for each file, press "y" to transfer the file.
9.) Reboot the router at the designated time by telnetting to it and typing "boot" (if you are using the old config file), or "boot 1:arn.exe 1:<config file name>" (if using a new config file).
After the router reboots, ensure that everything is OK. If everything is OK, you can do a "save config config" from a TI prompt, unless you did a named boot. If you did a named boot, do the following:
"copy config oldconfig"
"del config"
"copy <new config file name> config"
"del <new config file name>"
"save config config"
If you are confident that everything works ont he new config, you can delete the oldconfig file.
If you are performing a major rev update, flash the boot and diag proms as instructed below.
Flashing the BOOT and DIAG PROMs for major versions of code update.
After the router reboots on the new code and config, you will do the following from the TI:
"prom –v 1:arnboot.exe 1" This will verify the BOOT PROM version. This can take a few minutes. Take note of the PROM version.
"prom –w 1:arnboot.exe 1" This will write the new code to the PROM.
"prom –v 1:arndiag.exe 1" This will verify the DIAG PROM version. This can take a few minutes. Take note of the PROM version.
"Prom –w 1:arndiag.exe 1" This will write the new code to the PROM.
"save config config"
Reboot the router, with a standard "reboot" command.
After it reboots, type "save config config"
Run each of the prom –v commands again, and check the prom versions. They should be different. If they are not, that doesn’t mean that they did not flash, it simply means that the PROM versions did not change with that version of code. This can sometimes be the case, but better safe than sorry.
===========================================================
NOTE: For major revisions of code, such as from 14 to 15, you will have to create a new config file locally, then transfer it to the router via FTP.
If you are transferring a new config to the router, name it something other than “config” prior to the transfer so as to not overwrite the current config file. When you reboot the router, you will perform a named boot. This will ensure that if, for some reason, the new config file does not work correctly, you will still have the old config to fall back on with a simple power off/on.
So now that is out of the way, here is how to upgrade code:
Ensure that the directory on your PC that you are copying files from, has only files destined for the router, or you could encounter problems in steps 7 and 8.
1.) Open up Router Files Manager (within Site Manager) for the router in question.
2.) Click to highlight all files that you want to delete (all but config and ti_notice.txt when applicable), then click on Command, then choose Delete. Click Yes to confirm.
3.) Compact the flash card. This can either be done by clicking Command, Compact, or by telnetting to the router and issuing a compact command from the TI.
4.) Open a COMMAND prompt. Change to the directory that you have the new files for the router. This can be done, for example, by typing c: <enter>, cd temp <enter>, etc. This will, of course, vary by where you have the files at.
5.) Once there, type "ftp <router name>". When prompted, log in with the proper telnet username and password.
6.) After you are logged in, type "bin" to enter binary mode. You can enter hash if you like, but that is optional.
7.) Type "mput *.*"
8.) When prompted for each file, press "y" to transfer the file.
9.) Reboot the router at the designated time by telnetting to it and typing "boot" (if you are using the old config file), or "boot 1:arn.exe 1:<config file name>" (if using a new config file).
After the router reboots, ensure that everything is OK. If everything is OK, you can do a "save config config" from a TI prompt, unless you did a named boot. If you did a named boot, do the following:
"copy config oldconfig"
"del config"
"copy <new config file name> config"
"del <new config file name>"
"save config config"
If you are confident that everything works ont he new config, you can delete the oldconfig file.
If you are performing a major rev update, flash the boot and diag proms as instructed below.
Flashing the BOOT and DIAG PROMs for major versions of code update.
After the router reboots on the new code and config, you will do the following from the TI:
"prom –v 1:arnboot.exe 1" This will verify the BOOT PROM version. This can take a few minutes. Take note of the PROM version.
"prom –w 1:arnboot.exe 1" This will write the new code to the PROM.
"prom –v 1:arndiag.exe 1" This will verify the DIAG PROM version. This can take a few minutes. Take note of the PROM version.
"Prom –w 1:arndiag.exe 1" This will write the new code to the PROM.
"save config config"
Reboot the router, with a standard "reboot" command.
After it reboots, type "save config config"
Run each of the prom –v commands again, and check the prom versions. They should be different. If they are not, that doesn’t mean that they did not flash, it simply means that the PROM versions did not change with that version of code. This can sometimes be the case, but better safe than sorry.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question