FortiWeb
A FortiWeb can be configured to join a Security Fabric through the root or downstream FortiGate.
Deepak_Girimaji_FTNT
Article Id 408326
Description This article defines the scope of TAC support with respect to firmware upgrades, routine maintenance activities, and requests for proactive and standby support.
Scope FortiWeb.
Solution

Fortinet's Technical Assistance Centre (TAC) provides reactive support to troubleshoot break/fix issues, answer product-related questions, and investigate unexpected behavior. Proactive or standby assistance (such as remaining standby or on a call during planned activities) and routine administrative tasks (such as upgrades or disaster recovery drills) fall outside the scope of TAC.

 

Firmware upgrade:

 

The steps for upgrading firmware on a standalone node or cluster are outlined in the Administrator Guide. For details regarding a particular firmware version, including its upgrade path and important upgrade notes. The relevant release notes should be consulted. These can be downloaded for the appropriate version under the section 'Release Notes'.

 

All related documentation can be accessed from the FortiWeb documentation section.

 

DR activity or other maintenance tasks:

 

If specific instructions or guidance are required, the support ticket must include all the necessary detailed information. Providing comprehensive information enables TAC to understand the situation better and offer appropriate guidance. However, the activity itself remains the responsibility of the administrator, and TAC should only be engaged if an issue arises during or after the task.

 

Standby Support:

 

Standby support requests (except where an issue has already been previously encountered) are outside the scope of TAC. Such requirements can be covered through Advanced Support.

 

General Guidance:

 

In the event that issues are encountered during or after the activity (such as upgrade, DR drill or maintenance), a ticket with all necessary details must be raised so that TAC can proceed with troubleshooting. Each distinct issue must be submitted as a separate ticket with the relevant information. This ensures compliance with the 'one issue per ticket' policy, supporting clear orientation within the ticket and efficient review of the ticket history when required.


If the encountered issues are severe enough to be classified as P1/P2 (as per the FortiCare Service Level Agreements), the support line must be contacted to reach an available engineer, explain the business impact, and request a priority increase.