This section explains the FJSV format warning messages in the order of message numbers.
Content:
This message warns that the monitoring target with the process monitoring feature was stopped by other than the correct processing for stopping by the execution of the Offline script.
appli indicates the absolute path name of the monitored process that has been stopped.
Corrective action:
If the process was stopped because of an error, search for the cause by checking the process specification or core file error. The core file is written to the current directory of the process. If the file is written-enabled, the normal access control is applied. The core file is not generated for the process that has an effective user ID different than the actual user ID. For detailed investigations, contact the creator of this process.
Content:
This message indicates that the line switching unit cannot be detected, as the FJSVclswu is not installed.
Corrective action:
Devices other than the line switching unit register an automatic resource.
Install the FJSVclswu package and conduct the automatic resource registration of the line switching unit for using the line switching unit.
Content:
Change of RCI address is detected during operation.
nodename indicates the node name of which RCI address is changed. address represents the RCI address after change.
Corrective action:
Review the RCI address setting of the detected node.
Content:
This message indicates that an error has been detected in part of the transmission route to MMB.
Corrective action:
An error was detected in part of the transmission route to MMB. Check the following points:
Whether the NORMAL lamps on the HUB port and the device port to which the LAN cable is connected are on.
Whether the MMB port connector or the LAN cable from the HUB-side connector is disconnected.
Whether the load to MMB is high.
If one of the above items is found to be the cause, MMB monitoring agent recovers automatically after the corrective action is taken. Automatic recovery takes up to 10 minutes.
If the message 3082 appeared once but did not appear 10 minutes later in the next check cycle, the first message can be ignored because the cause of the message appearance can be considered as temporal high load on the MMB.
If the condition fails after the above items are checked, contact field engineers because there may be a network failure or a hardware failure, such as in the MMB of the HUB. If this corrective action does not work, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
An error was detected in the switching control board of the line switching unit.
addr: Indicates the RCI address of the line switching unit in which an error was detected.
mask: Indicates the LSU mask to be controlled.
status: Indicates the an internal status of the line switching unit by error type.
type: Indicates an error type.
3: Indicates that the reserved status was not canceled.
status: The reserved status of each LSU included in the switching unit is indicated by the value of the LSU mask.
0: Indicates that the LSU is in the released status.
1: Indicates that the LSU is in the reserved status.
4: Indicates that the connection has not changed.
status: The status of the connection of each LSU included in the switching unit is indicated by the LSU mask value.
0: Indicates that the LSU is connected to port 0.
1: Indicates that the LSU is connected to port 1.
5: Indicates that the reserved status could not be created.
status: The reserved status of each LSU included in the switching unit is indicated by the value of the LSU mask.
0: Indicates that the LSU is in the released status.
1: Indicates that the LSU is in the reserved status.
LSU mask value
LSU15 LSU14 LSU13 LSU12 ... LSU03 LSU02 LSU01 LSU00
0x8000 0x4000 0x2000 0x1000 ... 0x0008 0x0004 0x0002 0x0001
Corrective action:
No corrective action is required because processing is retried. If, however, retries fail repeatedly and if this warning occurs frequently, contact field engineers.
Content:
Notification of the completion of startup has not yet been posted from the resource controller. ident indicates a resource controller identifier while command indicates the startup script of the resource controller.
Corrective action:
It is possible that startup of GDS resource controller is delayed. If an error message is output after this warning message, take the corrective action instructed by the error message.
If the message is displayed again, collect the investigation information. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
If no error messages are output, there are no problems as GDS resource controller operates later.
Content:
Failed to start an online trace.
When this message is output, the following messages are also output:
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.mst Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.lck Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.dbc Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.dbu Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.com Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.syn Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.svlib Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.evm Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.evmhty Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.evmslb Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.evmmtx Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.cem Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.cemtm Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.cemlck Onltrc start fail
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
