Lumeta provides four different types of attributes:
Kind of Attributes
|1||Native||Native, out-of-the-box attributes||target, trusted, known, dnsname, ASname||true||false||false|
|2||Discovered||Attributes that get inserted as part of device processing||sysDesc, cifsName, sysName||false||false||false|
|3||Zone-level||Zone-level custom labels||Often used to configure locations by CIDR (usEast, usWest, EMEA)||false||true||false|
|4||Device-level||Device-level custom labels for devices at the granular level||customA, customB, customC||false||true||true|
To learn about zone- and device-level custom device attributes, watch this demo. For the best playback quality in YouTube, please choose HD quality playback (Settings > Quality > HD).
Adding Device Attributes
Device-level attributes can be added in bulk, or input manually.
- Bulk - See Overwriting vs. Appending Custom Attributes to learn how to add device attributes by file import.
- Individual - See Adding & Managing Labels & Custom Attributes to learn how to add device attributes individually, by hand.
To add one or several attributes to particular devices you select, Lumeta recommends that you use the form.
Lumeta supports an individual device having multiple attribute values for the same attribute name. For example, a single "Location" attribute, can have multiple attribute values associated with it:
- 10.0.0.0/8 Location = US
- 10.8.0.0/16 Location = New York
- 10.8.16.0/24 Location = 1 Penn Plaza
Attempting to create an attribute that already exists as a different kind may yield inconsistent behavior. For example . . .
- Adding a Zone-level attribute with the same name as an existing native or discovered attribute appears to succeed but the new attribute does not show up on the Zones | Custom Attributes screen (which is filtered to show userDefined attributes only)
- Adding a Zone-level attribute with the same name as an existing Device-level attribute results in hybrid behavior (you can seeming edit the Zone-level attribute on the Device Details page).
Enhancements to this are planned for development.
Automatic CIDR Correction
In Lumeta 3.3.4 and later releases, invalid CIDRs are made valid upon import to the Lumeta system. If you were to upload a text (.txt) file of custom attributes including the CIDR "10.7.100.0/16" the Lumeta system would automatically change it to "10.7.0.0/16".
Custom attribute lists show checkboxes. To select all in a range, Click the first record, then SHIFT+Click the last record in the range. Press CTRL+Click to clear any checkboxes in the range.
Maps can be highlighted by custom attribute and support having multiple values for the same attribute. See Grouping & Highlighting by Custom Attribute for more.