Avaya 8800 Troubleshooting Manual page 55

bf860005.007 file. You can avoid this if you rename the log file to something other than
the format used by SMP.
• If your TFTP server is a UNIX-based machine, any files written to the server must already
exist. For example, you must create dummy files with the same names as your system
log by sing the touch command (for example, touch bf860005.001).
Log file transfer criteria
Before logging a system message on the PCMCIA card (or external flash on the 8895 SF/
CPU), SMP calculates the space available for logging according to the parameters defined.
Either logging continues on the external memory card, or SMP transfers the existing log to a
remote host. After the current log file is transferred, a new log file is created on the external
memory card. If there is not enough free space on the external memory card for the new log
file to reach the configured minsize parameter, SMP logs to DRAM until there is enough free
space on the card.
Important:
Make sure you have sufficient space for the SMP log on your PCMCIA (or external flash)
card. Smaller amounts of free space for the log cause more frequent transfers.
If the transfer of a log file fails, a message indicating the failure is generated. If the configured
hosts are unreachable and the transfer fails, a log message is generated and the logging of
messages to the external memory card stops. A trap is generated and logging continues in the
DRAM.
After the system transfers the current SMP log file to a remote host, the system deletes the
SMP log on the external memory card. A new log file starts, with the extension incremented
by 1 (for example, /pcmcia/bf860005.003 is transferred, deleted, and /pcmcia/
bf860005.004 is created)
The following examples show how SMP determines when to transfer the log files and whether
to continue logging to the external memory card.
Example 1
The Avaya Ethernet Routing Switch 8800/8600 is operating with an 8 MB (8192 KB) PCMCIA
card installed.
The configured parameters are
• minsize: 100 KB
• maxsize: 2048 KB
• maxoccupyPercentage: 90
Troubleshooting
System Messaging Platform
July 2013 55