Windows 2003 Hosts cannot see EMC VMAX Storage - Troubleshooting

Windows 2003 Hosts cannot see EMC VMAX Storage - What are some troubleshooting tips from the storage side that can be done? Should Windows flags be checked along with WWN's?

Please follow below steps 

1) Check the HBA are configured properly at host end 

2) Check Proper WWNs are used in zoning and ports are logging fine. 

3) Check the IG(Initiator Group ) has been created with right WWNs 

4) SPC2 and OS2007 flags should enabled at Initiator (or) IG level(by default the   VMAX FA are enabled with these flags .) 

5) Check the Devices are in Ready (or) Read_Write state
5) Recheck Masking View again with proper (IG,SG and zoned Port_group ) are used.

***
Check the server hba zoning and logged in status in the VMAX array. Use
the below command 
symaccess -sid xxx list logins -wwn < wwn no>



***
There should be no more than 255 LUNs because Windows cant' see LUNs on target 255

NetApp Undedup Procedure

•   Confirm the available space on each volume using the command “df –g <volname>” 
•   Confirm the dedupe savings on each volume using the command “df –s <volname>” and/or “sis status /vol/<volname>”.
•  Confirm that the volume’s current utilization can accommodate the additional data blocks.
•   Pause snapmirror jobs by entering the “#” in the snapmirror.conf file on the destination system.
•  Resize both prod and COB volumes according to dedup savings.
•  Disable dedupe (ASIS) on each volume using the command sis off /vol/<volname>
•  Enter privileged command mode using the command “priv set diag”
•  Begin the process of un-deduping each volume using the command “sis undo /vol/<volname>”
•  Monitor processor utilization with the command “sis status /vol/<volname>.
•  Repeat for additional volumes.
•  Confirm that dedupe has been removed by comparing the output of df –g before and after the undedupe process.
•  Confirm that dedupe has been disabled by running the command “sis status”.
•  Confirm volume utilization by running the “df –g <volname>” command.
•  To stop undedup “sis stop /vol/path”.

Maximum NDMP sessions for Data ONTAP 8.x

Considerations when using NDMP

You have to take into account a list of considerations when starting the NDMP service on your

storage system.

• Data ONTAP supports a maximum of 16 concurrent backups, restores, or both on a local tape

drive.

This includes backups initiated by NDMP as well as by the storage system’s dump, restore, and

smtape commands.

However, a storage system supports a maximum of 32 dump or restore sessions and 32 smtape

sessions.

• NDMP supports a maximum of 128 concurrent sessions on NearStore and 40 on other systems.

The following table defines the maximum number of NDMP sessions for storage systems running Data ONTAP 8.x:

Platform	Max QSM/SV	Max QSM/SV	Max NDMP sessions	Max NDMP sessions
	(with NearStore)	(no NearStore)	(with NearStore)	(no NearStore)
==========	============	===========	===============	===============
FAS2040	160	64	232	136
FAS2240	120	64	192	136
FAS3040	160	64	232	136
FAS3070	320	64	392	136
FAS3140	160	64	232	136
FAS3160	320	64	392	136
FAS3170	384	64	456	136
FAS3210	120	64	192	136
FAS3240	320	64	392	136
FAS3270	320	64	392	136
FAS6030	384	96	456	168
FAS6040	384	96	456	168
FAS6070	512	128	584	200
FAS6080	512	128	584	200
FAS6210	512	128	584	200
FAS6240	512	128	584	200
FAS6280	512	128	584	200