symevent doesn't report link down problems.  This would be better served by port monitoring on the switch layer.  Turning it on for array ports is approrpiate, while for hosts not so much as they are rebooted frequently.

  Even some errors such as link errors or WP suspends are not always reported by the same director that experienced it, but rather the one director that had available time slices.  It's rather amusing to see a WP suspend error generated by an RA adapter that isn't cabled, zoned, or even has any rdf groups attached to it.

  If you are talking about the 'Events' for a given time interval then you will want to use the 'symaudit' command from the symcli.  Routine Clone / BCV splits that show up in the 'Events' tab in Performance are all recorded within the 'symaudit' output.

  Information such as pool utilization, FA busy / high water mark aren't going to be reported within either of these commands. This information is derived from collecting data from the SP, aggregating it, and generation of messages after a threshold is breached.

Turns out we had a bad I/O module. Odd thing is, we received no alerts from Unisphere For VMAX. I check and all alert profiles are enable but received no notifications. Do you know why this would be? We did get alerts when the tech replaced the module but not when it died.

As far as symevent, I think I just need to play around with the daemon config file to get it to display messages other than SRDF issues.

Some ports on FA 8 went offline. I opened a case, they dialed in and determined they needed to replace the module. It did not dial home.

When you say bad i/o module do you mean it was offline / down or that it dialed home and was slated for proactive replacement?

Odd, it should have dialed home.  If you look in support under this:

Service Center --> Site Administration --> (Choose site) --> Products --> Symmetrix SID

Click on the SID of the frame and it will show you the tickets opened against it.  There should be one that starts off with S7 with a following character of L, M or H. I've seen it log S7H when a director goes offline, or just a S7M when it's slated for proactive replacement.

I will research the site cases. I'm more interested in why Unisphere For VMAX didn't alert on the problem when it happened.  I only received alerts when tech did the swap of the module.