Bijdrage NetApp examen B&R NSO 510

Bij deze mijn bijdrage om het NetApp Data Protection examen NSO 510 goed voor te kunnen bereiden.  Bij het afnemen van het examen NSO 510, wordt er  van je verwacht dat er van de volgende onderdelen voldoende kennis en kunde aanwezig is:

  • Snapshots
  • SnapVault
  • SnapMirror
  • SyncMirror
  • MetroCluster
  • SnapProtect
  • OnCommand System Manager
  • OnCommand Unified Manager
  • SnapManager
  • SnapDrive

Lees de introductie.

Initiele configuratie Brocade en Cisco

BROCADE
Upgrade Firmware or FOS
msfsw1:admin> version
msfsw1:admin> firmwaredownload

Assign Domain ID (default 1)
msfsw1:admin> switchdisable 
msfsw1:admin> configure (enter yes, Domain 10 Fabric A or 11 for Fabric B, rest default)
msfsw1:admin> switchenable

Assign port speed (use fixed to avoid negotiation errors and prolonged fabric rebuilds)
msfsw1:admin> switchshow
Index Port Address Media Speed State     Proto
==============================================
  0   0   0b0000   id    N4   Online      FC  F-Port  50:0a:09:81:88:cc:d6:88

msfsw1:admin> portcfgspeed 0 4
msfsw1:admin> switchshow
Index Port Address Media Speed State     Proto
==============================================
  0   0   0b0000   id    4G   Online      FC  F-Port  50:0a:09:81:88:cc:d6:88


Create FC Zones (voorbeeld 2 Netapp targets en 1 HBA)
msfsw1:admin> alicreate na01_p0a, 50:0a:09:81:88:cc:d6:88
msfsw1:admin> alicreate na02_p0a, 50:0a:09:81:98:cc:d6:88
msfsw1:admin> alicreate msesx1_p1, 20:00:00:1b:32:1b:45:dd
msfsw1:admin> zonecreate z_msesx1, "na01_p0a;na02_p0a;msesx1_p1"
msfsw1:admin> cfgcreate ESXCfg_ver01, z_msesx1
msfsw1:admin> cfgsave
yes, y, no, n): [no] y
msfsw1:admin> cfgenable ESXCfg_ver01
(yes, y, no, n): [no] y

mmsfsw1:admin> cfgshow
Defined configuration:
 cfg:   ESXCfg_ver01
                z_msesx1
 zone:  z_msesx1
                msesx1_p1; na01_p0a; na02_p0a
 alias: msesx1_p1
                20:00:00:1b:32:1b:45:dd
 alias: na01_p0a
                50:0a:09:81:88:cc:d6:88
 alias: na02_p0a
                50:0a:09:81:98:cc:d6:88

Effective configuration:
 cfg:   ESXCfg_ver01
 zone:  z_msesx1
                20:00:00:1b:32:1b:45:dd
                50:0a:09:81:88:cc:d6:88
                50:0a:09:81:98:cc:d6:88

Save and Restore the configuration:
mmsfsw1:admin> configupload
mmsfsw1:admin> configdownload

CISCO
Upgrade Firmware or FOS
msfsw1# show version
msfsw1# show install all impact system
msfsw1# install all system
msfsw1# show install all status

Create a VSAN (avoid using default VSAN 1)
msfsw1# conf t
msfsw1 (config)# vsan database
msfsw1 (config-vsan-db)# vsan 2
msfsw1 (config-vsan-db)# vsan 2 interface fc1/8
msfsw1 (config-vsan-db)# vsan 2 interface fc1/9
msfsw1 (config-vsan-db)# end

Assign the Domain ID (Static or Preferred)
msfsw1# conf t
msfsw1 (config)# fcdomain domain 10 static vsan 2
msfsw1 (config)# end

Assign Port Speed
msfsw1# conf t
msfsw1 (config)# interface fc 1/1
msfsw1 (config-if)# switchport speed 4000 
Cntrl C

Verify Switch Configuration
msfsw1# show vsan membership
vsan 2 interfaces:
fc1/8 fc1/9
msfsw1# show fcdomain
The local switch is the Principal Switch.
 Local switch WWN:  10:00:00:0d:ec:19:cb:0e
 Running fabric name:  10:00:00:0d:ec:19:cb:0e
 Running priority:  128
 Current domain ID: 0x0a (10)
msfsw1# show interface brief (auto or fixed)
msfsw1# show flogi database

Create FC Zones
msfsw1# conf t
msfsw1 (config)# device-alias database
msfsw1 (config-device-alias-db)# device-alias name msesx1_p1 pwwn 20:00:00:1b:32:1b:45:dd
msfsw1 (config-device-alias-db)# device-alias name na01_p0a pwwn 50:0a:09:81:88:cc:d6:88
msfsw1 (config-device-alias-db)# end
msfsw1# conf t
msfsw1 (config)# device-alias commit
msfsw1 (config)# zone name z_msesx1 vsan 2
msfsw1 (config-zone)# member device-alias msesx1_p1
msfsw1 (config-zone)# member device-alias na01_p0a
msfsw1 (config-zone)# exit

Create and Activate Zonesets
msfsw1# conf t
msfsw1 (config)# zoneset name ESXCfg_ver01 vsan 2
msfsw1 (config-zoneset)# member z_msesx1 
msfsw1 (config-zoneset)# end
msfsw1# conf t
msfsw1 (config)# zoneset activate name ESXCfg_ver01 vsan 2

Save the Configuration:
msfsw1# copy running-config startup-config

Gather support data:
msfsw1# show tech-support details

Wat is zoning en masking

Zoning vind plaats op de SAN switch en masking vind plaats op de Storage array.

De oplossingen om initiators & targets te grouperen zijn: zoneren (1 initiator & multiple targets), igroup (WWPNs or IQNs) en Port sets (LIFS).

Een iGROUP is een manier om hosts/initiators (HBAs, NICs) te groeperen tot welke LUNs deze toegang hebben. Er is hier sprake van LUN masking.

LUN masking mechanism allows you to make LUNs available to some initiators and unavailable to others.

NetApp omschrijving van igroups:

Initiator groups (igroups) are tables of FC protocol host WWPNs or iSCSI host node names. You can define igroups and map them to LUNs to control which initiators have access to LUNs.

Typically, you want all of the host’s HBAs or software initiators to have access to a LUN. If you are using multipathing software or have clustered hosts, each HBA or software initiator of each clustered host needs redundant paths to the same LUN.

You can create igroups that specify which initiators have access to the LUNs either before or after you create LUNs, but you must create igroups before you can map a LUN to an igroup.

Initiator groups can have multiple initiators, and multiple igroups can have the same initiator. However, you cannot map a LUN to multiple igroups that have the same initiator.

Note: An initiator cannot be a member of igroups of differing ostypes.

Wat een port set(s) is:

Portsets limit host access to certain paths when they are bound to: An igroup

A Portset contains an access list consisting of LIFs

Command to group initiators to allow to be mapped to LUNs: igroup create

Over iGROUP throttles:

Data ONTAP implements a mechanism called igroup throttles, which you can use to ensure that critical initiators are guaranteed access to the queue resources and that less-critical initiators are not flooding the queue resources.

Operations using IGROUP throttles on a NetApp:

  • To assign a specific percentage of the queue resources on each physical port to the igroup
  • To reserve a minimum percentage of queue resources for a specific igroup
  • To limit the number of concurrent I/O requests an initiator can send to the storage system
  • To restrict an igroup to a maximum performance of use

https://library.netapp.com/ecmdocs/ECMP1368845/html/GUID-251C3111-CBAE-4DE2-82A1-3F452726FF34.html

Verder:

Igroups, port sets and LUN mappings are replicated across the SAN replicated database ring.

  • Igroups, port sets and LUN mappings

SAN management daemon process heet: bcomd.

Lees: What a cluster replication ring is:

https://library.netapp.com/ecmdocs/ECMP1196798/html/GUID-C8F1D8ED-7420-48CC-8CC8-FF0A80399AA0.html

 

Welkom!

Welkom op deze website. Deze website heeft als doel kennis en kunde te delen en nieuwe ontwikkelingen te beoordelen of te bespreken. Mijn kennis en kunde is het managen en inrichten van Data ICT infrastructuren, zeer hoog beschikbare geclusterde fysieke blade servers en Virtualisatie omgevingen. Termen als Business Continuïteit, data management, Operational Recovery en Disaster Recovery zijn zaken die hier aandacht gaan krijgen inclusief de gerelateerde fabrikanten en Cloud oplossingen en wat zoal gehyped en/of gebuzzed wordt in de ICT wereld.

Ik hoop dat dit initiatief goed gebruikt gaat worden en wie weet dat deze site uitgroeit tot een toegevoegde waarde om kennis en kunde te delen en te verbeteren.