Changes for page Processor Setup

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,12 +1,10 @@
1		-{{info}}
	1	+(% class="box errormessage" %)
	2	+(((
2	2	This page is for typical processor setup; for ZUM-HUB4 deployments, see our [[dedicated ZUM-HUB4 page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUM-HUB4 Processor Setup.WebHome]].
3		-{{/info}}
	4	+)))
4	4
5		-{{error}}
6		-All 4-Series processors require authentication to be configured when first connecting: **the Crestron Agent or Field Tech are responsible for recording these credentials. Chief Integrations cannot provide assistance unless the credentials are known. The only way to connect to a device for which the credentials have been lost is to factory reset the device, which may require redoing the start-up from scratch if the latest configuration was not saved and backed up. **
7		-{{/error}}
8		-
9		-{{warning}}
	6	+(% class="box warningmessage" %)
	7	+(((
10	10	ShowRunnerCLC™™ is tested against current Crestron firmware releases. **Please use at least the recommended firmware builds.**
11	11
12	12	* 3-Series: PUF 1.8001.0214
...	...	@@ -17,7 +17,7 @@
17	17
18	18	* Static IP or properly setup DHCP/DNS implementation required.
19	19	* Auto-Assigned/Link-Local IP address range of 169.254.x.x not supported (Crestron xPanel issue)
20		-{{/warning}}
	18	+)))
21	21
22	22	{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
23	23	{{toc/}}
...	...	@@ -68,17 +68,13 @@
68	68	*** Configure your DHCP server software to assign IP addresses in the desired range
69	69	*** Once the processor is assigned an IP address, connect to it via Text Console at the assigned IP address
70	70	*** Run the above commands to disable DHCP and assign a static IP address to the processor
71		-* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), there are some additional considerations and setup that must be performed:
72		-** Never connect an external router to the Control Subnet, as doing so will cause the internal DHCP server to shut down.
	69	+* For processors with a Control Subnet (CP3N/AV3/PRO3/CP4N/AV4/PRO4), additional setup is required
73	73	** Connect to the processor via Text Console and run the command: ##startprogafterrouter on##
74	74	*** This will force the processor to wait until the router has started before attempting to load the ShowRunnerCLC™ program, avoiding potential license validation issues if the processor boots up before the router.
75		-*** ShowRunnerCLC™ .puf versions 3.042 and newer automatically run this command when the "Configure Processor with Router" option is selected.
76	76	** The previously listed "ipa," "ipm," etc. commands will configure settings for the processor's LAN port, which should be connected to the building LAN or third party network.
77		-** Lighting control hardware (e.g. TSWs, DIN-CENCN-2s, etc.) should be left in DHCP mode and connected to the Control Subnet port.
78		-*** The processor acts as a DHCP server on the Control Subnet, with addresses that are determined automatically based on the LAN configuration.
79		-*** If lighting hardware is to be connected via the LAN anyway, then you must run the command: ##securegateway default##
	73	+** Lighting control hardware (e.g. TSWs, DIN-CENCN-2s, etc.) should be connected to the Control Subnet port. The processor acts as a DHCP server on the Control Subnet, with addresses that are determined automatically based on the LAN configuration. If lighting hardware is to be connected via the LAN anyway, run the command: ##securegateway default##
80	80	*** Note: this setting enables unsecure connections to the processor from the LAN. This is necessary if ZUMNET-JBOXs or other non-secure Crestron devices (such as 3-Series EISC) will be connected via the LAN port of the processor
81		-** The Control Subnet will automatically configure itself based on the LAN configuration, but it should be configured manually if the processor is to be connected to building LAN as the default scheme may cause networking issues:
	75	+** The Control Subnet will automatically configure itself based on the LAN configuration, but it can optionally be configured manually:
82	82	*** Using the "Functions>Ethernet Addressing...>Control Subnet" menu of Toolbox:
83	83	**** Set routing to "Manual" with the start address and subnet size
84	84	**** E.g., a setting of "100.64.0.0/20" will have the processor at 10.64.0.1 with an IP mask of 255.255.240.0 and a default gateway and DNS server at 100.64.0.2
...	...	@@ -103,14 +103,6 @@
103	103	** Double check that the correct PUF file is listed under the "Package Info" section and that the correct IP address is listed under "Target"
104	104	** Press the "Recheck" button
105	105	** Make sure that all three tasks are selected ("Load ShowRunner Program", "Update Crestron App", and "Update XPanel")
106		-** Additional tasks are available for certain processors:
107		-*** ZUM-HUB4:
108		-**** "Configure ZUM-HUB4" will automatically run commands: ##cwsanticsrf OFF## and ##startprogafterrouter on##
109		-**** "Configure ZUM-HUB4 Subnet" will automatically reconfigure the control subnet to a 100.64.0.0/20 configuration to avoid potential conflicts with corporate networks
110		-***** **NOTE: If you are connected to the Control Subnet and select this option, you will need to reconnect to the processor and run the .puf again in order to finish loading ShowRunnerCLC™ as this option will interrupt your connection to the processor.**
111		-**** "Configure ZUM-HUB4 SecureGateway" will automatically run command: ##securegateway default##
112		-*** Processors with Routers (AV3, CP3N, PRO3, AV4, CP4N, and PRO4)
113		-**** "Configure Processor with Router" will automatically run command: ##startprogafterrouter on##
114	114	** Press the "Update" button to begin loading ShowRunnerCLC™
115	115	* Sometimes the PUF tool will falsely report a failure to load the program
116	116	** Connect to the processor via Text Console