On Sat, 2012-08-18 at 05:26 +0000, Patil, Kiran wrote: > Generally FCFs don't support VN2VN yet. Hence using FCF between > initiator and target for VN2VN won't work. > > If you using any DCB switches, it VN2VN across DCB switch should work, > though you have to make sure DCB is enabled on both side interface > (initiator and target side). Are you using DCB switch in between? I am not using any switch at all between the eth6 interfaces on both hosts. There is a single SFP+ copper cable between the interfaces. Here is the initiator information: > [root@spv-21 host8]# ifconfig eth6 > eth6 Link encap:Ethernet HWaddr 00:1B:21:67:5F:28 > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::21b:21ff:fe67:5f28/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:38254 errors:0 dropped:0 overruns:0 frame:0 > TX packets:38268 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:2752430 (2.6 MiB) TX bytes:2753287 (2.6 MiB) > > [root@spv-21 host8]# cd /sys/class/fc_host/host8; for i in `/bin/ls port* node*`; do echo $i: `cat $i`; done > node_name: 0x1000001b21675f2a > port_id: 0x005f2a > port_name: 0x2000001b21675f2a > port_state: Online > port_type: NPort (fabric via point-to-point) Here is the target information: > [root@spv-20 host8]# ifconfig eth6 > eth6 Link encap:Ethernet HWaddr 00:1B:21:4B:0A:0C > inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::21b:21ff:fe4b:a0c/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:38277 errors:0 dropped:0 overruns:0 frame:0 > TX packets:38271 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:2753718 (2.6 MiB) TX bytes:2753260 (2.6 MiB) > > [root@spv-20 host8]# cd /sys/class/fc_host/host8; for i in `/bin/ls port* node*`; do echo $i: `cat $i`; done > node_name: 0x1000001b214b0a0e > port_id: 0x000a0e > port_name: 0x2000001b214b0a0e > port_state: Online > port_type: NPort (fabric via point-to-point) The only configuration that was done was assigning IP addresses and "echo eth6 >create_vn2vn". > 20:00:00:1b:21:4b:0a:0e : I assume this is target side SAN MAC > address? Yes. > Which network card (Ethernet) you are using. Looks like you are using > Intel(R) 10GbE Fiber Card. Id it is single port NIC, SAN MAC address > is actual MAC address +1 and if it is dual port NIC, SAN MAC address > is actual MAC address +2. Mean last byte of actual MAC address +2. That appears to true here. > Make sure you verify SAN MAC addresses on both side (initiator and > target). You can also capture wireshark or xgig trace and loot at it. > Typically it first goes thru' FIP state machine, then FLOGI, PLOGI, > PRLI from both end. Then only VN2VN session is established. Since I have not created VLANs with these Ethernet devices, could that be the problem? I did try tshark, but only the fcping of the > [root@spv-21 host8]# fcping -c 3 -h eth6 -F 0x000a0e > sending echo to 0xA0E > echo 1 accepted 0.429 ms > echo 2 accepted 0.444 ms > echo 3 accepted 0.384 ms > 3 frames sent, 3 received 0 errors, 0.000% loss, avg. rt time 0.419 ms > [root@spv-21 host8]# fcping -c 3 -h eth6 -P 0x2000001b214b0a0e > GID_PN error: Invalid argument > cannot find fcid of destination @ wwpn 0x2000001B214B0A0E > [root@spv-21 host8]# fcping -c 3 -h eth6 -N 0x2000001b214b0a0e > GID_NN error: Invalid argument > cannot find fcid of destination @ wwnn 0x2000001B214B0A0E > [root@spv-21 ~]# tshark -i eth6 > Running as user "root" and group "root". This could be dangerous. > Capturing on eth6 > 0.000000 0e:fd:00:00:5f:2a -> Broadcom_01:00:04 FIP Unknown op 0x5 > 1.590728 0e:fd:00:00:0a:0e -> Broadcom_01:00:04 FIP Unknown op 0x5 > 8.032008 0e:fd:00:00:5f:2a -> Broadcom_01:00:04 FIP Unknown op 0x5 > 9.686718 0e:fd:00:00:0a:0e -> Broadcom_01:00:04 FIP Unknown op 0x5 > 11.089857 00.5f.2a -> 00.0a.0e FC ELS ECHO > 11.090118 00.0a.0e -> 00.5f.2a FC ELS ACC (ECHO) > 12.090374 00.5f.2a -> 00.0a.0e FC ELS ECHO > 12.090643 00.0a.0e -> 00.5f.2a FC ELS ACC (ECHO) > 13.090861 00.5f.2a -> 00.0a.0e FC ELS ECHO > 13.091092 00.0a.0e -> 00.5f.2a FC ELS ACC (ECHO) > 16.064020 0e:fd:00:00:5f:2a -> Broadcom_01:00:04 FIP Unknown op 0x5 > 17.718712 0e:fd:00:00:0a:0e -> Broadcom_01:00:04 FIP Unknown op 0x5 > 24.128018 0e:fd:00:00:5f:2a -> Broadcom_01:00:04 FIP Unknown op 0x5 > 25.750698 0e:fd:00:00:0a:0e -> Broadcom_01:00:04 FIP Unknown op 0x5 > 32.192003 0e:fd:00:00:5f:2a -> Broadcom_01:00:04 FIP Unknown op 0x5 > 33.846728 0e:fd:00:00:0a:0e -> Broadcom_01:00:04 FIP Unknown op 0x5 > 40.224026 0e:fd:00:00:5f:2a -> Broadcom_01:00:04 FIP Unknown op 0x5 I am curious what the FIP Unknown ops are... > > Thanks, > -- Kiran P. Thanks! -Andrew -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
