We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

FSC-Series Deployment

  • Last updated on

Deploying a Barracuda NextGen FSC-Series network requires at least one FSC Access Cluster, a NextGen Control Center, and the deployment of the individual FSC devices.

FSC Access Cluster and NextGen Control Center Deployment

Each Secure Connector connecting to your network must be assigned to an Access Concentrator and a NextGen Control Center managing the Access Concentrators and Secure Connectors. The Access Concentrator is the VPN endpoint for the Secure Connectors and forwards management traffic to the Control Center. If the Access Concentrator is not in the same network a dedicated site-to-site VPN tunnel can be created from the Access Concentrator to the Control Center.

For more information, see Secure Access Concentrator and Control Center Deployment.

Access Concentrator in the Public Cloud

The Access Concentrator can be deployed directly in the public cloud. This allows the devices behind the Secure Connectors direct access to your backend services running in the Cloud. The Control Center can also be in the cloud, or be located on-premises. In case the Control Center is not directly reachable, a VPN tunnel from the Access Concentrator to the Control Center can be configured to transmit managment traffic from the Access Concentrator and the Secure Connectors to the Control Center.

For more information, see Secure Access Concentrator in the Public Cloud.

Secure Connector Deployment via Configuration File

The configuration for the Secure Connectors is created and managed on the Control Center, optionally using templates to reduce the configuration overhead. The configuration file is then exported and copied to the Secure Connector via USB OTG or web interface. The Secure Connector then automatically connects to the Access Concentrator assigned to it. This allows the Secure Connector to connect in VPN operational mode and authenticate by the certificates included in the configuration file.

For more information, see Secure Connector Deployment via Configuration File.

Secure Connector Deployment via VPN Deployment Mode

If you do not have physical access to the device, configure the Secure Connector in the Control Center. Directly on the Secure Connector, configure the WAN connection and VPN so the Secure Connector can connect to the Access Concentrator in VPN deployment mode. No certificates are required because the Access Concentrator uses a passphrase to authenticate. Once connected, the Control Center immediately pushes the operational configuration to the Secure Connector and switches the VPN to operational mode.

For more information, see Secure Connector Deployment via VPN Deployment Mode.

Last updated on