Tags and organization
Tags provide flexible categorization within inventories. Apply them to inventories and nodes for filtering and organization.
Use tags
Apply tags to inventories
Tag inventories to categorize them, for example:
- Environment tags: production, staging, development
- Region tags: us-east, us-west, emea, apac
- Function tags: core-network, edge-network, security
Apply tags to nodes
Tag nodes for filtering and targeted action execution, for example:
- Location tags: building-a, datacenter-1, site-chicago
- Role tags: core, distribution, access
- Status tags: active, maintenance, decommissioned
Filter by tags
Use tags to filter inventories and nodes in the Inventory Manager UI:
This helps you quickly find specific resources in large deployments.
Key behaviors
Platform 6.7+ Configuration Manager can use Inventory Manager tags to build device groups:
- Build device groups from tags: When you create a device group or add devices to one, you can select an inventory and its tags to find matching devices. See Manage device groups.
- View tags on device details: The Configuration Manager device details page shows the Inventory Manager tags applied to each device.
- Group membership is a snapshot: A device group holds the devices that matched when you saved it. Later tag changes in Inventory Manager don’t add or remove devices from the group.
- Access control applies: Configuration Manager shows only the inventories and tags that your Inventory Manager permissions allow.
In Platform 6.6 and earlier, Configuration Manager doesn’t see Inventory Manager tags, and device groups and tags operate independently.
Duplicate devices across inventories
The same physical device can exist as nodes in multiple inventories. Node names must be unique within an inventory, but the same device can appear in different inventories.
Examples
Different commands for the same device:
Different environments accessing the same devices:
Cross-functional access:
Device naming with duplicates
When using the adapter with device name prefixing enabled, duplicate devices appear with different names in Configuration Manager and command templates:
full-configs::core-switch-1interface-configs::core-switch-1
This prevents confusion about which inventory’s action will execute.
Best practices
Start simple:
- Begin with device-type-based inventories
- Add complexity only when needed
- Validate your approach with a pilot inventory
Plan for growth:
- Consider how your inventory structure scales
- Design for the organization you’ll have in a year, not just today
- Make it easy to add new device types or regions
Use tags consistently:
- Define a tagging taxonomy
- Document what each tag means
- Apply tags consistently across inventories