Starting an IGMP test
The IGMP test sends join messages to the device under test (DUT), such as a router or firewall, and the DUT forwards the data stream from the server.
Before starting an IGMP test:
Configure a multicast firewall with multicast-routing protocols. The following shows an example configuration using FortiGate.
FG1K5D3I14801425 # get system settings | grep multicast
multicast-forward : enable
multicast-ttl-notchange: disable
gui-multicast-policy: enable
FG1K5D3I14801425 # get router multicast | grep routing
multicast-routing : disable
FG1K5D3I14801425 # show firewall multicast-policy
config firewall multicast-policy
edit 1
set srcintf "port35"
set dstintf "port33"
set srcaddr "host-19-1-1-100"
set dstaddr "m-226-1-2-3"
next
end
To start an IGMP test:
- Go to Cases > Performance Testing > Protocol > IGMP to display the test case summary page.
- Click + Create New to display the Select case options dialog box.
- In the popup dialog, for the Network Config option, select the network template you have created in Cases > Security Testing > Objects > Networks. Then the network related options will automatically be filled. See Using network configuration templates for how to create a network template.
- Select a Certificate Group if applicable.
- Click OK to continue.
- Configure the test case options as described below.
- Click Start to run the test case.
FortiTester saves the configuration automatically so you can run the test again later. You can also click Save to save the test case without running it.
While the test case is running, use the following command on your FortiGate firewall to see the multicast session:
FG1K5D3I14801425 # diagnose sys mcast-session list
Tip: You can also copy an existing case, and change its settings to create a new case. In the case list, click Clone to clone the configuration. Only the case name is different from the original case. |
Settings | Guidelines |
---|---|
Basic Information | |
Name | Specify the case name, or just use the default. The name appears in the list of test cases. |
Ping Server Timeout | If a FortiTester connects to a DUT via a switch, the switch might cause a ping timeout, resulting in the test case failing to run. If this occurs, increase the timeout. The default is 15 seconds. The valid range is 0 to 600. Note: You can disable this end-to-end connectivity test by entering a setting of 0. If the DUT is unable to return packets, it is recommended you do so. |
Number of Samples | Select the number of samples. The default is 20, which means the web UI will show the last 20 sample data (about 20 seconds) in the test case running page. You can select 20, 60, or 120. |
Script Config |
Select the script that will run before/after the test. To create a script, see Using script object templates. |
Steady Duration | Specify the test duration. The default is 10 minutes. The test stops automatically after the duration you specify. |
Stopping Status in Second | The maximum time out in seconds allotted for FortiTester to close all TCP connections after the test finishes. |
DNS Host Group |
Select the DNS host group to look up the IP address of a domain name. To create a DNS host group, see Creating DNS host group. |
DUT Monitor |
Select to monitor a FortiGate device under test (DUT). If selected, you can monitor the DUT from the DUT Monitor tab on the management interface. To create a DUT monitoring, see Using DUT monitoring. |
Network Settings If you have selected a network config template, the network settings automatically inherit the configurations in the template. See Using network configuration templates for the description of network settings. |
|
Load | |
Simulated Users |
Number of users to simulate. |
Server Profile | |
Case Server Port | The server port where the test case traffic arrives. |
Client Network | |
Network MTU | The maximum transmission unit size. |
Multicast IP | Specify a multicast IP. For the example FortiGate configuration shown above, the Muticast IP would be 226.1.2.3. |
Server Network | |
Network MTU | The maximum transmission unit size. |
Client Limit | |
Bandwidth | Bandwidth in Mbps. The default is 0, which means the device will send traffic as fast as possible. |
Packets per Second | Rate of the packets per second. The default is 0, which means the device will create transactions as fast as possible. |
Server Limit | |
Bandwidth | Bandwidth in Mbps. The default is 0, which means the device will send traffic as fast as possible. |
Packets per Second | Rate of the packets per second. The default is 0, which means the device will create transactions as fast as possible. |