I love USB keys, I love free ones, conferences give away ones and ones shaped like lego blocks. The exciting thing (for me) is that if you buy a Storwize V7000, you also get a USB key: A key which has two fundamental purposes:
It's used to make installation very quick and easy (which it does very well!).
It's used to reset the superuser password (in case you forget what it is) or to set the service IP addresses (in case you didn't set them like I suggested you do ).
This is all well and good but what happens when you lose it, borrow it or accidentally throw it out? (oops) If you are searching for it, yours may well have looked like this:
So what to do? The answer is: It's OK, there is nothing magic about this key. In fact the key contains just one piece of software, which you can get from here. Just download the initialization tool and copy it onto your own USB key. The original key also had an Autorun file, but you don't need that (actually I object to auto-running USB keys anyway).
BUT... and there is always a but... I cannot guarantee that EVERY USB key you try will work. Why not? Because some USB keys are formatted strangely or insist on running unique applications before they will work. There is some good, simple advice on the InfoCenter that you can find here. The main trick is to use a USB key that is formatted with the FAT32, EXT2, or EXT3 file system on its first partition and does not need to auto-run any applications before working.
The big question of course is which drive type to choose? The answer is that ideally you should possess three pieces of information:
How much usable space do you need in GB or TiB? Don't confuse binary and decimal!
What is your typical I/O profile. For instance 70% reads 30% writes, 32KB block size.
What are your IOPS and response time requirements?
Armed with this information, get your IBM Sales Rep or Business Partner to model your requirements using Capacity Magic and Disk Magic. These modelling tools will tell you how much usable capacity a particular configuration will give you and what performance you can expect to get from it (given a particular I/O profile). If you don't know your I/O profile or IOPS requirements, you can still see performance modeling using industry standard benchmarks.
I am getting this question on a very regular basis:
"We have just upgraded to ESXi 5.0 but we cannot find the VAAI driver on the IBM Website"
The answer? There is no vendor supplied driver because no driver is needed. ESXi 5.0 uses a SCSI T10 compliant set of commands that all vendors need to support for VAAI to work.
But of course in the tradition of all answered questions, it leads to another question:
"Once I have upgraded to ESXi 5.0 how can I tell if VAAI is really working?"
The good news is that it is very easy to spot if ESXi 5.0 has detected a VAAI capable LUN. The moment a new LUN is detected by ESXi 5.0 it tries out an Atomic Test and Set command. If that works, you will see that Hardware Acceleration shows as Supported in vCenter. In the screen capture below I have three datastores, two from XIV and one from Storwize V7000, all presented to an ESXi 5.0 server. I dragged the Hardware Acceleration column over from the right hand side to help with the screen capture (in case your vCenter looks different), but you can see the Hardware Acceleration column shows each DataStore as Supported (and did so the moment the volume was detected).
Of course having seen the Hardware Acceleration Supported message only proves that Atomic Test and Set works. To confirm if XCopy (Hardware Accelerated Move) is working, on SVC or Storwize V7000 we can use the Performance monitoring panel. In the example below I first performed a storage vMotion, moving a virtual machine between two Datastores located on the same Storwize V7000 (running 18.104.22.168 firmware). I then performed a clone of the same virtual machine, where the source was on one datastore and the target was placed on another (but both located on the same Storwize V7000). What you can clearly see is that both operations (storage vMotion and cloning) generated no volume traffic, only MDisk traffic. This means that the ESXi server is doing none of the work and the storage is doing all of the work.
With the 6.3 release of the Storwize V7000 and SVC code (which I blogged about here), there are so many new features and functions that I have plenty more to blog about!
The first new feature I blogged about was LDAP support, but an existing feature that has been enhanced is the performance monitor (brought in with release 6.2). When this first came out I put a video on You Tube showing what metrics could be displayed in that release. This is a sped up image with no voiceover:
Now with release 6.3 IBM has added separate graphs for reads and writes plus the ability to display IOPS or MBPS, plus the ability to display graphs of read and write latency. Nice! I got so excited I made another You Tube video, this one with narration. So now you can compare the new to the old:
Once your SVC or Storwize V7000 is upgraded to version 6.3 you can start using LDAP for authentication. This means that when you logon, you authenticate with your domain user-id and password rather than a locally created user-id and password.
So why is this important?
It saves you having to configure every user on every SVC or Storwize V7000. If you have multiple machines this makes it far more efficient to set up authentication.
It means that when commands are executed on the SVC or Storwize V7000, the audit log will show the domain username that issued that command, rather than a local username, or worse just superuser (i.e. who mapped that volume? The superuser did.... who? )
It gives you central control over access. If someone leaves the company you just need to remove access at the domain controller, meaning there won't be orphan user-ids left on your Storage equipment.
So as an exercise I added my lab Storwize V7000 to our domain to show how it is done. This example also applies to an SVC so don't be confused if I only refer to Storwize V7000 from now on.
The first task is to negotiate with your Domain administrator to get a new group setup on the domain. In this example I use a group called IBM_Storage_Admins which lets me use this group for various storage devices (such as an XIV or a SAN Switch).
To create this group we need to logon to the Domain Controller and configure Active Directory. An easy way to do this from the AD controller is to go to Start → Run and type dsa.msc and hit OK. The Active Directory Users and Computers Management Console should open.
Select the groups icon to create a new group.
Enter your group name, in my case: IBM_Storage_Admins and hit OK.
Now right select relevant users who need access to the storage and add them to the IBM_Storage_Admins group. In this example I have selected Anthony (which uses anthonyv as a username).
In this example we are adding anthony into the IBM_Storage_Admins group:
Now it is time to configure the Storwize V7000 so start the Web GUI and logon as Superuser.
Firstly we go to Settings → Directory Services:
We choose the button to Configure Remote Authentication:
We choose LDAP and hit next.
We choose Microsoft Active Directory with no Transport layer Security. We then expand the Advanced Settings. My lab domain is ad.mel.stg.ibm so I use the Administrator ID on the Domain Controller to authenticate access. You could use any user that has authority to query the LDAP directory. We then hit Next.
We then add the domain controller which in this example is 10.1.60.50 and the base domain name chopped into pieces (so ad.mel.stg.ibm becomes dc=ad,dc=mel,dc=stg,dc=ibm ) and hit Finish.
Provided the command completes successfully we have defined the domain controller to the Storwize V7000. Now we need to add a group. Go to Access → Users.
Select the option to add a New User Group.
In this example we want to add a group for users allowed full admin access to the Storwize V7000. This matches the group we created on the Domain Controller. So we call the group IBM_Storage_Admins and we use the Security Administrator role (which is the most powerful role) and tick the box to enable LDAP for this group.
Now to test, I logon to the Storwize V7000 using the domain user-id anthonyv with that users domain password. Remember this user is not defined on the Storwize V7000 itself and that if it all goes wrong, we can still logon as Superuser.
Now I create a volume and delete it. Then I check the audit log from Access → Audit log.
Sure enough, we see exactly who did that command.
This is a great outcome for security,auditing and for easy access administration.
If you have issues, from the Settings → Directory Services menu, use the Global Actions dropdown on the right hand side to Test LDAP Connections and Authentication or re-configure LDAP.
If you already have existing users (what we call Local users), configuring remote authentication using LDAP does not disable or invalidate those local user-ids. This means you can either logon with a local user-id or logon with a Domain user-id. This is handy if the domain controller fails but can confuse you if your local user name and your domain user name are the same name (for example both anthonyv). The Storwize V7000 will look you up in the local user name list first. I suggest removing all local users (except superuser) as this will reduce confusion but still leave you a backdoor in case remote authentication stops working.
If you see any mistakes or have suggestions to improve the way I described this, please let me know.
The latest release of SVC and Storwize V7000 firmware is now available for download. The major new features that are added with this release are:
Global Mirror with Change Volumes
Native LDAP Authentication
Extended distance split clusters (for SVC)
Support for 4096 host WWPNs
These are some great new features. The ability to use Global Mirror with Change Volumes means clients can now mirror across far smaller pipes, while the increase in host WWPNs is very welcome news for NPIV installations that are suffering from WWPN sprawl.
If you plan to upgrade, firstly grab the new Upgrade Test Utility from here. The links to the Storwize V7000 and SVC versions are both on that page. Remember you can run this test as many times as you want whenever you want, to check the health of your device for upgrade. When you run the upgrade test utility on a Storwize V7000 you may get a message that your disks have down-level firmware. The process to update them is documented here.
If you're using a Storwize V7000 you can grab the 22.214.171.124 code from here. If you're using an SVC you can grab the 126.96.36.199 code from here. I am sending you to the compatibility matrix page because you should always check that your from level is ok for your to level.
To run the upgrade go to Configuration (the spanner icon) → Advanced → Upgrade Software →Launch Upgrade Wizard
I have not shown all the panels you will see because it is very much a follow-your-nose task, but in essence, first we feed it the Upgrade Test Utility file and run that test.
If you get warnings you may need to act on these. If you are unsure what to do to resolve a warning message, place a service call.
Once the test passes or you're happy you understand the warnings, we now point it at the code package and wait for it to copy across and keep hitting Next.
The application of the code shuts down and reboots each controller, with a 30 minute gap in between. You will transition from this (both nodes down-level, node1 being upgraded):
To this (node1 upgraded, node2 still online but waiting for 30 minutes):
When node2 starts the upgrade the GUI will failover to node1 and be upgraded to the new version. You will notice the difference immediately, it has a different look and feel. Please don't be tempted to play with the new functions until both controllers are upgraded! Wait until you see this (note a slight change, the GUI flow is now Settings (the spanner icon) → General → Upgrade Software:
Now your complete it is time to start checking out what is new... but that's a whole different blog post!
Henry Ford has long been quoted as having said: "Any customer can have a car painted any colour that he wants so long as it is black."
While there is some debate on what Mr Ford exactly said, it's clear that for some time now IBM has heartily embraced this philosophy with a succession of all black machines (occasionally graced with a coloured stripe). So I was rather excited to spot something new in the IBM Melbourne demo center: an IBM Netezza (pronounced net-ease-a) It's rack door is one of the coolest IBM covers I have seen in years!
Even the internal blades look cool (I love the big N).
In case your curious, IBM® Netezza® Analytics is a purpose-built advanced analytics platform that enables your enterprise to get the most out of its data, giving you quicker answers to increasingly complex questions. It is the simple appliance for serious analytics.
Of course while I should have been thinking about big data and smart analytics, instead I have been reminiscing about IBM machines with coloured covers. For instance the IBM 3350 (storage from the 1970s) could be ordered with covers that were red... (Actually I think the correct name was garnet rose).
As far as I can tell, IBM have not offered coloured panels on Enterprise kit since June 28, 2002.
Prior to this devices could be ordered with feature codes like:
#9060 Willow green #9061 Garnet rose #9062 Sunrise yellow #9063 Classic blue #9064 Charcoal brown #9065 Pebble gray.
While it is easy to find pictures of machines with Classic Blue covers like these 3380s (with 3880 control unit)
And even visions of a red computer room (with an all white 3800 printer on the left hand side):
The only picture I have found so far that shows a yellow machine appears to have faded to orange over the years (I don't think IBM sold orange System/38s?).
I did some more digging and found this great Youtube video. You can see some old System 360 kit with red covers and at 00:46 there are some machines in custom bright yellow! The client literally ordered the machines painted with a custom tint. That takescase modding to a whole new level.
So should IBM be embracing the new cool and coming out with a bright orange XIV? How about a Storwize V7000 in fluorescent blue? A man can dream....
And if you want to see more about Netezza and it's incredibly cool rack (and even cooler architecture), check this video out:
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: A really nice and simple reporting tool.
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 188.8.131.52 -u admin -p adminadmin"
myConfigs.Add "2", "-m 184.108.40.206 -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 XIV2 : Management: IP 10.1.20.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.
Arrays Tab List details about all your XIVs including: serial numbers, code versions, soft and hard capacity, how much of the soft and hard space is allocated, how much is free and how much space is being consumed. Great place to grab the machine serial number or confirm which machine has space available.
Pools tab Lists every pool in every XIV showing every possible sizing metric you could possibly want. Cells will be coloured red or yellow if limits are being reached. It is a great place to confirm if your pools are filling up and whether a pool is a good candidate to be changed to Thin Provisioning. Sort column L (allocated vs used) or column N (Hard Capacity Utilization) to identify good candidates for swapping to Thin Provisioning. These are the pools that can give up some hard space.
Hosts tab Will list every defined host for every XIV. You can straight away spot how much space has been allocated to each host and more importantly, how much is being used. Cells will be coloured yellow or red if limits are being reached. Some nice tricks:
Sort by column F (Allocated vs Used) to identify hosts that have asked for lots of space, but not used much of it.
Compare column G (# of volumes) with column I (# volumes mirrored). You may have critical hosts that require every volume to be mirrored, so a quick compare will confirm if there are exceptions.
Volumes tab Will list every volume defined on every XIV. This is a great tab to check which volumes are being mirrored, how many snapshots exist for each volume and how much space is being used by each volume. Again cells in the Used column will be coloured red or yellow if space is becoming short. Some great tricks here:
Sort column F or G (Used GB and %) to identify volumes with no or little data in them. Perhaps they are not really needed? Perhaps they are over-sized or should be in a Thin Provisioning pool.
Sort column H (Mirrored) to identify all volumes where Mirrored = No. Should they be mirrored?
Sort column K (Host Mapped) to identify all volumes not mapped to a host. Unmapped volumes are a great potential source of space!
Failures tab The Failures tab shows any failed components in your machines (like failed disks).
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...)
In you case you hear different, it's time for a few simple facts about XIV:
XIV was founded in 2002 and shipped its first product in 2005. XIV is now up to its third generation in the development process. After over 6 years, XIV is a mature and established product in the marketplace.
IBM has sold over 5000 XIVs: A number IBM is proud and happy to disclose. In fact IBM has been open and honest about sales numbers throughout the program, which speaks volumes about how pleased they are with the success of the product.
Another point about sales numbers: Compared to the XIV, the Storwize V7000 can be sold with a starting capacity of less than 1 TB. The smallest XIV Generation 2 has a starting capacity of 27 TB, while the smallest XIV Gen3 starts at 55 TB. So clearly lower entry point products like the Storwize V7000 will outsell larger Enterprise products like the XIV. The sales numbers of both products continue to be outstanding for their size and class.
There are over 2000 XIV customers, including a considerable number of reference accounts. There are 75 success stories on the IBM XIV Website, which you can checkout here.
IBM has announced the first Storage Performance Council (SPC) result with XIV, the very first on the SPC-2/E benchmark. The XIV Storage System demonstrated its ability to handle Big Data as well as providing associated energy use data. The SPC-2/E result showed that the XIV Storage System provides outstanding enterprise price-performance and Large File Processing (LFP) performance. The numbers? 8259.94 MBPS SPC-2 (LFP) Data Rate and $137.07 SPC-2 (LFP). In case these numbers don't mean much to you, they are truly outstanding, there is only one other competitor who is even in the same ball park. (Price-Performance Source: Storage Performance Council SPC-2 Benchmark Results:http://www.storageperformance.org/results/benchmark_results_spc2, Results current as of 10/20/11). (Thanks to Elizabeth Stahl for the SPC-2/E info).
IBM have offered Enterprise Storage Virtualization since June 2003 with the IBM SAN Volume Controller (SVC). October 2010 saw IBM releasing the Storwize V7000, taking the SVC code and packaging it into a midrange disk product. So now you have four possible choices:
Use SVC to virtualize your storage.
Use Storwize V7000 to provide internal SAS drives plus virtualize your storage.
Use Storwize V7000 as a midrange disk product.
Use Storwize V7000 virtualized behind SVC.
The great thing is that all four choices are valid and all four choices work just fine. But for customers already using SVC, or considering SVC, the question then becomes, should I virtualize a Storwize V7000 behind an SVC? Does this makes sense?
The short answer: YES!
We have a great many customers happily doing this, so I thought I would share some common questions I get around configuration. Firstly there is an InfoCenter page on this which you will find here. Secondly there is a debate about whether we should create individual volume/arrays on the Storwize V7000 or just create a single pool on the Storwize V7000 (which equates to striping on striping). More bench marking is being done to see if one method is truly better than the other, so until then I recommend the method described below. If you have already done stripe on stripe, don't go changing anything until I update this post.
How many ports should I use for Zoning?
The Storwize V7000 has 8 Fibre Channel ports, 4 from each node canister. You need to zone at least two ports from each node canister to your SVC cluster. This is no different to how you would zone a DS5100 or an EMC VNX.
How will the SVC detect the Storwize V7000?
On the SVC you will see two storage controllers, one for each node canister. This is quite normal. The reason for this is that each node canister reports its own WWNN. This is not a problem and will not affect volume failover if one node canister goes offline.
In the example below the SVC has detected two new controllers. The confusing factor is that both report as 2145s, but they are a Storwize V7000. Rename them to reflect what they really are (something like StorwizeV7000_1_Node1 and StorwizeV7000_1_Node2).
How should I define the SVC on the Storwize V7000?
You need to create a new host on the Storwize V7000 and call it something like SVC_1. if the SVC WWPNs don't appear in the WWPN dropdown, you will need to manually add them as shown below:
You can get the SVC WWPNs from your existing zoning or by doing an svcinfo lsnodeagainst each SVC node or display them in the SVC GUI as shown below:
What size Storwize V7000 volumes should I create?
My recommendation is to do the following on the Storwize V7000
Create arrays of preferably 8 disks in size. The ideal number will depend on how many disks you have. On my machine I have 22 disks, so I create three arrays each with seven disks (and one hot spare):
Create one pool for each array:
Create one volume out of each pool (using all space in the pool).
Define the SVC to the Storwize V7000 as a host (as described above) and map all volumes to the SVC.
On the SVC detect all the Storwize V7000 LUNs as MDisks and create one pool.
Now you should have a pool on the SVC that you can use to create volumes to present to your hosts. They will be striped by default, which is exactly what you want.
Hopefully all of this makes sense. Questions and comments very welcome.
For those of you with Apple iPads, you might consider dropping by the Apple Store and picking up your free IBM XIV Mobile Dashboard.
The IBM XIV Mobile Dashboard application can be used to securely monitor the performance and health of your XIV over a Wi-Fi or 3G link. Having downloaded and installed the Mobile Dashboard you will get a lovely XIV Icon:
When you start the Mobile Dashboard you will have the choice to either run in Demo Mode or to connect to an actual XIV. Demo mode can be accessed by selecting the Demo Mode option deep in the lower right hand corner. So you don't actually need an XIV to give it a test drive.
To logon to a real XIV you will need a valid username, password and IP address.
Once connected you have the choice of viewing volume performance or host performance. If you view (hold) the iPad in portrait mode you get a list of up to 27 volumes or hosts ordered by performance metrics (it defaults to ordering by IOPS). If you view the iPad in landscape mode you will get a more graphical output (as per the examples below). There are no options to perform configuration, the dashboard is intended only for monitoring. This means each panel will show the performance and redundancy state of the XIV.
The volume performance panel is shown by default. The example below shows the output when the iPad is operated in landscape mode. From this panel you can see up to 120 seconds worth of performance for a highlighted volume. Use your finger to rotate the arrow on the blue volume icon to switch the display between IOPS, bandwidth (in megabytes per second or MBps) and latency (in milliseconds or MS). The data redundancy state of the XIV is shown in the upper right hand corner (in this example it is in Full Redundancy, but it could be Rebuilding or Redistributing).
The example above shows the output when the iPad is operated in landscape mode. If you instead rotate the iPad to portrait mode, you will get a list of the performance of up to 27 of your busiest volumes.
Now swipe to the left to navigate to the Hosts panel as shown below.
From this panel you can see up to 120 seconds worth of performance for a highlighted host. Use your finger to rotate the arrow on the purple host icon to switch the display between IOPS, bandwidth (in megabytes per second or MBps) and latency (in milliseconds or MS). The data redundancy state of the XIV is shown in the upper right hand corner (in this example it is in Full Redundancy, but it could potentially also be Rebuilding or Redistributing). Swipe to the right to navigate to the Volumes panel.
The example above shows the output when the iPad is operated in landscape mode. If you instead rotate the iPad to portrait mode, you will get a list of the performance of up to 27 of your busiest hosts.
From either the volumes or the hosts panels you can log off from the mobile dashboard using the icon in the upper right hand-most corner of the display. When you log back on, the last used XIV IP address and username will be displayed (but not the password which will need to be entered again).
I can see some nice use cases here. You get a call regarding performance but you are on the road. Are there any problems with the XIV? You can quickly logon with your iPad and confirm if response times are normal and the redundancy state is Full Redundancy.
A better use case... now you can ask your manager to buy you an iPad, so you can monitor your XIV! Let me know how that goes #
I know the walls are coming down... but there are still many organizational barriers that can exist in IT. How about:
The Networking team (who may possibly be allied to or at war with the firewall/security team)
The Storage admin team (possibly split between open and System z)
The Systems admin teams (possibly split between System z and open and then split again into Windows and Unix or VMware and Unix)
The Applications admin teams (don't get me started on how those guys and gals can get split up)
The Security team
Team work and co-operation? Sure it's an option.... but then an option means its optional.... right?
So when vendors come along with plug-ins and products that dare to connect two worlds... is this a unifying force, or is it anti-matter, or do they just get ignored and not used?
A case in point being the IBM Storage Management Console for VMware vCenter which you can download from here. I have written about this plug-in before, but with the release of version 2.6 (that supports vSphere 5.0), I thought I would try something out. Installing the plug-in potentially offloads a lot of storage management from the storage admin to the VMware admin. But what if the storage admin does not WANT to offload this work?
The answer is to give the VMware admin read-only access.
When you configure your IBM storage device to the plug-in, you supply the plug-in with log-in credentials (so it can log into your IBM storage device and collect the required information). If the user-id supplied only has read-only access to the XIV for instance, the plug-in still works... but not for any operations that change resources. You cannot see the pools on the XIV, but you can still see your volumes and any snapshots that have been created (but annoyingly you cannot see mirrors).
This does have one big advantage. You can clearly match the VMware datatstore name to the XIV volume name. You can also identify which XIV supplied the volume.
This is must for large installations regardless of what storage admin tasks (if any) you want to allow the VMware admin to perform.
I also tested this with Storwize V7000 with a user in the Monitor category and got pretty well the same results. A nice bonus is that I could also see the state of the mirrors as well as the flashcopies. In the example below, all of this information would normally not be visible to the VMware admin, so this is very handy stuff.
Of course I get to also visit one-man bands where the same (exhausted) individual manages the VMware servers, the Operating System Guests, the Network, the Firewall, the Exchange server, the SQL servers and pretty well everything else including getting the elevators and coffee machine fixed. For those people, they need all the help they can get.
IBM has been selling IBM branded Brocade switches since 2001 when we announced the 8-port 2109-S08 and 16-port 2109-S16. These were classic switches that ran at 1 Gbps. They had a front operator panel with a small keypad (a feature which in the rush to fit in more SFPs, did not appear in future models). Since then IBM has gone on to sell many of Brocades switches and directors.
Sometimes you need to convert a Brocade model name to an IBM model name (or the other way around). One way to assure yourself with scientific accuracy which type of switch you are working on, is to telnet or SSH to a switch and issue a switchshowcommand. You will get a switchType value. In this example, my switch is a switchtype 27.2.
Or if you are using the Web GUI, you can also see the switch type on the opening screen. In this example the switch is a type 34.0.
Having scientifically determined the type of switch, we can now use my decoder ring to determine the IBM machine type, IBM model name and the Brocade model name. I have ordered the switches by Type number. There are three things to note:
Brocade have dropped the Silkworm branding, so I have dropped it too.
Each switch type has sub-types, for example 34.0 and 34.1. The difference is a sub-version number which is normally not published or documented.
IBM announced 16 Gbps SAN switches on August 16, 2011 so I updated the chart on that date.
If you use Data Center Fabric Manager (DCFM), it actually displays the Switch Type using Brocade model names. Here is an example report from the DCFM we are running in my lab. This level of information is very helpful.
Bob Leah is one of our leading lights in the developerWorks team. His blog (found here) is a great resource for Web designers. He recently created a new set of templates to enable a mobile page for developerWorks blogs. You can read his article about the new template here.
This morning I boldly went and installed the new templates and so far I think it looks fantastic, not only on the iPhone, but also the iPad and on regular browsers. My only complaint is that I lost the banner image of my Golden Retriever (my loyal hound Suzie). Bob assures me she will reappear soon. In the meantime, I would love to hear feedback about the new template. This is what it looks like on my iPhone: