This dialog sets the global settings for the connections between LANconfig and the devices:
- Network
- If a number of frequently changing devices share the same IP address in your network, then you should activate the option Always clear ARP cache before IP communication to ensure that your computer can communicate with these devices.
- Protocols
-
The transfer of configuration data when working with LANconfig can be handled by various protocols: HTTPS, SSH, HTTP
or TFTP.
Widely available protocols are defined globally. In addition, it is possible to disable protocols for specific
devices. However, it is not possible to re-enable a globally disabled protocol for individual devices as the global
communication settings take precedence over the device-specific settings.
The configuration of the communication protocols differentiates between the protocol strictly for testing the device
and the protocols for other operations, such as firmware uploads, etc.:
- HTTPS, SSH, HTTP, TFTPWhen this is selected, you enable the individual protocols for the operations firmware upload, configuration up/download, and script up/download. In these operations, LANconfig attempts to use these protocols in the order HTTPS, SSH, HTTP and TFTP. If the transfer fails when using one of the selected protocols, LANconfig automatically tries the next protocol.
- Prefer checks via TFTPThe device evaluation only transfers small amounts of data with the system information. As such, it makes sense to perform device checks in the LAN by TFTP protocol. When this option is activated, LANconfig first uses the TFTP protocol to check the device, regardless of the communication protocols set previously. If the check via TFTP fails, then LANconfig attempts the protocols HTTPS, SSH, and HTTP.
- SSH authentication
- If you have selected the SSH protocol, you can alternatively perform the authentication via a private key. In this case, the authentication dialog for password entry is not invoked. If you select Use public key authentication, enter the path to your private key file into the field, and, if necessary, the passphrase that you used to encrypt the file. Load the corresponding public key with LANconfig or WEBconfig onto each device.For detailed instructions about configuring the public-key authentication for your devices, see chapter SSH authentication using a public key.
- Concurrent RAS device connections
-
The number of concurrent RAS connections can be restricted. This makes sense where a limited number of physical RAS
channels is available, or where extreme loads on the system or network should be avoided.
If an action causes the number of RAS connections to exceed this limit, then the surplus actions are placed in a
queue and are only started when a RAS channel becomes available.
If you do not place a limit on the number, or you allow a higher number of connections than those physically
available, then the surplus actions are placed in a queue as mentioned above.
Note: This option can minimize the effects that a large number of concurrent actions can have on the system or network load.Note: If you do not limit the number and sufficient resources are available, then there is no limit on the system load or network load generated!
- Concurrent IP device connections
-
The number of concurrent IP connections can be restricted. This makes sense where a limited number of physical
channels is available, or where extreme loads on the system or network should be avoided.
If an action causes the number of IP connections to exceed this limit, then the surplus actions are place in a queue
and are only started when a logical IP channel becomes available.
If you do not place a limit on the number, or you allow a higher number of connections than those physically
available, then the surplus actions are interrupted with an error
Note: This option can minimize the effects that a large number of concurrent actions can have on the system or network load.Note: If you do not limit the number and sufficient resources are available, then there is no limit on the system load or network load generated!
