HP Integrity rx2800 HP Smart Update Manager User Guide - Page 101

Recovering from a discovery failure, Troubleshooting connection errors

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 101 highlights

The following is an example of the output trace in the OpMan.trace on how to determine if a component was prevented from being shown on the Select Items to Install screen or being deployed from the silent console mode. In the example, the binary image files 0.bin and 1.bin (which represented iLO firmware files), components cp011301.exe and cp011500.exe, and the HP BladeSystem Firmware Update Bundle for Windows represented by bundle file bp000648.xml were added to the installation set. All the other components were removed for various reasons. InstallSet.cpp[212]: Winnow--Adding FileName 0.bin InstallSet.cpp[212]: Winnow--Adding FileName 1.bin InstallSet.cpp[222]: Winnow--Removing FileName 2.bin InstallSet.cpp[212]: Winnow--Adding FileName cp011301.exe InstallSet.cpp[222]: Winnow--Removing FileName cp011321.exe InstallSet.cpp[222]: Winnow--Removing FileName cp011489.exe InstallSet.cpp[222]: Winnow--Removing FileName cp011497.exe InstallSet.cpp[212]: Winnow--Adding FileName cp011500.exe InstallSet.cpp[222]: Winnow--Removing FileName cp011504.exe InstallSet.cpp[222]: Winnow--Removing FileName cp011505.exe InstallSet.cpp[222]: Winnow--Removing FileName cp011550.exe InstallSet.cpp[222]: Winnow--Removing FileName cp011560.exe InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml Recovering from a discovery failure Troubleshooting connection errors If you are receiving an HP SUM Connection Error or Discovery Failed messages, follow these troubleshooting tips: • Ensure your workstation does not have an existing connection to the ADMIN$ share on the target IP address. If it does, it prevents HP SUM from connecting to the remote server's share because Windows only allows one connection from a client to a server's share. This can be verified by entering net use at a command prompt. If a share to the target IP address \admin$ share exists, delete it, and then attempt the installation again. • Ensure that the target IP address server's admin$ share is accessible. Validate the target server can be accessed by entering net use x: \\\admin$ for the target server IP address or DNS name. When the connection is validated, ensure that it is deleted by entering net use x: /d at the command prompt. • Ensure the user ID being used to connect to the target IP address server is part of the administrator's group. If it is not, HP SUM blocks installation to the target. • Ensure WMI is enabled and running on all Windows target servers. • For Windows target servers, enter the username in DOMAIN\USER format, where is the administrative username, and is either the NETBIOS computer name or the AD domain name for this user account. • For Linux, ensure the SSH port is not blocked. Troubleshooting 101

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
Troubleshooting 101
The following is an example of the output trace in the OpMan.trace on how to determine if a component
was prevented from being shown on the Select Items to Install screen or being deployed from the silent
console mode. In the example, the binary image files 0.bin and 1.bin (which represented iLO firmware
files), components cp011301.exe and cp011500.exe, and the HP BladeSystem Firmware Update Bundle
for Windows represented by bundle file bp000648.xml were added to the installation set.
All the other
components were removed for various reasons.
InstallSet.cpp[212]: Winnow--Adding FileName 0.bin
InstallSet.cpp[212]: Winnow--Adding FileName 1.bin
InstallSet.cpp[222]: Winnow--Removing FileName 2.bin
InstallSet.cpp[212]: Winnow--Adding FileName cp011301.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011321.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011489.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011497.exe
InstallSet.cpp[212]: Winnow--Adding FileName cp011500.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011504.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011505.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011550.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011560.exe
InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml
Recovering from a discovery failure
Troubleshooting connection errors
If you are receiving an HP SUM Connection Error or Discovery Failed messages, follow these
troubleshooting tips:
•
Ensure your workstation does not have an existing connection to the ADMIN$ share on the target IP
address. If it does, it prevents HP SUM from connecting to the remote server’s share because
Windows only allows one connection from a client to a server’s share. This can be verified by
entering
net use
at a command prompt. If a share to the target IP address \admin$ share exists,
delete it, and then attempt the installation again.
•
Ensure that the target IP address server’s admin$ share is accessible. Validate the target server can
be accessed by entering
net use x: \\<ip_address_or_dns_name>\admin$
for the target
server IP address or DNS name. When the connection is validated, ensure that it is deleted by
entering
net use x: /d
at the command prompt.
•
Ensure the user ID being used to connect to the target IP address server is part of the administrator’s
group. If it is not, HP SUM blocks installation to the target.
•
Ensure WMI is enabled and running on all Windows target servers.
•
For Windows target servers, enter the username in
DOMAIN\USER
format, where
<user
> is the
administrative username, and
<domain>
is either the NETBIOS computer name or the AD domain
name for this user account.
•
For Linux, ensure the SSH port is not blocked.