|
|
This appendix lists the error messages displayed by the Cisco 6510 Service Selection Gateway (Cisco 6510), explains the meaning of the message, and presents a suggested course of action to fix the error.
The following list shows each Cisco 6510 error message, in alphabetical order. Some of the messages are console messages, and other messages are syslog messages. Syslog messages are indicated with the notation "syslog message" in parentheses. An explanation of the possible cause of the error and a suggested course of action are provided for each message.
Explanation The system does not have enough memory to process an accounting message.
Recommended Action Try rebooting the system. If the message appears again, the physical memory on the unit might have become corrupted.
Explanation The accounting process did not have enough memory to process a retransmit queue.
Recommended Action Try rebooting the system. If the message appears again, the physical memory on the unit might have become corrupted.
Explanation The burnimg command was entered, but the Cisco 6510 was unable to open the indicated image file.
Recommended Action Make sure that the disk containing the image file is properly inserted into the Cisco 6510's drive. Check to make sure that you specified the correct filename for the image file with the burnimg command and that the filename is 8 characters or less. If the file still cannot be read, the file might have become corrupted. Contact Cisco to obtain another copy of the image file.
Explanation The failover process failed to connect to the standby unit. Possible causes are: (1) the failover cable is not connected correctly; (2) the standby unit is not powered on and functional; (3) the failover configuration specified the wrong IP address for the standby unit.
Recommended Action Verify that the failover connector is correctly connected to the failover port on both the active and the standby unit. Verify that the standby unit is powered on and is functional. Make sure that the IP address for the standby unit has been correctly set with the failover set command on the active unit.
Explanation If this message appears the first time that you start the Cisco 6510, this is not cause for concern. If the message occurs during system initialization after the system configuration has been saved using the config save command, this indicates a serious hardware problem.
Explanation A Cisco 6510 internal procedure did not have enough memory to execute.
Recommended Action Reboot the Cisco 6510. If the message reoccurs, this indicates that the physical memory on the system might be corrupted.
Explanation This error indicates a serious hardware problem.
Recommended Action Reboot the Cisco 6510. If the message occurs again, contact your support representative.
Explanation You entered the burnimg command to save the image file to the BIOS, but the operation failed.
Recommended Action Try the operation again. If the error persists, contact your support representative.
Explanation You entered a command or configuration parameter that specifies an IP address, but the IP address was not in the proper format.
Recommended Action Enter the command without a parameter value to get instructions on the proper format for IP addresses.
Explanation You entered the failover switchover command, but the unit failed to switch from the standby state to the active state.
Recommended Action Verify failover is enabled by entering the failovertest command on both units. If everything looks correct, enter failover cpconfig on the active unit and make sure the update occurs on the standby unit. Then, enter failover switchover again.
Explanation You entered the failover switchover command, but the unit failed to switch from the active state to the standby state.
Recommended Action Verify failover is enabled. Verify failover status on both units. If everything looks correct, enter failover cpconfig on the active unit and make sure the update occurs on the standby unit. Then, enter failover switchover again.
Explanation You entered the burnimg command, but did not specify a filename for the image file.
Recommended Action Specify the filename for the image file with the -f parameter (burnimg -f filename). For information on the burnimg command, see the "burnimg" section.
Explanation You entered logtarget -t syslog, but did not specify an IP address for the syslog server.
Recommended Action Reenter the command and specify an IP address for the syslog server (logtarget -t syslog -d ip_address). For information on the logtarget command, see the "logtarget" section.
Explanation You entered the logtarget command but did not specify a target with the -t parameter.
Recommended Action Reenter the command and specify a logging target with the -t parameter (logtarget target_num -t target). For information on the logtarget command, see the "logtarget" section.
Explanation The User Control Point (UCP) is not responding to Remote Access Dial-In User Service (RADIUS) accounting requests.
Recommended Action Check the Cisco 6510 configuration for RADIUSRemotePort and make sure that you have specified the correct IP address(es) and port number(s) for the UCP RADIUS accounting service. If the IP address(es) and port number(s) are correct, verify that the UCP accounting service is running. If the problem persists, there is most likely a network problem affecting the connection between the Cisco 6510 and the UCP.
Explanation You entered the burnimg command to update the system, but the system could not read the image file. The image file might have become corrupted on the disk.
Recommended Action Verify that the image file on the upgrade disk is readable. Contact your support representative if you need to obtain another upgrade file.
Explanation You entered the config save command, but the system was unable to save the configuration.
Recommended Action Try reentering the command. If the error reoccurs, contact your support representative.
Explanation You entered the logtarget command and specified tty with the -t parameter and an IP address with the -d parameter.
Recommended Action Reenter the command without specifying the -d parameter. An IP address is not required when the target is tty. For information on the logtarget command, see the "logtarget" section.
Explanation You entered an unrecognized command.
Recommended Action Enter help to display a list of valid commands.
|
|