Monitoring idrac (snmp) and host through and agent

[rubeel]

I am trying to monitor a host with an agent and then its Dell idrac using SNMP but i run into the following error

Cannot inherit LLD rule with key "net.if.discovery" of template "DELL PowerEdge R740 by SNMP - Cleaned" to host "servername", because an LLD rule with the same key is already inherited from template "Linux by Zabbix agent active"

how can iavoid this, since the discovery is needed by both and the conflict forced me to have seperate idrac hosts and agent hosts.

[Viktors Fomics]

Hello

As you already figured it out, the key uniqueness is required here, therefore it would make sense to clone this template and adjust this LLD rule's key to an unique one - then the new cloned template would have the unique key and could be used.

[cyber]

Hello

As you already figured it out, the key uniqueness is required here, therefore it would make sense to clone this template and adjust this LLD rule's key to an unique one - then the new cloned template would have the unique key and could be used.

No it would have no sense... How that clone would help? How would you make that key unique, if it has no parameters?
--------------
add "Alias=net.if.discovery[*]:net.if.discovery" to agent config... then you can add whatever you want as parameter to make them unique.. Without it is kind of difficult to make that key unique as it does not really have parameters...
Helps with other discovery items also.. vfs.fs.discovery, system.cpu.discovery etc

[Brewer]

I'm just going to spit out a bunch of things that I can think of and hopefully one helps... I'm a Zabbix Noob though so take everything with a grain of salt because this is all based on the limited self taught knowledge I've gained so far.

• IDEA 1

1. Temporarily change both keys of the Discovery rules to if.net.discovery.dell and if.net.discovery.linux in their respective templates.
2. Link them to the server. Which you should now be able to do since there is no longer a unique key collision.
3. Unlink them immediately afterwards (without using the "Unlink and Clear", just use the "Unlink").
4. Make a new item on the server itself that uses the original "if.net.discovery" key.
5. Within the server (not templates), change the "Type" for both Discovery rules, "if.net.discovery.dell" and "if.net.discovery.linux", to "Dependent item".
6. Point the Dependent Item at the Master Item. The "if.net.discovery" that you created in step 4.
7. Success??? idk

• IDEA 2

Depending on whether this method works at all, you could also join these templates into a new template using the same process. Then you would be able to reuse it for the next server.
______________________
NOTE:
Doing either IDEA 1 or 2 would mean that you aren't gathering the data twice as per going the Alias route mentioned in the comment above. You would just be providing the same raw data from our Master Item to both.
If you don't care about grabbing data twice then Cyber's suggestion would probably be the easiest route... Here are some other ideas of mine that would create duplicates in case you want more options.
______________________

• IDEA 3

Make a new host with a unique name that points to the same server? Have one called ServerA and the other ServerA-idrac. Then add 1 template to each.

• IDEA 4

You could possibly apply 1 template to the server, let it do it's discovery process which populates all the "Prototype" Items, Triggers, etc. into actual Items, Triggers, etc. on the host. After everything is populated... Unlink (not "Unlink and Clear") the template. Followed by deleting that Discovery rule (I'm assuming it's called "Network Interface Discovery") from the host. THEN apply the 2nd template to the server. Unless the Prototype's Keys conflict, you should be fine???
______________________
Maybe... idk... Again, just thinking out loud. Hope this helps someone at least.