Guest

Cisco Virtual Security Gateway

Cisco Virtual Security Gateway for Nexus 1000V Series Switch Release Notes, Release 4.2(1)VSG1(3.1)

  • Viewing Options

  • PDF (214.2 KB)
  • Feedback
Cisco Virtual Security Gateway for Cisco Nexus 1000V Series Switch Release Notes, Release 4.2(1)VSG1(3.1)

Table Of Contents

Cisco Virtual Security Gateway for Cisco Nexus 1000V Series Switch Release Notes, Release 4.2(1)VSG1(3.1)

Contents

Introduction

Software Compatibility

Features

Product Architecture

Trusted Multi-Tenant Access

Dynamic (Virtualization-Aware) Operation

Setting Up Cisco VSG and VLAN Usages

New and Changed Information

Cisco VSG for Nexus 1000V Series Switch, Release 4.2(1)VSG1(3.1a)

New Software Features

Limitations and Restrictions

Caveats

Open Caveats—Cisco VSG Release 4.2(1)VSG1(3.1)

Open Caveats—Cisco VSG Release 4.2(1)VSG1(3.1a)

Resolved Caveats—Cisco VSG Release 4.2(1)VSG1(3.1)

Resolved Caveats—Cisco VSG Release 4.2(1)VSG1(3.1a)

Related Documentation

Cisco Virtual Security Gateway Documentation

Cisco Virtual Network Management Center Documentation

Cisco Nexus 1000V Series Switch Documentation

Obtaining Documentation and Submitting a Service Request


Cisco Virtual Security Gateway for Cisco Nexus 1000V Series Switch Release Notes, Release 4.2(1)VSG1(3.1)


Updated: December 17, 2012
OL-25783-01

This document describes the features, limitations, and caveats for the Cisco Virtual Security Gateway and Cisco Virtual Network Management Center software. Use this document in combination with documents listed in the "Related Documentation" section. The following is the change history for this document.

Part Number
Revision
Date
Description

OL-25783-01

D0

12-17-12

Added resolved caveats CSCud01427, CSCud01515, CSCud1879, and CSCud33791.

OL-25783-01

C0

11-02-12

Added open caveat CSCud01427.

OL-25783-01

B0

05-08-12

Added the following resolved caveats for Release 4.2(1)VSG1(3.1a):

CSCtz21979

OL-25783-01

A0

05-02-12

Added the following open caveats for Release 4.2(1)VSG1(3.1):

CSCty18248

CSCty33854

CSCtq44369

Moved the CSCtu 47525 caveat from the open caveat list to the resolved caveat list for Release 4.2(1)VSG1(3.1).

Added the following resolved caveats for Release 4.2(1)VSG1(3.1a):

CSCty18248

CSCty33854

OL-25783-01

--

01-31-12

Created release notes for the Cisco Virtual Security Gateway for Nexus 1000V Series switch, Release 4.2(1)VSG1(3.1).


Contents

This document includes the following sections:

Introduction

Software Compatibility

Features

New and Changed Information

Limitations and Restrictions

Open Caveats—Cisco VSG Release 4.2(1)VSG1(3.1)

Resolved Caveats—Cisco VSG Release 4.2(1)VSG1(3.1)

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

The Cisco Virtual Security Gateway (VSG) for the Cisco Nexus 1000V Series switch is a virtual firewall appliance that provides trusted access to virtual data center and cloud environments with dynamic policy-driven operation, mobility-transparent enforcement, and scale-out deployment for dense multitenancy. The Cisco VSG enables a broad set of multitenant workloads that have varied security profiles to share a common compute infrastructure. By associating one or more Virtual Machines into distinct trust zones, the Cisco VSG ensures that access to trust zones is controlled and monitored through established security policies.

Together, the Cisco VSG and Cisco Nexus 1000V Virtual Ethernet Module provide the following benefits:

Efficient deployment—Each Cisco VSG can protect Virtual Machines across multiple physical servers, which eliminates the need to deploy one virtual appliance per physical server.

Performance optimization—By offloading Fast-Path to one or more Cisco Nexus 1000V VEM vPath modules, the Cisco VSG boosts its performance through distributed vPath-based enforcement.

Operational simplicity—You can insert a Cisco VSG in one-arm mode without creating multiple switches or temporarily migrating VMs to different switches or servers. Zone scaling is based on security profile, not on vNICs that are limited for virtual appliances.

High availability—For each tenant, you can deploy a Cisco VSG in an active-standby mode to ensure a highly available operating environment with vPath redirecting packets to the standby Cisco VSG when the primary Cisco VSG is unavailable

Independent capacity planning—You can place a Cisco VSG on a dedicated server, controlled by the security operations team so that maximum compute capacity can be allocated to application workloads. Capacity planning can occur independently across server and security teams, and operational segregation across security, network, and server teams can be maintained.

Software Compatibility

The servers that run the Cisco Nexus 1000V VSM and VEM must be in the VMware Hardware Compatibility list, which is a requirement for running the ESX 4.1 or 5.0 software.

For additional compatibility information, see the Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(5.1).

Features

This section provides the following information about this release:

Product Architecture

Trusted Multi-Tenant Access

Dynamic (Virtualization-Aware) Operation

Setting Up Cisco VSG and VLAN Usages

Product Architecture

The Cisco VSG operates with the Cisco Nexus 1000V distributed virtual switch in the VMWare vSphere hypervisor. The Cisco VSG leverages the virtual network service data path (vPath) that is embedded in the Cisco Nexus 1000V Virtual Ethernet module (VEM). vPath steers traffic, whether external-to-VM or VM-to-VM, to the Cisco VSG of a tenant. A split-processing model is applied where initial packet processing occurs in the Cisco VSG for policy evaluation and enforcement. After the policy decision is made, the Cisco VSG off-loads policy enforcement of remaining packets to vPath.

vPath supports the following features:

Intelligent interception and redirection—Tenant-aware flow classification and subsequent redirection to a designated Cisco VSG tenant

Fast-Path offload—Per-tenant policy enforcement of flows offloaded by the Cisco VSG to vPath

Trusted Multi-Tenant Access

You can transparently insert a Cisco VSG into the VMware vSphere environment where the Cisco Nexus 1000V distributed virtual switch is deployed. Upon insertion, one or more instances of the Cisco VSG is deployed on a per-tenant basis, which allows a highly scaled-out deployment across many tenants. Because tenants are isolated from each other, no traffic can cross tenant boundaries. Depending on the use case, you can deploy Cisco VSG at the tenant level, at the virtual data center (vDC) level, as well as at the vApp level.


Note The Cisco VSG is not inherently multitenant. It must be explicit within each tenant.


As VMs are instantiated for a given tenant, association to security profiles and zone membership occurs immediately through binding with the Cisco Nexus 1000V port profile. Upon instantation, each VM is placed into a logical trust zone. Security profiles contain context-aware rule sets that specify access policies for traffic that enters and exits each zone. With the VM and network contexts, you can leverage custom attributes to define zones directly through security profiles. The profiles are applied to zone-to-zone traffic and external-to-zone/zone-to-external traffic. This enforcement occurs within a VLAN because a VLAN often identifies a tenant boundary.

The Cisco VSGs evaluate access control rules and then offloads enforcement to the Cisco Nexus 1000V VEM vPath module for performance optimization. Access is permitted or denied based on policies. The Cisco VSG provides policy-based traffic monitoring capability and generates access logs.

Dynamic (Virtualization-Aware) Operation

A virtualization environment is dynamic, where frequent additions, deletions, and changes occur across tenants and especially across VMs. Live migration of VMs can occur due to manual or programmatic vMotion events.

A Cisco VSG operates with the Cisco Nexus 1000V (and vPath), which supports a dynamic VM environment. Typically, a tenant is created with the Cisco VSG (standalone or active-standby pair) and on the Cisco Virtual Network Management Center (VNMC). Associated security profiles are defined that include trust zone definitions and access control rules.

Each security profile is bound to a Cisco Nexus 1000V port profile (authored on the Cisco Nexus 1000V Virtual Supervisor Module and published to the VMWare Virtual Center). When a new VM is instantiated, you can assign appropriate port profiles to the virtual Ethernet port of the VM. Because the port profile uniquely refers to a security profile and VM zone membership, security controls are immediately applied. A VM can be repurposed by assigning a different port profile or security profile.

As vMotion events occur, VMs move across physical servers. The Cisco Nexus 1000V ensures that port profile policies and associated security profiles follow the VMs. Security enforcement and monitoring remain transparent to vMotion events.

Setting Up Cisco VSG and VLAN Usages

A Cisco VSG is set up in an overlay fashion so that VMs can reach a Cisco VSG irrespective of its location. The vPath component in the Cisco Nexus 1000V VEM intercepts the packets from the VM and sends them to the Cisco VSG for further processing.

A Cisco VSG is configured with three vNICS that are each connected to one of the VLANs. The VLAN functions are as follows:

The Management VLAN connects management platforms such as the VMware vCenter, Cisco Virtual Network Management Center, Cisco Nexus 1000V VSM, and the managed Cisco VSGs.

The Service VLAN provides communications between the Cisco Nexus 1000V VEM and Cisco VSGs. All Cisco VSGs are part of the Service VLAN. In layer 2 mode the VEM uses this VLAN for interaction with Cisco VSGs.

The HA VLAN identifies the active and standby relationship.

You can allocate one or more VM Data VLAN(s) for VM-to-VM communications. In a multitenant environment, the Management VLAN is shared among all tenants. The Service VLAN, HA VLAN, and the VM Data VLAN are allocated on a per-tenant basis. When VLAN resources are scarce, you can use a single VLAN for Service and HA functions.

New and Changed Information

This section describes the new and changed features for the Cisco Virtual Security Gateway for Nexus 1000V Series Switch, Release 4.2(1)VSG1(3.1).

Cisco VSG for Nexus 1000V Series Switch, Release 4.2(1)VSG1(3.1a)

This is a maintenance release that includes bug fixes. This release does not include new software features.

New Software Features

Support for Layer 3 mode—Release 4.2(1)VSG1(3.1) supports the Cisco VSG deployment in the Layer 3 mode. The Cisco VSG and the VEM are no longer required to be in the same Layer 2 network. The VEM and the Cisco VSG communicate with each other through a special virtual network interface called the Virtual Kernel NIC (vmknic). This vnmknic is created by an administrator. For more information, see the Cisco Virtual Security Gateway for Nexus 1000V Series Switch Configuration Guide, Release 4.2(1)VSG1(3.1).

VXLAN— Cisco Nexus 1000V release 4.2(1)SV1(5.1) supports Virtual Extensible Local Area Network (VXLAN) feature that defines a 24-bit LAN segment identifier to provide segmentation at cloud scale (for more information, see the Cisco Nexus 1000v Interface Configuration Guide, Release 4.2(1)SV1(5.1). With Release 4.2(1)VSG1(3.1), the Cisco VSG supports protection for VM backed by VXLAN.

Limitations and Restrictions

The Cisco Virtual Security Gateway for Nexus 1000V Series switch has the following limitations and restrictions:

Jumbo frames cannot be configured for the Cisco VSG management interface.

Vmotion of the Cisco VSG is validated for host upgrades only and not for DRS purposes.

Enabling firewall protection on a router virtual machine may cause problems for policies based on VM attributes; firewall protection should be enabled only for end-point Virtual Machines.

The maximum numbers for Cisco VSG objects are as follows:

Cisco VSG Objects
Limits

Rules per policy

256

Rules per VSN

1024

Active policies

32

Object-groups per VSN

64

Zones per VSN

32

Customer attributes per security profile

16

Concurrent connections

256,000


OVA Installation Behavior

During OVA installation, the following error message might be seen:

The network card VirtualE1000 has dvPort backing, which is not supported. This could be because the host does not support vDS, or because the host is not using vDS.

Workaround: Ensure that all three network interfaces in the Cisco VSG port profile are set to VM Network (port profile from vSwitch) during OVA installation. Once the virtual machine is created, the port profile for these three interfaces should be changed according to the Cisco Virtual Security Gateway, Release 4.2(1)VSG1(2) and Cisco Virtual Network Management Center, Release 1.2 Installation and Upgrade Guide.

If the VSM is down when the Cisco VSG is powered on, the Cisco VSG continuously tries to reboot.

Workaround: To prevent this situation, configure the Service VLAN and the HA VLAN used by the Cisco VSG as system vlan vlan_number in the uplink port profile.

Layer 2 Mode

When the VEM communicates with the Cisco VSG in the Layer 2 mode, an additional header with 74 bytes is added to the original packet. The VEM fragments the packet if it exceeds the uplink MTU.

For better performance, increase the MTU of all links between the VEM and the Cisco VSG by 74 bytes to account for packet encapsulation which occurs for communication between vPath and the Cisco VSG. For example, if the MTU values of the client and server VMs and uplink are all 1500 bytes, set the uplink MTU to 1574 bytes.

Layer 3 Mode

When the VEM communicates with the Cisco VSG in the Layer 3 mode, an additional header with 94 bytes is added to the original packet. The VEM does not support fragmentation in Layer 3 mode and the ports/network-elements (which carry vPath encapsulated packets) must be configured in such a way that the vPath overhead is accommodated. For example, if MTU values of client and server VMs and uplink are all 1500 bytes, set the uplink MTU to 1594 bytes.

If the jumbo frames are enabled in the network, make sure the MTU of the client and server VMs are 94 bytes smaller than the uplink. For example, if the uplink MTU is 9000 bytes, set the MTU of the client and server VMs to 8906 bytes.

When encapsulated traffic that is destined to a Cisco VSG is connected to a different subnet other than the vmknic subnet, the VEM does not use the VMware host routing table. Instead, the vmknic initiates an ARP for the remote Cisco VSG IP addresses. You must configure the upstream router to respond by using the proxy ARP feature.

The VEM does not support a routing functionality and it is assumed that the upstream switch/router is configured with the proxy-ARP configuration.

Configuring a Rule with a Reset Action

Configuring a rule with a reset action for the non-TCP/UDP protocol will result in dropped traffic. However, the syslog generated for this traffic shows that the action performed for the traffic is reset as shown below:

2011 June 16 07:19:56 VSG-Fw %POLICY_ENGINE-6-POLICY_LOOKUP_EVENT: 
policy=ps-web@root/Tenant-A rule=pol-B/udp-rule@root/Tenant-A action=Reset 
direction=ingress src.net.ip-address=172.31.2.107 dst.net.ip-address=172.31.2.101 
net.protocol=1 net.ethertype=800 src.vm.name=sg-centos-vk-7 src.vm.host-name 
=10.193.75.91 src.vm.os-fullname="red hat enterprise linux 5 (64-bit)" 
dst.vm.cluster-name 
="sg1-dc1-clu1 ankaa tenth" src.vm.cluster-name="sg1-dc1-clu1 ankaa tenth" 
dst.vm.portprofile-name=access-3770-tenant-a 
src.vm.portprofile-name=access-3770-tenant-a dst.zone.name=centos-zone@root/Tenant-A 
src.zone.name=centos-zone@root/Tenant-A src.vm.os-hostname=(null) 
src.vm.res-pool=(null)

Cisco VSG CLI Session Time Out

The CLI session for the Cisco VSG version 1.3x that is newly deployed will time out after a period of five minutes of an inactivity. The CLI session time out does not work on Cisco VSG that has been upgraded from version 1.0x.

On the Cisco VSG that is upgraded from version 1.0x, the show running-config will consist only of the following items:

- gold001-vsg01# sh run | i line|timeout

- line console

- gold001-vsg01#

As a workaround, when upgrade is done from 1.0x to 1.3 version of VSG, "exec-timeout 5" can be configured under "line console" and "line vty" command modes to enable a five minutes CLI session inactivity timeout.

Caveats

This section include the following topics:

Open Caveats—Cisco VSG Release 4.2(1)VSG1(3.1)

Open Caveats—Cisco VSG Release 4.2(1)VSG1(3.1a)

Resolved Caveats—Cisco VSG Release 4.2(1)VSG1(3.1)

Resolved Caveats—Cisco VSG Release 4.2(1)VSG1(3.1a)

Open Caveats—Cisco VSG Release 4.2(1)VSG1(3.1)

The following are descriptions of the caveats in Cisco Virtual Security Gateway for Nexus 1000V Series switch, Release 4.2(1)VSG1(3.1). The ID links open the Cisco Bug Toolkit.

ID
Open Caveat Headline

CSCtf94204

Inconsistencies appear in the slot numbering when the show commands show system internal redundancy are run.

CSCtg97333

The clear counters interface data0 command on the Cisco VSG is not working.

CSCth91644

The wrong syslog is pushed when the management interface IP is changed.

CSCti09598

VNSP binding for the same IP address in two VLANs replaces the old value in the Cisco VSG.

CSCti11925

Policy-engine control debugs displayed information related to the data traffic.

CSCti39155

Virtual Machine IP addresses are not learned by the VEM and VSM if the virtual machine is protected by the firewall, and no traffic has been sent from the virtual machine.

CSCti58398

The same policy-engine syslog is generated multiple times for a broadcast traffic.

CSCti89749

The Cisco VSG HA requires domain isolation for multi-tenant setups that share a management VLAN.

CSCtk01744

Policy-engine statistics and the service-path statistics do not show the correct information after a system switchover.

CSCtk83021

Remove unused commands on the Cisco VSG.

CSCto89854

VMs under tenants disappear and reappear.

CSCto97454

TCP Checks: Downloading of a file stops during/after vmotion.

CSCtr01200

Fail to copy running config to start-up with 1024 rules 16 conditions each.

CSCtr41120

Cisco VSG firewall has a firewall issue.

CSCtr50316

Port profile org root to default SP (root) is showing as "Org not configured in Port profile".

CSCtr56196

The show license usage...shows incorrect information after port profile edit.

CSCtr71543

The sh service-path conn command output does not show action inspect for rsh traffic.

CSCtr76752

The show ntp peers command periodically gets stuck with VNMC DNS configuration changes.

CSCtq44369

The show service-path connection command does not show the connection details on the destination module for a VEM to VEM connection.

CSCtu18273

The show vsn connection command shows wrong information.

CSCtu22546

The show service-path connection command output does not show the VXLAN number.

CSCtx08323

VNSP ID is retained even after the SP at root node is deleted from the VNMC.

CSCtx14556

The PA installation is successful with feature http_only enable and https disabled.

CSCtx49694

The show vsn connection command output may show inconsistent information for ping traffic with bidirectional traffic.

CSCty18248

After upgrading the Cisco VSG from Release 4.2(1)VSG1(2) to Release 4.2(1)VSG1(3.1) using the install all command, any changes to the VSG configuration that are done at the Cisco VNMC do not get applied to the Cisco VSG.

CSCty08228

When the virtual machines on the VEM are enabled only for vWAAS, the Cisco VSG license is checked out for that VEM.

CSCty33854

Zone classification may get evaluated incorrectly in a case where IP-binding is not learned before traffic reaches Cisco VSG.


Open Caveats—Cisco VSG Release 4.2(1)VSG1(3.1a)

The following are descriptions of the caveats in Cisco Virtual Security Gateway for Nexus 1000V Series switch, Release 4.2(1)VSG1(3.1a). The ID links open the Cisco Bug Toolkit.

ID
Open Caveat Headline

CSCty08228

When the virtual machines on the VEM are enabled only for vWAAS, the Cisco VSG license is checked out for that VEM.


Resolved Caveats—Cisco VSG Release 4.2(1)VSG1(3.1)

The following table describes the resolved caveats in Cisco Virtual Security Gateway for Nexus 1000V Series switch, Release 4.2(1)VSG1(3.1). The ID links open the Cisco Bug Toolkit.

ID
Resolved Caveat Headline

CSCtr55312

Large number is observed in sh vsn statistics o/p.

CSCtr73966

Intermittent ICMP IP fragment packet drops.

CSCtu47525

A new policy agent (PA) does not register when using the install command if there is no PA installed.

CSCud01427

The VSM/VEM licensing for Cisco VSG enters an unlicensed mode after you upgrade from Cisco Nexus 1000V Series switch Release 4.2(1) SV1(5.1) or Release 4.2(1) SV1(5.1a) to Release 4.2(1) SV1(5.2).

CSCud01515

A Cisco Nexus 1000V Series switch should fail close when no license is installed for Cisco VSG.

CSCud18794

PSOD related to a Cisco Nexus 1000V Series switch occurred on the ESXi host.

CSCud33791

A duplicate IP event is detected in Windows 2008 VMs in vPath when the network adapter flaps.


Resolved Caveats—Cisco VSG Release 4.2(1)VSG1(3.1a)

The following table describes the resolved caveats in Cisco Virtual Security Gateway for Nexus 1000V Series switch, Release 4.2(1)VSG1(3.1a). The ID links open the Cisco Bug Toolkit.

ID
Resolved Caveat Headline

CSCty18248

After upgrading the Cisco VSG from Release 4.2(1)VSG1(2) to Release 4.2(1)VSG1(3.1a) using the install all command, any changes to the VSG configuration that are done at the Cisco VNMC do not get applied to the Cisco VSG.

CSCty33854

Zone classification may get evaluated incorrectly in a case where IP-binding is not learned before traffic reaches Cisco VSG.

CSCtz21979

The Cisco VSG shows VSM (Nexus 1000V) sysObjectId in response to snmp query for sysObjectID.


Related Documentation

This section contains information about the documentation available for Cisco Virtual Security Gateway and related products.

Cisco Virtual Security Gateway Documentation

The following Cisco Virtual Security Gateway for the Nexus 1000V Series Switch documents are available on Cisco.com at the following URL:

http://www.cisco.com/en/US/products/ps13095/tsd_products_support_series_home.html

Cisco Virtual Security Gateway for Nexus 1000V Series Switch Release Notes, Release 4.2(1)VSG1(3.1)

Cisco Virtual Security Gateway, Release 4.2(1)VSG1(3.1) and Cisco Virtual Network Management Center, Release 1.3 Installation and Upgrade Guide

Cisco Virtual Security Gateway for Nexus 1000V Series Switch License Configuration Guide, Release 4.2(1)VSG1(3.1)

Cisco Virtual Security Gateway for Nexus 1000V Series Switch Configuration Guide, Release 4.2(1)VSG1(3.1)

Cisco Virtual Security Gateway for Nexus 1000V Series Switch Command Reference, Release 4.2(1)VSG1(3.1)

Cisco Virtual Security Gateway for Nexus 1000V Series Switch Troubleshooting Guide, Release 4.2(1)VSG1(3.1)

Cisco Virtual Network Management Center Documentation

The following Cisco Virtual Network Management Center documents are available on Cisco.com at the following URL:

http://www.cisco.com/en/US/products/ps11213/tsd_products_support_series_home.html

Cisco Nexus 1000V Series Switch Documentation

The Cisco Nexus 1000V Series Switch documents are available on Cisco.com at the following URL:

http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.