HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.1.x administrator guide (5697 - Page 53

Jun 5 08:15:32 [10.32.248.73.2.2] raslogd: AUDIT, 2006/06/05-13:38:17, [SEC-1000], WARNING, SECURITY, JaneDoe/root/192.168.132.19/ telnet, Domain A/DoeSwitch, , Incorrect password during login attempt. Shutting down switches and Directors To avoid corrupting your file system, HP recommends that you perform graceful shutdowns of switches and Directors. The following procedure describes how to gracefully shut down a switch. To power off a switch: 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the sysShutdown command. 3. At the prompt, enter y. switch:admin> sysshutdown This command will shutdown the operating systems on your switch. You are required to power-cycle the switch in order to restore operation. Are you sure you want to shutdown the switch [y/n]?y 4. Wait until the following message displays: Broadcast message from root (ttyS0) Wed Jan 25 16:12:09 2006... The system is going down for system halt NOW !! INIT: Switching to runlevel: 0 INIT: Sending processes the TERM signal Unmounting all filesystems. The system is halted flushing ide devices: hda Power down. 5. Power off the switch. To power off a Director: 1. From the active CP in a dual CP platform, enter the sysShutdown command. When the sysShutdown command is issued on the active CP, the active CP, the standby CP, and any AP blades are all shut down. 2. At the prompt, enter y. 3. Wait until you see the following message: 2006/01/25-17:01:40, [FSSM-1003], 194,, WARNING, NANDU, HA State out of sync HA is disabled Broadcast message from root (ttyS0) Wed Jan 25 17:01:41 2006... The system is going down for system halt NOW !! INIT: Switching to runlevel: 0 INIT: Sending processes the TERM signal Unmounting all filesystems. The system is halted flushing ide devices: hda Power down. 4. Power off the switch. High Availability of daemon processes Fabric OS 6.x supports automatic restart of non-critical daemons. Starting these non-critical daemons is automatic, you cannot configure the startup process. The following sequence of events occurs when a non-critical daemon fails: 1. When a non-critical daemon fails or dies, a RASLog and AUDIT event message is logged. 2. The daemon is automatically started again. 3. If the restart is successful, then another message is sent to RASLog and AUDIT reporting the successful restart status. 4. If the restart fails, another message is sent to RASLog and no further attempts are made to restart the daemon. Fabric OS 6.1.x administrator guide 53