GPIO Node Webserver sloooooooooooowwwwwww

[James_Nebraska]

I'm trying to configure the GPIO node for my Axia routing switcher, and the little webserver in it for configuration and monitoring takes forever to load, and many times IE will give up on it. Ping works fine to the IP address, and reports speedy results, but using IE to get into the node is not working.

I'll use IE to connect to the audio and router selector nodes, and they work just fine.

What should I do?

[AXIA_milos]

Is this a new GPIO node? Are you able to get to any pages or is it not letting you get to any? If you power cycle it, do you have any better results? Are you sure there isn't another device on the network with the same IP address?
What are the routes that you have in place?

[James_Nebraska]

Now, all nodes are really sluggish when trying to access them via web browser. The audio seems to be flowing well, and pings are speedy enough, but accessing the configuration pages for the nodes are either really slow, or they don't happen at all.

[AXIA_milos]

James_Nebraska:

You never responded to the questions I left on the forum. Please send an email to our support account (support (at) AxiaAudio (dot) com) so that we can resolve this in more timely manner. Please include your switch model, a copy of the configuration of the switch, some details on the gear connected to the switch. There is something not correct about your system that with all the information, a support person will be able to resolve this.

[James_Nebraska]

thanks

[AXIA_milos]

For any reading along, the issue was a switch configuration. If a switch has no configuration (or maybe incorrect configuration), the ports could behave in a flooding manner (all traffic being transported down the pipe). For example, as can be seen in the suggested switch configuration documents from the AxiaAudio web site, there are command lines which turn on IGMP (Internet Group Management Protocol). This manages the multicast data and without it, a switch will treat the mutlicast as Broadcast. This is just spreading the data out of all ports. With 2 nodes, this may not be a problem and why some customers actually have success with a pair of nodes on a none approved switch (or not configured switches); the data is being treated as broadcast and you can transfer audio from node to node as long as the port isn't saturated with data. Other devices on the network (your office PC) may begin to suffer a little since it would be receiving a lot of data it didn't ask for and has to use up resources to toss the data away. Once you begin to add more and more of these devices, eventually the network is saturated with Mutlicast which is being treated as broadcast, now your playing with a critical mass (of data).
With IGMP enabled and configured as Axia suggests, this sort of "waisted" broadcast traffic is avoided and the network actually performs more like a fine tuned race car and not a scientific experiment.
Configuring a switch may frighten you, but just like everything else, give yourself enough time to read the instruction, to apply what you have been instructed to do, and check your work. If it doesn't make sense, or the outcome isn't what you think it should be, ask someone that may know the answer. That is why Axia provides 24/7 support. If you have a question, just ask us, we are here to help you succeed.

[jp]

Thanks for the follow up, Milos. All too often threads like this just end with no resolution.

[clarknovak]

Configuring a switch may frighten you, but just like everything else, give yourself enough time to read the instruction, to apply what you have been instructed to do, and check your work. If it doesn't make sense, or the outcome isn't what you think it should be, ask someone that may know the answer. That is why Axia provides 24/7 support.

Frighten? Hey, it's not like you can break 'em. That's why there's a "reset" button! If a marketing wonk like me can configure a switch, anyone can!

And like Milos says, if you get stuck, we're always here to help.