background image

21   Release and Migration Notes - Updating Standard Hardware from 4.2.x to 5.0.3

Updating Standard Hardware from 4.2.x to 5.0.3

General

Due to a kernel version change between 4.2.x and 5.0.3 (Linux kernel 2.4 was changed to Linux kernel
2.6), the enumeration of NICs may on some hardware sort the ethX devices in a different order,
resulting in a loss of management access.

Therefore, a procedure has now been implemented to rename the interfaces after upgrading to 5.0.3
to stay identically with the 4.2.x interface names. This is done by creating an interface mapping table
using the eth device’s MAC addresses as identifiers. 

The following procedure 

must be performed on every single unit separately

 due to the fact the MAC

addresses are different per unit and so will be the mapping table.

If you find out later that your server is not affected by the resorting issue, then you may delete the
mapping configuration subsequently. The network activation log will then contain the following
message:

No difference found between configured and detected MAC to interface mapping

Update is possible on standalone as well as on NG CC-managed units from 
firmware 4.2.0 onwards to 5.0.3.

Updating from a base release in the range from 4.2.0 to 4.2.14 requires a hotfix 
to be installed. 4.2.15 and 4.2.16 include the functionality, hence no hotfix is 
required.

It is recommended to evaluate the process on a system with physical access 
or in a lab environment in case the upgrade fails.

The procedure is compatible with user defined interface mappings. If a user 
defined interface mapping is found, it will be applied after the MAC-to-eth 
mapping procedure.

If you add additional NICs after upgrading to 5.0.3, the mapping may fail. 
Therefore, do not use MAC mapping in this case any longer but switch to user 
defined interface mapping. The problem may occur if linux detects the new 
NICs before it detects the old ones.

Updating Procedure

Step 1: Prepare the Standard Hardware For the Update

If the unit runs on firmware 4.2.14 or below, you must install the hotfix

boxnet_mac2ifmapping-386-4.2.14

.

Summary of Contents for NG FIREWALL 5.0.3

Page 1: ...Version 5 0 3...

Page 2: ...1 All rights reserved Use of this product and this manual is subject to license Information in this document is subject to change without notice Trademarks Barracuda NG Firewall is a trademark of Barr...

Page 3: ...cuda NG Installer 10 Barracuda NG Firewall 10 Determine Your Update Scenario 13 Updating Unmanaged Units or NG Control Centers 15 Updating Units or NG Control Centers Using SSH 15 Updating HA Synced U...

Page 4: ...Release and Migration Notes...

Page 5: ...acuda Networks strongly recommends to study the Barracuda NG Firewall 5 0 Migration Instructions available for download at http barracuda com doc as under certain circumstances no countermanding is po...

Page 6: ...m system requirements for Barracuda NG Firewall Operation System included Barracuda OS Disk space 15 GB on a dedicated harddisk for gateway installation on harddisks 4 GB for gateway installation on a...

Page 7: ...s support If you are using standard hardware and or updating from phion netfence please pay also attention to the Barracuda NG Firewall 5 0 Migration Instructions and the Barracuda NG Firewall 5 2 Mig...

Page 8: ...s Target Version Current Version 5 0 5 0 1 5 0 2 5 0 3 4 2 10 and earlier 4 2 11 4 2 13 4 2 14 4 2 15 4 2 16 5 0 5 0 1 5 0 2 If you are going to update from a firmware release version below 5 0 then p...

Page 9: ...Release 5 0 1 5 0 2 5 0 3 Software Modules Firewall VPN Service Access Control Service HTTP Proxy Secure Web Proxy URL Filter Mail Gateway Spam Filter Virus Scanner DHCP Service DHCP Relay DNS FW Audi...

Page 10: ...rror message was generated An error occurred finding the installation image on your hard drive Please check your images and try again This issue was fixed Table 1 8 Barracuda NG Firewall Module Descri...

Page 11: ...nction with different firmware release versions on a Barracuda NG Control Center and its managed units certain configuration options may erroneously have been unavailable on the NG Control Center such...

Page 12: ...12 Release and Migration Notes Bugfixes Included with Barracuda NG Firewall 5 0 3...

Page 13: ...firmware 5 0 X use the patch xxx tgz file For a fresh installation use the iso file In case you are updating a HA synchronized unit to firmware release version 5 0 3 while not updating its secondary u...

Page 14: ...figuration Type Applicable Update Instructions Unmanaged Unit or NG Control Center If you want to update either an unmanaged unit or an NG Control Center then proceed to Updating Unmanaged Units or NG...

Page 15: ...ve unit To get the file onto the unit you may use the Send File button within the built in SSH client of Barracuda NG Admin Don t forget to change the directory first using cd var phion packages Step...

Page 16: ...ed in Updating Units or NG Control Centers Using SSH page 15 No more interaction with the HA unit is necessary Wait until the update is finished Depending on the hardware it will need from 15 minutes...

Page 17: ...ary Wait until the update is finished Depending on the hardware it will need from 15 minutes on the fastest appliances up to 60 minutes on the flash appliances Step 5 Switch Servers Back to the Primar...

Page 18: ...Control Center using Barracuda NG Admin Navigate to Control Firmware Update and click Import Select the update package within the file browser Step 2 Select Units to Update and Send them the Update Ch...

Page 19: ...minutes on the fastest appliances up to 60 minutes on the flash appliances Take a look into the box log file at Box Logs Box Release update after the update process has been finished In case of a not...

Page 20: ...Firewall 5 0 3 on standard hardware you need to apply hotfix 386 before migrating from 4 2 x to 5 0 3 in order to make use of the MAC to eth mapping feature that will help you to keep the port labeli...

Page 21: ...activation log will then contain the following message No difference found between configured and detected MAC to interface mapping Update is possible on standalone as well as on NG CC managed units f...

Page 22: ...dvanced configuration mode Set Use Assignment to yes Click Send Changes followed by Activate Step 4 Proceed to the Update Upgrade the unit following the standard 5 0 3 upgrade procedure as described i...

Page 23: ......

Page 24: ......

Reviews: