linux ako fc_targetv

2.9.2015 12:04 | Přečteno: 1020× | army |

Blog je o tom ako z linux boxu spravit fibre channel SAN target

konfig

dva servery

 

• 1xdl380g6 ako fc_target beziaci fedoru 22
• 1xdl380g8 beziaci esx ako initiator
• medzi nimi brocade 200e

 

oba servery su osadene 2x ISP2432-based 4Gfc qlogic kartami. Pre spravne nakonfigurovanie G6 ako fc_targetu je potrebne prepnut karty z initiator modu do host/target modu

 

[root@localhost ~]# cat /etc/modprobe.d/qla2xxx.conf

options qla2xxx qlini_mode="disabled"

[root@localhost ~]#

 

a nasledne bud reloadnut modul, alebo ak je vola persistentna tak dracut -f a reboot. V druhom kole naintalujeme balik targetcli priamo z default repositories. targetcli je mgmt  tool, nad lio subsystemom umoznujuci spravovat fcoe iscsi fc a co ja viem este ake luny/targety. Kontrola pred samotnym nastavenim je, qlogic-ky v target mode, + dolezita vec tcm_qla2xxx modul (target fabric module) musi byt enabled v kerneli alebo modul.

 

[root@localhost ~]# grep -i qla2 /boot/config-`uname -r`

CONFIG_TCM_QLA2XXX=m

[root@localhost ~]# cat /sys/module/qla2xxx/parameters/qlini_mode

disabled

V tomto bode mozme spusit targetcli a nakonfigurovat si LUN, ktory neskor vyexportujeme

o- / ..................................................................... [...]
  o- backstores .......................................................... [...]
  | o- fileio ............................................... [0 Storage Object]
  | o- block ............................................... [0 Storage Object]
  | o- pscsi ................................................ [0 Storage Object]
  | o- ramdisk.............................................. [0 Storage Object]
  | o- user ............................................... [0 Storage Object]
  o- iscsi .......................................................... [0 Target]
  o- loopback ....................................................... [0 Target]
  o- qla2xxx ........................................................ [0 Target]

Takto vyzera cisty nenakonfigurovany vypis (zoznam prikazov "help") pomocou "ls". V tejto stromovej strukture sa pohybujeme rovnako ako v shelli teda napr "cd /backstores/" , "cd .."  a podobne

cely postup vytvorenie a vyexportovania lunu je nasledovny (v nasom pripade ramdisk), spustime teda targetcli a ideme

/> cd /backstores/ramdisk

/backstores/ramdisk> create test 10G

Created ramdisk test with size 10G.

/backstores/ramdisk> cd /qla2xxx/

cd /qla2xxx

/qla2xxx> info

Fabric module name: qla2xxx

ConfigFS path: /sys/kernel/config/target/qla2xxx

Allowed WWN types: naa

Allowed WWNs list: naa.2100001b32155a38, naa.2100001b321ef7ad

Fabric module features: acls

Corresponding kernel module: tcm_qla2xxx

/qla2xxx> create naa.2100001b32155a38

Created target naa.2100001b32155a38.

/qla2xxx>

/qla2xxx> cd naa.2100001b32155a38/luns

/qla2xxx/naa....32155a38/luns> create /backstores/ramdisk/test

Created LUN 0.

/qla2xxx/naa....32155a38/luns> cd ../acls

/qla2xxx/naa....32155a38/acls> create 200000e08b865e9f

Created Node ACL for naa.200000e08b865e9f

Created mapped LUN 0.

/qla2xxx/naa....32155a38/acls>

 

najprv som teda vytvoril ramdisk backstore s nazvom test velkosti 10Gb, potom v adresari qla2xxx prikazom info zistil wwnka kariet a pokracoval vytvorenim targetu, dalej v adresari luns vytvoril z backstoru "test" LUN0 a ten v adresari acl vyexportoval na wwnko  200000e08b865e9f (co je wwnko hbacky v G8micke). po vytvoreni vsetkeho strom vyzera takto

/qla2xxx/naa....32155a38/acls> cd /

/> ls

o- / ......................................................................................................................... [...]

o- backstores .............................................................................................................. [...]

| o- block .................................................................................................. [Storage Objects: 0]

| o- fileio ................................................................................................. [Storage Objects: 0]

| o- pscsi .................................................................................................. [Storage Objects: 0]

| o- ramdisk ................................................................................................ [Storage Objects: 1]

| | o- test ................................................................................................ [(10.0GiB) activated]

| o- user ................................................................................................... [Storage Objects: 0]

o- iscsi ............................................................................................................ [Targets: 0]

o- loopback ......................................................................................................... [Targets: 0]

o- qla2xxx .......................................................................................................... [Targets: 1]

| o- naa.2100001b32155a38 ............................................................................................. [gen-acls]

| o- acls ............................................................................................................ [ACLs: 1]

| | o- naa.200000e08b865e9f ................................................................................... [Mapped LUNs: 1]

| | o- mapped_lun0 .................................................................................. [lun0 ramdisk/test (rw)]

| o- luns ............................................................................................................ [LUNs: 1]

| o- lun0 ..................................................................................................... [ramdisk/test]

o- vhost ............................................................................................................ [Targets: 0]

/>

..Po nakonfigurovani na esx-e a natiahnuti tohto 10G lunu do virtualky ako raw mapped device som testol speed..ta dosahovala cca 400Mb/s sekvencneho zapisu pri jednej ceste a cca 770Mb/s pri dvoch round-robin cestach..teda plne v limitoch 4gfc protokolu.

 

D.

P.S.: kedze ja pisat neviem tak sry za formu..

 

       

Komentáře

[MP]

Skutecne Mb/s ?
Jak se to zachova, pokud virtualni stroj prijde o konektivitu na ten RAW v pripade tohoto typu reseni?

[drunkezz]

jj 400Mb/s ..vsak 4G fibre

co sa tyka vypadkov, zalezi od robusnosti riesenia....od aplikacie samotnej ktora by hypoteticky uzivala taky LUN, cez nizsie vrstvy (fs, lvm...), cez redundanciu konektivity az po redundanciu (replikaciu) samotneho storidzu....

Cize v najhorsom pripade (raw lun, jedna cesta, nereplikovany storidz) je SPOF cokolvek.

Opacny pripad je replikacia storidzu, multipathing, a lokalne cachovanie dat + app cluster, kde SPOF neexistuje (resp nemal by)

D.

[stary guru]

dost napicu rychlost starec, tu flakas storidze hore dole LUNy, Cuky, Luky, fuky, optiky a RAWka a uplne totalne odjebana rychlost...

[Michal Kubeček]

jj 400Mb/s ..vsak 4G fibre

Takže ne 400 Mb/s ale 400 MB/s. Ono 400 Mb/s by bylo zatraceně málo (a FC by na to byl zbytečný přepych).

[drunkezz]

jj blby som...

d.

[Prohnutá nudle]

(a FC by na to byl zbytečný přepych).

to zalezi, kdybys treba chtel nizkolatencne kopirovat diskety

[halapatla]

Kto inak z tohto ekountu prispieva ? Dusan ci Lukas ?

[drunkezz]

Hm.... to D. nakonci hodne naznacuje...kto sa pyta?:)
D.

[halapatla]

L. a M. sa pytaju predsa....

[Prohnutá nudle]

Hezke, dik za ukazku

[Peter Golis]

Pekné.