| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Hi We have a Firewall Cluster in distributed architecture with following details: This is Check Point VPN-1(TM) & FireWall-1(R) NGX (R60) HFA_05, Hotfix 605 - Build 020 --> Splat It happens that it runs OK for few Weeks or month then all of a sudden we come to know that no traffic is passing through the firewall. when we try to ping any ip behind the firewall (Its a branch Office for us), we ping from our main Office, either it times out or we get high latancy. As the firewall is stil up the secondary do not takes over. If we reboot this firewall then every thing is back to normal again. normal latency 156 ms, after error latency is 1200 ms around. what can this be. As its a production firewall we can not let it remain down for long. |
| |||
| Well you can try to determine what is causing the slowdown. Maybe start by checking the CPU, RAM, connections, ideally when the problem is happening. Also check processes running, etc... The brute force option would be to just re-install that module. |
| |||
| What happens if you fail over to the other module when you are seeing these issues? Check all your interface setup match each other. i.e. if you ISP router is running at 100mb f/d then set the firewall external interface to match, continue this for each of the interfaces. |
| |||
| Hi Meriol I checked for CPU and memory utilization those are very much normal since last reboot. Danielpb As it has become a normal practice.. we just give reboot command as we see this error. Failover is OK. once the Primary comes up, traffic start going through it as if nothing has happened :)... Enforcement Module Interfaces are 1000 Base T, and it shows ---> eth0: negotiated 100baseTx-FD flow-control, link ok eth1: negotiated 100baseTx-FD, link ok SIOCGMIIPHY on 'eth2' failed: Operation not supported eth3: negotiated 100baseTx-FD, link ok eth2 is Sync Int. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |