09-12-2013 10:36 PM - edited 03-01-2019 11:14 AM
HI ,all
UCS B service profile health:inoperable and my server front red light.
description:health:inoperable
id;225695
type equipment
cause:equipment-inoperable
code:F0317
I do this ,the major can not OK. but the server is work good
Fault Code:F0317
Message
Server [id] (service profile: [assignedToDn]) health: [operability]Server [chassisId]/[slotId] (service profile: [assignedToDn]) health: [operability]
Explanation
This fault typically occurs when the server has encountered a diagnostic failure.
Recommended Action
If you see this fault, take the following actions:
Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.
Step 2 Check the POST results for the server.In Cisco UCS Manager GUI, you can access the POST results from the General tab for the server. In Cisco UCS Manager CLI, you can access the POST results through the show post command under the scope for the server.
Step 3 Reacknowledge the server.
Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.
fault doct
http://www.cisco.com/en/US/docs/unified_computing/ucs/ts/faults/reference/UCS_SEMs.html
what theis question?
Solved! Go to Solution.
09-16-2013 03:50 AM
Hello,
Please open a TAC SR to get CMOS battery replaced for Server 1/1. After you replace it, service profile inoperable alert would also get cleared out.
Padma
09-16-2013 08:53 AM
Hailin,
You may check the CMOS voltage yourself to see the current charge, run the following:
A# connect cimc x/y x= chassis y= blade
Trying 127.5.x.y...
Connected to 127.5.x.y.
Escape character is '^]'.
CIMC Debug Firmware Utility Shell [ support ]
[ help ]# sensors <<<< The output is extensive, but look for P3V_BAT_SCALED it is generally at the beginning but may vary. This will let you check is the voltage is within the accepted range.
I hope that helps before you open the SR tomorrow.
Always rate helpful answers!
-Kenny
09-13-2013 05:17 AM
Hello Hailin,
Can you please scope into server and execute " show fault " command and share the command with us ?
Thanks
Padma
09-13-2013 08:26 PM
is this show tech can use?
the next wokr day ,i can konw the "show fault "
thank you .
07-13-2015 06:55 PM
Attachment has been removed to comply to the CSC terms of use conditions.
09-16-2013 12:43 AM
HI ,thank you .
this is your need.
admin-A /chassis # show fault
admin-A /chassis # show fault
Severity Code Last Transition Time ID Description
--------- -------- ------------------------ -------- -----------
Major F0317 2013-09-12T06:38:12.755 226717 Server 1/1 (service profile
: org-root/ls-EMRS-sys1) health: inoperable
Info F0461 2013-09-12T06:38:12.755 226718 Log capacity on Management
Controller on server 1/1 is very-low
Minor F0424 2013-09-12T06:38:12.754 226716 Possible loss of CMOS setti
ngs: CMOS battery voltage on server 1/1 is lower-critical
Major F0408 2013-08-24T01:16:50.203 214936 Power state on chassis 1 is
redundancy-failed
Info F0440 2013-01-17T07:56:09.310 213451 Chassis discovery policy co
nflict: Link IOM 1/2/1 to fabric interconnect B:1/1 not configured
Major F0401 2013-01-17T07:56:09.310 213452 IOM 1/2 (B) current connect
ivity does not match discovery policy: unsupported-connectivity
Major F0399 2013-01-17T07:47:49.170 213446 Current connectivity for ch
assis 1 does not match discovery policy: unsupported-connectivity
Info F0461 2013-01-04T11:38:23.298 213387 Log capacity on Management
Controller on server 1/2 is very-low
Info F0461 2013-01-02T03:53:30.183 213359 Log capacity on Management
Controller on server 1/3 is very-low
Info F0440 2012-12-17T01:22:55.275 151707 Chassis discovery policy co
nflict: Link IOM 1/1/1 to fabric interconnect A:1/2 not configured
Major F0401 2012-12-17T01:22:51.531 85697 IOM 1/1 (A) current connect
ivity does not match discovery policy: unsupported-connectivity
Warning F0378 2012-11-30T05:27:22.614 54688 Power supply 4 in chassis 1
presence: missing
------------------------------
admin-A /chassis # show fault detail
Fault Instance
Severity: Major
Code: F0317
Last Transition Time: 2013-09-12T06:38:12.755
ID: 226717
Status: None
Description: Server 1/1 (service profile: org-root/ls-EMRS-sys1) health: inoperable
Affected Object: sys/chassis-1/blade-1
Name: Compute Physical Inoperable
Cause: Equipment Inoperable
Type: Equipment
Acknowledged: No
Occurrences: 1
Creation Time: 2013-09-12T06:38:12.755
Original Severity: Major
Previous Severity: Major
Highest Severity: Major
Severity: Info
Code: F0461
Last Transition Time: 2013-09-12T06:38:12.755
ID: 226718
Status: None
Description: Log capacity on Management Controller on server 1/1 is very-low
Affected Object: sys/chassis-1/blade-1/mgmt/log-SEL-0
Name: Sysdebug Mep Log M Ep Log Very Low
Cause: Log Capacity
Type: Operational
Acknowledged: No
Occurrences: 1
Creation Time: 2013-09-12T06:38:12.755
Original Severity: Info
Previous Severity: Info
Highest Severity: Info
Severity: Minor
Code: F0424
Last Transition Time: 2013-09-12T06:38:12.754
ID: 226716
Status: None
Description: Possible loss of CMOS settings: CMOS battery voltage on server 1/1 is lower-critical
Affected Object: sys/chassis-1/blade-1/board
Name: Compute Board Cmos Voltage Threshold Critical
Cause: Voltage Problem
Type: Environmental
Acknowledged: No
Occurrences: 1
Creation Time: 2013-09-12T06:38:12.754
Original Severity: Minor
Previous Severity: Minor
Highest Severity: Minor
Severity: Major
Code: F0408
Last Transition Time: 2013-08-24T01:16:50.203
ID: 214936
Status: None
Description: Power state on chassis 1 is redundancy-failed
Affected Object: sys/chassis-1
Name: Equipment Chassis Power Problem
Cause: Power Problem
Type: Environmental
Acknowledged: Yes
Occurrences: 1
Creation Time: 2013-08-24T01:16:50.203
Original Severity: Major
Previous Severity: Major
Highest Severity: Major
Severity: Info
Code: F0440
Last Transition Time: 2013-01-17T07:56:09.310
ID: 213451
Status: None
Description: Chassis discovery policy conflict: Link IOM 1/2/1 to fabric interconnect B:1/1 not configured
Affected Object: sys/chassis-1/slot-2/fabric/port-1
Name: Ether Switch Intfio Satellite Wiring Numbers Unexpected
Cause: Unexpected Number Of Links
Type: Connectivity
Acknowledged: No
Occurrences: 2
Creation Time: 2013-01-17T07:47:49.183
Original Severity: Info
Previous Severity: Cleared
Highest Severity: Info
Severity: Major
Code: F0401
Last Transition Time: 2013-01-17T07:56:09.310
ID: 213452
Status: None
Description: IOM 1/2 (B) current connectivity does not match discovery policy: unsupported-connectivity
Affected Object: sys/chassis-1/slot-2
Name: Equipment Iocard Unsupported Connectivity
Cause: Serial Debug Pnuosdisconnect Failed
Type: Connectivity
Acknowledged: Yes
Occurrences: 2
Creation Time: 2013-01-17T07:47:49.184
Original Severity: Major
Previous Severity: Cleared
Highest Severity: Major
Severity: Major
Code: F0399
Last Transition Time: 2013-01-17T07:47:49.170
ID: 213446
Status: None
Description: Current connectivity for chassis 1 does not match discovery policy: unsupported-connectivity
Affected Object: sys/chassis-1
Name: Equipment Chassis Unsupported Connectivity
Cause: Serial Debug Pnuosdisconnect Failed
Type: Connectivity
Acknowledged: Yes
Occurrences: 1
Creation Time: 2013-01-17T07:47:49.170
Original Severity: Major
Previous Severity: Major
Highest Severity: Major
Severity: Info
Code: F0461
Last Transition Time: 2013-01-04T11:38:23.298
ID: 213387
Status: None
Description: Log capacity on Management Controller on server 1/2 is very-low
Affected Object: sys/chassis-1/blade-2/mgmt/log-SEL-0
Name: Sysdebug Mep Log M Ep Log Very Low
Cause: Log Capacity
Type: Operational
Acknowledged: Yes
Occurrences: 1
Creation Time: 2013-01-04T11:38:23.298
Original Severity: Info
Previous Severity: Info
Highest Severity: Info
Severity: Info
Code: F0461
Last Transition Time: 2013-01-02T03:53:30.183
ID: 213359
Status: None
Description: Log capacity on Management Controller on server 1/3 is very-low
Affected Object: sys/chassis-1/blade-3/mgmt/log-SEL-0
Name: Sysdebug Mep Log M Ep Log Very Low
Cause: Log Capacity
Type: Operational
Acknowledged: Yes
Occurrences: 1
Creation Time: 2013-01-02T03:53:30.183
Original Severity: Info
Previous Severity: Info
Highest Severity: Info
Severity: Info
Code: F0440
Last Transition Time: 2012-12-17T01:22:55.275
ID: 151707
Status: None
Description: Chassis discovery policy conflict: Link IOM 1/1/1 to fabric interconnect A:1/2 not configured
Affected Object: sys/chassis-1/slot-1/fabric/port-1
Name: Ether Switch Intfio Satellite Wiring Numbers Unexpected
Cause: Unexpected Number Of Links
Type: Connectivity
Acknowledged: No
Occurrences: 6
Creation Time: 2012-12-10T06:51:40.268
Original Severity: Info
Previous Severity: Cleared
Highest Severity: Info
Severity: Major
Code: F0401
Last Transition Time: 2012-12-17T01:22:51.531
ID: 85697
Status: None
Description: IOM 1/1 (A) current connectivity does not match discovery policy: unsupported-connectivity
Affected Object: sys/chassis-1/slot-1
Name: Equipment Iocard Unsupported Connectivity
Cause: Serial Debug Pnuosdisconnect Failed
Type: Connectivity
Acknowledged: Yes
Occurrences: 11
Creation Time: 2012-12-03T01:02:45.450
Original Severity: Major
Previous Severity: Cleared
Highest Severity: Major
Severity: Warning
Code: F0378
Last Transition Time: 2012-11-30T05:27:22.614
ID: 54688
Status: None
Description: Power supply 4 in chassis 1 presence: missing
Affected Object: sys/chassis-1/psu-4
Name: Equipment Psu Missing
Cause: Equipment Missing
Type: Equipment
Acknowledged: No
Occurrences: 1
Creation Time: 2012-11-30T05:27:22.614
Original Severity: Warning
Previous Severity: Warning
Highest Severity: Warning
admin-A /chassis #
admin-A /chassis #
admin-A /chassis #
admin-A /chassis # show fa
fabric fan-module fault
admin-A /chassis # show fault
09-16-2013 03:50 AM
Hello,
Please open a TAC SR to get CMOS battery replaced for Server 1/1. After you replace it, service profile inoperable alert would also get cleared out.
Padma
09-16-2013 07:42 AM
thanke you .may be this problem.
but,before two weeks, we have open TAC SR to get CMOS battery replaced for Server 1/1.
is it the Motherboard problem.?
tomorrom,i will open tac sr to get new cmos battery.
09-16-2013 08:53 AM
Hailin,
You may check the CMOS voltage yourself to see the current charge, run the following:
A# connect cimc x/y x= chassis y= blade
Trying 127.5.x.y...
Connected to 127.5.x.y.
Escape character is '^]'.
CIMC Debug Firmware Utility Shell [ support ]
[ help ]# sensors <<<< The output is extensive, but look for P3V_BAT_SCALED it is generally at the beginning but may vary. This will let you check is the voltage is within the accepted range.
I hope that helps before you open the SR tomorrow.
Always rate helpful answers!
-Kenny
09-16-2013 06:31 PM
hi ,dear;
this log :
bba | 01/02/2013 19:39:53 | CIMC | Voltage P3V_BAT_SCALED #0x00 | Lower critical - going low | Asserted | Reading 2.42 < Threshold 2.42 Volts
bbb | 01/02/2013 19:39:54 | CIMC | Platform alert LED_BLADE_STATUS #0x57 | LED color is amber | Asserted
bbc | 01/02/2013 19:40:00 | CIMC | Voltage P3V_BAT_SCALED #0x00 | Lower critical - going low | Deasserted | Reading 2.46 > Threshold 2.42 Volts
bbd | 01/02/2013 19:40:00 | CIMC | Platform alert LED_BLADE_STATUS #0x57 | LED color is green | Asserted
bbe | 01/02/2013 19:40:02 | CIMC | Voltage P3V_BAT_SCALED #0x00 | Lower critical - going low | Asserted | Reading 2.42 < Threshold 2.42 Volts
bbf | 01/02/2013 19:40:02 | CIMC | Platform alert LED_BLADE_STATUS #0x57 | LED color is amber | Asserted
bc0 | 01/02/2013 19:40:03 | CIMC | Voltage P3V_BAT_SCALED #0x00 | Lower critical - going low | Deasserted | Reading 2.46 > Threshold 2.42 Volts
is it the CMOS voltage 1 question?
09-17-2013 09:13 AM
Hailin,
Yes, the P3V_BAT_SCALED is the CMOS battery and yes that is the voltage read. You can also check that in real time with the command I pasted above.
-Kenny
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide