BSM reports Sat 06 Dec, 2014 - 05:15:02 - A procGroupChangeTrap event has occurred, from Host_systemEDGE device, named rx????xxxx.1dc.com. The membership of process group monitor smpolicysrv process group has changed. pgmonIndex = 54220012 pgmonDescr =
we have a new server - server name changed for security purposes - that is running on RHEL 6.4 and CASiteMinder V12 SP3 CR011. This is the only RHEL 6.4 box we have in prod at this time but there are 9 more scheduled behind it in January. This is the first time in our team's history we've seen this trap.
Searching the web this is the only thing I can find which isn't enough context to help us decide what to do with the traip. It is important to note that CA SM and the server are both up and functioning properly when we get this trap.
procGroupChangeTrap
The following code shows the format of a procGroupChange trap, which the CA eHealth SystemEDGE agent sends to indicate that the process group has changed.
procGroupChangeEvent OBJECT IDENTIFIER ::= { traps 19 }
procGroupChangeTrap TRAP-TYPE
ENTERPRISE sysmgmt
VARIABLES { pgmonIndex, pgmonDescr, pgmonFlags, pgmonNumProcs, pgmonProcRegExpr, pgmonRowStatus, pgmonPIDList, pgmonStatusList}
DESCRIPTION "Membership in a process group has changed. (For example, members have joined or left the group or have changed.)”
::= 19