Have you tried rebooting?

Brocade CLI Zoning Tutorial

// March 11th, 2010 // No Comments » // Technical Know-It-All

Given that more and more features within Brocade SAN switches are configured using zones, thought I would share this quick CLI guide for those looking to script this.

Zoning is organised as such

- Every SAN device has a unique WWN (much like how IP devices have MAC addresses)
- WWN’s are then mapped to aliases
- Multiple aliases then form a zone
- Multiple zones then form a config
- Nutshell, WWN->Aliases->Zones->Config

So here are the steps to create a zones quickly using CLI.

1. Ensure you have noted down the device WWN and assign it a usable name for alias. WWN’s for devices can be found using “switchshow“. In this example, I will be mapping the following devices to the appropriate names

10:00:00:00:00:00:00:01 -> Server_HBA01
50:00:00:00:00:00:00:01 -> Storage_P01
50:00:00:00:00:00:00:02 -> Storage_P02

alicreate “Server_HBA01″, “10:00:00:00:00:00:00:01″

alicreate “Storage_P01″, “50:00:00:00:00:00:00:01″

alicreate “Storage_P02″, “50:00:00:00:00:00:00:02″

2. Next, we want to group these 3 members into a single zone so they can have access to each other. Let’s create a zone called “Zone_svr2_hba01_str_p01_str_po2″. Remember that zone members are case sensitive.

zonecreate “Zone_svr2_hba01_str_p01_str_p02″, “Server_HBA01; Storage_P01; Storage_P02″

3. After completing step 2, put the newly created zone into a config. For simplicity, I shall call this “Config_Test”. Again this is case sensitive.

cfgcreate “Config_Test”, “Zone_svr2_hba01_str_p01_str_p02″

4. Verify the zones using “cfgshow“. The zones should only show up under “Defined Configuration”. To make this zones active, you will need to enable it.

cfgenable “Config_Test”

5. Now if you run “cfgshow” again, you will realise that the “Defined Configuration” and “Effective Configuration” is the same. This is when you know the zones are activated.

6. To script this, you can simply prepare all commands in Notepad and open up a putty session then cut and paste it. You can also use SSH scripts if required.

The Buzz About FCoE and CEE

// February 26th, 2010 // No Comments » // Technical Know-It-All

The new buzzword these days in the Storage / Networking space is FCoE (fiber channel over ethernet) and CEE (converged enhanced ethernet). For those who are unfamiliar with the whole concept, in layman terms, it is a convergence of the traditional TCP/IP networks and traditional SAN networks into a single giant network.

While it is ideal from a C-Level perspective to streamline processes, reduce costs, go green and try doing more with less, at the technical level, it is never as easy as the vendors make it seem. Many industry experts have claimed that this new protocol will eventually replace the ever resilient FC Protocol and Ethernet. The jist of it is that, everything that has to do with “networking” will run on this newly improved protocol.

While this “could” be true, here are some points to ponder upon before taking the leap of faith to run your entire production systems on CEE and FCoE.

1. TCP/IP has never been known to be the most secure protocol (before I get flamed by the networking experts, it can potentially be secured with the right amount of tweaking). Compared to FC, while some may disagree, it is more secure in some ways (for starters, given that not every laptop will have an FC port to begin with, but having said that, more often than not SAN administrators take this for granted). By merging the 2 protocols together, suddenly we have a scenario where security might now be a concern to the traditional SAN guys.

2. Usually in large environments there is usually a Storage Team and Network Team. With the convergence, a discussion of job roles would probably emerge, and potentially job cuts (fingers crossed).

3. Standards. Currently, many of the protocols/standard are still very much in the review stage with IETF, T11 and the lot. Ethernet is stable today after many years of revision while CEE will take some time before reaching that level of maturity.

4. Physical infrastructures such as cabling are probably not ready today for a complete deployment. Many are still running cabling works that are barely rated for 1Gbit, let alone the 10-40Gbit as promised by CEE/FCoE. Also, existing Ethernet switches and FC switches are not meant to run this new protocol. Slowly and surely, vendors are releasing firmware updates to enable them to support the protocol in the legacy units, but having said that, the additional overheads of the protocol was never meant to run on existing hardware, so we might never know if it will be able to handle it. Newly released FCoE/CEE ready devices are slowly coming to market and today cost quite a fair bit.

Obviously, my little list above is not all conclusive, but my 2 cents of what I would probably be concerned about when thinking of rolling it out.

So in summary, I am not saying that CEE/FCoE is doomed for failure but maybe, just maybe, it is still too early for it to be totally viable in a full fledge production environment. I do believe that CEE/FCoE will take off and be a prominent protocol some day. Having said that I don’t think it will oust or replace traditional FC and Ethernet anytime soon as some major vendors are suggesting. It takes more than lowering cost and bandwidth to achieve total protocol dominance.

Just ask iSCSI and Infiniband.

Brocade SAN Health Tutorial

// December 10th, 2009 // 2 Comments » // Technical Know-It-All

As promised before, I will try to explain in detail how to work Brocade SAN Health. Just a recap, Brocade SH is an exceptionally informative tool that allows you to capture performance, and configuration data from Brocade and McData SAN fabrics. It will then take this data and churn out a very useful Visio diagram and an Excel file.

Alright, let’s start!

1. Firstly, you would need to download the tool from the Brocade website. Once downloaded, the install takes like 3 secs. Fire up the tool and you will see a screen like above.

2. Click on “New”, and it will prompt you to fill up all your contact details. Fill it in accordingly.

3. Click on the “Report Return” tab, and fill in the your email address. It is “IMPORTANT” to get your email address right here because ultimately, this is where your report is going to be sent to.

4. Click on the “SAN Details” tab next, and give your audited SAN a name.

5. Next click on “Add Switches”. Input the IP addresses and login details of the switches. Usually, you would only require 1 switch from each fabric. Once it successfully logs in to the first switch, the rest is discovered in-band.

6. Click on “Fabric Details”. Here fill up fabric name, vendor details, and the duration of this audit.

7. Verify that all the “Green Smiley” faces are there. If not click on each of those and make sure they are green. When that’s done, you are ready to do a preflight check! Go to the “Start Audit” tab and run “Pre-Flight Check”. If pre-flight is good, the “Start Audit” button will be available.

8. It will then start running. Depending on how long you want it to capture, you can probably minimise the window and let it run in the background. I usually recommend 24 hours just so you get a complete trending of the peaks and lows.

9. Once complete, it will encrypt the file (so it is safe to be sent across the Internet). Keep clicking “Next” and read the on-screen instructions.

10. The last screen will tell you where the <filename>.BSH ( Brocade San Health) file is saved. You will then need to forward the *.BSH file to SHUpload@brocade.com. This file will then get processed in the backend by Brocade server’s and then you should receive a reply in 24 hours (more often than not, you will get it in 4-5 hrs). In the event that you don’t hear from them in that time frame, email SHAdmin@brocade.com and let them know the filename of the *.BSH file, they will let you know if it’s in the queue.

That is it! Simple!

Many of my customers swear on this, and they do it on a weekly basis just to keep their SAN environments in check. So give it a go. Things that are FREE are rarely this good & usefull….

P/S : You cannot capture performance data from McData fabrics and there are no roadmaps for this.

Ethernet world is a jungle to a SAN guy…

// December 10th, 2009 // No Comments » // Technical Know-It-All

The last couple of days, I spent many long hours sitting in a tiny room with extremely loud carrier grade switches, blowing hot air in my face, learning to configure and set up MPLS, VPLS, VLL, PB, PBB, MRP and the list goes on.

It’s been many years since, that I have turned up onsite only to have technical jargon’s thrown at me that I have no clue (at all) what its all about. Having said that, I must say it has been quite an experience to finally have a feel what goes on behind your home internet connection.

Still getting to grips with how all these technologies fit in to the whole picture though. I managed to find a good whitepaper by Nortel that explains the evolution of Provider Bridges (PB) and Provider Backbone Bridges (PBB) which really helped cleared up some questions I had.

It will be great if anyone reading can share with me some whitepapers on VPLS and VLL.

SAN Assessments

// November 20th, 2009 // No Comments » // Technical Know-It-All

Just conducted another SAN Assessment this afternoon. While SAN Assessments are generally tedius and boring projects, I do get a sense of achievement and pride when I help another customer spot out an issue that nobody has managed to.

So I thought I would share a couple of goodies for SAN Administrators out there who wants to give their SAN a quick assessment and see how they are doing.

First get to the Brocade website and download this tool “SAN Health”. Just a side note, this tool only collects info from Brocade, and McData fabrics. Performance captures are only enabled on Brocade fabrics, not McData. If you are running Cisco, you are somewhat out of luck. You could still use SAN Health to capture Cisco fabrics but don’t expect it to return much. The capture utilizes SSH/Telnet to access the switches/directors and dump data off them. Once thats complete, you will need to upload it to Brocade and you should receive an email in 2-3 hours time from Brocade. The email will contain a zip file with and Excel spreadsheet and a Visio diagram.

I will try to post some screenshots when i get the chance.

Any how, there are many things to look out for in the excel spreadsheets from firmwares revisions to errors. For firmware revisions, check with your OEM vendors to see what is the latest supported versions and compare it against yours. For errors, pay additional attention to CRC errors, and Encoding Out errors. If you have high encoding out errors, chances are you have a faulty cable. If you get a combination of both, good chance you might have a SFP issue.

Feel free to post comments if you need more help. Meanwhile, if you need help with any SAN issues, you can search for Brocade Services APJ on Facebook. A few Brocade Consultants monitor that for questions.

UPDATED : Brocade SAN Health Step-by-Step