- Virtual Services Container
- Prerequisites for a Virtual Services Container
- Information About Virtual Services Container
- How to Configure a Virtual Services Container
- Installing and Activating an Application in a Virtual Services Container
- Deactivating and Uninstalling an Application from a Virtual Services Container
- Upgrading an Application in a Virtual Services Container
- Collecting General Troubleshooting Information
- Verifying Virtual Services Container Applications
- Troubleshooting Virtual Services Containers
- Troubleshooting Installation of Applications in a Virtual Services Container
- Troubleshooting Activation of Applications in a Virtual Services Container
- Troubleshooting Uninstallation of Applications in a Virtual Services Container
- Troubleshooting Deactivation of Applications in a Virtual Services Container
- Configuration Examples for a Virtual Services Container
- Additional References for the Virtual Services Container
- Feature Information for Virtual Services Container
- Glossary
Virtual Services
Container
Virtual Services Container
Prerequisites for a Virtual Services Container
-
You must have a Cisco device installed with an operating system release that supports virtual services and has the needed system infrastructure required for specific applications like Cisco Plug-in for OpenFlow.
Note
A compatibility matrix is delivered with each Cisco application. Refer to this matrix for information about which operating system release supports the features and infrastructure necessary for a particular application such as Cisco Plug-in for OpenFlow.
-
You must download an open virtual application (OVA) package that is compatible with the device operating system, and downloaded from an FTP server connected to the device.
-
You must have enough memory for installation and deployment of application. Refer to the application configuration guide for specific recommendations.
Information About Virtual Services Container
Virtual Services Containers and Applications
A virtual services container is a virtualized environment on a device. It is also referred to as a virtual machine (VM), virtual service, or container.
You can install an application within a virtual services container. The application runs in the virtual services container of the operating system of a device. The application is delivered as an open virtual application (OVA), which is a tar file with a .ova extension. The OVA package is installed and enabled on a device through the device CLI.
Cisco Plug-in for OpenFlow is an example of an application that can be deployed within a virtual services container.
Some of the files that can be found in an OVA file are the following:
-
Virtual machine definition file, in libvirt XML format, with Cisco extensions.
-
Manifest file, listing the contents of a distribution. It contains the hash information for each file in the OVA package.
-
Certificate file containing the signature of a manifest file. This file is used in validating the integrity of an OVA package.
-
Version file, used to check compatibility with the virtualization infrastructure.
How to Configure a Virtual Services Container
This section includes the following required and optional tasks:
- Installing and Activating an Application in a Virtual Services Container
- Deactivating and Uninstalling an Application from a Virtual Services Container
- Upgrading an Application in a Virtual Services Container
- Collecting General Troubleshooting Information
- Verifying Virtual Services Container Applications
- Troubleshooting Virtual Services Containers
Installing and Activating an Application in a Virtual Services Container
This task copies an open virtual application (OVA) package from an FTP file location, installs the application in a virtual services container, provisions the application, and activates it.
1.
enable
2.
copy
from://source-directory-url
destination-directory-url
3.
virtual-service install name
virtual-services-name
package
file
4.
configure
terminal
5.
virtual-service
virtual-services-name
6.
activate
7.
end
8.
copy running-config startup-config
DETAILED STEPS
You can now begin using your application.
Deactivating and Uninstalling an Application from a Virtual Services Container
(Optional) Perform this task to uninstall and deactivate an application from within a virtual services container.
1.
enable
2.
configure
terminal
3.
virtual-service
virtual-services-name
4.
no activate
5.
no
virtual-service
virtual-services-name
6.
end
7.
virtual-service uninstall name
virtual-services-name
8.
copy running-config startup-config
DETAILED STEPS
Upgrading an Application in a Virtual Services Container
(Optional) Perform this task to upgrade a virtual services container application.
Note | An application upgrade may require an upgrade of the device operating system. Check the compatibility matrix of the respective application software release before upgrading it. |
1.
enable
2.
copy
from://source-directory-url
destination-directory-url
3.
configure
terminal
4.
virtual-service
virtual-services-name
5.
no activate
6.
end
7.
virtual-service upgrade name
virtual-services-name
package
file
8.
configure terminal
9.
virtual-service
virtual-services-name
10.
activate
11.
copy running-config startup-config
DETAILED STEPS
You can now begin using your application.
Collecting General Troubleshooting Information
Information collected using the commands listed below can be sent to Cisco Technical Support for troubleshooting purposes.
1.
show system sysmgr service
name vman
2.
virtual-service move name
virtual-services-name
[core | log] to
destination-url
3.
show mgmt-infra trace
settings vman_trace
4.
set trace control
vman_trace buffer-size
buffer-size
5.
set trace control
vman_trace clear [location active]
6.
set trace vman_trace
level {debug | default | err | info | warning} [location active]
DETAILED STEPS
Verifying Virtual Services Container Applications
1.
show virtual-service [global]
2.
show virtual-service
detail
[name
virtual-services-name]
3.
show virtual-service
list
4.
show virtual-service
storage
pool list
5.
show virtual-service
storage volume list
6.
show virtual-service
version
name
virtual-services-name
installed
7.
show virtual-service
tech-support
8.
show virtual-service
redundancy state
9.
show virtual-service
utilization name
virtual-services-name
10.
show virtual-service
utilization statistics CPU
DETAILED STEPS
Troubleshooting Virtual Services Containers
Troubleshooting Installation of Applications in a Virtual Services Container
Device# show virtual-service list Virtual Service List: Name Status Package Name ------------------------------------------------------------------- multiova Activated multiova-working.ova WAAS Installed ISR4451X-WAAS-5.2.0-b...
Device# show version Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie s_home.html Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software are covered under the GNU Public License. A copy of the license is available at http://www.gnu.org/licenses/gpl.html. Software BIOS: version 1.2.0 loader: version N/A kickstart: version 6.0(2)U1(1) system: version 6.0(2)U1(1) Power Sequencer Firmware: Module 1: version v4.4 BIOS compile time: 08/25/2011 kickstart image file is: bootflash:///n3000-uk9-kickstart.6.0.2.U1.0.78.bin kickstart compile time: 5/7/2013 12:00:00 [05/07/2013 19:45:30] system image file is: bootflash:///n3000-uk9.6.0.2.U1.0.78.bin system compile time: 5/7/2013 12:00:00 [05/07/2013 20:54:48] Hardware cisco Nexus 3048 Chassis ("48x1GE + 4x10G Supervisor") Intel(R) Celeron(R) CPU P450 with 3980876 kB of memory. Processor Board ID FOC16434LJ2 Device name: n3k-202-194-2 bootflash: 2007040 kB Kernel uptime is 0 day(s), 19 hour(s), 5 minute(s), 45 second(s) Last reset at 132996 usecs after Wed May 8 18:27:54 2013 Reason: Reset Requested by CLI command reload System version: 6.0(2)U1(1) Service: plugin Core Plugin, Ethernet Plugin
Device# dir bootflash: 407 May 08 21:35:52 2013 admin.rc.cli 1332 Feb 28 16:51:27 2013 bxmnt-n3k 3348 May 08 16:21:57 2013 config-sumana-08-may-13 2826744 Feb 13 15:00:49 2013 dd2 2826744 Jan 30 15:26:15 2013 dplug 10273827 Apr 10 03:09:52 2013 gdb 123496 Apr 10 03:12:46 2013 libexpat.so.0 2016 Feb 28 15:18:33 2013 linux-mount-setup-n3k 2826744 Jan 29 19:51:24 2013 lltor-dplug_md.bin 49152 Nov 29 00:52:45 2012 lost+found/ 1903 Jan 11 16:08:49 2013 mts.log 31884800 Apr 01 18:40:52 2013 n3000-uk9-kickstart.6.0.2.U1.0.36.bin 31864320 Apr 08 15:53:00 2013 n3000-uk9-kickstart.6.0.2.U1.0.44.bin 32757760 May 08 16:37:08 2013 n3000-uk9-kickstart.6.0.2.U1.0.78.bin 232540777 Apr 04 18:24:30 2013 n3000-uk9.6.0.2.U1.0.40.bin 232535711 Apr 08 15:51:49 2013 n3000-uk9.6.0.2.U1.0.44.bin 232632475 May 08 16:36:35 2013 n3000-uk9.6.0.2.U1.0.78.bin 53555200 May 08 15:37:44 2013 n3k_ofa.ova 55101440 Feb 28 20:27:39 2013 n3k_ofa.ova-gdb 52613120 Apr 04 18:26:55 2013 n3k_ofa.ova.port-channel2 58675200 Feb 01 14:47:44 2013 n3k_ofa.ova1 58675200 Feb 01 20:40:47 2013 n3k_ofa.ova31-6 2201210 Feb 27 20:30:02 2013 of_agent 56729600 May 08 16:41:33 2013 ofa-0.1.0_46-n3000-SSA-k9.ova 4096 Jan 29 17:52:15 2013 onep/ 8552 Apr 04 18:10:50 2013 saveApril3 7536 Feb 28 19:08:06 2013 saveConfigFeb28 4096 Jan 29 00:48:00 2010 vdc_2/ 4096 Jan 29 00:48:00 2010 vdc_3/ 4096 Jan 29 00:48:00 2010 vdc_4/ 4096 May 08 18:56:52 2013 virt_strg_pool_bf_vdc_1/ 4096 Apr 09 20:24:06 2013 virtual-instance/ 0 May 08 16:51:44 2013 virtual-instance-upgrade.conf 63 May 08 16:51:44 2013 virtual-instance.conf Usage for bootflash://sup-local 1558257664 bytes used 90365952 bytes free 1648623616 bytes total
Device# show virtual-service global Virtual Service Global State and Virtualization Limits: Infrastructure version : 1.5 Total virtual services installed : 1 Total virtual services activated : 1 Machine types supported : LXC Machine types disabled : KVM Maximum VCPUs per virtual service : 1 Resource virtualization limits: Name Quota Committed Available -------------------------------------------------------------- system CPU (%) 6 1 5 memory (MB) 256 256 0 bootflash (MB) 256 164 92
Troubleshooting Activation of Applications in a Virtual Services Container
Device# show virtual-service list Virtual Service List: Name Status Package Name ------------------------------------------------------------------- WAAS Activated ISR4451X-WAAS-5.2.0-b...
Device# show virtual-service Virtual Service Global State and Virtualization Limits: Infrastructure version : 1.5 Total virtual services installed : 1 Total virtual services activated : 1 Machine types supported : LXC Machine types disabled : KVM Maximum VCPUs per virtual service : 1 Resource virtualization limits: Name Quota Committed Available -------------------------------------------------------------- system CPU (%) 6 1 5 memory (MB) 256 256 0 bootflash (MB) 256 164 92
Troubleshooting Uninstallation of Applications in a Virtual Services Container
Device# show virtual-service list Virtual Service List: Name Status Package Name ------------------------------------------------------------------- WAAS Deactivated ISR4451X-WAAS-5.2.0-b...
Device# delete bootflash:virtual-instance.conf Device# reloadSolution If the problem persists, collect general troubleshooting information and contact Cisco Technical Support. For more information, see Collecting General Troubleshooting Information.
Troubleshooting Deactivation of Applications in a Virtual Services Container
Device# show virtual-service list Virtual Service List: Name Status Package Name ------------------------------------------------------------------- oneFW Activated iosxe-cx-9.0.2-hudson...
Device# delete bootflash:virtual-instance.conf Device# reloadSolution If the problem persists, generate general troubleshooting information and contact Cisco Technical support. For more information, see Collecting General Troubleshooting Information.
Configuration Examples for a Virtual Services Container
Example: Cisco Plug-in for OpenFlow Virtual Services Container Installation Configuration
Device# enable Device# copy scp://myserver.com/downloads/ofa-1.0.0-n3000-SPA-k9.ova bootflash:/ofa-1.0.0-n3000-SPA-k9.ova Device# virtual-service install name openflow_agent package bootflash:ofa-1.0.0-n3000-SPA-k9.ova Device# configure terminal Device(config)# virtual-service openflow_agent Device(config-virt-serv)# activate Device(config-virt-serv)# end Device# copy running-config startup-config
Example: Verifying Cisco Plug-in for OpenFlow Virtual Services Container Installation Configuration
Device# show virtual-service list Virtual Service List: Name Status Package Name ----------------------------------------------------------------------- openflow_agent Installed ofa-1.0.0-n3000-SPA-k9.ova
Additional References for the Virtual Services Container
Related Documents
Related Topic |
Document Title |
---|---|
Cisco commands |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation and tools. Use these resources to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for Virtual Services Container
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Feature Name |
Releases |
Feature Information |
---|---|---|
Virtual Services Container |
Cisco Plug-in for OpenFlow runs in an operating system-level virtual services container on a device. Cisco Plug-in for OpenFlow is delivered in an open virtual application (OVA). The OVA package is installed and enabled on the device through the CLI. |
Glossary
- application
-
Application installed within and hosted from a virtual ervices container on a device.
- container
-
This is another name for virtual service container.
- guest
-
Application instance running within a container.
- host
-
Operating system installed on a device.
- KVM
-
Kernel Virtual Machine. This is a virtualization infrastructure for the Linux kernel.
- LxC
-
Linux Container. Operating system virtualization technology that shares the host kernel with the guest, but provides namespace extensions to the kernel.
- logical Switch
-
An Cisco Plug-in for OpenFlow switch configured on a device and controlled by an external controller using flows defined on the controller.
- OVA
-
This is an open virtual application. Software package used to install an application and related metafiles within a container. This is a tar file with a .ova extension.
- physical Switch
-
A physical device on which Cisco Plug-in for OpenFlow application is installed and deployed.
- virtual machine
-
This is another name for virtual service container.
- virtual service
-
This is another name for virtual service container.
- virtual services container
-
This is a virtualized environment on a device on which an application can be hosted. A virtualized environment on a Cisco device is called a Cisco virtual-services container.
- VMAN
-
This is the virtualization manager. A process that manages virtual service containers and runs as a host process.