Richter, It sounds like you just need to setup traps to send alerts to your SCOM server.  Normally to see the things you listed like changes to links, lags, stacks, authentication failures, and other critical changes to your switches, it is not necessary to poll an OID.  All of these can be monitored automatically with traps.  The CPU, memory, temp, fan, and power that you listed are in a different category as they are all sensors in the switch that can send a trap when a threshold is reached, but can also be polled for exact measurements.  Traps are easier to use than polling an OID and allow you to keep an eye on the areas you mentioned.  To setup traps, set your community string on your switches and management server,  enable all traps, and set your management server as your host recipient.  The commands are: (config)#snmp-server community private su (config)#snmp-server enable traps all (config)#snmp-server host 10.10.10.5 private   I hope this is helpful to you. -B
Hi  I was wondering if anyone could possible advise on this inquiry, as all my searches and inquiries so far have not produced any results. I am finishing off a large deployment for a customer who has a mix of PowerConnect 80xx, 62xx, 55xx, and Blade M8024K, M6348 Switches. All the switches are deployed and operational, and we are now looking to setup the SCOM server to use SNMP to retrieve events etc. from the switches.  the problem is that i have not been able to find SNMP OIDs anywhere for the switches involved, which are needed. the events we would like to keep an eye on relate to link up downs, lag failover, stack, authentication,  and any critical failures for the models involved. there is no requirement for CPU or memory usage, temperature, fan or power consumption, so these are not needed.  Are there any SCOM Management packs which might be of help here? Any advice or pointers will be greatly appreciated. cheers.   
SNMP OID List for PowerConnect Switches