Understanding testing basics

This section applies to all performance and security tests.

In v3.x/v4.x/v7.1, FortiTester configurations could only be exported from and imported to the same model. v7.2 removes this limitation.

Starting from v7.2+, FortiTester uses case ports, which separate the test case and physical ports. FortiTester decouples the test case and physical port, and allows test configuration(s) to be exported/imported freely between different models.

This feature is possible because of the following objects:

1. Port Mapping – maps Test Case ports to physical ports

2. Port Setting – consist of settings MAC masquerade, virtual router [optional], QinQ and subnet information

3. Network Object – which is a combination of port mapping and port setting

Pre-v7.2 test configuration

v7.2+ test configuration

Note: Pre-v7.2 test case configuration can be upgraded to use case ports settings. Default port mapping will be used after upgrade.

New - Port Mapping Objects (under Objects >> Port mapping)

V7.2 introduces concept of “case port”, which is used to map to a physical ports on FortiTester. This allows cases to exported and imported between DIFFERENT models, which was not possible before. This allows users to use same test cases between different hw/sw models.

Case port 1  map to physical port 1

Case port 2  map to physical port 2

After port mapping are saved, example below “port_mapping1”, this can be used under any performance test now, users can select port mapping here:

Note: users can also click a new icon to show the case port and physical port mapping relationship. “physical” port can also refer to port1-port4 of FTS VM also.

In v7.2 there are the following options in test case configuration:

- [NEW] Save Global port settings – this option saves port settings from current test config. This saves both client and server port settings. Note this settings only saves the ports selected (e.g. client side has two ports, will save port1 if selected)

- [EXISTING] Network Config – this option recalls saved network configuration (so users do not need to retype information such as subnets again), this option is in all FortiTester versions

- [NEW] Port Mapping – allow users to choose port mapping for particular use case. Port mapping can be reused in other cases

- [NEW] icon to display physical and case port relationship

Note: if users selects “default” in port mapping selection, case ports and physical ports mapping relationship will be set to N:N. e.g. case port1 = physical port1

New Port Settings configuration (Under Objects >> Port settings)

Note: port settings can be a ‘client side or server side only’ configuration , as follows:

New Networks Objects (Under Objects >> Network)

While looks similar to “port settings”, Network is a superset of port settings, consists of MAC masquerade, virtual router [optional], QinQ and Subnet information and CHOICE of port mappings (created earlier)

Note with export/import using case ports between different FortiTester models, there can be 3 scenarios:

1. Export & import into models with same ports – export/import will succeed, case will run

2. Export & import from FTS with LESS ports, to FTS with MORE ports (e.g. from FTS100F with 6 ports to FTS3000E with 8 ports (breakout 4 x 10G) - export/import will succeed and case will run.

3. Export & import from FTS with MORE ports, to FTS with LESS ports (e.g. from FTS3000E 8 port breakout configuration to FTS2500E with 4 ports - export/import will succeed, the following scenarios can happen:

a. If case ports 1-4 was used and imported, cases can be mapped and run on FTS2500E right away.

b. If case ports refers to port 5-8 (which FTS2500E does not have), case will import successfully, error will be prompted if case is run, users will need to remap case port to the physical port available on unit.