SANergy Supported Operating Systems and System requirements
SANergy supports the following operating systems with the following functions. | Supported Operating Systems | Host | MDC | SNMP | | Windows XP, 2003, 2003 R2 | X | X | X | | AIX 5.2, 5.3 and 6.1 | X | X | X (Non FSF SANergy) | | Solaris sparc 5.8, 5.9 and 5.10 | X | X | X (Non FSF SANergy) | | Linux Redhat 4 update 4 2.6.9 x86_64 | X | X | - | | Linux Redhat 4 update 4 2.6.9-42.ELsmp x86_64 only | X | X | - | | Linux RedHat 5.2 - kernel 2.6.18 for x86_64 bit servers | X | X | - | | Linux Suse 10.2 - kernel 2.6.16.60 for pseries 64 bit servers. | X | X | - | | Linux Suse 10.2 - kernel 2.6.16.60 for x86_64 bit servers | X | X | - | | HPUX 11i | X | - | - | | SGI IRIX 6.5 | X | - | - | SANergy MDC's supports the following File Systems: Operation System | File System | | Windows | NTFS | | Solaris | UFS QFS SAMFS (Non EFI partitions) | | Linux | EXT3 | | AIX 5.x and 6.x | JFS2 | All SANergy hosts will function with all SANergy MDCs provided the proper file sharing software is used to share the file systems. See the LAN Environment section below for a list of the appropriate sharing software. Each system in your SAN must meet the following requirements: 1 PCI slot available for a new host bus adapter Functional LAN network interface CD drives for software installation SAN host bus adapter in each system with appropriate SAN drivers installed
Windows systems
A Windows server and workstation require the following hardware and software: Machine: An Intel Pentium(R) processor Minimum memory and space requirements to run: RAM: 64 MB, in addition to the memory required by other applications Disk space: 20 MB Operating system: Windows XP, 2003, 2003 R2 Communication protocol: TCP/IP If there is a UNIX computer on your SAN, you must install and setup your NFS server software (Microsoft Services for Unix). Notes: For Windows MDCs, SANergy supports NTFS formatted volumes only, including new technology file system (NTFS) software stripe sets. SANergy does not currently support NTFS mirroring, software RAID (parity), or volume expansion. Windows shared volumes must be formatted using the NTFS with Windows. Windows support Microsoft Cluster Server (MSCS) failover.
Sun Solaris system
A Sun Solaris system requires the following hardware and software: Machine: SPARC systems only Minimum memory and space requirements to run: RAM: 128 MB Disk space: 20 MB Operating system: Solaris 5.8, 5.9 and 5.10 Sun Solaris NFS installed and operational (optional) Netscape with JavaScript(TM) support Communication protocol: TCP/IP, which comes standard with Sun Solaris SAMBA, if being used as an MDC to support Windows and Macintosh hosts. Note: For Sun Solaris MDCs, SANergy supports UFS and QFS formatted volumes only.
Linux Red Hat and SuSE
A Linux system requires the following hardware and software: Machine: X86 based PC architecture Pentium(R) processor and later
or PSeries 5 machine (for some releases). Minimum memory and space requirements to run: RAM: 128 MB Disk space: 20 MB Operating system: Linux
Linux Redhat 4 update 4, kernel 2.6.9 x86_64 (single and dual-processor systems) Linux Redhat 4 update 4, kernel 2.6.9-42.ELsmp x86_64 only Linux Suse 10, kernel 2.6.16.53 for pseries 64 bit servers
NFS installed and operational Samba, if being used as an MDC to support Windows hosts. Samba is included with Red Hat. Communication Protocol - TCP/IP, which comes standard with Linux.
IBM AIX system
An IBM AIX system requires the following hardware and software: Machine: RS/6000(R), Power PC Minimum memory and space requirements to run: RAM: 128 MB Disk space: 20 MB Operating system: AIX 5.2, 5.3 and 6.1 NFS installed and operational For all versions, use the SANergy command line tool Communication protocol: TCP/IP, which comes standard with AIX Note: For AIX MDCs, SANergy supports JFS2-formatted volumes only.
SGI IRIX UNIX system
An SGI IRIX UNIX system requires the following hardware and software: Machine: O2, Octane, Origin Minimum memory and space requirements to run: RAM: 128 MB Disk space: 20 MB Operating system: IRIX UNIX Release 6.5 ONC3/NFS version 2 or 3 installed and operational (found on the SGI operating system disks) NFS installed and operational Netscape with JavaScript support Communication protocol: TCP/IP, which comes standard with IRIX UNIX
Network requirements
SANergy network requirements are:
Access to the World Wide Web for software updates at http://www.tivoli.com/support/sanergy You must have at least one MDC on your SAN. SAN: All computers must be attached directly to the storage you want to share with both read and write permissions. The computers must attach not just by IP, but also by a SCSI-type connection, which includes SCSI, iSCSI, or Fibre Channel. MAPPING: You must have each computer map, or mount, the Meta Data Controller volume. This requires general networking hardware and software (for example, TCP/IP on Ethernet) installed and configured.
With Windows, use conventional Windows networking and sharing.
With UNIX computers, use NFS. You will need an NFS server for your Windows MDC computer.
On a UNIX MDC that has Windows hosts attached, you must install Samba or equivalent. Meta Data Controller
For each configuration, assign one computer as the security and Meta Data Controller (MDC) for SANergy shared volumes. There can be as many MDCs as there are file systems, or a single MDC for all file systems. The MDC system also acts as the server for the specific shared volume or volumes. However, the MDC's role as a server is only to manage user authentication, access control, and file system locking operations. SANergy redirects input and output directly over the SAN. LAN environment
All computers must share a common local area network and protocol (for example, TCP/IP over Ethernet), and be able to see each other on the LAN. This includes an operational LAN network interface (for example, embedded Ethernet or separate Ethernet adapter). All host computers must be able to map (mount) the MDC shared volumes. This requires that the standard network operating system software be installed and configured so that each machine can access a shared volume on the MDC server. MDC | Host | Sharing Software | | Windows | Windows | Normal Windows CIFS sharing | | Windows | Unix | Microsoft Services for Unix installed on MDC to create NFS shares | | Unix | Windows | Samba installed on the Unix to create CIFS shares | | Unix | Unix | Normal NFS sharing | For Windows, use the built-in Windows networking and sharing. For UNIX systems, use NFS to mount the shared volumes. To support UNIX systems, you also need NFS server software for your Windows MDC system. If you are going to include Windows computers as hosts with your UNIX MDCs, you must install a CIFS package, such as Samba, on your MDCs to create shares. SAN environment
All systems must share a common storage area network connection to shared storage devices. This can be a connection over shared Fibre Channel (switched or arbitrated loop) physical media. A SAN host bus adapter (HBA) is also required in each system with appropriate SAN drivers installed. The interconnect technology and associated HBA can be SCSI, iSCSI, or Fibre Channel. All HBAs must support a multi-initiator environment:
SAN network devices (for example, FC-AL hubs, fabric, and switches) SAN storage devices (for example, RAID or JBOD arrays) For Fibre Channel SANs, all systems and drives to be shared must also be in a common zone. Zones and fabrics might require additional configuration for proper operation. | 
