Note
This command and its syntax is common to both the User Executable and Privilege Executable configuration modes.virtual-machine [assign-usb-ports|console|export|install|restart|set|start|stop|uninstall]
virtual-machine assign-usb-ports team-vowlan {on <DEVICE-NAME>}
virtual-machine export <VM-NAME> [<FILE>|<URL>] {on <DEVICE-NAME>}
virtual-machine install [<VM-NAME>|team-urc|team-rls|team-vowlan]
virtual-machine restart [<VM-NAME>|hard|team-urc|team-rls|team-vowlan]
virtual-machine set [autostart|memory|vcpus|vif-count|vif-mac|vif-to-vmif|vnc]
virtual-machine set [autostart [ignore|start]|memory <512-8192>|vcpus <1-4>|vif-count <0-2>| vif-mac <VIF-INDEX> <MAC-INDEX>|vif-to-vmif <VIF-INDEX> <VMIF-INDEX>|vnc [disable|enable]] [<VM-NAME>|team-urc|team-rls|team-vowlan] {on <DEVICE-NAME>}
The following virtual-machine commands are supported only on the VX9000 platform:
virtual-machine volume-group [add-drive|replace-drive|resize-drive|resize-volume-group]
virtual-machine volume-group [add-drive|replace-drive] <BLOCK-DEVICE-LABEL>
virtual-machine volume-group replace-drive <BLOCK-DEVICE-LABLE> <NEW-BLOCK-DEVICE-LABEL>
virtual-machine volume-group resize-volume-group <BLOCK-DEVICE-LABEL>
virtual-machine assign-usb-ports team-vowlan {on <DEVICE-NAME>}
assign-usb-ports team-vowlan |
Assigns USB ports to TEAM-VoWLAN on a specified device
Note: Use
the
no
> virtual-machine > assign-usb-ports
command to reassign the port to WiNG.Note: TEAM-RLS VM cannot be
installed when USB ports are assigned to TEAM-VoWLAN.
|
virtual-machine export <VM-NAME> [<FILE>|<URL>] {on <DEVICE-NAME>}
virtual-machine export |
Exports an existing VM image and settings. Use this command to export the VM to another device in the same domain.
Note: The VM should be in a
stop state during the export process.
Note: If the destination is a
device, the image is copied to a predefined location (VM archive).
|
virtual-machine install [<VM-NAME>|team-centro|team-rls|team-vowlan] {on <DEVICE-NAME>}
virtual-machine install |
Installs the VM. The install command internally creates a VM template, consisting of the specified parameters, and starts the installation process.
Specify the device on which to install the VM.
|
virtual-machine set [autostart [ignore|start]|memory <512-8192>|vcpus <1-4>|vif-count <0-2>| vif-mac <VIF-INDEX> <MAC-INDEX>|vif-to-vmif <VIF-INDEX> <VMIF-INDEX>|vnc [disable|enable]] [<VM-NAME>|team-urc|team-rls|team-vowlan] {on <DEVICE-NAME>}
virtual-machine set |
Configures the VM settings
Each VM has a maximum of two network interfaces
(indexed 1 and 2, referred to as VIF). By default,
each VIF is automatically assigned a MAC from the
range allocated for that device. However, you can use
the ‘set‘ keyword to specify the MAC from within the
allocated range. Each of these VIFs are mapped to a
layer 2 port in the dataplane (referred to as VMIF).
These VMIFs are standard l2 ports on the DP bridge,
supporting all VLAN and ACL commands. The WiNG
software supports up to a maximum of 8 VMIFs. By
default, a VM‘s interface is always mapped to VMIF1.
You can map a VIF to any of the 8 VMIFs. Use the
vif-to-vmif command to map a VIF to a VMIF on the DP
bridge.
WiNG provides a dataplane bridge for external network connectivity for VMs. VM Interfaces define which IP address is associated with each VLAN ID the service platform is connected to and enables remote service platform administration. Each custom VM can have up to a maximum of two VM interfaces. Each VM interface can be mapped to one of the twelve ports for NX9500 on the dataplane bridge. This mapping determines the destination for service platform routing. By default, VM interfaces are
internally connected to the dataplane bridge via
VMIF1. VMIF1, by default, is an untagged port
providing access to VLAN 1 to support the capability
to connect the VM interfaces to any of the VMIF
ports. This provides the flexibility to move a VM
interface onto different VLANs as well as configure
specific firewall and QoS rules.
|
virtual-machine start [<VM-NAME>|team-urc|team-rls|team-vowlan] {on <DEVICE-NAME>}
virtual-machine start | Starts the VM, based on the parameters passed. Select one of the
following options:
The following keywords are common to all of the above parameters:
|
virtual-machine stop [<VM-NAME>|team-urc|team-rls|team-vowlan] {on <DEVICE-NAME>}
virtual-machine stop hard |
Stops the VM, based on the parameters passed. Select one of the
following options:
Note: The option ‘hard‘
forces the selected VM to shutdown.
|
virtual-machine uninstall [<VM-NAME>|team-urc|team-rls|team-vowlan] {on <DEVICE-NAME>}
virtual-machine uninstall |
Uninstalls the specified VM
Note: This command releases
the VM‘s resources, such as memory, VCPUS, VNC port, disk space, and
removes the RF Domain reference from the system.
|
virtual-machine volume-group [add-drive|resize-drive] <BLOCK-DEVICE-LABEL>
virtual-machine volume-group [add-drive|resize-drive] <BLOCK-DEVICE-LABEL>] | Enables provisioning of logical volume-groups on the
VX9000 platform. Logical volume-groups are created on
the primary storage device, allowing the database
storage to be expanded to include additional storage
drives. However, volume-groups can be provisioned only
on new VX9000 installation and cannot be added to
existing VX9000 installation.
|
virtual-machine volume-group replace-drive <BLOCK-DEVICE-LABEL> <NEW-BLOCK-DEVICE-LABEL>
virtual-machine volume-group replace-drive <BLOCK-DEVICE-LABEL> <NEW-BLOCK-DEVICE-LABEL>] | Enables provisioning of VMs as logical volume-groups
on the VX9000 platform. Logical volume-group VMs are
created on the primary storage device, allowing the
database storage to be expanded to include additional
storage drives.
|
virtual-machine volume-group resize-volume-group <BLOCK-DEVICE-LABEL>
virtual-machine volume-group resize-volume-group <BLOCK-DEVICE-LABEL> | Enables provisioning of VMs as logical volume-groups
on the VX9000 platform. Logical volume-group VMs are
created on the primary storage device, allowing the
database storage to be expanded to include additional
storage drives
|
The following examples show the VM installation process:
Insatllation media: USB
<DEVICE>#virtual-machine install <VM-NAME> type iso disk-size 8 install-media usb1://vms/win7.iso autostart start memory 512 vcpus 3 vif-count 2 vnc enable
Installation media: pre-installed disk image
<DEVICE>#virtual-machine install <VM-NAME> type disk install-media flash:/vms/win7_disk.img autostart start memory 512 vcpus 3 vif-count 2 vnc-enable on <DEVICE-NAME>
In the preceding example, the command is executed on the device identified by the <DEVICE-NAME> keyword. In such a scenario, the disk-size is ignored if specified. The VM has the install media as first boot device.
Installation media: VM archive
<DEVICE>#virtual-machine install type vm-archive install-media flash:/vms/<VM-NAME> vcpus 3
In the preceding example, the default configuration attached with the VM archive overrides any parameters specified.
Exporting an installed VM:
<DEVICE>#virtual-machine export <VM-NAME> <URL> on <DEVICE-NAME>
In the preceding example, the command copies the VM archive on to the URL (VM should be in stop state).
<DEVICE>>virtual-machine install team-urc Virtual Machine install team-urc command successfully sent. <DEVICE>>
VX-DE6F97>cirtual-machine add-drive sdb
VX-DE6F97>show virtual-machine volume-group status ----------------------------------------- Logical Volume: lv1 ----------------------------------------- STATUS : available SIZE : 81.89 GiB VOLUME GROUP : vg0 PHYSICAL VOLUMES : sda10 : 73.90 GiB sdc1 : 8.00 GiB AVAILABLE DISKS : sdb : size: 8590MB ----------------------------------------- * indicates a drive that must be resized ----------------------------------------- VX-DE6F97>