Yesterday night with a delay of over 2 months i have installed 6.303 patch on ASL 6.302 (at work).
I had not never made it, a Nightmare!!
Upgrade process starts regularly and Firewall reboots after few seconds.
But 5 mins after the firewall wasn't viewable yet on network, so i have gone on CED room and i have connected to console.
Firewall apparently seemed started, so i have done a IFCONFIG to see ethernet status.
With surprise i found out that there wasn't ethernet card active, only loopback interface present.
So I have given a REBOOT command from console.
The FW had restarted apparently regularly and without errors during boot process.
But I have noticed that the Classic Three Beep has not emitted at the end of boot process.
After relogin me (via console) with displeasure I have still seen that there wasn't Eth interfaces Active/Up and even if ASL had found ethernet HW present, no ip has been assigned to interfaces and all eth interfaces were Down.
I have tried to activate them handmade with an IP (using IFCONFIG), but if apparently it seemed to work (ip assigned and interface up) then i could not access to network (operation not permitted as response).
I have rebooted Fw many times (3 to 5) and i have done many tests with no success.
At the end discouraged I have stopped to make tests and experiments, but I am remained in the CED room to think to one solution.
After over 90 mins from first reboot (the 6.303 patch reboot) i have heard the three beeps and magically all interface have become active and with correct ip.
I have noticed from HW Report that CPU usage before patch installation was high and it is remained high during all downtime period.
So i suppose (but i haven't proofs) that FW had some heavy background tasks (i.e. Building Nightly Logs), and after the reboot
it has waited for completing heavy tasks before ending boot process and before activating interface and packet filter.
Fortunately it was deep night and the downtime has not created large problems to the company (only to me :-( ) , but it is unacceptable that applying a official patch it is ended in a downtime of beyond 90 minutes.
ASL runs on an powerfull IBM Biprocessor Rack Server with 2Gb RAM and raid SCSI
This thread was automatically locked due to age.