Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Troubleshooting Section in User Guide #135

Open
vansia43 opened this issue Oct 10, 2019 · 4 comments
Open

Update Troubleshooting Section in User Guide #135

vansia43 opened this issue Oct 10, 2019 · 4 comments

Comments

@vansia43
Copy link
Contributor

While analyzing the Hardware Guide, it was determined that Troubleshooting information should stay in the User Guide. The following suggestions come from the Hardware Guide project and could potentially be added to other troubleshooting tips in the User Guide. The suggestions need a content review from a subject matter expert.

Possible Local Connection Issues

  • First, check if the server is connected to the router using a cable or using WiFi. If you are using WiFi to connect the server to the same router network, this limits the bandwidth on the server. Connecting the server with a cable to the router should increase the performance.

  • Consider your local area connection’s wireless frequency. Wireless connection devices with a frequency of 2.4 GHz have less bandwidth than devices with frequencies of 5 GHz. This could be a factor related to slow performance. Keep in mind, however, that when you select your client devices, they need to have the ability to support 5 GHz connections.

  • Check to see if your router has an encrypted connection. Encrypted connections can take up more CPU load in both the router and client devices, which slows down performance.

  • Consider the quality of your network router. Below are some general guidelines to follow when selecting a router:
    *It is suggested that you do not use a router below 802.11n

    *Dual band routers are better than single band routers (as far as the clients can benefit of the dual band)

    *A big number of antennas (>3) means often the router has duplicated radio emitters, what means it's like having two or more routers

    *If the specs say it has MIMO means video/audio transmission is optimized.

    *Memory & CPU

  • For connecting up to 30 clients there are two options: either getting a good, likely expensive access point, or connecting 2 regular access points.

  • Any access point from Ubiquiti or Aruba (owned by HP) would be valid. Also high-end access points from other manufacturers will do it too.

@vansia43
Copy link
Contributor Author

Some other, potential updates that came from some of the base materials/resources used to update the Hardware Guide:

  • Do a hardware demo: This part would benefit from having a detailed script of steps to follow. What do I connect first? Where do I go to see Kolibri? What if I get an error?
  • One possibility would be to provide "checks" after each step that everyone can confirm, e.g.,
  1. STEP: turn on wifi
  2. CHECK: check that the new wifi hotspot Kπ is available

@benjaoming
Copy link
Contributor

Hi @vansia43 - these are great ideas. Do you want comments individually on each bullet?

I think in general, could be good to have a "Tips" section under Management or Advanced management to separate out the issues that relate to Troubleshooting vs. connection optimizations.

@vansia43
Copy link
Contributor Author

@benjaoming Got it. That makes a lot more sense and I think would fit in better with what is already in the existing Troubleshooting section. Yes, I would need someone to review the above bullets to make sure they are correct, so a comment for each one would be awesome, if that works for you!

@benjaoming
Copy link
Contributor

Awesome @vansia43 - I can definitely respond. Give me a day or two :)

@radinamatic radinamatic added this to the upcoming patch milestone Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants