APEX AD10 Gigabit Ethernet Port#
Usage of Gigabit Ethernet#

Hardware Connection#
Pre-conditions
Identify the location of the Gigabit Ethernet port.
Verify the use of an RJ45 Ethernet cable.
Insert the desired Gigabit Ethernet port to be used.
Connect using an RJ45 Ethernet cable through a switch or directly to a router.
Function vs Device Node#
Function |
Device Node |
|---|---|
LAN1 |
eth0 |
LAN2 |
eth1 |
LAN3 |
eth2 |
LAN4 |
eth3 |
Ethernet problem troubleshooting#
Phenomenon 1: No communication after connecting the network port to the external device#
Solution:#
Verify the network cable status.
Connect the current network cable to another normal device (such as a laptop), configure an IP in the same network segment and try to ping each other.
If it can be pinged, proceed to “Phenomenon 2” to check the network interface configuration of the device.
If it cannot be pinged, replace the network cable.
Phenomenon 2: Multiple network interfaces cannot communicate with other devices simultaneously#
Solution:#
Check the network interface IP configuration 1) Log in to the device management interface (such as web settings or use the command ifconfig), and check whether all network interfaces are configured with IP addresses in the same network segment. 2) If there are IP addresses in the same network segment → Assign IP addresses in different network segments to each network interface (for example: 192.168.1.10, 192.168.2.10); 3) If there are no IP addresses in the same network segment → Enter “Phenomenon 3” to check the network card status.
Alternative solutions for multi - network interface communication 1) If multiple network interfaces need to use the same network segment, it needs to be achieved through gateway or bridge functions (you need to contact the network administrator for configuration).
Phenomenon 3: The network card cannot be recognized or there is an abnormality in obtaining an IP address.#
Solution:#
1、Check the network card status
1)Enter commands in the terminal to view network card information:
ifconfig
2)Network card not displayed → Re-plug the network cable and restart the device;
3)Still unable to recognize → Re-burn the system image (backup data before operation).
2、Verify the IP acquisition mode
1)DHCP mode: Ensure that the device is set to obtain an IP address automatically;
2)Static IP mode: Check whether the configured IP is consistent with the actual network segment.
Phenomenon 4: Unable to connect to the external network after inserting the network cable#
Solution:#
Verify the status of the network cable and the external network.
Connect the current network cable to other normal devices (such as a laptop).
If it can connect to the network normally → carry out the “Phenomenon 2” to check the device’s network card.
If it still cannot connect to the network → replace the network cable or check the external network connection status of the router/optical modem.
Phenomenon 5: The device cannot recognize the network card#
Solution:#
Check the status of the network card driver
1)Open the terminal and enter the following command to check if the network card exists (for example, eth0):
ifconfig
2)Network card not displayed → Re-plug the network cable and restart the device;
3)Still unable to recognize → Enter the “Phenomenon 3” repair system environment.
Phenomenon 6: Abnormal system environment#
Solution:#
Re - burn the system image.
Obtain the latest system image file from the device manufacturer and complete the burning (backup data before operation).
After burning, restore network connection → There is a software conflict in the original system.
If still unable to connect to the network → Execute “Phenomenon 4” to check the network configuration.
Phenomenon 7: Abnormal IP address configuration#
Solution:#
1、Verify the IP acquisition status
1)Enter the following command in the terminal to check if the IP address is normal (it should be in line with the actual network segment):
ifconfig
2)Enter the following command in the terminal to check if the IP address is normal (it should be in line with the actual network segment):
3)If it is a static IP, you need to manually adjust it to dynamic acquisition (DHCP).
4)If it is DHCP but an IP address has not been obtained, restart the router or contact the network administrator.
2、Configure default routes
If the IP is normal but you still can’t access the network, try to manually add the default gateway (replace with the actual gateway IP):
sudo route add default <gateway_ip>
Technical support#
If all of the above troubleshooting measures are ineffective:
Collect diagnostic logs
1)Run the log collection script in the terminal (an internet connection is required):
curl -sSL https://doc.miivii.com/scripts/run_miivii_diagnostic.sh | bash -s ethernet
2)Submit the generated log file to technical support.