ESS History Log 1

[demanding]

In CM6.2, how long should the history log in an ESS system stay populated? Is there a setting to control this?

 

[AvayaTier3]

ESS and LSP lose CM SAT "list history" data on reset 4 of CM.

1800 entries in History log in CM SAT or in CM Linux bash (HISTSIZE)? Each login has /var/home/dadmin/.bash_history file that saves
CM Linux bash history. (substitute "dadmin" with LOGNAME) Can only be read or accessed by LOGNAME or "root / sroot")

ESS and LSP servers should all be set in the main to filesync. This includes Main xln which is
post processed at the ESS and LSP servers and CM restarts to load the most recent Main xln changes.
By design, this happens with Main CM daily save and Main CM SAT "save translation all" (see change system-parameters maintenance) This causes post process of file sync at every LSP and ESS server, then after the CM restart, there is no data in the LSP / ESS CM SAT Command: list history

CM SAT commands are saved to the associated Main / LSP / ESS server's CM /var/log/ecs/commandhistory files

change system-parameters maintenance                            Page   1 of   3
                   MAINTENANCE-RELATED SYSTEM PARAMETERS

OPERATIONS SUPPORT PARAMETERS
     CPE Alarm Activation Level: major

SCHEDULED MAINTENANCE
                                          Start Time: 00 : 15
                                           Stop Time: 04 : 30
                                    [b][COLOR=#CC0000]Save Translation: daily
 Update LSP and ESS Servers When Saving Translations: y
[/color][/b]                          Command Time-out (minutes):
                         Control Channel Interchange: Saturday
                      System Clocks/IPSI Interchange: Saturday

SYSTEM RESETS
            Reset System SAT Command Warning Message? n
--------------------------------------------------------------------------------
settings here determine what CM SAT history is saved in the Linux /var/log/ecs/commandhistory files.
You can also control what is in the CM SAT list history using this screen.
Command Logging? y and both saves before and after data into the commandhistory files.

change logging-levels                                           Page   1 of   2

                                 LOGGING LEVELS

 Enable Command Logging? y
        Log Data Values: both / new / 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: n
     Log CTA/PSA/TTI Transactions: y

dadmin@s8730-b> cd /var/log/ecs; pwd; ls -l commandhistory*
/var/log/ecs
-rw-r--r--  1 root root  25742 Sep 23 05:44 commandhistory
-rw-r--r--  1 root root  83056 Sep  1 02:05 commandhistory.1
-rw-r--r--  1 root root 165050 Aug  1 02:05 commandhistory.2
-rw-r--r--  1 root root 221651 Jul  1 02:05 commandhistory.3
-rw-r--r--  1 root root 201615 Jun  1 02:05 commandhistory.4

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

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]