Unsolved
This post is more than 5 years old
30 Posts
0
765
September 13th, 2013 07:00
Diffrenet Instrumentation class for same device system object id
Hello
As you know there oid2type_ .conf file where we can specify the instrumenation. I have following situation. Two devices same SystemObjectID, but the interfaces information are on one device in the IF-MIB and on the other device in the HR-MIB (Hostresource).
Question: Is there a way to configure two different instrumenation for the same devices. Disingushed can be done by the description.
Update: 17.09.2013
What about TopologyUpdateInfo for the SNMPAgent object?
I saw in a lot of disocvery scripts that these has been used and if I am adding following line to the discovery script I am getting the correct instrumenation class Interface_Fault_SC_hrDevice is used.
agentObj->TopologyUpdateInfo += list("FAULT",
ifObj->Name,
"Interface_Fault_SC_hrDevice",
index) ? LOG, IGNORE;
Regards,
Christian
Nachricht geändert durch Christian
Sean_Mackinnon
26 Posts
1
September 16th, 2013 07:00
Hello Christian,
What you want to do is not possible via the oid2type_ .conf file. In order to achieve what you want you will can follow a solution path similar to the one being discussed in the forum post located at https://community.emc.com/thread/178153
You will have to update the discovery process so that when it discovers a device with this particular SysOID it will cause the script to make a call and check another OID on the device that contains some sort of flag allowing the script to determine how to discover the device. Once this determination is made the script could choose to import instrumentation information from the oid2type_ .conf file or ignore the file and use a customer set of instrumentation from another conf file or that is hard coded into the script.
The task you want to accomplish can be very difficult to write depending on how much background you have in the Smarts software and the ASL/Perl scripting languages. If you are not sure of you back ground and your ability to complete this task then your best option is to engage the EMC professional services group and have them build the customization for you. In order to get hold of EMC Professional Services (Pro Serv) you will need to contact your EMC Sales Account Manager (SAM) and inform them of what you want to do and that you need EMC Professional Services to be engaged.
My suggestion for getting start is that you take a look at how the discussion linked above suggests using the cpProductNameOID to identify how the device is being used and make this the flag for the discovery logic to use in determining which instrumentation to apply.
I hope this makes sense to you. If you have any questions please feel free to ask and I will try to answer them as best as I can.