Hudu icon

Hudu

Interact with Hudu REST API

VLAN Zone → Create

AI-generated

Overview

This node operation creates a new VLAN Zone in the Hudu system. It is useful for network administrators or IT professionals who need to organize and manage VLAN zones within a company. For example, creating VLAN zones with specific VLAN ID ranges and associating them with a company helps in network segmentation and management.

Use Case Examples

  1. Create a VLAN Zone named 'Office VLAN' with VLAN ID ranges '100-200,300-400' for a specific company.
  2. Create a VLAN Zone with an optional description and set it as archived or active.

Properties

Name Meaning
Name Human-readable VLAN zone name, required for identifying the VLAN zone.
VLAN ID Ranges Comma-separated list of numeric VLAN ID ranges (e.g., '100-500,1000-1500'). Each range must be within 1-4094 and the start must be less than or equal to the end, required for defining the VLAN IDs included in the zone.
Company Name or ID The company to associate with the VLAN zone. Accepts a company name or numeric ID, required to link the VLAN zone to a specific company.
Additional Fields Optional additional fields such as 'Archived' (boolean to archive or activate the VLAN zone) and 'Description' (optional text description).

Output

JSON

  • id - Unique identifier of the created VLAN zone.
  • name - Name of the created VLAN zone.
  • vlan_id_ranges - The VLAN ID ranges assigned to the VLAN zone.
  • company_id - The ID of the company associated with the VLAN zone.
  • archived - Indicates if the VLAN zone is archived.
  • description - Description of the VLAN zone, if provided.

Dependencies

  • Requires an API key credential for Hudu REST API authentication.

Troubleshooting

  • Ensure the VLAN ID ranges are correctly formatted and within the valid range (1-4094).
  • Verify that the company ID or name exists and is accessible via the API.
  • Common errors include invalid VLAN ID ranges, missing required fields, or authentication failures. Check API credentials and input data for correctness.

Links

Discussion