Label types
You can associate two types of labels: Nokia pre-defined labels and user-configured custom labels. Fabric Services System comes with a series of predefined labels that you can associate with fabric items. If these labels do not meet your specific tagging criteria, you can also create new labels in the Label Factory.
Nokia pre-defined labels
Nokia pre-defined labels are a basic set of grouping labels for common use. Some pre-defined grouping labels have a built-in priority to resolve when conflicting configuration profiles are applied to it.
Pre-defined fabric intent labels are key and value pairings that can be applied to fabric intents and workload VPN intents. Nokia has defined these labels for use in common tagging scenarios. Pre-defined labels lists the Nokia pre-defined labels.
| Label key | Value | Description |
|---|---|---|
| Node-type | T1_LEAF | Identifies all T1 nodes in a fabric. It is dynamic, so new T1 nodes can join this group. |
| T2_SPINE | Identifies all T2 nodes in a fabric. It is dynamic, so new T2 can join this group. | |
| T3 | Identifies all T3 nodes in a fabric. It is dynamic, so new T3 nodes can join this group. | |
| T4 | Identifies all T4 nodes in a fabric. It is dynamic, so new T4 nodes can join this group. | |
| T5 | Identifies all T5 nodes in a fabric. It is dynamic, so new T5 nodes can join this group. | |
| Link-type | T1_ISL_T2 | Identifies inter-switch links between T1 and T2 nodes. This label is fabric-scoped. It is dynamic so new ISLs can join this group. |
| T2_ISL_T3 | Identifies inter-switch links between T2 and T3 nodes. This label is fabric-scoped. It is dynamic so new ISLs can join this group. | |
| T3_ISL_T4 | Identifies inter-switch links between T3 and T4 nodes. This label is fabric-scoped. It is dynamic so new ISLs can join this group. | |
| T4_ISL_T5 | Identifies inter-switch links between T4 and T5 nodes. This label is fabric-scoped. It is dynamic so new ISLs can join this group. | |
| EDGELINK | Identifies all edge links. This label is fabric-scoped. It is dynamic so new edge links can join this group. |
User-configured custom labels
User-configured custom labels allow you to group entities on which configuration profiles can be applied. You can define labels that broadly identify fabric elements, such as by geographical region. You can also define labels to identify highly specific elements, such as a physical location within a DC.
Every custom label has two parts:
- a key, which identifies the type of information the label contains
- a value, which is a specific value appropriate to the label's type
When a label is created, the key and value must be assigned, along with a description to describe the purpose of the label. You may want to define a label to identify physical fabric elements found in a specific location. When creating the key-and-value pairing, you can identify the general location as the label key and a specific region indicator as the value.
Fabric Services System provides some pre-defined label keys that you can use when configuring a custom label. These pre-defined label keys identify common elements of network fabrics that you may want to label and can help to guide you when you create new labels. Consider using any of the label keys as a starting point when you configure a custom label. Pre-defined label keys lists the pre-defined label keys. Nokia recommends using these label keys to ensure consistent naming conventions across fabric elements in your network.
| Label key | Description | Examples |
|---|---|---|
| ACL-GRP | Use to identify a group of switches, downlink ports, or a group of sub-interfaces used to apply ACL policies on the group. | ACL-GRP-1, ACL-GRP-WEB, ACL-GRP-APP, ACL-GRP-DB |
| AZ | Use to identify different availability zones (AZs) in a data center. By dividing the network infrastructure inside a DC into multiple fault boundaries, application teams can place compute across AZs and achieve higher availability to their distributed applications. | AZ-1, AZ-2 |
| Building | Use to identify individual buildings that make up a data center. If the data center exists in a single building, use the DC label type instead. | Building-A, Building-B |
| DC | Use to identify specific data centers. | DC-1, DC-Europe, DC-Atlanta |
| Edge-Link | Use to identify downlink ports to be used in a workload design. | Edge-1, Edge-A |
| Link-type | Use to identify a group of links of a specified type. | ISL-1, ISL-A |
| Maintenance | Use to identify nodes to be part of a collective maintenance action; either upgrade or node replacement. | Maintenance-upgrade1, Maintenance-replacement1 |
| Node-type | Use to identify a group of nodes of a specified type. | Node-1, Node-A |
| QOS-GRP | Use to identify a group of switches, downlink ports, or a group of sub-interfaces used to apply QoS policies on the group. | QOS-GRP-1, QOS-GRP-WORKLOAD1, QOS-GRP-MGMT, QOS-GRP-STORAGE |
| Region | Use to identify a group of resources on a per customer region. A region is a geographical area location, such as a city. | Region-A, Region-EAST, Region-Dallas |
| Room | Use to identify specific rooms within a data center. | Room-A, Room-B |
| Tenant | Use to identify a group of switches, downlink ports, or a group of sub-interfaces that describe a tenant in a DC. | Tenant-1, Tenant-ABC |
For example, you can create a label to identify fabric elements located in particular Availability Zones (AZs). When entering the key-and-value pairing, you could enter AZ as the key, and Zone1 as the value. The label can be assigned to all fabric elements in this specific zone. You can then create additional availability zone labels with the same AZ key, but define additional values to specify additional zones, such as Zone2, Zone3, and so on.