cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2549
Views
0
Helpful
8
Replies

Fault error Code on UCS 6140 Cluster

florent.tymen
Level 1
Level 1

Hi all,

I'm running a UCS 6140 Cluster with 1.4(3q) UCSM Version.

I've a Critical Fault.

The fault code is F999590. This fault code have no correspondance in the "Cisco UCS Faults and Error Messages Reference" doc.

By searching with fault description, i found:

fsmFailSwFcSanBorderDeploy

Fault Code:F999789

Message

[FSM:FAILED]: sam:dme:SwFcSanBorderDeploy

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to

resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the

Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve

the issue, execute the show tech-support command and contact Cisco Technical Support.

Fault Details

Severity: critical

Cause: fsm-failed

mibFaultCode: 999789

mibFaultName: fsmFailSwFcSanBorderDeploy

moClass: sw:FcSanBorder

Type: fsm

How can i investigate more ?

Thanks a lot.

Florent

1 Accepted Solution

Accepted Solutions

Hello Florent,

We need more logs and so I would suggest you to open a TAC service request to further investigate the following fault message for FI B FC links.

------------------------------------------

Code: F999590

Description: [FSM:FAILED]: Uplink fc port configuration on B(FSM:sam:dme:SwFcSanBorderDeploy)

Affected Object: sys/switch-B/border-fc

Creation Time: 2011-10-10T09:56:12.953

-------------------------------------------

Following information would also help the investigation

Were there any VSAN mismatch between FI and upstream FC switch ?

Is FI running End host or switching FC mode ?

Is FC trunking enabled on these links ?

If the FC ports are up and active, it could be also where the fault condition got cleared but fault message stayed on.

Padma

View solution in original post

8 Replies 8

padramas
Cisco Employee
Cisco Employee

Hello Florent,

Are you aware of any changes that triggered this fault ?

Can you please provide the output of " show vsan usage " from nxos cli mode ?

Padma

hi Padma,

Thanks you for responding.

The fault is appeared during implementation.

Below, you will find outputs.

fi1-A(nxos)# sh vsan usage

2 vsan configured

configured vsans:1,100

vsans available for configuration:2-99,101-4078,4080-4093

fi1-B(nxos)# sh vsan usage

2 vsan configured

configured vsans:1,200

vsans available for configuration:2-199,201-4078,4080-4093

no issue for me

Thanks

Florent

I found a difference in VSAN configuration.

Fabric A:

ID: 100

Port Type: aggregation

Transport type: FC

Port Channel Admin Speed is "Auto"

Operational Speed (Gbps): 32

Fabric B:

ID: 200

Port Type: aggregation

Transport type: FC

Port Channel Admin Speed is "8 Gbps"

Operational Speed (Gbps): 32

is this could be the problem ?

If i change, port channel admin speed, what are the consequences ?

Thanks

Florent

Hello Florent,

Were you trying to implement FC port channel ?

Can you please share related fault messages for this event from " show fault detail " output ?

scope fc-uplink

show interface

connect nxos ( from both FI )

show san-port-channel summary

Is it for both FIs ?

Padma

Hi all,

Here, you will find console output:

fi1-A# sh fault detail

Severity: Critical

Code: F999590

Last Transition Time: 2011-10-10T09:56:12.953

ID: 1509485

Status: None

Description: [FSM:FAILED]: Uplink fc port configuration on B(FSM:sam:dme:SwFcSanBorderDeploy)

Affected Object: sys/switch-B/border-fc

Name: Fsm Deploy Fsm Fail

Cause: Fsm Failed

Type: Fsm

Acknowledged: Yes

Occurrences: 1

Creation Time: 2011-10-10T09:56:12.953

Original Severity: Critical

Previous Severity: Critical

Highest Severity: Critical

fi1-A /fc-uplink # sh int

Interface:

Fabric ID  Slot  Port  Admin State  Oper State    State Reason

---------- ----- ----- ------------ ------------- ------------

A              2     5 Enabled      Sfp Not Present

                                                  SFP not present

A              2     6 Enabled      Sfp Not Present

                                                  SFP not present

B              2     5 Enabled      Sfp Not Present

                                                  SFP not present

B              2     6 Enabled      Sfp Not Present

                                                  SFP not present

fi1-A(nxos)# sh san-port-channel summary

U-Up D-Down B-Hot-standby S-Suspended I-Individual link

summary header

--------------------------------------------------------------------------------

Group  Port-      Type     Protocol  Member Ports

       Channel

--------------------------------------------------------------------------------

100    Spo100               FC      PCP      (U)  FC       fc2/1(P)  fc2/2(P)  fc2/3(P)  fc2/4(P)

fi1-A(nxos)# 

fi1-B(nxos)# sh san-port-channel summary

U-Up D-Down B-Hot-standby S-Suspended I-Individual link

summary header

--------------------------------------------------------------------------------

Group  Port-      Type     Protocol  Member Ports

       Channel

--------------------------------------------------------------------------------

200    Spo200               FC      PCP      (U)  FC       fc2/1(P)  fc2/2(P)  fc2/3(P) fc2/4(P)

fi1-B(nxos)#

Thanks for helping

Florent

Hello Florent,

We need more logs and so I would suggest you to open a TAC service request to further investigate the following fault message for FI B FC links.

------------------------------------------

Code: F999590

Description: [FSM:FAILED]: Uplink fc port configuration on B(FSM:sam:dme:SwFcSanBorderDeploy)

Affected Object: sys/switch-B/border-fc

Creation Time: 2011-10-10T09:56:12.953

-------------------------------------------

Following information would also help the investigation

Were there any VSAN mismatch between FI and upstream FC switch ?

Is FI running End host or switching FC mode ?

Is FC trunking enabled on these links ?

If the FC ports are up and active, it could be also where the fault condition got cleared but fault message stayed on.

Padma

Hello Padma and thanks for helping,

I'll open a TAC request on new week.

Thanks

Florent

florent.tymen
Level 1
Level 1

Hi all,

Good news, the fault has been cleared when i disable unused port.

So , i don't need to open a TAC request for the moment.

Thnaks for helping.

Florent

Review Cisco Networking for a $25 gift card

Review Cisco Networking for a $25 gift card