UCS C-Series VIC-1225 to Nexus 5000 setup

Hello,
I have two nexus 5000 setup with a vpc peer link. I also have an cisco c240 m3 server with a vic-1225 card that will be running esx 5.1. I also have some 4 2248 fabric extenders. I have been searching for some best practice information on how to best setup this equipment. The nexus equipment is already running, so its more about connecting the c240 and the vic-1225 to the nexus switches. I guess this is better to do rather than to connect to the fabric extenders in order to minmize hops?
All documention I have found involves setup/configuration etc with fabric interconnects which I dont have, and have been told that I do not need. Does anyone have any info on this? and can point me in the right direction to setup this correctly?
More specifically, how should I setup the vic-1225 card to the nexus? just create a regular vpc/port-channel to the nexuses? use lacp and set it to active?
Do I need to make any configuration changes on the vic card via the cimc on the c240 server to make this work?

Hello again, Im stuck
This is what I have done. I have created the vPC between my esx host and my two nexus 5000 switches, but it doesnt seem to come up:
S02# sh 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
4     Po4(SD)     Eth      LACP      Eth1/9(D)
vPC info:
S02# sh vpc 4
vPC status
id     Port        Status Consistency Reason                     Active vlans
4      Po4         down* success     success                    -
vPC config:
interface port-channel4
switchport mode trunk
switchport trunk allowed vlan 20,27,30,50,100,500-501
spanning-tree port type edge trunk
vpc 4
interface Ethernet1/9
switchport mode trunk
switchport trunk allowed vlan 20,27,30,50,100,500-501
spanning-tree port type edge trunk
channel-group 4 mode active
Im unsure what I must configure on the cisco 240M3(esx host) side to make this work. I only have the two default interfaces(eth0 and eth1) on the vic-1225 installed in the esx host, and both have the vlan mode is set to TRUNK.
Any ideas on what I am missing?
Message was edited by: HDA

Similar Messages

Cisco UCS C220 with VIC 1225

Hello,
We have Cisco UCS C220 M3 with VIC 1225 card installed. We connected only one 10G port of VIC 1225 to Nexus 5548UP switch. But I do not see this port on switch and in CIMI the status for this port shows Link Down. I wanted to to iSCSI boot from storage NetApp FAS2240 but since I don't see this port on my Nexus switch I am unable to do boot from NetApp. I tried both ports on VIC 1225 with same result. Please I need help in this matter. I know I am missing something very simple but can't figure this out.
Thanks,
Salman

Hi Kenny,
Here is the answers:
-What slot is this card installed in?
Mezzenine
-How many CPUs does the server have installed? (1 OR 2 CPUs can make the difference)
2x 2.90 GHz E5-2690/135W 8C/20MB Cache/DDR3 1600MHz
-Is the PCIe slot enabled in BIOS? << Let us know if you don't know how to check it from CIMC
I believe I did. Server>BIOS>BIOS advanced> PCIe (Let me know if this correct)
-Have you confirmed that the cable is good?
I have changed four cables. I am using SFP-H10GB-CU2M= Twinax cable.
-If the switch does not even see the port and CIMC says it is down, have you confirmed the switch port is properly configured?
CIMI says “Link Down” in VIC adapter General area. The switch interface config has only “switchport mode access” in default vlan 1.
-What is the firmware running on the server and the OS?
We upgraded the firmware with latest ucs-c220-huu-1.5.4-3.iso.
Let me share with you the complete BoM of the server:
UCSC-C220-M3S              1x UCS C220 M3 SFF w/o CPU mem HDD PCIe PSU w/ rail kit
UCS-CPU-E5-2690              2x 2.90 GHz E5-2690/135W 8C/20MB Cache/DDR3 1600MHz
UCS-MR-1X082RY-A    16x 8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v
CAB-9K10A-UK              2x Power Cord 250VAC 10A BS1363 Plug (13 A fuse) UK
UCSC-PCIE-CSC-02    1x           Cisco VIC 1225 Dual Port 10Gb SFP+ CNA
UCSC-PCIE-QSFP              1x Qlogic QLE8242-CU Dual Port 10 GbE FCoE CNA
UCSC-HS-C220M3              2x Heat Sink for UCS C220 M3 Rack Server
UCSC-RAIL1              1x Rail Kit for C220 C22 C24 rack servers

Twinax cable Nexus 5000

Hi,
According to this matrix the Nexus 5000 don't support 2meters Twinax SFP+ cable.
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps10110/data_sheet_c78-568589.html
Does anyone know why?
Thanks
Mattias

Thanks! I thought it should be resolved in a later release. And I didn't know 6.0 was released.
Do you also know when (or if it's already is) 2meters is supported in UCS Fabric Interconnect 6200?
http://www.cisco.com/en/US/docs/unified_computing/ucs/hw/6200/install/overview.html#wp1219488
And Cisco UCS C CNA VIC 1225
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10493/C220M3_SFF_SpecSheet.pdf
Page 27
Br,
Mattias

Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco® NX-OS.
The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response.
Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Gustavo
Please see my responses to your questions:
Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
Now for Data Plane we have two types of traffic – Unicast and Multicast.
The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
Similarity: For both products, loop avoidance is possible due to VSL bit
The VSL bit is set in the DBUS header internal to the Nexus.
It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
This mechanism is used for loop prevention within the chassis.
The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
Differences: In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
For more details please see below presentation:
https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
DCI Scenario: If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
Let us know if you have further questions.
Thanks,
Vishal

Nexus 5548 to UCS-C series network connectivity.

Hi There,
I am new to nexus world, mainly telecom side. I have a situation where a vendor like to deploy two Cisco UCS-C series servers for voice deployment.
Each UCS C240 M3 server has 4 NICs, 2 nics bonded 802.1q will connect to primary nexus 5k switch and other two bonded will connect to secondary nexus switch. we have a vPC domain and no FEXes so we have to connect these two servers directly to Nexus 5ks.
My question is it possible with teamed nics to coonect to 2 different nexus switches?
Can anyone guide me how can I achieve this design? see attached.
Thanks Much

It will also depend on the Server network settings such as OS, software switch flavor and NIC teaming option on the server.
x- if you run ESXi, then you may check out the following KB article.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004088
x- if you use N1Kv, then you can use LACP or static port-channeling, but be sure to make it consistent on the upstream switches.
hope it helps.
Michael

UCS C420M3 server with VIC 1225 , Cant see LOM ethernet ports

Hi Guyz,
we have C420M3 server with VIC 1225 connected on PCIe slot, with Fabric Interconnet.
After installing OS & drivers , vNICs created on VIC 1225 by service profile appear, but 4 gig ports on Server LOM dont appear.
Any Idea.?
Thank

If you integrate your rack server to UCSM, you will be able to use the LOM ports ONLY for Mgmt traffic, that is when you integrate the server in "Dual Wire Mode".
There is no need (unless you have one for an special reason I am not considering in this very moment) to use the LOM ports once you have integrated the server, precisely cause the VIC 1225 is a not a regular NIC card, nor a regular HBA, it is actually a CNA (Converged Network Adapter) which basically lets you do in one card, what you would do with two (meaning "what you would do with a separate NIC and HBA")
When you have a VIC card, you actually have the option to create up to 256 virtual interfaces (that's the capability of the hardware, always limited by the OS used, please keep that in mind), that is the reason why, after the server is integrated, you totally depend on the interfaces set in the Service Profile instead of the physical interfaces.
Find more info here:
http://www.cisco.com/c/en/us/products/interfaces-modules/unified-computing-system-adapters/models-comparison.html
Do you have a particular reason for using the LOM ports instead of creating 2 additional virtual interfaces in the Server's Service Profile?
-Kenny

Cisco VIC 1225 CNA Connectivity Options for 10G Upgrade

I've currently got an opportunity to upgrade a C220M3 UCS server from the standard Intel 1G LOM's to 10G and I'm looking at various ways to achieve this. This is for a standalone UCS server running VMware.
At the present time in this environment there isn't a 10G uplink switch port that can be used to connect a 10G UCS port to, so I'm looking at ways to at least complete the 10G hardware upgrade on the UCS side and have that component completed, while having a transition period of 1G connectivity in the short term.
It seems the VIC 1225 is the obvious choice for this, as price wise it's reasonable and it's fully featured, even if we only need the 10G ethernet (no FCoE in the short term).
One option I was looking at was to use the 1225T model, as this supports 10BaseT backwards compatible with 1000BaseT. However while it's an easy choice on the UCS, Cisco don't seem to have any 10G copper modules on the switch side, except in specific models in the Nexus family. This limits our switching options in the future (this rules out the use of 4500-X's or 3850s for example).
10G fibre is an option, as is Twinax, however this brings me to my next few questions.
1. It appears that based on the C220M3 spec sheet at http://www.cisco.com/c/dam/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/C220M3_SFF_SpecSheet.pdf (see Table 14) that the 1225 doesn't support Twinax. In fact it's the only NIC and CNA listed that apparently doesn't support it, which seems odd. Is this correct, and what is the reason behind this? Is this a hardware issue, a software issue or a documentation issue?
2. If Cisco Twinax is not an option, does the 1225 support 1G SFPs such as the GLC-SX-MM?
3. It looks like the X520 card for UCS might work, as I believe it can run with dual-rate 1G/10G SFPs. Has anyone tried this or have any comments on how those work with UCS?
Thanks,
Reuben

Reuben Farrelly
The 1225 (UCSC-PCIE-CSC-02) does supports twinax cables, the documentation has a type-o. If you look at the documentation for the c240 M3 that supports the same 1225 adapter, you will see that this card does supports the twinax cables (see attach screenshots). In the documentation it shows that the 1225T supports twinax but this card comes with 2 10GBASE-T ports so it won't support either twinax cables or SFPs.
Please let me know is this is helpful
C240 M3 Page (39)
http://www.cisco.com/c/dam/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/C240M3_SFF_SpecSheet.pdf
1225T (Table 2. Product Specifications )
http://www.cisco.com/c/en/us/products/collateral/interfaces-modules/ucs-virtual-interface-card-1225/data_sheet_c78-727604.html

CVP Virtualization on UCS B-Series

In the DocWiki document "Virtualization for Unified CVP" it is stated,
New B-Series deployments using Clustering Over the WAN must use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G.
I need to understand the reason behind the requirement. We are proposing a UCCE solution that includes CVP, based on UCS, but the client has an existing redudndant 6500 core switches but without VSS. The question is whether it is mandatory or just nice to have i.e. different etherchannels to each core or 1 to a VSS enabled core.

Hello Peter,
Does the blades have Cisco VIC CNA ?
There is known issue in PXE implementation which is tracked by following defect.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtu17983
Padma

C240 with VIC 1225 : enable Failover

Hi,
I have a C240M3 with a VIC 1225. I would want to enable failover.
In order that, i have to enable NIV mode. But it seems to me that i could not.
Why ????
how to solve this issue ???
C240-FCH1749V0VC /chassis/adapter # set
cli         CLI options
description Adapter description
fip-mode     Enable/disable FIP
vntag-mode   Enable/disable VNTAG
niv-mode not present.....
C240-FCH1749V0VC /chassis # show adapter 2 detail
PCI Slot 2:
   Product Name: UCS VIC 1225
   Serial Number: FCH17457ESH
   Product ID: UCSC-PCIE-CSC-02
   Adapter Hardware Revision: 6
   Current FW Version: 2.1(3a)
   VNTAG: Disabled
   FIP: Enabled
   Configuration Pending: no
   CIMC Management Enabled : yes
   VID: V03
   Vendor: Cisco Systems Inc
   Description:
   Bootloader Version: 2.1(3a)
   FW Image 1 Version: 2.1(3a)
   FW Image 1 State: RUNNING ACTIVATED
   FW Image 2 Version: 2.1(3a)
   FW Image 2 State: BACKUP INACTIVATED
   FW Update Status: Idle
   FW Update Error: No error
   FW Update Stage: No operation (0%)
   FW Update Overall Progress: 0%
C240-FCH1749V0VC /chassis #
any detail on NIV
My C240 is connect to Catalyst 3750.
Many thx.
Nicolas.

Hello Kenny,
My main question is « how to use and to configure failover on VIC 1225 ». I have already configure failover on B-serie but never on c-series
For more details (please see diagram in attach), my issue is that my C240 on DRP site (just 40 metres from main site) is connected to local switch (C3560) and to LAN core (C4506 on main site). This connection on 2 Catalyst devices seems to be a problem for vSphere :
i could see that : as soon as I connect the 2 ports, C240 lost connection to vCenter ; CIMC is still pinging.
I could read on ucsguru forum, someone has the same issue with 2 catalyst.
I do not have a lot of time for this deployment and installation. So, I told me to use actif/passif should be the faster way. If I connect only a cable (by shuting/ no shuting an interface on a catalyst), it works. In order to do that, automatically, I would want to implement failover on VIC1225
Any suggestion on my issue is welcome.
Many thanks.
Nicolas.

Is Cisco VIC 1225 supported on C210M2?

According to the spec-sheet, the only supported Cisco CNA would be P81E. P81E is EoS with migration diverted towards 1225, but when looking at the datasheet for 1225, it seems like only newer hardware is supported.
Can anyone confirm/deny if this would be a supported scenario or not?

Hello Marcus,
VIC 1225 is not supported on C210M2 Server.
Please find the below link for VIC 1225/1225T and attached screen shot for supported servers list:-
http://www.cisco.com/c/en/us/products/collateral/interfaces-modules/ucs-virtual-interface-card-1225/data_sheet_c78-708295.pdf
http://www.cisco.com/c/en/us/products/collateral/interfaces-modules/ucs-virtual-interface-card-1225/data_sheet_c78-727604.pdf
http://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/data_sheet_c78-587522.html
Hope it would helps you,Please mark as answered if you got your answer on this query.
Thanks,
Gaurav

C460-M2 with 2 VIC-1225, managed by UCSM

C460-M2 with 2 VIC-1225; all documents show only one VIC-1225 (which has to be in PCI slot nr.1) single wire managment with a UCS FI ?
Is this a limitation ? or must the second VIC-1225 be connected to a switch outside the FI ?
Walter.

I received the following answer
Good question Walter. The documentation is confusing. If running the C460 as part of a UCS integration, only 1 card is supported.Although the server supports 2 cards , slot 1 & 2 according to the specsheet. The datasheet states that upto 3 VIC can be supoprted int he server.
The Cisco CCW config tool allows you to configure 2 VIC1225 in the C460.
From the 460 spechseet.
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10493/ps11587/spec_sheet_c17-662220.pdf
Page 24
The C460 server accommodates the Cisco 1225 Virtual Interface card, which is supported only in slots 1 and 2. Note, however, that if the server is running UCSM, only slot 1 is supported for the VIC card.
■ The Cisco Card NIC mode is currently supported only with a Cisco 1225 VIC (UCSC-PCIE-CSC-02) that is installed in PCIe slot 1.
■ The C460 server accommodates the Cisco 1225 Virtual Interface card, which is supported only in slots 1 and 2. Note, however, that if the server is running UCSM, only slot 1 is supported for the VIC card.
From the datasheet
http://www.cisco.com/en/US/prod/collateral/modules/ps10277/ps12571/data_sheet_c78-708295.html
System Requirements
The Cisco UCS VIC 1225 is designed for use only on Cisco UCS C-Series Rack Servers. A single Cisco UCS VIC 1225 is supported on Cisco UCS C260 M2, C460 M2, C220 M3, C240 M3, C22 M3, and C24 M3 rack servers. Up to three Cisco UCS VIC 1225 cards are supported on these servers depending on the slot configuration.
Anyone at Cisco want to clarify the above?
Message was edited by: NABIL YAGHI

Issues configuring VIC 1225 in C240

I'm trying to configure a C240 server with the VIC 1225 installed.
First off, I'd like to know if it's even possible to use this without Fabric Interconnects or Nexus switches. Assume I'm just hooking them up to some regular 10GbE switches. I can change this but wante to have a better idea of my design decisions - not a lot of info regarding when the VIC 1225 can or should be used outside this context.'
Secondly, I am following the directions here:
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/cli/config/guide/1.4.1/b_Cisco_UCS_C-Series_CLI_Configuration_Guide_141_chapter_01001.html#task_3C31BD7B25BF4CF6839B7B12DE014482
I've verified that the VIC is installed in slot 1 visually as well as through the output below, but the output below isn't what I expected per the documentation. I'm not able to get into the scope of this adapter, and it's showing up in "show pci-adapters" and not "show adapters". It's like it's not even being recognized as a VIC.
Any help would be appreciated.
ucs-c240-m3 /chassis # scope adapter 1Error: Managed object does not exist, use show command to list valid targetsucs-c240-m3 /chassis # scope network-adapter 1Error: Managed object does not exist, use show command to list valid targetsucs-c240-m3 /chassis # scope pci-adapter 1% Incomplete commanducs-c240-m3 /chassis # scope pci-adapter 1 <CR> Press Enter keyucs-c240-m3 /chassis # scope adapter          Cisco Systems UCS Virtual Interface Card dimm-summary     Information common to all DIMMs fan-policy       Fan Policy parameters firmware         Get all Components Firmware flexflash        Cisco FlexFlash Controller gpu              Show GPU cards present in the system hdd              Host local hard disk drive network-adapter Show network adapters present in the system storageadapter   RAID Controllerucs-c240-m3 /chassis #

Matt,
The VIC 1225 is fully supported as a stand-alone card outside of UCSM and by default it runs in Classical Ethernet mode which means it's supported with any IEEE standard 10GE switch.
The VIC is not supported in Slot 1 in the C240, it is supported in Slot 2 or 5
(http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C240/install/replace.html#wp1337242).
Without being installed in the proper slots, the NC-SI connector at the end of the PCIe bus will not be conencted and the CIMC has no interface to to configure the card. Once you have installed it in a supported slot you should be able to scope chassis and show the adapter. Then scope to the adapter as shown below
ucs-c240-m3# scope chassis
ucs-c240-m3 /chassis # show adapter
PCI Slot Product Name   Serial Number Product ID     Vendor
2        UCS VIC 1225   FCH162974VP    UCSC-PCIE-C... Cisco Systems Inc
ucs-c240-m3 /chassis # scope adapter 2
ucs-c240-m3 /chassis/adapter #
Once you are able to see your VIC let me know if you have additional questions.
Steve McQuerry
UCS - Technical Marketing

Ask the Expert: Cisco UCS B-Series Latest Version New Features

Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about the Cisco UCS Manager 2.2(1) release, which delivers several important features and major enhancements in the fabric, compute, and operational areas. Some of these features include fabric scaling, VLANs, VIFs, IGMP groups, network endpoints, unidirectional link detection (UDLD) support, support for virtual machine queue (VMQ), direct connect C-Series to FI without FEX, direct KVM access, and several other features.
Teclus Dsouza is a customer support engineer from the Server Virtualization team at the Cisco Technical Assistance Center in Bangalore, India. He has over 15 years of total IT experience. He has worked across different technologies and a wide range of data center products. He is an expert in Cisco Nexus 1000V and Cisco UCS products. He has more than 6 years of experience on VMware virtualization products.
Chetan Parik is a customer support engineer from the Server Virtualization team at the Cisco Technical Assistance Center in Bangalore, India. He has seven years of total experience. He has worked on a wide range of Cisco data center products such as Cisco UCS and Cisco Nexus 1000V. He also has five years of experience on VMware virtualization products.
Remember to use the rating system to let Teclus and Chetan know if you have received an adequate response.
Because of the volume expected during this event, our experts might not be able to answer every question. Remember that you can continue the conversation in the Data Center community, under subcommunity Unified Computing, shortly after the event. This event lasts through May 9, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Jackson,
Yes its is possible. Connect the storage array to the fabric interconnects using two 10GB links per storage processor. Connect each SP to both fabric interconnects and configure the ports on the fabric interconnect as “Appliance” ports from UCSM
For more information on how to connect Netapp storage using other protocols like iSCSI or FCOE please check the url below.
http://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-6100-series-fabric-interconnects/whitepaper_c11-702584.html
Regards
Teclus Dsouza

VPC on Nexus 5000 with Catalyst 6500 (no VSS)

Hi, I'm pretty new on the Nexus and UCS world so I have some many questions I hope you can help on getting some answers.
The diagram below is the configuration we are looking to deploy, that way because we do not have VSS on the 6500 switches so we can not create only one Etherchannel to the 6500s.
Our blades inserted on the UCS chassis have INTEL dual port cards, so they do not support full failover.
Questions I have are.
- Is this my best deployment choice?
- vPC highly depend on the management interface on the Nexus 5000 for the keep alive peer monitoring, so what is going to happen if the vPC brakes due to:
     - one of the 6500 goes down
          - STP?
          - What is going to happend with the Etherchannels on the remaining 6500?
     - the Management interface goes down for any other reason
          - which one is going to be the primary NEXUS?
Below is the list of devices involved and the configuration for the Nexus 5000 and 65000.
Any help is appreciated.
Devices
·         2 Cisco Catalyst with two WS-SUP720-3B each (no VSS)
·         2 Cisco Nexus 5010
·         2 Cisco UCS 6120xp
·         2 UCS Chassis
     -    4 Cisco B200-M1 blades (2 each chassis)
          - Dual 10Gb Intel card (1 per blade)
vPC Configuration on Nexus 5000
TACSWN01
TACSWN02
feature vpc
vpc domain 5
reload restore
reload restore   delay 300
Peer-keepalive   destination 10.11.3.10
role priority 10
!--- Enables vPC, define vPC domain and peer   for keep alive
int ethernet 1/9-10
channel-group 50   mode active
!--- Put Interfaces on Po50
int port-channel 50
switchport mode   trunk
spanning-tree port   type network
vpc peer-link
!--- Po50 configured as Peer-Link for vPC
inter ethernet 1/17-18
description   UCS6120-A
switchport mode   trunk
channel-group 51   mode active
!--- Associates interfaces to Po51 connected   to UCS6120xp-A
int port-channel 51
swithport mode   trunk
vpc 51
spannig-tree port   type edge trunk
!--- Associates vPC 51 to Po51
inter ethernet 1/19-20
description   UCS6120-B
switchport mode   trunk
channel-group 52   mode active
!--- Associates interfaces to Po51 connected   to UCS6120xp-B
int port-channel 52
swithport mode   trunk
vpc 52
spannig-tree port   type edge trunk
!--- Associates vPC 52 to Po52
!----- CONFIGURATION for Connection to   Catalyst 6506
Int ethernet 1/1-3
description   Cat6506-01
switchport mode   trunk
channel-group 61   mode active
!--- Associate interfaces to Po61 connected   to Cat6506-01
Int port-channel 61
switchport mode   trunk
vpc 61
!--- Associates vPC 61 to Po61
Int ethernet 1/4-6
description   Cat6506-02
switchport mode   trunk
channel-group 62   mode active
!--- Associate interfaces to Po62 connected   to Cat6506-02
Int port-channel 62
switchport mode   trunk
vpc 62
!--- Associates vPC 62 to Po62
feature vpc
vpc domain 5
reload restore
reload restore   delay 300
Peer-keepalive   destination 10.11.3.9
role priority 20
!--- Enables vPC, define vPC domain and peer   for keep alive
int ethernet 1/9-10
channel-group 50   mode active
!--- Put Interfaces on Po50
int port-channel 50
switchport mode   trunk
spanning-tree port   type network
vpc peer-link
!--- Po50 configured as Peer-Link for vPC
inter ethernet 1/17-18
description   UCS6120-A
switchport mode   trunk
channel-group 51   mode active
!--- Associates interfaces to Po51 connected   to UCS6120xp-A
int port-channel 51
swithport mode   trunk
vpc 51
spannig-tree port   type edge trunk
!--- Associates vPC 51 to Po51
inter ethernet 1/19-20
description   UCS6120-B
switchport mode   trunk
channel-group 52   mode active
!--- Associates interfaces to Po51 connected   to UCS6120xp-B
int port-channel 52
swithport mode   trunk
vpc 52
spannig-tree port   type edge trunk
!--- Associates vPC 52 to Po52
!----- CONFIGURATION for Connection to   Catalyst 6506
Int ethernet 1/1-3
description   Cat6506-01
switchport mode   trunk
channel-group 61   mode active
!--- Associate interfaces to Po61 connected   to Cat6506-01
Int port-channel 61
switchport mode   trunk
vpc 61
!--- Associates vPC 61 to Po61
Int ethernet 1/4-6
description   Cat6506-02
switchport mode   trunk
channel-group 62   mode active
!--- Associate interfaces to Po62 connected   to Cat6506-02
Int port-channel 62
switchport mode   trunk
vpc 62
!--- Associates vPC 62 to Po62
vPC Verification
show vpc consistency-parameters
!--- show compatibility parameters
Show feature
!--- Use it to verify that vpc and lacp features are enabled.
show vpc brief
!--- Displays information about vPC Domain
Etherchannel configuration on TAC 6500s
TACSWC01
TACSWC02
interface range GigabitEthernet2/38 - 43
description   TACSWN01 (Po61 vPC61)
switchport
switchport trunk   encapsulation dot1q
switchport mode   trunk
no ip address
channel-group 61   mode active
interface range GigabitEthernet2/38 - 43
description   TACSWN02 (Po62 vPC62)
switchport
switchport trunk   encapsulation dot1q
switchport mode   trunk
no ip address
channel-group 62   mode active

ihernandez81,
Between the c1-r1 & c1-r2 there are no L2 links, ditto with d6-s1 & d6-s2. We did have a routed link just to allow orphan traffic.
All the c1r1 & c1-r2 HSRP communications ( we use GLBP as well ) go from c1-r1 to c1-r2 via the hosp-n5k-s1 & hosp-n5k-s2. Port channels 203 & 204 carry the exact same vlans.
The same is the case on the d6-s1 & d6-s2 sides except we converted them to a VSS cluster so we only have po203 with 4 *10 Gb links going to the 5Ks ( 2 from each VSS member to each 5K).
As you can tell what we were doing was extending VM vlans between 2 data centers prior to arrivals of 7010s and UCS chassis - which worked quite well.
If you got on any 5K you would see 2 port channels - 203 & 204 - going to each 6500, again when one pair went to VSS po204 went away.
I know, I know they are not the same things .... but if you view the 5Ks like a 3750 stack .... how would you hook up a 3750 stack from 2 6500s and if you did why would you run an L2 link between the 6500s ?
For us using 4 10G ports between 6509s took ports that were too expensive - we had 6704s - so use the 5Ks.
Our blocking link was on one of the links between site1 & site2. If we did not have wan connectivty there would have been no blocking or loops.
Caution .... if you go with 7Ks beware of the inability to do L2/L3 via VPCs.
better ?
one of the nice things about working with some of this stuff is as long as you maintain l2 connectivity if you are migrating things they tend to work, unless they really break

C460 Rack Server with two VIC 1225 - UCSM vNIC placement policy

I am trying to integrate C460 having 2 VIC 1225 cards with UCSM. The objective is to have 2 ethernet interfaces assigned to each VIC , one per FI.
vNIC 1 on VIC 1 - FI A failover to FI B
vNIC 2 on VIC 1 - FI B failover to FI A
vNIC 3 on VIC 2 - FI A failover to FI B
vNIC 4 on VIC 2 - FI B failover to FI A
I have created a service profile with 4 vNICs and assigned to C460. When the UCSM is configured to use the system default for vNIC/vHBA placement policy, all 4 vNICs are assigned to one VIC. When trying to place them manually with 2 on vCon1 and 2 on vCon2, I am seeing insufficient resource error. Both the VIC are recognized and UCSM server tab shows both of them as adapters.
Could someone please let me know how to achieve it?
Thanks!

The C460 has an integrated BCM 57711 which would also be recognized by the system. What's most likely happening is that the VIC 1225s are on vCon1 and vCon3 and the BCM card is on vCon2, since FF is not supported on the Broadcom adapter this would cause the association to fail. Try placing the manual placement with vCon1 and vCon3 and see if this clears up the issue.
Steve McQuerry
UCS - Technical Marketing

UCS C-Series VIC-1225 to Nexus 5000 setup

Similar Messages

Maybe you are looking for