Oracle VM Manager 3 CLI

Skip to end of metadata
Go to start of metadata

Introduction

The page is captured for reference purpose. Beginning with Oracle VM Manager 3.2.1, CLI is a fully supported feature of the product. Please review the product documentation for details.

Oracle VM Manager 3 CLI provides a command line interface for the Oracle VM Manager 3. You can use the CLI to perform the same functions as the Oracle VM Manager Web Interface, such as managing all your server pools, servers and guests. The CLI commands can be scripted and run in conjunction with the Web Interface, thus bringing more flexibility to help you deploy and manage an Oracle VM environment.

Beginning with Oracle VM Manager 3.1.1 build 365, the CLI is fully integrated into Oracle VM Manager.  The CLI automatically starts and stops with the rest of Oracle VM Manager components via the /etc/init.d/ovmm script. When Oracle VM Manager starts up, it reads config/CLIConfigParams.xml which contains the ssh port (by default set to 10,000), etc. Then to access the CLI, start an ssh client to connect to port 10000 of the Oracle VM Manager server.

There is an expect script within OVMCLI/expectscripts which should give you a pretty complete inventory of all the supported commands at this point. To customize the script for your setup, go into testscript with an editor and provide a name of a server (servername), pool (poolname), and VM (vmname) at the beginning of the file. This should be a server, pool and VM that you have already configured.

Aside from reviewing the expect script please note some of the cool features:

1. Use the up and down arrows for a history of commands (currently the last 50).
2. Use tab to complete tokens.
3. Use ? to get help or the command "help"; also use ? after a token to get the rest of the possible options
based on context.
4. You can have multiple clients connected concurrently.
5. You set to configure output mode and endline characters, e.g. if your ssh client adds on a
line feed (double spacing) you can set endline characters to "CR".
6. To close down the ssh session either close the ssh client or use the exit command.

The current build of Oracle VM Manager 3 CLI is provided "as-is" and is not formally supported. It should be used for testing purpose only.

Visit http://www.oracle.com/us/technologies/virtualization/oraclevm/index.html for more information about Oracle VM.

Download and Install

Oracle VM Manager 3.0.3 or 3.1.1 can be upgraded to the latest Oracle VM Manager 3.1.1 patch update. Download Oracle VM Manger 3.1.1 patch 14227416 from My Oracle Support. Unzip the patch file on the server running Oracle VM Manager and execute the runUpgrader.sh script.

Please refer to the Oracle VM Installation and Upgrade Guide http://docs.oracle.com/cd/E27300_01/E27308/html/index.html for details.

After the patch is applied, the CLI automatically starts and stops with the rest of Oracle VM Manager via the /etc/init.d/ovmm script.

Login

You can login to the CLI via puTTY or ssh directly. You will be prompted for password, e.g., ssh --l admin --p 10000 oraclevm-manager-host

Learning the CLI

The CLI is intended to be a self-learning tool.
help, showallcustomcmds, showobjtypes, and the context sensitive ? (e.g. show ?, clone ?), along w/ tab completion, up/down arrow history help a user learn the capabilities:

  • help
  • showallcustomcmds
  • showobjtypes
  • context sensitive ? (e.g. show ?, clone ?)
  • tab completion
  • up/down arrow history help a user learn the capabilities

For example say you don't know the format of the show server command.
Type "show ?" to see what object types are supported:

Use up arrow to bring back the command (save you from typing again) and then add "server":

Finally up arrow again and give the CLI the name of the server you are interested in, e.g., "name=ovs038" Be sure to use the tab to save typing, e.g. type "na <tab>" to get "name=".

And now you have it! The question mark works for all commands in exactly the same way.

Sample Use

The following are useful configuration tasks that you can perform with the CLI. Along the way you can use list to see all the objects of a certain type and show with identifier information to see the complete details of any object.

  1. Discover a Server: discoverServer ipAddress=$masterServer port=8899 username=oracle password=oracle takeOwnership=true
  2. Create a Server Pool: create serverpool virtualIP=$vip clusterEnable=false name=$poolName description='this is pool $poolName'
  3. Add a Server to the Pool: add server name=$masterServer to serverpool name=$poolName
  4. Create Storage: create FileServer name=$fileServerName plugin='Oracle-Generic-NFS' accessHost=$nfsAddress
  5. Add an Admin Server to the Storage: add Server name=$masterServer to FileServer name=$fileServerName
  6. Refresh the Storage: refresh FileServer name=$fileServerName
  7. Refresh a File System on the Storage: refresh FileSystem name=$fileSystemName servername=$masterServer
  8. Create a Repository on the Storage: create repository name=$repoName fileSystem=$fileSystemName sharepath=$fileSystemSharePath
  9. Present the Repository to a Server: add server name=$masterServer to Repository name=$repoName
  10. Refresh the Repository: refresh Repository name=$repoName
  11. Create a Virtual Disk: create virtualDisk name=$vdiskName size=3 sparse=true shareable=true on repository name=$repoName
  12. Create a VM: create VM name=$vmName1 repository=$repoName domainType=XEN_HVM on Server name=$masterServer
  13. Map the Virtual Disk to the VM: create vmDiskMapping slot=1 storageDevice=$vdiskName name-vdisk2 on vm name=$vmName1
  14. Create a Network: create EthernetNetwork name=$myNetwork roles=VIRTUAL_MACHINE
  15. Add a port on the Server to the network: add ethernetPort name='$serverPort' to network name=$myNetwork
  16. Create a VNIC on the network: create vnic name=$myVNIC network=$myNetwork
  17. Add the VNIC to the VM: add vnic name=$myVNIC to vm name=$vmName1
  18. Import an ISO: importvirtualcdrom repository name=$repoName server=$masterServer url=$isoURL
  19. Map the ISO to the VM: create vmdiskmapping slot=2 storageDevice=$isoName name=vdisk3 on vm name=$vmName1
  20. Set up the boot order: edit vm name=$vmName1 bootOrder='CDROM,DISK'\
  21. Start the VM: start VM name=$vmName1

Using Expect

The CLI fully support use of the 3rd party free tool, Expect. Within the distribution is an expectscripts directory.  
See sample demo scripts in ovm_cli/expectscripts:

At the top of each script is environmentally sensitive data, usernames, passwords, server names, IP addresses, etc. After a few edits at the top, you can get the CLI to setup a working VM. Use these scripts as guideline as to how to set up a working via the CLI using NFS, FC or iSCSI storage. Minimally these scripts will give you the format of a bunch of commands in a useful order. Use the '?' too; it works well.

Using the CLI from the Commandline

The ovmcli.sh script (depends on Expect and eovmcli script) gives you an example of how you might have a script that allows you to execute an OVM command from the standard command line. After editing the script for your environment you can execute a command like: ./ovmcli.sh "show server name=ovs004" to give you the information about the ovs004 server.  Note that ovmcli.sh is for demo purposes only as it embeds a user name and password in the file, alternatively use eovmcli or eovmclixml which do not have embedded user credentials.

The eovmclixml script  take three command line arguments (username, password and command; e.g., eovmclixml “admin” “Welcome1” “show server name=ovs004”) and returns the results in XML format, at the shell prompt.  XML is great for back end parsing. We do cache the core connection for 15-minutes so subsequent calls with the same username and password go very quickly. Customers can then easily write their own scripts and take advantage of all the rich constructs that the shell provides:   variables, looping, conditional execution, parsing, etc. One easy way to integrate with java is to use the exec method within the Runtime class and then parse the XML output with the SAX parser (there are many XML parsers that they may like better).  The eovmcli does the same thing but “pretty prints” the results to the screen, just like when you run the CLI via a ssh connection.

Note on SSH

We are using standard ssh. Because ssh provides a secure channel to servers, there are certain precautions it takes when first installing a new service, in our case, the new OVMCLI.
>>First login attempt:

>>Optionally delete the known_hosts file:

>>Or you can also use ssh-keygen -R <host> to only remove that single offending key, not needed to delete ALL known_hosts file.


>>Select yes:

>>Subsequent logins

Alternatively, from the ssh command line, you can pass StrictHostKeyChecking option as shown below. You can also set this option in your ssh_config file

If you are logging in to the server for the 1st time, it would permanently add the RSA to the list of known hosts without prompting you.

Using SSH key-based authentication with the CLI

One of the nice features of ssh is public key-based authentication. Subsequently we added public key-based authentication for CLI with Oracle VM Manager 3.1.1 build 399.

After key-based authentication is setup, you can issue a command via “ssh admin@ovmManager command” or just login to the CLI without being prompted for a password. E.g., “ssh admin@ovmManager --p 10000 “show server” or ssh admin@ovmManager --p 10000 “edit server description=’My primary server’; show server”.

How it works

First keys are setup between a local system and the management system (ovmManager). After the key is setup, the user logins once with his password into the management system from the local system. This action establishes a channel for public key authentication. The channel is identified to the CLI Server by the client IP address and user name.

 Subsequently when the user issues a command via ““ssh admin@ovmManager command” from same local machine, the CLI will first verify if the public key is available and then detect if there is an existing channel to use. If the desired channel exists, it will use the user name and password cached in memory by channel session to login to core. Like other sessions the user name and IP address will be within the CLI audit log.  If the channel is not found, it will redirect to user/password based authentication.

 For security reasons, the channel for public key authentication will expire after a designated period of time.  The default for keeping the channel open is 1 week (10080 minutes). The user may modify the default by editing the publicKeyAuthChannelTimeout value within /u01/app/oracle/ovm-manager-3/ovm_cli/config/CLIConfigParams.xml and restarting the CLI.  Consistent with WebLogic, a value of -1 will keep the channel open indefinitely.

 The channel will be closed when the timeout expires.  Also, the channel will be closed if the user’s password changes.  In both cases the user can re-login to CLI by entering the new password and reestablish the channel.

 Note that the new key-based authentication will not impact the existing authentication mechanism using a username and password.

How to set it up

1. Generate public/private key locally on the system which you want to log into the CLI via the key-based approach. Make sure you remember the passphrase that you enter. E.g.:

You will see the two keys generated in ~/.ssh/:

2.  On the same system, execute ssh-add to add your private key to the local authentication agent.  E.g.:

3. Copy public key to Oracle VM Manager server, e.g.

4.  Login to your management server (ovmManager) with the user "root" privileges. Go to the /home/oracle/.ssh directory and append the public key "admin.pub" to the CLI authorized file: "ovmcli_authorized_keys" by the command:

5. From your local machine, login to cli by command:

 For the first time, you will be asked password.  The second time you will be asked for your passphrase.  Subsequent logins will go over the newly established channel and not require a password.

List of CLI Commands

  1. add BondPort <instance> to Network <instance>
  2. add BondPort <instance> to VlanGroup <instance>
  3. add PhysicalDisk <instance> to AccessGroup <instance>
  4. add Port <instance> to BondPort <instance>
  5. add Port <instance> to Network <instance>
  6. add Port <instance> to VlanGroup <instance>
  7. add Server <instance> to FileServer <instance>
  8. add Server <instance> to Repository <instance>
  9. add Server <instance> to SanServer <instance>
  10. add Server <instance> to ServerPool <instance>
  11. add StorageInitiator <instance> to AccessGroup <instance>
  12. add Vm <instance> to Server <instance>
  13. add Vnic <instance> to Vm <instance>
  14. create AccessGroup name=<value> description=<value>
  15. create BondPort mode=[activeBackup,linkAggregation,adaptiveLoadBalancing] ethernet1Port=<value> ethernet2Port=<value> name=<value> description=<value>
  16. create FileServer plugin=[Oracle-Generic-NFS,Sun-ZFS-SA-NFS] accessHost=<value> adminHost=<value> adminUserName=<value> adminPassword=<value> name=<value> description=<value>
  17. create Network roles=[MANAGEMENT,LIVE_MIGRATE,CLUSTER_HEARTBEAT,VIRTUAL_MACHINE,STORAGE] vlanSegment=<value> server=<value> name=<value> description=<value>
  18. create PhysicalDisk size=<value> extraInfo=<value> shareable=[true,false] thinProvision=[true,false] name=<value> description=<value>
  19. create Repository fileSystem=<value> serverPool=<value> physicalDisk=<value> sharePath=<value> name=<value> description=<value>
  20. create SanServer plugin=[Oracle-Generic-SCSI,Oracle-NetApp-Filer,Sun-ZFS-SA] storageType=[FibreChannelStorageArray,iSCSIStorageArray] accessHost=<value> accessPort=<value> accessUsername=<value> accessPassword=<value> useChap=[true,false] adminHost=<value> adminUserName=<value> adminPassword=<value> name=<value> description=<value>
  21. create ServerPool clusterEnable=[true,false] keymapName=<value> virtualIP=<value> migrateUsingSsl=[true,false] fileSystem=<value> physicalDisk=<value> name=<value> description=<value>
  22. create VirtualDisk size=<value> shareable=[true,false] sparse=[true,false] name=<value> description=<value>
  23. create VlanGroup name=<value> description=<value>
  24. create VlanSegment index=<value> name=<value> description=<value>
  25. create Vm memory=<value> memoryLimit=<value> cpuCountLimit=<value> cpuCount=<value> cpuPriority=<value> cpuUtilizationCap=<value> highAvailability=[true,false] osType=[WIN_2003,WIN_2008,WIN_7,WIN_VISTA,OTHER_WIN,OL_4,OL_5,OL_6,RHL_4,RHL_5,RHL_6,LINUX_RECOVERY,OTHER_LINUX,SOLARIS_10,SOLARIS_11,OTHER_SOLARIS,NONE] mouseType=[OS_DEFAULT,PS2_MOUSE,USB_MOUSE,USB_TABLET] domainType=[XEN_HVM,XEN_HVM_PV_DRIVERS,XEN_PVM,LDOMS_PVM,UNKNOWN] keymapName=<value> bootOrder=[PXE,DISK,CDROM] networkBootPath=<value> repository=<value> name=<value> description=<value>
  26. create VmDiskMapping slot=<value> storageDevice=<value> name=<value> description=<value>
  27. create Vnic network=<value> name=<value> description=<value>
  28. delete AccessGroup <instance>
  29. delete Assembly <instance>
  30. delete BondPort <instance>
  31. delete FileServer <instance>
  32. delete FileSystem <instance>
  33. delete ISO <instance>
  34. delete Network <instance>
  35. delete PhysicalDisk <instance>
  36. delete Repository <instance>
  37. delete SanServer <instance>
  38. delete Server <instance>
  39. delete ServerPool <instance>
  40. delete VirtualDisk <instance>
  41. delete VlanGroup <instance>
  42. delete VlanSegment <instance>
  43. delete Vm <instance>
  44. delete VmDiskMapping <instance>
  45. delete Vnic <instance>
  46. edit AccessGroup <instance> name=<value> description=<value>
  47. edit Assembly <instance> name=<value> description=<value>
  48. edit BondPort <instance> mode=[activeBackup,linkAggregation,adaptiveLoadBalancing] name=<value> description=<value>
  49. edit FileServer <instance> accessHost=<value> adminHost=<value> adminUserName=<value> adminPassword=<value> name=<value> description=<value>
  50. edit FileSystem <instance> name=<value> description=<value>
  51. edit ISO <instance> name=<value> description=<value>
  52. edit Network <instance> roles=[MANAGEMENT,LIVE_MIGRATE,CLUSTER_HEARTBEAT,VIRTUAL_MACHINE,STORAGE] vlanSegment=<value> name=<value> description=<value>
  53. edit PhysicalDisk <instance> size=<value> extraInfo=<value> shareable=[true,false] name=<value> description=<value>
  54. edit Port <instance> mtu=<value> addressType=[none,staticIp,dynamic] ipAddress=<value> netMask=<value> name=<value> description=<value>
  55. edit Repository <instance> name=<value> description=<value>
  56. edit SanServer <instance> accessHost=<value> accessPort=<value> accessUsername=<value> accessPassword=<value> useChap=[true,false] adminHost=<value> adminUserName=<value> adminPassword=<value> name=<value> description=<value>
  57. edit Server <instance> maintenanceMode=[true,false] takeOwnership=[true,false] name=<value> description=<value>
  58. edit ServerPool <instance> keymapName=<value> migrateUsingSsl=[true,false] masterServer=<value> name=<value> description=<value>
  59. edit VirtualDisk <instance> size=<value> shareable=[true,false] name=<value> description=<value>
  60. edit VlanGroup <instance> name=<value> description=<value>
  61. edit VlanInterface <instance> mtu=<value> addressType=[none,staticIp,dynamic] ipAddress=<value> netMask=<value> name=<value> description=<value>
  62. edit Vm <instance> memory=<value> memoryLimit=<value> cpuCountLimit=<value> cpuCount=<value> cpuPriority=<value> cpuUtilizationCap=<value> highAvailability=[true,false] osType=[WIN_2003,WIN_2008,WIN_7,WIN_VISTA,OTHER_WIN,OL_4,OL_5,OL_6,RHL_4,RHL_5,RHL_6,LINUX_RECOVERY,OTHER_LINUX,SOLARIS_10,SOLARIS_11,OTHER_SOLARIS,NONE] mouseType=[OS_DEFAULT,PS2_MOUSE,USB_MOUSE,USB_TABLET] domainType=[XEN_HVM,XEN_HVM_PV_DRIVERS,XEN_PVM,LDOMS_PVM,UNKNOWN] keymapName=<value> bootOrder=[PXE,DISK,CDROM] networkBootPath=<value> name=<value> description=<value>
  63. edit VmDiskMapping <instance> name=<value> description=<value>
  64. edit Vnic <instance> network=<value> name=<value> description=<value>
  65. edit VolumeGroup <instance> name=<value> description=<value>
  66. edit YumConfig <instance> baseURL=<value> gpgKeyCheck=[true,false] gpgKey=<value>
  67. list AccessGroup
  68. list Assembly
  69. list BondPort
  70. list FileServer
  71. list FileSystem
  72. list ISO
  73. list Job
  74. list Network
  75. list PhysicalDisk
  76. list Port
  77. list Repository
  78. list SanServer
  79. list Server
  80. list ServerPool
  81. list StorageInitiator
  82. list VirtualDisk
  83. list VlanGroup
  84. list VlanInterface
  85. list VlanSegment
  86. list Vm
  87. list VmDiskMapping
  88. list Vnic
  89. list VolumeGroup
  90. remove BondPort <instance> from Network <instance>
  91. remove BondPort <instance> from VlanGroup <instance>
  92. remove PhysicalDisk <instance> from AccessGroup <instance>
  93. remove Port <instance> from BondPort <instance>
  94. remove Port <instance> from Network <instance>
  95. remove Port <instance> from VlanGroup <instance>
  96. remove Server <instance> from FileServer <instance>
  97. remove Server <instance> from Repository <instance>
  98. remove Server <instance> from SanServer <instance>
  99. remove Server <instance> from ServerPool <instance>
  100. remove StorageInitiator <instance> from AccessGroup <instance>
  101. remove Vm <instance> from Server <instance>
  102. remove Vnic <instance> from Vm <instance>
  103. set EndlineChars=[CRLF,CR,LF]
  104. set OutputMode=[Verbose,Sparse,Xml]
  105. show AccessGroup name=<instance>
  106. show Assembly name=<instance>
  107. show BondPort name=<instance>
  108. show FileServer name=<instance>
  109. show FileSystem name=<instance>
  110. show ISO name=<instance>
  111. show Job id=<instance>
  112. show Network name=<instance>
  113. show PhysicalDisk name=<instance>
  114. show Port name=<instance>
  115. show Repository name=<instance>
  116. show SanServer name=<instance>
  117. show Server name=<instance>
  118. show ServerPool name=<instance>
  119. show StorageInitiator name=<instance>
  120. show VirtualDisk name=<instance>
  121. show VlanGroup name=<instance>
  122. show VlanInterface name=<instance>
  123. show VlanSegment name=<instance>
  124. show Vm name=<instance>
  125. show VmDiskMapping name=<instance>
  126. show Vnic name=<instance>
  127. show VolumeGroup name=<instance>
  128. show YumConfig name=<instance>
  129. abort Job <instance>
  130. ackEvent eventId=<value>
  131. addAvailableVnic Vm <instance>
  132. clone VirtualDisk <instance> target=<value> cloneType=[Sparse,NonSparse]
  133. clone Vm <instance> destType=[Vm,VmTemplate] destName=<value> serverPool=<value>
  134. discoverServer ipAddress=<value> port=<value> username=<value> password=<value> takeOwnership=<value>
  135. getEvents AccessGroup <instance> type=[All,Ackable] amount=<value>
  136. getEvents FileServer <instance> type=[All,Ackable] amount=<value>
  137. getEvents FileSystem <instance> type=[All,Ackable] amount=<value>
  138. getEvents PhysicalDisk <instance> type=[All,Ackable] amount=<value>
  139. getEvents Repository <instance> type=[All,Ackable] amount=<value>
  140. getEvents SanServer <instance> type=[All,Ackable] amount=<value>
  141. getEvents Server <instance> type=[All,Ackable] amount=<value>
  142. getEvents ServerPool <instance> type=[All,Ackable] amount=<value>
  143. getEvents Vm <instance> type=[All,Ackable] amount=<value>
  144. getEvents VolumeGroup <instance> type=[All,Ackable] amount=<value>
  145. getIncompatibleReasons checkType=[VM_START,VM_MIGRATE_BY_POLICY,VM_MIGRATE_BY_USER,VM_DPM_POWER_ON_MIGRATE,VM_PLACEMENT] vm=<value> server=<value>
  146. getJobsUsingRange from=<value> to=<value>
  147. getLatestNumberOfJobs amount=<value>
  148. importAssembly Repository <instance> server=<value> url=<value>
  149. importTemplate Repository <instance> server=<value> url=<value>
  150. importVirtualCdrom Repository <instance> server=<value> url=<value>
  151. importVirtualDisk Repository <instance> server=<value> url=<value>
  152. initiateYumUpgrade Server <instance>
  153. kill Server <instance>
  154. kill Vm <instance>
  155. migrate Vm <instance> destServer=<value>
  156. refresh Assembly <instance>
  157. refresh FileServer <instance>
  158. refresh FileSystem <instance> serverName=<value>
  159. refresh PhysicalDisk <instance>
  160. refresh Repository <instance>
  161. refresh SanServer <instance>
  162. refresh Server <instance>
  163. refreshStorageLayer Server <instance>
  164. restart Server <instance>
  165. restart Vm <instance>
  166. resume Vm <instance>
  167. start Server name=<instance>
  168. start Vm <instance>
  169. stop Server <instance>
  170. stop Vm <instance>
  171. suspend Vm <instance>
  172. vnicCreate segment4=<value> segment5=<value> segment6=<value> numberToGenerate=<value>
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Sep 07, 2012

    Hi, the CLI config file should be CLIConfigParams.xml , not CLIConfigParms.xml

    Otherwise thanks for this overview!

  2. Jan 11, 2013

    Hello All

    I'm trying to create an bond via cli, but I cant get it running?

    OVM> create BondPort mode=activeBackup ethernetPort1=0004fb0000200000dd291799b774ce7d ethernetPort2=0004fb0000200000346b83c374cb91a8 name=bond2 on Server name=server1
    Command: create BondPort mode=activeBackup ethernetPort1=0004fb0000200000dd291799b774ce7d ethernetPort2=0004fb0000200000346b83c374cb91a8 name=bond2 on Server name=server1
    Status: Failure
    Time: 2013-01-11 18:52:13.836
    Error Msg: java.lang.Exception: Couldn't find a EthernetPort object with the identifier of 0004fb0000200000dd291799b774ce7d.

    OVM> create BondPort mode=activeBackup ethernetPort1='Port (6)' ethernetPort2='Port (7)' name=bond2 on Server name=server1                                        Command: create BondPort mode=activeBackup ethernetPort1='Port (6)' ethernetPort2='Port (7)' name=bond2 on Server name=server1
    Status: Failure
    Time: 2013-01-11 18:53:19.640
    Error Msg: java.lang.Exception: Couldn't find a EthernetPort object with the identifier of Port (6).
    OVM> create BondPort mode=activeBackup ethernetPort1=?
                                                         <value>
    OVM> create BondPort mode=activeBackup ethernetPort1 - Invalid format (missing equals sign).

    What is the <value> for ethernetPort1 and 2

    Thanks in advance

    Steph

    1. Mar 06, 2013

      Hi Steph,

      The following worked for me:

      OVM> showversion
      3.2.1.516

      OVM> list port
      Command: list port
      Status: Success
      Time: 2013-03-06 18:29:58,570 CET
      Data:
        id:0004fb0000200000d02c438285ea18f9  name:eth0 on ovm1.ecm.netitservices.com
        id:0004fb000020000000219af5d3031f61  name:eth1 on ovm1.ecm.netitservices.com
        id:0004fb0000200000834fe4440404b833  name:eth2 on ovm1.ecm.netitservices.com
        id:0004fb000020000014b3238c82526797  name:eth3 on ovm1.ecm.netitservices.com
        id:0004fb0000200000448b8e733f762854  name:eth0 on ovm2.ecm.netitservices.com
        id:0004fb00002000006f06b40d765ece79  name:eth1 on ovm2.ecm.netitservices.com
        id:0004fb0000200000d4c01177b6eeb77d  name:eth2 on ovm2.ecm.netitservices.com
        id:0004fb00002000007ad4aaf9d3b106a2  name:eth3 on ovm2.ecm.netitservices.com

      OVM> create BondPort mode=activeBackup ethernetPort1=0004fb000020000000219af5d3031f61 ethernetport2=0004fb0000200000834fe4440404b833 name=mybond mtu=1500 addressType=none on Server name=ovm1.ecm.netitservices.com
      Command: create BondPort mode=activeBackup ethernetPort1=0004fb000020000000219af5d3031f61 ethernetport2=0004fb0000200000834fe4440404b833 name=mybond mtu=1500 addressType=none on Server name=ovm1.ecm.netitservices.com
      Status: Success
      Time: 2013-03-06 18:33:38,049 CET
      Data:
        id:0004fb0000200000f2f89f48972124d7  name:mybond

      Are you also on 3.2.1 ?

      Can you send the output of list port ?

      Regards

      Frank

  3. Mar 06, 2013

    I'm trying to find a way to map the id of a physicaldisk to it's WWN (Page83 ID, or Path in the GUI)

    When I do a show physicaldisk it does not show up:

    OVM> show physicaldisk id=0004fb00001800008c74e79d78cdda0f
    Command: show physicaldisk id=0004fb00001800008c74e79d78cdda0f
    Status: Success
    Time: 2013-03-06 18:25:11,988 CET
    Data:
      Name = OI (1)
      Id = 0004fb00001800008c74e79d78cdda0f
      Size (GiB) = 20.0
      Shareable = No
      Thin Provision = Yes
      VolumeGroup = Generic_iSCSI_Volume_Group @ 0004fb00000900009841ae9e2673580e  [Generic_iSCSI_Volume_Group]
      San Server = 0004fb00000900009841ae9e2673580e  [openindiana1]

    Or in other words: If I present 5 LUN's of 50GB each, how can I - through CLI - find out which has which "WWN" (number as it apprears under /dev/mapper on the host) ?

    Thanks for any ideas how to do that.

    Frank

  4. Jun 29, 2013

    I think you need to remove the space before 'admin.pub' in

    scp ~/.ssh/ admin.pub  oracle@ovmManager:/home/oracle/.ssh/

    i.e., this command should be

    scp ~/.ssh/admin.pub  oracle@ovmManager:/home/oracle/.ssh/

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.