Dell EMC ML3 Support

we don't have such a library to test here, but if it's controllable via scsi (or iscsi) and works with 'mtx' it should work with pbs
 
Hi All,

We have Dell ML3.
Now we are in 2024, so any updates on this? Any help or guidance for PBS with ML3?
Look forward to any useful info.
 
did you try it? if yes, what errors do you get/ what problems do you have?

my last comment still stands, if it's a lib that works with 'mtx' on linux, it should work with pbs, see also https://pbs.proxmox.com/docs/tape-backup.html on how to set up tape drives/libraries in pbs
 
# lspci | grep -i fibre
03:00.0 Fibre Channel: Emulex Corporation LPe31000/LPe32000 Series 16Gb/32Gb Fibre Channel Adapter (rev 01)
03:00.1 Fibre Channel: Emulex Corporation LPe31000/LPe32000 Series 16Gb/32Gb Fibre Channel Adapter (rev 01)

Further, neither streamers nor tapes in PBS see any typical console commands.
proxmox-tape changer scan
proxmox-tape status
proxmox-tape scan
proxmox-tape inventory
proxmox-tape drive scan
 
can you post the output of 'dmesg' ?
 
dcsapak said:
can you post the output of 'dmesg' ?
Click to expand...
Hi, Dominik! Thanks for response!

Code: 
[8015645.550066] lpfc 0000:03:00.0: start 94 end 138 cnt 44
[8015645.550068] lpfc 0000:03:00.0: 94: [8015644.453553] 0:(0):0408 Report link error true: <x3:x103>
[8015645.550070] lpfc 0000:03:00.0: 95: [8015644.453554] 0:(0):0279 lpfc_nlp_release: ndlp: xffff917246243400 did fffffe refcnt:0 rpi:0
[8015645.550070] lpfc 0000:03:00.0: 96: [8015644.453555] 0:(0):0900 Cleanup node for NPort xfffffe Data: x0 x0 x0
[8015645.550071] lpfc 0000:03:00.0: 97: [8015644.453555] 0:(0):2819 Abort outstanding I/O on NPort xfffffe Data: x0 x0 x0
[8015645.550072] lpfc 0000:03:00.0: 98: [8015644.453556] 0:(0):0932 FIND node did xfffffe NOT FOUND.
[8015645.550072] lpfc 0000:03:00.0: 99: [8015644.453556] 0:(0):0932 FIND node did xfffffe NOT FOUND.
[8015645.550073] lpfc 0000:03:00.0: 100: [8015644.453556] 0:(0):0932 FIND node did xfffffe NOT FOUND.
[8015645.550074] lpfc 0000:03:00.0: 101: [8015644.453557] 0:(0):0932 FIND node did xfffffe NOT FOUND.
[8015645.550075] lpfc 0000:03:00.0: 102: [8015644.530337] 0:(0):0932 FIND node did xfffffe NOT FOUND.
[8015645.550075] lpfc 0000:03:00.0: 103: [8015644.530340] 0:(0):0354 Mbox cmd issue - Enqueue Data: x31 (x0/x0) x0 x0 xc600 x2
[8015645.550076] lpfc 0000:03:00.0: 104: [8015644.530341] 0:(0):0355 Mailbox cmd x31 (x0/x0) issue Data: x0 xc700
[8015645.550077] lpfc 0000:03:00.0: 105: [8015645.442272] 0:2539 Dropped frame rctl:x80 type:x0
[8015645.550077] lpfc 0000:03:00.0: 106: [8015645.442980] 0:0392 Async Event: word0:x8010140, word1:x3204000, word2:xc93265, word3:xc0011000
[8015645.550078] lpfc 0000:03:00.0: 107: [8015645.442983] 0:2896 Async FC event - Speed:8000GBaud Topology:x1 LA Type:x1 Port Type:1 Port Number:0 Logical speed:8000Mbps Fault:x0 Link Status:x40
[8015645.550079] lpfc 0000:03:00.0: 108: [8015645.442984] 0:(0):0354 Mbox cmd issue - Enqueue Data: x95 (x0/x0) x0 x0 xc600 x2
[8015645.550080] lpfc 0000:03:00.0: 109: [8015645.442985] 0:(0):0355 Mailbox cmd x95 (x0/x0) issue Data: x0 xc700
[8015645.550080] lpfc 0000:03:00.0: 110: [8015645.443290] 0:(0):0307 Mailbox cmd x95 (x0/x0) Cmpl lpfc_mbx_cmpl_read_topology [lpfc] Data: x9500 xc93265 x2001 x1 x80 xffe73800 x0 x200a x200a x0 x76cf064 x0
[8015645.550081] lpfc 0000:03:00.0: 111: [8015645.443294] 0:6077 Setup FDMI mask: hba x2efff port xffff
[8015645.550082] lpfc 0000:03:00.0: 112: [8015645.443295] 0:(0):0354 Mbox cmd issue - Enqueue Data: x8d (x0/x0) x0 x0 xc600 x2
[8015645.550082] lpfc 0000:03:00.0: 113: [8015645.443295] 0:(0):0354 Mbox cmd issue - Enqueue Data: x7 (x0/x0) x0 x6 xc600 x2
[8015645.550083] lpfc 0000:03:00.0: 114: [8015645.443296] 0:(0):0355 Mailbox cmd x8d (x0/x0) issue Data: x6 xc700
[8015645.550084] lpfc 0000:03:00.0: 115: [8015645.443466] 0:(0):0355 Mailbox cmd x7 (x0/x0) issue Data: x6 xc700
[8015645.550085] lpfc 0000:03:00.0: 116: [8015645.443475] 0:(0):0307 Mailbox cmd x8d (x0/x0) Cmpl lpfc_mbx_cmpl_read_sparam [lpfc] Data: x8d00 x0 x0 x70 xffe73c00 x0 x1 x0 x0 x0 x0 x0
[8015645.550085] lpfc 0000:03:00.0: 117: [8015645.443621] 0:(0):0307 Mailbox cmd x7 (x0/x0) Cmpl lpfc_mbx_cmpl_local_config_link [lpfc] Data: x700 x0 x0 x0 x7d0 x76c xa x0 xf x0 x1800 x0
[8015645.550086] lpfc 0000:03:00.0: 118: [8015645.443622] 0:(0):0354 Mbox cmd issue - Enqueue Data: x8d (x0/x0) x0 x6 xc600 x2
[8015645.550087] lpfc 0000:03:00.0: 119: [8015645.443622] 0:(0):0355 Mailbox cmd x8d (x0/x0) issue Data: x6 xc700
[8015645.550088] lpfc 0000:03:00.0: 120: [8015645.443809] 0:(0):0307 Mailbox cmd x8d (x0/x0) Cmpl lpfc_mbx_cmpl_read_sparam [lpfc] Data: x8d00 x0 x0 x70 xffe73c00 x0 x1 x0 x0 x0 x0 x0
[8015645.550088] lpfc 0000:03:00.0: 121: [8015645.443809] 0:(0):0247 Start Discovery Timer state x7 Data: x21 xffff916fd74d6a90 x0 x0
[8015645.550089] lpfc 0000:03:00.0: 122: [8015645.443810] 0:(0):0932 FIND node did xfffffe NOT FOUND.
[8015645.550090] lpfc 0000:03:00.0: 123: [8015645.443810] 0:0001 Allocated rpi:x0 max:x1800 lim:x1800
[8015645.550090] lpfc 0000:03:00.0: 124: [8015645.443810] 0:(0):0007 Init New ndlp xffff917246242000, rpi:x0 DID:fffffe flg:x0 refcnt:1
[8015645.550091] lpfc 0000:03:00.0: 125: [8015645.443811] 0:(0):0116 Xmit ELS command x4 to remote NPORT xfffffe I/O tag: x8d3, port state:x7 rpi x0 fc_flag:x90014
[8015645.550092] lpfc 0000:03:00.0: 126: [8015645.443812] 0:(0):0247 Start Discovery Timer state x7 Data: x21 xffff916fd74d6a90 x0 x0
[8015645.550093] lpfc 0000:03:00.0: 127: [8015645.549093] 0:0392 Async Event: word0:x8010240, word1:x3200102, word2:xc93266, word3:xc0011000
[8015645.550093] lpfc 0000:03:00.0: 128: [8015645.549096] 0:2896 Async FC event - Speed:8000GBaud Topology:x1 LA Type:x2 Port Type:1 Port Number:0 Logical speed:0Mbps Fault:x2 Link Status:x1
[8015645.550094] lpfc 0000:03:00.0: 129: [8015645.549097] 0:(0):0339 Abort IO XRI x7e, Original iotag x8d3, abort tag x890 Cmdjob : xffff916fd83cac00 Abortjob : xffff916fd83c2600 retval x0
[8015645.550095] lpfc 0000:03:00.0: 130: [8015645.549102] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90000 x0 x0
[8015645.550096] lpfc 0000:03:00.0: 131: [8015645.549103] 0:(0):0211 DSM in event xc on NPort xfffffe in state 0 rpi x0 Data: x0 x4
[8015645.550096] lpfc 0000:03:00.0: 132: [8015645.549103] 0:(0):0212 DSM out state 0 on NPort xfffffe rpi x0 Data: x0 x4
[8015645.550097] lpfc 0000:03:00.0: 133: [8015645.549103] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90000 x0 x0
[8015645.550098] lpfc 0000:03:00.0: 134: [8015645.549103] 0:(0):6012 Update NVME lport xffff916fdbbbf600 did x0
[8015645.550098] lpfc 0000:03:00.0: 135: [8015645.549104] 0:(0):6030 bound lport xffff916fdbbbf670 to DID x000000
[8015645.550099] lpfc 0000:03:00.0: 136: [8015645.550061] 0:0357 ELS CQE error: status=x3: CQE: 08d30300 00000000 01420016 90010000
[8015645.550100] lpfc 0000:03:00.0: 137: [8015645.550065] 0:0321 Rsp Ring 2 error: IOCB Data: x8d30300 x0 x1420016 x90010000
[8015645.550101] lpfc 0000:03:00.0: 0:(0):2858 FLOGI failure Status:x3/x103 TMO:x14 Data x19140820 x0
[8015645.550103] lpfc 0000:03:00.0: start 138 end 141 cnt 3
[8015645.550104] lpfc 0000:03:00.0: 138: [8015645.550102] 0:(0):0408 Report link error true: <x3:x103>
[8015645.550105] lpfc 0000:03:00.0: 139: [8015645.550103] 0:(0):0108 No retry ELS command x4 to remote NPORT xfffffe Retried:1 Error:x3/103 IoTag x8d3 nflags x0
[8015645.550105] lpfc 0000:03:00.0: 140: [8015645.550103] 0:(0):0150 FLOGI failure Status:x3/x103 xri x7e TMO:x14 refcnt 1
[8015645.550106] lpfc 0000:03:00.0: 0:(0):0100 FLOGI failure Status:x3/x103 TMO:x14
[8015646.539585] lpfc 0000:03:00.0: 0:1303 Link Up Event xc93267 received Data: xc93267 x0 x20 x0 x0
[8015646.645633] lpfc 0000:03:00.0: 0:1305 Link Down Event xc93268 received Data: xc93268 x7 x90014 x0
 
it seems that's not the whole output of dmesg. best to redirect into a file and either attach it here :

Code: 
dmesg > /tmp/dmesg.txt
 
thanks for sending this. it seems there are so many errors from the lpfc driver (fibre channel) that the beginning is cut off
you could give me the relevant output with
Code: 
journalctl -b -t kernel

depending on how large it is, you might want/need to zip/tar.gz it

but it seems the fc connection is not stable, the given log basically has this in a loop:

Code: 
lpfc 0000:03:00.0: 0:1305 Link Down Event xc9cd3c received Data: xc9cd3c x7 x90014 x0
[..]
lpfc 0000:03:00.0: 0:(0):2858 FLOGI failure Status:x3/x103 TMO:x14 Data x19140820 x0
[..]
lpfc 0000:03:00.0: 0:1303 Link Up Event xc9cd3d received Data: xc9cd3d x0 x20 x0 x0

can you check if the connection is stable? maybe check logs on the other side?
 
dcsapak said:
thanks for sending this. it seems there are so many errors from the lpfc driver (fibre channel) that the beginning is cut off
you could give me the relevant output with
Code: 
journalctl -b -t kernel

depending on how large it is, you might want/need to zip/tar.gz it

but it seems the fc connection is not stable, the given log basically has this in a loop:

Code: 
lpfc 0000:03:00.0: 0:1305 Link Down Event xc9cd3c received Data: xc9cd3c x7 x90014 x0
[..]
lpfc 0000:03:00.0: 0:(0):2858 FLOGI failure Status:x3/x103 TMO:x14 Data x19140820 x0
[..]
lpfc 0000:03:00.0: 0:1303 Link Up Event xc9cd3d received Data: xc9cd3d x0 x20 x0 x0

can you check if the connection is stable? maybe check logs on the other side?
Click to expand...
Dominik, thanks for fast response! Attached kernel log. Cable and sfp module (FC) corrected. On other side unfortunately no information.
 

Attachments

on lto drive port1 blinking after i connect FC cable (There is data transfer between devices). On FC card in server same blinking activity diodes.

browser_oXZugT1IdF.png
 
Last edited:
the logs look unsuspicious except the lpfc errors, especially these lines:

Code: 
lpfc 0000:03:00.0: 0:3176 Port Name 0 Optics faulted/incorrectly installed/not installed - Reseat optics, if issue not resolved, replace.
...
lpfc 0000:03:00.1: 1:3176 Port Name 1 Unqualified optics - Replace with Avago optics for Warranty and Technical Support - Link is operational

maybe there is still a problem with the connection?

sorry but aside from general fc disconnects/reconnects i can't see anything wrong with the log
 
You must log in or register to reply here.
Top Bottom