Fabric Interconnect join cluster

Hi! Experts:
When I join a new FI to the cluster, do I have to get the same firmware on the new FI before it can join?

It depends which version of UCS
I think since 2.1.3 it will automatically synch the versions, and therefore can join the cluster.
Before, you got the message: version mismatch, cannot join the cluster.
see Jeffs article: http://jeffsaidso.com/2014/05/cool-new-ucs-featurefirmware-sync/

Similar Messages

Changing fabric interconnect and cluster ip/sm/gw

I need to change the ip address/sm/gw of bnoth FI and the cluster but when I try to commit buffer
it keeps telling me this
Management IP of switch A & VIP are not in same subnet]

the error message is clear ! correct your input and it will work. what are your IP addresses and VIP, masks ??
It is most likely easier to do this with GUI: Admin ===> Management Interface

Fabric Interconnect 6120xp question

I have two fabric interconnect 6120xp in cluster on one i find the ip in running config and on the partner i dont. It might be due to this i dont get the ipaddress of the fabric interconnect (shows as 0.0.0.0) on my san switch when querying fcns database. Any help is appreciated.
lhr02-wxp00-fic01-B(nxos)# sh run |inc ip
ip host lhr02-wxp00-fic01-B 10.255.96.78
ip address 10.255.96.78/24
lhr02-wxp00-fic01-A(nxos)# sh run |inc ip
role name server-equipment
lhr02-wxp00-fic01-A(nxos)#
lhr02-wxif-san02# show fcns database npv
VSAN 20:
NPV NODE-NAME           NPV IP_ADDR     NPV IF CORE SWITCH WWN         CORE IF
20:14:54:7f:ee:04:c8:01 10.255.96.78    fc2/4   20:00:54:7f:ee:07:6e:80 fc1/6
20:14:54:7f:ee:04:c8:01 10.255.96.78    fc2/2   20:00:54:7f:ee:07:6e:80 fc1/5
lhr02-wxif-san01# show fcns database npv
VSAN 10:
NPV NODE-NAME           NPV IP_ADDR     NPV IF CORE SWITCH WWN         CORE IF
20:0a:54:7f:ee:03:ee:c1 0.0.0.0         fc2/1   20:00:54:7f:ee:17:eb:80 fc1/3
20:0a:54:7f:ee:03:ee:c1 0.0.0.0         fc2/3   20:00:54:7f:ee:17:eb:80 fc1/4

On the FI with the 0.0.0.0 ipaddress run the sho npv inter info | inc IP.
Next go into UCSM and select the equipment tab.Then pick the FI in question. On the right select General tab and then Access.
What is the ipaddress? Does it also show 0.0.0.0 here as well?
If it does, try changing it to the address you wanted and check it again.
If that does not work then you can try to erase the config on that FI and reconfiguring it from the begining.
Verify they it joins the cluster and HA is ready and the ipaddress is available.

Node can not join cluster after RAC HA Testing

Dear forum,
We are performing RAC failover tests according to document "RAC System Test Plan Outline 11gR2, Version 2.0". In testcase #14 - Interconnect network failure (11.2.0.2 an higher), we have disabled private interconnect network of node node1 (OCR Master).
Then - as expected - node node2 was evicted. Now, after enabling private interconnect network on node node1, i want to start CRS again on node2. However, node does not join cluster with messages:
2012-03-15 14:12:35.138: [ CSSD][1113114944]clssgmWaitOnEventValue: after CmInfo State val 3, eval 1 waited 0
2012-03-15 14:12:35.371: [ CSSD][1109961024]clssnmvDHBValidateNCopy: node 1, node1, has a disk HB, but no network HB, DHB has rcfg 226493542, wrtcnt, 2301201, LATS 5535614, lastSeqNo 2301198, uniqueness 1331804892, timestamp 1331817153/13040714
2012-03-15 14:12:35.479: [ CSSD][1100884288]clssnmvDHBValidateNCopy: node 1, node1, has a disk HB, but no network HB, DHB has rcfg 226493542, wrtcnt, 2301202, LATS 5535724, lastSeqNo 2301199, uniqueness 1331804892, timestamp 1331817154/13041024
2012-03-15 14:12:35.675: [ CSSD][1080801600]clssnmvDHBValidateNCopy: node 1, node1, has a disk HB, but no network HB, DHB has rcfg 226493542, wrtcnt, 2301203, LATS 5535924, lastSeqNo 2301200, uniqueness 1331804892, timestamp 1331817154/13041364
Rebooting node2 did not help. Node1 which was online all the time (although private interconnect interface was unplugged for a few minutes and then plugged back in). I suppose that if we reboot node2, the problem will disappear. But there should be solution, which keeps availability requirements.
Setup:
2 Nodes (OEL5U7, UEK)
2 Storages
Network bonding via Linux bonding
GI 11.2.0.3.1
RDBMS 11.1.0.7.10
Any ideas?
Regards,
Martin

I have found a solution myself:
[root@node1 trace]# echo -eth3 > /sys/class/net/bond1/bonding/slaves
[root@node1 trace]# echo -eth1 > /sys/class/net/bond1/bonding/slaves
[root@node1 trace]# echo +eth1 > /sys/class/net/bond1/bonding/slaves
[root@node1 trace]# echo +eth3 > /sys/class/net/bond1/bonding/slaves
Now node2 is automatically joining the cluster.
Regards,
martin

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#

6500 / fabric interconnect

Hi all,
its any issue to get a fabric interconnect cluster connected to a 6504??
becuase we are reviewing to get a connection betwen this 2 devices without any nexus devices.... is any problem with that??

Hello ,
Yes, you can connect UCS FI to 6500 switch.
Make sure you configure STP port fast on the 6K switch ports connecting to FI ( if operating in End host mode ).
Padma

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.

Fabric Interconnect ISSU support

I was asked by many cutomers about ISSU support for the UCS Fabric Interconnect ? They all know, that N5K (without L3 module) supports ISSU. Is it on the roadmap ?

Hello wdey,
This is a different concept, the nexus control plane need keep relationships during the upgrade process.
In the UCS Fabric Interconnect, you have others tecnologies to provide high avability to the system overall. (fabric failover, UCSM cluster, FC multipath).
Although the N5K and the FI is almost the same box, the systems running are completly different. The ISSU in the FI is not necessary, as all functions can be transfered to the pair FI that remained running.
Richard

FAS3220 and FAS2240 direct attach on fabric interconnect 6296UP

Hello everybody
I have the following architecture
1 Cisco Catalyst 6509-E
1 Cisco Catalyst 3560-x
2 Fabric Interconnect 6296UP
1 FAS 3220 (principal storage)
1 FAS2240 (vault backup)
1 chasis cisco UCS 5108
5 blade servers Cisco UCS B200M3
Firmware version: 2.2(3c)
Fabric Interconnect are direct attach on fabric interconnect 6296up and the ports are configurated as FC storage ports
My question is the following:
Can I zoning fabric interconnect with FAS3220 and FAS2240?
Can I present LUNS of FAS2240 and FAS3220 at the same time on the same boot policy, same san boot policy, and the same organization?
Thanks for your help

Well, even if that was possible. You're accounting for a critical failure - i.e. a failure of two redundant devices (both 3220s, which I would have assume would be running in a cluster ... or 7mode).
While just upstream you have a single cat 6500 - which would be a single point of failure.
Logic would dictate to account for a single device failure all across the path before looking into multi-device failure.

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

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

Node does not join cluster upon reboot

Hi Guys,
I have two servers [Sun Fire X4170] clustered together using Solaris cluster 3.3 for Oracle Database. They are connected to a shared storage which is Dell Equallogic [iSCSI]. Lately, I have ran into a weird kind of a problem where as both nodes come up fine and join the cluster upon reboot; however, when I reboot one of nodes then any of them does not join cluster and shows following errors:
This is happening on both the nodes [if I reboot only one node at a time]. But if I reboot both the nodes at the same time then they successfully join the cluster and everything runs fine.
Below is the output from one node which I rebooted and it did not join the cluster and puked out following errors. The other node is running fine will all the services.
In order to get out of this situation, I have to reboot both the nodes together.
# dmesg output #
Apr 23 17:37:03 srvhqon11 ixgbe: [ID 611667 kern.info] NOTICE: ixgbe2: link down
Apr 23 17:37:12 srvhqon11 iscsi: [ID 933263 kern.notice] NOTICE: iscsi connection(5) unable to connect to target SENDTARGETS_DISCOVERY
Apr 23 17:37:12 srvhqon11 iscsi: [ID 114404 kern.notice] NOTICE: iscsi discovery failure - SendTargets (010.010.017.104)
Apr 23 17:37:13 srvhqon11 iscsi: [ID 240218 kern.notice] NOTICE: iscsi session(9) iqn.2001-05.com.equallogic:0-8a0906-96cf73708-ef30000005e50a1b-sblprdbk online
Apr 23 17:37:13 srvhqon11 scsi: [ID 583861 kern.info] sd11 at scsi_vhci0: unit-address g6090a0887073cf961b0ae505000030ef: g6090a0887073cf961b0ae505000030ef
Apr 23 17:37:13 srvhqon11 genunix: [ID 936769 kern.info] sd11 is /scsi_vhci/disk@g6090a0887073cf961b0ae505000030ef
Apr 23 17:37:13 srvhqon11 scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Apr 23 17:37:13 srvhqon11 /scsi_vhci/disk@g6090a0887073cf961b0ae505000030ef (sd11): Command failed to complete (3) on path iscsi0/[email protected]:0-8a0906-96cf73708-ef30000005e50a1b-sblprdbk0001,0
Apr 23 17:46:54 srvhqon11 svc.startd[11]: [ID 122153 daemon.warning] svc:/network/iscsi/initiator:default: Method or service exit timed out. Killing contract 41.
Apr 23 17:46:54 srvhqon11 svc.startd[11]: [ID 636263 daemon.warning] svc:/network/iscsi/initiator:default: Method "/lib/svc/method/iscsid start" failed due to signal KILL.
Apr 23 17:46:54 srvhqon11 svc.startd[11]: [ID 748625 daemon.error] network/iscsi/initiator:default failed repeatedly: transitioned to maintenance (see 'svcs -xv' for details)
Apr 24 14:50:16 srvhqon11 svc.startd[11]: [ID 694882 daemon.notice] instance svc:/system/console-login:default exited with status 1
root@srvhqon11 # svcs -xv
svc:/system/cluster/loaddid:default (Oracle Solaris Cluster loaddid)
State: offline since Tue Apr 23 17:46:54 2013
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: /var/svc/log/system-cluster-loaddid:default.log
Impact: 49 dependent services are not running:
svc:/system/cluster/bootcluster:default
svc:/system/cluster/cl_execd:default
svc:/system/cluster/zc_cmd_log_replay:default
svc:/system/cluster/sc_zc_member:default
svc:/system/cluster/sc_rtreg_server:default
svc:/system/cluster/sc_ifconfig_server:default
svc:/system/cluster/initdid:default
svc:/system/cluster/globaldevices:default
svc:/system/cluster/gdevsync:default
svc:/milestone/multi-user:default
svc:/system/boot-config:default
svc:/system/cluster/cl-svc-enable:default
svc:/milestone/multi-user-server:default
svc:/application/autoreg:default
svc:/system/basicreg:default
svc:/system/zones:default
svc:/system/cluster/sc_zones:default
svc:/system/cluster/scprivipd:default
svc:/system/cluster/cl-svc-cluster-milestone:default
svc:/system/cluster/sc_svtag:default
svc:/system/cluster/sckeysync:default
svc:/system/cluster/rpc-fed:default
svc:/system/cluster/rgm-starter:default
svc:/application/management/common-agent-container-1:default
svc:/system/cluster/scsymon-srv:default
svc:/system/cluster/sc_syncsa_server:default
svc:/system/cluster/scslmclean:default
svc:/system/cluster/cznetd:default
svc:/system/cluster/scdpm:default
svc:/system/cluster/rpc-pmf:default
svc:/system/cluster/pnm:default
svc:/system/cluster/sc_pnm_proxy_server:default
svc:/system/cluster/cl-event:default
svc:/system/cluster/cl-eventlog:default
svc:/system/cluster/cl-ccra:default
svc:/system/cluster/ql_upgrade:default
svc:/system/cluster/mountgfs:default
svc:/system/cluster/clusterdata:default
svc:/system/cluster/ql_rgm:default
svc:/system/cluster/scqdm:default
svc:/application/stosreg:default
svc:/application/sthwreg:default
svc:/application/graphical-login/cde-login:default
svc:/application/cde-printinfo:default
svc:/system/cluster/scvxinstall:default
svc:/system/cluster/sc_failfast:default
svc:/system/cluster/clexecd:default
svc:/system/cluster/sc_pmmd:default
svc:/system/cluster/clevent_listenerd:default
svc:/application/print/server:default (LP print server)
State: disabled since Tue Apr 23 17:36:44 2013
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
svc:/application/print/rfc1179:default
svc:/application/print/ipp-listener:default
svc:/network/iscsi/initiator:default (?)
State: maintenance since Tue Apr 23 17:46:54 2013
Reason: Restarting too quickly.
See: http://sun.com/msg/SMF-8000-L5
See: /var/svc/log/network-iscsi-initiator:default.log
Impact: This service is not running.
######## Cluster Status from working node ############
root@srvhqon10 # cluster status
=== Cluster Nodes ===
--- Node Status ---
Node Name Status
srvhqon10 Online
srvhqon11 Offline
=== Cluster Transport Paths ===
Endpoint1 Endpoint2 Status
srvhqon10:igb3 srvhqon11:igb3 faulted
srvhqon10:igb2 srvhqon11:igb2 faulted
=== Cluster Quorum ===
--- Quorum Votes Summary from (latest node reconfiguration) ---
Needed Present Possible
2 2 3
--- Quorum Votes by Node (current status) ---
Node Name Present Possible Status
srvhqon10 1 1 Online
srvhqon11 0 1 Offline
--- Quorum Votes by Device (current status) ---
Device Name Present Possible Status
d2 1 1 Online
=== Cluster Device Groups ===
--- Device Group Status ---
Device Group Name Primary Secondary Status
--- Spare, Inactive, and In Transition Nodes ---
Device Group Name Spare Nodes Inactive Nodes In Transistion Nodes
--- Multi-owner Device Group Status ---
Device Group Name Node Name Status
=== Cluster Resource Groups ===
Group Name Node Name Suspended State
ora-rg srvhqon10 No Online
srvhqon11 No Offline
nfs-rg srvhqon10 No Online
srvhqon11 No Offline
backup-rg srvhqon10 No Online
srvhqon11 No Offline
=== Cluster Resources ===
Resource Name Node Name State Status Message
ora-listener srvhqon10 Online Online
srvhqon11 Offline Offline
ora-server srvhqon10 Online Online
srvhqon11 Offline Offline
ora-stor srvhqon10 Online Online
srvhqon11 Offline Offline
ora-lh srvhqon10 Online Online - LogicalHostname online.
srvhqon11 Offline Offline
nfs-rs srvhqon10 Online Online - Service is online.
srvhqon11 Offline Offline
nfs-stor-rs srvhqon10 Online Online
srvhqon11 Offline Offline
nfs-lh-rs srvhqon10 Online Online - LogicalHostname online.
srvhqon11 Offline Offline
backup-stor srvhqon10 Online Online
srvhqon11 Offline Offline
cluster: (C383355) No response from daemon on node "srvhqon11".
=== Cluster DID Devices ===
Device Instance Node Status
/dev/did/rdsk/d1 srvhqon10 Ok
/dev/did/rdsk/d2 srvhqon10 Ok
srvhqon11 Unknown
/dev/did/rdsk/d3 srvhqon10 Ok
srvhqon11 Unknown
/dev/did/rdsk/d4 srvhqon10 Ok
/dev/did/rdsk/d5 srvhqon10 Fail
srvhqon11 Unknown
/dev/did/rdsk/d6 srvhqon11 Unknown
/dev/did/rdsk/d7 srvhqon11 Unknown
/dev/did/rdsk/d8 srvhqon10 Ok
srvhqon11 Unknown
/dev/did/rdsk/d9 srvhqon10 Ok
srvhqon11 Unknown
=== Zone Clusters ===
--- Zone Cluster Status ---
Name Node Name Zone HostName Status Zone Status
Regards.

check if your global devices are mounted properly
#cat /etc/mnttab | grep -i global
check if proper entries are there on both systems
#cat /etc/vfstab | grep -i global
give output for quoram devices .
#scstat -q
or
#clquorum list -v
also check why your scsi initiator service is going offline unexpectedly
#vi /var/svc/log/network-iscsi-initiator:default.log

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)

Fabric Interconnect join cluster

Similar Messages

Maybe you are looking for