HP ProLiant Support Pack - Manual (Page 93)

Advanced topics 93
If you cannot connect to the target server or receive a Discovery failed message when executing HP Smart
Update Manager in an IPv6 environment, see the troubleshooting section ("
Troubleshooting HP Smart
Update Manager in IPv6 networks " on page 105 ).
After you connect to the target server, all other HP Smart Update Manager functions work identically. Log
files for IPv6 hosts are stored with all other HP Smart Update Manager files in the
\CPQSYSTEM\hp\log\ directory.
Limitations of IPv6 for Windows Server 2003 and Windows Server 2008
Windows Server® 2003 requires site-local addresses to provide the necessary file-sharing capabilities
needed by HP Smart Update Manager. This means that link-local and global IPv6 addresses are not
supported as remote targets with HP Smart Update Manager.
Windows Server® 2008 or Windows® environments do not have any known limitations to using HP
Smart Update Manager.
NOTE: Windows® XP clients are not supported in IPv6 networks for HP Smart Update
Manager deployment.
Configuring IPv6 for Linux
HP Smart Update Manager leverages the IPv6 capabilities of Linux as provided by the Red Hat Enterprise
Linux and Novell SUSE Linux Enterprise Server products. Using HP Smart Update Manager in this
environment enables you to use all the capabilities of IPv6 including link-local, site-local, and global IP
addresses for both local and remote target servers. Remote target servers must have the iptables-ipv6 RPM
installed before targeting them from HP Smart Update Manager. Failure to install the iptables-ipv6 RPM
prevents HP Smart Update Manager from opening the communications port needed to send data to the
initiating Linux workstation. You can disable the Linux firewall to allow HP Smart Update Manager to
work, but the Linux server becomes vulnerable to attack.
For information on how to setup IPv6 in a Linux environment, please see the Linux IPv6 How-To
(
http://www.linux.org/docs/ldp/howto/Linux+IPv6-HOWTO/index.html ).