Enabling Multi-tenancy within Enterprise IT Operations

by: Shehzad Merchant, Chief Strategy Officer at GigamonShehzad Merchant

Multi-tenancy is a well understood term in cloud and carrier environments where multiple customers serve as tenants over a common infrastructure. However, the notion of multi-tenancy, the associated SLAs for each tenant, and the ability to virtualize the underlying infrastructure to isolate individual tenants, is quickly making its way into enterprise IT operations. Today, enterprise IT organizations have multiple departments such as security, networking, applications, among others. Each department is increasingly being held to stringent requirements for ensuring network and application availability, responsiveness, and a good user experience. This is leading to an increasing reliance on various classes of tools that provide the ability to monitor and manage the applications, network, security, as well as user experience.  Many of these tools leverage Gigamon’s Visibility Fabric™ for optimal delivery of traffic from across physical and virtual networks to these tools. As departments are increasingly held to their own SLAs and KPIs, they need to be able to autonomously carve out traffic delivery to the departmental tools, as well as independently configure, manage, and adapt traffic flows to the departmental tools without impacting other departmental traffic flows. And they need to be able to do all of this over a common underlying Visibility Fabric, which leads to a model where the Visibility Fabric needs to support a true multi-tenant environment.

With the GigaVUE H Series 3.1 software release, Gigamon introduces several enhancements to the Visibility Fabric that enable multi-tenancy and enable IT departments to optimize their workflows, reduce workflow provisioning times and provide for both privacy as well as collaboration among departments when it comes to their monitoring infrastructure.

There are three key aspects to these new capabilities.

  1. Enabling departments to carve out their own slice of the Visibility Fabric using an intuitive Graphical User Interface (GUI) that supports the workflow required for multi-tenancy. Empowering multiple tenants to apportion the Visibility Fabric each with their own access rights, sharing privileges and their traffic flows, through a drag and drop GUI-based model is a key step towards simplifying the provisioning model in a multi-tenant environment. Moving away from a CLI based approach to a GUI based approach is a key step towards improving workflows across departmental silos.
  2. Advancing Gigamon’s patented Flow Mapping® technology within the Visibility Fabric Nodes to support multi-tenancy whereby each tenant can carve out their own Flow Maps, ports, and actions, without impacting the traffic flows associated with other tenants. This is a significant architectural advancement that builds on Gigamon’s existing Flow Mapping technology to provision resources within the underlying visibility nodes based on the department’s (or tenant’s) requirements.
  3. Providing role based access control (RBAC) so that departmental users can work both collaboratively as well as privately over the common underlying Visibility Fabric.

These capabilities represent a significant advancement in how IT operations can take advantage of the Visibility Fabric to rapidly deploy new tools, enable real time or near real time tuning of the Visibility Fabric and better meet their individual SLAs and KPIs. Taken together, these key capabilities empower IT organizations to provide Visibility as a Service to their various departments.

For more information, please see the Visibility as a Service Solutions Overview.

Visibility in Motion at Cisco Live Orlando

by: Huy Nguyen, Senior Director of Product
Management at Gigamon

Huy_Nguyen_headshot

Now that Cisco Live Orlando has come and gone and we’re gearing up for VMworld, we’re seeing even more attention being paid to virtualization given the interest in software defined networks (SDN) and data centers (SDDC). So, virtualization remains hot and with around 60 percent of all applications running in virtualized environments according to some studies, we shouldn’t be surprised that there are even summer camps being offered around the subject (I’m not kidding). I feel like 2013 is the Summer of Virtualization!
That being said, it makes sense to let you know how Gigamon is continuing to address the visibility challenges being experienced by organizations utilizing virtualized environments.  On the first day of the Cisco Live World of Solutions expo we announced GigaVUE-VM 2.0. If you’re not familiar with our GigaVUE-VM, it is basically a virtual instance of one of our Visibility Fabric nodes. Because traffic between virtual machines may be switched locally, it will never traverse the physical network, rendering existing monitoring and analysis tools blind to this virtual traffic.  The GigaVUE-VM fabric node provides that packet-level visibility into the virtualized server world.
One of the dynamic things about the 2.0 update in addition to exposing inter-VM traffic flowing within a physical host and across physical hosts is that GigaVUE-VM now supports Cisco’s Nexus 1000V virtual switch as well as VMware’s vSphere Distributed Switch (VDS). GigaVUE-VM works with these virtual switches to abstract copies of the packets before intelligently filtering and forwarding the packets to the management, security, and monitoring tools that require packet-level visibility, such as application and network performance monitoring tools and intrusion detection systems.
Perhaps even more exciting is that GigaVUE-VM 2.0 has the ability to automatically reconfigure Gigamon’s Visibility FabricTM architecture and migrate monitoring policies to maintain continuous visibility when a virtual machine vMotion event occurs. Essentially, GigaVUE-VM preserves visibility into the traffic flowing between VMs even after that VM moves from one physical host to another for what we call “visibility in motion.”
What’s so significant about this function is that without the ability to automatically migrate the monitoring policies, visibility that had been configured would be lost once the vMotion occurs and would require manual reconciliation which very well could be arduous given the agile virtual infrastructures of today.
For even more information, check out our white paper,
Visibility into the Cloud and Virtualized Data Center”.
CiscoLiveOrlando_GIGAMON6 CiscoLiveOrlando-GIGAMON5 CiscoLiveOrlando-GIGAMON4 CiscoLiveOrlando-GIGAMON1 CiscoLiveOrlando_GIGAMON3 CiscoLiveOrlando_GIGAMON2