This section explains the 415XX message series.
[Description]
During an operation on obj, processing of function could not be performed, so it was skipped.
The name of the resource is displayed for obj.
The name of the skipped process is displayed for function.
The reason the process could not be performed is displayed for cause.
The following strings are displayed for function and cause.
When function is "VLAN settings"
Changes could not be made to the VLAN settings of the LAN switch.
When cause is "resource is in unsupported state. (IBP mode)"
As the LAN switch blade has been changed to IBP mode, it cannot be controlled using Resource Orchestrator.
The name of the LAN switch is displayed for resource.
[Corrective Action]
From the ROR console, check on the details window for the LAN switch displayed for resource that the end of "Device name(Product name)" of the basic information is "(Mode:IBP)". No action is required.
[Cloud Edition]
[Description]
During an operation on obj, processing of function could not be performed, so it was skipped.
The name of the resource is displayed for obj.
The name of the skipped process is displayed for function.
The reason the process could not be performed is displayed for cause.
[Corrective Action]
When "StorageChassisFailover" is displayed for function:
The process obj was skipped by the switchover between operating and standby storage.
Take corrective action based on the content displayed for cause.
"not supported"
There are no storage unit name or volume identifiers in the disk information.
Check that the content of the replication definition file is correct.
"mirror_definition not found"
The replication definition file corresponding to a disk registered in Resource Orchestrator does not exist.
Check that the content of the replication definition file is correct.
"not pre_created"
The disk registered with Resource Orchestrator is not the one created in advance.
The target is the disk created in advance.
When "DisasterRecovery(prepare)" is displayed for function:
The process obj was skipped by the extraction of disk resource information from the configuration information of the manager of the operating storage.
Take corrective action based on the content displayed for cause.
"mirror_definition not found"
The replication definition file corresponding to a disk registered in Resource Orchestrator does not exist.
Check that the content of the replication definition file is correct.
