Specifications

CHAPTER 13: ADVANCED ADMINISTRATION 203
To stop CC-NOC from monitoring a device, it can be unmanaged. Please refer to the
CommandCenter NOC Administrator Guide for additional information.
Note: Use the CC-NOC Synchronization Report to view targets that the CC-SG is subscribing to.
The report also displays any new targets that have been discovered by CC-NOC. Please refer to
Chapter 1
1: Generating Reports, CC-NOC Synchronization Report for additional information.
7. Specify a Synchronization Time to schedule when the target information is retrieved from
the CC-NOC database. This will refresh the databases as targets are discovered or become
unmanaged. The default is the current time as set on the client machine. You may want to
schedule synchronization during an off-peak time so synchronization will not affect the
performance of other processes.
8. For Heartbeat Interval, enter how often, in seconds, CC-SG sends a heartbeat message to
CC-NOC. This confirms if CC-NOC if still up and available. Default is 60 seconds. Valid
range is 30-120 seconds. Normally, this does not have to be changed.
9. For Failed Heartbeat Attempts, enter the number of consecutive heartbeats that must pass
without a response before a CC-NOC node is considered unavailable. Default is 2 heartbeats.
Valid range is 2-4 heartbeats. Normally, this does not have to be changed.
10. Click Next.
11. Either copy and paste the passcodes into CC-NOC fields if you are the CC-NOC
administrator, or submit the two passcodes to the CC-NOC administrator. As documented in
the CommandCenter NOC Administrator Guide, the CC-NOC administrator will then
enter the passcodes in CC-NOC, which initiates an exchange of security certificates.
Important: To increase security, you must enter the passcodes in CC-NOC
within five minutes after they are generated on CC-SG. This will minimize the
window of opportunity for intruders to breach the system with a brute-force
attack. Avoid transmitting the passcodes over email or other electronic means
to avoid a possible interception by automated systems. A phone call or
exchange of written codes between trusted parties is better protection
against automated interception.
12. Once the certificate exchange process is complete, a secure channel has been established
between CC-NOC and CC-SG. The CC-NOC data will be copied to CC-SG. Click OK to
complete the process. If the process does not complete within 5 minutes, it times out and data
is not saved in CC-SG and any stored certificates are deleted. Retry the procedure again−go
to Step 1. in
Add a CC-NOC on page 201.
Note: CommandCenter NOC can only be added to standalone or primary node CC-SG servers.
Edit a CC-NOC
1. On the Access menu, click CC-NOC Configuration.
2. Highlight a CC-NOC in the list, and then click Edit.
3. Change the configuration as needed. Please refer to the previous section,
Add a CC-NOC,
for additional information fields.
Launch CC-NOC
To launch CC-NOC from CC-SG:
1. On the Access menu, click CC-NOC Configuration.
2. In the CC-NOC Configuration screen, select an available CC-NOC.
3. Click Launch. This will connect you to a configured CC-NOC.