The gateway is rebooted if the Allow Reboot option was selected and the package requires it. The gateway version is updated in SmartDashboard. The installed packages are updated in SmartUpdate.
Upgrading a VSX Gateway Important - Before you begin, make sure no other administrators are connected to the management server. On the management server, log in to Expert mode. Upgrading Standalone Full High Availability Full High Availability: The server and the gateway are in a standalone configuration and each has High Availability to a second standalone machine.
To upgrade Full High Availability for cluster members in standalone configurations, there are different options: Upgrade one machine and synchronize the second machine with minimal downtime.
Upgrade with a clean installation on one machine and synchronize the second machine with system downtime. Upgrading with Minimal Downtime You can do a Full High Availability upgrade with minimal downtime to the cluster members. To upgrade Full High Availability with minimal downtime: Make sure the primary cluster member is active and the secondary is standby: check the status of the members.
Start failover to the second cluster member. The secondary cluster member processes all the traffic. Log in with SmartDashboard to the management server of the secondary cluster member. Click Change to Active. Configure the secondary cluster member to be the active management server. Upgrade the primary cluster member to the appropriate version. Log in with SmartDashboard to the management server of the primary cluster member.
Make sure version of the SmartDashboard is the same as the server. Upgrade the version of the object to the new version. Install the policy on the cluster object. The primary cluster member processes all the traffic. Upgrade the secondary cluster member to the appropriate version. Synchronize for management High Availability.
Upgrading with a Clean Installation You can do a Full High Availability upgrade with a clean installation on the secondary cluster member and synchronize the primary cluster member.
To upgrade Full High Availability with a clean installation: Make sure the primary cluster member is active and the secondary is standby: check the status of the members. Install the secondary member. From SmartDashboard, configure the cluster object. Change the secondary details if necessary.
Establish SIC. Upgrading Clusters If the appliance to upgrade was not the primary member of a cluster before, export its database before you upgrade. To upgrade an appliance and add it to a cluster: If the appliance was not the primary member of a cluster, export the Security Management Server database. Upgrade the appliance. If the appliance was not the primary member of a cluster, Import the database.
Using the Portal, on the Cluster page, configure the appliance to be the primary member of a new cluster. Connect a second appliance to the network. If the second appliance is based on an earlier version: get the relevant upgrade package from the Download Center, save it to a USB stick, and reinstall the appliance as a secondary cluster member.
If the second appliance is upgraded: run the first-time wizard and select Secondary Cluster Member. For IPv6 Support , select On. When prompted, select Yes to reboot. Off-Topic Discussions. Try out the new CheckMates Labs! Create a Post. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Sign In Help. One member was not working and need to rebuild. Click Next.
Change the default administrator password and click Next. Configure the Management Connection settings: IPv4 address and Subnet mask of the management interface Note - You can leave the IP address and the subnet mask unchanged. Configure Connection to UserCenter settings optional - an additional interface for remote management: Interface - select an interface on the appliance Configure IPv4 - Select On from the drop-down menu by default, it is off Enter the IPv4 address and Subnet mask of the interface Configure IPv6 - Select On from the drop-down menu by default, it is off Enter the IPv6 address and Subnet mask of the interface Click Next.
On UTM-1 and models only - Get a license automatically from the User Center and activate it, or use the trial license. Review the summary, make sure it is correct, and click Finish.
On UTM-1 and models only, click Yes t o start the configuration process. A progress bar tracks the configuration of each task. Click OK to finish the installation. To install Gaia on an open server: Start the computer using the installation media. When the first screen shows, select Install Gaia on the system and press Enter. You must press Enter in 60 seconds, or the computer will try to start from the hard drive.
The timer countdown stops once you press Enter. There is no time limit for the subsequent steps. Press OK to continue with the installation. Select a keyboard language. English US is the default. Make sure the disk space allocation is appropriate for the environment. Enter and confirm the password for the admin account. Configure the management IP address, net mask and default gateway. You can define the DHCP server on this interface. Select OK to format your hard drive and start the installation.
Press reboot to complete the installation. Select Continue with configuration of Gaia R Change the default administrator password. Set the host name for the appliance. Set the username and password for the Security Management Server administrator account and then click Next.
You can also select a range of IPv4 addresses. Get a license automatically from the UserCenter and activate it, or use the trial license. Review the summary and, if correct, click Finish.
To start the configuration process, click Yes. If necessary, download SmartConsole from the Gaia Portal. Permanent Kernel Global Variables Make sure that the upgrade does not overwrite custom values with defaults.
For upgrades to R Note or record the cluster ID before the upgrade. Upgrade each cluster member. See the cluster ID. Get the values of the variables after the upgrade. Each must be the same as before the upgrade. Make sure that you have the correct ISO file. Install the Gaia or SecurePlatform operating system on Smart See instructions in UTM-1 and Models. To select the Security Management Server image: While the appliance is restarting, open the terminal emulation program.
When prompted, press any key to enter the boot menu. Type yes and press Enter. Log in using the default username and password: admin and admin. Run the show interfaces command to get the name of the management interface. Open a connection from a browser to the management IP address. Log in to the system with the default username and password: admin and admin Click Login.
Follow the instructions on the screen. Install from a USB device. Recovery Automatic version recovery from the Check Point Cloud. Import an existing snapshot. In the Authentication Details page, change the default administrator password. Use this connection to download a license and activate it. Reload to refresh your session. You signed out in another tab or window. By upgrading to Gaia, customers will benefit from improved appliance connection capacity and reduced operating costs.
As a Bit OS, Gaia increases the connection capacity of existing appliances supporting up-to 10M concurrent connections for select Models. Furthermore, Gaia greatly increases operation efficiency by offering Automatic Software Update.
0コメント