To validate that the IPv6 network is configured correctly for HP SUM support, you must verify the following based on your operating system version.
Validate that the addresses are site-local. Site-local addresses normally start with "FEC0:". Global and link-local IPv6 addresses are not supported when the remote target is Windows Server 2003.
Validate that you can ping the remote target server. With computers running Windows, you can still use the
ping
command to ping IPv6 addresses:Ensure you can ping the IPv6 loopback address:
Use the DNS hostname instead of IPv6 address to ensure the address is correct.
Ensure you have installed the IPv6 protocol. It is not installed by default in Windows Server 2003. Be sure to reboot the server after installing the protocol to ensure addresses are properly obtained.
Verify that you can connect to the admin$ share using the credentials within HP SUM 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 are using a user name that is not the same as 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.
NOTE: You do not need to use the .ipv6-literal.net suffix when entering IPv6 address into the HP SUM user interface or when passing IPv6 address using command line parameters to HP SUM.
After you validate that you can access the admin$ share on the remote target server, HP SUM works unless other network or hardware issues exist.
Ensure you have made the registry change on remote target servers. For more information, see Configuring IPv6 for Windows Server 2003.
Move back to an IPv4 network address to ensure HP SUM properly finds the remote target server without any issues.
You can always copy HP SUM to the target servers and execute using the local installation method.