Step 2. Make sure that the Ethernet cable is installed correctly.
• The cable must be securely attached at all connections. If the cable is attached but the problem
remains, try a different cable.
• If you set the Ethernet controller to operate at 100 Mbps or 1000 Mbps, you must use Category
5 cabling.
Step 3. Determine whether the hub supports auto-negotiation. If it does not, try configuring the integrated
Ethernet controller manually to match the speed and duplex mode of the hub.
Step 4. Check the Ethernet controller LEDs on the rear of the server. These LEDs can help indicate which
Ethernet port is experiencing a problem and help you islolate whether the problem might be with a
connector, cable, hub or the network adapter installed in the server.
• The Ethernet link status LED is lit when the Ethernet controller receives a link pulse from the hub.
If the LED is off, there might be a defective connector or cable or a problem with the hub.
• The Ethernet transmit/receive activity LED is lit when the Ethernet controller sends or receives
data over the Ethernet network. If the Ethernet transmit/receive activity is off, make sure that the
hub and network are operating and that the correct device drivers are installed.
Step 5. Check the network activity LED on the front of the server. The network activity LED flickers when
data is active on network connections from the LOM or ML2 network adapters. If the network
activity LED is off, make sure that the hub and network are operating and that the correct device
drivers are installed.
Step 6. Check for operating-system-specific causes of the problem, and also make sure that the operating
system drivers are installed correctly.
Step 7. Make sure that the device drivers on the client and server are using the same protocol.
If the Ethernet controller still cannot connect to the network but the hardware appears to be working, the
network administrator must investigate other possible causes of the error.
Troubleshooting by symptom
Use this information to find solutions to problems that have identifiable symptoms.
To use the symptom-based troubleshooting information in this section, complete the following steps:
1. Check the event log of the application that is managing the server and follow the suggested actions to
resolve any event codes.
• If you are managing the server from the Lenovo XClarity Administrator, begin with the Lenovo XClarity
Administrator event log.
• If you are using some other management application, begin with the Lenovo XClarity Controller event
log.
For more information about event logs, see “Event logs” on page 243)
2. Review this section to find the symptoms that you are experiencing and follow the suggested actions to
resolve the issue.
3. If the problem persists, contact support (see “Contacting Support” on page 273).
Power on and power off problems
Use this information to resolve issues when powering on or powering off the server.
• “Embedded hypervisor is not in the boot list” on page 252
• “The power button does not work (server does not start)” on page 252
251
Содержание ThinkAgile VX 4-Socket 4U Certified Node
Страница 6: ...iv User Guide for ThinkAgile VX7820 Appliance ThinkAgile VX 4 Socket 4U Certified Node ...
Страница 10: ...viii User Guide for ThinkAgile VX7820 Appliance ThinkAgile VX 4 Socket 4U Certified Node ...
Страница 69: ...Chapter 2 Server components 59 ...
Страница 76: ...66 User Guide for ThinkAgile VX7820 Appliance ThinkAgile VX 4 Socket 4U Certified Node ...
Страница 96: ...86 User Guide for ThinkAgile VX7820 Appliance ThinkAgile VX 4 Socket 4U Certified Node ...
Страница 252: ...242 User Guide for ThinkAgile VX7820 Appliance ThinkAgile VX 4 Socket 4U Certified Node ...
Страница 276: ...266 User Guide for ThinkAgile VX7820 Appliance ThinkAgile VX 4 Socket 4U Certified Node ...
Страница 284: ...274 User Guide for ThinkAgile VX7820 Appliance ThinkAgile VX 4 Socket 4U Certified Node ...
Страница 295: ......
Страница 296: ......