Anthony's Blog: Using System Storage - An Aussie Storage Blog
So something I truly hate to see when visiting computer rooms is fibre cables hanging in the breeze with no dust covers, their precious glass connectors exposed to the world.
Even worse are fibre patch panels and HBAs without dust covers.
When new equipment arrives, every HBA, every patch panel port and every fibre optic cable will have a dust cover.
So what to do with these little guys once you remove them?
When you unplug a cable later you need to immediately re-install those precious covers both onto the cable and into the HBA or patch panel port, to protect the fibre optics from contamination.
I recommend storing dust covers in sealed plastic bags, preferably kept in the relevant rack so they are close to hand.
The picture below (taken from the rear of an XIV) is cute in that it shows a clever re-use of the XIV power cable covers,
but the dust covers are now exposed to contamination from the open air.
Since we are on the subject, take note of the colour coded power cables in the XIV.
Its another example of clever design to make power redundancy visually obvious.
The ends of the power cords are red, yellow and green to indicate which of the three UPSs these cables come from.
The unused cords at the top of the image are free because this machine is not fully populated with modules.
I started my IBM career with very dirty hands.
Every day I would go to work and come home smeared with toner, ink, grease and oil.
No I didn't work for a newspaper or in a garage... I worked for IBM, fixing cheque sorters and printers. This was the late 1980s and early 1990s. The years I spent working on IBMs 3800 and 3825 printers and 3890 cheque sorters were great years. I loved working with my customers and I loved working on those big machines. It was lots of fun... but there were lots of ways to get dirty.
What were these machines? Well for one, the IBM 3800 was the worlds first commercial fan-fold laser printer (released in 1975!). Here is a picture, but I would point out that this 3800 looks remarkably clean:
The 3890 Cheque Sorter was an enormous document processor that could move 2400 cheques per minute. For even better clothing destruction, the 3890 has an ink jet printer that used a special ink that you could easily remove from any garment - provided you used a pair of scissors. As for the IBM 3825 Page Printer, it used Charged Area Development, which without very regular maintenance, could result in huge amounts of toner wandering around inside the machine. No wonder the acronym for that technology is CAD.
And yet in all of this... I wore a suit and tie to work... every day... and I always wore a white shirt. It was an IBM standard that had existed for a very long time. People who turned up for work in a non-white shirt had better be a top performer and only the most remarkable or safety conscious turned up for work wearing something that is now rare in the workplace: The Bow Tie.
The only other IT organization I knew that was just (if not more) obsessed with suit and tie? EDS.
As for the System 38 utopian image below.... thats not me on the right! I never wore tan trousers or short sleeves to work. (Check out the size of those monitors!).
Things changed in the mid 1990s. Suddenly we didn't need to wear a tie. Some of us started wearing corporate branded polo shirts. Times had changed and we changed with them. One irony is that I now regularly wear black business shirts to work, something that I would never have gotten away with in 1990. Yet today the closest I come to toner is when I go and get a printout from the printer.
If your interested in seeing some great photos of how IBMers used to dress, visit the IBM History exhibit here: "The way we wore: A century of IBM attire". You could also head over to IBM's 100 Icons of Progress and in particular visit The Making of IBM to see Thomas J Watson Snr looking very smooth indeed.
I was brought to reminiscing about this when visiting a client on a friday. Friday has become casual clothes day at many organizations. And yet given how far we have come... I am pondering why we bother? In comparison to 20 years ago, every day is casual clothes day. Perhaps its time to put aside the polo shirts and bring back the bow tie? As Dr Who says "Bow Ties are Cool"
So are you with me? Bow Tie Friday?
Comments always welcome.
With the announcement that you can order an XIV with 3 TB SAS disks, IBM now have some amazing capacity options and some equally clever growth options with XIV Gen3.
As you hopefully know, the XIV consists of modules that each contain 12 disks. An XIV can have 6, 9, 10, 11, 12, 13, 14 or 15 modules (all modules must have the same size disk). You can start at any of those points and then grow without interruption or outage up to 15 modules (that's 243.3 TB!). There is practically no planning required to do a capacity upgrade and the data relocation to re-balance between the nodes is done automatically by the machine (without any end-user intervention).
The useable capacity sizing with 3 TB drives stretches from 84.1 TB with 6 modules to 243.3 TB with 15 modules (these are decimal TB).
However the Capacity on Demand (CoD) options are far more interesting. With CoD you effectively buy a certain amount of capacity up front but also get up to 3 more modules shipped with the machine. You can start using this extra capacity when your business requirements demand it, at which point you will be asked by IBM to purchase it. The advantage here is that you physically get a bigger machine up front with all the performance benefits that bestows, plus you don't have to contact IBM to start using that extra capacity. Lets look at the possible configurations.
So lets take a scenario. You need 100 TB today, but you know this will grow to 130 TB over the next 12 months. So you could purchase an XIV with 9 physical modules (using 3 TB drives), with 7 CoD activations. This means IBM ship a machine that physically has 132 TB and that physically has 108 drives in 9 modules. Your data will be spread over all these drives and all of these modules will be active and working. However you have effectively only paid for 103 TB of that space up front. If you order extra CoD activations, you could also order extra physical modules. As long as you stick to the chart above and have at least one un-activated module, you stay in the CoD program.
When your data requirements exceed 103 TB you just start using the extra space, no license keys or special tasks required. Nice!
So having told you how great it is... are there any disadvantages?
1) You need to actually buy the storage... eventually. Depending on the CoD contract there will be a point when IBM expect you to purchase this extra capacity. The whole point of CoD is that it is like pre-ordering capacity without actually paying for it up front. If your really not certain you need extra capacity, your probably better off not ordering CoD capacity in the first place. Instead order capacity upgrades as you require them.
2) There is nothing to stop you using the storage. Now this is a curious disadvantage because it means that if you have paid for 103 TB and you start using 105 TB, the machine will not tell you off, or yell at you. So is this a good thing or a bad thing? Well I really like the flexibility so I think it is a good thing. Plus there is a nice command called cod_list which displays consumed capacity to help keep you on the path. You can also display it in the GUI. So it just means you need to keep an eye on volume and pool creation to ensure you don't start configuring extra capacity until your prepared to pay for it.
You can also use CoD with 2 TB drives on XIV Gen3 so this is another option. With 2 TB drives, the useable capacities look like this:
Questions? Fire away....
A final blog entry before Christmas, with a little Christmas present for all our midrange storage users.
The IBM System Storage Interoperation Center (SSIC) found here now lists all of IBMs LSI based
Midrange and Entry Disk systems. So you can now select VMware vSphere/ESX 4.1...
and then find products like the DS4700 and DS4800.
As you can see, the DS4700 has 5808 different configuration results, so hopefully your environment is in there.
If your environment is still not listed, please contact your IBM FTSS or Business Partner to ask for a SCORE request to get support.
I see this comment occasionally and it makes me bristle:
"Disk and tape traffic must be in separate zones because they have different characteristics. If they are in the same zone this can cause performance problems or have other adverse affects."
True statement or totally wrong?
Well actually kinda wrong... If you have a single HBA with only one port, then separating disk and tape traffic into separate zones does NOTHING to get around the fact that both streams of traffic (random bursty disk traffic and sequential streaming tape traffic) are all coming from or going to the same HBA port. All zoning achieves in this case is stop the disk and tape devices from talking to each other (something that in general they are not interested in doing).
Separating disk and tape traffic is best done with separate HBA ports (whether thats a dual ported HBA or two single port HBAs).
So lets change the wording:
"Disk and tape traffic should ideally be handled by separate HBA ports, because they have different characteristics. If both traffic types use the same HBA port this can cause performance problems or have other adverse affects."
Guess what? This advice has not changed since 2001.
Rob Jackard from the ATS Group has kindly supplied me with this great summation of recent updates to various parts of the IBM Support sites.
Its worth just running your eyes down the list to see if there is anything that might apply to you and your environment.
For XIV users, please update to the latest GUI release, version 2.4.3a (see the link below).
The release notes (which you can also find at the link below) detail an important fix that could prevent an outage when mapping new volumes
to a clustered group of hosts which uses private mappings, (which you might do if you have separate dump or boot drives for clustered hosts).
DS3000 / DS4000 / DS5000:
(2010.06.21) Best Practices for Running an Oracle Database on an IBM Midrange Storage Subsystem.
(2010.06.15) IBM DS3500 ESM and firmware bundle version 3.16.
(2010.06.15) IBM DS3000 HDD firmware package version 4.7.
(2010.06.14) IBM DS3500 Controller Firmware bundle version 7.70.16.01.
(2010.06.03) Retain Tip# H196875: Upgrade from 6.xx firmware to 7.60.28.00 may fail - IBM System Storage.
NOTE: Affected configurations- DS4200 (Type: 1814), DS4700 (Type: 1814), DS4800 (Type: 1815). Release scheduled 2nd QTR 2010.
DS6000 / DS8000:
(2010.06.30) A quick capacity (physical/effective) table for DS6000 and DS8000.
(2010.06.30) Accelerate with ATS: DS8700 Easy Tier Webinar.
(2010.06.23) Potential Data Error on FlashCopy targets using Space Efficient FlashCopy (SEFLC) volumes after a DS8000 LPAR Failover or Failback.
(2010.06.21) IBM DS8000 Storage Virtualization Overview Including Storage Pool Striping, Thin Provisioning, Easy Tier.
(2010.06.02) Support for VMware Site Recovery Manager.
(2010.05.27) Enabling multipath SAN booting with DS8000 and DMMP.
(2010.07.02) Hard Disk Drive (HDD) Firmware for N series Publication Matrix.
(2010.06.29) Firmware release NA01 available for the Seagate SAS disk drive identifiers: X286_S15K6146A15, X287_S15K6288A15, and X289_S15K6420A15.
(2010.06.29) Firmware release NA01 available for the Seagate FC disk drive identifiers: X278_S15K6146F15, X279_S15K6288F15, and X291_S15K6420F15.
(2010.06.07) IBM System Storage N series FRU (Field Replaceable Unit) lists.
(2010.06.01) NEWS: Recommended Release for IBM System Storage N series Data ONTAP.
(2010.06.01) Data ONTAP 7.3.3 recommended for IBM Systems Storage N series.
(2010.06.14) IBM SAN b-type Firmware Version 6.x Release Notes.
(2010.06.01) Data Center Fabric Migration Guide.
(2010.06.16) IBM System Storage SVC Code V18.104.22.168.
(2010.06.16) 2145-CF8 Nodes May Stall on Error 231 During Upgrade to V22.214.171.124.
(2010.06.16) SAN Volume Controller Concurrent Compatibility and Code Cross Reference.
(2010.06.02) Support for VMware Site Recovery Manager.
(2010.06.02) SVC V5.1.0.x Cluster Nodes May Repeatedly Reboot When Performing Multiple Image Mode Migration Commands on the Same VDisk.
NOTE: This problem will be resolved in a future SVC release.
(2010.05.14) IBM System Storage SVC Code V126.96.36.199.
SSPC / TPC / TPC-R:
(2010.06.24) Accelerate with ATS: Working with TPC Disk- Midrange Edition.
(2010.06.24) Accelerate with ATS: TPC Disk Midrange Edition- Installation and Tailoring.
(2010.06.22) (IBM Internal/BP) Managing Virtualized Storage Environments with IBM Tivoli Storage Productivity Center.
(2010.06.21) TPC 4.1.x – Supported Storage Product List.
(2010.06.09) Latest Downloads for Tivoli Storage Productivity Center.
(2010.06.06) Ten things for the new TPC-SE Administrator to do to make TPC 4.1.1 more valuable.
(2010.06.04) Q2, 2010- IBM Tivoli TotalStorage Productivity Center Suite Customer Support Technical Information Update.
(2010.05.12) Tivoli Storage Productivity Center v4.1.x fix pack history technote (FAQ).
NOTE: Latest includes TPC 188.8.131.52 and TPC-R 184.108.40.206.
(2010.07.01) IBM XIV Host Attachment Kit for AIX version 1.5.2.
(2010.07.01) IBM XIV Remote Support Proxy version 1.0.0.
(2010.06.23) IBM XIV Management Tools (XIVGUI, XIVTop, XCLI) version 2.4.3a for all platforms.
(2010.06.23) IBM XIV XCLI (only) for Linux/AIX/Solaris/HPUX, version 2.4.3.
(2010.06.21) ATS XIV- Asynchronous Mirror Webinar.
(2010.06.10) IBM XIV Storage System Application Programming Interface Reference.
(2010.07.04) Oracle Architecture and Tuning on AIX v2.0.
(2010.06.30) Basic Monitoring of I/O on AIX.
(2010.06.11) AIX SDDPCM System Crash During a Dynamic Hardware Replacement of Controller A or B on a DS4K/DS5K Storage Subsystem
(2010.06.07) All hdisks and vpath devices must be removed from host system before upgrading to SDD host attachment script 220.127.116.11 and above. All MPIO hdisks must be removed from host system before upgrading to SDDPCM host attachment script 18.104.22.168.
(2010.06.04) SDDPCM open path failures and VIOS VTD configuration failures.
(2010.06.03) SDD User’s Guide correction for pcmquerypr tool.
anthonyv 2000004B9K Tags:  ds5100 2107 ds6000 1750 shark ds5300 ds480 ds8000 2105 xiv ds3400 storwize v7000 8,277 Views
For many years I have been working on a document that lets you translate a World Wide Port Name (WWPN) into a physical location on an IBM Storage System.
I blogged recently about how SVC and Storwize V7000 WWPNs have a slightly different layout.
The contents of that blog entry come straight from that document.
I have now pushed that document out to IBM Techdocs.
You can download it from here:
Feel free to share any feedback you have and share it with your colleagues.
I know I have already blogged about the XIV GUI and how it just keeps getting better and better....
But I feel the need to share yet another improvement to the way the GUI presents information.
In this case its an additional widget to show the health of each module in the XIV.
A fully configured XIV consists of 15 modules, each module containing components like fans, power supplies and disk drives.
In addition it is of course running firmware (the secret sauce of the XIV).
Another new feature is that now when you hover over the left hand side of each module, a small magnifying glass appears.
When it does, just left click on your mouse and the module slides out (virtually of course!).
If you then hover over a component within the module, health information is displayed. How nice is that?
Don't forget, you can download the GUI and just logon as p10demomode to check it out for yourself (without an XIV).
If you have an existing XIV, its time to upgrade your XIV GUI to version 2.4.3 Build 11.
When your buying a car it's worth opening the boot (that's the trunk for my American friends) and looking at the spare to see what kind it is. Car manufacturers sometimes choose to sacrifice a full spare to save space (or cost). I can understand the motivation, but there is nothing worse than having a flat and then finding that your spare is half the tyre you expected it to be.
With low end fibre channel switches there is a similar challenge when working to achieve the lowest cost and smallest footprint in a 1U form factor. The main way it expresses itself is with power supplies.
The IBM SAN24B-4 (a 24 port switch) is a case in point as it only has one fixed power supply. This of course means that if that power supply fails, then that switch will be down and the entire unit will have to be replaced. If you have dual fabrics (two switches) with dual pathed hosts, then this should not cause an application outage, but it may not be what you expected. You also need to ensure that each switch is connected to a different power rail (and/or UPS) to cater for building power issues.
How to avoid this? Purchase the slightly larger IBM SAN40B-4 (a 40 port switch) which comes with two hot swap power supplies as standard. It's a little more expensive (which makes sense as it has more ports and more hardware) but also offers redundant power and greater scaleability.
Of course in the end you need to select the switch which matches your budget. The SAN24B-4 starts at only 8 ports active while the SAN40B-4 starts at 24 ports active, so the SAN24B-4 will always be a cheaper purchase. The SAN24B-4 is also much smaller, lighter (it weighs 4.35 kg versus 9.34 kg) and uses less power (48 W versus 84 W).
My preference? Well I would always choose to use a switch with dual redundant hot-swappable power supplies, but then I am not the person signing the cheques. What I would suggest is that if you choose the SAN24B-4 then you need to ensure your backing up your switch config (especially if your running single switch fabrics). You could look atSimply-Save-Your-SAN as one way to do this.
And no... that is not my car. By shear synchronicity I was thinking about this issue when I spotted this car in the carpark at Southgate. Timing is everything.
For the next few weeks I may not blog as frequently. It's not that I am tired of writing, but I will be writing on a different subject: Helping to update the four XIV Redbooks.
IBM Redbooks are one of the many ways that IBM differentiates itself from its competitors. They are very detailed how-to guides that IBM gives away for free, you don't even need a userid to download them. IBMs customers and business partners use them extensively and IBMs competitors love them too (for different reasons).
With the General Availability date of XIV Gen3 rapidly approaching, the Redbooks of course need to be updated. We have assembled a great team of residents (which due to the timing of the residency, could not include non-IBMers) and have started our chapter updates. Some of the chapters I have already picked up include Monitoring, Volume Copies and SVC migration with XIV. I am re-learning the joys of Adobe FrameMaker and have actually had the pleasure of running I/O to an XIV Gen3 (in fact two of them).
So my only question to all of you is: What do you want to see in the next XIV Redbook?
Things have been pretty revolting lately, and I am not talking about Tunisia or Egypt or Libya (thought actually they could equally apply to my story).
What I am talking about is mother nature, and she is pretty angry with us right now.
In the last few months Australia and New Zealand have seen massive floods in Queensland, Victoria and Western Australia, destructive cyclones hitting Queensland and Western Australia, ferocious bush fires in Western Australia and most recently, a massive earthquake in New Zealand.
The personal loss of life and of property have been shocking and tragic. Each of these events have reminded me how quickly everything we hold dear can be taken away in an instant... by an event over which you have no control.
Which leads me to storage clouds....
If something can be stored electronically, then it can be stored in a cloud. A cloud that is hopefully well backed up, and far away from your own personal location. And no this is not an advertisement... its a suggestion....
Given the events of the last few months, I have started using a storage cloud provider to protect my photos, my music and my insurance information.
I looked for cloud storage providers who:
I considered the following uses:
Let me give you an example of a document I would never want to have to replace....
My son is practicing to get his drivers license. In Victoria you need 120 hours of driving experience recorded in a log book. This log book needs to be filled in every time he drives the car. If the log book is lost... those 120 hours would need to be driven again. I cannot tell you how hard it is to find 120 hours of driving opportunities (and I heartily support the 120 hours scheme!). Even if you did feel inclined to create fake entries to recreate the book (which is illegal), frankly creating 120 hours of fake driving log entires would be very hard work. To make things worse... where I am storing this booklet? In the car of course (which is the most convenient place to store it). So what happens if the car is stolen? There goes the logbook.... So the plan I work on is that every time a page is filled up, I scan that page as an image stored on my laptop. The image goes into a folder that is automatically backed up to the cloud. Yes it does depend on my being diligent, but the actual process of copying the file somewhere else is automatic. Now I have 3 copies... the original, the scanned image on my laptop and a third (automatically created) copy way off in the cloud somewhere.
As for personal recommendations:
1) Get 2 GB free on Dropbox. This is a great point solution and a great way to dip your toes in.
Have there been issues with storage cloud providers? A quick search reveals stories like: Flikr deleted a users data and Carbonite lost data due to hardware failure. Still... I have no plans to store my ONLY copy of data in the cloud. For me its a backup medium... not a primary storage location.
Are you convinced?
Oh... and my son? He is on 89 driving hours... 31 to go....
IBM is announcing a set of remarkable new storage products and enhancements.
· Storage Efficiency
· Ease of use
· Smart technology
The announcements show not only IBMs significant investment in storage but also IBMs tremendous depth of knowledge and experience.
You will rapidly see that the focus is on our new Midrange Storage product, the Storwize V7000. However this is only one of four major releases that you will see (plus many more other incremental releases). From a product perspective the big new announcements are:
XIV. The XIV will support the VMWare VAAI API by updating the firmware to version 10.2.4. To remind you what I am talking about, check out my earlier blog on this subject here.
Storwize V7000. This is a major new product offering in the midrange space. It takes the intelligence and history of the SVC; brings in some disk controller technology from the DS8000; adds SAS version 2 disk enclosures; provides the sub-LUN performance benefits delivered by Easy Tier; uses a simplified GUI influenced strongly by XIV and has a simplified licensing structure. This is all put into a 2U modular form factor. Because the Storwize V7000 uses the same code base as the SAN Volume Controller (SVC), it brings all the smarts of SVC including virtualized disk (using both internal SAS disks and external storage controllers), thin provisioning, transparent data migration and mirroring (including Metro and Global Mirror). Right now there is no RACE technology in the Storwize V7000 (despite IBM using the Storwize brand). But I think you can take the name as a hint of things to come.
DS8800. This is a fantastic incremental new development in the DS8000 family. It takes the long history of DS8000 development and combines it with small form factor (2.5”) SAS version 2 disks connected via 8 Gbps host adapters and 8 Gbps device adapters. The performance numbers, the environmental and floor-space requirements are all improved by a significant factor. It positions the DS8000 for many years of new functions and features.
SVC. For SVC we are releasing SVC version 6.1. This is a major software update to the SVC code. It delivers a remarkable new GUI with Easy Tier and a whole raft of functional improvements.
Other announcements will include enhancements to TPC, IBM Director, the DS3500 and Softek TDMF.
As soon as I have the announce letter URLS, I will post them. There is clearly plenty more to come.
Steve Duplessie from the Enterprise Strategy Group sent out an amusing tweet the other day. He said:
I am unsure about unnatural love, but perhaps the level of enthusiasm he is seeing comes from: ease of use, awesome GUI, consistent performance, freedom from planning RAID groups, simple growth and upgrade path... I could keep going... it all adds up.
So if you are a member of the cult of XIV, I have a little present for you:
Here is what you need to do:
1) Download XIV Capacity Report 3.7 from this link. Click where it says Downloading this file.
2) You will get a zip file with five files in it. Unzip them into a folder on a Windows workstation. The Windows workstation also needs the XIV GUI installed on it (actually you only need the XCLI, but the Windows version of the GUI will give you that).
3) Of the five files you just unzipped, you need to edit the file called: xiv_capacity_report_get_files.vbs. Open that file with a text editor (such as Notepad). The easiest way to do this is to right-select the file and choose edit.
4) You need to edit the section that looks like this:
' *********** Edit this list of IP/names and user/password for your own configs ************************ myConfigs.Add "1", "-m 22.214.171.124 -u admin -p adminadmin" myConfigs.Add "2", "-m 126.96.36.199 -u admin -p adminadmin"
Lets say you have two XIVs, the details for which are:
XIV1 : Management: IP 10.1.10.100 Userid: admin Password: passw0rd
So we edit the section I mentioned above and make it look like this:
' *********** Edit this list of IP/names and user/password for your own configs ************************ myConfigs.Add "1", "-m 10.1.10.100 -u admin -p passw0rd" myConfigs.Add "2", "-m 10.1.20.100 -u admin -p passw0rd"
Now save the file and we are done editing. If you only have one XIV, then delete the line starting with myConfigs.Add "2" (or put an apostrophe at the start of the line to comment it out). If you have more than two XIVs, just add extra lines for myConfigs.Add "3", myConfigs.Add "4" and so on, adding details for each machine as shown above. You can ignore the lines further down in the file that start with an apostrophe, these are just examples.
Unless you acquire another XIV, you will not have to do this file editing again.
5) Now double-click on the icon: xiv_create_capacity_report.bat. This is a Windows bat file that will create a Windows command prompt while it is running. It uses XCLI commands, so if the XIV GUI or XCLI is not installed, it won't work. The output will be a new folder with today's date and time. Inside that folder will be a report that will be named something like: xiv_capacity_report_2011_10_30_17_6_36.xls
You can now open the report and check it out (presuming you have Microsoft Excel or some other software that can open XLS files). On my laptop I get a message talking about file formats, when I open the file.
You can ignore this message. If you save the file as an XLS you won't get this message again.
The report itself will have five tabs as shown below:
For every column in every tab, filtering (or sorting) is already setup. This makes it really easy to re-arrange the data to suit what you're looking for.
So please download the tool and try it out. Service providers love using this tool for reporting, it is so quick and easy to set up and run. Every time you run the tool you get a new report, so you can automate report creation and keep a nice history.
If you were signed into IBM developerWorks when you downloaded the tool and an update is made available, you should be notified by email, provided your IBM ID is set-up properly with a valid e-mail address.
And as for cults... there is only one cult I ever really liked and they really were called The Cult. The video takes about 15 seconds to get going and yes, the lead singer is dressed like a pirate. Enjoy! (if you like 80s rock...)
The XIV GUI (which you can download here) is available for a very wide variety of platforms:
My gut feel is that the truly vast number of installations and downloads are for the Windows GUI version. I suspect the rest rarely get a look in, I mean do people actually use the XIV GUI on AIX, Solaris or HP-UX hosts? I really doubt it.
However you can also get just the XIV command line interface (also called the XCLI) for the following operating systems:
Now I can see why these would be popular. Being able to script XIV CLI commands and execute them locally makes perfect sense, so all the major Operating Systems are represented. But it is curious that a separate Windows CLI installer is not listed. Of course you get the XIV CLI when you install the Windows GUI, but I am equally curious if there are users who want to avoid having the GUI present on servers that only need the CLI.
An example of this would be if you use Commvault SnapProtect with XIV, since each client will need to issue XCLI commands to drive the hardware based snapshots. So the good news is that you can actually force the XIV GUI installer to install only the CLI component. You can do this by using the following command (in a command prompt with the XIV GUI installer file in that directory):
xivgui-3.0.1-build3-win.exe /SP- /NOCANCEL /VERYSILENT /NORESTART /TYPE="xcli" /LOG="%SYSTEMDRIVE%\xcli.txt"
You will need to change the file name at the start of the command to suit the version you have downloaded. I tested it on version 3.01 and it worked just fine, all it installed was the XIV CLI. So keep this in your back pocket and use when required.
And if you ARE using the XIV GUI on AIX, HP-UX or Solaris, I would love to hear which platform you are using and why. And if you are still using Windows ME.... your persistence is admirable.
On Friday November 18, 2011, IBMers around the world engaged in the worlds first group therapy session held entirely in Twitter!
It focused entirely on tweeting classic lines heard in day to day life at IBM, using the hashtag #stuffibmerssay. The result was an amusing out-pouring that kept growing as the day went on (and has not stopped). Karl Roche did a great summary write-up here where he captured some of the more classic stuff. Holly Neilson also wrote a nice blog post on the subject here.
You will notice many of the tweets focus on phone conferences, which are without a doubt the greatest contributor to and destroyer of, productivity in IBM. Classics such as this one came up again and again (and it's a common problem for me):
Nicely counter-balanced by failures to mute like these:
Enjoy.... and if you're an IBMer, please feel free to contribute, it's all in good fun.