1. Home
  2. Knowledge Base
  3. GWN Manager – On-Premise Network Controller FAQ

AI Documentation Assistant

✨

GWN Manager – On-Premise Network Controller FAQ

This Frequently Asked Questions (FAQ) document provides practical answers and guidance for installing, configuring and operating Grandstream GWN Manager, the on-premise network controller for GWN access points, routers, switches and GCC devices.

It is intended to assist network administrators in planning deployments, managing devices and sites, troubleshooting common issues, and understanding key features such as Wi-Fi and LAN configuration, monitoring, alerts, security and ongoing maintenance.

Product Overview & Architecture

GWN Manager is an on-premise network management platform designed to centrally manage Grandstream GWN access points, routers, switches and GCC devices from a single web-based interface. It is installed on your own server or virtual machine and provides a unified place to configure, monitor and maintain all supported devices across one or multiple sites.

Using GWN Manager instead of configuring each device individually allows you to:

  • Apply and update configurations centrally instead of logging into every device one by one.
  • Use templates, profiles and batch operations to deploy Wi-Fi, VLAN, WAN and other settings consistently across many devices.
  • Monitor device status, clients, bandwidth and performance from a single dashboard and receive alerts when issues occur.
  • Schedule and manage firmware upgrades in bulk, reducing maintenance time and human error.
  • Standardize policies and settings across branches or locations, simplifying day-to-day administration and scaling the network more easily.

GWN Manager is built to manage Grandstream GWN series networking devices, including GWN Wi-Fi access points, GWN routers, GWN switches and GCC convergence devices. It is designed specifically for Grandstream networking products and does not manage third-party hardware.

There is no fixed software limit on the number of devices or sites. Capacity depends on the server resources you allocate (CPU, memory and storage). As a general guideline, a properly sized server can support thousands of devices and tens of thousands of clients, with higher-end hardware recommended for larger deployments.

For detailed hardware sizing examples and recommended server configurations, refer to “GWN Manager – Server Configuration Requirements for On-Premise Deployment” available at:
https://documentation.grandstream.com/knowledge-base/gwn-manager-server-configuration-requirements-for-on-premise-deployment

GWN Manager software is available for free from the Grandstream Support → Tools page, where you can download the latest installation packages and OVA images:
https://www.grandstream.com/support/tools

From this page you can obtain:

  • Installation packages for supported Linux distributions (AlmaLinux 9, CentOS 7, Ubuntu)
  • OVA images for deployment on common virtualization platforms
  • Related documentation such as the Quick Installation Guide

As a general guideline:

Both options provide the same management features; the choice depends on your operating system and virtualization environment.

Both GWN Manager and GDMS Networking are management platforms for Grandstream GWN devices and provide a similar feature set for configuration, monitoring and reporting.

The key differences are:

  • Deployment model
    • GWN Manager runs on your own on-premise server or virtual machine, typically inside a private network.
    • GDMS Networking is a cloud platform hosted by Grandstream.
  • Ownership & maintenance
    • With GWN Manager, you control the server hardware, operating system, backups and updates.
    • With GDMS, Grandstream maintains the infrastructure; you simply log in via browser.
  • Connectivity & data location
    • GWN Manager is ideal when you want management to stay inside your own environment, or when Internet access is limited.
    • GDMS is convenient when you want easy remote access to multiple sites without managing servers or VPNs.

In short, choose GWN Manager when you need an on-premise controller with full local control, and GDMS Networking when you prefer a cloud-hosted service with no server to maintain.

GWN Manager can run entirely on a local network. As long as the server can reach your GWN access points, routers, switches and GCC devices over IP, it can manage them without Internet access.

An Internet connection is still recommended for things like time synchronization, downloading firmware files, remote access and sending email or external notifications, but it is not required for day-to-day local management and operation.

GWN Manager is free to use. There are no per-device licenses, subscriptions or recurring management fees required to manage supported Grandstream devices with GWN Manager.

You only need to provide your own server or virtual environment that meets the hardware and OS requirements. Once installed, you can add supported devices without purchasing additional management licenses.

In a typical deployment, GWN Manager sits on the management network as a server or virtual machine. It communicates with your Grandstream APs, routers, switches and GCC devices over the LAN to push configuration and collect statistics.

Your existing routers, switches and VLAN design remain responsible for forwarding user traffic. GWN Manager does not replace your gateway or core switch; it provides centralized configuration, monitoring, firmware management and troubleshooting tools for Grandstream devices within that topology.

Installation, Deployment & Access

GWN Manager can be deployed either as a native Linux installation or as a virtual machine using the official OVA image. The choice depends on how you normally run services in your environment:

  • Use the Linux package if:
    • You already have a supported Linux server (AlmaLinux 9, CentOS 7 or Ubuntu).
    • You prefer to manage GWN Manager like any other application on your existing OS.
    • You want direct control over the underlying OS, services and resources.
  • Use the OVA virtual machine if:
    • You run most workloads on a hypervisor and prefer VM-based deployments.
    • You want a quicker, more standardized deployment with the OS preconfigured.
    • You need an easy way to snapshot, back up or move the controller between hosts.

You can download both the Linux packages and OVA images from the Grandstream Support → Tools page:
https://www.grandstream.com/support/tools

For detailed steps, use:

Both deployment methods provide the same GWN Manager features; it’s mostly a question of whether you prefer a bare Linux server or a virtual appliance.

GWN Manager is a Linux-based on-premise platform. The official quick installation guide specifies the following example server requirements for typical deployments:

  • Supported operating systems (package install):
    • CentOS 7
    • AlmaLinux 9
    • Ubuntu (supported versions listed in the Quick Installation Guide)
  • Example hardware sizing (from the Quick Installation Guide):
    • For up to 200 devices / 2,000 clients
      • CPU: Intel® Core™ i3-3240 or above
      • RAM: 4 GB or above
      • Storage: 250 GB (SSD recommended, depending on retained data size)
    • For up to 3,000 devices / 30,000 clients
      • CPU: Intel® Xeon® Silver 4210
      • RAM: 16 GB or above
      • Storage: 250 GB (SSD recommended, depending on retained data size)

For larger deployments, Grandstream provides an extended “GWN Manager – Server Configuration Requirements for On-Premise Deployment” document with guidance for managing up to and beyond 50,000 devices, including recommendations for CPU cores, RAM, SSD size and clustered deployments.

GWN Manager software and documentation are available from Grandstream’s official resources:

These resources ensure you have the correct files, supported platforms and sizing information before installing GWN Manager in production.

The exact steps depend on whether you use the Linux package or the OVA image, but the overall process is similar.

1. Install GWN Manager (Linux package example)

Typical high-level steps on a supported Linux server:

  1. Download the GWN Manager bundled package for your OS from the Support → Tools page.
  2. Extract the downloaded archive.
  3. Run the provided installation script (for example sudo ./install) to install GWN Manager and its components (database, web server, services).
  4. On CentOS 7 / AlmaLinux 9, add firewall exceptions for the management ports (such as 8443) as documented in the guide.
  5. Start the GWN Manager services using the provided script (for example /gwn/gwn start).

These steps are detailed in the GWN Manager – Quick Installation Guide.

2. Deploy GWN Manager from the OVA image

When using the OVA:

  1. Import the official GWN Manager OVA into your hypervisor (for example VMware).
  2. Allocate CPU, RAM and disk according to the recommended requirements for your deployment size.
  3. Configure the VM’s network interface(s) so the server has a reachable IP address on your management network.
  4. Power on the VM and verify that GWN Manager services are running as per the OVA guide.

3. Access the web interface and create the admin account

After the service is running (package or OVA):

  • Open a supported web browser and go to:
    https://<GWN_Manager_Server_IP>:8443
  • On first use, GWN Manager displays an initial setup wizard where you:
    • Set the admin username
    • Create an admin password
    • Provide an email address for the administrator account

Once the wizard is completed, the regular login page appears and you can log in with the newly created credentials. For more info check this guide.

GWN Manager is designed to be accessed securely over HTTPS and to communicate with devices using dedicated management ports.

1. Required ports for GWN Manager services

The Quick Installation Guide specifies the default ports used by GWN Manager:

  • TCP 8443 – HTTPS web service (Nginx) for administrator access to the web interface
  • TCP 10014 – Gateway communication port used for management traffic between GWN Manager and devices

On firewalls (for example CentOS 7 / AlmaLinux 9 firewalld), these ports must be allowed so that:

  • Administrators can reach https://<server_ip>:8443 from their management PCs
  • Managed devices can communicate with GWN Manager on the configured management IP/port (typically 10014 by default)

2. Local access on the management network

For typical on-premise deployments:

  • Place the GWN Manager server/VM in a management VLAN or subnet that has IP connectivity to all GWN access points, routers, switches and GCC devices.
  • Ensure that management workstations (administrators’ PCs, jump hosts, etc.) can reach TCP 8443 on the GWN Manager server.
  • Keep GWN Manager behind a firewall and only open access from trusted internal segments.

3. Secure remote access (multi-site and branch deployments)

For remote sites or branch offices, recommended approaches include:

  • Site-to-site VPN or secure tunnels between the remote networks and the central site where GWN Manager is hosted, so devices and admins appear as if they are on the same private network.
  • Restricting direct Internet exposure of ports 8443 and 10014 whenever possible; if exposure is unavoidable, use strong passwords, up-to-date TLS configuration and IP/ACL restrictions.

GWN Manager uses HTTPS by default and automatically generates an SSL certificate on installation. You can replace this with a certificate signed by a trusted Certificate Authority to avoid browser warnings and improve security.

By keeping GWN Manager on a protected management network, opening only the necessary ports and using VPN or private links for remote locations, administrators and devices can access the platform securely without exposing the controller unnecessarily to the public Internet.

Device & Network Management

When GWN Manager and the devices are on the same local VLAN (same Layer-2 broadcast domain), you can:

  1. Go to Devices → Adopt in the GWN Manager web interface.
  2. GWN Manager scans the local network and lists all discoverable GWN access points, routers, switches and GCC devices.
  3. Select the devices you want to bring under management and click Adopt.
  4. Assign the selected devices to the appropriate network/site.

Manual controller address (different VLAN / subnet / remote site)
If the devices are located in a different VLAN, subnet or remote site:

  1. Log in to the device’s local web UI.
  2. Configure the GWN Manager address and port (the controller’s IP/FQDN and management port, typically 10014).
  3. Ensure routing and firewall rules allow communication between the device and the GWN Manager server.
  4. The device will then appear under Devices → Adopt, where you can select it and click Adopt, assigning it to the desired network/site.

This process lets you adopt devices from both local and remote networks while keeping the workflow centralized in the Devices → Adopt page.

For devices to be discovered and adopted correctly:

  • The device must support GWN Manager (GWN APs, routers, switches, GCC).
  • There must be IP connectivity between the device and the GWN Manager server on the management port (typically TCP 10014).
  • If using automatic discovery, GWN Manager and the devices should be on the same local subnet/VLAN or reachable via allowed broadcast / discovery traffic.
  • If devices are in a different subnet or remote site, you must configure the Controller / GWN Manager address on the device and ensure routing/firewall rules allow traffic between the device and server.
  • Time and DNS should be reasonably correct to avoid certificate / connectivity issues.

If these conditions are met, new devices will appear in GWN Manager and ready for adoption.

An access point can only be managed by one controller at a time. If an AP is already paired to a GWN router, GCC or another local “master” AP, that device is considered its current controller.

When you adopt APs into GWN Manager, GWN Manager becomes the central controller, and those APs should no longer be managed by a router/GCC or by a local master AP group.

Typical migration flow:

  1. Add the router or GCC to GWN Manager: Adopt the GWN router/GCC itself into GWN Manager so its WAN/LAN/VPN configuration is managed centrally.
  2. Reset or unpair the access points from the old controller: Remove / factory reset APs that were previously paired to the router, GCC or a “master AP” so they are no longer bound to that controller.
  3. Adopt the APs into GWN Manager: In GWN Manager, go to Devices → Adopt, discover the APs, and adopt them into the desired site/network.

Once this is done, GWN Manager is the only manager for those devices.

  • The router/GCC configuration is controlled from GWN Manager.
  • All APs are controlled from GWN Manager.

Mixing controllers (router/GCC managing Wi-Fi while GWN Manager also tries to manage the same APs) is not supported and will cause conflicts, so you always move them fully under GWN Manager when you decide to use it as the main controller.

Yes. GWN Manager is designed so you don’t have to configure every device one by one. You can use groups and profiles to push configuration to many devices in a consistent way.

1. Device groups for Wi-Fi / SSIDs

  • You can create device groups, for example a group that contains all wireless devices such as access points and wireless routers.
  • When you create or edit an SSID in GWN Manager, you don’t have to manually select every AP.
  • Instead, you can assign the SSID to a group (for example, “All-APs” or “Lobby-APs”), and all devices in that group will broadcast that Wi-Fi network.
  • If you later add a new AP to that group, it automatically inherits the SSIDs assigned to the group, so you don’t have to reconfigure anything.

This makes it easy to keep SSIDs consistent across many APs and locations.

2. Port profiles for switches

  • For switches, you can create port profiles that define settings such as:
    • VLAN ID / tagged & untagged VLANs
    • Port mode (access/trunk)
    • PoE settings
    • Other port-related options
  • Instead of configuring each port manually, you just apply the port profile to one or more switch ports.
  • The same profile can be reused across multiple switches. If you update the profile (for example, change the VLAN), all ports using that profile can be updated accordingly.

Using groups and port profiles keeps configuration consistent, reduces mistakes and makes it much faster to roll out changes across multiple APs, routers and switches managed by GWN Manager.

In GWN Manager, a Network is a logical container that groups devices, settings and statistics for a specific environment. A network usually represents things like:

  • A physical site (head office, branch, warehouse, store)
  • A building or floor in a campus
  • A separate customer in a managed-services deployment

This concept does not exist on standalone devices; it is specific to the management platform.

Using Networks in GWN Manager gives you several advantages:

  • Clear separation of environments: Each network has its own list of devices, SSIDs, VLANs, clients and alerts. This prevents confusion when you manage multiple locations or customers.
  • Cleaner dashboards and reports: You can view health, usage and alerts per network, so you immediately see which site has issues instead of digging through a global device list.
  • Role-based administration per site: You can assign different network administrators to different networks so each admin only manages their own site or customer, while a global admin can still see everything.
  • Easy replication for new sites: Networks can be cloned, letting you reuse an existing configuration (Wi-Fi, VLANs, policies, etc.) for a new site without rebuilding everything from scratch.

For detailed, step-by-step instructions on how to create and configure a network, refer to the official user guide section:
https://documentation.grandstream.com/knowledge-base/gwn-management-platforms-user-guide/#create-a-new-network

Features & Use Cases

Network Topology in GWN Manager is an automatic live map of your network, showing how routers, switches, access points and clients are connected to each other.

On a single screen you can typically see:

  • The uplink path from the gateway/router down through switches and APs to the end clients.
  • Whether a device is connected wired or wirelessly.
  • Which port a device is using on a switch, along with link speed and status.
  • Wireless details such as RSSI / signal strength, SSID and band for connected clients.
  • Device icons and basic status (online/offline) for routers, switches, APs and clients.

You can click on devices in the topology to open their details or configuration, so you don’t have to go hunting through separate lists just to find where something is connected.

This view is especially useful for:

  • Quickly answering “where is this client actually connected?”
  • Verifying that APs and switches are cabled to the correct uplinks
  • Spotting misconnected devices, dead links or unexpected cascades
  • Understanding the overall structure of a site without physically tracing cables

For more detailed information on how Network Topology works and the available options, see the official user guide section:
https://documentation.grandstream.com/knowledge-base/gwn-management-platforms-user-guide/#network-topology

The GWN mobile app (Android® and iOS®) is a companion app that lets you monitor and manage networks controlled by GWN Manager from your smartphone.

After you link your GWN Manager instance to your Grandstream account and sign in on the app, you can:

  • View networks and sites managed by GWN Manager, including device and client counts and basic health status.
  • Check device status (online/offline), see key information for routers, switches and APs, and drill down into a specific site when needed.
  • Receive push notifications for alerts, so you’re notified quickly when important events occur (for example, devices going offline).
  • Add devices on-site by scanning the QR code / barcode on the GWN device or entering its MAC address and password, then assigning it to the correct network in GWN Manager.
  • Perform basic monitoring and troubleshooting from your phone, such as reviewing usage and important debug information without opening the full web interface.

This makes the GWN mobile app especially useful for on-site installers and admins who need quick visibility into GWN Manager–managed networks while they’re away from their desks.

The Map & Floor Plans features in GWN Manager let you visualize where your devices are and how Wi-Fi coverage behaves in the real world, instead of just looking at a list of MAC addresses.

There are two views:

  • Map view
    • Place GWN devices or buildings on a world map and link them to specific locations or branches.
    • Devices can be positioned manually or automatically based on IP information.
    • Useful for multi-site deployments where you want to see which devices belong to which city, branch or campus at a glance.
  • Floor Plans view
    • Upload a floor plan image of a building (office, school, hotel, warehouse, etc.).
    • Add “virtual walls” with different materials (brick, glass, drywall) so the system can estimate RF attenuation.
    • Place real or virtual GWN APs on the floor plan to simulate coverage.
    • Generate a Wi-Fi heatmap on 2.4 GHz and 5 GHz to see coverage strength and potential weak spots before or after deployment.

This is useful for:

  • Designing new Wi-Fi deployments and explaining coverage to customers or management.
  • Checking if AP placement is reasonable without walking around guessing.
  • Planning expansions or fixes when users complain about weak signal in specific areas.

For detailed steps and options, see the “Map & Floor Plans” section in the GWN Management Platforms User Guide: https://documentation.grandstream.com/knowledge-base/gwn-management-platforms-user-guide/#map-floor-plans

The Site Survey feature in GWN Manager is basically a built-in Wi-Fi scanner that lets you see the real RF environment around your network from the perspective of your GWN devices, not just what your laptop sees.

When you run a Site Survey, GWN Manager instructs the selected AP/Wireless Router to scan nearby wireless networks and reports back things like:

  • Nearby SSIDs and BSSIDs
  • Channels and bands in use
  • Signal strength (RSSI) of each neighboring network
  • Security type and other basic parameters

This gives you a live picture of who else is talking on the air around your deployment.

Typical benefits and use cases:

  • Channel planning & interference reduction: You can quickly see which channels are heavily used and adjust your own channel plan to reduce co-channel interference and congestion.
  • Finding problem areas: If users complain about slow or unstable Wi-Fi, a Site Survey helps you check whether the area is crowded with overlapping APs from neighbors or other branches.
  • Validating design decisions: After moving APs or changing power/channel settings, you can re-run Site Survey to confirm that your coverage and channel reuse look better than before.
  • Security & visibility: By seeing all nearby SSIDs, you can more easily spot unknown or unexpected networks that might interfere with or mimic your own setup.

Site Survey is managed centrally in GWN Manager, so you don’t have to log into each device one by one to run scans. You trigger it from the platform, review the results, then decide how to adjust channels, power or placement based on real RF data instead of guesswork.

For more details and screenshots, see the official user guide section:
https://documentation.grandstream.com/knowledge-base/gwn-management-platforms-user-guide/#site-survey

Monitoring, Security & Maintenance

GWN Manager supports multi-user access with role-based permissions, so you’re not stuck with a single “super admin” account for everything.

You can:

  • Create multiple user accounts (for example: system admin, helpdesk, NOC operator, site admin, guest-view account).
  • Assign them to built-in roles such as administrator or read-only, depending on how much access they should have.
  • Create custom roles where you define exactly what each role can see and do.

Custom roles are very granular. You can enable or disable access to specific areas and actions, such as:

  • Viewing or editing devices
  • Managing Wi-Fi / SSIDs, VLANs, WAN, VPN
  • Managing users and roles
  • Access to logs, alerts, topology, maps
  • Ability to upgrade firmware, delete devices, change system settings, and more

Once a custom role is defined, you simply assign that role to a user account. This lets you, for example:

  • Give a site admin rights to manage devices and SSIDs only for their site.
  • Give a NOC operator rights to view all devices and acknowledge alerts, but not change system settings.
  • Give auditors or guests read-only access to dashboards and reports.

GWN Manager includes a customizable dashboard that gives an overview of what’s happening on the network in real time and over longer periods.

From the dashboard you can:

  • See the status of Internet, routers, switches, APs and clients at a glance.
  • View time-based charts for things like client count and bandwidth usage to spot peaks or drops.
  • Display different client analytics, such as device types, operating systems, manufacturers and guest activity.
  • Highlight “top” items (for example most active clients, devices or SSIDs) to quickly see who or what is using the most resources.

Admins can choose which charts to show and adjust their order, so each person can focus on the information that matters most to them.

GWN Manager also keeps historical statistics for an extended period (up to several months, typically around six months depending on configuration and storage). That longer history is useful for:

  • Identifying recurring performance issues
  • Comparing usage between sites or time periods
  • Planning capacity and upgrades based on real trends

So instead of just seeing what’s happening right now on each device, the dashboard lets you see how the network has been behaving over time, all in one place.

GWN Manager includes a flexible alert system that helps administrators detect and react to issues without constantly monitoring the web interface.

1. Alert categories and events
Alerts are organized into categories such as System, Performance, Security and Network.
Within each category you can enable specific events, for example:

  • Access point, router or switch offline/online after a configurable delay
  • Device configuration synchronization failures
  • WAN or gateway issues
  • Upgrade success or failure
  • Hardware or temperature warnings

Administrators simply select which events should generate alerts and, where applicable, define the time thresholds.

2. Notification types per alert

For every alert type, GWN Manager supports four independent notification methods:

  • Web: display the alert in the GWN Manager web interface
  • Email: send the alert to one or more configured email addresses
  • App: send a push notification to the GWN mobile app
  • 3rd-Party Platform: forward the alert to an external messaging or webhook platform

Each user account can choose which alerts to receive and which notification methods to use, allowing NOC teams and local administrators to tailor notifications to their responsibilities.

3. Third-party platform integration (optional)

When 3rd-Party Platform is enabled, GWN Manager can forward alerts to supported messaging or webhook services. This requires parameters such as:

  • Request Address (API endpoint or bot URL)
  • Token (authentication key)
  • Optional Extension or other identifiers

Because configuration depends on the external platform, Grandstream provides a dedicated guide:

GDMS Networking – Alert Notifications to Third-Party Platforms

This approach allows alerts to be delivered through email, mobile app and third-party tools, ensuring that critical events are communicated promptly to the appropriate teams.

GWN Manager supports integration with a local GWN Speed Test server, which allows you to measure throughput between your network and a nearby test server instead of relying on public internet speed-test sites.

Using a local speed test server offers several advantages:

  • More accurate LAN/WAN performance checks: The test traffic stays inside your own network or data center (or a nearby POP), so results are not affected by random congestion on the public internet.
  • End-to-end testing from managed devices: Supported GWN devices (such as routers or access points) can run speed tests directly to the configured server, and results are visible from GWN Manager. This helps you see whether issues are on the WAN link, between sites, or only on the client side.
  • Consistent benchmark for different sites: Multiple branches can test against the same central speed test server, making it easier to compare performance and verify that each location is getting the bandwidth it should.
  • Useful for validation and SLA checks: After changing ISP, upgrading a link, or adjusting QoS policies, you can quickly verify the impact using repeatable tests from the devices themselves.

The actual deployment requires installing a compatible speed test server in your environment and configuring its address in GWN Manager and the managed devices. Grandstream provides step-by-step instructions in the dedicated guide: Deploy a Local GWN Speed Test Server (GDMS Networking / GWN Manager)

Yes. GWN Manager supports Multi-Factor Safety Authentication for administrator accounts. When this option is enabled in a user’s Personal Settings, logging in to GWN Manager requires both the account password and a second verification code.

On GWN Manager, administrators can typically choose between two MFA methods:

  • Software token authentication
    Uses a TOTP-compatible application on a phone or computer (for example, a standard authenticator app). The app scans a QR code or uses a secret key, then generates time-based one-time passwords that must be entered at login.
  • Security token authentication
    Uses a hardware token that supports open TOTP standards. The token generates a 6-digit code that changes periodically; the user types this code in after the password.

MFA is configured per account, so you can enforce it for high-privilege administrators first and then roll it out more broadly. Enabling Multi-Factor Safety Authentication significantly strengthens the security of GWN Manager, because an attacker would need both the password and the token code to access the platform.

Trademarks
All product names, logos and brands mentioned in this article are the property of their respective owners. They are used here for identification purposes only and do not imply endorsement.

Was this article helpful?

Yes No
Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support