This topic lists error messages for the ports command.
See Common errors for a list of error messages that apply to all commands.
| Error message | Definition |
|---|---|
| A certificate must first be in place before SSL can be enabled. | The user tries to enable SSL before setting up a valid SSL certificate. |
| An SSH server key must first be in place before SSH can be enabled. | The user tries to enable SSH before setting up a valid SSH server key. |
| Duplicate port number entered. | The user tries to enter a command with a port number that is already in use. |
| Enabling SNMPv1 failed | The SNMPv1 configuration does not meet required criteria. |
| Enabling SNMPv3 failed | The SNMPv3 configuration does not meet required criteria. |
| Error: A community is configured without an IP address or host name. Please use ‘snmp' command for snmp configuration. | Attempted to configure community without an IP address or host name. |
| Error: A duplicate community name is configured. Please use ‘snmp' command for snmp configuration. | Attempted to configure a community name that was already defined. |
| Error: At least one configured community is required to enable SNMPv1. Please use ‘snmp' command for snmp configuration. | Attempted to enable SNMPv1 without configuring at least one community. |
| Error: IP address of 0.0.0.0, 0::0 is allowed only when the first community is configed as Get or Set access type. Please use ‘snmp' command for snmp configuration. | IP address of 0.0.0.0 or 0::0 is allowed only when the first community is configured as a GET or SET access type. |
| Error: System contact must be defined to enable SNMPv1. Please use ‘snmp' command for snmp configuration. | Attempted to enable SNMPv1 without defining a system contact. |
| Error: System location must be defined to enable SNMPv1. Please use ‘snmp' command for snmp configuration. | Attempted to enable SNMPv1 without defining a system location. |
| Error: System contact must be defined to enable SNMPv3. Please use ‘snmp' command for snmp configuration. | Attempted to enable SNMPv3 without defining a system contact. |
| Error: System location must be defined to enable SNMPv3. Please use ‘snmp' command for snmp configuration. | Attempted to enable SNMPv3 without defining a system location. |
| Error sanity checking of SNMP configuration. | An error occurs while the management module is checking the SNMP configuration. |
| Invalid parameter. The timeout must be between 0 and 4294967295 seconds. | The user tries to enter a timeout that is outside of the valid range. |
| Maximum connections can not exceed 20. | A user attempts to configure more than 20 connections. |
| No valid server certificate is in place for Secure TCP Command Mode. Use the sslcfg command to generate a certificate. | A user tries to change the state of stcm without a valid certificate in place. |
| Port number out of range. | A user tries to enter a port number that is outside of the valid range. |
| Resetting all ports to default values failed. | An error occurs while the management module is resetting all ports to their default values. |
| Secure SMASH CLP cannot be enabled without a valid SSH server key in place. | The user tries to enable the secure SMASH CLP before setting up a valid SSH server key. |
| The -prior option has been deprecated.
Please use the -rpp option instead. where prior is kvmp, rdp, rdocp, or sdsp. |
The user tries to enter a command with a deprecated option, such as -kvmp, -rdp, -rdocp, or -sdsp. |
| The total number of secure and legacy connections of TCP Command Mode cannot exceed 20 | A user attempted to configure more than 20 TCP Command Mode connections. |
| This I/O module does not support port speed configuration. | The user tries to enter a command for a speed configuration which not supported by the targeted I/O module. |
| Warning: Communication with IBM Director via Secure TCP Command Mode has been disabled. | A user has disabled the Secure TCP command mode. |
| Warning: Communication with IBM Director via TCP Command Mode has been disabled. | A user has disabled the TCP command mode. |