Fabric Interconnect Login types

Hello all,
so im trying to login to my fabric interconnects via SSH and cant login in with the 'Local' Account i have set up OR the Local Admin account on the FI's.
we have our 'Native' Authentication setup for LDAP so that works.
I have tried Admin@local , Admin.local and it doesnt seem to work.
i dont want to have to change the 'Native' or Default Authentication type just to login in with local admin to the FI's.
any help would be appreciated. Thanks.
6248's
2.21d for UCSM and Infra.
Francisco-

Hi,
Please find the below link for "Configuring Authentication", hope it helps you.
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-0/b_UCSM_GUI_Configuration_Guide_2_0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0111.html
Thanks,
Gaurav

Similar Messages

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

6248U Fabric Interconnect bootloader prompt

Hi -
I am setting up a couple of new 6248U Fabric Interconnects. When i console into them I noticed it at the following prompt.
loader>
So I would run a dir command and found this in the file listing
ucs-6100-k9-system-kickstart.5.0.3.N2.2.04b.bin
so at the prompt I would type boot ucs-6100-k9-system-kickstart.5.0.3.N2.2.04b.bin
after that boots I would get the following prompt:
switch(boot)#
These are not plugged into any chassis or i/o modules yet. I wante dto pre configure and put the management ip's and cluster ip into these FI's..
What am I doing wrong

Thanks for the reply. This is the result I got: (look at the prompt I got on the bottom)
boot ucs-6100-k9-system-kickstart.5.0.3.N2.2.04b.bin ucs-6100-k9-system.5.0.3.N2.2.04b.bin
Starting kernel...
Usage: init 0123456SsQqAaBbCcUu
INIT: version 2.85 booting
I2C - Mezz absent
sprom_drv_init_platform: nuova_i2c_register_get_card_index
blogger: /var/log/isan.log: No such file or directory (2).
Starting system POST.....
Executing Mod 1 1 SEEPROM Test:...done (1 seconds)
Executing Mod 1 1 GigE Port Test:....done (32 seconds)
Executing Mod 1 1 PCIE Test:.................done (0 seconds)
Mod 1 1 Post Completed Successfully
POST is completed
autoneg unmodified, ignoring
autoneg unmodified, ignoring
S10mount-ramfs.supnuovaca Mounting /isan 3000m
Mounted /isan
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
Checking all filesystems....r. done.
Warning: switch is starting up with default configuration
Checking NVRAM block device ... done
The startup-config won't be used until the next reboot.
Loading system software
Uncompressing system image: bootflash:///ucs-6100-k9-system.5.0.3.N2.2.04b.bin
Loading plugin 0: core_plugin...
Loading plugin 1: eth_plugin...
Loading plugin 2: fc_plugin...
INIT: Entering runlevel: 3
Exporting directories for NFS kernel daemon...done.
Starting NFS kernel daemon:rpc.nfsd.
rpc.mountddone.
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
INIT: Id "sm" respawning too fast: disabled for 5 minutes
/isan/bin/first-setup: line 1663: /isan/etc/common_defs: No such file or directory
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
/isan/sbin/sysmgr: error while loading shared libraries: libconvertinfra.so: cannot open shared object file: No such file or directory
INIT: Id "sm" respawning too fast: disabled for 5 minutes
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
bash-2.05b#
bash-2.05b#
bash-2.05b#

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!

Connecting Fabric Interconnect to iSCSI array

I need to connect my Fabric Interconnect to a new iSCSI array. There are a number of UCS blades that need to connect to iSCSI LUNs. The FI is currently connected to the rest of the network through Nexus 7000K switches. Should I connected directly from the FI to the iSCSI array, or go through the 7000K and then to the array?

Hi
this is more of a design question, you have to think what will need access to the ISCCI storage array. For example, if only UCS blaes will have access to this storage array, you may want to consider connecting it directly as iscsi traffic won't have to go through your N7Ks if both fabrics are active.
If you want another type of server such as HP or IBM to access the storage you may want to consider connecting the storage array to the N7Ks if your fabric are configured in end-host-mode. Again this will depend on your current implementation

Fabric Interconnect Uplink port channeling...

Hi,
We setup port channel of two 10G uplink interfaces on each Fabric Interconnect. Everything is running as expected.
However we noticed that under 'Port-Channel # (Fabric #)' setting on LAN tap, 'Admin Speed' was set to '10Gbps'.
Should we leave this configuration as is or match to the maximum bandwidth of port Channel we set up (20Gbps)?
I only see four options on each port channel configuration, 1 Gbps, 10Gbps, 20Gbps and 40Gbps so I'm not sure if we should change this setting.
Thank you

Hello,
You do not need to change the speed ( admin ). 20 Gbps configuration is applicable for certain server models.
-------- NXOS output -----------------
FI-A(nxos)# sh run int port-channel 1
interface port-channel1
description U: Uplink
switchport mode trunk
speed 10000
FI-A(nxos)# show int port-channel 1
port-channel1 is up
Hardware: Port-Channel, address: 547f.ee67.e0fb (bia 547f.ee67.e0fb)
Description: U: Uplink
MTU 1500 bytes, BW 20000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is trunk
full-duplex, 10 Gb/s
FI-A(nxos)# sh int bri
Port-channel VLAN Type Mode   Status Reason                    Speed Protocol
Interface
Po1          1     eth trunk up      none                       a-10G(D) lacp
There is cosmetic defect where we list the operational speed as 10 Gbps instead of 20Gbps
FI-A /eth-uplink/fabric # show port-channel detail
Port Channel:
    Port Channel Id: 1
    Name: FIA
    Admin State: Enabled
    Oper State: Up
   Speed: 10 Gbps
    Oper Speed: 10 Gbps
    State Reason:
    flow control policy: default
HTH
Padma

Fabric Interconnect 6248 & 5548 Connectivity on 4G SFP with FC

Hi,
Recently I came across a scenario when I connected a 4G SFP on Expansion Module of 6248 Fabric Interconnect at one end and at other end 4G SFP on 5548UP. I was unable to establish FC connectivity between both of the devices and the momemt I connected 4G SFP on Fixed Module of 6248 connectivity got established between both the devices
I would like to know do I have to do any changes on FI's Expansion module to get the connectivity working or this kind of behivor is expected behavior
Do let me know if you need any other information on this
Regards,
Amit Vyas

Yes, On FI-B port 15-16 should be in VSAN 101 instead of 100, I have made that correction
Q. are you migrating the fc ports from the fixed to the expansion module ?
     A: As off now I am not migrating FC port but in near future I have to migrate FC ports to Expansion module and I don't want to waste my time for troubleshooting at that time.
Is my understanding correct, that you have 2 links from each FI to a 5548, no port fc port-channel ?
     A: Yes, your understanding is correct we have 2 links from each FI to 5548 and no FC port-channel is configured
I will do the FC port-channel later on once I am able to fix the connectivity issue
I will try to put 4G SFP on expansion module and will provide you output of "show interface brife"
Following is the out of "show interface brife" from both 5548UP switches
Primary5548_SW# show interface brief
Interface Vsan   Admin Admin   Status          SFP    Oper Oper   Port
                  Mode   Trunk                          Mode Speed Channel
                         Mode                                 (Gbps)
fc1/29     100    auto   on      up               swl    F       4    --
fc1/30     100    auto   on      up               swl    F       4    --
fc1/31     100    auto   on      up               swl    F       4    --
fc1/32     100    auto   on      up               swl    F       4    --
Ethernet      VLAN    Type Mode   Status Reason                   Speed     Port
Interface                                                                    Ch #
Eth1/1        1       eth access down    Link not connected          10G(D) --
Eth1/2        1       eth access down    Link not connected          10G(D) --
Eth1/3        1       eth access down    SFP not inserted            10G(D) --
Eth1/4        1       eth access down    SFP not inserted            10G(D) --
Eth1/5        1       eth access down    SFP not inserted            10G(D) --
Eth1/6        1       eth access down    SFP not inserted            10G(D) --
Eth1/7        1       eth access down    SFP not inserted            10G(D) --
Eth1/8        1       eth access down    SFP not inserted            10G(D) --
Eth1/9        1       eth access down    SFP not inserted            10G(D) --
Eth1/10       1       eth access down    SFP not inserted            10G(D) --
Eth1/11       1       eth access down    SFP not inserted            10G(D) --
Eth1/12       1       eth access down    SFP not inserted            10G(D) --
Eth1/13       1       eth access down    SFP not inserted            10G(D) --
Eth1/14       1       eth access down    SFP not inserted            10G(D) --
Eth1/15       1       eth access down    SFP not inserted            10G(D) --
Eth1/16       1       eth access down    SFP not inserted            10G(D) --
Eth1/17       1       eth access down    SFP not inserted            10G(D) --
Eth1/18       1       eth access down    SFP not inserted            10G(D) --
Eth1/19       1       eth access down    SFP not inserted            10G(D) --
Eth1/20       1       eth access down    SFP not inserted            10G(D) --
Eth1/21       1       eth access down    SFP not inserted            10G(D) --
Eth1/22       1       eth access down    SFP not inserted            10G(D) --
Eth1/23       1       eth access down    SFP not inserted            10G(D) --
Eth1/24       1       eth access down    SFP not inserted            10G(D) --
Eth1/25       1       eth access down    SFP not inserted            10G(D) --
Eth1/26       1       eth access down    SFP not inserted            10G(D) --
Eth1/27       1       eth access down    SFP not inserted            10G(D) --
Eth1/28       1       eth access down    SFP not inserted            10G(D) --
Eth2/1        1       eth access down    SFP not inserted            10G(D) --
Eth2/2        1       eth access down    SFP not inserted            10G(D) --
Eth2/3        1       eth access down    SFP not inserted            10G(D) --
Eth2/4        1       eth access down    SFP not inserted            10G(D) --
Eth2/5        1       eth access down    SFP not inserted            10G(D) --
Eth2/6        1       eth access down    SFP not inserted            10G(D) --
Eth2/7        1       eth access down    SFP not inserted            10G(D) --
Eth2/8        1       eth access down    SFP not inserted            10G(D) --
Eth2/9        1       eth access down    SFP not inserted            10G(D) --
Eth2/10       1       eth access down    SFP not inserted            10G(D) --
Eth2/11       1       eth access down    SFP not inserted            10G(D) --
Eth2/12       1       eth access down    SFP not inserted            10G(D) --
Eth2/13       1       eth access down    SFP not inserted            10G(D) --
Eth2/14       1       eth access down    SFP not inserted            10G(D) --
Eth2/15       1       eth access down    SFP not inserted            10G(D) --
Eth2/16       1       eth access down    SFP not inserted            10G(D) --
Port   VRF          Status IP Address                              Speed    MTU
mgmt0 --           up     172.20.10.82                            1000     1500
Interface Vsan   Admin Admin   Status      Bind                 Oper    Oper
                  Mode   Trunk               Info                 Mode    Speed
                         Mode                                            (Gbps)
vfc1       100    F     on     errDisabled Ethernet1/1              --
Primary5548_SW#
Secondary5548_SW# show interface brief
Interface Vsan   Admin Admin   Status          SFP    Oper Oper   Port
                  Mode   Trunk                          Mode Speed Channel
                         Mode                                 (Gbps)
fc1/29     101    auto   on      up               swl    F       4    --
fc1/30     101    auto   on      up               swl    F       4    --
fc1/31     101    auto   on      up               swl    F       4    --
fc1/32     101    auto   on      up               swl    F       4    --
Ethernet      VLAN    Type Mode   Status Reason                   Speed     Port
Interface                                                                    Ch #
Eth1/1        1       eth access down    Link not connected          10G(D) --
Eth1/2        1       eth access down    Link not connected          10G(D) --
Eth1/3        1       eth access down    SFP not inserted            10G(D) --
Eth1/4        1       eth access down    SFP not inserted            10G(D) --
Eth1/5        1       eth access down    SFP not inserted            10G(D) --
Eth1/6        1       eth access down    SFP not inserted            10G(D) --
Eth1/7        1       eth access down    SFP not inserted            10G(D) --
Eth1/8        1       eth access down    SFP not inserted            10G(D) --
Eth1/9        1       eth access down    SFP not inserted            10G(D) --
Eth1/10       1       eth access down    SFP not inserted            10G(D) --
Eth1/11       1       eth access down    SFP not inserted            10G(D) --
Eth1/12       1       eth access down    SFP not inserted            10G(D) --
Eth1/13       1       eth access down    SFP not inserted            10G(D) --
Eth1/14       1       eth access down    SFP not inserted            10G(D) --
Eth1/15       1       eth access down    SFP not inserted            10G(D) --
Eth1/16       1       eth access down    SFP not inserted            10G(D) --
Eth1/17       1       eth access down    SFP not inserted            10G(D) --
Eth1/18       1       eth access down    SFP not inserted            10G(D) --
Eth1/19       1       eth access down    SFP not inserted            10G(D) --
Eth1/20       1       eth access down    SFP not inserted            10G(D) --
Eth1/21       1       eth access down    SFP not inserted            10G(D) --
Eth1/22       1       eth access down    SFP not inserted            10G(D) --
Eth1/23       1       eth access down    SFP not inserted            10G(D) --
Eth1/24       1       eth access down    SFP not inserted            10G(D) --
Eth1/25       1       eth access down    SFP not inserted            10G(D) --
Eth1/26       1       eth access down    SFP not inserted            10G(D) --
Eth1/27       1       eth access down    SFP not inserted            10G(D) --
Eth1/28       1       eth access down    SFP not inserted            10G(D) --
Eth2/1        1       eth access down    SFP not inserted            10G(D) --
Eth2/2        1       eth access down    SFP not inserted            10G(D) --
Eth2/3        1       eth access down    SFP not inserted            10G(D) --
Eth2/4        1       eth access down    SFP not inserted            10G(D) --
Eth2/5        1       eth access down    SFP not inserted            10G(D) --
Eth2/6        1       eth access down    SFP not inserted            10G(D) --
Eth2/7        1       eth access down    SFP not inserted            10G(D) --
Eth2/8        1       eth access down    SFP not inserted            10G(D) --
Eth2/9        1       eth access down    SFP not inserted            10G(D) --
Eth2/10       1       eth access down    SFP not inserted            10G(D) --
Eth2/11       1       eth access down    SFP not inserted            10G(D) --
Eth2/12       1       eth access down    SFP not inserted            10G(D) --
Eth2/13       1       eth access down    SFP not inserted            10G(D) --
Eth2/14       1       eth access down    SFP not inserted            10G(D) --
Eth2/15       1       eth access down    SFP not inserted            10G(D) --
Eth2/16       1       eth access down    SFP not inserted            10G(D) --
Port   VRF          Status IP Address                              Speed    MTU
mgmt0 --           up     172.20.10.84                            1000     1500
Interface Vsan   Admin Admin   Status      Bind                 Oper    Oper
                  Mode   Trunk               Info                 Mode    Speed
                         Mode                                            (Gbps)
vfc1       1      F     on     errDisabled Ethernet1/1              --
Secondary5548_SW#

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?

Port-channel L2 problem with Fabric Interconnect and Nexus 7010

Hi,
i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
I was trying :
1. I using non dedicated port in Nexus 7010.
      - rate-mode share
      - channel-group 1 mode active
      - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
2. I using non dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode on
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
3. I using dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
4. I using dedicated port in Nexus 7010
     - rate-mode dedicated
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up and running well.
but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
i attach the topology of N7K with Fabric interconnect.
regards,
Berwin H

Hi Manish,
the issue was solved, i was fix it last week.
the solution is:
i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2) so i allocate the interface on all module
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
So here the result of my port-channel :
SVRN7KFARM-HO-01# show 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)
Group Port-       Type     Protocol Member Ports
      Channel
1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                     Eth1/4(P)    Eth1/25(P)
2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                     Eth1/12(P)   Eth1/26(P)
3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)
4     Po4(SU)     Eth      NONE      Eth10/32(P) Eth10/34(P) Eth10/35(P)
                                     Eth10/36(P)
Thanks.
Berwin H

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.

Can the system name of the Fabric Interconnects be changed

I need to change the system name of the Fabric interconnects
I have given eg. EDCD
the FI now have EDCD-A
EDCD-B
I need to change it to ... ECCD-A
ECCD-B..
is it possible ?

Shyam,
You can definitely do it and for sure is not disruptive and take effect right away. Just go to the Admin tab> All> Management Interfaces> Name > Edit it with what you need > Apply.
It is so easy and fast that if at the same time you have an SSH session, as soon as you change the name, the system makes the change on your SSH session too.
Note: There is no need to look for the way to do this on each fabric. The name you are changing is for both FIs and the system will then add the xya-A or xya-B by itself.
Rate ALL helpful answers.
-Kenny

Info about Cisco Fabric Interconnect 6140 Operating System

Hello. We're looking for tech specs about Cisco Fabric Interconnect 6140 Operating System. For us is important to know if the os is NX-OS or not.
Posted by WebUser Federica Rossi

The underlying OS is built on NX-OS, but there is a lot of software running on top that is the actual UCSM itself.
The UCSM software controls the NXOS portions directly - there is no ability to actually configure the system from an NXOS level.
UCS-250-A(nxos)# sh ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Software
BIOS:      version 1.5.0
loader:    version N/A
kickstart: version 5.0(3)N2(2.1m)
system:    version 5.0(3)N2(2.1m)

Why would Fabric Interconnects populate in fabric topology?

If the Fabric Interconnects are configured in End-Host mode, why would it be sending management traffic through an F port link making it populate on our fabric topology. We don’t have this on our existing Blades centers and would expect that we would be able to suppress this for these UCS interconnect devices. These devices are not managed by the SAN teams and they would prefer them NOT to appear as though they are.
Any advice?

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.

No link between IOM port 2/2/3 and fabric interconnect B

Hello
I am trying to remove an uplink from an IOM to the fabric interconnect as its not required. I have tried to reset the I/O module and re-acknowledge the chassis with no luck, it is still shown in the GUI with the error message as in the subject. We are currently running 2.0(1s). The kit isn't in production yet.
Thanks for any help

Yes i agress thats a pretty heavy approach to clean it. No if you left it there as it is, there would have been no operational issues. It would have just left this fault in the UCSM.
./Abhinav

Fabric Interconnect vNic Failover

We have the following Palo vNIC allocation for an ESXi host with 1000v in our vBlock:
VLANs on vNIC #
1: 14;
2: 41
3: 42
4 20,12,22,24;
5: 4,3,6
Now the statement has been made to us that this would not provide a redundant networking configuration in the event of a Fabric Interconnect failure, and there must be pairs of vNICs carrying a VLAN – one that traverses the left FIC and one the right FIC. The suggestion to us was to only use 2 vNICs and carry all VLANs.
My understanding is that with the M81KR vNICs, they can be set to ‘Fabric Failover Mode’ which will switch the accessible path in the event of a FIC failure seamlessly to the host. Removing the host managed failover and maintaining the HA within the fabric instead.
Is this a correct deployment when using Fabric Failover?

I think I have found the answer to my own question:
https://supportforums.cisco.com/docs/DOC-14992

Fabric Interconnect Login types

Similar Messages

Maybe you are looking for