
Table 13 Known issues (continued)
ResolutionIssue
Do not create network teams until after the initial configuration tasks have
been completed. If a system is to be connected to a network where specific
Network teaming cannot be configured
during initial system configuration.
VLANs with VLAN tagging enabled (for example, for connecting to a domain
controller), it is recommended that the network switch be temporarily
configured to pass untagged network packets on the specific VLAN or to
configure the network interface properties to operate using the specific VLAN
ID. Configuring VLAN settings is accomplished by opening the properties
dialog for the network interface and then configuring the network adapter
by clicking on the Configure button.
This may be cause by having multiple interfaces on the same network subnet
as that used by the network interface names “Cluster Internal”. By default,
During initial system configuration, the
Initial Configuration Tasks window may
display the following message:
Connecting to remote server
169.254.2.111 failed with the
the Cluster Internal network uses an APIPA address (169.254.0.0/16). This
is the default subnet used by other network interfaces that are connected and
there is no DHCP server. This results in multiple network routes between
nodes.
Disable or disconnect network interfaces that are connected to networks
where no DHCP server is available. During the initial configuration you will
following error message: The
WinRM client cannot process
the request. If the
be given the opportunity to assign network addresses to other network
authentication scheme is
interfaces. After addresses are assigned the network interfaces can be
reconnected or enabled.
different from Kerberos, or
if the client computer is not
joined to a domain, then
HTTPS transport must be used
or the destination machine
must be added to the
TrustedHosts configuration
setting. Use winrm.cmd to
configure TrustedHosts. Note
that computers in the
TrustedHosts list might not
be authenticated.
You must upgrade the HP 1210m controller first and reboot the server. Then,
upgrade the disk enclosure firmware and it will succeed.
If the HP 1210m controller in the HP
StoreEasy 5000 Storage is running an
older version (1.56 or earlier) when you
perform a firmware upgrade, the
upgrade to the disk enclosure I/O
module will fail. The Firmware Update
Tool (FMT) will display the following
message: "Version not updated after
flash and reset of SEPxxxxxxxxxxxxxxx".
Set the system level proxy to explicitly bypass the HA file servers. For example,
instead of using the following command:
netsh winhttp set proxy myproxy.fabrikam.com:80
"<local>"
When attempting to use Failover Cluster
Manager to add a File Share to an HA
File Server on the cluster, the Add Share
wizard will not start.
Also, attempting to use Failover Cluster
Manager to view any existing shares on
set the proxy using a command like the following:
netsh winhttp set proxy myproxy.fabrikam.com:80
"<local>;*.fabrikam.com"
file servers in the cluster, just results in a
perpetual “Loading” message. This
happens when a system level HTTP proxy
In this example, “*.fabrikam.com” is the client access point used on the
HA file servers.
server is set. Some users will require a
system level proxy to make Cluster
Aware Updating work, but if one is set,
it is important to explicitly prevent access
to your HA file servers from using the
proxy.
The Storage Management Provider
displays the following error message:
0x26005054 The service failed
to subscribe for events
1. Open Add/Remove Programs and verify that HP Insight Management
Agents is installed.
2. If it is installed, open the Run dialog box and enter WBEMTEST and click
Connect.
3. Enter root\hpq as the namespace. Wait to see if the namespace
connects. If it does not connect, the WBEM installation is corrupt.
Known issues 51
Kommentare zu diesen Handbüchern