...
If the power and Ethernet indicators are off, check the integrity of the power supply, the Ethernet cables , and the RJ-45 connectors. Replace the power supply and the cables if necessary.
...
| Center | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
If the power indicator is on and there is connection via the Ethernet interface, connect to the device directly as it is shown in the scheme below. Make sure that the IP address of the PC is in the same subnet as the device's oneIP address of the device. You can restore the IP address and reset the device to the factory settings using the ERConsole utility.
...
If you were able to access the device by connecting directly, try to determine the possible reason for the unavailability through the network. Pay attention to the wired interface statistics. In order to do this, go to the "Device status" section of the web interface and open the "General statistics" window for the Ethernet interface in the "Interface statistics" section. Pay attention to the CRC errors number, as they indicate a violation of the data 's integrity during the transmission over the wired segment. Also, the problem can be caused by a queue overflow or an inappropriate frame size (Out of range).
...
If there is no access to the device's web interface, run the "ifconfig eth0" command to get statistics via the CLI.
The description of the parameters for a complete diagnostic is available in the "Ifconfig command (interfaces configuration)" article.
...
We recommend to set the auto-negotiation mode provided by the Ethernet standard. The problem can occur due to the connection between two devices with different duplex settings. For example, if one device is in auto-negotiation mode and the other is in fixed full duplex mode.