Quick Overview

The MetaData page in zWAN allows administrators to define and manage device-specific configuration templates linked to an Edge Controller’s Product ID or Model Number. Metadata entries are used during onboarding to auto-populate critical configuration fields such as WAN settings, WiFi profiles, certificates, and more. This helps streamline deployment and ensures consistency across similar device models.

How to Use This Feature in the UI

1. Navigate to the MetaData section in the zWAN Director UI.
2. Review existing metadata entries, which are listed by:
   • Product ID
   • Model Number
   • Name
3. To Search for Metadata:
   • Use the search bar at the top-left to filter metadata by Product ID, Name, or Model Number.
4. To Create Metadata:
   • Click Create Metadata in the top-right corner.
   • Select the relevant Model Number to load the appropriate form.
   • Enter the required data (WAN config, WiFi, certs, etc.) and click Create.
5. To Import Metadata:
   • Click Import Metadata.
   • Browse to select a valid CSV file.
   • Optionally check Overwrite to replace existing entries with matching keys.
   • Download a sample format if needed before importing.
   • Click Import to upload the data.
6. To Export Metadata:
   • Click Export Metadata to download all current entries to your local system in CSV format.
7. To Delete Metadata:
   • Use the checkboxes to select one or more entries from the list.
   • Click Delete Selected to permanently remove them from the system.
8. To Edit Metadata:
   • Hover over any row and click the Edit icon (pen) to open the form.
   • Modify the values as needed and save your changes.

Concepts & Use Cases

• Automated Configuration: Metadata allows Edge Controllers to be provisioned with default settings immediately upon onboarding, reducing manual effort.
• Model-Based Consistency: Ensure that devices with the same model receive consistent configuration profiles.
• Bulk Updates via Import: Use the CSV import function to rapidly update or register multiple metadata entries.
• Pre-Staging: Define metadata before device arrival so onboarding can proceed without delay.

Troubleshooting & FAQs

• Why doesn’t a device receive the expected settings during onboarding?
  Ensure the correct Product ID is matched to the metadata and that the metadata entry is complete and not corrupted.
• Can I edit metadata after a device is onboarded?
  Yes, but changes will only take effect if the device is re-onboarded or the policy is re-applied manually.
• What happens if I import a file with missing fields?
  The import may fail or result in incomplete configurations. Always validate CSV data before importing.
• Is it possible to manage metadata per device rather than per model?
  Metadata is generally model-based, but key-value fields can be used to store device-specific tags.