DOC 6501_Release V
ATS-6501 Users Guide
203
Type Model Description
93 TSC2135 ECL distribution module
94 TSC2138 BITS Interface
95 TSC2154 2 Channel Counter
96 TSC2210 SONET Interface
97 TSC2213 GPS RX
98 TSC2230 D/A & DIO
Table 13 2000 Series Chassis Node Types
Type Model Description
16 3000 Series SONET Chassis (embedded CPU) Modular backplane
111 TSC3024 Chassis monitor
112 TSC3032 Pulse distribution amplifier
113 TSC3036 RF distribution amplifier
114 TSC3059 Distribution amplifier
Table 14 3000 Series Chassis Node Types
Type Model Description
17 6395 Modular backplane
120 6301 Blank panel
121 6310 Pulse distribution amplifier
122 6312 ECL distribution amplifier
123 6315 RF distribution amplifier
124 6359 LF distribution amplifier
125 6391 RF fault switch
126 6392 IRIG fault switch
127 6393 Pulse fault switch
128 6332 1x6 PPS Dist Amp
128 6313 Pulse Converter (Single to ECL)
Table 15 6300 Series Chassis Node Types
Once the node.cfg file is configured correctly the ATS-6501 or ATS-6511 must be restarted to start the
SMCP. To verify that SMCP has started in the unit being configured start a telnet session to port 2125
in an ATS-6511 or port 2125 in an ATS-6501.
6501B> telnet 10.11.11.2 3125
If SMCP has started, text similar to the following will be seen:
nib NIB
]@ç%R
nib NIB
Ênib
F.4 Troubleshooting
If a connection can be made to port 3125 in the ATS-6501 but no NIB’s are appearing, it is most likely
the child nodes are not running SMCP. Configure the child nodes and verify NIB in the ATS-6501
port 3125.
If a connection cannot be made to port 3125 in an ATS-6501 or port 2125 in an ATS-6511 then SMCP
is not running. The problem will most likely be in the node.cfg file. If any errors with the node.cfg file
occur, they will appear in the logs of the unit. Check /var/log/messages in the unit and look for any
errors that refer to SMCP. or node.cfg. If any errors are found in the node.cfg file the must be fixed,
saved and then the unit must be restarted in order to start SMCP.
To Next Page
Loading...