Download firmware to UCS PE Fabric Interconnect fails

I think because the Local Storage Information shows the bootflash partition, opt partition and workspace partition all have a size of 0MB.
How can I increase the size of the Local Storage in the UCS Platform Emulator?
Thanks

Hello,
the upgrade through CLI is too complicated compared with the same process done through the GUI. If you have access through CLI, can you tell me what is the version of firmware running on the FI?
Also, what is the specific error you receive when you try to connect through the GUI? Could provide an screenshot of it?
Rate ALL helpful answers
-Kenny

Similar Messages

Cisco UCS 6324 Fabric Interconnect Used as a FEX?

Hi,
Is it possible to use the Cisco UCS 6324 Fabric Interconnect as a FEX to uplink UCS 5108 Blade Chassis to Cisco UCS 6200 Series Fabric Interconnects? Thank you.

How does it work if I want to add a second 5108 to a pair of 6324's? Having the 6324's replace the IOM (FEX) modules is cool but would you need to buy IOM's for the second chassis and then use up either 4 x 10GB ports or the 1 x 40GB or would I need to purchase 2 more 6324's?
Thanks in advance.

Cisco UCS 6200 Fabric InterConnects Needed?

Currently looking to put Cisco UCS 5100 blades into our datacenter. Our core currently has a 7K with F2 48-Port blades with FCOE licenses. We currently have our ESXi servers terminating directly to the 7K for both 10G Ethernet and storage via FCOE. If we decide to replace our standalone rackmount servers with UCS blades, can we connect the blade chassis directly to the 7K, or are the 6200 fabric interconnects required? If so, what purpose do they serve. Thanks.

Yes, fabric interconnect is required for a UCS blade solution; it can aggregate a maximum of 20 chassis a 8 blades, or a total of 160 blades.
On the fabric interconnect runs UCS manager as a application, which allows you to do firmware management for the server farm (bios, I/O adaptor, CIMC,....); the concept of service profiles implements server abstraction and mobility across hardware.

UCS 6248 Fabric Interconnect loud fan RPM noise

Hello,
Our currently installed 6248 Fabric Interconnect pair are generating a loud FAN noise.
Is there any way to reduce theirs RPM? So then can be quieter? The server room have proper air conditioning.
Some logs as bellow:
FABRIC-A(nxos)# show environment fan detail
Fan:
Module Fan Airflow        Speed(%) Speed(RPM)
             Direction
1       1    Front-to-Back 60        15428
1       2    Front-to-Back 60        11065
1       3    Front-to-Back 60        14835
1       4    Front-to-Back 60        10997
2       1    Front-to-Back 60        15000
2       2    Front-to-Back 60        11134
2       3    Front-to-Back 60        14835
2       4    Front-to-Back 60        11065
Power Supply:
Module Airflow        Configured
        Direction      Speed (%)
1       Front-to-Back 60
2       Front-to-Back 60
FABRIC-A(nxos)#
FABRIC-A(nxos)#
FABRIC-A(nxos)# show environment
Fan:
Fan             Model                Hw         Status
Chassis-1       UCS-FAN-6248UP       --         ok
Chassis-2       UCS-FAN-6248UP       --         ok
PS-1            UCS-PSU-6248UP-AC    --         ok
PS-2            UCS-PSU-6248UP-AC    --         ok
Temperature
Module   Sensor     MajorThresh   MinorThres   CurTemp     Status
                    (Celsius)     (Celsius)    (Celsius)
1        Outlet     67            58           35          ok
Power Supply:
Voltage: 12 Volts
PS Model                Input Power       Power     Status
                         Type (Watts)     (Amp)
1   UCS-PSU-6248UP-AC    AC     780.00     65.00     ok
2   UCS-PSU-6248UP-AC    AC     780.00     65.00     ok
Mod Model                   Power     Power       Power     Power       Status
                            Requested Requested   Allocated Allocated
                            (Watts)   (Amp)       (Watts)   (Amp)
1    UCS-FI-6248UP-SUP      492.00    41.00       492.00    41.00       powered-up
3    UCS-FI-DL2             24.00     2.00        24.00     2.00        powered-up
Power Usage Summary:
Power Supply redundancy mode:                 Redundant
Power Supply redundancy operational mode:     Redundant
Total Power Capacity                             1560.00 W
Power reserved for Supervisor(s)                  492.00 W
Power currently used by Modules                    24.00 W
Total Power Available                            1044.00 W
FABRIC-A(nxos)#

UPDATE
I opened a TAC, then after several reviews of the LOGs and huge sh tech files, we concluded that all was normal. This loud noise is normal   and within in normal operational ranges.
However as the server room is not fully acoustics proof and located near production work desks, we managed to get a RMA for the fan modules for the version 2 modules which are MUCH quieter than V1 due new design.
I have upload both pictures for comparison of the designs.
Thank You!

Fabric Interconnect Fail over behavior expectations..

Dear Team,
We have 2 FI A and primary and B as subordinate in HA ready mode
Some configuration setting made in ESXi (2 VNic 1 in vlan 7 and other in Vlan 8,Vnic1-in FI A in vlan 7 connected and working vnic2-FI B in vlan8 is disconnected)and is working fine
Now we truned off A and B started the election process and we tried to make it as primary by "lead" "force" then it said its doing that
process by itself please wait and it got emerged as "primary"
Now on turning off FI A connectivity to this ESXi was lost as expected as Vnic2-FI B in vlan 8 is not connected,ok
So we connected the vnic2 which is in FI B in ESXi,since the network flow was allowed for only Vlan7, we had to make the vlan for vnic2 in FI B as vlan7 and all fine ,and connectivity came back up.( This Change was made in Service profile Network tab and selection the vnic properties and changing vlan after connecting to FI B)
Now we turned on the FI A and it took over from FI B as primary, and we found that the connectivity was again lost, When we examined we found that
the changes (change of vlan from 8 to 7) to vnic2 made in FI B was reverted to its initial state that was in FI A before it was turned off ie the vlan got changed to Vlan 8,we had to change that to vlan7 manually in FI A for the network connectivity to come up
So the Question is why the changes made to vlan for vnic2 in FI B was reverted to the config that was there in FI A before switching off?
Now its case of a vNIC so any other major config or Service profile is there a chance of that getting reverted?
Is there any thing that we have missed out in setting to achive the latest config (in FI B) only when the FI A takes over as primary from FI B?
Thanks and Regards
Jose

Release notes in 2.0(5a) showed
CSCua91672
The fcoe_mgr hap reset will no longer cause FI reboot.
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/OL_25363.html
I am really never on the Fiber Interconnects to execute any CLI commands. But a memory leak for some other reason would certainly be a possibility. The fact that its own High Availability process causes double reset in its own High Availability architecture is troubling.

Error: Failed to parse path in URl (Cisco UCS 6100 Series Fabric Interconnect)

I have to shut down parts of my network due to an electrical outage this weekend. I have a Cisco UCS 6100 Server Fabric Interconnect. I am trying to backup the configuration. This is the command I am using create backup tftp://*.24.1.88 full-state enabled. The error I receive is Error: failed to parse URI. Which I believe URI means URL.

Hi Parakiteiz,
Looks like the format is incorrect and you have an extra 't' on the tftp command you provided. Please take a look at the link below for configuration assistance.
Creating backup operaiton.
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/cli/config/guide/1-1-1/b_CLI_Config_Guide_1_1_1/CLI_Config_Guide_1_1_1_chapter38.html#task_4704260519853629974
Please let me know if this help

Failed Download Task in UCS

I have been attempting to download new UCS firmware version into my UCS Fabric Interconnect using FileZilla and I keep getting the error '550 File not found' see sreen capture below. What could be the issue??

from the filezilla log you are attempting to download 'F:ftproot/ucsb' from the FTP root directory and this is invalid.
Try leaving the path blank in the UCS, and placing the file in the root directory of the FTP server and entering only the filename and IP into the UCS.
Also TFTPd32 is much simpler if you don't need FTP, the only configuration possible in TFTPd32 is root directory and IP address.

UCS-Fabric Interconnect Replacement

Hello everybody,
I have a UCS domain with a failed Fabric Interconnect and i have to replace this Fabric. For me there is no action to do in the configuration of the new FI i just have to add it in the existing domain and give it the IP address, but i have a question about the firmware version. is the firmware automatically installing in the new Fabric or have i to install it manually ? the firmware version in my domain is 2.2(1b).
Thanks for the answer
Best Regards
François Fiocre

Hi Claudio
I assume you talk about 10G copper, not 1G copper;
and if 10G: CX-4 (Twinax) cables, or 10G Base-T ?
There is a 12-port 10GBASE-T module, but this is only supported on the Nexus 5596T so of no use on Nexus 5596UP switch, nor UCS FI.
Anyway, it is a not recommended to connect UCS FI Uplinks to a Nexus 22xx ? just think about the oversubscription ! you would like to have as much bandwidth Northbound as possible.

Failed:Error disabled - SFP vendor not supported on Fabric Interconnect 6248UP

We are connecting a FC-uplink on a Fabric Interconnect 6248UP to a MDS9124. On the Fabric Interconnect side we use a 8Gbps SFP (DSpSFP-FC8G-SW) on the MDS9124 side there is a 4 Gbps SFP.This should work when speed is at fixed speed 4 Gbps on both sides (I was told). When the SFP's and cabling is connected I get an error in the UCS manager on the FC-uplink port we are using:
Failed:Error disabled - SFP vendor not supported.
I cannot change the speed on the FC-Uplink ( I can only set user-label). The Fabric Interconnect is configured for FC on the last 8 ports and that is where the SFP for the storage is located (port 31).

I have a similar problem. I'm using port 1/41 and gets this output
show system firmware expand | head lines 10
UCSM:
   Running-Vers: 2.1(3a)
   Package-Vers: 2.1(3a)A
   Activate-Status: Ready
Catalog:
   Running-Vers: 2.1(3a)T
   Package-Vers: 2.1(3a)A
   Activate-Status: Ready
sh interface fc 1/41
fc1/41 is down (Error disabled - SFP vendor not supported)
   Hardware is Fibre Channel, SFP is Unknown(0)
   Port WWN is 20:29:00:2a:6a:7e:7b:00
   Admin port mode is F, trunk mode is off
   snmp link state traps are enabled
   Port vsan is 1
   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
show int fc 1/41 transceiver details
fc1/41 sfp is present but not supported
   name is CISCO-FINISAR
   part number is FTLX8571D3BCL-C2
   revision is A
   serial number is FNS17401NYG
   FC Transmitter type is Unknown(0)
   FC Transmitter supports Unknown(0) link length
   Transmission medium is Unknown(0)
   Supported speeds are - Min speed: -1 Mb/s, Max speed: -1 Mb/s
   Nominal bit rate is 10300 MBits/sec
   Link length supported for 50/125mm fiber is 80 m(s)
   Link length supported for 62.5/125mm fiber is 20 m(s)
   No tx fault, no rx loss, no sync exists, diagnostic monitoring type is 0x68
   SFP Diagnostics Information:
                                     Alarms                 Warnings
Is this a firmware problem?

Is there a way to see SAN luns from the UCS fabric interconnect.

Hello,
I have recently added a 3rd and 4th vHBA to a B440 running RHEL5.
Originally I had 2 vHBAs', and each created a path to 172 luns. (I was multipathed to 172 luns)
Now I have added two additional vHBA's and my SAN admin assures me he has mapped, zoned and masked all 172 luns to the 2 new vHBA's.
So, at this time I should have 4 paths to 172 luns....but I don't.
What I see is 4 paths to 71 luns.
I still see 2 paths to all 172 luns, but only see 4 paths on 71 of them.
Its almost like my SAN admin either mapped or masked only 71 of the 172 luns to my 3rd and 4th path.
Via the RHEL5 OS I have rescaned the FC paths, rebooted, done lsscsi, looked in the lowest level places for what devices are present on my FC channels, always I see 172 devices on the 2 original FC paths and 71 devices on the 2 new FC paths.
My question is....is there a way to see all devices (luns) accociated with an vHBA from the command line in the Fabric Interconnect?
My configuration is UCS w 2 FI's, using 8Gb FC connections to Cisco 9500 directors, to an EMC DMX4.
Thanks in advance,
Gene

wdey,
The link you supplied in your response is the answer.
You can look at the devices on the FC boot paths, but not while the OS is running.
I have a test server I could reeboot to try what you have in your document, and it does work.
Too bad Cisco could not create a linux util rpm that would allow looking down the fabric while running. Im quit sure emulex has this kind of util, called HBAanywhere...at least for solaris.
In any case, thanks for the link to your article, it was VERY good!
My problem with seeing a shorter list of luns on 2 of my FC paths may get solved this afternoon by a change my SAN admin is going to make.. If it does I will post the fix.

My IPhone is set up with an internet downloaded firmware of ios7 because my phone would not restore, the system has failed and I had to do a manual erase fro within the phone. My computer will not accept the phone because they say it's a "Developer?"

My IPhone is set up with an internet downloaded firmware of ios7 because my phone would not restore, the system has failed and I had to do a manual erase fro within the phone. My computer will not accept the phone because they say it's a "Developer?" Help. I cannot not even get passed the activation step on the computer or phone because it will not activate the device.

Hello buddyacw
You would have to restore the iPhone. Download the latest version of iTunes and then follow the steps in the article below to get it working again.
iOS: Unable to update or restore
http://support.apple.com/kb/HT1808
Thanks for using Apple Support Communities.
Regards,
-Norm G.

UCS Fabric Interconnect Stuck on Loader

Hi,
I've UCS with 2 Fabric interconnect, today one of FI not working and from Console its boot but not respond to Ctrl+J or Crtl+Shft+R then Hung on "Loader>" ?
Any suggest Please

Hi Balhomaish,
for this particular issue I would recommend you to call cisco TAC and open a case with them.

Use UCS Fabric Interconnect 6100 with Extension Module E0060 (6 FC Ports)

Hi Everybody,
I have problem in my Architecture !!! I THINK
I want to use Extension Module E0060 (6 FC Ports) for UCS Fabric Interconnect 6100 for interconnectiong my Storage Array ( 2 Controlers with 2 FC Ports by cont.) instead of use Nexus 5000 between FI 6100 and my Storage Array
I tried to find details or case study for this way but No thing find !!!!!!!!!!!!
I just find that th e best practices is to use Nexus 5000 but I have enough FC Ports with this Module ...... I THINK but I m not an Expert
Thanks for your help.

Thanks for your answer Michael,
But I really don't understand why I can't use the Module E0060 (6 FC Ports) in the FI 61xx instead of NEXUS 500 (I hope that's not commercial goal ) ????
As you now the hardware architecture of FI 61xx is the same that Nexus 5000, the difference is that 61xx have features added and UCS Manager embedded.
Now, If they have a features limited in 61xx like NPV or other things, I wil understand But until this moment I don't find Real ANswer in Cisco site of forum ( Al cisco documents mentionned that the best practices and the perfect design is to use 61xx and Nexus 5000 and MDS Switch between UCS and Storage Array ???????
I Hope that you understand my problem

Monitoring traffic between UCS fabric extenders and fabric interconnect?

What is the best way to monitor the traffic between UCS fabric extenders (chassis) and fabric interconnect? Specifically I am looking for parameters to keep an eye on to determine when we may need to move from 2 links per fabric extender to 4 to handle greater IO needs.
Thanks.
- Klaus

One way you could monitor usage is by looking at the interface stats just as you would for any switch uplink.
Connect to the Cluster CLI
connect NXOS
Look at the input/output rate of your Server Uplink interfaces.
In my example I'm using fixed ports 1 through 4 on my FI's connecting to the IOM of the Chassis.
UCS-A(nxos)# show int eth1/1-4 | include rate
30 seconds input rate 17114328 bits/sec, 1089 packets/sec
30 seconds output rate 8777736 bits/sec, 693 packets/sec
    input rate 5.07 Mbps, 198 pps; output rate 1.03 Mbps, 99 pps
30 seconds input rate 2376 bits/sec, 0 packets/sec
30 seconds output rate 1584 bits/sec, 2 packets/sec
    input rate 1.58 Kbps, 0 pps; output rate 1.58 Kbps, 3 pps
30 seconds input rate 2376 bits/sec, 0 packets/sec
30 seconds output rate 31680 bits/sec, 20 packets/sec
    input rate 1.58 Kbps, 0 pps; output rate 30.89 Kbps, 18 pps
30 seconds input rate 2376 bits/sec, 0 packets/sec
30 seconds output rate 1584 bits/sec, 1 packets/sec
    input rate 1.58 Kbps, 0 pps; output rate 1.58 Kbps, 3 pps
If you notice your two links pushing near 10G consistently, it might be time to add another 2 link.
Other than this you can use SNMP to log the stats and look based on daily/weekly/monthly usage.
Robert

Fabric Interconnect B, management services are unresponsive

Hi,
We have configured Call Home option in UCSM and we are getting below error from Call Home option since last Saturday. We have open TAC with Cisco to troubleshoot this error but as per TAC "The error is a transient error from which the fabric interconnects can automatically recover."
Below is the error messages we are getting
E-mail-1:
Subject:
System Notification from System-A - diagnostic:GOLD-major - 2011-12-27 17:54:09 GMT-00:00 Fabric Interconnect B, management services are unresponsive
Body Message:
System Name:System-A
Time of Event:2011-12-27 17:54:09 GMT-00:00
Event Description:Fabric Interconnect B, management services are unresponsive
Severity Level:6
E-mail-2:
Subject:
System Notification from System-A - diagnostic:GOLD-major - 2011-12-27 17:54:09 GMT-00:00 Fabric Interconnect B, management services are unresponsive
Body Message:
<?xml version="1.0" encoding="UTF-8" ?>
<soap-env:Envelope xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
<soap-env:Header>
<aml-session:Session xmlns:aml-session="http://www.cisco.com/2004/01/aml-session" soap-env:mustUnderstand="true" soap-env:role="http://www.w3.org/2003/05/soap-envelope/role/next">
<aml-session:To>http://tools.cisco.com/neddce/services/DDCEService</aml-session:To>
<aml-session:Path>
<aml-session:Via>http://www.cisco.com/appliance/uri</aml-session:Via>
</aml-session:Path>
<aml-session:From>http://www.cisco.com/appliance/uri</aml-session:From>
<aml-session:MessageId>1058:SSI1442BFRC:4EFA0641</aml-session:MessageId>
</aml-session:Session>
</soap-env:Header>
<soap-env:Body>
<aml-block:Block xmlns:aml-block="http://www.cisco.com/2004/01/aml-block">
<aml-block:Header>
<aml-block:Type>http://www.cisco.com/2005/05/callhome/diagnostic</aml-block:Type>
<aml-block:CreationDate>2011-12-27 17:54:09 GMT-00:00</aml-block:CreationDate>
<aml-block:Builder>
<aml-block:Name>UCS 6100 Series Fabric Interconnect</aml-block:Name>
<aml-block:Version>4.2(1)N1(1.43q)</aml-block:Version>
</aml-block:Builder>
<aml-block:BlockGroup>
<aml-block:GroupId>1059:Serial Number:4EFA0641</aml-block:GroupId>
<aml-block:Number>0</aml-block:Number>
<aml-block:IsLast>true</aml-block:IsLast>
<aml-block:IsPrimary>true</aml-block:IsPrimary>
<aml-block:WaitForPrimary>false</aml-block:WaitForPrimary>
</aml-block:BlockGroup>
<aml-block:Severity>6</aml-block:Severity>
</aml-block:Header>
<aml-block:Content>
<ch:CallHome xmlns:ch="http://www.cisco.com/2005/05/callhome" version="1.0">
<ch:EventTime>2011-12-27 17:54:09 GMT-00:00</ch:EventTime>
<ch:MessageDescription>Fabric Interconnect B, management services are unresponsive</ch:MessageDescription>
<ch:Event>
<ch:Type>diagnostic</ch:Type>
<ch:SubType>GOLD-major</ch:SubType>
<ch:Brand>Cisco</ch:Brand>
<ch:Series>UCS 6100 Series Fabric Interconnect</ch:Series>
</ch:Event>
<ch:CustomerData>
<ch:UserData>
<ch:Email>[email protected]</ch:Email>
</ch:UserData>
<ch:ContractData>
<ch:CustomerId>[email protected]</ch:CustomerId>
<ch:ContractId>ContractID</ch:ContractId>
<ch:DeviceId>N10-S6100@C@SSI1442BFRC</ch:DeviceId>
</ch:ContractData>
<ch:SystemInfo>
<ch:Name>System-A</ch:Name>
<ch:Contact>Name</ch:Contact>
<ch:ContactEmail>[email protected]</ch:ContactEmail>
<ch:ContactPhoneNumber>+00-0000000000</ch:ContactPhoneNumber>
<ch:StreetAddress>Office Address</ch:StreetAddress>
</ch:SystemInfo>
</ch:CustomerData>
<ch:Device>
<rme:Chassis xmlns:rme="http://www.cisco.com/rme/4.0">
<rme:Model>N10-S6100</rme:Model>
<rme:HardwareVersion>0.0</rme:HardwareVersion>
<rme:SerialNumber>SerialNumber</rme:SerialNumber>
</rme:Chassis>
</ch:Device>
</ch:CallHome>
</aml-block:Content>
<aml-block:Attachments>
<aml-block:Attachment type="inline">
<aml-block:Name>sam_content_file</aml-block:Name>
<aml-block:Data encoding="plain">
<![CDATA[
<faultInst
ack="no"
cause="management-services-unresponsive"
changeSet=""
code="F0452"
created="2011-12-27T23:24:09.681"
descr="Fabric Interconnect B, management services are unresponsive"
dn="sys/mgmt-entity-B/fault-F0452"
highestSeverity="critical"
id="2036245"
lastTransition="2011-12-27T23:24:09.681"
lc=""
occur="1"
origSeverity="critical"
prevSeverity="critical"
rule="mgmt-entity-management-services-unresponsive"
severity="critical"
status="created"
tags=""
type="management"/>]]>
</aml-block:Data>
</aml-block:Attachment>
</aml-block:Attachments>
</aml-block:Block>
</soap-env:Body>
</soap-env:Envelope>
We want to understand that what is the impact of this error and is there anything that we can do to prevent this error? Also want to know what might be the cause get this error?
Let me know if anything else is needed from my side
show-tech file uploaded.

Padma,
TAC Engineer sent below mail
Hi Amit,
I’ve checked through the show tech you’ve uploaded and have not found any indicators of errors for the error message you are seeing.
As I mentioned in the call, the error is a transient error from which the fabric interconnects can automatically recover from. The recommended action is to wait for a few (10-15min) to see if the error clears automatically. If the error does not clear then we will need to do further troubleshooting. This error on its own is not a cause for worry. As you have HA in your system the management services would have failed over the to the other fabric interconnect and would not affect your system performance.
We can leave the system under observation for a few days to see if other errors occur concurrently with this error.
I will upload show-tech logs here, find my reply below
Is the alert generated only for FI B or both FIs ->> Amit: Alert generated for FI-B only
Any change in cluster state corresponding to alert time stamp ->> Amit: Unfortunately when this error generating we are unable to see the cluster state because of timing. If you can guide / suggest from any other location I can find the state that will be helpful
Cluster physical link status ->> Amit: Cluster link is OK
Does FI have any core dumps ->> Amit: I don't have any idea about this. How can check this ?
Regards,
Amit Vyas

Download firmware to UCS PE Fabric Interconnect fails

Similar Messages

Maybe you are looking for