The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure the virtual service nodes and virtual network services for vPath.
This chapter includes the following sections:
•Configuring Virtual Service Nodes
•vService Specific Configurations
•Verifying the Cisco VSN Configuration
vPath and vServices has the following configuration guidelines and limitations:
•If the jumbo frames are enabled in the network, make sure that the MTU of the client and server VMs are reduced by the vPath encapsulation size.
•When the VEM communicates with the Cisco VSN in the Layer 3 mode, an additional header with 82 bytes is added to the original packet. The VEM does not support fragmentation in Layer 3 mode and the ports/network- elements that carry the vPath encapsulated packets must be configured so that the vPath overhead is accommodated.
This section includes the following topics:
•Configuring the vService Node
•Associating a Port Profile to a Virtual Service Node
Before begining this procedure, you must know or do the following:
•Setup the vService node.
•You have the Virtual Service Node (VSN) software installed and the basic installation completed.
•Default license is installed.
1. configure
2. vservice node node_name type {vsg }
3. {ip address ip_addr | no ip address}
4. {adjacency { l3 | no adjacency}
5. {{failmode {close | open} | no failmode}
DETAILED STEPS
Before beginning this procedure, you must know or do the following:
•You have the Cisco VSN software installed and the basic installation completed.
•Default license is installed.
•You have completed creating the Cisco VSG port profiles for the service and high-availability (HA) interface. See the Cisco Virtual Security Gateway for Microsoft Hyper-V Configuration Guide, Release 5.2(1)VSG1(4.1).
•You have defined the vservice node that will be added to the port profile.
•You are logged in to the switch CLI in EXEC mode.
1. configure
2. port-profile port-profile-name
3. org org-name
4. vservice node node name profile [security-profile-name]
5. (Optional) copy running-config startup-config
6. exit
DETAILED STEPS
This topic includes the following topics:
•Configuring Virtual Network Adapter for the Layer 3 Mode VSN Encapsulation
•Configuring TCP State-Checks for All Cisco VSGs in the vPath
You can configure virtual network adapters for a Cisco VSN in the Layer 3 mode encapsulation.
Before beginning this procedure, you must know or do the following:
•Identify a VLAN to be used for transporting the Cisco VSN in the Layer 3 mode-encapsulated traffic. Ensure that the VLAN is configured on the uplink port profile for all VEMs on which the Cisco VSN in Layer 3 mode can be configured.
1. port-profile type vethernet vsm_gs_l3vns
2. capability l3-vservice
3. no shutdown
4. state enabled
5. publish port-profile
The Transmission Control Protocol (TCP) state checks performs three checks on TCP traffic that is routed through the Cisco VSG:
•invalid-ack—When the ACK (acknowledge) number of a received TCP packet is greater than the sequence number of the TCP packet to be sent next, it is an invalid ACK.
•seq-past-window—The sequence number of a received TCP packet is greater than the right edge of the TCP receiving window.
•window-variation—The window size mechanism allows TCP to advertise a large window and to subsequently advertise a much smaller window without accepting a lot of data. From the TCP specification, it is recommended not to make the window size smaller.
When the state check is turned on, the data packets are dropped by the Cisco VSG if they meet either of the three TCP traffic check criteria.
Before beginning this procedure, you must know or do the following:
•You have the Cisco VSG software installed and the basic installation completed. For details, see the Cisco Virtual Security Gateway, Release 5.2(1)VSG1(4] and Cisco Virtual Network Management Center, Release 2.1 Installation Guide.
•Default license must be installed.
•You have completed creating the Cisco VSG port profiles for the service and HA interface.
•You are logged in to the switch CLI in EXEC mode.
1. configure
2. vservice global type vsg
3. [no] tcp state-checks
4. exit
DETAILED STEPS
Licenses are requied for some of the virtual services such as VSG. See Licensing for more information.
You can use the following procedures in this section to transfer licenses between VEMs and transfer license from a VEM to the VSM license pool:
•Transferring Licenses Between VEMs
•Transferring Licenses to the License Pool
Use the following procedure to transfer licenses from one VEM to another. For example, you might transfer licenses between VEMs after moving a VM from one host to another.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•You know the VEM that you want to transfer licenses from and the number of licenses it has.
•You know the VEM that you are transferring licenses to and the number of licenses required.
•You know the number of CPUs installed on the destination VEM.
•Licenses cannot be transferred to a VEM unless there are enough licenses in the pool to cover all of its CPUs.
•Licenses cannot be transferred to a VEM that does not have a VSN service configured.
•When licenses are successfully transferred from one VEM to another, the virtual machines on the source VEM can no longer use Cisco VSG services and the virtual machines on the destination VEM can now use Cisco VSG services.
1. vservice license type vsg transfer src-module mod_no dst-module mod_no
2. show license usage package_name
This example shows how to transfer a license from VEM 3 to VEM 5 and verify the transfer in the license usage:
n1000v# vservice license type vsg src-module 3 dst_module 5
n1000v(config)#
n1000v# show license usage NEXUS_VSG_MSFT_SERVICES_PKG
--------------------------------------
Feature Usage Info
--------------------------------------
Installed Licenses : 10
Eval Licenses : 0
Max Overdraft Licenses : 16
Installed Licenses in Use : 4
Overdraft Licenses in Use : 0
Eval Licenses in Use : 0
Licenses Available : 22
--------------------------------------
Application
--------------------------------------
VEM 4 - Socket 1
VEM 4 - Socket 2
VEM 5 - Socket 1
VEM 5 - Socket 2
--------------------------------------
Use the following procedure to transfer licenses from a VEM to the VSM license pool. For example, you might remove a license from a VEM and transfer it to the VSM license pool.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•When you transfer its licenses to the VSM license pool, all VMs on the VEM can no longer use the Cisco VSN service.
1. vservice license type vsg transfer src-module mod_no license_pool
2. show license usage package_name
This example shows how to display the licenses in use on each VEM. Notice that the licenses on VEM 3 are no longer in use.
vservice license type vsg transfer src-module 5 license-pool
n1000v# show license usage NEXUS_VSG_MSFT_SERVICES_PKG
--------------------------------------
Feature Usage Info
--------------------------------------
Installed Licenses : 10
Eval Licenses : 0
Max Overdraft Licenses : 16
Installed Licenses in Use : 2
Overdraft Licenses in Use : 0
Eval Licenses in Use : 0
Licenses Available : 24
--------------------------------------
Application
--------------------------------------
VEM 4 - Socket 1
VEM 4 - Socket 2
--------------------------------------
Note You can use the following command to transfer a license from a service pool to a VEM machine:
vservice license type vsg transfer license-pool dst-module mode_no
To display information related to a Cisco VSN, perform one of the following tasks on the switch CLI:
•vPath Ping Command for the Layer 3 Mode
Note The vPath ping command for the Layer 3 mode is not supported on Cisco vWAAS.
This example shows how to see the vsn connections:
vsm# ping vsn ip 10.1.1.40 src-module vpath-all
ping vsn 10.1.1.40 vlan 0 from module 9 11 12, seq=0 timeout=1-sec
module(usec) : 9(698) 11(701) 12(826)
ping vsn 10.1.1.40 vlan 0 from module 9 11 12, seq=1 timeout=1-sec
module(usec) : 9(461) 11(573) 12(714)
ping vsn 10.1.1.40 vlan 0 from module 9 11 12, seq=2 timeout=1-sec
module(usec) : 9(447) 11(569) 12(598)
ping vsn 10.1.1.40 vlan 0 from module 9 11 12, seq=3 timeout=1-sec
module(usec) : 9(334) 11(702) 12(559)
ping vsn 10.1.1.40 vlan 0 from module 9 11 12, seq=4 timeout=1-sec
module(usec) : 9(387) 11(558) 12(597)
vsm#
This example shows how VSN ping options are dispalyed for all sources modules:
vsm# ping vsn all src-module all
ping vsn 10.1.1.44 vlan 0 from module 9 10 11 12, seq=0 timeout=1-sec
module(usec) : 9(508)
module(failed) : 10(VSN ARP not resolved) 11(VSN ARP not resolved)
12(VSN ARP not resolved)
ping vsn 10.1.1.40 vlan 0 from module 9 10 11 12, seq=0 timeout=1-sec
module(usec) : 9(974) 11(987) 12(1007)
module(failed) : 10(VSN ARP not resolved)
ping vsn 10.1.1.44 vlan 0 from module 9 10 11 12, seq=1 timeout=1-sec
module(usec) : 9(277) 10(436) 11(270) 12(399
)
ping vsn 10.1.1.40 vlan 0 from module 9 10 11 12, seq=1 timeout=1-sec
module(usec) : 9(376) 10(606) 11(468) 12(622)
ping vsn 10.1.1.44 vlan 0 from module 9 10 11 12, seq=2 timeout=1-sec
module(usec) : 9(272) 10(389) 11(318) 12(357)
ping vsn 10.1.1.40 vlan 0 from module 9 10 11 12, seq=2 timeout=1-sec
module(usec) : 9(428) 10(632) 11(586) 12(594)
ping vsn 10.1.1.44 vlan 0 from module 9 10 11 12, seq=3 timeout=1-sec
module(usec) : 9(284) 10(426) 11(331) 12(387)
ping vsn 10.1.1.40 vlan 0 from module 9 10 11 12, seq=3 timeout=1-sec
module(usec) : 9(414) 10(663) 11(644) 12(698)
ping vsn 10.1.1.44 vlan 0 from module 9 10 11 12, seq=4 timeout=1-sec
module(usec) : 9(278) 10(479) 11(334) 12(469)
ping vsn 10.1.1.40 vlan 0 from module 9 10 11 12, seq=4 timeout=1-sec
module(usec) : 9(397) 10(613) 11(560) 12(593)
vsm#