This section explains information about incompatibility between V3.1.0 and V3.0.0.
Details of Modification
The message displayed when operating an L-Server has been changed.
Message output when a MacAddress cannot be obtained, when applying for an L-Platform including a physical L-Server, or creating a physical L-Server
For V3.0.0
FJSVrcx:ERROR:65910:The value of MacAddress, value, is invalid.
FJSVrcx:ERROR:67154:MacAddress:not found
For V3.1.0
FJSVrcx:ERROR:62552:value is outside range of targets
FJSVrcx:ERROR:62553:no AddressType found in targets
FJSVrcx:ERROR:62554:AddressType:no more addresses available
Message output when the WWNAddress cannot be obtained, when applying for an L-Platform including a physical L-Server, or creating a physical L-Server
For V3.0.0
FJSVrcx:ERROR:67133:remained amount of WWN address:out of range
For V3.1.0
FJSVrcx:ERROR:62552:value is outside range of targets
FJSVrcx:ERROR:62553:no AddressType found in targets
FJSVrcx:ERROR:62554:AddressType:no more addresses available
Message output when the specified system disk does not exist, when applying for an L-Platform including a physical L-Server, or creating a physical L-Server
For V3.0.0
FJSVrcx:ERROR:67154:System Disk:not found
For V3.1.0
FJSVrcx:ERROR:62549:obj1 not specified for obj2. (detail)
Message output when the resource has no access authority, when starting an L-Platform including a physical L-Server, or starting a physical L-Server
For V3.0.0
FJSVrcx:ERROR:67280:obj:start not supported. The resources used are permission denied.
For V3.1.0
FJSVrcx:ERROR:62548:obj1 access rights not possessed for obj2. (detail)
Message output when there are no physical servers, when applying for an L-Platform including a physical L-Server, or creating or starting a physical L-Server
For V3.0.0
FJSVrcx:ERROR:65911:Specified resource PhysicalServer not found.
For V3.1.0
FJSVrcx:ERROR:62532:resource not found in target. (detail)
FJSVrcx:ERROR:62533:resource matching conditions not found in target. (detail)
Message output when there is no access authority for the person creating a virtual L-Server to VM host associating the configured virtual machine and the virtual L-Server
For V3.0.0
FJSVrcx:ERROR:67154:TargetServer id=id:not found
For V3.1.0
FJSVrcx:ERROR:62547:obj access rights not possessed. (detail)
Message output when the resource has no access authority, when starting an L-Platform including a virtual L-Server, or starting a virtual L-Server
For V3.0.0
FJSVrcx:ERROR:67280:obj:start not supported. The resources used are permission denied.
For V3.1.0
FJSVrcx:ERROR:62548:obj1 access rights not possessed for obj2. (detail)
The message is output to command prompt and the terminal where the command was executed when operating it by the command.
Corrective Action
It is necessary to add the message for the target of monitoring, when monitoring the messages (numbers or message text) for Resource Orchestrator using other vendors' products.
It is necessary to add or revise messages after modification, when the messages before modification are described in the operation guide created by users.
Details of Modification
The lines for VMHostPool and StoragePool[num] are added to the information output using the rcxadm lserver show command. Depending on the status of resource allocation, the information may not be displayed.
The following tags are added to the information using the rcxadm lserver show -format xml command. Depending on the status of resource allocation, the information may not be displayed.
Pool elements in Current elements
Current elements in Disk elements, and Pool elements under Current elements
When disk space is unclear and the VM type is Solaris Containers, DiskSize is shown as "-" in the information output using the rcxadm lserver show command.
Effect
When the command output results are analyzed by programs, the analysis may fail.
Corrective Action
When the command output results are analyzed by programs, it is necessary to skip reading of added information.
When the output results are analyzed in the text format, it is necessary to extract the necessary items by lines, but this is only required for users analyzing the results in text format.
Details of Modification
The Date format displayed on the Dashboard (System Conditions) has been modified.
In V3.0 the format was yyyy/mm/dd.
In V3.1, the format is yyyy-mm-dd.
Note that the date format output to CSV files has also been modified.
Effect
When using the date output to the CSV file, processing may fail.
Corrective Actions
When using the date output to the CSV file, modification is required.
Details of Modification
The Date format displayed on the Dashboard (pool conditions) has been modified.
In V3.0 the format was mm/dd/yyyy.
In V3.1, the format is yyyy-mm-dd.
Note that the date format output to CSV files has also been modified.
Effect
When using the date output to the CSV file, processing may fail.
Corrective Actions
When using the date output to the CSV file, modification is required.
Details of Modification
The method of handling L-Server template setting values that occur in L-Platform reconfiguration has been modified.
In V3.0, when reconfiguring post deployment L-Platforms, even if the following setting values were modified to a different type (L-Server template), the changes were not reflected in the L-Server setting values:
Alive Monitoring Settings
Redundancy
Repurpose
In V3.1, when reconfiguring post deployment L-Platforms, if the above setting values are modified to a different type (L-Server template), the changes are now reflected in the L-Server setting values.
Corrective Actions
Reregister the L-Server template which has the same setting values as the following items:
Also, when modifying only the Server specs, select the type of Server that has the same setting values as the following items, and perform the L-Platform reconfiguration:
Alive Monitoring Settings
Redundancy
Repurpose
Details of Modification
Previously, when registering L-Platform template image information which specified cloning images that included data disks, the image information from the system disk configuration only was registered in V3.0.
But in V3.1, image information with the data disks is now included in the configuration is registered.
Corrective Actions
Infrastructure administrators
After deleting the data disk from the L-Server which was the source of the cloning image collection, recollect the cloning image. Specify the recollected cloning image and reregister the image information.
Tenant administrators
After deploying a configuration which includes the data disks, collect a cloning image in the [L-Platform] tab of the ROR console which specifies exclusion of the data disks. If this is done, image information configured only with system disks is automatically registered.
Details of Modification
AttachDisk or CreateDisk of the L-Platform API was able to attach one disk to a server even if the maximum number of extension disks of the server was set to zero.
It has been corrected, and now AttachDisk and CreateDisk cannot attach a disk if the maximum number of extension disks is zero.
Corrective Actions
If it is expected that a disk will be attached to a server that is created using image information with the maximum number of extension disks set to zero, edit the image information and change the maximum number of extension disks to a value more than zero.
