This problem is related to the network environment settings. Specifically, it is necessary to set the gateway according to the on-site environment. Please refer to "Setup Method for Dual Network Cards to Connect to Internal and External Networks at the same time"
https://console.box.lenovo.com/l/u1Fbef
Refer to "One-way transmission network card test and packet loss problem solution"
https://console.box.lenovo.com/l/Yo7VYY
Refer to "NetSwitchTeam Network Aggregation Tutorial" for operation
https://console.box.lenovo.com/l/UJY1Fa
You can first refer to the "Camera Frame Loss Troubleshooting Method" to troubleshoot the cause. If you cannot solve it, please contact our FAE for assistance.
https://console.box.lenovo.com/l/q5W9IY
Does the network card support DPDK?
Products currently in mass production can basically support DPDK. For details, please refer to the product specifications of the corresponding models;
Generally, the iperf tool software can be used for testing on the system platform. For specific usage methods, parameter selection, etc., please refer to the official website.
Under the Linux system, you can use the command to identify: ethtool –p ethX; the indicator light of the corresponding port will flash;
Under the Windows system, you can open the configuration tool - Intel PROSet Adapter Configuration Utility after installing the complete driver, click 'Identify Adapter' - 'Start Flashing', and observe which port's indicator light on the network port flashes to indicate the corresponding port.
The 100G network card (Intel E810 master) has the FEC function enabled by default. The switch and network card need to be set to the same FEC mode before they can be connected.
Check whether the network card supports 4x25G mode. If it does, switch to 4*25G mode and use a 1/4 cable to connect; if it does not support it, it cannot;
The problem lies in whether the network card supports 4x10G mode. If it does, you can use a 1/4 cable to switch modes. If it doesn't, you can't.
By looking at the port name: ifconfig –a
Check the transceiver queue of the network card: ethtool -I network port name.
By looking at the port name: ifconfig –a
Check the buffer size: ethtool -g network port name
Set the buffer size: ethtool -G network port name tx/rx required buffer size.
When conducting high-speed rate testing, it is generally necessary to increase the size of the sending and receiving buffers of the corresponding ports.
PCIe x4 network cards can be used in x8 slots; PCIe x1 bus width network cards can be used in PCIe x1, PCIe x4, PCIe x8, PCIe x16 slots; PCIe x8 network cards can be used in PCIe x8, PCIe x16 slots use;
1. Too many software programs are installed and running on the computer, causing too many computer resources to be occupied, which affects the computer's running speed and is relatively slow;
2. There are too many junk files in the computer operating system and too many disk fragments, which affect the reading and writing of hard disk data;
3. There is a problem with the local connection settings (IP settings, DNS settings, etc.);
4. Gigabit causes slow connection during the process of adapting to 100M or 10M.
1. Please turn off the firewall of the computer systems at both ends of the connection;
2. If you are running a Linux operating system, please confirm whether other ports of the network card are connected and are in the same network segment/gateway. At this time, you can modify the test network segment to facilitate testing or change it to automatic acquisition.
3. You can ping the network card IP to check whether the driver is installed correctly (or ping 127.0.0.1 locally).
Since some drivers depend on specific patch installation packages, just install the appropriate patch. As mentioned in the title, if it is a 64-bit operating system, you need to install the KB3033929 patch; if it is a 32-bit system, install the corresponding KB3033929 patch; for a 64-bit system, install the 64-bit KB3033929 patch. The problem can be solved by installing the driver again after installing the patch.
Since some drivers depend on specific patch installation packages, just install the appropriate patch. As mentioned in the title, if it is a 64-bit operating system, you need to install the KB3033929 patch; if it is a 32-bit system, install the corresponding KB3033929 patch; for a 64-bit system, install the 64-bit KB3033929 patch. The problem can be solved by installing the driver again after installing the patch.
The power supply at the network card end is +12V, and the output voltage at the POE end is 48~57V.
The power supply at the network card end is+12V, and the output voltage at the POE end is 48-57V.
1. Check whether the network card speed and working mode are specified (change to auto-negotiation or a speed mode that both ends can support);
2. Whether the rate of the peer device matches the network card. The electrical port network card defaults to auto-negotiation mode and will adapt to the lowest rate at both ends;
3. Check whether the twisted pair cables comply with regulations, whether they are correctly wired, and check the cable quality (for example, 10G uses network cables of Category 6e or above or above, etc.);
4. If it is a multi-port network card, set the speed and working mode of two network ports to auto-negotiation, and use a confirmed cable to directly connect the two network cards to see if the speed is normal.
There are many factors that affect the copy speed between machines, such as the hard disk read and write speeds at both ends of the connection, platform processing capabilities, file types, and intermediate node forwarding capabilities; even the operating system will have an impact. You can use the network card to test directly. Use tools such as Iperf to test the speed of the network.
1. Check whether the network card speed and working mode are specified (change to auto-negotiation or a speed mode that both ends can support);
2. Whether the rate of the peer device matches the network card. The electrical port network card defaults to auto-negotiation mode and will adapt to the lowest rate at both ends;
3. Check whether the twisted pair cables comply with regulations, whether they are correctly wired, and check the cable quality (for example, 10G uses network cables of Category 6e or above or above, etc.);
4. If it is a multi-port network card, set the speed and working mode of two network ports to auto-negotiation, and use a confirmed cable to directly connect the two network cards to see if the speed is normal.
There are many factors that affect the copy speed between machines, such as the hard disk read and write speeds at both ends of the connection, platform processing capabilities, file types, and intermediate node forwarding capabilities; even the operating system will have an impact. You can use the network card to test directly. Use tools such as Iperf to test the speed of the network.
1. Too many software programs are installed and running on the computer, causing too many computer resources to be occupied, which affects the computer's running speed and is relatively slow;
2. There are too many junk files in the computer operating system and too many disk fragments, which affect the reading and writing of hard disk data;
3. There is a problem with the local connection settings (IP settings, DNS settings, etc.);
4. Gigabit causes slow connection during the process of adapting to 100M or 10M.
Refer to the "Troubleshooting Method for Network Card Bandwidth Test Substandard" to troubleshoot the reasons.
https://console.box.lenovo.com/l/nuNV1Q
Please refer to "vmware ESXI Network Card Support List Query Tutorial" to query, or you can query on the ESXi site;
https://console.box.lenovo.com/l/boX2Xp
At present, the board card products developed and produced by our company follow the standard interface specifications and are suitable for (X86) slots that use the standard PCI or PCIe protocol, as long as the slots can be used. For network security motherboards or customized motherboards, please check the specific specifications manual to determine.
If the product encounters platform adaptation questions (such as domestic platforms, etc.), check the product specifications of the corresponding model, or contact our business personnel or FAE for answers.
Most of the above prompts appear because the kernel-headers package and kernel-devel package are not installed on the operating system; or the installed kernel-headers package and kernel-devel package do not match the currently running Linux kernel version. It can be installed through online upgrade + online installation.
You need to check the details actually. Different images may not have drivers or not. You can check the network port under the system to determine the details. If you can see the network port, it means that the driver is already included.
(For Windows systems, go to the Device Manager or go to "Control Panel\Network and Internet\Network Connections" to check whether there is network information;
Under Linux systems, you can use the lspci | grep -eth command to check whether there is information about the corresponding network card. )
You can check directly on Synology’s official website based on your own NAS model or the NAS model you want to purchase. The compatibility query address on Synology’s official website is:
https://www.synology.cn/zh-cn/compatibility?search_by=category&category=network_interface_cards&p=1&change_log_p=1
Please refer to product specifications.
At present, the board card products developed and produced by our company follow the standard interface specifications and are suitable for (X86) slots that use the standard PCI or PCIe protocol, as long as the slots can be used. For network security motherboards or customized motherboards, please check the specific specifications manual to determine.
If the product encounters platform adaptation questions (such as domestic platforms, etc.), check the product specifications of the corresponding model, or contact our business personnel or FAE for answers.
1. Check whether the network port is disabled. (For Windows, you can check the Device Manager or "Control Panel\Network and Internet\Network Connections"; for Linux systems, you can use the IP -a command to check whether the status of the network card is up.)
2. Check whether the connection of the network cable is defective (replace with a new network cable for verification test);
3. Whether the equipment at the other end is defective (including system, network port, etc.);
4. Check whether the connection rates at both ends match (generally the default is adaptive);
5. Replace the network card and check whether the individual network card is defective.
1. It is necessary to verify that the speed of the optical fiber equipment at both ends is consistent (use the same brand and model of optical fiber modules);
2. It is necessary to verify that the speed of the optical fiber modules at both ends matches the speed of the equipment at both ends (use the same brand and model of optical fiber modules);
3. The optical fiber modules at both ends have the same wavelength and the same speed (use the same brand and model of optical fiber modules);
4. The optical fiber modules used do not match (usually occurs on single-mode single-fiber connection links. The optical fiber modules at both ends use the same model, causing the connection to fail. The parameters of one end are: TX 1550nm RX 1310nm, and the parameters of the opposite end need to be :TX 1310nm RX 1550nm);
5. The sequence of the optical fiber jumper must be correct (generally the connection method for SFP dual-fiber is: A's sending to B's receiving, A's receiving to B's sending);
6. The optical fiber module is compatible with optical fiber equipment (it involves the compatibility of various manufacturers. The best method at present is to inquire and confirm whether it is compatible before purchasing);
7. Check whether the optical module or cable is defective through cross testing (such as moving the normally used optical fiber cable to the doubtful board to confirm).
1. Need to verify that the speed of the fiber optic equipment on both ends is consistent (using fiber optic modules of the same brand and model);
2. Need to verify that the speed of the fiber optic modules at both ends matches the speed of the equipment at both ends (using fiber optic modules of the same brand and model);
3. The wavelength and speed of the fiber optic modules at both ends are the same (using fiber optic modules of the same brand and model);
4. The fiber modules used do not match (usually appearing on the connection link of single-mode single fiber, where the fiber modules at both ends use the same model to prevent connection, with one end having parameters of TX 1550nm RX 1310nm and the other end having parameters of TX 1310nm RX 1550nm);
5. The fiber optic jumper wire sequence needs to be correct (the general connection method for SFP dual fiber is: A sends to B receives, A receives to B sends);
6. Fiber optic modules are compatible with fiber optic equipment (which involves compatibility with various manufacturers. Currently, a better method is to consult and confirm compatibility before purchasing);
7. Conduct cross testing to identify any defects in the optical module or cable (such as moving the normally used fiber optic cable to a suspicious board to confirm).
Confirm where the exclamation point appears:
1. An exclamation mark appears in the network connection at the bottom right foot. You need to check whether the router is connected to the operator's network. Change the network settings to automatic acquisition (DHCP). At the same time, you need to check the whitelist settings of the router.
2. If it appears under "Ethernet Controller", the driver has not been installed yet. Just install the corresponding network card driver;
3. Appear under "Network Adapter", disable the network port with the exclamation mark, and then enable it;
4. If it is a fiber-optic network card, pull out the fiber-optic module first, then disable-enable it, and then insert the fiber-optic module. If an exclamation mark appears after plugging in the fiber-optic module, it means there is a compatibility issue between the fiber-optic module and the network card, and a compatible fiber needs to be replaced. module.
5. You can contact FAE for support.
Check whether PXE is displayed multiple times during the boot process. This will prolong the boot time due to the PXE self-test time. Some motherboards can disable PXE in the motherboard's BIOS, set the system disk as the first startup item, and disable other enablements. item.
1. Determine whether the hardware cannot be recognized or the driver is not installed (Windwos system can check and confirm under ‘Device Manager-Network Adapter/Other Devices’).
2. Prevent the slot from being unrecognizable due to poor contact caused by oxidation (install the network card and plug it in and out two or three times when the power is turned off, and then install it again).
3. Verify that the corresponding installed slot is PCIe protocol, not SATA protocol (since the Mini PCIe slot and Msata slot have the same appearance or are shared, you can check the motherboard's specification sheet or check the motherboard's silk screen. The printed MPCIe is PCIe, the one with MSATA is SATA)
1. In Windows system, enter the device manager and check if there is an 'Ethernet controller' in 'Other Devices'. If so, it means that the hardware has been recognized and the driver has not been installed yet. Just install the driver;
In Linux systems, use the lspci | grep -eth command to check whether there is a card corresponding to the chip. If so, it means that the hardware has been recognized and the driver has not been installed. Just install the driver.
2. Is the network card installed in the wrong slot (for example, the network card of the PCIe interface is installed in the PCI slot, just correct it);
3. On a multi-channel CPU server, when the CPU is not full, the network card happens to be installed in the slot that is not controlled by the CPU. At this time, it needs to be replaced with the corresponding slot of the CPU that is installed and working normally. (by changing the slot);
4. Caused by poor contact of the gold finger (the device is powered off, reinstall the board, plug and unplug the slot two or three times, and then fix the network card);
5. Plug the network card into another motherboard for testing and verification to check whether the network card is defective.
1. In the Windows system, enter the Device Manager and check if there is an Ethernet controller in "Other Devices". If there is, it indicates that the hardware has been recognized and the driver has not been installed yet. Simply install the driver;
Linux system uses the lspci | grep - eth command to check if there is a card corresponding to the chip. If there is, it indicates that the hardware has been recognized and no driver has been installed. Simply install the driver.
2. Is the network card installed in the wrong slot (for example, if the PCIe interface network card is installed in the PCI slot, correct it);
3. On a multi CPU server, when encountering an underfilled CPU, the network card happens to be installed in the slot without CPU control. At this time, it needs to be replaced with the corresponding slot of the CPU that is already installed and working properly. (by replacing the slot);
4. Poor contact with the golden finger (caused by power failure of the device, reinstalling the board and performing two or three insertion and removal operations on the slot before fixing the network card);
5. Insert the network card into another motherboard for testing and verification to check if the network card is faulty.
