Files for SMB troubleshooting

[G_W_Albrecht]

From the "big" gateways we know about log files for troubleshooting, e.g.the famous /var/log/messages. But on SMB units, some file locations are different. Important logs are:

/var/log/log/sfwd.el*
/var/log/log/cpwd.elg
/var/log/log/cposd.elg
/var/log/log/boot_log.elg
/fwtmp/temp_boot_log
/var/log/messages

Further information can be collected in expert mode by the following commands:

# echo show diag | clish > diag.txt
# cpinfo -z -o mycpinfo
# dmesg > mydmesg.txt

For cores we have to look here:

# ls -l /logs

Troubleshooting firmware upgrades may also be an important topic in case of issues. Log files of the upgrade and the upgrades auto-generated clish file can be found in directory:  /pfrm2.0/post_upgrade and a log file in:  /tmp/post_upgrade.log and /logs/backup_settings.

[Maarten_Sjouw]

One remark with the above mentioned log files, they are on a RAM-disk, so reboot and they are gone...

Some more helpful commands:

   > show configuration (available since R77.20) will show all configuration over a number of pages. 

to directly login into expert mode, go into expert mode and issue the command: bashUser on ; to switch it off again: bashUser off

Once logged on in bash you can run:

  # clish -c "show configuration" | grep route ; to see all routing commands

  # clish -c "show configuration" | grep interface ; to see all interface commands

[G_W_Albrecht]

That is rather very true, logs are hard to keep on SMB (if not re-directed to USB ;-). For  > show configuration, please also see my CheckMates article Configuration transfer between different SMB models.

[PVADS]

Just the sort of helpfull information that can address those unexspected issues 🙂

[G_W_Albrecht]

It at least offers a chance to be able to spot the cause.

[Pedro_Espindola]

/var/log/log/ is actually /tmp/log/, so I always prefer to go there, since it is shorter to type.

[G_W_Albrecht]

Yes, in /var we find a link to /tmp - i think this is the old SPLAT& GAiA /var/log/ Spirit 😉