IBM Flex System Manager Typ 7955, 8731 und 8734 - Softwarefehlernachrichten
Die Ereignisprotokolle für IBM® Flex System Manager Typ 7955, 8731 und 8734 können die folgenden Fehlernachrichten enthalten.
DNZDVM150E
There is no value specified for the User ID. You must specify a value for the user ID. Please specify a valid value for the user ID.
DNZDVM151E
The format of the specified password is not valid. The password must consist of 7 or more alphnumeric characters. Please specify a valid value for the password.
DNZDVM152E
You must specify a value for the date. The required format for the date is dd/mm/yyyy. Please specify a valid date in the required format.
DNZDVM153E
You must specify a value for the time. The required format for the time is hh:mm:ss AM/PM. Please specify a valid time in the required format.
DNZDVM154E
The format of the specified date is not valid. The required format for the date is dd/mm/yyyy. Please specify a valid date in the required format.
DNZDVM155E
The format of the specified time is not valid. The required format for the time is hh:mm:ss AM/PM. Please specify a valid time in the required format.
DNZDVM156E
The format of the specified domain name is not valid. The required format for the domain name is xxx.xxx.xxx, for example, server1.mycompany.com. Please specify a valid domain name in the required format.
DNZDVM157E
The format of the specified domain name is not valid. The domain name can consist of alphanumeric characters a through z, A through Z, 0 through 9, and the hyphen character, separated by a period. The value must be more than 3, and fewer than 255, characters. The required format for the domain name is xxx.xxx.xxx, for example, server1.mycompany.com. Please specify a valid domain name in the required format.
DNZDVM158E
You must specify a value for the domain name. The required format for the domain name is xxx.xxx.xxx, for example, server1.mycompany.com. The domain name can consist of the alphanumeric characters a through z, A through Z, 0 through 9, and the hyphen character, separated by a period. The value must be more than 3, and fewer than 255, characters. Please specify a valid domain name in the required format.
DNZDVM159E
The specified domain name is longer than the allowed maximum length. The domain name must consist of fewer than 255, and more than 3, alphanumeric characters, hyphens, and periods. Please specify a valid domain name that meets the length requirements.
DNZDVM160E
The specified domain name is shorter than the allowed minimum length. The domain name must consist of more than 3, and fewer than 255, alphanumeric characters, hyphens, and periods. Please specify a valid domain name that meets the length requirements.
DNZDVM161E
The format of the specified gateway IP address is not valid. The required gateway IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify valid gateway IP address in the required format.
DNZDVM162E
You must specify a value for the gateway address. The required gateway IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid gateway IP address in the required format.
DNZDVM163E
The format of the specified gateway address range is not valid. The required gateway IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid gateway address range in the required format.
DNZDVM164E
The format of the specified IP address is not valid. The required IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid IP address in the required format.
DNZDVM165E
You must specify a value for the IP address. The required IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid IP address in the required format.
DNZDVM166E
The format of the specified IP address range is not valid. The required IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid IP address range in the required format.
DNZDVM167E
The format of the specified network mask is not valid. The required network mask format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid network mask in the required format.
DNZDVM168E
You must specify a value for the network mask. The required format for the network mask is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid network mask in the required format.
DNZDVM169E
The format of the specified netmask range is not valid. The required format for the netmask is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid netmask in the required format.
DNZDVM170E
Unable to find an IP address. You must specify at least one IP address. Please specify at least one valid IP address.
DNZDVM171E
The format of the specified IP address is not valid. The required format of the IP address is: nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid IP address in the required format.
DNZDVM172E
The specified DNS server has already been added. The specified DNS server is a duplicate entry. Please specify a new DNS server to add, or click Next to continue to the next step.
DNZDVM173E
The specified domain suffix has already been added. The specified domain suffix is a duplicate entry. Please specify a new domain suffix to add, or click Next to continue to the next step.
DNZDVM174E
The format of the specified IPv6 address is not valid. Abbreviation of IPv6 addresses is not supported. The required format is xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx. Please specify a valid IPv6 address in the required format.
DNZDVM175E
The specified IPv6 address is already in the list. The specified IPv6 address is a duplicate entry. Please specify a different IPv6 address, or click Next to continue to the next step.
DNZDVM176E
The format of the IPv6 prefix length is not valid. The required format of the prefix length is a number between 1 and 128. Please specify a prefix length in the required format.
DNZDVM177E
The specified passwords are not identical. Both specified passwords must be the same. Please specify passwords that match.
DNZDVM178E
The specified user ID already exists. The specified user ID is a duplicate entry. Please specify a different user ID.
DNZDVM179E
You did not accept the license agreement. You must accept the license agreement before you can continue to the next step. Accept the license agreement, then click Next.
DNZDVM180E
The selected application uses IPv6 addresses only. You cannot specify an IPv4 address. Please specify a valid IPv6 address in the required format of xxxx:xxxx:xxxx:xxx:xxxx:xxxx:xxxx:xxxx.
DNZDVM181E
The selected application uses IPv4 addresses only. You cannot specify an IPv6 address. Please specify a valid IPv4 address in the required format of nnn.nnn.nnn.nnn.
DNZDVM182E
The specified host already exists. The specified host is a duplicate entry. Please specify a different host.
DNZDVM183E
The IP address or network mask field is not empty. The IP Address or network mask fields contain values that must be used or discarded before you can continue. Please click Add to add the values, or clear the values from the fields.
DNZDVM184E
The DNS or domain suffix field is not empty. The DNS or domain suffix fields contain values that must be used or discard before you can continue. Please click Add to add the values, or clear the values from the fields.
DNZDVM185E
The specified host name is not valid. The specified host name contains characters that are not valid. Please specify a valid host name in the required format.
DNZDVM186E
You must specify a value for the host name. A host name is required. Please specify a valid host name.
DNZDVM187E
A label in the specified host name is longer than the allowed maximum length. The maximum length for a label is 63 or fewer alphabetic characters. Please specify a host name that meets the length requirements for each label.
DNZDVM188E
You must specify a value for the host name. A host name is required. Please specify a valid host name.
DNZDVM189E
The specified host name label begins or ends with the hyphen (-) character. A host name label cannot begin or end with the hyphen (-) character. Please specify host name labels in the required format.
DNZDVM190E
The specified host name is longer than the allowed maximum length. The maximum length of the host name is 255 or fewer alphabetic characters. Please specify a host name that meets the length requirements for the host name.
DNZDVM191E
The specified user ID does not begin with an alphabetic character. The user ID must begin with an alphabetic character. Please specify a user ID that begins with an alphabetic character.
DNZDVM192E
The specified user ID contains one or more special characters. The user ID cannot contain special characters. Please specify a value for the user ID that not does contain special characters.
DNZDVM198E
The IP address range 192.168.70.200 - 192.168.70.299 is reserved and cannot be used.
DNZDVM199E
Cannot use localhost as the host name for the management server.
DNZDVM200E
You need to add at least one IPv6 address. Please specify at least one valid IP address.
DNZDVM202E
The specified password does not comply with the system's password quality rules. To view a list of these rules, click on the help link below.
DNZDVM204E
We have detected both network adapters being on the same subnet, which is not supported. IP Address VALUE_0 and IP Address VALUE_1 are on the same subnet. You can fix this by specifying different subnets or using just one network adapter (eth0).
DNZDVM205E
The format of the specified IP address is not valid. The required IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid IP address in the required format.
DNZDVM206E
The format of the specified IP address range is not valid. The required IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid IP address range in the required format.
DNZDVM207E
You must specify a value for the IP address. The required IP address format is nnn.nnn.nnn.nnn, where nnn is a number between 0 and 255. Please specify a valid IP address in the required format.
DNZDVM208E
The User ID you specified contains an invalid character. Please pick a different User ID.
DNZDVM209E
The User ID you specified is reserved. Please pick a different User ID.
DNZDVM210E
The User ID cannot start with a number. Please pick a different User ID.
DNZDVM255E
The static IPv4 address and the DHCPv6 client cannot both be selected at the same time.
DNZDVM256E
The DHCPv4 client and the static IPv6 address cannot both be selected at the same time.
DNZDVM271E
The specified time is before the system build time: VALUE_0. This will result in failure to start system. Please specify a time after the system build time, then retry the operation.
DNZDVM272E
The specified time is more than an hour before current time, Verify the time is set correctly.
DNZDVM273E
The specified time is more than an hour after current time, Verify the time is set correctly.
DNZDVM300E
The specified IP address already exists in the network. To prevent an address conflict, please specify a different IP address.
DNZFM0001E
Unable to obtain resource. (GUID: VALUE_0). Contact Support.
DNZFM0002E
Unable to get local computerSystem resource. (GUID: VALUE_0). Contact Support.
DNZFM0003E
A Resource caching exception occurred. See the next log entry for more information.
DNZFM0004E
Unable to find resource. (GUID: VALUE_0). Contact Support.
DNZFM0005E
Found multiple resources when only one was expected. Contact Support.
DNZFM0006E
The root group cannot be found. Contact Support.
DNZFM0007E
An unexpected class type was encountered. Expected class type: VALUE_0. Contact Support.
DNZFM0112E
Task VALUE_0 must be invoked with one or more targets.
DNZFM0201E
The check for ITMEs task has finished with errors.
DNZFM0400E
Exception occurred in Sample Command VALUE_0
DNZFM0510E
Unable to generate security certificate because of an internal error (command failure). Make sure that your user ID is assigned to a role of SMAdministrator (smadmin group) and attempt the generate the certificate again. If the problem persists, contact Support.
DNZFM0515E
Internal error occurred (no host information). Contact Support.
DNZFM0516E
Internal error occurred while initializing the user registry. Check the logs for
more detailed information and contact Support.
DNZFM0517E
Internal error occurred while resetting the user registry. Check the logs for more detailed
information and contact Support.
DNZFM0518E
Internal error occurred while initializing the user registry. The chkconfig command failed. Contact Support.
DNZFM0519E
Internal error occurred while initializing the user registry. The chmod script failed updating of the /etc/init.d/ldap script. Contact Support.
DNZFM0520E
Internal error occurred while initializing the user registry. The System Administrator ID could not be found. Contact Support.
DNZFM0521E
Internal error occurred while initializing the user registry. The password for the System Administrator passed down to the LDAP initialization
component. Contact Support.
DNZFM0522E
Internal error occurred while getting the UUID of the FSM. rc = {0}. Contact Support.
DNZFM0523E
An internal error occurred while processing a security policy. Error: {0} occurred in method: {1}. Contact Support.
DNZFM0524E
Invalid NTP version 3 authentication key value.
DNZFM0525E
Invalid NTP version 3 authentication key index.
DNZFM0527E
The password entered does not meet the criteria for a secure password for reason {0}.
Reason 1: Password must contain three of the following combinations:
one lowercase alphabetic character, one uppercase alphabetic character, one numeric character, one special character.
Reason 2: Password must contain no more than three of the same characters used consecutively.
Reason 3: Password must not be a repeat or reverse of the associated user ID.
Reason 4: Password must have at least 2 characters that are different from the previous password.
DNZFM0528E
The new password must have at least 8 characters.
DNZFM0529E
Internal error occurred while upgrading the user registry. The upgrade failed. Check the logs for more detailed
information and contact Support.
DNZFM0530E
The LDAP version was not able to be updated while upgrading the user registry. The upgrade failed. Check the logs for more detailed
information and contact Support.
DNZFM0531E
The LDAP schema was not able to be updated while upgrading the user registry. The upgrade failed. Check the logs for more detailed
information and contact Support.
DNZFM0532E
An internal error occurred while attempting to retrieve the password policy for the FSM. Contact Support.
DNZFM1023E
The data management service is not available.
DNZFM1024W
Information is still being collected about the Flex System Manager and its managed chassis. The information displayed on this panel may not be complete. Please log out, wait two minutes, and log back in. If this message persists, contact IBM support.
DNZFM1025I
The password policy has been configured.
DNZFM1046E
The specified maximum number of CMM sessions is not valid. The value in the maximum number of CMM sessions field must be a whole number between VALUE_0 and VALUE_1.
DNZFM1050E
The new passwords do not match. Reenter the new password and confirm the new password.
DNZFM1051W
The Flex System Manager is about to restart. This Web connection will be ended.
DNZFM1052E
When the Flex System Manager security level is set to Secure, the server must be enabled to check for password quality and cannot accept the password if unable to check it.
DNZFM1053E
When the Flex System Manager security level is set to Secure, users must change the password at first logon.
DNZFM1054E
When the Flex System Manager security level is set to Secure, the server must enable account lockout.
DNZFM1055E
Cannot create the user because the user name is not valid. The user name must begin with an alphabetic character, must contain only a-z,A-Z,0-9, - or _. It must be no longer than 32 characters. Enter a valid name and create the user again. If the problem persists, contact Support.
DNZFM1056E
A security policy level has not been selected. Please select a valid level to change the security policy level.
DNZFM1057E
The following syslog server configurations could not be removed: VALUE.
DNZFM1058E
A syslog server configuration with these values already exists.
DNZFM1059E
The syslog server configuration was not modified. Verify the entered values are correct and attempt the operation again.
DNZFM1060E
The syslog server configuration was not added. Verify the entered values are correct and attempt the operation again.
DNZFM1061E
There was a problem uploading the encryption files. Verify the files are valid and attempt the operation again.
DNZFM1062E
One or more of the encryption files specified do not have a .pem extension. Verify the files are valid and attempt the operation again.
DNZFM1063E
One or more chassis need to be selected to proceed.
DNZFM1064E
Syslog server encryption configuration could not be modified. Verify the files are valid and attempt the operation again.
DNZFM1065E
A valid host name or IP address must be entered for the remote syslog configuration.
DNZFM1066E
A value was not specified for the SFTP user or password field.
DNZFM1067W
The security level in the backup file (VALUE_0) and the current security level (VALUE_1) are different. Select <b>Allow restore with a different security level</b> if you would like to continue with this restore and try again.
DNZFM1068E
The FSM security policy level must be set to legacy to configure unencrypted remote syslog configurations.
DNZFM1069E
The value in the SSH timeout field must be a whole number between VALUE_0 and VALUE_1.
DNZFM1086E
The selected CMM could not be restarted.
DNZFM1087E
The value specified for the certificate file path is not valid.
DNZFM1088W
The following users could not be deleted: VALUE.
DNZFM1089E
The following IMMs were not able to return network configuration data: VALUE.
DNZFM1090W
One or more chassis is already managed by another Flex System Manager. Managing a chassis will remove it from the other Flex System Manager.
DNZFM1091W
The Features on Demand chassis key limit purchased is VALUE chassis. Managing the indicated chassis will exceed this limit.
DNZFM1092I
The graphical view was closed because the shown chassis began the unmanage process.
DNZFM1093W
The graphical view was unable to retrieve necessary data.
DNZFM1094E
Please select one or more $$IO_MODULES_UPPER_CASE$$ to configure.
DNZFM1095E
$$IO_MODULES_UPPER_CASE$$ VALUE must be online and unlocked in order to continue with the wizard.
DNZFM1096E
The following $$IO_MODULES_UPPER_CASE$$ were not successfully configured: VALUE.
DNZFM1097I
The network configuration for the following $$IO_MODULES_UPPER_CASE$$ were successfully configured: VALUE.
DNZFM1098E
User VALUE cannot be added to any group.
DNZFM1099E
Users belonging to the FSM VALUE_0 role must be in the VALUE_1 user group.
DNZFM1100E
The VALUE user group must be specified for the user. All users must be a member of VALUE user group.
DNZFM1101E
User group $$ROOT_USER_GROUP$$ is not a valid selection for this user.
DNZFM1102E
The discovery process is complete. No chassis were found for this management domain.
DNZFM1103I
The chassis you are trying to manage: VALUE_1 is already being managed from the following IP addresses:
VALUE.
When a chassis is managed, an event subscription is created for the managing entity on the CMM. Having multiple subscriptions can have an effect on performance.
If the other managing entity is a FSM, you can try to remove the subscription by unmanaging. If that is not possible, you can remove the subscription by clicking the 'Manage Subscriptions' button to manually unsubscribe each event subscription. Then, attempt to manage the chassis from this FSM again.
DNZFM1104E
A default role and resource group combination can not be removed for the user.
DNZFM1105E
When the Flex System Manager security level is set to Secure, the account lockout duration can not be less than 60 minutes or different than 0.
DNZFM1106I
The chassis VALUE being unmanaged has lost access. Without access the FSM can not remove CIM indications or remove
the configurations that was done during the management of this chassis. It is recommended that the No Access link on
the FSM Management Domain page be used to request access to the chassis before unmanaging it.
DNZFM1107I
The chassis VALUE you are attempting to unmanage has related resources (managed endpoints) that will not be automatically removed if you continue with the unmanage process. This is generally due to Operating System resources, Virtual Machines and other managed endpoints that are associated with the Compute Node resources in the management domain. Unmanaging the chassis without removing these related resources from the management domain can cause problems if these resources are re-managed. It is recommended that you manually remove these resources from the management domain before continuing with the unmanage operation. For more information about how to identify and remove these resources, see Unmanaging a chassis in the online FSM Information Center.
DNZFM1108E
The PRODUCT_NAME_SHORT does not have Platform agent update files imported that support the operating system types running on the following systems: VALUE.
DNZFM1109E
The CIM server encountered a error. Please try again.
DNZFM1111E
The IBM FSM User ID and/or Password is not valid. (Click the Edit Credentials button)
DNZFM1112E
The User ID is not a supervisor on the IBM FSM or the password for the user is expired. (Click the Edit Credentials button) Please verify the user credentials and retry the action.
DNZFM1113W
Selecting to automatically set an IPv6 unique address on each chassis component will overwrite any existing static IPv6 addresses.
DNZFM1114I
Initial inventory is still being collected for components in WERT. As components are inventoried, the number of components discovered and accessed will be updated.
DNZFM1115E
Connecting to user registry server WERT failed. Make sure you have specified the correct port and that the server is available.
DNZFM1116E
Authentication failed connecting to external user registry server WERT.
DNZFM1117E
Connecting to user registry server WERT failed. Check to make sure you have a valid configuration.
DNZFM1118W
The network interface for the management network is configured to use DHCP, which means that the management interface IP address can change when the DHCP lease expires. If the address does change you will be required to unmanage all chassis and then manage them all again. Alternatively, you can change the management interface to a static IP address, you can make sure that the DCHP server configuration is set so that the DHCP IP address is based on a MAC address, or you can make sure that the DHCP server configuration is set to prevent the DHCP lease from expiring.
DNZFM1119E
Using the Recovery User ID to manage a chassis is not allowed. Please specify a different User ID.
DNZFM1120E
The recovery password is invalid. Please enter a different password.
DNZFM1121E
The recovery passwords do not match. Please type in the password again.
DNZFM1122I
You have selected remote chassis WERT. Centralized management and automatic assignment of IPv6 Unique Local Addresses (ULAs) are not supported options for remote chassis. To include these options for local chassis, please manage remote and local chassis as separate operations.
DNZFM1123E
Connecting to user registry server WERT failed. Check to make sure you have a valid configuration.
DNZFM1124I
The Secure Policy for FSM is set to Legacy, but you have chosen to enable SSL, please verify the port number specified is correct.
DNZFM1125E
Anonymous bind is not supported on user registry server.
DNZFM1126E
The Default base Distinguished Name is invalid.
DNZFM2001W
The specified chassis could not be unmanaged because is not currently managed by the FSM. Validate that you are specifying the correct FSM and chassis on the command.
DNZFM2002W
The specified chassis is already managed by the FSM.
Validate that you are specifying the correct FSM and chassis on the command.
DNZFM2003W
The specified chassis cannot be managed. If the problem persists, contact Support.
DNZFM2004W
The specified chassis could not be unmanaged. If the problem persists, contact Support.
DNZFM2005W
The chassis with the following IP address cannot be found: VALUE_0.
Verify that the specified IP address is valid.
DNZFM2006W
The specified IP address does not match any known chassis IP address.
Specify a valid chassis IP address and run the command again.
DNZFM2007W
The FSM is not managing Call Home notifications for the specified chassis with host name: VALUE_0.
Call Home is currently being managed by host name: VALUE_1.
DNZFM2008W
The FSM is not receiving alert notifications for chassis with host name: VALUE_0.
***Note: Action depends on CMM functionality.
DNZFM2009E
Unable to obtain the chassis managed endpoint. Contact Support.
DNZFM2010E
The FSM cannot determine the IP address of the specified chassis.
Attempt to rediscover the chassis, if the problem persists, contact Support.
DNZFM2011E
The specified FSM cannot be resolved from the specified IP address.
Make sure that the FSM IP address is valid and attempt to run the command again.
DNZFM2012E
The FSM that is managing the chassis is not the FSM that is expected to be managing the chassis.
Make sure that the specified FSM is the FSM managing the chassis and run the command again.
DNZFM2013E
An exception occurred while running inventory. Attempt to run inventory again. If the problem persists, contact Support.
DNZFM2014E
A Service Location Protocol (SLP) exception occurred. Contact Support.
DNZFM2015E
An internal error occurred (data management) during initialization. Contact Support
DNZFM2016E
An internal error occurred (data management) during parsing.
Contact Support.
DNZFM2017E
The FSM cannot reach the chassis using its available IP addresses.
You must define an external address for the chassis that has the same type (IPV4 or IPV6) that the management interface (eth0) of the FSM is using.
Verify the chassis IP address by refreshing the view. Then try again. If the problem persists, contact Support.
DNZFM2018E
The FSM cannot discover the chassis using the IP addresses that are available. You must define an external address for the chassis that has the same type (IPV4 or IPV6) that the management interface (eth0) of the FSM is using.
.
DNZFM2019E
The FSM cannot unmanage the chassis without leaving behind manageable elements.
You may unmanage with the force option if you wish to manually clean up the elements that were left behind.
DNZFM2020E
The number of chassis that will be managed will exceed the chassis management
license currently in place. You should upgrade the license to support
the management of additional chassis.
DNZFM2021E
The network interface for the management network is currently configured to use DHCP.
The management interface IP address can change when the DHCP lease expires.
If the address does change you will be required to unmanage the chassis and remange the chassis.
To prevent problems either change the management interface to a static IP address, or insure
that the DCHP server configuration is set so that the DHCP address is based on a MAC address
or that the DHCP lease does not expire.
If your DHCP server is configured to base DHCP address on the MAC address or the DHCP lease does
not expire, you may manage with the force option to override this message.
DNZFM2023E
A resource caching exception occurred. Contact Support.
DNZFM2025E
The discovery service is not available.
Restart the FSM and attempt to manage the chassis. If the problem persists, contact Support.
DNZFM2026E
The chassis Discovery process did not complete. Refresh the chassis list by clicking the Discover New Chassis button and attempt to manage the chassis again. If the problem persists, contact Support.
DNZFM2027E
The operating system discovery process did not complete. Make sure that the operating system is reachable from the same network on which the FSM is attached. Then, perform the operation again.
If the problem persists, contact Support.
DNZFM2028E
Unable to move the management of the chassis to the specified FSM. Make sure that the FSM is functioning and that you can log in to the FSM.
Then, attempt to move the chassis again.
DNZFM2029E
The operating system discovery process did not complete successfully. A timeout was reached while waiting for the operating system discovery to complete. This does not mean that the discovery failed. However, the operating system will not be accessible automatically. From the Chassis Manager, right-click on the node and select Security -> Configure access. Enter the correct authentication credentials to gain access. If the problem persists, contact Support.
DNZFM2030E
An error was encountered while trying to remanage chassis after rebooting the FSM. Make sure that the chassis is running correctly and that there is a working network connection between the chassis and the FSM. Then manage the chassis again (You do not need to unmanage first). If the problem persists, contact support.
DNZFM2031E
Internal error (problem reading properties file). Make sure that the user account has proper permissions to read files on the FSM. If the problem persists, contact Support.
DNZFM2032E
Invalid command usage: run WERT_0 -? for information about running this command.
DNZFM2033E
The chassis you are trying to manage is already being managed from the following IP addresses: VALUE_0.
When a chassis is managed, an event subscription is created for the managing entity on the CMM. Having multiple subscriptions can have an effect on performance.
If the other managing entity is a FSM, you can remove the subscription using the unmanage command.
If the other managing entity is another application, run the command: smcli lschassisind to manually remove event subscriptions.
Then, attempt to manage the chassis from this FSM again.
DNZFM2035E
Failed to add object to database (Internal Error). Contact Support.
DNZFM2036E
No chassis specified on command. Run the command again, specifying a valid chassis.
DNZFM2100E
Could not get the localhost IP address for the FSM. Contact Support.
DNZFM2200E
The group service is not available. Restart the FSM and attempt to manage the chassis.
If the problem persists, contact Support.
DNZFM2201E
Unable to request access to the Operating System with host name: WERT_0.
From the Chassis Manager, right-click on the node and select Security -> Configure access. Enter the correct authentication credentials to
gain access. If the problem persists, contact Support.
DNZFM2203E
The chassis with the IP address: VALUE_0 is in the process of being managed.
Therefore, it cannot be deleted. Wait until the management process completes; then, attempt to delete the chassis again.
DNZFM2204E
Unable to request access to the chassis with host name: WERT_0.
From the user interface, use the link to Fix Access Error and enter correct authentication credentials.
From the command line, verify that you are entering a userID and password that can authenticate
with the chassis and run the command again.
Additionally you can verify that a valid root CA certificate for the chassis with host name: WERT_0 exists on the FSM by using FSM Resource Explorer and viewing the \"All
Systems\" group. If the chassis is \"Not Trusted\" you will need to accept the CA certificate to
successfully manage this chassis. If the problem persists, contact Support.
DNZFM2205E
Unable to revoke access to the chassis with host name: VALUE_0.
DNZFM2206E
An exception was returned while configuring the chassis user registry (LDAP). Make sure that the CMM in the chassis is functional and connected to the network.
Attempt to log in to the CMM with the same credentials that you used to manage the chassis.
If successful, attempt to manage the chassis again. Otherwise, attempt to manage the chassis using CMM
credentials that can be used to access the CMM directly.
If the problem persists, contact Support.
DNZFM2207E
The manageable element for the chassis with IP address: VALUE_0 was deleted unexpectedly.
Attempt to discover and manage the chassis again.
DNZFM2208E
The FSM cannot manage the specified chassis with host name WERT_0 because FSM management of that type of chassis is not supported. Specify a supported chassis and try again.
DNZFM2210E
The FSM for the IP address: VALUE_0 is unknown to this FSM. Validate that the IP address was specified correctly, and make sure that a chassis with the specified IP address is functioning and connected to the network. Then, perform the operation again.
DNZFM2211E
The chassis with the IP address: VALUE_0 is unknown to this FSM. Validate that the IP address was specified correctly, and make sure that a chassis with the specified IP address is functioning and connected to the network. Then, perform the operation again.
DNZFM2212E
The user ID and password provided for the chassis were incorrect.
Use the link to Fix Access Error and enter the correct user ID and password.
DNZFM2213E
The request access process for the chassis returned a Not Accessible error.
DNZFM2214E
The request access process for the chassis returned a Not Supported error.
DNZFM2215E
Unable to request access to the chassis with host name: WERT_0.
The authentication credentials have expired. Use the link to Change Password and enter a new password.
If you are using an external User Registry with your chassis, connect to either the chassis
or the external User Registry to restore the expired credentials.
DNZFM2216E
Request access failed on chassis with host name: VALUE_0.
Use the link to Fix Access Error and enter valid user ID and password.
DNZFM2217E
Revoke access failed with status of 'result not available'. The chassis with host name: VALUE_0 is
unavailable. Make sure that the chassis is running and that there is a working network connection between
the chassis and the FSM. Then, attempt to revoke access again.
DNZFM2218E
The user ID and password provided for the FSM were incorrect. Specify a valid user ID and password.
DNZFM2219E
The specified FSM is unknown to this FSM. Validate that the specified FSM
is functioning and connected to the network. Then, perform the operation again.
DNZFM2220E
The specified chassis is unknown to this FSM. Validate that the specified chassis
is functioning and connected to the network. Then, perform the operation again.
DNZFM2221E
An exception was returned while resetting the chassis user registry (LDAP) during an unmanage operation.
The unmanage was successful but
the chassis user registry was not reset. Make sure the chassis is functioning and connected to the network.
Then, log in to the chassis
command-line interface using the RECOVERY_ID user account. Verify that user registry authentication is set to local authentication
(CMM command: accseccfg -am local -T mm[p]), verify that the SSL client is disabled (CMM
command: sslcfg -client disabled -tc1 remove -T mm[p]), and verify that the CMM local accounts are not disabled
(CMM command: fsmcm -off -T mm[p]). Once you have manually reset the chassis user registry using the commands listed,
it can be managed again. If the problem persists, contact Support.
DNZFM2222E
The unmanage of the chassis failed because some contained hardware elements were not removed.
They will have to be deleted manually in order to manage the chassis again.
DNZFM2223E
The unmanage of the chassis failed because the removal of contained hardware elements could not be monitored.
If any hardware elements are not deleted after a few minutes, they might have to be deleted manually in order to manage the chassis again.
DNZFM2224E
The unmanage of the chassis failed because the managed endpoint of the chassis was not removed.
Wait a few minutes then try again. If the problem persists, contact Support.
DNZFM2225E
The user ID and password provided for the chassis were incorrect. Specify a valid user ID and password.
DNZFM2226E
The remote FSM for the IP address: VALUE_0 is unknown to this FSM. Validate that the IP address was specified correctly, and make sure that a FSM with the specified IP address is functioning and connected to the network. Then, perform the operation again.
DNZFM2227E
Unable to change expired password on chassis with host name: WERT_0.
Login to chassis web GUI to change the password, then attempt the manage again.
DNZFM2228E
The chassis user account is locked on host: WERT_0.
You can attempt to manage the chassis again using a different set of credentials. In addition,
you can attempt to manage the chassis using the currently specified credential after the account
lock-out period (typically 1 hour), or you can log in to the CMM Web interface using a CMM user account
with Supervisor permissions to unlock the account.
DNZFM2229E
The chassis WERT_0 has exceeded the number of available connections.
Wait for a connection to become available or, if necessary, restart the chassis or the FSM.
DNZFM2250E
A core service is initializing. Wait a few minutes and try again. If the problem persists, contact Support.
DNZFM2251E
The chassis you are trying to manage is already sending alerts to the following IP Addresses: WERT_0.
Follow the link to managing FSM and unmanage the chassis.
If you cannot unmanaged the chassis, run the smcli command lschassisind --clear
DNZFM2252E
Either the user ID or password is invalid. Enter the correct user ID and password and try again.
DNZFM2253E
The following exception was thrown while trying to run the command.
DNZFM2254E
The following exception was received: VALUE_0
DNZFM2260E
Validating that the V7000 storage node with address: WERT_0
has been discovered already and can be deleted.
DNZFM2261E
The specified V7000 storage node is not currently being managed, so it cannot be unmanaged.
DNZFM2262I
The V7000 storage node is in the process of being deleted from the list of managed resources.
DNZFM2263I
Command to remove the data source: VALUE_0
DNZFM2264E
The removal of the data source failed with message: WERT_0
Attempt to remove the data source again. If the problem persists, contact Support.
DNZFM2265E
No fibre channel switch was found at address: WERT_0 Check that you are
specifying a valid address and that the fibre channel switch is accessible from the FSM. Then, try the command again.
DNZFM2266E
Connection was refused to the V7000 storage node. Error code: WERT_0
DNZFM2267I
Removing the SSH key from WERT_0
on the V7000: WERT_1
DNZFM2268I
Pushing the SSH public key for admin to the V7000 storage node using the command: WERT_0
DNZFM2269E
The V7000 storage node with the management address: WERT_0 was not unmanaged.
DNZFM2269I
The V7000 storage node with the management address: WERT_0 was unmanaged succesfully.
DNZFM2270E
V7000 with management address: VALUE_0 was not managed.
DNZFM2270I
V7000 with management address: VALUE_0 was managed succesfully.
DNZFM2271E
The V7000 storage node has been discovered already.
DNZFM2272E
User WERT_0 has a public key defined on the V7000 storage node,
which means that the storage node is managed already. Remove the key from
WERT_1 on the storage node. Optionally, run smcli unmanageV700
from the FSM that is currently managing the V7000 storage node.
DNZFM2273I
Generating SSH keys for admin using command: VALUE_0
DNZFM2274E
SSH public key for admin failed to be generated.
DNZFM2275I
SSH public key for admin was generated successfully
DNZFM2276I
SSH public key for admin was not pushed to the V7000 storage node.
DNZFM2277I
SSH public key for admin was pushed to the V7000 storage node successfully.
DNZFM2283I
Collecting inventory of the farm resource.
DNZFM2284I
Waiting for storage device managed endpoint to be created.
DNZFM2285I
The V7000 storage node with the management address: WERT_0
was not managed succesfully. You might need to wait for the inventory of the storage farm to complete.
DNZFM2286E
Enabling the manufacturing mode on the V7000 storage node was unsuccessful.
DNZFM2287E
Superuser was not created on the V7000 storage node.
DNZFM2288E
Could not generate SSH key for superuser on the V7000.
DNZFM2294E
The backup of the FSM was not successful. Click view log for more details. If the problem persists, contact Support.
DNZFM2295E
Restore of the FSM failed. Check the log and make sure that the backup you are trying to
restore from completed successfully. If the problem persists, contact support.
DNZFM2296E
Restore of the FSM failed. Make sure that the FTP server is on the network and is reachable from the FSM, the credentials for the server are correct, and contains the specified restore image, then try again. If the problem persists, contact support.
DNZFM2297E
The restoration of the FSM was not successful. Make sure the USB device contains the specified
restore image, and attempt to restore the FSM again. If the problem persists, contact Support.
DNZFM2298E
The backup of the FSM was not successful. Make sure that the FTP server is on the network and is reachable
from the FSM, the credentials for the server are correct, and that there is enough storage
space on the server. Attempt to back up the FSM again. View log for more details. If the problem persists, contact Support.
DNZFM2299E
The backup of the FSM was not successful. Make sure that the USB device has sufficient space available
and attempt to back the FSM again. View log for more details. If the problem persists, contact Support.
DNZFM2300E
An I/O error occurred while attempting to run a backup/restore operation. Make sure that the user account being used to run
the operation has permission to perform the operation. Then, attempt to perform the operation again.
If the problem persists, contact Support
DNZFM2302E
Internal error occurred (file not found). Contact Support.
DNZFM2303E
An error occurred while trying to assign the NTP server to the managed chassis.
DNZFM2330E
The USB device could not be mounted. Multiple USB devices might be installed, or the USB device might be already
mounted under a different user. Make sure that only one USB device is connected, and that the USB device is not already
mounted by a different user. Attempt to mount the USB device again. If the problem persists, contact Support.
DNZFM2331E
The USB device could not be mounted because there is no USB device connected to the FSM.
Make sure only one USB device is connected to the FSM, and attempt to mount the USB device.
If the problem persists, contact Support.
DNZFM2400E
An error occurred while attempting to update the configuration for the specified node.
From the Chassis Manager, make sure that the node is functioning and that there is a
working network connection between the FSM and the node.
Attempt to update the configuration again. If the problem persists, contact Support.
DNZFM2401E
An error occurred while attempting to retrieve the configuration for the specified node.
From the Chassis Manager, make sure that the node is functioning and that there is a working
network connection between the FSM and the node.
Attempt to retrieve the configuration again. If the problem persists, contact Support.
DNZFM2402E
An error occurred while trying to determine if the chassis is currently being managed
by the FSM. Attempt to run the command again, if the
problem persists, contact Support.
DNZFM2403E
An error occurred while trying to determine if the chassis can be centrally managed
by the FSM. Attempt to run the command again. If the problem persists, contact Support.
DNZFM2404E
The chassis you are trying to manage is already centrally managed.
DNZFM2405E
The chassis you are trying to manage does not support centralized management. Update the chassis firmware
to a level that supports centralized management. Then attempt the command again. If the problem persists, contact Support.
DNZFM2406E
A specified parameter is not valid or is missing. When you specify to update the chassis to be centrally
managed, you must provide the following information for the CMM: user ID, password, and valid host name or IP address.
Attempt to run the command again specifying all required parameters.
DNZFM2407I
Updating chassis: WERT_0 to be managed centrally.
This command can take up to 4 minutes to complete. The -c, --Uc, --Cu, --Cp and --Rp parameters are the only
valid parameters for the update function, all others will be ignored.
DNZFM2408E
The chassis: VALUE_0 is now centrally managed.
DNZFM2409E
An attempt to centrally manage chassis: VALUE_0 failed.
Check for other messages related to this issue and resolve them. Attempt to run the command again. If the problem persists, contact Support.
DNZFM2410E
The chassis: WERT_0 cannot be centrally managed because it is not currently
being managed by the FSM. Run the smcli command manageChassis to manage the chassis, specifying that it be
centrally managed. The --UpdateToCentralized option is intended to be used on chassis
that are already managed non-centrally.
DNZFM2411E
An error occurred while checking the FSM credentials. Attempt to run the command again, if the
problem persists, contact Support.
DNZFM2412E
User ID: {0} does not have supervisor authority. Attempt to run the command again using a user ID with supervisor authority.
DNZFM2413E
Could not point the chassis user registry to the FSM. Attempt to run the command again with the generate ULA option specified, or use the assignULA CLI command before centrally managing the chassis again. If the problem persists, contact Support.
DNZFM2414E
Could not update FSM user registry with chassis data. Attempt to run the command again, if the
problem persists, contact Support.
DNZFM2415E
Could not update FSM property to centralized. Attempt to run the command again, if the
problem persists, contact Support.
DNZFM2416E
An error occurred checking the chassis recovery password. Attempt to run the command again, if the
problem persists, contact Support.
DNZFM2417E
The FSM is using an external user registry therefore the chassis cannot be
centrally managed.
DNZFM2418I
Attempting to manage chassis: WERT_0 centrally.
This command can take up to five minutes to complete. Specify the -W parameter to determine how the manage
process is progressing. Otherwise, you can check the Chassis Manager in the user interface to determine if
the manage process completed successfully.
DNZFM2419E
An error occurred while centrally managing the chassis. The Flex System Manager could not reach
the chassis component with resource type WERT_0,
IPV6 address WERT_1,
IPV4 address WERT_2,
bay WERT_3. Make sure at least one IP
address assigned to this component can be reached by the FSM. Alternatively,
you can choose the option to generate a unique local address (ULA) when managing the chassis.
Ensure that the chassis component has an IP address that can be reached by the Flex System Manager or
select the generate ULA option and attempt to manage the chassis again.
DNZFM2420W
The chassis WERT_0 is centrally managing the node user accounts for IPMI and SNMP.
If WERT_0 is centrally managed by FSM the management of these SNMPv3 and IPMI accounts will be controlled by
the managed endpoints (IMMv2). The current accounts will be preserved, but you will not be able to manage them from the CMM.
To successfully manage WERT_0 use the force option when using a CLI command or select the OK button to continue when using the web interface.
DNZFM3000E
The feature key file could not be imported. Make sure that the feature key is being imported to the FSM for which it was purchased. Then, attempt to import the feature key again.
DNZFM3001E
The specified feature key file (VALUE_0) could not be opened. Make sure that you specify the full path to a valid key and that the key file is in the specified location. Then attempt to import the key again.
DNZFM3002I
The feature key was imported successfully. You need to restart the FSM to begin using the feature.
DNZFM3003E
An internal error occurred while importing the key. Contact Support.
DNZFM3004E
The feature key file could not be imported. The serial number in the key does not match this system.
DNZFM3005E
The feature key file could not be imported. Feature {0} is not supported on the FSM.
DNZFM3006E
The feature key file could not be imported. The file is not a valid key file and may have been corrupted.
DNZFM3007E
The feature key file could not be imported. Validation of the signature failed. The file has been modified after it was created. Get a new copy of the file and try again.
DNZFM3008E
An internal error occured. Try again or contact Support.
DNZFM5002E
Unable to access the user registry. Verify that you are using the correct password.
DNZFM5003E
A communication failure occurred accessing the user registry. Wait a few seconds and attempt the request again.
If the problem persists, contact Support.
DNZFM5004E
An error occurred during user registry initialization. If the problem persists, contact Support.
DNZFM5005E
Cannot search for the specified entry because the search criteria are not valid. Verify that the search criteria is complete and valid.
Then, attempt to search again.
DNZFM5006E
Cannot create the specified user because one or more parameters are not valid. Verify that all parameters are valid and attempt to
create the user again. If the problem persists, contact Support.
DNZFM5007E
Cannot create or delete the specified role because one or more parameters are not valid.
Verify that all parameters are valid and attempt to add or delete the role again.
If the problem persists, contact Support.
DNZFM5008E
Cannot create the specified role because the role information is not complete. Role name, type, and permissions are required.
Verify that the role information is complete and valid. Then attempt to create the role again.
DNZFM5009E
Unable to obtain roles from the user registry because FSM could not communicate with the user registry. If the problem persists, contact Support.
DNZFM5010E
Predefined roles cannot be modified. Select a different role to be changed.
DNZFM5011E
The specified role type VALUE_0 is not valid. Specify a valid role type, such as CMM, IMM or FSM.
DNZFM5012E
The specified user {0} exists. Choose a different user name and try the request again.
DNZFM5013E
The specified role {0} type {1} exists. Choose a different role name and try the request again.
DNZFM5015E
An exception occurred while modifying a role. No changes have been made to the role. Verify
that the role has at least one set of permissions associated with it. If the role
is associated with a chassis, make sure that the chassis is available and being managed
by the FSM. Then, attempt to modify the role again.
DNZFM5017E
The user group {0} cannot be changed because it does not exist.
DNZFM5018E
The user group {0} cannot be deleted because it does not exist.
DNZFM5019E
A FSM internal error occurred in the user management component. Contact Support.
DNZFM5020E
A FSM internal error (null parameter) occurred in the user management component. If the problem persists, contact Support.
DNZFM5021E
The selected chassis is already managed by FSM. Select a different chassis to manage.
DNZFM5022E
An internal error occurred while attempting to put a chassis under management. This might be a network
communication error, a problem with the user registry on the CMM, or the CMM might not be available.
Attempt to put the chassis under management again. If the problem persists, contact Support.
DNZFM5023E
An internal error occurred while attempting to put a chassis under management. This might be a problem
with the user registry on the FSM. If the problem persists, contact Support.
DNZFM5024E
An internal error occurred while adding a new element to the user registry. If the problem persists, contact Support.
DNZFM5025W
An attempt was made to remove a chassis from FSM management,
but the chassis was not found in the list of managed chassis.
DNZFM5026E
An error occurred while attempting to locate branch {0} in the user registry. The branch does not exist. Verify that the chassis is under FSM
management and try the request again. If the problem persists, contact Support.
DNZFM5027E
An internal error occurred while attempting to put a chassis under management. The FSM could not create a new branch: {0} in the user registry.
Attempt to put the chassis under management again. If the problem persists, contact Support.
DNZFM5028E
An internal error occurred while attempting to change the internal system-defined user registry configuration. If the problem persists, contact Support.
DNZFM5029E
One or more errors occurred while updating the system password. The system will be restarted now.
For more information, contact Support.
DNZFM5030E
An attempt was made to place this FSM under management, which is not allowed. Make sure that you are using
the IP address or host name for a CMM in a chassis that has connectivity to the FSM.
If the problem persists, contact Support.
DNZFM5031E
The IP address for the user registry on the CMM is not valid. If the problem persists, contact Support.
DNZFM5032E
A user with the specified user group name {0} exists. Choose a different user group name and try the request again.
DNZFM5033E
A user group with the specified user name {0} exists. Choose a different user name and try the request again.
DNZFM5034E
A specified permission is not valid for role type {0}. Specify a valid permission.
DNZFM5035E
User {0} could not be created. Verify that the group to which the user belongs is valid and that
the user roles and resources exist. Then attempt to create the user again. If the problem persists, contact Support.
DNZFM5036E
An internal error occurred while attempting to access the password policy for the FSM. Contact Support.
DNZFM5037E
An internal error occurred while attempting to put a chassis under management. The FSM could not
create one of the required objects: {0} in the user registry. Attempt to put the chassis under management again.
If the problem persists, contact Support.
DNZFM5038E
The specified {0} role {1} does not exist. Choose a different role and try the request again.
DNZFM5039E
The user has insufficient permissions to perform the requested action.
DNZFM5040E
An internal error occurred while attempting to update the identifier of a chassis that is
under management. The chassis with identifier {0} was not found in the list of managed chassis
maintained by the user management component. If the problem persists, contact Support.
DNZFM5041E
An error occurred while attempting to retrieve the FSM authentication mode (remote or local).
Run the resetToLocal command to recover. Then, run the remote user registry setup wizard if
you want to use an external user registry. If the problem persists, contact Support.
DNZFM5042E
The password provided is incorrect. Re-enter the current system password.
DNZFM5043E
User {0} is a FSM required user and cannot be deleted.
DNZFM5044E
The syntax for the role resources or role scope is not correct. Verify that the command contains at least one
compute node bay or I/O bay. When adding a user to an IMM type role, be sure to include a centrally managed chassis as well.
DNZFM5046E
An internal error occurred while attempting to retrieve the password policy information for the FSM. Contact support.
DNZFM5047E
Unable to update the LDAP attribute. The schema policy does not allow the requested action.
DNZFM5048E
The user {0} cannot be changed because it does not exist.
DNZFM5049E
The user {0} cannot be deleted because it does not exist.
DNZFM5050E
The role {0} cannot be changed because it does not exist.
DNZFM5051E
The role {0} cannot be deleted because it does not exist.
DNZFM5052E
The user {0} cannot be created because user group {1} does not exist in the user registry.
DNZFM5053E
The user {0} cannot be created because role {1} does not exist.
DNZFM5054E
The user {0} cannot be modified because user group {1} does not exist in the user registry.
DNZFM5055E
The user {0} cannot be modified because {1} role {2} does not exist.
DNZFM5056E
The specified user group {0} exists. Choose a different user group name and try the request again.
DNZFM5057E
The user group {0} cannot be created because user {1} does not exist.
DNZFM5058E
The user group {0} cannot be created because {1} role {2} does not exist.
DNZFM5059E
The user group {0} cannot be modified because user {1} does not exist.
DNZFM5060E
The user group {0} cannot be modified because {1} role {2} does not exist.
DNZFM5061E
The user name VALUE_0 is not valid. The name must begin with
an alphabetic character, and it must contain only a-z,A-Z,0-9, - or _. It must be no longer than 32 characters. Enter a valid user name.
DNZFM5062E
The user group name VALUE_0 is not valid. The name cannot
contain certain non-alphabetic characters, such as ! # $ & ( ) + = | ; ' < > , . ? / .
Enter a valid user group name.
DNZFM5063E
The role name VALUE_0 is not valid. The name cannot
contain certain non-alphabetic characters such as ! # $ & ( ) + = | ; ' < > , . ? / .
Enter a valid role name.
DNZFM5065E
User group {0} is a required user group and cannot be deleted.
DNZFM5066E
An error occurred while updating the user's password on the local file system. If the problem persists, contact Support.
DNZFM5067E
User {0} is a required user and cannot be disabled.
DNZFM5068E
The specified password for user {0} is not correct. Enter the correct password.
DNZFM5069E
The new password does not meet the password policy criteria. Re-enter a different password.
DNZFM5070E
The specified new password has been used recently. The password policy in
effect for the FSM controls the number of previously used passwords that cannot be used.
Specify a different password.
DNZFM5071E
The password cannot be changed because it was modified recently. The password policy in
effect for the FSM controls how often passwords can be changed. Wait the required time
interval and attempt to change the password again.
DNZFM5072E
User {0} is a required user and cannot be modified.
DNZFM5073E
User group {0} is a required user group and cannot be modified.
DNZFM5074E
User group {0} is a required user group and its roles cannot be modified.
DNZFM5075E
User {0} is a FSM required user and its membership cannot be modified.
DNZFM5076E
The new password must have at least {0} characters.
DNZFM5077E
To change or reset the password for the user root, select the Change System Password task under the Administration tab
or use the chFsmSysPwd command.
DNZFM5078E
Changing the password for user {0} is not supported.
DNZFM5079I
Users {0} were deleted. Users {1} were not deleted. Users that are not deleted do not exist or are in use.
DNZFM5080I
User groups {0} were deleted. User groups {1} were not deleted. User groups that are not deleted do not exist.
DNZFM5081E
The specified password does not meet the criteria for a secure password for reason {0}.
Reason 1: Password must contain at least three of the following characters in
any combination:
one lowercase alphabetic character, one uppercase alphabetic character, one numeric character, one special character.
Reason 2: Password must contain no more than three of the same characters used consecutively.
Reason 3: Password must not be a repeat or reverse of the associated user ID.
Reason 4: Password must contain at least 2 characters that are different from the previous password.
DNZFM5082E
User group {0} cannot be removed. All users must be a member of this user group.
DNZFM5083E
The {0} user group must be specified for the user. All users must be a member of {0} user group.
DNZFM5084E
Users belonging to the FSM {0} role must be in the {1} user group.
DNZFM5085E
The security policy level for the FSM is set to secure. The password policy settings do not meet the criteria for the secure policy level.
Use the setFsmSecPolicy command to set the FSM security policy level.
DNZFM5086E
User {0} is a FSM user and cannot be specified.
DNZFM5087E
The account for user {0} is locked. See the system administrator for help.
DNZFM5088E
The password provided is incorrect. Retry the command using the correct system password.
DNZFM5089E
An error occurred while importing the certificate during external user registry setup.
Check the file path of the certificate to make sure it is correct.
DNZFM5206E
Cannot create entry {0} because one or more parameters set for the object are not valid. Verify that all parameters are valid and attempt to
create the entry again. If the problem persists, contact Support.
DNZFM5207E
Usage error: the VALUE_0 can only be used if the VALUE_1 option is also specified.
DNZFM5208E
No options were specified when invoking the command.
DNZFM5209E
The command terminated due to an unexpected internal error. If the problem persists, contact Support.
DNZFM5210E
The VALUE_0 option requires a value. Run the command again, specifying a value for the option.
See the command help for the correct usage.
DNZFM5211E
The value {0} is not valid for the specified option. See the command help for the correct usage.
DNZFM5213E
The FSM is using an external user registry therefore the chassis cannot be
centrally managed. Do not select the chassis to be centrally managed and try the request
again.
DNZFM5214I
There are no centrally managed chassis.
DNZFM5215E
The CLI command lsCentrallyManagedChassis failed for this reason: {0}.
DNZFM5216E
The CLI command rmCentrallyManagedChassis failed for this reason: {0} If the problem persists, contact Support.
DNZFM5217I
Chassis with UUID: {0} was removed from centralized management successfully.
You must now reaquire access with credentials for the chassis.
DNZFM5218E
The UUID (parameter -u | --uuid) is required. Attempt to run the command again, specifying a valid UUID.
DNZFM5219E
User name error: VALUE_0 is not a valid user name.
The user name must begin with an alphabetic character, must contain only a-z,A-Z,0-9, - or _, and must be no longer than 32 characters.
DNZFM5220E
Chassis error: VALUE_0 is not a centrally managed chassis.
Use the lsCentrallyManagedChassis CLI command to find all centrally managed chassis.
DNZFM5221E
Role error: VALUE_0 is not a valid role entry.
The role must have the format role-type:role-name[:role-target].
DNZFM5222E
Extending and removing roles cannot be specified together. Choose to extend or to remove roles.
DNZFM5223E
Extending and removing groups cannot be specified together. Choose to add or to remove groups.
DNZFM5224E
SSH time out value must be non-negative and less than 2147483647. Enter a valid value for SSH time out.
DNZFM5225E
Role {0} that is type {1} must contain at least one chassis.
DNZFM5226E
Cannot change, delete, add, or remove user group {0} because it does not exist.
DNZFM5227I
You will need to restart the FSM to activate this change.
DNZFM5249E VALUE_0 is not a valid user group name.
A user group name cannot contain certain non-alphabetic characters such as ! # $ & ( ) + = | ; ' < > , . ? / .
DNZFM5250E VALUE_0 is not a valid role name.
A role name cannot contain certain non-alphabetic characters such as ! # $ & ( ) + = | ; ' < > , . ? / .
DNZFM5272E
Extending and removing users cannot be specified together. Choose to add or to remove users.
DNZFM5273I
Some settings for user {0} could not be changed. See the previous errors for specific issues with those settings.
DNZFM5274I
Some settings for user group {0} could not be changed. See the previous errors for specific issues with those settings.
DNZFM5275E
Old and new passwords are required parameters.
DNZFM5276I
The system password was changed successfully. System is being restarted for the change to take effect.
DNZFM5277I
Are you sure that you want to change the system password and restart the Flex System Manager? (Y,N)
DNZFM5278I
You entered {0}. The system will be restarted after the password is changed.
DNZFM5279I
You entered {0}. The command is canceled.
DNZFM5280E
Userid: {0} or password: {1} is incorrect. If a valid userid is given, that account may
become locked if too many attempts are made with an incorrect password. Try the request again
with caution.
DNZFM5281E
An internal error occurred attempting to unmanage the CMM: {0}. The LDAP client configuration was not
reset.
DNZFM5282E
The VALUE_0 option is limited to {1} characters. Run the command again, specifying a different value.
DNZFM5283E
Usage error: At least one value listed for the scope is not valid.
Specify c1 for a chassis, bay 1 to 10, or iobay 1 to {0}.
DNZFM5284E
The specified UUID: {0} is not valid. Try the command again specifying a valid UUID. Run the CLI command lsCentrallyManagedChassis and select the appropriate UUID from the output.
DNZFM5285E
The attempt to remove chassis with UUID: {0} from centralized management was partially successful. The Flex System Manager now recognizes the CMM as decentralized, however some operations failed while decentralizing the chassis. Make sure the chassis is functioning and connected to the network.
Then, log in to the chassis command-line interface using the RECOVERY_ID user account. Verify that user registry authentication is set to local authentication (CMM command: accseccfg -am local -T mm[p]), verify that the SSL client is disabled (CMM command: sslcfg -client
disabled -tc1 remove -T mm[p]) and verify that the CMM local accounts are not disabled (CMM command: fsmcm -off -T mm[p]). If the problem persists, contact Support.
DNZFM5300E
This Flex System Manager is configured to use an external registry. This command is not supported for use with an external registry.
Instead, you must use the commands that are available with the external registry.
DNZFM5301E
The name WERT_0 is not a valid name for this command. Review the command help then try the command again.
DNZFM5302E
The Flex System Manager Operating System and user registry passwords are not synchronized. Run this command again using a new password that meets the Password policies set on this Flex System Manager.
DNZFM5303E
This Flex System Manager is configured to use the internal registry. This command is not supported for use with an internal registry.
Instead, you must use the commands that are available with the internal registry.
DNZFM8750E
A valid operating system image file in an ISO format must be specified.
DNZFM8751E
Only one operating system image file may be specified at a time.
DNZFM8752E
The specified operating system image does not exist.
DNZFM8753E
An internal error occurred while importing the image. Attempt the command again. If the problem persists, contact Support.
DNZFM8754E
The deployment service encountered a problem while importing the image. Restart the FSM and attempt the command again. If the problem persists, contact Support.
DNZFM8755E
The specified operating system image is not valid. Attempt the command again, specifying a supported operating system image.
DNZFM8756W
An expected return code was returned while importing the image. Return code: {0}.
DNZFM8758I
The import operation will continue to run in the background.
DNZFM8759E
The imported operating systems could not be retrieved.
DNZFM8760W
Information is still being collected about the FSM and its managed chassis.
DNZFM8761E
Invalid task activation context is passed. Retry the operation with valid activation context.
DNZFM8762E
At least one compute node must be specified for deploying image. Retry the operation with valid compute node.
DNZFM8763E
The number of image deployments in progress (WERT_0) and the newly requested image deployments (WERT_1) exceeds the maximum number of images that can be deployed concurrently. You can deploy a maximum of WERT_2) images concurrently.
DNZFM8764E
Required image deployment data is missing in the task activation context.
DNZFM8766E
An internal error occurred while the FSM was attempting to activate the image deployment process (invalid image deployment data WERT_0).
DNZFM8767E
An internal error occurred while attempting to deploy an operating system image (FEHLERMELDUNG).
DNZFM8768E
The image for compute node WERT_0 cannot be deployed. An internal error (missing image deployment data) occurred while attempting to deploy the operating system image for the compute node.
DNZFM8769E
An internal error occurred while attempting to deploy an operating system image.
DNZFM8770E
The operating system deployment process did not complete for compute node WERT_0. The image deployment process for this compute node did not complete because another image deployment is already in progress for this compute node.
DNZFM8771E
The operating system deployment process did not complete for compute node WERT_0. The image deployment process for this compute node did not complete because it is not a server resource.
DNZFM8772E
The operating system deployment process did not complete for compute node WERT_0 (VALUE_1). The image deployment process for this compute node did not complete because the FSM cannot identify the MAC address for this compute node. Collect inventory of this compute node and attempt to deploy the image again.
DNZFM8773E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node did not complete because this compute node is not unlocked. From the FSM, request access to the compute node and attempt to deploy the image again.
DNZFM8774E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node did not complete because this compute node is offline. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node. Perform verify connection to the compute node and attempt to deploy the image again.
DNZFM8775E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node did not complete because this compute node does not have an associated restart or power-on task. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node. Perform verify connection to the compute node and attempt to deploy the image again.
DNZFM8776E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node did not complete because the FSM cannot determine which chassis is managing this compute node. Collect inventory on the chassis managing this compute node and attempt to deploy the image again.
DNZFM8777E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node did not complete because the chassis WERT_2 (WERT_3) managing this compute node is not unlocked. Perform request access to the chassis and attempt to deploy the image again.
DNZFM8778E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node did not complete because the chassis WERT_2 (WERT_3) managing this compute node is offline. Make sure that the chassis is functioning and that there is a working network connection between the FSM and the chassis. Perform verify connection to the chassis and attempt to deploy the image again.
DNZFM8779I
Image deployment lock acquired for compute node WERT_0 (WERT_1).
DNZFM8780E
An exception occured while acquiring an image deployment lock for compute node WERT_0. The associated error is FEHLERMELDUNG.
DNZFM8781I
Pre-deployment validation completed sucessfully for all specified compute nodes.
DNZFM8782E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node has timed out while preparing for image deployment at WERT_2. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8783I
All valid targeted compute nodes preparation for image deployement has completed sucessfully.
DNZFM8784I
Started monitoring WERT_0 image deployments for compute nodes WERT_1.
DNZFM8785E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node has timed out because its status has not been updated from WERT_2 in the last WERT_3 minutes. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8786I
Image deployment has completed successfully on the compute node WERT_0 (WERT_1).
DNZFM8787I
Image deployment has completed successfully for all specified compute nodes.
DNZFM8788E
The operating system deployment process did not complete for the compute node. The image deployment process did not complete because the Flex System Manager could not create a node profile for this compute node.
DNZFM8789E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node did not complete because an internal exception occured while creating a node profile for this compute node.
DNZFM8790E
The operating system deployment process did not complete for the compute node. The image deployment process did not complete because the Flex System Manager could not get node profile information for this compute node.
DNZFM8791E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node did not complete because an node profile was not found for this compute node.
DNZFM8792W
Failed to get node profile infromation for the compute node.
DNZFM8793E
The operating system deployment process did not complete for the compute node. The image deployment process did not complete because the Flex System Manager could not create a bootable ISO image for this compute node.
DNZFM8794E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process did not complete because the Flex System Manager could not create a bootable ISO image for this compute node.
DNZFM8795E
The operating system deployment process did not complete for the compute node. The image deployment process did not complete because the Flex System Manager could not mount the remote media to this compute node. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8796E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process did not complete because the Flex System Manager could not mount the remote media WERT_2 to this compute node. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8797E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process did not complete because the Flex System Manager could not mount the remote media WERT_2 to this compute node (error code of WERT_3). Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8798E
Failed to unmount bootable ISO due to missing information about the compute node.
DNZFM8799E
Could not unmount remote media WERT_0 from compute node WERT_1 (WERT_2).
DNZFM8800E
An WERT_0 error occured during the unmount of remote media WERT_1 from compute node WERT_2 (WERT_3).
DNZFM8801E
The operating system deployment process did not complete for the compute node. The image deployment process did not complete because the Flex System Manager could not modify the UEFI boot sequence for this compute node. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8802E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process did not complete because the Flex System Manager could not modify the UEFI boot sequence for this compute node. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8803E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process did not complete because this compute node did not restart.
DNZFM8804E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process did not complete because the Flex System Manager cannot restart or power on this compute node. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8805E
Unable to determine FSM system administrator user ID for the remote media mount operation.
DNZFM8806E
Unable to determine FSM password for the system administrator user account WERT_0.
DNZFM8807E
An internal error occurred due to an invalid or missing value for WERT_0 property in FlexCat.properties file.
DNZFM8808E
An internal error occurred (JSON response WERT_0)
DNZFM8819E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). An error occurred while trying to restart the compute node. Wait several minutes and verify that the image was successfully deployed on the compute node by attempting to discover the operating system through the IBM Flex System Manager.
DNZFM8820E
The operating system deployment process did not complete for compute node WERT_0 (WERT_1). The image deployment process for this compute node has timed out because its status has not been updated from WERT_2 in the last WERT_3 minutes. Make sure the compute node is functioning and that there is a working network connection between the FSM and the compute node.
DNZFM8821I
Discovering the newly installed operating system WERT_0 running on compute node WERT_1 (WERT_2).
DNZFM8822E
The newly installed operating system WERT_0 running on compute node WERT_1 (WERT_2) could not be discovered.
DNZFM8823I
Image deployment completed successfully for compute node WERT_0 (WERT_1).
DNZFM8824I
Image deployment completed with errors. Errors occurred while attempting to deploy the operating system to the compute nodes. Check previous messages in this job log for information about the errors.
DNZFM8825E
Global settings have not been applied. The IP assignments mode for image deployments cannot be changed while there are images currently being deployed. Wait until all images have been deployed and retry the operation.
DNZFM8826E
The operating system cannot be deployed for compute node WERT_0 (WERT_1). The installed IMM firmware version WERT_2 is not at or above required minimum version of WERT_3. Update the firmware for this compute node and attempt to deploy the operating system image again.
DNZFM8827E
The operating system cannot be deployed for compute node WERT_0 (WERT_1). The installed UEFI firmware version WERT_2 is not at or above required minimum version of WERT_3. Update the firmware for this compute node and attempt to deploy the operating system image again.
DNZFM8828E
The operating system cannot be deployed for compute node WERT_0 (WERT_1). The IBM Flex System Manager cannot deploy the operating system to the compute node because there is not enough free storage space in WERT_2 on IBM Flex System Manager for hosting the bootable ISO image.
DNZFM8829E
The specified operating system image name was not found in IBM Flex System Manager inventory.
DNZFM8830E
One or more required parameters is missing. For more information about the required options, see the help that is available for the command.
DNZFM8831E
One or more parameters are not valid. For more information about the options, see the help that is available for the command.
DNZFM8832E
The xCat server restart operation completed with an error. Return code: {0}.
DNZFM8834I
The specified operating system image name was found in IBM Flex System Manager inventory.
DNZFM8835E
The specified operating system profile cannot be deleted.
DNZFM8836E
The specified operating system profile cannot be deleted. An internal error occurred (REST call) while attempting to delete the operating system profile.
DNZFM8837E
No operating system image was specified to be deleted.
DNZFM8838E
Only one operating system image at a time can be specified for deletion.
DNZFM8840E
The maximum number of imported operating systems has been reached. IBM Flex System Manager supports a maximum of WERT_0 imported operating system images. Delete an operating system image, using smcli deleteosimage, and attempt the import operation again.
DNZFM8842E
The image deployment service is disabled.
DNZFM8843E
The default operating system credential have not been changed. The default opreating system credential cannot be changed while there are images currently being deployed. Wait until all images have been deployed and retry the operation.
DNZFM8844E
The default operating system credential have not been changed. An error occured while updating the default opreating system credential for key WERT_0.
DNZFM8845E
Failed to get the default credentials to be used during operating system deployment.
DNZFM8846I
Discovery of ESXi operating system using IPv6 address is not supported. The newly installed operating system running on compute node WERT_0 (WERT_1) cannot be auto discovered. Manually discover this operating system using IPv4 address.
DNZFM8847E
The operating system image WERT_0 cannot be imported. The IBM Flex System Manager image repository directory WERT_1 does not have enough free space to import the given operating system image of size WERT_2. Delete unused operating system image, using smcli deleteosimage, and attempt the import operation again.
DNZFM9001E
Unable to generate security certificate because of an internal error (command failure). Make sure that your user ID is assigned to a role of SMAdministrator (smadmin group) and attempt to generate the certificate again. If the problem persists, contact Support.
DNZFM9003E
Unable to regenerate user registry certificates. Make sure that the specified user ID has sufficient permissions to regenerate a certificate. Then attempt to regenerate the certificate again. If the problem persists, contact Support.
DNZFM9004E
Unable to generate user registry certificates. Make sure that the specified user ID has sufficient permissions to generate a certificate. Then attempt to generate the certificate again. If the problem persists, contact Support.
DNZFM9005E
An internal error occurred (exception) while generating user registry certificates during centralized management setup. Contact Support.
DNZFM9006E
An internal error occurred (failed return code) while generating user registry certificates during centralized management setup. Contact Support.
DNZFM9007E
An internal error occurred while processing a security policy. Error: {0} occurred in method: {1}. Contact Support.
DNZFM9008E
An internal error occurred while attempting to get the FSM security policy level. Contact Support.
DNZFM9009E
The object identifier (parameter -o | --oid) value {0} is not valid. It must be the object identifier for a CMM that is currently managed by the FSM. Attempt to run the command again, specifying a valid object identifier.
DNZFM9010E
The security level (parameter -l | --level) value {0} is not supported. Attempt to run the command again, specifying legacy or secure for the security level.
DNZFM9011E
The security level (parameter -l | --level) is required. Attempt to run the command again, specifying a valid security level.
DNZFM9012E
The object identifier (parameter -o | --oid) is required. Attempt to run the command again, specifying a valid object identifier.
DNZFM9013E
Command failed with exception: {0}. Contact Support.
DNZFM9014E
The specified security policy for CMM: {0} failed with return code: {1}.
DNZFM9015E
The specified security policy for the FSM failed with return code: {0}.
DNZFM9016I
The security policy for CMM: {0} was successfully set to: {1}.
DNZFM9017I
The security policy for the FSM was successfully set to: {0}.
DNZFM9018E
The security policy level for the FSM must be set to legacy to change legacy protocols.
DNZFM9019E
A required parameter was not specified. Attempt to run the command again, specifying either the enable or disable parameter (-E|--enable or -D|--disable).
DNZFM9020E
The specified protocol {0} is not a supported protocol. Run the command again, specifying a valid protocol.
DNZFM9021I
The {0} protocol has been disabled successfully.
DNZFM9022E
Unable to disable {0} protocol. Attempt to run the command again. If the problem persists, contact Support.
DNZFM9023I
The {0} protocol has been enabled successfully.
DNZFM9024E
Unable to enable {0} protocol. Attempt to run the command again. If the problem persists, contact Support.
DNZFM9025E
An internal error occurred while importing a certificate during external user registry setup. Refer to previous messages in the log for specific details. If no earlier messages exist, contact Support.
DNZFM9026W
While removing a certificate the following exception occurred: {0}. This may occur in normal processing. If there are no other issues, ignore this warning.
DNZFM9027W
The security policy is already at the requested level. Try the request again, specifying a different level.
DNZFM9028W
FSM security policy level was updated to {0}, but any chassis that were centrally managed did not get updated to the new policy. Use the Web interface to check the security policy of the managed chassis and update it if necessary.
DNZFM9029W
The following unsecure protocol: {0} is active on the FSM so the security policy level cannot be upgraded to: {1}. Use the chLegacyProtocol CLI command to disable the unsecure protocol, and try the request again.
DNZFM9030E
An internal error occurred while attempting to get the chassis security policy level.
DNZFM9031E
The following exception occurred while attempting to get or set the chassis security policy. Contact Support. Exception: {0}.
DNZFM9032E
An internal error occurred while attempting to get the chassis security policy state. The state {0} is not supported.
DNZFM9040E
An error occurred while changing the trust/key store password (internal error). Contact Support.
DNZFM9041E
Unable to change the trust/key store password. Make sure that the previous password is correct, and that the new password complies with the current FSM security policy.
If the problem persists, contact Support.
DNZFM9042E
An error occurred getting the security policy status information for CMM {0}.
DNZFM9043E
An internal error occurred (exception) while attempting to set or get a security policy. The exception is: {0}.
DNZFM9044E
An internal error occurred while parsing the results from setting or getting the CMM security policy.
DNZFM9045E
Security level check for chnetcfg was successful.
DNZFM9046E
An error occurred while getting the key store or trust store password (internal error). Contact Support.
DNZFM9047E
The TFTP server cannot be started because the required port is already in use. Verify that the Update Manager is not using this FSM as a TFTP server and try again.
To verify this, go to the Home page, select the Plug-ins tab and then select Update Manager. From the Common Tasks section, select Configure Settings and make sure that the FSM is not used as a TFTP server.
DNZFM9048E
The TFTP server cannot be stopped because it is in use by another process. Verify that the Update Manager is not using this FSM as a TFTP server and try again.
To verify this, go to the Home page, select the Plug-ins tab and then select Update Manager. From the Common Tasks section, select Configure Settings and make sure that the FSM is not used as a TFTP server.
DNZFM9100W
Security services did not start correctly. Wait a few minutes and try the command again. Then, restart the FSM. If the problem persists, contact Support.
DNZFM9101I
This command is not supported on the Flex System Manager.
DNZFM9102W
The Flex System Manager is managing one or more chassis.
When you change the network interface for the management network, you must unmanage all chassis that are managed by the Flex System Manager
and then manage the chassis again.
DNZFM9103W
If the network interface for the management network is configured to use DHCP, the management interface IP address can change when the DHCP lease expires. If the address does change you will be required to unmanage all chassis that are managed and then manage all chassis again. Alternatively, you can change the management interface to a static IP address, you can make sure that the DCHP server configuration is set so that the DHCP IP address is based on a MAC address, or you can make sure that the DHCP server configuration is set to prevent the DHCP lease from expiring.
DNZFM9104W
The Flex System Manager is managing one or more chassis.
When the Flex System Manager LDAP certificate is reset, you must unmanage all chassis that are managed by the Flex System Manager
and then manage the chassis again.
DNZPWZ050E
The duration to continue checking for updates was not specified.
DNZPWZ051E
The duration to continue checking for updates was not specified.
DNZPWZ052E
The specified duration to continue checking for updates is not greater than zero.
DNZPWZ053E
The specified duration to continue checking for updates is not greater than zero.
DNZPWZ055E
The specified duration to continue checking for updates is not valid. A number between VALUE_0 and VALUE_1 is required for the duration.