NEC EXP320J, Руководство пользователя

Страница: 272 / 504

5-54 Installing and Using Utilities
Start and Stop of Components
To start or stop a component with NEC ESMPRO Manager, use the [Maintenance] tree of the
component in the [ft] tree of the DataViewer. Open the tree of the component to be started or
stopped and select the [Maintenance] tree.
To start or stop a component with the ft server utility, use the utility screen of the component.
The table below shows the common cases in which a component is to be started or stopped.
Start Stop Compo-
nent
Remote Local Remote Local
CPU
Module When the cause of
down is reviewed
and the system is
restarted in module
down state.
Executable in any of
the following module
states (this can be
viewed on manager
screen):
•
Removed
•
Broken
•
Shot
•
Firmware Update
Complete
•
Diagnostics
Passed
When the cause of
down is reviewed
and the system is
restarted in module
down state.
Executable in the
following module
state:
•
When the status
LED 1 is amber
and the status LED
2 is off
Only the status LED
illuminates amber
when the module is
in one of the
following states:
•
Removed
•
Broken
•
Shot
•
Firmware Update
Complete
•
Diagnostics
Passed
When system is
stopped forcibly
due to replacement
or malfunction of
module.
Executable in the
following module
state (this can be
viewed on manager
screen):
•
Duplex
When system is
stopped forcibly
due to replacement
or malfunction of
module.
Executable in the
following module
state:
•
Only the green
LED is on and in
redundant
configuration
state
The both green
LEDs are on when
the module is in the
following state:
•
Duplex
PCI Module Same as above Same as above Same as above Same as above
SCSI Slot – – – –
Remote: Executable from remote management PC by using NEC ESMPRO Manager
Local:
Executable on local server by using ft server utility
–: Not supported
IMPORTANT:
PCI modules, SCSI adapters, SCSI buses, and modules under the SCSI
enclosure have impact on each other. You need to be aware of this, for example, when you
replace a PCI module. For details, see “Impact When Module Status Changes” described
earlier in this chapter.