cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
354
Views
0
Helpful
1
Replies

Intersight Managed- Server shows DCE down

JDMils
Level 1
Level 1

I have a UCSX-210C-M7 server which is using a Server Profile derived from a Server Profile Template which is being used by other servers in the same rack, yet when I view the Topology for this server, I can see 2 connections to IOM 1 and 2 connections to IOM 2. However one of the connections to IOM 1 is red. Inventory shows adapter UCSX-ML-V5Q50G with interface DCE-3 with OperState Down.

I've logged this with TAC however they asked me to reseat the MLOM card. Is there any other checks I can do to reset the DCE like I used to in UCSM?

TAC says they found the following in the logs:

 

 

Here are my findings from the logs:
[+] Server is reporting a time out issue during discovery. 

3:2024 Feb  5 23:55:52 UTC:+0000:(5.2(0.230127)):mctpd:2590: upstream.c:168:write_read_message: request timeout for eid:0x0, bdf:0xe718.. retry count:0
5:2024 Feb  5 23:55:52 UTC:+0000:(5.2(0.230127)):cipmi:2420: [[xxxCVxxx]]:oem_command.c:469:IPMI Request Message --> Chan:15, Netfn:0x06, Cmd:0x06, Data: 0x80 0x80, CC:0x00
3:2024 Feb  5 23:55:54 UTC:+0000:(5.2(0.230127)):mctpd:2590: upstream.c:168:write_read_message: request timeout for eid:0x0, bdf:0xe718.. retry count:1
3:2024 Feb  5 23:55:56 UTC:+0000:(5.2(0.230127)):mctpd:2590: upstream.c:168:write_read_message: request timeout for eid:0x0, bdf:0xe718.. retry count:2
3:2024 Feb  5 23:55:56 UTC:+0000:(5.2(0.230127)):mctpd:2590: discovery_v2.c:570:endpoint_discovery: timed out
3:2024 Feb  5 23:55:57 UTC:+0000:(5.2(0.230127)):mctpd:2590: discovery_v2.c:3166:mctp_discovery_task: Discovery failed for 0xE718, Adding to excluded list 
3:2024 Feb  5 23:55:59 UTC:+0000:(5.2(0.230127)):mctpd:2590: upstream.c:168:write_read_message: request timeout for eid:0x0, bdf:0x6a18.. retry count:0
3:2024 Feb  5 23:56:01 UTC:+0000:(5.2(0.230127)):mctpd:2590: upstream.c:168:write_read_message: request timeout for eid:0x0, bdf:0x6a18.. retry count:1
3:2024 Feb  5 23:56:03 UTC:+0000:(5.2(0.230127)):mctpd:2590: upstream.c:168:write_read_message: request timeout for eid:0x0, bdf:0x6a18.. retry count:2
3:2024 Feb  5 23:56:03 UTC:+0000:(5.2(0.230127)):mctpd:2590: discovery_v2.c:570:endpoint_discovery: timed out
3:2024 Feb  5 23:56:04 UTC:+0000:(5.2(0.230127)):mctpd:2590: discovery_v2.c:3166:mctp_discovery_task: Discovery failed for 0x6A18, Adding to excluded list 
5:2024 Feb  6 00:13:48 UTC:+0000:(5.2(0.230127)):kernel:-:[60327.814082] [lpc_reset_isr_handler]:126:LPC Reset ISR -> ResetState: 1
4:2024 Feb  6 00:13:49 UTC:+0000:(5.2(0.230127)):LPCResetMonitor:2383: LPCResetMonitor.c:365:Failed to disable usb-nic : (1)
5:2024 Feb  6 00:13:49 UTC:+0000:(5.2(0.230127)):selparser:2491: [[xxxCVxxx]]:src/selparser.c:845: # F6 00 00 00 01 02 00 00 BD 79 C1 65 20 00 04 25 2C 00 00 00 08 00 0F 0F # f6 | 02/06/2024 00:13:49 UTC | CIMC | Entity presence BIOS_POST_CMPLT #0x2c | Device Absent | Asserted

 

 

 

1 Reply 1

JDMils
Level 1
Level 1

I reseated the mLOM card on the server however this did not fix the issue. Is there anything else I can look at?

Review Cisco Networking for a $25 gift card