
DOC 6501_Release V
ATS-6501 Users Guide
196
Appendix F System Monitoring and Control Protocol
(SMCP)
F.1 Description
The System Monitoring and Control Protocol (SMCP) is used between an ATS-6501 and an
ATS-6511 where a TCP/IP Network connection may not be available to provide the status of the
remote ATS-6511. This protocol is mainly used in conjunction with the Microsemi Alarm Server
application. The system is based on a child/parent configuration. The parent being the Ensemble
A or B (ATS-6501 #1 and #2 respectively) and the children are a combination of TSC4340s
(Fiber Distribution Amplifiers, ATS-6511s Fiber Slaves, or other equipment tied into the network
port of the ATS-6511. The ATS-6511 will accept limited commands from the ATS-6501s and
send status information through the fiber connection back to the ATS-6501s. Also, when an
ATS-6511 has a 5071A or TSC-4145 Ultra Clean Oscillator, their status can also be sent through
the fiber connection of the ATS-6511.
In SMCP mode data is transferred between the ATS-6501 and downstream units in the form of
Fiber Packets. The downstream packet is sent from a fiber node to its child fiber nodes. It is used
to convey the transmitting node's state and an optional directive that changes the state of one or
more children or grandchildren. The communication of upstream packets is managed by FPGA
firmware running on each end of the fiber. During transmission, firmware emits a header,
followed by the software payload, followed by a CRC that is used to verify the integrity of the
transmission, and ending with padding consisting of zeros to the end of the 1,562,500 byte
structure. The following diagram shows an example of the upstream packet.
Figure 13 Upstream Fiber Packet
Within the Software payload are the
node information blocks
(NIBs). The length of NIBs varies
according to their type and the data that they contain. NIBs contain subsystem (i.e. internal output
card status) state data, alarm conditions, measurements and other data that must be conveyed up
the fiber.
For the SMCP to work, both the ATS-6501 and ATS-6511 must have valid node.cfg files placed
in the
/mod/tsc/site/
directory. Once the node.cfg file is configured correctly and the node must be
restarted, SMCP will start automatically. At this time ATS-6511 status information will be sent
to the ATS-6501. Also a limited command set can now be sent to the ATS-6511 over the fiber
from the ATS-6501. The following commands are currently supported:
•
Warm-Restart
•
Cold-Restart
•
Warm-Reboot
•
Cold-Reboot
•
Set System Autoswitch Participant
•
Clear Masked Alarms
•
Set Holdover Reference