Depending on the IfgMode parameter in ntservice.ini the minimum interframe-gap is either interpreted as 10 ns steps or bytes. If IfgMode is set to NS the value will be rounded up or down to the nearest HW-supported value, which depends on the link speed. The default minimum gap is 0 ns. If the IfgMode is set to BYTE the value is written directly to the HW. More...

Depending on the IfgMode parameter in ntservice.ini the maximum interframe-gap is either interpreted as 10 ns steps or bytes. If the IfgMode is set to NS the value will be rounded up or down to the nearest HW-supported value, which depends on the link speed. The default maximum gap is the maximum HW-supported value. If the IfgMode is set to BYTE the value will be written directly to the HW. Setting the maximum interframe gap to 0, corresponds to disabling the check for maximum IFG. More...

TX power state on read and command on write. Controls laser power on/off on fiber SFP, XFP, SFP+ and QSFP+ modules. Note that not all modules support enable/disable of the laser. An error code is returned if not supported. More...

Examples

Depending on the IfgMode parameter in ntservice.ini the minimum interframe-gap is either interpreted as 10 ns steps or bytes. If IfgMode is set to NS the value will be rounded up or down to the nearest HW-supported value, which depends on the link speed. The default minimum gap is 0 ns. If the IfgMode is set to BYTE the value is written directly to the HW.

Examples

Depending on the IfgMode parameter in ntservice.ini the maximum interframe-gap is either interpreted as 10 ns steps or bytes. If the IfgMode is set to NS the value will be rounded up or down to the nearest HW-supported value, which depends on the link speed. The default maximum gap is the maximum HW-supported value. If the IfgMode is set to BYTE the value will be written directly to the HW. Setting the maximum interframe gap to 0, corresponds to disabling the check for maximum IFG.

Examples

TX power state on read and command on write. Controls laser power on/off on fiber SFP, XFP, SFP+ and QSFP+ modules. Note that not all modules support enable/disable of the laser. An error code is returned if not supported.

Examples

Host loopback position.
Applying host loopback has the effect that data sent from the host is looped back to the host on the same port regardless of, if a NIM (Network Interface Module) has been plugged in, and if a physical loopback has been applied. The link will therefore be reported as up despite that no NIM is present or that no physical link is present.
In general simultaneous host and line loopback is not allowed.
The available loopback positions are adapter dependent and applying a loopback position that is not supported will result in a returned error code by the API function. In general only the following values NtHostLoopback_e should be used.
Applying loopback along with settings that require PHY setup changes or applying these settings when already in loopback mode represents a conflict and will not be carried out. A returned error code will indicate this. In order to avoid conflicts, it is in general recommended to enable loopback separately.
When applying loopback special settings are used and for trispeed modules this means that the link speed is changed to maximum. The original settings are restored when loopback is removed.

Examples

Line loopback position.
Applying line loopback has the effect that data sent from the line is looped back to the line on the same port. This requires that a NIM (Network Interface Module) has been plugged in. The link will in general be reported as up and traffic can be received by the host but any traffic transmitted by the host will be replaced by the traffic looped back. In general simultaneous host and line loopback is NOT allowed.
The available loopback positions are adapter dependent and applying a loopback position that is not supported will result in a returned error code by the API function. In general only the following values NtLineLoopback_e should be used.
Applying loopback along with settings that require PHY setup changes or applying these settings when already in loopback mode represents a conflict and will not be carried out. A returned error code will indicate this. In order to avoid conflicts, it is in general recommended to enable loopback separately.
When applying loopback special settings are used and for trispeed modules this means that the link speed is changed to maximum. The original settings are restored when loopback is removed.

Examples

Port identification state. Turns the port identification feature on/off. An error code is returned if not supported. When enabled the port led will start to blink regardless if the link is up or the port receives data or not.

Set TX port replication.
An error code is returned if not supported or the configuration is invalid. When set to a different port it will replicate all TX traffic from that port. It will not be possible to transmit on this port when replication is activated. It is not possible to change the replication configuration while TX traffic is active on this port or the port it is replicating from.

Set Tx port rate limit in bits per second.
A value of zero disables the Tx port rate limit. The resulting ports speed will be an aproximated value close to the specified value. An error code is returned if not supported or the configuration is invalid. Special case: a value in the range of 1 to 100 specifies a limit as percentage of the link speed.