Cumulus Linux generates support files called cl-support whenever issues are detected.
This file is used to aid in troubleshooting customer issues. The Cumulus Networks global support staff often requests customers to provide this file when they open support tickets.
The cl-support file is located in the /var/support directory and is named cl_support_xxx.txz.
There are three ways cl-support is generated:
- If
switchdor any other process generates a core file (located in/var/support/core), then thecl-supportfile is generated. - After the first failure of one of the following monitored services since the switch was rebooted or power cycled:
- clagd
- frr/quagga
- openvswitch-vtep
- portwd
- ptmd
- rdnbrd
- switchd
- vxrd
- vxsnd
- A
cl-supportfile can be triggered by issuing thecl-supportcommand.
Note: You should only run this command at the direction of a member of the Cumulus Networks support staff.
If you need to copy the cl-support file off of the switch to a remote host for collection, use scp:
cumulus@switch:~$ scp /var/support/ username@myserver:/path/
Is there an better way ( than a dirty cron job ) to exec cl-support every N hour ? ( a bit like what Arista is doing by default
)
During tshoot, there is often a miss in collecting a show tech-support prior to take action like power cycle ( :p ) and you loose the ability to dig deeper afterward. Getting at least N hour old show-tech could help
Nicolas; it's a bad idea to run cl-support when it's not needed, because it can cause problems just by being run.
There are many ways to monitor CL on a switch, that don't involve running cl-support. And of course, there's netq.