Connecting many Brocade switches to Nexus 5548UP

Hello,
I have a SAN network composed of few separate PODs. Each POD is divided into SAN-A and SAN-B. Most of those PODs are Brocade switches (FOS 6.1). There are also few Nexus 5520s. Now, we have built new core infrastructure with Nexus 5548UPs and many MDS 9148s. We would like to move all servers and sotrage from old Brocades to the new SAN. As we cannot move all devices at the same time, all segments must be connected to the core for some time. Each POD has different zoning. Some zonings on Brocade switches are based on PWWN, some on Domain ID and Port ID. In my opinion, the only way of successfuly connecting all PODs together is to merge zones manualy (in excel, etc). and paste them on all switches. However, maybe there is some other way of merging all zones? What if I leave Nexus 5548UP in native mode (so zones from Brocade will not get merged), and only implement that manually merged zoneset on Nexus 5548UP? Will the ISL links get isolated due to zoning merge failure? Or they will maintain operational state even if zones are different on each POD? I do not have any lab boxes, so I cannot test it. Any advidse will be appreciated.
Best regards,
Krzyszof

well since you can not cluster the 45K as a virtual switch ( Cisco with new sup will start support VSS in the 4500 try to check which sup exactly and if you can upgrade as this will make a significant improvement to your design )
anyway the only method that you can use currently is the traditional way which is depending on STP ( use rapid-PVST)
from each N5K use one separate link to each 45K and STP will put on of the links in blocking mode
however you might do some STP and vlan design for load sharing where you can send vlan x over link1 and vlan y over link b to the 45K using STP cost
HTH

Similar Messages

Cisco Nexus 5548UP to Brocade SAN Connectivity

Hi,
I have a Server-SAN-Storage setup as shown in the attachment/below. There are new Cisco UCS rack mount servers with VIC 1225 and Virtual servers on VMware Esxi hypevisor connected to a new Cisco Nexus 5548UP switch in IP+FCoE mode. The new 5548 switch then connects to an existing production SAN of Brocade 48000 Director SAN switch which connects to storage in production environment.
I need to know the best way to connect the 5548 switch to the Brocade SAN switch without disrupting the existing Production SAN environment i.e. Brocade SAN switch configurations & setup e.g. Fabric Principal switch. priority etc.
Would configuring the 5548 switch in NPV mode be best practice?

See Figure 6-2 Converged Multi-hop FCoE Network Design Using FCoE NPV
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/fcoe/513_n1_1/ops_fcoe/ops_fcoe_npv.html
You have to use NPV on N5k, there is no FC interop support on N5k, to connect to Brocade.

Connect Nexus 5548UP-L3 to Catalyst 3750G-24T-E Layer 3 Switch

Please help!
Could anyone out there please assist me with basic configuration between Nexus Switch and Catalyst Switch, so that devices connected on the catalyst switch can talk to devices connected on nexus switch and vice-versa? In my current setup all servers on VLAN 40 are connected on the Catalyst Switch A as shown in the diagram below, and all desktops and all other peripherals are connected on the Catalyst Switch B. I am required to implement/add a new Nexus Switch 5548 that in the future will replace the Switch A. From now I just need to connect both switches together and start moving the server from Switch A to the Nexus Switch.
The current network setup is shown as per diagram below:
SWITCH A – this is a layer 3 switch. All servers are connected to this switch on the VLAN 40.
SWITCH B – all desktops, VoIP telephones, and printers are connected on tis switch. This switch is also a layer 3 switch.
I have connected together the Nexus 5548UP and SWITCH A (3750G) using the GLC-T= 1000BASE-T SFP transceiver module for Category 5 copper wire. The new network is shown as per diagram below:
Below is the configuration I have created in both Switches:
SWITCH A - 3750G
interface Vlan40
description ** Server VLAN **
ip address 10.144.40.2 255.255.255.128
ip helper-address 10.144.40.39
ip helper-address 10.144.40.40
interface Vlan122
description connection to N5K-C5548UP Switch mgmt0
ip address 172.16.0.1 255.255.255.128
no ip redirects
interface Port-channel1
description UpLink to N5K-C5548UP Switch e1/1-2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
interface GigabitEthernet1/0/3
description **Connected to server A**
switchport access vlan 40
no mdix auto
spanning-tree portfast
interface GigabitEthernet1/0/20
description connection to N5K-C5548UP Switch mgmt0
switchport access vlan 122
switchport mode access
spanning-tree portfast
interface GigabitEthernet1/0/23
description UpLink to N5K-C5548UP Switch e1/1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
channel-group 1 mode active
interface GigabitEthernet1/0/24
description UpLink to N5K-C5548UP Switch e1/2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
channel-group 1 mode active
N5K-C5548UP Switch
feature interface-vlan
feature lacp
feature dhcp
feature lldp
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1
vlan 100
service dhcp
ip dhcp relay
interface Vlan1
no shutdown
interface Vlan40
description ** Server VLAN **
no shutdown
ip address 10.144.40.3/25
ip dhcp relay address 10.144.40.39
ip dhcp relay address 10.144.40.40
interface port-channel1
description ** Trunk Link to Switch A g1/0/23-24 **
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
interface Ethernet1/1
description ** Trunk Link to Switch A g1/0/23**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,12
speed 1000
channel-group 1 mode active
interface Ethernet1/2
description ** Trunk Link to Switch A g1/0/24**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
channel-group 1 mode active
interface Ethernet1/3
description **Connected to server B**
switchport access vlan 40
speed 1000
interface mgmt0
description connection to Switch A g2/0/20
no ip redirects
ip address 172.16.0.2/25
I get a successful response from Server A when I ping the N5K-C5548UP Switch (VLAN 40 interface (10.144.40.3) .But if I try to ping from Server A to Server B or vice-versa the ping fails. From N5K-C5548UP I can ping successful either Server A or Server B. What am I doing wrong here? Is there any additional configuration that I need to add on the Nexus Switch? Please Help. Thank you.

no, no secret aukhadiev
I made a mistake without realising and the interface e1/3 was showing "Interface Ethernet1/3 is down (Inactive)". After spending sometime trying to figure out what was wrong with that interface or switch, it turned out to be that i forgot to add the vlan 40. Now the config looks like this:
N5K-C5548UP Switch
feature interface-vlan
feature lacp
feature dhcp
feature lldp
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1
vlan 40
vlan 100
service dhcp
ip dhcp relay
interface Vlan1
no shutdown
interface Vlan40
description ** Server VLAN **
no shutdown
ip address 10.144.40.3/25
ip dhcp relay address 10.144.40.39
ip dhcp relay address 10.144.40.40
interface port-channel1
description ** Trunk Link to Switch A g1/0/23-24 **
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
interface Ethernet1/1
description ** Trunk Link to Switch A g1/0/23**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,12
speed 1000
channel-group 1 mode active
interface Ethernet1/2
description ** Trunk Link to Switch A g1/0/24**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
channel-group 1 mode active
interface Ethernet1/3
description **Connected to server B**
switchport access vlan 40
speed 1000
interface mgmt0
description connection to Switch A g2/0/20
no ip redirects
ip address 172.16.0.2/25
Thank you,
JN

Connecting backup server to brocade switch help

Hi all
We are implementing a new backup server for our SAN, the server currently had one connection to our brocade switch, is it possible to put a second connection to the brocade switch from the server? and will it team them or become a failover connection, I believe the FC card in the server is Q Logic
hope you can help
thanks
Carl

There are no restrictions whatsoever to how many ports you use to connect from your server to the switch. I had a single server that used 16 ports to each switch.
I was wrong with the first post as I got sidetracked talking about how FC does trunking. You can't trunk from the server to the switch. It does from switch to switch though. The server multipathing software manages the traffic to the storage array normally in a round robin approach.
If you just have a backup server <-> switch <-> FC tape drive, the traffic is managed by the backup media agent. Backups are pretty simple as tape drives are just one thing. They are not like storage arrays.
As far as broadcast goes, look up RSCN.
FC networking is different to IP so get a book and read up about it.

Nexus 6004 TOR connectivity to Brocade DCX

Hi Experts,
I am facing an issues in our new data centre. We want to install Nexus 6004 in the TOR and connect the FC links back to the existing DCX?
I see from the datasheets that the 6004 now has native FC capability. Is it supported to set the 6004 to NPIV mode and connect as an Access gateway to the edge for the Brocade SAN?
Any advise appreciated as I really want to push CISCO at the TOR.
digduggo

See Figure 6-2 Converged Multi-hop FCoE Network Design Using FCoE NPV
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/fcoe/513_n1_1/ops_fcoe/ops_fcoe_npv.html
You have to use NPV on N5k, there is no FC interop support on N5k, to connect to Brocade.

Nexus 5548UP with 1Gb ether to 10Gb ether on same switch

I have a Nexus 5548UP switch with a couple of systems some of which have been configured with 1Gb nic's running various OS's and other that have 10Gb nic's. When I try to SSH from 1Gb box to a 1Gb box everything is fine, when I SSH from 1Gb to 10Gb box it does not work but 10Gb to 10Gb boxes will work. The switch is a fresh install and has one VLAN 51 the first 2 ports are setup with LACP and the only differences is speed of 1000 and 10000 for the boxes attached. Is there some trick or additional configuration that is needed to make 1Gb to 10Gb work for SSH and other applications? I trying to setup some test boxes now to have a repeatable environment and will update when completed.
!Command: show running-config
!Time: Fri Jan 9 18:30:44 2009
version 5.2(1)N1(4)
hostname ISC5548B
no feature telnet
feature lacp
feature lldp
...... account info removed
ssh key rsa 2048
ip domain-lookup
class-map type qos class-fcoe
class-map type queuing class-fcoe
match qos-group 1
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-fcoe
match qos-group 1
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
vrf context management
ip route 0.0.0.0/0 192.168.52.1
vlan 1
vlan 51
name InfoSec
port-profile default max-ports 512
interface port-channel1
switchport access vlan 51
speed 1000
interface Ethernet1/1
lacp port-priority 500
switchport access vlan 51
speed 1000
channel-group 1 mode active
interface Ethernet1/2
switchport access vlan 51
speed 1000
channel-group 1 mode active
interface Ethernet1/3
switchport access vlan 51
speed 1000
interface Ethernet1/4
switchport access vlan 51
speed 1000
interface Ethernet1/5
switchport access vlan 51
speed 1000
interface Ethernet1/6
switchport access vlan 51
speed 1000
interface Ethernet1/7
switchport access vlan 51
speed 1000
interface Ethernet1/8
switchport access vlan 51
speed 1000
interface Ethernet1/9
switchport access vlan 51
speed 1000
interface Ethernet1/32
switchport access vlan 51
speed 1000
interface Ethernet2/1
switchport access vlan 51
interface Ethernet2/2
switchport access vlan 51
interface Ethernet2/3
switchport access vlan 51
interface Ethernet2/4
switchport access vlan 51
interface Ethernet2/5
switchport access vlan 51
interface Ethernet2/6
switchport access vlan 51
interface Ethernet2/7
switchport access vlan 51
interface Ethernet2/8
switchport access vlan 51
interface Ethernet2/14
switchport access vlan 51
interface Ethernet2/15
switchport access vlan 51
interface Ethernet2/16
switchport access vlan 51
interface mgmt0
ip address 192.168.52.4/24
line console
line vty
boot kickstart bootflash:/n5000-uk9-kickstart.5.2.1.N1.4.bin
boot system bootflash:/n5000-uk9.5.2.1.N1.4.bin
ISC5548B# show int brief
Ethernet      VLAN    Type Mode   Status Reason                   Speed     Port
Interface                                                                    Ch #
Eth1/1        51      eth access up      none                       1000(D) 1
Eth1/2        51      eth access up      none                       1000(D) 1
Eth1/3        51      eth access up      none                       1000(D) --
Eth1/4        51      eth access up      none                       1000(D) --
Eth1/5        51      eth access up      none                       1000(D) --
Eth1/6        51      eth access up      none                       1000(D) --
Eth1/7        51      eth access up      none                       1000(D) --
Eth1/8        51      eth access up      none                       1000(D) --
Eth1/9        51      eth access up      none                       1000(D) --
Eth1/10       51      eth access up      none                       1000(D) --
Eth1/11       51      eth access up      none                       1000(D) --
Eth1/12       51      eth access up      none                       1000(D) --
Eth1/13       51      eth access down    Link not connected         1000(D) --
Eth1/14       51      eth access down    Link not connected         1000(D) --
Eth1/15       51      eth access up      none                       1000(D) --
Eth1/16       51      eth access down    Link not connected         1000(D) --
Eth1/17       51      eth access down    SFP not inserted           1000(D) --
Eth1/18       51      eth access down    SFP not inserted           1000(D) --
Eth1/28       51      eth access down    SFP not inserted           1000(D) --
Eth1/29       51      eth access down    SFP not inserted           1000(D) --
Eth1/30       51      eth access down    SFP not inserted           1000(D) --
Eth1/31       51      eth access down    SFP not inserted           1000(D) --
Eth1/32       51      eth access down    SFP not inserted           1000(D) --
Eth2/1        51      eth access up      none                        10G(D) --
Eth2/2        51      eth access up      none                        10G(D) --
Eth2/3        51      eth access up      none                        10G(D) --
Eth2/4        51      eth access up      none                        10G(D) --
Eth2/5        51      eth access up      none                        10G(D) --
Eth2/6        51      eth access up      none                        10G(D) --
Eth2/7        51      eth access down    SFP not inserted            10G(D) --
Eth2/8        51      eth access down    SFP not inserted            10G(D) --
Eth2/9        51      eth access down    SFP not inserted            10G(D) --
Eth2/10       51      eth access down    SFP not inserted            10G(D) --
Eth2/11       51      eth access down    SFP not inserted            10G(D) --
Eth2/12       51      eth access down    SFP not inserted            10G(D) --
Eth2/13       51      eth access down    Link not connected          10G(D) --
Eth2/14       51      eth access down    SFP not inserted            10G(D) --
Eth2/15       51      eth access down    Link not connected          10G(D) --
Eth2/16       51      eth access down    Link not connected          10G(D) --
Port-channel VLAN    Type Mode   Status Reason                    Speed   Protocol
Interface
Po1          51      eth access up      none                      a-1000(D) lacp
Port   VRF          Status IP Address                              Speed    MTU
mgmt0 --           up     192.168.52.4                            100      1500
ISC5548B# show interface ethernet 1/3
Ethernet1/3 is up
Dedicated Interface
Hardware: 1000/10000 Ethernet, address: 8c60.4f49.818a (bia 8c60.4f49.818a)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 1000 Mb/s, media type is 10G
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 1d02h
Last clearing of "show interface" counters 1d20h
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 304 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
    input rate 0 bps, 0 pps; output rate 200 bps, 0 pps
RX
    0 unicast packets 0 multicast packets 0 broadcast packets
    0 input packets 0 bytes
    0 jumbo packets 0 storm suppression bytes
    0 runts 0 giants 0 CRC 0 no buffer
    0 input error 0 short frame 0 overrun   0 underrun 0 ignored
    0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
    0 input with dribble 0 input discard
    0 Rx pause
TX
    202 unicast packets 87027 multicast packets 1077 broadcast packets
    88306 output packets 7601016 bytes
    0 jumbo packets
    0 output errors 0 collision 0 deferred 0 late collision
    0 lost carrier 0 no carrier 0 babble 0 output discard
    0 Tx pause
4 interface resets
ISC5548B# show interface ethernet 2/1
Ethernet2/1 is up
Dedicated Interface
Hardware: 1000/10000 Ethernet, address: 8c60.4f23.5de0 (bia 8c60.4f23.5de0)
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 10 Gb/s, media type is 10G
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 1d20h
Last clearing of "show interface" counters never
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 312 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
    input rate 0 bps, 0 pps; output rate 200 bps, 0 pps
RX
    285 unicast packets 0 multicast packets 218 broadcast packets
    503 input packets 32724 bytes
    0 jumbo packets 0 storm suppression bytes
    0 runts 0 giants 0 CRC 0 no buffer
    0 input error 0 short frame 0 overrun   0 underrun 0 ignored
    0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
    0 input with dribble 0 input discard
    0 Rx pause
TX
    406 unicast packets 89109 multicast packets 1077 broadcast packets
    90592 output packets 7827146 bytes
    0 jumbo packets
    0 output errors 0 collision 0 deferred 0 late collision
    0 lost carrier 0 no carrier 0 babble 0 output discard
    0 Tx pause
1 interface resets

I have a laptop connected to a port on the switch and I am currently adding a SUSE 11 SP2 to another port that has a 10G card for a NIC. Once I finished the install I will post more specific tests using ping and SSH to illustrate.
Here is the output you requested.
ISC5548B# show port-channel summary
Flags: D - Down        P - Up in port-channel (members)
        I - Individual H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
        M - Not in use. Min-links not met
Group Port-       Type     Protocol Member Ports
      Channel
1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)
ISC5548B# sh int po1
port-channel1 is up
Hardware: Port-Channel, address: 8c60.4f49.8188 (bia 8c60.4f49.8188)
MTU 1500 bytes, BW 2000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 1000 Mb/s
Input flow-control is off, output flow-control is off
Switchport monitor is off
EtherType is 0x8100
Members in this channel: Eth1/1, Eth1/2
Last clearing of "show interface" counters never
30 seconds input rate 560 bits/sec, 0 packets/sec
30 seconds output rate 3064 bits/sec, 2 packets/sec
Load-Interval #2: 5 minute (300 seconds)
    input rate 128 bps, 0 pps; output rate 2.74 Kbps, 2 pps
RX
    578695 unicast packets 11167 multicast packets 1056 broadcast packets
    590918 input packets 760063851 bytes
    0 jumbo packets 0 storm suppression bytes
    0 runts 0 giants 0 CRC 0 no buffer
    0 input error 0 short frame 0 overrun   0 underrun 0 ignored
    0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
    0 input with dribble 0 input discard
    0 Rx pause
TX
    392417 unicast packets 434693 multicast packets 2984 broadcast packets
    830094 output packets 320257324 bytes
    0 jumbo packets
    0 output errors 0 collision 0 deferred 0 late collision
    0 lost carrier 0 no carrier 0 babble 0 output discard
    0 Tx pause
1 interface resets

Nexus 5548UP / FEX Connectivity doubt

Hello Everybody,
Some weeks ago, we decided to do a connectivity test with our nexus equipment. The topology was fairly simple, only one Nexus 5548UP, no vPC domain configured. 2 Nexus 2248TP Fabric Extenders connected to the 5548UP. Finally, a server, doing NIC teaming, ACTIVE-ACTIVE in a PortChannel config, one link to each Nexus 2248TP Fabric Extender. Topology attached below.
My understanding was that the FEXs were remote line cards, so what we are doing here is like adding 2 linecards to a moludar switch like a 6500 and creating a PortChannel using 1 link to 1 linecard, and 1 link to another linecard.
To my surprise, this was not allowed.
I tried to find and explanation why this could not be configured, but nothing found.
Anyone has an idea why this could be happening?
thanks in advance,
Fernando

Hello Everybody,
Some weeks ago, we decided to do a connectivity test with our nexus equipment. The topology was fairly simple, only one Nexus 5548UP, no vPC domain configured. 2 Nexus 2248TP Fabric Extenders connected to the 5548UP. Finally, a server, doing NIC teaming, ACTIVE-ACTIVE in a PortChannel config, one link to each Nexus 2248TP Fabric Extender. Topology attached below.
My understanding was that the FEXs were remote line cards, so what we are doing here is like adding 2 linecards to a moludar switch like a 6500 and creating a PortChannel using 1 link to 1 linecard, and 1 link to another linecard.
To my surprise, this was not allowed.
I tried to find and explanation why this could not be configured, but nothing found.
Anyone has an idea why this could be happening?
thanks in advance,
Fernando

Fabric with two Nexus-5548 and a brocade switch does not get fabric updates

We have a fabric containing two Nexus 5548 and a Brocade 5000 switch in interop mode 2. When i make changes to the zoning, the first nexus (the fabric principal) and the brocade switch see the zone changes. The second Nexus switch does not see it. There are no error messages but the change just can't be seen. What can i do to find out, what goes wrong ?

Ouch, deprecated is not the word i wanted to read
We are using 5.1(3)N1(1a) on nexus-rz1-a
and 6.0(2)N1(2) on nexus-rz2-a.
The fabric can be seen :
nexus-rz2-a# show fcs ie vsan 10
IE List for VSAN: 10
IE-WWN                   IE     Mgmt-Id Mgmt-Addr (Switch-name)
10:00:00:05:1e:90:57:27 S(Rem) 0xfffc01 10.88.133.110 (bc-san1)
20:0a:00:2a:6a:72:ba:01 S(Loc) 0xfffc1c 10.88.133.105 (nexus-rz2-a)
20:0a:54:7f:ee:7f:dc:01 S(Adj) 0xfffc0b 10.88.133.100 (nexus-rz1-a)
[Total 3 IEs in Fabric]
nexus-rz1-a# show fcs ie vsan 10
IE List for VSAN: 10
IE-WWN                   IE     Mgmt-Id Mgmt-Addr (Switch-name)
10:00:00:05:1e:90:57:27 S(Adj) 0xfffc01 10.88.133.110 (bc-san1)
20:0a:00:2a:6a:72:ba:01 S(Adj) 0xfffc1c 10.88.133.105 (nexus-rz2-a)
20:0a:54:7f:ee:7f:dc:01 S(Loc) 0xfffc0b 10.88.133.100 (nexus-rz1-a)
[Total 3 IEs in Fabric]
I try to distribute the zoneset this way:
zoneset distribute vsan 10
Zoneset distribution initiated. check zone status
nexus-rz1-a# show zone status
VSAN: 10 default-zone: deny distribute: full Interop: 2
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 6291 bytes
    Zonesets:1 Zones:62 Aliases: 44
Active Zoning Database :
    DB size: 10243 bytes
    Name: FABRIC1 Zonesets:1 Zones:60
Status: Zoneset distribution completed at 08:06:00 UTC Dec 3 2013
nexus-rz2-a# show zone status
VSAN: 1 default-zone: deny distribute: active only Interop: default
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 4 bytes
    Zonesets:0 Zones:0 Aliases: 0
Active Zoning Database :
    Database Not Available
Status:
VSAN: 10 default-zone: deny distribute: full Interop: 2
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 6291 bytes
    Zonesets:1 Zones:62 Aliases: 44
Active Zoning Database :
    DB size: 10243 bytes
    Name: FABRIC1 Zonesets:1 Zones:60
Status: Activation completed at 13:03:42 UTC Dec 2 2013

Connecting a 3500 through a Brocade Switch to Hitachi SAN

I have a E3500 with a x6730A fiber card attached to a Brocade Switch and that switch to a Hitachi SAN. I wanted to find out where I need to start? I can see that E3500 recognizes the HBA card, but unsure as to where to go from here. Do I need to get Veritas FS or can I create volumes through Solstice? Any advice would be appreciated. I have all 3 components configured separatly but have never connected any of them together.
# ls -la /dev/cfg
total 18
drwxr-xr-x 2 root root 512 Mar 1 12:10 .
drwxr-xr-x 14 root sys 3072 Mar 9 13:52 ..
lrwxrwxrwx 1 root root 51 Mar 1 12:10 c0 -> ../../devices/sbus@2,0/SUNW,socal@d,10000/sf@0,0:fc
lrwxrwxrwx 1 root root 51 Mar 1 12:10 c1 -> ../../devices/sbus@2,0/SUNW,socal@d,10000/sf@1,0:fc
lrwxrwxrwx 1 root root 46 Mar 1 12:10 c2 -> ../../devices/sbus@3,0/SUNW,fas@3,8800000:scsi
lrwxrwxrwx 1 root root 47 Mar 1 12:10 c3 -> ../../devices/sbus@3,0/SUNW,socal@0,0/sf@0,0:fc
lrwxrwxrwx 1 root root 47 Mar 1 12:10 c4 -> ../../devices/sbus@3,0/SUNW,socal@0,0/sf@1,0:fc
c3 and c4 are the addresses of the HBA card

I am currently running Solaris 8 and will be using a Hitachi SAN to put an Oracle 9 database on it. Currently the Brocade switch can see our Hitachi SAN, but we are stuck on how to connect E3500 through x6730A to the Brocade.
SunOS morrison 5.8 Generic_117350-23 sun4u sparc SUNW,Ultra-Enterprise
# luxadm probe
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node WWN:20000020378f9154 Device Type:Disk device
Logical Path:/dev/rdsk/c0t0d0s2
Node WWN:20000020379c5e10 Device Type:Disk device
Logical Path:/dev/rdsk/c1t4d0s2
Node WWN:20000020375cca44 Device Type:Disk device
Logical Path:/dev/rdsk/c1t5d0s2
Node WWN:20000020371ae3ef Device Type:Disk device
Logical Path:/dev/rdsk/c0t1d0s2
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020378f9154,0
1. c0t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /u04
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371ae3ef,0
2. c1t4d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /u02
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w21000020379c5e10,0
3. c1t5d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /u03
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w21000020375cca44,0

Do we have a built-in option for web based tool in Nexus 5548UP switches for management purpose?

I have purchased Nexus 5548UP switch, i want to know if we have a built-in option for web based tool to manage and configur it just as ASA have ASDM. If there is no such options then what are the options available that can be freely available and can be used to get performance monitoring done.
Message was edited by: Praveen Varun

DCNM (Data Center Network Manager) runs on a server (Windows, RHEL or Solaris) and can be used to manage Nexus devices. It's free for Nexus 1K through 5K devices (paid license required for Nexus 7K management).
http://www.cisco.com/en/US/products/ps9369/index.html
There is not a "built-in" management product like ASDM for ASA.

Nexus 5548UP for SAN Switch

We have purchased a Nexus 5548UP switch for our SAN environment. I've only configured it for jumbo frames and currently doing testing on the performance, as some say use jumbo frames while others say do not. My question is, and I know this is a loaded question but how do you guys go about configuring your SAN switches? What exactly are you configuring on it? Such as for performance tuning or the like. The reason I ask, is we have the switch and it's pretty much working, but I'd like to learn more about it and how to tune it and fully take advantage of the switch.

That is correct, between two Dell Optiplex workstations. We also tested between the server that will go into prod and an Optiplex, but once again the Optiplex could be the limiting factor. You think that could be it? Here's my config, so you know how it's setup right now.
version 5.2(1)N1(7)
hostname N5K
feature telnet
feature lldp
feature vtp
username admin password 5 $1$oZ1234567898765432123456/ role network-admin
banner motd #Nexus 5000 Switch
ip domain-lookup
policy-map type network-qos jumbo
class type network-qos class-default
mtu 9216
multicast-optimize
system qos
service-policy type network-qos jumbo
snmp-server user admin network-admin auth md5 0x422842c9d320064123456789fc703d20
priv d3264f23456789000c703d20 localizedkey
vrf context management
port-profile default max-ports 512
interface Ethernet1/1
flowcontrol receive on
flowcontrol send on
interface Ethernet1/2
interface Ethernet1/3
interface Ethernet1/4
interface Ethernet1/5
flowcontrol receive on
flowcontrol send on
interface Ethernet1/6
interface Ethernet1/7
interface Ethernet1/8
interface Ethernet1/9
flowcontrol receive on
flowcontrol send on
interface Ethernet1/10
interface Ethernet1/11
interface Ethernet1/12
interface Ethernet1/13
flowcontrol receive on
flowcontrol send on
interface Ethernet1/14
interface Ethernet1/15
interface Ethernet1/16
interface Ethernet1/17
interface Ethernet1/18
interface Ethernet1/19
interface Ethernet1/20
interface Ethernet1/21
interface Ethernet1/22
interface Ethernet1/23
interface Ethernet1/24
interface Ethernet1/25
interface Ethernet1/26
interface Ethernet1/27
interface Ethernet1/28
interface Ethernet1/29
interface Ethernet1/30
interface Ethernet1/31
interface Ethernet1/32
interface mgmt0
ip address 11.11.11.11/24
line console
exec-timeout 720
line vty
boot kickstart bootflash:/n5000-uk9-kickstart.5.2.1.N1.7.bin
boot system bootflash:/n5000-uk9.5.2.1.N1.7.bin

Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)

Hi, we're currently have Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)
It's not listed as affected version:
Known Affected Releases:
(5)
5.2(1)N1(8a)
6.0(2)N2(5)
7.0(3)N1(0.125)
7.0(4)N1(1)
7.1(0)N1(0.349)
The Known Fixed Releases as follow:
Known Fixed Releases:
(7)
6.0(2)N2(4.3)
6.0(2)N2(5a)
7.0(1)ZN(0.615)
7.0(5)N1(0.173)
7.0(5)N1(1)
7.1(0)N1(0.371)
7.1(0)N1(1)
Do we need to update to the latest releases?
If yes, which version of the known fixed release is best suit our current version
Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)
Thanks.

I had the same question, so I opened a TAC case to find the right software version. I was told that the software listed as available on the bug report were custom NX-OS builds and that there are no patched versions available for the 5548p. The support engineer also said that the Nexus 5k upgrades were not expected until November or December. The best advice I could get was to subscribe to the bug report and wait to be notified of an available upgrade.

Cisco Nexus 5548UP connecting to HP P4330 StoreVirtual over iScsi

Hi,
I need some advice when it comes to how to setup a port-channel between Nexus 5548UP and a HP StoreVirtual 4330 device. The idea is to use 2 10 GB ports in a port-channel group and this far I've this on the port-channel group;
interface port-channel1002
priority-flow-control mode off
switchport access vlan 400
load-interval counter 2 30
load-interval counter 3 300
What about priority-flow-control, any needs to change anything here? Any other things that needs to be considered when using iScsi?
Much appreciated!
Tony Lewis

Hi Tony,
You do not have to worry about PFC. Priority-Flow-Control is something which is related to FCOE or DCBX protocol. With iSCSI as this is a TCP traffic, you have to make sure that you have a proper QOS for the IP Subnet or VLAN that has your iSCSI hosts transmitting the data. As iSCSI rides over TCP this is the major issue that I have seen related to the valid QOS config for the traffic. There is not best practice for it but you have make sure that you added it to a class other than BE or Scavanger class.
Hope this helps.
Cheers,
-amit singh

Nexus 5548UP

Hi,
Just want to know, how many ports in Nexus 5548UP can be used for 10G connectivity?
Thanks,
Sridhar

Hi Sridhar,
At least 32 10G ports SFP+ up to 48:
"Cisco Nexus 5548P Switch
The Cisco Nexus 5548P Switch (Figure 1) is the first of the Cisco Nexus 5500 platform switches. It is a one-rack-unit (1RU) 10 Gigabit Ethernet and FCoE switch offering up to 960-Gbps throughput and up to 48 ports. The switch has 32 1/10-Gbps fixed SFP+ Ethernet and FCoE ports and one expansion slot."
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/data_sheet_c78-618603.html
Regards,
Gus Magno

Nexus 5548UP zone problems?

Hello all,
I can say I'm relatively new in storage and fcoe. I have installed two 5548UP ( version 5.2(1)N1(6) ) and two B22HP FEX using EvPC. I'm using this guide for configuration http://www.cisco.com/c/en/us/products/collateral/switches/nexus-b22-blade-fabric-extender/guide_c07-686089.html
The 5548UP are FC connected to Brocade 2498 B50 using NPV. Connection to Broceade is ok. On brocade side can see wwn's of FC ports. Also on 5548UP look OK
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
fc1/31 400 NP on up swl NP 8 --
fc1/32 400 NP on up swl NP 8 --
Normaly we need also wwn's from blade servers to transfer and see on brocade.
License info:
nexsw-01(config)# show license usage
Feature Ins Lic Status Expiry Date Comments
Count
FCOE_NPV_PKG No - Unused -
FM_SERVER_PKG No - Unused -
ENTERPRISE_PKG Yes - Unused Never -
FC_FEATURES_PKG Yes - In use Never -
VMFEX_FEATURE_PKG No - In use Grace 116D 22H
ENHANCED_LAYER2_PKG No - Unused -
LAN_BASE_SERVICES_PKG No - Unused -
LAN_ENTERPRISE_SERVICES_PKG No - Unused -
I've tried to create zones (by examle guide up) but cannot execute znoe command???!!!
nexsw-01(config)# zone ?
^
% Invalid command at '^' marker.
Can you please help me, do I need any extra license or what?
Thanks in advance,

To clarify
Are you running FCoE between blade and N5K and then classical FC between N5k and Brocade ?
There is a FC NPV and another one FCoE NPV; the 2 require a different license
Have you enabled feature FCoE and NPV ?
On the N5k
can you please show us (CCLI), the features, show npv status... and any available show npv command
Do you have a OS installed on the blade, and CNA configured ?
I think your configuration is Fig. 8-11 in
http://www.ciscopress.com/articles/article.asp?p=2030048&seqNum=4

Connecting many Brocade switches to Nexus 5548UP

Similar Messages

Maybe you are looking for