QPADEV0006 message spamming on history log

15 pts.
Tags:
DSPLOG
In "DSPLOG", I keep getting the following message spammed. Any help would be greatly appreciated:
Description for device QPADEV0006 changed.
Session to device QPADEV0006 ended normally.
Description for device QPADEV0006 changed.
Session to device QPADEV0006 ended normally.
Description for device QPADEV0006 changed.
Session to device QPADEV0006 ended normally.
Description for device QPADEV0006 changed.
Session to device QPADEV0006 ended normally.
Description for device QPADEV0006 changed.
Session to device QPADEV0006 ended normally.
Description for device QPADEV0006 changed.
Session to device QPADEV0006 ended normally.
Description for device QPADEV0006 changed.
Session to device QPADEV0006 ended normally.
Description for device QPADEV0006 changed.
Session to device QPADEV0006 ended normally.
Description for device QPADEV0006 changed.
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • pdraebel
    Have you tried prompting the messages (F1 key) and checked the times those messages were sent?
    Is QPADEV0006 getting active?

    7,545 pointsBadges:
    report
  • ToddN2000
    Is it possible that this device is used by a automated process? Have you checked the times to see if it relates to an external process?
    132,590 pointsBadges:
    report
  • kf4wto
    There is nothing that connects the the 400 by any automated process. The times are random and it happens every second for about a minute then stops and does it again after an unspecific amount of time. It could be a 1/2 hour later or 6 hours later it starts again. I varied off QPADEV0006 and now it does it on QPADEV0002. I can't see it active at all, or at least have not be able to catch it active at anytime.
    15 pointsBadges:
    report
  • TheRealRaven
    The system audit journal should be where you start looking. Use the message times to narrow the search, and look for 'ZR', 'ZC', 'CA', 'OM' or any other entries that cluster at those times. Also use QPADEV0006 (or whichever device) as the job name as part of the selection criteria with the starting date/time.

    When you locate such clusters, look at the journal entry header info to see if a remote IP address is referenced. Look at some representative number of clusters to see if an address pattern appears. The IP addresses should lead to whatever the source (probably remote) is.

    If there are no relevant audit journal entries, you might want to review your audit procedures since some critical data is being lost.
    35,010 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: