Connect UCS to Nexus

Hi,
I am adding UCS FI to our network, connect to a Nexus switch. our network has multiple isolate Vlans, and normal Vlans, that all need to be trunk to FI. On switch port, should I do normal trunk mode, or private-vlan trunk mode.
Thanks,

Hi
In general, all vlan's defined in a UCS domain are trunked on all Nortbound links, see
http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-manager/116095-configure-ucs-upstream-port-channel-00.html
However, there is also the concept of disjoint vlan's, see
http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/unified-computing/white_paper_c11-692008.html
Walter.

Similar Messages

Design question, UCS and Nexus 5k - FCP

Hi,
I need some advice from (Mainly a Nexus person); I have drawn and attached the proposed solution (below).
I am designing a solution with 3 UCS chassis, Nexus 5K and 2X NetApp 3240 (T1 and T2). FC will be used to access disk on the SAN. Also, Non UCS compute will need access to the T2 SAN only. (UCS will access T1 and T2). It is a requirement for this solution that non UCS devices do not connect to the same Nexus switches that the UCS chassis use.
UCS Compute:
the 3 X chassis will connect to 2 X 6296 FIs which will cross connect to the a 2 X Nexus 5K through a FC port channel, the Nexus 5Ks will be configured in NPIV mode to provide access to the SAN. FC from each Nexus 5K to the NetApp controllers will be provided through a total of 4 X FC Port Channels (2 FC member ports per PC) from each nexus 5K one going to controller A and the other to controller B.
Non UCS compute:
These will connect directly through their HBAs to their own Nexus 5Ks and then to the T2 SAN, these will be zoned to never have access to the T1 SAN.
Questions:
1-      As the UCS compute will need to have access to the T1, what is the best way to connect the Nexus 5Ks on the LHS in the image below to the Nexus on the RHS (This should be FC connection).
2-      Can fiber channel be configured in a vPC domain as Ethernet? Is this a better way for this solution?
3-      Is FC better than FCoE for this solution? I hear FCoE is still not highly recommended.
4-      Each NetApp controller is only capable of pushing 20GBps max, this is why each port channel connecting to each controller is only 2 members. However, I’m connecting 4 port channel members from each Fabric Interconnect (6296) to each Nexus switch. Is this a waste? Remember that connectivity form each FI is also required to the T2 SAN.

Max,
What you are implementing is traditional FlexPod design with slight variations.
I recommend to look at FlexPod design zone for some additional material if you have not done so yet.
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns743/ns1050/landing_flexpod.html
To answer your questions:
1) FC and FCoE do not support vPC. If UCS needs to have access to T1, then there is no need to have ISL between sites. If UCS needs to have access to T1 and T2, then best option would be to set up VSAN trunking on N5K and UCS and configure vHBAs accordingly.
2) Both should work just fine. If you go with FCoE, then UCS would need to be on the latest version for multi-hop FCoE support.
3) If you only worried about storage throughput then yes, you will never utilize 40Gb PO if your source will be 20Gb PO. What are your projected peak and average loads on this network?

Connecting UCS 6248 FI to N5K-C5548UP

hi,
How do i connect UCS 6248 Fabric Interconnect to N5K-C5548UP? do i need to use FCoE or vPC as i will have multiple SAN connected (using FC) on FI.
Please suggest best possible solution where i have minimul cabling hedache & can optimise physicl ports on N5K.
Regards
Mahesh

Hi Mahesh,
vPC for FCoE uplink and / or unified uplinks is not supported at this time.
vPC only for pure ethernet uplinks still works the same way.
./Abhinav

Use GLC-T to connect ucs 6120 and 2960s (RJ45),.have SFP validation failed problem

hi,every .
i use GLC-T to connect ucs 6120 and cisco2960s (RJ45),.have sfp validation failed problem.
I have done speed to 1G then I am getting error " link not connected" even I have connected the nnetwork cable..

UCS6120-A(nxos)# show interface e1/7
Ethernet1/7 is down (SFP validation failed)
Hardware: 1000/10000 Ethernet, address: 0005.73d2.934e (bia 0005.73d2.934e)
Description: U: Uplink
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is trunk
auto-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 never
Last clearing of "show interface" counters never
30 seconds input rate 0 bits c, 0 bytes c, 0 packets c
30 seconds output rate 0 bits c, 0 bytes c, 0 packets c
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
RX
0 unicast packets 0 multicast packets 0 broadcast packets
0 input packets 0 bytes
--More--

Trouble seeing vhba from UCS on Nexus 5k

I have UCS > 6100(a/b)> nexus 5k (a/b) > emc vnx 5300. I have two vsans setup and my switch can see both ports on my vnx5300 with show flogi. However, my 5ks do not see the vhba on the ucs system. I have two vhba configured, one for fabric a and one for fabric b. As of now the nexus is connected to the 6100 as a port channel. Port-channel is configred as a trunk. Now this makes me think this is where the vsan communication is failing. Does the connection to the 6100 and nexus need to be something more than a simple trunk?
Dennis

Dennis,
I hope you're taking about Fiber Channel uplinks to your N5K and not Eth/FCoE (there's no multihop FCOE yet).
Assuming you have your 6100's with FC trunks to your N5Ks, and the N5K have "npiv" enabled, you should see the flogi from your Host vHBAs.
From the 6100 CLI you can also "connect nxos" and do "show npv flogi" which will show you FC sessions between your 6100 and N5K - which I think is where you problem is.
All your SAN connections would travel over the 6100 Fiber Channel module, up to the N5K Fiber Channel module, then to your array. You can still trunk and SAN port channel your FC uplinks. Just confirm this is what you've done and not using Ethernet Uplinks to your N5K expecting that to work.
Can you provide a diagram or detail the exact topology (Eth, FC etc)
Regards,
Robert

UCS to NEXUS

Hello,
Is it possible to connect a UCS solution to a pair of Nexus 5500 via native Ethernet as per the LAN communications and via native FC as per the SAN communications? Then I was planning to connect EMC VNX arrays to the Nexus 5500 via native FC and the core of his LAN via native Ethernet. In other words, I'm using Nexus 5500 as a consolidated LAN/SAN device, but WITHOUT using a consolidated protocol like FCoE. Is this design ok? Does it have any caveats or things to bear in mind?
Also, in this scenario would it add any benefit to connect the VNX arrays to the Nexus via FCoE instead of native FC?
Thanks,

That will work. We do it all the time in our lab. The 5500 replaces the need for an MDS or Brocade FC switch. It will work fine. You can use the 5500 as an NPIV switch or you can enable FC switching on the UCS box and do an E or TE port between the 5500 and UCS FIs. We also support F port channel trunk between the 5500 and UCS FI, so you can do just about every FC connection option between the Nexus and UCS boxes.
I can't comment on the VNX and it's FCOE capabilities.
louis

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

Conectar Cisco UCS via Nexus a NFS via IP

Tenemos una solución Cisco UCS la cual esta conectada a los Switches de Agregación Nexus y cuando se trata de conectar un o unos ServidoresVirtuales o SX a un NFS via IP no establece la conexión generando time-out, pero si la solución Cisco UCS es conectada a unos 6500 que se comportan como unas extensiones del Nexus, si se establece la conexión sin problemas.

Si efectivamente tenemos este problema, los UCS conectados a través del Nexus llegan a establecer la conexión a los NFS luego de varios intentos se establece, cuando se hace la consulta de información se vuelve extremadamente lenta , los nexus en nuestra red son los Switches Cabecera de Acceso manejan la capa 3 del Datacenter y se encuentran conectados a ellos 4 Switches 6513 vía vpc como extensiones en capa 2, la conexión de los Fabrics de los UCS conectados tambien via vpc hacia ambos nexus, cuando se tenían conectados los fabrics en los 6500 la conexión hacia los NFS se establecía normalmente, tuvimos que sacar los servidores que requieren este tipo de conexión a unos Blade de IBM que están conectados a los 6500

Connectivity Issue between Nexus 5548 to VNX 5300

Hi All,
I am doing a lab setup where i want to connect Nexus 5548 UP to VNX 5300 storage directly. The physical connectivity is established between switch and storage but On Nexus the status of the port shows "linkFailure". I tried matching the port mode (like Auto, F) and speed but the port always shows "linkFailure".
The connectivity from Nexus to VNX is FC.
Anyone can suggest the root cause or any troubleshooting steps.
Regards,
Abhilash

LinkFailure might be a GUI status.
show interface fcx/y might say,
Link failure or not connected
The physical layer link is not operational.
This means the switch is not detecting light, so the phyiscal layer is the cable and lasers (sfp's, HBAs or whatever adapter the VNX uses). It could mean you need to turn the interfaace up from the vnx side.

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.

Connecting UCS to IBM DS4700, FC zoning

I am trying to accomplish connecting my UCS to an older SAN that I have to migrate data off. I currently have a UCS system that is connected to an EMC VNX using 8G FC. The zoning for this is configured in my UCS. All works well with the connection to the VNX and I have dual active/active paths working. What I am trying to do is connect a second SAN to my UCS system, a IBM DS4700. This DS4700 currently has a Brocade FC Switch connected to it, which then connects to a IBM bladecenter chassis.
I configured a second VSAN for the IBM array and configured the port on my fabric interconnect with that VSAN. I went into the IBM array and I could see the UCS WWN for my HBA, so I connected it to my UCS. When I did this, I had an unexpected result. My VMWare ESXi host on the UCS could see all the datastores on the IBM DS4700 BUT lost connection to all the ones on the VNX. Also, on the IBM DS4700, all of my paths failed over to the controller that had the host connection from the UCS. I tried to fail them back over to the other controller but they wouldn't move until I disconnected the UCS from IBM DS4700. Once disconnected from the UCS, everything went back to normal on both sides.
Does any one have an idea on how I am setup wrong here? The ESX host on the UCS could see the datastores on the IBM so it is somewhat correct but it caused all sorts of problems.
Thanks in advance.

yes, zones are created on UCS.
Ok, so you don't have enough host ports to connect Controller A and Controller B to each FI. Since you are experiencing some odd failovers i would do this than. Since this is a migration effort and will not be a permanent configuration you can try this route ..connect both controllers to just one FI:
UCS FI FABRIC A:
IBM DS4700 Controller A - Host Port 2
IBM DS4700 Controller B - Host Port 2
this will ensure that UCS servers have access to both controllers so if a LUN on DS4700 happens to failover to another controller, UCS servers can still connect to it.
@dynamoxxx

Virtualized Lab Infrastructure - 3560G connecting to a Nexus 7000 - Help!

Hi all,
I've been struggling with the configuration for my small environment for a week or so now, and being a Cisco beginner, I'm worried about going down the wrong path, so I'm hoping someone on here would be able to help with my lab configuration.
As you can see from the graphic, I have been allocated VLANs 16-22 for my use, on the Nexus 7000. There are lots of other VLANs in use on the Nexus, by other groups, most of which are routable between one another. VLAN 99 is used for switch management, and VLAN 11, is where the Domain Controller, DHCP and Windows Deployment Server reside for the lab domain. Servers across different VLANs use this DC/DHCP/WDS set of servers. These VLANS route out to the internet successfully.
I have been allocated eth 3/26 on the Nexus, as my uplink connection to my own ToR 3560G. All of my servers, of which there are around 8 in total, are connected to the 3560. I have enabled IP routing on the 3560, and created VLANs 18-22, providing an IP on each. This config has been assigned to all 48 gigabit ports on the 3560 (using the commands in the graphic), and each Windows Server 2012 R2 Hyper-V host connects to the 3560 via 4 x 1GbE connections. On each Hyper-V host, the 4 x 1GbE ports are teamed, and a Hyper-V vSwitch is bound to that team. I then assign the VLAN ID at the vNIC level.
Routing between the VLANs is currently working fine - As a test, i can put 2 of the servers on different VLANs, each with their respective VLAN default gateway, and they can ping between one another.
My challenge is, I'm not quite sure what i need to do for the following:
1) How should I configure the uplink gi 0/52 on the 3560 to enable my VLANs to reach the internet?
2) How should I configure eth 3/26 on the Nexus?
3) I need to ensure that the 3560 is also on the management VLAN 99 so it can be managed successfully.
4) I do not want to route to VLAN 11, as i intend to have my own domain (DC/DNS/DHCP/WDS)
Any help or guidance you can provide would be much appreciated!
Thanks!
Matt

Hi again Jon,
OK, been battling with it a little more.
Here's the config for the 3560:
Current configuration : 11643 bytes
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
hostname CSP_DX_Cluster
no aaa new-model
vtp mode transparent
ip subnet-zero
ip routing
no file verify auto
spanning-tree mode pvst
spanning-tree extend system-id
vlan internal allocation policy ascending
vlan 16,18-23,99
interface GigabitEthernet0/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 18
switchport trunk allowed vlan 18-22
switchport mode trunk
spanning-tree portfast trunk
<same through interface GigabitEthernet0/48>
interface GigabitEthernet0/52
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 16,99
switchport mode trunk
interface Vlan1
no ip address
interface Vlan16
ip address 10.0.6.2 255.255.255.252
interface Vlan18
ip address 10.0.8.1 255.255.255.0
interface Vlan19
ip address 10.0.9.1 255.255.255.0
interface Vlan20
ip address 10.0.12.1 255.255.255.0
interface Vlan21
no ip address
interface Vlan22
ip address 10.0.14.1 255.255.255.0
interface Vlan99
ip address 10.0.99.87 255.255.255.0
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.6.1
ip http server
control-plane
l
end
At the Nexus end, the port connecting to the 3560 is configured as:
interface Ethernet3/26
description DX_3560_uplink
switchport
switchport mode trunk
switchport trunk allowed vlan 16,99
no shutdown
Now, the problem I'm currently having, is that on the 3560, things route fine, between VLANs. However, from on a server within one of the VLANs, say, 18, trying to ping the default gateway of the 3560 fails. I can ping 10.0.6.2 which is the 3560-end of VLAN 16, but i can't get over to 10.0.6.1 and beyond. I suspect, it's relating to what you said about "the only thing missing is you also need routes on the Nexus switch for the IP subnets on your 3560 and the next hop IP would be 10.0.6.2 ie the vlan 16 SVI IP on the 3560"
I suspect that, in layman's (my terms!) terms, the Nexus simply doesn't know about the networks 10.0.8.1 (VLAN 18), 10.0.9.1 (VLAN 19) and so on.
So, i need routes on my Nexus to fix this. The problem is, I'm not quite sure what that looks like.
Would it be:
ip route 10.0.8.0 255.255.255.0 10.0.6.2
ip route 10.0.9.0 255.255.255.0 10.0.6.2 and so on?
To give a bit of history, prior to me creating VLANs 18-22 on the 3560, all VLANs originally existing on the Nexus. Everything routed fine out to the internet, for all of the VLANs (with the same subnet settings that i have configured, i.e. 10.0.8.x for VLAN 18 etc), so i'm presuming once I get the Nexus to understand that the IP subnets live on the 3560, traffic should flow successfully to the internet.
Should.... :-)

Directly connect UCS C-series to External storage

Hi,
I have a customer that is looking for an entry level data centre solution.
I have speced up 2 UCS C240 servers (with 10GB or 8GB FC) and I was wondering whether we can attach directly to external storage from the servers for now and buy a switch in the future.
As replication of their database is an issue, they would like to use external storage. The customer is looking at an IBM V7000. in the following URL -
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix8.html the V7000 is compatible with the B-series but it's not listed under the C-series. Has anyone used the V7000 with the C-Series? Is there a better option for an entry level external storage array?
Any pointers or help would be much appreciated.
Cheers,
Georgia

Hello Georgia,
What is the HBA installed on the server ?
The matrix lists supported arrays only for Cisco CNA.
Padma

BB playbook does not connect to google Nexus one via bluetooth

I am not able to connect play book and nexusvone smartphone using bluetooth. Every thing is OK till they pair. After that connect option won't highlight. How to connect both via bluetooth.
Murali

Working now. Used the gear icon instead of the bridge icon under setup.

Configuring an MDS 9148 attached to a Nexus 5048 connected to a Nexus 4000

Hi,
I'm configuring a SAN fabric FC between an MDS 9148 and a Nexus 5048 which is carrying FCOE from a Nexus 4000 in a bladecenter with blade server's having Qlogic CNAs.
Naturally,I have portchannels between MDS 9K and Nexus 5K and between Nexus 5K and Nexus 4K.
The problem is that there is no communication between the servers and storage!
The switches configurations are attached.
I 'm wondering if it's mandatory to activate NPV?
Any other suggestions?
Best regards!
Meryem.

It is not mandatory to use NPV mode. One thing I see missing in your Nexus 5548 configuration are the FCOE
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/qos/502_n1_1/Cisco_Nexus_5000_Series_NX-OS_Quality_of_Service_Configuration_Guide_Rel_502_N1_1_chapter3.html#con_1116601
Configure the following and you should be fine
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

Connect UCS to Nexus

Similar Messages

Maybe you are looking for