anchor.diff:  Allow Systems Management Data Engine SNMP to connect to snmpd using SMUX
   smuxpeer .1.3.6.1.4.1.674.10892.1
   ----
  +// I can verify this in a few days
   * You'll need to know the maximum number of possible logical disks you have in your environment. + 
   For example: If you have 3 RAID arrays, you need 3 service poller.
  +* Additional listing with the OIDs the monitor is using: +
  +virtualDiskRollUpStatus = ".1.3.6.1.4.1.674.10893.1.20.140.1.1.19"; +
  +arrayDiskLogicalConnectionVirtualDiskNumber = ".1.3.6.1.4.1.674.10893.1.20.140.3.1.5"; +
  +arrayDiskNexusID = ".1.3.6.1.4.1.674.10893.1.20.130.4.1.26"; +
  +arrayDiskLogicalConnectionArrayDiskNumber =".1.3.6.1.4.1.674.10893.1.20.140.3.1.3"; +
  +arrayDiskState=".1.3.6.1.4.1.674.10893.1.20.130.4.1.4"; +
  +additional listing for the interpretation of the diskstatus values: +
  +1: "Ready" +
  +2: "Failed" +
  +3: "Online" +
  +4: "Offline" +
  +6: "Degraded" +
  +7: "Recovering" +
  +11: "Removed" +
  +15: "Resynching" +
  +24: "Rebuilding" +
  +25: "noMedia" +
  +26: "Formating" +
  +28: "Running Diagnostics" +
  +35: "Initializing" +
  
positive.code: [options="header, autowidth"]
  |===
  | Parameter           | Description                                              | Required | Default value
  | `virtualDiskNumber` | The disk index of your RAID array                        | required | `-`
  | `retry`             | Amount of attempts opening a connection and try +
                          to get the greeting banner before the service goes down. | optional | `-`
  | `timeout`           | Time (in milliseconds) to wait before receiving the +
                          SNMP response.                                           | optional | `-`
  |===
  
  
  ==== Examples
  Some example configuration how to configure the monitor in the `poller-configuration.xml`
  [source, xml]
  ----
  <service name="OMSA_Storage_Disk_1" interval="300000"
  
negative.code:  <parameter key="timeout" value="6000"/>
   <parameter key="virtualDiskNumber" value="1"/>
  </service>
  <monitor service="OMSA_Storage_Disk_1" class-name="org.opennms.netmgt.poller.monitors.OmsaStorageMonitor"/>
  ----
  
  If there is more than one RAID array to monitor you need an additional configuration. In this case *virtualDiskNumber = 2*. And so on...
  [source, xml]
  ----
  <service name="OMSA_Storage_Disk_2" interval="300000"
    user-defined="false" status="on">
   <parameter key="retry" value="3"/>
   <parameter key="timeout" value="6000"/>
   <parameter key="virtualDiskNumber" value="2"/>
  </service>
  <monitor service="OMSA_Storage_Disk_2" class-name="org.opennms.netmgt.poller.monitors.OmsaStorageMonitor"/>
  ----
  
  
  ==== This section is optional and give some specific hints
  
  * The monitored system needs a specific snmp configuration to get a working datacollection. Not sure, if it is required for monitoring RAID status.
  [source]
  