Dell Unity,VNX: How to run the check vdm script to detect problems in the vdm.cfg before rebooting or upgrading (User Correctable)

Reboot or failing over a datamover can create a data unavailable condition if the vdm.cfg is missing data.

The cause is presently unknown.

1. Prior to any reboots do the following
2. Transfer the attached file (checkVdmsV9.py) from this KB Article to the control station. (see Attachments below)
3. chmod 775 to checkVdmsV9.py
4. execute the file via ./checkVdmsV9.py 
5. This is an example of a clean check

1. The script will flag any vdm.cfg with missing information.
2. This is a example of a failure

1. When the vdm fails the sanity check we need to recover the vdm.cfg before any reboots.
2. We should notify the customer that the script has found a potential problem and any reboot/failover will create a DU situation.
3. We should run ls -l on the vdm.cfg effect and note the timestamps.
4. We should engage Support to recover a backup version of vdm.cfg making sure to run ls -l against the vdm.cfg before any recovery.
5. At this point the vdm.cfg would need to be recovered from an old collect support material or sccs.
6. The script also makes copies in your present working directory/vdmcfg
7. This would require escalation to level 2 to perform recovery
8. .After a datamover reboot of an effected system we should verify the vdm information is valid. Another words check to make sure any cifs server are online and the vdm has all of the exports.
9.  Execute the script again post reboot to validate the vdm.cfg file
10. It is recommended that the script be executed pre and post upgrade.

This is a example of a failure that does not require a recovery

---------------------------------------------------------------
VDM BAMBA2 configuration does not match with running configuration!

=====================
Current Configuration
=====================
Id = 6
Name = BAMBA2
Server = server_2
Slot = 2
VDM Interfaces = 1 / CFG VDM Interfaces = 1
CIFS Interfaces = 1 / CFG CIFS Interfaces = 1
CIFS Server = 1 / CFG CIFS Server =  1
Exports = 0 / CFG Exports = 1

You can see the information on the left of the forward slash matches the information on the right side with the exception of the exports.
We have information in the vdm.cfg but not in running memory.
This is because we have a export that refers to a invalid path that did not load during boot.

please note you cannot ignore the opposite scenario.
Exports = 1 / CFG Exports = 0
In this case there is one export running in memory, but not in the vdm.cfg file.
This would require recovery.