Client access is virtualized to appear local.
Goal of SAN is to provide dedicated storage, not shared.
block-level (therefore do not provide FSs directly).
SAN filesystems and other file systems (shared and not) provide FS and
 sharing capabilities on top of SAN.
Usually have a private, local, high speed SAN device network.
Booting off of SAN is still considered new.
SCSI is the typical comm medium.  (What about "a few meters" limitation,
 and I heard that fiber channel was standard?)
FCP = SCSI over Fibre Channel
iSCSI mapping of SCSI over TCP/IP
NETWORK.  Often Fiber Channel fabric topology made up of Fibre Channel
 switches.
+ 3PAR InServ product family 2.3-960 TB
+ EMC and Symmetrix "flagship" 2TB-1054 TB families
 (many other families too)
    Latest Symmetix series is 2009's VMAX.
    Great Symmetrix article: http://en.wikipedia.org/wiki/Symmetrix
        Symmetrix VMAX + Symmetrix VMAX SE (Single Engine)
            run Enginuity  OS.  For open OSes
        DMX.  OS?

Excellent doc at http://solarisguru.getquickstart.com/2008/05/san-storage-configuration-in-solaris.html
Also http://www.mj12net.org/index.php/system-administrator-interview-cheat-sheet.html#SAN
Multipathing is Sun-specific means to access 1 target device object from
 multiple physical hosts.
Fibre Channel HBA (Host Bus Adapters) manufacturers:
    QLogic + Emulex make 90%.  Small mfgs incl. Agilent, ATTO, Brocade, LSI.
WWNs (World Wide Names) like:
   8 byte/segment addrs similar to IPV6 like 50:a9:80:00:55:CC:66:CD.
Adapter gets a WWNN (World Wide Node Name) correponding to Mac addr.
Each port gets a WWPN (World Wide Port Name).
Awesome installation doc (covers other OSes too):
  http://www.datadisk.co.uk/html_docs/emc/emc_hba_setup.html
SAN-side config.  Define 'initiator groups', which are lists of WWPNs.
    Name the i.g. as the Sun host name.
    Group created like: igroup create -f -t solaris sunHostName sunWwpn1...
Solaris config.
    See hbaConfig.html.
    Install doc lists changes needed to /etc/system,
      /kernel/drv/lpfc.conf (Emulex), /kernel/drv/emlxs.conf (Sun Emulex),
      /kernel/drv/qla2300.conf (QLogic), /kernel/drv/qlc.conf (Sun QLogic),
      /kernel/drv/sd.conf, /kerlen/drv/glm.conf.
    Assign unique scsi-initiator-ids with openboot:  setenv scsi-initiator-id 6
    Requires StorEdge packages (and many patches)
    HBA device names like lpfc0.
    /usr/sbin/sanlun fcp show adapter -c  # Output needed to create initiator
                # group on the SAN server.   "Network Appliance" program?
    Involves 'prtdiag', 'devfsadm', 'cfgadm', 'update_drv', 'lputil'
        Particularly interested in 'cfgadm' in c* records of type "fc-fabric".
        'prtpicl', 'scli'
        'prtconf -vp', 'fcinfo' starting with Sol 10.
    /usr/sbin/lpfc/lputil  (Emulex program)
        (but all we need are the friggin WWNNs?)
        Assign "Node Name" of the SAN node WWNN (without colons)
        Enter a distinctive [SCSI] target number for this SAN server.
    IMPORTANT:  lputil being replaced by hbacmd (Distributed HBAnywhere CLI).
    Add lines for many lun slots, since this is only read upon boot.
     Append to /kernel/drv/sd.conf:
        name="sd" parent="lpfc" target=1 lun=0;  [hba="lpfcZ"]

  Need option to dislay LUNs:  cfgadm -al -o show_SCSI_LUN
  With sol 8 need:  cfgadm -al -o show_FCP_Dev c[23]
  Integer after the comma is the LUN number
Host node clients (initiators) connect to storage server (target).
Need to set up 'persistent bindings' to ensure LUNs don't change upon
  reboot.