Requirements and Limitations

The following requirements and limitations apply to the GMS transition to NSM 3.0 or later.

• Your GMS environment needs to be running GMS9.5.0 before the migration can be initiated. Refer to the Global Management System 9.5 Upgrade Guide for the details.
• During the transition, reporting and firewall log data stored in GMS is not moved to NSM. However, during transition NSM adds GMS as an external analytics agent which allows the user to view historical reports and logs stored in GMS from the NSM user interface.
• The transition process is designed to move only manage firewalls, GMS domains as NSM tenant, GMS users, schedule reports and related data from GMSto NSM. All other configuration needs to be performed manually by the user in NSM.
• The transition process does not provision required licenses on NSM. This has to be performed by the user separately by following the existing NSM on-prem licensing workflow.
• NSM on-prem supports reporting and analytics only for Gen 7 and Gen 8 firewall models. Reporting and analytics is not enabled for any Gen 6 firewalls.
• The GMS transition workflow moves all firewalls managed in GMS to NSM on-prem and does not provide the option to move only selected firewalls.
• If your GMS system has both syslog and flow reporting, you have to select which one reporting type for viewing GMS historical reports in the NSM firewall view.
• Since NSM only manages firewalls, other security appliances types supported by GMS such, as Secure Remote Access (SMA) and Email Security, are not transitioned to NSM. Use respective management solution to manage these devices.

• NSM reporting and analytics is based on flow events collected from firewall and it does not support reporting and analytics based on firewall syslogs.