Category: News

IPv6 support in vSphere

With all the talk lately of IPv4 addresses being exhausted on the internet I thought I would post a snippet from my book Maximum vSphere that covers IPv6 support in vSphere. This is just a small part of a whole chapter on networking so for more good networking information be sure an check out my book, currently only $28.22 on Amazon.

blkfade

Another new feature in vSphere is support for IP version 6 (IPv6) which is the successor to the traditional IPv4 IP addresses that are commonly used today. IPv6 was created to deal with the exhaustion of the number of IP addresses that IPv4 supported. IPv4 uses 32-bit IP addresses which yields a maximum number of around 4 billion unique IP addresses. IPv6 on the other hand uses 128-bit IP addresses which results in an insanely high number of unique IP addresses (340 undecillion or 3.4 x 10 to the power of 38). Besides more IP addresses IPv6 also has many enhanced features over IPv4 like stateless host auto-configuration to obtain IP addresses, mandatory IPSEC for security and mandatory multi-cast. IPv4 addresses are all numeric and an IPv4 address is 4 bytes, also referred to as octets (4 bytes of 8 bits = 32-bits) such as 192.168.1.125 or in binary it would be 11000000 10101000 00000001 11111101. Each byte contains 8 bits which results in possible values of 0 through 255 or a total of 4,294,967,296 possible IP addresses.

IPv6 addresses are 16 bytes (128 bits) and represented in hexadecimal and a typical IPv6 address is in the following form: hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh. IPv6 addresses have both a full and shorthand notation, the full notation displays the whole address of 8 sections, i.e. E3D7:0000:0000:0000:51F4:9BC8:C0A8:7625; the shorthand notation drops the extra zeros which are common in IPv6 addresses, i.e. E3D7::51F4:9BC8:C0A8:7625. The double colon denotes the zero sections that were dropped. Support for IPv6 was enabled in vSphere for the networking in the VMkernel, Service Console and vCenter Server. Support for using IPv6 for network storage protocols is currently considered experimental and not recommended for production use. Mixed environments of IPv4 and IPv6 are also supported.

To enable IPv6 on a host you simply select the host and choose the Configuration tab and then Networking. If you click the Properties link (not the vSwitch Properties) there is a checkmark to enable IPv6 for that host. Once enabled you must restart the host for the changes to take effect. Once restarted you will see in the VMkernel, Service Console (ESX) or Management Network (ESXi) properties of the vSwitch both an IPv4 and IPv6 address as shown below.

ipv6

You can edit the IPv6 settings and specify to obtain IPv6 addresses automatically through DHCP or through router advertisements as well as set a static address. While IPv6 is better than IPv4 it has not seen widespread adoption and in order to use it your network environment needs to support it, this includes DNS/DHCP servers, switches and routers. In many cases IPv6 is tunneled through IPv4 networks so both can co-exist together.

blkfade1

One additional note to add about IPv6 support in vSphere, as of vSphere 4.1, IPv6 is supported for:

  • Guest virtual machines
  • ESX/ESXi management
  • vSphere client
  • vCenter Server
  • vMotion
  • IP storage (iSCSI, NFS)-experimental

NOTE: IPv6 is not supported for vSphere vCLI, VMware HA and VMware FT logging.

Update from VMware on vShield support:

We have support for IPv6 on the roadmap for vShield Edge to support IPv6 on external interface. For vShield App, Zones and Endpoint, we will be agnostic to v4 vs. v6 being as layer 2. Beyond that, vShield manager will support all UI for the v6 configs. Regarding timeframe, we may phase in the support for this over a few releases and exact details are in works.

Share This:

Tech Field Day #5 wrap-up – Day 1 – Drobo

drobo_logo1After a visit to Symantec HQ in the morning it was off to Drobo’s HQ. Drobo stands for Data Robotics but they have permanently moved to the Drobo name instead. There products consist of of low-end storage devices for the consumer and SMB markets. The Drobo line ranges from small 4-bay storage units up to their soon to be released 12-bay unit. Much of their presentation was focused on their new B1200i 12-bay iSCSI SAN storage and their newly designed management UI. I’ve always thought Drobo’s were attractive and well built units but I felt that they were overpriced compared to the many other similar units on the market from vendors like NetApp, Synology, QNAP and Iomega.

I’ve always felt like Drobo has had a bit of an identity crisis, they target a specific market with each of their storage devices instead of going after a much broader market. Most of their business class devices only support the iSCSI protocol which limits their use cases. Their FS line doesn’t natively support iSCSI or NFS but if you install one of their Drobo Apps on it then you can use NFS. Finally their smaller consumer units only support direct attach via FireWire or USB. Each line is marketed at a different use case and has different connectivity. This limits each device to only being used for a specific purpose. The problem with that is all of their competitors support all protocols and connectivity options across their entire line of devices. If you take Synology or NetGear for example, from their small 1 bay units all the way up to their expandable 5-bay units they support all the same features across most of their product line. This means any of their devices can support iSCSI, NFS, CIFS, FTP, AFP and much more. As a result they can be used for a multitude of things simultaneously, the Drobo units on the other hand are very limited in what they can do. I can’t see that it would be all that difficult to provide support for both iSCSI & NFS on all their devices so customers can choose what they want to use. Having consistent software and protocol support across all their devices would also make development easier.

Drobo unveiled there new 12-bay unit (B1200i) to us which fits into their “Drobo means business” theme, it looks like a larger version of their 8-bay units with a few key differences.

  • Dual hot-swappable power supplies (other Drobos only have single fixed power supplies)
  • Support for SATA, SAS and SSD drives (other Drobos only support SATA)
  • 3 Gigabit Ethernet ports (other Drobos only have 2)
  • 1 Gigabit Ethernet port dedicated to device management (other Drobos don’t have this)

lg_b1200i_open_800x5001lg_b1200i_rear_800x500

I asked some questions such as if they supported 6.0 GB/s SAS drives and they said they did, which is nice, but some other answers I didn’t like so much. The first is that while they have 3 Ethernet ports, they have no ability to team them together for load balancing or failover. Each port is independent and must be assigned its own IP address, they seemed to think this was OK because users and apps could use different IP addresses to access the Drobo but I thought this was too complicated and unrealistic. The B1200i only has a single controller card but has additional empty ports for future expansion. I asked if they planned on supporting a second controller card and they said they might at some point in the future. That seemed to me like they were releasing a product that wasn’t completely done yet.

The next is the price, they had said the B1200i was going to be released at just under $10,000 half-populated with 12TB of storage. That just seems way to high for a storage unit that is missing many enterprise features and is in the same price range as the NetApp FAS2020, EMC VNXe & HP MSA, all of which are much more robust, enterprise class units. They plan on also offering a lower cost model with no/smaller drives but the price is still way too high. They need to be down around the price range of the Iomega ix12-300r which starts at $4999 for a 4TB model.

They also showed off their new Drobo Dashboard which was visually very nice looking but I felt was lacking in many areas. They were asked several questions on if it supported different features like SNMP and they kept answering that additional features would be coming later. I felt that if they were going to put all that effort into developing a new interface they should get it right before they release it. It seemed like much of the development effort went into improving the visual elements of the interface and not the functional elements. The Dashboard lets you manage multiple Drobo units that are on the network in a centralized view but seemed lacking enterprise features like AD or LDAP authentication.

dashboard_lg_main_800x5751dashboard_lg_mgmt_800x5751dashboard_lg_status_800x575

The Drobos use a proprietary RAID called BeyondRAID which is the only RAID that you can use as they do not support any traditional RAID levels. You are limited to a single RAID group even on the 12-drive model. Think of BeyondRAID as kind of a dynamic, intelligent RAID level that has the ability to use drives of different sizes and types in a RAID group. The size of the RAID group can be increased simply by removing a drive and inserting a larger drive and letting the RAID rebuild itself. Being able to increase drive sizes without data loss is a nice feature but I’m not a big fan of mixing different size/type drives in a single RAID group. There is support for standby hot spares and also dual disk redundancy, also drives can be re-inserted in any order without data loss. Thin provisioning is supported but only for traditional OS volumes, it is not supported for VMware VMFS volumes.

I’d really like to see Drobo succeed but I feel to do so they need to do a few things to better compete with the many other low-end storage devices on the market.

  • More competitive pricing, across your whole line, its OK to charge more if you’re offering more then your competitors but in most cases they are not.
  • Feature and protocol parity across their entire product line, offer iSCSI, NFS and other features on all models from the 4-bay Drobo up to the 12-bay B1200i.
  • More features on both consumer and business models, take your Drobo Apps that are only available on the FS models and integrate them in all your models. Features like FTP & CIFS support, jumbo frames, backups, rsync, AFP, SSH and SNMP should be on all your models.
  • Simpler product line, right now there is a Drobo, Drobo S, Drobo FS, DroboPro, DroboElite, DroboPro FS, Drobo B1200i, B800i and B800 FS. This is kind of confusing as all the models have a specific use case, consolidate into 4-5 models by bringing features together, the i (iSCSI) & FS (NFS) should be one unit.
  • Better centralized management interface, it looks great but add more features and functionality to it.

One of the best things Drobo has going for it is that they seem to have very well built and well designed storage devices. The devices are high quality and it looks like a lot of thought went into their design. They are attractive looking units with nice LED indicators that give visual indications of how the device is functioning. If Drobo could pack some more features into the devices they would better compete with everyone else. I’ve really always wanted to like these devices and I’ve been tempted to buy one for my home lab but the high cost and lack of features turned me off. If Drobo can address some of these issues I could definitely see myself being a Drobo owner.

Share This:

Tech Field Day #5 wrap-up – Day 1 – Symantec

symantec2

Symantec totally brought their A game to the event, the presenters were mostly technical which was good and included their Chief Architect for the NetBackup product family. They also served a very nice breakfast which included bacon! They have a huge campus in Mountain View, CA which is their world headquarters and where we visited. A big surprise to us all was that their CEO, Enrique Salem, flew into town just to talk to us for a bit. He seemed like a very high energy, approachable, down to earth guy who gave us some vision for Symantec and let us ask him questions. At one point he popped a Milky Way into his mouth to get some nourishment and he also gave out his cell phone number to us in case we wanted to contact him later.

Symantec primarily covered their backup products which includes NetBackup and Backup Exec, there was a heavy emphasis on their virtualization integration which was appealing to me. I found that they are now integrated with vSphere extremely well and are fully leveraging the vStorage APIs for data protection. NetBackup and Backup Exec are now jointly developed so much of the same code is used in both so they no longer have to do double the work to develop the same features in both versions. I asked if there was any future plans to eventually merge the two into one product and they responded that there was not and that both products while sharing many of the same features would remain independent.

What impressed me the most about their virtualization integration was the fact that they could perform restores of individual files from image level backups to tape. Almost all vendors can do individual file restores from disk targets but Symantec found a way to do it directly from tape by only restoring the blocks for that file and not the whole VM to do it. Symantec inserts a filter in their image level backups that reads all the data being backed up so it can index and know exactly where files reside on the target media. Typically with file restores the virtual disk must be mounted from the target repository so the files can be selected and restored, NetBackup doesn’t require this.

What was also impressive is the number of enterprise backup features that have found there way into Backup Exec as well which makes it a great affordable and robust solution for SMBs. Their emphasis with Backup Exec compared to NetBackup is simplification, Symantec believes that SMBs with smaller IT staffs do not want a highly configurable solution. As a result they have developed Backup Exec with many of the same features as NetBackup but have made the administration and configuration options much simpler. I think one of the strengths of the Netbackup/Backup Exec line is that they support both physical and virtual machine backups which is one of the weaknesses for the virtualization only platforms from vendors like Veeam and Quest.

Most environments are not 100% virtual so using Backup Exec or NetBackup means you only need one backup solution. However, Symantec’s development cycle seems slow and smaller vendors like Veeam are quicker to support new features related to backups, such as the vStorage APIs for Data Protection and the Changed Block Tracking feature. The strength of Veeam is that they are lean and mean and can move at a very fast pace to support changes and new technologies in the backup space, they also think outside the box and come up with innovative features. I asked Symantec if they had planned on introducing features similar to Veeam’s SureBackup and they said no, they didn’t feel that their was a high demand for it. But if you’re looking for a single backup solution that supports both physical servers and virtual machines you can’t go wrong with NetBackup or Backup Exec that has some great features and is very well integrated with virtualization.

Overall I came away pretty impressed with their products, the new 7.1 version of NetBackup is supposed to be released later this month and has some additional new features in it. While we had the attention of Symantec’s CEO I did ask him a question, I wanted to know where they were at with producing a version of their anti-virus software that would be compatible with vShield Endpoint. Currently Trend Micro is the only vendor shipping a product for it, he stated that did not plan on releasing something anytime soon and it would be at least a year before they released a new product that would support vShield. The reason for the delay is that they are waiting for the next generation of vShield to be released that has more features and better integration to more effectively secure the platform. They plan on releasing an Endpoint compatible product called Single Instance Security in the first half of 2012.

The next post will cover our meeting with Drobo & Druva. Here are the videos that were shot during the Symantec presentation:

Share This:

Tech Field Day #5 wrap-up – Day 0 – Arrival & Dinner

Well Tech Field Day #5 which was held in San Jose, CA is over and it was a great 2 intensive and long days spending time with various vendors. This will be a series of posts on my thoughts and experiences at TFD5, overall I had a great experience there and would highly recommend it to any bloggers out there that get invited. The event is run by Stephen Foskett and his Gestalt IT company and is designed to bring together highly regarded bloggers and vendors from various IT industries. Delegates are selected from a list of independent bloggers that prior TFD delegates rank in several categories using a point scale, those at the top of the list get selected, apparently I was the highest ranking delegate that had never attended a TFD event, I had prior invitations but had turned them down due to conflicts. There were 12 delegates for TFD with a variety of backgrounds that included virtualization, storage, backups and networking.

BloggerWebsiteTwitterLocationSpeciality
Sean Clarkhttp://seanclark.us/@vSeanClarkIowaVirtualization
Jeff FryFryGuy’s Blog@FryGuy_PAPennsylvaniaNetworking
Robin HarrisStorage Mojo@StorageMojoArizonaStorage
Bill HillVirtual Bill@Virtual_BillOregonVirtualization
Tom HollingsworthThe Networking Nerd@NetworkingNerdOklahomaNetworking
Matthew NorwoodNetwork Therapy@MatthewNorwoodGeorgiaNetworking
Devang PanchigarStorage Nerve@StorageNerveNew JerseyStorage
W. Curtis PrestonBackup Central@WCPrestonCaliforniaBackup
Maish Saidel-KeesingTechnodrone@MaishSKIsraelVirtualization
Eric SiebertvSphere-land@EricSiebertColoradoVirtualization
Greg StuartvDestination@vDestinationArizonaVirtualization
Chris Wells@vSamurai@wygtyaJapanVirtualization

I arrived late Wednesday afternoon and after a meetup in the hotel lounge we were off to a group dinner at a nearby restaurant, Zeytoun which featured middle eastern food. Dinner was great, we had the whole restaurant to ourselves and featured great food, gift exchanges and a belly-dancer which was the highlight of the evening. The gifts were small tokens from each bloggers local culture and consisted of micro brews, Japanese whiskey, rocks from Colorado, pastries from Israel and much more. It was a great time and gave a chance for all of us bloggers from all over the globe to get to know each other better. I had previously met about half the bloggers at other events and knew a few of the others but there were some that were completely new to me.

tfd-1

After dinner a bunch of us hung out in the hotel lounge before heading off to bed to get some sleep before our 7:30am start the following day which included a visit to Symantec’s HQ, Drobo’s HQ and the Computer History Museum for a presentation from Xangati followed by a reception. Stay tuned for the next post which will cover our trip to Symantec.
Share This:

On the way to Tech Field Day

Well after turning down several previous TFD invitations because of scheduling conflicts I”m finally on my way to one. Tech Field Day is a recurring event that is the brainchild of Stephen Foskett from Gestalt IT and is an intensive deep dive with vendors on their products and technology. Tech Field Day #5 which runs from 2/10 – 2/11 is being held in San Jose and features a great cast of sponsors and delegates. Of the vendors that will be there I’m pretty familiar with HP, Symantec, Drobo & Xangati and don’t know too much about NetEx and InfoBlox. Supposedly a new company is launching at the event as well which I’ll be interested in finding more about.

These types of events are enjoyable because they are much more techie then the usual marketing pitches you get at typical seminars. They are also fun because you get to be around other bloggers and industry people who you typically only interact with online. I look forward to meeting old friends and making new ones as well, I also get to see my pal Curtis Preston again after our last night on the town when he was in Denver.

There is full coverage on Gestalt IT’s Tech Field Day #5 link page and I’ll be posting here my thoughts and experiences as well.

Share This:

ESX vs. ESXi: Convincing your boss to move to ESXi

Since VMware first introduced its ESXi hypervisor at the end of 2007, the ESX-vs.-ESXi debate has escalated. But now that VMware plans to phase out ESX and switch to ESXi, migrating to ESXi has become increasingly important.

But the reality is that many VMware shops still run the ESX hypervisor. ESXi has a radically different management approach, and many ESX shops have avoided ESXi because it lacked the power of ESX’s service console. Additionally, several ESX features were not available in early ESXi iterations.

But ESXi has steadily matured, and now the consensus is that the stripped-down hypervisor is on par with ESX’s features and management. But many IT shops still run ESX because they are used to it, and the transition to ESXi can be time-consuming and difficult.

Now that ESXi will replace ESX, you may be ready to switch hypervisors. But you might have to convince your boss and coworkers to get on board. To end the ESX vs. ESXi debate for good, this sample letter should help you make a convincing argument for migrating to ESXi.

Read the full article at searchvmware.com…

Share This:

NetGear ReadyNAS review: A look at the ReadyNAS 2100

Having shared storage is a must for most IT environments, whether they are large or small. Shared storage enables collaboration, document sharing and is a key requirement for many advanced features in virtualization. An attractive alternative to complex and expensive storage area networks (SANs) for small- and medium-sized businesses (SMBs) are network-attached storage (NAS) units.

NAS units are dedicated standalone units that attach to your network and contain both disk controllers and hard disks all in one unit that can be accessed by any device on the network. They can range from small one-drive units to multi-drive units that support multiple RAID levels to protect against disk failures. Most units support a wide variety of protocols that can be used to connect to the NAS unit, such as Windows CIFS/SMB, iSCSI, NFS, Apple’s AFP, FTP and more.

NetGear ReadyNAS storage devices

The NetGear ReadyNAS family of devices range from their small two-drive ReadyNAS Pro desktop units up to the larger 12-drive ReadyNAS 4200 rack mount units. Most of the ReadyNAS models have the same feature and protocol support; the main differences between them are the hardware specifications outlined below:

Read the full article at searchsmbstorage.com…

Share This:

10 VM administration tips and virtualization best practices

I originally did these 10 tips for searchvmware.com but they ended up with 5 of the general ones published on searchservervirtualization.com and 5 of the VMware specific ones published on searchvmware.com.

5 tips at searchvmware.com

VMware administration and management can be complicated and frustrating. But it’s much easier when you know the optimal way to handle virtual machines (VMs).

VMware administration and management requires not only technical expertise but also problem-solving skills. And if you don’t properly manage a VMware environment, it can quickly come back to bite you. These VMware administration and management tips will help you better manage your VMs and avoid common mistakes.

VMware administration tip No. 1: Thin is in
You should strive to properly size virtual disks, but sometimes disk size grows, such as with a database server that accumulates additional data on a regular basis.

In these situations, administrators often allocate more disk space to a VM than is initially needed. Thin provisioning helps reduce this wasted space.

Read the full article at searchvmware.com…

5 tips at searchservervirtualization.com

Virtual machines (VMs) have specific management requirements that don’t apply to physical servers. For effective VM administration, you need to know how to properly manage, maintain and troubleshoot your VMs.

There are several challenges that you should be aware of to keep your VMs fit and healthy. In this article, I share five virtualization best practices to help you efficiently and effectively manage VMs. For VMware-specific advice, check out this companion article on five ways to improve VMware administration and management.

VM administration tip No. 1: Avoid overallocation
You virtualize physical servers to make use of wasted resources. But many administrators allocate the same amount of resources to virtual machines as they did to physical servers.

Read the full article at searchservervirtualization.com…

Share This: