HP 6125XLG R2306-HP 6125XLG Blade Switch Network Management and Monitoring Con - Page 65
Managing security logs
View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 65 highlights
Step 4. Enable log file overwrite-protection 5. (Optional.) Specify the maximum size of the log file. 6. (Optional.) Specify the directory to save the log file. Command Remarks info-center logfile overwrite-protection [ all-port-powerdown ] By default, log file overwrite-protection is disabled. With the all-port-powerdown keyword specified in the command, the device shuts down all the physical ports except for the console port, the management Ethernet port, and IRF ports when the log file is full or the free space of the flash is not enough. To restore normal state, backup the log file, delete the original log file to release storage space, and then bring up the ports. This feature is available only in FIPS mode. For more information about FIPS, see Security Configuration Guide. info-center logfile size-quota size The default setting is 10 MB. To ensure normal operation, set the size argument to a value between 1 MB and 10 MB. info-center logfile switch-directory dir-name By default, the log file is saved in the directory flash:/logfile. The configuration made by this command cannot survive an IRF reboot or a master/subordinate switchover. 7. Save the logs in the log file buffer to the log file. • Method 1: Configure the interval to perform the save operation: Use either method. info-center logfile frequency freq-sec By default, the system saves logs to the log file every 86400 seconds. • Method 2: Manually save the The logfile save command is logs in the log file buffer to the available in any view. log file: logfile save Managing security logs Security logs are very important for locating and troubleshooting network problems. Generally, security logs are output together with other logs. It is difficult to identify security logs among all logs. To solve this problem, you can save security logs into the security log file without affecting the current log output rules. 59