¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Crestron
  2. Topics

Duplicate IP-IDs on same network with different systems

 

Hi All,
This is probably a dumb question but I can't test it with the equipment I have on hand at the moment...

This is not something that I usually do in my work, but I have a project where I will potentially have three similar systems on the same network (Let's say for the discussion that it is a FLAT network, just to prove the concept.)
I would like to have one primary program with the TSWs having a single IP-ID (ex: 91)
Each of the three TSWs IPTable settings would be pointing to three different processors.

If I had all three TSW IP-IDs at 91 but each pointing to a different IP address for each processor, would this create an issue for the Crestron gear??
I can see both sides of the story...

Obviously I could do a save as and change the IP-IDs for each system, but I wanted to see if this really would be necessary...
TIA!
 

¿ªÔÆÌåÓý

Mmm, the ip table relates to the ipaddress and ipid, so I might think that no issues would occur, but maybe someone has a different point of view.


NFH

On 31 Jul 2023, at 17:14, ckangis <chris@...> wrote:

?Hi All,
This is probably a dumb question but I can't test it with the equipment I have on hand at the moment...

This is not something that I usually do in my work, but I have a project where I will potentially have three similar systems on the same network (Let's say for the discussion that it is a FLAT network, just to prove the concept.)
I would like to have one primary program with the TSWs having a single IP-ID (ex: 91)
Each of the three TSWs IPTable settings would be pointing to three different processors.

If I had all three TSW IP-IDs at 91 but each pointing to a different IP address for each processor, would this create an issue for the Crestron gear??
I can see both sides of the story...

Obviously I could do a save as and change the IP-IDs for each system, but I wanted to see if this really would be necessary...
TIA!

 

It should work fine, there is no Auto discovery to muck it up, just configure each TP with its respective processors IPID
 

The CIP/SCIP connection is initiated by the secondary device to the primary device. When you give a TSW an IP ID of 91 and point it to the IP address, hostname, or FQDN of the primary device, it doesn't matter what else is on the network with the same IP ID, it matters that the primary device's network status is up and it has a populated IP table and programming to establish what gets communicated between the devices.

The only time this is an issue, using your example, is if you were to have one processor, therefore one IP/hostname/FQDN, running multiple programs and multiple secondary devices (TSW's) trying to connect using the same IP ID. An IP ID can only be used once per primary device, not once per program, with the exception being things like EISC.
 

Thanks, Guys!
That's what I thought but wanted to get some confirmation!!
 

Yea we did this type of thing as a redundancy solution and It was slightly quirky at first but in the end it seemed to work pretty well. Not sure if thats the solution you are working towards here, but the multiple processor/ID part of it did work for us.?

1 - 6 of 6