NEC Express5800/340Hb-R N8800-047F, User Manual

Page: 258 / 312

7-14 Troubleshooting
Failure in CPU module duplication and the following event is logged:
→
If the simultaneous replacement of the CPU and PCI modules causes the CPU and
PCI modules to control duplication, the CPU module duplication may fail with the
following message saved in the system event log. If so, the system can be
recovered from the failure starting the CPU module with ft server utility or by
reinserting the CPU module.
Source: srabid
ID: 16474
Description: Diagnostics failure of 2: ‘CPU Get Chipset Info’ (0xf026,0x0,0x0).
EvntAgnt-related logs are recorded in the application event log:
→
The event does not affect the system (it also does not affect the SNMP service).
You need not to cope with this event.
Source: EvntAgnt
ID: 1003
Description: TraceFileName
parameter not located in registry;
Default trace file used is.
Source: EvntAgnt
ID: 1015
Description: TraceLevel parameter not located in registry;
Default trace level used is 32.
sra_ssn-related logs are recorded in the application event log:
→
Although the following log may be recorded in the application event log when
starting the system, there is no real problem on operation. (In the description, X
represent alphanumeric characters.)
Source: sra_ssn
ID: 10319
Description: Authorization failed to ftSAA XXX.XXX.X.X
Error=0xXXXXXXXX.
Source: sra_ssn
ID: 10336
Description: Retry starting for ftSAA XXX.XXX.X.X host log connection.
Source: sra_ssn
ID: 10320
Description: Add Host Log entry failed to ftSAA SMMX.
Source: sra_ssn
ID: 10338
Description: Retry starting for RPC server initialization.