Hello,
This is always an interesting topic. So strap-on, this might be a wild ride.
To kick things off, get yourself familiar with the overall MIB documentation available here: https://cdn1.raritan.com/download/pdu-g2/4.1.1/MIB_Usage_4.1.1_49961.pdf
Now i hope this is the correct one, but generally speaking the process for making sure any custom or extended discovery over SNMP works is mostly the same. Before we even jump into pattern design we need to make sure that we can classify the devices. Based on your question, i'd assume that this is exactly where you are stuck at.
And this is a quite common issue. Not all SNMP devices follow the same MIB structure. So not all of them will have the OID in the same place (or even exposed... looking at you SIEMENS). First step is always to identify some SNMP path which allows us to classify the device correctly. Usually we can use the OID, but apparently - and based on the documentation available - this is true for Raritan PDUs. So let's check the documentation (specifically chapter 5 - Object indexing):
Awesome, at least it is documented. So based on this, we can be somewhat sure that the following SNMP path will yield an OID - so we are in luck! This means we can use OID classifiers. Based on this documentation, the OID you want to add for any Raritan PDU is ".1.3.6.1.3.1.13742". Add this to your OID classifiers.
Next we need to add a classifier for PDUs - or more specifically Raritan PDUs. Then reference this classifier in your newly created OID classifier. On both records make sure the CI table is set to the PDU class.
Afterwards feel free to create a new SNMP patter to identify your PDU. Based on the documentation your hardware info is available as a single index as described in chapter 5.2
Overall this should get you to where you want to be. Always start with the classification. Then go into the discovery. And in this case, if you can, add the MIB file to the MID-Server MIB files.
Hope this helps,
Regards
Fabian
