1,775
edits
Settings: Difference between revisions
no edit summary
No edit summary |
|||
| Line 86: | Line 86: | ||
Following settings are possible for PTP and should match to the settings of the PTP grandmaster: | Following settings are possible for PTP and should match to the settings of the PTP grandmaster: | ||
* Delay mechanism: Use end-to-end (E2E), peer-to-peer (P2P) or automatic delay measurement. In case automatic measurement is selected, E2E is used at the beginning and switched to P2P when a peer delay request is received. Default is | * Delay mechanism: Use end-to-end (E2E), peer-to-peer (P2P) or automatic delay measurement. In case automatic measurement is selected, E2E is used at the beginning and switched to P2P when a peer delay request is received. Default is '''Auto'''. | ||
* Network transport: Use UDPv4, UDPv6 or Layer 2 as network transport. Default is | * Network transport: Use UDPv4, UDPv6 or Layer 2 as network transport. Default is '''UDPv4'''. | ||
* Domain number: The domain number of the grandmaster. This is used to define logical groups of synchronized clocks. | * Domain number: The domain number of the grandmaster. This is used to define logical groups of synchronized clocks. | ||
| Line 146: | Line 146: | ||
* Max RX queues per socket: This setting specifies the amount of threads dedicated to read and write interactions with the network interface controllers. By increasing this value, network receive bandwidth can be increased before packet drops occur. By decreasing this value, data analysis will improve. The default setting of 2 RX queues is suitable for most configurations as data analysis typically needs much more processing ressources. | * Max RX queues per socket: This setting specifies the amount of threads dedicated to read and write interactions with the network interface controllers. By increasing this value, network receive bandwidth can be increased before packet drops occur. By decreasing this value, data analysis will improve. The default setting of 2 RX queues is suitable for most configurations as data analysis typically needs much more processing ressources. | ||
* Use Hyper-Threading for RX queues: This setting allows enabling or disabling Hyper-Threading for the threads dedicated to read and write interactions with the network interface controllers. By disabling it, network performance can be improved as the RX queues will be distributed to physical CPU cores only. By enabling it, RX queues will also be distributed to virtual Hyper-Threading CPU cores which is not as efficient as physical CPU cores. By using Hyper-Threading, data analysis will improve as there are more CPU cores available for these tasks. Hyper-Threading is used by default. This is suitable for most configurations as data analysis typically needs much more processing ressources. | * Use Hyper-Threading for RX queues: This setting allows enabling or disabling Hyper-Threading for the threads dedicated to read and write interactions with the network interface controllers. By disabling it, network performance can be improved as the RX queues will be distributed to physical CPU cores only. By enabling it, RX queues will also be distributed to virtual Hyper-Threading CPU cores which is not as efficient as physical CPU cores. By using Hyper-Threading, data analysis will improve as there are more CPU cores available for these tasks. Hyper-Threading is used by default. This is suitable for most configurations as data analysis typically needs much more processing ressources. | ||
* Preferred Network interface controller: This setting allows fine tuning of network and data analysis performance for dedicated network controllers. The selected set of network controllers will be preferred over the others. Usually the fastest or the network controller with the most traffic should be preferred. The | * Preferred Network interface controller: This setting allows fine tuning of network and data analysis performance for dedicated network controllers. The selected set of network controllers will be preferred over the others. Usually the fastest or the network controller with the most traffic should be preferred. The '''Auto''' setting is used by default, preferring the fastest network controller. | ||
You should only change these parameters in discussion with the Allegro Packets support. | You should only change these parameters in discussion with the Allegro Packets support. | ||
| Line 154: | Line 154: | ||
The processing performance may be modified on high-performance systems. This is only visible if your Network Multimeter is capable of changing this setting. | The processing performance may be modified on high-performance systems. This is only visible if your Network Multimeter is capable of changing this setting. | ||
* Processing performance mode: This setting allows for fine tuning processing performance. By using | * Processing performance mode: This setting allows for fine tuning processing performance. By using '''Analysing''', as much processing ressources on all CPUs as possible are used for data analysis. By using '''Capturing''', the focus will be on high data throughput and low latency for capturing purposes by using only the CPU where the preferred newtork controller is attached to. This has an impact on data analysis performance. '''Analysing''' is used by default. | ||
You should only change this parameter in discussion with the Allegro Packets support. | You should only change this parameter in discussion with the Allegro Packets support. | ||
| Line 365: | Line 365: | ||
The values required depend on the setup of the LDAP server. | The values required depend on the setup of the LDAP server. | ||
The user filter requires a | The user filter requires a '''%s''' as a placeholder for the username. | ||
The group filter requires either | The group filter requires either '''%s''' as a placeholder for the username, or any '''${value}''' attribute of the user. The special value '''${DN}''' references the distinguished name of the user. | ||
In the | In the '''Allegro MM users group''' and '''Allegro MM admins group''', a comma-separated list of the common name of the groups is given. If the user is in any of the groups, he is allowed to log in. If the user is in one of the admins group, he is treated as an administrator. | ||
Example for a simple LDAP setup involving only the username: | Example for a simple LDAP setup involving only the username: | ||