ServerView Resource Orchestrator V3.4.0 Messages

3.1.3 415XX Series

This section explains the 415XX message series.

41502

FJSVrcx:WARNING:41502:obj:function was skipped (cause)

[Virtual 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.
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.
  Take corrective action based on the content displayed for cause.

  • When cause is "resource is in unsupported state. (IBP mode)"

  • When cause is "resource is in unsupported state. (Converged Fabric mode)"

  • When cause is "resource is in unsupported model. (VDX2730)"

  • When cause is "port is in unsupported state. (Automatic Migration of Port Profile)"

  • When cause is "resource is in unsupported model. (N2K-B22FTS-P)"

Corrective Action

When function is "VLAN settings"

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.
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 necessary.

When cause is "resource is in unsupported state. (Converged Fabric mode)"

As the LAN switch blade has been changed to Converged Fabric mode, it cannot be controlled using Resource Orchestrator.
The name of the LAN switch is displayed for resource.
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:Converged Fabric)". No action is necessary.

When cause is "resource is in unsupported model. (VDX2730)"

For a PY CB DCB SW 10Gb 18/6/6 LAN switch blade, VLANs cannot be configured for external ports.
The name of the LAN switch is displayed for resource.
From the ROR console, check on the details window for the LAN switch displayed for resource that the "Model" in the basic information is "VDX2730". No action is necessary.

When cause is "port is in unsupported state. (Automatic Migration of Port Profile)"

VLANs cannot be configured for ports which have an Automatic Migration of Port Profile (AMPP) configured.
Log in to the target LAN switch, and check if an Automatic Migration of Port Profile (AMPP) has been configured.
When configuring VLAN settings, release the Automatic Migration of Port Profile (AMPP) settings.

When cause is "resource is in unsupported model. (N2K-B22FTS-P)"

VLANs cannot be configured for a LAN switch blade PY CB 10Gb FEX Nexus B22.
The name of the LAN switch is displayed for resource.
From the ROR console, check on the details window for the LAN switch displayed for resource that the "Model" in the basic information is "N2K-B22FTS-P". No action is necessary.

[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.
Take corrective action based on the content displayed for cause.

• When "StorageChassisFailover" is displayed for function:

  The process obj was skipped by the switchover between operating and standby storage.

  • When cause is "not supported"

  • When cause is "mirror_definition not found"

  • When cause is "not pre_created"

• When "DisasterRecovery(prepare)" is displayed for function

  The process obj was skipped during the extraction of disk resource information from the configuration information of the manager of the operating storage.

  • When cause is "mirror_definition not found"

• When function is "DisasterRecovery(specification of uplink port for network resources)"

  In the Import process of network resources for Rcxrecovery, as the external connection port configured for the network resource could not be found connection to the external connection port was skipped.

  • When cause is "switch(SWITCH NAME) not found"

• When "Automatic Network Configuration" is displayed for function

  • When cause is "vmhost is not active mode"

  • When cause is "use virtual network definition for vmhost"

  • When cause is "require physical lan segment to configure vmhost"

  • When cause is "resources belong to different tenants(detail)"

• When "port profile association" is displayed for function

  • If cause is "MAC address not found. L-Server(lserver) NIC(nic)"

  • When cause is "NIC(NIC_index,...) was allocated by older manager"

• When "port profile deletion" is displayed for function

  • If cause is "associated VSI exists"

  • If cause is "in maintenance mode"

• When "port profile disassociation" is displayed for function

  • If cause is "in maintenance mode"

Corrective Action

When "StorageChassisFailover" is displayed for function:

When cause is "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.

When cause is "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.

When cause is "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

When cause is "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.

When function is "DisasterRecovery(specification of uplink port for network resources)"

When cause is "switch(SWITCH NAME) not found"

The LAN switch SWITCH NAME used for the network resource displayed for obj was not found.
When the configuration is one that degrades chassis, no corrective action is necessary.
For configurations that do not degrade chassis, ensure that the LAN switches displayed on the server tree of each site are in the same configurations.

When "Automatic Network Configuration" is displayed for function

When cause is "vmhost is not active mode"

When configuring network settings automatically, change the VM host vmhost to active mode, and take corrective action again.

When cause is "use virtual network definition for vmhost"

Check the content of the virtual network definition file.
When configuring the network settings automatically with a VM type that supports auto-configuration of the network, delete the virtual network definition, and perform the corrective action again.
When using a VM type that does not support auto-configuration of the network, the network device auto-configuration settings cannot be configured.

When cause is "require physical lan segment to configure vmhost"

After creating the server NIC definition and specifying the physical LAN segment name for the network resource, perform the operation again.

When cause is "resources belong to different tenants(detail)"

Perform the operation again after moving the resources displayed in detail to the same tenant.

When "port profile association" is displayed for function

If cause is "MAC address not found. L-Server(lserver) NIC(nic)"

The port profile linking process was skipped because there is no MAC address information for the nicth NIC of lserver.
Manually create a link on the Ethernet Fabric switch if necessary.

When cause is "NIC(NIC_index,...) was allocated by older manager"

The process to link the network with the port profile was skipped due to the following reasons:

• The MAC address is not managed because the virtual L-Server was created using an earlier version of Resource Orchestrator

• The MAC address cannot be retrieved from the NIC on the virtual machine

Manually perform the configuration on the Ethernet Fabric switch.

When "port profile deletion" is displayed for function

If cause is "associated VSI exists"

The port profile was not deleted because there is a VSI linked with the corresponding port profile on the Ethernet Fabric switch.
When deleting port profiles, delete any associated VSIs such as links with the MAC addresses of L-Servers first, and then delete the port profiles.

If cause is "in maintenance mode"

The port profile deletion process was skipped because the Ethernet Fabric switch is in maintenance mode.
Manually delete the port profile on the Ethernet Fabric switch if necessary.

When "port profile disassociation" is displayed for function

If cause is "in maintenance mode"

The port profile deletion process was skipped because the Ethernet Fabric switch is in maintenance mode.
Manually delete the port profile on the Ethernet Fabric switch if necessary.