UCS-FI-6248UP vs UCS-FI-6248UP-UPG

What is the difference between UCS-FI-6248UP and UCS-FI-6248UP-UPG? This question applies to many other UCS SKUs that have -UPG in them.

Hello Roman,
Both refer to same device and the PID difference is due to back end ordering tool through which the order get's processed.
HTH
Padma

Similar Messages

UCS 6248UP to UCS 2104XP AND UCS 6120XP to UCS 2208XP

Hi,
Is the UCS 6248UP compatible with the UCS 2104XP? AND
Is the UCS 6120XP compatible with the UCS 2208XP?
Thank you.

We have 2 x 6120XPs connected to one chassis with 2 x 2208 IOMs running the newest code, 2.2.3.
I have tried everything I can think of to create port channels between the FIs and the IOMs, but for some reason it appears that this cannot be done.
Can anyone confirm where the limitation is? I assume the 6120XPs as I have the same setup running port channels on the newer 6248s. Can anyone confirm with a possible link to capabilities?
Thanks,
Joe

Enhanced vpc with ucs 6248up

I got 2 6248up FI going to 2 N7k.
can i stup enhanced vpc using both FI as active uplinks or can only 1 be active at one time?
in ucsm, I am only seeing 1 pot channel on fabric A - with 4 uplinks 17-20
but on fabric B i see 1 port channel with no links

If your FI's are in endhost mode, they should act like access ports and not disable a connectino via STP. If that is happening maybe you are in Switch mode?
Craig

IPv6 Support on Cisco UCS 6248UP Device

Hi,
We are in process of implementing IPv6 in our production environment and wanted to know what needs to be done on UCS level to achive the same ?
We have Cisco 4948 and Nexus 3048 switches in our production environment above 6248 switch
Thanks,
Amit Vyas

Starting with 2.2.1b (El Capitan) IPv6 is supported (don't forget, Fabric Interconnect is a L2 switch, no L3 = routing)
IPv6 Management Support:
All 3 IP addresses (2 physical and 1 cluster) are now able to have IPv6 addresses as are the new CIMC “in band” addresses. Services such as NTP, DNS are also reachable via IPv6.

Connecting 6248up to a dcx

what are the steps to connect 2 FI 6248UP to a brocade dcx switch?
I have a total of 6 FC Ports shown but they are configured as uplink ports. Should they be FC storage ports instead?
I am not sure I need all 6 links to the dcx switch, so maybe 4 on each FI is ok? This is 8GB FC.
Also looking at the FI, I see that it is set for FC End-Host mode.
Should that be set to FC Switching mode?
thanks

Tony,
I don't know the exact command syntax for brocade, but essentially you can leave your FI's in FC end host most, and simply connect your FC uplinks from the FI to the brocade.
Since Brocades have no concept of VSANs you'll probably just use the default VSAN for all your FC connectivity. FC Storage ports are only for directly connecting a Storage Array to the FI. When using a fabric switch, you will use FC uplinks for your port mode.
You're probably right about not needing 6 x 8GB FC uplinks per fabric. This would depend on how many chassis you have connected to your FI's and how heavy of storage traffic their pushing, but I have seen 4 uplinks to each fabric be more than enough in most environments. With four uplinks each I would create a san port channel with all four links between the FI and brocade.
You can refer to the UCS config guides for the FI side, and brocade docs for their end. There's a similar thread on creating a san port channel between a brocade and Nexus 5000 in NPV mode here:
http://community.brocade.com/message/10201#10201
This is pretty much the same thing as your FI's in End Host mode.
Regards,
Robert

Cisco UCS 6248 and Dell EQ 6510x

We have a Dell EQ 6510x we have in production and we are about to power on a Cisco UCS B series chassis and a pair of 6248UP FIs. I'm planning to connect the 4 6510x 10G ports directly to the 6248 FIs and set them as Applicance Ports.
My question is would be be better to connect the 6510x Primary controller's two 10G ports directly to FI-A and the standby controller 10G ports directly to FI-B, or stagger them? Stagger meaning Primary Controller one10G to FI-A and one 10G to FI-B then Standby controller one 10G to FI-A and one10G to FI-B. Thanks!

Hello there,
In your design always keep in mind that both UCS FI are separate switches, they always will talk each other by the upstream switch. The best pratice is connect anything that have to talk with UCS domain in the upstream switch.
If there is no option to do so, you can connect through the FIs, using a appliance port. In your case I believe that connect stagger mode is the best option, but I'm not sure, depends how your vnics are configured and if your Dell EQ can do port-channel in active-standby mode.

Change ucs FI system name

Is it possible to change the already deployed system name on a paired cluster of 6248up fi's? Firmware is 2.2 3b...
Thanks

According to the config guide, this is possible.
F241-POD-1-UCS-1-A# scope system
F241-POD-1-UCS-1-A /system # set
F241-POD-1-UCS-1-A /system # set name niles
Warning: System name modification changes FC zone name and redeploys them non-disruptively
F241-POD-1-UCS-1-A /system* # commit-buffer
F241-POD-1-UCS-1-A /system #
niles-A /system #
niles-A /system # set name F241-POD-1-UCS-1
Warning: System name modification changes FC zone name and redeploys them non-disruptively
niles-A /system* # commit-buffer
F241-POD-1-UCS-1-A /system #
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/cli/config/guide/2-2/b_UCSM_CLI_Configuration_Guide_2_2/b_UCSM_CLI_Configuration_Guide_2_2_chapter_0101.html#task_4F5115C9511C4870A30B890BF0EEFC78
HTH,
/niles

6248UP Back-To-Front Airflow?

I understand that the port side of the 6248UP is considered the back. I was wondering if it is possible to get back-to-front airflow with the 6248UP. Essentially making the port side the front

Hello Peter,
Airflow is front to back and cannot be reversed in FI 6248.
http://www.cisco.com/en/US/docs/unified_computing/ucs/hw/6200-install-guide/6200_HIG_chapter_010.html#ID67
Can you please elaborate your requirement ?
Padma

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!

6248UP - Fabric Interconnect [id], HA functionality not ready

Hello
Having an HA issue with a FI cluster and have not able to find much info.
The error I get (in the subject) leads me the the below URL with 5 steps to check.
http://www.cisco.com/en/US/docs/unified_computing/ucs/ts/faults/reference/2.0/UCS_SEMs.html
Step 1 - Not sure how to check this - Any input on this ?
Step 2 - Have checked and even replaced the cables
Step 3 - Checked and confirmed under Equipments -> Rack-Mounts -> Fex ( 2 x N2K-C2232PP-10GE)
Step 4 - Checked and confirmed under Equipments -> Rack-Mounts -> Servers ( 4 x UCSC-C220-M3)
Step 5 - New installation no active contract as yet.
Anyone had similar issues, any assistance would be appreciated.
Thanks

Step 1
Management all setup with initial setup-script, confirmed in extract from running config below
scope fabric-interconnect a
     set out-of-band ip 172.16.1.4 netmask 255.255.255.0 gw 172.16.1.1
scope fabric-interconnect b
     set out-of-band ip 172.16.1.5 netmask 255.255.255.0 gw 172.16.1.1
scope system
     set virtual-ip 172.16.1.6
Double confirmed via show commands below
CTCPFIHA-A# scope fabric-interconnect a
CTCPFIHA-A /fabric-interconnect # show detail
Fabric Interconnect:
    ID: A
    Product Name: Cisco UCS 6248UP
    PID: UCS-FI-6248UP
    VID: V01
    Vendor: Cisco Systems, Inc.
    Serial (SN): SSI163308YF
    HW Revision: 0
    Total Memory (MB): 16232
    OOB IP Addr: 172.16.1.4
    OOB Gateway: 172.16.1.1
    OOB Netmask: 255.255.255.0
    Operability: Operable
    Thermal Status: Ok
    Current Task 1:
    Current Task 2:
CTCPFIHA-A /fabric-interconnect # scope fabric-interconnect b
CTCPFIHA-A /fabric-interconnect # show detail
Fabric Interconnect:
    ID: B
    Product Name: Cisco UCS 6248UP
    PID: UCS-FI-6248UP
    VID: V01
    Vendor: Cisco Systems, Inc.
    Serial (SN): SSI16330FY1
    HW Revision: 0
    Total Memory (MB): 16232
    OOB IP Addr: 172.16.1.5
    OOB Gateway: 172.16.1.1
    OOB Netmask: 255.255.255.0
    Operability: Operable
    Thermal Status: Ok
    Current Task 1:
    Current Task 2:
CTCPFIHA-A /fabric-interconnect # scope system
CTCPFIHA-A /system # show detail
Systems:
    Name: CTCPFIHA
    Mode: Cluster
    System IP Address: 172.16.1.6
    System Owner:
    System Site:
    Description for System:
Step 2
L1<>L1 L2<>L2 confirmed and new cables tried.

UCS FI and iSCSI Storage

We're getting ready to implement a UCS B Series. I have a question about the 6248UP FI. I've read and used the emulator for UCS Manager and noticed you can configure FI ports as Appliance ports for storage. Is this limited to a certain storage protocol or vendor? We use Dell EQ and plan to connect the EQ 6510X to it. Just wondering if that is supported and if upstream iSCSI traffic would be able to access the storage?
The 6248UPs will be uplinked to a pair of Catalyst 4506-E running VSS. We have a IBM blade chassis and the servers would need to be able to access the EQ6510X too. I'm assuming i just need to trunk the iSCSI VLAN to the 6248UP and the servers would have access?
Thanks!

Hi Cowetac,
Yes, not all storage arrays are supported by UCS, but your DELL Equalogic is supported. If you have any questions about other storage arrays compatibility, you can take a look at the UCS Storage Interoperability Matrix (See Link Below).
UCS Storage Interoperability Matrix (Table 10-2     UCS-B Storage Support Matrix)
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix8.html
I'm assuming i just need to trunk the iSCSI VLAN to the 6248UP and the servers would have access?
Depends, if you are going to use t an appliance port on UCS to connect directly to the storage, you can only use a single vlan.
if you are connecting via the Ethernet uplinks through a switch, then you would have to set your switchs port as a trunk.

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?

UCS Chassis 5108 both IOMs inaccessible

Dear forum users,
Problem description: Sometime our UCS Chassis 5108 and both IOM are suddenly INACCESSIBLE. This happens frequently (Happend 5 times in just a month)
Temporary Solution: To unplug and re-plug Chassis power cords twice, then the Chassis back to normal
Once the Chassis is inaccessible state, below are what we witness on the Chassis:
- All the blades LEDs on chassis-1 shows amber lit
- 8 ports on IOM A and IOM B shows NO LED lit (Not even amber lit)
- Sudden increased in Fan speed on chassis-1
- FI ports which connected to Chassis-1, shows NO LED it
- Please find attached (Chassis-1_Fault.jpg) Fault message on chassis-1
We had tried the following:
- Tried re-sit the uplink cable
- Tried replacing the uplink cable, the port is still down
- Reboot FI
- Decommission the chassis-1
- Recommission the chassis-1
Below is our setup environment:
- 2x UCS 6248UP
- 2x UCS 5108
- 4x UCS 2208XP (2 IOM per chassis)
- 2x UCS B200 M2
- 5x UCS B250 M2
- Firmware 2.0(3b)
- Each IOM has 4 Uplink cables connect to FI
- Chassis Discovery Policy
1. Action (4 Links)
2. Link Grouping Preference (Port Channel)
We hope, someone should have experience with the same problem or have some advise to be shared.
Please let me know should you need any further details of the problem or other information.
Look forward to a positive reply.

Hello Mohamed,
Please open a TAC service request with UCSM and Chassis tech support log files.
Also, include approximate date & time of the event.
Padma

Are these UCS numbers accurate?

A Cisco UCS 6296UP Fabric Interconnect costs $96,000 each. That includes hardware for 96-ports (the chassis plus 3 expansion modules) but enough licenses to only enable 18 of them.
Each additional license is $2,774 PER PORT. That means 78 x $2,774.
So, a Cisco UCS 6296UP Fabric Interconnect with all the licensing costs over $300,000 each.
Of course this is at list

Note that each 16-port module also comes with 8 port licenses, so a fully populated 6296UP actually has 42 port licenses included (18 base + 3 x 8 per module)
It's worth noting that this means that on a 6248UP or 6296UP it's actually cheaper to buy an expansion module and get the 8 included licenses than it is to pay for 6-8 port licences (and you get a 'free' 16 port module...)
In any case it means that it's not $300K for a fully populated 6296UP, even at list price.
If you do have a requirement for a fully populated 6296UP I presume you are running the full 20 chassis and up to 160 blades or rack servers in that one UCS domain.

UCS Manager Update from 2.1(1a) / 2.1(1b) to full 2.1(3b) cause Policy Reference Error on iSCSI

Hello,
I actualy did a UCS firmware upgrade from a mixed 2.1(1a) and 2.1(1b) to a full 2.1(3a) version.
Chassis are 2208XP, Fabrics are 6248UP and blades are all B200-M3.
I use firmware policy to update the firmware on the blades.
Here are the current version of the different componments:
- CIMC, Adapterers and BIOS Server: 2.1(3b)
- UCS Software: 2.1(3b)
- IO Modules: 2.1(1b)
- Fabric Kernel / System : 2.1(1b)
After UCS Software update when I connect on UCS Manager I got several warning referencing the error "Policy reference autProfileName does not resolve to named policy" on different parts.
I have follow some post to resolve some of them:
- iSCSI nic is created without Authentication profile issues:
https://tools.cisco.com/bugsearch/bug/CSCui43905
- Default SOL policy issue:
https://tools.cisco.com/bugsearch/bug/CSCtl88314
This resolve a lot of error but I'm still having errors like this on all my iscsi NIC:
Causing this:
Right now the update of the IOMs and FIs are on standby until I resolve this.
Can I have some help please.

It looks like you are hitting:
https://tools.cisco.com/bugsearch/bug/CSCui43905
Symptom:
Warning with the text "Policy reference authProfileName does not resolve to named policy" is seen when creating an iSCSI nic on a service profile.
Conditions:
Issue happens only when iSCSI nic is created without an Authentication profile
Workaround:
Use Authentication profile
Create a Default Authentication Profile
Existing warnings from the previous version would still exist even after the upgrade and that can be isolated only using the above work around. If new service profiles are created on the 2.2.1b version will not experience this issue.
Here is how to create an authentication profile:
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.1/b_UCSM_GUI_Configuration_Guide_2_1_chapter_011111.html#task_5DBBCD17FFA046A395B4493104838B1F

UCS-FI-6248UP vs UCS-FI-6248UP-UPG

Similar Messages

Maybe you are looking for