Skip to content
  • There are no suggestions because the search field is empty.

How do I set up VLANs on the Stratix 5800 switch?

This video describes configuring VLANs (Virtual Local Area Networks) on the Stratix 5800 switch. It covers creating VLANs, assigning ports to VLANs, and verifying configurations. The demo helps network engineers, automation technicians, and IT staff quickly set up logical network segmentation using the Stratix 5800’s interface.

 

Prerequisites & Requirements

Before you begin, make sure you have:

  • Access credentials (username/password) to the Stratix 5800 management interface

  • Network connectivity to the switch (via Ethernet or console)

  • A PC on the same subnet (or a management VLAN)

  • Knowledge of VLAN IDs & intended port assignments

Steps to Configure VLANs on Stratix 5800

  1. Log in to the Switch
    Access the web UI (or CLI) of the Stratix 5800 using your credentials.

  2. Create VLAN IDs
    Navigate to the VLANs section and add new VLANs (e.g. VLAN 10, VLAN 20).
    Give them descriptive names (e.g. “Production”, “Control”) for easier identification.

  3. Assign Ports to VLANs

    • Select each port you want to include in a VLAN

    • Set its VLAN membership mode (e.g. access, trunk)

    • Assign the untagged VLAN (the default VLAN for untagged frames)

    • For trunk ports, configure tagged VLANs (if multiple VLANs will traverse that port)

  4. Set Up Inter-VLAN (Layer 3) Routing (if supported/needed)
    If you need devices in different VLANs to communicate, enable routing or set up a Layer 3 interface and static routes or routing protocols as needed.

  5. Verify Configuration

    • Use status or summary pages to view active VLANs and port assignments

    • Run ping tests between devices in same VLAN and across VLANs (if routing is enabled)

    • Check LED indicators and port status for link/activity

  6. Save / Apply the Configuration
    Make sure to commit or save the config so changes persist through reboots.

Best Practices & Tips

  • Use descriptive VLAN names to help with future troubleshooting.

  • Limit trunk ports only to those that need to carry multiple VLANs.

  • Use management VLAN separate from data VLANs for security.

  • Document VLAN assignments (which port = which VLAN) for your site’s network map.