AMX AV/IT Administrators Guide
Rev. 1.0 (7/29/2014) www.amx.com Page 16
entry to communicate with system #1. If the system #7 Central Controller’s URL List does contain the IP
address for system #1 a relay loop will be created which will lead to problems.
Once the systems are connected to each other they exchange ICSP routing information such that each
Central Controller will learn about all the Central Controllers connected to each other. The
implementation of Central Controller ICSP routing primarily involves the communication of ICSP routing
tables between Central Controllers. The ICSP routing table is built using the entries within the local URL
List, the DPS entries in the DEFINE_DEVICE section of the code, and from the ICSP routing tables
exchanged between connected Central Controllers. ICSP Routing tables are exchanged between Central
Controllers upon their initial connection and updates to the ICSP routing tables are exchanged
periodically. ICSP route table transmission has a certain amount of randomization built in to prevent
flooding the network with ICSP routing table transmissions when a Central Controller reports
online/offline. Each Central Controller in a network will add a minor random delay (1-5 seconds) so that
they don’t all transmit at the same time.
*Note: Any TCP/IP devices, including NetLinx Central Controllers, which utilize DHCP to obtain its TCP/IP
configuration, are subject to having their IP address change at any time. Therefore, NetLinx Central
Controller’s IP address must be static unless the network supports Dynamic DNS AND a DHCP server
capable of updating the DNS tables on behalf of the DHCP client. If a Dynamic DNS/DHCP server is
available then the NetLinx Central Controller’s host name may be used in the URL List.
Central Controller to Central Controller Topology
In a system with more than two Central Controllers who need to communicate, the topology of the
logical routes may be a concern. In the Star Topology below if Central Controller #2 needs to
communicate with a device bound to Central Controller #3, then a ICSP packet is sent over IP to Central
Controller #1, the packet is de-encapsulated, read, re-encapsulated in an IP Packet and then sent to
Central Controller #3, where it is de-encapsulated, read and forwarded to the device.
In systems with a large amount of control between systems a fully meshed topology may be more
appropriate. In the fully meshed topology each Central Controller is aware of all other Central
Controllers. Routing loops are avoided by the use of a “ROUTE MODE DIRECT” command in each Central
Controller which allows communication only between Central Controllers who are logically connected
using the URL List.
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales