Unisphere 9.x with VMAX 40k

Recently, I update Unisphere and Solutions Enabler to 9.0 for the VMAX 40k.  Unisphere 8.4 will not be supported after May 2020.  Few things are not supported for VMAX 40k in Unisphere 9.0.  Belows are the things I don't like about new Unisphere 9.

1. I cannot export list of luns in storage group.  I guess EMC wants customer to use ViPR SRM to run report (not sure if this is only applied to VMAX 40k)
2. No more provision template for VMAX 40k and that is not convenient.  
3. Cannot change FAST priority in the GUI any more for SG of VMAX40k
4. Heatmap is not shown in a single page.  

Heat Map in 8.4

Heat Map in 9.0

      5.   In Unisphere 8.4, if you want to delete meta members after dissolve a meta lun, you can select the option to delete meta members.  However, it will only delete meta head in Unisphere 9.  It will be fixed in Unisphere 9.1 according to support.  Because there is no more meta from VMAX, I suspect the developer forget about the VMAX 40k.    

6. There is a limitation with Unisphere 9.0.  Only the first 1024 luns will be shown.  You can use the filter to display the luns after the first 1024.  The filter for lun label does not work too well in 8.x.  However, once it is fixed in version 9, now, only the first 1024 luns will be shown.  See EMC kb Unisphere for PowerMax: Maximum viewable amount is 1024 volumes(000529643)

There was a bug in earlier version of Unisphere 8.x.  When you try to delete a meta lun under Virtual lun, it will crash the Unisphere GUI for VMAX 40k.  It is fixed in Unisphere 8.4.  Glad it is passed to Unisphere 9.0.  Also, if you try to create metalun from Unisphere, striped is populated auto and cannot be changed.  I have not tried to create concatenated lun with CLI in SE 9.0.

Just a reminder don't forget to change the smc password after installing Unisphere.

For VMAX 40k, you cannot change the Unisphere smc password running in SP.  So, make sure to restrict IP access to SP from the network. 

========================================================================
Just upgrade to Unisphere 9.1 (12/2019) 
It does fix the issue mentioned before for dissolve and delete meta luns.  However, it generates 3 new problems.

a) AD login does not work after upgrade.  (using local account at the moment)
b) Cannot customize performance alert for each thin pool / disk group.  (no workaround)
c) Dash Board reduces the overall health by 20 points because SSD pool is 95% full (recommendation  by vendor is to reserve only 1% of space given no lun is bounded / pinned to SSD and only thin provision is used).  This is not an issue.  Just ignore it. 

Hopefully, next patch fixes it. 

Also database in 9.1 is different.  Upgrade fails at database upgrade.  Since I ran all the monthly reports, I actually need to uninstall 9.1 and then install again in another folder.  So, it is a fresh installation for me.  
========================================================================

Update to Unisphere 9.1.0.20 (11/2020)  

AD login issue is still not resolved.  Still using local account.  

Alert customization for each Thin Pool / Disk Group seems fixed if I set it up in IE (won't work with Chrome).   

I doubt the last one mentioned before will be fixed.  Dash Board still reduce overall health by 20 points for SSD usage over 95%.  I will probably stay in this version until migration to PowerMax.  

Performance between different OS for Raspberry pi 4

Raspup 8.2 is the first one I installed in Raspberry pi 4 (4GB RAM).  It is ok but I am not happy with the performance for web browsing.  So, I tried Gentoo and Raspberry Pi OS.  I got the Raspberry pi 4 as a desktop replacement for the old laptop for my parents.  They only use browser or goto youtube.  

Definitely, Raspberry Pi OS is slightly faster than Gentoo.  Raspup 8.2 performance is the worst among the three.  Since they use it for browsing, I have not spent time to do research on how to make it faster.  So, I only use default settings.  

You can find the OS links below.  

Raspup | Home (eezy.xyz)

Releases · sakaki-/gentoo-on-rpi-64bit · GitHub

Raspberry Pi OS – Raspberry Pi

AppSync login page won't load with 404 error

 After Windows patching and AppSync server reboot, the management page of AppSync won't load.  It only show the 404 error Not found.  Restart server makes no difference.  Check from support page and find the kb 501522  https://support.emc.com/kb/501522

I do see the three files with undeployed below.  So follow the kb and the issue is fixed.  

apollo.ear.undeployed

archway-ear.ear.undeployed

remotex.rar.undeployed

Below is kb501522 from EMC support site.  

Cause

This may be seen if the Appsync Server services are Started and Stopped in quick succession. There are a number of files, such as E:\EMC\AppSync\jboss\.\standalone\..\applications\apollo.ear which are deployed by the Appsync Server during startup. If the service is stopped before these files are fully deployed the Appsync Server may begin to throw this error.

When we check the location C:\EMC\AppSync\jboss\applications we should see the following 6 files in a healthy system: 

• Apollo.ear
• apollo.ear.deployed
• archway-ear.ear
• archway-ear.ear.deployed
• remotex.rar
• remotex.rar.deployed

When we check on a system showing the "Error 404 not found" error we should find some of these files marked as undeployed, eg "apollo.ear.undeployed ".

Workaround

In order to resolve this issue we have to get the Appsync Server service to deploy the .EAR files. Follow the procedure outlined below to accomplish this. 
When we find undeployed files in the C:\EMC\AppSync\jboss\applications folder perform below mentioned steps to resolve:

1. Stop all the services.
2. Take backup of the C:\EMC\AppSync\jboss\applications.
3. Rename Apollo.ear.undeployed to Apollo.ear.dodeploy.
4. Perform the same steps as step 3 in case any other EAR files are also shown as undeployed.
5. Start the services.
6. Check the status for .EAR files again at the location C:\EMC\AppSync\jboss\applications.

i. Apollo.ear

ii. apollo.ear.deployed

iii. archway-ear.ear

iv.archway-ear.ear.deployed

v.remotex.rar

vi.remotex.rar.deployed

7. Try to log in into appsync GUI after 5 minutes and you should be able to log in.

Update Cisco DCNM to 11.3(1) due to security Vulnerabilities

Because of Cisco DCNM security issues (see below), just update DCNM to 11.3(1).  Update should be done ASAP.

I am not using the appliance and it is running on Windows with version 11.1(1).  It is running with Oracle Express 11g and managing only MDS FC switches.  We don't use advance features like SAN Insight and it is a standalone Windows server.  Upgrade step is pretty straight forward.

https://www.cbronline.com/data-centre/cisco-data-center-network-manager/

Setting up PuppyLinux on my Raspberry

Just receive my Raspberry pi 4 with 4GB of memory.  Decide to install Raspup 8.2 on it.  Details instructions can be found in Raspup page.

I copy the Windows instructions below.

1. Download Raspup image from the Downloads page and check the checksum.
2. Extract the image file from the downloaded .zip file, so you now have "raspup-XXXXXX.img".
3. Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example G:) by looking in the left column of Windows Explorer. You can use the SD Card slot (if you have one) or a cheap Adapter in a USB slot.
4. Download the Win32DiskImager utility (it is also a zip file). You can run this from a USB drive.
5. Extract the executable from the zip file and run the Win32DiskImager utility; you may need to run the utility as Administrator! Right-click on the file, and select 'Run as Administrator'
6. Select the image file you extracted above.
7. Select the drive letter of the SD card in the device box. Be careful to select the correct drive; if you get the wrong one you can destroy your data on the computer's hard disk! If you are using an SD Card slot in your computer (if you have one) and can't see the drive in the Win32DiskImager window, try using a cheap Adapter in a USB slot.
8. Click Write and wait for the write to complete.
9. Exit the imager and eject the SD card.
10. You are now ready to plug the card into your Raspberry Pi.
11. In Windows, the SD card will appear only to have a fairly small size once written - about 512 MB. This is because most of the card has a partition that is formatted for the Linux operating system that the Raspberry Pi uses which is not visible in Windows. If you don't see this small directory with files such as kernel.img then the copy may not have worked correctly.

PuppyLinux is my favourite Linux and it is a nice desktop for my dad to browse the net.

To read Chinese, just install package fonts_arphic_uming.  

To create Shortcut, go to /usr/share/applications and drag the icon to the Desktop.