2.checkpoint Firewall Troubleshooting
2.checkpoint Firewall Troubleshooting
2.checkpoint Firewall Troubleshooting
Network Shield
This blog is specially dedicated to those people who are keen learner of networking. You can learn lots of about networking and network
security here. We will share basic networking concept to complex networking, troubleshooting steps here. Also, we will share network security
questions and other stuffs here.
Showing posts with label Checkpoint Firewall Troubleshooting. Show all posts
IP Subnet
Calculator
IP Subnet Calculator
Checkpoint Schedule management database backup
YouTube 969 Local Weather
Report
Know Your Local Weather
Checkpoint Schedule management database backup Report
Network World
Checkpoint
The upgrade_tools (or the migrate command) is a powerful and simple tool that allows us to perform a backup of our Checkpoint database,
Checkpoint Firewall
objects, policies
Troubleshooting
Interview Question
Backing up periodically the Checkpoint congura on allows us to recover quickly from a disaster by se ng up a new SMS (Security Management
ASA (7)
Server). This involves two steps:
Data Interview Question
Checkpoint Firewall Training
Script that exports the Checkpoint congura on (2)
This could be the most simple version of the script (migrate_export.sh for example): F5 (2)
Home
VPN Videos
#!/bin/bash
source $HOME/.bash_profile
TODAY=`date +%Y-%d-%m`
TARGET_PATH=/BACKUPS_FOLDER
TARGET_FILE=$TARGET_PATH/EXPORTDB_$TODAY.tgz
if [ -d $TARGET_PATH ]
then
cpstop &> /dev/null
$FWDIR/bin/upgrade_tools/migrate export -n $TARGET_FILE
cpstart &> /dev/null
fi
It i s i nteres ng a s a n op on to us e a s the ta rget path a mounted vol ume to us e a nother s erver a s a ba ckup repos i tory or stora ge.
I created a "SCRIPTS" subfolder on my user $HOME. Choose the loca on to save your script and then, add execu on permissions.
# chmod +x /home/admin/SCRIPTS/migrate_export.sh
Test it by launching it manually to ensure it works like you want. Then we can con nue with the next step
This is a light and fast backup so that we can schedule it to be executed once a week for example.
This example shows an schedule congura on every monday at 7:00 that can be done via Gaia WebUI or command:
G AI A WE BUI
add cron job EXPORTDB command /home/admin/SCRIPTS/migrate_export.sh recurrence weekly days 1 time 07:00
When the recurrence is weekly: To specify the days, enter the day by number: 0 is Sunday and 6 is Saturday.
When the recurrence is monthly: To specify the days, enter the day by number: 1 to 31.
Separate several days with commas. For example: for Monday and Thursday enter 1,4
No comments:
Having our Checkpoint VSX Virtual System ac ve connec ons under control can be very important to avoid problems, congure a higher
connec on limit, be ready for growth (and so scalate our environment)
Nagios and SNMP can be used to congure a VS connec on monitor plugin:
Contents [hide]
We can use either the OID (.1.3.6.1.4.1.2620.1.16.23.1.1.2) or the MIB object name (vsxCountersConnNum). To download the MIB, this link: sk90470
This OID/Object shows the ac ve connec ons for the physical VSX (vsxCountersConnNum.1.0) and for each virtual system (f.e.
vsxCountersConnNum.2.0 for VS1, )
Very important! If the queries are unexpectedly returned with value 0, look at this post:
Checkpoint SNMP return 0 value when querying virtual systems
HOST=$1
VS=$2
LIMIT=$3
LIMIT2=$4
Made
SNMP=`/usr/bin/snmpwalk -v1 -c public $HOST vsxCountersConnNum.$VS 2> /dev/null`
of
if [ $? -ne 0 ]
then
echo "UNKNOWN: No SNMP response from $HOST"
exit 3
fi
The script receives the host, the virtual system, warning and cri cal number of connec ons and returns exit code as Nagios expects, and the
output shows a message and sends performance data (to generate the graphs).
A er crea ng the script and copying it to the nagios plugins folder, the new check command can be congured.
Sec on Congura on / Commands / Checks sec on
For Centreon:
Assign a name and congure this command line (parameters of the script, the rst one is assigned by Nagios using the host value):
define command{
command_name check_fw_vs_connections
command_line $USER1$/check_fw_vs_connections.sh $HOSTADDRESS$ $ARG1$ $ARG2$ $ARG3$
}
Subnet
Calcula
tor
(CIDR)
Home
Check Command: The value should be the name assigned to the command (check_fw_vs_connec ons) Checkpoint
Args: Will contain 3 parameters, star ng and separated with the character '!' ASA
Interview
Param 1: VS (remember 1.0 is the VSX itself, 2.0 is the VS1) Question
define service{
host_name Checkpoint_VSX1, Checkpoint_VSX2
service_description Conns EXTERNAL
_SERVICE_ID 202
use SRV_TEMPLATE_1min
check_command check_fw_vs_connections!2.0!100000!200000
}
This example !2.0!100000!200000 is for Virtual System 1, when connec ons are under 100000 the state is OK, between 100000 and 200000 is
WARNING and more then 200000 is cri cal.
A er restar ng Nagios services, the connec ons should be monitorized and the graphs being generated within some minutes
No comments:
In my post Checkpoint Automa c NAT vs Manual NAT I explained both types of NAT clarifying that the Manual NAT makes neccesary the Proxy
ARP entry congura on. This example is for a Checkpoint VSX cluster scenario.
This is an example that was used:
The IP that should be congured to answer to ARP request is the 80.80.100.100 (No server in my environment has this IP congured but the Proxy
ARP entry will allow the rewall to manage and NAT the packets sent to that IP).
The entry "links" the IP address with the MAC address of the interface that should manage the packet. There is a le that contains all that
entrys: $FWDIR/conf/local.arp
1. Congure the Policy Global Proper es to make this work (only once)
2. Log in expert mode and edit the $FWDIR/conf/local.arp (if it does not exist, create it) for all cluster nodes.
3. Install the corresponding policy
When "Merge manual proxy ARP congura on" is unchecked the local.arp le is ignored.
So ensure this op on is checked:
Change to the virtual system where the NAT is performed (this is for my perimetral FW VS1):
[Expert@vsx1:0]# vsenv 1
Context is set to Virtual Device VSX1_EXTERNAL (ID 1).
This is my way to know the MAC address. Surely there are more (and or be er) ways:
Other scenarios
Be aware that this congura on is valid for virtual systems on a VSX cluster environment.
Check this ocial SK30197 for more scenarios.
No comments:
Last week my smartcenter server became corrupted (the lesystem) and I could not install any fw policy (checkpoint so ware could not nd some
needed inodes).
Fortunately I perform periodically checkpoint congura on backups (using the migrate export u lity) this way -> Checkpoint Schedule
management database backup
It is evident but we need a new machine to be used as SMS server. As a best prac ce, if virtual environment is available, the best solu on is to
generate a new virtual machine so the recovery can nished as soon as possible.
If there is no choice the same machine can be used (I completely discourage it). Anyway try to save the data (if s ll can access the old server) you
can miss in another path (scripts, patches). The backup is supposed to be in another secure path.
Finally, shut o the old server if s ll on the network (or change the network to test one on the virtual machine to isolate it).
A er that, get the Checkpoint ISO (the same version that was installed) and run it on the new machine. So the installa on starts
Ok, proceed
Keyboard selec on
Disk par oning, leave it by default or customize. A er the installa on I add a new disk with more space to store the logs so I dont think much
about this congura on
Choose a password to access via SSH or web GUI to the SMS server
Congure the same parameters as the old server. The hostname is specially important to be the same! (like the management IP)
Again congure the same management IP. (This screenshot shows empty elds but they are prelled with the IP congured on the previous step).
A er completed the installa on we have a fully func onal SMS server but with empty rewall policies, databases, etc
Import the Checkpoint congura on backup
CO NNE CT T O T HE S M S V I A S S H
Connect via SSH to the SMS server, establish an expert password and enter expert mode
[Expert@SMS:0]#
CO P Y T HE B A CK UP FI L E
Copy the backup of the Checkpoint congura on to the SMS server (via SCP for example if the backup is located on another Linux machine)
I M P O RT T HE B A CK UP
This will pause the cp services, import all the congura on policies, databases, objects and start the services
Maybe you have lost changes made between the backup and the crash. If possible (documented, emails) add those changes
CO NFI G URE L O S T S E RV E R PA RA M E T E RS
For example, I had to congure some OS level parameters to make the DHCP Relay work. Fortunately, I documented that change.
No comments:
Simplilearn
Hive Tutorial
Hive In Hadoop Big Data Tutorial For Beginners