HP-UX 11i Version 1.5 Release Notes, September 2001

File and Disk Management
VERITAS Volume Manager
Chapter 4 67
• Problem: The Storage Administrator does not support communication
between the client and server across a firewall.
• Workaround: None
Problem with Multiple Host Names
• Problem: The Storage Administrator can have trouble connecting to a
host machine (server) if multiple host names are associated with a
single IP address. The following message is displayed:
Summary:
There is no such server (host1)
Detail:
java.net.UnknownHostException: Unknown host:
[host2:32839]; nested exception is:
java.net.UnknownHostException:host2
In this example, the administrator specified host1 for the VMSA
connection, but the server host machine was identified as host2.
In some cases, this may be a problem with the way DNS is set up. A
DNS reverse lookup (by IP address) may return a host name that
differs from the host name provided to VMSA at startup (host1). You
may have to make appropriate changes to DNS so that the names are
consistent. In other cases, this happens because host1 is not the first
host in the list of hosts for the associated IP address in the
/etc/hosts file.
• Workaround: Make sure host1 shows up as the first host in the list of
names for the address of host1 in /etc/hosts.
Cannot Grow gen Volume
• Problem: VMSA does not grow a volume of use_type gen
• Workaround: None
X Window Errors at VMSA Startup
• Problem: When the Storage Administrator is started, the following X
Window System error can occur:
Xlib: connection to "hostname:0.0" refused by
server
Xlib: Client is not authorized to connect to Server