| |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [FW-1] fw reboot when doing secureclient site update !!!!
- To: [email protected]
- Subject: Re: [FW-1] fw reboot when doing secureclient site update !!!!
- From: Walter Nordmann <[email protected]>
- Date: Thu, 1 Aug 2002 09:59:12 +0200
- Reply-to: Mailing list for discussion of Firewall-1 <[email protected]>
- Sender: Mailing list for discussion of Firewall-1 <[email protected]>
- Thread-index: AcI43R4sAE1mJjW7Tu6R2sNoYI6m8QAU2dFC
- Thread-topic: [FW-1] fw reboot when doing secureclient site update !!!!
hi john,
we had the same problem with a cluster ng fp1 - it was a bug which has been fixed in fp2.
btw: both fw-modules don't boot at the "same" time - the first one dies and after some seconds the client talks to the other fw-module and that dies too.
don't use fp1 with ha AND vpn !
walter nordmann, cards germany
-----Original Message-----
From: Jim Parker [mailto:[email protected]]
Sent: Wed 7/31/2002 18:11
To: [email protected]
Cc:
Subject: [FW-1] fw reboot when doing secureclient site update !!!!
upgrade to sp6
----- Original Message -----
From: "Yannick Lo Guidice" <[email protected]>
To: <[email protected]>
Sent: 31 July 2002 09:43
Subject: [FW-1] fw reboot when doing secureclient site update !!!!
> Hi all,
>
> I have a situation here with my firewall. My firewall is a cluster of Sun
> Solaris 7 w/ CP 4.1 SP5. The management station is a W2K server w/ CP NG
> FP2.
>
> The firewall logs show that when a user connects to the firewall by the
> internet side of the firewall, this is working. But if the user connects
> himself on the LAN, when his machine boots up the secureclient asks for
> update site ; this update makes the firewall reboot 1 minute after... And
> both firewalls reboot at the same time !!!
>
> You sure understand how important this situation is, I would greatly
> appreciate your opinion on this issue.
>
> The log message on the firewall changes sometimes but is often related to
> cookies error. I include below an example error message...
>
> Jul 31 09:13:38 myfirewallhost unix: FW-1: cookie_get_data: cookie too
> small 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: one_cookie_length: cookie too
> small 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: cookie_length: problem with
> cookie 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: one_cookie_length: cookie too
> small 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: cookie_length: problem with
> cookie 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: cookie_get_data: cookie too
> small 80af50bc
> Jul 31 09:13:38 myfirewallhost last message repeated 3 times
> Jul 31 09:13:38 myfirewallhost unix: FW-1: one_cookie_length: cookie too
> small 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: cookie_length: problem with
> cookie 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: one_cookie_length: cookie too
> small 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: cookie_length: problem with
> cookie 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: cookie_get_data: cookie too
> small 80af50bc
> Jul 31 09:13:38 myfirewallhost last message repeated 7 times
> Jul 31 09:13:38 myfirewallhost unix: FW-1: one_cookie_length: cookie too
> small 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: FW-1: cookie_length: problem with
> cookie 80af50bc
> Jul 31 09:13:38 myfirewallhost unix: BAD TRAP: cpu=0 type=0x31
> rp=0x7094fce8 addr=0xbaddcb0b mmu_fsr=0x0
> Jul 31 09:13:38 myfirewallhost unix: sched:
> Jul 31 09:13:38 myfirewallhost unix: trap type = 0x31
> Jul 31 09:13:38 myfirewallhost unix: addr=0xbaddcb0b
> Jul 31 09:13:38 myfirewallhost unix: pid=0, pc=0x1023e320, sp=0x7094fd78,
> tstate=0x4480001e00, context=0x98e
> Jul 31 09:13:38 myfirewallhost unix: g1-g7: 700ea2f0, baddcafe, 3cebdc,
22,
> 70126fa0, 0, 40027e60
> Jul 31 09:13:39 myfirewallhost unix: Begin traceback... sp = 7094fd78
> Jul 31 09:13:39 myfirewallhost unix: Called from 10037d70, fp=7094fdd8,
> args=70182000 80c63f20 80b2ba38 70172a50 100 100
> Jul 31 09:13:39 myfirewallhost unix: Called from 7080953c, fp=7094fe38,
> args=80b2ba38 80c63f20 700e5688 10100 1023e30c 80b2ba98
> Jul 31 09:13:39 myfirewallhost unix: Called from 70823b08, fp=7094fea0,
> args=80af50a4 80ae53b0 8 800001 2 14
> Jul 31 09:13:39 myfirewallhost unix: Called from 70800144, fp=7094ff00,
> args=80ae5398 0 0 0 3388 260
> Jul 31 09:13:39 myfirewallhost unix: Called from 70824614, fp=40027918,
> args=7094ff00 7082363c 80ae5398 0 0 0
> Jul 31 09:13:39 myfirewallhost unix: End traceback...
> Jul 31 09:13:41 myfirewallhost unix: panic[cpu0]/thread=40027e60:
> Jul 31 09:13:41 myfirewallhost unix: trap
> Jul 31 09:13:41 myfirewallhost unix:
>
>
=================================================
To set vacation, Out Of Office, or away messages,
send an email to [email protected]
in the BODY of the email add:
set fw-1-mailinglist nomail
=================================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
=================================================
If you have any questions on how to change your
subscription options, email
[email protected]
=================================================
================================================To set vacation, Out Of Office, or away messages,
send an email to [email protected]
in the BODY of the email add:
set fw-1-mailinglist nomail
================================================To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================If you have any questions on how to change your
subscription options, email
[email protected]
================================================
|
|
