HP Integrity Superdome 2 8/16 HP Smart Update Manager 5.0 User Guide - Page 71

Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2008 environment

Get HP Integrity Superdome 2 8/16 PDF manuals and user guides View all HP Integrity Superdome 2 8/16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 71 highlights

Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2008 environment To validate that the IPv6 network is configured correctly for HP Smart Update Manager support, you must verify the following based on your operating system version. • Validate that you can ping the remote target server. With Windows® operating systems, you can use the ping command to ping IPv6 addresses: ping . • Ensure you can ping the IPv6 loopback address: ping ::1. • Use the DNS hostname instead of IPv6 address to ensure the address is correct. • Verify that you can connect to the admin$ share using the credentials within HP Smart Update Manager by issuing the following command at a console prompt: net use * \\.ipv6-literal.net\admin$ /user: net use * \\fec0::2.ipv6-literal.net\admin$ /user:administrator You might need to provide the password if you use a user name that is different from the one you used to log in to the local system. All network shares require the use of the .ipv6-literal.net name string to be properly configured by Windows®. After you validate you can access the admin$ share on the remote target server, HP Smart Update Manager works unless there are other network or hardware issues. Troubleshooting HP Smart Update Manager in IPv6 Red Hat and Novell SUSE-based Linux environments • Verify that you can establish an SSH connection to the remote target server using the credentials within HP Smart Update Manager by issuing the following command at a console prompt: ssh SSh 2101:db8:0:1::9 You must enter the root password for the target Linux server at the console to complete the IPv6 connection. • Validate that you can ping the remote target server. In Linux, you need to use the ping6 command to ping IPv6 addresses: ping6 . • Ensure you can ping the IPv6 loopback address: ping6 ::1. • Use the DNS hostname instead of IPv6 address to ensure the address is correct. • Use ipconfig to validate you have IPv6 addresses assigned to your NICs. For more information about troubleshooting your configuration, see the Linux IPv6 How-To (http://www.linux.com/learn/docs/ldp/592-linuxipv6-howto). • For more information about setting up and troubleshooting IPv6 networks, see Getting Around IPv6 by Carla Schroder (http://www.enterprisenetworkingplanet.com/netsp/article.php/3634596). • Move back to an IPv4 network address to ensure HP Smart Update Manager properly finds the remote target server without any issues. • HP Smart Update Manager can always be copied to the target servers and executed using the local installation method. Troubleshooting 71

  • 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
Troubleshooting 71
Troubleshooting HP Smart Update Manager in IPv6 Windows
Server 2008 environment
To validate that the IPv6 network is configured correctly for HP Smart Update Manager support, you must
verify the following based on your operating system version.
•
Validate that you can ping the remote target server. With Windows® operating systems, you can use
the ping command to ping IPv6 addresses: ping <ipv6 address>.
•
Ensure you can ping the IPv6 loopback address: ping ::1.
•
Use the DNS hostname instead of IPv6 address to ensure the address is correct.
•
Verify that you can connect to the admin$ share using the credentials within HP Smart Update Manager
by issuing the following command at a console prompt:
net use * \\<ipv6-address>.ipv6-literal.net\admin$ /user:<username>
net use * \\fec0::2.ipv6-literal.net\admin$ /user:administrator
You might need to provide the password if you use a user name that is different from the one you
used to log in to the local system. All network shares require the use of the .ipv6-literal.net name
string to be properly configured by Windows®.
After you validate you can access the admin$ share on the remote target server, HP Smart Update
Manager works unless there are other network or hardware issues.
Troubleshooting HP Smart Update Manager in IPv6 Red Hat and
Novell SUSE-based Linux environments
•
Verify that you can establish an SSH connection to the remote target server using the credentials within
HP Smart Update Manager by issuing the following command at a console prompt:
ssh <ipv6 address>
SSh 2101:db8:0:1::9
You must enter the root password for the target Linux server at the console to complete the IPv6
connection.
•
Validate that you can ping the remote target server. In Linux, you need to use the ping6 command to
ping IPv6 addresses: ping6 <ipv6 address>.
•
Ensure you can ping the IPv6 loopback address: ping6 ::1.
•
Use the DNS hostname instead of IPv6 address to ensure the address is correct.
•
Use
ipconfig
to validate you have IPv6 addresses assigned to your NICs. For more information about
troubleshooting your configuration, see the Linux IPv6 How-To
(
).
•
For more information about setting up and troubleshooting IPv6 networks, see
Getting Around IPv6
by
Carla Schroder (
).
•
Move back to an IPv4 network address to ensure HP Smart Update Manager properly finds the remote
target server without any issues.
•
HP Smart Update Manager can always be copied to the target servers and executed using the local
installation method.