Dynamic Modeling: Vendor equipment using Linux Host SystemObjectID

Hello Gabriel.

I'm not exactly understand what is "I cannot change the class "Host " in Prod.
Do you want to refine some attributes in class Host or do you want to change class type in oid2type_Misc.conf?

Hi,
The sysobjectID of the element I want to add is used to define a Linux Host. So Smarts deal with it as a member of class Host by default.
I can't refine the Class Host because this element has to be member of a new Class.

On My tests I changed the file oid2type_Misc.conf and Smarts could look for a new TYPE of element instead of Host ( TYPE = "MyClass" ).
This new TYPE is the class that I created using dynmodel.

With this change in oid2type_Misc.conf the inverse is occurring with my Linux Hosts: They are discovered as a member of my new Class.
That was expected and now I'm looking for a solution.

Your question is my problem. I cannot do any of the options you asked.
The third option is do not change oid2type_Misc.conf and tell Smarts to "convert" the class of the element to my new class during the discovery process.
I don't know how to do this third option.

You lost me as well.

Are you saying you cannot change the Linux SysOID to a different class assignment than "Host" in production because you have other existing Linux devices which must remain as "Host"? Or are you saying that you made the change in the oid2type files but it does not appear to be taking effect?

If you have made the changes, reloaded config, and are not seeing the devices re-classed it is most likely because they have not been rediscovered since the hanges were implemented.

If your problem is that you only want a subset of Linux devices to be re-classed into your new class, then you will have to utilize a discovery hookscript to perform additional checks and assign the class accordingly.

Yes!!!



It is what I want. But I don't know how to do.

Hi Gabriel,

this is not really possible, right now, out of the box. You can do some stuff using the post discovery feature, but this is difficult to do (lots of ASL, use of "no so documented" methods, ...) and to support.
Depending of your needs, you may have some alternative: you won't have a different class for your system, but you can still have the specific instrumentation. Using the post discovery feature, based on some parameters, you can create the instrumentation and attached them to the associated components of your system (in the topology). But this really depends on what you want to achieve.

--Fred

=== Monitor your Smarts environment with APG Smarts Health Report Pack ===
Frederic Meunier
Solutions Watch4Net Inc
APG (performance management) & Smarts InCharge (fault management) integration
http://www.watch4net.com

Hi Fred,

I will think what to do.

Anyway, as I said before, we already asked the vendor of the equipment for a updated Firmware of the equipment whith a different SysObjectID.

The solution will be wait for the firmware update.

But if anyone have any other tip, please post here...

Thanks.

Gabriel