Free NS0-502 Exam Dumps Preview

DOT 8.0.1 first allowed both FCoE and traditional Ethernet protocols using the same Unified Target Adapter (UTA).

http://www.cosonok.com/2012/02/netapp-ns0-502-study-notes-part-34-san.html

With no reserves set and no snapshots being taken, using default options, the LUNs will each consume 100GB of the volume.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_lun.1.html
lun create -s size -t ostype [ -o noreserve ] [ -e space_alloc ] lun_path

By default, the LUN is space-reserved. To manage space usage manually, -o noreserve can be specified. Using this option will create a LUN without any space being reserved. Provisioning threshold events can be enabled by specifying -e space_alloc option. This option has to be used in conjunction with -o noreserve.

Best practice calls for dual fabric. This would also be the most cost effective approach at this size.

5 x dual-port HBAs for Windows = 10 ports split across two fabrics 4 x single-port HBAs for Linux = 4 ports on any fabric. 10 x dual-port HBAs for Solaris = 20 ports split across two fabrics.

Each FAS3100 has 4 onboard FC ports, for a total of 8 ports split across two fabrics.

34 initiator ports and 8 target ports totalling 42.

snap delta [ vol_name [ snapshot-name ] [ snap_shot-name ]]

Displays the rate of change of data between snapshots. When used without any arguments it displays the rate of change of data between snapshots for all volumes in the system, or all aggregates in the case of snap delta -A. If a volume is specified, the rate of change of data is displayed for that particular volume.
The query can be made more specific by specifying the beginning and ending snapshots to display the rate of change between them for a specific volume. If no ending snapshot is listed, the rate of change of data between the beginning snapshot and the Active File System is displayed.

http://backdrift.org/man/netapp/man1/na_snap.1.html

Steps prior to replacing a failed Brocade FC Switch:

Change the domain ID of the replacement switch to the domain ID of the failed switch.
Clear all zoning configuration on the replacement switch.
Change the core PID format of the replacement switch to the core PID format of the failed switch.

When hard zoning (domain ID plus port) is in use and a host HBA is replaced, no changes need to be made provided the new HBA is connected to the same port.

http://www.cosonok.com/2012_02_01_archive.html

When designing a NetApp storage solution for a customer, check the row in the IMT for Host OS & patches
HBA driver
Volume Manager
File System
Clustering

http://www.cosonok.com/2012_02_01_archive.html

Enter an account that can be used as a service account for the SnapDrive services. This account must be a member of the Built-In Administrators group.

http://www.sysadmintutorials.com/tutorials/netapp/installing-netapp-snapdrive-for-windows/

Explanation: while the host will see the space freed up by the deletion, the thin-provisioned LUN is not going to shrink on the volume until space reclamation is run.

NetApp thin provisioning is designed to allow you to present more logical storage to hosts or users than you actually have in your physical storage pool. Instead of allocating space upfront, storage space is dynamically allocated to each volume or LUN as data is written. In most configurations, free space is also released back to your common storage pool when data in the volume or LUN is deleted (and is not being held by any Snapshot copies).

https://communities.netapp.com/docs/DOC-8122

From a storage system perspective, the percentage used of a LUN will always increase and never decrease unless space reclamation is run.

http://netappsky.com/wp-content/uploads/2010/09/Lun_Provisioning.pdf

lun stats -i interval [ -c count ] [ -o ] [ -a | lun_path ]

The -i option will report per LUN performance statistics at the per second interval given.
The default output format for -i is as follows:

Read Write Read Write Average Queue Lun
Ops Ops kB kB Latency Length
#### #### ##### ##### ##.## ###.## lun_path

http://backdrift.org/man/netapp/man1/na_lun.1.html

When documenting the existing configuration, factors that should be considered include:

disk ownership settings
igroups being used
protocols in use
Snapshot configuration

http://www.cosonok.com/2012/02/netapp-ns0-502-study-notes-part-14-san.html

Power on order:

Network Switches.

Disk Shelves
Any Tape Backup Devices
NetApp Controller Heads.

If a NetApp storage system fails on its first boot; check for a description of the problem on the LCD and console, and follow the instructions.

http://www.cosonok.com/2012/02/netapp-ns0-502-study-notes-part-34-san.html

http://www.cosonok.com/2012/02/netapp-ns0-502-study-notes-part-34-san.html

Because the question requests that you not change the igroup attributes, the igroup is implicitly a non-ALUA igroup. So the ESX4.x system must use VMW_SATP_DEFAULT_AA. That is the best answer here.

Note: the best practice contradicts this:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010713
https://kb.netapp.com/support/index?page=content&id=3011171

In ESX/ESXi 4.x, MRU is the default policy for all NetApp storage devices in ALUA mode. However, for the ESX/ESXi 3.x release, the default policy for the NetApp devices is Fixed.

3. X and ESX 4. X hosts, the following solutions exist:

Initiators for ESX 3.X should placed into a dedicated igroup: ALUA should not be enabled.
The ESX 3.X hosts should continue using the Fixed policy.
Initiators for ESX 4.X should placed into a dedicated igroup.
ALUA should be enabled.
The ESX 4.X hosts should continue using the MRU or RR path selection policy as described above.

VLANs are a standard layer 2 mechanism for segmenting and effectively isolating application traffic. Data on one VLAN cannot be seen or accessed by data traversing another VLAN, they are effectively separate streams.

Common best practices are to isolate IP storage traffic from other protocols, for performance and security.
It is also beneficial to isolate management traffic to a restricted VLAN.

https://devcentral.f5.com/articles/virtualization-how-to-isolate-application-traffic#.UiyA6zAgZBU

NetApp recommended Ethernet topology for iSCSI: LAN with VLANs implemented.

http://www.cosonok.com/2012/02/netapp-ns0-502-study-notes-part-14-san.html

In order to capture an application consistent (i.e. quiesced) image, software like SnapManager or the Virtual Storage Console must be employed to coordinate the snapshot procedure with the application. So snapshots are not ALWAYS application consistent.

FC_Switch1 - 9 are edge switches. FC_Switch 9-10 are core edge switches.

http://www.filibeto.org/sun/lib/nonsun/brocade/53-0000231-05.pdf

sanlun fcp show adapter : UNIX CLI NetApp host utility command to verify WWNN and WWPNs esxcfg-info : VMware ESX CLI command to verify WWNN and WWPNs

http://www.cosonok.com/2012_02_01_archive.html

cfmode single-image

All LUNs in the active/active configuration are available on all ports in the active/active configuration by default. As a result, there are more paths to LUNs stored on the active/active configuration because any port on each node can provide access to both local and partner LUNs.

Each LUN has two paths per fabric from each initiator port. 4 paths x 10 LUNs = 40 paths total.

http://hd.kvsconsulting.us/netappdoc/733docs/html/ontap/bsag/GUID-31DC026F-2B78-425A-BA55-487782F9909A.html

Brocade® Web Tools, an intuitive and easy-to-use interface, enables IT organizations to monitor and manage single Brocade Fabric OS® (FOS)-based switches.

http://www.brocade.com/downloads/documents/data_sheets/product_data_sheets/WebTools_DS_10.pdf

The factory settings for switches in the Cisco MDS 9000 Family have only the default VSAN 1 enabled. We recommend that you do not use VSAN 1 as your production environment VSAN. If no VSANs are configured, all devices in the fabric are considered part of the default VSAN. By default, all ports are assigned to the default VSAN.

http://www.cisco.com/en/US/products/ps5989/products_configuration_guide_chapter09186a0080662ce3.html#wp1094457

show version - To display information about the currently loaded software along with hardware and device information
http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_s4.html#wp1499591

Cabinet diagram information:

Physical location of the rack in the datacenter.
Rack identifying information.
Location in the rack of NetApp storage controllers and storage shelves.
Switch placement.
Storage shelf connectivity.

http://www.cosonok.com/2012/02/netapp-ns0-502-study-notes-part-24-san.html