Fortinet black logo

Step 4: Model the Device

Step 4: Model the Device

For the FortiNAC software to recognize the device, it must be added to Inventory either by prompting the FortiNAC software to discover the device or by adding it manually. Regardless of how the device is added, the FortiNAC software must be able to communicate with it.

  1. Under Network > Inventory add the device models. Use the chart below to determine which IP address to use when modeling the controller.

    Controller Configuration

    Model Using …

    Individual controllers (no redundancy)

    Controller IP

    Controllers in redundant configuration

    Active/Active (No VIP)

    IP of each controller

    Controllers in redundant configuration

    Active/Active (VIP)

    VIP

    Controllers in redundant configuration

    Active/Passive

    VIP

    See section Add or modify a device or Discovery in the Administration Guide for instructions.

    SNMP Settings: SNMP v1 or v3 credentials

    CLI Settings: Credentials used for CLI access.

    Note: If a “?” appears as the icon, then support needs to be added for that device. See KB article Options for Devices Unable to Be Modeled in Topology for instructions.

  2. Click the Polling tab in the right panel of the model.

  3. Set L2 (Hosts) Polling to 10 minutes. And click Save.

  4. Set the PerserveSSIDs device attribute. This prevents SSIDs already associated with the device model from being deleted should FortiNAC fail to read the SSIDs of the controller. When SSIDs are removed, corresponding SSID configurations and group memberships are also removed.

  5. Log into the CLI as root and type:

  6. device -ip <DEVICE_MODEL_IP> -setAttr -name PreserveSSIDs -value true

    Note: This attribute is not set by default.

Step 4: Model the Device

For the FortiNAC software to recognize the device, it must be added to Inventory either by prompting the FortiNAC software to discover the device or by adding it manually. Regardless of how the device is added, the FortiNAC software must be able to communicate with it.

  1. Under Network > Inventory add the device models. Use the chart below to determine which IP address to use when modeling the controller.

    Controller Configuration

    Model Using …

    Individual controllers (no redundancy)

    Controller IP

    Controllers in redundant configuration

    Active/Active (No VIP)

    IP of each controller

    Controllers in redundant configuration

    Active/Active (VIP)

    VIP

    Controllers in redundant configuration

    Active/Passive

    VIP

    See section Add or modify a device or Discovery in the Administration Guide for instructions.

    SNMP Settings: SNMP v1 or v3 credentials

    CLI Settings: Credentials used for CLI access.

    Note: If a “?” appears as the icon, then support needs to be added for that device. See KB article Options for Devices Unable to Be Modeled in Topology for instructions.

  2. Click the Polling tab in the right panel of the model.

  3. Set L2 (Hosts) Polling to 10 minutes. And click Save.

  4. Set the PerserveSSIDs device attribute. This prevents SSIDs already associated with the device model from being deleted should FortiNAC fail to read the SSIDs of the controller. When SSIDs are removed, corresponding SSID configurations and group memberships are also removed.

  5. Log into the CLI as root and type:

  6. device -ip <DEVICE_MODEL_IP> -setAttr -name PreserveSSIDs -value true

    Note: This attribute is not set by default.