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. SECUI MF2 uses separate administrator accounts for CLI and Java GUI access. To connect with a data collector, it is required that you access it at the command line using your root account. To get a root account for CLI mode access into SECUI MF2, refer to your firewall administrator.
  2. To remotely access into SECUI MF2 using CLI or the Java web interface, the IP address of the data collector must first be registered. To register the IP address, do the following in SECUI MF2 web application:
    1. On the main menu, click System.
    2. Under Admin Configuration, click Admin IP.
    3. On the Admin IP tab, click the left button in top left corner to add an IP address.
    4. In the Add Admin IP dialog box, enter the following:
      • In the Allowed IP Address * field, enter the IP address of the Security Manager Data Collector.
      • Optional: In the Description field, enter a description.
    5. Click OK.
  3. To forward syslog data from SECUI MF2 device to the Security Manager Data Collector: 

    1. On the main menu, click Monitoring.

    2. Under Monitoring Settings, click Syslog Settings.
    3. On the Syslog Settings tab, do the following:
      • Select Enable.
      • In the Server IP (Domain) address field, enter the IP address.
      • In the Format field, choose WELF.
      • In the Description field, enter a description such as "FireMon."
    4. Click Apply.
  4. Verify that Monitoring is still selected.
  5. Under Monitoring Settings, click Log Settings. As administrator of the device, select the basic settings you want, and then click Apply.

Step 2: Add the Device in the Administration Module

  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 check box 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 dynamic superuser account.
  2. In the Password box, type the password used for the dynamic superuser account.
  1. In the Re-enter Password box, retype the password entered above.
  2. In the Root Password (SECUI OS v4 only) box, type the root password used for OS v4 device only.
  3. In the Re-enter Root Password box, retype the password entered above.

Retrieval

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

Log Monitoring

Select the Enable Log Monitoring check box 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 check box 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 check box 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 check box 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 check box 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 check box 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.