https://community.hpe.com/t5/server-management-systems/sim-alert-two-weeks-later/m-p/3572527#M12752 Any ideas why an alert would come through more than two weeks after it's time stamp?<BR /><BR />See below:<BR /><BR />-----Original Message-----<BR />From: <BR />Sent: Sunday, June 26, 2005 3:23 AM<BR />To: Messaging Admins<BR />Subject: rriexcl01b: Cluster Resource Degraded: SIM Alert!<BR /><BR /><BR />Event Name: Cluster Resource Degraded<BR />Event originator: rriexcl01b<BR />Event Severity: Major<BR />Event received: 10-Jun-2005, 13:47:24<BR /> <BR />Event description: This trap will be sent any time the condition of a cluster resource becomes degraded. User Action: Make a note of the cluster resource name then check the resource for the cause of the degraded condition.<BR /> <BR />Cluster Resource Name: P:<BR /> Tue, 28 Jun 2005 14:21:58 GMT Dee Dickerson 2005-06-28T14:21:58Z https://community.hpe.com/t5/server-management-systems/sim-alert-two-weeks-later/m-p/3572527#M12752 Any ideas why an alert would come through more than two weeks after it's time stamp?<BR /><BR />See below:<BR /><BR />-----Original Message-----<BR />From: <BR />Sent: Sunday, June 26, 2005 3:23 AM<BR />To: Messaging Admins<BR />Subject: rriexcl01b: Cluster Resource Degraded: SIM Alert!<BR /><BR /><BR />Event Name: Cluster Resource Degraded<BR />Event originator: rriexcl01b<BR />Event Severity: Major<BR />Event received: 10-Jun-2005, 13:47:24<BR /> <BR />Event description: This trap will be sent any time the condition of a cluster resource becomes degraded. User Action: Make a note of the cluster resource name then check the resource for the cause of the degraded condition.<BR /> <BR />Cluster Resource Name: P:<BR /> Tue, 28 Jun 2005 14:21:58 GMT https://community.hpe.com/t5/server-management-systems/sim-alert-two-weeks-later/m-p/3572527#M12752 Dee Dickerson 2005-06-28T14:21:58Z