This FAQ provides answers to common questions about Grandstream network switches across the full lineup, from plug-and-play models to advanced managed switches, including Unmanaged, Layer 2 Lite, Layer 2+ / Pro, Layer 3, and Aggregation categories.
Getting Started & Switch Categories
Grandstream switches are grouped by how much control and scalability you need, from simple plug-and-play to full managed switching:
- Unmanaged (e.g., GWN770x / GWN770xP / GWN770xM): Plug-and-play, no config.
- Layer 2 Lite (e.g., GWN771x(P), GWN772x(P), incl. GWN7710R): Basic management for small networks.
- Layer 2+ / Pro (e.g., GWN780x, GWN780x Pro): Advanced Layer 2 control and scalability.
- Layer 3 (e.g., GWN781x, GWN782x): Adds routing features.
- Aggregation (e.g., GWN783x): High-capacity core/backbone switching.
Choose an Unmanaged switch if you only need to add Ethernet ports and want plug-and-play operation with minimal setup. Choose a Managed switch if you need more control, visibility, or the ability to apply network rules and policies across ports and connected devices. As a general rule, if you’re supporting multiple users, departments, locations, or business-critical services, a managed switch is the safer long-term choice.
Layer 2 Lite Managed switches are designed to provide essential managed-switch functionality for smaller environments while keeping configuration simpler and hardware requirements modest. Layer 2+ / Pro Managed switches are built for larger or growing networks that need more scalability, higher capacity, and more advanced control. If the network is expected to expand, or you need more advanced enterprise-style capabilities, Layer 2+ / Pro is typically the better fit.
Choose a Layer 3 switch when your network design requires routing capability within the switching layer, such as routing between different network segments at the switch level. If your network is simple and routing is handled by a router/firewall, a Layer 2 / Layer 2+ switch is often sufficient. Layer 3 becomes more relevant as segmentation and network scale increase.
An Aggregation switch is typically used as a core or distribution switch. Its main job is to connect multiple switches together and handle heavier “backbone” traffic between parts of the network. In most designs, access switches connect end devices, while the aggregation switch concentrates uplinks and provides higher-capacity switching at the center of the network.
Some key factors to consider:
- PoE: If you’re powering APs/phones/cameras, check PoE support and the total PoE budget.
- Ports & uplinks: Size ports for today + growth; choose uplinks (RJ45/SFP/SFP+) that match your backbone speed.
- Management needs: Unmanaged for simple expansion; managed if you need VLANs, QoS, monitoring, or better control.
- Performance: Match the switch to your traffic (VoIP, cameras, many users, file transfers).
- Form factor: Desktop vs rack, fanless vs fan-cooled, and where it will be installed.
Deployment & Installation
Use an order that prevents loops, avoids surprise outages, and makes issues easy to spot.
- Mount/place the switch and ensure ventilation (and grounding for outdoor models).
- Connect the uplink first to the router/firewall/core switch.
- Power on and let it fully boot, then confirm basic LEDs/link status.
- Connect endpoints gradually in batches so problems are easier to isolate.
- Connect PoE devices last, ideally one-by-one to catch PoE budget/device issues early.
- Final check: confirm expected link speeds and make sure no accidental loops exist.
If your computer is connected to the same network as the switch, you can open the switch Web UI using a local hostname based on its MAC address:
- Locate the switch MAC address on the device label or packaging.
- In your browser, enter the following format:
https://gwn_<MAC>.local
Important formatting:
- Enter the MAC address without colons or dashes
- Use lowercase characters
Example (MAC: ec74d71d291e): Open: https://gwn_ec74d71d291e.local/
Use the switch’s default management IP and set a temporary static IP on your PC.
- Connect your PC to the switch (any RJ45 port).
- Set a static IP on your PC (example: 192.168.0.10 / 255.255.255.0).
- Open a browser and go to http://192.168.0.254.
The default login uses:
- Username:
admin - Password: a random, unique default password printed on the device MAC label/tag (often on the switch itself or the packaging).
Yes. Grandstream managed switches are designed to support desktop placement and 19-inch standard rack mounting.
Managed models come in two physical form factors:
- Standard (full-width) models: These mount directly into a 19-inch rack using the standard rack brackets included with the switch.
- Compact (small-size) models: These also support 19-inch rack mounting, but they typically use extended rack mounting brackets/kits so the smaller chassis can fit properly in a standard 19-inch rack.
Console access is available on managed models (Layer 2+/Pro, Layer 3, and aggregation). Unmanaged and Layer 2 Lite models do not include a console port.
Use it when:
- You don’t know the switch IP (or DHCP isn’t available)
- Web UI/SSH isn’t reachable
- You need initial setup or recovery without relying on the LAN
Note: Console connections use 115200 baud (default).
Access & Management
MGMT VLAN is the VLAN the switch uses for management access (Web UI/CLI). The switch’s management IP lives on that VLAN, so you can only reach it from the same VLAN (or from another VLAN that is routed and permitted).
How to keep the management IP stable:
- Recommended: Set the switch to DHCP on the MGMT VLAN, then create a DHCP reservation on the router/DHCP server (same IP every time, easier to manage).
- Alternative: Set a Static IP on the switch (useful if DHCP isn’t available). The router won’t “override” it because the switch stops using DHCP.
Quick checks before changing MGMT VLAN/IP: Make sure the MGMT VLAN is allowed on the uplink, and the IP/subnet/gateway match that VLAN, or you’ll lock yourself out.
You can manage GWN switches locally on the device, or through a centralized platform for one or multiple sites.
- Local management: Web UI (browser). (Console is available on some managed models for recovery/troubleshooting.)
- Centralized management: GDMS Networking (cloud), GWN Manager (on-premises), or GCC60xx (local controller).
Use the fastest methods first, then fall back to network discovery.
- MAC-based access (easy): From a PC on the same LAN, open https://gwn_<MAC>.local (use the switch MAC without colons).
- If managed centrally: In GDMS Networing / GWN Manager / GCC Device, open the switch details page to see the current IP.
- Check DHCP/router leases: Look in the router/DHCP lease table and match the switch by MAC address.
- If still unknown: Use an IP scan on the same subnet or check the upstream device’s neighbor/LLDP table (if available).
Yes. From the switch’s local Web UI, you can manage accounts under: System → User Management
You’ll typically see the built-in admin account as Administrator, and you can add more users with limited roles.
User levels:
- Administrator: Full access to all switch settings and actions. This is the default account level used when you log in with the factory/default credentials.
- Operator: Can perform most configuration and operational tasks, but factory reset is not allowed.
- Monitor: View-only access. Can view information and status, but cannot make changes.
Why this matters: Use Administrator for trusted admins only, Operator for day-to-day IT operations and Monitor for read-only monitoring or audits.
In most cases, configure it from the management platform. It acts as the primary configuration point and applies settings to the switch, helping keep your network consistent.
Use the platform for: policies, bulk changes, and day-to-day configuration. Local changes may be overwritten when the platform syncs.
Use the local Web UI for: troubleshooting, emergency access when the platform isn’t reachable, and rare cases where a feature is available locally before it appears in the platform.
Best practice: Platform = primary configuration, Local UI = status checks and exceptions.
Switching Features
Yes. On supported managed models, Grandstream switches can bundle multiple physical ports into one logical link (Link Aggregation/LAG).
What it helps with:
- More uplink capacity: higher total throughput than a single cable.
- Redundancy: traffic can continue if one link in the bundle fails.
Common uses: switch-to-switch uplinks (access to distribution/core) and switch-to-server/NAS connections with multiple NICs.
Note: Configure aggregation on both ends of the link (switch and upstream switch/server) to avoid unstable links or traffic issues.
Grandstream managed switches include loop-protection features designed to keep the network stable in two common scenarios: planned redundancy and accidental cabling mistakes.
- For planned redundancy (multiple links between switches): Use Spanning Tree. It prevents switching loops in networks with redundant switch-to-switch connections by allowing only the correct path to forward traffic while keeping backup links available.
- For accidental loops (miswiring at the edge): Use Loopback Detection on access/user-facing ports. It helps protect the network when someone unintentionally creates a loop (for example, patching two wall ports together or plugging a cable from one port back into another).
Recommended approach: In most deployments, enable Spanning Tree for switch-to-switch links and redundancy, and enable Loopback Detection on edge/access ports as an added safety layer. This reduces the chance that a single loop event will impact the entire LAN.
Yes. Supported managed GWN switches can apply a Voice VLAN to ports so IP phones are separated from data devices (useful when a phone and PC share the same port).
Common methods include:
- Auto Voice VLAN: automatically treats the port as voice-capable and applies the Voice VLAN to connected phones.
- OUI (MAC prefix) detection: identifies phones by vendor MAC prefix and applies the Voice VLAN automatically.
- LLDP / LLDP-MED: helps with phone discovery and voice-related port information in enterprise VoIP setups.
Tip: For most deployments, start with Auto Voice VLAN, then use OUI or LLDP/LLDP-MED if you need more control or better discovery.
On PoE-capable models, you can manage PoE per port from the switch Web UI (PoE settings) to control how power is delivered and protect the total PoE budget.
Common controls:
- PoE Mode: keep Auto for normal operation; use Off/Shut Down to disable PoE on a port.
- Per-Port Power Limit: caps the maximum power a single port can draw.
- Power Priority: sets which ports stay powered first if the total PoE budget is exceeded.
- PoE Schedule (optional): turns PoE on/off by time for energy saving or planned reboots.
Tip: Use Auto + per-port limits + priorities to prevent one device from taking the full budget.
Port Auto Recovery automatically brings a port back up after the switch disables it due to a protection event (for example loop/storm protection or similar safeguards).
Enable it for: edge ports connected to phones, APs, cameras, or user devices, especially at remote sites where you want automatic recovery from temporary issues.
Avoid it on: uplinks/trunks. If an uplink is being disabled, it usually indicates a real misconfiguration or loop that should be fixed, not retried.
Delay setting tip: use a short delay for one-time issues, and a longer delay if the port keeps triggering to reduce flapping.
Note: If the same port keeps disabling, it’s an indicator of an underlying issue. Check events/logs and address the cause.
No. GWN Manager and GDMS Cloud do not support stacking on the switches. To configure stacking, you need to access the switch directly.
Maintenance & Troubleshooting
On the switch Web UI, go to Backup & Restore page. Use the Back Up buttons to generate a config file, and use Upload Configuration File to restore it.
To back up, click one of these two options:
- Back Up Running Configurations: backs up the settings currently active on the switch (use this in most cases).
- Back Up Saved Configurations: backs up the saved/startup configuration stored on the switch (use this if you want the stored baseline, not the current running state).
After you click Back Up Running Configurations or Back Up Saved Configurations, a .cfg backup file will be created in the Backups list. Download that file to your local machine and save it somewhere safe (so you can upload it later if you need to restore).
To restore, stay on the same Backup & Restore page, go to Restore Configuration, click Upload Configuration File, and upload your saved .cfg file.
Use backups before firmware upgrades, before major changes (VLANs, trunks, routing, ACLs, QoS, PoE), before factory reset or hardware replacement, and after initial setup as a “known-good” baseline.
Port Mirroring (SPAN) copies traffic from one or more ports (or a LAG) to a monitor port so you can capture and analyze it with a tool like Wireshark, without disrupting the live connection.
Common uses: troubleshooting slow/unstable connections, verifying traffic flow, VoIP capture (SIP/RTP), or investigating unusual traffic.
Note: Use a dedicated monitor port and make sure it can handle the mirrored traffic rate (otherwise captures may drop packets). Enable SPAN only when needed, and treat captures as sensitive data.
Use a reset when you’re locked out (wrong IP/VLAN), a misconfiguration breaks connectivity, or you need a clean baseline.
Reset options:
- Web UI factory reset (preferred): Use this if you can still log in. It’s safer because you can back up the configuration first.
- Physical RESET button (last resort): Use this only if you can’t access the Web UI at all.
Before resetting (quick checks): If possible, back up the config and confirm how you’ll regain access after reboot (management IP/VLAN, MAC-based access, or console).
GWN switches support several upgrade methods depending on whether you want a one-time manual upgrade, a reusable network method, or centralized management.
Common upgrade options:
- Manual upload (local file): Upload firmware from your PC. Best for a specific version (beta, pinned, rollback).
- Firmware server path (network upgrade): Point the switch to a firmware URL/server so it downloads the file. Best for repeatable upgrades across multiple switches.
- DHCP option provisioning (if used in your network): DHCP can provide the firmware server/path automatically. Best for structured deployments that already use DHCP provisioning.
Firmware source: Grandstream firmware portal: https://www.grandstream.com/support/firmware
Note: If the switch is adopted in GDMS / GWN Manager, upgrades can also be done from the platform (often preferred for multi-switch deployments).
This usually happens because the management interface moved to a different VLAN/subnet, or the uplink no longer carries the management VLAN.
- Basic checks: Confirm power and link LEDs, and that your PC is on the correct port/path.
- Try MAC-based access (same LAN):
https://gwn_<MAC>.local(MAC without colons). - If adopted: Check GDMS / GWN Manager / GCC for the switch status and current IP.
- Confirm you’re on the right network: If you changed MGMT VLAN or management subnet, your PC must be in that VLAN/subnet (or routed to it and allowed).
- Verify the uplink/trunk: Make sure the MGMT VLAN is carried correctly (tagging matches, correct PVID/native VLAN, VLAN not removed from allowed list).
- Find the new IP: Check the DHCP/lease table by MAC, or scan the subnet and match by MAC/vendor.
- Console (managed models): Use console to view/fix management VLAN/IP and trunk settings (console doesn’t need an IP).
- Last resort: Factory reset only if you accept losing the config, then reconfigure or restore a saved backup after access is restored.
Note: Back up before major VLAN/IP changes so you can restore quickly once access is recovered.