How works 'Equipment import and link rules'¶
Equipment import and link rules are complex and misconfiguration can seriously hurt your GLPI.
First thing to know¶
The rules engine goal is to detect if a device exists or if it has to be created.
The rule engine is used for:
- network devices
- network printers
Common problems related to the rule engine are:
- duplicated device.
- device pushed in the “Ignored import devices”
The engine stops on the first checked rule.
When these rules are played?¶
It's played in these cases:
- Computer inventory, including ESX servers
- Network discovery
- Network Inventory (switches, printers...)
Port MAC addresses from network switch are not used as criterias
Criteria of a rule¶
The criteria can be either normal or global.
The normal criteria are defined by an information (IP, MAC, etc) and a filter:
- is not
- does not contains
- starting with
- finished by
- regular expression checks
- regular expression does not match
- exists: mean the value exist and not be empty in the inventory come from the agent
- does not exist: mean the value doesn't exist in the inventory come from the agent
- Search GLPI equipement with this status: search in GLPI database if the device exist with value defined
If the device is found, all criteria are checked, this rule is checked and now run the actions
Actions of a rule¶
The actions are defined by:
- FusionInventory link > Link if possible, else create device: if device is found (in case use a global criteria), update this device, else create a new device with itemtype defined in inventory (computer, switches...)
- FusionInventory link > Link if possible, else import denied: if device is found (in case use a global criteria), update this device, else deny creation of device and so is not be imported in GLPI inventory
- FusionInventory link > Import denied