Log Messages
Check Point products provide you with the ability to collect comprehensive information on your network activity in the form of logs. You can audit these logs at any given time, analyze your traffic patterns and troubleshoot networking and security issues. Familiarizing yourself with the logs can help you understand and learn the status of your network, as well as resolve problems you are experiencing with the system. Reviewing traffic logs is a very important aspect of security management, and should get careful attention.
Carrier Security Log Messages
This section contains a list of Carrier Security log messages and resolutions, listed alphabetically. You may encounter self-explanatory log messages that are not included here.
Log Message |
Meaning |
Resolution |
---|---|---|
Duplicate sequence number |
This G-PDU |
Enforcement of G-PDU Also, it is possible to change the drop and alert behavior of the rate limiting feature by editing the gtp_sequence_deviation_drop |
Echo Request not within time limit |
An echo request was received too close to a previous echo request. This echo request will be dropped. |
This will happen only if you set the value of the |
Echo Request on a path which is not in use |
An echo request was received on a path (SGSN |
This happens if you set the value of the |
GTP |
This packet (PDU) exceeded the Signaling Rate Limit defined for the indicated destination host |
This could be the result of a Signaling flood attack. If this happens during normal operation it might be advisable to increase Enforce GTP Signal packet rate limit for this GSN |
GTP: T-PDU |
This T-PDU packet (The internal packet of a G-PDU) is a GTP packet by itself. This may indicate on attempt to inject GTP packets into the system. |
If you do want to enable such type of packets, you can check the Allow GTP in GTP in the Carrier Security page of the Global Properties tab (equivalent to setting |
GTP: Invalid End User IP Address |
This T-PDU packet (The internal packet of a G-PDU) has an end user address IP that does not match the end user IP address of the PDP context |
Uncheck the Enforce GTP AntiSpoofing property in the Carrier Security page of the Global Properties window (this is equivalent to setting the To uncheck only GTP IPv6 AntiSpoofing, set the |
GTP intra-tunnel Inspection: Forbidden MS |
The end user address of this T-PDU does not conform to the end user Domain Policy defined for the APN |
Change the end user Domain Policy in the APN Properties window. |
Illegal Handover |
An Update Request was initiated from a new SGSN (source IP) which is not in the Handover group of the old SGSN of the tunnel. You can see the new SGSN IP in the Source column and the old SGSN IP in the SGSN Signal column. |
Adjust the GSN Handover Group definitions in the GSN Handover Group window. |
Illegal Handover GSN Signaling |
Illegal redirection attempt for GSN signaling. The GSN Signaling Information Element IP is not in the same Handover group as the Source IP of the message. You can see both IPs in the log. |
Adjust the GSN Handover Group definitions in the GSN Handover Group window. |
Illegal Handover - GSN Traffic |
Illegal redirection attempt for GSN traffic. The GSN traffic Information Element IP is not in the same Handover group as the source IP of the message. You can see both IPs in the log. |
Adjust the GSN Handover Group definitions in the GSN Handover Group window. |
Illegal Handover Recreate PDPC |
This "Create PDP Context Request" PDU did not conform to the handover policy. |
If the GSN handover and GSN redirection are only allowed within a GSN Handover Group. If this PDU does conform to your handover policy, adjust the GSN Handover Group definitions in the GSN Handover Group window. |
Illegal response cause |
The response cause in this response message is illegal for this message type. |
|
Invalid G-PDU |
Relevant for V0 G-PDUs. The SGSN IP, GGSN IP or Flow Label of the G-PDU does not match the definitions of the tunnel the G-PDU belongs to. (Tunnel association is according to TID |
You can remove flow label compliance on the Carrier Security page of the Global Properties window. However if the Flow Labels are wrong, it is recommended to investigate the cause. IP checking cannot be disabled. |
Invalid Signaling Recreate Req PDU |
Relevant for V0. There was an attempt to create a PDP Context of an already established tunnel. |
The recreate policy of established tunnels is determined by the A |
Invalid Signaling Req PDU |
Relevant for V0 Delete Request, V0 Update Request, and V0->V1 Update Request. Either the source IP address, dest. IP address, or flow label does not match those of the tunnel (TID) to which the packet belongs. |
Flow label verification can be disabled by deselecting the Verify Flow Label setting, found in the Carrier Security tab of Global Properties. IP checking cannot be disabled. |
Invalid Signaling Flow Label PDU (Update Resp) |
V0 Update Resp. The flow label does not match the tunnel (TID) to which the packet belongs. |
Flow label verification can be disabled by deselecting the Verify Flow Label setting, found in the Carrier Security tab of Global Properties. IP checking cannot be disabled.
|
Invalid Signaling Flow Label PDU (Create Resp) |
V0 Create Resp. The flow label does not match the tunnel (TID) to which the packet belongs. |
Flow label verification can be disabled by deselecting the Verify Flow Label setting, found in the Carrier Security tab of Global Properties. IP checking cannot be disabled.
|
Invalid Signaling Flow Label PDU (Delete Resp) |
V0 Delete Resp. The flow label does not match the tunnel (TID) to which the packet belongs. |
Flow label verification can be disabled by deselecting the Verify Flow Label setting, found in the Carrier Security tab of Global Properties. IP checking cannot be disabled.
|
IP is not in the APN domain |
The assigned static or dynamic end user IP is not part of end user Domain defined for the related APN. |
This packet is dropped according to the APN end user Domain defined in SmartConsole |
Malformed Path Management PDU |
This Path management PDU does not conform to GTP standards. |
Path management PDUs are verified against GTP Release 1997 and 1999 Standards.
|
No Match on Create PDP Context PDU |
A "Create PDP Context Request" PDU was not matched on the Rule Base |
The allowed types of "Create PDP Context Request" PDUs are defined in the Rule If the combination of the above in the dropped PDU should have been allowed, please review your Rule Base to allow this traffic. If the last rule in the Security Policy |
Out of range sequence number |
This G-PDU carries an out-of-range sequence number. |
Enforcement of G-PDU sequence numbers is determined in the Carrier Security page of the Global Properties window, where you can also define the maximum allowed deviation for all Carrier Security Gateways. Also, it is possible to change the drop and alert behavior of the rate limiting feature by editing |
Packet or some Information Element is shorter than expected |
During stateful inspection, this packet (PDU) was shorter than expected. |
This packet does not have the minimal length to hold the GTP header information, or the packet size is small than indicated by the length field in the GTP header. |
Passed maximum create request |
Too many re-transmissions of the same delete request were received (while create response not received yet by the Carrier Security Gateway |
Set the |
Passed maximum delete request |
Too many re-transmissions of the same delete request were received (while delete response not received yet by the Carrier Security Gateway). This request packet will be dropped. |
This can occur if the Carrier Security Gateway is configured to close all end user connections using the SAM API. Set the |
Passed maximum update request |
Too many re-transmissions of the same update request were received (while update response not received yet by the Carrier Security Gateway). |
Set the |
re-using TEID |
The specified TEID of this tunnel create attempt is in use by another tunnel (for the same SGSN- GGSN pair). The new tunnel is created. |
If the attribute |
re-using TEID Data Downlink |
The specified TEID of this tunnel create attempt is in use by another tunnel (for the same SGSN- GGSN pair). The new tunnel is created. |
If the attribute |
re-using TEID Data Uplink |
The specified TEID of this tunnel create attempt is in use by another tunnel (for the same SGSN- GGSN pair). The new tunnel is created. |
If the attribute |
re-using TEID Control Uplink |
The specified TEID of this tunnel create attempt is in use by another tunnel (for the same SGSN- GGSN pair). The new tunnel is created. |
If the attribute |
re-using TEID Control Uplink, SRC=0 |
The specified TEID of this tunnel create attempt is in use by another tunnel (for the same SGSN-GGSN pair). The new tunnel is created. |
If the attribute |
Request/ Response Mismatch |
This Signaling Response PDU carries a wrong Sequence number or does not match any Signaling Request. |
Signaling Response PDUs must match a previously approved Signaling Request PDU in order to pass the Carrier Security Gateway. This cannot be configured. |
TEID 0 not allowed for Update message type |
A V1 Update Request has TEID 0. This is valid only for V0 to V1 handover cases. However the imsi and nsapi Information Elements of this Request do not match an existing V0 tunnel. |
This packet will be dropped. |
TID 0 not allowed for this message type |
A Signaling PDU carries a NULL TID violating the GTP protocol. |
This packet violated basic packet integrity and will not pass through the Carrier Security Gateway. |
Unestablished Tunnel |
This signaling or data packet belongs to an unestablished tunnel.
|
PDUs can only pass the Carrier Security Gateway if they carry a Tunnel ID (V0) or a Tunnel EndPoint ID (V1) of a previously established PDP context that was not yet terminated. This packet violates basic tunnel integrity and will not be allowed. |
Unknown GTP Message Type |
This packet constitutes an unsupported GTP Signaling message. |
|
Unsupported version |
A GTP packet with version other than V0 or V1 was received. |
The packet will be dropped. |
Adding Information Elements to Logs
Carrier Security 6.0 provides the option of including certain Information Elements to logs with GTP information. These Information Elements are:
-
RAT - (Radio Access Type)
-
IMEI-SV (International Mobile Equipment Identity - Software Version)
-
MS-Time Zone
-
Mobile User Location
To add these Information Elements to the log, use the GuiDBedit database tool to set the attribute gtp_log_additional_fields
to true
. The default setting is false
. Adding Information Elements to Logs
Carrier Security 6.0 provides the option of including certain Information Elements to logs with GTP information. These Information Elements are:
-
RAT - (Radio Access Type)
-
IMEI-SV (International Mobile Equipment Identity - Software Version)
-
MS-Time Zone
-
Mobile User Location
To add these Information Elements to the log, use the GuiDBedit database tool to set the attribute gtp_log_additional_fields
to true
. The default setting is false
. Adding Information Elements to Logs
Carrier Security 6.0 provides the option of including certain Information Elements to logs with GTP information. These Information Elements are:
-
RAT - (Radio Access Type)
-
IMEI-SV (International Mobile Equipment Identity - Software Version)
-
MS-Time Zone
-
Mobile User Location
To add these Information Elements to the log, use the GuiDBedit database tool to set the attribute gtp_log_additional_fields
to true
. The default setting is false
.