List History

[31lima]

Are there any new features within CM 5.2 that will allow you to gather more information on changes in CM?(list history e.t.c)



The moment you think you know it all, is the moment you stop learning...

 

[AvayaTier3]

many of the things you are asking about were enhanced in cm4

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[31lima]

Never had that, do you have a link.

Thanks

The moment you think you know it all, is the moment you stop learning...

 

[AvayaTier3]

Information about commands and history of transactions in CM and Linux commands

"all commands entered at the console or Definity terminal emulator"

This is not possible because the software only logs commands for add, change,
remove, and some maintenance commands like test, busy, release, reset to name a
few. Display, list, status, commands and many others do not get logged and you
would never know that anyone is doing them unless you do status logins while
these type commands are active.

You can monitor user's changes with Command: notify history (in realtime)

Command: list history (1800 line circular buffer of commands)

How fast this buffer fills is determined by numbers of changes and what data you
are sending to the history log. (This can be controlled in cm4 and higher)

Items like tti / psa / cms agent changes in loads before cm4 can also be
controlled.
----------------------
cm4 and higher:

Command: change logging-levels

Enable Command Logging? y
       Log Data Values: both

 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




                                 LOGGING LEVELS

      Log All Submission Failures: y
          Log PMS/AD Transactions: y
  Log IP Registrations and events: y
     Log CTA/PSA/TTI Transactions: y
---------------
prior to cm4:

system-parameters features

Record CTA/PSA/TTI Transactions in History Log? y
 Record All Submission Failures in History Log? y
     Record PMS/AD Transactions in History Log? y
        Record IP Registrations in History Log? y
------------------
different versions of CM store commands (CM and linux) in different files.
Data that is stored in the files changed from version to version.
Basically all of this is in the file system and you will have to look at the
files and timestamps on the files to see what your system normally stores before
the data is overwritten. These files will store more than the 1800 lines that
you can access from CM Command: list history
Also be aware that on duplicated servers, the offline (standby) server logfiles
will not have current CM commands stored. The commands logfiles will have data
from the last time the server was active. Knowing this about your system and
doing interchanges based on times just before files are to be overwritten will
double the amount of stored data in the combined server's files.

/var/log/messages
/var/log/messages.1
/var/log/messages.2
/var/log/messages.3
/var/log/messages.4
/var/log/commandhistory
/var/log/commandhistory.1
/var/log/commandhistory.2
/var/log/commandhistory.3
/var/log/commandhistory.4
----------------------------------
you could write a script to copy or tar and zip and copy to another server
on an as needed basis.

script could be as simple as follows which will create a tar.gz file with the
server_name and date in the file name. Then use scp or ftp to copy the archive
file off of the server to another server.

tar cvf /var/home/ftp/pub/`uname -n`_`date +%m%d%y`_hist_logs.tar /var/log/mess*
tar rvf /var/home/ftp/pub/`uname -n`_`date +%m%d%y`_hist_logs.tar /var/log/ecs/c
ommandhist*
gzip /var/home/ftp/pub/`uname -n`_`date +%m%d%y`_hist_logs.tar

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[31lima]

Thanks you Sir....

The moment you think you know it all, is the moment you stop learning...