UCS file is stored in, bydefault a cs file is generate before acrchive restore -var/local/ucs/cs_backup.ucs
/config/bigip.conf has GUI LTM tab configuration
/config/bipip_base.conf has GUI Network & System tab configuration
/config/bipip_user.conf
/config/profile_base.conf Default Profiles configurations
/config/bigip.conf Custom Profiles configuration
/config/bigip.conf Custom Profiles configuration
/config/ssl/ssl.cert and /config/ssl/ssl.key certificate location on bigip
/etc/hosts file DNS host entry The BIG-IP system first refers to the local /etc/hosts file.
/var/core Core files contain the contents of the system memory at the time a crash occurred
/var/tmp/f5.com.qkview location where qkview file is saved to be sent to f5 support
/bin/ping , /bin/traceroute location of ping tool
/shared/log/eud.logEUD test log file location
/var/log/ltm, /em /gtm /asm respective module log files
/config/httpd/conf/ssl.crt/server.crt device certificate
/shared/images/by default images(.iso) file imported in BIG-IP location
/var/log/secure file The BIG-IP system generates a log message whenever a user or an application attempts to log in to or log out of the system. The system logs both successful and unsuccessful login attempts.
/etc/alertd/alert.conf file defines standard system alerts, and the /config/user_alert.conf file defines custom settings.
Core files contain the contents of the system memory at the time a crash occurred. If the system has been configured to save core files, they will be located in the /var/core directory
can replace the /config/bigip.license file with the original bigip.license file that you backed up from the target system
add a name server to your /etc/resolv.conf file, Do not attempt to manually edit the /etc/resolv.conf file as such changes do not persist reboots or configuration reloads. It is not necessary to save the TMOS Shell (tmsh) for this change to persist through a restart or configuration re-load
No comments:
Post a Comment