Skip to Content

Changes for page ZUM-HUB4 Processor Setup

Last modified by Alexander Mott on 2025/04/30 15:58
From version 48.1
edited by Craig Lewis
on 2025/03/13 15:48
Change comment: There is no comment for this version
To version 50.1
edited by Alexander Mott
on 2025/04/30 15:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.craig\.lewis@chiefintegrations\.com
1 +XWiki.alexander\.mott@chiefintegrations\.com
Content
... ... @@ -45,8 +45,16 @@
45 45  ** Force waiting to start program: ##startprogafterrouter on##
46 46  ** Processor must be rebooted with "##reboot##" command before these take effect, but you can wait to reboot if there are other settings you must change that also require a reboot
47 47  ** ShowRunnerCLC™ .puf versions 3.042 and newer automatically run this command when the "Configure ZUM-HUB4" option is selected.
48 +* Here are some things to consider before doing any network configuration on the ZUM-HUB4 processor:
49 +** **Never **connect an external router to the Control Subnet, as doing so will cause the internal DHCP server to shut down.
50 +** **Never **set the LAN IP address to an address that is in the range of the Control Subnet
51 +*** e.g. for a processor with the default 172.22.0.0/20 Control Subnet configuration, the LAN IP address must be below 172.22.0.0 or above 172.22.15.255
52 +** **Always** set devices on the Control Subnet to DHCP so that their IP addresses are managed by the built-in DHCP server. Only set static IP addresses on the Control Subnet if you really know what you are doing.
53 +*** If setting static IP addresses on the Control Subnet for any reason: **always** assign an address within the Control Subnet range, but **never** use the first two or the last address in the range
54 +*** e.g. for a processor with the default 172.22.0.0/20 Control Subnet configuration, IP addresses must be in the range 172.22.0.3 through 172.22.15.254
55 +**** 172.22.0.0 is not a valid address, 172.22.0.1 is taken by the processor, 172.22.0.2 is taken by the DHCP server (default gateway), and 172.22.15.255 is the broadcast address for the Control Subnet
48 48  * Determine whether the lighting control hardware will be connected to the ZUM-HUB4's LAN port or the Control Subnet port:
49 -** If the system is standalone (not integrated with building LAN), then lighting hardware can be connected to either the LAN port or the Control Subnet port, but it is still recommended to use the Control Subnet for Crestron hardware as the ZUM-HUB4 has a router built-in that will assign IP addresses:
57 +** If the system is standalone (not integrated with building LAN), then lighting hardware can be connected to either the LAN port or the Control Subnet port, but it is still recommended to use the Control Subnet for Crestron hardware as the ZUM-HUB4 has a built-in router that will assign IP addresses via DHCP:
50 50  *** If connecting lighting hardware to the LAN port, then you must configure the LAN as a static IP (example is for a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet, with a processor IP address of (% style="color:blue" %)**10.0.0.10**(%%)):
51 51  **** Disable DHCP: ##dhcp 0 off##
52 52  **** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.10**(%%)##
... ... @@ -129,4 +129,4 @@
129 129  
130 130  Due to SSL Management, Processors and Secondary network hardware with SSL enabled will require CS Authentication to be enabled and setup.
131 131  
132 -Follow these steps to setup [[SSL User Configuration>>doc:Main.SSL User Configuration]]
140 +Follow these steps to setup [[SSL User Configuration>>doc:SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Appendix.SSL User Configuration.WebHome]]