Chapter 1. Overview

Information About Microsoft System Center Virtual Machine Manager 2012 SP1

Microsoft Hyper-V Extensible Switch

Logical Switch

Creating a Switch Extension

Cisco Nexus 1000V for Microsoft SCVMM

Logical Networks and Network Segment Pools

VM Networks

Network Segments

IP Pool Templates

Port Profiles

Policy and Network Separation

Dynamic Port Profiles

Uplink Port Profile

Configuring PVLANs

Chapter 2. Configuring Network Segmentation Manager

Prerequisites

Guidelines and Limitations

Creating a Logical Network

Creating a Network Segment Pool

Creating an IP Pool Template

Creating a Network Segment

Creating an Ethernet Port Profile

Creating a vEthernet Port Profile

Configuring an Uplink Network

Configuring a Network Uplink in Access Mode

Configuring Uplink Profile in Port-Channel Mode

Configuring a vEthernet Profile with Features

Configuring System VLAN

Configuring PVLAN on vEthernet and Ethernet Interfaces

Configuring Secondary PVLAN Mode

Feature History for Network Segmentation Manager

Chapter 3. Verifying the Configuration using Show Commands

Verifying the NSM Configuration

Preface

Audience

Document Conventions

Related Documentation for Cisco Nexus 1000V for KVM Software

Related Documentation for Cisco Nexus 1000V for Microsoft Hyper-V Software

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. Overview

This chapter contains the following sections:

- Information About Microsoft System Center Virtual Machine Manager 2012 SP1

- Microsoft Hyper-V Extensible Switch

- Logical Switch

- Creating a Switch Extension

- Cisco Nexus 1000V for Microsoft SCVMM

- Logical Networks and Network Segment Pools

- VM Networks

- Network Segments

- IP Pool Templates

- Port Profiles

- Policy and Network Separation

- Dynamic Port Profiles

- Uplink Port Profile

- Configuring PVLANs

Information About Microsoft System Center Virtual Machine Manager 2012 SP1

Microsoft System Center Virtual Machine Manager 2012 SP1 is a comprehensive IT infrastructure, virtualization, and cloud management platform. With this platform, you can manage your applications and services across multiple hyper visors and across public, hosted, and private cloud infrastructures to deliver flexible and cost-effective IT services. Microsoft SCVMM allows the administrators to configure and manage the servers, the network, and the storage resources.

Microsoft SCVMM 2012 SP1 introduces the following constructs to model and configure the networks on the Hyper-V servers:

- Logical Network

- Network Site

- VM Network

- VM Subnet

- IP Pool

- Uplink Profile

- Port Classification

- Logical Switch

Microsoft Hyper-V Extensible Switch

Microsoft Hyper-V supports an extensible switch architecture. The third party networking vendors can provide Monitoring, Filtering, and Forwarding extensions to the Microsoft Extensible Switch (native virtual switch). Cisco Nexus 1000V is a Forwarding extension to the Microsoft Extensible Switch. Because the Forwarding extensions can also be used to perform the filtering and capturing functionality, an Hyper-V Extensible Switch running the Cisco Nexus 1000V can perform the forwarding, filtering, and monitoring functions.

Logical Switch

A Logical Switch, created on Microsoft SCVMM 2012 SP1, is a switch template. It contains a set of parameters (for example, switch extensions, uplink port profiles, and port classifications that are introduced later in this document) that you can use to create Hyper-V Virtual Switches on Windows Server 2012 host computers. A Logical Switch helps to configure a consistent network policy across many Hyper-V hosts.

Creating a Switch Extension

To use the Cisco Nexus 1000V as a Forwarding extension in a Logical Switch (an Hyper-V extensible switch on a Hyper-V host) on Microsoft SCVMM, the SCVMM administrator should first register the Cisco Nexus 1000V by creating a Virtual Switch Extension Manager (VSEM). The VSEM connects to the Cisco Nexus 1000V VSM using an IP address and the administrator credentials of the Cisco Nexus 1000V. See the Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide for information on creating a switch extension.

Note

Changing the administrator password requires a corresponding change in the Run As Account that the VSEM uses to connect to the Cisco Nexus 1000V VSM.

Cisco Nexus 1000V for Microsoft SCVMM

Microsoft SCVMM SP1 models the physical networks as a fabric. As part of this approach, a number of new abstractions have been introduced. To aid the network administrator managing the virtual access layer, Cisco Nexus 1000V has introduced a capability to configure and edit the following new objects based on Microsoft SCVMM SP1 network object model:

- Logical Networks

- Network Segment Pools (results in the creation of Network Sites on VMM)

- Network Segments (results in the creation of VM Network and VM Subnet)

- IP Pools

See the Microsoft SCVMM SP1 networking object model for reference.
Microsoft SCVMM SP1 Networking Object Model

Logical Networks and Network Segment Pools

A logical network models distinct networks managed by an enterprise. The logical network abstraction hides the VLANs and IP Subnets that make the network from all the users (the VM network administrators, the tenant administrators, and the server administrators) other than the fabric administrator managing the physical fabric. In other words, a logical network is composed of one or more network segment pools and each network segment pool is a group of VLANS, IP subnets, or VLAN/IP subnet pairs.

Consider an hypothetical enterprise that operates two data centers, one in San Francisco and one in New York. The enterprise has two subnets at each site:

- The San Francisco site uses subnet 10.0.0.0/8 to provide an Intranet network. The subnet 20.0.0.0/8 is used to create a DMZ network.

- The New York site uses subnet 30.0.0.0/8 to provide an Intranet network. The subnet 40.0.0.0/8 is used to create a DMZ network.

Logical Networks

To model the network fabric, the SCVMM administrator creates two logical networks: Intranet and DMZ. The Intranet logical network has two network sites, 10.0.0.0/8 and 30.0.0.0/8 and two VLANs . The DMZ logical network has two network sites, 20.0.0.0/8 and 40.0.0.0/8 and two VLANs. The server administrator deploys the host to the Intranet logical network.

VM Networks

VM networks allow the Microsoft SCVMM administrator to create an isolated virtual Layer 3 network. Each VM network can have one or more VM subnets (virtual Layer 2 domain). The Microsoft SCVMM SP1 supports VLAN-backed and Network Virtualization (NVGRE)-backed VM networks. The Cisco Nexus 1000V allows the network administrators to create the VLAN-backed VM networks only.

Note

The Microsoft SCVMM SP1 allows creating multiple VM subnets under a VM network only when NVGRE is used. A VLAN-backed VM network always contains only one VM subnet.

VM Networks and VM Subnets

In the example, the San Francisco datacenter has two IP subnets each of which is associated with a VLAN. In San Francisco datacenter, the subnet 10.0.0.0/8 is associated with VLAN 100. The subnet 20.0.0.0/8 is associated with VLAN 200. To deploy the VMs to VLAN 100 and VLAN 200, the network administrator creates two network segments, for example, VMNetworkA and VMNetworkB. After the network administrator creates a network segment VMNetworkA, the Microsoft SCVMM administrator has to create a VM network that uses the network segment, VMNetworkA. This is a prerequisite for the VMs to be deployed to the VLAN/network segment. To deploy the VMs to VLAN 300 and VLAN 400, the network administrator creates two network segments, for example, VMNetworkC and VMNetworkD as illustrated in the following example.

VM Networks in a Logical Network

Network Segments

A network segment is associated with a unique broadcast domain. A network segment facilitates the availability of the network resources to a virtual machine. OpenStack controller uses the VM networks and the VM subnets to provide the isolated virtual machine networks. When Cisco Nexus 1000V is used to manage the virtual network, the OpenStack controller creates the VM networks that use an external isolation. An external isolation is provided by creating the network segments on the Cisco Nexus 1000V by the network administrator. The network administrator provides the isolated networks using the VLANs and the private VLANs.

Note

In OpenStack controller, a VLAN is not created to define a bridge domain. Instead, a network segment is created on the VSM. Creating a network segment triggers an auto-creation of VLANs.

IP Pool Templates

The server administrators can manage the IP addresses for the virtual environment using an IP pool template. You can assign a range of IP addresses to the hosts and to the virtual machines that are running inside the OpenStack environment using the IP pool templates. When you create an IP pool template for a VM network, you can define a range of IP addresses that are used by the VMs that are managed by OpenStack controller.

Note

In an IP pool template, the maximum number of reserved IP addresses is 128.

The IP pool templates are the address templates that are applied to the network segments.

Port Profiles

A port profile is a collection of the interface-level configuration attributes. The network administrator creates a consistent network policy across the similar VM interfaces by defining the Virtual Ethernet port profiles. The network administrator can also create a port profile for the VM hosts adapters. The profile defines the policy to be applied on the physical Ethernet adapters on the servers.

Policy and Network Separation

In the Cisco Nexus 1000V for OpenStack environment, features and network segments are independently associated with the interfaces. The independent association allows you to assign the same set of features on the interfaces that are spread across multiple dynamically-allocated network segments. With this capability, a network administrator can define the policy profiles and export policy profiles to the OpenStack environment. The OpenStack cloud administrator can allocate the network segments from the network pools dynamically, and associate the virtual machine (VM) interfaces to the policy profile and the allocated network segment. This decoupling provides the flexibility to allocate network segments dynamically while grouping the network features to be applied on the interfaces.

Dynamic Port Profiles

A virtual machine (VM) is deployed to the virtual access layer by choosing the Port Classification, the VM Network, and the VM subnet. When a VM is deployed, a port profile is dynamically created on the Cisco Nexus 1000V for each unique combination of the network segment and policy port profile. All other VMs deployed with the same policy to this network reuse this dynamic port profile. This dynamic port profile is a combination of network isolation and network policy.

Note

The auto-generated profile should neither be modified nor inherited in any other port profiles.

The port-attach notification carries a port UUID. The VSM looks up the port UUID and retrieves the associated combination of policy port profile and network segment. This combination is represented by a dynamic port profile that is inherited on the interface. If more than one port uses the same combination of policy port profile and the network segment, the dynamic port profile is shared. Dynamic port profiles are auto-created in the VSM as a result of configuration steps executed using SCVMM.

Uplink Port Profile

An uplink port profile is essentially a template in which you define the list of network segment pools that should be associated with any (physical) network adaptors that it is applied to. It also allows you to specify the protocols and the port policy for the uplink adapter using an Ethernet port profile.

Configuring PVLANs

Each network segment is associated with one broadcast domain. In case of PVLAN, each secondary VLAN is considered as one broadcast domain and a network segment is created to represent that. All secondary VLAN network segments for a particular primary VLAN are bundled into one network segment pool and the network segment pool defines which primary VLAN it represents.

For every primary VLAN, a network segment pool is created. The primary VLAN is also represented as a network segment. All secondary network segments and the corresponding primary network segments are bundled into one network segment pool. There can be only one primary VLAN network segment in a given network segment pool. This bundle can also have the normal VLAN network segments.

A network segment identifies whether it represents a community, isolated, or promiscuous port. The secondary VLAN network segments can either be in a community, isolated, or promiscuous mode. When the mode is promiscuous, it can specify which secondary VLANs are allowed. A port attaching to the secondary VLAN network segment becomes a part of a community, or stand isolated, or be in a promiscuous mode and is able to listen on the specified secondary VLANs. A VM port also can be a promiscuous port.

Chapter 2. Configuring Network Segmentation Manager

This chapter contains the following sections:

Prerequisites

Network Segmentation Manager has the following prerequisites:

- You have installed the Cisco Nexus 1000V software and configured the VSM using the Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide.

Guidelines and Limitations

The network segmentation manager feature has the following configuration guidelines and limitations:

- The network-segmentation-manager feature is enabled on the VSM by default. Verify the output of the show feature command on the VSM to make sure that the network-segmentation-manager feature is enabled by default.

- Microsoft SCVMM should be able to communicate with the Cisco Nexus 1000V using HTTP.

- The http-server feature is enabled by default on the Cisco Nexus 1000V to allow web service communication.

- To modify the association of a published network segment to a network segment pool, you must delete and re-create the network segment with the new association. This rule is applicable for the network segment pool, the network uplink, and the virtual port-profiles.

Creating a Logical Network

You can create a logical network for the host connectivity using the following steps:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# nsm logical network <name>

3.    (Optional) switch(config-logical-net)# description <description >

4.    (Optional) switch(config-logical-net)# no description

5.    switch(config-logical-net)# end

6.    switch(config-logical-net)# exit

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# nsm logical network <name>

Creates a logical network.

Step 3

switch(config-logical-net)# description <description >

(Optional)
Configures the description for the logical network. The maximum size of the characters is 256.

Step 4

switch(config-logical-net)# no description

(Optional)
Negates a command or sets its defaults.

Step 5

switch(config-logical-net)# end

Navigates to the execution mode.

Step 6

switch(config-logical-net)# exit

Exits the logical network.

This example shows how to create a logical network named IntranetSFO. Use the show nsm logical network name <name> command to display the configuration details of the logical network.

switch# configure terminal
switch(config)# nsm logical network IntranetSFO
switch(config-logical-net)# description  Network for external Internet connectivity
switch(config-logical-net)# exit

switch(config)# show nsm logical network name IntranetSFO
Name: IntranetSFO
Description: Network for external Internet connectivity

Creating a Network Segment Pool

You can create a network segment pool for the host connectivity using the following steps:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)#nsm network segment pool <name>

3.    switch(config-net-seg-pool)#member-of logical network name

4.    (Optional) switch(config-net-seg-pool)#no [intraportcom | member-of]

5.    (Optional) switch(config-net-seg-pool)#this config

6.    switch(config-net-seg-pool)# end

7.    switch(config-net-seg-pool)# exit

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)#nsm network segment pool <name>

Configures the name of the network segment pool. The maximum size of the characters is 64.

Step 3

switch(config-net-seg-pool)#member-of logical network name

Configures a logical network for the network segment pool.

Step 4

switch(config-net-seg-pool)#no [intraportcom | member-of]

(Optional)
Negates a command or sets its defaults.

Step 5

switch(config-net-seg-pool)#this config

(Optional)
Shows the running configuration for the current object (mode's instance).

Step 6

switch(config-net-seg-pool)# end

Goes to the configuration mode.

Step 7

switch(config-net-seg-pool)# exit

Exits the configuration mode.

This example shows how to configure a network segment pool named IntranetSJ. Use the show nsm network segment pool name <name> to view the configuration.

switch#  configure terminal
switch(config)#  nsm network segment pool IntranetSJ
switch(config-net-seg-pool)#  member-of logical network IntranetSFO
switch(config-net-seg-pool)#  exit

switch(config)# show nsm network segment pool name IntranetSJ
Name: IntranetSJ
GUID: 5e4cb505-3255-4ef8-8480-685904fc9685
Logical network Name: IntranetSFO
Intra Port Communication: Disabled
Publish-name: IntranetSJ

Creating an IP Pool Template

You can create an IP pool template using the following steps:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)#nsm ip pool template <name>

3.    switch(config-ip-pool-template)#ip [address | reserved]

4.    switch(config-ip-pool-template)#network <A.B.C.D> <a.b.c.d>

5.    (Optional) switch(config-ip-pool-template)#default-router <A.B.C.D>

6.    (Optional) switch(config-ip-pool-template)#description

7.    (Optional) switch(config-ip-pool-template)#dhcp

8.    (Optional) switch(config-ip-pool-template)#dns-server <A.B.C.D>

9.    (Optional) switch(config-ip-pool-template)#dns-suffix

10.    (Optional) switch(config-ip-pool-template)#netbios-name-server <A.B.C.D>

11.    (Optional) switch(config-ip-pool-template)#netbt

12.    (Optional) switch(config-ip-pool-template)#no <description>

13.    switch(config-ip-pool-template)#end

14.    switch(config-ip-pool-template)#exit

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)#nsm ip pool template <name>

Configures the name of the NSM IP pool template. The maximum size of the characters is 64.

Step 3

switch(config-ip-pool-template)#ip [address | reserved]

Configures an IP address or a reserved IP address for the IP pool template.

Note:
You cannot configure the IP address range starting with an IP address x.x.x.0 or x.x.x.1. The range of the IP address should start with an IP address x.x.x.2 and onwards.

Note:
You can modify the IP pool range after the IP pool is part of the network segment. Use the ip address command under nsm ip pool template to specify the new ip pool range.

Step 4

switch(config-ip-pool-template)#network <A.B.C.D> <a.b.c.d>

Configures the network address range for the IP pool template, where <A.B.C.D> is the range of the IP address and <a.b.c.d> is the subnet.

Step 5

switch(config-ip-pool-template)#default-router <A.B.C.D>

(Optional)
Configures a gateway for the IP pool template.

Step 6

switch(config-ip-pool-template)#description

(Optional)
Configures the description of the IP pool template.

Step 7

switch(config-ip-pool-template)#dhcp

(Optional)
Configures DHCP support of the IP pool template.
Note:
This command is not supported for the current release.

Step 8

switch(config-ip-pool-template)#dns-server <A.B.C.D>

(Optional)
Configures the DNS server IP address of the IP pool template.

Step 9

switch(config-ip-pool-template)#dns-suffix

(Optional)
Configures DNS suffix for the IP pool template.

Step 10

switch(config-ip-pool-template)#netbios-name-server <A.B.C.D>

(Optional)
Configures the IP address of the netbios name server for the IP pool template.

Step 11

switch(config-ip-pool-template)#netbt

(Optional)
Enables netbios over TCP/IP for the IP pool template.

Step 12

switch(config-ip-pool-template)#no <description>

(Optional)
Negates a command or sets its defaults.

Step 13

switch(config-ip-pool-template)#end

Goes to the execution mode.

Step 14

switch(config-ip-pool-template)#exit

Exits the logical network.

The following example displays how to create an IP pool template named pool10. Add a description and configure a range of the IP address, subnet mask, and gateway for the IP pool template using the commands in the example. Use the show nsm ip pool template name <name> command to view the configuration.

switch# configure terminal
switch(config)# nsm ip pool template pool10
switch(config-ip-pool-template)# description pool
switch(config-ip-pool-template)# ip address 172.16.10.7 172.16.10.100
switch(config-ip-pool-template)# network 172.16.10.10 255.255.255.0
switch(config-ip-pool-template)# exit

switch(config)# show nsm ip pool template name pool10
Name: pool10
Description: pool
IP-address-range: 172.16.10.7-172.16.10.100
Network: 172.16.10.10
Subnet mask: 255.255.255.0
Default router:
Netbios: Disabled
DHCP: Disabled
Reserved-ip-list:
Netbios-name-server-list:
DNS-server-list:
DNS-suffix-list:
switch(config)# show nsm ip pool template usage network segment
Ip-pool: pool10
VMNetworkA
switch(config)#
//Modify the IP pool range
switch(config)# nsm ip pool template pool10
switch(config-ip-pool-template)# ip address 172.16.10.7 172.16.10.150
switch(config)# show nsm ip pool template name pool10
Name: pool10
Description: pool
IP-address-range: 172.16.10.7-172.16.10.150
Network: 172.16.10.10
Subnet mask: 255.255.255.0
Default router:
Netbios: Disabled
DHCP: Disabled
Reserved-ip-list:
Netbios-name-server-list:
DNS-server-list:
DNS-suffix-list:

Creating a Network Segment

You can create a network segment for the VM connectivity using the following steps:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)#nsm network segment <name>

3.    (Optional) switch(config-net-seg)#description <name>

4.    switch(config-net-seg)# ip pool import template <template-name>

5.    switch(config-net-seg)#member-of network segment pool <name>

6.    (Optional) switch(config-net-seg)#no [description | ip | network | publish | switchport | system ]

7.    switch(config-net-seg)#switchport [ access | private-vlan ]

8.    (Optional) switch(config-net-seg)#system network segment

9.    switch(config-net-seg)#publish network segment <name>

10.    switch(config-net-seg)#end

11.    switch(config-net-seg)#exit

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)#nsm network segment <name>

Creates a network segment.

Step 3

switch(config-net-seg)#description <name>

(Optional)
Enters the description of the network segment.

Step 4

switch(config-net-seg)# ip pool import template <template-name>

Import an IP pool template.

Note:
You can modify the IP pool range after the IP pool is part of the network segment.

Step 5

switch(config-net-seg)#member-of network segment pool <name>

Configures a network segment pool for the VM network segment pool.

Step 6

switch(config-net-seg)#no [description | ip | network | publish | switchport | system ]

(Optional)
Negates a command or sets its defaults.

Step 7

switch(config-net-seg)#switchport [ access | private-vlan ]

Configures the switchport mode as access or private-vlan for the network segment pool. The default mode is access.

Step 8

switch(config-net-seg)#system network segment

(Optional)
Configures the segment as a system segment.

Step 9

switch(config-net-seg)#publish network segment <name>

Publishes the VM network segment to SCVMM. The name option is used to publish the segment with a different name. The default published name is same as the segment name.

Step 10

switch(config-net-seg)#end

Goes to the configuration mode.

Step 11

switch(config-net-seg)#exit

Exits the configuration.

The following example shows how to configure a network segment named VMNetworkA. Configure the switchport mode as access and associate a network segment pool named IntranetSJ to the network segment. Use the show nsm network segment name <name>, show nsm network segment brief, and show nsm network segment virtual usage commands to view the network segment configuration.

switch#  configure terminal
switch(config)#  nsm network segment VMNetworkA
switch(config-net-seg)# switchport access vlan 100
switch(config-net-seg)# member-of network segment pool IntranetSJ
switch(config-net-seg)# ip pool import template pool10
switch(config-net-seg)# publish network segment VMNetworkA
switch(config-net-seg)# end

switch(config)# show nsm network segment name VMNetworkA
Name: VMNetworkA
VM Network Name: VMNetworkA
VM Network GUID: 584d510b-0eba-485d-9262-a78c0a1fcfe3
Description:
GUID: 68f827e8-247d-4f3d-bebf-73d14d0a613a
Network segment pool: IntranetSJ
Vlan: 100
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: fb05d8b0-724d-478b-a550-bf75f0a646ad
Publish-name: VMNetworkA

switch(config)# show nsm network segment brief

--------------------------------------------------------------------------------
Network segment               Mode           VLAN      Pub       Sys
--------------------------------------------------------------------------------
VMNetworkA                    access         100       1         0

--------------------------------------------------------------------------------
Total          Total Pub      Total Sys
--------------------------------------------------------------------------------
1              1              0

switch(config)# show nsm network segment virtual usage

-------------------------------------------------------------------------------
Network segment     Port Profile                                                                                       Port        Owner
-------------------------------------------------------------------------------
VMNetworkA                  dynpp_34417837-ae75-4360-87e8-3c33d9f59370_
3fb0ef6f-2b0e-47c8-b226-2da2dbc1bbe2
Veth2       ABC_VM_02
Veth3       ABC_VM_03
net-seg-101         dynpp_34417837-ae75-4360-87e8-3c33d9f59370_
60b14436-6cc6-45df-8071-082b2e2e5652
Veth1       XYZ_VM_01

Creating an Ethernet Port Profile

Ethernet port profiles define a template that can be applied on physical Ethernet (uplink) ports on Hyper-V hosts. Unlike Virtual Ethernet profiles which are published to SCVMM, Ethernet port profiles are not published to SCVMM. Instead, Ethernet port profiles are imported by the uplink-network that is defined on the Cisco Nexus 1000V VSM.

Note

The auto-generated profile will have all the contents derived from the uplink network and it should not be modified.

Complete the following steps to configure an Ethernet port profile:

Before You Begin

- Log in to the CLI in EXEC mode.

- You know whether the ports need to be initialized with system settings.

- You have identified the characteristics needed for this port profile.

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# port-profile type ethernet name

3.    (Optional) switch(config-port-prof)# channel-group auto mode on [mac-pinning |sub-group ]

4.    switch(config-port-prof)# no shutdown

5.    switch(config-port-prof)# state enabled

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# port-profile type ethernet name

Enters the port profile configuration mode for the named Ethernet port profile. If the port profile does not already exist, it is created using the following characteristics:

- name—Port profile name that can be up to 80 characters and must be unique for each port profile.

- type—(Optional) Specifies the port profile type can be Ethernet or vEthernet. Once configured, the type cannot be changed. The default is the vEthernet type.

Defining a port profile type as Ethernet allows the port profile to be used for physical (Ethernet) ports.

Note:
If a port profile is configured as an Ethernet type, it cannot be used to configure the virtual ports.

Step 3

switch(config-port-prof)# channel-group auto mode on [mac-pinning |sub-group ]

(Optional)
Configure the ports and channels in the port profile using a mac-pinning or sub-group mode.

Note:
This command can be used only for the Ethernet ports.

Step 4

switch(config-port-prof)# no shutdown

Enables all ports in the port profile.

Step 5

switch(config-port-prof)# state enabled

Enables the operational state of the port profile.

The following example shows how to create an Ethernet port profile named UplinkNoPortChannel. Use the show port-profile name UplinkNoPortChannel and show running-config port-profile UplinkNoPortChannel commands to view the port profile configuration.

switch# configure terminal
switch(config)# port-profile type ethernet UplinkNoPortChannel
switch(config-port-prof)# no shutdown
switch(config-port-prof)# state enabled
switch(config-port-prof)# end

switch(config)# show port-profile name UplinkNoPortChannel
port-profile UplinkNoPortChannel
type: Ethernet
description:
status: enabled
max-ports: 512
min-ports: 1
inherit:
config attributes:
no shutdown
evaluated config attributes:
no shutdown
assigned interfaces:
port-group:
system vlans: none
capability l3control: no
capability iscsi-multipath: no
capability vxlan: no
capability l3-vn-service: no
port-profile role: none
port-binding: static

switch(config)# show running-config port-profile UplinkNoPortChannel
!Command: show running-config port-profile UplinkNoPortChannel
!Time: Fri Feb 15 12:56:33 2013

version 5.2(1)SM1(5.1)
port-profile type ethernet UplinkNoPortChannel
no shutdown
guid 38b1aff5-5fc4-4086-87d5-1a19fb3fde60
max-ports 512
state enabled

switch(config)#

Creating a vEthernet Port Profile

Complete the following steps to configure a vEthernet port profile:

Before You Begin

- Log in to the CLI in EXEC mode.

- You know whether the ports need to be initialized with system settings.

- You have identified the characteristics needed for this port profile.

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# port-profile type vethernet name

3.    switch(config-port-prof)# no shutdown

4.    switch(config-port-prof)# state enabled

5.    switch(config-port-prof)# publish port-profile name

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# port-profile type vethernet name

Enters the port profile configuration mode for the named vEthernet port profile.

Step 3

switch(config-port-prof)# no shutdown

Enables all ports in the port profile.

Step 4

switch(config-port-prof)# state enabled

Enables the operational state of the port profile.

Step 5

switch(config-port-prof)# publish port-profile name

Changes the published name to the Microsoft SCVMM.

This example shows how to create a vEthernet port profile:

switch#  configure terminal
switch(config)#  port-profile type vethernet AllAccess1
switch(config-port-prof)# no shutdown
switch(config-port-prof)# state enabled
switch(config-port-prof)# publish port-profile
switch(config-port-prof)# show port-profile name AllAccess1
port-profile AllAccess1
type: Vethernet
description:
status: enabled
max-ports: 32
min-ports: 1
inherit:
config attributes:
no shutdown
evaluated config attributes:
no shutdown
assigned interfaces:
port-group: AllAccess1
system vlans: none
capability l3control: no
capability iscsi-multipath: no
capability vxlan: no
capability l3-vn-service: no
port-profile role: none
port-binding: static
switch(config-port-prof)#

switch(config)# show running-config port-profile AllAccess1
!Command: show running-config port-profile AllAccess1
!Time: Wed Feb 13 14:38:38 2013

version 5.2(1)SM1(5.1)
port-profile type vethernet AllAccess1
no shutdown
guid f7adc9ea-19c0-4e96-995c-04c6dfd85112
publish port-profile
state enabled

switch(config)#

Configuring an Uplink Network

The uplink network is a combination of an Ethernet port profile and one or more network segment pools. When applied to the physical adapter on a server, the uplink network defines the policy and the VLANs that are allowed on the physical adapter.

Note

The switchport mode trunk and switch port mode private-vlan trunk commands are not supported under the nsm network uplink command.

Note

For an uplink network mode access functionality, create an uplink network with trunk mode and allow a native VLAN to achieve the same result.

Complete the following steps to configure an uplink network:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)#nsm network uplink <name>

3.    (Optional) switch(config-uplink-net)#allow network segment pool <name>

4.    (Optional) switch(config-uplink-net)#import port-profile name

5.    (Optional) switch(config-uplink-net)#native network segment <name>

6.    switch(config-uplink-net)#system network uplink

7.    switch(config-uplink-net)#publish network uplink <name>

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)#nsm network uplink <name>

Configures the uplink network.

Step 3

switch(config-uplink-net)#allow network segment pool <name>

(Optional)
Configures the allowed network segment pools.

Note:
For more than one network segment pools, repeat the same command with more than one name for the pool.

Step 4

switch(config-uplink-net)#import port-profile name

(Optional)
Imports the Ethernet port profile that gives the policy for the uplink.

Step 5

switch(config-uplink-net)#native network segment <name>

(Optional)
Configures the network segment to be a native network segment.

Note:
The VLAN of the network segment must be defined in order to be defined as a native network segment.

Step 6

switch(config-uplink-net)#system network uplink

Enables system VLAN on the network uplinks.

Step 7

switch(config-uplink-net)#publish network uplink <name>

Publishes the uplink network to the Microsoft SCVMM. Adding the name of the network uplink, for example, the variable <name> in the command is optional. When the network uplink is published to Microsoft SCVMM, it is published as an uplink port profile.

The following example shows how to create a new uplink network named NexusUplink, how to import a port profile named UplinkNoPortChannel that gives the policy for the uplink, how to associate the uplink network to a network segment pool, and publish the uplink network. Use the show nsm network uplink name <name> command to view the network uplink configuration.

switch(config)# configure terminal
switch(config)# nsm network uplink NexusUplink
switch(config-uplink-net)# allow network segment pool IntranetSJ
switch(config-uplink-net)# import port-profile UplinkNoPortChannel
switch(config-uplink-net)# native network segment VMNetworkA
switch(config-uplink-net)# system network uplink
switch(config-uplink-net)# publish network uplink NexusUplink
switch(config-uplink-net)# exit

switch# show nsm network uplink name NexusUplink
uplink network: NexusUplink
Publish-name: NexusUplink
import port-profile: UplinkNoPortChannel
network segment pool:
IntranetSJ
System Uplink-Network: TRUE
Native network segment: VMNetworkA
port-profile config:
switchport mode private-vlan trunk promiscuous
switchport private-vlan trunk allowed vlan 100,200
switchport private-vlan trunk native vlan 101

switch# show nsm network uplink brief

--------------------------------------------------------------------------------
network uplink                Pub       Sys
--------------------------------------------------------------------------------
NexusUplink                   1         1

--------------------------------------------------------------------------------
Total          Total Pub      Total Sys
--------------------------------------------------------------------------------
1              1              1

Configuring a Network Uplink in Access Mode

You can create the network segments with VLANs that are carried by a network uplink:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# nsm logical network <name>

3.    switch(config-logical-net)# description <name>

4.    switch(config-logical-net)# exit

5.    switch(config)# nsm network segment pool <name>

6.    switch(config-net-seg-pool)# member-of logical network <name>

7.    switch(config-net-seg-pool)# exit

8.    switch(config)# nsm network segment <name>

9.    switch(config-net-seg)# switchport access vlan <number>

10.    switch(config-net-seg)# member-of network segment pool <name>

11.    switch(config-net-seg)# ip pool import template <name>

12.    switch(config-net-seg)# publish network segment <name>

13.    switch(config-net-seg)# exit

14.    switch(config)# nsm network uplink <name>

15.    switch(config-uplink-net)# allow network segment pool <name>

16.    switch(config-uplink-net)# native network segment <name>

17.    switch(config-uplink-net)# import port-profile <name>

18.    switch(config-uplink-net)# publish network uplink

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# nsm logical network <name>

Creates a logical network with a given name.

Step 3

switch(config-logical-net)# description <name>

Describes the logical network.

Step 4

switch(config-logical-net)# exit

Exits the configuration.

Step 5

switch(config)# nsm network segment pool <name>

Creates a network segment pool with a given name.

Step 6

switch(config-net-seg-pool)# member-of logical network <name>

Associates the logical network to the network segment pool.

Step 7

switch(config-net-seg-pool)# exit

Exits the configuration.

Step 8

switch(config)# nsm network segment <name>

Creates a network segment with a given name.

Step 9

switch(config-net-seg)# switchport access vlan <number>

Sets the VLAN ID for the segment. It automatically creates a VLAN if it does not exist.

Step 10

switch(config-net-seg)# member-of network segment pool <name>

Associates the network segment to the network segment pool.

Step 11

switch(config-net-seg)# ip pool import template <name>

Associates the IP pool template to the network segment.

Step 12

switch(config-net-seg)# publish network segment <name>

Publishes the network segment to the Microsoft SCVMM. Adding a name of the network segment, for example, the variable <name> in the command is optional.

Step 13

switch(config-net-seg)# exit

Exits the configuration.

Step 14

switch(config)# nsm network uplink <name>

Creates a network uplink object.

Step 15

switch(config-uplink-net)# allow network segment pool <name>

Associates the network uplink object with network segment pool that is carrying one or more segments.

Step 16

switch(config-uplink-net)# native network segment <name>

Declares a network segment to be native.

Step 17

switch(config-uplink-net)# import port-profile <name>

Inherits the profile that you created.

Step 18

switch(config-uplink-net)# publish network uplink

Publishes the network uplink to the Microsoft SCVMM.

Refer to the following example to create the network segments with VLANs that are carried by an uplink, associate each network segment to a network segment pool, create an uplink network named trunk with the required network segment pool under it, and publish the uplink network to the Microsoft SCVMM. Use the show run port-profile <name> command to view the configuration.

switch(config)#   nsm logical network IntranetSFO
switch(config-logical-net)# description network for host connectivity
switch(config-logical-net)# exit

switch(config)# nsm network segment pool IntranetSJ
switch(config-net-seg-pool)# member-of logical network IntranetSFO
switch(config-net-seg-pool)# exit

switch(config)# nsm network segment VMNetworkB
switch(config-net-seg)# switchport access vlan 100
switch(config-net-seg)# member-of network segment pool IntranetSJ
switch(config-net-seg)# ip pool import template pool10
switch(config-net-seg)# publish network segment VMNetworkB
switch(config-net-seg)# exit

switch(config-uplink-net)# nsm network uplink NexusUplink
switch(config-uplink-net)# allow network segment pool IntranetSJ
switch(config-uplink-net)# native network segment VMNetworkB
switch(config-uplink-net)# import port-profile UplinkNoPortChannel
switch(config-uplink-net)# publish network uplink
switch(config-net-seg)# end

switch#  show nsm network segment name VMNetworkB
Name: VMNetworkB
VM Network Name: VMNetworkB
VM Network GUID: 3248a6f9-30ca-4cc5-b925-ef0bf6994b75
Description:
GUID: 65a6d0de-c666-448b-a912-60cc960f11cc
Network segment pool: IntranetSJ
Vlan: 100
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: 3ea151c8-ab80-47b1-8491-88a5fb651fe7
Publish-name: VMNetworkB

switch#  show nsm network segment pool name IntranetSJ
Name: IntranetSJ
GUID: 39362fa4-7ae2-47ee-8f64-1f8ecceda867
Logical network Name: IntranetSFO
Intra Port Communication: Disabled
Publish-name: IntranetSJ

switch#  show nsm network uplink name NexusUplink
uplink network: NexusUplink
Publish-name: NexusUplink
import port-profile: UplinkNoPortChannel
network segment pool:
IntranetSJ
System Uplink-Network: TRUE
Switchport mode override: auto
Native network segment: VMNetworkB
port-profile config:
switchport mode trunk
switchport trunk allowed vlan 100
switchport trunk native vlan 100

switch#  show nsm logical network name IntranetSFO
Name: IntranetSFO
Description: Intranet network

switch(config)# show run port-profile UplinkNoPortChannel

!Command: show running-config port-profile UplinkNoPortChannel
!Time: Sun Apr 28 14:08:50 2013

version 5.2(1)SM1(5.1)
port-profile type ethernet UplinkNoPortChannel
guid d7ebe0d0-9152-4415-815d-36ec25deece6
max-ports 512

Configuring Uplink Profile in Port-Channel Mode

You can configure an uplink profile in port-channel mode:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)#nsm logical network <name>

3.    switch(config-log-net)# description <name>

4.    switch(config-log-net)#exit

5.    switch(config)#nsm network segment pool <name>

6.    switch(config-net-seg-pool)#member-of logical network <name>

7.    switch(config-net-seg-pool)#exit

8.    switch(config)#nsm network segment <name>

9.    switch(config-net-seg)#switchport access vlan <number>

10.    switch(config-net-seg)#member-of network segment pool <name>

11.    switch(config-net-seg)# publish network segment <name>

12.    switch(config-net-seg)# exit

13.    switch(config)# port-profile type ethernet <name>

14.    switch(config-port-prof)#channel-group auto mode on

15.    switch(config-port-prof)#state enabled

16.    switch(config-port-prof)#no shut

17.    switch(config-net-seg)# exit

18.    switch(config)#nsm network uplink <name>

19.    switch(config-uplink-net)# allow network segment pool <name>

20.    switch(config-uplink-net)#import port-profile <name>

21.    switch(config-uplink-net)#publish network uplink <name>

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)#nsm logical network <name>

Enters a name for the logical network.

Step 3

switch(config-log-net)# description <name>

Describes the logical network.

Step 4

switch(config-log-net)#exit

Exits the configuration.

Step 5

switch(config)#nsm network segment pool <name>

Enters a name for the network segment pool.

Step 6

switch(config-net-seg-pool)#member-of logical network <name>

Associates the logical network to the network segment pool.

Step 7

switch(config-net-seg-pool)#exit

Exits the configuration.

Step 8

switch(config)#nsm network segment <name>

Creates a network segment.

Step 9

switch(config-net-seg)#switchport access vlan <number>

Creates a network segment for access VLAN that is carried by an uplink.

Step 10

switch(config-net-seg)#member-of network segment pool <name>

Associates the network segment to the network segment pool.

Step 11

switch(config-net-seg)# publish network segment <name>

Publishes the network segment to the Microsoft SCVMM.

Step 12

switch(config-net-seg)# exit

Exits the configuration.

Step 13

switch(config)# port-profile type ethernet <name>

Enters a name for the Ethernet port profile.

Step 14

switch(config-port-prof)#channel-group auto mode on

Creates a classification profile carrying the channel-group command.

Step 15

switch(config-port-prof)#state enabled

Configure the state as enabled.

Step 16

switch(config-port-prof)#no shut

Configure no shutdown command.

Step 17

switch(config-net-seg)# exit

Exits the configuration.

Step 18

switch(config)#nsm network uplink <name>

Creates a network uplink object.

Step 19

switch(config-uplink-net)# allow network segment pool <name>

Associates the network uplink object with the network segment pool.

Step 20

switch(config-uplink-net)#import port-profile <name>

Imports the port profile.

Step 21

switch(config-uplink-net)#publish network uplink <name>

Publishes the network uplink object to the Microsoft SCVMM. The name parameter is optional and it can be used to change the name with which the uplink object is published. By default, the uplink is published with the uplink object name.

Use the following example to create a network uplink named NexusUplink in port-channel mode. Use the show nsm network uplink name <name> command to view the configuration.

switch# configure terminal
switch(config)# port-profile type ethernet UplinkNoPortChannel
switch(config-port-prof)# channel-group auto mode on
switch(config-port-prof)# state enabled
switch(config-port-prof)# no shutdown
switch(config-port-prof)# exit

switch(config)#  nsm network uplink NexusUplink
switch(config-uplink-net)# allow network segment pool IntranetSJ
switch(config-uplink-net)# import port-profile UplinkNoPortChannel
switch(config-uplink-net)# publish network uplink NexusUplink
switch(config-uplink-net)# exit

switch(config)# show nsm network uplink name NexusUplink

uplink network: NexusUplink
Publish-name: NexusUplink
import port-profile: UplinkNoPortChannel
network segment pool:
IntranetSJ
System Uplink-Network: TRUE
Native network segment:
port-profile config:
switchport mode trunk
switchport trunk allowed vlan 100
switchport trunk native vlan 100

Configuring a vEthernet Profile with Features

You can configure a vEthernet profile with features:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# port-profile type vethernet <name>

3.    switch(config-port-prof)# service-policy input <name>

4.    switch(config-port-prof)# ip port access-group <name> in

5.    switch(config-port-prof)# publish port-profile

6.    switch(config-port-prof)# state enabled

7.    switch(config-port-prof)# no shut

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# port-profile type vethernet <name>

Creates a vEthernet port profile with a given name.

Step 3

switch(config-port-prof)# service-policy input <name>

Attaches a QoS policy to the port profile.

Step 4

switch(config-port-prof)# ip port access-group <name> in

Attaches an ACL policy to the port profile.

Step 5

switch(config-port-prof)# publish port-profile

Publishes the port profile to the Microsoft SCVMM. Associates both the network segment and the profile to a vEthernet interface on the Microsoft SCVMM.

Step 6

switch(config-port-prof)# state enabled

Enables the port profile for the server administrator usage.

Step 7

switch(config-port-prof)# no shut

Configures the no shutdown command.

See the following example to configure a service policy on the vEthernet port profile named ACL_POLICY. Use the show run port-profile ACL_policy command to view the configured policy on the port profile.

switch#  config t
switch(config)#  port-profile type vethernet ACL_policy
switch(config-port-prof)# service-policy input policy1
switch(config-port-prof)# ip port access-group acl-test in
switch(config-port-prof)# publish port-profile
switch(config-port-prof)# state enabled
switch(config-port-prof)# no shut
switch(config-port-prof)# end

switch(config)# show run port-profile ACL_policy
!Command: show running-config port-profile ACL_POLICY
!Time: Sun Feb 24 20:33:56 2013

version 5.2(1)SM1(5.1)
port-profile type vethernet ACL_POLICY
service-policy input policy1
ip port access-group acl-test in
no shutdown
guid be85760a-e01d-4417-b7a7-6cf5ffb83423
publish port-profile
state enabled

For more information on configuring port profiles, see Cisco Nexus 1000V for Microsoft Hyper-V Port Profile Configuration Guide.

Configuring System VLAN

You can configure a system VLAN after completing the following steps:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)#nsm logical network <name>

3.    switch(config-logical-net)# description <name>

4.    switch(config-logical-net)#exit

5.    switch(config)#nsm network segment pool <name>

6.    switch(config-net-seg-pool)#member-of logical network <name>

7.    switch(config-net-seg-pool)#exit

8.    switch(config)#nsm network segment name

9.    switch(config-net-seg)#switchport access vlan <number>

10.    switch(config-net-seg)#allow network segment pool <name>

11.    switch(config-net-seg)#system network segment

12.    switch(config-net-seg)# publish network segment

13.    switch(config-net-seg)# exit

14.    switch(config)#nsm network uplink <name>

15.    switch(config-uplink-net)#allow network segment pool <name>

16.    switch(config-uplink-net)#system network uplink

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)#nsm logical network <name>

Enters a name for the logical network.

Step 3

switch(config-logical-net)# description <name>

Describes the logical network.

Step 4

switch(config-logical-net)#exit

Exits the configuration.

Step 5

switch(config)#nsm network segment pool <name>

Enters a name for the network segment pool.

Step 6

switch(config-net-seg-pool)#member-of logical network <name>

Associates the logical network to the network segment pool.

Step 7

switch(config-net-seg-pool)#exit

Exits the configuration.

Step 8

switch(config)#nsm network segment name

Creates a network segment.

Step 9

switch(config-net-seg)#switchport access vlan <number>

Creates a network segment with access VLAN that will be carried by an uplink.

Step 10

switch(config-net-seg)#allow network segment pool <name>

Associates the network segment to the network segment pool.

Step 11

switch(config-net-seg)#system network segment

Enables system VLANs.

Step 12

switch(config-net-seg)# publish network segment

Publishes the network segment to the Microsoft SCVMM.

Step 13

switch(config-net-seg)# exit

Exits the configuration.

Step 14

switch(config)#nsm network uplink <name>

Creates a network uplink object. System VLANs on the uplink port profile are enabled by creating an uplink network object with a network segment pool carrying the system network segments.

Step 15

switch(config-uplink-net)#allow network segment pool <name>

Associates the network uplink object with network segment pool.

Step 16

switch(config-uplink-net)#system network uplink

Enables the system VLANs on the uplink object.

See the following example to create a network segment with access VLAN that will be carried by a network uplink named Channel. Use the show nsm network uplink name <name> command to view the system VLAN configuration.

switch(config)# configure terminal
switch(config)# nsm logical network IntranetSFO
switch(config-logical-net)# description network for host connectivity
switchM(config-logical-net)# exit

switch(config)#  nsm network segment pool IntranetSJ
switch(config-net-seg-pool)# member-of logical network IntranetSFO
switch(config-net-seg-pool)# exit

switch(config)# nsm network segment VMNetworkB
switch(config-net-seg)# switchport access vlan 101
switch(config-net-seg)# network segment pool IntranetSJ
switch(config-net-seg)# system network segment
switch(config-net-seg)# publish network segment
switch(config-net-seg)# exit

switch(config)# nsm network uplink Channel
switch(config-uplink-net)# allow network segment pool IntranetSJ
switch(config-uplink-net)# publish network uplink

switch(config-uplink-net)# show nsm network uplink name Channel
uplink-network: Channel
Publish-name: Channel
import port-profile: uplink_network_default_policy
network-segment-pool:
IntranetSJ
port-profile config:
switchport mode trunk
switchport trunk allowed vlan 101

switch(config)# show run port-profile Channel
!Command: show running-config port-profile channel
!Time: Mon Feb 25 10:02:43 2013

version 5.2(1)SM1(5.1)
port-profile type ethernet channel
inherit port-profile uplink_network_default_policy
switchport mode trunk
guid 6fe46002-5a4d-4d6f-949c-12eb41ee7ae3
max-ports 512
description NSM created profile. Do not delete.
system vlan 101
state enabled

Configuring PVLAN on vEthernet and Ethernet Interfaces

You can configure a PVLAN on vEthernet and Ethernet interfaces:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)#feature private-vlan

3.    switch(config)#nsm logical network <name>

4.    switch(config-logical-net)#description <description>

5.    switch(config-logical-net)#exit

6.    switch(config)#nsm network segment pool <name>

7.    switch(config-net-seg-pool)#member-of logical network <name>

8.    switch(config-net-seg-pool)#exit

9.    switch(config)#nsm network segment <name>

10.    switch(config-net-seg)#member-of network segment pool <name>

11.    switch(config-net-seg)#switchport mode private-vlan primary

12.    switch(config-net-seg)#switchport private-vlan primary "primary vlan"

13.    switch(config-net-seg)#exit

14.    switch(config)#nsm network segment <name>

15.    switch(config-net-seg)#member-of network segment pool <name>

16.    switch(config-net-seg)#switchport mode private-vlan host [ isolated | community | promiscuous ]

17.    switch(config-net-seg)#switchport private-vlan host association "primary vlan" "secondary vlan" OR switchport private-vlan mapping "primary vlan" "list of secondary vlan"

18.    switch(config-net-seg)#publish network segment

19.    switch(config-net-seg)#exit

20.    switch(config)#nsm network uplink name

21.    switch(config-uplink-net)#allow network segment pool <name>

22.    switch(config-uplink-net)# publish network uplink

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)#feature private-vlan

Enables the PVLAN feature on the VSM.

Step 3

switch(config)#nsm logical network <name>

Enters a name for the logical network.

Step 4

switch(config-logical-net)#description <description>

Describes the logical network.

Step 5

switch(config-logical-net)#exit

Exits the configuration.

Step 6

switch(config)#nsm network segment pool <name>

Enters a name for the network segment pool.

Step 7

switch(config-net-seg-pool)#member-of logical network <name>

Associates the logical network to the network segment pool.

Step 8

switch(config-net-seg-pool)#exit

Exits the configuration.

Step 9

switch(config)#nsm network segment <name>

Creates a network segment.

Step 10

switch(config-net-seg)#member-of network segment pool <name>

Associates the network segment to the network segment pool.

Step 11

switch(config-net-seg)#switchport mode private-vlan primary

Configures the network segment to be type private-vlan primary.

Note:
Make sure that feature private vlan is enabled on the VSM.

Step 12

switch(config-net-seg)#switchport private-vlan primary "primary vlan"

Sets primary VLAN on a network segment. The primary VLAN segment is used as an anchor segment for creating the secondary VLAN segment.

Step 13

switch(config-net-seg)#exit

Exits the configuration.

Step 14

switch(config)#nsm network segment <name>

Configures a secondary VLAN.

Step 15

switch(config-net-seg)#member-of network segment pool <name>

Associates the network segment to the network segment pool which was used in step 10.

Step 16

switch(config-net-seg)#switchport mode private-vlan host [ isolated | community | promiscuous ]

Create a network segment for secondary VLAN with the port mode as private-vlan host and configure the PVLAN mapping.

Note:
The host mode can be isolated or community or promiscuous.

Step 17

switch(config-net-seg)#switchport private-vlan host association "primary vlan" "secondary vlan" OR switchport private-vlan mapping "primary vlan" "list of secondary vlan"

The host association is used for creating a private-vlan host segment in either isolated or community mode. The mapping option is used for creating the private-vlan host segment in promiscuous mode.

Step 18

switch(config-net-seg)#publish network segment

Publishes the secondary network segments to the Microsoft SCVMM. The vEthernet interfaces can be attached to these segments on the Microsoft SCVMM.

Step 19

switch(config-net-seg)#exit

Exits the configuration.

Step 20

switch(config)#nsm network uplink name

Creates a network uplink with the network segment pool that carries the primary and secondary VLAN network segments.

Step 21

switch(config-uplink-net)#allow network segment pool <name>

Associates the network uplink with the network segment pool.

Step 22

switch(config-uplink-net)# publish network uplink

Publishes the network segments and the network uplinks to the Microsoft SCVMM.

Use the following example to configure the network segments as primary and secondary PVLANs that will be carried by an uplink network named Channel. Use the show feature | inc private-vlan command to verify that the PVLAN feature is enabled. Use the show vlan private-vlan command to verify PVLAN mappings.

switch# configure terminal
switch(config)# feature private vlan
switch# show feature | inc private-vlan
private-vlan 1 enabled

switch(config)# nsm logical network IntranetSFO
switch(config-logical-net)# description network for host connectivity
switch(config-logical-net)# exit

switch(config)# nsm network segment pool IntranetSJ
switch(config-net-seg-pool)#member-of logical network IntranetSFO
switch(config-net-seg-pool)#exit

switch(config)# nsm network segment Pvlan_Primary_Segment
switch(config-net-seg)# member-of network segment pool IntranetSJ
switch(config-net-seg)# switchport mode private-vlan primary
switch(config-net-seg)# switchport private-vlan primary 100
switch(config-net-seg)# exit

switch(config)# nsm network segment VMNetworkB
switch(config-net-seg)# member-of network segment pool IntranetSJ
switch(config-net-seg)# switchport mode private-vlan host community
switch(config-net-seg)# switchport private-vlan host-association 100 200
switch(config-net-seg)# publish network segment
switch(config-net-seg)# exit

switch(config)# nsm network uplink Channel
switch(config-uplink-net)# allow network segment pool IntranetSJ
switch(config-uplink-net)# publish network uplink
switch(config-uplink-net)# exit

switch#  show vlan private-vlan
Primary Secondary Type                                             Ports
------- --------- --------------- -------------------------------------------
101                     200                     primary                                Po1, Po3, Po5, Po7, Po9, Po11
400                     402                     community                             Po1, Po3, Po5, Po7, Po9, Po11

Configuring Secondary PVLAN Mode

You can change the secondary PVLAN mode from community to isolated and vice versa:

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)#nsm network segment sec -2169

3.    switch(config-net-seg)#no switch port private host-association

4.    switch(config-net-seg)#switchport mode private-vlan host isolated

5.    switch(config-net-seg)#switchport private-vlan host-association 2167 2169

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)#nsm network segment sec -2169

Creates a network segment.

Step 3

switch(config-net-seg)#no switch port private host-association

Step 4

switch(config-net-seg)#switchport mode private-vlan host isolated

.

Step 5

switch(config-net-seg)#switchport private-vlan host-association 2167 2169

.

Here sec-2169 is orignally a community network segment as follows:
Name: sec-2169
VM Network Name: sec-2169
VM Network GUID: 188a9da2-3685-4dfd-b42e-14594256ee37
Description:
GUID: 45fbeb2c-9c51-497f-94e4-43b922bb412e
Network segment pool: hyperv
Mode: switchport mode private-vlan host community.
Vlan: 0
PVLAN Host-Association: primary {2167} secondary {2169}
System Network Segment: FALSE
ip pool template: ip-pool
ip pool template GUID: 420a9b02-d4eb-42da-ba42-9dfc699ddcff
Publish-name: sec169

Feature History for Network Segmentation Manager

This table includes only the updates for those releases that have resulted in additions or changes to the feature.

Feature Name

Release

Feature Information

Network Segmentation Manager

5.2(1)SK1(2.1)

Introduced the Network Segmentation Manager (NSM) feature.

Chapter 3. Verifying the Configuration using Show Commands

This chapter contains the following sections:

- Verifying the NSM Configuration

Verifying the NSM Configuration

Use one of the following commands to verify the configuration:

- show nsm ip pool template name <name>

- show nsm ip pool template usage network segment

- show nsm logical network name <name>

- show nsm network segment brief

- show nsm network segment filter network segment pool name <name>

- show nsm network segment filter vlan <vlan_ID>

- show nsm network segment filter pvlan host <vlan_ID>

- show nsm network segment filter pvlan primary <vlan_ID>

- show nsm network segment filter pvlan promiscuous <vlan_ID>

- show nsm network segment filter pvlan secondary <vlan_ID>

- show nsm network segment filter network segment pool <name>

- show nsm network segment name <name>

- show nsm network segment pool name <name>

- show nsm network uplink brief

- show nsm network uplink filter import Ethernet Port-Profile name

- show dynamic-port-profile

- show dynamic-port-profile <name>name

- show dynamic-port-profile inherit <name>

- show dynamic-port-profile network segment <name>

show nsm ip pool template name <name>

This show command displays an IP pool template of a given name.

switch# show nsm ip pool template name pool10
Name: pool10
Description:
IP-address-range: 30.0.0.2-30.0.0.100
Network: 30.0.0.2
Subnet mask: 255.255.255.0
Default router:
Netbios: Enabled
DHCP: Disabled
Reserved-ip-list:
Netbios-name-server-list:
DNS-server-list:
DNS-suffix-list:
switch#

show nsm ip pool template usage network segment

The following show command displays the network using an IP pool template.

switch# show nsm ip pool template usage network segment
Ip-pool: pool10
VMNetworkA
switch#

show nsm logical network name <name>

This command displays the Logical Network of a given name.

switch# show nsm logical network name <name>
Name: IntranetSFO
Description: Intranet network

show nsm network segment brief

This command displays information about mode, VLAN, publish status, and the system segment status for all the network segments.

switch# show nsm network segment brief

--------------------------------------------------------------------------------
Network segment               Mode           VLAN      Pub       Sys
--------------------------------------------------------------------------------
VMNetworkA                    access         100       1         0
VMNetworkB                    pvlan primary  101(P)    1         0
VMNetworkC                    pvlan promiscu 0(P) (S)  0         0
VMNetworkD                    pvlan promiscu 0(P) (S)  0         0

--------------------------------------------------------------------------------
Total          Total Pub      Total Sys
--------------------------------------------------------------------------------
4               2              0

show nsm network segment filter network segment pool <name>

This command displays all network segments that are part of a given network segment pool.

switch# show nsm network segment filter network segment pool IntranetSJ
Name: VMNetworkB
VM Network Name: VMNetworkB
VM Network GUID: 3248a6f9-30ca-4cc5-b925-ef0bf6994b75
Description:
GUID: 65a6d0de-c666-448b-a912-60cc960f11cc
Network segment pool: IntranetSJ
Mode: switchport mode private-vlan primary
Primary Private-VLAN: 101
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: 3ea151c8-ab80-47b1-8491-88a5fb651fe7
Publish-name: VMNetworkB

show nsm network segment filter vlan <vlan_ID>

This command displays the network segment that is using a given VLAN ID.

switch# show nsm network segment filter vlan 312
Name: VMNetworkA
VM Network Name: VMNetworkA
VM Network GUID: e5120491-9948-4147-8923-19b748c204c3
Description:
GUID: c8cef5c6-0550-489b-b55c-6f3fb162da47
Network segment pool: IntranetSJ
Vlan: 312
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: 06359032-9ff5-436e-8560-da6bdfa13abe
Publish-name: VMNetworkA
switch#

show nsm network segment filter pvlan host <vlan_ID>

This command displays all the PVLAN host network segments that are using the a given primary VLAN.

switch# show nsm network segment filter pvlan host 264
Name: VMNetworkD
VM Network Name: VMNetworkD
VM Network GUID: 3e7724f5-ab85-441d-a7e2-53f57902a8c7
Description:
GUID: 1fa0229d-70a4-4931-bd96-259a8338961c
Network segment pool: IntranetSJ
Mode: switchport mode private-vlan host community
Vlan: 0
PVLAN Host-Association: primary {264} secondary {10}
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: df25ee13-5cf7-4c26-a926-d99bf04d86e5
Publish-name: VMNetworkD
switch#

show nsm network segment filter pvlan primary <vlan_ID>

This command displays primary VLAN network segment for a given primary VLAN.

switch#  show nsm network segment filter pvlan primary 264
Name: VMNetworkC
VM Network Name: VMNetworkC
VM Network GUID: 5def43e9-1a84-4273-a235-84ebf066c971
Description:
GUID: 0037b276-cd32-46ce-9c64-eb1e8c1bc53d
Network segment pool: IntranetSJ
Mode: switchport mode private-vlan primary
Primary Private-VLAN: 264
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: 790d7b34-d23f-4000-8984-f30a9f733657
Publish-name: <unpublished>
switch#

show nsm network segment filter pvlan promiscuous <vlan_ID>

The following show command displays the promiscuous mode host segment under a given primary VLAN.

switch#  show nsm network segment filter pvlan promiscuous 403
Name: VMNetworkB
VM Network Name: sec-promisc
VM Network GUID: 4676a384-26e5-45f2-b6fe-6504e5db57cf
Description:
GUID: 849adbd9-10a3-425d-b01b-0f188ee5ac71
Network segment pool: IntranetSJ
Mode: switchport mode private-vlan promiscuous
Vlan: 0
PVLAN Mapping: primary {403} secondary {ALL}
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: 17994236-8df9-4007-8628-767d55817fd9
Publish-name: VMNetworkB
switch#

show nsm network segment filter pvlan secondary <vlan_ID>

This command displays PVLAN host network segment carrying the given secondary VLAN.

switch#  show nsm network segment filter pvlan secondary 256
Name: sec-256
VM Network Name: sec-256
VM Network GUID: f802ab37-df8f-45f1-92d0-60a7661389f1
Description:
GUID: d50c9a94-6a5a-46a6-9a9c-476ca613f0c9
Network segment pool: pvlan-nd1
Mode: switchport mode private-vlan host community
Vlan: 0
PVLAN Host-Association: primary {255} secondary {256}
System Network Segment: FALSE
ip pool template: default
ip pool template GUID: 3958c9c5-cb67-4cba-8684-6d4c545f073b
Publish-name: sec-256
switch#

show nsm network segment filter network segment pool <name>

The following show command displays a list of the network segments that are associated with a given network segment pool.

switch# show nsm network segment filter network segment pool IntranetSJ
Name: VMNetworkB
VM Network Name: VMNetworkB
VM Network GUID: 3248a6f9-30ca-4cc5-b925-ef0bf6994b75
Description:
GUID: 65a6d0de-c666-448b-a912-60cc960f11cc
Network segment pool: IntranetSJ
Mode: switchport mode private-vlan primary
Primary Private-VLAN: 101
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: 3ea151c8-ab80-47b1-8491-88a5fb651fe7
Publish-name: VMNetworkB

Name: VMNetworkC
VM Network Name: VMNetworkC
VM Network GUID: 70afb65b-3bdf-406d-810c-eebdb9c887f8
Description:
GUID: 4a1a2711-c0ad-4bd0-9e9b-93d3a012e9ca
Network segment pool: IntranetSJ
Mode: switchport mode private-vlan promiscuous
Vlan: 100
System Network Segment: FALSE
ip pool template:
ip pool template GUID:
Publish-name: <unpublished>

Name: VMNetworkA
VM Network Name: VMNetworkA
VM Network GUID: 4f9e637c-cc31-47cc-ad6c-684bb3e381f4
Description:
GUID: 354c98a7-8ed1-4675-bdc5-402ad865807d
Network segment pool: IntranetSJ
Mode: switchport mode private-vlan promiscuous
Vlan: 100
System Network Segment: FALSE
ip pool template:
ip pool template GUID:
Publish-name: <unpublished>
switch#

show nsm network segment name <name>

The following show command displays the details of the network segment.

switch# show nsm network segment name VMNetworkA
Name: VMNetworkA
VM Network Name: VMNetworkA
VM Network GUID: 584d510b-0eba-485d-9262-a78c0a1fcfe3
Description:
GUID: 68f827e8-247d-4f3d-bebf-73d14d0a613a
Network segment pool: IntranetSFO
Vlan: 100
System Network Segment: FALSE
ip pool template: pool10
ip pool template GUID: fb05d8b0-724d-478b-a550-bf75f0a646ad
Publish-name: VMNetworkA
switch#

show nsm network segment pool name <name>

The following show command displays which network segments are used by a given network segment pool.

switch#  show nsm network segment pool name <name>
WORD  Name of the network segment pool (Max Size 64)
switch# show nsm network segment pool name IntranetSJ
Name: IntranetSJ
GUID: 39362fa4-7ae2-47ee-8f64-1f8ecceda867
Logical network Name: IntranetSFO
Intra Port Communication: Disabled
Primary Private-VLAN: 101
Publish-name: IntranetSJ
switch#

show nsm network uplink brief

The following show command displays brief information about the network uplink.

switch# show nsm network uplink brief

--------------------------------------------------------------------------------
network uplink                Pub       Sys
--------------------------------------------------------------------------------
NexusUplink                   1         1

--------------------------------------------------------------------------------
Total          Total Pub      Total Sys
--------------------------------------------------------------------------------
1              1              1
switch#

show nsm network uplink filter import <name>

The following show command displays the list of the network uplinks that are filtered based on the Ethernet policy port profile.

switch# show nsm network uplink filter import UplinkNoPortChannel
uplink network: NexusUplink
Publish-name: NexusUplink
import port-profile: UplinkNoPortChannel
network segment pool:
IntranetSJ
System Uplink-Network: TRUE
Switchport mode override:auto
Native network segment: VMNetworkB
port-profile config:
switchport mode private-vlan trunk promiscuous
switchport private-vlan trunk allowed vlan 100,200
switchport private-vlan trunk native vlan 101
switch#

show nsm network uplink filter network segment pool <name>

The following show command displays the list of the network uplinks that are filtered based on the network segment pools used.

switch# show nsm network uplink filter network segment pool IntranetSJ
uplink network: NexusUplink
Publish-name: NexusUplink
import port-profile: UplinkNoPortChannel
network segment pool:
IntranetSJ
System Uplink-Network: TRUE
Switchport mode override:auto
Native network segment: VMNetworkB
port-profile config:
switchport mode private-vlan trunk promiscuous
switchport private-vlan trunk allowed vlan 100,200
switchport private-vlan trunk native vlan 101
switch#

show dynamic-port-profile

The following show command displays a list of all the dynamically created profiles.

switch#  show dynamic-port-profile
dynamic-port-profile: dynpp_0f025c08-0e30-4c06-89ae-69b39d418121_90894e82-fac6-4
54d-8405-e62ddebd9a1b
inherit port-profile: veth-policy
network segment: VMNetworkD
switch#

show dynamic-port-profile name <name>

The following show command displays a specific dynamic port profile.

switch#   show dynamic-port-profile name veth-policy
dynpp_ebdcbd8e-96ab-4f9a-8975-c71283d0adc7_0cf1a4ea-a6e0-4cdf-b4ec-fcfa95ced562
dynamic-port-profile: dynpp_ebdcbd8e96ab-4f9a-8975-c71283d0adc7_0cf1a4ea-a6e0-4cdf-b4ec-fcfa95ced562
inherit port-profile: default
network-segment: VMNetworkD
switch#

show dynamic-port-profile inherit <name>

The following show command displays the list of dynamic port profile inheriting a specific vEthernet policy profile.

switch# show dynamic-port-profile inherit default_policy
dynamic-port-profile: dynpp_ebdcbd8e-96ab-4f9a-8975-c71283d0adc7_0cf1a4ea-a6e0-4cdf-b4ec-fcfa95ced562
inherit port-profile: default
network-segment: VMNetworkA
dynamic-port-profile: dynpp_ebdcbd8e-96ab-4f9a-8975-c71283d0adc7_1cb25b88-4a94-4dd6-9660-ee1ba12c60d8
inherit port-profile: default
network-segment: VMNetworkB
dynamic-port-profile: dynpp_ebdcbd8e-96ab-4f9a-8975-c71283d0adc7_36c067a9-3d5c-42c0-a9cd-3ae6c6cc0f19
inherit port-profile: default
network-segment: VMNetworkC
dynamic-port-profile: dynpp_ebdcbd8e-96ab-4f9a-8975-c71283d0adc7_6c59962d-b356-4c55-b8be-d2019f6965ea
inherit port-profile: default
network-segment: VMNetworkD
switch#

show dynamic-port-profile network-segment <name>

The following show command displays the list of dynamic port profile using a given network segment.

switch# show dynamic-port-profile network segment ?
WORD  Name of the network-segment (Max Size 64)

switch# show dynamic-port-profile network segment B_vlan_342
dynamic-port-profile: dynpp_ebdcbd8e-96ab-4f9a-8975-c71283d0adc7_1cb25b88-4a94-4dd6-9660-ee1ba12c60d8
inherit port-profile: default
network-segment: VMNetworkC
switch#

Preface

This preface contains the following sections:

- Audience

- Document Conventions

- Related Documentation for Cisco Nexus 1000V for KVM Software

- Related Documentation for Cisco Nexus 1000V for Microsoft Hyper-V Software

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

Audience

This publication is for network administrators who configure and maintain Cisco Nexus devices.

Document Conventions

Command descriptions use the following conventions:

Convention

Description

bold

Bold text indicates the commands and keywords that you enter literally as shown.

Italic

Italic text indicates arguments for which the user supplies the values.

[x]

Square brackets enclose an optional element (keyword or argument).

[x | y]

Square brackets enclosing keywords or arguments separated by a vertical bar indicate an optional choice.

{x | y}

Braces enclosing keywords or arguments separated by a vertical bar indicate a required choice.

[x {y | z}]

Nested set of square brackets or braces indicate optional or required choices within optional or required elements. Braces and a vertical bar within square brackets indicate a required choice within an optional element.

variable

Indicates a variable for which you supply values, in context where italics cannot be used.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

Examples use the following conventions:

Convention

Description

screen font

Terminal sessions and information the switch displays are in screen font.

boldface screen font

Information you must enter is in boldface screen font.

italic screen font

Arguments for which you supply values are in italic screen font.

< >

Nonprinting characters, such as passwords, are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

This document uses the following conventions:

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.

Caution

Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Related Documentation for Cisco Nexus 1000V for KVM Software

This section lists the documents used with the Cisco Nexus 1000V for KVM software:

General Information

Cisco Nexus 1000V for KVM Release Notes

Install and Upgrade

Cisco Nexus 1000V for KVM Software Installation Guide

Configuration Guides

Cisco Nexus 1000V for KVM High-Availability Configuration Guide

Cisco Nexus 1000V for KVM Interface Configuration Guide

Cisco Nexus 1000V for KVM Layer 2 Configuration Guide

Cisco Nexus 1000V for KVM License Configuration Guide

Cisco Nexus 1000V for KVM Virtual Network Configuration Guide

Cisco Nexus 1000V for KVM Port Profile Configuration Guide

Cisco Nexus 1000V for KVM REST API Configuration Guide

Cisco Nexus 1000V for KVM Security Configuration Guide

Cisco Nexus 1000V for KVM System Management Configuration Guide

Cisco Nexus 1000V for KVM Verified Scalability Guide

Cisco Nexus 1000V for KVM VXLAN Configuration Guide

Reference Guides

Cisco Nexus 1000V for KVM Command Reference

Cisco Nexus 1000V for KVM OpenStack REST API Reference

Troubleshooting and Alerts

Cisco Nexus 1000V for KVM Troubleshooting Guide

Related Documentation for Cisco Nexus 1000V for Microsoft Hyper-V Software

This section lists the documents used with the Cisco Nexus 1000V for Microsoft Hyper-V software:

General Information

Cisco Nexus 1000V for Microsoft Hyper-V Release Notes

Install and Upgrade

Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide

Configuration Guides

Cisco Nexus 1000V for Microsoft Hyper-V High Availability and Redundancy Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Interface Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Layer 2 Switching Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V License Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Network Segmentation Manager Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Port Profile Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Quality of Service Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Security Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V System Management Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Verified Scalability Guide

Reference Guides

Cisco Nexus 1000V for Microsoft Hyper-V Command Reference

Troubleshooting and Alerts

Cisco Nexus 1000V for Microsoft Hyper-V Troubleshooting Guide

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to:

We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation, at: Click Here .

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.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)