MikeMeredith, There are no 'dumb' questions. We all start somewhere, so no worries! You're on the right path with checking the jobs. Good work. Could you run the following command in the CLI, via SSH session, and log the session output to a file? 'tail follow yes mp-log ms.log' This will show you the output from the ms.log management log file. This may show us some more details about what is going on when these AddrObjRefresh jobs kick off. I'm referencing a very similar case here, with a pair of 5000 series having the exact same issue. (225414) They also had setup User-ID recently and experienced the same behavior, so this could be the same issue, or very close. How many profiles were setup for User-ID (ldap, etc) ? In their scenario, the firewall was having trouble communicating to the LDAP server, due to other network issues, therefore user-id was taking up more cpu/ram than expected and constantly refreshing as it attempted to pull the group information. I will bet you $100 that if you were to disable the recent changes with User-ID and the server profiles, the issue would stop occurring. If you get the chance, please try this out and verify while it is not in production. This will help narrow down the issue. Let me know and we can go from there, Thanks!
... View more