To display the status of installation of all applications on the virtual service container, use the show virtual-service list command in privileged EXEC mode.
showvirtual-servicelist
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)U1(1)
This command was introduced.
Examples
The following is sample output of the show virtual-service list command with the status of the installation is shown as Installing.
Device# show virtual-service list
System busy installing virtual-service 'WAAS'. The request may take several minutes...
Virtual Service List:
Name Status Package Name
-------------------------------------------------------------------
multiova Activated multiova-working.ova
WAAS Installing ISR4451X-WAAS-5.2.0-b...
fe-ovr2#
*Feb 13 14:08:25.276: %VIRT_SERVICE-5-INSTALL_STATE: Successfully installed virtual service WAAS
The following is sample output of the show virtual-service list command with the status of the installation is shown as Installed.
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...
Table 1 show virtual-service Field Descriptions
Command
Description
Status
Indicates the status of installation of all applications installed in the virtual services container of a device. It can be one of the following:
Initializing—Indicates that support for the application is being initialized.
Installing—Indicates that the application e is being installed.
Installed—Indicates that the application has been installed but has not been activated yet.
Activating—Indicates that virtual services package has been installed and is being activated.
Activated—Indicates that virtual services package has been installed and activated.
Activate Failed—Indicates that activation of the application has failed.
Deactivated—Indicates that the application has been deactivated.
Installs an application on the virtual services container of a device.
show virtual-service detail
To display the resources committed by applications installed in the virtual services container of a device upon activation, use the show virtual-service detail command in privileged EXEC mode.
(Optional) Specifies the name of the application for which resources committed is to be displayed. The maximum length of the name is 20. The hyphen is not a valid character.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)U1(1)
This command was introduced.
Examples
The following is sample output of the show virtual-service detail command:
Device# show virtual-service detail
Virtual Service vm_foo Detail:
Package Metadata:
Package name : foo.ova
Application name : SampleApp
Application description : Sample suite - HelloNetwork
Certificate type : Development Package
OVA path : /bootflash/foo.ova
State : Activated
Watchdog : Disabled
Disk reservation : 81 MB
Memory reservation : 510 MB
CPU reservation : 20% system CPU
VCPUs : 1
Attached devices:
Type Name Alias
---------------------------------------------
Serial/shell serial0
Disk /mnt/config_disk
Disk /
Serial/Trace serial3
Serial/Syslog serial2
Serial/aux serial1
Serial/shell serial0
The following is sample output of the show virtual-service detail name command:
Device# show virtual-service detail name openflow_agent
Virtual service openflow_agent detail
State : Installed
Package information
Name : ofa-1.0.0-n3000-SPA-k9.ova
Path : bootflash:/ofa-1.0.0-n3000-SPA-k9.ova
Application
Name : OpenflowAgent
Installed version : 0.1
Description : Cisco Openflow Agent
Signing
Key type : Cisco development key
Method : SHA-1
Licensing
Name : None
Version : None
Resource reservation
Disk : 55 MB
Memory : 0 MB
CPU reservation : 0% system CPU
Attached devices
Type Name Alias
---------------------------------------------
Serial/Trace serial3
Serial/Syslog serial2
Serial/aux
Serial/shell
Disk /mnt/core
Disk /mnt/ofa
Disk _rootfs
Table 2 show virtual-service detail Field Description
Field
Description
State
Indicates the status of the installation of an application on the virtual services container of a device. It can be one of the following:
Initializing—Indicates that support for the application is being initialized.
Installing—Indicates that the application is being installed.
Installed—Indicates that the application has been installed but has not been activated yet.
Activating—Indicates that the application has been installed and is being activated.
Activated—Indicates that the application has been installed and activated.
Activate Failed—Indicates that the application activation has failed.
Deactivated—Indicates that the application has been deactivated.
Package information
Displays information related to the application installation package with .ova extension (OVA file) used for installation.
Application
Displays information related to the installed application.
Signing
Displays information related to the method used to sign the OVA file.
SHA-1—Cisco signed package
Licensing
Displays the name and version of the license of the OVA file.
Resource reservation
Resources reserved by the application. This includes disk space, memory, and CPU usage.
Attached devices
Type, name, and alias of the device attached to the application. This is defined in the machine definitions file delivered with the OVA package.
show virtual-service storage pool list
To display an overview of storage locations (pools) used for virtual service containers, use the show virtual-service storage pool list command in privileged EXEC mode.
showvirtual-servicestoragepoollist
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)U1(1)
This command was introduced.
Examples
The following is sample output of the show virtual-service storage pool list command:
Device# show virtual-service storage pool list
Virtual-Service storage pool list
Name Pool Type Path
--------------------------------------------------------------------------
virt_strg_pool_bf_vdc_1 directory /bootflash/virt_strg_pool_bf_vdc_1
Provisions an application installed in the virtual services container of a device.
show
virtual-service utilization
To display an
overview of resources used by applications installed in the virtual services
container of a device, use the
show virtual-service
utilization command in privileged EXEC mode.
Provisions an application installed in the virtual services container of a device.
show virtual-service version
To display the version of an application installed in the virtual service container of a device, use the show virtual-service version command in privileged EXEC mode.
(Optional) Specifies the name of an application installed in the virtual services container of a device.
installed
Specifies that the installed version of OpenFlow Agent must be displayed.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)U1(1)
This command was introduced.
Examples
The following is sample output of the show virtual-service version command:
Device# show virtual-service version name openflow_agent installed
Virtual service openflow_agent installed version:
Name : OpenflowAgent
Version : 1.0
Installs an application on the virtual services container of a device.
show virtual-service version installed
To display the version of OpenFlow Agent application installed on the virtual services container of device, use the show virtual-service version installed command in privileged EXEC mode.
showvirtual-serviceversioninstalled
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)U1(1)
This command was introduced.
Examples
The following is sample output of the show virtual-service version installed command:
Device# show virtual-service version installed
Virtual service openflow_agent installed version:
Name : OpenflowAgent
Version : 1.0
Provisions an application installed in the virtual services container of a device.
show virtual-service
To display an overview of resources used by virtual service containers, use the show virtual-service command in privileged EXEC mode.
showvirtual-service
[ detail
[ namevirtual-service-name ] | list | global | storagepoollist | version
[ namevirtual-service-name ]
installed | utilization
{ name virtual-service-name | statisticsCPU } ]
Syntax Description
detail
(Optional) Displays detailed information of all or a specific virtual service container.
namevirtual-service-name
(Optional) Specifies the name of the virtual service. The length of the name is 20 characters. Hyphen is not a valid character.
list
(Optional) Displays a list of all virtual services.
global
(Optional) Displays information related to all virtual services containers.
storage pool list
(Optional) Displays location of pools where virtual services are stored.
version namevirtual-service-nameinstalled
(Optional) Displays version information of the specified virtual services container.
versioninstalled
(Optional) Displays version information of all virtual services container.
utilizationnamevirtual-service-name
(Optional) Displays resource utilization of a virtual services container.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
Cisco Nexus 3000 Series NX-OS Release 6.0(2)U1(1)
This command was introduced.
Examples
The following is sample output of the show virtual-service command:
Device# show virtual-service
Virtual Service Global State and Virtualization Limits:
Infrastructure version : 1.2
Total virtual services installed : 4
Total virtual services activated : 1
Maximum memory for virtualization : 1000 MB
Maximum HDD storage for virtualization : 0 MB
Maximum bootflash storage for virtualization : 600 MB
Maximum system CPU : 80%
Maximum VCPUs per virtual service : 1
Committed memory : 510 MB
Committed disk storage : 81 MB
Committed system CPU : 20%
Available memory : 490 MB
Available disk storage : 519 MB
Available system CPU : 60%
Machine types supported : LXC
Device# show virtual-service global
Virtual Service Global State and Virtualization Limits:
Infrastructure version : 1.3
Total virtual services installed : 1
Total virtual services activated : 1
Maximum memory for virtualization : 768 MB
Maximum HDD storage for virtualization : 0 MB
Maximum bootflash storage for virtualization : 600 MB
Maximum system CPU : 6%
Maximum VCPUs per virtual service : 1
Committed memory : 700 MB
Committed disk storage : 285 MB
Committed system CPU : 1%
Available memory : 68 MB
Available disk storage : 211 MB
Available system CPU : 5%
Machine types supported : LXC
Machine types disabled : KVM
Examples
The following is sample output of the show virtual-service detail command:
Device# show virtual-service detail
Virtual Service vm_foo Detail:
Package Metadata:
Package name : foo.ova
Application name : SampleApp
Application description : Sample suite - HelloNetwork
Certificate type : Development Package
OVA path : /bootflash/foo.ova
State : Activated
Watchdog : Disabled
Disk reservation : 81 MB
Memory reservation : 510 MB
CPU reservation : 20% system CPU
VCPUs : 1
Attached devices:
Type Name Alias
---------------------------------------------
Serial/shell serial0
Disk /mnt/config_disk
Disk /
Serial/Trace serial3
Serial/Syslog serial2
Serial/aux serial1
Serial/shell serial0
Examples
The following is sample output of the show virtual-service list command:
Device# show virtual-service list
Virtual Service List:
Name Status Package Name
-------------------------------------------------------------------
vm_foo Activated foo.ova
Examples
The following is sample output of the show virtual-service storage pool list command:
Device# show virtual-service storage pool list
Virtual-Service storage pool list
Name Pool Type Path
--------------------------------------------------------------------------
virt_strg_pool_bf_vdc_1 directory /bootflash/virt_strg_pool_bf_vdc_1
Examples
The following is sample output of the show virtual-service version installed command:
Device# show virtual-service version installed
Virtual service openflow_agent installed version:
Name : OpenflowAgent
Version : 0.1
Examples
The following is sample output of the show virtual-service utilization command:
Provisions an application installed in the virtual services container of a device.
virtual-service
To provision an application installed in the virtual services container of a device and enter virtual services configuration mode, use the virtual-service command in global configuration mode To remove the provisioning of an application installed in the virtual services container of a device and exit virtual services configuration mode, use the no form of this command.
virtual-servicevirtual-service-name
novirtual-servicevirtual-service-name
Syntax Description
virtual-service-name
Name of the application installed on the virtual services container of a device.
Command Default
An installed application is not provisioned.
Command Modes
Global configuration (config)
Command History
Release
Modification
6.0(2)U1(1)
This command was introduced.
Usage Guidelines
You can configure only one virtual service container at a time.
Examples
Device# hardware profile openflow agent
Device# virtual-service install name openflow_agent package bootflash:/ofa-1.0.0-n3000-SPA-k9.ova
Note: Installing package 'bootflash:/ofa-1.0.0-n3000-SPA-k9.ova' for virtual service 'openflow_agent'. Once the install has finished, the VM may be activated. Use 'show virtual-service list' for progress.
Device# 2013 Mar 8 20:35:23 n3k-202-194-2 %$ VDC-1 %$ %VMAN-2-INSTALL_STATE: Successfully installed virtual service 'openflow_agent'
Device# configure terminal
Device(config)# virtual-service openflow_agent
Device(config-virt-serv)# activate
Installs an application on the virtual services container of a device.
virtual-service connect
To connect to an application installed on the virtual services container of a device, use the virtual-service connect command in privileged EXEC mode.
virtual-serviceconnectnamevirtual-service-name
{ console | aux }
Syntax Description
namevirtual-service-name
Specifies the name of the application installed on the virtual services container of a device.
console
Specifies that a connection to the application is to be made through the console port defined by the virtual services container.
Note
This does not refer to the console port of the device.
aux
Specifies that a connection to the application is to be made through the AUX port of the virtual services container.
Note
This does not refer to the auxiliary port of the device.
Command Default
No connection exists to the specified application installed on the virtual services container of a device.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)U1(1)
This command was introduced.
Usage Guidelines
You can connect to a virtual service running on a device through serial ports defined in the machine definition file in XML. You cannot connect to the virtual service container if the virtual machine definition file, does not specify that access to console or AUX port is needed.
The console and AUX ports used in the command does not refer to the console and AUX ports of the device.
The username requested here is dbg. To exit the login shell, enter Ctrl-C three times.
Examples
Device# virtual-service connect name myagent aux
Connecting to virtual-service. Exit using ^c^c^c
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
MontaVista(R) Linux(R) 6.0
MontaVista Linux CGE 6 .dev-snapshot-20130430 nx3k-1.cisco.com ttyS1
nx3k-1.cisco.com login: dbg
Last login: Thu Jun 20 12:33:35 BST 2013 on pts/1
1) ps
2) wd-disable
3) wd-enable
4) ls_core
5) exit
#?^CConnection closed by foreign host.
Connection to virtual-service terminated.
Device#
Collect log and core files of an application installed in the virtual services container of a device
virtual-service install
To install an application on the virtual services container of a device, use the virtual-service install command in privileged EXEC mode. To upgrade an installed application, use the upgrade keyword of the command.
Specifies the name of the virtual service. The length of the name is 20 characters. Hyphen is not a valid character.
packagefile-url
Specifies the complete path of the OVA package that is to be installed. This is a file with a .ova extension.
Command Default
Specified application is not installed on a virtual services container.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)U1(1)
This command was introduced.
Usage Guidelines
The OpenFlow Agent application software is packaged into a file with a .ova extension (OVA file). The package must first be copied to a location on a device using the copy scp: command before it is installed on the device.
The install keyword extracts the OVA file, validates the contents of the file, creates a virtual service instance, and validates the virtual machine definition file in XML. The command adds a line to the bootflash://virtual-instance.conf file. Copying configurations to the startup-config file of the device is not required to preserve the installation of the OVA file. You can install a different OVA file on the active and standby Route Processors (RPs).
To activate the installed virtual services container, use the activate command.
The upgrade keyword replaces the software in the virtual services container with the specified package. The command adds a line to the file. The virtual service may not be upgraded while it is activated. Use the no activate command to deactivate it.
Examples
The following example shows how the virtual-service install command is used to install a virtual services container.
Device# copy scp://10.10.1.1/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
Note: Installing package 'bootflash:/ofa-1.0.0-n3000-SPA-k9.ova' for virtual service 'openflow_agent'. Once the install has finished, the VM may be activated. Use 'show virtual-service list' for progress.
Device# 2013 Mar 8 20:35:23 n3k-202-194-2 %$ VDC-1 %$ %VMAN-2-INSTALL_STATE: Successfully installed virtual service 'openflow_agent'
Device# configure terminal
Device(config)# virtual-service openflow_agent
Device(config-virt-serv)# activate
The following examples shows how you can monitor the status of the installation of the virtual services container. The Status field indicates the status of the installation.
The following is sample output of the show virtual-service list command with status of the installation is ‘Installing’.
Device# show virtual-service list
System busy installing virtual-service 'WAAS'. The request may take several minutes...
Virtual Service List:
Name Status Package Name
-------------------------------------------------------------------
multiova Activated multiova-working.ova
WAAS Installing ISR4451X-WAAS-5.2.0-b...
Device#
*Feb 13 14:08:25.276: %VIRT_SERVICE-5-INSTALL_STATE: Successfully installed virtual service WAAS
The following is sample output of the show virtual-service list command with the status of the installation is ‘Installed’.
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...
Collect log and core files of an application installed in the virtual services container of a device
virtual-service
uninstall
To uninstall an
application from the virtual services container of a device, use the
virtual-service uninstall
command in privileged EXEC mode.
virtual-serviceuninstallnamevirtual-service-name
Syntax Description
namevirtual-service-name
Specifies
the name of the application installed in the virtual services container of a
device.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)U1(1)
This
command was introduced.
Usage Guidelines
The
uninstall
keyword removes the installed virtual service container. The virtual service
may not be uninstalled while it is configured or activated.
Before
uninstalling a virtual services container, use the
no
virtual-service command to remove the configurations of the
application and the
no activate
command to deactivate it.
Examples
Device# configure terminal
Device(config)# virtual-service openflow_plugin
Device(config-virt-serv)# no activate
Device(config-virt-serv)# end
Device# virtual-service uninstall name openflow_plugin
Collect log and core files of an application installed in the virtual services container of a device
virtual-service move
To collect log and core files of an application installed in the virtual services container of a device, use the virtual-service move command in privileged EXEC mode.