Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


How do I get history to not log events by ip-u and ip-a?

How do I get history to not log events by ip-u and ip-a?

How do I get history to not log events by ip-u and ip-a?

Avaya Aura® Communication Manager. I went to check my history for an occurrence that occurred a week ago to try to track who made a change only to find out that my history only had 3 days worth of entries due to ip-u and ip-a login id's performing a change station multiple times to 3 of my stations once every minute until my history overwrote itself effectively erasing my history. The problem creating the entries was resolved by switching ports on the switch that those three phones were plugged into. Now I need to make sure this doesn't happen again, so I need to know how to disable history entries for login-ids of ip-u and ip-a. Apparently these 3 stations had an issue with the port they were plugged into on the switch causing multiples ip-u entries into the logs for every minute over a day and overwrote all of my older history. I know ip-u = unregister ip-a = associate then the change station that occurs with the various phones tells me which stations caused the issue, but I really just want to eliminate those entries from the history so I only see human initiated command history. Any assistance would be appreciated. I saw an older post similar to this but it had no response to it. Hopefully someone will respond to this post.

RE: How do I get history to not log events by ip-u and ip-a?

Change logging-levels and set IP registration to n.

RE: How do I get history to not log events by ip-u and ip-a?

Where is that done? I have been to the server and not found this setting, but yes this is what I need done. This is not a syslog issue but a history issue as we don't use syslog.

RE: How do I get history to not log events by ip-u and ip-a?

CM SAT session

Command: change logging-levels


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: n
  Log IP Registrations and events: n
     Log CTA/PSA/TTI Transactions: n

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


40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting

RE: How do I get history to not log events by ip-u and ip-a?

Thank you for your assistance. I totally missed that command in the ASA.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close