Cloning is available with SmartServer 2.7 Update 1 and higher.
...
| Warning | ||
|---|---|---|
| ||
You should save the apollo password for any backed-up SmartServer system image. If you restore a system image onto a new SmartServer, then the new SmartServer will have its password changed to the old SmartServer's password (from the backup image file). |
The reference SmartServer can include the most comprehensive configuration of devices likely to be seen in the field. For subsets of the reference configuration, devices that are not present in some sites can either be ignored or deleted accordingly. Cloned Modbus and BACnet networks should be configured with the same addressing and baud rate information as the reference SmartServer IoT networks. LON networks will need their devices replacing in the CMS with the new UIDs.
...
- Connect an Ethernet patch lead from the source SmartServer IoT's RJ45 LAN connector to an Ethernet switch port on your local LAN with a DHCP server running (unless you are using a static IP address).
- Connect your PC to the same LAN and subnet as the source SmartServer IoT using an Ethernet lead. Alternatively, use the SmartServer's Rapid Fallback feature (if enabled) to set the SmartServer IoT's address to 192.168.1.222, which will allow a direct Ethernet connection from the PC to the SmartServer IoT. In this case you will have to manually configure the PC to be on the same subnet as the source SmartServer IoT.
- Remove any USB devices from the source SmartServer.
- Connect the terminal emulator to the console port using a USB cable and power up the SmartServer.
Find the SmartServer IoT's IPV4 address for the eth0 port (shown as inet addr:192.168.168.5 in the example below, third line) by entering the following command at the console:
ifconfig
A result similar to the following appears:Code Block apollo@smartserver-17q41xs:~$ ifconfig eth0 Link encap:Ethernet HWaddr 00:d0:71:07:46:eb inet addr:192.168.168.5 Bcast:192.168.168.255 Mask:255.255.255.0 inet6 addr: fe80::2d0:71ff:fe07:46eb/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:38427 errors:0 dropped:17168 overruns:0 frame:0 TX packets:35507 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2909558 (2.9 MB) TX bytes:6099630 (6.0 MB) Interrupt:51 Base address:0x6000 eth1 Link encap:Ethernet HWaddr 00:d0:71:07:46:ec UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:50 Base address:0xe000 ip70 Link encap:Ethernet HWaddr 00:d0:71:07:6f:50 inet addr:192.168.239.128 Bcast:192.168.239.255 Mask:255.255.255.0 inet6 addr: fe80::2d0:71ff:fe07:6f50/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6538 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:380111 (380.1 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MULTICAST MTU:65536 Metric:1 RX packets:1230995 errors:0 dropped:0 overruns:0 frame:0 TX packets:1230995 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:170737328 (170.7 MB) TX bytes:170737328 (170.7 MB) apollo@smartserver-17q41xs:~$
- Connect to the source /wiki/spaces/TEMP/pages/44041710 SmartServer IoT's CMS from a browser at:
- With SmartServer release 2.8 or higher: https://<IPV4 address>/cms
- With SmartServer release prior to 2.8: https://<IPV4 address>:8443/cms
The CMS login window appears.
- Login using the username and password. Note that the username is always apollo, but the password may have been changed from the one that is printed on the rear label of the SmartServer.
Open the Devices widget, SEGMENT CONTROLLERS tab and perform a full system backup as described in Backing Up the Database and/or Settings, or System section of the Backing Up, Restoring, and Cloning the SmartServer.
...
| Warning | ||
|---|---|---|
| ||
You should save the apollo password for any backed-up SmartServer system image. If you restore a system image onto a new SmartServer, then the new SmartServer will have its password changed to the old SmartServer's password (from the backup image file). |
- Connect an Ethernet patch lead from the target SmartServer's RJ45 LAN connector to an Ethernet switch port on your local LAN with a DHCP server running (this assumes a new SmartServer).
Connect your PC to the same subnet as the target SmartServer using an Ethernet lead. Alternatively, use the SmartServer's Rapid Fallback feature to set the SmartServer's address to 192.168.1.222, which will allow a direct Ethernet connection from the PC to the SmartServer.
Remove any USB devices from the target SmartServer.
Connect the terminal emulator to the console port using a USB cable and power-up the SmartServer.
- Find the SmartServer's IPV4 address by entering the following command at the console:
ifconfig - Connect to the source /wiki/spaces/TEMP/pages/44041710 SmartServer IoT's CMS from a browser at:
- With SmartServer release 2.8 or higher: https://<IPV4 address>/cms
- With SmartServer release prior to 2.8: https://<IPV4 address>:8443/cms
The CMS login window appears.
- Login using the username and password. Note that the username is always apollo, but the password may have been changed from the one that is printed on the rear label of the SmartServer.
Open the Devices widget, SEGMENT CONTROLLER tab.
Note Note: To best view all of the information on this widget, click the /wiki/spaces/TEMP/pages/44631776 ( 
). 
- Click the Action button (
) and select the Restore action.
The restore view appears.
- Select Full System for the Backup Contents.
The Restore Original Segment ID option is already set to No (cloning).
- Select the system backup file to be used for the clone operation from the Restore File dropdown list.
Click RESTORE to proceed with the clone operation.
A message similar to the following appears:
- Click OK to proceed with the clone operation.
You will not be able to access the CMS during the system clone operation. - To ensure full functionality after the reboot process completes, perform the following steps:
Power-cycle the target SmartServer IoT to ensure full functionality.
Note The target SmartServer IoT may not be accessible over the current IP infrastructure due to IP address changes, and that its password may have changed to that of the source SmartServer IoT. - Verify target SmartServer IoT operations.
...