FireBrick Updates: Difference between revisions
Content deleted Content added
No edit summary |
mNo edit summary |
||
| (20 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[File:2700-small.png|link=:Category:FireBrick]] |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
The 2x00 will by default update itself for new factory releases. |
|||
| ⚫ | |||
| ⚫ | |||
The 2500/2700 will by default update itself for new factory releases. |
|||
| ⚫ | |||
Auto update is controlled in the <system... /> settings. The default (i.e., with no sw-update value set, is to update to the latest factory software. |
|||
Other settings are: |
Other settings are: |
||
*false Do no auto load |
*false Do no auto load |
||
| Line 11: | Line 13: | ||
*alpha Load test releases |
*alpha Load test releases |
||
==Disable auto-updates== |
==Example: Disable auto-updates== |
||
set: |
set: |
||
<syntaxhighlight> |
<syntaxhighlight> |
||
| Line 17: | Line 19: | ||
</syntaxhighlight> |
</syntaxhighlight> |
||
==Enable Beta software updates |
==Example: Enable Beta software updates overnight only== |
||
updating the software will reboot the FireBrick, and will mean a short amount of down time. A FireBrick reboots in less than 1 second, but then may take a few more seconds to bring up PPPoE. |
updating the software will reboot the FireBrick, and will mean a short amount of down time. A FireBrick reboots in less than 1 second, but then may take a few more seconds to bring up PPPoE. |
||
You can set a time profile, in which updates will only be applied, for example: |
You can set a time profile, in which updates will only be applied, for example: |
||
<syntaxhighlight> |
<syntaxhighlight> |
||
<system name="My FireBrick" contact="Bob" sw-update="beta" sw-update-profile=" |
<system name="My FireBrick" contact="Bob" sw-update="beta" sw-update-profile="night"/> |
||
<profile name=" |
<profile name="night" comment="Profile for updates overnight only"> |
||
<time start="01:00:00" stop="05:00:00"/> |
<time start="01:00:00" stop="05:00:00"/> |
||
</profile> |
</profile> |
||
| Line 29: | Line 31: | ||
This will only update software (level beta) between 1am and 5am on any day. |
This will only update software (level beta) between 1am and 5am on any day. |
||
You can test the status of a profile, e.g. from telnet (using 'uptime' and 'show profiles': |
|||
<pre> |
|||
My FireBrick> uptime |
|||
Version: FB2700 Inigo+ (V0.02.051 2011-02-18T20:24:43) |
|||
Uptime 01:53:44 |
|||
Current time: 21st Feb 2011 11:13:26 |
|||
My FireBrick> show profiles |
|||
updates INACTIVE outside time profile |
|||
</pre> |
|||
As you can see, it's currently 11:13, and the time profile is inactive. |
|||
==Update Logging== |
|||
Here are log line resulting in an Auto update: |
|||
<pre> |
|||
Feb 25 01:00:10 90.155.90.129 983C7 V0.02.051 DNS lookup: 0.02.051.FB2700.1294261101.306027970.2700-0009-9737.et.firebrick.ltd.uk |
|||
Feb 25 01:00:11 90.155.90.129 032C7 V0.02.051 Automatic software upgrade to alpha release V0.02.055 |
|||
Feb 25 01:00:11 90.155.90.129 032C7 V0.02.051 DNS lookup: www.firebrick.co.uk |
|||
Feb 25 01:00:11 90.155.90.129 110C7 V0.02.051 Release note: |
|||
Feb 25 01:00:11 90.155.90.129 110C7 V0.02.051 Fix to loader that was stopping 054 load. Fixed. |
|||
Feb 25 01:00:11 90.155.90.129 110C7 V0.02.051 |
|||
Feb 25 01:00:11 90.155.90.129 168C7 V0.02.051 Downloading 532478 bytes |
|||
Feb 25 01:00:12 90.155.90.129 667C7 V0.02.051 Downloaded 532478 bytes |
|||
Feb 25 01:00:12 90.155.90.129 667C7 V0.02.051 Installing new code |
|||
Feb 25 01:00:12 90.155.90.129 878C7 V0.02.051 Software image FB2700 Inigo+ (V0.02.055 2011-02-24T15:18:54) |
|||
Feb 25 01:00:12 90.155.90.129 879C7 V0.02.051 Erasing flash blocks 76 to 80 |
|||
Feb 25 01:00:17 90.155.90.129 030C7 V0.02.051 Flashing 532578 bytes to blocks 76 to 80 |
|||
Feb 25 01:00:20 90.155.90.129 944C7 V0.02.051 FB2700 Inigo+ (V0.02.055 2011-02-24T15:18:54) flashed to blocks 76-80 (532578 bytes) |
|||
Feb 25 01:00:21 90.155.90.129 288C2 V0.02.051 Shutting down |
|||
Feb 25 01:00:21 90.155.90.129 289C2 V0.02.051 Clean shutdown |
|||
Feb 25 01:00:21 90.155.90.129 368C5 V0.02.051 PPPoE 0 shutdown |
|||
Feb 25 01:00:21 90.155.90.129 369C7 V0.02.051 PPPoE 0 Tx C021:LCP 05 00 0004 TermReq |
|||
Feb 25 01:00:21 90.155.90.129 369C7 V0.02.051 PPPoE 0 PADT requested |
|||
Feb 25 01:00:21 90.155.90.129 388C7 V0.02.051 PPPoE unknown session C9A9 |
|||
Feb 25 01:00:23 90.155.90.129 290C2 V0.02.051 Shutdown complete, rebooting |
|||
Feb 25 01:00:23 90.155.90.129 836C2 V0.02.051 OS_ExecuteImage: Preparing to execute image FB2700 Inigo+ (V0.02.055 2011-02-24T15:18:54) |
|||
Feb 25 01:00:23 90.155.90.129 852C2 V0.02.051 Booting Image FB2700 Inigo+ (V0.02.055 2011-02-24T15:18:54) from flash block 76 |
|||
Jan 1 00:00:00 90.155.90.129 489C5 V0.02.055 PPPoE 0 ??? created 1/0 |
|||
Jan 1 00:00:00 90.155.90.129 496C5 V0.02.055 Config loaded OK |
|||
</pre> |
|||
It then brought up the PPP again, and set it's clock... |
|||
=Bootloader Info= |
|||
The bootloader isn't updated automatically by the FireBrick - it's just the software - this is by design. |
|||
The bootloader seldom changes. |
|||
You can manually upgrade the bootloader if you like - but unless there are new features that are useful, then there is often no need. |
|||
The bootloader version does get updated with each software release, even if there are no actual changes. The release notes will say if there are changes to the bootloader though. |
|||
[[Category:FireBrick|updates]] |
|||