Monthly Archives: February 2011

Tech Field Day – Drobo

Posted on by
1

Drobo, the company formerly known as Data Robotics, is one that has a long history with Tech Field Day. They were presenters at TFD 1 and have been associated with several since then. I hadn’t heard much about them prior to my TFD 5 trip, so I was quite eager to hear about some of their offerings.

After lunch at Drobo, we launched right into discussions of their products. Leading the charge was Mario Blandini, and to describe him as animated is a disservice. Mario is excited and ready to talk. He showed us a picture of him talking about Drobo in character as pitchman Billy Mays, blue shirt and all. That character fits him totally. Drobo also won my first annual “Fewest Slides with a Point” award, as they had a very quick deck of 4-5 slides that included a short video for intro purposes. After that, we killed the video feed for a whiteboard session that delved into some of the “secret sauce” that Drobo uses in their Beyond RAID technology. While I can’t talk about it, and in some cases didn’t quite get the really technical details, it did make me rethink how RAID works in legacy applications.  Drobo has put a lot of thought into their methods of drive utilization, and their whole concept of “beyond RAID” makes some sense to me.  I really think I’d need some more one-on-one time to totally get it down, as storage is not my first language.  As a side note, the whiteboard at Drobo was a pane of glass anchored to a beige wall. This scored cool points for form, but the markers were a little hard to read against the beige and sometimes didn’t make nice, clear marks. Should you be of the bent to go for the glass whiteboard for your home or office, be sure the background is bright to help those of us with terrible eyesight.

Once the cameras came back up, Drobo unveiled a new 12-bay storage appliance designed for business, the B1200i. This coincided with a new focus on this market driven by the tagline “Drobo Means Business”. It showed in the product development as well. The home-use products I saw previously appeared to be geared toward the consumer market, with unified housing and smaller form factors. The new Drobo 12-bay was designed to work with SMB/small enterprise setups, with rack mounting capability and removable FRU parts that don’t require the whole unit to be replaced when something breaks. It even has iSCSI support to allow it to be attached to Windows servers and VMware boxes easily. We were able to demo the unit, showing the capabilities of removing drives from the array and reinserting them out-of-order while the unit chugged right along playing a Quicktime movie trailer. Normally, reinserting a RAID drive in the wrong spot could be considered a Resume Generating Event (RGE), but Drobo has no problems with it at all.  Once the software rebuilt the array, all the pretty lights on the front went back to green and you’d never know anything happened.  Coupled with the fact that all the drives in the unit were of mismatched sizes, I was even more impressed.

We were also treated to a demo of the redesigned Drobo dashboard software. This slick looking piece of software allows one to administer multiple Drobo units as well as view status such capacity, health, and firmware levels. Everything pops up in a nice dashboard view, allowing you to drill down to the individual unit quickly. You can also launch a discovery process to go out and find all the units connected to your local subnet. This would be helpful in a case where you aren’t familiar with the network topology, or where someone might have plugged in a unit and forgotten how to contact it.  From a security standpoint, I was a little worried that it was so easy to discover the units.  Sure, you have to have a username and password to access them, but even knowing they are out there can give you a few avenues of attack.  If there were a way to turn or discovery or simply get more information about which ports are being used by discovery so they can be disabled by us paranoid security types, it would help out.

I was highly impressed with the ease of use of the unit, from both setup and maintenance aspects. This appears to be a unit that I can have at my home, or perhaps even in a small branch office that can just be provisioned without the traditional RAID headaches. In fact, that type of low-tech maintenance is perfect for the person that needs to send a unit to a branch office in New Mexico that may not have a dedicated tech resource. Managing the unit with the dashboard software is simple, and should a problem develop with a drive, you can just ship a new one there and tell them to replace the funny colored light instead of the need to walk them through the ritual of rebuilding RAID arrays. I’m considering pulling the trigger on ordering one of these puppies to store some of my important files at home, like the mountain of pictures my wife seems to have accumulated over the last few years. If you’re considering ordering one too, be sure to use the “DRIHOLLING” coupon code on their website for, well, the best Drobo deal ever (it’s case sensitive BTW).

If you are intersted in learning more, head over to their website at http://www.drobo.com or check them out on Twitter as @drobo.

EDIT

If you are interested in getting a Drobo unit all for yourself, the good folks at Drobo have given me a discount code that’s good for the following discounts:

$50 off on Drobo 4-bay
$100 off on Drobo 4-bay with drives
$100 off on Drobo S & Drobo FS
$150 off on Drobo S and Drobo FS with drives
$150 off on DroboPro & DroboPro FS
$200 off DroboPro & DroboPro FS with drives

Just use the code DRIHOLLING (case matters).  And enjoy your new Drobo!

Tech Field Day Disclaimer

Drobo was a sponsor of Tech Field Day 5, and as such was partly responsible for my airfare and hotel accommodations. In addition, they provided lunch and the use of their facility for our sessions. We were also provided refreshment in the form of cupcakes with enough frosting to spackle my bathroom, which were quite delicious. Drobo did not ask for, nor did they receive any consideration for this article. The opinions expressed here are my own and were not influenced in any way by Drobo.

Tech Field Day – Symantec

Posted on by
2

Our first session at Tech Field Day 5 was a trip the Symantec campus to hear about some interesting backup solutions from both NetBackup and BackupExec.  I’ve been an on-and-off user of BackupExec for many years now, dating back to version 8 running on Netware boxes and it was still a Veritas product.  However, things have changed significantly today when it comes to backing up devices.  Thanks to Symantec, I have a much clearer picture now of what that entails.

We started out the day by hearing from one of Symantec’s NetBackup product specialists, George Winter.  He described how their product allowed them to do some amazing things, especially in the VMware arena.  You can imagine that my ears perked up at this point, as VMware is something that I’m becoming increasingly attached to from both the network and the server end.  I’ve never had the pleasure of using VMware Consolidated Backup, but from the cheers in the room when we were told that NetBackup instead uses the new VMware storage API calls, allowing a NetBackup appliance to get the information it needs to backup VMware guests without the need for the “agent” software program that has typically been needed in the past.  This is nice for me, since I don’t have to go through the trouble of installing agents on each guest as I bring them online.  I can just tell NetBackup to go out and backup the whole server, or a selected subset of guests chosen by groups.  NetBackup is even smart enough to know that if I add a guest to a folder that is currently being backed up that I probably want the new host backed up as well, so it adds the host automatically.   There was a great live demo of the ease of use in setting up the system and selecting backup options.  Demos are always great for engin…I mean Network Rock Stars because we can see things in action and generate questions based on options we can see in the live client and now some canned flash demo that glosses over the knobs and switches.

After the first session, we were graced by the presence of Enrique Salem, the CEO of Symantec.  He took some time out of his busy schedule to talk to us about the vision of Symantec and some of the emerging opportunities he sees for his company in the next year.  He appears to be a driven guy and dedicated to his principles.  So dedicated in fact that he not only gave us his e-mail address, but his cell number as well.  In front of a live video audience, no less!  Men with this kind of dedication earn big points with me because they aren’t afraid to talk to their customers and partners about their products.

A quick break paved the way for the BackupExec team to step up and start talking about the word that would quickly become the underlying theme to Tech Field Day 5 – dedupe.  For those of you network folks that may not completely understand dedupe, it is the process of removing similar data from a backup stream by use of hashing values in order to reduce the amount of data being transmitted, especially over slow WAN links.  Every time I think about it, it reminds of the basic method in which programs like WinRAR and WinZIP use to compress files.  If you really want to know more about data deduplication, you should head over to Curtis Preston’s Backup Central website.  Curtis is now my go-to person when I have a backup question, and he should be yours as well.

We learned more about how Symantec can use dedupe to reduce bandwidth consumption and tame processor utilization, which are ideas that appeal to me greatly.  BackupExec appears to be positioned more toward the SMB/small enterprise end of the market when it comes to backup software.  This is the realm that I play in more than anything else, so this product speaks to me.  There are a lot of options for backing up the VMware hosts that are found in the NetBackup product line, yet scaled down to allow SMB admins to easily use them to quickly backup and restore data.  They even have the capability of performing single file restoration to guest VMs even though the only thing backed up was the VMDK disk files.  Quite interesting if you ask me, as most of the restore requests I receive are for a single Word document, not a whole server.

Overall, I was very happy with what I heard from Symantec.  Their products appear to fully embrace the new landscape of server virtualization and the challenges that it presents to legacy backup solutions.  My own experience with Symantec in the past has varied from use to use, but this presentation went a long way to repairing some of my hard feelings about their solutions, especially in the BackupExec arena.  I’ll definitely be taking another look at them soon.

You can get more information from http://www.symantec.com or follow them on Twitter as @backupexec and @netbackup.

Tech Field Day Disclaimer

Symantec was a sponsor of Tech Field Day 5, and as such was partly responsible for my airfare and hotel accommodations.  In addition, they provided me with a very delicious hot breakfast and some “swag” that included a steel water bottle, t-shirt, notepad and pen set, and a 2GB Symantec-branded USB drive that contained copies of the presentation we were given.  At no time did they ask for or receive any kind of consideration in the writing of this review.

Tips for Presenting at Tech Field Day

Posted on by
11

Tech Field Day delegates are a rough bunch when it comes to presenters.  There is a reputation that precedes us when we walk into a briefing center.  I’m surprised they haven’t started confiscating our empty water bottles when we walk in so as to not provide us ammunition to express displeasure.  In fact, our displeasure with the same old presentation comes from the fact that it’s been seen a thousand times.  We want something that appeals to us as delegates for a technical event.  I wanted to put together some ideas for those who might be considering standing up in front of a Tech Field Day.

1. “Analyst” is a four letter word.  The almost-universal Tech Field Day revulsion to the name “Gartner” is probably the most legendary part of presenting.  If the “G” word gets mentioned, groans and hisses are lobbed toward the front of the room, and in some cases they may be followed by bottles, shoes, and chairs.  Other analyst quotes are also likely to generate some noise amongst the masses.  We get tired of hearing about this kind of fluff every day.  My ire with anaylysts is the fact they charge exorbitant amounts of money to tell you common sense things.  I can see the utility of providing head-to-head information on some products, but to be honest I don’t think Gartner has any better idea about private cloud strategy than I do.  Keep the analyst quotes out of your presentation.  Instead, focus on what your product does and why you love it so much.  Think about this scenario.  Your neighbor walks up and complements you on the new picket fence you’ve installed in your yard.  Are you going to thank them and talk about how it was back-breaking work and discuss the reason you used pressure treated pine over oak?  Or are you going to provide your neighbor with a report from the homeowners association detailing how your fence is high in “appeal” and moderate in “privacy” in the HOA “Super Triangle”?  Make your excitement about your product sound organic and we’ll believe it.  Watch the TFD 5 video from Jaspreet Singh of Druva and you’ll realize he loves his product and believes in it.  He doesn’t need to give you analyst quotes about it.

2.  Pencils have a point.  You should too.  Ever notice that most television shows have a pre-credit sequence today? A little vignette designed to grab your attention and pull you in to make you watch the ensuing 42 minutes of program and 18 minutes of commercials.  Know what they call this little segment in the industry?  The Hook.  It’s designed to draw you in and keep you focused on the show.  Likewise, if you want to keep the attention of a group of tech nerds in a room surrounded with distractions, you need a hook.  In most cases, the hook can be as simple as telling us up front what you’re striving for.  You need to get our attention.  Then you need to keep it.  When I give presentations, I try to do something in the first few minutes during my intro that makes my audience want to listen to me.  To me, the worst thing in the world is a pair of eyes wandering all over the place or focused intently on a computer screen.  At that point, I’ve lost you as a presenter.  TFD delegates like small slide decks for a the same reason they like to have the fat trimmed away on a good steak.  When all the fat is gone, the only thing left is the meat.  On your slide deck, when the fat of pointless exposition is gone, on the meat of the point or purpose is left.  Pick a point or a theme to your whole presentation and try to link back to it for each slide.  I put together a presentation one time for proper networking standards that referenced building a house.  Each slide had house imagery on it and I tried to come back to the that message before moving to the next slide. I reinforced my point in a way that hopefully resonated with my audience.  I’ve already said that should I be invited back for another Field Day, I’m going to make a sign labeled The Point and put it on the desk in front of me.  When I think a presenter is getting lost and is missing the point of the message, I’m going to make them stop and walk over to touch the sign.  That way, they are physically and mentally “Getting to the Point”.

3.  Keep the audience engaged. This kind of dovetails with number 2 above, but you need to find something to keep the attention of your audience.  Most people do this with a demo at Tech Field Day.  But two presenters went above and beyond for me.  Drobo asked a delegate to come up and pull a drive out of one of their demo units while we watched the screens to prove the unit would do what it said it would.  Could the presenter have done this?  Sure.  However, by picking on one of us, he got our attention.  Sure, we heckled Sean and had a good time with it.  We were also focused on what was happening in front of us.  The next day, the Netex “TCP as Beer” example was another way to get everyone in the room engaged.  By passing beer down the table to simulate TCP packets, we not only each had to handle the beer, but keep our buddies engaged as well.  I’m not suggesting that you stoop to the level of making us all do jumping jacks but don’t rely on only your slide deck.  Do keep in mind that many people watch the presentations being streamed over live video, so if you can find something to keep the home audience engaged as well, you’ll have gone a long way to winning the battle for the attention of Tech Field Day.

4.  We have a pulse.  Be sure to check it.  The funny thing about putting a group of technical people into a room during a presentation with communication devices is that we communicate.  We use Twitter to express our opinions about things.  By using appropriate hashtagging, we can let our audience know about things we like or dislike in real time.  During TFD 5, I experimented with an IRC channel for a different picture of things.  I got almost exactly what I expected – a Mystery Science Theater 3000 style of commentary.  For those in the chat room, we were able to express opinions without being restricted to 120-ish characters.  For the delegates in the room, we could express feelings without the need to interrupt the presenters.  Even some our more joking Twitter posts paid off eventually.  Sean Clark remarked that bacon was good.  Jeff Fry was a huge fan of chocolate-covered espresso beans.  When we got to the Thursday presentation by Xangati, we found bacon and chocolate waiting for us.  Even during the presentation, Xangati had a couple of people in the room keeping an eye on Twitter and answering our feedback in real time.  It was kind of surreal to have a second conversation going on in cyberspace even as we were talking in the room, much like the director’s commentary on a DVD.  If you as a presenter really want to get what we’re thinking, you should set up two projectors in the room.  One is for the use of your slide deck and for the delegates to see.  The other is projecting a Twitter feed or TweetDeck search for #TechFieldDay so you can see our feedback as we give it.  That way, you can see what’s working for you as a presenter, or in the worst case scenario, you can see when you’re losing us and need to get back on track.  I’m not saying that kind of presentation would be easy.  But for those with lots of slides, or those going for a more conversational approach, it can give you an idea of what we’re talking about without asking us.

5. If you’re going to skydive without a parachute, you better know how to fly.  At Net Field Day, Force 10 mezmerized the delegates by giving a presentation with just a dry erase marker.  No slides, no projector, no Powerpoint.  Just a whiteboard and a well of technical knowledge a mile deep.  If you’re going to give a presentation with just a whiteboard, you better be ready to keep your audience focused.  You also don’t have much room for error or pacing issues when you have nothing to keep you on track.  I’ve seen slide-less presentations and classes done before.  Narbik Kocharians is almost mythical with his ability to teach a 5-day CCIE prep class with zero Powerpoint.  Wanna know his secret?  He knows his stuff.  He studies everything over and over again.  He can answer questions off the top of his head.  He does his homework.  Think of a presentation just like carving a statue out of marble.  The basic outline is easy to come up with.  But the fine work of making a hand or a face can take days to complete.  The same is true of a presentation.  Throwing together 50 slides about a topic is easy (more or less).  But shaving those down to 25 takes twice as long.  And shaving that down further to 12 slides takes four times as long.  Why?  Because you have to know what you’re talking about the less you rely on visual aids.  You have to have the discipline to focus on the topic at hand and not get dragged off into tangents.  You have to be able to be a lightning rod for the attention of the audience so they don’t drift into solitaire.  I’ll admit, it would be very difficult for me to go totally slide free about something, even my recent IPv6 presentation that I knew backwards and forwards.  Because you don’t have the slides to guide the conversation and direct the focus of your audience, you run the risk of going off script quickly.  And you want your whiteboard presentation to sound more like a live episode of ER and less like Whose Line Is It Anyway.  Don’t just give a slideless presentation just to try and impress the delegates.  Impress us with your knowledge and product first, and your presentation method second.

I hope these tips will be useful not only to presenters for Tech Field Day, but for technical presenters in general.  We aren’t the usual group of marketing drones or unwashed masses.  We do our homework and we bring lots of questions to the table.  We aren’t impressed by slide transitions or rankings.  We want to see the gears and knobs and switches.  We want to see it work or see it break in real time.  Keeping all that in mind will put you ahead of the game when you step on the floor for your turn with the Tech Field Day delegates.  It should also help you avoid any flying water bottles.

Things I Learned From Tech Field Day, Part 2

Posted on by
Reply

Day 2

The inclusion of a self-serve machine for making an on-demand Dirty Chai is instantly successful.

Using beer as an analogy for TCP transmission is nice.  If you don’t mind near 100% packet loss.

The History of Network Protocols isn’t nearly as exciting as you might believe.

Setting up an IRC channel was easier than I thought.  Controlling it is an entirely different matter.

Some people don’t like IPv6.  Some people really like NAT.  These people should be rounded up and forced to eat lunch with me so I can prove them wrong.

Deduping the word “dedupe” from Tech Field Day 5 might have trimmed 4 hours from the total presentation time.

Standards are good.  Unless they are bad.  Then they can still be good, but only if you aren’t bad.

Jay Mellman is really tall.  And coming from me, that’s high praise.

Don’t let your kids succumb to George Lucas Syndrome.

Even 10-year-olds need to go on a date every once in a while.

Even a van full of the Tech Field Day Gold Support Team can’t make some people see reason.

Hotels don’t frown on you bringing your own beer to the pool at 9:00 p.m.

I can be entertaining and funny so long as everyone else is highly intoxicated.

Tech Field Day 5 has come to a close.  I have gained a lot from my experience here, while at the same time realizing I have much more to learn.  Seeing my online friends in reality was as fun as I imagined, and meeting new friends was great as well (yes, even Curtis Preston).  I have a healthy respect for Stephen Foskett and his crew and the wonderful job that they do putting together each Tech Field Day.  The coordination that allows us to seamlessly move from one briefing to another so easily takes a crack team to pull off.

In the coming days, I will have many more words to write about the sponsors of TFD 5.  While they did pay to fly me to California and gave me a place to catch a combat nap between sessions, I am in no way beholden to them.  I plan on giving my fair and honest opinion about the things I’ve seen.  I hope that my readers will find my condensation and appraisals to be useful and maybe even a little insightful.

In the end, I have found this experience to be quite unique.  I look forward to the day when I might be able to attend another TFD and gain even more knowledge that I can share with my friends and colleagues.  Who knows what I might learn next time?  I might even bring a belt.

Things I Learned From Tech Field Day, Part 1

Posted on by
3

Don’t be late in the morning.  Claire will find you and drag you to the van.

Symantec knows how to cook breakfast.  And they even remember the Diet Dr. Pepper.

Streaming video is frowned upon by almost every cell phone provider.

I’m not the only person that sweats during presentations.

CEOs are very forthcoming with their cell phone numbers.

Drobo means business.  And lots of frosting.

Skype should be disabled during presentations.

Storage companies that dedupe their own names are very meta.

Even a deduped backup is enough to make a Mi-Fi crawl.

Bacon and chocolate-covered coffee beans are the best. bribes. evar.

Charles Babbage built the first computer in slightly more time than it took to talk about it (and I have it on video).

The lack of a console port on the Babbage Difference Engine made me cry a little.

Lady Gaga hates bad restores.

And, the Tech Field Day crew knows how to keep my brain working overtime.

There were a lot a great presentations today with tons of good information that I’m still trying to digest.  Great companies, great stories, and a realization that I’m still very green when it comes to some of the rabbit holes of backup and virtualization.  I promise to give each presenter their due in time, with appropriate information and opinions on each.

Tomorrow should be an interesting day with some more networking-focused companies.  If you’d like to see the live stream of our event, head over to the Gestalt IT website for Tech Field Day 5 (http://gestaltit.com/field-day/tfd5/) and watch along with us.  If you have any questions you’d like answered during the presentation, don’t hesitate to shout them out on Twitter with the #TechFieldDay hashtag.  I promise I’ll do my best to keep up and ask away.

Let Me Google (Chrome) That For You

Posted on by
1

Back in December, I applied for a Google Chrome OS notebook.  I figured that if I got one I could use it for testing and checking out Google’s ideas about a web-enabled OS.  I then promptly forgot about it.  Guess what showed up on Monday?

I am now the proud possessor of a Google CR-48 Chrome OS laptop.  It’s a pretty utilitarian thing, which suits me just fine.  The finish is matte all over.  No fancy aluminium or gloss plastic.  Likewise, the connection ports are equally spartan.  An SD card slot, headphone jack, single USB port, and a power connector adorn the right side.  The VGA out occupies the left side.  No Firewire, no Ethernet, no optical drive.  This thing is designed to use wireless to connect to the network and pretty much run on it’s own without many (if any) peripherals.

The hardware is very netbook-ish.  An Atom processor with 2GB of RAM, along with a 16 GB SSD.  The latter allows the machine to wake from sleep almost instantly, much like a certain Air-y demo from the Fruit Company Not-A-Netbook press conference last year.  There’s even an integrated Verizon 3G modem for connectivity outside of Wi-Fi areas.  All in all, the looks combined with the hardware specs would most likely not even get a second glance from a buyer.  It’s what’s under the hood that is so very different.

For those of you out there that are fans of the Google Chrome web browser like I am, you’ll find the interface to be identical on the CR-48.  Here’s the catch, though.  That web browser is the ENTIRE OS.  No start menu.  No dock.  The whole OS concept revolves around the browser, and by extension, the web itself.  The user account for the system is a Google account.  It pulls your information from GMail, Google Docs, and even your Chrome favorites if you’ve set them to sync.  All of my Google information was pulled down the first time I logged into the laptop.  The 16GB drive is enough to handle a few downloads, but most of your file manipulation will occur in the “cloud”.  Google Docs for an office suite, for instance.  Any other apps you might need can be downloaded from the Google Apps Web Store.  Twitter clients, note taking apps, remote access apps, and so on.  They can all be “installed” into the browser OS for access to the things you use the most.  The more I used the system, though, the more I found myself thinking in terms of web-based content and less in terms of document storage and programs like I think of on my work laptop.   For a child or a spouse the spend 85-95% of their time doing online-related content creation and consumption (like Facebook or webmail), this would be the perfect laptop.

That’s not to say that the CR-48 is a perfect laptop.  There are some issues, even taking into account this early beta type OS/Platform.  Bluetooth doesn’t work.  Neither does connecting to a Wi-Fi network that uses certificate authentication.  The trackpad is a little tough to get used to.  I’ve heard some people compare it to the type found on the latest Macbook.  It takes some getting used to, and the gesture support isn’t quite intuitive for me just yet.  The other bug I ran into was with the Verizon 3G modem.  There’s a quick link for activating the Verizon account that Google has graciously provided.  However, I hit a geographical snag.  It appears that the Verizon towers in my area code (405) used to belong to Alltel Communications before they were purchased by Verizon last year.  So, when the activation signal was sent, it wouldn’t register correctly.  I was only able to activate it correctly when I went out of state.  To Google’s credit, they Chrome Netbook Ninja (support person) I talked to diagnosed the problem inside of 5 minutes after the Verizon pre-paid tech fought with it for 30 minutes.  Kudos to Google for having competent support people.  And even more kudos for allowing them to call themselves ninjas.

I plan on using the Chrome netbook to take notes during Tech Field Day this week to give it a good run and see how well it performs.  I may even let my kids start using it to see how well it holds up to the gentle caresses of a 5 year old and a 2 year old.  Stay tuned for further reports.

When Is A Trunk Not A Trunk?

Posted on by
28

When I was an impressionable youth back in my college years, I decided it might be a good idea to take Japanese as a foreign language.  I spent three semesters learning vocabulary and kanji and eventually managed to forget pretty much everything I learned.  One lesson that did stick with me, however, occurred in my first semester.  Our professor was explaining to us gaijins (Westerners) that we needed to be very careful about how we pronounced certain words.  Since words in Japanese are limited by a very small number of vowel sounds, there are many cases were words use the same sounds but have totally different meanings.  Such is the case with shujin. When pronounced as I have written it, it is the word for “husband”.  However, if you hold the “u” sound a little too long, as in shuujin, you instead have referred to that person as a “prisoner”.  As my professor explained, “Well, perhaps those two words really aren’t so different.”  In this case, a small difference in pronunciation can have a profound difference in meaning.

Another place where I see an issue similar to this is when someone starts asking questions about terminology differences between HP Networking (nee Procurve) and Cisco terminology on switches.  Often, these questions boil down to two major terminology differences based around one word: trunk.  It’s pronounced the same in both vendors world, but just like in Japanese, it can have a very different meaning depending on how it’s used.  Allow me to illustrate:

In Ciscoland, when I use the term trunk, I am referring to a port that carries multiple VLANs.  Trunk ports carry information about each of the VLANs on the switch in either Cisco’s ISL proprietary format or in the 802.1q vendor-neutral format.  Newer switches, like the 2960, have no support for ISL and will only form trunks using 802.1q, so I’ll use 802.1q for my examples.  Just keep in mind that if the switch doesn’t support ISL, you don’t need to configure the trunk encapsulation.  When these ports are designated as “trunks”, the frames are tagged with a special 802.1q header that indicates which VLAN they are a part of.  The only VLAN that is not tagged with an 802.1q header (by default) is the native VLAN.  On Cisco equipment, the default native VLAN for an 802.1q trunk is VLAN 1.  The behavior of Cisco IOS is to transmit information about all VLANs present on the switch over the trunk.  You can narrow this behavior through use of the switchport trunk allowed vlan command.  A sample Cisco trunk config might look like this:

Switch(config)#interface gig 0/1
Switch(config-int)#switchport trunk encapsulation dot1q
Switch(config-int)#switchport trunk allowed vlan 1,10,99
Switch(config-int)#switchport mode trunk

This configuration is sufficient to setup an 802.1q trunk and only allow VLANs 1, 10, and 99 to pass traffic on it.

In HPvania, the terminology used for a port that carries multiple VLANs is a tagged port.  On an HP switch, the individual ports are rarely configured directly.  Instead, the VLAN itself is configured and the ports are added to the VLAN configuration.  In order to setup an access port, it is configured as an untagged member of the VLAN it needs to belong to.  Since HP does not support ISL trunking, the terminology is straight from 802.1q.  The untagged ports do not carry 802.1q headers that specify they VLAN information.  This would be known as an “access port” on a Cisco switch.  In order to create a port that carries information for multiple VLANs, we must “tag” those VLANs on that port.   This modifies the packets sent on that port to carry VLAN tags for the VLANs indicated.  A sample configuration for an HP switch connected to the above Cisco switch might look like this:

Switch(config)#vlan 1
Switch(config-vlan)#untagged 1
Switch(config-vlan)#untagged 48
Switch(config-vlan)#vlan 10
Switch(config-vlan)#tagged 48
Switch(config-vlan)#vlan 99
Switch(config-vlan)#tagged 48

Notice that the configuration is done under the VLAN and references the port number on the switch.  Access ports are untagged members of a particular VLAN, and the native VLAN of an 802.1q trunk is also an untagged member.  Even though 802.1q has a native VLAN that doesn’t carry a tag, on an HP switch this VLAN needs to be explicitly set.  The other VLANs must be tagged to the uplink port in order for their information to be carried between switches.  This lends itself to being an additive solution, where VLANs are only present on a trunk if they have been specifically configured.  There is no need to prune VLANs or exclude them from the trunk if they aren’t needed.  They just aren’t configured in the first place.

Which method is better?  This tends to devolve into an OSPF vs. IS-IS type of argument.  If you are more comfortable with one you tend to prefer it.  I tend to use the Cisco terminology in my day-to-day operations, and I have a slight preference for not needing to remember to add each individual VLAN to an uplink port.  However, from a security perspective, I do like the HP idea of only adding VLANs that are needed.  In fact, this same concept of VLAN creation is present in the Force10 OS.  If you’d like to see more of it in action, you should check out Stretch’s excellent intro to Force10 over on Packetlife.net.

So, if HP refers to an uplink carrying multiple VLANs are a tagged port, then does HP have a “trunk”?  In fact they do.  In HPvania, a trunk is a logical construct that aggregates multiple ports into one logical link.  For those of you that might be out there scratching your heads about this one, this means that when you “trunk” a group of ports on an HP switch, you are creating one LACP link from up to four individual ports.  This kind of configuration should look like this:

Switch(config)#trunk 19-24
Switch(config)#trk1
Switch(config-trk)#lacp
Switch(config-trk)#vlan 1
Swtich(config-vlan)#untagged trk1
Swtich(config-vlan)#vlan 10
Swtich(config-vlan)#tagged trk1
Swtich(config-vlan)#vlan 99
Swtich(config-vlan)#tagged trk1

Those of you that are fans of irony will appreciate that the above config sets up this LACP port aggregation to pass multiple VLANs to another switch.  In other words, we are configuring a Cisco “trunk” on top of an HP “trunk”.

In Ciscoland, the idea of aggregating multiple ports into a grouping is referred to by many names, usually “port channeling” or “Etherchanneling”.  The latter is the term that usually describes the Cisco-proprietary Port Aggregation Protocol (PAgP) links that are created by default.  However, this term has more or less become genericized and is used to refer to any group of aggregated ports on a Cisco switch.  Cisco does support LACP on aggregated ports, so let’s see how we’d configure this switch to use LACP and send tagged VLAN traffic back to the HP switch:

Switch(config)#interface range gi 0/19-24
Switch(config-int-range)#switchport trunk encapsulation dot1q
Switch(config-int-range)#switchport trunk allowed vlan 1,10,99
Switch(config-int-range)#switchport mode trunk
Switch(config-int-range)#channel-group 1 mode active
Switch(config-int-range)#channel-protocol lacp

This will set the aggregated ports to use LACP and pass VLANs across the link with 802.1q tags.  Note that you must set the channel-group command to “active” in order to use LACP on the link.  If you set it to “auto” or “desirable”, it will use PagP by default.  If you set the mode to “on”, it will not use LACP or PAgP at all.

There you have it.  The terminology is different, but as long as you know what you are trying to accomplish, you can usually figure out what you need to configure in order to make it all work correctly.  Hopefully you’ll never find yourself married to any particular configuration, much less become a prisoner of it.  In the end, just remember that a trunk is still just a trunk.  The meaning is entirely up to you.