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.
vPath and vServices has the following configuration guidelines and limitations:
This section includes the following topics:
Before begining this procedure, you must know or do the following:
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 }
Before beginning this procedure, you must know or do the following:
2. port-profile port-profile-name
6. vservice node node name profile [ security-profile-name ]
8. (Optional) copy running-config startup-config
This topic includes the following topics:
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:
The Transmission Control Protocol (TCP) state checks performs three checks on TCP traffic that is routed through the Cisco VSG:
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. By default, TCP state checks functionality is disabled, use the tcp state-checks command to enable or disable TCP state checks.
Before beginning this procedure, you must know or do the following:
To display information related to a Cisco VSN, perform one of the following tasks on the switch CLI:
This example shows how to see the vsn connections:
module(usec) : 9(698) 11(701) 12(826)
module(usec) : 9(461) 11(573) 12(714)
module(usec) : 9(447) 11(569) 12(598)
module(usec) : 9(334) 11(702) 12(559)
module(usec) : 9(387) 11(558) 12(597)
This example shows how VSN ping options are dispalyed for all sources modules:
module(usec) : 9(508)
module(failed) : 10(VSN ARP not resolved) 11(VSN ARP not resolved)
12(VSN ARP not resolved)
module(usec) : 9(974) 11(987) 12(1007)
module(failed) : 10(VSN ARP not resolved)
module(usec) : 9(277) 10(436) 11(270) 12(399
)
module(usec) : 9(376) 10(606) 11(468) 12(622)
module(usec) : 9(272) 10(389) 11(318) 12(357)
module(usec) : 9(428) 10(632) 11(586) 12(594)
module(usec) : 9(284) 10(426) 11(331) 12(387)
module(usec) : 9(414) 10(663) 11(644) 12(698)
module(usec) : 9(278) 10(479) 11(334) 12(469)
module(usec) : 9(397) 10(613) 11(560) 12(593)