CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. Come to CPUG CON 2008 EUROPE in Switzerland on September 8th - 9th!
    Two days full of technical content for Check Point administrators in the beautiful Swiss Alps!
    We already have sign-ups from twelve different countries!
2. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 7/14, 8/25, 10/6, 11/3, 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8.
3. Corrent S3500 SecureXL Turbocards For Sale - Last Six Remaining - Get Your Spares!
4. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 And Related Products > Miscellaneous
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2005-08-12
BarryStiefel BarryStiefel is offline
Administrator
 
Join Date: 2005-08-11
Location: San Francisco, CA
Posts: 534
Rep Power: 10
BarryStiefel has disabled reputation
Default Error "FW-1 IP xxx the fw-1 driver could not be informed"

Error "FW-1 IP xxx the fw-1 driver could not be informed"

FW-1 NG FP3 or NG AI on Solaris 8 or Solaris 9. The Solaris host OS is a minimal install which has been hardened by Sun's jass tool.



Console and /var/adm/messages keep showing this error: fwip: [ID 719488 kern.notice] FW-1 IP: An interface configuration command has been issued, but the FW-1 driver could not be informed.This may be due to the driver being removed from the system, or a failure of the fw bootd process.If this message keeps appearing afterrebooting the machine, please contact Check Point technical support.This message can be safely ignored inthe following cases:FW-1 has just been uninstalled or upgraded and has not been rebooted yetorThe machine is now in single user mode.This message will be suppressed for the next 127 times.

One possible cause of this error message is the hardening jass does to syslogd. jass configures syslogd to no longer accept logs from remote machines.

To resolve this error:

On Solaris 8:
  • vi /etc/init.d/syslog and remove the option '-t' from the line that calls /usr/sbin/syslogd (last line in the 'start' section before the closing 'fi')

On Solaris 9:
  • vi /etc/default/syslogd and change LOG_FROM_REMOTE from NO to YES

On both Solaris 8 and 9, restart syslogd: # cd /etc/init.d# ./syslog stop# ./syslog start

If you wish to be doubly sure this worked, reboot your firewall, and verify that the error no longer occurs during boot.

-- PhoneBoy - 05 Jan 2004

FAQForm FAQs.Class: TroubleshootingFAQs FAQs.OS: OsSolaris FAQs.Version:
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -7. The time now is 19:36.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
LinkBacks Enabled by vBSEO 3.0.0