11-05-2018 06:52 AM
We recently performed a switchover on a Nexus 7K to the standby sup module in order to repair a flash issue related to a bug defect. There were no issues with failing over, but we have noticed now that we are not seeing any events at all in the log file. There have been some events that would typically generate eigrp log messages, but we are not seeing any of that in the log file since the failover.
11-05-2018 07:12 AM
Hello Awatson,
I hope you are doing great,
I would urge you to check the /var/log directory to see if it is fully used. If it is full you would see it as follow:
Nexus# show system internal flash
Mount-on 1K-blocks Used Available Use% Filesystem
/ 409600 61104 348496 15 /dev/root
/proc 0 0 0 0 proc
/sys 0 0 0 0 none
/isan 716800 315088 401712 44 none
/var 51200 612 50588 2 none
/etc 5120 1616 3504 32 none
/nxos/tmp 40960 4 40956 1 none
/var/log 51200 51200 0 100 none
This conducts this type of behavior, also could you share the bug that affected the flash?, You could follow the following link for solution on issues related to Logging on Nexus:
Keep me posted, let me know if you need anything,
Please qualify all of the helpful answers!
David Castro,
11-05-2018 07:21 AM
11-05-2018 07:46 AM
Hello A Watson,
So yes, the memory is on 100% of utilization. The usual cost is that there could be new messages that are not being redirected properly to the logfile, instead they go to a file called:
libdt_helper.log
And this is cause due to a bug:
https://quickview.cloudapps.cisco.com/quickview/bug/CSCue98451
Even when that is not your version, the recommended step is to delete that file, since that file does not corelate the files properly as the logfile and therefore causes the memory to be full. Below I will share a document with good practices on memory issues, and if you would like to unmount and mount the file in the directory again:
Also the guide for troubleshooting the flash memory:
Keep me posted, let me know if you need anything else,
Please qualify all the helpful answers, and mark as solved if it helped you solving the issue,
David Castro,
11-05-2018 08:27 AM
We are not hitting the bug you are referencing. We are actually hitting this one according to TAC:
11-05-2018 08:55 AM
Hi A Watson,
Awesome, let me Know if it worked after the reload. Also is there any other doubt or question from you regarding this?
Regards,
David Castro.
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