* Conserve Mode Activation:
* FortiGate enters conserve mode to prevent system crashes when the memory usage reaches critical levels. The "red threshold" is the point at which FortiGate starts dropping new sessions to conserve memory.
* When the system memory usage exceeds this threshold, the FortiGate will block new sessions that require significant memory resources, such as those needing content inspection.
* Exiting Conserve Mode:
* The "green threshold" is the memory usage level below which FortiGate exits conserve mode and resumes normal operation.
* Once the system memory usage drops below this threshold, FortiGate will start allowing new sessions again.
References:
* Fortinet Community: Understanding conserve mode and its thresholds(Welcome to the Fortinet Community!)(Welcome to the Fortinet Community!).
* Fortinet Documentation: Memory conserve mode and thresholds(Welcome to the Fortinet Community!)(Fortinet GURU).

* RADIUS Server IP Address:
* The debug output shows that the RADIUS request was sent to the server atIP=172.25.188.164.
This indicates that the RADIUS server being queried for authentication is indeed located at this IP address.
* Authentication Result:
* The debug output includes a line indicating the result for the RADIUS server:Result for radius svr 'RadiusServer' 172.25.188.164(0) is 0. A result code of0typically signifies that the authentication attempt was unsuccessful.
* Authentication Scheme:
* The debug output does not indicate that the authentication scheme used was pop3; it mentions using CHAP (Challenge Handshake Authentication Protocol).
* Two-factor Authentication:
* There is no indication in the debug output that two-factor authentication was required for this session.
References
* Fortinet Network Security 7.2 Support Engineer Documentation
* RADIUS Authentication Configuration and Debugging Guides

The session table entry provided shows detailed information about a specific network session passing through the FortiGate device. From the session details, we can see that the session has various attributes such as state, protocol, policy, and inspection details.
* The session state (proto_state=11) indicates that the session is being actively processed and inspected.
* Thenpd_state=00000000suggests that the session is being handled by the CPU rather than offloaded to a Network Processor (NP).
* The session is marked for security profile inspection, evident from the detailed byte/packet counts and other session parameters.
From these indicators, it's clear that FortiGate is using its CPU to perform security profile inspection on this session rather than simply forwarding the traffic without inspection or relying solely on IPS inspection.
References
* Fortinet Documentation on Session Table
* Fortinet Community Discussion on Session Table

* IKE_SA_INIT:
* This is the first exchange in IKEv2. It establishes a secure, authenticated channel between peers and negotiates cryptographic algorithms and keys.
* IKE_Auth:
* The second exchange authenticates the IKE SA (Security Association) using the previously negotiated keys and algorithms. This exchange also establishes the first IPsec SA.
* Create_CHILD_SA:
* This exchange creates additional IPsec SAs after the initial authentication. It can also be used to rekey existing IPsec SAs to maintain security.
* Informational:
* This is a generic exchange used for various purposes such as error notification, deletion of SAs, and other control messages.
References:
* Fortinet Community: IKEv2 packet exchanges and troubleshooting
* Fortinet Documentation: IPsec VPN Concepts

The exhibit displays the output of a real-time debug of the URL filtering process on a FortiGate device. The debug output includes various details about a web request being processed.
* SNI (Server Name Indication): This is part of the SSL/TLS handshake where the client specifies the hostname it is trying to connect to. FortiGate can use this information to apply appropriate web filtering rules based on the server name.
* CN (Common Name): This is a field in the server's SSL certificate that typically contains the server's hostname. FortiGate can extract this information to verify the identity of the server and apply security policies accordingly.
Given that the debug output includes the hostname "training.fortinet.com," it is likely derived from the SNI in the client's request or the CN in the server's certificate, indicating that FortiGate is using this information to process the web request.
References
* Fortinet Community Documentation on Real-time Debugging