HP Clustered FileSystem3.6.1 for Windows release notes (T4422-96003, September 2008)

Issue

172 09

17660

18265

Description

Removing the M icrosoft SNMP service causes HP Clustered File System SNMP

agent

to fail

If the Microsoft SNMP service is uninstalled, the HP Clustered File System SNMP

extension agent will fail to send traps. This problem occurs because registry

entries for the HP Clustered File System SNMP extension agent are removed

when the Microsoft SNMP service is uninstalled. Reinstalling the Microsoft SNMP

service does not restore the registry entries for the HP Clustered File System SNMP

extension agent.

Workaround. The preferred workaround is to uninstall HP Cluster ed File System

(saving the conﬁguration) and then reinstall it. If this is not possible, open

Windows Explorer and go to \bin in the HP Clustered File System installation

directory, double-click on mxsnmp_add.reg, and then reboot.

Cluster des

cription cannot be reset when HP C lustered File System is not running

The cluster description is set when you initially conﬁgure the cluster. If you need

reset the description at a later time, HP Clustered File S ystem must be running

while you make the change.

Export fails when multiple nodes are speciﬁed

When the cluster conﬁgura tion is exported to multiple nodes, the export m ay fail

for a particular node or nodes because the FibreChannel switch is receiving too

many requests. The following error is displayed, followed by a Java exception.

com.polyserve.mxconfig.StorageException: Cannot get switch information

mxsanconf: 10.11.20.241 failed

The given host is not responding to ICMP pings.

This may be an indication that:

1) The given host is incorrect.

2) The given host is not online.

3) ICMP traffic is blocked.

Please verify that the switch port is enabled and the

IP address is correct, or if a hostname was supplied,

that it is registered with DNS. Also verify that the

FC switch and storage array are connected properly and

that the HBAs are using the correct driver version.

Workaround. Stop and restart the Conﬁgure Cluster GUI and then retry the export

to the remaining nodes.