NMS Commands Reference
H-5
3610-A2-GB91-90
July 1999
Table H-1
(4 of 4)
NMS Command Set
3600 Series
DSU
COMSPHERE
6700/6800
System
Controller
ANALYSIS
6510
Disruptive
Effect
1
DSU
ADp or DPII Mode
Controller
6510
Control
Trib
Stat:ID
Identity
Identity
Long Status
N
E
9
Confg:Dir
—
List Directory
—
N
E
Test:Lpbk
Loopback
Loopback
Loopback
D
D
Test:Devic
Modem/Device Test
Device Test
Device Self
Test
D
D
Stat:TPwr
Report Terminal
Power
Report Terminal
Power
—
N
E
Bckup:Bkup
Standby Facility
Standby Facility
12
—
E
8
—
Test:BERT
Modem BERT &
Transmit Test
Pattern
Modem BERT &
Transmit Test
Pattern
—
D
D
13
—
Send Message
—
—
N
E
—
Trending Reports
—
—
D
14
D
14
—
—
—
Device
NOOP
N
E
1
The disruptive effect of most commands depends on the position of the addressed device in the circuit
and the setting of the Diagnostic Type configuration option. Commands addressed to a control DSU use
the NMS control channel (CC) or diagnostic channel (DC), and are nondisruptive to the primary data
channel. Since a tributary is remote, commands addressed to it can be disruptive unless the associated
DBMs are in Standby mode or the DSU is configured for nondisruptive mode.
E = If the DSU is configured for disruptive or mixed diagnostics, this command may cause errors
requiring retransmission of data. If the DSU is configured for nondisruptive diagnostics, this
command will not cause errors in the user data.
N = Nondisruptive.
D = Session-disruptive.
8
Session-nondisruptive but may cause errors requiring retransmission of data.
9
Command cannot be addressed to a tributary DSU by the ANALYSIS 6510 NMS if the firmware release is
less than 2.4.
12
A Standby facility addressed to a DBM/DBM-V/DBM-S/DBM-D performs a Dial Mode/Dial Standby
command.
13
To terminate the Transmit Test Pattern command, execute an Abort command to the tributary DSU instead
of using a TTP release command.
14
Session-disruptive depending upon test type.
Содержание COMSPHERE 3610
Страница 4: ...COMSPHERE 3600 Series Data Service Units C July 1999 3610 A2 GB91 90 Notices ...
Страница 16: ...COMSPHERE 3600 Series Data Service Units x July 1999 3610 A2 GB91 90 ...
Страница 27: ...Introduction 1 11 3610 A2 GB91 90 July 1999 Figure 1 4 NMS Interfaces to the SDU 1 of 2 ...
Страница 120: ...COMSPHERE 3600 Series Data Service Units 4 40 July 1999 3610 A2 GB91 90 This page intentionally left blank ...
Страница 128: ...COMSPHERE 3600 Series Data Service Units 5 6 July 1999 3610 A2 GB91 90 ...
Страница 186: ...COMSPHERE 3600 Series Data Service Units 6 58 July 1999 3610 A2 GB91 90 ...
Страница 187: ...A 1 3610 A2 GB91 90 July 1999 Data Service Unit Menu A ...
Страница 188: ...COMSPHERE 3600 Series Data Service Units A 2 July 1999 3610 A2 GB91 90 ...
Страница 189: ...Data Service Unit Menu A 3 3610 A2 GB91 90 July 1999 ...
Страница 190: ...COMSPHERE 3600 Series Data Service Units A 4 July 1999 3610 A2 GB91 90 ...
Страница 192: ...COMSPHERE 3600 Series Data Service Units B 2 July 1999 3610 A2 GB91 90 This page intentionally left blank ...
Страница 224: ...COMSPHERE 3600 Series Data Service Units C 22 July 1999 3610 A2 GB91 90 ...
Страница 246: ...COMSPHERE 3600 Series Data Service Units E 2 July 1999 3610 A2 GB91 90 Figure E 1 Control Channel ...
Страница 247: ...Network Management Connectivity E 3 3610 A2 GB91 90 July 1999 Figure E 2 Extended Control Channel ...
Страница 259: ...Pin Assignments F 11 3610 A2 GB91 90 July 1999 Figure F 8 EIA 232 D Crossover Cable 4951 035F ...
Страница 263: ...Troubleshooting G 3 3610 A2 GB91 90 July 1999 Figure G 2 No Signal NS Condition Troubleshooting ...
Страница 265: ...Troubleshooting G 5 3610 A2 GB91 90 July 1999 Figure G 4 Out of Frame OOF Condition Troubleshooting ...
Страница 272: ...COMSPHERE 3600 Series Data Service Units H 6 July 1999 3610 A2 GB91 90 ...
Страница 278: ...COMSPHERE 3600 Series Data Service Units I 6 July 1999 3610 A2 GB91 90 ...
Страница 280: ...COMSPHERE 3600 Series Data Service Units J 2 July 1999 3610 A2 GB91 90 ...
Страница 292: ...COMSPHERE 3600 Series Data Service Units L 10 July 1999 3610 A2 GB91 90 ...