Data Storage

NetApp FAS3170 Configuration

NetApp FAS3100 Series Storage Configuration

NetApp FAS3100 Series can be accessed by NetApp System Manager (GUI based management tool), FilerView through Web browser, and CLI through (telnet or ssh). This configuration guide is for FilerView.

Access FSA 3170 using Internet Explorer:
Enter the FilerView URL:
http://X.X.X.X/na_admin/

Click on FilerView icon (left pane) to open FilerView window.

NetAPP FilerView Icon

Storage Configuration:

1. Create a New Volume
● Volume -> Add
Volume Wizard will launch, click Next
NetAPP FilerView Volume Wizard

-> next screen, Volume Wizard – Volume Parameters, enter the Volume Name, click Next
Note: “vol0″ already exist, this is the root volume.
-> next screen, Volume Wizard – Flexible Volume Parameters, select the Containing Aggregate.
-> next screen, Volume Wizard – Flexible Volume Size, enter Volume Size and Snapshot Reserve
-> next screen, Volume Wizard – Commit, Review the summary and click Commit.

2. Create a New LUN
● LUNs -> Add
In the right pane, “Add LUN”, use the following:
Path: /volume_name/LUN_number
LUN Protocol Type: Solaris, Windows, Linux, VMware, etc…
Size: LUN_size
Then click “Add” button

3. Create a New Storage Group
● LUNs -> Initiator Groups -> Add
Initiator can be FC, iSCSI or FCoE
“Add Initiator Group”, use the following:
Group Name: Meaningful name to identify initiator
Type: FCP or iSCSI
Operating System: Solaris, Windows, Linux, VMware, etc…
Initiators: Enter a list of initiator  name, a list should appear, click the “Add” button.

4. Assign LUN to Initiator (LUN Map)
LUNs -> Manage
- Locate the intended LUN.
- At the far right column, Maps, click on No Maps to open LUN Map window.
- Click Add Groups to Map at the top right corner
- Select Initiator Group from the list box on the right, then click the Add button.
- Enter the LUN ID (Start at LUN 0).
- Click Manage LUNs at the upper left corner. The initiator should be listed in the Map column.

CLI


Telnet to Netapp

To create a volume:
vol create $Volume_Name $Aggregate $Volume_Size
example: vol create WindowsVol aggr1 1000m
Created a volume name WindowsVol in aggr1 size of 1GB

To create a LUN:
lun create -s $LUN_size -t $OS /vol/$Volume_Name/LUN_Name
example: lun create -s 1000m -t Windows_2008 /vol/WindowsVol/LUN0
Created a LUN name LUN0 in WindowsVol Volume


Be the first to comment  Posted by Ferdy - March 10, 2011

Categories: Data Storage   Tags:

Fibre Channel SAN

Fibre Channel SAN Notes from Brocade FC Protocol Training.

Fabric: term to describe a generic switching environment, it can consist of one or more interconnected switches (domains).

One Fibre Channel Switch = One Fabric Domain.
Maximum Domains = 239 in a single Fabric based on 24-bit addressing.
Principal Switch: Determine precedence between FC Swithced without adding a separate external. Fabric management software. it facilitates the initialization of the Fabric, and acts as controller of domains.

Switch Ports:
E_port – expansion port, connects 2 FC switches together to make a Fabric.
F_port – Fabric port where N_port attaches.
FL_port – Fabric loop port where NL_Port attaches.

Device Ports:
N_port – port designator for direct fabric attached devices.
NL_port – device that is attached to the loop (seldom used, support for old FC stuff).

FC_ID: 24 Bit Address Space: Dynamically assigned during login.
| Domain ID | Area ID | Node ID |
Domain ID = upper 8 bits, identifies the FC Switch
Area ID = middle 8 bits, identifies port number
Node ID = lower 8 bits, N_Port address

Unique Identification:
-Fixed 64bit value assigned by manufacturer.
-Used in mapping to upper layer protocols.
WWPN: uniquely identify a port (Port_Name).
WWNN: uniquely identify a node (Node_Name).

FC defines two types of login procedures:
Fabric Login (flogi) – After link established, N_Port sends flogi frames to the fabric and receive responses back.

N_Port Login (plogi) – Enable a N_port to communicate with another N_port. Once logged in, it will stay indefinitely.

Fiber Channel Frame

FC transmits data in frames, defines variable length:
36 bytes of overhead
SOF – 4 bytes
Header – 24 bytes
CRC – 4 bytes
EOF – 4 bytes
Up to 2112 bytes of payload
Optional Header – up to 64 bytes
Data – up to 2048 bytes

FC Layers:
FC-4: Upper layer protocola interface – SCSI, IP, and so on roughly as transport layer in the OSI model.
FC-3: common Services
FC-2: Data delivery – Framing Protocol and Flow Control. Similer to layer 2 of OSI.
FC-1: Encoding – 8b/10b (1,2,4,9 Gb/s) and 64b/66b (10 Gb/s). Link Controls
FC-0: Physical Interface – Media Connectors and Cables.

FC starndards site: http://www.t11.org
FC-FS: Fibre Channel Framing and Signaling Interface
FC-LS: Fibre Channel Link Service
FC-GS: Fibre Channel General Services
FCP: Fibre Channel Protocol for SCSI

FC switches:
Brocade 4900: 4Gb FC
Cisco MDS 9216A: 2Gb and 4Gb FC
Cisco MDS 9222i: 4Gb FC and 1Gb Ethernet

Targets:
EMC Symmetrix
EMC Clariion CX4
IBM DS4700

Be the first to comment  Posted by Ferdy - February 25, 2011

Categories: Data Storage, Network   Tags: ,

FCoE

FCoE is part of FC-BB-5 project: http://www.t11.org/fcoe

FCoE converges FC and Ethernet (HBA + NIC = FCoE) to reduce infrastructure costs (less adapters, cabling, and power consumption).

Terminologies:
FC – Fiber Channel
FCoE – Fiber Channel over Ethernet
CEE – Converged Enhanced Ethernet (from Brocade)
CNA – Converged Network Adapters
DCFM – Brocade Data Center Fabric Manager

FCoE Before and After Diagram

FCoE Before and After Diagram from Cisco Training


FC Payload inside Ethernet FrameFC payload inside Ethernet Frame



FCoE and FC LayersComparing FC and FCoE Layers



Encapsulated FC Frame



Example FCoE Switches and CNAs Products:
Prices as of Feb 2011 using Google Shopping (Best price from top rated stores).

FCoE Switches:
Cisco Nexus 5020: $22,209 (Amazon.com)
Cisco Nexus 5010: $10,619 (CompSource.com)
Brocade 8000: $9,905.00 (NextDayPC.com)

10 Gigabit CNAs:
Qlogic QLE8142: $1,394 (Buy.com)
Emulex OCE10102-FM: $1,393 (KYRO.com)
Intel x520-SR2: $1,168 (2020pc)

Be the first to comment  Posted by Ferdy - February 18, 2011

Categories: Data Storage, Network   Tags:

« Previous PageNext Page »