各位，我这里有个5K tftp的告警麻烦帮忙看下吧

[1749450065]

cisco Nexus 5696 Chassis ("Nexus 5696 Supervisor")
Intel(R) Xeon(R) CPU @ 1.80 with 16511824 kB of memory.

XTWK-XX-5696-1 %SYSMGR-FEX102-3-CORE_OP_FAILED: Core operation failed: connect_and_upload_to_tftp: could not get tftp addr VDC: 1, idx: 0

May I ask what the problem is? Is it caused by the inability to access the tftp server? Why is fex102-3 displayed? Is fex102 accessing the tftp server？Could you please help me take a look

show fex   is normal

show module is normal

[anpetit]

Hi @1749450065 , 

Checking your thread, this log means that FEX 102 failed to copy a core file to the parent switch, in your case the Nexus 5696. The FEX is connected to the Admin VDC and that's why it's trying to upload the core file to the parent.
Core file are most of the time created when a process is crashing, hence, in your case, a process might have crashed on FEX 102. 
 
Regarding: Why is fex102-3 displayed? It's FEX 102 with log severity 3. 
May I ask if this log is kept being generated or was it a one time issue ?
Hope it helps you clarify your concerns. 
Let me know. 
Kind Regards,
Antoine

[1749450065]

This log has been reporting continuously

How can this problem be solved?

The business is normal now, but it keeps alerting and ignoring what impact it will have?

[anpetit]

Hello @1749450065 ,
Thanks for the reply. 
Then, if logs keep being generated, it means there is a core file on FEX 102.
Clearing the core file on the FEX will stop the log generation. 
To access the specific folder where this core file is on the FEX, you will need a specific debug plugin that only TAC can provide depending on the release you are running on. 
Let me know if it answers your concerns. 
Have a nice day. 
Kind Regards,
Antoine