Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Facilité d'utilisation
Management console
•
If the management console service is stopped on the active management console and, within a
minute, the passive management console experiences a shutdown or reboot, the passive
management console will become active when the node is restarted. When the fusionmanager
is started on the formerly active management console (or that node is rebooted), that management
console will also be in active mode. Although both management consoles are active, only one of
these consoles will control the cluster virtual interface.
To recover from this scenario, take the following steps:
1.
Determine which management console is running the cluster virtual interface:
ifconfig -a
In the output, check for a configured bond0:1 virtual interface.
2.
Place the management console that is not running the cluster interface into maintenance
mode, and then place it into passive mode:
ibrix_fm -m maintenance
ibrix_fm -m passive
If the recovery is not successful, contact HP Support.
•
If the node hosting the active management console goes down, it is important to reboot it as soon
as possible. The management console on that node can then assume a passive role and receive
updates from the new active management console. If the node remains down and the node hosting
the active management console also goes down, the cluster configuration data may become
inconsistent, depending on the order in which the nodes are rebooted.
•
When the active management console is moved to maintenance mode, a passive management
console will transition to active mode. Be sure that this transition is complete before you move the
previously active management console from maintenance mode to passive mode. (Use the
ibrix_fm -i command to check the mode of each management console.) If the passive
management console has not yet assumed active mode, the management console being moved
from maintenance to passive mode will become active again.
CIFS
•
CIFS and X9000 Windows clients cannot be used together because of incompatible AD user to
UID mapping. You can use either CIFS or X9000 Windows clients, but not both at the same time
on the cluster.
•
Occasionally a share cannot be mounted using the DNS name. The workaround is to use the IP
address instead.
•
The X9000 CIFS server does not support connections from Linux SMB clients. The workaround is
to use NFS for Linux.
•
Alternate Data Streams (ADS) are not supported. When a file with an ADS is moved or copied
to the CIFS Server, X9000 Software moves/copies the file, but the attached ADS is not copied.
Attempts to create an ADS or a filename containing a colon (:) will be failed by the CIFS Server.
•
When the Microsoft Windows Share Management interface is used to add a CIFS share, the
share path must include the X9000 file system name. The Browse button on the MMC cannot be
used to locate the file system. Instead, enter the entire path, such as C:\data\.
•
The X9000 management console GUI and CLI allow only X9000 file systems and directories to
be exported as CIFS shares. However, the Microsoft Windows Share Management interface
allows you to create a CIFS share that is not on an X9000 file system. Although the share will be
available from the file serving node to which Windows Share Management was connected, it
will not be propagated to the other file serving nodes in the cluster.
Workarounds
11
... Ce manuel est également adapté pour les modèles :
données dispositifs de traitement - HP IBRIX X9320 10GbE Performance Block (250.14 kb)
données dispositifs de traitement - HP IBRIX X9320 IB Performance Block (250.14 kb)
données dispositifs de traitement - HP StoreAll 8800 Storage Node (250.14 kb)
données dispositifs de traitement - HP StoreAll 9320 1GbE Storage Node Pair (250.14 kb)