SECUI MF2 Series

To add an MF2 device, complete the following steps.

Step 1: Configure the Device

FireMon strives to provide up-to-date product information, however we are not always aware when vendors change their device UI. If any Configure the Device procedure differs from your device version (UI location of fields, not information needed), please consult your device's user guide.

  1. On the SECUI MF2 device, add a user account for the Data Collector. You can complete this step in MF2 web UI.

    1. Log into MF2 Web UI with admin credentials.

    2. In the Navigation, go to System > Admin config > Admin > Add.

    3. Create a user from Add admin.

    4. Type the ID.

    5. Type the Password and Confirm Password.

    6. Type the Password Setting Period(days).

    7. Select an Access level.

      • Level 1 for monitoring.

      • Level 3 for change management (Policy Push).

    8. Other fields are optional.

    9. Click OK.

    10. Click Apply.

  2. Register the Data Collector to the administrator IP address.

    1. Log into MF2 Web UI with admin credentials.

    2. In the Navigation, go to System > Admin config > Admin IP > Add.

    3. Add the Data Collector’s IP address in Allowed IP address.

    4. Click OK.

    5. Click Apply.

  3. Syslog forwarding.

    1. Log into MF2 Web UI with admin credentials.

    2. In the Navigation, go to Monitoring > Monitoring Settings > Syslog settings.

    3. Syslog forwarding configuration in Server list section.

      1. Select the Enable checkbox.

      2. Type the IP address of the Data Collector.

      3. Type the Port number (keep default value 514 unless changed).

      4. Select local0 as a Function.

      5. Select WELF as a Format.

      6. Select the Protocol (keep default value UDP unless changed).

      7. Click Apply.

  4. Syslog forwarding configuration.

    1. Log into MF2 Web UI with admin credentials.

    2. In the Navigation, go to System > Interwork Server > Syslog settings.

    3. Create a syslog server in Server list section.

      1. Click the Enable checkbox.

      2. Type the IP address of the Data Collector.

      3. Type the Port number (keep default value 514 unless changed).

      4. Select local0 as a Function.

      5. Select WELF as a Format.

      6. Select the Protocol (Keep default value UDP unless changed).

      7. Click Apply.

    4. Syslog forwarding.

      1. In the Navigation, go to Monitoring > Monitoring Settings > Log settings.

      2. Enable System Log > Admin Log and Firewall Log > Firewall Allow Log & Firewall Deny Log by selecting the checkboxes for the syslog server configured above.

      3. Click Apply.

Step 2: Onboard the Device in the Administration Module

Contact FireMon Support to receive a specific device pack (a .jar file) if it was not included in the FMOS GA release. Review the steps to upload a device pack.

After onboarding, if you change any device settings, confirm that those updates were automatically applied to the discovered devices.

  1. On the toolbar, click Device > Devices.
  1. Click Create and then click SECUI > MF2 Firewall.
  1. General Properties section.

To prevent errors in device group-level device maps and incorrect reporting data, all devices added in Administration must have unique IP addresses. If devices with duplicate IP addresses must be added within a domain, it is strongly recommended that those devices be separated into discrete device groups, where no duplicate IP addresses are included in the same device group. Devices with duplicate IP addresses will cause errors in the All Devices device map, and may cause incorrect data in reports, even if they are in discrete device groups.

  1. In the Name box, type the name of the device as you want to see it in SIP.
  2. In the Description box, type an optional description of the device being added.
  3. In the Management IP Address box, type the IP address of the device.
  4. In the Data Collector Group box, select the IP address of the data collector group that will collect data from this device.
  5. In the Central Syslog Server box, select the syslog server from the list (optional).

Syslog fields are optional if the device uses the same IP for syslog and management.
A central syslog server is required only if syslog messages come from a different IP. A central syslog server must be created before it can be assigned to a device. To track usage via syslog, the device must support Level 3+.

  1. In the Syslog Match Names box, type the syslog match name (optional). You can enter multiple comma-separated names.
  2. By default, the Automatically Retrieve Configuration checkbox is selected.
  3. In the External ID box, type a unique identifier to be used when the device identifier is different than what is displayed in SIP.
  1. Collection Configuration is enabled on the management station or by duplicating and then editing the default configuration (Device > Collection Configuration). Default is what is set on the installed device pack.
  1. Device Settings section.

Credentials

  1. In the User Name box, type the user name used for the device.
  2. In the Password box, type the password used for the device.
  1. In the Re-enter Password box, retype the password entered above.
  2. In the Root Password box, type the CLI root password.
  3. In the Re-enter Root Password box, retype the password entered above.

Retrieval

  • By default, Protocol is SSH and the Port is 22.
  • By default, REST Port is 443.
  1. Monitoring section.

Log Monitoring

Select the Enable Log Monitoring checkbox to use for Rule Usage Analysis.

  • Track Usage Via is set to Syslog.
  • Log Update Interval is set to 10 (minutes); this number determines how often usage data is sent to the application server.

Change Monitoring

Select the Enable Check for Change checkbox to enable checking for configuration changes after the specified interval, and perform a retrieval is changes are detected.

  • Enter an optional Alternate Syslog Source IP.
  1. Retrieval section.

Scheduled Retrieval

Select the Enable Scheduled Retrieval checkbox to perform a retrieval at a set time regardless of change detection. This will activate additional fields to complete.

  • Set the Scheduled Retrieval Time to fit your requirements.

  • Select the Scheduled Retrieval Time Zone from the list.

Check for Change Retrieval

Select the Enable Check for Change checkbox to check for configuration changes after the specified interval and perform a retrieval if changes are detected. This will activate an additional field to complete.

  • The default Check for Change Interval time is 1440 minutes (every 24 hours). You can change the check interval time to best fit your requirements. The minimum required interval is 60 minutes (1 hour).

  1. Advanced section.
    • Select the Automatically Update SSH Keys checkbox if you want the data collector to automatically update the SSH key for a device when a conflict occurs.
    • Select the Enable Deprecated Ciphers and Algorithms checkbox to allow the use of weak SSH keys to extend the OpenSSH options with deprecated ciphers and algorithms for devices that cannot update the OS to a supported OpenSSH version.
  2. Enforcement Window section.

Select one of the available enforcement options:

  •  Allow All: All automation is allowed (enforcement, change, manual).

  • Manual Only: When selected all changes must be manually pushed for this device.

  •  Prevent All: No automation is allowed.

  • Window Only: Automation can only take place in the assigned enforcement window.

If this device is assigned to an enforcement or change window, it will be listed. If no assignment, changes must be manually pushed for this device.

  1. Supplemental Routes section.

Supplemental routes cannot be added until after a retrieval normalizes successfully. You can perform a manual retrieval before continuing.

  1. Click Add.

  2. Complete fields in the Add Supplemental Routes dialog box:

  • Select an Interface.

If you select an Interface, you will not need to select a virtual router and next virtual router. If no interface is selected, you will need to select a Virtual Router and Next Virtual Router.

  • Type the Destination IP address.
  • Type the Gateway IP address.
  • Select a Virtual Router.
  • Select a Next Virtual Router.
  • Switch the Drop toggle to enable (disabled = Accept).
  • Click Add.
  1. Click Save.

Step 3: Verify Communication

Because automatically retrieving a configuration is enabled by default, there is nothing for you to do. Security Manager will automatically attempt to retrieve a device configuration.

To do a manual retrieval, select the device row, click the Menu icon and then click Retrieve Configuration.

It may take up to 15 minutes to see the status result of the retrieval.