HP Advanced Services zl Module with Microsoft® Windows Server® 2008 R2 Installation and Getting Started Guide

5-4
Troubleshooting
Gain Access to a Module that Has No Network Connectivity
Gain Access to a Module that Has No
Network Connectivity
Read this section if you cannot gain access to the headless server that is
running on your module.
Note You will find it easier to troubleshoot if you understand the differences
between the module’s three interfaces and how your server is using them.
Refer to “Module Interfaces” on page 2-1 in Chapter 2: “Getting Started.”
If the server is using Hyper-V, you should also understand how that feature
affects the interface functionality. “Module’s Behavior Based on Enabled and
Disabled Interfaces” on page 5-9 provides comprehensive information.
Before beginning more systematic troubleshooting, you can try these tips:
 Wait about a minute—The module’s HP Services Management Agent
(SMA) should automatically reenable the internal interface 2 (whether
disabled from the switch or the server side). Therefore, if your server has
its IP address on this interface, before troubleshooting further, you should
wait a minute and attempt to access the server again.
 Check the interface settings on the host zl switch—Verify that the
internal interface to which you are attempting to connect is enabled and
assigned to the correct VLAN in the HP zl switch CLI.
 Connect to the module’s management port and access the server
using RDP—If you have physical access to the HP zl switch in which the
module is installed, connect a management station directly to the man-
agement interface on the module’s front panel.
Assign your station an IP address in the same network as the management
IP address. If you do not know this address, you might be able to use the
module CLI to find it. (See Appendix E, “Command-Line Reference” for
commands.) The default address is 192.168.2.10/30, which means that
your management station requires IP address 192.168.2.9 255.255.255.252.
Initiate an RDP connection to the management IP address and log in. If
you have logged in as a domain user previously, the server might have
cached your credentials, allowing you to log in as a domain user now.
Otherwise, because the server has lost IP connectivity, you must log in as
a local administrator.