Adding a 5108 chassis

We purchased UCS (2 6120XP fabric interconnects and 2 5108 chassis with blades) a couple of years ago. We are just getting to the point of needing to add an additional chassis. I'm presuming adding the additional chassis is pretty straight forward. Plug the chassis into the fabric interconnects, allocate the a couple of the ports on the fixed modules to be Server ports, and then power the chassis on. Is there anything that I need to be aware of or could be a potential gotcha?

When adding a new chassis the firmware shipped with the IOMs may be different than what you're currently running. The IOMs will automatically download the matching fw version from the FI's - so just be patient once enabling the server ports for the new chassis and blade to discover. Could take up to 20mins (to pull upgrade image and reboot if necessary).
Other than that, ensure all IOM - FI links are acknowledged. Once the chassis is discovered you can re-ack the new Chassis just to be sure.
Regards,
Robert

Similar Messages

SNMP polling for 5108 Chassis

I'm attempting to set up SNMP statistics polling for the 5108 Chassis with 4 half width blade servers. I can get SNMP data from the 6120 Fabric Extender just fine such as IFs and such, but I don't see any OIDs corrisponding to the chassis.
Is there a separate host I should poll for the chassis, or perhaps a different community name?
I'm specifically looking to monitor power draw from the four Chassis PSUs, as well as the two FE PSUs.
root@sj-mon:~# snmpwalk -v 2c -c public ucs1 .1.3.6.1.4.1.9.9.117.1.1.1
SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.1.470 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.1.471 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.2.470 = STRING: "CentiAmps @ 12V"
SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.2.471 = STRING: "CentiAmps @ 12V"
SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.3.470 = INTEGER: 4538
SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.3.471 = INTEGER: 4538
SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.4.470 = INTEGER: 29
SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.4.471 = INTEGER: 29
Here is all I've been able to pull for the FE PSUs, and the 4538 value doesn't seem to have any correlation to what's being shown in the UCS Manager under Statistics.
Thanks!

There are no stats for the chassis.
You can only snmpget stats for the "NXOS" part of the Fabric Interconnect.
You can get snmptraps for all of UCS (go a google for UCS-MIB, and there's a doc explaining this on cisco.com - do a google for site:cisco.com ucs documentation roadmap).
At the end of the year I believe a full MIB will be available to do what you want.
If you want stats, use the XMLAPI.
Cheers
Steve

Adding new Blade into 5108 Chassis

Hi Guys,
               I am about to add a new Blade into the chassis which current having 7 running blades into it.There is also a default template profile ready to create new profile for new blades. Since this is the first time that i am going to add a new blade... I am looking for some guidance. So there is my plan:
1. Insert the new M3 Blade server into a chassis... Noted the chassis number;
2. Go to the profile template, and create profile from template;
3. Go to the new added blade and associate it with the profile create in steps two;
Blade should be ready to boot?
There is where i am not sure, the blade is diskless! we intended to boot from SAN... so where should i have a blade to look for ESXi for the insall? Should i mounted the ESXi image prior then use KVM to tell the server where to get ESXi image to boot?
Thanks,

Thank you guys for these great answer... Really appreciate it.
I have one more question though... I intent is to boot from SAN, the storage team has mentioned that i need to zone the LUNs, so the Blade can see it. Well i assume there is no different than zone the datastore for ESXi hosts, right? For instance:
fcalias name ESX1 vsan 1
    member pwwn 20:00:00:25:b5:b0:00:ff
zone name PCVNX_A5_ESX1 vsan 1
    member fcalias ESX1
    member fcalias PCVNX_A5
Then add the zone above to the zoneset. And lastly, re-activate the zoneset.
Now by reactivate the zoneset, will that affect traffic?
Thanks

SNMP OID for 5108 Chassis input and output Watts?

Anybody know these?
Craig

Craig,
OID for cucsEquipmentChassisStatsTable -- 1.3.6.1.4.1.9.9.719.1.15.10
UCS MIBs are available here
ftp://ftp.cisco.com/pub/mibs/supportlists/ucs/ucs-manager-supportlist.html
HTH
Padma

UCS Chassis I/O problems

: Anyone else having Cisco UCS 6140/5108 chassis problems that cause the fans to act up and the I/O card to have power and temp alarms ver1.3.0 even when the environmental conditions are OK?

FYI there are a couple of fixes in this release for these problems. I believe the problem you are describing is related to this, which is part of the release discussed.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl43716

New Chassis with 2204XP IOM & B200 M3 Servers

Hi,
We are going to install 2 more additional chassis in existing setup, below is the list of existing setup and new chassis details
Existing Setup Details:
2 x 6120XP Fabric Interconnect with 2.0(1t) firmware
2 x 5108 Chassis with 2 x 2201XP IOM and 8 x B200 M2 servers per chassis
New Chassis Details:
2 x 5108 Chassis with 2 x 2204XP IOM and 8 x B200 M3 servers per chassis
Just wanted to know that is there any issue / problem if we install different configuration IOM and Blade servers in existing setup? If answer is yes then why? And if answer is no then too why? Just want to understand how the things works if answer is no
-Amit

Hello Amit,
B200 M3 servers require a minimum UCS version of 2.0(2). Please upgrade prior to installing the new blades.
No problem mixing the newer & older IOMs on the same FI as they fully backwards compatible. Since the FIs are the 6100 model, the 2204 will not form port-channels on the fabric ports (IOM to FI). A 6200 would be required for that functionality.
The webinar given in February covers the hardware & software configuration differences for the new FIs, IOMs, mezz adapters.
https://supportforums.cisco.com/community/netpro/data-center/unified-computing?view=video
Matthew

Are UCS hardware upgrades service disruptive?

Hi Community,
Is fabric interconnect hardware upgrade from dual (clustered) 6120XP to dual 6248 service disruptive?
Is adding a new 5108 chassis to the existing UCS configuration with dual 6120XP service disruptive?

Thanks Kenny.
1). I have actually been using this document for my project, and I think I worked out a pretty good migration plan based on it, but there are some grey areas/questions, MARKED IN BOLD CAPS. Could you clarify them for me?
Step 1 Upgrade UCS firmware across all the devices to the same version - 2.1(1f). THE NEW 6248S CAN BE TEMPORARY CONFIGURED AS STANDALONE OR IN A CLUSTER FOR THE FIRMWARE UPGRADE, AND THEN THE CONFIGURATION SHOULD BE WIPED OUT AND THE FABRIC INTERCONNECTS POWERED OFF.
Step 2 Using either the UCS manager CLI or GUI, verify the state (subordinate or active) of the existing (production) fabric interconnects.
!!! Step 3 Back up the software configuration information and the UCS Manager software !!!
Step 4 Disable the server ports on the subordinate fabric interconnect – NEW or EXISTING? THIS STEP IS CONFUSING AND IT IS REFERENCED IN STEP 17.
Step 5 Power down the EXISTING subordinate fabric interconnect by unplugging it from the power source. If you are monitoring the upgrade using a KVM session, you may need to reconnect the KVM session when you power down the fabric interconnect.
THE NEW FABRIC INTERCONNECT(S) SHOULD BE POWERED OFF AT THIS POINT
Step 6 Disconnect the cables running from the chassis IO Modules to the subordinate fabric interconnect ports in slot 1 (the old EXISTING fabric interconnect).
Step 7 Connect these cables into the corresponding ports in slot 1 on one of the new Cisco UCS 6248 UP fabric interconnect, using the connection records to preserve the port mapping and the configured server pinning.
See Fabric Interconnect Port Connection Record, on page 7.
See Fabric Interconnect Upgrade Considerations, on page 1.
Step 8 Disconnect the L1/L2, M1 management, and Console cables on the old fabric interconnect. The ports for these connections are on the opposite side of the interconnect, so if your cables are just barely long enough to connect two rack-adjacent UCS 6120 interconnects you will probably need new cables.
Step 9 Connect the M1 management, and Console cables to the new Cisco UCS 6248 UP.
Step 10 Connect the L1/L2 cables that were disconnected to the new Cisco UCS 6248 UP. L1 connects to L1, L2 connects to L2.
Step 11 Disconnect the Ethernet or FC cables from slot 2 of the old fabric interconnect.
Step 12 Connect the Ethernet or FC cables to the corresponding ports in slot 2 of the new Cisco UCS 6248 UP. Some may go to slot 1, depending on the mappings planned out earlier in the process
I HAVE NO SLOT 2 ON THE NEW FABRIC INTERCONNECTS ON THE OLD ONES, SIX PORTS IN SLOT 2 ARE CONFIGURED AS FIBER CHANNEL PORTS. WILL I NEED TO MANUALLY CONFIGURE LAST SIX PORTS AS FC PORTS? IF YES, AT WHAT STEP IS THIS CONFIGURATION DONE, AND ARE THE FIBER CHANNEL CABLES SUPPOSED TO BE PLUGGED IN BEFORE OR AFTER THE PORTS ARE CONFIGURED AS FC PORTS?
Step 13 Connect the power to the new Cisco UCS 6248 UP, it will automatically boot and run POST tests.
Important: Directly connect the console cable to a terminal and observe the boot sequence. You should at some point see the Basic System Configuration Dialog, where you will configure the switch as a subordinate interconnect. - IS THIS THE WIZARD THAT RUNS ON EVERY UNCONFIGURED FABRIC INTERCONNECT WHEN YOU POWER IT ON, WHEN YOU HAVE TO GIVE IP, NAME, DNS, ETC.? CAN I USE THE SAME IP THAT WAS ON THE OLD FABRIC INTERCONNECT?
If you do not see this dialog, you either have different builds of software on your old primary and new subordinate, or the new subordinate has previously been part of a cluster and will need to have all configuration information wiped before it can be added to a cluster as a subordinate. In either case, immediately disconnect the L1 and L2 connections and complete the bringup as a standalone fabric interconnect, then correct the issue before proceeding further.
I AM NOT SURE IF THE NEXT STEP IS APPLICABLE TO ME AT ALL, AS I DO NOT HAVE N10-E0440, I HAVE N10-E0060. COULD YOU COMMENT ON THIS?
Step 14 (Optional) Remap UCS 6100 fabric interconnect FC ports 2/1 to 2/4 on a N10-E0440 expansion module or any slot 3 ports onto the new fabric interconnect expansion module.
a) Use UCS Manager to delete the ports on the subordinate fabric interconnect that you will need to move within the configuration - WHERER DO I DELETE THE PORTS - ON THE NEW ONE?
b) For each port you have just deleted, create new ports on either slot 1 or slot 2. These ports must use the same port type definitions as the old ports, but will use different port numbers.
c) For recently moved Ethernet server ports, reconfigure the associated service profile to use the new port number for the appropriate LAN pin group.
d) For recently moved uplink Ethernet ports, reconfigure the port channel settings to use the new ports.
e) For recently moved uplink FC ports, reconfigure the associated service profile SAN pin group to use the new ports.
f) Re-acknowledge chassis for blade servers and fabric extender for rack servers.
This will be disruptive to traffic, but is necessary in this specific scenario. DO I LOOSE CONNECTIVITY FOR THE ENTIRE CHASSIS, OR JUST ONE FABRIC?
Step 15 The new subordinate fabric interconnect will automatically synchronize the configuration and database/state information from the primary fabric interconnect. Synchronization between primary and subordinate fabric interconnects can take several minutes. The port configuration is copied from the subordinate switch to the new hardware.
Step 16 Verify that the data path is ready.
See Verifying that the Data Path is Ready.
Make sure all faults are resolved before proceeding.
a) Verify and if necessary reconfigure the SAN pin group for FC ports in the associated service profile.
b) Verify and if necessary reconfigure the LAN pin group for Ethernet ports in the associated service profile.
c) Verify and if necessary reconfigure the port channel for uplink Ethernet ports.
THE FOLLOWING STEP IS ALSO CONFUSING. IF IT IS TALKING ABOUT THE OLD SUBORDINATE FABRIC INTERCONNECT THAT IS BEING REPLACED, WHY DO WE NEED TO ENABLE THE SERVER PORTS ON IT, THERE IS NOTHING CONNECTED TO IT. IF IT IS TALKING ABOUT THE NEW ONE - 6248, THEN, IT MEANS THEY HAVE TO BE DISABLED IN STEP 4, BUT IT MAKES NO SENSE, BECAUSE THEY ARE NOT SUPPOSED TO HAVE ANY CONFIGURATION ON IT. CAN YOU CLARIFY?
Step 17 Enable the server ports that had been disabled in Step 4. -
a) If you have changed port mappings, you may need to re-acknowledge the chassis or rack server connected to the subordinate fabric interconnect. DOES IT APPLY TO ALL TYPES OF PORTS – FC, SERVER, UPLINK ETHERNET PORTS?
b) Verify and if necessary reconfigure Ethernet ports as server ports.
Step 18 Promote the subordinate fabric interconnect to active, and repeat the process on the second Cisco UCS 6248 UP. Cable the second new fabric interconnect identically to the first, and allow the reconfiguration done to be applied to the second new fabric interconnect as well. DOES THE SECOND NEW 6248 NEED TO BE OFF OR ON WHEN CABLING IT? DO I NEED TO GO THROUGH THE WIZARD AT THE POWER ON TO MAKE IT A PART OF THE CLUSTER?
See Forcing a Fabric Interconnect Failover.
2). Does CISCO have a document outlining the steps for adding a chassis?
Regards,
Maxim.

Win 2012 R2 virtual fiber channel

Hello,
I enabled virtual fiber channel adapters on the physical Win 2012 R2 node.
Now I would like to enable virtual fiber channel on the virtual machine. I shut downed VM and added two virtual fiber channel adapters. I turned on VM and fcinfo gives me information about them.
Need to mention that I'm using default Windows WWNs.
Now I would like to connect some LUNs from NetApp to VM. I've added WWNs of VM to NetApp but LUN doesn't appear in the VM.
My setup:
Cisco UCS 5108 chassis
FI6248 fabric interconnects
B200M3 blades
I don't have Nexus switches.
flogi shows connected VM fiber channel to the fabric interconnect.
INTERFACE VSAN FCID PORT NAME NODE NAME
vfc809 100 0x290201 c0:03:ff:0b:b5:9f:00:0a c0:03:ff:00:00:ff:ff:00
My question is how to setup fc zoning on the fabric interconnect that VMs could connect to the NetApp storage via FC.
Is there any guide how to setup FC zoning by Cisco best practices?
Thank you

Hi Aleksandras
Maybe the situation / problem is the following:
1) you have e.g. 2 FC initators which are Hyper-V host based (eg. vhba0 and vhba1).
2) in addition you have the FC initators of the virtual hba's of the VM's.
You have a direct attached storage, and zoning is done on the FI. However, this automatic zoning only happens with FC initiators defined in the vhba's of the service profile, 1) above
UCS is totally unaware of the OS, and therefore of virtual hba's of the VM's.
That's why you see the flogi of the VM virtual hba's but no corresponding zone.
Solution: connect your UCS via a FC switch to the storage subsystem, and the zoning can be done for the Hyper-V host, as well as the VM's.

How can I acquire data in a PCI DAQ board using a SCXI rack?

Hello.
I have an acquisition system that consists in:
· 3 PCI DAQ boards:
- PCI-MIO-16-E-1
- PCI-6052-E
- PCI-6034-E
· 3 cables to connect PCI boards and SCXI modules
· 1 SCXI chassis:
- SCXI-1001
· SCXI modules + terminal blocks:
- 4x SCXI_1121 + SCXI_1320 (for voltage analog inputs)
- 1x SCXI_1520 + SCXI_1314 (for strain gauges)
- 1x SCXI_1530 (for accelerometers)
I have been trying to acquire different signals (specially voltage signals that are easier to reproduce) but I haven't been able to do it. I can't read anything from MAX or LabView. I have tested the PCI boards with a SCB68 terminal block (without any SCXI component) and they work properly. Problems appear when I use the SCXI chassis and the SCXI modules. I don't know if there is a problem with the hardware or it is a wrong configuration.
I guess channels in the SCXI modules correspond to analog input channels in the PCI board they are connected to, but I don't know if I have to read data from analog input channels of the PCI boards or from SCXI channels that appear in MAX (I have tried both posibilities, but they don't seem to work).
I don't know if I have to use Differential, RSE or NRSE configuration. I have tried all of them. Sometimes I only read noise, sometimes signal is fixed in a limit value (maximum or minimum, it depends), sometimes it's fixed in a value near zero,... I have changed connections and configuration options so many times I can't exactly say when one thing or another happens.
I have tested only one PCI board with only a SCXI module in order to avoid interaction and confusion. Nothing.
I think I have tried changing almost every option in MAX, but it doesn't work.
I'm sure I'm missing something and solution is quite simple, but I can't find it.
Can anybody explain to me how to connect and configure my system to read any signal? I only need a few steps or highlights. Maybe some clues about what the problem can be.
Thanks!

I have several comments and suggestions:
A) Have you "added a device" in MAX and actually added the SCXI chassis? This step is necessary to get the chassis to work. Click on "add a device" and choose the 1001 chassis . Do this for one DAQ card and one module only initially. The Set Up wizard should walk you through the configuration. If you are unable to add a chassis within MAX, I suspect the chassis is not working correctly.
B) Once configured, you can examine the SCXI channels in MAX as follows:
1) Open the DAQ card in MAX and Open the Test Panels
2) For the SCXI channel to view, use the following convention OB0!sc(n)!md(m)!ch where the letter (n) corresponds to the chassis number in MAX (usually = 1), the letter (m) corresponds to the module number (slot) where the module is located in the chassis, and (ch) represents the channel(or channels) you wish to view. So presuming chassis ID=1, and a module in slot 1, and you wish to view channel 3, you would type the following in the channel field for the DAQ card channel to view:
OB0!sc1!md1!3 (note OB0!sc1!md1!3:6 will display channels 3 through 6)
All of the SCXI channels for a given DAQ card are multiplexed through channel 0 of the DAQ card, Channels 1 and up are not used, hence the initial three characters in the SCXI call refer to "On-Board Channel 0 (OB0)"
C) For the subsequent set up, it will be necessary to first add the additional modules to the chassis (when powered off). Then open MAX and update the chassis. (If you get an error then simply delete the chassis reference in MAX and add a new chassis). You will then be required to set the interface mode of each module as either parallel or multiplexed. In parallel mode, you associate a distinct module with a distinct DAQ card in the host PC. For those DAQ cards that will address multiple modules, you must first configure the modules to be in adjacent slots in the chassis and then assign the first module to the cabled DAQ card - then all of the modules assigned to that DAQ card should be configured in "multiplexed" mode.
D) Once the chassis has been properly configured, you can click on each module and set the gains, filters, and terminal block types.
I hope that this helps to get you started.

Ask the Expert: Technical Discussion on UCS-Mini platform

Welcome to the Cisco Support Community Ask the Expert conversation.
Ask your technical questions on UCS-Mini platform.
The Discussion/Q&A is from November 24th through December 5th, 2014
Cisco UCS, originally designed for the data center, is now optimized for branch and remote offices, point-of-sale, and smaller IT environments with Cisco UCS Mini. UCS Mini is for customers who need fewer servers (expandable to 15 servers) but still want the robust management capabilities provided by UCS Manager. UCS 6324 Fabric Interconnect is main component which makes this solution possible on UCS 5108 Chassis with B200 M3 Blade Servers
This solution delivers servers, storage, and 10 Gigabit networking in an easy-to-deploy, compact form factor.
Vishal Mehta is a customer support engineer for Cisco’s Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in the TAC for the past 3 years with a primary focus on data center technologies such as Cisco Nexus® 5000, Cisco UCS, Cisco Nexus 1000V, and virtualization. He presented at Cisco Live in Orlando 2013, Milan 2014, and San Francisco 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/Switching, Service Provider & Data Center.
Rosalind Lee is customer support engineer specializing in Unified Computing System (UCS) blade servers including B series, C series, and E series. Rosalind holds a bachelor’s degree from UC Berkeley in Electrical Engineering and Computer Science and is currently pursuing her Masters of Information and Data Science at UC Berkeley.
Please use the rating system to let the experts know if you have received an adequate response.
Remember that you can continue the conversation in Data Center under the sub-community Unified Computing discussion forum shortly after the event. This event lasts through Dec 5th, 2014. Visit this forum often to view responses to your questions and the questions of other community members.

Hello Wilson,
This series is focused to answer any queries related with UCS-Mini deployments
We are not doing webinar, however below is detailed UCS-Mini session done by Product Manager on Google Hangout+
https://www.youtube.com/watch?v=gRVhLGsH8oI
Thanks,
Rosalind

W520 battery died after 6.5 months. Not a recalled unit

Is there a way to resurrect a dead battery that failed way too soon? Seems it's the chip that has the problem.
I bought a second battery from Amazon to "back up" my original battery sent in the machine at purchase late October 2011. I have a 427637U that has had an mSATA and SSD 256 added to the chassis. Spinning HD in the optical bay. Usual stuff, right? I knew that there was only a chance that it was really new -- as advertised. All seemed to go well with this new battery but about a month ago it seemed to stop charging at 49% and then it actually would not power the computer a little while ago.
I ran the battery recall ID software and it returns a "product not covered" message. I do have Amazon helping me get something back from the seller of the second battery.
I ran the Lenovo Power Manager software "battery reset" routine but no help. The Power Manager says there's a battery error and confirms that it will not power the laptop. The stats are not at zero for voltage, etc., though.
I might have made this happen because once when the laptop was on AC and I took out the battery to swap to the other unit -- I noticed a real hiccup in the notifications area. I wish I could remeber exactly what I saw.
I hope Monday brings word the retailer willl swap it out, but I doubt it. I hope someone here has an idea (I *did* search a bunch of different query strings...)
Thanks in advance for any suggestions.
Jonathan7007
4276-37U -- W520. Still have an X61t. First laptop in my house was an Osborne! Now that was a cool computer. (...for its time!)
Solved!
Go to Solution.

This was sold as a Lenovo. It had the right labels, tags, etc., although those can be counterfitted. I looke closely at the typography, etc. Further, I looked at the numbers when I first received the battery and those looked OK although I didn't create a screenshot, which in retrospect I wish I had.
I am waiting for a reply from the seller and I will report back what they say. An Amazon rep promised that Amazon would want the seller to give me some kind of compensation. How much clout that has with the seller remains to be seen.
Thanks for replies. I guess no one knows a way to wake up the battery through a software frontal lobotomy on the embedded chip. My intuition says this is the issue. Disclaimer: I am not a registered Pyschic.
jonathan7007
4276-37U -- W520. Still have an X61t. First laptop in my house was an Osborne! Now that was a cool computer. (...for its time!)

Copying data to a SAN attached to UCS

Hi Folks,
We have a 2 5108 chassis with 3 B200 blades each and 2 fabric interconnect 6248. This UCS connects to a hitachi storage array. The virtual machines configured use VMware.
I am not very familiar with the SAN aspect and I wanted an idea on how we can migrate 4TB of data to the Hitachi Storage array . The external storage device which consists of the 4TB of data has a USB connection but the UCS system does not.
Can you give some options as to how this is normally done or can be done? Other than the USB.
Thanks

Is your Hitachi array connected directly to UCS, or via a SAN, and if yes, what kind of SAN (Brocade, Cisco) ?
One can connect a dongle (KVM local I/O cable) to any blade, and get 2 external USB connections:
The KVM local I/O cable ships with every UCS 5100 Series blade server chassis accessory kit. The KVM local I/O cable provides a connection into the server, providing a DB9 serial connector, a VGA connector for a monitor, and dual USB ports for a keyboard and mouse. With this cable, you can create a direct connection to the operating system and the BIOS running on the server.
I believe this could be misused to temporarly connect your storage for data transfer, although a very ugly solution.

How to connect a 6120XP to Cat3560 Uplink Eth Switch?

Hi guys,
I have a question the company has bought a 5108 Chassis,6 B-200 M2 blades and 2 6120XP for our test lab.But i need to know that how can i connect my 6120XPs to the Cat 3560 for uplink ethernet?
I tried to use that SFP GigPort on the 3560 but it didn't respond.I think i need to know what kind of SFP+ trancievers or which models do i have to use.
Thanks.
BR from Istanbul

The first 8 ports on the 6120 FI supports GE SFPs. Please see the following link Table 2:
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10276/data_sheet_c78-524724.html
Table 3 of the above link has all the supported GE SFPs. SFP's part number starts with GLC is supported on the 3560s.
HTH,
jerry

FCoE options for Cisco UCS and Compellent SAN

Hi,
We have a Dell Compellent SAN storage with iSCSI and FCoE module in pre-production environment.
It is connected to new Cisco UCS infrastructure (5108 Chassis with 2208IOM + B200 M2 Blades + 6248 Fabric Interconnect) via 10G iSCSI module (FCoE module isn't being used at th is moment).
I reviewed compatibility matrix on interconnect but Compellent (Dell) SAN is only supported on FI NXOS 1.3(1), 1.4(1) without using 6248 and 2208 IOM which is what we have. I'm sure some of you have similar hardware configuration as ours and I'd like to see if there's any supportive Cisco FC/FCoE deployment option for the Compellent. We're pretty tight on budget at this moment so purchasing couple of Nexus 5K switches or something equipvalent for such a small number of chassis (only only have one) is not a preferred option. If additional hardware acquisition is inevitable, what would be the most cost effective solution to be able to support FCoE implementation?
Thank you in advance for your help on this.

Unfortunatly there isn't really one - with direct attach storage there is still the requirement that an upstream MDS/N5k pushes the zoning to it. Without a MDS to push the zoning the system it's recommended for production.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html#concept_05717B723C2746E1A9F6AB3A3FFA2C72
Even if you had a MDS/N5K the 6248/2208's wouldn't support the Compellent SAN - see note 9.
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix8.pdf
That's not to say that it won't work, it's just that we haven't tested it and don't know what it will do and thus TAC cannot troubleshoot SAN errors on the UCS.
On the plus side iSCSI if setup correctly can be very solid and can give you a great amount of throughput - just make sure to configure the QoS correctly and if you need more throughput then just add some additional links

UCS direct attach to NetApp in Flexpod

Hello Experts,
We have a new project which is based on Flexpod design and needs a direct attach between the FI 6248 and NetAPP storage.(Without a Fabric Switch N5K or MDS)
We had concern if Cisco has validated this design.Or else if there is CVD(Cisco Validated Design) based on Direct attach of UCS with NetAPP storage.Also if there is/are any constraints / limitations that must be considered in such a direct attach design
Is there any document (CVD) by Cisco or NetApp which details the diagram/configuration steps and other relevant information for the direct attach between UCS FI and Netapp storage.
FYI: The architecture will be like this
2 FI6248
1 5108 Chassis
1 B200m2 and 1 b200m3 Blade
2 2104 IOM
No Fabric Switch between FI and NetApp storage.
An early response will be very much appreciated and a useful doc with details.

Thanks Abhinav and Matthew,
Now Since UCSM 2.1 supports direct-attached NetApp.So to validate the architecture I updated by UCSM to 2.1.1a and now it should support a direct attach NetApp with UCS System.
I have conncted ports 31 and 32 of both FI (FC Stoarge Port with required SFPs) to my NetApp Device.But problem I am facing is,it says Link failure or not-connected and is in Orange Colour.Any idea where am I wrong?
I dont want to use FCoE Traffic or NFS between FI and NetApp.I want to use the FC traffic between UCS and NetApp.Is it possible and if yes How?
=================================
(nxos)# show interface fc 1/31
fc1/31 is down (Link failure or not-connected)
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is 20:1f:54:7f:ee:a9:d9:40
    Admin port mode is F, trunk mode is off
    snmp link state traps are enabled
    Port vsan is 14
    Receive data field Size is 2112
    Beacon is turned off
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
        0 CRC, 0 unknown class
        0 too long, 0 too short
      0 frames output, 0 bytes
        0 discards, 0 errors
      0 input OLS, 0 LRR, 0 NOS, 0 loop inits
      0 output OLS, 0 LRR, 0 NOS, 0 loop inits
    last clearing of "show interface" counters never
====================================

Adding a 5108 chassis

Similar Messages

Maybe you are looking for