Home Installation and Configuration

Installation and Configuration

Information with how to install and configure FastNetMon and FNM Manager

By Administrator MKE Solutions

• 10 articles

FastNetMon & FNM Manager Installation Steps

FNM Manager is a web panel designed to simplify the management of FastNetMon. Follow these steps to complete the installation successfully. System Requirements To ensure proper functionality of FastNetMon and FNM Manager, make sure your system meets the following requirements: 1. Operating System: - Ubuntu 22.04 (recommended for maximum compatibility and stability). 2. Server Resources: System resources (CPU, RAM, and storage) depend on: - The total traffic on the network. - The bandwidth being handled. - The number of networks being monitored. Minimum recommendations: - CPU: Modern multi-core processor. - Memory (RAM): 8 GB (minimum for efficient traffic processing). - Storage: 250 GB (recommended 500 GB or more) for storing traffic data, statistics, and historical analysis. Installation Steps 1. Download the FNM Manager installer Run the following command to download the installer: wget https://install.fastnetmon.mkesolutions.net/installer_fnm -Oinstaller_fnm && chmod +x installer_fnm 2. Execute the installer with the FastNetMon voucher Run the installer using your FastNetMon voucher code: ./installer_fnm -m FULL -f YOUR_VOUCHER_CODE Replace YOUR_VOUCHER_CODE with the code provided in your portal account. 3. Register the FNM Manager license Register your license by running the following command: fnm_cli --register_license --voucher="YOUR_LICENSE_CODE" --name="YOUR_COMPANY_NAME" --email="YOUR_EMAIL" Replace: - YOUR_LICENSE_CODE: The code provided when you purchased the license. - YOUR_COMPANY_NAME: Your registered company name or user. - YOUR_EMAIL: The email associated with your portal account. 4. Select the license type In the next step, you will be prompted to select the license to apply: - BASIC: A license with basic features. - PRO: A license with advanced features. 5. Set the system user password After registering the license, configure a password for the default system user system@fnm.local. You can choose a password manually or generate a random one: - To set a manual password: fnm_cli --system_user --password=system - To generate a random password: fnm_cli --system_user --password --random 6. Access the web panel Access the FNM Manager web panel in your browser at: https://YOUR_SERVER_IP:8081 Replace YOUR_SERVER_IP with the IP address of the server where FNM Manager was installed. 7. Configure FastNetMon and FNM Manager Follow the standard configuration logic to enable telemetry, define networks, and set up actions for attack responses. Refer to the official documentation for further details. Important Notes - Compliance: Following FastNetMon and European Union regulations, this software cannot be sold or distributed in banned countries. Please verify the list of restricted regions before proceeding with the installation.

Last updated on Jan 21, 2025

Basic Configuration of FNM Manager

The configuration of the FNM Manager web panel follows a similar logic to FastNetMon. Below are the essential steps to perform a basic configuration. 1. Enable Traffic Capture FNM Manager supports various telemetry protocols for traffic capture, including: - NetFlow (v5, v9, IPFIX). - sFlow. - Port Mirroring (if the above protocols are not compatible). Steps: 1. Go to Settings > General. 2. Enable the desired protocols and configure the corresponding ports. 3. Adjust the sampling ratio if a value different from the default is used. Important: - Configure the active and inactive flow timeout on your network devices (recommended: 30 seconds). - Adjust the Average Calculation Time in FNM Manager to be slightly higher than the timeout configured on the devices. 2. Enable Counters & Tracking You can enable the counters and tracking options you want to analyze. Keep in mind that activating more options may increase hardware resource usage. Available Options: - ASN Counters: Enable/disable traffic counting by ASN. - Interfaces Counter: Monitor traffic by interface. - Connection Tracking: Enable tracking of active connections. - Remote Host Tracking: Track remote IPs (not recommended for large environments). 3. Configure Networks You must define the networks that will be analyzed by FastNetMon. If a network is not configured here: - Its traffic will not be protected. - It will appear as "Others Traffic." Configuration Options: 1. Add networks manually in CIDR format. 2. For large volumes of networks, you can associate an ASN, and FNM Manager will automatically detect the related networks. Note: Keep the networks updated to ensure continuous protection. 4. Configure Databases FNM Manager requires ClickHouse as a mandatory database for its operation. You can also enable InfluxDB for legacy support purposes. Additional Features: - Threshold calculator based on stored traffic. - Calculation by maximums or 95th percentile for each hostgroup. 5. Configure Customers / Hostgroups By default, FastNetMon applies the same thresholds to all hosts in the network using the global hostgroup. However, you can create different hostgroups with customized thresholds to suit your needs. Common Use Cases: - Enterprise customers. - ISP clients. - Content caches. - NAT or CGNAT groups. Note: Hostgroups allow for more granular and specific configuration for each network segment. Hostgroup/Customer Configuration: Define thresholds for each group. Configure banning actions or profiles. Set up notifications for the customer/hostgroup. 6. Configure Actions to Detect an Attack Once thresholds are configured, activate the ban mode and define actions to mitigate an attack. Options include: 1. Blackhole: Publish a /32 via BGP with a specific community for routing policy handling. 2. Scrubbing Center: Publish a /24 via BGP to redirect traffic to a cleaning center. 3. FlowSpec: Create advanced filtering rules distributed via BGP. 4. MikroTik API: Send the /32 IP to a MikroTik device to add it to an address list and apply actions, such as NAT or masquerade.

Last updated on Jan 20, 2025

Database Maintenance and Disk Space Management

Database Maintenance and Disk Space Management Managing the database efficiently is crucial for ensuring optimal performance of FNM Manager. The more traffic you monitor and the longer the retention period for storing data, the more disk space will be required. Below are the details and steps to maintain and manage the ClickHouse database effectively. ClickHouse Database TTL By default, ClickHouse in FastNetMon is configured with a 7-day Time-To-Live (TTL). This means data older than 7 days will automatically be purged to save disk space. You can view and adjust the TTL settings both via the web interface and the CLI. View TTL Settings 1. Navigate to Settings > Database Settings in the FNM Manager web interface. 2. Alternatively, you can use the CLI to view the current TTL settings and database size: fnm_cli --clickhouse_ttl Modify TTL Settings You can adjust the retention period for data stored in the ClickHouse database. The default CLI command sets the TTL to 2 days, but you can customize it with the --days parameter. Example Commands: - Set TTL to 2 days: fnm_cli --set_clickhouse_ttl - Set TTL to a custom value (e.g., 5 days): fnm_cli --set_clickhouse_ttl --days=5 Note: The retention period directly affects disk space usage. A longer TTL requires more storage but retains more historical data for analysis. Monitor Database Disk Usage It's essential to keep track of the database size to prevent the system from running out of disk space. - Use the Advanced Database Settings in the web interface to view the size of each table and its TTL configuration. - CLI command to view database sizes: fnm_cli --clickhouse_ttl Best Practices 1. Optimize TTL Settings: - Set the TTL based on your organization's requirements for data retention and available disk space. - For example: - High traffic environments: Consider a TTL of 2-3 days to conserve space. - Low traffic environments: A TTL of 7+ days may be acceptable. 2. Regular Monitoring: - Check database size regularly to ensure the system is not nearing disk capacity. 3. Scale Disk Storage: - As your traffic and retention requirements grow, plan for additional disk storage to maintain performance

Last updated on Jan 20, 2025

Security Guide: Configuring the Access Control List (ACL) in FNM Manager

Security Guide: Configuring the Access Control List (ACL) in FNM Manager Configuring an Access Control List (ACL) in FNM Manager allows you to restrict panel access to specific IP addresses and Autonomous System Numbers (ASNs), ensuring that only authorized devices can interact with it. This functionality enhances security by preventing unauthorized access from external networks. Benefits of Enabling the Access List 1. Enhanced Security: Only predefined IPs and ASNs will be able to access the panel. 2. Granular Control: Ability to define access for entire networks or specific entities. 3. Risk Mitigation: Reduces the risk of intrusions from untrusted networks. Steps to Configure an Access Control List in FNM Manager 1. Access the Security Settings - Log in to FNM Manager as an administrator. - Navigate to Settings > System Security & Privacy. 2. Add IP Addresses or ASNs to the Whitelist - IP Address: - In the "Enter Network or ASN for Access List" field, enter a network in CIDR format (e.g., 192.168.1.0/24) or a specific IP address (e.g., 192.168.1.100). - Select the Whitelist option. - Click Add to include it. Networks or ASNs will be automatically added to the allowed list. - ASN: - Enter the Autonomous System Number (ASN), such as AS15169. - Select the Whitelist option. - Click Add to include it. ASNs will also be added automatically. 3. Verify Current Access - The interface will display the IP address you are currently accessing from, along with the associated ASN. Ensure it is listed as allowed ("Access Allowed"). 4. Enable the Access List and Save the Configuration - Once you have confirmed that your IP, network, or ASN is correctly configured in the whitelist, activate the Enable Access List option. - Enabling this functionality will change the default behavior to "deny all access" for any IPs and ASNs not specified in the whitelist. - Click Save Config to save this configuration. This step will enable the access list and apply the configured rules. Maintaining the Access List View the Current List - Allowed (whitelist) and blocked (blacklist) entries will be displayed with their type (IP or ASN) and associated value. Delete Entries - To remove a specific entry, click the Delete button next to it. - If you want to clear the entire list, use the Delete All button. Cleaning Configuration via CLI - If the access list is misconfigured and you lose access to the panel, you can clean the configuration using the following command in the command-line interface (CLI): fnm_cli --clean_security_acl Security Recommendations 1. Configure Before Enabling: Ensure your current IP is included in the whitelist before enabling the access list to avoid losing access to the panel. 2. Use CIDR Ranges or ASNs: To simplify management, use entire networks or ASNs if multiple IPs are associated with a trusted organization. 3. Periodic Audits: Regularly review the access list to ensure entries are valid and necessary. 4. Understand Default Behavior: When the access list is enabled, the default mode is "deny all access." If no whitelist range is specified, you will lose access to the panel and will need to clean the configuration via CLI to regain access. With this configuration, FNM Manager will be protected against unauthorized access, strengthening your network security and minimizing potential risks.

Last updated on Jan 20, 2025

Flexible Thresholds and Traffic Rules in FNM Manager

Flexible Thresholds and Traffic Rules in FNM Manager Introduction FastNetMon includes a "Flexible Thresholds" functionality that allows network administrators to configure specific rules to detect traffic patterns. FNM Manager simplifies the configuration of this functionality, making it easier to create Traffic Rules and customized thresholds for each Hostgroup. This tool is especially useful for identifying and mitigating volumetric attacks, such as those based on amplified protocols (NTP, DNS, DHCP, among others). Configuring Flexible Thresholds in FNM Manager The Flexible Thresholds functionality allows users to define up to 10 specific traffic patterns due to resource limitations in FastNetMon. The most commonly used protocols to detect and mitigate volumetric attacks are: - DNS (UDP 53) - NTP (UDP 123) - DHCP (UDP 67 and 68) - Chargen (UDP 19) - SNMP (UDP 161) - Additional protocols like BGP, MT_API, and MT_Winbox. Steps to Configure Flexible Thresholds: 1. Settings Configuration: - Navigate to Traffic Rules > Advanced Settings. - Enable the "Enable Flexible Counters" option to allow customized threshold configuration. 2. Protocol Selection: - In the "Default Amplification Vectors" field, select the relevant protocols. Common examples include DNS, NTP,TFTP, DHCP, Chargen, and SNMP. 3. Creating Traffic Rules: - FNM Manager will automatically create traffic rules for the selected patterns. For example: - DNS: UDP 53 - NTP: UDP 123 - DHCP: UDP 67 and 68 - TFTP: UDP 69 - Chargen: UDP 19 - SNMP: UDP 161 Configuring Hostgroups After adding the traffic rules (Traffic Rules), the next step is to configure the customized thresholds for each Hostgroup based on the selected patterns. These thresholds enable more precise and tailored mitigation according to each network segment's requirements. Recommendations: - Set a minimum of 1000 PPS for NTP, DNS, and Chargen, as these are the most common in volumetric attacks. - Adjust the Mbps and PPS thresholds based on the typical traffic behavior in the network to avoid false positives. Benefits of Flexible Thresholds 1. Custom Detection: Identifies specific malicious traffic patterns, such as NTP or DNS amplification attacks. 2. Efficient Mitigation: Customized thresholds block anomalous traffic before it impacts the network. 3. Simplified Configuration: FNM Manager automates the creation of traffic rules and thresholds. 4. Granular Control: Hostgroups allow tailored configurations for each network segment. Best Practices - Select only the most relevant protocols for your network. - Adjust the PPS and Mbps thresholds to reflect typical network traffic behavior, avoiding false positives. - Use "bgp_flow_spec" if your network supports this functionality for more robust mitigation.

Last updated on Jan 21, 2025

Whitelists and Remote Whitelists in FNM Manager

Whitelists and Remote Whitelists in FNM Manager Introduction FastNetMon includes two types of whitelists for managing network exceptions that should not be blocked during DDoS attack detection: 1. Whitelist: Local networks that should not be sent to blackhole. 2. Remote Whitelist: External networks that should also be excluded from blocking. These functionalities are easily managed through the "Block Manager" module in FNM Manager, offering granular control over networks that need differentiated protection. Configuring Whitelists Local Whitelist The local whitelist is useful to prevent traffic from internal networks from being blocked during mitigation. This ensures that critical services within the infrastructure continue to function without interruptions. Example of configuration in FastNetMon: sudo fcli set main networks_whitelist 192.168.0.0/24 In FNM Manager, you can add local networks through the section: - Block Manager > Whitelist. - Enter the network address with its mask (e.g., /24) and click "Add to Whitelist Now". Remote Whitelist The remote whitelist allows excluding external networks from blocking. This is useful to prevent interruptions in traffic to and from specific partners, providers, or key clients. Example of configuration in FastNetMon: sudo fcli set main networks_whitelist_remote 8.8.8.8/32 In FNM Manager, you can add remote networks through the section: - Block Manager > Remote Whitelist. - Enter the external IP or network address with its mask and click "Add to Remote Whitelist Now". Reasons to Create Exceptions 1. Critical Local Services: Avoid blocking networks that host important internal services, such as internal DNS servers, databases, or email systems. 2. Partner and Provider Networks: Ensure uninterrupted connections with strategic partners or key providers during attack mitigation. 3. Priority Clients: Exclude traffic from important clients or critical networks to maintain their uninterrupted experience. 4. Essential Public Services: Prevent blocking of services like trusted public DNS servers (e.g., Google’s 8.8.8.8). Benefits of Using Whitelists - Customized Mitigation: Allows excluding specific networks from blocking without compromising overall security. - Service Continuity: Ensures that critical services remain operational during a DDoS attack. - Improved Customer Relationships: Ensures that connections with key external networks are not affected.

Last updated on Jan 21, 2025

Telegram Bot Manager in FNM Manager

Telegram Bot Manager in FNM Manager Introduction The Telegram Bot Manager in FNM Manager allows administrators to interact with the panel via Telegram (chat or group). This feature provides real-time access to FastNetMon's main data, such as total traffic and top hosts. It also enables actions like sending IPs or networks to Black Hole, applying FlowSpec rules as needed, and retrieving details about BGP peers or recent attacks. Key Features - Retrieve FastNetMon's main data (e.g., total traffic, top hosts). - Query details about recent attacks and view attack reports. - View active Black Hole rules, with the ability to add or remove IPs or networks. - Manage FlowSpec rules: view active rules, access a predefined rule database, inject these rules via BGP, or clear FlowSpec rules from the RIB. - Configure interaction using two methods: GetUpdates Polling or Webhooks. - Use the same API Token and Chat ID as Telegram notifications or configure separate ones for the Bot Manager. Configuration Options Interaction Methods 1. GetUpdates Polling: - Regularly polls Telegram for updates at a configured interval (e.g., every 3 or 5 seconds). - Requires the Telegram Bot Manager service to be running to receive messages. 2. Webhooks: - Telegram sends real-time updates to a specified URL. - Requires a valid SSL certificate or a self-signed certificate (in this case, you must upload the public key to Telegram). - Supported ports for Webhooks: - 443, 80, 88, 8443 - It is highly recommended to review the official Telegram documentation for proper webhook configuration. Shared or Separate Configuration - Shared Configuration: - Use the same API Token and Chat ID for notifications and the Telegram Bot Manager. - Separate Configuration: - Configure a different API Token and Chat ID to separate functions between notifications and the bot. Steps to Configure Telegram Bot Manager 1. Enable Telegram Bot Manager: - Navigate to System Notifications > Telegram Bot Manager. - Enable the "Enable BOT Manager" option. 2. Set API Token and Chat ID: - Enter the Telegram API Token. - Provide the Chat ID for administration. 3. Choose the Interaction Mode: - Select either GetUpdates Polling or Webhooks. 4. Save the configuration. 5. Test and Start the Bot: - Use the "Send Test" button to validate the configuration. - Start the bot service with "Start Service BOT" to begin receiving messages. Important Notes 1. Exclusivity Between GetUpdates and Webhooks: - Updates cannot be received via GetUpdates while a webhook is configured. 2. Self-Signed Certificates: - If using a self-signed certificate, upload the public key using the certificate parameter (sending a string is not supported). 3. Port Configuration: - Ensure the webhook URL uses one of the supported ports: 443, 80, 88, or 8443. 4. Service Requirement for GetUpdates: - When using GetUpdates Polling, the Telegram Bot Manager service must be active to receive messages at the configured interval (e.g., 3 or 5 seconds). Example with Webhook settings. Example with GetUpdate settings Interaction with the Bot The Telegram bot allows simple commands to retrieve network data or execute actions. Examples of available commands: - /help: Displays the list of available commands. - /status: Shows system status (CPU, memory, traffic, recent attacks, etc.). - /total_traffic: Provides detailed statistics on total traffic (incoming and outgoing). - /top_talkers: Lists the top hosts by incoming and outgoing traffic. - /blackhole: - Displays the total number of active Black Hole rules. - Allows adding or removing IPs or networks to/from Black Hole. - /flowspec: - Displays active FlowSpec rules. - Allows querying the predefined rule database. - Injects predefined rules into the RIB via BGP. - Clears FlowSpec rules from the RIB. Interaction Example Command /blackhole - Displays the total number of active Black Hole rules. - Additional options: - Show the current rules. - Add or remove rules as needed. Command /flowspec - Manages FlowSpec rules: - flowspec_active: Displays active FlowSpec rules. - flowspec_db: Shows the predefined rule database. - flowspec_send_rib: Publishes the predefined rules to the RIB via BGP. - flowspec_flush_rib: Clears FlowSpec rules from the RIB. Recommendations - SSL Certificates: - Use a valid SSL certificate for Webhooks. - Consider setting up a reverse proxy with SSL (e.g., Nginx or Apache). Screenshots /help /status /total_traffic /flowspec

Last updated on Jan 21, 2025

Opsgenie by Atlassian Notifications in FNM Manager

Opsgenie Notifications in FNM Manager Introduction FNM Manager integrates seamlessly with Opsgenie by Atlassian to deliver advanced alerting and notification capabilities. This integration ensures that critical events detected by FastNetMon are promptly communicated to your team, enabling quick responses to network incidents. Key Features - Real-time alerts for critical events in FastNetMon. - Customizable priority levels for alerts. - Ability to define source identifiers and alias prefixes for better organization. - Supports integration using an Opsgenie API key. Configuration Steps 1. Enable Opsgenie Integration: - Navigate to System Notifications > Alerts Opsgenie by Atlassian. - Toggle the Enable Alerts by Opsgenie option. 2. Enter the Opsgenie API Key: - Obtain your API key from your Opsgenie account. - Paste the API key into the Opsgenie API_KEY field. 3. Define Source and Alias Prefix: - Source: Specify the source identifier for the alerts (e.g., src-01). - Alias Prefix: Add a custom prefix for the alerts to organize notifications (e.g., aliasprefi). 4. Set Alert Priority Levels: - Choose a priority level from the dropdown menu: - P1 Critical: Highest priority for critical incidents. - P2 High: High priority for major incidents. - P3 Moderate: Moderate priority for less urgent issues. - P4 Low: Low priority for minor issues. - P5 Informational: Lowest priority for informational alerts. 5. Save Configuration: - Once all fields are completed, click on Save Config to apply the changes. Note on Opsgenie Plans If you're using Opsgenie's Free or Essentials plan or if you’re using Opsgenie with Jira Service Management's Standard plan, you can only add this integration from your team dashboard. The Integrations page under Settings is not available in these plans. Steps to add the integration: - Go to Teams and select your team. - Select Integrations from the left navigation menu, then choose Add Integration. Benefits of Using Opsgenie - Customizable Alert Management: Tailor the priority of alerts to match the severity of network events. - Centralized Notifications: Integrate with Opsgenie to consolidate alerts from multiple sources. - Enhanced Team Coordination: Alerts sent to Opsgenie can trigger workflows, ensuring incidents are assigned and resolved efficiently.

Last updated on Jan 22, 2025

Management of FlowSpec with FNM Manager PRO

Management of FlowSpec with FNM Manager PRO The use of FlowSpec in FNM Manager PRO allows network administrators to configure and manage traffic mitigation rules efficiently through an intuitive web interface. This functionality is designed to simplify the implementation of advanced configurations without the need for command-line usage. FlowSpec Configuration in the Web Panel Enabling FlowSpec 1. Navigate to the BGP, FlowSpec & Scrubbing section in the main menu of the panel. 2. Enable the Enable Flow spec Support option to activate the FlowSpec functionality across the configuration. Configuring BGP Peers 1. In the same section, configure the BGP peers by clicking on the Edit Peer BGP option. - Enter the necessary information, such as Local Address, Local ASN, Remote Address, and Remote ASN. - Enable the Enable ipv4_flowspec and Enable ipv6_flowspec options to support FlowSpec. - Save the changes by clicking on Save BGP Peer. Advanced FlowSpec Options In the Flow Spec Settings section, several advanced options are available to customize the behavior of FlowSpec: - Enable mitigations per each hostgroups: Allows applying specific mitigations at the hostgroup level. - Threshold specific ban details: Activates advanced logic that applies rules based on traffic crossing defined thresholds. - Options to exclude specific fields from FlowSpec rules, such as: - flow_spec_do_not_process_ip_fragmentation_flags_field - flow_spec_do_not_process_length_field - flow_spec_do_not_process_source_address_field - flow_spec_do_not_process_tcp_flags_field These options are useful to adapt to limitations of different hardware vendors and optimize performance. Check your vendor’s documentation for the specific configuration required for your device. Actions and Traffic Limits - In the panel configuration, you can define the default action for FlowSpec rules (e.g., discard, rate-limit, accept). - If you select rate-limit, specify the speed limit in bytes per second in the corresponding field. Activation by Hostgroups 1. To enable FlowSpec for specific groups, navigate to the desired hostgroup configuration. 2. Enable the Enable bgp_flow_spec for this hostgroup option. 3. Save the changes to apply the configuration. Custom FlowSpec Rules FNM Manager PRO allows the creation of custom FlowSpec rules through its Custom FlowSpec Rules section. This functionality gives administrators the flexibility to configure specific rules according to network needs and apply them in various ways. Creating and Publishing Rules 1. In the web panel, navigate to Block Manager > Create Custom FlowSpec Rules (PRO). 2. Fill in the required fields to define a custom rule: - Source Prefix and Destination Prefix: Enter prefixes with their CIDR mask. - Source Port and Destination Port: Define the source and destination ports. - Protocol: Select the relevant protocol (e.g., UDP, TCP). - Fragmented: Specify whether to include fragmented packets. - Packet Lengths and TCP Flags: Configure packet lengths and TCP flags as appropriate. - Action Type: Choose the action to take (e.g., discard, rate-limit). 3. Optionally, you can: - Save the rule in the database for future activation. - Publish the rule directly through BGP. Rule Validation The flow_spec_execute_validation option validates the source and destination prefixes entered in the rules to ensure they comply with requirements, such as being declared in the networks list. This option can be disabled in scenarios where custom rules need to be created without validation restrictions, keeping in mind that this might increase the risk of configuration errors. Activating Saved Rules From the Saved FlowSpec Rules section, previously saved rules can: - Be published directly via the web panel by clicking the Resend All option. - Be activated through integrations such as Telegram Bot Manager using the /flowspec command, enabling efficient and flexible remote control. Considerations - Verify that your routers support FlowSpec and configure the necessary AFI capabilities. - The panel configurations are compatible with most router vendors, including Cisco, Juniper, and Huawei. With these options, FNM Manager PRO offers complete and flexible control over FlowSpec rules, facilitating attack mitigation and the management of malicious traffic.

Last updated on Jan 22, 2025

Migrating from Debian or CentOS to Ubuntu 22.04 for FNM Manager

Migrating from Debian or CentOS to Ubuntu 22.04 for FNM Manager If you’re running FastNetMon on a Debian or CentOS server and need to migrate to Ubuntu 22.04 to meet the requirements for FNM Manager, this guide will walk you through the steps. The migration process involves creating a backup, setting up Ubuntu 22.04, reinstalling FastNetMon and FNM Manager, and restoring the backup. Step 1: Backup FastNetMon Configuration Before starting the migration, back up the current FastNetMon configuration on your existing server by running the following command in the shell: sudo fcli export_configuration fastnetmon_backup.tar This will generate a backup file named fastnetmon_backup.tar. Save this file securely, as it will be used to restore the configuration on the new server. Step 2: Install Ubuntu 22.04 Perform a fresh installation of Ubuntu 22.04 on the new server using the standard installer. Ensure the server is properly configured with the required network and system settings. Step 3: Install FastNetMon and FNM Manager Once Ubuntu 22.04 is installed, set up FastNetMon and FNM Manager using a full installation process. Follow the detailed steps provided in the official installation guide: FastNetMon and FNM Manager Installation Guide Step 4: Restore FastNetMon Configuration After installing FastNetMon and FNM Manager, restore the configuration from the backup file. 1. Clear the existing FastNetMon configuration: sudo fcli create_configuration 2. Remove the default global hostgroup: sudo fcli delete hostgroup global 3. Import the backup configuration: sudo fcli import_configuration fastnetmon_backup.tar Step 5: Reconfigure FNM Manager With the restored FastNetMon configuration, reconfigure FNM Manager to synchronize with the current setup: fnm_cli --setup_fnm_api Step 6: Register the FNM Manager License To complete the setup, register your FNM Manager license using the following command: fnm_cli --register_license --voucher="YOUR_LICENSE_CODE" --name="YOUR_COMPANY_NAME" --email="YOUR_EMAIL" Once the license is successfully registered, you can access the FNM Manager panel by opening a web browser and navigating to: https://YOUR_SERVER_IP:8081 Log in to verify that everything is functioning correctly. For additional details on the registration process, refer to the installation guide. Summary This migration process ensures a seamless transition to Ubuntu 22.04 while preserving your existing FastNetMon configuration. By following these steps, you can quickly set up your environment and continue managing your network effectively with FNM Manager.

Last updated on Jan 22, 2025