Total Access
®
3000/3010 System Manual
6TADLP726-1E
TOTAL ACCESS 3000/3010
DLP-726
Page 4 of 6
© 2002, ADTRAN, Inc.
Perform Steps Below in the Order Listed
If the X.25 status is not correct, check the connection to the X.25 network and
correct the problem before proceeding.
NOTE
If the SCU is to be connected to one or more Operational Support Systems,
the following steps should be performed for each OSS to ensure that the OSS
can communicate with the SCU.
7. Have the OSS Connect to the SCU
Contact the administration center for the OSS and have the personnel at the center
perform a manual connect to the SCU over the X.25 network. You will need to
provide the X.25 LDN in order for the call to be completed. If you are unsure of
the LDN, get it from the X.25 network administrator.
If the attempt to connect is not successful, contact the X.25 network administrator
and report the symptoms of the failure.
8. Have the OSS Perform a TL1 Activate User Command
Once the OSS is successfully connected to the SCU, have the OSS personnel log
in by performing a TL1 Activate User command using the syntax below:
act-user::test:1::<password>;
where <password> is the READ_WRITE password set in the SCU. This will log
the OSS in as user “test.”
9. Check the X.25 Status to Ensure that the OSS is Properly Logged In
Once the OSS is successfully logged in, issue the following TL1 command on the
local terminal to check the X.25 status:
rtrv-stat-x25:::2;
The response should be:
<CLLI Code> <date> <time>
M 2 COMPLD
/* Link status 0x50 */
/* Frame status 0x0 */
/* Server 0 status 104 user ‘’ */
/* Server 1 status 104 user ‘’ */
/* Server 2 status 104 user ‘’ */
/* Server 3 status 104 user ‘’ */
/* Server 4 status 0 user ‘TEST’ */
To Next Page
Loading...
