Personal WiFi Docs
  • Getting Started
  • WiFi Integration
    • Summary of supported WiFi vendors
      • Cisco Meraki
        • Meraki oAuth integration
      • Cisco Catalyst WLC (IOS-XE)
      • Cisco Meraki Easy PSK
      • Aruba - Unbound MPSK
      • Fortinet (FortiGate Secure Wireless Controller)
      • Extreme Networks
      • Ruckus SmartZone
      • Cambium cnMaestro
      • Juniper (Mist)
      • TP-Link Omada
      • Huawei - iMaster NCE-Campus
  • Service management
    • Dashboard
    • Managing Accounts
    • Groups
    • Managing Networks
      • Network Managers
    • Units
    • General options
      • Personal Area Networks (PAN)
      • Service Options
      • Organization details
    • Network Policies
    • WiFi Portal & Onboarding
      • Access Control options
      • WiFi Portal options
      • IoT Devices Authentication
      • WiFi Portal distribution
    • Visitors (beta)
    • Admins
      • Multi Organizations
    • Account settings
    • My Profile
    • Support platforms integrations
    • Service Monitoring and Assurance
      • Anomalies
      • Activity Logs
      • Network Health
  • Cloud Identity Platforms integrations
    • Coworking management platforms
      • Optix
      • Office RnD
      • Nexudus
      • Andcards
    • Property Management Systems
      • Oracle Opera Cloud
      • Mews
      • Cloudbeds
      • Apaleo
      • StarRez
    • Enterprise cloud IdPs
      • Microsoft Entra ID (SAML)
      • Microsoft Entra ID (oAuth)
      • Google Workspace (oAuth)
      • Shibboleth
      • Group mapping
    • Passwordless SSO
      • Custom HTTP Request
  • MSP Operations
    • MSP Dashboard
    • MSP Account settings
  • Add-ons
    • Billing
    • White label
    • Passpoint
    • SMS Services - via Twilio
  • APIs
    • Getting Started
    • Account management
  • PRODUCT
    • Coming soon...
      • Engenius Cloud
      • Zyxel Nebula (Pro)
    • Changelog
    • Datasheet
  • Solution guides
    • Student living
      • Sample FAQ: WiFi for the Resident Hall
    • BYOD
Powered by GitBook
On this page
  • Meraki
  • Using Network Policies
  • Troubleshooting Network Policies

Was this helpful?

  1. Service management

Network Policies

PreviousOrganization detailsNextWiFi Portal & Onboarding

Last updated 5 months ago

Was this helpful?

For some WiFi vendors, you need to setup Network Policies before creating Tenants. The section Network Policies in the Integration page appears automatically based on the WiFi vendor you set up.

Meraki

While creating an iPSKs, Meraki require to set a Group Policy. By creating Network Policies, Cusna automatically creates and keeps in sync the Group Policies in the Meraki account for all the network involved (one network per each Network)

Click Add a new Policy.

The New Network Policy dialog appears. Fill the form

  • name: reference name for the policy (e.g. "Default")

  • bandwidth downlink: max downlink spee in Kbps

  • bandwidth uplink: max downlink spee in Kbps

  • VLAN

Click Save.

The Network Policies create appears in the list.

Using Network Policies

Once you have created network policies, you can use them in different ways.

First of all, whenever you create a Network, you'll be required to assign a "default" network policy. This is the policy that will be assigned by default to Accounts associated to that Network whenever the network policy is not specified on the Account during initialization.

When creating a new account manually, you can opt to use the Network default network policy, or you can manually pick one of those you have already initialized in setup.

You can also assign a Network Policy to a group. This will be assigned to all Accounts of type "group member" assigned to this group.

Finally, you can also assign Network Policies individually to each Accoutn when creating or managing them form the dashboard.

Troubleshooting Network Policies

Network Policies sync with equivalent entities in the network management system. For example, each Network Policy is deployed as a Group Policy in each Meraki Network connected to a Cusna Network.

In case a Group Policy already exists in the Meraki Network with the same name assigned to the Network Policy in Cusna, Cusna will attempt to create it with a slightly different name, adding a numerical suffix to the name (e.g. <policyname>_1)

All policies initializd on the network are forced with the prefix "CU-" in front of the name you select.

In order to check the matching Group Policies in the Meraki network, you can click the info icon on the Network Policy card. A dialog will show the list of the matching Group Policies in each Meraki Network.