ServerView Resource Orchestrator V3.2.0 Release Notes

2.3.5 Information about Incompatibility between V3.1.2 (T009379LP-05/T009378WP-06) and V3.1.2 (T009379LP-04/T009378WP-05)

2.3.5.1 Modification of the Coordination Method with VDI Management Server

Details of Modification

Modify the method for coordinating the VDI management server with Resource Orchestrator to use the VDI coordination function.

• For V3.1.2 (T009378WP-05)

  Use the following definition files:

  VDI Management Server Definition File

  Storage Location of the Definition File

  [Windows Manager]
  Installation_folder\SVROR\Manager\etc\customize_data

  Definition File Name

  vdi_management_info.rcxprop

  Definition File Format

  Describe each line of the definition file in the following format:

  Key = Value

  Definition File Items

  Specify the following items:

  Key	Value
  vdi_number.name	Specify the VDI management server name. Enter a character string beginning with an alphabetical character and containing up to 15 alphanumeric characters and hyphens ("-"). Specify the name using a unique value for each VDI management server.
  vdi_number.type	Specify the VDI management server type. When using VMware Horizon View, specify "vmwareview".
  vdi_number.ipaddr	Specify the IP address of the VDI management server name used for control from Resource Orchestrator.
  vdi_number.user	Specify the administrator user name of the VDI management server. Enter a character string containing up to 84 alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e). For details, refer to "K.1.1 VDI Coordination Function" in the "Design Guide CE".
  vdi_number.password	Specify the administrator password of the VDI management server. Enter a character string containing up to 128 alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e).
  vdi_number.vmmgr	Specify the name of the VM management software registered on the VDI management server that is used in Resource Orchestrator. When there are more than one VM management software, specify the VM management software names, separated by commas (",").
  vdi_number.connect_info	Specify the connection information of the VDI management server specified when the VDI user uses the virtual desktop. Enter a character string containing up to 1024 alphanumeric characters and symbols (ASCII characters (0x20 to 0x2b, 0x2d to 0x7e)) other than commas (","). Up to three sets of connection information can be specified. When specifying multiple sets of connection information, specify the information separated by commas (","). When deploying L-Platforms, notification of the first connection information is made using email. When using VMware Horizon View Client Specify the host name or IP address of the VDI management server used by the virtual desktop user as the connection destination.

  Note

  It is not necessary to restart the ROR manager after creating the definition files.

  Enter an item to define on each line for each VDI management server.

  When adding comments, start the line with a number sign ("#").

  Start number with 1 and increase it by 1 for each additional management server.

  When multiple lines have the same key, the line described last is valid.

  When multiple VDI management servers with the same VDI management server name are defined, the definition described last is valid.

  In VDI management server definitions, any definitions with missing items or invalid values are ignored.

  Blank spaces at the start and end of lines, and before and after "=" are ignored.

  Example

  #VDI1
  vdi1.name=horizonview1
  vdi1.type=vmwareview
  vdi1.ipaddr=192.168.2.1
  vdi1.user=viewdomain1\admin1
  vdi1.password=password1
  vdi1.vmmgr=vc1,vc2
  vdi1.connect_info=192.168.123.1, http://192.168.123.1/vmwareview/

  #VDI2
  vdi2.name=horizonview2
  vdi2.type=vmwareview
  vdi2.ipaddr=192.168.2.2
  vdi2.user= viewdomain2\admin2
  vdi2.password=password2
  vdi2.vmmgr=vc3,vc4
  vdi2.connect_info=192.168.123.2

• For V3.1.2 (T009378WP-06)

  Register a VDI management server with Resource Orchestrator as VDI management software.

  For details on how to register the VDI management software, refer to "5.15 Registering VDI Management Software" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

  
  

Corrective Action

Use the following procedure to register the VDI management server as VDI management software in Resource Orchestrator based on the information in the VDI management server definition file.

When the information has not been registered, register it quickly as until it is registered, creation, modification, and deletion of L-Platforms and L-Servers for which VDI coordination is enabled cannot be performed.

However, the registration does not affect the use of already created L-Platforms and L-Servers for which VDI coordination is enabled.

After performing the procedure, the VDI management server definition files can be deleted.

The information of the VDI management server definition file can be migrated, using the migration tool for VDI management server definition information.

For details on how to use the migration tool, refer to "How to Use the Migration Tool for VDI Management Server Definition Information".

1. Following the table below, assign the information from the VDI management server definition file to the corresponding items to enter in the registration dialog of the VDI management software.

   VDI Management Server Definition File		Registering VDI Management Software
   Item Name	Key
   VDI management server name	vdi_number.name	Specify in [VM management software name].
   VDI management server type	vdi_number.type	In step 2, select the registration dialog in the VDI management software based on the type of the VDI management server. There are no relative items to enter in the registration dialog in the VDI management software.
   IP address of the VDI management server	vdi_number.ipaddr	Specify in [IP address].
   Administrator user name of the VDI management server	vdi_number.user	Specify in [User ID].
   Administrator password of the VDI management server.	vdi_number.password	Specify in [Password].
   VM management software name	vdi_number.vmmgr	Specify in [VM management software list].
   Connection information of the VDI management server	vdi_number.connect_info	Specify in [Connection information].

   Note

   Specify the same VDI management server name as defined in the VDI management software definition file for the [VM management server name] specified when registering the VDI management software.
   When the names are not the same, the modification and deletion of already created L-Platforms and L-Servers for which VDI coordination is enabled may fail.
   If VDI management software is accidentally registered with an unmatched [Management software name], delete the VDI management software from Resource Orchestrator, and then register it using a matching [Management software name].

2. Register the VDI management software. For details, refer to "5.15 Registering VDI Management Software" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

3. When multiple VDI management servers are registered in the VDI management server definition file, repeat steps 1 and 2 as many times as there are VDI management servers.

   
   

How to Use the Migration Tool for VDI Management Server Definition Information

Perform the following procedure:

1. Login to the management server as a system administrator (with OS administrative privileges).

2. Execute the migration tool.

   Execute the following command from the command prompt:

   > cd Installation_folder\SVROR\Manager\opt\FJSVrcxmr\sys\VdiMigrationTool <RETURN>
   > migrate_vdi.bat <RETURN>

   The process may take a few minutes to complete.
   It takes approximately two minutes to migrate the definition information of a single VDI management server. When two or more VDI management servers are the target, the time to complete this process increases by 40 seconds per additional server.

   The execution result of the migration tool is output to the standard output for each VDI management server, in the following format.

   • When the migration of the VDI management server information has been completed

     Succeeded: Name of the VDI management server, ip= IP address of the VDI management server

   • When the migration process was skipped because a VDI management server with the same name has been already registered

     Warning: Name of the VDI management server, already exist

     Example

     Output Example of Execution Results:

     Succeeded: horizonview1, ip=192.168.2.1
     Warning: horizonview2, already exist
     Succeeded: horizonview3, ip=192.168.2.2

   Migration is performed starting with the VDI management server defined at the beginning of the VDI management server definition file, in order.
   When migration of all VDI management server definitions is completed, the migration tool exits correctly with the exit status "0".
   When migration of a VDI management server definition fails, the migration tool ends abnormally with the exit status "1". In this case, an error message is output in the standard error output.
   Resolve the cause of the error based on the error message, and then re-execute the migration tool.

   Point

   • Execute the migration tool with the manager of Resource Orchestrator running.

   • Ensure that the migration tool is executed in the storage folder.

3. Confirm the registration results of VDI management software.

   Execute the following command from the command prompt to confirm that the information of the VDI management server that was defined in the VDI management server definition file is displayed as VDI management software.

   > Installation_folder\SVROR\Manager\bin\rcxadm vdimgr list <RETURN>

   Example

   Display Example of the Command for Displaying a List of VDI Management Software

   > C:\Program Files (x86)\Resource Orchestrator\SVROR\SVROR\Manager\bin\rcxadm vdimgr list <RETURN>

   NAME                              TYPE           IPADDRESS       STATUS
   ----                              ----           ---------       ------
   horizonview1                      Horizon View   192.168.2.1     normal
   horizonview2                      Horizon View   192.168.2.2     normal

   The above example is for the case where the VDI management server definition file is defined as follows.

   #VDI1
   vdi1.name=horizonview1
   vdi1.type=vmwareview
   vdi1.ipaddr=192.168.2.1
   vdi1.user=viewdomain1\admin1
   vdi1.password=password1
   vdi1.vmmgr=vc1,vc2
   vdi1.connect_info=192.168.123.1, http://192.168.123.1/vmwareview/
   #VDI2
   vdi2.name=horizonview2
   vdi2.type=vmwareview
   vdi2.ipaddr=192.168.2.2
   vdi2.user= viewdomain2\admin2
   vdi2.password=password2
   vdi2.vmmgr=vc3,vc4
   vdi2.connect_info=192.168.123.2

   
   

2.3.5.2 Obtaining VLAN Information of Network Devices

Details of Modification

To suppress the increase of the load of the product, the initial collection process used to obtain VLAN information from network devices after resource registration has been changed.

• For V3.1.2 (T009379LP-04/T009378WP-05)

  After resource registration of network devices, the VLAN information of all network devices is collected within 20 seconds.

• For V3.1.2 (T009379LP-05/T009378WP-06)

  After resource registration of network devices, the VLAN information of all network devices is collected sequentially within the set monitoring interval (*1).

  *1: This is set in the Interval element of network configuration information.

Effect

After resource registration of network devices, it may take time until the VLAN information is reflected on the network device attribute information on the Resource Details window of the ROR console.

Corrective Action

No action is required.

After resource registration of network devices, if it is necessary to check reflection of VLAN information quickly, select the relevant device and then select [Update] from the pop-up menu.