0% found this document useful (0 votes)
34 views4 pages

VMAX3 Onlpost

The document outlines procedures for maintaining MMCS systems, including checking free disk space to prevent error code 08.0492.03, synchronizing Windows Firewall Configuration Tool (WFCT) settings, and enabling VMAX3. It also details steps for VMAX Managed File Transfer registration, updating site information, and ensuring proper dial-home configurations. Additionally, it emphasizes the importance of closing all programs before logging off to avoid issues with automated tasks.

Uploaded by

tachyon.20230417
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
34 views4 pages

VMAX3 Onlpost

The document outlines procedures for maintaining MMCS systems, including checking free disk space to prevent error code 08.0492.03, synchronizing Windows Firewall Configuration Tool (WFCT) settings, and enabling VMAX3. It also details steps for VMAX Managed File Transfer registration, updating site information, and ensuring proper dial-home configurations. Additionally, it emphasizes the importance of closing all programs before logging off to avoid issues with automated tasks.

Uploaded by

tachyon.20230417
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

 MMCS Free Disk Space Check and Cleanup

The purpose of this step is to prevent 08.0492.03 error code dial homes. Refer to KB 469168. 
When less than 25% percent of free disk capacity is left on a hard drive in the service processor,
a threshold is crossed, triggering the error code 08.0492.03 to dial home.

1. From the MMCS desktop, double-click on Computer. You will see something similar to what
is below:

In this example, the O drive is at 20% free space left, which is causing the 08.0492.03 to
post.

2. Double-click on the O drive, and then double-click on the 'release_files' folder. Review the
code executable's code level and EPack revision.

The example here shows the executable is for code level 5977.1125.1125 and EPack level
6846

3. Navigate back out to the root O drive. Review the folders in the O drive. If you find code
folders or multiple 'newcode' or 'oldcode' folders, please navigate to each and compare the
executable code level and EPack revision in those folders to the one found in 'release_files'.
If they are older or lower, the file packages and folders may be safely deleted. To delete the
files, please use 'Shift-Delete' as simply using Delete will send the files to the Recycle Bin
and not delete the space or the files.

4. If you can't find additional folders, then please have a look inside the 'Newcode' folder.
Typically the folder has no contents, but as already stated, this is where pre-staging of code
should be performed. Have a close look for sub-folders, and if old and obsolete files are
found, they should be deleted as well.

 Windows Firewall Configuration Tool (WFCT) sync between MMCS’s


The purpose of this step is to help stop false alarm dial homes. Refer to KB 516894. The 
following steps prevent a datestamp mismatch within the WFCT rules configuration JSON files
between MMCS-1 and MMCS-2.

1. Open a Command Prompt on MMCS-1


a. From MMCS-1 desktop, click on the Start button.
b. In the 'Search programs and files' field, type 'cmd'. The Command Prompt
(cmd.exe) program will appear, click on the icon in the programs menu or hit Enter.
2. Type 'o:' to switch to the O drive.
3. Type 'cd emc\wfct' to navigate to o:\emc\wfct folder.
4. Type 'wfct sync' to synchronize the files between MMCSs. You should see the following
displayed in the command prompt window:

5. Type 'wfct healthcheck' to ensure the files are synced and WFCT finds no issues on the
array. You should see the following displayed:

6. Please confirm that the second to last line reports 'Validation Success : 0'. If anything else
appears, please refer to KB article VMAX3 & VMAX All Flash: Error code: 08.04DC.30
through 3B to troubleshoot, or contact the VMAX Support Center for assistance.
7. If the WFCT Healthcheck comes back clean, the procedure is complete, and you may close
the command prompt.

 Enable the VMAX3:


From the SymmWin Menu-Bar select Tools option Inlines 
 To enable DA’s – At the prompt, from the Default Director, issue $BC,DA,F0,CE,0.
 Issue E0, verify that the DA’s are online.
 Enable Host Interfaces - Issue F0,CE,0 on every Channel Director.
 Issue E0, verify that host interfaces are online.

 VMAX Managed File Transfer registration


This step MUST be completed. 
Reference the VMAX Managed File Transfer (MFT) document in Solve Desktop on the steps to
setup registration for MFT.

Open Solve Desktop > VMAX All Flash, VMAX3, VMAX, and DMX > “select relevant platform” >
Customer Service Documentation > Reference Material > VMAX Managed File Transfer.
 Site Information

 From Simplified Symmwin, select Site Information and set/verify
o Spare Service Type: Deferred Service
o ESRS Push Mode: True
o The relevant VMAX3/VMAX All Flash Solutions to True.
 E.g. If eNAS is configured set Solutions eNAS to True
 Click Save once relevant values have been set.
 Update the Install base record in CSI Service Request

You need to update IB with eNAS information.

Fill out the IB group New Installation Request form from the IB Portal from
http://emc.force.com/BusinessServices :
And
http://emc.force.com/BusinessServices/SC_Case_Form?recordType=Install%20Base
%20Group&langForPage=en_US

Note: For VMAX3/VMAX All Flash with eNAS, you need two separate TLAs in the IB to add both
HYPERMAX OS / Enginuity level and NAS Code.
 SymmConnect:
 Follow the instructions in KB Article 338169 to manually enable SymmConnect monitoring. 
 Symm Connect installation instructions can be found on the SymmConnect Website:
http://omega.corp.emc.com/omega/AppSYR/application/Symmetrix/SymmConnect/
SymmConnect_Overview.aspx

 Call Home Information



 Enable Call Home and Run a Test Dial Home
Configure call home using instructions in the corresponding customer service procedure
and in the ConnectEMC for Windows Release xxx User Guide. Configure remote access
using customer’s specifications.

 Open Simplified Symmwin and goto the System Management tab. Under the
Verification/Sanity options select Test Call Home.

Please Contact the Customer Service Center for assistance if you have any issues with the
test dial home that cannot be resolved.

 For all Call Home Information Procedures reference


http://www.cs.isus.emc.com/csweb2/udh/udhhome.htm,

 KB Article 319799 for reference on where to get the information on the correct numbers for
dial-home?"
 Dial Home Information:
Check for and remove UUNET dial-home numbers. 
UUNET is a service EMC contracted to provide local numbers to be used for EMC device dial
home. The UUNET service provider has informed EMC that their services will no longer be
available as of December 31, 2007. All customer devices utilizing UUNET dial home numbers
must be reconfigured to utilize MCI or AT&T dial home numbers

For more information reference KB Article 302676.

 Update the SymmAPI Database on the host: (Required to be run on all hosts running Solutions
Enabler affected by the change. It is best practice to run on all hosts attached to this system. For SRDF 
configuration, suggest to run on servers attached to both R1(Local) and R2(Remote) site )

To update the SYMAPI database on the host, have the customer run the following command
symcfg discover

 For no dial home allowed site (dark site), EMC CE/IDE needs to collect SYR files and upload it
manually. 
From the SymmWin Menu Bar, select Procedures ® Procedure Wizard ® SYR Services ®
Collection SYR Information option, follow all the instructions. Click to zip them after files
generated and copy it into USB drive.

An issue has been seen where the Collecting SYR information script does not include all
required files. Verify that the zip file includes the siteinfo.ini file. If this file is not present repeat
the SYR Collection from the scheduler using the process described below. Please reference KB
Article 459723.

To create a complete zip file from the Scheduler, follow the steps below:

1. Launch SymmWin and open up Tools > Scheduler.


2. Highlight the NoProcDoneProcEntry(SyrInfo NOT_SIMUL) Task.
3. Click the green arrow at the top left.
4. Close SymmWin and reopen it. This will kick off the Task.
5. Once it is complete, go into o:\emc\public\syr\upload.

The new syrfiles.zip includes all files required.

Once connecting to EMC network, CE/IDE can upload it to SYR database manually:
Navigate to SYR web site
http://omega.corp.emc.com/omega/AppSYR/application/Common/SYRManualFileUpload/
SYRFileUpload.aspx?prod_id=0&flag=Search
Click on the left for “Manual Upload”, key in all necessary information and then select file syrfiles.zip to
upload.

 All open programs (except EMCRemote) MUST be closed prior to “Log Off”
All open programs on the Windows Desktop (except EMCRemote Host) must be closed prior to 
using the Logout dialog box for Windows 7. The only running program on the Taskbar is
EMCRemote Host.
Once all open programs are closed, to log out of the MMCS:
1. Click on the 'Start' button on the Windows Desktop.
2. Click on 'Log off' button on the right.
Failure to close all foreground programs on the MMCS can lead to failed automated tasks within
Symmwin and other services running on the MMCS. Reference KB Article 491913 for more
information.

You might also like