How to backup PIN Server? How to built the Intel Unite Enterprise High availability?

[idata]

Hello all,

We have thousands Meeting Room need to deploy Intel Unite. Who can give us the advice about Intel Unite Enterprise. We want to deploy two Pin server for backup.

thanks.

[idata]

Hello sdh1984:

In order for us to be able to provide the most accurate information about this matter, we will start an investigation, as soon as I get any updates I will post all the details on this thread. Any further questions, please let me know. Regards Alberto

[RHein3]

The PIN server is just a windows machine (it doesn't have to be a vPro machine either).

I currently have it running on Server Core on VMWare.

I am having difficulties with the SRV record/dns based discovery, but editing the ServerConfig.xml manually made my connection come right up.

The section at least seems to allow for multiple server hosts, so you should be able to specify additional servers there for redundancy.

[idata]

Hello:

Thank you very much to rheiniluoma for the information provided above. To sdh1984: According to our research if there is not a DNS record configured when the Unite hub starts, it will not detect automatically where is the Unite server is sitting at. If you use the serverconfig.xml file it will for sure get a PIN, but to enter more than one server address, in case that either of them does not respond it will automatically pick another one, is not possible. That is not the way Intel® Unite works. In this case what we recommend is to create a DNS record so Unite connects to the pin server on its own and also to configure the server to have high availability, by no means it is dependable of Intel® Unite. Any questions, please let me know. Regards Alberto

[RHein3]

Alberto,

Thank you for the clarification.

There *may* be a bug in the service record lookup in the current release of the Unite Hub.

When I was monitoring via wireshark, it was doing a lookup on the _uniteservice._tcp record without the domain name appended.

Not sure if this is standard/normal, or if there's a setting I'm overlooking, but at the present moment I'm failing that lookup. My dns servers happily find it when the domain name is appended, but without the domain name, it's referring the query out to root servers.

[idata]

Hello rheiniluoma:

You are welcome.In regard to your inquiry, we will continue our research to confirm, as you mentioned, if there may be a bug with the tool. As soon as I get any updates, I will post all the details on this thread.To sdh1984:I just wanted to check if the information posted previously was useful for you, and if you need further assistance on this matter?Any questions, please let me know. Regards Alberto

[Ronny_G_Intel]

Hi rheiniluoma,

I am not really well familiarized with Wireshark, would you mind providing more details on the "bug" reported so that I can reported this back? Perhaps screenshots or anything else that could help me either reproduce or report?

Regards,

Ronny G

[idata]

Dear,

Sorry for replay late. Your answer was very helpful.

Many thanks!

[RPada]

Hi,

Do we have a solution for this issue (DNS service lookup)

[RHein3]

Wireshark is a packet capture solution for the Windows platform.

By running it on the Intel Unite Hub I was able to watch the raw packet traffic, and identify the DNS queries that were actually made "on the wire".

in my domain, I have the service _uniteservice, protocol _tcp defined with Priority 0 and Weight 0, with port number 443, and it points at the VM where I am hosting the Unite Server.

When i see the lookup go out, it's just sending _uniteservice._tcp instead of _uniteservice._tcp.mydomain.com

When I do a quick test, without the domain name appended, i fail the lookup, but when i append the domain name, it succeeds and returns the correct address.