Apple propose depuis hier une mise à jour de l'utilitaire Xserve RAID Admin Tools 1.3.2.

La version proposée au téléchargement est la 1.3.2. Comme d'habitude, cette mise à jour est disponible via le module Mise à jour ou directement sur le site d'Apple. 

Alors, juste après ces quelques mots, et en une seule ligne, voici le descriptif de cette mise à jour :



Vous pouvez télécharger directement cette mise à jour ici (Apple) :



Bon, ben en anglais, on va en savoir un peu plus sur cette mise à jour :

Xserve RAID Admin Tools 1.3.2

About Xserve RAID Admin Tools
RAID Admin is the Xserve RAID’s powerful remote management software that dramatically simplifies setup and monitoring of storage volumes. This Java-based application provides an intuitive interface for creating protected storage volumes, logging events, managing preferences, and monitoring storage hardware from virtually any networked computer over TCP/IP. Monitoring panes display detailed information on arrays, drives, LUN mappings, Fibre Channel, network, thermal, power, and events. You can add new systems to the Admin via IP or Apple’s innovative Rendezvous technology.

What’s New in this Version
This software release improves overall reliability and is recommended for all users. If you are using Xserve RAID in an Xsan environment, you must upgrade the Xserve RAID with the firmware in this release. The versions of RAID Admin and Xserve RAID firmware in this release should replace all earlier versions. Key enhancements include:
- 400GB hard drive support
- Improved integration with Xsan cluster file system software
- Fixed LUN ID compatibility issue with older Xserve RAID firmware 1.1-117a and 1.2-116f
- Enhanced “Repair LUN Map” function to repair entries with a missing LUN ID or more than one LUN ID
- RAID Admin locks out certain operations on Xserve RAID units with older incompatible firmware
- Fixed case where masking LUN 0 prevented other LUNs from being discovered on some host computers
- Corrected response to SCSI REPORT LUNS command where large allocation length caused an incorrect LUN list length