Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
A stack of Catalyst Switches could print the following logging: %PLATFORM-3-ELEMENT_TMPFS_WARNING: Switch 1 R0/0: smand: 4/RP/0: TMPFS value 41% above warning level 40% %PLATFORM-3-ELEMENT_TMPFS_WARNING: Switch 2 R0/0: smand: 4/RP/0: TMPFS value 41% above warning level 40% %PLATFORM-3-ELEMENT_TMPFS_WARNING: Switch 2 R0/0: smand: 3/RP/0: TMPFS value 43% above warning level 40% and, the "tmp" filesystem, is showing high utilization: show platform soft mount switch 1 r0 | i ^tmpfs.*tmp | e /tmp/|Used Filesystem Used Available Use % Mounted on tmpfs 1416712 2462104 37% /tmp show platform soft mount switch 2 r0 | i ^tmpfs.*tmp | e /tmp/|Used Filesystem Used Available Use % Mounted on tmpfs 1565236 2313580 41% /tmp show platform soft mount switch 3 r0 | i ^tmpfs.*tmp | e /tmp/|Used Filesystem Used Available Use % Mounted on tmpfs 3663612 215204 95% /tmp show platform soft mount switch 4 r0 | i ^tmpfs.*tmp | e /tmp/|Used Filesystem Used Available Use % Mounted on tmpfs 3505048 373760 91% /tmp on all stack members.Furthermore, the excessive number of chasync logs can be seen in "crashinfo/tracelogs" directory: /crashinfo/tracelogs]$ date ; ls -ltr | grep chasync ... -rw-------. 1 root root 1591 Jan 14 11:58 chasync_R0-0.7075_3.20220114115821.bin.gz -rw-------. 1 root root 1784 Jan 14 11:58 chasync_R0-0.7075_2.20220114115821.bin.gz -rw-------. 1 root root 1835 Jan 14 11:58 chasync_R0-0.7075_4.20220114115821.bin.gz -rw-------. 1 root root 1678 Jan 14 11:58 chasync_R0-0.7075_5.20220114115822.bin.gz -rw-------. 1 root root 1815 Jan 14 11:58 chasync_R0-0.7075_6.20220114115835.bin.gz -rw-------. 1 root root 1459 Jan 14 11:58 chasync_R0-0.7075_7.20220114115854.bin.gz -rw-r--r--. 1 root root 1590 Jan 14 11:59 chasync_R0-0.7075_8.20220114115855.bin.gz -rw-------. 1 root root 1534 Jan 14 11:59 chasync_R0-0.7075_9.20220114115900.bin.gz -rw-------. 1 root root 1777 Jan 14 11:59 chasync_R0-0.7075_10.20220114115916.bin.gz -rw-------. 1 root root 1428 Jan 14 11:59 chasync_R0-0.7075_11.20220114115944.bin.gz -rw-------. 1 root root 1566 Jan 14 11:59 chasync_R0-0.7075_12.20220114115945.bin.gz -rw-------. 1 root root 1764 Jan 14 12:00 chasync_R0-0.7075_13.20220114115950.bin.gz -rw-------. 1 root root 1440 Jan 14 12:01 chasync_R0-0.7075_14.20220114120034.bin.gz -rw-------. 1 root root 1525 Jan 14 12:01 chasync_R0-0.7075_15.20220114120106.bin.gz -rw-------. 1 root root 1666 Jan 14 12:01 chasync_R0-0.7075_16.20220114120108.bin.gz -rw-------. 1 root root 1613 Jan 14 12:01 chasync_R0-0.7075_17.20220114120124.bin.gz
None, this was first identified on a Stack of switches running 17.3.4 release. No configuration or changes triggers this.
None, apart from removing the excessive Btrace files from TMPFS - contact Cisco TAC, as it requires a Linux Shell access.
The issue has been addressed with an SMU patch, which is available for 17.3.4 release: https://software.cisco.com/download/home/286313983/type/286308587/release/Amsterdam-17.3.4 - cat9k_iosxe.17.03.04.CSCwa67435.SPA.smu.bin