FCoE capable Storage Array connected directly to Nexus 5000 FCoE port

hi,
can someone help me verify if it is possible to connect an FCoE capable SAN storage to a Nexus 5000 FCoE port? thanks!

yes, i have connected both EMC VNX and NetApp to N5Ks FCoE. EMC requires active mode twinax or fiber.

Similar Messages

What are best practices for connecting asa to nexus 5000

just trying to get a feel for the best way to connect redundant asa to redundant nexus 5000
using a vpc vlan is fine, but then running a routing protocol isn't supported, so putting static routes on 5000 works, but it doesn't support ip sla yet so you cant really stop distributing the default if your internet goes down. just looking for what was recommended.

you want to test RAC upgrade on NON RAC database. If you ask me that is a risk but it depends on may things
Application configuration - If your application is configured for RAC, FAN etc. you cannot test it on non RAC systems
Cluster upgrade - If your standalone database is RAC one node you can probably test your cluster upgrade there. If you have non RAC database then you will not be able to test cluster upgrade or CRS
Database upgrade - There are differences when you upgrade RAC vs non RAC database which you will not be able to test
I think the best way for you is to convert your standalone database to RAC one node database and test it. that will take you close to multi node RAC

Nexus 4000 fcoe & ethernet connectivity

Hi!
I have a question about the Nexus 4000. We currently have a Nexus 4000 connected to a Nexus 5000 connect to a 6500 Switch.
We have VLAN 115 for Ethernet & Vlan 1115 for Fcoe.
The FCOE part of the configuration is working, it is doing a fabric login to the 5K by FIP Snooping.
We are having trouble with the Ethernet component, we can't seem to get a response. The vlans are allowed end to end but all mac addresses on the port are visible in VLAN 1115.
How do we get the Ethernet part of the CNA working? The Nexus 4000 does not seem to learn the Ethernet MAC from the CNA.
Thanks
Brad

Hi,
Port on the 4k -
interface Ethernet1/5
switchport mode trunk
switchport trunk allowed vlan 1,115,1115
spanning-tree port type edge
speed auto
CNA used -Qlogic....the 4 k is part of the IBM Blade Chassis
OS on 4K - n4000-bk9.4.1.2.E1.1b.bin
We also modifed the native vlan to VLAN 115 which the MAC appeared in VLAN 115 but still no connectivity. From the looks of things, the ethernet part takes the native vlan, now is this probably because the server is sending an untagged packet, as it may not be setup to do dot1q trunking.

PFC configuration on Nexus 5000

Hi,
I have a CNA in my server connected to cisco nexus 5000 interfcae. I Want to genearate pause frames for FCOE class of traffic using the default class class-fcoe and cos value 3, the firmware version running is 5.0(3) N1 (1b). Can anyone tell me how can i configure it ?
Thanks,
Manju

Sorry for the delayed response, Here is what you asked
Cisco-5020# sh mod
Mod Ports Module-Type                      Model                  Status
1    40     40x10GE/Supervisor               N5K-C5020P-BF-SUP      active *
2    8      4x10GE + 4x1/2/4G FC Module      N5K-M1404              ok
Mod Sw              Hw      World-Wide-Name(s) (WWN)
1    5.0(3)N1(1b)    1.2     --
2    5.0(3)N1(1b)    1.0     20:41:00:0d:ec:b2:15:40 to 20:44:00:0d:ec:b2:15:40
Mod MAC-Address(es)                         Serial-Num
1    000d.ecb2.1548 to 000d.ecb2.156f         JAF1303ACES
2    000d.ecb2.1570 to 000d.ecb2.1577         JAF1245AJLF
Cisco-5020#
Cisco-5020#
Cisco-5020# sh run
!Command: show running-config
!Time: Fri Oct 28 17:40:02 2005
version 5.0(3)N1(1b)
feature fcoe
feature npiv
feature telnet
feature lldp
username admin password 5 $1$v9Tm8Y77$ZSdbOfBxe1.Z9Oz1V9V2B0 role network-admin
no password strength-check
ip domain-lookup
hostname Cisco-5020
logging event link-status default
service unsupported-transceiver
class-map type qos class-fcoe
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
policy-map type network-qos jumbo
class type network-qos class-fcoe
    pause no-drop
    mtu 2158
class type network-qos class-default
    mtu 9216
system qos
service-policy type network-qos jumbo
snmp-server user admin network-admin auth md5 0x2694501fdfbe5abed9e85d51e4e31038 priv 0x2694501fdfbe5abed9e85d51e4e31038 localizedkey
snmp-server host 138.239.198.184 traps version 2c public udp-port 1163
snmp-server host 138.239.198.184 traps version 2c public udp-port 1164
snmp-server host 138.239.198.200 traps version 2c public udp-port 1163
snmp-server host 138.239.198.200 traps version 2c public udp-port 1164
snmp-server host 138.239.200.118 traps version 2c public udp-port 1163
snmp-server host 138.239.198.200 traps version 2c public udp-port 1163
snmp-server enable traps entity fru
snmp-server community snmpv3 group network-operator
vrf context management
ip route 0.0.0.0/0 10.192.207.254
vlan 1-2,8
vlan 10
fcoe vsan 10
vlan 20
fcoe vsan 20
vlan 30
vlan 35
fcoe vsan 35
vlan 40,50
vlan 52
fcoe vsan 52
vsan database
vsan 20
vsan 52
fcdomain fcid database
vsan 52 wwn 10:00:00:00:c9:b1:e5:3d fcid 0x180000 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:3b fcid 0x180001 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:4d:e3 fcid 0x180002 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:ad fcid 0x180003 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:41 fcid 0x180004 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:b9 fcid 0x180005 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:b5 fcid 0x180006 dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:d1 fcid 0x180007 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:4d:e1 fcid 0x180008 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:a9 fcid 0x180009 dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:d5 fcid 0x18000a dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:5d fcid 0x18000b dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:9b fcid 0x18000c dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:99 fcid 0x18000d dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:5b fcid 0x18000e dynamic
vsan 1 wwn 10:00:00:00:c9:f2:73:b3 fcid 0x050000 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:47 fcid 0x18000f dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a7:93 fcid 0x180010 dynamic
vsan 52 wwn 10:00:00:00:c9:91:f8:19 fcid 0x180011 dynamic
vsan 52 wwn 10:00:00:00:c9:9c:e0:77 fcid 0x180012 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a7:d3 fcid 0x180013 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a3:bb fcid 0x180014 dynamic
vsan 52 wwn 10:00:00:00:c9:97:3b:c5 fcid 0x180015 dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:91 fcid 0x180016 dynamic
vsan 52 wwn 10:00:00:00:c9:a4:00:91 fcid 0x180017 dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:8d fcid 0x180018 dynamic
vsan 52 wwn 20:0f:00:11:0d:7f:a8:00 fcid 0x180019 dynamic
vsan 52 wwn 20:0f:00:11:0d:7f:a8:01 fcid 0x18001a dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a3:b7 fcid 0x18001b dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a5:27 fcid 0x18001c dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a3:53 fcid 0x18001d dynamic
vsan 52 wwn 10:00:00:00:c9:bb:c8:37 fcid 0x18001e dynamic
vsan 52 wwn 10:00:00:00:c9:5b:76:e5 fcid 0x18001f dynamic
vsan 20 wwn 10:00:00:00:c9:5b:a3:83 fcid 0xd30000 dynamic
vsan 52 wwn 10:00:00:00:c9:91:00:00 fcid 0x180020 dynamic
vsan 52 wwn 10:00:00:00:00:91:f7:f1 fcid 0x180021 dynamic
vsan 1 wwn 10:00:00:00:c9:5b:4d:e3 fcid 0x050001 dynamic
vsan 52 wwn 10:00:00:00:c9:97:3b:0f fcid 0x180022 dynamic
vsan 52 wwn 10:00:00:00:c9:3c:8e:21 fcid 0x180023 dynamic
vsan 52 wwn 10:00:00:00:c9:97:3b:11 fcid 0x180024 dynamic
vsan 20 wwn 10:00:00:00:c9:b1:e6:b7 fcid 0xd30001 dynamic
vsan 52 wwn 10:00:f8:19:00:91:f8:19 fcid 0x180025 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a3:8b fcid 0x180026 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e4:ff fcid 0x180027 dynamic
vsan 52 wwn 10:00:00:00:c9:3c:8e:25 fcid 0x180028 dynamic
vsan 52 wwn 50:06:01:61:44:60:23:4f fcid 0x1800ef dynamic
vsan 52 wwn 10:00:00:00:c9:5b:d6:b9 fcid 0x180029 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:43 fcid 0x18002a dynamic
vsan 52 wwn 20:01:00:00:c9:5b:ab:99 fcid 0x18002b dynamic
vsan 52 wwn 20:02:00:00:c9:5b:ab:99 fcid 0x18002c dynamic
vsan 52 wwn 50:06:01:60:44:60:23:4f fcid 0x1801ef dynamic
vsan 52 wwn 10:00:00:00:c9:9d:1f:bf fcid 0x18002d dynamic
vsan 52 wwn 10:00:00:00:c9:9d:1f:c1 fcid 0x18002e dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:d3 fcid 0x18002f dynamic
vsan 20 wwn 10:00:00:00:c9:bb:c8:37 fcid 0xd30002 dynamic
vsan 52 wwn 10:00:00:00:c9:12:34:56 fcid 0x180030 dynamic
vsan 52 wwn 10:00:00:00:c9:12:34:57 fcid 0x180031 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:ea:81 fcid 0x180032 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:ea:7f fcid 0x180033 dynamic
vsan 20 wwn 10:00:00:00:c9:12:34:56 fcid 0xd30003 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:1b fcid 0x180034 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:1d fcid 0x180035 dynamic
vsan 52 wwn 10:00:00:00:c9:bb:c7:8f fcid 0x180036 dynamic
vsan 52 wwn 10:00:00:00:c9:bb:cb:8f fcid 0x180037 dynamic
vsan 52 wwn 10:00:00:00:c9:bb:cb:93 fcid 0x180038 dynamic
vsan 52 wwn 10:00:00:00:c9:bb:c7:93 fcid 0x180039 dynamic
vsan 20 wwn 10:00:00:00:c9:12:34:57 fcid 0xd30004 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:c4 fcid 0x18003a dynamic
vsan 52 wwn 10:00:00:00:c9:bb:17:b7 fcid 0x18003b dynamic
vsan 52 wwn 10:00:00:00:c9:a0:ce:2d fcid 0x18003c dynamic
vsan 52 wwn 10:00:00:00:c9:91:f7:f1 fcid 0x18003d dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:c0 fcid 0x18003e dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:5f fcid 0x18003f dynamic
vsan 52 wwn 10:00:00:00:c9:e3:06:89 fcid 0x180040 dynamic
vsan 52 wwn 50:06:01:68:44:60:23:4f fcid 0x1802ef dynamic
vsan 1 wwn 50:06:01:61:44:60:23:4f fcid 0x0500ef dynamic
vsan 52 wwn 10:00:00:00:c9:d1:16:24 fcid 0x180041 dynamic
vsan 52 wwn 10:00:00:00:c9:d1:16:25 fcid 0x180042 dynamic
vsan 52 wwn 10:00:00:00:c9:d1:0a:6d fcid 0x180043 dynamic
vsan 20 wwn 10:00:00:00:c9:d1:16:25 fcid 0xd30005 dynamic
vsan 20 wwn 10:00:00:00:c9:d1:16:24 fcid 0xd30006 dynamic
vsan 20 wwn ff:f2:00:00:c9:12:34:78 fcid 0xd30007 dynamic
vsan 20 wwn ff:f2:00:00:c9:d1:16:46 fcid 0xd30008 dynamic
vsan 52 wwn ff:f2:00:00:c9:d1:0a:8c fcid 0x180044 dynamic
vsan 20 wwn ff:f3:00:00:c9:d1:16:46 fcid 0xd30009 dynamic
vsan 52 wwn ff:f0:00:00:c9:d1:0a:8c fcid 0x180045 dynamic
vsan 52 wwn 10:00:00:00:c9:d1:0a:6c fcid 0x180046 dynamic
vsan 20 wwn ff:f2:00:00:c9:d1:0a:8c fcid 0xd3000a dynamic
vsan 20 wwn 10:00:00:00:c9:d1:0a:6d fcid 0xd3000b dynamic
vsan 52 wwn ff:f2:00:00:c9:d1:16:46 fcid 0x180047 dynamic
vsan 20 wwn ff:f3:00:00:c9:12:34:78 fcid 0xd3000c dynamic
vsan 52 wwn ff:f3:00:00:c9:12:34:78 fcid 0x180048 dynamic
vsan 52 wwn 50:06:01:69:44:60:23:4f fcid 0x1803ef dynamic
vsan 52 wwn ff:f3:00:00:c9:d1:16:46 fcid 0x180049 dynamic
vsan 52 wwn 10:00:00:00:c9:12:34:5b fcid 0x18004a dynamic
vsan 52 wwn 10:00:00:00:c9:12:34:5a fcid 0x18004b dynamic
vsan 52 wwn ff:f2:00:00:c9:12:34:78 fcid 0x18004c dynamic
vsan 52 wwn 10:00:00:00:c9:a5:ac:f3 fcid 0x18004d dynamic
vsan 52 wwn 10:00:00:00:c9:a5:ad:15 fcid 0x18004e dynamic
vsan 52 wwn 10:00:00:00:c9:a5:ac:f5 fcid 0x18004f dynamic
vsan 52 wwn 20:01:00:00:c9:a5:ac:f3 fcid 0x180050 dynamic
vsan 52 wwn 20:02:00:00:c9:a5:ac:f3 fcid 0x180051 dynamic
vsan 52 wwn ff:f3:00:00:c9:12:34:85 fcid 0x180052 dynamic
vsan 52 wwn 20:00:00:11:0d:77:9c:00 fcid 0x180053 dynamic
vsan 52 wwn 20:01:00:11:0d:77:9d:00 fcid 0x180054 dynamic
interface port-channel3
interface vfc1
no shutdown
interface vfc4
interface vfc9
bind interface Ethernet1/9
no shutdown
interface vfc10
interface vfc11
bind interface Ethernet1/11
no shutdown
interface vfc19
bind interface Ethernet1/19
no shutdown
interface vfc21
bind interface Ethernet1/21
no shutdown
interface vfc22
bind interface Ethernet1/22
switchport trunk allowed vsan 52
no shutdown
interface vfc24
bind interface Ethernet1/24
switchport trunk allowed vsan 52
no shutdown
interface vfc25
bind interface Ethernet1/25
switchport trunk allowed vsan 52
no shutdown
interface vfc26
bind interface Ethernet1/26
switchport trunk allowed vsan 52
no shutdown
interface vfc27
bind interface Ethernet1/27
no shutdown
interface vfc28
bind interface Ethernet1/28
no shutdown
interface vfc29
bind interface Ethernet1/29
no shutdown
interface vfc30
bind interface Ethernet1/30
switchport trunk allowed vsan 52
no shutdown
interface vfc31
bind interface Ethernet1/31
shutdown
interface vfc32
bind interface Ethernet1/32
no shutdown
interface vfc33
bind interface Ethernet1/33
no shutdown
interface vfc34
bind interface Ethernet1/34
no shutdown
interface vfc35
bind interface Ethernet1/35
no shutdown
interface vfc36
bind interface Ethernet1/36
no shutdown
interface vfc37
bind interface Ethernet1/37
no shutdown
interface vfc38
bind interface Ethernet1/38
no shutdown
interface vfc39
bind interface Ethernet1/39
no shutdown
interface vfc40
bind interface Ethernet1/40
no shutdown
vsan database
vsan 52 interface vfc1
vsan 52 interface vfc9
vsan 52 interface vfc11
vsan 52 interface vfc19
vsan 52 interface vfc21
vsan 52 interface vfc22
vsan 52 interface vfc24
vsan 52 interface vfc26
vsan 52 interface vfc27
vsan 52 interface vfc28
vsan 52 interface vfc29
vsan 52 interface vfc30
vsan 52 interface vfc31
vsan 52 interface vfc32
vsan 52 interface vfc33
vsan 52 interface vfc34
vsan 20 interface vfc35
vsan 52 interface vfc36
vsan 52 interface vfc37
vsan 52 interface vfc38
vsan 52 interface vfc39
vsan 52 interface vfc40
vsan 52 interface fc2/1
vsan 52 interface fc2/2
vsan 52 interface fc2/3
vsan 52 interface fc2/4
interface fc2/1
switchport trunk allowed vsan 1
switchport trunk allowed vsan add 52
switchport trunk mode auto
no shutdown
interface fc2/2
switchport trunk mode auto
no shutdown
interface fc2/3
no shutdown
interface fc2/4
no shutdown
interface Ethernet1/1
interface Ethernet1/2
speed 1000
interface Ethernet1/3
interface Ethernet1/4
interface Ethernet1/5
interface Ethernet1/6
interface Ethernet1/7
switchport mode trunk
interface Ethernet1/8
interface Ethernet1/9
switchport mode trunk
switchport trunk allowed vlan 1,10,20,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/10
interface Ethernet1/11
priority-flow-control mode on
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/12
switchport mode trunk
interface Ethernet1/13
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/14
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/15
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/16
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/17
interface Ethernet1/18
switchport mode trunk
switchport trunk allowed vlan 1,30
interface Ethernet1/19
switchport mode trunk
switchport access vlan 10
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/20
switchport mode trunk
switchport access vlan 52
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/21
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/22
interface Ethernet1/23
flowcontrol receive on
flowcontrol send on
interface Ethernet1/24
switchport mode trunk
switchport access vlan 52
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/25
switchport mode trunk
switchport trunk allowed vlan 1,8,30,52
interface Ethernet1/26
switchport mode trunk
switchport access vlan 52
switchport trunk allowed vlan 1,8,30,52
interface Ethernet1/27
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/28
switchport mode trunk
switchport trunk allowed vlan 1,8,30,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/29
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/30
description line
switchport mode trunk
switchport access vlan 52
switchport trunk allowed vlan 1,8,30,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/31
switchport mode trunk
switchport trunk allowed vlan 1,10,20,52
interface Ethernet1/32
switchport mode trunk
switchport trunk allowed vlan 1,10,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/33
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/34
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/35
switchport mode trunk
switchport access vlan 10
switchport trunk allowed vlan 1,10,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/36
switchport mode trunk
switchport trunk allowed vlan 1,30,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/37
switchport mode trunk
switchport trunk allowed vlan 1,30,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/38
switchport mode trunk
switchport trunk allowed vlan 1,10,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/39
shutdown
switchport mode trunk
switchport trunk allowed vlan 1,10,20,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/40
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet2/1
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet2/2
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet2/3
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet2/4
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface mgmt0
ip address 10.192.194.111/20
system default zone default-zone permit
system default zone distribute full
line console
line vty
boot kickstart bootflash:/n5000-uk9-kickstart.5.0.3.N1.1b.bin
boot system bootflash:/n5000-uk9.5.0.3.N1.1b.bin
interface fc2/1
interface fc2/2
interface fc2/3
interface fc2/4
zone default-zone permit vsan 20
zone default-zone permit vsan 52
zoneset distribute full vsan 1
zoneset distribute full vsan 20
zoneset distribute full vsan 52
!Full Zone Database Section for vsan 1
zone name bg-qa vsan 1
    member pwwn 10:00:00:00:c9:5b:ab:ca
    member pwwn 21:00:00:0c:50:c3:70:23
    member pwwn 21:00:00:0c:50:c3:70:22
    member pwwn 21:00:00:0c:50:c3:70:16
    member pwwn 21:00:00:0c:50:c3:70:1e
    member pwwn 22:00:00:0c:50:c3:70:26
    member pwwn 22:00:00:18:62:06:76:8a
    member pwwn 22:00:00:11:c6:17:68:c3
    member pwwn 22:00:00:0c:50:c3:70:1d
    member pwwn 22:00:00:0c:50:c3:6f:c2
    member pwwn 22:00:00:11:c6:17:68:dc
    member pwwn 21:00:00:0c:50:c3:6a:d0
    member pwwn 21:00:00:0c:50:79:92:90
    member pwwn 21:00:00:11:c6:17:69:a0
    member pwwn 21:00:00:0c:50:79:93:af
    member pwwn 22:00:00:0c:50:48:10:80
    member pwwn 22:00:00:11:c6:18:46:c6
    member pwwn 22:00:00:0c:50:32:2e:0f
    member pwwn 22:00:00:0c:50:48:10:74
    member pwwn 22:00:00:11:c6:18:46:f2
    member pwwn 21:00:00:00:87:13:cb:d1
    member pwwn 21:00:00:0c:50:79:91:0f
    member pwwn 10:00:00:00:c9:3c:8e:49
    member pwwn 10:00:00:00:c9:5b:ab:c2
    member pwwn 10:00:00:00:c9:5b:af:f3
zone name sf_RAM vsan 1
    member pwwn 10:00:00:00:c9:5b:af:c9
    member pwwn 21:00:00:0c:50:b4:8e:20
zone name anand vsan 1
    member pwwn 10:00:00:00:c9:65:69:31
    member pwwn 22:00:00:18:62:06:7f:f6
zone name syedzone vsan 1
    member fwwn 20:11:00:0d:ec:56:7b:40
    member pwwn 50:06:01:60:44:60:23:4f
zone name bg_qa vsan 1
zoneset name TOM vsan 1
    member bg-qa
zoneset name bg_dvt vsan 1
    member sf_RAM
zoneset name lancer vsan 1
    member anand
zoneset name bg-qa vsan 1
zoneset name syed vsan 1
    member syedzone
zoneset activate name lancer vsan 1
!Full Zone Database Section for vsan 20
zone name amrita_zone1 vsan 20
    member pwwn 10:00:00:00:c9:5b:a3:83
    member pwwn 22:00:00:04:cf:89:19:67
    member pwwn 22:00:00:0c:50:48:10:80
    member pwwn 22:00:00:11:c6:18:46:f2
    member pwwn 22:00:00:0c:50:79:93:ae
zone name amr_zset vsan 20
zoneset name amr_zset vsan 20
    member amrita_zone1
zoneset activate name amr_zset vsan 20
!Full Zone Database Section for vsan 52
zone name vinod vsan 52
    member pwwn 50:06:01:69:44:60:23:4f
    member pwwn ff:f3:00:00:c9:12:34:78
    member pwwn 10:00:00:00:c9:12:34:5b
    member pwwn 10:00:00:00:c9:12:34:57
zone name neha vsan 52
zone name siv1 vsan 52
    member pwwn 10:00:00:00:c9:ad:ac:43
    member pwwn 50:06:01:61:44:60:23:4f
    member pwwn 10:00:00:00:c9:ad:ac:47
zone name neha1 vsan 52
    member pwwn 10:00:00:00:c9:5b:ab:ad
    member pwwn 50:06:01:60:44:60:23:4f
zone name neha2 vsan 52
    member pwwn 50:06:01:60:44:60:23:4f
    member pwwn 10:00:00:00:c9:5b:ab:a9
zone name neha3 vsan 52
    member pwwn 10:00:00:00:c9:9d:1f:bf
    member pwwn 50:06:01:60:44:60:23:4f
zone name neha4 vsan 52
    member pwwn 50:06:01:60:44:60:23:4f
    member pwwn 10:00:00:00:c9:9d:1f:c1
zone name chetan vsan 52
    member pwwn 10:00:00:00:c9:f2:73:d3
    member pwwn 50:06:01:60:44:60:23:4f
    member pwwn 10:00:00:00:c9:ad:ac:47
zone name siv2 vsan 52
    member pwwn 10:00:00:00:c9:d1:0a:6d
    member pwwn ff:f2:00:00:c9:d1:0a:8c
    member pwwn 22:00:00:0c:50:79:93:af
    member pwwn 22:00:00:0c:50:79:92:90
    member pwwn 22:00:00:0c:50:79:91:0f
    member pwwn 20:01:00:11:0d:77:9d:00
zone name sroy vsan 52
    member pwwn 10:00:00:00:c9:b1:ea:7f
    member pwwn 50:06:01:60:44:60:23:4f
    member pwwn 10:00:00:00:c9:5b:ab:99
    member pwwn 10:00:00:00:c9:bb:cb:8f
    member pwwn 10:00:00:00:c9:5b:ab:c4
    member pwwn 10:00:00:00:c9:d1:16:25
    member pwwn 50:06:01:61:44:60:23:4f
    member pwwn 10:00:00:00:c9:a5:ac:f3
zone name manju vsan 52
    member pwwn 10:00:00:00:c9:bb:c7:8f
    member pwwn 50:06:01:61:44:60:23:4f
zone name ram vsan 52
    member pwwn 50:06:01:60:44:60:23:4f
    member pwwn 10:00:00:00:c9:a0:ce:2d
    member pwwn 10:00:00:00:c9:bb:17:b7
    member pwwn 10:00:00:00:c9:5b:a5:27
    member pwwn 10:00:00:00:c9:91:f7:f1
    member pwwn 10:00:00:00:c9:b1:e5:5f
zone name jana vsan 52
    member pwwn 10:00:00:00:c9:91:f7:f1
    member pwwn 50:06:01:60:44:60:23:4f
zone name priya vsan 52
    member pwwn 10:00:00:00:c9:e3:06:89
    member pwwn 50:06:01:60:44:60:23:4f
zoneset name IBMraptor vsan 52
    member vinod
    member siv1
    member neha1
    member neha2
    member neha3
    member neha4
    member chetan
    member siv2
    member sroy
    member manju
    member ram
    member priya
zoneset name ananda vsan 52
zoneset name vinod vsan 52
zoneset activate name IBMraptor vsan 52
no system default switchport shutdown san
Cisco-5020# sh system internal dcbx info interface ethernet 1/38
Interface info for if_index: 0x1a025000(Eth1/38)
tx_enabled: TRUE
rx_enabled: TRUE
dcbx_enabled: TRUE
DCX Protocol: CIN
Port MAC address: 00:0d:ec:b2:15:6d
DCX Control FSM Variables: seq_no: 0x1, ack_no: 0x0,my_ack_no: 0x0, peer_seq_no:
0x0 oper_version: 0x0, max_version: 0x0 fast_retries 0x0
Lock Status: UNLOCKED
PORT STATE: UP
LLDP Neighbors
No DCX tlvs from the remote peer
6 Features on this intf for Protocol CIN(0)
3 Features on this intf for Protocol CEE(1)
6 Features on this intf for Protocol CIN(0)
Feature type LLS (6)sub_type FCoE Logical Link Status (0)
feature type 6(LLS)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
     feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 0
     remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
     disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x1d9
Desired config cfg length: 1 data bytes:00
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type PFC (3)
feature type 3(PFC)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
     feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
     remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
     disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
Desired config cfg length: 1 data bytes:08
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type App(Fcoe) (5)sub_type FCoE (0)
feature type 5(App(Fcoe))sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
     feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
     remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
     disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
Desired config cfg length: 1 data bytes:08
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type PriMtu (8)
feature type 8(PriMtu)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
     feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
     remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
     disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
Desired config cfg length: 16 data bytes:24    00    24    00    24    00    08    6e    24    00    24    00    24    00    24    00
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type PriGrp (2)
feature type 2(PriGrp)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
     feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
     remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
     disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
Desired config cfg length: 24 data bytes:32    32    00    00    00    00    00    00    00    0f    00    0f    00    0e    20    64    00    0e    00    0e
   00    0e    00    0e
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type LLS (6)sub_type LAN Logical Link Status (1)
feature type 6(LLS)sub_type 1
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
     feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
     remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
     disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0xaf
Desired config cfg length: 1 data bytes:80
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Traffic Counters
DCBX pkt stats:
    Total frames out: 20296
    Total Entries aged: 27
    Total frames in: 0
    DCBX frames in: 0
    Total frames received in error: 0
    Total frames discarded: 0
    Total TLVs unrecognized: 0
Cisco-5020#
Cisco-5020#
Cisco-5020#
I am new to this PFC, and first time trying to configure so you can see nothing being configured.

Fiber Channel Storage Directly Connected to Nexus 5000

Can you connect Fiber Channel SAN storage directly to a Nexus 5000.
I swear I remember that you could not (at least when it first came out) and you had to connect it to a FC SAN switch. The docs look like it can act as a full fledge SAN switch, but it does say "Each Fibre Channel port can be used as a downlink (connected to a server) or as an uplink (to the data center SAN fabric)."
So It sounds like a server can connect to it directly via Fiber Channel, but you still need to connect it to a switch (i.e. data center SAN fabric).
Thanks for any help in clearing up this confusion.
Joe

You can connect any storage array and get it to work from a protocol perspective. But most storage OSMs have a certification process and you might want to check to see if the storage array you have is tested and certified for direct connect target.

What are some of the advantages/disadvantage of using FC or FCoE with a storage array (EMC)? What is Cisco's recommendation and why?

What are some of the advantages/disadvantages of using FC or FCoE for a storage array? What does Cisco recommend?

This is what I'm considering:
Power:
1050W Seasonic 80PLUS Gold Power Supply
Motherboard:
ASUS, Rampage IV Extreme, 2011, SATA6, True Quad SLI/XFIRE, Extreme OC Capable
CPU:
Intel Core i7-4960X 3.60GHz, 2133MHz DDR3, 15MB Cache, Hex Core Processor
System Memory:
16GB (4 x 4GB) , PC3-19200, 2400MHz (G.Skill - x79)
Video Adapter 1:
NVIDIA GeForce GTX 780ti 3GB GDDR5
Video Adapter 2:
None
Optical 1
16X Blu-ray Burner - 16xBD-R, 2xBD-RW/16xDVD-R, 8xDVD-RW/48xCD-R, 24xCD-RW
Bay Accessories 1
NZXT Aperture M Multi-media Hub
RAID [Requires Identical Hard Drive Selections]
RAID 0 | 2 Disk Min. Striped set, improved performance, additional storage drive highly recommended
Hard Drive 1
Crucial M550 1TB 2.5" SATA III 6GB/sec Solid State Drive
Hard Drive 2
Crucial M550 1TB 2.5" SATA III 6GB/sec Solid State Drive
Hard Drive 3
Crucial M550 1TB 2.5" SATA III 6GB/sec Solid State Drive
Sound Card
Creative Labs Sound Blaster Z PCI Express

Is it possible to record data directly from PXI-5112 scope card through PXI bus to SCSI RAID array (connected to PXI-8210)?

Colleagues,
Is it possible to record data directly from PXI-5112 scope card through PXI bus to SCSI RAID array (connected to PXI-8210)?
Which will be the maximum transfer rate for continuous data recording?
Thank you,
Sergey
Sergey

Sergey,
The PXI-8210 can connect to any SCSI 2 compliant device. If the RAID controller is SCSI 2 and appears just like a hard drive in the operating system, then you can send data directly to the RAID array. The problem is that the driver for the PXI-5112 does not yet support continuous acquisition. The on-board 16MB or 32MB buffer stores the data until the entire acquisition is completed. Once the acquisition complete, all of the data is transferred from the on-board buffer to the hard drive. After that happens, the NI 5112 is ready for another acquisition.
Best Regards,
Jace Curtis
NI Applications Engineering

ISCSI Initator still connects to NAS after deleting OVM Storage Array

I've got a 3.0.2 test rig with a couple of VM servers, a VM Manager and an Iomega NAS
I have a working solution using NFS storage, so the next step was to get a working solution with iSCSI
I started by enabling iSCSI and creating LUNs on an Iomega NAS
I then created an iSCSI Storage Array in OVM which pointed at the NAS
I registered a couple of iSCSI Initators in the OVM configuration.
I then created a server pool etc and everything looks good
Time to cleanup
I deleted ISCSI based repository contents and then the serverpool.
I deleted the LUNS from the OVM Storage Array definition
I tried to remove the iSCSI Initators but it said it couldn't do that with an iSCSI generic initator
I deleted the OVM Storage array
I then went to the Iomega NAS to delete the LUNs and it says that there are still VM Server iSCSI Initators connected.
I suspect I will be able to get rid of the iSCSI initiators connecting to the NAS by shutting down my two VM Servers and then rebooting the NAS. Since the VM servers aren't running there will be no connections coming from them so I will be able to delete the LUNS and turn off iSCSI.
Should the delete of the OVM storage Array definition have deleted the iSCSI Initators or did I miss a step somewhere ?
At this point, is there an easier to way to cleanup without rebooting everything ?

After hooking up a couple of OVM3.0.2 servers setup to an HP P4000 VSA - I noticed that when deleting iSCSI LUNs first from VM Manager, and then from the VSA - after rebooting the hosts - the OVM servers would try to connect to the LUNs even though they had been deleted.
If the LUN was deleted from VM Manager, but not the SAN - the LUN would just re-appear.
If the LUN was deleted from VM Manager, along with the iSCSI Disk Array registration - the LUN would end up in 'unmanaged iSCSI array'.
For some reason I can't seem to un-assign a server initiator from the arrays 'default access group'. I guess perhaps this is the problem.
The only way to get around this is to delete the entire array registration!
I created an SR and the latest news on that is that it's been filed as a bug.....
Jeff

UCS/Nexus and FCoE Question

Hi, All:
Can one connect an FCoE target directly to a Fabric Interconnect or a Nexus 5xxx FCF when in NPV mode and not connected to an FC switch for fabric services and still be able to have the initiator see the target and be able to provision storage accordingly?
So, the scenario would be the following:
a rack server with a CNA connected to a Nexus 5xxx FCF in NPV mode
OR
a blade server with a CNA connected to a UCS Fabric Interconnect (which is also an FCF) in NPV mode
AND
In either of the cases above, there is NO CONNECTION between the FCF and an FC switch.
Will I be able to have the CNA (FCoE initiator) see the Strorage array (FCoE target)?
Thank you

Ganesh, your answers make sense, and given my understanding of FCoE and the FLOGI and PLOGI processes, I want to agree with you. BUT I have had a person who I believe to be very knowledgeable in UCS (former Cisco solutions engineer) tell me that you CAN connect an FCoE storage array directly to an FI FCoE port while the FI is in NPV mode and be able to provision storage, even if the FI is not connected to an FC switch. To me, that doesnt make sense because, in such a case, there is no appliance to provide FC services to support the FIP FLOGI and PLOGI processes - and therefore, how would an E_Node (VN_Port) be able to log into the fabric, get an FC-ID and FPMA, register with the name server and engage in peer VN_Port capability discovery? How would a server CNA even know that there is a storage array that is reachable without the PLOGI process?

Nexus 5K FCoE Licences

Hi ,
I need following clarification from anyone who is familliar with Nexus switch family , Since this things are bit confusing .
1) . If only one N55-8P-SSK9 ( Nexus 5500 Storage License, 8 Ports ) licences is installed in Nexus 5596UP, Does this enable FCoE capability to entire switch or only for 8 Ports ?
2). If 2232PP is connected to 5596UP ,Do all the Downlink ports which connected to 2232PP counts as FCoE ?
Thanks
Rajitha

Hello Rajitha,
Please see the below table for N55-8P-SSK9( Nexus 5500 Storage License, 8 Ports )
1)
For more info on this please refer to below link:-
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html
2) If 2232PP is connected to 5596UP, Yes all the Downlink ports which connected to 2232PP counts as FCoE.
Thanks,
Gaurav.

Sparc Storage Array 200: HOWTO?

Hi, I have a sun enterprise 5000 machine up and running with Solaris 10. I also have a Sparc Storage Array 200 which connects via a fibre channel to the machine. I have tried to search for documentation online, but can�t seem to find any on Sun�s website. What I was able to find out is that that there is a program called ssaadm which might help me talk to the array. However that program is not installed and when I do pkgadd it tells me that no packages were found in /var/spool/pkg. I�m very use to the some GNU/linux package management systems (such as apt (debian) or emerge (gentoo)), and they just get the packages online from the repository and download, (compile), and install them. I also cant find any info as what the dev nodes will be for the fibre card (I dont even know if solaris has drivers for it). If anyone could either tell me what needs to be done or point me in the direction of documentation I would greatly like that. Thanks.

drop down to Solaris 9... if you really want to use the SSA, then Solaris 9 was the last OS that supported it...
I doubt there is any support in Linux...
haroldkarl
oh yes... documentation... docs.sun.com...
ftp://192.18.109.11/802-2041/802-2041.pdf
Message was edited by:
haroldb

FCoE in Nexus 5000

Hi,
I have a Nexus 5000 conected with a UCS C-200 with qlogic CNA in FCoE. The ethernet traffic is ok, but FC dont work fine, i thinks that i have configured all ok, by the show int vfc show the trunk vsan in initializating mode and i dont find what is the problem
switch(config-if)# sh int vfc 1
vfc1 is trunking
    Bound interface is Ethernet1/9
    Port description is Conexion FC con UCS1
    Hardware is Virtual Fibre Channel
    Port WWN is 20:00:00:0d:ec:e8:2c:7f
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 1
    Trunk vsans (admin allowed and active) (1)
    Trunk vsans (up)                       ()
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (1)
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
    Interface last changed at Mon Dec 20 19:59:31 2010
switch(config-if)# show port internal info interface vfc 1
vfc1 - if_index: 0x1E000000, phy_port_index: 0x1000
     local_index: 0xffff
Admin Config - state(up), mode(F), speed(auto), trunk(on)
    beacon(off), snmp trap(on), tem(false)
    description(Conexion FC con UCS1)
    port owner()
Operational Info - state(trunking), mode(TF), speed(auto), trunk(on)
    state reason(None)
    phy port enable (1), phy layer (FC), port_osm_mode(OSM)
    participating(1), fcid(0x000000), bb_scn(0)
    config port vsan (1), oper port vsan (1)
    rx bb_credit(0), rx bb_credit multiplier(0)
    rx bb_credit performance buffers(0), tx bb_credit(0)
    not first time port bringup is 0
    Port WWN is 20:00:00:0d:ec:e8:2c:7f
    current state [PI_FSM_ST_TXPORT_INIT_TRUNKING_ENABLED]
    port_init_eval_flag(0x00000401), cfg wait for none
        FC_PORT_INIT_DATA_VALID (0)
        FC_PORT_INIT_ADMIN_ST_DOWN_TO_UP (10)
        FC_PORT_INIT_PHY_PORT_UP (49)
    Mts node id 0x0
    Lock Info: resource [vfc1]
      type[0] p_gwrap[(nil)]
          FREE @ 259535 usecs after Mon Dec 20 19:59:31 2010
      type[1] p_gwrap[(nil)]
          FREE @ 260559 usecs after Mon Dec 20 19:59:31 2010
      type[2] p_gwrap[(nil)]
          FREE @ 266012 usecs after Mon Dec 20 19:59:31 2010
    0x10000001e000000
    eport_init_flag(0x00000000), elp_chk_flag(0x00000000)
    elp_rcvd_fc2_handle(0x00000000), elp_sent_fc2_handle(0x00000000)
    esc_chk_flag(0x00000000), esc_fc2_handle(0x00000000)
    elp_flags(0x0000), classes_supported(F), tx bb_credit(0)
    Peer ELP Revision: 0
    Timer active for PI_FSM_EV_TE_2_E_TIMER_EXPIRED
    cnt_link_failure(0), cnt_link_success(0), cnt_port_up(0)
    cnt_cfg_wait_timeout(2), cnt_port_cfg_failure(2), cnt_init_retry(0)
    nos link failures (0), debounce window (300 ms), elp wait tout (750 ms)
    link fail reason (0x0)    num_elps_before_up (0)
    internal_reinit_counter (0) external_reinit_counter (0)
Trunk Info -
    trunk vsans (allowed active) (1)
    trunk vsans (operational allowed) (1)
    trunk vsans (up) ()
    trunk vsans (isolated) ()
TE port per vsan information
vfc1, Vsan 1 - state(down), state reason(waiting for flogi), fcid(0x000000)
    port init flag(0x0),
    Lock Info: resource [vfc1, vsan 1]
      type[0] p_gwrap[(nil)]
          FREE @ 270103 usecs after Mon Dec 20 19:59:31 2010
      type[1] p_gwrap[(nil)]
          FREE @ 270104 usecs after Mon Dec 20 19:59:31 2010
      type[2] p_gwrap[(nil)]
          FREE @ 270105 usecs after Mon Dec 20 19:59:31 2010
    0x40000011e000000
current state [TE_FSM_ST_WAIT_FOR_FLOGI]
    RNID info not found.
    first time elp: 1
    Peer ELP Revision: 0
Pacer Info -
    Pacer state: released credits due to timer expiry
PQP: not in progress
My configuration
vlan 701
fcoe vsan 1
name FCoE-Vsan1
interface vfc1
bind interface Ethernet1/9
switchport description Conexion FC con UCS1
no shutdown
interface Ethernet1/9
description Conexion FCoE con UCS1
switchport mode trunk
spanning-tree port type edge trunk
I need configure anything in UCS?.
Regards.

A network diagram would be quite useful ? is it multihop FCoE, Storage connectivity with FCoE,......

Single Nexus 5548UP- FCoE configuration with multiple server ports

Hello Everyone,
I am new to Networking so please bear with me.
Here is some background information. We have a SINGLE Nexus 5548 UP switch to which we are connecting both the storage and the UCS C240 M3 servers (with CNA). Both the storage and server has 2 ports each going to this nexus switch.
We want to implement FCoE with this solution.
Below are the steps (for server ports) that I have followed to configure the nexus. But the port not logging into the SAN (no flogi) with the config.
Enable Features
config t
feature lacp
feature dot1x
feature interface-vlan
feature sshServer
feature npiv
end
Confgure Ethernet Ports - Server
configure
interface ethernet 1/17
description To_UCS_rack_server_1_FCoE_port_1
switchport mode trunk
switchport trunk native vlan 6
switchport trunk allowed vlan 1,6
spanning-tree port type edge trunk
priority-flow-control mode on
no shutdown
end
configure
interface ethernet 1/18
description To_UCS_rack_server_1_FCoE_port_2
switchport mode trunk
switchport trunk native vlan 6
switchport trunk allowed vlan 1,6
spanning-tree port type edge trunk
priority-flow-control mode on
no shutdown
end
Create VLAN
configure
vlan 6
name FCOE_VLAN
fcoe vsan 6
end
Setup FCoE QOS
configure terminal
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy
end
Create vfc for Initiators (UCS Servers)
configure
interface vfc 17
bind interface ethernet 1/17
switchport description virtual_fiber_channel_Server1_Port1
end
configure
interface vfc 18
bind interface ethernet 1/18
switchport description virtual_fiber_channel_Server1_Port2
end
Adding vFC’s to VSAN
configure
vsan database
vsan 6 interface vfc 17
vsan 6 interface vfc 18
Create Zonesets and Zones
configure
show flogi database vsan 6 ----> Do not see any pwwn here???
show fcns database vsan 6
Any help in the regard would be highly appreciated.
Cheers,
KS

Fixed the issue. "switchport trunk native vlan 6" was causing the issue. Maybe the storage and Servers were not configured with proper VLAN's. I removed the native vlan and everything logged in fine.
Any how I have configured a single zone with all 3 servers pWWN's. I know single initiator zoning is the way to go.
Can you please guide me if I can move these servers in their separate zones without any outages? If it helps, all severs have 2 pWWN's. The current zoneset is active with that single zone.
Please let me know if you need any additional details.
Cheers,
KS

Connecting directly macbook pro to ethernet big disk...

I was wondering if i could connect directly my macbook pro to the ethernet plug of ethernet big disk with ethernet cable. I have used the lacie connected to netgear router but the big disk showed that it was connected at 100mbits/s. When I tried to take same cable and plug it in macbook pro and fiddle around wth advanced ethernet option, the settings always came back to previous ones. Why? Thank you for looking at this tread and hope i will enjoy super fast transfer rates because it is painfully slow at 100mbits/s. Funny how firewire 800 makes such a difference. Thanks.
David

Hi, as a matter of fact there is such a thing...
http://eshop.macsales.com/item/NewerTech/VIDU2DVIA/
Features
Works on PC and Intel Mac models
Lossless compression
LCD, CRT, projector displays
Connect one extra monitor per adapter to your desktop or laptop's USB port!
Configure connected monitors to either clone your primary screen, or extend the desktop allowing visibility of more applications at the same time!
Display Modes:
Can easily Mirror the main display
Extend left, right, above, or below
Can be rotated left, right, or upside-down
Windows Vista & 7 Aero support
Windows XP and Vista 32-bit support
Standard and Widescreen ratio aspects
High-Performance DDR memory
Completely silent operation
Uses very little computer resources and offers a vast array of screen resolutions and color depths ensuring little performance difference between a screen directly connected or via USB 2.0
Supports resolutions up to 2048 x 1152 including SDTV/HDTV resolutions: 480i/p (640x480), 720p (1280x720), 1080i/p (1920x1080)
There may also be an Apple adapter, but they change Video ports more often than I can keep track of.

Couldn't see LUNS fpr Compaq Storage array 1000 solaris box

Hi All,
I want to connect Compaq storage Works SAN array to solaris10 Box. I can see array as connected but state as unusable.
How can i see the luns from the storage on solaris box??
dmesg output:
Feb 1 08:29:54 testappl        ndi_devi_online: failed for array-controller: target=11000 lun=0 ffffffff
Feb 1 08:30:25 testappl fctl: [ID 517869 kern.warning] WARNING: fp(7)::PLOGI succeeded: no skip(2) for D_ID 11000
Feb 1 08:30:25 testappl genunix: [ID 599346 kern.warning] WARNING: Page83 data not standards compliant COMPAQ   MSA1000          2.38
Feb 1 08:30:25 testappl scsi: [ID 243001 kern.info] /pci@1d,700000/SUNW,emlxs@2/fp@0,0 (fcp7):
Feb 1 08:30:25 testappl        ndi_devi_online: failed for array-controller: target=11000 lun=0 ffffffff
Feb 1 08:47:27 testappl emlxs: [ID 349649 kern.info] [ 5.05F8]emlxs3: NOTICE: 730: Link reset.
Feb 1 08:47:27 testappl emlxs: [ID 349649 kern.info] [ 5.0337]emlxs3: NOTICE: 710: Link down.
Feb 1 08:47:30 testappl emlxs: [ID 349649 kern.info] [ 5.054D]emlxs3: NOTICE: 720: Link up. (2Gb, fabric, initiator)
Feb 1 08:47:30 testappl genunix: [ID 599346 kern.warning] WARNING: Page83 data not standards compliant COMPAQ   MSA1000          2.38
Feb 1 08:47:30 testappl scsi: [ID 243001 kern.info] /pci@1d,700000/SUNW,emlxs@2/fp@0,0 (fcp7):
Feb 1 08:47:30 testappl        ndi_devi_online: failed for array-controller: target=11000 lun=0 ffffffff
cfgadm -al output:
bash-3.00# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c0                             scsi-bus     connected    configured   unknown
c0::dsk/c0t0d0                 CD-ROM       connected    configured   unknown
c1                             scsi-bus     connected    configured   unknown
c1::dsk/c1t0d0                 disk         connected    configured   unknown
c1::dsk/c1t1d0                 disk         connected    configured   unknown
c1::dsk/c1t2d0                 disk         connected    configured   unknown
c2                             fc           connected    unconfigured unknown
c5                             scsi-bus     connected    unconfigured unknown
c6                             fc           connected    unconfigured unknown
c7                             fc-fabric    connected    configured   unknown
c7::500805f3000186d9           array-ctrl   connected    configured   unusable
usb0/1                         usb-device   connected    configured   ok
usb0/2                         unknown      empty        unconfigured ok
usb1/1                         unknown      empty        unconfigured ok
usb1/2                         unknown      empty        unconfigured okthanks in advance.

Looks like the LUN is not configured correctly on the storage array. The kernel can't take the LUN online.
I have seen this on various boxes, most of the time it was either that the LUN wasn't set online on the SAN box or there is a SCSI reservation on the LUN.
Can you access the LUN from another host?

FCoE capable Storage Array connected directly to Nexus 5000 FCoE port

Similar Messages

Maybe you are looking for