Configuration Guide
Table Of Contents
- ExtremeControl Guest and IoT Manager Configuration
- Extreme Networks® Software License Agreement
- Table of Contents
- About this Document
- New in this Document
- Guest and IoT Manager Overview
- Installing Guest and IoT Manager
- Administering Guest and IoT Manager
- Configuring Onboarding Template
- Creating an Onboarding Template
- Configuring the Common Details
- Configuring the Guest User Account Details
- Configuring Sponsor Approval
- Configuring the Device Record Details
- Configuring Device Type Groups
- Configuring the Account Notification Templates
- Configuring Advanced Details
- Configuring Guest User Provisioning Using Outlook Add-in
- Configuring Guest User Provisioning Using Vouchers
- Configuring Guest User and Device Provisioning Using CSV
- Configuring Device Record Details
- Configuring Zero Touch Guest User Provisioning
- Managing Onboarding Templates
- Configuring Custom Attributes
- Configuring Access Groups
- Creating an Onboarding Template
- Configuring Provisioners
- Configuring Self-Services
- Managing Guest Users
- Managing Devices
- Configuring Guest and Devices
- Using Self-Provisioning Services
- Guest and IoT Manager Add-In for Outlook
- Automated Login of the Guest User using the Login URL
- Troubleshooting and FAQs
- Testing RADIUS Connection Settings
- Restarting Guest and IoT Manager
- Problem: Virtual Appliance Troubleshooting
- Problem: Saving Access Control Engine Settings
- Problem: User Groups / End System Group Not Visible in Guest and IoT Manager
- Problem: Provisioner Cannot Login
- Problem: Guest and IoT Manager Email / SMS Notification Failed
- Problem: Unable to Access Guest and IoT Manager Application URL
- Problem: User and Device Troubleshooting
- Problem: Sponsor List is Not Available
- Problem: Modification in Network Interface settings does not reflect post dep...
- Problem: Outlook Add-in Issues
- Problem: Service Unavailable in Browser
- Problem: Time Zone Issues for Schedule Tasks
- Problem: Users/Devices are not getting cleaned up for Housekeeping Tasks
- Problem: Unable to Access GIM UI
- Problem: LDAP Provisioner login fails
- Problem: LDAP Sponsors are not populating in the Self-Service Page
- Problem: Server Error during bulk creation
- Problem: Unable to Renew Password
- Problem: Guest User account is not created post sending SMS
- Problem: Login URL redirects to Captive Portal
- Problem: “Server Error. Please contact Administrator Error message on clickin...
- Problem: FQDN not being used in URLs
- Problem: Unable to Customize Provisioner Login page
- Problem: Login failed. Invalid credentials/Account Expired” message on clicki...
- Problem: Outlook Add-in throws Security Exception post enabling FQDN
- Command Line Interface
Problem: LDAP Sponsors are not populating in the Self-Service Page
274 of 291
l If the LDAP Group to which the Provisioner belongs is specified in one or more of
the Onboarding Templates in the Associated LDAP Groups section. Then, you must
specify the LDAP group and not the User search root as previously specified in 8.2.x.
l Only the Onboarding Templates that have the LDAP group mapped (to which the
Provisioner belongs) or have the Default Onboarding Template checkbox marked as
checked are sent back by NAC for LDAP Provisioners.
Problem: LDAP Sponsors are not populating in the
Self-Service Page
Problem
The list of LDAP sponsors that was populating in GIM 8.2.x does not populate
after migrating to GIM 8.3.0
Solution
The LDAP Sponsor configuration done in GIM 8.2.x does not work in GIM 8.3.0.
As, Guest and IoT Manager lists the Sponsor details with matching LDAP groups
in 8.3.0, unlike matching User Search Root as in 8.2.x
Problem: Server Error during bulk creation
Problem
When Guest Users or Devices are being imported using CSV. This occurs only
when a very large number such as 1000 records are attempted in continuous
batches of 1000 (maximum limit for each upload is 1000).
Solution
This occurs due to the time required in enforcement of the created Guest Users /
Devices between XMC and NAC.
The time taken to complete the enforcement is the reason for the Server Error
displayed.
To overcome this wait for some time before attempting to create more records
so that the enforcement can complete.