40733025 (677.00 KB)
8/2/2023 3:48 AM
Last saved by EMC
Shutdown Centera w/CUA nodes
This procedure describes the steps to shutdown a Centera Cluster (rack) that also contains any of the
following: Gen3, Gen4, Gen4LP CUA/CFA nodes.
This procedure is used to shut down a cluster only if a power outage is expected or if a maintenance
activity requires the rack [cua &cluster] to be shut down.
Overview
 Gracefully shutdown the CUA/CFA nodes
 Gracefully shutdown the Centera
 This procedure is applicable to CentraStar version 3.0.x and CUA/CFA 3.6 and greater.
Check for unwritten files on the CUA/CFA
a. Verify that all applications have stopped writing.
b. Log into the active CUA/CFA using the gwsetup account and select X) Enter bash shell
Note:
Note: A connection can be established using Monitor & Keyboard, Serial Port or a ssh session.
c. Check if there are any files that are not yet written to Centera by performing the following
commands:
service@[host_name]:~>sudo caginfo
Example: No files waiting to be written back
service@v4cua:~>sudo caginfo
service@v4cua:~>[no files are shown]
Example: Files waiting to be written back
service@v4cua:~>sudo caginfo
/sfs/gateway_cifs/new2/CenteraViewer-31SP3/CuaExt.jar
//sfs/gateway_cifs/new2/CenteraViewer-31SP3/FieldExt.jar
/sfs/gateway_cifs/new2/CenteraViewer-31SP3/CenteraViewer.jar
/sfs/gateway_cifs/new2/CenteraViewer-31SP3/FirmwareExt.jar
/sfs/gateway_cifs/new2/CenteraViewer-31SP3/GlobalServices_3_1_SP3.exe
/sfs/gateway_cifs/new2/CenteraViewer-31SP3/javastartpath.txt
d. If there are files waiting to be written to the Centera – wait a few minutes and run the “sudo
caginfo” command again and see if the files are decreasing. Depending upon the backlog this may
take some time. If they are not decreasing then the reason should be investigated. i.e. network
issues, Centera configuration (profiles, etc),
Note: You can use the following commands to specifically check nfs and cifs
sudo sfsproxyd_read_rfi -w /sfs/gateway_cifs
sudo sfsproxyd_read_rfi -w /sfs/gateway_nfs
To force write a file
bash-2.04$# sudo sfsproxyd_write –F /sfs/gateway_cifs/filexxx
bash-2.04$# sudo sfsproxyd_write –F /sfs/gateway_nfs/filexxx
1
40733025 (677.00 KB)
8/2/2023 3:48 AM
Last saved by EMC
Force a CA backup:
Force a backup by selecting W at the Utility menu.
Welcome to the Centera Universal Access CUA4.0_4735 Setup Utility
----------------------------------------------------------------A) Simulate alerts
B) Browse Metadata
C) Configuration options
D) Configure Centera FileArchiver
K) Capture system information
M) Send E-mail notification
O) Set CLI operational parameters (editor, locale)
P) Alter File Protection
R) Restore system configuration
S) Shutdown system
T) Reboot system
U) Upgrade system
V) Initiate Failover
W) Backup system
X) Enter bash shell
Q or E) Exit
Example: of a successful backup
Welcome to the EMC Centera Universal Access Module.
Backup system
------------Backing Up System
Starting backup process
Backup in progress...
**************************************************************
*** Logging started at Mon Sep 10 14:49:32 2007
**************************************************************
Command: '/usr/local/bin/acagd --full -Q', status: 0
Command: 'psql xms -U postgres -c 'vacuum analyze;'' now being executed...
VACUUM
Command: 'psql xms -U postgres -c 'vacuum analyze;'', status: 0
Full backup completed!
**************************************************************
*** Logging stopped at Mon Sep 10 14:49:48 2007
**************************************************************
Backup complete
Press any key to continue
The CA generated by the backup will be sent to the E-mail alert recipients
Example: of the Backup e-mail alert:
CUA blackcua.svtdomain.us.dg.com (10.241.185.101) v4.0 Full Backup started, using
access profile 'cua', at Mon Sep 10 14:49:34 2007
Configuration files backup completed at Mon Sep 10 14:49:43 2007
XMD backup completed at Mon Sep 10 14:49:45 2007
Aggregate backup completed at Mon Sep 10 14:49:45 2007
CUA blackcua.svtdomain.us.dg.com (10.241.185.101) v4.0 Full Backup completed at Mon
Sep 10 14:49:45 2007
2
40733025 (677.00 KB)
8/2/2023 3:48 AM
Last saved by EMC
CA is EC8KDPUPO66B3e7TJU3ERAKKAING412JNUBM0G0NA3FAM0UN0MG1I, used access profile
'cua'
Shutting down the CUA
a. If this is an EA configuration - log into the STANDBY CUA/CFA and shut it down 1st. Then log into
the active CUA/CFA and perform the shutdown. Do not failover.
b. In the setup Utility select S to start the shutdown
Welcome to the Centera Universal Access CUA4.0_4735 Setup Utility
----------------------------------------------------------------A) Simulate alerts
B) Browse Metadata
C) Configuration options
D) Configure Centera FileArchiver
K) Capture system information
M) Send E-mail notification
O) Set CLI operational parameters (editor, locale)
P) Alter File Protection
R) Restore system configuration
S) Shutdown system
T) Reboot system
U) Upgrade system
V) Initiate Failover
W) Backup system
X) Enter bash shell
Q or E) Exit
c. Select Y when asked if you are sure you want to shutdown.
Are you sure you want to shut down the system?: y
d. Select N when asked if you want to crash the system.
Please note that shutting down the system will save some
information in the system logs, but not the complete current system
state. If you are shutting down the system because you are experiencing
problems with the current operation of the system, you may wish to
intentionally crash the system in order to capture the complete system
state.
Do you want to crash the system to capture the complete state?: N
Note: The CUA/CFA will response that the shutdown is now in process. If you have Putty (ssh) into the
CUA the window will close.
Shutdown the Centera Cluster
Establish a Local Connection to the Centera Cluster
If you do not know how to establish a local connection to the cluster, refer to How to Establish a Local
Connection
If you do not know the EMC confidential username and password, refer to Username and Password.
Shutting Down the Cluster
It is advisable to shut down a cluster only if a power outage is expected or if a maintenance activity
requires the cluster to be shut down.
Before shutting down a cluster make sure that:
3
40733025 (677.00 KB)
8/2/2023 3:48 AM
Last saved by EMC
 There is no other service intervention in progress.
 There is no software upgrade running: issue the show config version command to verify
 that you see a single code version for Active & Oldest code version …. and if displayed
 distribution status & Activation status: complete
 Application activity is halted: contact the application provider if necessary. Check the following for
activity.
 Tools > Field > Cluster Usage > Access Role
 Tools > Field > Network Information > Current External Connections
e. From CV select Commands > Shutdown and then select “yes” in the next Warning GUI.
Figure 1
Figure 2
f. For Gen2 and Gen3 hardware, go to the front of the cabinet. All front panel displays show the
node name, type and part number on the screen until the panel power LED light goes out. The
shutdown process is complete when this occurs on all nodes. This may take a few minutes to
complete.
4
40733025 (677.00 KB)
8/2/2023 3:48 AM
Last saved by EMC
Figure 3
g. For Gen4/Gen4LP hardware, go to the front of the cabinet and verify that the CSE Power LED
goes out on all nodes. This indicates that the shutdown process is complete. This may take a few
minutes to complete. When shutting down the CUA on a Gen4/Gen4LP the node will shutdown
(power off) for 30 seconds and then power up again unless the power (I/O) button is hit again
when it starts to power up.
Figure 4
h.
Note:
Go to the back of the cabinet and toggle all power switches to the OFF position.
For customer supplied racks locate and toggle off the rack main breakers.
Gen2 and Gen3 hardware
Gen4 hardware
Figure 5
5