IBM Support

Device not instantiated to custom aoc file

Troubleshooting


Problem

Discovery completes with custom aoc file and gui does not reflect the desired aoc file name as 'classname'. Instantiated to wrong name, or wrong icon.

Environment

aoc files customized in $PRECISION/aoc

Resolving The Problem

When creating a custom aoc file the device must match the parameters of the instantiate_rule in aoc file. But also must have passed the instantiate rules of the super_class of the aoc file.

For example


active object 'Cisco3567'
{
super_class = 'CiscoNonRoutingSwitch';

instantiate_rule = "EntityOID = '1.3.6.1.4.1.9.1.5678'";

visual_icon = 'Switch';
};

To be instantiated as Cisco3567, this OID must also need to pass through the CiscoNonRoutingSwitch.aoc file. Review that file and make sure there was a successful match in that file also.

[{"Product":{"code":"SSSHRK","label":"Tivoli Network Manager IP Edition"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"3.9","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21627224