On Sat, 2012-08-18 at 22:47 -0700, Ross Brattain wrote:
> On Fri, 17 Aug 2012 20:53:47 -0500
> Andrew Theurer <[email protected]> wrote:
>
> > On Fri, 2012-08-17 at 18:17 -0700, Nicholas A. Bellinger wrote:
> > > On Fri, 2012-08-17 at 14:02 -0500, Andrew Theurer wrote:
> > > > Hello,
> > > >
>
> <snip>
>
> > > > We are now trying to create a test-bed with FCoE, with only FCoE targets
> > > > and initiators (no FCF's). For the moment, I am trying a
> > > > directly-connected 82599EB adapters from two systems (one the target,
> > > > the other the initiator). These interfaces are configured for IP and
> > > > ping-able. I created vn2vn FC ports and I now have 1 fc_host per
> > > > system. I have created a target on one via targetcli with a single LUN:
> > > >
> > > >
> > > > > /> ls
> > > > > o- /
> > > > > .........................................................................................................
> > > > > [...]
> > > > > o- backstores
> > > > > ..............................................................................................
> > > > > [...]
> > > > > | o- block
> > > > > ....................................................................................
> > > > > [0 Storage Object]
> > > > > | o- fileio
> > > > > ...................................................................................
> > > > > [1 Storage Object]
> > > > > | | o- lun1
> > > > > .....................................................................
> > > > > [/tmp/lun1.img (1.0G) activated]
> > > > > | o- pscsi
> > > > > ....................................................................................
> > > > > [0 Storage Object]
> > > > > o- loopback
> > > > > ...........................................................................................
> > > > > [0 Target]
> > > > > o- tcm_fc
> > > > > .............................................................................................
> > > > > [1 Target]
> > > > > o- 20:00:00:1b:21:4b:0a:0e
> > > > > ...........................................................................
> > > > > [enabled]
> > > > > o- acls
> > > > > ..............................................................................................
> > > > > [1 ACL]
> > > > > | o- 20:00:00:1b:21:67:5f:2a
> > > > > .................................................................. [1
> > > > > Mapped LUN]
> > > > > | o- mapped_lun1
> > > > > ...................................................................
> > > > > [lun1 fileio/lun1 (rw)]
> > > > > o- luns
> > > > > ..............................................................................................
> > > > > [1 LUN]
> > > > > o- lun1
> > > > > ......................................................................
> > > > > [fileio/lun1 (/tmp/lun1.img)]
> > > >
> > > > The initiator has a port name of 0x2000001b21675f2a and both target and
> > > > initiator ports are "Online". However, after re-scanning for devices,
> > > > the initiator does not find any new LUNs.
> > > >
> > > > I tried to do a fcping, but I can only successfully ping a FC ID, and
> > > > not a port name:
> > > >
> > > > > [root@spv-21 ~]# fcping -c 3 -h eth6 -F 0x000a0e
> > > > > sending echo to 0xA0E
> > > > > echo 1 accepted 0.468 ms
> > > > > echo 2 accepted 0.428 ms
> > > > > echo 3 accepted 0.462 ms
> > > > > 3 frames sent, 3 received 0 errors, 0.000% loss, avg. rt time 0.453 ms
> > > >
> > > > > [root@spv-21 ~]# fcping -h eth6 -N 0x2000001b214b0a0e
> > > > > GID_NN error: Invalid argument
> > > > > cannot find fcid of destination @ wwnn 0x2000001B214B0A0E
>
>
> 0x2000001b214b0a0e is an Intel WWPN. Try fcping -P for WWPNs, or use
> -N with the WWNN which should be 0x1000001b214b0a0e.
>
> It looks like you have created the VN2VN fc_host on the real device
> eth6. Normally we would expect the fc_host to be on a VLAN, e.g.
> eth6.101-fcoe, so that DCB can use proper VIDs when tagging.
I have just created eth6.101 on both hosts and then created vn2vn
fc_hosts (host7). I get the same results with fcping:
> [root@spv-21 host7]# fcping -c 3 -h eth6.101 -F 0x000a0e
> sending echo to 0xA0E
> echo 1 accepted 0.339 ms
> echo 2 accepted 0.347 ms
> echo 3 accepted 0.374 ms
> 3 frames sent, 3 received 0 errors, 0.000% loss, avg. rt time 0.353 ms
> [root@spv-21 host7]# fcping -c 3 -h eth6.101 -P 0x2000001b214b0a0e
> GID_PN error: Invalid argument
> cannot find fcid of destination @ wwpn 0x2000001B214B0A0E
> [root@spv-21 host7]# fcping -c 3 -h eth6.101 -N 0x1000001b21675f2a
> GID_NN error: Invalid argument
> cannot find fcid of destination @ wwnn 0x1000001B21675F2A
tshark only showed activity on the fcping with -F
I did try an strace with the port name:
> [root@spv-21 host7]# strace fcping -c 3 -h eth6.101 -P 0x2000001b214b0a0e
> ..
> <snip>
> ..
> stat("/sys/class/net/eth6.101", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
> open("/dev/bsg/fc_host7", O_RDWR) = 3
> ioctl(3, SG_IO, {'Q', 0 /* SG_DXFER_??? */, cmd[2]=[0x1], mx_sb_len=0,
> iovec_count=0, dxfer_len=20, timeout=24973900, flags=0x10}) = -1 EINVAL
> (Invalid argument)
> fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7fcd6fd86000
> write(1, "GID_PN error: Invalid argument\n", 31GID_PN error: Invalid argument
> ) = 31
> write(2, "cannot find fcid of destination "..., 58cannot find fcid of
> destination @ wwpn 0x2000001B214B0A0E
> ) = 58
> close(3) = 0
> munmap(0x7fcd6fb6b000, 2136912) = 0
> munmap(0x3c30400000, 2128752) = 0
> exit_group(1) = ?
Is the invalid argument error on the ioctl an issue?
Thanks
-Andrew
_______________________________________________
devel mailing list
[email protected]
https://lists.open-fcoe.org/mailman/listinfo/devel
