Label Key Schema
Guidelines governing column names
-
There must be one column with a header “IP” in the label key schema. Additionally, there must be at least one other column with attributes for the IP address.
-
The column “VRF” has special significance in the label schema. If provided, it should match the root scope to which you upload the labels. It’s mandatory when uploading the CSV file using the Scope Independent API.
-
Column names may contain only the following characters: Letters, numbers, space, hyphen, underscore, and slash.
-
Column names cannot exceed 200 characters.
-
Column names cannot be prefixed with “orchestrator_”, “TA_”, “ISE_”, “SNOW_”, nor “LDAP_” since these can conflict with labels from internal applications.
-
The CSV file should not contain duplicate column names.
Guidelines governing column values
-
Values are limited to 255 characters. However, they should be as short as possible while still being clear, distinctive, and meaningful to users.
-
Keys and values are not case sensitive. However, consistency is recommended.
-
Addresses appearing under the “IP” column should conform to the following format:
-
IPv4 addresses can be of the format “x.x.x.x” and “x.x.x.x/32”.
-
IPv4 subnets should be of the format “x.x.x.x/<netmask>”, where netmask is an integer from 0 to 31.
-
IPv6 addresses in the Long format (“x:x:x:x:x:x:x:x” or “x:x:x:x:x:x:x:x/128”) and the Canonical format (“x:x::x” or “x:x::x/128”) are supported.
-
IPv6 subnets in the Long format (“x:x:x:x:x:x:x:x/<netmask>”) and the Canonical format (“x:x::x/<netmask>”) are supported. Netmask must be an integer from 0 to 127.
-
The order of the columns does not matter. The first 32 user-defined columns will automatically be enabled for label. If more than 32 columns are uploaded, up to 32 can be enabled using the checkboxes on the right-side of the page.