Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
History file size 2
- Thread starter tone70
- Start date
-
1
- #2
AvayaTier3
Technical User
Definity / CM
Command: list history
varies in size based on hardware platform and software version. This size cannot be changed. It works as a circular buffer. Oldest record is thrown away when a new record is added to the beginning.
g3si - 500 entries
g3r - 1250 entries
linux - 1800 entries
You could use ASA or other means to log the history before
it is overwritten.
this same history for linux is put into the file system.
/var/log/ecs/commandhistory files
commandhistory
commandhistory.1
commandhistory.2
commandhistory.3
commandhistory.4
These files last about 6 weeks before they get overwritten.
You could copy the history contents from them to files that can be archived.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
Command: list history
varies in size based on hardware platform and software version. This size cannot be changed. It works as a circular buffer. Oldest record is thrown away when a new record is added to the beginning.
g3si - 500 entries
g3r - 1250 entries
linux - 1800 entries
You could use ASA or other means to log the history before
it is overwritten.
this same history for linux is put into the file system.
/var/log/ecs/commandhistory files
commandhistory
commandhistory.1
commandhistory.2
commandhistory.3
commandhistory.4
These files last about 6 weeks before they get overwritten.
You could copy the history contents from them to files that can be archived.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
- Thread starter
- #3
-
1
- #4
phoneguy55
Programmer
In ASA use the report option and schedule the list history command to run montly. Then you can archive your history log forever.
- Thread starter
- #5
AvayaTier3
Technical User
change logging-levels in newer loads lets you control what goes into the history logs. You can turn off stuff that fills up the log quickly or useless data.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
Code:
change logging-levels Page 1 of 2
LOGGING LEVELS
Enable Command Logging? y
Log Data Values: none
When enabled, log commands associated with the following actions:
add? y export? y refresh? y
busyout? y get? n release? y
campon-busyout? y go? y remove? y
cancel? n import? y reset? y
change? y list? n save? y
clear? y mark? n set? y
disable? y monitor? y status? n
display? n netstat? n test? y
duplicate? y notify? n traceroute? n
enable? y ping? n upload? n
erase? y recycle? y
change logging-levels Page 2 of 2
LOGGING LEVELS
Log All Submission Failures: y
Log PMS/AD Transactions: y
Log IP Registrations and events: y
Log CTA/PSA/TTI Transactions: yA great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
- Status
Similar threads
- Locked
- Question