Usage
rules -type=IP [-ruleset={* | MAIN | <IP Rule Set>}] [-verbose]
[-schedule] [<rules>]...
Show IP rules.
rules -type={ROUTING | PIPE | IDP | THRESHOLD | IGMP} [-verbose]
[-schedule] [<rules>]...
Show a specific type of rules.
Options
-ruleset={* | MAIN | <IP Rule Set>}
Show a specified IP ruleset.
-schedule
Filter out rules that are not currently allowed by
selected schedules.
-type={IP | ROUTING | PIPE | IDP |
THRESHOLD | IGMP}
Type of rules to display. (Default: IP)
-verbose
Verbose: show all parameters of the rules.
<rules>
Range of rules to display. (default: all rules).
2.2.74. selftest
Run appliance self tests.
Description
The appliance self tests are used to verify the correct function of hardware components.
IMPORTANT: In order for a selftest result to be reliable the test must be run using a default
configuration and having the SGW disconnected from any networks.
IMPORTANT: Normal SGW operations might be disrupted during the test(s).
The outcome of the throughput crypto accelerator tests are dependent on configuration values.
If the number of large buffers (LocalReassSettings->LocalReass_NumLarge) too low, it might
lower throughput result. In the field 'Drop/Fail', the 'Drop' column contains the number of
packets that were dropped before ever reaching the crypto accelerator and the 'Fail' column
contains the number of packets that for some reason failed encryption. The 'Pkt In/Out' field
shows the total number of packets sent to, and returned from the accelerator.
The interface tests 'traffic' and 'throughput' are dependent on the settings for the NIC ring sizes
and possibly also license limitations. The 'traffic' test uses a uniform random distribution of six
packet sizes between 60 and 1518 bytes. The content of each received packet is validated. The
'throughput' test uses only the largest packet size, and does not validate the contents of the
received packets.
Example 2.13. Interface ping test between all interfaces
Chapter 2: Command Reference
79
Summary of Contents for NetDefend DFL-260E
Page 21: ...Chapter 1 Introduction 21...
Page 104: ...Chapter 2 Command Reference 104...
Page 240: ...Comments Text describing the current object Optional Chapter 3 Configuration Reference 240...
Page 317: ...Comments Text describing the current object Optional Chapter 3 Configuration Reference 317...
