Fortinet black logo

Handbook

Test Center

Copy Link
Copy Doc ID 6a43e9d7-b060-11ea-8b7d-00505692583a:957579
Download PDF

Test Center

You can join multiple appliances into a Test Center when throughput requirements are too high for a single FortiTester appliance to handle. In Test Center mode, some FortiTester appliances can act as clients and others act as servers, to provide more powerful capacity for performance testing.

Requirements and Restrictions

Tester Center supports at most 4 appliances or VMs:

  • In NAT or TP mode, you can configure at most 2 servers and 2 clients.
  • In Application mode, you can configure at most 4 clients.

The appliances or VMs can be different models, but based on the following conditions:

  • For all FortiTester-VMs they have to be properly licensed.
  • For all FortiTester-VMs, Center/Slave must have the same vCPU number, VM type, port number.
  • Software - Center/Slave must have the same major version number (e.g. 3.8.0 can run with 3.8.1 but NOT 3.7)
  • For 3000E, Center/Slave must have the same fanout mode (e.g. 3000E can break out 2 x 40G into 8 x 10G)
  • Center/Slave must be in the same group i.e.:
    • "2K": ["FTS_2000D", "FTS_2000E", "FTS_2500E"],
    • "3K": ["FTS_3000E"],
    • "4K": ["FTS_4000E"],
    • "VM": ["FTS_VM_KVM"],
    • "VM_ESXI": ["FTS_VM"],
    • "AWS": ["FTS_VM_AWS"],
    • "AWS_BYOL": ["FTS_VM_AWS_BYOL"],
    • "AZR_BYOL": ["FTS_VM_AZURE_BYOL"],
    • "OCI_BYOL": ["FTS_VM_OCI_BYOL"],
    • "GCP_BYOL": ["FTS_VM_GCP_BYOL"]

Configuring work mode settings

The work mode settings determine whether the FortiTester operates as a standalone appliance or is joined with other FortiTester appliances to form a Test Center.

By default, FortiTester appliances operate in Standalone work mode.

If your test plans require more interfaces than provided by a single FortiTester, you can join the appliances into what is called a Test Center. One appliance is the Test Center master appliance; the others are Test Center slaves. You manage test cases from the Test Center appliance management interface; the web UI is not available for an appliance in Test Slave work mode. When you enter the web UI address for the Test Slave appliance, it displays the following page instead.

Test Slave Mode

To set up a Test Center:
  1. Log into the web UI of one FortiTester (e.g. 172.22.4.217).
  2. Go to System > Work Mode.
  3. The appliance is in Standalone work mode by default.
  4. Select Test Center to make it the Test Center master. The Work Mode page shows current work mode of this appliance is TestCenter, and a table lists the appliances that are under control of this one.
  5. Log into another FortiTester (e.g. 172.22.4.218).
  6. Go to System > Work Mode.
  7. Select Test Slave.
  8. Enter the IP address of the Test Center master and click Connect.
  9. Return to the Work Mode page on the master and click Refresh. You will see 172.22.4.218 is in the table.
  10. Test Center
    You can click the Disconnect button in the slave Web GUI to return to Standalone mode.
    When the appliances have been added to the Test Center, you can select one or more FortiTester appliances to work as clients and others to work as servers when you create test cases. In this example, 172.22.4.217 has the client ports; 172.22.4.218 has the server ports. You can add up to four pairs of appliances to a Test Center.

  11. Configure Heartbeat Interval and Heartbeat Lost Threshold to manage the heartbeat traffic between center and slaves in Test Center mode.

Test Center

You can join multiple appliances into a Test Center when throughput requirements are too high for a single FortiTester appliance to handle. In Test Center mode, some FortiTester appliances can act as clients and others act as servers, to provide more powerful capacity for performance testing.

Requirements and Restrictions

Tester Center supports at most 4 appliances or VMs:

  • In NAT or TP mode, you can configure at most 2 servers and 2 clients.
  • In Application mode, you can configure at most 4 clients.

The appliances or VMs can be different models, but based on the following conditions:

  • For all FortiTester-VMs they have to be properly licensed.
  • For all FortiTester-VMs, Center/Slave must have the same vCPU number, VM type, port number.
  • Software - Center/Slave must have the same major version number (e.g. 3.8.0 can run with 3.8.1 but NOT 3.7)
  • For 3000E, Center/Slave must have the same fanout mode (e.g. 3000E can break out 2 x 40G into 8 x 10G)
  • Center/Slave must be in the same group i.e.:
    • "2K": ["FTS_2000D", "FTS_2000E", "FTS_2500E"],
    • "3K": ["FTS_3000E"],
    • "4K": ["FTS_4000E"],
    • "VM": ["FTS_VM_KVM"],
    • "VM_ESXI": ["FTS_VM"],
    • "AWS": ["FTS_VM_AWS"],
    • "AWS_BYOL": ["FTS_VM_AWS_BYOL"],
    • "AZR_BYOL": ["FTS_VM_AZURE_BYOL"],
    • "OCI_BYOL": ["FTS_VM_OCI_BYOL"],
    • "GCP_BYOL": ["FTS_VM_GCP_BYOL"]

Configuring work mode settings

The work mode settings determine whether the FortiTester operates as a standalone appliance or is joined with other FortiTester appliances to form a Test Center.

By default, FortiTester appliances operate in Standalone work mode.

If your test plans require more interfaces than provided by a single FortiTester, you can join the appliances into what is called a Test Center. One appliance is the Test Center master appliance; the others are Test Center slaves. You manage test cases from the Test Center appliance management interface; the web UI is not available for an appliance in Test Slave work mode. When you enter the web UI address for the Test Slave appliance, it displays the following page instead.

Test Slave Mode

To set up a Test Center:
  1. Log into the web UI of one FortiTester (e.g. 172.22.4.217).
  2. Go to System > Work Mode.
  3. The appliance is in Standalone work mode by default.
  4. Select Test Center to make it the Test Center master. The Work Mode page shows current work mode of this appliance is TestCenter, and a table lists the appliances that are under control of this one.
  5. Log into another FortiTester (e.g. 172.22.4.218).
  6. Go to System > Work Mode.
  7. Select Test Slave.
  8. Enter the IP address of the Test Center master and click Connect.
  9. Return to the Work Mode page on the master and click Refresh. You will see 172.22.4.218 is in the table.
  10. Test Center
    You can click the Disconnect button in the slave Web GUI to return to Standalone mode.
    When the appliances have been added to the Test Center, you can select one or more FortiTester appliances to work as clients and others to work as servers when you create test cases. In this example, 172.22.4.217 has the client ports; 172.22.4.218 has the server ports. You can add up to four pairs of appliances to a Test Center.

  11. Configure Heartbeat Interval and Heartbeat Lost Threshold to manage the heartbeat traffic between center and slaves in Test Center mode.