![]() ![]() If an upgrade to Xsan 4 or later has been performed, Xsan is disabled after the upgrade. Quantum recommends you reboot the client. When the Xsan client is loaded using the command launchctl load, the client will need to be rebooted before the Xsan client is loaded. Quantum recommends you verify a driver is loaded and skip the unload step if the driver is not loaded. Note: On a new Xsan 4 driver installation, an Xsan client may not have been loaded and an error will be displayed when you execute launchctl unload. Xsan4client$ sudo profiles –I –F nfigprofile Xsan4client$ for i in `cat /tmp/oldprofiles` do sudo profiles –R –p $i done ![]() Xsan41client$ sudo profiles –L | grep | awk '' > /tmp/oldprofiles Mdc# scp nfigprofile Remove any existing Xsan profiles from the client: Copy the resultant profile to the Xsan 4.1 client:.To connect Xsan 4.1 clients to StorNext MDCs: Mounting the StorNext File System on Xsan 4.1 The fsnameservers file must be identical on all StorNext MDCs, StorNext and StorNext FX clients, and Xsan clients. auth_secret files should be removed from the Xsan clients, the StorNext clients, and the MDCs. However, if the only MDCs in use are StorNext MDCs, the. If the system configuration includes both Xsan and StorNext MDCs, and Xsan clients, ALL machines in the configuration must have the identical. StorNext MDCs must have license.dat file in the configuration directory of the system.įor Linux MDCs, the configuration directory is:įor Windows MDCs, the configuration directory is: StorNext MDCs and Xsan clients must be connected to the same SAN and be able to see the same LUNs In order to connect Xsan Clients to StorNext MDCs, ensure the following: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |