Nexus switch for storage

we are currently evaluating solutions for our storage upgrade.
we required 10GbE connection from storage to our servers.
there are 2 proposals that uses nexus switch.
1 uses nexus 5548 while the other one uses 3524.
i understand that 5548 is of a higher grade than the 3524.
i have 7 dell servers that will be connected to the switch using 10GbE NIC.
which nexus switch is more suitable for my environment.
7 servers -> 2 10GbE iSCSI switch -> 1x iSCSI storage(20TB)

Well...you're on a Cisco forum, so we'd be remiss in not recommending Cisco gear.
The Nexus 5548UP is around 17k for the base model without any special layer 3 licenses.
http://www.softchoice.com/catalog/en-us/hubs-switches-cisco-nexus-5548up-switch-managed-N5K-C5548UP-FA-HV7684
If you don't use layer 3 on the Nexus (which I wouldn't), they've got pretty good port density for the cost. NXOS takes little bit of getting used to and, for us, the copper SFPs have been a royal pain in the ass, but otherwise, they're pretty solid devices.

Similar Messages

ACI-How are the new advancements in ACI helping the drawbacks in nexus switching?

ACI-How are the new advancements in ACI helping the drawbacks in nexus switching?

ACI is a paradigm shift in data centre designs.
According to this solution overview ACI is the next generation of Software Defined Networking:
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/guide-c07-731461.html
Having worked with Nexus switches for a couple of years now I haven't encountered any serious drawbacks with these devices.

Cisco Nexus 1000v Virtual Switch for Hyper-V Availability

Hi,
Does anyone have any information on the availability of the Cisco Nexus 1000v virtual switch for Hyper-V. Is it available to download from Cisco yet? If not when will it be released? Are there any Beta programs etc?
I can download the 1000v for VmWare but cannot find any downloads for the Hyper-V version.
Microsoft Partner

Any updates on the Cisco Nexus 1000v virtual switch for Hyper-V? Just checked on the Cisco site, however still only the download for VMware and no trace of any beta version. Also posted the same question at:
http://blogs.technet.com/b/schadinio/archive/2012/06/09/windows-server-2012-hyper-v-extensible-switch-cisco-nexus-1000v.aspx
"Hyper-V support isn't out yet. We are looking at a beta for Hyper-V starting at the end of February or the begining of March. "
-Ian @ Cisco Community
|| MCITP: EA, VA, EMA, Lync SA, makes a killer sandwich. ||

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

Configure Nexus 5548 for native FC

hi
does anyone have steps on how to configure n5k for native fc to a storage controller and then map that to an interface running fcoe to a fabric interconnect say 6200 ?
appreciate any pointers

I hope this helps. For integrating UCS in FC NPV mode, you need to enable NPIV on the N5k (feature NPIV)
Fiber Channel (FC) Ports on Nexus 5000
Cisco Nexus 5000 is a Cisco Data Center switch platform that supports conventional Ethernet, Storage Area Network (SAN) and Fiber Channel over Ethernet (FCoE). The switch platform has support for connection directly to native Fiber Channel (FC) SAN network with its FC ports. This is needed at least for now as most of customers' storages are still using FC or are behind FC network.
This post will look at specifically on how to enable FC ports on Nexus 5500 (Nexus 5548UP and Nexus 5596UP) when we need to connect and integrate to FC network. In addition to that, we will look at some of the rules or restrictions that are worth to note based on the current hardware implementation when allocating ports on the switch for FC.
Cisco Nexus 5548UP and Nexus 5596UP are Unified Fabric switches that have 32 and 48 Fixed SFP+ ports, respectively. This fixed or built-in ports are unified ports which means that each of the ports can be used for conventional Ethernet, FCoE or FC. Out of the box, all of the 32 or 48 ports are "Ethernet" port type. As the name implies, with this port type, the port are ready for us to be used as conventional Ethernet port or for FCoE. Remember that FCoE is basically transporting FC traffic over Ethernet, so we need "Ethernet" port type for FCoE.
In that case, what if we need to use some of the built-in ports for FC?
To use some of the ports as FC ports, we need to change the port type of the port(s) that we intent to use for FC connection. Here's an example of commands to change port type on the switch:
N5K(config)#slot 1
N5K(config-port)#port 41-48 type fc
N5K(config-port)#copy running-config startup-config
N5K(config-port)#Reload
As the above command example, we change ports 31 and 32 from the default "Ethernet" to "FC" type. Similarly, to convert back from FC to Ethernet port type:
N5K(config)#slot 1
N5K(config-port)#port 41-48 type ethernet
N5K(config-port)#copy running-config startup-config
N5K(config-port)#Reload
Note: Refer to this Cisco's Command Reference document for further detail of this command: http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/command/reference/layer2/n5k-l2_cmds_p.html#wp2326019
You might surprise that there's a reload command in the end? Yes, you need to reload the entire switch to convert port type. So...one of the important notes here is that, as much as possible, convert the ports before the switch is in production.
After the port type has been changed from Ethernet to FC, the FC port will not be enabled on the switch until FCOE feature is enabled:
N5K(config)#feature FCOE
C license checked out successfully
fc_plugin extracted successfully
FC plugin loaded successfully
FCoE manager enabled successfully
FC enabled on all modules successfully
Enabled FCoE QoS policies successfully
After that, we verify that the port type is changed successfully and the FC ports appear on the switch:
N5K# show interface brief
Interface Vsan   Admin Admin   Status          SFP    Oper Oper   Port
                  Mode   Trunk                          Mode Speed Channel
                         Mode                                 (Gbps)
fc1/41     1      auto   on      sfpAbsent        --     --           --
fc1/42     1      auto   on      sfpAbsent        --     --           --
fc1/43     1      auto   on      sfpAbsent        --     --           --
fc1/44     1      auto   on      sfpAbsent        --     --           --
fc1/45     1      auto   on      sfpAbsent        --     --           --
fc1/46     1      auto   on      sfpAbsent        --     --           --
fc1/47     1      auto   on      sfpAbsent        --     --           --
fc1/48     1      auto   on      sfpAbsent        --     --           --
Ethernet      VLAN    Type Mode   Status Reason                   Speed     Port
Interface                                                                    Ch #
Eth1/1        1       eth trunk down    SFP validation failed       10G(D) 22
Eth1/2        1       eth access down    SFP not inserted            10G(D) --
Eth1/3        1       eth trunk down    SFP validation failed       10G(D) 32
Eth1/4        1       eth access down    SFP not inserted            10G(D) --
Besides the fixed ports, each of the switch model have slot for expansion module for increasing the port density. The number of slot is 1 for Nexus 5548UP and 3 for 5596UP. For supporting FC, the following modules are available to choose from:
- Fibre Channel plus Ethernet module that provides eight Ethernet port and eight native Fibre Channel ports.
   The first 8 ports of this module is Ethernet port and the remaining 8 ports are FC ports. The location of Ethernet and FC ports are indicated with different colors.
http://3.bp.blogspot.com/-46A5Xu-iy3g/UALOGhdiW-I/AAAAAAAAAF4/DuhCP59VX54/s1600/Nexus+5000+-+Module2.PNG
- Unified port module that provides up to sixteen Ethernet ports OR up to sixteen native Fibre Channel ports
   This is unified port, similar to the fixed or built-in ports whereby it's up to us to use the ports either for Ethernet or FC. Probably you only want to use some of the ports or even the entire module for FC.
http://4.bp.blogspot.com/-f95sJ9tsntM/UALOPrUXNpI/AAAAAAAAAGA/M4VA-C2Yh3U/s1600/Nexus+5000+-+Module3.PNG

L3 Link for Storage Replication

Hi,
Has anyone experienced on provisioning L3 MPLS link for Storage Replication. I have two DC at different location and EMC Storage.
we will have 2 MPLS L3 Link between two DCs to replicate the data. We have 4 RPA at each side and 2 MPLS Link. but dont have idea how to connect all these things. I have Nexus 7k in new DC and 6509 in old DC.
If anyone has any idea how to provisioned this link, it would great help to me.

Hi Micky,
Such table doesn´t exist in standard SAP! You should try to accomplish this in a view!

VPC between server and nexus switches

Hi all,
I would like to ask following question:
We are using virtual portchannels to connect e.g. ESXi-Servers with trunks on two Nexus switches. When the switch "rz2sw1" has gone faulty, we expect that the trunk connections between switch rz2sw2 would still work. That's the reason why they are built. But they didn't as you can see in the screenshot (attaced) former mail.
Do you know what can be problem.. thank you

It appears that the peer-link was down. If the peer-link is down and the keep-alive is still up, the secondary device will shutdown all of it's VPC links to ensure dual active (split brain) is avoided.
On a Nexus 7000, its recommended to use a front panel (data port) for the keep-alive instead of the management port. My assumption would be that you are using the MGMT0 for keep-alive and all front panel ports went off-line. If you use a front panel port for keep-alive and all line cards go off line on the primary, the secondary will take over as expected.

Connecting two Nexus switches with link

Hi,
I would like to connect two nexus switches with a link. Like one c5020 and one c5548p. How do i need to configure the ports at both the switches which will be joined with a fiber cable.
For MDS switches such links becomes E-port and fabric is merged. Not sure what happenes at the Nexus swictches. Any input will be appreciated.
Thanks,

Do you have fc modules in each nexus? If so, they act much like the MDS 9148. All ports should be default auto speed and auto switchport mode. Insert fc-sfp's and a regular multimode fc cable between them. Default mode is fc switch.
If that doesn't work, configure the mode on each port as E.
Once done, the fc switch portion of each nexus will merge.
Dave

MDS FC Blade Switch for IBM - Licensing

Hi,
our customer has got installed the 20-port-switch of the "Cisco MDS Fibre Channel Blade Switch for IBM BladeCenter". He wants to change some of the links now. For that reason he asked me:
- Is there a fix relationship between a port and a license?
- Can we use any port as long as we fall below the number of licenses?
Thanks in advance and regards
Matthias

Hello Matthias,
Cisco Fabric Switch for IBM BladeCenter (20 ports; 14 internal 2/4 Gbps, and 6 external full-rate ports) licenses for internal ports are allocated as the ports come up. Licenses for external ports are allocated sequentially.
Refer "On-Demand Port Licensing" section on CLI guide here :
http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3/ondport.html
Customer can select the specific external ports he wants licensed.
switch# config t
switch(config)# interface fc1/1
switch(config-if)#port-license acquire
Thanks,
Prateek

ADF Mobile: Client state access failed to establish a place for storage

Hi,
I hope it's fine to ask about adf mobile in this discussion room.
following problem:
While switching from two views/pages, both display a list, an error was thrown with the message: "Client state access failed establish a place for storage: null".
From the list view, I can navigate to see the details of the list-element. This error message wasn't shown up if I navigate from the details back to the list overview.
The application is developed using jdeveloper 11.1.2.4 and deployed on iPhone simulator 6.1 (xcode version 4.6.3).
There is no further information about this error in the log file. I'm not really sure if this message is really coming from the framework itself.
Has anyone probably ever heard about this message? It'll really helpful.
Thanks!

Hi.
I got this error message once. I was trying to copy the full selected row for a table in the view scope using a setPropertyListener. Something like this:
<amx:setPropertyListener from="#{row}" to="#{viewScope.visit}" type="swipeRight"/>
This will not work. The workaround is not to be lazy and simply copy the row attributes you need one by one.
Best Regards,
Frédéric Desbiens
ADF Product Manager
Twitter: @BlueberryCoder
blog: http://blogs.oracle.com/blueberry

Help on MP for Storage Devices

Hi, I'm starting to use the MP for Storage Devices (Cloud Management Marketplace | Solution Exchange) and it seems really well done. It get lots of information but it seems that the automatic discovery has some problem with object naming.
Just to do an example in my configuration I have mostly ESXi with a NetApp Storage and NFS mounts.
MP for SD seems to discover everything up to the switch ports but it name all my switch as "10" (it's the first octect of the their IP address) and all port 10_Ethernetx/y (the Ethernetx/y is correct but there's not the switch ip/name but the first octect of the ip address).
Does anyone know if there's some way to make it "name" the object in a better way (the full ip address will be a good solution).

No one have tested this and have any suggestion?

PoAP message on Nexus switch

Hi,
We are seeing this message continually coming from our new Nexus switch. Is this a problem?
how do we subdue this.
2013 Aug 13 04:05:34 switch %$ VDC-1 %$ %POAP-2-POAP_DHCP_DISCOVER_START: POAP DHCP Discover phase started
2013 Aug 13 04:05:34 switch %$ VDC-1 %$ %POAP-2-POAP_INFO: Abort Power On Auto Provisioning and continue with normal setup ?(yes/no)[n]:
2013 Aug 13 04:05:34 switch %$ VDC-1 %$ %POAP-2-POAP_FAILURE: POAP DHCP discover phase failed
2013 Aug 13 04:05:34 switch %$ VDC-1 %$ %POAP-2-POAP_INFO: Abort Power On Auto Provisioning and continue with normal setup ?(yes/no)[n]:
2013 Aug 13 04:05:39 switch %$ VDC-1 %$ %POAP-2-POAP_DHCP_DISCOVER_START: POAP DHCP Discover phase started
Thanks for all inputs.

Hi,
The message is caused by the Cisco PowerOn Auto Provisioning process. This is a feature that simplifies upgrading software and installing configuration files on new Cisco Nexus switches. This is not a problem assuming the switch has just been installed and has not yet been configured.
To stop the messages you simply press Y and return at the prompt "%POAP-2-POAP_INFO: Abort Power On Auto Provisioning and continue with normal setup ?(yes/no)[n]:"
Regards

WEB ROE - Convert previous (RPCROEK0) data for storage in ROE Workbench

Hi,
We are in processing of moving to NEW VERSION (WEB ROE) version of ROE, activated BADI as required for switching from old ROE to new WEB ROE.I'm trying to execute SPRO node - Convert previous (RPCROEK0) data for storage in ROE Workbench, but in live run I'm getting error "Error writing to table T5KR1" is encountered. Please let me know how this can be resolved and what is causing this error in the system.
Regards,
Babu

Look into note Note 635693 - ROE: Error in Conversion Report (RPCROEK0_CONVERSION).

Suggest me the Naxus Switch for our Datacenter

Dear Experts,
Please suggest me the Naxus switches for our Data Center.
Right now we are using cisco 4500 series switches.
Please give any link which shows benifits of Naxus switches.
Regards,

The product pages are a good start :
Nexus 7000:
http://www.cisco.com/en/US/products/ps9402/index.html
Nexus 5000:
http://www.cisco.com/en/US/products/ps9670/index.html
Nexus 2000:
http://www.cisco.com/en/US/products/ps10110/index.html
Nexus1000v:
http://www.cisco.com/en/US/products/ps9902/index.html
Look at white papers, data sheets.

Nexus-switches issues no arp-requests.

Hallo all,
I see a very strange behavior on my two nexus switches.
Both are Nexus 5548 with L3-daughter-cards. Both do l2 and l3-switching, ACL-filtering and other things. Furthermore I have a set of servers connected to both switches in a vPC-setup. All in all I do nothing special.
After reloading the primary switch (vpc-primary, root-bridge for all vlans and hsrp-active with preemption for all SVIs) the switche comes back online and after getting up all links and reconverging everthing the network breaks. After a lot of debugging and curses and connection tries and a few additional gray hairs later I have got it to work by pinging all ip-addresses from the switch that I have previously rebooted.
Later I do some tests to find out what was going wrong. I found out that if I clear the arp-cache I will get the same issue. Pinging from server A in one subnet to server B in another subnet doesn't lead to success, because the switch issues no arp-requests. To make it work just ping server B from the switch and all works fine. The switch does arp, the arp-table is updated and the pings from the server A will reach the server B.
Any ideas?
Regards
Thomas
^^°-°^^

I can post a extraction of the relevant config items.
   - --[ vpc-primary
cfs01# sh run
!Command: show running-config
!Time: Wed Nov 13 08:46:18 2013
version 5.2(1)N1(1b)
cfs eth distribute
vrf context CEPH
vrf context management
ip route 172.31.0.0/20 172.31.8.190
vlan 14
name 172.31.50.0/26_CN/NN/OSDs@DMZ
vlan 4080
name 172.31.48.64/26_NAS.Infrastr@DMZ
spanning-tree vlan 1-129,131-3967,4048-4093 priority 0
udld aggressive
vpc domain 1
role priority 1
peer-keepalive destination 172.31.8.179 source 172.31.8.178
peer-config-check-bypass
delay restore 150
peer-gateway
auto-recovery
ip arp synchronize
interface Vlan14
no shutdown
mtu 9216
description CN/NN/OSDs@DMZ
ip access-group acl-vl14-in in
vrf member CEPH
no ip redirects
ip address 172.31.50.61/26
no ip port-unreachable
hsrp version 2
hsrp 3
    authentication md5 key-string 3-14
    preempt delay minimum 30 reload 60
    priority 255
    ip 172.31.50.62
interface Vlan4080
no shutdown
mtu 9216
description NAS.Infrastr@DMZ
ip access-group acl-vl4080-in in
vrf member CEPH
no ip redirects
ip address 172.31.48.125/26
no ip port-unreachable
hsrp version 2
hsrp 3
    authentication md5 key-string 3-4080
    preempt delay minimum 30 reload 60
    priority 255
    ip 172.31.48.126
interface port-channel7
switchport mode trunk
switchport trunk native vlan 991
spanning-tree port type network
speed 10000
vpc peer-link
interface port-channel100
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14-19,991,4078-4080
speed 10000
vpc 100
interface port-channel102
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14,18,991,1299-1400
speed 10000
vpc 102
interface Ethernet1/1
no cdp enable
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14-19,991,4078-4080
channel-group 100 mode active
interface Ethernet1/3
no cdp enable
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14,18,991,1299-1400
channel-group 102 mode active
interface Ethernet1/29
description cfs02_Eth29
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/30
description cfs02_Eth30
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/31
description cfs02_Eth31
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/32
description cfs02_Eth32
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface mgmt0
description oam01_Gi0/19
ip address 172.31.8.178/26
cfs01#
   - --[ vpc-secondary
cfs02# sh run
!Command: show running-config
!Time: Wed Nov 13 08:46:05 2013
version 5.2(1)N1(1b)
cfs eth distribute
vrf context CEPH
vrf context management
ip route 172.31.0.0/20 172.31.8.190
vlan 14
name 172.31.50.0/26_CN/NN/OSDs@DMZ
vlan 4080
name 172.31.48.64/26_NAS.Infrastr@DMZ
spanning-tree vlan 1-129,131-3967,4048-4093 priority 4096
udld aggressive
vpc domain 1
role priority 2
peer-keepalive destination 172.31.8.178 source 172.31.8.179
peer-config-check-bypass
delay restore 150
peer-gateway
auto-recovery
ip arp synchronize
interface Vlan14
no shutdown
mtu 9216
description CN/NN/OSDs@DMZ
ip access-group acl-vl14-in in
vrf member CEPH
no ip redirects
ip address 172.31.50.60/26
no ip port-unreachable
hsrp version 2
hsrp 3
    authentication md5 key-string 3-14
    priority 254
    ip 172.31.50.62
interface Vlan4080
no shutdown
mtu 9216
description NAS.Infrastr@DMZ
ip access-group acl-vl4080-in in
vrf member CEPH
no ip redirects
ip address 172.31.48.124/26
no ip port-unreachable
hsrp version 2
hsrp 3
    authentication md5 key-string 3-4080
    priority 254
    ip 172.31.48.126
interface port-channel7
switchport mode trunk
switchport trunk native vlan 991
spanning-tree port type network
speed 10000
vpc peer-link
interface port-channel100
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14-19,991,4078-4080
speed 10000
vpc 100
interface port-channel102
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14,18,991,1299-1400
speed 10000
vpc 102
interface Ethernet1/1
no cdp enable
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14-19,991,4078-4080
channel-group 100 mode active
interface Ethernet1/3
no cdp enable
switchport mode trunk
switchport trunk native vlan 991
switchport trunk allowed vlan 2,14,18,991,1299-1400
channel-group 102 mode active
interface Ethernet1/29
description cfs01_Eth29
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/30
description cfs01_Eth30
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/31
description cfs01_Eth31
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface Ethernet1/32
description cfs01_Eth32
switchport mode trunk
switchport trunk native vlan 991
channel-group 7 mode active
interface mgmt0
description oam02_Gi0/19
ip address 172.31.8.179/26
cfs02#

Nexus switch for storage

Similar Messages

Maybe you are looking for