LogoLogo
  • FitController User Manual
  • Product Overview
    • Introduction
    • LED Behavior
    • Technical Specification
  • Getting Started
    • Power on Device
    • Logging On
    • Registering Devices to Organization
    • Assigning Devices to Network
    • Device Pairing
  • FitController (VM)
    • Platform Requirements (VM)
    • Software Packages (VM)
  • Working with Organization Trees
    • Hierarchy View
    • Network
  • Managing Devices
    • Managing Access Points
      • Configure and Check AP Details
    • Managing Switches
      • PoE scheduling
      • Getting Switch Analytics
      • Mirror
      • Link Aggregation
    • Managing Clients
    • Topology
  • Configuring Networks
    • Configuring SSIDs
      • 802.11 Settings
      • Configuring Security
      • Client IP Addressing
      • Dynamic VLAN Pooling
      • Advanced Settings
      • QoS
      • Captive Portal
      • Social Login
      • Voucher Service
      • Configuring Splash Page
      • Access control
    • Configuring Radio
    • Configuring VLAN
    • Configuring Switch Settings
    • Firmware Upgrade
    • General Settings
    • Access Control
  • Analytics
    • Device Events
    • System Events
    • Config Logs
  • Managing Organizations
    • Managing Device Inventory
    • Email Alerts
  • Managing Team Members
    • Roles and Permissions
  • Notification & Alerts
    • Notification Center
    • Configuring Alert Settings
  • Appendix
    • Compliance
    • Declaration of Conformity
    • Disclaimer/ Note
Powered by GitBook
On this page
  • EnGenius FIT Network Management Controller (FitCon100)
  • Before You Begin

FitController User Manual

NextProduct Overview

Last updated 2 years ago

EnGenius FIT Network Management Controller (FitCon100)

IMPORTANT

To install this device, please refer to the Quick Installation Guide included in the product packaging.

Other Languages:

Before You Begin

To start using the EnGenius FitController system, you must prepare the following:

  • At least one supported EnGenius Fit-series wireless access point or switch.

  • An existing network connection including DHCP and DNS configuration.

Is Internet connection needed?

  1. FitController is an On-premises solution where permanent internet connection is not necessary.

Is your Network required with DHCP?

  1. You can either set static IP or DHCP (default setting) on your FitController.

  2. For some circumstances, static IP can be used to ease the debug.

Is FitController management within Subnet or Cross Subnet?

  1. The discovery of FitController service on the subnet is based on mdns. Therefore, managed device (AP/switch) is basically required to be in the same subnet of FitController.

  2. A newly installed Fit-series device would look for a FitController in the same subnet with mdns and then try to connect with FitController using HTTP/HTTPS protocols. There is a “pairing” procedure in FitController to approve the managed plan on that device.

  3. There are two ways to let FitController service across subnets:

    • Turn on the mDNS reflector if it is supported in your gateway. In this way, the mDNS message of FitController will be reflected to other subnets.

    • Utilize DHCP option43 to send FitController service IP to devices.

日本語