| SPARC Enterprise M4000/M5000/M8000/M9000 Servers Dynamic Reconfiguration (DR) User’s Guide |    
|
| A P P E N D I X A |
|
Message Meaning and Handling |
This appendix explains the meaning and handling of DR-related messages.
This appendix includes these sections:
This section explains the console messages printed by the DR driver. The output for messages that do not have an output field is console.
DR: PROM detach board X
[Explanation] Detach system board X.
OS configure dr@0:SBX::cpuY
[Explanation] Configure CPU Y on system board X.
OS configure dr@0:SBX::memory
[Explanation] Configure memory on system board X.
OS configure dr@0:SBX::pciY
[Explanation] Configure PCI Y on system board X.
OS unconfigure dr@0:SBX::cpuY
[Explanation] Unconfigure CPU Y on system board X.
OS unconfigure dr@0:SBX::memory
[Explanation] Unconfigure memory on system board X.
OS unconfigure dr@0:SBX::pciY
[Explanation] Unconfigure PCI Y on system board X.
suspending <device name>@<device info> (aka <alias>)
[Explanation] Suspending the device
suspending <device name>@<device info>
[Explanation] Suspending the device
resuming <device name>@<device info> (aka <alias>)
[Explanation] Resuming the device
resuming <device name>@<device info>
[Explanation] Resuming the device
DR: resuming kernel daemons...
[Explanation] Resuming kernel daemons
DR: resuming user threads...
[Explanation] Resuming user threads
DR: suspending user threads...
[Explanation] Suspending user threads
DR: resume COMPLETED
[Explanation] DR resume operation completed
DR: checking devices...
[Explanation] Checking if there are any DR unsafe device drivers loaded
DR: dr_suspend invoked with force flag
[Explanation] User command requests DR operation without checking for unsafe conditions
DR: suspending drivers
[Explanation] Suspending device drivers
DR: in-kernel unprobe board <board>
[Explanation] Unprobing the board.
URGENT_ERROR_TRAP is detected during FMA.
[Explanation] A fatal HW error was encountered during copy-rename.
[Remedy] Please contact customer service.
Failed to remove CMP X LSB NN
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
drmach_copy_rename_fini: invalid op code <opcode>
[Explanation] Internal error happened during kernel migration.
[Remedy] Please contact customer service.
Cannot locate source or target board
[Explanation] Cannot locate source or target board during kernel migration.
[Remedy] Please contact customer service.
Could not update device nodes
[Explanation] Could not update device nodes during kernel migration.
[Remedy] Please contact customer service.
Irrecoverable FMEM error <error code>
[Explanation] Internal error during kernel migration
[Remedy] Please contact customer service.
scf fmem request failed error code = 0x<error code>
[Explanation] Internal error during kernel migration
[Remedy] Please contact customer service.
scf_fmem_end() failed rv=0x<error code>
[Explanation] Internal error during kernel migration
[Remedy] Please contact customer service.
CPU nn hang during Copy Rename
[Explanation] A fatal HW error was encountered during copy-rename.
[Remedy] Please contact customer service.
# megabytes not available to kernel cage
[Explanation] Lack of memory resource deleted.
[Remedy] Detach the board, then attach it again.
IKP: init failed
[Explanation] The initial device tree walk to locate the nodes that are interesting to IKP fails.
[Remedy] Please contact customer service.
dr#: failed to alloc soft-state
[Explanation] Failed to allocate soft-state due to lack of the memory resource
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr#: module not yet attached
[Explanation] Failed to attach the DR driver.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr_add_memory_spans: unexpected kphysm_add_memory_dynamic return value X; basepfn=Y, npages=Z
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_cancel_cpu: failed to disable interrupts on cpu X
[Explanation] Failed to disable interrupt on CPU X.
[Remedy] Disable interrupt on cpu X with psradm -I and if this command fails again, respond in the manner directed by command message.
dr_cancel_cpu: failed to online cpu X
[Explanation] Failed to online CPU X.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr_cancel_cpu: failed to power-on cpu X
[Explanation] Failed to power-on cpu X
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr_copyin_iocmd: (32bit) failed to copyin sbdcmd-struct
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_copyin_iocmd: failed to copyin options
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_copyin_iocmd: failed to copyin sbdcmd-struct
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_copyout_errs: (32bit) failed to copyout
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_copyout_errs: failed to copyout
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_copyout_iocmd: (32bit) failed to copyout sbdcmd-struct
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_copyout_iocmd: failed to copyout sbdcmd-struct
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_status: failed to copyout status for board #
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_status: unknown dev type (#)
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_dev2devset: invalid cpu unit# = #
[Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr_dev2devset: invalid io unit# = #
[Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr_dev2devset: invalid mem unit# = #
[Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr_exec_op: unknown command (#)
[Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr_post_attach_cpu: cpu_get failed for cpu X
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_pre_release_cpu: thread(s) bound to cpu X
[Explanation] The thread in the process is bound to the detached CPU X.
[Remedy] Check if the process bound to the CPU exists by pbind(1M) command. If it exists, unbind from the CPU and repeat the action.
dr_pre_release_mem: unexpected kphysm_del_release returnvalue #
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_pt_ioctl: invalid passthru args
[Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
dr_release_mem: unexpected kphysm error code #, id 0xX
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_release_mem_done: mem-unit (X.Y): deleted memory still found in phys_install
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_release_mem_done: target: mem-unit (X.Y): deleted memory still found in phys_install
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_release_mem_done: unexpected kphysm_del_release returnvalue #
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_reserve_mem_spans memory reserve failed. Unexpected kphysm_del_span return value #; basepfn=# npages=#
[Explanation] The selected target board can no longer fit all the kernel memory of the source board since it was last selected.
[Remedy] Please repeat the action. If the problem remains, please contact customer service.
dr_release_mem_done: <device path>: error <error code> noted
[Explanation] Error noted for a device during releasing memory.
[Remedy] Please contact customer service.
drmach_log_sysevent failed (rv #) for SBX
[Explanation] There may be minor error in the system.
[Remedy] Please contact customer service.
unexpected kcage_range_add return value #
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
unexpected kcage_range_delete return value #
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_select_mem_target: no memlist for mem-unit X, board Y
[Explanation] Detected inconsistency of the memory unit information in the DR driver's internal data.
[Remedy] Please contact customer service.
FAILED to suspend <device name>@<device info>
[Explanation] Device suspension failed
[Remedy] Repeat the action. If the message persists, please contact customer service.
FAILED to resume <device name>@<device info>
[Explanation] The device cannot be resumed.
[Remedy] Please contact customer service.
dr_stop_user_threads: failed to stop thread: process=<name>, pid=#
[Explanation] Cannot stop the user thread.
[Remedy] Please contact customer service.
Cannot stop user thread: <pid> <pid> ...
[Explanation] The DR driver cannot stop all the user processes in the list.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Cannot setup memory node
[Explanation] DR is unable to read the HW information for the memory device.
[Remedy] Please contact customer service.
Kernel Migration fails. 0xX
[Explanation] Kernel data migration failed as a result of DR detach.
[Remedy] Please contact customer service.
TOD on board X has already been attached.
[Explanation] Time of Date Clock on board X has been attached. This may be a minor inconsistency in the system.
[Remedy] Please contact customer service.
TOD on board X has already been removed.
[Explanation] Time of Date Clock on board X has been removed. This may be a minor inconsistency in the system.
[Remedy] Please contact customer service.
Unable to detach last available TOD on board X
[Explanation] Detaching the system board will result in detaching the last available Time of Date clock.
[Remedy] Attach another system board before detaching.
Device in fatal state
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
I/O error: dr@0:SBX::memory
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Invalid argument
[Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Invalid argument: ########
[Explanation] Invalid argument is passed to the driver.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Invalid CPU/core state
[Explanation] DR finds some faulty CPU that fails to power on.
[Remedy] Please contact customer service.
No error
[Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
no error: dr@0:SBX::memory
[Explanation] There may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Unrecognized platform command: #
[Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Bad address: dr@0:SBX::memory
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Cannot read property value: device node XXXXXX property: name
[Explanation] Fail to get the property from OBP.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Cannot read property value: property: scf-cmd-reg
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Cannot find mc-opl interface
[Explanation] DR cannot locate mc-opl driver's suspend/resume interface. mc-opl is probably not loaded or incorrect version is used.
[Remedy] Please contact customer service.
Cannot find scf_fmem interface
[Explanation] DR cannot locate SCF driver's FMEM interface functions. SCF is probably not loaded or incorrect version is used.
[Remedy] Please contact customer service.
Device busy: dr@0:SBX::pciY
[Explanation] Some devices are still referenced.
[Remedy] Confirm that all devices in this pci slot are not in use and repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Device driver failure: path
[Explanation] The device driver failed in attach or detach operation.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Error setting up FMEM buffer
[Explanation] DR fails to allocate enough memory to perform copy rename.
[Remedy] Retry and if the problem persists, contact customer service.
Failed to off-line: dr@0:SBX::cpuY
[Explanation] Failed to off-line CPU Y on board X.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Failed to on-line: dr@0:SBX::cpuY
[Explanation] Failed to online CPU Y on system board X.
[Remedy] Online CPU with psradm -n. If it fails to online CPU, and if this command fails again, respond in the manner directed by command message.
[Output] Console and Standard Output
Failed to start CPU: dr@0:SBX::cpuY
[Explanation] Failed to start CPU Y on system board X.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Failed to stop CPU: dr@0:SBX::cpuY
[Explanation] Failed to stop CPU Y on system board X.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Firmware deprobe failed: SBX::cpuY
[Explanation] Failed to deprobe the CPU.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Firmware probe failed: SBX
[Explanation] Failed to probe the board.
[Remedy] Respond in the manner directed by the other message.
[Output] Console and Standard Output
Insufficient memory: dr@0:SBX::memory
[Explanation] Detected lack of memory resource.
[Remedy] Check the size of memory, detach the board and attach again. If the problem still exists, please contact customer service.
[Output] Console and Standard Output
Internal error: dr.c #
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Internal error: dr_mem.c #
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Invalid argument: dr@0:SBX::memory
[Explanation] The memory board X is currently involved in other DR operation and cannot be detached.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Invalid board number: X
[Explanation] Invalid board number.
[Remedy] Check the board number and repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Kernel cage is disabled:
[Explanation] The kernel cage memory feature is disabled.
[Remedy] Ensure /etc/system is edited to enable kernel cage memory.
[Output] Console and Standard Output
Memory operation failed: dr@0:SBX::memory
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Memory operation refused: dr@0:SBX::memory
[Explanation] The DR operation is refused.
[Remedy] Respond in the manner directed by the other message.
Memory operation cancelled: dr@0:SBX::memory
[Explanation] The DR operation is canceled.
[Remedy] Respond in the manner directed by the other message.
No device(s) on board: dr@0:SBX
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Non-relocatable pages in span: dr@0:SBX::memory
[Explanation] There is non-relocatable (kernel) memory on the system board.
[Remedy] The target board with kernel memory cannot be disconnected by DR. It depends on your server if you can remove a kernel memory board or not.
Operator confirmation for quiesce is required: dr@0:SBX::memory
[Explanation] There is non-relocatable (kernel) memory on the board.
[Remedy] The target board with kernel memory cannot be disconnected by DR.
[Output] Console and Standard Output
Unexpected internal condition: drmach.c #
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Unexpected internal condition: SBX
[Explanation] The attempt to call OBP failed.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Device busy: dr@0:SBX::cpuY
[Explanation] CPU Y on system board X is busy during release operation.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Insufficient memory: dr@0:SBX::cpuY
[Explanation] Lack of memory resources detected.
[Remedy] Check the size of available memory and detach the board. If the problem still exists, please contact customer service.
[Output] Console and Standard Output
Invalid argument: dr@0:SBX::cpuY
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Invalid state transition: dr@0:SBX::cpuY
[Explanation] Invalid state transition of cpu Y on system board X
[Remedy] Repeat the action. If the problem still exists, please contact customer service.
[Output] Console and Standard Output
Invalid state transition: dr@0:SBX::memory
[Explanation] Invalid state transition of memory on system board X
[Remedy] Repeat the action. If the problem still exists, please contact customer service.
[Output] Console and Standard Output
Invalid state transition: dr@0:SBX::pciY
[Explanation] Invalid state transition of pci Y on system board X
[Remedy] Repeat the action. If the problem still exists, please contact customer service.
[Output] Console and Standard Output
No such device: dr@0:SBX::cpuY
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Operation already in progress: dr@0:SBX::cpuY
[Explanation] The operation on cpu Y on system board X is in progress.
[Remedy] Repeat the action. If the problem still exists, please contact customer service.
[Output] Console and Standard Output
dr_move_memory: failed to quiesce OS for copy-rename
[Explanation] There is a task not suspended in the process.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
No available memory target: dr@0:SBX::memory
[Explanation] The system board cannot be detached because it contains kernel memory and there is no available target memory board.
[Remedy] Add new system board and then try the detach operation again.
[Output] Console and Standard Output
Unsafe driver present: <driver name|major #> ...
[Explanation] DR driver found DR unsafe drivers in the system.
[Remedy] Unload the unsafe drivers and try the DR operation again.
[Output] Console and Standard Output
Device failed to resume: <driver name|major #> ...
[Explanation] Devices on the list failed to resume
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Device failed to suspend: <driver name|major #> ...
[Explanation] Devices on the list failed to suspend
[Remedy] Please contact customer service.
[Output] Console and Standard Output
Operation not supported: ERROR
[Explanation] Invalid operation.
[Remedy] Repeat the action. If this error message appears again, please contact customer service.
[Output] Console and Standard Output
Cannot setup resource map opl-fcodemem
[Explanation] Resource memory mapping cannot be set up.
[Remedy] Please contact customer service.
opl_cfg failed to load, error=<errno>
[Explanation] opl_cfg module failed to load.
[Remedy] Please contact customer service.
IKP: failed to read HWD header
[Explanation] The header of the hardware descriptor could not be read.
[Remedy] Please contact customer service.
IKP: create cpu (<board>-<chip>-<core>-<cpu>) failed
[Explanation] There was a problem creating the device node for a cpu.
[Remedy] Please contact customer service.
IKP: create core (<board>-<chip>-<core>) failed
[Explanation] There was a problem creating the device node for a core.
[Remedy] Please contact customer service.
IKP: create chip (<board>-<chip>) failed
[Explanation] There was a problem creating the device node for a chip.
[Remedy] Please contact customer service.
IKP: create pseudo-mc (<board>) failed
[Explanation] There was a problem creating the pseudo-mc device node for the board.
[Remedy] Please contact customer service.
opl_claim_memory - unable to allocate contiguous memory of size zero
[Explanation] A claim request with size zero was issued by the fcode interpreter.
[Remedy] If DR failed after this message, please contact customer service.
opl_claim_memory - vhint is not zero vhint=0x<vhint> - Ignoring Argument
[Explanation] A claim request with a nonzero hint came from the fcode interpreter.
[Remedy] If DR failed after this message, please contact customer service.
opl_claim_memory - unable to allocate contiguous memory
[Explanation] Memory allocation failed for the fcode interpreter.
[Remedy] If DR failed after this message, please contact customer service.
opl_get_fcode: Unable to copy out fcode image
[Explanation] Failed to copy out the fcode image to the efcode daemon.
[Remedy] If DR failed after this message, please contact customer service.
opl_get_hwd_va: Unable to copy out cmuch descriptor for <addr>
[Explanation] Failed to copy out the cmuch HWD to the efcode daemon.
[Remedy] If DR failed after this message, please contact customer service.
opl_get_hwd_va: Unable to copy out pcich descriptor for <addr>
[Explanation] Failed to copy out the pcich HWD to the efcode daemon.
[Remedy] If DR failed after this message, please contact customer service.
IKP: create leaf (<board>-<channel>-<leaf>) failed
[Explanation] A device node was not created for a PCI device.
[Remedy] If DR failed after this message, please contact customer service.
IKP: Unable to probe PCI leaf (<board>-<channel>-<leaf>)
[Explanation] The fcode interpreter returned a bad status for the probe.
[Remedy] If DR failed after this message, please contact customer service.
IKP: Unable to bind PCI leaf (<board>-<channel>-<leaf>)
[Explanation] The driver binding fails, after the leaf has been probed.
[Remedy] If DR failed after this message, please contact customer service.
IKP: destroy pci (<board>-<channel>-<leaf>) failed
[Explanation] The node was not destroyed.
[Remedy] Please contact customer service.
IKP: destroy pseudo-mc (<board>) failed
[Explanation] The node was not destroyed.
[Remedy] Please contact customer service.
IKP: destroy chip (<board>-<chip>) failed
[Explanation] The node was not destroyed.
[Remedy] Please contact customer service.
dr_del_mlist_query: mlist=NULL
[Explanation] The memory list to be deleted is NULL. This warning is also shown at memoryless board.
[Remedy] Please ignore this message on memoryless boards. If DR failed after this message, please contact customer service.
dr_memlist_canfit: memlist_dup failed
[Explanation] System might have run out of memory. Or there is a memoryless board.
[Remedy] Please ignore this message on memoryless boards. If DR failed after this message, please check if the system has enough memory resource and repeat the action. If the error remains, please contact customer service.
Cannot get floating-boards proplen
[Explanation] Failed to get property information of floating-boards.
[Remedy] Please contact customer service.
Cannot get floating-boards prop
[Explanation] Failed to get property information of floating-boards.
[Remedy] Please contact customer service.
Device node 0x<dip> has invalid property value, board#=<board>
[Explanation] The device node has invalid property value.
[Remedy] Please contact customer service.
DR - IKP initialization failed
[Explanation] IKP initialization failed
[Remedy] Please contact customer service.
I/O callback failed in pre-release
[Explanation] I/O callback failed in pre-release
[Remedy] Please contact customer service.
I/O callback failed in post-attach
[Explanation] I/O callback failed in post-attach
[Remedy] Please contact customer service.
Kernel Migration fails. 0x%x
[Explanation] Internal error happened during kernel migration.
[Remedy] Please contact customer service.
Failed to add CMP%d on board %d
[Explanation] CPU failed to power-on during DR attach.
[Remedy] Please contact customer service.
FMEM error = 0x<error code>
[Explanation] DR detects error during the copy rename operation.
[Remedy] Please contact customer service.
Cannot proceed; Board is configured or busy
[Explanation] Board cannot be disconnected because its status is busy.
[Remedy] Repeat the action; If the problem still exists, please contact customer service.
drmach parameter is not a valid ID
[Explanation] ID parameter for status command is not a valid ID.
[Remedy] Correct the format of the ID parameter.
drmach parameter is inappropriate for operation
[Explanation] Parameter(s) for DR command specified incorrectly.
[Remedy] Correct the parameter(s).
drmach_node_ddi_get_parent: NULL dip
[Explanation] Internal error during DR operation.
[Remedy] Please contact customer service.
drmach_node_ddi_get_parent: NULL parent dip
[Explanation] Internal error during DR operation.
[Remedy] Please contact customer service.
Failed to remove CMP xx on board n
[Explanation] Internal error during DR operation.
[Remedy] Please contact customer service.
scf_fmem_cancel() failed rv=0x<error code>
[Explanation] Internal error during kernel migration.
[Remedy] Please contact customer service.
scf_fmem_start error
[Explanation] SCF fails to start the FMEM operation. It is possible that there is HW error and there is no SCF path or the SP is down.
[Remedy] Please contact customer service.
scf_fmem_cancel error
[Explanation] DR detects some error in the copy rename process and informs SCF to cancel the operation. However, SCF fails to cancel the operation.
[Remedy] Please contact customer service.
Unknown cpu implementation
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
dr_mem_ecache_scrub:address (0x%lx) not on page boundary
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
unexpected kcage_range_delete_post_mem_del return value
[Explanation] There may be inconsistency in the system.
[Remedy] Please contact customer service.
opl_fc_ops_free_handle: DMA seen!
[Explanation] A DMA resource was found in the resource list that is being freed while the board is unprobed.
[Remedy] Please contact customer service.
opl_fc_ops_free: unknown resource type <type>
[Explanation] An unknown resource type was found in the resource list that is being freed while the board is unprobed.
[Remedy] Please contact customer service.
VM viability test failed: dr@0:SBX::memory
[Explanation] There is not enough real memory to detach memory on system board X.
[Remedy] Check the amount of available real memory, and repeat the action.If this error message appears again, please contact our customer service.
DR parallel copy timeout
[Explanation] Internal error happened during kernel migration.
[Remedy] Retry and if the problem persists, contact customer service.
SCF busy
[Explanation] SCF was busy during kernel migration.
[Remedy] Retry and if the problem persists, contact customer service.
SCF I/O Retry Error
[Explanation] Internal error happened during kernel migration.
[Remedy] Please contact customer service.
FMEM command timeout
[Explanation] Internal error happened during kernel migration.
[Remedy] Please contact customer service.
Hardware error
[Explanation] Internal error happened during kernel migration.
[Remedy] Please contact customer service.
FMEM operation terminated
[Explanation] Internal error happened during kernel migration.
[Remedy] Please contact customer service.
Memory copy error
[Explanation] Memory copy error happened during kernel migration.
[Remedy] Retry and if the problem persists, contact customer service.
SCF error
[Explanation] Internal error happened during kernel migration.
[Remedy] Please contact customer service.
Cannot add SPARC64-VI to domain booted with all SPARC64-VII CPUs
[Explanation] System board with SPARC64-VI cannot be added into a domain booted with all SPARC64-VII CPUs when the domain's CPU mode is set as 'auto' via XSCF.
[Remedy] The system board that failed to be added is 'assigned' to the target domain. Please delete the system board to restore the status as 'available'.
SCF OFFLINE
[Explanation] XSCF failure or failover occurred during kernel migration.
[Remedy] Log in to XSCF again to check the status, and repeat the action.
XSB#XX-X will be assigned to DomainID X. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
XSB#XX-Xwill be configured into DomainID X. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
DR operation canceled by operator.
[Explanation] DR operation canceled by operator.
Domain (DomainID X) is not currently running.
[Explanation] Destination domain #0 was not active when "-c configure" was specified.
[Remedy] Execute it by specifying "-c assign".
XSB#XX-X is already assigned to another domain.
[Explanation] The specified system board (XSB#XX-X) has already been assigned to another domain.
[Remedy] XSB has already been assigned to another domain. Confirm the XSB by showboards(8).
XSB#XX-X is not installed.
[Explanation] System board (XSB#XX-X) is not installed.
[Remedy] Specify the wrong XSB. Confirm the XSB by showboards(8).
XSB#XX-X is currently unavailable for DR. Try again later.
[Explanation] The specified system board (XSB#XX-X) has already been executed by another operation.
[Remedy] DR or power-off has been executing for another session. Try again after waiting for a while, with the confirmation of the XSB status.
XSB#XX-X has not been registered in DCL.
[Explanation] System board (XSB#XX-X) is not registered to DCL.
[Remedy] Register DCL information by setdcl(8).
Another DR operation is in progress. Try again later.
[Explanation] The specified system board (XSB#XX-X) has already been executed by another session.
[Remedy] DR operation is in progress by another session. Try again after waiting for a while, with the confirmation of the XSB status.
XSB#XX-X has been detected timeout by DR self test.
[Explanation] The timeout occurred during DR processing because the hardware diagnosis did not complete. There is something wrong with the hardware.
[Remedy] Find out the cause of the DR failure referring monitoring message and errorlog. Replace the failure component.
XSB#XX-X encountered a hardware error. See error log for details.
[Explanation] An error occurred during hardware diagnosis. There is something wrong with the hardware.
[Remedy] Find out the cause of the DR failure referring monitoring message and errorlog. Replace the failure component.
IP address of DSCP path is not specified.
[Explanation] DR cannot communicate with the domain because the DSCP IP Address is not set up or registered.
[Remedy] Register the DSCP IP Address.
An internal error has occurred. This may have been caused by a DR library error.
[Explanation] The DR processing cannot be failed on the domain OS. The error occurred at the DR library.
[Remedy] Find out the cause of the DR failure referring monitoring message and errorlog. Confirm the patch applying status and the XCP version
DR failed. Domain (DomainID X) cannot communicate via DSCP path.
[Explanation] DR processing cannot communicate with the domain. The reasons are that domain is powered off, the DSCP setting is wrong or the error occurs at the DSCP path.
[Remedy] Confirm the domain powered off, DSCP setting, DSCP error with monitoring message and errorlog.
XSB#XX-X could not be configured into DomainID X due to operating system error.
[Explanation] An error occurred from DR library of domain OS at DR process. The error occurred at configuration management of domain OS.
[Remedy] Find out the cause of the DR failure referring monitoring message and console message. Try again after taking out cause.
Invalid parameter.
[Explanation] There is an error in the specified argument or operand.
[Remedy] Confirm the specified argument or operand and execute the command once again.
Permission denied.
[Explanation] Do not have privilege.
[Remedy] Confirm the user privilege and the command privilege. In the case of high-end servers, please also confirm whether command is executed by XSCF on standby side.
The current configuration does not support this operation.
[Explanation] Cannot execute the command in the current configuration, or it is not supported.
[Remedy] Confirm the current hardware configuration and support status.
A hardware error occurred. Please check the error log for details.
[Explanation] Hardware error occurred. Please confirm monitoring message and the error log.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Replace the failure component.
An internal error has occurred. Please contact your system administrator.
[Explanation] DR failed. There is a possibility that DR failed because of an internal error in XSCF.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Please also confirm the XCP version.
Timeout detected during self-test of XSB#XX-X.
[Explanation] Because the hardware diagnosis in DR did not complete, a timeout occurred. There is a possibility that a hardware error occurred.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Replace the failure component.
XSB#XX-X will be unassigned from domain immediately. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
XSB#XX-X will be unconfigured from domain immediately. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
XSB#XX-X will be unassigned from domain after the domain restars. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
DR operation canceled by operator.
[Explanation] DR operation canceled by operator
XSB#XX-X is not installed.
[Explanation] System board (XSB#XX-X) is not installed.
[Remedy] Specify the wrong XSB. Confirm the XSB by showboards(8).
XSB#XX-X is currently unavailable for DR. Try again later.
[Explanation] The specified system board (XSB#XX-X) has already been executed by another operation.
[Remedy] DR or power-off has been executing for another session. Try again after waiting for a while, with the confirmation of the XSB status.
XSB#XX-X has not been registered to DCL.
[Explanation] System board (XSB#XX-X) is not registered to DCL.
[Remedy] Register DCL information by setdcl(8).
XSB#XX-X is the last LSB for DomainID X, and this domain is still running. Operation failed.
[Explanation] XSB#XX-X is the last LSB for domain#X.
[Remedy] Power-off the domain by specifying "-c reserve".
IP address of DSCP path is not specified.
[Explanation] DR cannot communicate with the domain because DSCP IP Address is not set up or not registered.
[Remedy] Register the DSCP IP Address.
An internal error has occurred. This may have been caused by a DR library error.
[Explanation] The DR processing cannot be failed on the domain OS. The error occurred at the DR library.
[Remedy] Find out the cause of the DR failure referring monitoring message and errorlog. Confirm the patch applying status and the XCP version.
DR failed. Domain (DomainID X) cannot communicate via DSCP path.
[Explanation] DR processing cannot communicate with the domain. The reasons are that domain is powered off, the DSCP setting is wrong or the error occurs at the DSCP path.
[Remedy] Confirm the domain powered off, DSCP setting, DSCP error with monitoring message and errorlog.
XSB#XX-X could not be unconfigured from DomainID X due to operating system error.
[Explanation] An error occurred from DR library of domain OS at DR process. The error occurred at configuration management of domain OS.
[Remedy] Find out the cause of the DR failure referring monitoring message and console message. Try again after taking out cause.
Invalid parameter.
[Explanation] There is an error in the specified argument or operand.
[Remedy] Confirm the specified argument or operand and execute the command once again.
Permission denied.
[Explanation] Do not have privilege.
[Remedy] Confirm the user privilege and the command privilege. In the case of high-end servers, please also confirm whether command is executed by XSCF on standby side.
A hardware error occurred. Please check the error log for details.
[Explanation] Hardware error occurred. Please confirm monitoring message and the error log.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Replace the failure component.
An internal error has occurred. Please contact your system administrator.
[Explanation] DR failed. There is a possibility that DR failed because of an internal error in XSCF.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Please also confirm the XCP version.
XSB#XX-X will be moved from DomainID X to DomainID X immediately. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
XSB#XX-X will be assigned to DomainID X immediately. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
XSB#XX-X will be assigned to DomainID X after DomainID X restarts. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
DR operation canceled by operator.
[Explanation] DR operation canceled by operator.
Domain (DomainID X) is not currently running.
[Explanation] Destination domain #X was not active when "-c configure" was specified.
[Remedy] Execute it by specifying "-c assign".
XSB#XX-X cannot be moved due to System Board Pool.
[Explanation] The XSB in the system board pool cannot be moved.
[Remedy] Executing addboard command.
XSB#XX-X is not installed.
[Explanation] System board (XSB#XX-X) is not installed.
[Remedy] Specify the wrong XSB. Confirm the XSB by showboards(8).
XSB#XX-X is currently unavailable for DR. Try again later.
[Explanation] The specified system board (XSB#XX-X) has already been executed by another operation.
[Remedy] DR or power-off has been executing for another session. Try again after waiting for a while, with the confirmation of the XSB status.
XSB#XX-X has not been registered in DCL.
[Explanation] System board (XSB#XX-X) is not registered to DCL.
[Remedy] Register DCL information by setdcl(8).
Another DR operation is in progress. Try again later.
[Explanation] The specified system board (XSB#XX-X) has already been executed by another session.
[Remedy] DR operation is in progress by another session. Try again after waiting for a while, with the confirmation of the XSB status.
XSB#XX-X is the last LSB for DomainID X, and this domain is still running. Operation failed.
[Explanation] XSB#XX-X is the last LSB for domain#X.
[Remedy] Power off the domain by specifying "-c reserve".
XSB#XX-X detected timeout by DR self test.
[Explanation] The timeout occurred during DR processing because the hardware diagnosis did not complete. There is something wrong with the hardware.
[Remedy] Find out the cause of the DR failure referring monitoring message and errorlog. Replace the failure component.
XSB#XX encountered a hardware error. See error log for details.
[Explanation] An error occurred during hardware diagnosis. There is something wrong with the hardware.
[Remedy] Find out the cause of the DR failure referring monitoring message and errorlog. Replace the failure component.
IP address of DSCP path is not specified.
[Explanation] The DR processing cannot communicate the domain because DSCP IP Address is not set up.
[Remedy] Register the DSCP IP Address.
An internal error has occurred. This may have been caused by a DR library error.
[Explanation] The DR processing cannot be failed on the domain OS. The error occurred at the DR library.
[Remedy] Find out the cause of the DR failure referring monitoring message and errorlog. Confirm the patch applying status and the XCP version.
DR failed. Domain (DomainID X) cannot communicate via DSCP path.
[Explanation] DR processing cannot communicate with the domain. The reasons are that domain is powered off, the DSCP setting is wrong or the error occurs at the DSCP path.
[Remedy] Confirm the domain powered off, DSCP setting, DSCP error with monitoring message and errorlog.
XSB#03-0 could not be unconfigured from DomainID 1 due to operating system error, or XSB#03-0 could not be configured into DomainID 0 due to operating system error.
[Explanation] An error occurred in DR library of domain OS at DR process. The error occurred at configuration management of domain OS.
[Remedy] Find out the cause of the DR failure referring monitoring message and console message. Try again after taking out cause.
Invalid parameter.
[Explanation] There is an error in the specified argument or operand.
[Remedy] Confirm the specified argument or operand and execute the command once again.
Permission denied.
[Explanation] Do not have privilege.
[Remedy] Confirm the user privilege and the command privilege. In the case of high-end servers, please also confirm whether command is executed by XSCF on standby side.
The current configuration does not support this operation.
[Explanation] Cannot execute the command in the current configuration, or it is not supported.
[Remedy] Confirm the current hardware configuration and support status.
A hardware error occurred. Please check the error log for details.
[Explanation] Hardware error occurred. Please confirm monitoring message and the error log.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Replace the failure component.
An internal error has occurred. Please contact your system administrator.
[Explanation] DR failed. There is a possibility that DR failed because of an internal error in XSCF.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Please also confirm the XCP version.
Timeout detected during self-test of XSB#XX-X.
[Explanation] Because the hardware diagnosis in DR did not complete, a timeout occurred. There is a possibility that a hardware error occurred.
[Remedy] Find out the cause of the DR failure referring to the monitoring message and error log. Replace the failed component.
XSB#XX-X will be assigned to DomainID X. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
XSB#XX-Xwill be configured into DomainID X. Continue? [y|n]:
[Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it.
XSB#XX-X could not be configured into DomainID X due to operating system error.
[Explanation] An error occurred in DR library of domain OS at configuration process. The error occurred at configuration management of domain OS.
[Remedy] Find out the cause of the DR failure referring monitoring message and console message. Try again after resolving cause.
XSB is already assigned to an LSB in a running Domain (DomainID X).
[Explanation] The system board of the specified LSB has already been registered in DCL.
[Remedy] Power off the domain, or move XSB to the system board pool. Try again.
LSB#00 is already registered in DCL.
[Explanation] The system board of the specified LSB has already been registered in DCL.
[Remedy] Confirm the domain, LSB and XSB. Setup data correctly.
LSB#00 has not been registered in DCL yet.
[Explanation] The domain and LSB weren’t set up, when the DCL of no-mem, no-io and floating-board was changed.
[Remedy] Set up the domain and LSB. Try again.
DomainID X does not exist.
[Explanation] No LSB was set up on the domain, when the DCL of configuration-policy was changed.
[Remedy] Set up the domain and LSB. Try again.
Invalid parameter.
[Explanation] There is an error in the specified argument or operand.
[Remedy] Confirm the specified argument or operand and execute the command once again.
Permission denied.
[Explanation] Do not have privilege.
[Remedy] Confirm the user privilege and the command privilege. In the case of high-end servers, please also confirm whether command is executed by XSCF on standby side.
An internal error has occurred. Please contact your system administrator.
[Explanation] DR failed. There is a possibility that DR failed because of an internal error in XSCF.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Please also confirm the XCP version.
SB#XX is currently in use.
[Explanation] Because the system board of the PSB is running on the domain or is assigned, PSB configuration cannot be changed.
[Remedy] Please confirm whether the system board of the PSB is assigned to the domain or not, and release the system board if it is in the assigned status.
SB#XX is not installed.
[Explanation] Because PSB is not installed, it could not be set.
[Remedy] Please execute it again after confirming installation of the hardware.
Operation has completed. However, a configuration error was detected.
[Explanation] Although configuration of PSB is changed, configuration error is occurring on the system board created. Confirm the CPU module and DIMM slot on the specified PSB and status of Memory Mirror Mode.
[Remedy] Confirm the CPU module and DIMM slot on the PSB board and status of Memory Mirror Mode.
The specified parameter is not supported in this model.
[Explanation] Unsupported parameter in this server is specified. For this reason, the command was canceled.
[Remedy] Confirm the specified parameter and your server, and execute the command once again.
Invalid parameter.
[Explanation] There is an error in the specified argument or operand.
[Remedy] Confirm the specified argument or operand and execute the command once again.
Permission denied.
[Explanation] Do not have privilege.
[Remedy] Confirm the user privilege and the command privilege. In the case of high-end servers, please also confirm whether command is executed by XSCF on standby side.
The current configuration does not support this operation.
[Explanation] Cannot execute the command in the current configuration, or it is not supported.
[Remedy] Confirm the current hardware configuration and support status.
An internal error has occurred. Please contact your system administrator.
[Explanation] DR failed. There is a possibility that DR failed because of an internal error in XSCF.
[Remedy] Find out the cause of the DR failure referring monitoring message and error log. Please also confirm the XCP version.
XSB#%s is not currently running.
[Explanation] The system was not able to get some parameter for the XSB.
[Remedy] Confirm the information for the XSB via the showboards command.
cannot get device information from DomainID.
[Explanation] The system was unable to collect the requested information from the domain.
[Remedy] Confirm that the DSCP setting is correct, confirm that the dsc process is running fine on the domain.
| SPARC Enterprise M4000/M5000/M8000/M9000 Servers Dynamic Reconfiguration (DR) User’s Guide | 821-2796-10 |
|
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.