Professional Documents
Culture Documents
OSN 8800 6800A 3800A V100R006C03 Installing, Operating and Maintaining Your Network
OSN 8800 6800A 3800A V100R006C03 Installing, Operating and Maintaining Your Network
V100R006C03
Issue 03
Date 2013-06-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Related Versions
Product Name Version
Intended Audience
This document provides guides to get the information about how to installing, perform initial
commissioning the products. This document also provides guides for routine operation on site.
This document is intended for:
l Field Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
3.2 OptiX OSN 8800 l OptiX OSN 8800 T32: Changed the maximum subrack power
Subrack and Power consumptiona from 3500 W to 4800 W.
Requirement l OptiX OSN 8800 T16: Changed the maximum subrack power
consumptiona from 1600 W to 2400 W.
8 Parts Replacement Added the step for enabling the board removal indication function
to the procedure for replacing a board supporting maintenance
blinking.
Update Description
Update Description
Update Description
7 Routine Operation l 7.1.3 Board Indicators: Added maintenance blinking mode for
On-site the STAT indicator.
l 8 Parts Replacement:
– Added the step for enabling the board removal indication
function to the procedure for replacing a board supporting
maintenance blinking.
– 8.1.5 Substitution Relationships: Added LOA, LSC, LSQ,
LTX, TN54TEM28, TN54TOA, TN53ND2, TN53NQ2,
TN53NS2, TN55NS3, TN53TDX, TN53TQX, TN55TQX,
TN54TSXL TN12M40, TN12M40V, TN12D40, TN14FIU,
WSMD9, TN11DAS1, TN13OAU1 boards.
– 8.2 Replacing an SCC Board with One of the Same TNxx
Version: Changed the indicator that is used to observe
database clearing status from the PROG indicator to the
STAT indicator. Added the methods of replacing the
TN16SCC board.
– 8.3 Replacing the SCC Board with One of a Different
TNxx Version: Changed the indicator that is used to observe
database clearing status from the PROG indicator to the
STAT indicator. Added the methods of replacing the
TN16SCC board.
– 8.4.1 Substitution Relationships: Added TNK4SXH and
TNK4XCT boards.
– Added 8.5 Replacing the TN16XCH Board.
– Added 8.6 Replacing the PID Board.
– 8.8.1 Substitution Relationship: Added TN16AUX board.
– 8.15 Replacing the Subrack: Added the methods of
replacing the OptiX OSN 8800 T16 subrack.
Update Description
Whole manual l Added descriptions of the OptiX OSN 8800 T16 subracks.
l Added descriptions of the enhanced OptiX OSN 8800 T32
subracks.
Modifi
cation
Mode Command Description Impact
CONN-
TST-40GETH
DISC-TST-40GETH
RTRV-
TST-40GETH
RTRV-
RSLT-40GETH
Modifi
cation
Mode Command Description Impact
RST-40GETH
ED-FFP-CFP
OPR-PROTNSW-
CFP
RLS-PROTNSW-
CFP
RLS-LPBK-EC
RTRV-LPBK-EC
Modifi
cation
Mode Command Description Impact
RTRV-COND-
<HDSDIRBR/
3GSDIRBR/
CBR10G>
RTRV-ALM-
<HDSDIRBR/
3GSDIRBR/
CBR10G>
RTRV-ATTR-
<HDSDIRBR/
3GSDIRBR/
CBR10G>
SET-ATTR-
<HDSDIRBR/
3GSDIRBR/
CBR10G>
Modifi
cation
Mode Command Description Impact
Modifi
cation
Mode Command Description Impact
Modifi
cation
Mode Command Description Impact
Modifi
cation
Mode Command Description Impact
l V100R006C01SPC300
None
l V100R006C01SPC200
Modifi
cation
Mode Command Description Impact
l V100R006C01SPC100
Modifi
cation
Mode Command Description Impact
RLS-LPBK-
ODUFLEX
RTRV-LPBK-
ODUFLEX
RMV-ODUFLEX
RST-ODUFLEX
SET-TH-ODUFLEX
RTRV-TH-
ODUFLEX
Modifi
cation
Mode Command Description Impact
RTRV-
{OTU1,OTU2,OTU
3,OTU5G,OTU4,
ODU1,ODU2,ODU3
,ODU5G,ODU4,OD
UFLEX }
Modifi
cation
Mode Command Description Impact
Modifi
cation
Mode Command Description Impact
Modifi
cation
Mode Command Description Impact
ENT-LAG The –
LAGSHAREMODE
ED-LAG parameter is added to
specify the type of
algorithm for
calculating LAG load-
sharing bandwidth.
The LAGHOTIME
parameter is added to
specify the hold-off
time for LAG
protection switching.
l V100R006C00SPC300
None
l V100R006C00SPC100
Modifi
cation
Mode Command Description Impact
Modifi
cation
Mode Command Description Impact
RTRV-IBQDR
RTRV-CBR10G
RTRV-CPRI1
RTRV-CPRI2
RTRV-CPRI3
RST-OTU4
RST-ODU4
Contents
4 Node Configurations................................................................................................................298
4.1 80 Wavelength Configuration....................................................................................................................................299
4.1.1 OTM........................................................................................................................................................................299
4.1.1.1 Signal Flow...........................................................................................................................................................299
4.1.1.2 Subrack Layout.....................................................................................................................................................299
4.1.1.3 Subrack Connections............................................................................................................................................301
4.1.2 Back to Back OTM..................................................................................................................................................303
4.1.2.1 Signal Flow...........................................................................................................................................................303
4.1.2.2 Subrack Layout.....................................................................................................................................................304
4.1.2.3 Subrack Connections............................................................................................................................................306
4.1.3 1 Degree ROADM...................................................................................................................................................308
4.1.3.1 Signal Flow...........................................................................................................................................................308
4.1.3.2 Subrack Layout.....................................................................................................................................................309
8 Parts Replacement.....................................................................................................................493
8.1 General Guide for Replacing a Board........................................................................................................................495
8.1.1 Prerequisite..............................................................................................................................................................495
8.1.2 Impact on the System..............................................................................................................................................495
8.1.3 Tools, Equipment, and Materials.............................................................................................................................497
8.1.4 Precautions...............................................................................................................................................................497
8.1.5 Substitution Relationships.......................................................................................................................................500
8.1.5.1 Optical Transponder Boards.................................................................................................................................500
8.1.5.2 Tributary and Line Boards....................................................................................................................................502
8.1.5.3 Optical Multiplexer and Demultiplexer Boards...................................................................................................505
8.1.5.4 Optical Add and Drop Multiplexing Boards........................................................................................................507
8.1.5.5 Reconfigurable Optical Add and Drop Multiplexing Boards...............................................................................507
8.1.5.6 Optical Amplifier Boards.....................................................................................................................................507
8.1.5.7 Optical Supervisory Channel Boards...................................................................................................................508
8.1.5.8 Optical Protection Boards.....................................................................................................................................508
8.1.5.9 Spectrum Analyzer Boards...................................................................................................................................508
8.1.5.10 Variable Optical Attenuator Boards...................................................................................................................508
8.1.5.11 Optical Power and Dispersion Equalizing Boards.............................................................................................508
8.1.5.12 Clock Board........................................................................................................................................................508
8.1.6 Procedure for Replacing a Board.............................................................................................................................508
8.2 Replacing an SCC Board with One of the Same TNxx Version................................................................................514
8.2.1 Setting the Jumper and DIP Switch on the SCC Board...........................................................................................515
8.2.2 Replacing the Protected SCC in a Master Subrack.................................................................................................519
8.2.3 Replacing the Unprotected SCC in a Master Subrack.............................................................................................523
8.2.3.1 Replacing the SCC by Backing Up Database Data from the NMS (NE Is Unreachable)....................................524
8.2.3.2 Replacing the SCC by Backing Up Database Data from a CF Card (NE Is Unreachable)..................................531
8.2.3.3 Replacing the SCC by Backing Up Database Data to the NMS (NE Is Reachable)............................................538
8.2.3.4 Replacing the SCC by Backing Up Database Data to a CF Card (NE Is Reachable)..........................................546
8.2.3.5 Replacing the SCC After Configuring SCC 1+1 Protection................................................................................554
8.2.4 Replacing the SCC Board in a Slave Subrack.........................................................................................................558
8.3 Replacing the SCC Board with One of a Different TNxx Version............................................................................561
8.3.1 Substitution Relationships.......................................................................................................................................561
8.3.2 Replacing the Protected SCC Board in a Master Subrack.......................................................................................561
8.3.3 Replacing the Unprotected SCC Board in a Master Subrack..................................................................................566
8.3.3.1 Replacing the SCC with the Database Backed Up to the NMS...........................................................................566
8.3.3.2 Replacing the SCC with the Database Backed Up to a CF Card.........................................................................574
8.3.3.3 Replacing the Board After Configuring SCC 1+1 Protection..............................................................................583
8.3.4 Replacing the SCC in a Slave Subrack....................................................................................................................586
8.4 Replacing the Cross-Connect Board...........................................................................................................................589
8.4.1 Substitution Relationships.......................................................................................................................................589
9 Network Reconstruction..........................................................................................................633
9.1 Expanding NEs by Adding Shelves............................................................................................................................634
9.1.1 Expanding NEs of Version V100R005 or Later When the New Shelf Software Version Is V100R005 or Later
..........................................................................................................................................................................................634
9.1.1.1 Expansion Flow....................................................................................................................................................634
9.1.1.2 Connecting the Master and Slave Shelves with Network Cables.........................................................................635
9.1.1.3 Powering On the Slave Shelf................................................................................................................................635
9.1.1.4 Checking the New Shelf ID..................................................................................................................................636
9.1.1.5 Uploading NE Data to the U2000.........................................................................................................................637
9.1.1.6 Removing an Unneeded Logical Slave Shelf on the U2000................................................................................638
9.1.1.7 Validation.............................................................................................................................................................639
9.1.2 Expanding NEs of Version V100R005 or Later When the New Shelf Software Version Is Unknown..................639
9.1.2.1 Expansion Flow....................................................................................................................................................639
9.1.2.2 Upgrading the TN51SCC Software of the New Shelf to V100R005C00 or Later...............................................640
9.1.2.3 Connecting the Master and Slave Shelves with Network Cables.........................................................................642
9.1.2.4 Powering On the New Shelf and Clearing the SCC Software and Database.......................................................642
9.1.2.5 Powering On the Slave Shelf................................................................................................................................643
A.3.10 RTRV-VACANTSLOT......................................................................................................................................1027
A.4 Communication Management..................................................................................................................................1028
A.4.1 Configuring VLAN...............................................................................................................................................1028
A.4.1.1 ED-LAN............................................................................................................................................................1029
A.4.1.2 DLT-ACL..........................................................................................................................................................1031
A.4.1.3 ED-ACL.............................................................................................................................................................1032
A.4.1.4 ENT-ACL..........................................................................................................................................................1033
A.4.1.5 RTRV-ACL.......................................................................................................................................................1034
A.4.1.6 RTRV-LAN.......................................................................................................................................................1035
A.4.1.7 ED-COM-SERVICE..........................................................................................................................................1037
A.4.1.8 RTRV-COM-SERVICE....................................................................................................................................1038
A.4.1.9 ACT-SSL-CAFILE............................................................................................................................................1039
A.4.1.10 ED-SSL-MODE...............................................................................................................................................1040
A.4.1.11 RTRV-SSL-MODE.........................................................................................................................................1041
A.4.1.12 ED-SSL-ENCRYPTION.................................................................................................................................1042
A.4.1.13 RTRV-SSL-ENCRYPTION............................................................................................................................1043
A.4.1.14 ED-ADVANCED-ACL...................................................................................................................................1044
A.4.1.15 ENT-ADVANCED-ACL................................................................................................................................1045
A.4.1.16 RTRV-ADVANCED-ACL..............................................................................................................................1047
A.4.1.17 DLT-ADVANCED-ACL................................................................................................................................1049
A.4.2 Enquire PPP/IP Interface Information..................................................................................................................1050
A.4.2.1 RTRV-IPIF-INFO..............................................................................................................................................1050
A.4.2.2 RTRV-PPPIF-COUNT......................................................................................................................................1051
A.4.2.3 RTRV-PPPIF-STATE.......................................................................................................................................1052
A.4.2.4 RTRV-ROUTE-INFO.......................................................................................................................................1054
A.4.3 Configuring FTP...................................................................................................................................................1055
A.4.3.1 ED-FTP..............................................................................................................................................................1055
A.4.3.2 RTRV-FTP........................................................................................................................................................1057
A.4.4 Configuring Serial................................................................................................................................................1058
A.4.4.1 ED-SERIAL.......................................................................................................................................................1058
A.4.4.2 RTRV-SERIAL.................................................................................................................................................1059
A.4.5 Configuring IP......................................................................................................................................................1061
A.4.5.1 DLT-TIDIPMAP...............................................................................................................................................1061
A.4.5.2 ENT-TIDIPMAP...............................................................................................................................................1062
A.4.5.3 RTRV-TIDIPMAP............................................................................................................................................1063
A.4.5.4 DLT-IPROUTE-STATIC..................................................................................................................................1064
A.4.5.5 ENT-IPROUTE-STATIC..................................................................................................................................1065
A.4.5.6 RTRV-IPROUTE-STATIC...............................................................................................................................1066
A.4.5.7 RTRV-IPROUTE..............................................................................................................................................1068
A.4.5.8 RTRV-STAT-TCP.............................................................................................................................................1069
A.4.5.9 RTRV-TCPIP-INFO..........................................................................................................................................1071
A.4.5.10 IP-PING...........................................................................................................................................................1072
A.4.5.11 IP-TRACERT..................................................................................................................................................1073
A.4.6 Configure OSI.......................................................................................................................................................1075
A.4.6.1 RTRV-OSI-ADJS..............................................................................................................................................1075
A.4.6.2 ED-OSI-DCC.....................................................................................................................................................1076
A.4.6.3 ENT-OSI-DLTUNNEL.....................................................................................................................................1077
A.4.6.4 DLT-OSI-DLTUNNEL.....................................................................................................................................1078
A.4.7 Configuring OSPF................................................................................................................................................1079
A.4.7.1 ED-OSPF-DCC..................................................................................................................................................1079
A.4.7.2 ED-OSPF-LAN..................................................................................................................................................1081
A.4.7.3 ED-OSPF-SYS..................................................................................................................................................1082
A.4.7.4 RTRV-OSPF-ALL.............................................................................................................................................1084
A.4.8 Configuring NTP..................................................................................................................................................1086
A.4.8.1 DLT-NTP-ACCTL............................................................................................................................................1086
A.4.8.2 ENT-NTP-ACCTL............................................................................................................................................1087
A.4.8.3 RTRV-NTP-ACCTL.........................................................................................................................................1088
A.4.8.4 DLT-NTP-AUTHPARA....................................................................................................................................1090
A.4.8.5 ED-NTP-AUTHPARA......................................................................................................................................1091
A.4.8.6 ENT-NTP-AUTHPARA....................................................................................................................................1092
A.4.8.7 RTRV-NTP-AUTHPARA.................................................................................................................................1093
A.4.8.8 DLT-NTP-SERVER..........................................................................................................................................1095
A.4.8.9 ENT-NTP-SERVER..........................................................................................................................................1096
A.4.8.10 RTRV-NTP-SERVER.....................................................................................................................................1097
A.4.8.11 ED-NTP-SYS..................................................................................................................................................1099
A.4.8.12 RTRV-NTP-SYS.............................................................................................................................................1100
A.4.8.13 RTRV-NTP-STATUSINFO............................................................................................................................1101
A.4.9 Configuring SNMP...............................................................................................................................................1102
A.4.9.1 DLT-SNMP-ACCESSIP...................................................................................................................................1102
A.4.9.2 ED-SNMP-ACCESSIP......................................................................................................................................1103
A.4.9.3 ENT-SNMP-ACCESSIP...................................................................................................................................1105
A.4.9.4 RTRV-SNMP-ACCESSIP................................................................................................................................1106
A.4.9.5 DLT-SNMP-TRAPINFO..................................................................................................................................1107
A.4.9.6 ED-SNMP-TRAPINFO.....................................................................................................................................1108
A.4.9.7 ENT-SNMP-TRAPINFO..................................................................................................................................1110
A.4.9.8 RTRV-SNMP-TRAPINFO................................................................................................................................1111
A.4.9.9 ED-SNMP-COMMUNITY...............................................................................................................................1113
A.4.9.10 RTRV-SNMP-COMMUNITY........................................................................................................................1114
A.5 Equipment Management..........................................................................................................................................1115
A.5.1 ENT-EQPT...........................................................................................................................................................1115
A.5.2 ED-EQPT..............................................................................................................................................................1118
A.5.3 DLT-EQPT...........................................................................................................................................................1124
A.5.4 RTRV-EQPT........................................................................................................................................................1126
A.5.5 RTRV-ETH-EQPT...............................................................................................................................................1131
A.7.5 DLT-WMU-CONN..............................................................................................................................................1225
A.7.6 RTRV-WMU-CONN...........................................................................................................................................1226
A.8 Configuring Cross-Connections..............................................................................................................................1228
A.8.1 Configuring OXC.................................................................................................................................................1228
A.8.1.1 ENT-PXC-OCH.................................................................................................................................................1228
A.8.1.2 ED-PXC-OCH...................................................................................................................................................1230
A.8.1.3 DLT-PXC-OCH.................................................................................................................................................1232
A.8.1.4 RTRV-PXC-OCH..............................................................................................................................................1233
A.8.1.5 RTRV-PXCINFO-OCH....................................................................................................................................1236
A.8.1.6 RTRV-PXC-WASTAGE...................................................................................................................................1238
A.8.1.7 DLT-PXC-WASTAGE......................................................................................................................................1240
A.8.1.8 ED-PXC-WASTAGE........................................................................................................................................1241
A.8.1.9 ED-OXC-NEPORT...........................................................................................................................................1242
A.8.1.10 RTRV-OXC-NEPORT....................................................................................................................................1244
A.8.1.11 RTRV-OCCUP-WAVE...................................................................................................................................1245
A.8.2 Configuring EXC..................................................................................................................................................1247
A.8.2.1 ENT-CRS-<MOD2>..........................................................................................................................................1247
A.8.2.2 ED-CRS-<MOD2>............................................................................................................................................1250
A.8.2.3 DLT-CRS-<MOD2>..........................................................................................................................................1253
A.8.2.4 RTRV-CRS-<MOD2>.......................................................................................................................................1255
A.9 Configuring Transparently Transmitted FE Singal.................................................................................................1259
A.9.1 ENT-CRS-OHFE..................................................................................................................................................1259
A.9.2 RTRV-CRS-OHBYTE.........................................................................................................................................1260
A.9.3 DLT-CRS-OHFE..................................................................................................................................................1261
A.10 Configuring Service Protection.............................................................................................................................1262
A.10.1 Configuring Equipment Level Protection...........................................................................................................1262
A.10.1.1 ENT-EQPT-PG................................................................................................................................................1262
A.10.1.2 ED-EQPT-PG..................................................................................................................................................1264
A.10.1.3 DLT-EQPT-PG................................................................................................................................................1265
A.10.1.4 RTRV-EQPT-PG.............................................................................................................................................1266
A.10.1.5 OPR-PROTNSW-EQPT..................................................................................................................................1268
A.10.1.6 RLS-PROTNSW-EQPT..................................................................................................................................1269
A.10.2 Configuring FFP Protection................................................................................................................................1270
A.10.2.1 ENT-FFP-<OCH/OC/WDM/CFP>.................................................................................................................1270
A.10.2.2 ED-FFP-<OCH/OC/WDM/CFP>....................................................................................................................1273
A.10.2.3 DLT-FFP-<OCH/OC/WDM/CFP>.................................................................................................................1274
A.10.2.4 RTRV-FFP-<OCH/OC/WDM/CFP>..............................................................................................................1276
A.10.2.5 RTRV-FFP-LOG.............................................................................................................................................1279
A.10.2.6 INIT-FFP-LOG................................................................................................................................................1280
A.10.2.7 OPR-PROTNSW-<OCH/OC/WDM/CFP>.....................................................................................................1281
A.10.2.8 RLS-PROTNSW-<OCH/OC/WDM/CFP>.....................................................................................................1283
A.10.3 Configuring SNCP Protection............................................................................................................................1285
A.10.3.1 RLS-PROTNSW-<MOD2>............................................................................................................................1285
A.10.3.2 OPR-PROTNSW-<MOD2>............................................................................................................................1286
A.11 Configuring SCC Protection..................................................................................................................................1288
A.11.1 ED-AUTOSYNC-ENABLE...............................................................................................................................1288
A.11.2 REPT^SW...........................................................................................................................................................1289
A.11.3 RTRV-BACKUP-INFO.....................................................................................................................................1290
A.11.4 ALW-SWDX-EQPT...........................................................................................................................................1291
A.11.5 INH-SWDX-EQPT.............................................................................................................................................1292
A.11.6 RTRV-BATCHBAK-CAUSEHIS.....................................................................................................................1294
A.11.7 RTRV-MSCOM-INTRPHIS..............................................................................................................................1295
A.11.8 RTRV-AUTOSYNC-ENABLE.........................................................................................................................1296
A.11.9 RTRV-SWITCH-HIS.........................................................................................................................................1297
A.11.10 RTRV-BAD-INFO...........................................................................................................................................1299
A.11.11 RTRV-BACKUPMOD-INFO..........................................................................................................................1300
A.11.12 RTRV-BATCH-PROCESS..............................................................................................................................1302
A.11.13 RTRV-SYNC-ENABLE...................................................................................................................................1304
A.11.14 RTRV-DX-MODE...........................................................................................................................................1305
A.11.15 RTRV-DX-WORK...........................................................................................................................................1306
A.11.16 RTRV-DX-EQPT.............................................................................................................................................1307
A.11.17 RTRV-HD-STA................................................................................................................................................1308
A.11.18 RTRV-AS-ENABLE........................................................................................................................................1309
A.11.19 RTRV-FORCELOCK-SUPPORT....................................................................................................................1310
A.11.20 RTRV-MANU-ENABLE.................................................................................................................................1311
A.11.21 SW-DX-EQPT..................................................................................................................................................1313
A.12 Configuring Ethernet Related Protection...............................................................................................................1314
A.12.1 Configuring Ethernet Ring Protection................................................................................................................1314
A.12.1.1 ENT-ERPS.......................................................................................................................................................1314
A.12.1.2 ED-ERPS.........................................................................................................................................................1317
A.12.1.3 RTRV-ERPS....................................................................................................................................................1318
A.12.1.4 DLT-ERPS.......................................................................................................................................................1322
A.12.1.5 REPT^EVT^ERPS..........................................................................................................................................1323
A.12.2 Configuring LAG................................................................................................................................................1324
A.12.2.1 ENT-LAG........................................................................................................................................................1324
A.12.2.2 ED-LAG..........................................................................................................................................................1326
A.12.2.3 DLT-LAG........................................................................................................................................................1328
A.12.2.4 RTRV-LAG.....................................................................................................................................................1329
A.12.2.5 ED-LAGSYS...................................................................................................................................................1332
A.12.2.6 RTRV-LAGSYS..............................................................................................................................................1333
A.12.2.7 ED-LAGPORT................................................................................................................................................1335
A.12.2.8 RTRV-LAGPORT...........................................................................................................................................1336
A.12.2.9 INIT-LAGPORT..............................................................................................................................................1338
A.12.2.10 ENT-DLAG...................................................................................................................................................1340
A.12.2.11 ED-DLAG......................................................................................................................................................1342
A.12.2.12 DLT-DLAG...................................................................................................................................................1343
A.12.2.13 RTRV-DLAG................................................................................................................................................1344
A.12.2.14 DLT-MCLAG................................................................................................................................................1348
A.12.2.15 ED-MCLAG..................................................................................................................................................1349
A.12.2.16 ENT-MCLAG................................................................................................................................................1351
A.12.2.17 RTRV-MCLAG.............................................................................................................................................1353
A.12.2.18 DLT-MCSP....................................................................................................................................................1355
A.12.2.19 ED-MCSP......................................................................................................................................................1356
A.12.2.20 ENT-MCSP....................................................................................................................................................1357
A.12.2.21 RTRV-MCSP.................................................................................................................................................1359
A.12.2.22 INIT-LACP-PKT...........................................................................................................................................1360
A.12.2.23 RTRV-LACP-PKT........................................................................................................................................1362
A.12.2.24 INIT-LAGSTAST-<FETH/GETH>..............................................................................................................1364
A.12.2.25 RTRV-LAGSTAT-<FETH/GETH>..............................................................................................................1365
A.12.2.26 RTRV-STATE-LAGPORT...........................................................................................................................1366
A.12.3 Configuring STP.................................................................................................................................................1368
A.12.3.1 ED-STP-VB.....................................................................................................................................................1368
A.12.3.2 RTRV-STP-VB................................................................................................................................................1370
A.12.3.3 INIT-STP-VB..................................................................................................................................................1372
A.12.3.4 ED-STP-VBLP................................................................................................................................................1374
A.12.3.5 RTRV-STP-VBLP...........................................................................................................................................1375
A.12.3.6 SW-STP-VBLP................................................................................................................................................1377
A.12.3.7 REPT^EVT^VBLP..........................................................................................................................................1379
A.12.4 Configuring VLAN SNCP .................................................................................................................................1380
A.12.4.1 ENT-VLANSNCP-PG.....................................................................................................................................1380
A.12.4.2 ED-VLANSNCP-PG.......................................................................................................................................1382
A.12.4.3 RTRV-VLANSNCP-PG..................................................................................................................................1384
A.12.4.4 DLT-VLANSNCP-PG.....................................................................................................................................1386
A.12.4.5 OPR-PROTNSW-VLANSNCP.......................................................................................................................1388
A.12.4.6 RLS-PROTNSW-VLANSNCP.......................................................................................................................1389
A.13 Configuring Ethernet Feature................................................................................................................................1390
A.13.1 Configuring Ethernet Interface ..........................................................................................................................1391
A.13.1.1 ED-<FETH/GETH/XGETH/100GETH/40GETH>........................................................................................1391
A.13.1.2 RMV-<FETH/GETH/XGETH>......................................................................................................................1398
A.13.1.3 RTRV-<FETH/GETH/XGETH/100GETH/40GETH>...................................................................................1399
A.13.1.4 RST-<FETH/GETH/XGETH>........................................................................................................................1404
A.13.1.5 OPR-LPBK-<FETH/GETH/XGETH>............................................................................................................1405
A.13.1.6 RLS-LPBK-<FETH/GETH/XGETH>............................................................................................................1407
A.13.1.7 RTRV-LPBK-<FETH/GETH/XGETH>.........................................................................................................1408
A.13.1.8 ED-ETH-VCG.................................................................................................................................................1409
A.13.1.9 RTRV-ETH-VCG............................................................................................................................................1411
A.13.1.10 ED-PORT-TRAFFIC.....................................................................................................................................1412
A.13.1.11 RTRV-PORT-TRAFFIC...............................................................................................................................1414
A.13.1.12 RTRV-PORT-TRFFLUX..............................................................................................................................1416
A.13.2 Configuring Flow................................................................................................................................................1419
A.13.2.1 ENT-FLOW.....................................................................................................................................................1419
A.13.2.2 ED-FLOW.......................................................................................................................................................1421
A.13.2.3 DLT-FLOW.....................................................................................................................................................1422
A.13.2.4 RTRV-FLOW..................................................................................................................................................1424
A.13.3 Configuring Ethernet Link..................................................................................................................................1426
A.13.3.1 ENT-ETHLINK...............................................................................................................................................1426
A.13.3.2 ED-ETHLINK.................................................................................................................................................1430
A.13.3.3 DLT-ETHLINK...............................................................................................................................................1432
A.13.3.4 RTRV-ETHLINK............................................................................................................................................1434
A.13.3.5 ENT-PW..........................................................................................................................................................1437
A.13.3.6 ED-PW.............................................................................................................................................................1439
A.13.3.7 RTRV-PW.......................................................................................................................................................1440
A.13.3.8 DLT-PW..........................................................................................................................................................1442
A.13.3.9 ENT-TUNNEL................................................................................................................................................1443
A.13.3.10 DLT-TUNNEL..............................................................................................................................................1445
A.13.3.11 RTRV-TUNNEL...........................................................................................................................................1446
A.13.3.12 ED-TUNNEL.................................................................................................................................................1447
A.13.4 Configuring Virtual Bridge.................................................................................................................................1449
A.13.4.1 ENT-VB...........................................................................................................................................................1449
A.13.4.2 ED-VB.............................................................................................................................................................1451
A.13.4.3 DLT-VB...........................................................................................................................................................1454
A.13.4.4 RTRV-VB........................................................................................................................................................1455
A.13.4.5 ENT-VLANENTRY-VB.................................................................................................................................1457
A.13.4.6 ED-VLANENTRY-VB...................................................................................................................................1458
A.13.4.7 DLT-VLANENTRY-VB.................................................................................................................................1460
A.13.4.8 RTRV-VLANENTRY-VB..............................................................................................................................1461
A.13.4.9 ED-VBLP........................................................................................................................................................1463
A.13.4.10 RTRV-VBLP.................................................................................................................................................1464
A.13.4.11 INIT-MACENTRY........................................................................................................................................1466
A.13.5 Configuring VLAN Group.................................................................................................................................1467
A.13.5.1 ENT-PORT-VLANGROUP............................................................................................................................1467
A.13.5.2 ED-PORT-VLANGROUP..............................................................................................................................1469
A.13.5.3 DLT-PORT-VLANGROUP............................................................................................................................1471
A.13.5.4 RTRV-PORT-VLANGROUP.........................................................................................................................1472
A.13.6 Configuring MAC Filter.....................................................................................................................................1474
A.13.6.1 ENT-MACENTRY-VB...................................................................................................................................1474
A.13.6.2 DLT-MACENTRY-VB...................................................................................................................................1476
A.13.6.3 RTRV-MACENTRY-VB................................................................................................................................1478
A.13.6.4 RTRV-FWDTABPHY-VB..............................................................................................................................1480
A.13.6.5 RTRV-MACSTAT..........................................................................................................................................1482
A.13.7 Configuring IGMP..............................................................................................................................................1483
A.13.7.1 ED-IGMP-VB..................................................................................................................................................1484
A.13.7.2 RTRV-IGMP-VB............................................................................................................................................1485
A.13.7.3 ENT-IGMPTABLE-VB..................................................................................................................................1486
A.13.7.4 ED-IGMPTABLE-VB..................................................................................................................................... 1488
A.13.7.5 DLT-IGMPTABLE-VB..................................................................................................................................1489
A.13.7.6 RTRV-IGMPTABLE-VB................................................................................................................................1491
A.13.7.7 RTRV-MCGROUP-VB...................................................................................................................................1493
A.13.7.8 ED-IGMP-QKLV............................................................................................................................................1494
A.13.7.9 RTRV-IGMP-QKLV....................................................................................................................................... 1496
A.13.7.10 REPT^EVT^IGMPMEMFULL.....................................................................................................................1497
A.13.8 Configuring QoS.................................................................................................................................................1498
A.13.8.1 ENT-CAR........................................................................................................................................................1498
A.13.8.2 ED-CAR..........................................................................................................................................................1500
A.13.8.3 DLT-CAR........................................................................................................................................................1502
A.13.8.4 RTRV-CAR.....................................................................................................................................................1503
A.13.8.5 ENT-COS........................................................................................................................................................1504
A.13.8.6 ED-COS........................................................................................................................................................... 1506
A.13.8.7 DLT-COS........................................................................................................................................................1507
A.13.8.8 RTRV-COS......................................................................................................................................................1508
A.13.8.9 ED-QUEUE.....................................................................................................................................................1510
A.13.8.10 RTRV-QUEUE..............................................................................................................................................1512
A.13.8.11 ED-PORT-SHAPING....................................................................................................................................1513
A.13.8.12 RTRV-PORT-SHAPING..............................................................................................................................1515
A.13.8.13 RTRV-FLUX-FLOW....................................................................................................................................1516
A.13.9 Configuring Ethernet Interface Mirror...............................................................................................................1518
A.13.9.1 ENT-MIRROR................................................................................................................................................1518
A.13.9.2 ED-MIRROR................................................................................................................................................... 1520
A.13.9.3 RTRV-MIRROR..............................................................................................................................................1521
A.13.9.4 DLT-MIRROR................................................................................................................................................1523
A.13.9.5 DLT-SRVMIRROR-ETHLINK......................................................................................................................1524
A.13.9.6 ENT-SRVMIRROR-ETHLINK......................................................................................................................1526
A.13.9.7 RTRV-SRVMIRROR-ETHLINK...................................................................................................................1527
A.13.9.8 DLT-SRVMIRROR-PW.................................................................................................................................1529
A.13.9.9 ENT-SRVMIRROR-PW.................................................................................................................................1531
A.13.9.10 RTRV-SRVMIRROR-PW............................................................................................................................1532
A.13.9.11 DLT-SRVMIRROR-TUNNEL.....................................................................................................................1533
A.13.9.12 ENT-SRVMIRROR-TUNNEL.....................................................................................................................1534
A.13.9.13 RTRV-SRVMIRROR-TUNNEL..................................................................................................................1536
A.13.10 Configuring OAM............................................................................................................................................1537
A.13.10.1 OPR-OAM-LB..............................................................................................................................................1537
A.13.10.2 OPR-OAM-LT...............................................................................................................................................1539
A.13.10.3 ENT-MD........................................................................................................................................................1541
A.13.10.4 DLT-MD........................................................................................................................................................1542
A.13.10.5 RTRV-MD.....................................................................................................................................................1544
A.13.10.6 ENT-MA........................................................................................................................................................1545
A.13.10.7 DLT-MA........................................................................................................................................................1546
A.13.10.8 RTRV-MA.....................................................................................................................................................1547
A.13.10.9 ENT-MP........................................................................................................................................................1549
A.13.10.10 ED-MP.........................................................................................................................................................1554
A.13.10.11 DLT-MP......................................................................................................................................................1557
A.13.10.12 RTRV-MP....................................................................................................................................................1558
A.13.10.13 REPT^EVT^OAMSERVICELOOP...........................................................................................................1562
A.13.10.14 STA-OAM-PING........................................................................................................................................1563
A.13.10.15 STP-OAM-PING.........................................................................................................................................1564
A.13.10.16 STA-OAM-PERDECT................................................................................................................................1565
A.13.10.17 STP-OAM-PERDECT.................................................................................................................................1567
A.13.10.18 ED-P2POAM-ADMIN................................................................................................................................1568
A.13.10.19 RTRV-P2POAM-ADMIN...........................................................................................................................1571
A.13.11 Other Maintenace commands...........................................................................................................................1574
A.13.11.1 STA-PING-<FETH/GETH/XGETH>...........................................................................................................1574
A.13.11.2 STP-PING-<FETH/GETH/XGETH>............................................................................................................1576
A.13.11.3 RTRV-PING-<FETH/GETH/XGETH>........................................................................................................1577
A.13.11.4 INIT-PING-<FETH/GETH/XGETH>..........................................................................................................1579
A.13.11.5 REPT^EVT^PING.........................................................................................................................................1580
A.13.11.6 STA-CAPT....................................................................................................................................................1582
A.13.11.7 STP-CAPT.....................................................................................................................................................1584
A.13.11.8 RTRV-CAPT.................................................................................................................................................1585
A.13.11.9 INIT-TEST-<FETH/GETH/VCG>...............................................................................................................1586
A.13.11.10 RTRV-TEST-<FETH/GETH/VCG>...........................................................................................................1588
A.13.11.11 STA-TEST-<FETH/GETH/VCG>..............................................................................................................1589
A.13.11.12 STP-TEST-<FETH/GETH/VCG>..............................................................................................................1591
A.14 Configuring OTN Overhead..................................................................................................................................1592
A.14.1 ED-<ODUN>......................................................................................................................................................1592
A.14.2 RTRV-<ODUN>................................................................................................................................................1599
A.14.3 ED-<OTUN>......................................................................................................................................................1606
A.14.4 RTRV-<OTUN>.................................................................................................................................................1610
A.14.5 ED-<TCMMOD2>.............................................................................................................................................1613
A.14.6 RTRV-<TCMMOD2>........................................................................................................................................1617
A.15 Automatic Optical Power Management.................................................................................................................1621
A.15.1 Configuring Intelligent Power Adjustment (IPA)..............................................................................................1621
A.15.1.1 ENT-IPA..........................................................................................................................................................1621
A.15.1.2 ED-IPA............................................................................................................................................................1623
A.15.1.3 DLT-IPA..........................................................................................................................................................1626
A.15.1.4 RTRV-IPA.......................................................................................................................................................1627
A.15.1.5 ED-IPA-WDM.................................................................................................................................................1631
A.15.1.6 OPR-IPA-WDM..............................................................................................................................................1632
A.15.1.7 RTRV-IPA-WDM...........................................................................................................................................1633
A.15.1.8 OPR-IPA..........................................................................................................................................................1635
A.15.1.9 ENT-IPA-ASTDECT......................................................................................................................................1636
A.15.1.10 DLT-IPA-ASTDECT....................................................................................................................................1637
A.15.1.11 RTRV-IPA-ASTDECT..................................................................................................................................1639
A.15.1.12 REPT^EVT^IPA............................................................................................................................................1640
A.15.2 Configuring Automatic Power Equilibrium (APE)............................................................................................1642
A.15.2.1 ENT-APE.........................................................................................................................................................1642
A.15.2.2 ED-APE...........................................................................................................................................................1644
A.15.2.3 DLT-APE.........................................................................................................................................................1645
A.15.2.4 OPR-APE.........................................................................................................................................................1646
A.15.2.5 RTRV-APE......................................................................................................................................................1647
A.15.2.6 ED-APE-WCH................................................................................................................................................1649
A.15.2.7 RTRV-APE-WCH...........................................................................................................................................1651
A.15.2.8 REPT^EVT^APE.............................................................................................................................................1652
A.15.3 Configuring Automatic Level Control (ALC)....................................................................................................1655
A.15.3.1 ENT-ALC-NODE............................................................................................................................................1655
A.15.3.2 ED-ALC-NODE..............................................................................................................................................1657
A.15.3.3 DLT-ALC-NODE............................................................................................................................................1659
A.15.3.4 RTRV-ALC-NODE.........................................................................................................................................1660
A.15.3.5 OPR-ALC-CHAIN..........................................................................................................................................1664
A.15.3.6 RTRV-ALC-CHAIN.......................................................................................................................................1665
A.15.3.7 OPR-ALC-NODE............................................................................................................................................1668
A.15.3.8 INIT-ALC-LOG..............................................................................................................................................1669
A.15.3.9 RTRV-ALC-LOG............................................................................................................................................1670
A.15.3.10 REPT^EVT^ALC..........................................................................................................................................1672
A.16 Configuring MCA..................................................................................................................................................1677
A.16.1 ED-MCACHN....................................................................................................................................................1677
A.16.2 RTRV-MCACHN...............................................................................................................................................1679
A.16.3 RTRV-MCADATA............................................................................................................................................1680
A.17 Configuring Tunable Dispersion Compensator ....................................................................................................1682
A.17.1 ED-TDC..............................................................................................................................................................1682
A.17.2 OPR-TDC...........................................................................................................................................................1683
A.17.3 RTRV-TDC........................................................................................................................................................1684
A.17.4 REPT-EVT-TDCSCAN.....................................................................................................................................1686
A.18 System Monitor.....................................................................................................................................................1687
A.18.1 ED-DST-V2........................................................................................................................................................1687
A.18.2 RTRV-DST-V2...................................................................................................................................................1690
A.18.3 RTRV-CHECK-PERIOD...................................................................................................................................1692
A.18.4 RTRV-CPU-PEAKINFO...................................................................................................................................1693
A.18.5 RTRV-CPUUSAGE...........................................................................................................................................1699
A.18.6 RTRV-LIST........................................................................................................................................................1701
A.18.7 RTRV-SCCID.....................................................................................................................................................1711
A.18.8 RTRV-MEMPEAK-INFO..................................................................................................................................1713
A.18.9 RTRV-MEMUSAGE-INFO...............................................................................................................................1714
A.18.10 RTRV-MEMUTIL-INFO.................................................................................................................................1715
A.18.11 RTRV-MODULE-DUMPINFO.......................................................................................................................1716
A.18.12 RTRV-MODULE-LISTINFO..........................................................................................................................1718
A.18.13 RTRV-QUELENALM-STATE........................................................................................................................1719
A.18.14 RTRV-REBOOT-LOG.....................................................................................................................................1720
A.18.15 RTRV-RESERVEMEM...................................................................................................................................1722
A.18.16 RTRV-SWTTHRINFO.....................................................................................................................................1724
A.18.17 RTRV-SYMADDR..........................................................................................................................................1725
A.18.18 RTRV-TASKSTACK.......................................................................................................................................1726
A.18.19 RTRV-TASKONMSGQUE.............................................................................................................................1728
A.18.20 RTRV-TASKONSEM......................................................................................................................................1729
A.18.21 RTRV-VFS-PEAKINFO..................................................................................................................................1731
A.18.22 RTRV-BDINFO-EQPT....................................................................................................................................1732
A.18.23 SET-CPUTESTSTA.........................................................................................................................................1734
A.18.24 WRT-BB...........................................................................................................................................................1735
A.19 Performance Management.....................................................................................................................................1736
A.19.1 ED-PMALMCTRL-<MOD2>............................................................................................................................1736
A.19.2 RTRV-PMALMCTRL-<MOD2>......................................................................................................................1739
A.19.3 ED-PMHISTCTRL.............................................................................................................................................1742
A.19.4 RTRV-PMHISTCTRL.......................................................................................................................................1743
A.19.5 INIT-REG-<MOD2>..........................................................................................................................................1745
A.19.6 RTRV-PM-<MOD2>.........................................................................................................................................1747
A.19.7 REPT^PM^<MOD2>.........................................................................................................................................1749
A.19.8 RTRV-PMDAY..................................................................................................................................................1751
A.19.9 SET-PMDAY.....................................................................................................................................................1752
A.19.10 RTRV-TH-<MOD2>........................................................................................................................................1753
A.19.11 SET-TH-<MOD2>...........................................................................................................................................1756
A.19.12 RTRV-ATTRTCA-<MOD2>...........................................................................................................................1758
A.19.13 SET-ATTRTCA-<MOD2>..............................................................................................................................1761
A.19.14 INIT-PMSTAT-<MOD2>................................................................................................................................1763
A.19.15 RTRV-PMSTAT-<MOD2>.............................................................................................................................1765
A.19.16 INIT-PMHIST-<MOD2>.................................................................................................................................1767
A.19.17 RTRV-PMHIST-<MOD2>...............................................................................................................................1769
A.19.18 REPT^PM^FALLING......................................................................................................................................1771
A.19.19 REPT^PM^RISING..........................................................................................................................................1772
A.20 Alarm and Event Management..............................................................................................................................1774
A.20.1 ALW-AUD-ALL................................................................................................................................................1774
A.20.2 INH-AUD-ALL..................................................................................................................................................1775
A.20.3 ALW-VSL-ALL.................................................................................................................................................1776
A.20.4 INH-VSL-ALL...................................................................................................................................................1777
A.20.5 ED-ALMTH-<MOD2>......................................................................................................................................1778
A.20.6 RTRV-ALMTH-<MOD2>.................................................................................................................................1780
A.20.7 RTRV-ALMTHRNG-<MOD2>.........................................................................................................................1782
A.20.8 REPT^ALM^<MOD2>......................................................................................................................................1784
A.20.9 REPT^EVT^<MOD2>.......................................................................................................................................1786
A.20.10 RLS-EXT-CONT..............................................................................................................................................1788
A.20.11 RTRV-EXT-CONT..........................................................................................................................................1789
A.20.12 OPR-EXT-CONT.............................................................................................................................................1791
A.20.13 RTRV-ALM-<MOD2>....................................................................................................................................1792
A.20.14 RTRV-ALM-CONTIME..................................................................................................................................1796
A.20.15 SET-ALM-CONTIME.....................................................................................................................................1797
A.20.16 RTRV-ALM-ENV............................................................................................................................................1798
A.20.17 REPT^ALM^ENV............................................................................................................................................1800
A.20.18 RTRV-ATTR-<MOD2>...................................................................................................................................1801
A.20.19 SET-ATTR-<MOD2>......................................................................................................................................1803
A.20.20 RTRV-ATTR-ENV..........................................................................................................................................1805
A.20.21 SET-ATTR-ENV..............................................................................................................................................1807
A.20.22 RTRV-ATTR-CONT........................................................................................................................................1809
A.20.23 SET-ATTR-CONT...........................................................................................................................................1810
A.20.24 RTRV-ATTR-CONTTM..................................................................................................................................1812
A.20.25 SET-ATTR-CONTTM.....................................................................................................................................1813
A.20.26 RTRV-COND-<MOD2>..................................................................................................................................1814
A.20.27 OPR-ACO-ALL................................................................................................................................................1817
A.20.28 OPR-ALM-CONFIRM.....................................................................................................................................1818
A.20.29 RTRV-ALM-CONFIRM..................................................................................................................................1819
A.20.30 ED-ALM-CONFIRM.......................................................................................................................................1820
A.21 Configuring LPT....................................................................................................................................................1821
A.21.1 ED-LPT...............................................................................................................................................................1821
A.21.2 RTRV-LPT.........................................................................................................................................................1822
A.22 Configuring Loopback...........................................................................................................................................1823
A.22.1 OPR-LPBK-<MOD2>........................................................................................................................................1824
A.22.2 RLS-LPBK-<MOD2>........................................................................................................................................1825
A.22.3 RTRV-LPBK-<MOD2>.....................................................................................................................................1826
A.22.4 ED-BDXCLOOP................................................................................................................................................1828
A.22.5 RTRV-BDXCLOOP...........................................................................................................................................1829
A.23 Connection Test.....................................................................................................................................................1830
A.23.1 CONN-TST-<OTUN/ODUN/OCN/STMN>.....................................................................................................1830
A.23.2 CONN-TST-<40GETH/100GETH>..................................................................................................................1832
A.23.3 DISC-TST-<OTUN/ODUN/OCN/STMN/40GETH/100GETH>......................................................................1834
A.23.4 RTRV-RSLT-<OTUN/ODUN/OCN/STMN>...................................................................................................1835
A.23.5 RTRV-RSLT-<40GETH/100GETH>................................................................................................................1836
A.23.6 RTRV-TST-<OTUN/ODUN/OCN/STMN>......................................................................................................1838
A.23.7 RTRV-TST-<40GETH/100GETH>...................................................................................................................1839
A.23.8 REPT^EVT^PRBS.............................................................................................................................................1841
A.24 System Maintenance..............................................................................................................................................1843
A.24.1 ABT-ERRPICK..................................................................................................................................................1843
A.24.2 ACK-ERRPICK..................................................................................................................................................1844
A.24.3 OPR-ERRPICK..................................................................................................................................................1845
A.24.4 REPT^EVT^ERRPICKEND..............................................................................................................................1846
A.24.5 REPT^EVT^ERRPICKPROGRESS..................................................................................................................1848
A.24.6 REPT^EVT^ERRPICKUPLOAD......................................................................................................................1849
A.24.7 RTRV-ERRPICK-STATE..................................................................................................................................1850
A.24.8 RTRV-ERRPICK-TYPE....................................................................................................................................1851
A.24.9 ALW-MSG-ALL................................................................................................................................................1852
A.24.10 INH-MSG-ALL................................................................................................................................................1854
A.24.11 RTRV-MSG-ALL.............................................................................................................................................1855
A.24.12 ALW-PMREPT-ALL.......................................................................................................................................1856
A.24.13 INH-PMREPT-ALL.........................................................................................................................................1857
A.24.14 RTRV-PMREPT-ALL......................................................................................................................................1858
A.24.15 ALW-MSG-DBCHG........................................................................................................................................1860
A.24.16 INH-MSG-DBCHG..........................................................................................................................................1861
A.24.17 RTRV-MSG-DBCHG......................................................................................................................................1862
A.24.18 COPY-FILE......................................................................................................................................................1863
A.24.19 INIT-SYS..........................................................................................................................................................1864
A.24.20 REPT^DBCHG.................................................................................................................................................1867
A.24.21 RTRV-CMDNODE-INFO...............................................................................................................................1869
A.24.22 RTRV-ELABEL...............................................................................................................................................1870
A.24.23 RTRV-LIST......................................................................................................................................................1871
A.24.24 RTRV-SCCID...................................................................................................................................................1882
A.24.25 RTRV-TEST-VER...........................................................................................................................................1883
A.24.26 RTRV-VRCBVER...........................................................................................................................................1885
A.24.27 RTRV-PATCH-LIST.......................................................................................................................................1886
A.24.28 ED-DUMP-CLEARCODE...............................................................................................................................1887
A.24.29 ED-DUMP-SETCON.......................................................................................................................................1888
A.24.30 ED-DUMP-SETCODE.....................................................................................................................................1890
A.24.31 REPT GSPDUMP.............................................................................................................................................1891
A.24.32 RTRV-GSP-TEST............................................................................................................................................1892
A.24.33 WRT-BB...........................................................................................................................................................1893
A.24.34 PTP...................................................................................................................................................................1894
A.25 Security Management............................................................................................................................................1896
A.25.1 ACT-USER.........................................................................................................................................................1896
A.25.2 ALW-USER-SECU............................................................................................................................................1897
A.25.3 DLT-USER-SECU.............................................................................................................................................1898
A.25.4 ED-USER-SECU................................................................................................................................................1899
A.25.5 ENT-USER-SECU.............................................................................................................................................1901
A.25.6 INH-USER-SECU..............................................................................................................................................1903
A.25.7 RTRV-USER-SECU...........................................................................................................................................1904
A.25.8 CANC-USER......................................................................................................................................................1906
A.25.9 RTRV-CHECKINFO-SECU..............................................................................................................................1907
A.25.10 ED-PID.............................................................................................................................................................1908
A.25.11 ED-WARNSCR................................................................................................................................................1909
A.25.12 RTRV-WARNSCR...........................................................................................................................................1910
A.25.13 ED-WARNSCRSTATE...................................................................................................................................1912
A.25.14 RTRV-WARNSCRSTATE..............................................................................................................................1913
A.25.15 REPT^LOGOFF...............................................................................................................................................1914
A.25.16 REPT^EVT^SECU...........................................................................................................................................1915
A.25.17 REPT^ACCESS^WARNING..........................................................................................................................1916
A.25.18 REPT^ACCOUNTEXPIRED^WARNING.....................................................................................................1917
A.25.19 REPT^EVT^OPLOGNEEDUPLOAD.............................................................................................................1919
A.25.20 REPT^EVT^OPLOGCIRCLE..........................................................................................................................1920
A.25.21 REPT^MODIFYPASSWORD^NOTIFY.........................................................................................................1921
A.25.22 DLT-SSH-HOSTKEY......................................................................................................................................1922
A.25.23 ED-SSH-PASSPHRASE..................................................................................................................................1923
A.25.24 DLT-SSH-PEERPUBKEY...............................................................................................................................1924
A.25.25 ED-SSH-PEERPUBKEY.................................................................................................................................1925
A.25.26 ENT-SSH-PEERPUBKEY...............................................................................................................................1927
A.25.27 ENT-SSH-HOSTKEY......................................................................................................................................1928
A.25.28 RTRV-SSH-HOSTKEY...................................................................................................................................1929
A.25.29 RTRV-SSH-HOSTKEYLIST...........................................................................................................................1931
A.25.30 ED-USER-SSHPEERPUBKEY.......................................................................................................................1932
A.25.31 ED-USER-SSHAUTHTYPE............................................................................................................................1933
A.25.32 RTRV-USER-SSH...........................................................................................................................................1935
A.25.33 RTRV-SSH-PEERPUBKEYINFO...................................................................................................................1936
A.25.34 RTRV-SSH-PEERPUBKEYLIST...................................................................................................................1937
A.25.35 RTRV-SSH-SRVINFO.....................................................................................................................................1939
A.26 Backup and Recover..............................................................................................................................................1940
A.26.1 ED-PE-DBPERIOD............................................................................................................................................1940
A.26.2 RTRV-PE-DBPERIOD......................................................................................................................................1941
A.26.3 ED-PE-DATA.....................................................................................................................................................1942
A.26.4 RECOVER-PE-DATA.......................................................................................................................................1943
A.26.5 RTRV-DBBKUP................................................................................................................................................1945
A.26.6 RTRV-FREESPACE..........................................................................................................................................1947
A.26.7 SCHED-DBBKUP..............................................................................................................................................1949
A.26.8 REPT^EVT^DBBKUP.......................................................................................................................................1952
A.26.9 RTRV-PE-AUTOBACKUP...............................................................................................................................1953
A.26.10 SET-PE-AUTOBACKUP.................................................................................................................................1954
A.26.11 REPT^EVT^PEBACKUPFAIL.......................................................................................................................1955
A.26.12 RTRV-VERMATCH........................................................................................................................................1957
A.26.13 REPT^EVT^DBFDLACTIVATED.................................................................................................................1958
A.27 System Update.......................................................................................................................................................1959
A.27.1 ABT-CMD..........................................................................................................................................................1960
A.27.2 ACT-SWDLGROUP..........................................................................................................................................1961
A.27.3 DLT-SWDLGROUP..........................................................................................................................................1962
A.27.4 ED-SWDLGROUP.............................................................................................................................................1963
A.27.5 ED-SWDL-CUSTOM........................................................................................................................................1965
A.27.6 AUD-SWDLGROUP.........................................................................................................................................1966
A.27.7 RTRV-SWDLGROUP.......................................................................................................................................1967
A.27.8 ED-LOADSOFT.................................................................................................................................................1968
A.27.9 RTRV-LOADSOFT...........................................................................................................................................1969
A.27.10 RTRV-LOADSUPPORTINFO........................................................................................................................1970
A.27.11 ED-GROUPMODE..........................................................................................................................................1972
A.27.12 RTRV-GROUPSTATUS..................................................................................................................................1973
A.27.13 REPT^GROUP^ACTIVITED..........................................................................................................................1974
A.27.14 COMMIT-SW...................................................................................................................................................1976
A.27.15 COPY-RFILE...................................................................................................................................................1977
A.27.16 COPY-OLDVERFILE......................................................................................................................................1979
A.27.17 CPY-MEM........................................................................................................................................................1980
A.27.18 DLT-FILE.........................................................................................................................................................1981
A.27.19 ENT-SWDU-DUINFO.....................................................................................................................................1982
A.27.20 RESET-ACTGROUP.......................................................................................................................................1984
A.27.21 RTRV-FILE......................................................................................................................................................1984
A.27.22 RTRV-FPATROL-STATE...............................................................................................................................1986
A.27.23 RTRV-FREESPACE........................................................................................................................................1987
A.27.24 RTRV-SOFT-VER...........................................................................................................................................1988
A.27.25 RTRV-SWDU-DUINFO..................................................................................................................................1990
A.27.26 RTRV-SWDU-DUSTATE...............................................................................................................................1991
A.27.27 RTRV-UPGRADE-BDLIST............................................................................................................................1992
A.27.28 RTRV-PKGTYPE............................................................................................................................................1993
A.27.29 RTRV-PKGVER..............................................................................................................................................1995
A.27.30 RTRV-PKTSTAT.............................................................................................................................................1996
A.27.31 RTRV-STATE..................................................................................................................................................1997
A.27.32 REPT^BKPKG^START...................................................................................................................................2002
A.27.33 REPT^BKPKG^END.......................................................................................................................................2003
A.27.34 REPT^EVT^ACTIVATED..............................................................................................................................2004
A.27.35 REPT^EVT^AUTOSWDL...............................................................................................................................2005
A.27.36 REPT^EVT^AUTOSYNC...............................................................................................................................2006
A.27.37 REPT^EVT^BDMATCHFAILED...................................................................................................................2008
A.27.38 REPT^EVT^BDSWDL....................................................................................................................................2009
A.27.39 REPT^EVT^COMMITEND............................................................................................................................2010
A.27.40 REPT^EVT^COMMITFAILED......................................................................................................................2011
A.27.41 REPT^EVT^COMMITRSLT...........................................................................................................................2012
A.27.42 REPT^EVT^CPYMEM....................................................................................................................................2013
A.27.43 REPT^EVT^FXFR...........................................................................................................................................2015
A.27.44 REPT^EVT^FXFRHALT................................................................................................................................2016
A.27.45 REPT^EVT^CPYMEMEND............................................................................................................................2017
A.27.46 REPT^EVT^INIT.............................................................................................................................................2018
A.27.47 REPT^EVT^NOSWINPKG.............................................................................................................................2020
A.27.48 REPT^EVT^OFFLINEINPROCESS...............................................................................................................2021
A.27.49 REPT^EVT^PKGNOTSAME..........................................................................................................................2022
A.27.50 REPT^EVT^PROGRESS.................................................................................................................................2023
A.27.51 REPT^EVT^ROLLBACKSTART...................................................................................................................2024
A.27.52 REPT^EVT^ROLLBACKEND.......................................................................................................................2025
A.27.53 REPT^EVT^ROLLBACKRSLT......................................................................................................................2026
A.27.54 REPT^EVT^SLVMATCHFAILED.................................................................................................................2027
A.27.55 REPT^EVT^SWDL..........................................................................................................................................2028
A.27.56 ABT-COPY-END.............................................................................................................................................2031
A.27.57 RTRV-SWDL-ONLINEBDLIST.....................................................................................................................2032
A.27.58 RTRV-SWDL-DISTRIBUTEINFO.................................................................................................................2033
A.27.59 RTRV-SWDL-SUBGROUPSTATUS.............................................................................................................2034
A.27.60 RTRV-SWDL-SUBGROUP............................................................................................................................2036
A.27.61 RTRV-SWDL-BDLIST....................................................................................................................................2038
A.27.62 RTRV-SWDL-CUSTOM.................................................................................................................................2039
A.27.63 RTRV-SWDU-DUMODE................................................................................................................................2040
A.27.64 SET-FPATROL-STATE..................................................................................................................................2041
A.27.65 STA-NESOFT..................................................................................................................................................2042
A.28 Patch Management.................................................................................................................................................2043
A.28.1 ACT-PATCH......................................................................................................................................................2043
A.28.2 DEACT-PATCH.................................................................................................................................................2044
A.28.3 DLT-PATCH......................................................................................................................................................2046
A.28.4 LOAD-PATCH...................................................................................................................................................2047
A.28.5 RTRV-PATCH...................................................................................................................................................2048
A.28.6 RUN-PATCH.....................................................................................................................................................2049
A.28.7 SYNC-PATCH...................................................................................................................................................2051
A.28.8 LOAD-PATCHPKG...........................................................................................................................................2052
A.28.9 LOAD-PATCHPKGMEM.................................................................................................................................2053
A.28.10 ACT-PATCHPKG............................................................................................................................................2054
A.28.11 DEACT-PATCHPKG.......................................................................................................................................2055
A.28.12 RUN-PATCHPKG...........................................................................................................................................2057
A.28.13 DLT-PATCHPKG............................................................................................................................................2058
A.28.14 INST-PATCHPKG...........................................................................................................................................2059
A.28.15 ROLLBACK-PATCHPKG..............................................................................................................................2061
A.28.16 RTRV-PATCHPKG-INFO...............................................................................................................................2062
A.28.17 RTRV-PATCHPKG-STATE...........................................................................................................................2064
A.28.18 CHK-PATCHPKG...........................................................................................................................................2066
A.28.19 REPT^PATCHPKG..........................................................................................................................................2067
A.28.20 RTRV-PATCH-RESULT.................................................................................................................................2069
A.29 Database Management...........................................................................................................................................2070
A.29.1 CHECK-DBMS-CFDB......................................................................................................................................2070
A.29.2 COPY-DBMS-ALL............................................................................................................................................2071
A.29.3 RTRV-DBMS-AUTOBACKUP........................................................................................................................2073
A.29.4 SET-DBMS-AUTOBACKUP............................................................................................................................2074
A.29.5 RTRV-DBMS-BACKUPTIME..........................................................................................................................2075
A.29.6 ED-DBMS-CYCLEBACKUP............................................................................................................................2076
A.29.7 RTRV-DBMS-CYCLEBACKUP......................................................................................................................2077
A.29.8 RTRV-DBMS-DBF............................................................................................................................................2078
A.29.9 RTRV-DBMS-LIST...........................................................................................................................................2079
A.29.10 RTRV-DBMS-MODE......................................................................................................................................2081
A.29.11 RTRV-DBMS-NDBF.......................................................................................................................................2082
A.29.12 RTRV-DBMS-PMMODE................................................................................................................................2083
A.29.13 RTRV-DBMS-PERIOD...................................................................................................................................2084
A.29.14 RTRV-DBMS-RECNO....................................................................................................................................2085
A.30 Log Management...................................................................................................................................................2086
A.30.1 INIT-LOG...........................................................................................................................................................2086
A.30.2 RTRV-LOG........................................................................................................................................................2088
A.30.3 RTRV-AO...........................................................................................................................................................2089
A.30.4 RTRV-DBCHGSEQ...........................................................................................................................................2091
A.30.5 RTRV-ERRLOG................................................................................................................................................2092
A.30.6 RTRV-LOG-BYMOD........................................................................................................................................2093
A.30.7 RTRV-LOG-BYLEVEL.....................................................................................................................................2095
A.30.8 RTRV-LOG-BYTIME.......................................................................................................................................2097
A.30.9 TEST-DMM.......................................................................................................................................................2098
A.31 License Management.............................................................................................................................................2100
A.31.1 RTRV-LCS-INFO..............................................................................................................................................2100
A.31.2 RTRV-LCS-ESN................................................................................................................................................2102
A.31.3 RTRV-LCS-CTRLITEM....................................................................................................................................2103
A.31.4 VERIFY-LCSFILE.............................................................................................................................................2104
A.31.5 ACT-LCS............................................................................................................................................................2106
A.31.6 CANC-LCS.........................................................................................................................................................2107
A.31.7 ABT-LCS............................................................................................................................................................2108
A.31.8 ED-LICENSE.....................................................................................................................................................2109
A.31.9 RTRV-LICENSE................................................................................................................................................2111
A.32 TL1 Parameters......................................................................................................................................................2112
A.32.1 Port Numbering..................................................................................................................................................2112
A.32.1.1 Rule for Port Numbering.................................................................................................................................2112
A.32.1.2 Port Numbering on Transponder Cards...........................................................................................................2113
A.32.1.3 Port Numbering on Line Cards........................................................................................................................2119
A.32.1.4 Port Numbering on Tributary Cards................................................................................................................2120
A.32.1.5 Port Numbering on Other Cards......................................................................................................................2123
A.32.2 Access Identifier (AID)......................................................................................................................................2136
A.32.2.1 ALC.................................................................................................................................................................2136
A.32.2.2 APE..................................................................................................................................................................2140
A.32.2.3 CFP..................................................................................................................................................................2144
A.32.2.4 CLNT...............................................................................................................................................................2145
A.32.2.5 CRS-OHBYTE................................................................................................................................................2153
A.32.2.6 EC....................................................................................................................................................................2154
A.32.2.7 EQPT...............................................................................................................................................................2157
A.32.2.8 EQPT-PG.........................................................................................................................................................2174
A.32.2.9 FCMOD2.........................................................................................................................................................2174
A.32.2.10 FIBER............................................................................................................................................................2178
A.32.2.11 FFP.................................................................................................................................................................2196
A.32.2.12 GCC/DCC......................................................................................................................................................2224
A.32.2.13 IPA.................................................................................................................................................................2235
A.32.2.14 LPT................................................................................................................................................................2247
A.32.2.15 MCA..............................................................................................................................................................2252
A.32.2.16 OC..................................................................................................................................................................2253
A.32.2.17 OCH...............................................................................................................................................................2261
A.32.2.18 OCN/STMN...................................................................................................................................................2276
A.32.2.19 OMS...............................................................................................................................................................2281
A.32.2.20 OSC................................................................................................................................................................2285
A.32.2.21 OTS................................................................................................................................................................2287
A.32.2.22 OTUN............................................................................................................................................................2288
A.32.2.23 ODUN............................................................................................................................................................2298
A.32.2.24 OXC-NEPORT..............................................................................................................................................2321
A.32.2.25 PORT.............................................................................................................................................................2336
A.32.2.26 PROTNSW-EQPT.........................................................................................................................................2351
A.32.2.27 TDC...............................................................................................................................................................2352
A.32.2.28 TRAFFICMOD2............................................................................................................................................2355
A.32.2.29 TST................................................................................................................................................................2360
A.32.2.30 WDM.............................................................................................................................................................2371
A.32.3 Parameter Description........................................................................................................................................2382
A.32.3.1 ALARMTYPE.................................................................................................................................................2382
A.32.3.2 CONDTYPE....................................................................................................................................................2383
A.32.3.3 CONTTYPE....................................................................................................................................................2400
A.32.3.4 DEVICETYPE.................................................................................................................................................2401
A.32.3.5 DIRN................................................................................................................................................................2401
A.32.3.6 EVENTID........................................................................................................................................................2401
A.32.3.7 LPBKTYPE.....................................................................................................................................................2402
A.32.3.8 LTCACTEN....................................................................................................................................................2402
A.32.3.9 MOD2..............................................................................................................................................................2402
A.32.3.10 MONTYPE....................................................................................................................................................2403
A.32.3.11 OPRT.............................................................................................................................................................2412
A.32.3.12 PLDTYPE......................................................................................................................................................2413
A.32.3.13 PST_STATE..................................................................................................................................................2415
A.32.3.14 RVRTV..........................................................................................................................................................2415
A.32.3.15 SAFE..............................................................................................................................................................2415
A.32.3.16 SC..................................................................................................................................................................2415
A.32.3.17 SST_STATE..................................................................................................................................................2416
A.32.3.18 STATE...........................................................................................................................................................2418
A.32.3.19 STATELEVEL..............................................................................................................................................2419
A.32.3.20 SWITCHSTATE............................................................................................................................................2419
A.32.3.21 TYPE.............................................................................................................................................................2419
A.32.3.22 WORKMODE of Ethernet port.....................................................................................................................2420
A.32.3.23 WORKMODE of WDM equipment..............................................................................................................2421
A.33 Parameters Related to State Model........................................................................................................................2421
B Glossary....................................................................................................................................2425
2.1 Overview
When installing, operating, or maintaining Huawei equipment, follow the safety instructions
and take the essential safety precautions attached to the equipment or described in the product
documentation to prevent personal injuries.
2.2 Alarm and Safety Symbols
During equipment installation and maintenance, observe the precautions indicated by the alarm
and safety symbols to help prevent personal injury or equipment damage.
2.3 Electrical Safety
This section describes safety precautions regarding high voltage, thunderstorms, high leakage
current, power cables, fuses, and electrostatic discharge.
2.4 Inflammable Environment
This section describes safety precautions for the operating environment of a device.
2.5 Battery
This section describes safety precautions you must take when performing operations on storage
batteries and lithium batteries.
2.6 Laser
When installing and maintaining equipment, observe the laser safety precautions to prevent
personal injury or equipment damage. Note that Huawei equipment complies with IEC 60825-1
and IEC 60825-2.
2.7 Short Circuit
Exercise caution where you place metallic tools so that you do not cause a short circuit in any
equipment.
2.8 ESD
During installation and maintenance, follow antistatic procedures to prevent equipment damage:
2.9 Working at Heights
This section describes safety precautions you must take when working at heights.
2.10 Equipment Safety
This section describes safety precautions you must take when drilling holes, handling sharp
objects, performing operations on fans, or carrying heavy objects.
2.11 Working on Equipment with Power Applied
When you perform operations on the equipment when power is applied, ensure that you take the
safety precautions to prevent personal injury or equipment damage.
2.12 Miscellaneous
This section describes the safety precautions you must take when removing and reinstalling
boards, fibers and pluggable optical modules, bundling signal cables, and routing cables at a low
temperature.
2.1 Overview
When installing, operating, or maintaining Huawei equipment, follow the safety instructions
and take the essential safety precautions attached to the equipment or described in the product
documentation to prevent personal injuries.
DANGER
Before performing any operation, read the instructions and precautions carefully to prevent the
possibility of accidents. The Caution, Warning and Danger signs in other documents do not
cover all the safety precautions that must be followed. The most important safety precautions
are provided.
When operating equipment, adhere to the local laws and regulations. The precautions listed in
this chapter are in compliance with the local safety regulations.
When operating Huawei equipment, follow all the precautions and the special safety instructions
of Huawei.
l Only trained and qualified personnel are allowed to install, operate, and maintain Huawei
equipment.
l Only the qualified personnel are permitted to dismantle safety appliances and repair Huawei
devices.
l Only the personnel authenticated or authorized by Huawei are permitted to replace or swap
Huawei devices or parts of Huawei devices (including software).
l The operating personnel must immediately report the faults or errors that may cause safety
problems to the person in charge.
Grounding Requirements
The ground connections of Huawei equipment must comply with ETS 300 253 and GR 1089
CORE. The following requirements only apply to equipment that must be grounded:
l When installing a device, first connect the ground cable to the device. When uninstalling
the device, disconnect the ground cable lastly.
l Ensure that the ground conductor is intact.
l Do not operate the device in the absence of a suitably installed ground conductor.
l Ensure that the device is permanently connected to the protection ground before operation.
Before operating the device, check the electrical connections of the device, and ensure that
the device is properly grounded.
Human Safety
l Do not operate the device or cables during thunderstorm weather.
l To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to
telecommunication network voltage (TNV) circuits.
l Do not look into optical ports without eye protection. Otherwise, eyes may be hurt by laser
beams.
l Before operating a device, wear an ESD coat, ESD gloves, and an ESD wrist strap. In
addition, get off the conductive objects, such as jewelry and watches, to prevent electric
shock and burn.
l In case of fire, leave the building or site where the device is located and press the fire alarm
button or dial the telephone number for fire alarms. Do not enter the building on fire again
in any situation.
Equipment Safety
l Before performing any operation, install the equipment firmly on the ground or other rigid
objects, such as on a wall or in a rack.
l When the system is working, ensure that the ventilation hole is unblocked.
l When installing the front panel, use a tool to tighten the screws firmly.
l After installing the device, clean up the packing materials.
Safety Symbols
Safety symbols indicate the safety instructions that must be followed during the installation or
maintenance.
The safety symbols are divided into three levels: danger, warning, and caution.
l Danger: Indicates the possibility of a major accident if the safety instructions are ignored.
l Warning: Indicates the possibility of a major or severe injury, or equipment damage, if the
safety instructions are ignored.
l Caution: Indicates an injury might occur, or the equipment might be damaged, if the safety
instructions are ignored.
Table 2-2 describes the alarm and safety symbols on the WDM equipment.
Symbol Describes
Grounding symbol.
Indicates the position of the grounding point.
High Voltage
DANGER
The high voltage power supply provides power for the device operation. Direct or indirect contact
(through damp objects) with high voltage and AC mains supply may result in fatal danger.
l When installing the AC power supply facility, comply with the local safety regulations.
The personnel who install the AC facility must be qualified for performing high voltage
and AC operations.
l Do not wear articles that conduct electricity, such as watches, chains, bracelets and rings
when performing high voltage operations.
l Switch off the power supply immediately, if you find water in the rack or if the rack is
damp.
l Make sure that the device is kept away from water when being operated in a damp
environment.
CAUTION
Non-standard and improper high voltage operations may result in fire and electric shock.
Therefore, you must abide by the local rules and regulations when bridging and wiring AC cables
through a certain area. The personnel who perform high voltage operations must be qualified
for performing high voltage and AC operations.
Thunderstorm
DANGER
Do not perform any operation, including high voltage and AC operations, on a steel tower or
mast during a thunderstorm.
When there is a thunderstorm, the electromagnetic field generated in the thunderstorm area may
cause damage to electronic components. To prevent the device from being damaged by lightning,
use proper grounding.
WARNING
Ground the device before powering it on. Otherwise, personal injury or device damage may be
caused by high leakage current.
If a "high electrical leakage" tag is present on the power terminal of the device, you must ground
the device before powering it on.
Power Cable
DANGER
Do not install or remove power cables when the device is on. Transient contact between the core
of the power cable and the conductor may generate electric arcs or sparks, which may cause fire
or hurt human eyes.
l Before bringing the power cable into the power distribution frame (PDF), bind the bare
parts of the power cable with insulating tapes.
l Before installing or removing the power cable, turn off the power switch.
l Before connecting a power cable, check that the label on the power cable is correct.
Fuse
WARNING
If a fuse is to be replaced, the new fuse must be the same type and have the same specifications
to ensure that equipment is running safely.
Electrostatic Discharge
CAUTION
The static electricity generated by human bodies may damage the electrostatic-sensitive
components on boards, for example, the large-scale integrated (LSI) circuits.
l Human body movement, friction between human bodies and clothes, friction between shoes
and floors, or handling of plastic articles causes static electromagnetic fields on human
bodies. These static electromagnetic fields cannot be eliminated until the static is
discharged.
l To prevent electrostatic-sensitive components from being damaged by the static on human
bodies, you must wear a well-grounded ESD wrist strap when touching the device or
handling boards or application-specific integrated circuits (ASICs).
Figure 2-1shows how to wear an ESD wrist strap.
DANGER
Do not place the device in an environment that has inflammable and explosive air or gas. Do
not perform any operation in this environment.
2.5 Battery
This section describes safety precautions you must take when performing operations on storage
batteries and lithium batteries.
DANGER
Before operating storage batteries, carefully read the safety precautions for battery handling and
connection.
CAUTION
Improper handling of storage batteries causes hazards.
l When operating storage batteries, avoid short circuit and overflow or leakage of the
electrolyte.
l Electrolyte overflow may damage the device. It will corrode metal parts and circuit boards,
and ultimately damage the device and cause short circuit of circuit boards.
l A storage battery contains a great deal of energy. Misoperations on a storage battery may
cause a short-circuit, or even personal injuries.
Basic Precautions
Before installing and maintaining the battery, note the following:
l Use special insulation tools.
l Take care to protect your eyes when operating the device.
l Wear rubber gloves and a protective coat in case of electrolyte overflow.
l When handling a storage battery, ensure that its electrodes are upward. Leaning or reversing
the storage battery is prohibited.
l Before installing or maintaining the storage battery, ensure that the storage battery is
disconnected from the power supply that charges the storage battery.
Short Circuit
DANGER
Battery short circuit may cause human injuries. Although the voltage of ordinary batteries is
low, the instantaneous high current caused by the short circuit releases a great deal of energy.
CAUTION
Keep away metal objects, which may cause battery short circuit, from batteries. If metal objects
must be used, first disconnect the batteries in use before performing any other operations.
Hazardous Gas
CAUTION
l Do not use unsealed lead acid storage batteries. Lead acid storage batteries must be placed
horizontally and stably to prevent the batteries from releasing flammable gas, which may
cause fire or erode the device.
l Lead acid storage batteries in use emit flammable gas. Therefore, ventilation and fireproofing
measures must be taken at the sites where lead acid storage batteries are used.
Battery Temperature
CAUTION
If a battery overheats, the battery may be deformed or damaged, and the electrolyte may
overflow.
When the temperature of the battery is higher than 60ºC, check the battery for electrolyte
overflow. If the electrolyte overflows, absorb and counteract the electrolyte immediately.
Battery Leakage
CAUTION
When the electrolyte overflows, absorb and counteract the electrolyte immediately.
When moving or handling a battery whose electrolyte leaks, note that the leaking electrolyte
may hurt human bodies. When you find the electrolyte leaks, use the following substances to
counteract and absorb the leaking electrolyte:
Select a substance to counteract and absorb the leaking electrolyte according to the instructions
of the battery manufacturer.
If any part of your body comes into contact with the battery acid, immediately rinse your skin
thoroughly with water. Seek medical help immediately in the event of a severe injury.
WARNING
l There is danger of explosion if the battery is incorrectly replaced. Therefore, replace the
battery only with the same or equivalent type recommended by the manufacturer.
l Exhausted lithium ion batteries must be disposed of according to the instructions.
l Do not throw lithium ion batteries into fire.
2.6 Laser
When installing and maintaining equipment, observe the laser safety precautions to prevent
personal injury or equipment damage. Note that Huawei equipment complies with IEC 60825-1
and IEC 60825-2.
Hazard levels
According to the laser output values, the laser hazard levels of Huawei equipment includes two
hazard levels: HAZARD LEVEL 1 and HAZARD LEVEL 1M. Table 2-3 shows the laser hazard
levels of the equipment.
Personal Injury
WARNING
The laser beam emitted from the optical interface is invisible infrared light, which may cause
permanent eye injury. During maintenance, do not stare at the optical interface.
DANGER
Laser beams from the optical ports on boards or from the fiber connectors cause eye damage.
Do not look directly at the optical ports or fiber connectors during the installation and
maintenance of boards or fibers. Do not shine laser beams into the eyes of other workers.
DANGER
The Raman amplifier board is very high. Shut down the pump laser before you insert or remove
fiber connectors on the Raman amplifier board to help prevent personal injury that is caused by
high optical power.
To prevent eye damage in the case of an optical port that is in use, use protective caps to cover
the optical interface and the fiber connector after you remove the fiber from the optical interface.
Laser transceivers are used in optical transmission systems and associated test tools. A bare
optical fiber can produce a laser beam, which has high power density but is invisible. Eyes will
be injured when a beam of light enters eyes.
Generally, looking at an un-terminated optical fiber or a damaged optical fiber without eye
protection at a distance of greater than 150 mm does not cause eye injury. However, eyes may
be hurt if an optical aid such as a microscope, magnifying glass, or eye loupe is used to look at
an un-terminated optical fiber even though the distance is greater than 150 mm.
Equipment Damage
To prevent equipment damage when you handle the equipment, take the following precautions:
l Use protective caps to cover optical interfaces and optical connectors that are not in use.
l After you remove a fiber jumper from an optical interface, use protective caps to cover the
optical interface and the fiber jumper connector.
l Use an attenuator to prevent high optical power from damaging the optical receiver while
using a fiber jumper for the hardware loopback on an optical interface.
l Before using an optical time domain reflectometer (OTDR), remove the fiber jumper
between the opposite site and the optical interface . Such a measure also prevents high
optical power from damaging the optical receiver.
l Do not insert or remove a that is connected with a fiber.
CAUTION
The optical power of the Raman amplifier board is very high. Observe the following precautions
when using the Raman amplifier board to prevent damage to the equipment.
l Do not use fiber connectors within 0–20 km. The fibers at every joint point must be spliced.
l The single-point additional loss within 0–10 km must be smaller than 0.1 dB (G.652) or 0.2
dB (G.655) and the single-point return loss must not be smaller than 40 dB.
l The single-point additional loss within 10–20 km must be smaller than 0.2 dB (G.652) or 0.4
dB (G.655) and the single-point return loss must not be smaller than 40 dB.
l Fiber connections must be complete before you enable the lasers on the Raman amplifier
board. Make sure that the fiber connectors are clean. Otherwise, the fiber connectors might
be damaged when you insert or remove the fiber connectors.
l The optical power of the LINE interface on the Raman amplifier board is very high. The
LSH/APC optical connectors must be used in the fiber that is connected to the LINE interface.
l For the Raman amplifier board with backward pump, the strong pump light enters the fiber
through the input end (LINE) instead of the output end (SYS). Do not add boards or non-
fiber devices, such as attenuators or fiber jumpers, at the input end.
l The bent radius of the fiber that is connected to the LINE interface on the Raman amplifier
board must be larger than 30 mm to prevent the fiber from being burned.
Safety Guidelines
Follow the following guidelines to avoid laser radiation:
Handling Fibers
Read the instructions before handling fibers:
l Only trained and qualified personnel can cut or splice fibers, check and clean fiber
connectors.
l Before cutting or splicing a fiber, ensure that the fiber is disconnected from the optical
source. After disconnecting the fiber, use protecting caps to protect all the optical
connectors.
CAUTION
Do not place tools, such as screwdrivers, on the air baffle.
CAUTION
Ensure that screws do not fall off into the subrack or chassis.
2.8 ESD
During installation and maintenance, follow antistatic procedures to prevent equipment damage:
l Always wear an ESD wrist strap during the operation.
l Check that the equipment is securely grounded.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch equipment or boards. Make sure
that the wrist strap touches your skin. Insert the ESD strap connector into the ESD socket of the
equipment.
For information about how to wear an ESD wrist strap, see Figure 2-2.
NOTE
Insert the connector of the ESD strap into the equipment port. For details, see the Quick Installation Guide.
When you are following antistatic procedures, take the following precautions:
l Check the validity and functionality of the wrist strap. Its resistance value must be between
0.75 mega ohm to 10 mega ohm. If the wrist strap validity period (usually two years) has
expired, or if the resistance value fails to meet requirements, replace it with a wrist strap
that provides the required resistance value.
l Do not touch a board with your clothing. Clothing generates static electricity that is not
protected by the wrist strap.
l Wear an ESD wrist strap and place the board on an ESD pad when you replace boards or
chips. Use ESD tweezers or extraction tools to replace chips. Do not touch chips, circuits,
or pins with your bare hands.
l Keep the boards and other ESD-sensitive parts you are installing in ESD bags. Place the
removed boards and components on an ESD pad or ESD material. Do not use non-antistatic
materials such as white foams, common plastic bags, or paper bags to pack boards, and do
not let these materials touch the boards.
l Wear an ESD wrist strap when operating the ports of boards because they are also ESD-
sensitive. Discharge the static electricity of cables and protective sleeves before you connect
them to the ports.
l Keep packing materials (such as, ESD boxes and bags) available in the equipment room
for packing boards in the future.
ESD complies with IEC Publication 1000, EN 55022, EN 55024, IEC 61000 and GR-1089-
CORE.
WARNING
When working at heights, take proper measures to prevent objects from falling down.
l The personnel who work at heights must have received corresponding training.
l Carry and handle the operating machines and tools with caution to prevent them from falling
down.
l Take safety measures. For example, wear a helmet and a safety belt.
l Wear cold-proof clothes when working at heights in cold areas.
l Check all lifting appliances thoroughly before starting the work, and ensure that they are
intact.
WARNING
Do not walk below the cantilever or hoisted objects when heavy objects are being hoisted.
Checking a Ladder
l Before using a ladder, check whether the ladder is damaged. Only the ladder in good
condition can be used.
l Before using a ladder, you should know the maximum weight capacity of the ladder. Avoid
overweighing the ladder.
Placing a Ladder
The recommended gradient of a ladder is 75 degrees. You can measure the gradient of the ladder
with an angle square or your arms. See Figure 2-4. When using a ladder, ensure that the wider
feet of the ladder are downward, or take protection measures for the ladder feet to prevent the
ladder from sliding. Ensure that the ladder is placed securely.
Climbing Up a Ladder
When climbing up a ladder, observe the following points:
l Ensure that the center of gravity of your body does not deviate from the edges of the two
long sides.
l To minimize the risk of falling, hold your balance on the ladder before any operation.
l Do not climb higher than the fourth rung of the ladder (counted from up to down).
If you want to climb up a roof, ensure that the ladder top is at least one meter higher than the
roof. See Figure 2-5 .
Figure 2-5 Ladder top being one meter higher than the roof
Drilling Holes
WARNING
Do not drill the cabinet at will. Drilling holes without complying with the requirements affects
the electromagnetic shielding performance of the cabinet and damages the cables inside the
cabinet. In addition, if the scraps caused by drilling enter the cabinet, the printed circuit boards
(PCBs) may be short circuited.
l Before you drill a hole in the cabinet, wear insulated gloves and remove the internal cables
from the cabinet.
l Wear an eye protector when drilling holes. This is to prevent your eyes from being injured
by the splashing metal scraps.
l Wear protective gloves when drilling holes.
l Ensure that the scraps caused by drilling do not enter the cabinet. After drilling, clean the
metal scraps immediately.
Sharp Objects
WARNING
Before you hold or carry a device, wear protective gloves to avoid getting injured by sharp edges
of the device.
Handling Fans
l When replacing a component, place the component, screws, and tools in a safe place.
Otherwise, if any of them fall into the operating fans, the fans may be damaged.
l When replacing a component near fans, do not insert your fingers or boards into the
operating fans until the fans are switched off and stops running.
WARNING
l When carrying a heavy object, wear protective gloves to prevent hands from being hurt.
l Before carrying a heavy object, prevent yourself from being strained or pressed by the heavy
object.
l When pulling a chassis out of the cabinet, be cautious to the unstable or heavy objects on the
cabinet. This is to prevent the heavy objects on the cabinet top from falling down, which may
hurt you.
l When carrying a heavy object such as a cabinet, use a tool such as a pallet truck.
l Two persons are needed to carry a chassis. It is not allowed for only one person to carry a
heavy chassis. When carrying a chassis, stretch your backs and move stably to avoid being
strained.
l When moving or lifting a chassis, hold the handles or bottom of the chassis. Do not hold
the handles of the modules installed in the chassis, such as the power modules, fan modules,
and boards.
DANGER
Do not install or disassemble equipment when power is applied.
DANGER
Do not install or disassemble power cables on equipment when power is applied.
2.12 Miscellaneous
This section describes the safety precautions you must take when removing and reinstalling
boards, fibers and pluggable optical modules, bundling signal cables, and routing cables at a low
temperature.
CAUTION
When installing a board, use proper force to prevent the pins on the backplane from being leaned.
WARNING
When a loopback test is performed at an optical port using a fiber jumper, the optical attenuation
must be increased to avoid damage to the equipment due to the extremely high optical power of
the laser. For a board which caters for an attenuator to be added, the attenuator must be added
to the receive optical port.
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
DANGER
Raman amplifier emits strong light. Do not insert or remove the fiber connector when the laser
is working, to avoid damage to human body.
l When connecting a fiber, insert the fiber gently into the optical port. When the optical power
is extremely high, an attenuator must be used to avoid damage to the optical port.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
DANGER
Cover a fiber with a protection cap immediately after you remove it.
CAUTION
Before you connect a fiber to a pluggable optical module, test the input optical power of the
module and confirm that the tested input optical power is within the normal range. Otherwise,
the input optical power might cross the overload point and the receiver optical module is burnt
and damaged.
The overload optical power point of an APD receiver laser is only -9 dBm, which must be taken
with special caution to prevent the optical module from being burnt or damaged.
CAUTION
When binding signal cables, ensure that they are not mixed with high-current or high-voltage
cables. The space between two adjacent ties must be at least 30 mm.
Laying Cables
When the temperature is very low, violent strike or vibration may damage the cable sheathing.
To ensure safety, comply with the following requirements:
l Cables can be laid or installed only when the temperature is higher than 0ºC.
l Before laying cables which have been stored in a temperature lower than 0ºC, move the
cables to an environment of the ambient temperature and store them at the ambient
temperature for at least 24 hours.
l Handle cables with caution, especially at a low temperature. Do not drop the cables directly
from the vehicle.
OptiX OSN 8800 T32 The OptiX OSN 8800 T32 is mainly applicable to the large-
capacity aggregation layer.
l 1.28T ODUk (k=0,1,2,2e,3,flex) cross-connection capacity
l Max. wavelengths: 80 x 2.5G/10G/40G/100G (DWDM), 8 x
2.5G (CWDM)
l DWDM Max. distance without electrical regeneration:
– 10Gbit/s system: 32 span x 22 dB/span
– 40Gbit/s system: 25 span x 22 dB/span
– 100Gbit/s system: 14 span x 22 dB/span
l DWDM ultra long-haul single span:
– 10Gbit/s system: 1 span x 81 dB/span (with ROPA), 1 span
x 69 dB/span (without ROPA)
– 40Gbit/s system: 1 span x 71 dB/span (with ROPA), 1 span
x 62 dB/span (without ROPA)
l Full service access over flexible shared 2.5G, 10G, 40G,
100G channels
l Non-block 2/4/9degree ROADM
l O&E hybrid switch facilitates the end-to-end free connection
with services pass-through, adding and dropping
l Service and equipment protections for high reliability
l "5A" automatic optical power management: ALC, AGC, APE,
IPA and OPA
l Simple E2E service provisioning
OptiX OSN 8800 T16 The OptiX OSN 8800 T16 is mainly applicable to the large-
capacity aggregation layer.
l 640G ODUk (k=0,1,2,2e,3,flex) cross-connection capacity
l Max. wavelengths: 80 x 2.5G/10G/40G/100G (DWDM), 8 x
2.5G (CWDM)
l DWDM Max. distance without electrical regeneration:
– 10Gbit/s system: 32 span x 22 dB/span
– 40Gbit/s system: 25 span x 22 dB/span
– 100Gbit/s system: 14 span x 22 dB/span
l DWDM ultra long-haul single span:
– 10Gbit/s system: 1 span x 81 dB/span (with ROPA), 1 span
x 69 dB/span (without ROPA)
– 40Gbit/s system: 1 span x 71 dB/span (with ROPA), 1 span
x 62 dB/span (without ROPA)
l Full service access over flexible shared 2.5G, 10G, 40G,
100G channels
l Non-block 2/4/9degree ROADM
l O&E hybrid switch facilitates the end-to-end free connection
with services pass-through, adding and dropping
l Service and equipment protections for high reliability
l "5A" automatic optical power management: ALC, AGC, APE,
IPA and OPA
l Simple E2E service provisioning
OptiX OSN 6800A The OptiX OSN 6800A is mainly applicable to the aggregation
layer or the backbone layer with average capacity.
l 360G ODUk (k=1,2,2e) cross-connection capacity.
l 180G GE or 360 10GE cross-connection capacity.
l Max. wavelengths: 80 x 2.5G/10G/40G/100G(DWDM), 8 x 5G
(CWDM)
l DWDM Max. distance without electrical regeneration:
– 10Gbit/s system: 32 span x 22 dB/span
– 40Gbit/s system: 25 span x 22 dB/span
– 100Gbit/s system: 14 span x 22 dB/span
l DWDM ultra long-haul single span:
– 10Gbit/s system: 1 span x 81 dB/span (with ROPA), 1 span
x 69 dB/span (without ROPA)
– 40Gbit/s system: 1 span x 71 dB/span (with ROPA), 1 span
x 62 dB/span (without ROPA)
l Full service access over flexible shared 2.5G, 10G,40G, 100G
channels
l Non-block 2/4/9degree ROADM
l O&E hybrid switch facilitates the end-to-end free connection
with services pass-through, adding and dropping
l Service and equipment protections for high reliability
l "5A" automatic optical power management: ALC, AGC, APE,
IPA and OPA
l Simple E2E service provisioning
OptiX OSN 3800A The OptiX OSN 3800A is mainly applicable to the access layer.
l 4 x ODU1 or 4 x GE or 4 x Any cross-connection capacity.
l Max. wavelengths: 4 x 10G or 8 x 2.5G (DWDM), 8 x 5G
(CWDM)
l DWDM max. distance without electrical regeneration:10Gbit/s
system, 32 span x 22 dB/span
l DWDM ultra long-haul single span: 10Gbit/s system, 1 span x
69 dB/span
l Full service access over flexible shared 2.5G or 10G channels
l Service end-to-end configuration is available.
l Service and equipment protections for high reliability
l "3A" automatic optical power management: ALC, AGC and
IPA
l Simple E2E service provisioning
3.2.1.1 Structure
Subracks are the basic working units of the OptiX OSN 8800 T64. Each subrack has independent
power supply.
Figure 3-2 shows the structure of the OptiX OSN 8800 T64 subrack.
Table 3-2 describes the mechanical specifications of the 8800 T64 subrack.
Figure 3-1 OptiX OSN 8800 T64 subrack structure (subrack door included)
Door
Figure 3-2 OptiX OSN 8800 T64 subrack structure (subrack door excluded)
or
5 2
3
4
l Board area: All the boards are installed in this area. 93 slots are available.
l Fiber cabling area: Fiber jumpers from the ports on the front panel of each board are routed
to the fiber cabling area before being routed on a side of the open rack.
l Fan tray assembly: Four fan tray assemblies are available for this subrack. Each fan tray
assembly contains three fans that provide ventilation and heat dissipation for the subrack.
The front panel of the fan tray assembly has four indicators that indicate fan status and
related information.
NOTE
For detailed descriptions of the fan tray assembly, see 3.2.1.5 Fan and Heat Baffle.
l Air filter: It protects the subrack from dust in the air and requires periodic cleaning. Air
filter features include:
– Dust arrest rating of of 85%.
Item Specification
a: An empty subrack means no boards are installed in the board area, and no fan tray assembly
or air filter is installed.
Slots of the OptiX OSN 8800 T64 subrack are shown in Figure 3-3.
IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU
19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68
Cross-connect board
Cross-connect board
Cross-connect board
Cross-connect board
IU IU IU IU
9 10 43 44
IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU
1 2 3 4 5 6 7 8 11 12 13 14 15 16 17 18 35 36 37 38 39 40 41 42 45 46 47 48 49 50 51 52
IU90 IU92
l The following table provides the slots for housing active and standby boards of the subrack.
Board Slots for Active and Standby Boards
PIU IU69 & IU78, IU70 & IU79, IU80 & IU88, and IU81 &IU89
The subrack provides various communication and maintenance interfaces for the management
and maintenance purposes, as shown in Table 3-3.
TN51 EFI2 Typical Power Alarm cascading For detailed information, refer
EFI2 Consumption at interfaces: LAMP1, to 3.10.2 Management
25°C (77°F): 13 LAMP2 Interfaces and Connections
W Network of OptiX OSN 8800/6800A.
LAMP1
ETH1
TNK ATE Typical Power Alarm input For detailed information, refer
2AT Consumption at interface to 3.9.1 OptiX OSN 8800
E A B C D 25°C (77°F): 5 W Housekeeping Alarm and
Maximum Power Control Interfaces.
1
2 Consumption at
3
4
55°C (131°F): 7
5 W
6
7
8
TNK STI Typical Power Alarm output For detailed information, refer
2STI Consumption at interface to 3.9.1 OptiX OSN 8800
A B C D 25°C (77°F): 1 WClock signal Housekeeping Alarm and
Maximum Power interface Control Interfaces.
1
2 Consumption at
3
4
55°C (131°F): 1
5 W
6
7
8
WARNING
The intra-building port(s) of the equipment or subassembly is suitable for connection to
intrabuilding or unexposed wiring or cabling only. The intra-building port(s) of the equipment
or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or
its wiring. These interfaces are designed for use as intra-building interfaces only (Type 2 or Type
4 ports as described in GR-1089-CORE, Issue 5) and require isolation from the exposed OSP
cabling. The addition of Primary Protectors is not sufficient protection in order to connect these
interfaces metallically to OSP wiring.
Version Description
Only one functional version of the fan tray assembly is available, that is, TN51.
Basic function Dissipates the heat generated by a network element (NE), so that
the NE can operate normally within the designated temperature
range.
Section-dependent heat Each subrack is divided into six sections to provide efficient heat
dissipation dissipation. The fan speed in each section is independently
regulated.
Hot swapping Provides the hot swapping function for the fan tray assembly.
Alarming Reports alarms of the fans, and reports the in-service information.
Working Principle
A fan tray assembly inside a subrack ventilates the subrack to ensure that the subrack works
effectively at an appropriate temperature. The fan tray assembly is located in the lower portion
of a subrack. It draws in air into the subrack, forming an air duct from bottom to top. Other
boards in the subrack are installed vertically. In other words, the boards are parallel to the air
duct. This design ensures reliable heat dissipation. Heat baffles allows for air to be drawn in
from the bottom of the subrack and direct the exhausted air to the top of the subrack. Figure
3-4 shows how ventilation is performed in the OptiX OSN 8800 T64.
Figure 3-4 shows how ventilation is performed in the OptiX OSN 8800 T64.
Heat Baffle
Air outlet
Board
Area
Optical fiber
laying area
Fan tray assembly
Air inlet
The OptiX OSN 8800 supports two fan speed modes, as described in Table 3-5. The section-
dependent speed regulating function is available in Auto Speed Mode. The Auto Speed Mode
is recommended.
Auto Speed Mode Fan speed in each section is regulated automatically according to the
temperature of the boards in the section that the fans are targeted for.
l Lower than 25°C (77°F): the fans run at low speed.
l Higher than 45°C (113°F): the fans run at high speed.
l 25°C to 45°C (77°F to 113° F): The fans automatically adjust their
rotation speeds. This mode can reduce noise and is power-saving.
Fan speed in each section is independently regulated.
The fans run at full speed if the speed regulating signal is abnormal.
If one of the fans in one section fails, the other fans in this section run at
full speed.
When the user queries the fan speed using the NMS, the highest fan speed
among all sections is displayed. In other words, if the fans in one section
rotate at high speed, the NMS displays the fan speed as high speed in the
query result.
Adjustable Speed Six fan speeds are supported: Stop, Low Speed, Medium-Low Speed,
Mode Medium Speed, Medium-High Speed, and High Speed. In this mode,
the user manually sets the fan speed and fans in all sections run at the
same speed. The user cannot independently set the fan speed for a
specific section.
Set the fan speed mode to STOP before removing or replacing an air
filter to prevent dust from entering the fan tray assembly.
Each OptiX OSN 8800 T64 subrack has two sides. Each side has six sections. See Figure 3-5.
Figure 3-5 Section-dependent heat dissipation of the OptiX OSN 8800 T64 subrack
IU91
IU93
Front Back
IU19 IU20 IU21 IU22 IU23 IU24 IU25 IU26 IU27 IU28 IU29 IU30 IU31 IU32 IU33 IU34 IU53 IU54 IU55 IU56 IU57 IU58 IU59 IU60 IU61 IU62 IU63 IU64 IU65 IU66 IU67 IU68
IU1 IU2 IU3 IU4 IU5 IU6 IU7 IU8 IU11 IU12 IU13 IU14 IU15 IU16 IU17 IU18 IU35 IU36 IU37 IU38 IU39 IU40 IU41 IU42 IU45 IU46 IU47 IU48 IU49 IU50 IU51 IU52
IU50 IU50
IU90
Partition 1 Partition 2 Partition 3 Partition 4 Partition 5 Partition 6 IU92
NOTE
If any one of the six fans in the two fan tray assemblies fails, the system can keep on operating for 96
consecutive hours in an environment with temperatures between 0°C to 45°C (32°F to 113°F).
Replace the fan tray assembly in either of the following two situations:
l Two or more fans fail in one of the two fan tray assemblies.
l One or more fans fail in each of the two fan tray assemblies.
In a system that is operating normally, the two fans in the same section (such as FAN1 and FAN4) run at
the same speed.
The fan tray assembly consists of fans and fan control unit. Figure 3-6 shows the functional
blocks of the fan tray assembly.
FAN
l FAN: dissipates heat generated by normal operation of the subrack. FAN is the core of the
fan tray assembly.
l Fan control board:
– Controls the fan speed according to the fan speed regulating signals.
– Detects faults. After a fault is detected, the fan control unit reports an alarm. In this case,
the SCC board issues commands to instruct the other fans to run at the full speed.
– Monitors speed regulating signals, the fan status, and the online/offline state of the fan
tray assembly.
– Receives and carries out commands from the SCC board to shut down the fans on the
fan tray assembly if necessary.
Appearance
Figure 3-7 shows a fan tray assembly.
NOTE
An air filter is installed on the lower fan tray assembly to prevent dust from entering the subrack.
Valid Slots
The fan tray assembly occupies one slot. The valid slots for the fan tray assembly are IU90 IU91,
IU92 and IU93 in the OptiX OSN 8800 T64 subrack.
NOTE
For the transport equipment, heat consumption and power consumption are similar and can be taken as the
same. Heat consumption (BTU/h) = Power consumption (W) x Time (h)/0.2931(Wh).
Item Specification
Dimensions (H x W x D) 64.0 mm (2.5 in.) x 493.7 mm (19.4 in.) x 280.5 mm (11.0 in.)
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 270 W.
Table 3-7 describes the power consumption of an OptiX OSN 8800 T64 subrack.
NOTE
For transport equipment, the heat consumption and power consumption are similar and can be considered
the same. Heat consumption is expressed in BTU/h and power consumption is expressed in W. The
conversion between the two units is as follows: 1 BTU/h = 0.2931 W.
Typical configuration power consumption indicates the average power consumption of the equipment with
the typical configuration and the equipment runs at the room temperature. Maximum power consumption
indicates the possible maximum power consumption when the equipment runs in an environment with
extreme conditions.
a: The maximum subrack power consumption refers to the theoretical power consumption
obtained when boards with the highest power consumption are installed in every slot on the
subrack.
Table 3-8 describes the power consumption of the subrack in typical configuration in an OptiX
OSN 8800 T64.
Table 3-8 Power consumption of the common units in an OptiX OSN 8800 T64
Unit Name Typical Maximum Remarks
Power Power
Consumptio Consumptio
n at 25°C (77° n at 55°C
F) (W)a (131°F) (W)a
a: Indicates that the power consumption of the subrack and open rack is the value in a certain
configuration. The value is for reference only. The actual power consumed by the chassis and
open rack is a calculation based on the power consumption of each module.
Table 3-9 Requirements on voltage and current of an OptiX OSN 8800 T64
Item Requirement
PIU
The PIU board receives and provides DC power for equipment. For OptiX OSN 8800/6800A,
the PIU board must be TN41PIU.
l Function
Accesses DC power in a range from -40 V to -57 V. Provides lightning protection and
power filtering functions.
l Front Panel
Appearance of the Front Panel
PIU
PWR
RTN(+) REG(-)
OptiX OSN 8800 T64 IU69, IU70, IU78, IU79, IU80, IU81, IU88, and IU89
l Specifications
– Performance Specifications
– Mechanical Specifications
Dimensions of front panel: 50.8 mm (W) x 220 mm (D) x 80 mm (H) (2.0 in. (W) x 8.7
in. (D) x 3.1 in. (H))
Weight: 0.7 kg (1.54 lb.)
– Power Consumption
TN41PIU 45 45
Cables
l Power cables
The power cable uses a two-hole OT terminal to connect to the PIU board of each OptiX
OSN 8800/6800A subrack, as shown in Figure 3-9.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-9 Two-hole OT terminals on the OptiX OSN 8800/6800A power cable
NOTE
Two-hole OT terminals are installed on PIU terminal sockets. A PIU terminal socket is 0.49 inch wide and so
two-hole OT terminal's width cannot exceed 0.49 inch.
l Ground cables
The ground cable of each OptiX OSN 8800/6800A uses a two-hole OT terminal, as shown
in Figure 3-10. The subrack, DCM frame, and heat baffle each has a ground point. For
details on how to connect ground cables, see Quick Installation Guide.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-10 OT terminal on the ground cable of the OptiX OSN 8800/6800A
M6 screw
0.25 inch
Subrack
0.75 inch
0.75
inch
Two-hole OT terminal
M6(0.25 inch)
3.2.2.1 Structure
Subracks are the basic working units of the OptiX OSN 8800 T32. Each subrack has independent
power supply.
Figure 3-12 shows the structure of the OptiX OSN 8800 T32 subrack.
Figure 3-11 OptiX OSN 8800 T32 subrack structure diagram (subrack door included)
Figure 3-12 OptiX OSN 8800 T32 subrack structure diagram (subrack door excluded)
1
6
3
4
NOTE
A subrack identified by "Enhanced" is an enhanced OptiX OSN 8800 T32 subrack. If the subrack is not identified
by "Enhanced", it is a general OptiX OSN 8800 T32 subrack.
l Board area: All the boards are installed in this area. 50 slots are available.
l Fiber cabling area: Fiber jumpers from the ports on the front panel of each board are routed
to the fiber cabling area before being routed on a side of the open rack.
l Fan tray assembly: Fan tray assembly contains three fans that provide ventilation and heat
dissipation for the subrack. The front panel of the fan tray assembly has four indicators that
indicate subrack status.
NOTE
For detailed descriptions of the fan tray assembly, see 3.2.2.5 Fan and Heat Baffle.
l Air filter: It protects the subrack from dust in the air and requires periodic cleaning. Air
filter features include:
– Dust arrest rating of of 85%.
– Fire rating of UL94V-0.
– Preventing any air bypass.
l Fiber spool: Fixed fiber spools are on two sides of the subrack. Extra fibers are coiled in
the fiber spool on the open rack side before being routed to another subrack.
l Mounting ears: The mounting ears attach the subrack in the cabinet.
a: An empty subrack means no boards are installed in the board area, and no fan tray assembly
or air filter is installed.
IU51
SCC
IU20 IU21 IU22 IU23 IU24 IU25 IU26 IU27 IU29 IU30 IU31 IU32 IU33 IU34 IU35 IU36
Cross-connect board
Cross-connect board
IU28
IU9 IU10
IU1 IU2 IU3 IU4 IU5 IU6 IU7 IU8 IU12 IU13 IU14 IU15 IU16 IU17 IU18 IU19
IU11
IU50
The subrack provides various communication and maintenance interfaces for the management
and maintenance purposes, as shown in Table 3-13.
TN51 EFI2 Typical Power Alarm cascading For detailed information, refer
EFI2 Consumption at interfaces: LAMP1, to 3.10.2 Management
25°C (77°F): 13 LAMP2 Interfaces and Connections
W Network of OptiX OSN 8800/6800A.
LAMP1
ETH1
TNK ATE Typical Power Alarm input For detailed information, refer
2AT Consumption at interface to 3.9.1 OptiX OSN 8800
E A B C D 25°C (77°F): 5 W Housekeeping Alarm and
Maximum Power Control Interfaces.
1
2 Consumption at
3
4
55°C (131°F): 7
5 W
6
7
8
TNK STI Typical Power Alarm output For detailed information, refer
2STI Consumption at interface to 3.9.1 OptiX OSN 8800
A B C D 25°C (77°F): 1 WClock signal Housekeeping Alarm and
Maximum Power interface Control Interfaces.
1
2 Consumption at
3
4
55°C (131°F): 1
5 W
6
7
8
WARNING
The intra-building port(s) of the equipment or subassembly is suitable for connection to
intrabuilding or unexposed wiring or cabling only. The intra-building port(s) of the equipment
or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or
its wiring. These interfaces are designed for use as intra-building interfaces only (Type 2 or Type
4 ports as described in GR-1089-CORE, Issue 5) and require isolation from the exposed OSP
cabling. The addition of Primary Protectors is not sufficient protection in order to connect these
interfaces metallically to OSP wiring.
Version Description
Only one functional version of the fan tray assembly is available, that is, TN51.
Function Description
Basic function Dissipates the heat generated by a network element (NE), so that
the NE can operate normally within the designated temperature
range.
Partitioned heat Each subrack is divided into three partitions to help provide
dissipation efficient heat dissipation. The fan speed in each partition is
independently regulated.
Hot swapping Provides the hot swapping function for the fan tray assembly.
Alarming Reports alarms of the fans, and reports the in-service information.
Working Principle
A fan tray assembly inside a subrack dissipates heat for the subrack to ensure that the subrack
works effectively at a specified temperature. The fan tray assembly is located on the lower part
of a subrack. It blows air into the subrack, forming an air duct from bottom to top. Other boards
in the subrack are installed vertically. In other words, the boards are parallel to the air duct. This
design ensures reliable heat dissipation. Heat baffles will cause air to be drawn from the bottom
of the subrack and direct hot fan exhaust to the top of the subrack.Figure 3-14 shows the heat
dissipation and ventilation system in the OptiX OSN 8800 T32.
Heat Baffle
Air outlet
Board
Area
Optical fiber
laying area
Fan tray assembly
Air inlet
The OptiX OSN 8800 supports two fan speed modes, as described in Table 3-15. The section-
dependent speed regulating function is available in Auto Speed Mode. The Auto Speed Mode
is recommended.
Auto Speed Mode Fan speed in each section is regulated automatically according to the
temperature of the boards in the section that the fans are targeted for.
l Lower than 25°C (77°F): the fans run at low speed.
l Higher than 45°C (113°F): the fans run at high speed.
l 25°C to 45°C (77°F to 113° F): The fans automatically adjust their
rotation speeds. This mode can reduce noise and is power-saving.
Fan speed in each section is independently regulated.
The fans run at full speed if the speed regulating signal is abnormal.
If one of the fans in one section fails, the other fans in this section run at
full speed.
When the user queries the fan speed using the NMS, the highest fan speed
among all sections is displayed. In other words, if the fans in one section
rotate at high speed, the NMS displays the fan speed as high speed in the
query result.
Adjustable Speed Six fan speeds are supported: Stop, Low Speed, Medium-Low Speed,
Mode Medium Speed, Medium-High Speed, and High Speed. In this mode,
the user manually sets the fan speed and fans in all sections run at the
same speed. The user cannot independently set the fan speed for a
specific section.
Set the fan speed mode to STOP before removing or replacing an air
filter to prevent dust from entering the fan tray assembly.
Each OptiX OSN 8800 T32 subrack is divided into three partitions in terms of heat dissipation.
The subrack adopts two fan tray assemblies to implement partitioned heat dissipation. See
Figure 3-15.
Figure 3-15 Partitioned heat dissipation of the OptiX OSN 8800 T32 subrack
IU37 IU38 IU39 IU40 IU41 IU42 IU43 IU44 IU45 IU46 IU47 IU48
IU20 IU21 IU22 IU23 IU24 IU25 IU26 IU27 IU28 IU29 IU30 IU31 IU32 IU33 IU34 IU35 IU36
IU9 IU10
IU1 IU2 IU3 IU4 IU5 IU6 IU7 IU8 IU11 IU12 IU13 IU14 IU15 IU16 IU17 IU18 IU19
IU50
NOTE
If any one of the six fans in the two fan tray assemblies fails, the system can keep on operating for 96
consecutive hours in an environment with temperatures between 0°C to 45°C (32°F to 113°F).
Replace the fan tray assembly in either of the following two situations:
l Two or more fans fail in one of the two fan tray assemblies.
l One or more fans fail in each of the two fan tray assemblies.
In a system that is operating normally, the two fans in the same partition (such as FAN1 and FAN4) run
at the same speed.
The fan tray assembly consists of fans and fan control unit. Figure 3-16 shows the functional
blocks of the fan tray assembly.
FAN
l FAN: dissipates heat generated by normal operation of the subrack. FAN is the core of the
fan tray assembly.
l Fan control board:
– Controls the fan speed according to the fan speed regulating signals.
– Detects faults. After a fault is detected, the fan control unit reports an alarm. In this case,
the SCC board issues commands to instruct the other fans to run at the full speed.
– Monitors speed regulating signals, the fan status, and the online/offline state of the fan
tray assembly.
– Receives and carries out commands from the SCC board to shut down the fans on the
fan tray assembly if necessary.
Appearance
Figure 3-17 shows a fan tray assembly.
NOTE
An air filter is installed on the lower fan tray assembly to prevent dust from entering the subrack.
Valid Slots
The fan tray assembly occupies one slot. The valid slots for the fan tray assembly are IU50 and
IU51 in the OptiX OSN 8800 T32 subrack.
NOTE
For the transport equipment, heat consumption and power consumption are similar and can be taken as the
same. Heat consumption (BTU/h) = Power consumption (W) x Time (h)/0.2931(Wh).
Item Specification
Dimensions (H x W x D) 64.0 mm (2.5 in.) x 493.7 mm (19.4 in.) x 280.5 mm (11.0 in.)
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 270 W.
Table 3-17 describes the power consumption of an OptiX OSN 8800 T32 subrack.
NOTE
For transport equipment, the heat consumption and power consumption are similar and can be considered
the same. Heat consumption is expressed in BTU/h and power consumption is expressed in W. The
conversion between the two units is as follows: 1 BTU/h = 0.2931 W.
Typical configuration power consumption indicates the average power consumption of the equipment with
the typical configuration and the equipment runs at the room temperature. Maximum power consumption
indicates the possible maximum power consumption when the equipment runs in an environment with
extreme conditions.
a: The maximum subrack power consumption refers to the theoretical power consumption
obtained when boards with the highest power consumption are installed in every slot on the
subrack.
Table 3-18 describes the power consumption of the subrack in typical configuration in an OptiX
OSN 8800 T32.
Table 3-18 Power consumption of the common units in an OptiX OSN 8800 T32
Unit Name Typical Power Maximum Power Remarks
Consumption at Consumption at
25°C (77°F) (W)a 55°C (131°F) (W)a
a: Indicates that the power consumption of the subrack is the value in a certain configuration.
The value is for reference only. The actual power consumed by the subrack is a calculation
based on the power consumption of each module.
Table 3-19 Requirements on voltage and current of an OptiX OSN 8800 T32
Item Requirement
Item Requirement
PIU
The PIU board receives and provides DC power for equipment. For OptiX OSN 8800/6800A,
the PIU board must be TN41PIU.
l Function
Accesses DC power in a range from -40 V to -57 V. Provides lightning protection and
power filtering functions.
l Front Panel
Appearance of the Front Panel
PIU
PWR
RTN(+) REG(-)
OptiX OSN 8800 T64 IU69, IU70, IU78, IU79, IU80, IU81, IU88, and IU89
l Specifications
– Performance Specifications
– Mechanical Specifications
Dimensions of front panel: 50.8 mm (W) x 220 mm (D) x 80 mm (H) (2.0 in. (W) x 8.7
in. (D) x 3.1 in. (H))
Weight: 0.7 kg (1.54 lb.)
– Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C Consumption at 55°C
(77°F) (W) (131°F) (W)
TN41PIU 45 45
Cables
l Power cables
The power cable uses a two-hole OT terminal to connect to the PIU board of each OptiX
OSN 8800/6800A subrack, as shown in Figure 3-19.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-19 Two-hole OT terminals on the OptiX OSN 8800/6800A power cable
NOTE
Two-hole OT terminals are installed on PIU terminal sockets. A PIU terminal socket is 0.49 inch wide and so
two-hole OT terminal's width cannot exceed 0.49 inch.
l Ground cables
The ground cable of each OptiX OSN 8800/6800A uses a two-hole OT terminal, as shown
in Figure 3-20. The subrack, DCM frame, and heat baffle each has a ground point. For
details on how to connect ground cables, see Quick Installation Guide.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-20 OT terminal on the ground cable of the OptiX OSN 8800/6800A
M6 screw
0.25 inch
Subrack
0.75 inch
0.75
inch
Two-hole OT terminal
M6(0.25 inch)
3.2.3.1 Structure
Subracks are the basic working units of the OptiX OSN 8800 T16. Each subrack has independent
power supply.
Figure 3-21 OptiX OSN 8800 T16 subrack structure (subrack door included)
Door
Figure 3-22 OptiX OSN 8800 T16 subrack structure (subrack door excluded)
1
6
2
5
3
4
l Board area: All the boards are installed in this area. 24 slots are available.
l Fiber cabling area: Fiber jumpers from the ports on the front panel of each board are routed
to the fiber cabling area before being routed on a side of the open rack.
l Fan tray assembly: Fan tray assembly contains ten fans that provide ventilation and heat
dissipation for the subrack. The front panel of the fan tray assembly has four indicators that
indicate fan status and related information.
NOTE
For detailed descriptions of the fan tray assembly, see 3.2.3.5 Fan and Heat Baffle.
l Air filter: It protects the subrack from dust in the air and requires periodic cleaning. Air
filter features include:
– Dust arrest rating of 85%.
– Fire rating of UL94V-0.
– Preventing any air bypass.
l Fiber spool: Fixed fiber spools are on two sides of the subrack. Extra fibers are coiled in
the fiber spool on the open rack side before being routed to another subrack.
l Mounting ears: The mounting ears attach the subrack in the cabinet.
a: An empty subrack means no boards are installed in the board area, and no fan tray assembly
or air filter is installed.
IU9 IU10
IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU
1 2 3 4 5 6 7 8 11 12 13 14 15 16 17 18
IU25 FAN
NOTE
Slots IU9 and IU10 can be used to house service boards only when the OptiX OSN 8800 T16 functions
as a slave subrack.
If slots IU9 and IU10 are used to house service boards, install a special filler panel in each slot first
l The following table provides the slots for housing active and standby boards of the subrack.
Board Slots for Active and Standby Boards
The subrack provides various communication and maintenance interfaces for the management
and maintenance purposes, as shown in Table 3-22.
Maximum Power
ETH1
SERIAL
W ETH3 Connections
Management of OptiX
OSN
NM_ETH1
NM_ETH2
serial interface:
ETH3
SERIAL 8800/6800A.
Alarm cascading
interfaces:
LAMP1,
LAMP2
WARNING
The intra-building port(s) of the equipment or subassembly is suitable for connection to
intrabuilding or unexposed wiring or cabling only. The intra-building port(s) of the equipment
or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or
its wiring. These interfaces are designed for use as intra-building interfaces only (Type 2 or Type
4 ports as described in GR-1089-CORE, Issue 5) and require isolation from the exposed OSP
cabling. The addition of Primary Protectors is not sufficient protection in order to connect these
interfaces metallically to OSP wiring.
An OptiX OSN 8800 T16 subrack can cross-connect ODU0, ODU1, ODU2, ODU2e, ODU3,
and ODUflex granularities at the same time with a maximum cross-connect capacity of 640 Gbit/
s. Slots IU1-IU8 and IU11-IU18 provide the same cross-connect capacity and each of the slots
supports a maximum of 40 Gbit/s cross-connect capacity.
Version Description
Only one functional version of the fan tray assembly is available, that is, TN16.
Function Description
Basic function Dissipates the heat generated by a network element (NE), so that
the NE can operate normally within the designated temperature
range.
Partitioned heat Each subrack is divided into five partitions to help provide
dissipation efficient heat dissipation. The fan speed in each partition is
independently regulated.
Function Description
Hot swapping Provides the hot swapping function for the fan tray assembly.
Alarming Reports alarms of the fans, and reports the in-service information.
Working Principle
A fan tray assembly inside a subrack dissipates heat for the subrack to ensure that the subrack
works effectively at a specified temperature. The fan tray assembly is located on the lower part
of a subrack. It blows air into the subrack, forming an air duct from bottom to top. Other boards
in the subrack are installed vertically. In other words, the boards are parallel to the air duct. This
design ensures reliable heat dissipation. Heat baffles will cause air to be drawn from the bottom
of the subrack and direct hot fan exhaust to the top of the subrack. Figure 3-24 shows the heat
dissipation and ventilation system in the OptiX OSN 8800 T16.
Air o utlet
Board area
Optical fiber
laying area
Fan tray assembly
Airinlet
The OptiX OSN 8800 T16 supports two fan speed modes, as described in Table 3-24. The
partitioned speed regulating function is available in Auto Speed Mode. It is recommended that
you operate fans in Auto Speed Mode by default.
Auto Speed Mode Fan speed in each partition is regulated automatically according to the
temperature of the boards in the partition where the fans are installed.
l Lower than 25°C (77°F): the fans run at low speed.
l Higher than 45°C (113°F): the fans run at high speed.
l 25°C to 45°C (77°F to 113° F): The fans automatically adjust their
rotation speeds. This mode can reduce noise and is power-saving.
Fan speed in each partition is independently regulated.
The fans run at full speed if the speed regulating signals are abnormal.
If one of the fans fails, the other fans run at full speed.
Adjustable Speed Five fan speed modes are available: Low Speed, Medium-Low
Mode Speed, Medium Speed, Medium-High Speed, and High Speed. You
can set the fan speed manually. In Adjustable Speed Mode, the fans in
all partitions run at the same speed and do not support the partitioned
manual fan speed adjustment.
Each OptiX OSN 8800 T16 subrack is divided into five partitions in terms of heat dissipation.
The subrack adopts one fan tray assembly to implement partitioned heat dissipation. See Figure
3-25.
Figure 3-25 Partitioned heat dissipation of the OptiX OSN 8800 T16 subrack
IU9 IU10
IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU IU
1 2 3 4 5 6 7 8 11 12 13 14 15 16 17 18
Fan tray
A B C D E
assembly
In the OptiX OSN 8800 T16, there are five partitions (A, B, C, D, and E) in each subrack. Two
fans in each partition dissipate heat generated by the boards in the partition where the fans reside.
NOTE
If any one of the ten fans in the fan tray assembly fails, the system can keep on operating for 96 consecutive
hours in an environment with temperatures between 0°C to 45°C (32°F to 113°F).
Replace the fan tray assembly immediately if two or more fans fail in the fan tray assemblies.
The fan tray assembly consists of fans and fan control unit. Figure 3-26 shows the functional
blocks of the fan tray assembly.
FAN
l FAN: dissipates heat generated by normal operation of the subrack. FAN is the core of the
fan tray assembly.
l Fan control board:
– Controls the fan speed according to the fan speed regulating signals.
– Detects faults. After a fault is detected, the fan control unit reports an alarm. In this case,
the SCC board issues commands to instruct the other fans to run at the full speed.
– Monitors speed regulating signals, the fan status, and the online/offline state of the fan
tray assembly.
– Receives and carries out commands from the SCC board to shut down the fans on the
fan tray assembly if necessary.
Appearance
Figure 3-27 shows a fan tray assembly.
NOTE
An air filter is installed on the fan tray assembly to prevent dust from entering the subrack.
Valid Slots
The fan tray assembly occupies one slot. The valid slot for the fan tray assembly is IU25 in the
OptiX OSN 8800 T16 subrack.
NOTE
For the transport equipment, heat consumption and power consumption are similar and can be taken as the
same. Heat consumption (BTU/h) = Power consumption (W) x Time (h)/0.2931(Wh).
Dimensions 493.7 mm (W) x 266.6 mm (D) x 56.1 mm (H) (19.44 in. (W)
x 10.5 in. (D) x 2.21 in. (H))
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 215 W.
NOTE
For transport equipment, the heat consumption and power consumption are similar and can be considered
the same. Heat consumption is expressed in BTU/h and power consumption is expressed in W. The
conversion between the two units is as follows: 1 BTU/h = 0.2931 W.
Typical configuration power consumption indicates the average power consumption of the equipment with
the typical configuration and the equipment runs at the room temperature. Maximum power consumption
indicates the possible maximum power consumption when the equipment runs in an environment with
extreme conditions.
a: The maximum subrack power consumption refers to the theoretical power consumption
obtained when boards with the highest power consumption are installed in every slot on the
subrack.
Table 3-27 describes the power consumption of the subrack in typical configuration in an 8800
T16.
Table 3-27 Power consumption of the common units in an OptiX OSN 8800 T16
Unit Typical Maximum Remarks
Name Power Power
Consumpt Consumpt
ion at 25°C ion at 55°C
(77°F) (W)a (131°F)
(W)a
a: Indicates that the power consumption of the subrack and cabinet is the value in a certain
configuration. The value is for reference only. The actual power consumed by the chassis and
cabinet is a calculation based on the power consumption of each module.
Table 3-28 Requirements on voltage and current of an OptiX OSN 8800 T16
Item Requirement
PIU
The PIU board receives and provides DC power for equipment. For OptiX OSN 8800/6800A,
the PIU board must be TN41PIU.
l Function
Accesses DC power in a range from -40 V to -57 V. Provides lightning protection and
power filtering functions.
l Front Panel
Appearance of the Front Panel
PIU
PWR
RTN(+) REG(-)
OptiX OSN 8800 T64 IU69, IU70, IU78, IU79, IU80, IU81, IU88, and IU89
l Specifications
– Performance Specifications
– Mechanical Specifications
Dimensions of front panel: 50.8 mm (W) x 220 mm (D) x 80 mm (H) (2.0 in. (W) x 8.7
in. (D) x 3.1 in. (H))
Weight: 0.7 kg (1.54 lb.)
– Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C Consumption at 55°C
(77°F) (W) (131°F) (W)
TN41PIU 45 45
Cables
l Power cables
The power cable uses a two-hole OT terminal to connect to the PIU board of each OptiX
OSN 8800/6800A subrack, as shown in Figure 3-29.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-29 Two-hole OT terminals on the OptiX OSN 8800/6800A power cable
NOTE
Two-hole OT terminals are installed on PIU terminal sockets. A PIU terminal socket is 0.49 inch wide and so
two-hole OT terminal's width cannot exceed 0.49 inch.
l Ground cables
The ground cable of each OptiX OSN 8800/6800A uses a two-hole OT terminal, as shown
in Figure 3-30. The subrack, DCM frame, and heat baffle each has a ground point. For
details on how to connect ground cables, see Quick Installation Guide.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-30 OT terminal on the ground cable of the OptiX OSN 8800/6800A
M6 screw
0.25 inch
Subrack
0.75 inch
0.75
inch
Two-hole OT terminal
M6(0.25 inch)
Figure 3-31 OptiX OSN 6800A subrack structure (subrack door included)
Door
Figure 3-32 OptiX OSN 6800A subrack structure (subrack door excluded)
NOTE
The interface area is behind the indicator panel in the upper part of the subrack. Remove the indicator panel
before you connect cables.
l Indicator: indicate the running status and alarm status of the subrack.
l Board area: All service boards are installed in this area. 20 slots are available.
l Air filter: The air filter protects the subrack from dust in the air. Air filter features include
– Dust arrest rating of 85%.
– Fire rating of UL94V-0.
– Preventing any air bypass.
l Fiber cabling area: Fiber jumpers from the ports on the front panel of each board are routed
to the fiber cabling area before being routed on the side of the open rack.
l Fan tray assembly: The fan tray assembly contains ten fans that provide ventilation and
heat dissipation for the subrack.
NOTE
For detailed descriptions of the fan tray assembly, see 3.3.5 Fan and Heat Baffle.
l Fiber spool: Fixed fiber spools are on two sides of the subrack. Extra fibers are coiled in
the fiber spool on the open rack side before being routed to another subrack.
l Mounting ear: The mounting ears attach the subrack to the open rack.
l Interface area: The interface area provides functional interfaces, such as management
interface, inter-subrack communication interface, alarm output and cascading interface,
alarm input and output interface. It is located behind the subrack indicator panel.
Table 3-30 lists the technical specifications of the OptiX OSN 6800A subrack.
a: An empty subrack means no boards are installed in the board area, and no fan tray assembly
or air filter is installed.
IU1 IU2 IU3 IU4 IU5 IU6 IU7 IU8 IU11 IU12 IU13 IU14 IU15 IU16
IU20
IU9 IU10 IU17 IU18
AUX
Fan
The subrack provides various communication and maintenance interfaces for the management
and maintenance purposes, as shown in Table 3-31.
of OptiX OSN
8800/6800A.
WARNING
The intra-building port(s) of the equipment or subassembly is suitable for connection to
intrabuilding or unexposed wiring or cabling only. The intra-building port(s) of the equipment
or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or
its wiring. These interfaces are designed for use as intra-building interfaces only (Type 2 or Type
4 ports as described in GR-1089-CORE, Issue 5) and require isolation from the exposed OSP
cabling. The addition of Primary Protectors is not sufficient protection in order to connect these
interfaces metallically to OSP wiring.
Integrated Grooming
When using the XCS board, an OptiX OSN 6800A subrack can cross-connect ODU1,
ODU2,ODU2e, 10GE, and GE services between any two slots among slots IU1-IU8 and slots
IU11-IU16. Figure 3-34 provides the cross-connect capacity for each slot.
IU1 IU2 IU3 IU4 IU5 IU6 IU7 IU8 IU11 IU12 IU13 IU14 IU15 IU16
IU20
IU9 IU10 IU17 IU18
AUX
Fan
Table 3-32 describes the cross-connect capacities of an OptiX OSN 6800A subrack when
TN12XCS boards are configured in the subrack.
ODU1/ODU2/ GE
ODU2e/10GE
Distributed Grooming
An OptiX OSN 6800A subrack provides seven pairs of slots: IU1 and IU2, IU3 and IU4, IU5
and IU6, IU7 and IU8, IU11 and IU12, IU13 and IU14, IU15 and IU16. GE/Any/ODU1/OTU1
services can be cross-connected between paired slots. No XCS board is required when paired
slots are used to cross-connect electrical services.
Version Description
Only one functional version of the fan tray assembly is available, that is, TN11.
Function Description
Basic function Dissipates the heat generated by an NE so that the NE can operate
normally within the designated temperature range.
Partitioned heat Each subrack is divided into five partitions to help provide
dissipation efficient heat dissipation. The fan speed in each partition is
independently regulated.
Function Description
Hot swapping Provides the hot swapping feature for the fan tray assembly.
Alarming Reports alarms of the fans, and reports the in-service information.
Working Principle
Air flow from the subrack is bottom intake top exhaust. Heat baffles will cause air to be drawn
from the bottom of the subrack and direct hot fan exhaust to the top of the subrack. Figure
3-35 shows the heat dissipation and ventilation system in the OptiX OSN 6800A.
Air o utlet
Board area
Optical fiber
laying area
Fan tray assembly
Airinlet
The OptiX OSN 6800A supports two fan speed modes, as shown in Table 3-34. The partitioned
speed regulating function is available in Auto Speed Mode. It is recommended that you set the
speed mode to Auto Speed Mode.
Auto Speed Mode Fan speed in each partition is regulated automatically according to the
temperature of the boards in the partition where the fans are installed.
l Lower than 25°C (77°F): the fans run at low speed.
l Higher than 45°C (113°F): the fans run at high speed.
l 25°C to 45°C (77°F to 113° F): The fans automatically adjust their
rotation speeds. This mode can reduce noise and is power-saving.
Fan speed in each partition is independently regulated.
The fans run at full speed if the speed regulating signals are abnormal.
If one of the fans fails, the other fans run at full speed.
Adjustable Speed Four fan speed modes are available: Stop, Low Speed, Medium
Mode Speed, and High Speed. You can set the fan speed manually. In
Adjustable Speed Mode, the fans in all partitions run at the same speed
and do not support the partitioned manual fan speed adjustment.
Set the fan speed mode to Stop before you replace an air filter to prevent
dust from entering the fan.
Each OptiX OSN 6800A subrack is divided into five partitions in terms of heat dissipation. The
subrack adopts one fan tray assembly to implement partitioned heat dissipation. See Figure
3-36.
Figure 3-36 Partitioned heat dissipation of the OptiX OSN 6800A subrack
IU19
IU1 IU2 IU3 IU4 IU5 IU6 IU7 IU8 IU9 IU10 IU11 IU12 IU13 IU14 IU15 IU16 IU17 IU18
IU20
A B C D E IU26
There are five partitions (A, B, C, D, and E) in each subrack. Two fans in each partition dissipate
heat generated by the boards in the partition where the fans reside.
NOTE
l If any one of the ten fans in the fan tray assembly fails, the system can keep on operating for 96
consecutive hours in an environment with temperatures between 0°C to 45°C (32°F to 113°F).
l Replace the fan tray assembly immediately if:
Two or more fans fail in the fan tray assemblies.
The fan tray assembly consists of ten fans and one fan control unit. Figure 3-37 shows the
functional blocks of the fan tray assembly.
FAN
l FAN: dissipates heat generated by normal operation of the subrack. FAN is the core of the
fan tray assembly.
l Fan control board:
– Controls the fan speed according to regulating signals.
– Detects faults. After a fault is detected, the fan control unit reports an alarm. In this case,
the SCC board issues commands to instruct the other fan in the same partition to run at
full speed.
– Monitors the fan speed regulating signals, the fan status, and the online/offline state of
the fan tray assembly.
– Receives and carries out commands from the SCC board to shut down the fans on the
fan tray assembly if necessary.
Appearance
Figure 3-38 shows a fan tray assembly.
NOTE
An air filter is installed on the fan tray assembly to prevent dust from entering the subrack.
Valid Slots
One slot houses one fan tray assembly. The valid slots for the fan tray assembly is IU26.
NOTE
For the transport equipment, heat consumption and power consumption are similar and can be taken as the
same. Heat consumption (BTU/h) = Power consumption (W) x Time (h)/0.2931(Wh).
Item Specification
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 120 W.
NOTE
For the transport equipment, heat consumption and power consumption are similar and can be taken as the
same. Heat rate (BTU/h) = Power consumption (W) x Time (h)/0.2931(Wh).
Typical configuration power consumption indicates the average power consumption of the equipment with
the typical configuration and the equipment runs at the room temperature. Maximum power consumption
indicates the possible maximum power consumption when the equipment runs in an environment with
extreme conditions.
Table 3-37 lists the power consumption of the common units in an OptiX OSN 6800A.
Table 3-37 Power consumption of the common units in an OptiX OSN 6800A
Unit Name Typical Maximum Remarks
Power Power
Consumpti Consumpti
on at 25°C on at 55°C
(77°F)a (131°F)a
a: Indicates that the power consumption of the subrack and cabinet is the value in a certain
configuration. The value is for reference only. The actual power consumption of the chassis
and cabinet is calculation based on the power consumption of each module.
b: Subrack 1 and subrack 2 are used as subracks in the line dimensions at a four-dimension
RADOM station; subrack 3 and subrack 4 are used as subracks for adding/dropping local
services. Service boards can be configured in another subrack.
PIU
The PIU board receives and provides DC power for equipment. For OptiX OSN 8800/6800A,
the PIU board must be TN41PIU.
l Function
Accesses DC power in a range from -40 V to -57 V. Provides lightning protection and
power filtering functions.
l Front Panel
Appearance of the Front Panel
PIU
PWR
RTN(+) REG(-)
OptiX OSN 8800 T64 IU69, IU70, IU78, IU79, IU80, IU81, IU88, and IU89
l Specifications
– Performance Specifications
– Mechanical Specifications
Dimensions of front panel: 50.8 mm (W) x 220 mm (D) x 80 mm (H) (2.0 in. (W) x 8.7
in. (D) x 3.1 in. (H))
Weight: 0.7 kg (1.54 lb.)
– Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C Consumption at 55°C
(77°F) (W) (131°F) (W)
TN41PIU 45 45
Cables
l Power cables
The power cable uses a two-hole OT terminal to connect to the PIU board of each OptiX
OSN 8800/6800A subrack, as shown in Figure 3-40.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-40 Two-hole OT terminals on the OptiX OSN 8800/6800A power cable
NOTE
Two-hole OT terminals are installed on PIU terminal sockets. A PIU terminal socket is 0.49 inch wide and so
two-hole OT terminal's width cannot exceed 0.49 inch.
l Ground cables
The ground cable of each OptiX OSN 8800/6800A uses a two-hole OT terminal, as shown
in Figure 3-41. The subrack, DCM frame, and heat baffle each has a ground point. For
details on how to connect ground cables, see Quick Installation Guide.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-41 OT terminal on the ground cable of the OptiX OSN 8800/6800A
M6 screw
0.25 inch
Subrack
0.75 inch
0.75
inch
Two-hole OT terminal
M6(0.25 inch)
Figure 3-42 Appearance of an OptiX OSN 3800A chassis (chassis door included)
Door
Figure 3-43 Appearance of an OptiX OSN 3800A chassis (chassis door excluded)
6
2
7
1
1. Fiber frame 2. Mounting ear 3. Board area 4. Fan indicator
5. Air filter 6. Airduct frame 7. Rotary fiber routing rack
NOTE
When an OptiX OSN 3800A chassis is installed in a 19-inch open rack, an airduct frame cannot be installed in
the chassis; when the OptiX OSN 3800A chassis is installed in a 23-inch open rack, an airduct frame is optional.
l Fiber frame: Fiber jumpers in the service board area are routed through the fiber frame.
l Mounting ears: Mounting ears attach the chassis in the open rack.
l Board area: All service boards are installed in this area. In total, 11 slots are available.
l Fan indicator: The fan indicator indicates the status of the fans.
l Air filter: The air filter prevents dust from entering the chassis.
– Dust arrest rating of 85%.
– Fire rating of UL94V-0.
– Preventing any air bypass.
IU1 IU11
IU6/APIU
IU2
FAN IU3 IU7/APIU
IU4 IU9/SCC
IU5 IU10/AUX
NOTE
l : service boards.
l Slots IU1 and IU11 can be used as two independent slots, each for housing an FOADM board with a height
of 118.9 mm (4.7 in.). They can be also used as one slot for housing a service board with a height of 264.6
mm (10.4 in.). When the two slots are used as one slot, the slot ID is represented as IU11.
l Pair slots refer to a pair of slots whose resident boards' overhead can be processed by the buses on the
backplanes.
l A mesh group refers to a group of slots housing the boards whose overhead can be processed by the buses
on the backplane.
Maximum Management
Power serial
NM_ETH2
Consumptio interface:
n at 55°C SERIAL
(131°F): 17 Alarm input
W interface:
ALMI1/
ALMI2
EXT
NOTE
EXT
interfaces
include
AUX ETH,
SERIAL,
ALMI1, and
ALMI2. The
ETH
interface is
reserved for
future use.
Therefore,
do not
connect a
cable to the
ETH
interface.
WARNING
The intra-building port(s) of the equipment or subassembly is suitable for connection to
intrabuilding or unexposed wiring or cabling only. The intra-building port(s) of the equipment
or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or
its wiring. These interfaces are designed for use as intra-building interfaces only (Type 2 or Type
4 ports as described in GR-1089-CORE, Issue 5) and require isolation from the exposed OSP
cabling. The addition of Primary Protectors is not sufficient protection in order to connect these
interfaces metallically to OSP wiring.
3.4.4 Fan
Each OptiX OSN 3800A chassis has one fan tray assembly, which includes six independent fans
and an air filter. The air filter can be drawn out and replaced.
Version Description
Only one functional version of the fan tray assembly is available, that is, TN61.
Working Principle
Air flow from the subrack is left intake right exhaust. Heat baffles will cause air to be drawn
from the bottom of the subrack and direct hot fan exhaust to the top of the subrack. Figure
3-46 shows the heat dissipation and ventilation system in the OptiX OSN 3800A.
Figure 3-46 Front view of the heat dissipation and ventilation system
The OptiX OSN 3800A supports two fan speed modes, as shown in Table 3-43. It is
recommended that you set the speed mode to Auto Speed Mode.
Adjustable Speed Four fan speed modes are available: Stop, Low Speed, Medium
Mode Speed, and High Speed. You can set the fan speed manually. In
Adjustable Speed Mode, the fans in all partitions run at the same speed
and do not support the partitioned manual fan speed adjustment.
NOTE
l If any one of the six fans in the fan tray assembly fails, the system can keep on operating for 96
consecutive hours in an environment with temperatures between 0°C to 45°C (32°F to 113°F).
l Replace the fan tray assembly immediately if:
Two or more fans fail in the fan tray assembly.
The fan tray assembly consists of six fans and one fan control unit. Figure 3-47 shows the
functional block of the fan tray assembly.
Status signal
l FAN: dissipates heat generated by normal operation of the chassis. FAN is the core of the
fan tray assembly.
l Fan control board:
– Controls the fan speed according to regulating signals.
– Detects faults. After a fault is detected, the fan control unit reports an alarm.
– Monitors the fan speed regulating signals, the fan status, and the online/offline state of
the fan tray assembly.
– Receives and carries out commands from the SCC board to shut down the fans on the
fan tray assembly if necessary.
Appearance
Figure 3-48 shows a fan tray assembly.
Valid Slots
One slot houses one fan tray assembly. The valid slot for the fan tray assembly is IU12.
NOTE
For the transport equipment, heat consumption and power consumption are similar and can be taken as the
same. Heat consumption (BTU/h) = Power consumption (W) x Time (h)/0.2931(Wh).
Dimensions 41.0 mm (W) x 262.6 mm (D) x 126.5 mm (H) (1.61 in. (W) x
10.34 in. (D) x 4.98 in. (H))
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 32.7 W.
NOTE
For transport equipment, the heat consumption and power consumption are similar and can be considered
the same. Heat consumption is expressed in BTU/h and power consumption is expressed in W. The
conversion between the two units is as follows: 1 BTU/h = 0.2931 W.
Typical configuration power consumption indicates the average power consumption of the equipment with
the typical configuration and the equipment runs at the room temperature. Maximum power consumption
indicates the possible maximum power consumption when the equipment runs in an environment with
extreme conditions.
Item Value
Table 3-46 lists the power consumption of the common units in an OptiX OSN 3800A.
Table 3-46 AC Power consumption of the chassis in typical configuration in an OptiX OSN
3800A
a: Indicates that the power consumption of the chassis is the value in a certain configuration.
The value is for reference only. The actual power consumption of the chassis is calculated
based on the power consumption of each module.
Item Requirement
Item Requirement
APIU
The APIU board receives and provides AC power for equipment. For OptiX OSN 3800A, the
APIU board must be TN21APIU.
l Function:
Accesses AC power in a range from 90 V to 285 V. Provides lightning protection and power
filtering functions.
l Front Panel:
Appearance of the Front Panel
APIU
RUN
OFF
ON
~100-240V
S1 S11 APIU
S5 AUX
S4 SCC
S3 APIU
S2
l Specifications:
– Performance Specifications
Input frequency Hz 50
– Mechanical Specifications
Dimensions of front panel: 37.5 mm (H) x 100 mm (W) x 220 mm (D) or 1.5 in. (H) x
3.9 in. (W) x 8.7 in. (D)
Weight: 0.8 kg (1.8lb.)
– Power Consumption
TN21APIU 50 55
Cables
Figure 3-50 shows an AC power cable for OptiX OSN 3800A.
NOTE
Determine the power cable diameters and colors based on the network configuration
Table 3-49 describes the DC power consumption of an OptiX OSN 3800A chassis.
NOTE
For the transport equipment, heat consumption and power consumption are similar and can be taken as the
same. Heat rate (BTU/h) = Power consumption (W) x Time (h)/0.2931(Wh).
Typical configuration power consumption indicates the average power consumption of the equipment with
the typical configuration and the equipment runs at the room temperature. Maximum power consumption
indicates the possible maximum power consumption when the equipment runs in an environment with
extreme conditions.
Item Value
Table 3-50 lists the power consumption of the common units in an OptiX OSN 3800A.
Table 3-50 DC Power consumption of the chassis in typical configuration in an OptiX OSN
3800A
a: Indicates that the power consumption of the chassis is the value in a certain configuration.
The value is for reference only. The actual power consumption of the chassis is calculated
based on the power consumption of each module.
PIU
The PIU board receives and provides DC power for equipment. For OptiX OSN 3800A, the PIU
board must be TN61PIU.
l Function:
Accesses DC power in a range from -40 V to -57 V. Provides lightning protection and
power filtering functions.
l Front Panel:
Appearance of the Front Panel
PWR
-48 V
10 A
S1 S11
S6
S5
S4
S2
SCC
SCC
AUX
PIU
PIU
Do not hot
plug this unit!
PIU
– Mechanical Specifications
Dimensions of front panel: 218.50 mm (H) x 107.76 in. (W) or 8.6 in. (H) x 4.2 in. (W)
Weight: 0.5 kg (1.0 lb.)
– Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C Consumption at 55°C
(77°F) (W) (131°F) (W)
TN61PIU 19 21
Cables
l Power cables
The power cable uses a one-hole OT terminal to connect to the PIU board of each OptiX
OSN 3800A chassis, as shown in Figure 3-52.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-52 One-hole OT terminal on the OptiX OSN 3800A power cable
0.164 inch
One-hole OT terminal
M4(Stude Size #8,0.164)
M4 screw Power cable PIU
NOTE
One-hole OT terminals are installed on PIU terminal sockets. A PIU terminal socket is 0.51 inch wide and so
two-hole OT terminal's width cannot exceed 0.51 inch.
l Ground cables
The ground cable of each OptiX OSN 3800A chassis uses a one-hole OT terminal, as shown
in Figure 3-53. The chassis, DCM frame, and heat baffle each has a ground point.
NOTE
Select the OT terminals and determine the power cable diameters and colors based on the network
configuration. Ensure that the diameters of the OT terminals match the power cable diameters.
Figure 3-53 OT terminal on the ground cable of the OptiX OSN 3800A chassis
M4 screw
0.164 inch
Chassis
0.625 inch
0.625
inch
Two-hole OT terminal
M4(Stud size #8, 0.164)
3.5 Frame
1 2
1 2
Table 3-53 Performance requirements for C-band dispersion compensation optical fibers (G.
652 fibers)
a: The Max. Allowed Power refers to the maximum input optical power that the optical module
can receive without being damaged.
Table 3-54 Performance requirements for C-band dispersion compensation optical fibers (G.
655 LEAF fibers)
a: The Max. Allowed Power refers to the maximum input optical power that the optical module
can receive without being damaged.
Table 3-55 Performance requirements for C-band dispersion compensation optical fibers (G.
653 fibers)
DCM Distance Max. DSC PMD PDL Max. Opera
Module (mi./km) Insert R (ps) (dB) Allowe ting
ion d Wavel
Loss Powera ength
(dB) (dBm) (nm)
a: The Max. Allowed Power refers to the maximum input optical power that the optical module
can receive without being damaged.
Table 3-56 Performance requirements for C-band dispersion compensation optical fibers (TW-
RS fibers)
DCM Module Distance Max. DSC PMD PDL Max. Opera
(mi./km) Insert R (ps) (dB) Allowe ting
ion d Wavel
Loss Powera ength
(dB) (dBm) (nm)
a: The Max. Allowed Power refers to the maximum input optical power that the optical module
can receive without being damaged.
Dimensions l DCM frame for 23–inch open rack: 50.0 mm (H) x 536.0 mm (W)
x 375.0 mm (D) (2.0 in. (H) x 21.1 in. (W) x 14.8 in. (D))
l DCM frame for 19–inch open rack: 48.0 mm (H) x 436.0 mm (W)
x 280.0 mm (D) 1.9 in. (H) x 17.2 in. (W) x 11 in. (D)
Weight l DCM frame for 23–inch open rack: 1.5 kg (3.3 lb.)
l DCM frame for 19–inch open rack: 1.3 kg (2.9 lb.)
Item Value
CAUTION
Always wear a properly grounded ESD wrist strap when holding a board to prevent static from
damaging the board.
Table 3-59 shows the appearance and dimensions of the different board types.
Height
Depth
Height
Depth
Height
Depth
Height
Depth
Such information as frequency of signals queried on the U2000 is a commissioning value, different from
that on the bar code.
Figure 3-57 and Figure 3-58 show the bar codes of boards installed with optical modules.
Figure 3-59 and Figure 3-60 show the bar codes of boards not installed with optical modules.
Serial number
Manufacture month
Vendor
Manufacture year
BOM Environmental Board Tunable Characteristic
friendliness flag name code
(Y: Environmentally
friendly)
Serial number
Manufacture month
Vendor
Manufacture year
The complete BOM Environmental Board model
should be 0303OHFY. friendliness flag number
"03" are taken out in the (Y: Environmentally
BOM above. friendly)
The first four numbers in the board BOM indicate whether the board is installed with an optical
module. Table 3-61 provides the meanings of the first four numbers in the board BOM.
Table 3-61 Meanings of the first four numbers in the BOMs for boards
Board First Four Description First Four Numbers
Configuration Numbers in in the BOM of the
the board Required Optical
BOM Module
Board not installed 0303 The board is installed 3406 or 0303 (client
with optical modules with a wavelength side)
tunable optical module
on its WDM side.
Client-side optical
modules need to be
selected as required for
the board.
Manufacture Year Indicates the last digit of the year when a board is manufactured.
For example, "4" indicates 2004. From 2010 onwards, a letter is
used to indicate the manufacture year. For example, the letter A
indicates 2010, the letter B indicates 2011, and so on.
Manufacture Month Indicates the month when a board is manufactured. The value is
expressed in hexadecimal format. For example, the letter B
indicates November.
Serial Number Indicates the production serial number of a board. The value ranges
from 000001 to 999999.
TN12LOG Y Y Y
TN12LO Y Y Y
M
TN13LSX Y Y Y
TN15LSX Y Y N
L
TN53TQX Y Y Y
TN55TQX Y Y Y
TN54TSX Y Y Y
L
TN53ND2 Y Y Y
TN53NQ2 Y Y Y
TN54NQ2 Y Y Y
TN53NS2 Y Y Y
TN54NS3 Y Y Y
TN55NS3 Y Y Y
TNK4XC Y N N
T
TN51SCC N Y N
d
TN52SCC N Y N
TNK2SCC Y N N
TN51AUX Y Y N
TN12M40 Y Y Y
V
TN14FIU Y Y Y
TN13WS Y Y Y
D9
TN13WS Y Y Y
M9
TN12WS Y Y Y
MD4
TN12OAU Y Y Y
1
TN13OAU Y Y Y
1
TN12OBU Y Y Y
1
TN11OBU Y Y N
2
TN12OBU Y Y Y
2
TNK2STG Y N N
TN51EFI1 Y Y N
TN51EFI2 Y Y N
a: For TN11RMU9: OptiX OSN 8800 T16 only supports the TN11RMU902.
b: For details of the ROPA subsystem unit refer to ROPA System.
c: For details of the interface area unit refer to Data Communication and Equipment Maintenance Interfaces.
d:TN51SCC only supports General OptiX OSN 8800 T32.
Table 3-64 lists the boards for the OptiX OSN 6800A.
TN12LOG
TN13LSX
TN52TDX
TN53TDX
TN52TOM
TN52TQX
TN55TQX
TN12ND2
TN52ND2
TN53ND2
TN52NQ2
TN53NQ2
TN52NS2
TN53NS2
TN52NS3
TN54NS3
TN55NS3
TN12M40V
TN14FIU
TN13WSM9
TN12OAU1
TN13OAU1
TN12OBU1
TN12OBU2
Interface area TN41ATE interface board of alarm & timing & expanding
unitb
TN51EFI1 EMI filter interface board
a: For the details of the ROPA subsystem unit, refer to ROPA System.
b: For the details of the interface area unit, refer to 3.3 OptiX OSN 6800A Subrack and
Power Requirement.
TN12LOG
TN13LSX
TN52TOM
TN52NS2
TN53NS2
TN21CMR4
TN21MR2
TN21MR4
TN12OAU1
TN13OAU1
TN12OBU1
TN12OBU2
Convergence Application
Convergence application means multiple client services are aggregated into one ODUk signal
to improve the bandwidth utilization.
Figure 3-61 uses the TOM board as an example to illustrate the convergence application.
TOM board
ESCON ESCON
GE GE OTUk
ODU1 Line
FC100 FC100 board
Non-convergence Application
Non-convergence application means that each client service is directly mapped into an ODUk
signal that matches the client service. In this application, flexible service grooming is achieved.
Figure 3-62 uses the TQX board as an example to illustrate the non-convergence application.
The TOA, and TOM boards support both convergence mode and non-convergence applications.
The TQM board only supports the convergence application.
l In the convergence application, the TOA, TQM, and TOM boards aggregate multiple low-
rate client services into one ODU1 or ODU0 signal.
l In the non-convergence application, the TOA, and TOM boards map one client service into
one ODUk signal.
Other tributary boards only support the non-convergence application and therefore can only map
one client service into one ODUk signal.
Compared with the compatible mode, the standard mode makes operations easier and has fewer
end-to-end trail layers, reducing maintenance costs.
TN54TSXL - 54TSXL
TN55NS3 - 55NS3
TN54ENQ2(STND) - 54ENQ2
TN55NPO2(STND) - 55NPO2
TN55NPO2E - 55NPO2E
NOTE
TN54TSXL/TN55NO2/TN55NS3/TN54NS4//TN55NPO2/TN54ENQ2/TN55NPO2E support only the
standard mode.
The following uses the TN53NS2 board as an example to introduces the standard and compatible
modes of a line board.
Standard mode
Figure 3-63 shows the board model of the TN53NS2 board in standard mode.
IN/OUT-OCh:1-ODU2:1-ODUflex:(1~2)
ODUflex:1
ODU2:1 OCh:1
2XODUflex ODUflex:2
IN/OUT-OCh:1
OCh :1
1 xODU2/
1xODU 2e
IN/OUT-OCh:1-ODU2:1-ODU1:(1~4)
Other tributary/line/PID board
ODU1:1
ODU2:1 OCh : 1
4 xODU1
ODU1:4 IN/OUT
IN/OUT-OCh:1-ODU2:1-ODU1:(1~4)-ODU0:(1~2)
ODU0:1
ODU1:1
ODU0:2
ODU2:1 OCh :1
8 xODU0 ODU 0:1
ODU 1:4
ODU 0:2
IN/OUT-OCh:1-ODU2:1-ODU0:(1~8)
ODU0:1
ODU2:1 OCh :1
8 xODU0
ODU0: 8
Backplane
Compatible mode
Figure 3-64 shows the board model of the TN53NS2 board in compatible mode.
161
51
(ODU0LP1/ODU0LP1)-1
161 ODU1 (ODU1LP1/ODU1LP1)-1
(ODU0LP1/ODU0LP1)-2
71
(ODU2LP1/ODU2LP1)-1 1
(IN1/OUT1)-1
164
ODU2
(ODU0LP4/ODU0LP4)-1 51
164 ODU1 (ODU1LP1/ODU1LP1)-4
(ODU0LP4/ODU0LP4)-2
Logical ports are internal points used to adapt, terminate, and multiplex internal signals of the
board. They also can be used as sources or sinks of cross-connections.
Path View In the NE panel, select a See Figure 3-65. See Figure 3-66.
board, double-click the board
icon or right-click and choose
Path View from the shortcut
menu.
WDM In the NE Explorer, select the See Figure 3-67. See Figure 3-68.
Interface required board and choose
Configuration > WDM
Interface from the Function
Tree.Click the Advanced
Attributes tab.
Create Cross- In the NE Explorer, select the See Figure 3-69. See Figure 3-70.
Connection required NE and choose
Service Configuration > WDM
Service Management from
the Function Tree.
Figure 3-71 shows the appearance of the eSFP/SFP+ optical module. Figure 3-72 shows the
appearance of the XFP optical module.Figure 3-73 and Figure 3-74 show the appearance of the
CFP optical module.
Table 3-70 Quick reference table for client-side specifications of OTUs and tributary boards
10 Gbit/s 4 0 -24.0 -7
Multirate-80
km-XFP
FC400/ -2 -8 -18 0
FICON4G
Module-10 km
(Single mode) -
eSFP
FC400/ -2 -8 -18 0
FICON4G
Module-10 km
(Single mode)-
eSFP
L-16.2/LR-2 3 -2 -28 -9
OC-48-80 km-
eSFP
L-16.2/LR-2 3 -2 -28 -9
OC-48-80 km-
eSFP
L-16.2/LR-2 3 -2 -28 -9
OC-48-80 km-
eSFP
10 Gbit/s 4 0 -24.0 -7
Multirate-80
km-XFP
10 Gbit/s 4 0 -24.0 -7
Multirate-80
km-XFP
10 Gbit/s 4 0 -24.0 -7
Multirate-80
km-XFP
S-16.1/IR-1 0 -5 -18 0
OC-48-15 km-
eSFP
L-16.1/LR-1 3 -2 -27 -9
OC-48-40 km-
eSFP
L-16.2/LR-2 3 -2 -28 -9
OC-48-80 km-
eSFP
10 Gbit/s 4 0 -24 -7
Multirate-80
km-XFP
10 Gbit/s 4 0 -24.0 -7
Multirate-80
km-XFP
10 Gbit/s 4 0 -24.0 -7
Multirate-80
km-XFP
10 Gbit/s 4 0 -24 -7
Multirate-80
km-XFP
L-16.2/LR-2 3 -2 -28 -9
OC-48-80 km-
eSFP
L-16.2/LR-2 3 -2 -28 -9
OC-48-80 km-
eSFP
L-16.2/LR-2 3 -2 -28 -9
OC-48-80 km-
eSFP
L-16.2/LR-2 3 -2 -28 -9
OC-48-80 km-
eSFP
10 Gbit/s 4 0 -24.0 -7
Multirate-80
km-XFP
10 Gbit/s 4 0 -24.0 -7
Multirate-80
km-XFP
10 Gbit/s 4 0 -24 -7
Multirate-80
km-XFP
TN12LSC 100GE 100 G -1.3 4.5 -8.6 4.5 -4.3 4.5 -10. 4.5 10.5 CFP
BASE- 6
LR4-10
km-CFP
100 G -2.8 3.5 -8.8 3.5 -5.8 3.5 -10. 3.5 13.5
BASE-1 8
0×10
G-10
km-CFP
TN54TSXL 40GE 40GBA -4 3.5 -11. 3.5 -7 2.3 -13. 2.3 8.3
SE- 5 7
LR4-10
km-CFP
Table 3-72 Quick reference table for DWDM-side specifications of OTU boards
a: The 12800 ps/nm-PIN and 12800ps/nm-APD modules do not support pilot tone modulation mode.
Table 3-73 Quick reference table for CWDM-side specifications of OTU boards
Board Access Optical Module
Name Service
Type Optical Interface Type Mean Launched Receiver Minimu Not
Supported Optical Power Sensitivi m e
ty (dBm) Overload
Maximu Minimu Point
m (dBm) m (dBm) (dBm)
Table 3-74 Quick reference table for specifications of WDM-side gray optical modules on OTU boards
Board Access Optical Module
Name Service
Type Optical Interface Type Mean Launched Receiver Minimu Note
Supported Optical Power Sensitivi m
ty (dBm) Overload
Maximu Minimu Point
m (dBm) m (dBm) (dBm)
Board Channel Nomin Input Power Range per Channel Nominal single-
Name Gain (dB) al (dBm) wavelength input optical
Chann power (dBm)
el Gain
(dB) 40 channels 80 channels 40 channels 80 channels
Board Channel Nomin Input Power Range per Channel Nominal single-
Name Gain (dB) al (dBm) wavelength input optical
Chann power (dBm)
el Gain
(dB) 40 channels 80 channels 40 channels 80 channels
TN12OBU1P1 -30 to 7 9
RAU1 19 to 33 19 to 35 20
Table 3-80 Quick reference table for board insertion loss specifications
Board Name Insertion Loss (dB)
Add/drop channel ≤4
Drop channel ≤4
Add channel ≤6
Add/drop channel ≤1
Add/drop channel ≤2
Add/drop channel ≤1
EIN-ETC ≤1
ERC-EOUT
WIN-WTC
WRC-WOUT
TN11D40/TN12D40 ≤6.5
TN11D40V ≤8a
IN-TC ≤1
RC-OUT
IN-TE <2.5
IN-TO
IN-TE <3
IN-TO
TN11M40/TN12M40 ≤6.5
TN11M40V/TN12M40V ≤8a
ROA-Drop(DM1-DM8) ≤11.5
IN-EXPO ≤12.5
IN-TOA ≤1
AMxb-TOA ≤12.5a
ROA-OUT ≤1.5
IN-DM ≤7
EXPI-OUT ≤14a
IN-EXPO ≤3
IN-DMxd ≤4.5
IN-DMxd/EXPO ≤12
Table 3-81 Ratio of the optical power of signals at MON to that of the main-path signals of each type of board
Board Name Ratio of MON Interface to Received Ratio of MON Interface to
Signal in Main Path Transmitting Signal in Main Path
FIU - l TN13FIU01/TN14FIU/TN21FIU:
"MONT"/"LOUT" = 1/99 (20 dB)
l TN13FIU02: "MONT"/"LOUT" =
0.1/99.9 (30 dB)
RAU1 - "MONO"/"OUT"=1/99(20dB)
"MONS"/"SYS"=1/99(20dB)
Table 3-82 Basic functions of OTUs, tributary boards and line boards
Board Tun ESC ALS OT FEC Encoding WDM Opti PRB PRB
Name able Fun Fun N Specificati cal S on S on
Wa ctio ctio Fun on Mod the the
vele n n ctio ule Clie WD
ngt n FEC AFE AFE HFE DW CW nt M
h C C-2 C DM DM Side Side
Fun
ctio
n
TN11L4 Y Y Y Y Y N N N Y N eSFP N N
G
TN12LD Y Y Y Y Y N Y N Y N XFP Y Y
X
TN11LE Y Y Y Y Y N N N Y N XFP/ N Y
M24 SFP
+
TN11LE Y Y Y Y Y N N N Y N XFP/ N Y
X4 SFP
+
Board Tun ESC ALS OT FEC Encoding WDM Opti PRB PRB
Name able Fun Fun N Specificati cal S on S on
Wa ctio ctio Fun on Mod the the
vele n n ctio ule Clie WD
ngt n FEC AFE AFE HFE DW CW nt M
h C C-2 C DM DM Side Side
Fun
ctio
n
TN11LO Y Y Y Y Y Y N N Y Y XFP/ Y Y
A eSFP
/SFP
+
TN11LO Y Y Y Y Y Y N N Y N eSFP N Y
G
TN12LO Y Y Y Y Y N Y N Y N eSFP N Y
G
TN11LO Y Y Y Y Y Y N N Y N eSFP N Y
M
TN12LO Y Y Y Y Y N Y N Y N eSFP N Y
M
TN11LQ Y Y Y Y Y N N N Y N eSFP N Y
G
TN13LQ N Y Y Y Y N N N Y Y eSFP Y Y
M
TN12LQ Y Y Y Y Y N N N Y N eSFP Y Y
MD
TN12LQ Y Y Y Y Y N N N Y N eSFP Y Y
MS
TN12LS Y Y Y Y N N N Y Y N CFP N Y
C
TN11LS Y Y Y Y Y N Y N Y N N Y N
Q
TN12LS Y Y Y Y Y Y N N Y N XFP Y Y
X
TN13LS Y Y Y Y Y N Y N Y N XFP Y Y
X
TN12LS Y Y Y Y Y Y N N Y N N Y N
XL
TN15LS Y Y Y Y N N N Y Y N N Y Y
XL
Board Tun ESC ALS OT FEC Encoding WDM Opti PRB PRB
Name able Fun Fun N Specificati cal S on S on
Wa ctio ctio Fun on Mod the the
vele n n ctio ule Clie WD
ngt n FEC AFE AFE HFE DW CW nt M
h C C-2 C DM DM Side Side
Fun
ctio
n
TN12LS Y Y Y Y Y Y N N Y N N N N
XLR
TN11LS Y Y Y Y Y Y N N Y N XFP N N
XR
TN11LT Y Y Y Y N N N Y Y N XFP Y Y
X
TN12L Y Y Y N N N N N Y Y eSFP N N
WXS
TN11T Y Y Y Y Y Y N N Y N eSFP Y Y
MX
TN12T Y Y Y Y Y N Y N Y N eSFP Y Y
MX
TN11N Y Y N Y Y Y N N Y N N – Y
D2
TN12N Y Y N Y Y Y Y N Y N N – Y
D2
TN52N Y Y N Y Y Y Y N Y N N – Y
D2
TN51N N Y N Y Y N N N Y N XFP – Y
Q2
TN53N Y Y N Y Y N Y N Y N XFP - Y
D2
TN52N N Y N Y Y N Y N Y N XFP – Y
Q2
TN53N Y Y N Y Y N Y N Y N XFP - Y
Q2
TN54N Y Y N Y Y N Y N Y N XFP - Y
Q2
TN12NS Y Y Y Y Y Y N N Y N N – Y
2
TN52NS Y Y Y Y Y N Y N Y N N – Y
2
Board Tun ESC ALS OT FEC Encoding WDM Opti PRB PRB
Name able Fun Fun N Specificati cal S on S on
Wa ctio ctio Fun on Mod the the
vele n n ctio ule Clie WD
ngt n FEC AFE AFE HFE DW CW nt M
h C C-2 C DM DM Side Side
Fun
ctio
n
TN11NS Y Y N Y Y Y N N Y N N – Y
3
TN52NS
3
TN53NS Y Y N Y Y N Y N Y N XFP - Y
2
TN54NS Y Y N Y Y N Y N Y N N – Y
3
TN55NS Y Y N Y N N N Y Y N N - Y
3
TN12TD N N Y N N N N N N N eSFP Y –
X
TN52TD N Y Y N N N N N N N eSFP Y –
X
TN53TD N Y Y Y N N N N N N XFP Y –
X
TN54TE N N Y Y N N N N N N eSFP N N
M28 /SFP
+
TN54TO N N Y Y Y N N N N N eSFP Y –
A
TN11TO N Y Y Y Y N N N Y Y eSFP Y Y
M
TN52TO
M
TN11TQ N N Y Y N N N N N N XFP Y –
X
TN53TQ
X
TN55TQ N Y Y Y N N N N N N XFP Y –
X
TN11TS N N Y Y N N N N N N N N –
XL
Board Tun ESC ALS OT FEC Encoding WDM Opti PRB PRB
Name able Fun Fun N Specificati cal S on S on
Wa ctio ctio Fun on Mod the the
vele n n ctio ule Clie WD
ngt n FEC AFE AFE HFE DW CW nt M
h C C-2 C DM DM Side Side
Fun
ctio
n
TN53TS N N Y Y N N N N N N N Y –
XL
TN54TS N N Y Y N N N N N N N N -
XL
TN52TO N N Y Y N N N N N N eSFP N –
G
NOTE
l "Y" indicates that the OTU supports the function. "N" indicates that the OTU does not support the function
l The SCC board can automatically detect that the eSFP and XFP modules are installed and online. The following information
about the modules can be obtained through a query on the U2000: VendorName, BarCode, and type of optical interface.
l The boards using different FEC codes cannot interconnect with each other.
Table 3-83 Loopback function of OTUs, tributary boards and line boards
LDX Y Y Y Y N
LOA Y Y N Y Y
LOG Y Y Y Y N
LOM Y Y Y Y N
LQG Y Y Y Y N
LQM Y Y Y Y N
LQMD Y Y Y Y N
LQMS Y Y Y Y N
LSC Y Y Y Y N
LSQ Y Y Y Y N
LSX Y Y Y Y N
LSXL Y Y Y Y N
LSXLR N N N N N
LSXR N N N N N
LTX Y Y Y Y N
LWXS Y Y Y Y N
TMX Y Y Y Y N
ND2 N N Y Y Y
NQ2 N N Y Y Y
NS2 N N Y Y Y
NS3 N N Y Y Y
TDX Y Y N N N
TEM28 Y Y N N N
TOA Y Y N N Y
TN11TOM Y Y Y Y N
TN52TOM Y Y Y Y Y
TQM Y Y N N N
TQX Y Y N N N
TSXL Y Y N N N
NOTE
"Y" indicates that the OTU supports the function. "N" indicates that the OTU does not support the function.
FACILITY Loopback
FACILITY Loopback
FACILITY Loopback
Table 3-85 Protection mode of OTUs, tributary boards and line boards
L4G Y Y N Y Y N N N
LDX N N N Y Y N N N
LEM24 N Y N Y Y N N N
LEX4 N Y N Y Y N N N
LOA N N N Y Y N N N
LOG Y N N Y Y N N N
LOM N N N Y Y N N N
LQG Y N N Y Y N N N
LQM Y N N Y Y N N N
LQMD Y N N Y Y N N N
LQMS Y N Y Y N N N Y
LSC N N N Y Y N N N
LSQ N N N Y Y N N N
LSX N N N Y Y N N N
LSXL N N N Y Y N N N
LSXLR N N N N N N N N
LSXR N N N N N N N N
LTX N N N Y Y N N N
LWXS N N N Y N N N N
TMX N N N Y Y N N N
ND2 N N Y N Y N N Y
NQ2 N N Y N Y N N Y
NS2 N N Y N Y N N Y
NS3 N N Y N Y N N Y
TBE Y Y N Y N Y Y N
TDX N N Y Y N N N Y
TEM28 N N Y N N N N N
TOA N N Y Y N N N Y
TOM Y N Y Y Y N N Y
TQM Y N Y Y N N N Y
TQX N N Y Y N N N Y
TSXL N N Y Y N N N Y
TOG N N Y Y N N N N
NOTE
"Y" indicates that the OTU supports the function. "N" indicates that the OTU does not support the function.
For detailed electrical cross-connection functions, refer to Table 3-86, Table 3-87 and Table
3-88.
Table 3-86 Electrical cross-connection of OTUs, tributary boards and line boards in OptiX OSN 8800
LDX N
LOG N
LEM24 N
LEX4 N
LOA N
LOM N
LQM N
LQMD N
LQMS N
LSC N
LSQ N
LSX N
LSXL N
LSXLR N
LSXR N
LTX N
LWXS N
TMX N
TOG 8 x ODU0
TSXL 1 x ODU3
NOTE
Only the TN53TSXL/TN54TSXL supports ODU3
"N" indicates that the OTU does not support the function.
Table 3-87 Electrical cross-connection of OTUs, tributary boards and line boards in OptiX OSN 6800A
Board Name Electrical Cross-Connection
L4G 4 x GE 4 x GE
LDX N N
LEM24 2 x 10GE N
LEX4 2 x 10GE N
LOA N N
LOG 8 x GE 8 x GE
LOM N N
LQG 4 x GE 4 x GE
LSC N N
LSQ N N
LSX N N
LSXL N N
LSXLR N N
LSXR N N
LTX N N
LWXS N N
TMX N N
TBE 16 x GE N
"N" indicates that the OTU does not support the function.
Table 3-88 Electrical cross-connection of OTUs, tributary boards and line boards in OptiX OSN 3800A
Board Name Electrical Cross-Connection
L4G 4 x GE
LDX N
LOA N
LOG 8 x GE
LOM N
LQG 4 x GE
LQM 4 x Any/4 x GE
LQMD 4 x Any/4 x GE
LQMS 4 x Any/4 x GE
LSX N
LSXR N
LWXS N
TMX N
NS2 4 x ODU1
TBE 16 x GE
TOG 4 x ODU1
"N" indicates that the OTU does not support the function.
The power consumption, weight and valid slots of the boards are shown in Table 3-89. The
values listed in the following table indicate the power consumption of the boards when they
normally work at 25°C and 55°C.
Table 3-89 Power consumption, weight and valid slots of the boards
Board Modul Power Weigh Numb Valid Slots
e Type Consumption t (kg/ er of
(W) lb.) Occup
ied
Typica Maxi Slots 8800 8800 8800 6800A 3800A
l 25°C mum T64 T32 T16
(77°F) 55°C
(131°F)
TN11L 3400 50.0 55.0 1.4/3.1 1 N/A N/A N/A IU1- IU2-
4G ps/nm- IU8, IU5
C IU11-
Band- IU16
Fixed
Wavele
ngth-
NRZ-
APD
TN12L 800 ps/ 44.5 51.2 1.6/3.5 1 IU1- IU1- IU1- IU1- IU2-
DX nm-C IU8, IU8, IU18 IU17 IU5,
Band IU11- IU12- IU11
(Odd & IU42, IU27,
Even IU45- IU29-
Wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN-
XFP
TN11L 800 ps/ 31.8 36 1.19/2. 1 IU1- IU1- IU1- IU1- IU2-
OA nm-C 64 IU8, IU8, IU8, IU8, IU5
Band IU11- IU12- IU11- IU11-
(Odd & IU42, IU27, IU18 IU16
Even IU45- IU29-
Wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN-
XFP
10Gbit/
s
Multira
te -
10km-
XFP
10Gbit/
s
Multira
te -
40km-
XFP
TN11L 800 ps/ 40.0 45.0 1.6/3.5 1 IU1- IU1- N/A IU1- IU2-
OG nm-C IU8, IU8, IU8, IU5
Band IU11- IU12- IU11-
(odd & IU42, IU27, IU16
even IU45- IU29-
wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN
800 ps/
nm-C
Band-
Fixed
Wavele
ngth-
NRZ-
PIN
TN12L 800 ps/ 37.0 41.44 1.1/2.4 1 IU1- IU1- IU1- IU1- IU2-
OG nm-C IU8, IU8, IU8, IU8, IU5
Band IU11- IU12- IU11- IU11-
(Odd & IU42, IU27, IU18 IU16
Even IU45- IU29-
Wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN-
XFP
10Gbit/
s
Multira
te
-10km-
XFP
10Gbit/
s
Multira
te
-40km-
XFP
10Gbit/
s
Multira
te
-80km-
XFP
TN11L 800 ps/ 92.7 101.7 2.3/5.1 2 IU1- IU1- N/A IU1- IU3-
OM nm-C IU7, IU7, IU16 IU5
Band IU11- IU12-
(odd & IU17, IU18,
even IU19- IU20-
wavele IU25, IU26,
ngths)- IU27- IU29-
Fixed IU33, IU35
Wavele IU35-
ngth- IU41,
NRZ- IU45-
PIN IU51,
800 ps/ IU53-
nm-C IU59,
Band- IU61-
Fixed IU67
Wavele
ngth-
NRZ-
PIN
TN12L 800 ps/ 61.8 69.2 1.1/2.4 1 IU1- IU1- IU1- IU1- IU2-
OMa nm-C 2 IU8, IU8, IU18 IU17 IU5,
Band IU11- IU12- IU11
(Odd & IU42, IU27,
Even IU45- IU29-
Wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN-
XFP
TN11L 3400 28.4 32.0 1.3/2.9 1 N/A N/A N/A IU1- IU2-
QG ps/nm- IU8, IU5
C IU11-
Band- IU16
Fixed
Wavele
ngth-
NRZ-
APD
TN12L 800 ps/ 30.5 36.6 1.4/3.1 1 IU1- IU1- N/A IU1- IU2-
SX nm-C IU8, IU8, IU17 IU5,
Band IU11- IU12- IU11
(odd & IU42, IU27,
even IU45- IU29-
wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN
800 ps/
nm-C
Band-
Fixed
Wavele
ngth-
NRZ-
PIN
TN13L 800 ps/ 29.4 32.8 1.1/2.4 1 IU1- IU1- IU1- IU1- IU2-
SX nm-C IU8, IU8, IU18 IU17 IU5,
Band- IU11- IU12- IU11
Tunabl IU42, IU27,
e IU45- IU29-
Wavele IU68 IU36
ngth-
NRZ-
PIN
TN12L 500 ps/ 74.0 81.0 3.75/8. 3 IU3- IU3- N/A IU3- N/A
SXL nm-C 27 IU8, IU8, IU17
Band- IU13- IU13-
Tunabl IU18, IU19,
e IU21- IU22-
Wavele IU26, IU27,
ngth- IU29- IU31-
ODB- IU34, IU36
PIN IU37-
IU42,
500 ps/ 84.0 94.0 IU47-
nm-C IU52,
Band- IU55-
Tunabl IU60,
e IU63-
Wavele IU68
ngth-
DQPS
K-PIN
TN15L 60000 140 155 3.8/8.4 IU2- IU2- IU2- IU2- N/A
SXL ps/nm- IU7, IU7, IU7, IU16
C IU12- IU13- IU12-
Band- IU17, IU18, IU17
Tunabl IU20- IU21-
e IU25, IU26,
Wavele IU28- IU30-
ngth- IU33, IU35
ePDM- IU36-
BPSK- IU41,
PIN IU46-
IU51,
IU54-
IU59,
IU62-
IU67
TN11L 800 ps/ 34.8 37.8 1.2/2.6 1 IU1- IU1- N/A IU1- IU2-
SXR nm-C IU8, IU8, IU17 IU5,
Band IU11- IU12- IU11
(odd & IU42, IU27,
even IU45- IU29-
wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN
800 ps/
nm-C
Band-
Fixed
Wavele
ngth-
NRZ-
PIN
TN11N 800 ps/ 61.1 68.4 1.6/3.5 1 N/A N/A N/A IU1- N/A
D2 nm-C IU8,
Band IU11-
(Odd & IU16
Even
Wavele
ngth)-
Fixed
Wavele
ngth-
NRZ-
PIN
TN12N 800 ps/ 57.2 64.0 1.6/3.5 1 N/A N/A N/A IU1- N/A
D2 nm-C IU8,
Band- IU11-
Tunabl IU16
e
Wavele
ngth-
NRZ-
PIN
TN52N 800 ps/ 67.8 74.6 1.4/3.1 1 IU1- IU1- IU1- IU1- N/A
D2 nm-C IU8, IU8, IU8, IU8,
Band- IU11- IU12- IU11- IU11-
Tunabl IU42, IU27, IU18 IU16
e IU45- IU29-
Wavele IU68 IU36
ngth-
(D)RZ-
PIN
800 ps/ 27 30
nm-C
Band-
Tunabl
e
Wavele
ngth-
NRZ-
PIN-
XFP
TN51N 800 ps/ 88.0 95.0 1.6/3.5 1 N/A N/A N/A IU1- N/A
Q2 nm-C IU8,
Band IU11-
(Odd & IU16
Even
Wavele
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN-
XFP
800 ps/
nm-C
Band-
Tunabl
e
Wavele
ngth-
NRZ-
PIN-
XFP
10Gbit/
s
Multira
te
-10km-
XFP
10Gbit/
s
Multira
te
-40km-
XFP
TN52N 800 ps/ 88.0 97.0 2.0/4.4 1 IU1- IU1- IU1- IU1- N/A
Q2 nm-C IU8, IU8, IU8, IU8,
Band IU11- IU12- IU11- IU11-
(Odd & IU42, IU27, IU18 IU16
Even IU45- IU29-
Wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN-
XFP
800 ps/
nm-C
Band-
Tunabl
e
Wavele
ngth-
NRZ-
PIN-
XFP
10Gbit/
s
Multira
te
-10km-
XFP
10Gbit/
s
Multira
te
-40km-
XFP
800 ps/ 49 54
nm-C
Band-
Tunabl
e
Wavele
ngth-
NRZ-
PIN-
XFP
TN54N 800 ps/ 53 58.3 1.6/3.5 1 IU1- IU1- IU1- N/A N/A
Q2 nm-C IU8, IU8, IU8,
Band IU11- IU12- IU11-
(Odd & IU42, IU27, IU18
Even IU45- IU29-
Wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN-
XFP
800 ps/
nm-C
Band-
Tunabl
e
Wavele
ngth-
NRZ-
PIN-
XFP
10Gbit/
s
Multira
te
-10km-
XFP
10Gbit/
s
Multira
te
-40km-
XFP
TN12N 800 ps/ 38.8 43.4 1.2/2.6 1 N/A N/A N/A IU1- IU2-
S2 nm-C 4 IU8, IU5
Band IU11-
(Odd & IU16
Even
Wavele
ngth)-
Fixed
Wavele
ngth-
NRZ-
PIN
TN52N 800 ps/ 51.3 56.4 1.3/2.8 1 IU1- IU1- N/A IU1- IU2-
S2 nm-C 6 IU8, IU8, IU8, IU5
Band- IU11- IU12- IU11-
Tunabl IU42, IU27, IU16
e IU45- IU29-
Wavele IU68 IU36
ngth-
NRZ-
PIN
800 ps/ 21 25
nm-C
Band-
Tunabl
e
Wavele
ngth-
NRZ-
PIN-
XFP
TN11N 500 ps/ 92 101.22. 2.2/4.9 2 N/A N/A N/A IU2- N/A
S3 nm-C 2/4.9 IU8,
Band- IU12-
Tunabl IU16
e
Wavele
ngth-
DQPS
K-PIN
TN52N 500 ps/ 118 130 2.4/5.2 2 IU2- IU2- N/A IU2- N/A
S3 nm-C IU8, IU8, IU8,
Band- IU12- IU13- IU12-
Tunabl IU18, IU19, IU16
e IU20- IU21-
Wavele IU26, IU27,
ngth- IU28- IU30-
DQPS IU34, IU36
K-PIN IU36-
800 ps/ IU42,
nm-C IU46-
Band- IU52,
Tunabl IU54-
e IU60,
Wavele IU62-
ngth- IU68
DQPS
K-PIN
TN54N 800 ps/ 71.0 78.0 1.8/3.9 1 IU1- IU1- IU1- IU1- N/A
S3 nm-C 6 IU8, IU8, IU8, IU8,
Band- IU11- IU12- IU11- IU11-
Tunabl IU42, IU27, IU18 IU16
e IU45- IU29-
Wavele IU68 IU36
ngth-
DQPS
K-PIN
40 62 69
Gbit/s
Multira
te-2 km
TN21A - 50.0 55.0 0.8/1.8 1.5 N/A N/A N/A N/A IU6-
PIU IU8
TN11T 800 ps/ 40.3 44.3 1.4/3.1 1 IU1- IU1- N/A IU1- IU2-
MX nm-C IU8, IU8, IU17 IU5,
Band IU11- IU12- IU11
(odd & IU42, IU27,
even IU45- IU29-
wavele IU68 IU36
ngths)-
Fixed
Wavele
ngth-
NRZ-
PIN
800 ps/
nm-C
Band-
Fixed
Wavele
ngth-
NRZ-
PIN
TN12T 800 ps/ 41.0 45.5 1.2/2.6 1 IU1- IU1- IU1- IU1- IU2-
MX nm-C IU8, IU8, IU18 IU17 IU5,
Band- IU11- IU12- IU11
Tunabl IU42, IU27,
e IU45- IU29-
Wavele IU68 IU36
ngth-
(D)RZ-
PIN
a: When the FC extension function of the TN12LOM board is used, the power consumption of the board increases
by another 2 W.
Table 3-90 Power consumption, weight and valid slots of the OptiX OSN 8800 cross-connect
boards
Board Power Consumption (W) Weig Num Valid Slots
ht ber of
Typic Maxi War War (kg/ Occu 8800 8800 8800
al 25° mum m m lb.) pied T64 T32 T16
C (77° 55°C Back Back Slots
F) (131° up up
F) (25°C, (55°C,
77°F) 131°
F)
TNK2 530- 583- 190 209 3.74 1+1 TNK2 N/A N/A
SXM 3.6 x 3.6 x (8.2) SXM :
+TNK (64- n) (64- n) +3.6 IU10,
2XCT (7.9) IU44
TNK2
XCT :
IU9,
IU43
TNK2 378- 416- 173 190 3.74 1+1 TNK2 N/A N/A
SXM 2.5 x 2.5 x (8.1) SXM :
+TNK (64- n) (64- n) +2.9 IU10,
4XCT (6.3) IU44
TNK4
XCT :
IU9,
IU43
TNK2 630– 693– 169 186 3.7 1+1 Enhan N/A N/A
USXH 7.4 x 8.1 x (8.1) ced:
+TNK (64–n) (64–n) +3.8 TNK2
2UXC (8.4) USXH
T (IU10,
IU44)
/
TNK2
UXCT
(IU9,
IU43)
Gener
al: N/
A
TNK4 324- 356- 114 125 3.0 1+1 TNK4 N/A N/A
SXM 2.5 x 2.5 x (6.6) SXM :
+TNK (64- n) (64- n) +3.6 IU10,
2XCT (7.9) IU44
TNK2
XCT :
IU9,
IU43
TNK4 321- 353- 112 123 2.68 1+1 TNK4 N/A N/A
SXH 2.5 x 2.5 x (5.9) SXH :
+TNK (64-n) (64-n) +3.6 IU10,
2XCT (7.9) IU44
TNK2
XCT :
IU9,
IU43
OptiX OSN 8800 T64/OptiX OSN 8800 T32 Housekeeping Alarm Input/Output and
Control Interfaces
OptiX OSN 8800 T64/OptiX OSN 8800 T32 Housekeeping Alarm Input Interfaces
The TNK2ATE board provides 16 alarm inputs and remote monitoring of alarm signals from
the external systems, such as the environmental monitoring system. Users can configure the
names and severity of the 16 alarm inputs so that the equipment works with external systems to
remotely monitor the external alarms. The alarm signals are forwarded to the EFI1 board after
the TNK2ATE board processes them.
Table 3-91 OptiX OSN 8800 T64/OptiX OSN 8800 T32 housekeeping alarm input interfaces
OptiX OSN 8800 T64/OptiX OSN 8800 T32 Housekeeping Alarm Output and Control
Interfaces
The TNK2STI board provides six alarm output interfaces that are used to send alarms to a
centralized alarm management system. The TNK2STI board also provides two housekeeping
control interfaces for remotely controlling external equipment.
Table 3-92 describes the alarm output and control interfaces.
Table 3-92 OptiX OSN 8800 T64/OptiX OSN 8800 T32 housekeeping alarm output and control
interfaces
Pin Diagram PIN Definition Function
No.
Alarm output A1 CR-V When the system generates
Interfaces
a critical visual alarm, this
STI B1 interface sends the alarm
Clock signals
A B C D signal to the centralized
1 alarm management system.
2
3
4 A2 MJ-V When the system generates
5
6
a major visual alarm, this
7
B2 interface sends the alarm
8
signal to the centralized
alarm management system.
Reserved
Control Interfaces
Interfaces A3 MN-V When the system generates
a minor visual alarm, this
B3 interface sends the alarm
signal to the centralized
alarm management system.
C8 – Reserved
D8 Reserved
NOTE
The C1- C7 and D1- D7 interfaces provide inputs and outputs of clock signals.
OptiX OSN 8800 T16 Housekeeping Alarm Input/Output Interfaces and Control
Interfaces
The TN41ATE board provides 16 alarm inputs and remote monitoring of alarm signals from or
to external systems, such as the environmental monitoring system. Users can configure the names
and severities of the 16 alarm inputs so that the equipment works with external systems to
remotely monitor the external alarms. The alarm signals are forwarded to the EFI1 board after
the ATE processing is complete. The TN41ATE board also provides six alarm output interfaces,
sending alarms to a centralized alarm management system. Further, the TN41ATE board
provides two housekeeping control interfaces to remotely control external equipment.
Table 3-93 describes the alarm input/output and control interfaces.
G8 - Reserved
H8 Reserved
NOTE
The G1-G7 and H1-H7 interfaces provide clock inputs and outputs.
G8 - Reserved
H8 Reserved
NOTE
The G1-G7 and H1-H7 interfaces provide inputs and outputs of clock signals.
1
A X2
X1 ALMI2 View B
1
X3 B
ALMI1 8
View C
X4 C 1
Table 3-95 lists the relationships between connectors and interface types.
X4 ALMI1
X3 ALMI2
NOTE
Connector X2 is an ETH interface. The ETH interface is reserved for future use. Therefore, do not connect a
cable to the ETH interface. Connector X5 is a serial interface.
Network Cable
This section describes the network cable connections and the pin assignments of the straight-
through and crossover cables.
l Figure 3-78 shows the connections of straight-through cables and crossover cables.
Pin8 Pin8
Pin1 Pin1
X1 X2
Straight-through cable
Pin8 Pin8
Pin1 Pin1
X1 X2
Crossover cable
Serial Cable
This section describes the appearance and pin assignment of a serial cable.
l Figure 3-79 shows the appearance of a serial cable for the OptiX OSN 8800/6800A.
Figure 3-79 Appearance of a serial cable for the OptiX OSN 8800/6800A
Pos.1 1
View A
Pos.9
A
1
2
2 View B
W1 1
B
X1 8
X2
Figure 3-80 shows the appearance of a serial cable for the OptiX OSN 3800A
Figure 3-80 Appearance of a serial cable for the OptiX OSN 3800A
View A
Pos.64
1
2
Pos.1 2 View B
A B 1
1
X2 8
W5
W4
X3
X1
W3
X4
W2 View C
350 mm (13.8 in.) 3
3 Pos.9
C
X5
560 mm (22.0 in.) Pos.1
640 mm (25.2 in.)
Table 3-100 lists the relationships between connectors and interface types.
X2 ETH
X3 ALMI2
X4 ALMI1
X5 Serial
NOTE
The ETH interface is reserved for future use. Therefore, do not connect a cable to the ETH interface.
The ALMI1/ALMI2 interface is used for receiving alarms.
l Table 3-101 lists the pin assignment of the serial cable for the OptiX OSN 8800/6800A.
Table 3-101 Pin assignment of the serial cable for the OptiX OSN 8800/6800A
X1.3 X2.2
Table 3-102 lists the pin assignment of the serial cable for the OptiX OSN 3800A.
Table 3-102 Pin assignment of the serial cable for the OptiX OSN 3800A
Connector X1 Connector X4 Relationship
X1.11 X4.2
X1.15 X4.6
X1.19 X4.5
X1.12 X4.8
3.10.2.1 Interfaces
Interfaces
For OptiX OSN 8800/OptiX OSN 6800A, the NM_ETH1/NM_ETH2 interfaces on the
TN51ETH1/TN51ETH2/TN16EFI boards are used for achieving inter-NE communication. The
ETH1, ETH2, and ETH3 interfaces on the TN51ETH2/TN16EFI boards are used to achieve
intra-NE communication. Table 3-103 provides the correct connections of these network
interfaces.
OpitX TN51 EFI1 NM_E RJ4 l Connects the network interface on the
OSN EFI1 TH2 5 equipment through a network cable to that
8800 on an NM server so that the NM can
T64/8 manage the equipment.
NM_ETH2
TN51 EFI2 LAMP RJ4 Controls the power and alarm indicators of
EFI2 1/ 5 the cabinet that holds the subrack with the
LAMP TN51EFI2 board.
LAMP1
ETH1
2 CAUTION
The LAMP interfaces on the TN51EFI2 board
LAMP2
ETH2
OpitX TN16 LAMP RJ4 Controls the PWR indicators and alarm
OSN EFI EFI
1- 5 indicators of the cabinet that holds the
8800 LAMP subrack.
LAMP1
ETH1
SERIAL
T16 2 CAUTION
LAMP2
ETH2
NM_ETH1
NM_ETH2
ETH3
Pin Assignment
Figure 3-81 shows the pin assignment of the RJ45 connector.
8 7 6 5 4 3 2 1
.
1
6
2
7
3
8
4
9
4 NC Not connected
5 NC Not connected
7 NC Not connected
8 NC Not connected
4 NC Not connected
5 NC Not connected
7 NC Not connected
8 NC Not connected
Table 3-108 describes the pin assignment of the LAMP1 and LAMP2 interfaces.
5 GND Ground
6 - Reserved
7 - Reserved
8 GND Ground
DIP switches
Before the board is used, make sure that the setting of the SW1 of TN51EFI1/TN16EFI board
is the same as that shown in Figure 3-83 and Figure 3-84. There is no need to set DIP switches
on the TN51EFI2 board.
NM_ETH2
CPLD ON ON
ON ON
SERIAL ON ON
ON ON
SW1 SW2
U8
SERIAL
T1
NM_ETH2
SW1
SW2
3.10.2.2 Connections
On a network where only OptiX OSN 8800 or OptiX OSN 6800A NEs are used, intra-NE and
inter-NE communication are achieved through fiber connections and network cable connections.
NE Connections
Figure 3-85 and Figure 3-86 show the NE connection scheme. The figure presents connections
between two NEs: NE1 and NE2. Each NE consists of three subracks, one of which is the master
subrack and the other two are slave subracks. The master and slave subracks are connected using
fibers and network cables.
NE1 NE2
Master Subrack (1) EFI2 EFI2
EFI1 Master Subrack (1)
NM_ETH2
LAMP1LAMP2NM_ETH1
LAMP1LAMP2NM_ETH1
SCC SCC
ETH1 ETH2
EFI1/EFI2
ETH1 ETH2
EFI2
OTU OTU
OTU OTU
SERIAL
ETH3
ETH3
OTU OTU
OTU OTU
EFI2
Slave Subrack (2) EFI2 Slave Subrack (2)
LAMP1LAMP2NM_ETH1
LAMP1LAMP2NM_ETH1
ETH1 ETH2
SCC SCC
ETH1 ETH2
Other
EFI2
EFI2
Other
NE NE
FIU SC2 SC2 FIU
ETH3
ETH3
OADM/OA/O Other OADM/OA/O
FIU
FIU
M/OD M/OD
NE
EFI2
Slave Subrack (3) EFI2 Slave Subrack (3)
SCC SCC
ETH1 ETH2
ETH1 ETH2
Other Other
EFI2
EFI2
NE NE
FIU SC2 SC2 FIU
ETH3
ETH3
FIU
M/OD NE M/OD
NE1 NE2
Master Subrack (1) EFI EFI Master Subrack (1)
ETH1 ETH2
XCH XCH
SERIAL
SERIAL
EFI
EFI
OTU OTU
OTU OTU
NM_ETH2
NM_ETH2
ETH3
ETH3
OTU OTU
OTU OTU
ETH1 ETH2
ETH1 ETH2
AUX AUX
SERIAL
SERIAL
Other Other
EFI
EFI
NE NE
FIU SC2 SC2 FIU
NM_ETH2
NM_ETH2
ETH3
ETH3
FIU
M/OD M/OD
NE
ETH1 ETH2
ETH1 ETH2
AUX AUX
SERIAL
SERIAL
Other Other
EFI
EFI
NE NE
FIU SC2 SC2 FIU
NM_ETH2
NM_ETH2
ETH3
ETH3
FIU
M/OD NE M/OD
Inter-NE communication:
l As shown in the figure above, NE1 connects to the NMS through the NM_ETH1 interface
on the EFI2/EFI board in the master subrack using a network cable, enabling the NMS to
manage the two NEs.
l Inside each NE, OTU, OADM/OA/OM/OD, OSC, and FIU boards are properly connected
through fibers. The FIU boards are also connected to other NEs. ESC or OSC channels are
used to achieve inter-NE communication.
l The NM_ETH2 interface on the EFI1/EFI board in the master subrack of one NE is
connected to the NM_ETH1 interface on the EFI2/EFI board inside the master subrack of
the other NE using a network cable, achieving inter-NE communication over Ethernet
channels.
Intra-NE communication:
For each NE, the ETH2 and ETH3 interfaces on the EFI2/EFI board inside the master subrack
are connected to the ETH1 interfaces on the EFI2/EFI boards in the slave subracks to achieve
communication between the subracks.
3.10.3.1 Interfaces
Interfaces
For OptiX OSN 3800A, the NM_ETH1 and NM_ETH2 interfaces of TN22AUX and TN61AUX
boards are used for achieving inter-NE communication. Table 3-110 provides the correct
connections of these network interfaces.
TN2 NM_E RJ l Connects the OptiX OSN 3800A housing the TN22AUX or
2AU STAT
TH1/ 45 TN61AUX board to the U2000 server through a network cable
X/ PROG
NM_E so that the U2000 can manage the OptiX OSN 3800A.
TN6 TH2 l Connects the TN22AUX or TN61AUX board inside one NE to
1AU the NM_ETH1/NM_ETH2 interface on the TN22AUX or
NM_ETH1
AUX
Pin Assignment
Figure 3-87 shows the pin assignment of the RJ45 connector.
8 7 6 5 4 3 2 1
.
Table 3-111 shows the pin assignment of the NM_ETH1 and NM_ETH2 interfaces.
4 NC Not defined
5 NC Not defined
7 NC Not defined
8 NC Not defined
For details about the pin assignment of the serial cable, see 3.10.1 Network Cable and Serial
Cable.
For details about the pin assignment of the ALMI1 and ALMI2 interfaces, see 3.9.3 OptiX OSN
3800A Housekeeping Alarm Interfaces.
Jumper
Before the board is used, make sure that the setting of the J4 jumper of TN22AUX board is the
same as that shown in Figure 3-88. Do not cap other jumpers. There is no need to set jumpers
on the TN61AUX board.
Jumper
Jumper cap
8 (J4)
3.10.3.2 Connections
On a network that uses only OptiX OSN 3800A NEs, communication between the NEs is
achieved through fiber connections and network cable connections.
NE Connections
Figure 3-89 shows the NE connection scheme. The figure presents how two NEs, namely NE1
and NE2, are connected using fibers and network cables.
NE1
STAT
PROG
NM_ETH1 NM_ETH2
SCC
AUX
OTU
EXT
OTU
AUX
NE2
STAT
PROG
SCC
NM_ETH1 NM_ETH2
AUX
Other
NE
FIU SC2
OADM/OA FIU
EXT
AUX
Other Other
NE NE
Inter-NE communication:
l As shown in the figure above, the NEs are connected to the NMS through the NM_ETH1
and NM_ETH2 interfaces on the AUX boards using network cables, enabling the NMS to
manage the two NEs.
l The OTU, OADM/OA, OSC, and FIU boards of the NEs are properly connected through
fibers and the FIU boards are also connected to other NEs. ESC or OSC channels are used
to achieve inter-NE communication.
l The NM_ETH1 and NM_ETH2 interfaces on the AUX boards of the two NEs are connected
using network cables, achieving inter-NE communication over Ethernet channels.
On a hybrid network where OptiX OSN 8800, 6800A, and 3800A NEs are used, the inter-NE
communication and intra-NE communication are achieved through fiber connections and
network cable connections.
Connections
Figure 3-90 shows the NE connection scheme. The figure illustrates how three NEs (namely
NE1, NE2, and NE3) of different types are connected. As shown in the figure, NE1 consists of
a master subrack (OptiX OSN 8800) and two slave subracks (OptiX OSN 8800 T16/6800A);
NE2 and NE3 are two OptiX OSN 3800A NEs.
NE1 NE2
8800 T32/T64 STAT
SCC SCC
LAMP1 LAMP2 NM_ETH1
EFI1/EFI2
ETH1 ETH2
AUX
OTU OTU
OTU OTU
SERIAL
ETH3
OTU OTU
EXT
OTU OTU
Other
EFI
STAT
PROG
NE
FIU SC2
NM_ETH1 NM_ETH2
SCC
NM_ETH2
AUX
Other
ETH3
OADM/OA/ Other NE
SC2 FIU
FIU
OM/OD NE
EFI2
Slave Subrack (3)
LAMP1 LAMP2 NM_ETH1
SCC
ETH1 ETH2
Other AUX
EFI2
NE
FIU SC2
Other NE
ETH3
OADM/OA/ Other
FIU
OM/OD NE
Inter-NE communication:
l As shown in the figure above, NE1 connects to the NMS through the NM_ETH1 interface
on the EFI2 board in the master subrack using a network cable, enabling the NMS to manage
all the NEs.
l The OTU, OADM/OA/OM/OD, OSC, and FIU boards inside NE1 are connected through
fibers. The FIU boards are also connected to other NEs. ESC or OSC channels are used to
achieve inter-NE communication.
l NE2 and NE3 are connected through their OTU, OADM/OA, OSC, and FIU boards using
fibers. The FIU boards of the two NEs are also connected to other NEs. ESC or OSC
channels are used to achieve inter-NE communication.
l The NM_ETH2 interface on the EFI1 board of the master subrack inside NE1 connects to
the NM_ETH1 interface on the AUX board inside NE2 through a network cable. The
NM_ETH2 interface on the AUX board inside NE2 also uses a network cable to connect
to the NM_ETH1 interface on the AUX board inside NE3. In this manner, all the NEs
communicate with each other using Ethernet channels.
Intra-NE communication:
For NE1, the ETH2 and ETH3 interfaces on the EFI2 board inside the master subrack are
connected to the ETH1 interfaces on the EFI2/EFI boards in the slave subracks to achieve
communication between the subracks.
4 Node Configurations
4.1.1 OTM
Configuration Principle
Configuration principle for an optical multiplexer unit and demultiplexer unit:
l For an 80-wavelength OTM node, ITL boards must be configured if the M40V/M40/D40
boards are used for adding/dropping wavelengths.
Configuration principle for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
Configuration principle for a spectrum analyzer unit:
l When WMU and MCA4/MCA8/OPM8 boards are required for an OTM node, configure
WMU boards prior to MCA4/MCA8/OPM8 boards.
l When only MCA4/MCA8/OPM8 boards are required for an OTM node, configure MCA4
boards prior to MCA8/OPM8 boards.
l It is recommended that you connect an MCA4/MCA8/OPM8 board to the MON port on
an optical amplifier board or the MON port on an FIU board.
Configuration principle for an optical supervisory channel unit:
l For an 80-wavelength OTM node, one SC1 board can be configured.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-2 shows the typical configuration for the optical layer of an 80-wavelength OTM node.
As shown in the figures, this configuration requires two subracks in total.
Figure 4-2 Typical configurations for the optical layer of an 80-wavelength OTM node
20
A
O O
U
A A M
F S I S S X
U U C
I C T C C
1 1 A
U 1 L C C
0 0 4
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
RM VI VI RO
TE
RE
The signal flow of the transmit direction is the reverse process of the receive direction.
Figure 4-4 shows the signal flow of an 80-wavelength back-to-back OTM node.
Configuration Principle
Configuration principle for an optical multiplexer unit and demultiplexer unit:
l For an 80-wavelength back-to-back OTM node, ITL boards must be configured if the
M40V/M40/D40 boards are used for adding/dropping wavelengths.
Configuration principle for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
Configuration principle for a spectrum analyzer unit:
l When WMU and MCA4/MCA8/OPM8 boards are required for an OTM node, configure
WMU boards prior to MCA4/MCA8/OPM8 boards.
l When only MCA4/MCA8/OPM8 boards are required for an OTM node, configure MCA4
boards prior to MCA8/OPM8 boards.
l It is preferred to connect an MCA4/MCA8/OPM8 board to the MON port on an optical
amplifier board or the MON port on an FIU board.
Configuration principle for an optical supervisory channel unit:
l For an 80-wavelength back-to-back OTM node, two SC1 or one SC2 can be configured.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-5 and Figure 4-6 show the typical configuration for the optical layer of a back-to-back
OTM node. As shown in the figures, this configuration requires four subracks in total.
Figure 4-5 Typical configurations for the optical layer of a back-to-back OTM node (westbound)
20
A
O O
U
A A M
F S I S S X
U U C
I C T C C
1 1 A
U 2 L C C
0 0 4
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-6 Typical configurations for the optical layer of a back-to-back OTM node (eastbound)
20
A
O O
U
A A
F I S X
U U
I T C
1 1
U L C
0 0
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-7 Subrack fiber connections for an 80-wavelength back-to-back OTM node
Configuration Principle
Configuration principles for a reconfigurable optical add and drop multiplexing unit:
l One WSMD2 board, or WSMD4 board, or one combination of WSD9+WSM9 board, or
one combination of RDU9+WSM9 board, or one WSMD9 board must be used.
l If the node needs to be upgraded to a 2-, 3-, or 4-degree node, the WSMD4 boards are
recommended.
l If the node needs to be upgraded to more than four degrees, the combinations of RDU9
+WSM9 boards or combinations of WSD9+WSM9 boards or the WSMD9 boards are
recommended.
Configuration principle for an optical multiplexer unit and demultiplexer unit:
l For an 80-wavelength ROADM node, ITL boards must be configured if the M40V/M40/
D40 boards are used for adding/dropping wavelengths.
Configuration principles for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
l When WSDM4/WSMD9 boards are used, it is recommended that optical amplifier boards
be configured in wavelength-dropping directions.
l If optical amplifier boards need to be used in wavelength-adding directions, low-power
optical amplifiers are recommended.
Configuration principles for a spectrum analyzer unit:
l For a 1-degree ROADM node:
– When WMU and MCA4/MCA8/OPM8 boards are required for an OTM node, configure
WMU boards before you configure MCA4/MCA8/OPM8 boards.
– When only MCA4/MCA8/OPM8 boards are required for an ROADM node, configure
MCA4 boards before you configure MCA8/OPM8 boards.
– It is recommended that you connect an MCA4/MCA8/OPM8 board to the MON port
on an optical amplifier board or the MON port on an FIU board.
l Automatic deployment:
– MCA4/MCA8/OPM8 boards must be configured for automatic deployment. If OSNR
detection for 10 Gbit/s rates is not required, configure OPM8 boards before you
configure MCA4/MCA8 boards.
– An MCA4/MCA8/OPM8 board must be configured for remote power commissioning
and must be connected to the MON port on the OA board that is connected to an FIU
board.
– When there are five or more fiber spans between two power equalization sites, an
MCA4/MCA8/OPM8 board must be configured in the middle of the spans (spans/2
±0.5), in both the transmit and receive directions.
– When there are four or fewer fiber spans between two power equalization sites, an
MCA4/MCA8/OPM8 board must be configured at the transmit end.
Configuration principle for an optical supervisory channel unit:
l The optical supervisory unit is required in each direction of an ROADM node. For a 1-
degree ROADM node, one SC1 board can be configured.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-9 shows the typical configuration for the optical layer of a 1-degree 80-wavelength
ROADM node that uses one WSMD4 boards. As shown in the figures, this configuration requires
two subracks in total.
Figure 4-9 Typical configurations for the optical layer of a 1-degree 80-wavelength ROADM
node
20
A
O O O O
W U
A A B B M
F S S I S S X
U U U U C
I C M T C C
1 1 1 1 A
U 1 D L C C
0 0 0 0 4
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-10 Subrack fiber connections for a 1-degree 80-wavelength ROADM node
AM2 TE
DM3 RE
AM3
DM4
AM4
The 2-degree ROADM node consists of two WSMD4s. The signal grooming of the west
WSMD4 is used for the following example. The signal grooming of the east WSMD4 is the
same as that of the west WSMD4.
The signal flow of the transmit direction is the reverse process of the receive direction.
Configuration Principle
Configuration principles for a reconfigurable optical add and drop multiplexing unit:
l Two WSMD2 board, or two WSMD4 board, or two combinations of WSD9+WSM9
boards, or two combinations of RDU9+WSM9 boards, or two WSMD9 boards must be
used.
l If the node needs to be upgraded to a 3- or 4-degree node, the WSMD4 boards are
recommended.
l If the node needs to be upgraded to more than four degrees, combinations of RDU9+WSM9
boards or combinations of WSD9+WSM9 boards or the WSMD9 boards are recommended.
l The optical supervisory unit is required in each direction of an ROADM node. For a 2-
degree ROADM node, configure two SC1 or one SC2 boards.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-12 and Figure 4-13 show the typical configurations for the optical layer of a 2-degree
80-wavelength ROADM node that uses two WSMD4 boards. As shown in the figures, this
configuration requires four subracks in total.
Figure 4-12 Typical configurations for the optical layer of a 2-degree 80-wavelength ROADM
node (westbound)
20
A
O O O O
W U
A A B B M
F S S I S S X
U U U U C
I C M T C C
1 1 1 1 A
U 2 D L C C
0 0 0 0 4
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-13 Typical configurations for the optical layer of a 2-degree 80-wavelength ROADM
node (eastbound)
20
A
O O O O
W U
A A B B M
F S S I S S X
U U U U C
I C M T C C
1 1 1 1 A
U 1 D L C C
0 0 0 0 8
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-14 Subrack fiber connections for a 2-degree 80-wavelength ROADM node
The 3-degree ROADM node consists of three WSMD4 boards. The signal grooming of the west
WSMD4 board is used as an example. The signal grooming of the east and south WSMD4 boards
are the same as that of the west WSMD4 board.
In the receive direction:
l The optical supervisory signals and the main-path optical signals are separated from the
line signals received from west. The optical supervisory signals are sent to the optical
supervisory unit for processing, and the main-path optical signals are sent to the WSMD4
board after being amplified.
l The WSMD4 board splits the main-path optical signals into three equal optical signals.
– One optical signal is sent to the ITL board and split into two multiplexed wavelength
signals (odd wavelength and even wavelength) with frequency spacing of 100 GHz.
Then the two optical signals are locally dropped through two demultiplexer boards.
– The other two optical signals each pass through the east and south WSMD4 boards.
The signal flow of the transmit direction is the reverse process of the receive direction.
Figure 4-15 shows the signal flow of 3-degree ROADM.
Tributary Tributary
Units Units
OD OM OD OM
C-ODD C-ODD C-EVEN C-EVEN
ITL
OA OA
OA
F
WSMD4 I
South
U
OA
West East
OA OA
F F
I WSMD4 WSMD4 I
U U
OA OA
OA OA OA
OA
ITL ITL
OM OD OM OD OM OD OM OD
C-EVEN C-EVEN C-ODD C-ODD C-EVEN C-EVEN C-ODD C-ODD
Configuration Principle
Configuration principles for a reconfigurable optical add and drop multiplexing unit:
l Three WSMD4 boards, or three combinations of WSD9+WSM9 boards, or three
combinations of RDU9+WSM9 boards, or three WSMD9 boards must be used.
l If the node needs to be upgraded to four degrees, the WSMD4 boards are recommended.
l If the node needs to be upgraded to more than four degrees, the combinations of RDU9
+WSM9 boards or combinations of WSD9+WSM9 boards or the WSMD9 boards are
recommended.
Configuration principle for an optical multiplexer unit and demultiplexer unit:
l For an 80-wavelength ROADM node, ITL boards must be configured if the M40V/M40/
D40 boards are used for adding/dropping wavelengths.
Configuration principles for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
l When WSDM4/WSMD9 boards are used, it is recommended that optical amplifier boards
be configured in wavelength-dropping directions.
l If optical amplifier boards need to be used in wavelength-adding directions, low-power
optical amplifiers are recommended.
Configuration principle for a spectrum analyzer unit:
l For a 3-degree ROADM node:
– When WMU and MCA4/MCA8/OPM8 boards are required for an OTM node, configure
WMU boards before you configure MCA4/MCA8/OPM8 boards.
– When only MCA4/MCA8/OPM8 boards are required for an ROADM node, configure
MCA8/OPM8 boards before you configure MCA4 boards.
– It is recommended that you connect an MCA4/MCA8/OPM8 board to the MON port
on an optical amplifier board or the MON port on an FIU board.
l Automatic deployment:
– MCA4/MCA8/OPM8 boards must be configured for automatic deployment. If OSNR
detection for 10 Gbit/s rates is not required, configure OPM8 boards before your
configure MCA4/MCA8 boards..
– An MCA4/MCA8/OPM8 board must be configured for remote power commissioning
and must be connected to the MON port on the OA board that is connected to an FIU
board.
– When there are five or more fiber spans between two power equalization sites, an
MCA4/MCA8/OPM8 board must be configured in the middle of the spans (spans/2
±0.5), in both the transmit and receive directions.
– When there are four or fewer fiber spans between two power equalization sites, an
MCA4/MCA8/OPM8 board must be configured at the transmit end.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-16 and Figure 4-17 show the typical configurations for the optical layer of a 3-degree
80-wavelength ROADM node that uses three WSMD4 boards. As shown in the figures, this
configuration requires six subracks in total.
Figure 4-16 Typical configurations for the optical layer of a 3-degree 80-wavelength ROADM
node (westbound)
20
A
O O O O
W U
A A B B M
F S S I S S X
U U U U C
I C M T C C
1 1 1 1 A
U 2 D L C C
0 0 0 0 8
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-17 Typical configurations for the optical layer of a 3-degree 80-wavelength ROADM
node (eastbound/southbound)
20
A
O O O O
W U
A A B B
F S S I S X
U U U U
I C M T C
1 1 1 1
U 1 D L C
0 0 0 0
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-18 Subrack fiber connections for a 3-degree 80-wavelength ROADM node
OD OM OD OM OD OM OD OM
C-ODD C-ODD C-EVEN C-EVEN C-ODD C-ODD C-EVEN C-EVEN
ITL ITL
OA OA OA OA
OA OA
F F
North I WSMD4 WSMD4
I South
U (north) (south)
U
OA OA
OA OA
F F
WSMD4 WSMD4
West I I East
(west) (east)
U U
OA OA
OA OA OA OA
ITL ITL
OM OD OM OD OM OD OM OD
C-EVEN C-EVEN C-ODD C-ODD C-EVEN C-EVEN C-ODD C-ODD
Pass-through
signal
Configuration Principle
Configuration principles for a reconfigurable optical add and drop multiplexing unit:
l Four WSMD4 boards, a combination of WSD9 and WSM9 boards, or a combination of
RDU9 and WSM9 boards, or four WSMD9 boards must be used.
l If the node needs to be upgraded to more than four degrees, a combination of RDU9 and
WSM9 boards or a combination of WSD9 and WSM9 boards or the WSMD9 boards is
recommended.
l The optical supervisory unit is required in each direction of an ROADM node. For a 4-
degree ROADM node, you can four SC1 or two SC2 boards.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-20 and Figure 4-21 show the typical configurations for the optical layer of a 4-degree
80-wavelength ROADM node that uses four WSMD4 boards. As shown in the figures, this
configuration requires eight subracks.
Figure 4-20 Typical configurations for the optical layer of a 4-degree 80-wavelength ROADM
node (westbound)
20
A
O O O O
W U
A A B B M
F S S I S S X
U U U U C
I C M T C C
1 1 1 1 A
U 2 D L C C
0 0 0 0 8
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-21 Typical configurations for the optical layer of a 4-degree 80-wavelength ROADM
node (eastbound/southbound/northbound)
20
A
O O O O
W U
A A B B
F S S I S X
U U U U
I C M T C
1 1 1 1
U 2 D L C
0 0 0 0
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-22 Subrack fiber connections for a 4-degree 80-wavelength ROADM node
The signal flow of the REG is similar to that of back-to-back OTMs, except that no signal is
added or dropped. Signals are regenerated through the OTU or line unit. The REG node is
responsible for processing the optical signals in two transmission directions.
Configuration Principle
Configuration principle for an optical multiplexer unit and demultiplexer unit:
l For an 80-wavelength REG node, ITL boards must be configured if the M40V/M40/D40
boards are used for adding/dropping wavelengths.
Configuration principle for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
Configuration principles for a spectrum analyzer unit:
l When WMU and MCA4/MCA8/OPM8 boards are required for an REG node, configure
WMU boards prior to MCA4/MCA8/OPM8 boards.
l When only MCA4/MCA8/OPM8 boards are required for an REG node, configure MCA4
boards prior to MCA8/OPM8 boards.
l It is recommended that you connect an MCA4/MCA8/OPM8 board to the MON port on
an optical amplifier board or the MON port on an FIU board.
Configuration principle for an optical supervisory channel unit:
l For an 80-wavelength REG node, you can configure two SC1 boards or one SC2 board.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-24 and Figure 4-25 show the typical configuration for the optical layer of an 80-
wavelength REG node. As shown in the figures, this configuration requires four subracks.
Figure 4-24 Typical configurations for the optical layer of an 80-wavelength REG node
(westbound)
20
A
O O
U
A A M
F S I S S X
U U C
I C T C C
1 1 A
U 2 L C C
0 0 4
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-25 Typical configurations for the optical layer of an 80-wavelength REG node
(eastbound)
20
A
O O
U
A A
F S I S X
U U
I C T C
1 1
U 1 L C
0 0
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M M D D
S X
4 4 4 4
C
0 0 0 0
C
E O E O
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
4.2.1 OTM
F
I
SC1
U
Configuration Principle
Configuration principle for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-28 shows the typical configuration for the optical layer of a 40-wavelength OTM node.
As shown in the figures, this configuration requires two subracks.
Figure 4-28 Typical configurations for the optical layer of a 40-wavelength OTM node
20
A
O O
U
A A M
F S S S X
U U C
I C C C
1 1 A
U 1 C C
0 0 4
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-29 shows the subrack fiber connections for the optical layer of a 40-wavelength OTM
node.
TM VO VO
RM VI VI
Shelf2-IU1 Shelf2-IU15
M40 D40
MON MON
OUT IN
M01 D01
M40 D40
West East
OD O Client- O OM
OA side OA
T T
F F
U services U
I I
U U
O Client- O
T side T
OA OM OD OA
U services U
Configuration Principle
Configuration principle for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-31 and Figure 4-32 show the typical configuration for the optical layer of a 40-
wavelength back-to-back OTM node. As shown in the figures, this configuration requires four
subracks in total.
Figure 4-31 Typical configurations for the optical layer of a 40-wavelength back-to-back OTM
node (westbound)
20
A
O O
U
A A M
F S S S X
U U C
I C C C
1 1 A
U 2 C C
0 0 4
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-32 Typical configurations for the optical layer of a 40-wavelength back-to-back OTM
node (eastbound)
20
A
O O
U
A A
F S S S X
U U
I C C C
1 1
U 1 C C
0 0
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-33 Subrack fiber connections for a 40-wavelength back-to-back OTM node
TM TM2 VO VO
RM VI VI
RM2
Shelf2-IU1 Shelf2-IU15
M40 D40
MON MON
OUT IN
M01 D01
M40 D40
OA
F
I SC1 WSMD4
West U
OA
OA OA
OM OD
Line Units
Tributary
Units
Client-side
services
West signal
Configuration Principle
Configuration principle for a reconfigurable optical add and drop multiplexing unit:
l One WSMD2 board, or one WSMD4 board, or one combination of WSD9+WSM9 board,
or one combination of RDU9+WSM9 board, or one WSMD9 board must be used.
l If the node needs to be upgraded to a 2-degree node, WSMD2 boards are recommended.
l If the node needs to be upgraded to a 3-, or 4-degree node, WSMD4 boards are
recommended.
l If the node needs to be upgraded to more than four degrees, combinations of RDU9+WSM9
boards or combinations of WSD9+WSM9 boards or the WSMD9 boards are recommended.
l The optical supervisory unit is required in each direction of an ROADM node. For a 1-
degree ROADM node, one SC1 board can be configured.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-35 show the typical configuration for the optical layer of a 1-degree 40-wavelength
ROADM node that uses one WSMD4 boards. As shown in the figures, this configuration requires
two subracks.
Figure 4-35 Typical configurations for the optical layer of a 1-degree 40-wavelength ROADM
node
20
A
O O O O
W U
A A B B M
F S S S S X
U U U U C
I C M C C
1 1 1 1 A
U 1 D C C
0 0 0 0 4
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-36 Subrack fiber connections for a 1-degree 40-wavelength ROADM node
Shelf2-IU1 Shelf2-IU15
M40 D40
MON MON
OUT IN
M01 D01
M40 D40
The signal flow of the transmit direction is the reverse process of the receive direction.
SC2
F F
OA OA
I I
U U
West WSMD4 WSMD4 East
OA OA
OA OA OA OA
OM OD OM OD
Tributary Tributary
Units Units
Client-side Client-side
services services
Configuration Principle
Configuration principles for a reconfigurable optical add and drop multiplexing unit:
l Two WSMD2 boards, two WSMD4 boards, a combination of two WSD9 and two WSM9
boards, or a combination of two RDU9 and two WSM9 boards, or two WSMD9 boards
must be used.
l If the node needs to be upgraded to a 3-, or 4-degree node, the WSMD4 boards are
recommended.
l If the node needs to be upgraded to more than four degrees, the combinations of RDU9
+WSM9 boards or combinations of WSD9+WSM9 boards or the WSMD9 boards are
recommended.
Configuration principles for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
l When WSMD2 boards are used, no optical amplifier boards are required in the wavelength-
adding or wavelength-dropping directions.
l When WSDM4/WSMD9 boards are used, it is recommended that you configure optical
amplifier boards in wavelength-dropping directions.
l If optical amplifier boards need to be used in wavelength-adding directions, low-power
optical amplifiers are recommended.
Configuration principles for a spectrum analyzer unit:
l For a 2-degree ROADM node:
– When only MCA4/MCA8/OPM8 boards are required for an ROADM node, configure
MCA4 boards before your configure MCA8/OPM8 boards.
– It is recommended that you connect an MCA4/MCA8/OPM8 board to the MON port
on an optical amplifier board or the MON port on an FIU board.
l Automatic deployment:
– MCA4/MCA8/OPM8 boards must be configured for automatic deployment. If OSNR
detection for 10 Gbit/s rates is not required, configure OPM8 boards before your
configure MCA4/MCA8 boards.
– An MCA4/MCA8/OPM8 board must be configured for remote power commissioning
and must be connected to the MON port on the OA board that is connected to an FIU
board.
– When there are five or more fiber spans between two power equalization sites, an
MCA4/MCA8/OPM8 board must be configured in the middle of the spans (spans/2
±0.5), in both the transmit and receive directions.
– When there are four or fewer fiber spans between two power equalization sites, an
MCA4/MCA8/OPM8 board must be configured at the transmit end.
Configuration principle for an optical supervisory channel unit:
l The optical supervisory unit is required in each direction of an ROADM node. For a 2-
degree ROADM node, one SC2 or two SC1 boards can be configured.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-38 and Figure 4-39 show the typical configurations for the optical layer of a 2-degree
40-wavelength ROADM node that uses two WSMD4 boards. As shown in the figures, this
configuration requires four subracks.
Figure 4-38 Typical configurations for the optical layer of a 2-degree 40-wavelength ROADM
node (westbound)
20
A
O O O O
W U
A A B B M
F S S S S X
U U U U C
I C M C C
1 1 1 1 A
U 2 D C C
0 0 0 0 4
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-39 Typical configurations for the optical layer of a 2-degree 40-wavelength ROADM
node (eastbound)
20
A
O O O O
W U
A A B B M
F S S S S X
U U U U C
I C M C C
1 1 1 1 A
U 2 D C C
0 0 0 0 4
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-40 Subrack fiber connections for a 2-degree 40-wavelength ROADM node
Shelf2-IU1 Shelf2-IU15
M40 D40
MON MON
OUT IN
M01 D01
M40 D40
Client services
Tributary
Units
Line Units
OD OM
OA OA
OA
F
WSMD4 I
South
U
OA
West East
OA OA
F F
I WSMD4 WSMD4 I
U U
OA OA
OA OA OA
OA
OM OD OM OD
Tributary Tributary
Units Units
Configuration Principle
Configuration principle for a reconfigurable optical add and drop multiplexing unit:
l Three WSMD4 boards, a combination of three WSD9 and three WSM9 boards, or a
combination of three RDU9 and three WSM9 boards, or three WSMD9 boards must be
used.
l If the node needs to be upgraded to four degrees, the WSMD4 boards are recommended.
l If the node needs to be upgraded to more than four degrees, combinations of RDU9+WSM9
boards or combinations of WSD9+WSM9 boards or the WSMD9 boards are recommended.
Configuration principles for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
l When WSDM4/WSMD9 boards are used, it is recommended that you configure optical
amplifier boards in wavelength-dropping directions.
l If optical amplifier boards need to be used in wavelength-adding directions, low-power
optical amplifiers are recommended.
Configuration principles for a spectrum analyzer unit:
l For a 3-degree ROADM node:
– When only MCA4/MCA8/OPM8 boards are required for an ROADM node, configure
MCA8/OPM8 boards before you configure MCA4 boards.
– It is recommended that you connect an MCA4/MCA8/OPM8 board to the MON port
on an optical amplifier board or the MON port on an FIU board.
l Automatic deployment:
– MCA4/MCA8/OPM8 boards must be configured for automatic deployment. If OSNR
detection for 10 Gbit/s rates is not required, configure OPM8 boards before your
configure MCA4/MCA8 boards.
– An MCA4/MCA8/OPM8 board must be configured for remote power commissioning
and must be connected to the MON port on the OA board that is connected to an FIU
board.
– When there are five or more fiber spans between two power equalization site, an MCA4/
MCA8/OPM8 board must be configured in the middle of the spans (spans/2±0.5), in
both the transmit and receive directions.
– When there are four or fewer fiber spans between two power equalization site, an
MCA4/MCA8/OPM8 board must be configured at the transmit end.
Configuration principle for an optical supervisory channel unit:
l The optical supervisory unit is required in each direction of an ROADM node. For a 3-
degree ROADM node, three SC1 or one SC2 plus one SC1 board can be configured.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-42 and Figure 4-43 show the typical configurations for the optical layer of a 3-degree
80-wavelength ROADM node that uses three WSMD4 boards. As shown in the figures, this
configuration requires six subracks in total.
Figure 4-42 Typical configurations for the optical layer of a 3-degree 40-wavelength ROADM
node (westbound)
20
A
O O O O
W U
A A B B M
F S S S S X
U U U U C
I C M C C
1 1 1 1 A
U 2 D C C
0 0 0 0 8
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-43 Typical configurations for the optical layer of a 3-degree 40-wavelength ROADM
node (eastbound/southbound)
20
A
O O O O
W U
A A B B
F S S S X
U U U U
I C M C
1 1 1 1
U 1 D C
0 0 0 0
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-44 Subrack fiber connections for a 3-degree 40-wavelength ROADM node
Shelf2-IU1 Shelf2-IU15
M40 D40
MON MON
OUT IN
M01 D01
M40 D40
Tributary Tributary
Units Units
OD OM OD OM
OA OA OA OA
OA OA
F F
North I WSMD4 WSMD4
I South
U (north) (south)
U
OA OA
OA OA
F F
WSMD4 WSMD4
West I I East
(west) (east)
U U
OA OA
OA OA OA OA
OM OD OM OD
Tributary Tributary
Units Units
Pass-through
signal
Configuration Principle
Configuration principles for a reconfigurable optical add and drop multiplexing unit:
l Four WSMD4 board, a combination of four WSD9 and four WSM9 boards, or a
combination of four RDU9 and four WSM9 boards, or four WSMD9 boards must be used.
l If the node needs to be upgraded to more than four degrees, combinations of RDU9+WSM9
boards or combinations of WSD9+WSM9 boards or the WSMD9 boards are recommended.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-46 and Figure 4-47 show the typical configurations for the optical layer of a 4-degree
80-wavelength ROADM node that uses four WSMD4 boards. As shown in the figures, this
configuration requires eight subracks in total.
Figure 4-46 Typical configurations for the optical layer of a 4-degree 40-wavelength ROADM
node (westbound)
20
A
O O O O
W U
A A B B M
F S S S S X
U U U U C
I C M C C
1 1 1 1 A
U 2 D C C
0 0 0 0 8
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-47 Typical configurations for the optical layer of a 4-degree 40-wavelength ROADM
node (eastbound/southbound/northbound)
20
A
O O O O
W U
A A B B M
F S S S S X
U U U U C
I C M C C
1 1 1 1 A
U 2 D C C
0 0 0 0 8
4 A
1 3 1 4
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-48 Subrack fiber connections for a 4-degree 40-wavelength ROADM node
Shelf2-IU1 Shelf2-IU15
M40 D40
MON MON
OUT IN
M01 D01
M40 D40
01
OA OD OM OA
West n East
F F
I I
U U
01
OA OM OD OA
n
Configuration Principle
Configuration principle for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
Configuration principle for a spectrum analyzer unit:
l When only MCA4/MCA8/OPM8 boards are required for an REG node, configure MCA4
boards before you configure MCA8/OPM8 boards.
l It is recommended that you connect an MCA4/MCA8/OPM8 board to the MON port on
an optical amplifier board or the MON port on an FIU board.
Configuration principle for an optical supervisory channel unit:
l For a 40-wavelength REG node, you can configure two SC1 boards or one SC2 board.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-50 and Figure 4-51 show the typical configuration for the optical layer of a 40-
wavelength REG node. As shown in the figures, this configuration requires four subracks in
total.
Figure 4-50 Typical configurations for the optical layer of a 40-wavelength REG node
(westbound)
20
A
O O
U
A A M
F S S S X
U U C
I C C C
1 1 A
U 2 C C
0 0 4
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-51 Typical configurations for the optical layer of a 40-wavelength REG node
(eastbound)
20
A
O O
U
A A
F S S S X
U U
I C C C
1 1
U 1 C C
0 0
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20
A
U
M D S X
4 4 C
0 0 C
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
TM VO VO
TM2
RM VI VI
RM2
Shelf2-IU1 Shelf2-IU15
M40 D40
MON MON
OUT IN
M01 D01
M40 D40
4.3 OLA
The FIU board separates the optical supervisory signal from the main path optical signals and
sends the former to the OSC unit for processing. The main path optical signals are amplified by
the amplifier unit and multiplexed with the OSC that has already been processed, and then sent
to the line fiber for transmission.
OA
West East
F F
I SC2 I
U U
OA
Configuration Principle
Configuration principle for an optical amplifier unit:
l Optical amplifier boards must be configured according to the power budget for actual
situations.
l For an 80-wavelength OLA node, when WMU or MCA4/MCA8/OPM8 boards are required
for an OLA node, configure WMU boards before you configure MCA4/MCA8/OPM8
boards.
l When only MCA4/MCA8/OPM8 boards are required for an OLA node, configure MCA4
boards before you configure MCA8/OPM8 boards
l It is recommended that you connect an MCA4/MCA8/OPM8 board to the MON port on
an optical amplifier board or the MON port on an FIU board.
Configuration principle for an optical supervisory channel unit:
l For an OLA node, you can configure two SC1 or one SC2 board.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-54 shows the typical configuration for the optical layer of an OLA node. As shown in
the figures, this configuration requires only one subrack in total.
Figure 4-54 Typical configurations for the optical layer of an OLA node
20
A
O O
U
A A M
F S F S S X
U U C
I C I C C
1 1 A
U 2 U C C
0 0 4
1 3 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
TM VO VO TM
TM2
RM VI VI RM
RM2
l Finally, the signals are multiplexed with the processed optical supervisory signals for line
transmission.
Configuration Principle
Configuration principle for an OADM unit:
l If a DMR1 board is used, and the transmission distance is short, the FIU board cannot be
used.
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-57 and Figure 4-58 show the typical configurations for the optical layer of a FOADM
node that uses two MR4 boards. As shown in the figures, this configuration requires two subracks
in total.
Figure 4-57 Typical configurations for the optical layer of a FOADM node (westbound)
20
A
O O
U
A B
F S M S S X
U U
I C R C C
1 1
U 2 4 C C
0 0
1 1 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-58 Typical configurations for the optical layer of a FOADM node (eastbound)
20
A
O O
U
A B
F M S S X
U U
I R C C
1 1
U 4 C C
0 0
1 1 A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
TC OUT OUT MO
TM1
IN IN MI
RC RM1
D1
TM TM2 VO VO
A1
RM RM2 VI VI D2
A2
D3
A3
D4
A4
Figure 4-60 uses a FOADM node as an example to illustrate how fibers are connected for the
optical subrack of the node.
4.5 PID
For the image above for the PID board group, different PID groups provide different service
access capacities. Currently, three PID groups are available for a 40G to 200G service access
capacity.
l NPO2 or NPO2E: providing a 40G/80G service access capacity
l NPO2+ENQ2 or NPO2E+ENQ2: providing a 120G service access capacity
l NPO2E+ENQ2+NPO2: providing a 160G/200G service access capacity
80G l TN55NPO2+TN54PQ2
system l TN55NPO2E Tribut
TN55 TN55
Tribut
NPO2( NPO2(
ary/ ary/
+TN54PQ2 line
E)+
TN54
E)+
TN54
line
board board
PQ2 PQ2
120G l TN55NPO2+TN54PQ2
system +TN54ENQ2
TN55 TN55
l TN55NPO2E Tributary/
NPO2(E)
+
NPO2(E)
+
Tributary/
line board
line board
+TN54PQ2 TN54
TN54
PQ2
TN54
PQ2 TN54
160G TN55NPO2E+TN54PQ2
system +TN54ENQ2+TN55NPO2
(not configured with
TN54PQ2)
TN54 TN55 TN55 TN54
Tributary/ ENQ2 NPO2E NPO2E ENQ2 Tributary/
line board + + line board
TN54 TN54
PQ2 PQ2
TN55 TN55
NPO2 NPO2
200G TN55NPO2E+TN54PQ2
system +TN54ENQ2+TN55NPO2
+TN54PQ2
TN54 TN55 TN55 TN54
ENQ2 NPO2E NPO2E ENQ2 Tributary/
Tributary/ + + line board
line board TN54 TN54
PQ2 PQ2
TN55 TN55
NPO2 NPO2
+ +
TN54 TN54
PQ2 PQ2
19 20 21 22 23 24
X X
N N
E N C C E N
P T T T P T T
N P H H N P
O O O O O D D
Q O Q O
2 M M M 2 X X
2 2 2 2
E E
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
NOTE
In a subrack, the PID boards in slots 1-3 serve the west direction and those in slots 11-13 serve the east direction.
TO2 TO2
TX1
RO2 RO2
RX1
TO TO
RI RI TX1
IN IN
RX8
Receive Transmit
direction signal direction signal
Typical Configuration
This section uses the OptiX OSN 6800A as an example to illustrate a typical configuration.
Figure 4-65 shows the typical configurations for the optical layer of an 8-wavelength CWDM
FOADM node that uses two CMR4 boards. As shown in the figure, this configuration requires
only one subrack in total.
Figure 4-65 Typical configurations for the optical layer of an 8-wavelength CWDM FOADM
node
20
A
U
C C
S S X
M M
C C
R R
C C
4 4
A
U
X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Figure 4-66 Subrack fiber connections for an 8-wavelength CWDM FOADM node
Shelf1-IU1 Shelf1-IU2
CMR4 CMR4
OUT OUT
IN IN
MO MO
MI MI
D1 D1
A1 A1
D2 D2
A2 A2
D3 D3
A3 A3
D4 D4
A4 A4
l For detailed installation procedures of OptiX OSN 8800 T64, refer to OptiX OSN 8800
T64 Quick Installation Guide.
l For detailed installation procedures of OptiX OSN 8800 T32, refer to OptiX OSN 8800
T32 Quick Installation Guide.
l For detailed installation procedures of OptiX OSN 8800 T16, refer to OptiX OSN 8800
T16 Quick Installation Guide.
l For detailed installation procedures of OptiX OSN 6800A, refer to OptiX OSN 6800A
Quick Installation Guide.
l For detailed installation procedures of OptiX OSN 3800A, refer to OptiX OSN 3800A
Quick Installation Guide.
Initial commissioning must be conducted using the Web LCT because NEs cannot be managed
in the network management center (NMC) before initial commissioning is completed. During
initial commissioning, NEs must be connected and configured onsite, so that the U2000 can
remotely manage these NEs.
Figure 6-1 shows the flow for conducting initial commissioning using the Web LCT.
Connecting NEs to
the Web LCT
Configuring NE
Attributes
Configuring the
TN11TOM/TN52TOM
Board Onsite
Configuring the OA
Boards
Checking NE
Communication Status
Backing Up the NE
Database to the SCC
Board
Mandatory
Exiting the Web LCT Optional
Optional Operations
l Configure the TN11TOM or TN52TOM board onsite.
If there is no OSC channel on an NE and the TN11TOM or TN52TOM board is required
to provide an ESC channel, this operation must be performed. The U2000 can remotely
manage the NE and its connected NEs after the TN11TOM or TN52TOM board is
configured.
NOTE
Figure 6-2 Application scenario in which the TOM board provides an ESC channel
Site A
NMS
WDM-side
ESC channel
SCC
Client-side Client-side
ESC channel ESC channel
– The TN11TOM or TN52TOM board provides an ESC channel only when it receives
OTU1 signals on the client side or transmits OTU1 signals on the WDM side. Similarly,
an ESC channel (on the client or WDM side) is available after cross-connections for
OTU1 signals are configured.
– Client-side ESC channel: When the TN11TOM or TN52TOM board receives OTU1
signals on the client side, the client-side ESC channel is available after client-side
OTU1 cross-connections are configured.
– WDM-side ESC channel: When the TN11TOM or TN52TOM board transmits
OTU1 signals on the WDM side, the WDM-side ESC channel is available after
WDM-side OTU1 cross-connections are configured.
– In OTU1 regeneration scenarios, the ESC channel on either the client or WDM side
is required.
l Configure the OA boards.
If NEs are unreachable by the U2000 and optical power must be set for optical amplifier
(OA) boards, connect the Web LCT to the NEs onsite and perform this operation.
Installing the Web LCT by Copying and Decompressing the Software Package
1. Obtain the software package that contains the Web LCT from Huawei engineers.
2. Decompress the installation software package that includes
U2000WebLCTversion_en_win32_x86.zip.
NOTE
The version indicates the detailed version number of the Web LCT. Ensure that the decompressing
directory contains no spaces, punctuation, or non-alphabetic characters.
When you click Browse to select a different installation folder, ensure that the destination path does
not contain spaces or punctuation.
7. The following dialog box is displayed. Select the features you want to install based on the
following NOTE. Click Next.
NOTE
When you select the features to be installed, COMMON must be selected and other features can be
selected based on the managed equipment.
l For OTN equipment using the North American version only, select NA OTN.
l For OTN equipment using the global version only, select NG WDM.
l It is recommended that all the features are selected.
8. Click Install to install the Web LCT. The entire installation process lasts five minutes.
9. After the installation is complete, the Installation finished dialog box is displayed. Click
Finish.
Procedure
Step 1 Connect the crossover or straight-through cable to the Web LCT. One end of the cable should
be connected to the network port of the computer. For the specific ports and boards to be
connected, see Table 6-1.
Step 2 Check the green indicator of the network adapter interface of the computer and the indicators
on the board that connect to the computer.
NOTE
The indicator of the computer and the green "LINK" indicator on the board remain on. The orange "ACT"
indicator on the board should blink.
If the three indicators are malfunctioning:
l Replace the network cable with a new one. If the indicators are functioning correctly, the original cable
is faulty.
l If all the above-mentioned indicators are still malfunctioning, check whether the network adapter of
the computer and the board that connects to the network cable are functioning correctly.
Step 3 Change the IP address of the computer being used to commission the NE so that the computer
IP address is on the same subnet as the default IP Address of the NE.
NOTE
----End
Procedure
Step 1 Double-click the startweblct.bat file at "WebLCT\WebLCT\Tomcat" to launch the Web LCT
application.
Step 2 In the browser, enter the default value admin for User Name and Changeme_123 for
Password.
----End
Procedure
Step 1 Click NE Search and select Advanced Search at the bottom of the Screen. A Search NE
window opens.
Attribute Value
Domain Type l GNE IP Domain: Search for all NEs in the specified IP domain.
l GNE IP Address: Search for a specific NE using the specified IP address.
Domain Address l If Domain Type is set to GNE IP Domain, enter an IP domain value,
for example, 10.191.255.255.
l If Domain Type is set to GNE IP Address, enter an IP address, for
example, 10.191.167.131.
----End
Result
The NE to be commissioned is now in the list of NEs on the main Web LCT screen, and the
login status is Not Logged In or Logged In.
6.3.2 Logging In to an NE
Log in to an NE that has been added if the NE indicates "Not Logged In".
Procedure
Step 1 Highlight the NE in the main Web LCT screen and click NE Login. Enter the default value
SONET for both User Name and Password.
----End
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > NE Attribute from the Function
Tree.
Step 3 Click Apply. Click OK in the two displayed Confirm dialog boxes. Then click Close in the
displayed Operation Result dialog box.
----End
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 Set the IP address, Subnet Mask and Gateway of the NE.
Step 3 Click Apply. Click OK in the two displayed Confirm dialog boxes. Then click Close in the
displayed Operation Result dialog box.
NOTE
You will lose your connection to the NE at this point. To restore communications, perform the following:
l Change the IP address of your computer to an address on the same subnet as the NE.
l Re-run 6.3.1 Searching and Adding NEs and 6.3.2 Logging In to an NE.
----End
Background Information
The OptiX OSN 8800/6800A supports the management of master/slave subracks. When multiple
subracks are required for an NE, the master/slave subrack mode must be used for centralized
management.
In this mode, the master subrack and its slave subracks are displayed as one NE in the network
management system.
They share the same NE name and IP address.
Procedure
Step 1 In the NE Explorer, select a NE and the Slot Layout is displayed.
Step 2 Select a subrack on the top of the Slot Layout, right-click, and choose Add Slave Subrack from
the shortcut menu. The Add Slave Subrack dialog box is displayed.
Step 3 Set Shelf Type, Shelf Name, and Subrack FIC in the Add Slave Subrack dialog box. Click
OK.
NOTE
l The subrack FIC is the physical location of the NE in the rack. Set the location information of the shelf.
The recommended format is Floor-Room-Aisle-Open rack-shelf.
l For the OptiX OSN 8800, the following table lists the values for Cross-Connect Type and Cross-
Connect Capacity.
Parameter Value
Cross-Connect Type OTN
Cross-Connect Capacity l OptiX OSN 8800 T16: 0G to 640G
l OptiX OSN 8800 T32: 0G to 1.28T
l OptiX OSN 8800 T64: 0G to 2.56T
----End
Procedure
Step 1 Check whether the logical boards and physical boards are consistent.
l If yes, go to the next step.
l If no, check as follows:
– If the number of logical boards is less than the number of physical boards, verify that
the physical boards are correctly inserted and add the logical boards.
NOTE
If add the CRPC or ROP board, you should click to display the slots.
2. Verify that the physical boards are correctly inserted. On the Slot Layout pane,
right-click the corresponding logical slot, and select the required board type from
the shortcut menu.
.
– If the logical board types are inconsistent with the physical board types, delete and re-
add the logical boards.
1. In the NE Explorer, select Slot Layout.
2. Right-click the board to be deleted and change State to OOS. Then right-click the
board and choose Delete from the shortcut menu.
3. Right-click the target logical slot and select the required board type from the
shortcut menu.
Step 2 Check whether the physical boards and the boards specified in the network plan are consistent.
l If yes, you do not need to perform any other operations.
l If no, replace the physical boards, and delete and re-add the logical boards on the panel
layout.
----End
Table 6-2 lists the available working modes of the TN11TOM board and the service mapping
path for each scenario.
Table 6-2 Mappings between the working modes and the service mapping paths
OTU1 cross-connections must be configured so that an ESC channel is available between the
NE equipped with the TN11TOM board and its connected NEs.
Application Diagram
Figure 6-3 shows the position of the TN11TOM board in a WDM system where the TN11TOM
board works in cascading ODU1 tributary mode.
Figure 6-3 Position of the TN11TOM board in a WDM system (scenario 1: ODU1 tributary
mode (cascading))
1xODU1 1xOTU2 1xOTU2 1xODU1
TOM TOM
FE, GE, FDDI, 1
M M 1
STM-1, OC-3, FE, GE, FDDI,
DVB-ASI, SDI, U U STM-1, OC-3,
STM-16, OC- X X DVB-ASI, SDI,
1×ODU1
1×ODU1
N N
8×Any
8×Any
48, ESCON, / / STM-16, OC-
S D S
STM-4, OC-12, D 48, ESCON,
2 M 2
FC100, FICON, M STM-4, OC-12,
FC200, FICON U U FC100, FICON,
Express, HD- 8 X X 8 FC200, FICON
SDI, OTU1 Express, HD-
SDI, OTU1
Any ODU1 ODU1 Any
Cross-Connection Diagram
Create a cross-connection between the internal client-side and ClientLP ports on the TN11TOM
board, which is marked (1) in Figure 6-4.
Figure 6-4 Cross-connection diagram for the TN11TOM board (scenario 1: cascading ODU1
tributary mode)
WDM side
51(ODU1LP1/ODU1LP1)-1
51(ODU1LP1/ODU1LP1)-2
Other board 51(ODU1LP1/ODU1LP1)-3
Cross-connect
51(ODU1LP1/ODU1LP1)-4
module
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
A cross-connection can be configured between any client-side port and any ClientLP port.
Procedure
Step 1 Set the state of the TN11TOM board.
Before configuring the TN11TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
1. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Card from the drop-down list.
3. Double-click the Card Mode field and set it to CASCADING.
4. Click Apply.
5. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Configure a service mode for the client-side ports on the TN11TOM board. It is recommended
to select the port that is carrying the service channel specified in the network plan.
Because the service type is OTU1, Service Mode must be set to OTN for the ports.
1. Click By Card/Channel and choose Channel from the drop-down list. Click the Basic
Attributes tab in the WDM Interface pane.
2. Select a client-side port. Double-click the Service Mode field and set it to OTN.
3. Click Apply.
Step 4 Set the service type to OTU1 for ClientLP the ports. It is recommended to select the ClientLP
port that is carrying the service channel specified in the network plan.
1. Click the Advanced Attributes tab in the WDM Interface pane.
2. Select a ClientLP port. Double-click the Service Type field and set it to OTU1.
3. Click Apply.
Step 5 Configure an intra-board client-side cross-connection.
Configure an intra-board bidirectional OTU1 cross-connection between a client-side port and a
ClientLP port. Ensure that the client-side and ClientLP ports are identical to those configured
at steps 3 and 4.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level to OTU1, and set other parameters as required. The following figure
shows an example of configuring a bidirectional OTU1 cross-connection between the 3
(RX1/TX1) port and the 201(ClientLP1/ClientLP1) port.
----End
ESC channel between the local and remote NEs, configure an intra-board client-side OTU1
cross-connection. In other cases, either a WDM-side or a client-side intra-board cross-
connection is required to provide an ESC channel.
Application Diagram
Figure 6-5 shows two scenarios in which the TN11TOM board works in cascading ODU1
tributary-line mode. Configure the TN11TOM board according to the network plan.
l Dual-fed and selectively receiving on the WDM side: The TN11TOM board receives a
maximum of six services on the client side and the other two client-side ports work as
WDM-side ports, which selectively receive services.
l Single transmitting and single receiving on the WDM side: The TN11TOM board receives
a maximum of seven services on the client side and the other client-side port works as a
WDM-side port, which also receives services.
Figure 6-5 Position of the TN11TOM board in a WDM system (scenario 2: ODU1 tributary-
line mode (cascading))
1×ODU1
1×OTU1
6×Any
6×Any
48,ESCON, 48,ESCON,
FC100, FICON, FC100, FICON,
FC200, FICON FC200, FICON
MUX/ MUX/
Express, HD-SDI, Express, HD-SDI,
DMUX DMUX
DVB-ASI, SDI, OTU1 6 6 DVB-ASI, SDI, OTU1
Any Any
1×ODU1
1×OTU1
7×Any
48,ESCON, 48,ESCON,
7×Any
MUX/ MUX/
FC100, FICON, DMUX DMUX FC100, FICON,
FC200, FICON FC200, FICON
Express, HD-SDI, Express, HD-SDI,
DVB-ASI, SDI, OTU1 7 7 DVB-ASI, SDI, OTU1
Any Any
Cross-Connection Diagram
Create an OTU1 cross-connection between the internal 51(ODU1LP1/ODU1LP1) and WDM-
side ports on the TN11TOM board, which is marked (2) in Figure 6-6.
Figure 6-6 Cross-connection diagram for the TN11TOM board (scenario 2: ODU1 tributary-
line mode (cascading))
The internal cross-connection of the board, which needs to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
NOTE
l Only the RX7/TX7 and RX8/TX8 optical ports can be used as WDM-side optical ports.
l A cross-connection can be configured between any client-side port and any ClientLP port.
Configuration Process
The configuration process for providing a client-side ESC channel differs from that for providing
a WDM-side ESC channel. Table 6-3 lists the configuration process.
Remarks:
l Yes: This task is required.
l No: This task is not required.
Procedure
Step 1 Set the state of the TN11TOM board.
Before configuring the TN11TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Step 2 Configure the working mode for the TN11TOM board.
Set Card Mode to CASCADING.
1. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Card from the drop-down list.
3. Double-click the Card Mode field and set it to CASCADING.
4. Click Apply.
5. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Optional: Set the port type.
NOTE
Set an RX/TX port as a WDM-side port according to the network plan. It is recommended to
set the type for the port that is carrying the service channel specified in the network plan. For
the application of "dual-fed and selectively receiving on the WDM side", set the type for the
port planned to carry the working channel.
1. Right-click the board in the Slot Layout pane and choose Path View from the shortcut
menu.
2. Right-click the port and choose Delete Port.
3. Right-click the blank area and choose Add Port. The Add Port dialog box is displayed.
4. Set Type according to the network plan. Click OK to apply the configuration.
Step 4 Optional: Configure a service mode for client-side ports on the TN11TOM board. It is
recommended to set a service mode for the client-side port that is carrying the service channel
specified in the network plan.
NOTE
Because the service type is OTU1, Service Mode must be set to OTN for the ports.
1. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Channel from the drop-down list. Click the Basic
Attributes tab in the WDM Interface pane.
3. Select a client-side port. Double-click the Service Mode field and set it to OTN as shown
in the following figure.
Step 5 Optional: Set the service type to OTU1 for the ClientLP ports. It is recommended to set a service
type for the ClientLP port that is carrying the service channel specified in the network plan.
NOTE
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level to OTU1, and set other parameters as required.
l To configure a client-side cross-connection, configure a cross-connection between a
client-side port and a ClientLP port. Ensure that the client-side and ClientLP ports are
identical to those configured in steps 4 and 5. The following figure shows an example
of configuring such a cross-connection.
mode. When the TN11TOM board works in non-cascading ODU1 tributary mode, intra-board
client-side OTU1 cross-connections must be configured so an ESC channel is available between
the NE equipped with the TN11TOM board and its connected NEs.
Application Diagram
Figure 6-7 shows the position of the TN11TOM board in a WDM system where the TN11TOM
board works in non-cascading ODU1 tributary mode.
Figure 6-7 Position of the TN11TOM board in a WDM system (scenario 3: ODU1 tributary
mode (non-cascading))
4xODU1 1xOTU2 1xOTU2 4xODU1
TOM TOM
1 1
FC100, FICON, FE, FC100, FICON, FE,
GE, STM-1, OC-3, 1 1 GE, STM-1, OC-3,
STM-4, OC-12, STM-4, OC-12,
4×ODU1
4×ODU1
8×Any
8×Any
STM-16, OC-48 MUX/ MUX/ STM-16, OC-48
NS2 NS2
, FC200, FICON DMUX DMUX , FC200, FICON
Express, DVB-ASI, Express, DVB-ASI,
ESCON, FDDI, SDI, 4 4 ESCON, FDDI, SDI,
HD-SDI, OTU1 8 8 HD-SDI, OTU1
Cross-Connection Diagram
Create a cross-connection between the internal client-side and ClientLP ports on the TN11TOM
board, which is marked (1) in Figure 6-8.
Figure 6-8 Cross-connection diagram for the TN11TOM board (scenario 3: ODU1 tributary
mode (non-cascading))
WDM side
51(ODU1LP1/ODU1LP1)-1
51(ODU1LP1/ODU1LP1)-2
Other board 51(ODU1LP1/ODU1LP1)-3
Cross-connect 51(ODU1LP1/ODU1LP1)-4
module
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
A cross-connection can be configured between any client-side port and any ClientLP port.
Procedure
Step 1 Set the state of the TN11TOM board.
Before configuring the TN11TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Step 2 Configure the working mode for the TN11TOM board.
Set Card Mode to NON-CASCADING.
1. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Card from the drop-down list.
3. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
4. Click Apply.
5. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Configure a service mode for the client-side ports on the TN11TOM board. It is recommended
to set a service mode for the client-side port that is carrying the service channel specified in the
network plan.
Because the service type is OTU1, Service Mode must be set to OTN for the ports.
1. Click By Card/Channel and choose Channel from the drop-down list. Click the Basic
Attributes tab in the WDM Interface pane.
2. Select a client-side port. Double-click the Service Mode field and set it to OTN as shown
in the following figure.
Step 4 Set the service type to OTU1 for the ClientLP ports. It is recommended to set a service type for
the ClientLP port that is carrying the service channel specified in the network plan.
1. Click the Advanced Attributes tab in the WDM Interface pane.
2. Select a ClientLP port. Double-click the Service Type field and set it to OTU1 as shown
in the following figure.
----End
Application Diagram
Figure 6-9 shows the position of the TN11TOM board in a WDM system where the TN11TOM
board works in non-cascading ODU1 tributary-line mode.
Figure 6-9 Position of the TN11TOM board in a WDM system (scenario 4: ODU1 tributary-
line mode (non-cascading))
4xOTU1 4xOTU1
TOM TOM
FC100, FICON, FE, 1 1 1 1
FC100, FICON, FE,
GE, STM-1, OC-3 GE, STM-1, OC-3
, STM-4, OC-12, , STM-4, OC-12,
4×ODU1
4×OTU1
4×ODU1
4×OTU1
4×Any
4×Any
Any Any
Cross-Connection Diagram
Create an OTU1 cross-connection between the internal ODU1LP and WDM-side ports on the
TN11TOM board, which is marked (2) in Figure 6-10.
Figure 6-10 Cross-connection diagram for the TN11TOM board (scenario 4: ODU1 tributary-
line mode (non-cascading))
Client side WDM side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1) 51(ODU1LP1/ODU1LP1) 7(TX5/RX5)-1
1 3 2
4(TX2/RX2)-1 202(ClientLP2/ClientLP2) 52(ODU1LP2/ODU1LP2) 8(TX6/RX6)-1
5(TX3/RX3)-1 203(ClientLP3/ClientLP3) 53(ODU1LP3/ODU1LP3) 9(TX7/RX7)-1
6(TX4/RX4)-1 204(ClientLP4/ClientLP4) 54(ODU1LP4/ODU1LP4) 10(TX8/RX8)-1
The internal cross-connection of the board, which needs to be configured on the NMS
NOTE
Procedure
Step 1 Set the state of the TN11TOM board.
Before configuring the TN11TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Step 2 Configure the working mode for the TN11TOM board.
Set Card Mode to NON-CASCADING.
1. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Card from the drop-down list.
3. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
4. Click Apply.
5. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Set the port type.
Set an RX/TX port as a WDM-side port according to the network plan. It is recommended to
set the type for the port that is carrying the service channel specified in the network plan.
1. Right-click the board in the Slot Layout pane, and choose Path View from the shortcut
menu.
2. Right-click the port and choose Delete Port.
3. Right-click the blank area and choose Add Port. The Add Port dialog box is displayed.
4. Set Type according to the network plan. Click OK to apply the configuration.
----End
Application Diagram
Figure 6-11 shows the position of the TN11TOM board in a WDM system where the TN11TOM
board works as an electrical regeneration board in ODU1 tributary-line mode.
Figure 6-11 Position of the TN11TOM board in a WDM system (scenario 5: ODU1 tributary-
line mode (electrical regeneration board))
4xOTU1 4xOTU1
TOM
4×ODU1
4×OTU1
4×OTU1
DMUX MUX
4xOTU1 4xOTU1
TOM4×ODU1
4×OTU1
4×OTU1
MUX DMUX
Cross-Connection Diagram
l Create a cross-connection between the internal client-side and ClientLP ports on the
TN11TOM board, which is marked (1) in Figure 6-12.
l Create an OTU1 cross-connection between the internal ODU1LP and WDM-side ports on
the TN11TOM board, which is marked (2) in Figure 6-12.
Figure 6-12 Cross-connection diagram for the TN11TOM board (scenario 5: ODU1 tributary-
line mode (electrical regeneration board))
Client side WDM side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1) 51(ODU1LP1/ODU1LP1) 7(TX5/RX5)-1
1 3 2
4(TX2/RX2)-1 202(ClientLP2/ClientLP2) 52(ODU1LP2/ODU1LP2) 8(TX6/RX6)-1
5(TX3/RX3)-1 203(ClientLP3/ClientLP3) 53(ODU1LP3/ODU1LP3) 9(TX7/RX7)-1
6(TX4/RX4)-1 204(ClientLP4/ClientLP4) 54(ODU1LP4/ODU1LP4) 10(TX8/RX8)-1
The internal cross-connection of the board, which needs to be configured on the NMS
NOTE
Configuration Process
The configuration process for providing a client-side ESC channel differs from that for providing
a WDM-side ESC channel. Table 6-4 lists the configuration process.
Remarks:
l Yes: This task is required.
l No: This task is not required.
Procedure
Step 1 Set the state of the TN11TOM board.
Before configuring the TN11TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Step 2 Configure the working mode for the TN11TOM board.
Set Card Mode to NON-CASCADING.
1. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Card from the drop-down list.
3. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
4. Click Apply.
5. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Optional: Set the port type.
NOTE
Set an RX/TX port as a WDM-side port according to the network plan. It is recommended to
set the type for the port that is carrying the service channel specified in the network plan.
1. Right-click the board in the Slot Layout pane and choose Path View from the shortcut
menu.
2. Right-click the port and choose Delete Port.
3. Right-click the blank area and choose Add Port. The Add Port dialog box is displayed.
4. Set Type according to the network plan. Click OK to apply the configuration.
Step 4 Optional: Configure a service mode for the client-side ports on the TN11TOM board. It is
recommended to set a service mode for the port that is carrying the service channel specified in
the network plan.
NOTE
Because the service type is OTU1, Service Mode must be set to OTN for the ports.
1. In the NE Explorer, select the TN11TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Channel from the drop-down list. Click the Basic
Attributes tab in the WDM Interface pane.
3. Select a client-side port. Double-click the Service Mode field and set it to OTN as shown
in the following figure.
Step 5 Optional: Set the service type to OTU1 for the ClientLP ports. It is recommended to set a service
type for the ClientLP port that is carrying the service channel specified in the network plan.
NOTE
----End
Table 6-5 Mapping between the working modes and the service mapping paths
Board Scenar Port Working Mapping Path Configuration
Workin io No. Mode Scenario
g Mode
NOTE
[->ODU1]: indicates that "ODU1" is optional. For example, in non-cascading ODU0 tributary mode, there
are two service signal mapping paths: Any->ODU0 and Any->ODU0->ODU1.
Application Diagram
Figure 6-13 shows two scenarios in which the TN52TOM board works in cascading ODU0
tributary-line mode. Configure the TN52TOM board according to the network plan.
l Dual-fed and selectively receiving on the WDM side: The TN52TOM board receives a
maximum of six services on the client side and the other two client-side ports work as
WDM-side ports, which selectively receive services.
l Single transmitting and single receiving on the WDM side: The TN52TOM board receives
a maximum of seven services on the client side and the other client-side port works as a
WDM-side port, which also receives services.
Figure 6-13 Position of the TN52TOM board in a WDM system (scenario 2: Any->ODU0-
>ODU1->OTU1)
Dual-fed and selectively receiving on the WDM side:
1xOTU1 1xOTU1
TOM TOM
1 MUX/ MUX/ 1
DMUX DMUX
FE, GE, FE, GE,
FC100, FICON, FC100, FICON,
2×ODU0
1×ODU1
1×ODU1
2×ODU0
1×OTU1
1×OTU1
6×Any
6×Any
DVB-ASI, SDI, DVB-ASI, SDI,
ESCON, FDDI ESCON, FDDI
MUX/ MUX/
6 DMUX DMUX 6
Any Any
TOM TOM
1 1
2×ODU0
FC100, FICON,
2×ODU0
1×ODU1
1×ODU1
1×OTU1
1×OTU1
FC100, FICON,
7×Any
7×Any
DVB-ASI, SDI, MUX/ MUX/
DVB-ASI, SDI,
ESCON, FDDI DMUX DMUX
ESCON, FDDI
7 7
Any Any
Cross-Connection Diagram
Create an OTU1 cross-connection between the internal 51(ODU1LP1/ODU1LP1) and WDM-
side ports on the TN52TOM board, which is marked (2) in Figure 6-14.
Figure 6-14 Cross-connection diagram for the TN52TOM board (scenario 2: Any->ODU0-
>ODU1->OTU1)
Dual-fed and selectively receiving on the WDM side:
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
l Only the RX7/TX7 and RX8/TX8 optical ports can be used as WDM-side optical ports.
l A cross-connection can be configured between any client-side port and any ClientLP port.
Procedure
Step 1 Set the state of the TN52TOM board.
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Set Work Mode to CASCADING and Port Working Mode to ODU0 tributary-line mode
(Any->ODU0->ODU1->OTU1).
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, set Port Working Mode for the 201(ClientLP1/
ClientLP1) port. Double-click the Port Working Mode field and choose ODU0 tributary-
line mode (Any->ODU0->ODU1->OTU1).
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Set the port type.
Set an RX/TX port as a WDM-side port according to the network plan. It is recommended to
set the type for the port that is carrying the service channel specified in the network plan. For
the application of "dual-fed and selectively receiving on the WDM side", set the type for the
port planned to carry the working channel.
1. Right-click the board in the Slot Layout pane and choose Path View from the shortcut
menu.
2. Right-click the port and choose Delete Port.
3. Right-click the blank area and choose Add Port. The Add Port dialog box is displayed.
4. Set Type according to the network plan. Click OK to apply the configuration.
Application Diagram
Figure 6-15 shows two scenarios in which the TN52TOM board works in cascading ODU1
tributary-line mode. Configure the TN52TOM board according to the network plan.
l Dual-fed and selectively receiving on the WDM side: The TN52TOM board receives a
maximum of six services on the client side and the other two client-side ports work as
WDM-side ports, which selectively receive services.
l Single transmitting and single receiving on the WDM side: The TN52TOM board receives
a maximum of seven services on the client side and the other client-side port works as a
WDM-side port, which also receives services.
TOM TOM
1 1 FE, GE, STM-1,
FE, GE, STM-1, MUX/ MUX/ STM-4, STM-16,
STM-4, STM-16, DMUX DMUX OC-3, OC-12, OC-
OC-3, OC-12, OC-
1×ODU1
1×ODU1
1×OTU1
1×OTU1
6×Any
Any Any
TOM TOM
1 1
FE, GE, STM-1, FE, GE, STM-1,
STM-4, STM-16, STM-4, STM-16,
OC-3, OC-12, OC- OC-3, OC-12, OC-
1×ODU1
1×ODU1
1×OTU1
1×OTU1
7×Any
7×Any
48, FC100, FC200, MUX/ MUX/ 48, FC100, FC200,
FICON, FICON DMUX DMUX FICON, FICON
Express, HD-SDI, Express, HD-SDI,
DVB-ASI, SDI, DVB-ASI, SDI,
ESCON, FDDI 7 7 ESCON, FDDI
Any Any
Cross-Connection Diagram
Create an OTU1 cross-connection between the internal 51(ODU1LP1/ODU1LP1) and WDM-
side ports on the TN52TOM board, which is marked (2) in Figure 6-16.
Figure 6-16 Cross-connection diagram for the TN52TOM board (scenario 4: OTU1/Any-
>ODU1->OTU1)
The internal cross-connection of the board, which needs to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
NOTE
l Only the RX7/TX7 and RX8/TX8 optical ports can be used as WDM-side optical ports.
l A cross-connection can be configured between any client-side port and any ClientLP port.
Procedure
Step 1 Set the state of the TN52TOM board
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane, and choose State > OOS from the shortcut
menu.
Step 2 Configure the working mode for the TN52TOM board.
Set Work Mode to CASCADING, and Port Working Mode to ODU1 tributary-line mode
(OTU1/Any->ODU1->OTU1).
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, set Port Working Mode for the 201(ClientLP1/
ClientLP1) port. Double-click the Port Working Mode field and set it to ODU1 tributary-
line mode (OTU1/Any->ODU1->OTU1).
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Set the port type.
Set an RX/TX port as a WDM-side port according to the network plan. It is recommended to
select the port that is carrying the service channel specified in the network plan. For the
application of "dual-fed and selectively receiving on the WDM side", set the type for the port
planned to carry the working channel.
1. Right-click the board in the Slot Layout pane and choose Path View from the shortcut
menu.
2. Right-click the port and choose Delete Port.
3. Right-click the blank area and choose Add Port. The Add Port dialog box is displayed.
4. Set Type according to the network plan. Click OK to apply the configuration.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed. Set the parameters.
After these configurations are complete, set the statel to IS, which indicates that the board is in
service.
1. Right-click the board in the Slot Layout pane and choose State > IS.
----End
Application Diagram
Figure 6-17 shows two scenarios in which the TN52TOM board works in non-cascading ODU0
tributary-line mode. Configure the TN52TOM board according to the network plan.
l Dual-fed and selectively receiving on the WDM side: The TN52TOM board receives a
maximum of four services on the client side and the other two client-side ports work as
WDM-side ports, which selectively receive services.
l Single transmitting and single receiving on the WDM side: The TN52TOM board receives
a maximum of six services on the client side and the other client-side port works as a WDM-
side port, which also receives services.
Figure 6-17 Position of the TN52TOM board in a WDM system (scenario 6: Any->ODU0-
>ODU1->OTU1)
2xOTU1 2xOTU1
TOM TOM
1 MUX/ MUX/ 1
DMUX DMUX
FE, GE, FE, GE,
FC100, FICON,
2×ODU1
4×ODU0
FC100, FICON,
4×ODU0
2×ODU1
2×OTU1
2×OTU1
4×Any
4×Any
DVB-ASI, SDI, DVB-ASI, SDI,
ESCON, FDDI ESCON, FDDI
MUX/ MUX/
4 DMUX DMUX 4
Any Any
TOM TOM
1 1
2×ODU1
2×OTU1
4×ODU0
FC100, FICON,
2×ODU1
2×OTU1
4×ODU0
6×Any
FC100, FICON,
6×Any
6 6
Any Any
Cross-Connection Diagram
Create an OTU1 cross-connection between the internal ODU1LP and WDM-side ports on the
TN52TOM board, which is marked (2) in Figure 6-18.
Figure 6-18 Cross-connection diagram for the TN52TOM board (scenario 6: Any->ODU0-
>ODU1->OTU1)
Dual-fed and selectively receiving on the WDM side:
Client side 161(ODU0LP1/ WDM side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1 51(ODU1LP1/ 7(TX5/RX5)-1
4(TX2/RX2)-1 201(ClientLP1/ClientLP1)-2 ODU0LP1)-1 8(TX6/RX6)-1
201(ClientLP1/ClientLP1)-3 3 ODU1LP1)-1
5(TX3/RX3)-1 1 3 9(TX7/RX7)-1
6(TX4/RX4)-1 201(ClientLP1/ClientLP1)-4 2 10(TX8/RX8)-1
202(ClientLP2/ClientLP2)-1 161(ODU0LP1/
202(ClientLP2/ClientLP2)-2 ODU0LP1)-2
202(ClientLP2/ClientLP2)-3
202(ClientLP2/ClientLP2)-4 162(ODU0LP1/ 52(ODU1LP2/
203(ClientLP3/ClientLP3)-1 ODU0LP1)-1 ODU1LP2)-1
203(ClientLP3/ClientLP3)-2
204(ClientLP4/ClientLP4)-1 162(ODU0LP1/ TOM
204(ClientLP4/ClientLP4)-2 ODU0LP1)-2
Cross-connect module Cross-connect module Cross-connect module Cross-connect module
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
NOTE
Procedure
Step 1 Set the state of the TN52TOM board.
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Step 2 Configure the working mode for the TN52TOM board.
Set Work Mode to NON-CASCADING, and Port Working Mode to ODU0 tributary-line
mode (Any->ODU0->ODU1->OTU1).
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, double-click the Port Working Mode field and set the
205 (or 207) port to None (not for ports) first. Then set the 201 (or 203) port to ODU0
Tributary-Line Mode (Any->ODU0->ODU1->OTU1).
It is recommended to set a working mode for the port that is carrying the service channel
specified in the network plan.
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Set an RX/TX port as a WDM-side port according to the network plan. It is recommended to
set the type for the port that is carrying the service channel specified in the network plan. For
the application of "dual-fed and selectively receiving on the WDM side", set the type for the
port planned to carry the working channel.
1. Right-click the board in the Slot Layout pane and choose Path View from the shortcut
menu.
2. Right-click the port and choose Modify Port from the shortcut menu. The Modify Port
dialog box is displayed. Set Type according to the network plan.
Select an internal port from (3) in Figure 6-18. The internal port that is identical to the service
port specified in the network plan is recommended. Then configure an intra-board cross-
connection between the internal port and a WDM-side port. Ensure that the WDM-side port is
the one for which the port type is changed in step 3.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level and Service Type, and set other parameters as required.
After these configurations are complete, set the state to IS, which indicates that the board is in
service.
1. Right-click the board in the Slot Layout pane and choose State > IS.
----End
Application Diagram
Figure 6-19 shows the position of the TN52TOM board in a WDM system where the TN52TOM
board works in non-cascading ODU1 tributary mode.
Figure 6-19 Position of the TN52TOM board in a WDM system (scenario 7: OTU1->ODU1)
4xODU1 1xOTU2 1xOTU2 4xODU1
TOM TOM
1 1 1 1
4×ODU1
4×ODU1
4×OTU1
4×OTU1
MUX/ MUX/
OTU1 NS2 NS2 OTU1
DMUX DMUX
4 4 4 4
ODU1 ODU1
NOTE
In this working mode, configurations for the TN52TOM board to receive Any services differ from those
for the board to receive OTU1 services. If the TN52TOM board is configured to receive Any services, it
cannot carry an ESC channel. In this case, no configuration is required.
Cross-Connection Diagram
Create an OTU1 cross-connection between the internal client-side and ClientLP ports on the
TN52TOM board, which is marked (1) in Figure 6-20.
Figure 6-20 Cross-connection diagram for the TN52TOM board (scenario 7: OTU1->ODU1)
WDM side
51(ODU1LP1/ODU1LP1)-1
51(ODU1LP1/ODU1LP1)-2
Other board 51(ODU1LP1/ODU1LP1)-3
Cross-connect 51(ODU1LP1/ODU1LP1)-4
module
The internal cross-connection of the board, which needs to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
A cross-connection can be configured between any client-side port and any ClientLP port.
Procedure
Step 1 Set the state of the TN52TOM board.
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Step 2 Configure the working mode for the TN52TOM board.
Set Work Mode to NON-CASCADING and Port Working Mode to ODU1 mode (OTU1/
Any->ODU1).
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, set Port Working Mode for a ClientLP port. The port
that is carrying the channel specified in the network plan is recommended. Double-click
the Port Working Mode field and set it to ODU1 mode (OTU1/Any->ODU1).
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Configure the working mode for the client-side ports on the TN52TOM board as OTN.
Because the service type is OTU1, set Service Mode to OTN for the port. It is recommended
to select the port that is carrying the service channel specified in the network plan.
1. In the NE Explorer, select the TN52TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Channel from the drop-down list.
3. Click the Basic Attributes tab and select a client-side port. Double-click the Service
Mode field and choose OTN.
4. Click Apply.
Step 4 Set the service type to OTU1 for the ClientLP ports. It is recommended to select the ClientLP
port that is carrying the service channel specified in the network plan.
1. Click the Advanced Attributes tab and select a ClientLP port.
2. Double-click the Service Type field and set it to OTU1.
3. Click Apply.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level to OTU1, and set other parameters as required. The following figure
shows an example of configuring a bidirectional OTU1 cross-connection between the 3
(RX1/TX1) port and the 201(ClientLP1/ClientLP1) port.
----End
Application Diagram
Figure 6-21 shows the position of the TN52TOM board in a WDM system where the TN52TOM
board works in non-cascading ODU1 tributary mode.
Figure 6-21 Position of the TN52TOM board in a WDM system (scenario 8: OTU1->ODU1-
>Any->ODU0->ODU1)
4xODU1 1xOTU2 1xOTU2 4xODU1
TOM TOM
1 1
1 1 M M 1 1
U U
X X
8×ODU0
8×Any
4×ODU1
4×ODU1
4×ODU1
4×ODU1
4×OTU1
8×ODU0
4×OTU1
64×Any
N N
64×Any
8×Any
8×Any
8×Any
32×Any
/ /
32×Any
OTU1 OTU1
S D S
D
2 M 2
M
U U
4 4 4 4 4
4 X X
Cross-Connection Diagram
Create a cross-connection between the internal client-side and ClientLP ports on the TN52TOM
board, which is marked (1) in Figure 6-22.
Figure 6-22 Cross-connection diagram for the TN52TOM board (scenario 8: OTU1->ODU1-
>Any->ODU0->ODU1)
WDM
side
51(ODU1LP1/ODU1LP1)-1
51(ODU1LP1/ODU1LP1)-2
Other board 51(ODU1LP1/ODU1LP1)-3
Cross-connect 51(ODU1LP1/ODU1LP1)-4
module
Client WDM
side 201(ClientLP1 233(AnyLP1/AnyLP1)-1 237(AnyLP5/AnyLP5)-1 161(ODU0LP1 side
3(TX1/RX1)-1 /ODU0LP1)-1
/ClientLP1)-1
1 2 3 2 4
4(TX2/RX2)-1 203(ClientLP3 233(AnyLP1/AnyLP1)-8 237(AnyLP5/AnyLP5)-8
/ClientLP3)-1 238(AnyLP6/AnyLP6)-1
5(TX3/RX3)-1
205(ClientLP5 162(ODU0LP2
6(TX4/RX4)-1 /ClientLP5)-1 238(AnyLP6/AnyLP6)-8 /ODU0LP2)-1
234(AnyLP2/AnyLP2)-1 239(AnyLP7/AnyLP7)-1
207(ClientLP7
7(TX5/RX5)-1 /ClientLP7)-1
234(AnyLP2/AnyLP2)-8 239(AnyLP7/AnyLP7)-8
235(AnyLP3/AnyLP3)-1 163(ODU0LP3
8(TX6/RX6)-1 240(AnyLP8/AnyLP8)-1
/ODU0LP3)-1
235(AnyLP3/AnyLP3)-8 240(AnyLP8/AnyLP8)-8
9(TX7/RX7)-1
244(AnyLP12/AnyLP12)1
10(TX8/RX8)-1 236(AnyLP4/AnyLP4)-7 164(ODU0LP4
236(AnyLP4/AnyLP4)-8 244(AnyLP12/AnyLP12)-8 /ODU0LP4)-1
Cross-connect Cross-connect Cross-connect Cross-connect Cross-connect
TOM module module module module module
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
A cross-connection can be configured between any client-side port and any ClientLP port.
Procedure
Step 1 Set the state of the TN52TOM board.
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, set Port Working Mode for a ClientLP port. The port
that is carrying the channel specified in the network plan is recommended. Double-click
the Port Working Mode field and choose ODU1_ANY_ODU0_ODU1 re-encapsulation
mode (OTU1->ODU1->Any->ODU0->ODU1).
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Configure the service mode for the client-side ports on the TN52TOM board as OTN.
Because the service type is OTU1, Service Mode must be set to OTN for the ports. It is
recommended to select the port that is carrying the service channel specified in the network plan.
1. In the NE Explorer, select the TN52TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Channel from the drop-down list.
3. Click the Basic Attributes tab and select a client-side port.
4. Double-click the Service Mode field and set it to OTN.
5. Click Apply.
Step 4 Set the service type to OTU1 for the ClientLP ports. It is recommended to select the ClientLP
port that is carrying the service channel specified in the network plan.
1. Click the Advanced Attributes tab and select a ClientLP port.
2. Double-click the Service Type field and set it to OTU1.
3. Click Apply.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level to OTU1, and set other parameters as required. The following figure
shows an example of configuring a bidirectional OTU1 cross-connection between the 3
(RX1/TX1) port and the 201(ClientLP1/ClientLP1) port.
----End
Application Diagram
Figure 6-23 shows the position of the TN52TOM board in a WDM system where the TN52TOM
board works in non-cascading ODU1 tributary-line mode (OTU1->ODU1->Any->ODU0-
>ODU1->OTU1).
Figure 6-23 Position of the TN52TOM board in a WDM system (scenario 9: OTU1->ODU1-
>Any->ODU0->ODU1->OTU1)
2xOTU1 2xOTU1
TOM TOM
MUX/ MUX/
1 DMUX DMUX 1
32×Any
32×Any
2×ODU1
4×ODU0
4×ODU0
2×ODU1
2×OTU1
2×OTU1
2×ODU1
2×ODU1
2×OTU1
2×OTU1
16×Any
16×Any
OTU1 OTU1
MUX/ MUX/
2 DMUX DMUX 2
Cross-Connection Diagram
l Create a cross-connection between the internal client-side and ClientLP ports on the
TN52TOM board, which is marked (1) in Figure 6-24.
l Create an OTU1 cross-connection between the internal ODU1LP and WDM-side ports on
the TN52TOM board, which is marked (4) in Figure 6-24.
Figure 6-24 Cross-connection diagram for the TN52TOM board (scenario 9: OTU1->ODU1-
>Any->ODU0->ODU1->OTU1)
Client side WDM side
237(AnyLP5/AnyLP5)-8
234(AnyLP2/AnyLP2)-8
238(AnyLP6/AnyLP6)-1
238(AnyLP6/AnyLP6)-8
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
NOTE
Configuration Process
The configuration process for providing a client-side ESC channel differs from that for providing
a WDM-side ESC channel. Table 6-6 lists the configuration process.
Remarks:
l Yes: This task is required.
l No: This task is not required.
Procedure
Step 1 Set the state of the TN52TOM board.
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, double-click the Port Working Mode field and set the
205 (or 207) port to None (not for ports) first. Then set the 201 (or 203) port to
ODU1_ANY_ODU0_ODU1 re-encapsulation tributary-line mode (OTU1->ODU1-
>Any->ODU0->ODU1->OTU1).
It is recommended to set a working mode for the port that is carrying the service channel
specified in the network plan.
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Set an RX/TX port as a WDM-side port according to the network plan. It is recommended to
set a service type for the port that is carrying the service channel specified in the network plan.
1. Right-click the board in the Slot Layout pane and choose Path View from the shortcut
menu.
2. Right-click the port and choose Modify Port from the shortcut menu. The Modify Port
dialog box is displayed.
3. Set Type according to the network plan.
Because the service type is OTU1, Service Mode must be set to OTN for the ports.
1. Click the Basic Attributes tab in the WDM Interface pane.
2. Select a client-side port. Double-click the Service Mode field and set it to OTN as shown
in the following figure.
3. Click Apply.
Step 5 Optional: Set the service type to OTU1 for the ClientLP ports. It is recommended to select the
ClientLP port that is carrying the service channel specified in the network plan.
NOTE
2. Click Apply.
Step 6 Configure an intra-board cross-connection.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level to OTU1, and set other parameters as required.
l To configure a client-side cross-connection, configure a cross-connection between a
client-side port and a ClientLP port. Ensure that the client-side and ClientLP ports are
identical to those configured in steps 4 and 5. The following figure shows an example
of configuring such a cross-connection.
After these configurations are complete, set the state to IS, which indicates that the board is in
service.
1. Right-click the board in the Slot Layout pane and choose State > IS.
----End
Application Diagram
Figure 6-25 and Figure 6-26 show the position of the TN52TOM board in a WDM system
where the TN52TOM board works in non-cascading ODU1 tributary-line mode (OTU1/Any-
>ODU1->OTU1). Configure the TN52TOM board according to the network plan.
l Figure 6-25 shows a scenario in which OTU1 signals are electrically regenerated.
l Figure 6-26 shows a scenario in which the TN52TOM board works in tributary-line mode
and receives Any signals.
– Dual-fed and selectively receiving on the WDM side: The TN52TOM board receives a
maximum of four services on the client side, and the other four client-side ports work
as WDM-side ports, two of which selectively receive services.
– Single transmitting and single receiving on the WDM side: The TN52TOM board
receives a maximum of six services on the client side, and the other two client-side ports
work as WDM-side ports, which also receive services.
Figure 6-25 Position of the TN52TOM board in a WDM system (scenario 10: OTU1->ODU1-
>OTU1)
4xOTU1 4xOTU1
TOM
RX1 TX5
D
RX2 TX6 M
4×ODU1
4×OTU1
4×OTU1
M
U
U RX3 TX7 X
X RX4
TX8
TX1 RX5
D
M TX2
4×ODU1
4×OTU1
4×OTU1
RX6 M
U
X TX3 RX7 U
X
TX4 RX8
Figure 6-26 Position of the TN52TOM board in a WDM system (scenario 10: Any->ODU1-
>OTU1)
2×ODU1
2×OTU1
2×OTU1
4×Any
4×Any
Any Any
4×OTU1
4×Any
4×Any
Any Any
Cross-Connection Diagram
l Create a cross-connection between the internal client-side and ClientLP ports on the
TN52TOM board, which is marked (1) in Figure 6-27 and Figure 6-28.
l Create an OTU1 cross-connection between the internal ODU1LP and WDM-side ports on
the TN52TOM board, which is marked (3) in Figure 6-27 and Figure 6-28.
Figure 6-27 Cross-connection diagram for the TN52TOM board (scenario 10: OTU1->ODU1-
>OTU1)
Client side WDM side
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
Figure 6-28 Cross-connection diagram for the TN52TOM board (scenario 10: Any->ODU1-
>OTU1)
Dual-fed and selectively receiving on the WDM side:
Client side WDM side
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
NOTE
Configuration Process
The configuration process for providing a client-side ESC channel differs from that for providing
a WDM-side ESC channel. Table 6-7 lists the configuration process.
Remarks:
l Yes: This task is required.
l No: This task is not required.
Procedure
Step 1 Set the state of the TN52TOM board.
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Set Work Mode to NON-CASCADING, and Port Working Mode to ODU1 tributary-line
mode (OTU1/Any->ODU1->OTU1).
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, double-click the Port Working Mode field and set Port
Working Mode for each Optical Port.
l For the 201(ClientLP1/ClientLP1)-207(ClientLP7/ClientLP7) ports, set Port Working
Mode to ODU1 tributary-line mode (OTU1/Any->ODU1->OTU1).
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Optional: Set the port type.
NOTE
Set the port as a WDM-side port according to the network plan. It is recommended to select the
port that is carrying the service channel specified in the network plan.
1. Right-click the board in the Slot Layout pane and choose Path View from the shortcut
menu.
2. Right-click the port and choose Modify Port from the shortcut menu. The Modify Port
dialog box is displayed. Set Type to Line Side Colorless Optical Port.
Because the service type is OTU1, Service Mode must be set to OTN for the ports. It is
recommended to select the port that is carrying the service channel specified in the network plan.
1. Click the Basic Attributes tab in the WDM Interface pane. Select a client-side port,
double-click the Service Mode field and set it to OTN.
2. Click Apply.
Step 5 Optional: Set the service type to OTU1 for the ClientLP ports. It is recommended to select the
ClientLP port that is carrying the service channel specified in the network plan.
NOTE
3. Click Apply.
Step 6 Configure an intra-board cross-connection.
Configure bidirectional OTU1 cross-connections between the 51(ODU1LP1/ODU1LP1)-54
(ODU1LP4/ODU1LP4) optical ports and 7(RX5/TX5)-10(RX8/TX8) optical ports based on
Figure 6-27 and Figure 6-28.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level to OTU1, and set other parameters as required.
l To configure a client-side cross-connection, configure a cross-connection between a
client-side port and a ClientLP port. Ensure that the client-side and ClientLP ports are
identical to those configured in steps 4 and 5. The following figure shows an example
of configuring such a cross-connection.
After these configurations are complete, set the state to IS, which indicates that the board is in
service.
1. Right-click the board in the Slot Layout pane and choose State > IS.
----End
Application Diagram
Figure 6-29 shows the position of the TN52TOM board in a WDM system where the TN52TOM
board works in non-cascading ODU1 tributary mode.
Figure 6-29 Position of the TN52TOM board in a WDM system (scenario 11: OTU1->ODU1-
>ODU0)
8xODU0 1xOTU2 1xOTU2 8xODU0
TOM TOM
1 1
1 1 M M 1 1
U U
X X
8×ODU0
8×ODU0
4×ODU1
4×ODU1
4×OTU1
4×OTU1
N N
8×Any
8×Any
OTU1 / / OTU1
S D S
D
2 M 2
M
U U
4 8 8 8 8 4
X X
Cross-Connection Diagram
Create a cross-connection between the internal client-side and ClientLP ports on the TN52TOM
board, which is marked (1) in Figure 6-30.
Figure 6-30 Cross-connection diagram for the TN52TOM board (scenario 11: OTU1->ODU1-
>ODU0)
WDM
161(ODU0LP1/ODU0LP1)-1 side
161(ODU0LP1/ODU0LP1)-2
162(ODU0LP2/ODU0LP2)-1
Other board 162(ODU0LP2/ODU0LP2)-2
163(ODU0LP3/ODU0LP3)-1
163(ODU0LP3/ODU0LP3)-2
Cross-connect 164(ODU0LP4/ODU0LP4)-1
module 164(ODU0LP4/ODU0LP4)-2
Client WDM
side 3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1 161(ODU0LP1/ODU0LP1)-1 side
4(TX2/RX2)-1 161(ODU0LP1/ODU0LP1)-2
5(TX3/RX3)-1 203(ClientLP3/ClientLP3)-1 162(ODU0LP2/ODU0LP2)-1
6(TX4/RX4)-1 3 162(ODU0LP2/ODU0LP2)-2
1 205(ClientLP5/ClientLP5)-1 163(ODU0LP3/ODU0LP3)-1 2
7(TX5/RX5)-1 163(ODU0LP3/ODU0LP3)-2
8(TX6/RX6)-1 207(ClientLP7/ClientLP7)-1 164(ODU0LP4/ODU0LP4)-1
9(TX7/RX7)-1 164(ODU0LP4/ODU0LP4)-2
10(TX8/RX8)-1
TOM Cross-connect module Cross-connect module Cross-connect module
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
A cross-connection can be configured between any client-side port and any ClientLP port.
Procedure
Step 1 Set the state of the TN52TOM board.
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
Set Work Mode to NON-CASCADING, and Port Working Mode to ODU1_ODU0 mode
(OTU1->ODU1->ODU0).
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, set Port Working Mode for a ClientLP port. It is
recommended to select the port that is carrying the service channel specified in the network
plan. Double-click the Port Working Mode field and set it to ODU1_ODU0 mode
(OTU1->ODU1->ODU0).
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Configure the working mode for the ports on the TN52TOM board as OTN.
Because the service type is OTU1, Service Mode must be set to OTN for the ports. It is
recommended to select the port that is carrying the service channel specified in the network plan.
1. In the NE Explorer, select the TN52TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Channel from the drop-down list.
3. Click the Basic Attributes tab and select a client-side port. Double-click the Service
Mode field and set it to OTN.
4. Click Apply.
Step 4 Set the service type to OTU1 for the ClientLP ports. It is recommended to select the ClientLP
port that is carrying the service channel specified in the network plan.
1. Click the Advanced Attributes tab and select a ClientLP port.
2. Double-click the Service Type field and choose OTU1.
3. Click Apply.
Step 5 Configure intra-board client-side cross-connections.
Configure an intra-board bidirectional OTU1 cross-connection between a client-side port and a
ClientLP port. Ensure that the client-side and ClientLP ports are identical to those configured
in steps 3 and 4.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level to OTU1, and set other parameters as required. The following figure
shows an example of configuring a bidirectional OTU1 cross-connection between the 3
(RX1/TX1) port and the 201(ClientLP1/ClientLP1) port.
4. Click OK. The newly created cross-connection is displayed in the user interface.
Step 6 Optional: Set the state of the TN52TOM board.
After these configurations are complete, set the state to IS, which indicates that the board is in
service.
1. Right-click the board in the Slot Layout pane and choose State > IS.
----End
be configured so an ESC channel is available between the NE equipped with the TN52TOM
board and its connected NEs.
Application Diagram
Figure 6-31 shows the position of the TN52TOM board in a WDM system where the TN52TOM
board works in non-cascading ODU1 tributary mode.
Figure 6-31 Position of the TN52TOM board in a WDM system (scenario 12: OTU1->ODU1-
>Any->ODU0)
8xODU0 1xOTU2 1xOTU2 8xODU0
TOM TOM
1 1
1 1 M M 1 1
U U
X X
4×ODU1
8×ODU0
4×OTU1
32×Any
64×Any
8×ODU0
4×ODU1
4×OTU1
64×Any
32×Any
N N
8×Any
8×Any
OTU1 / / OTU1
S D S
D
2 M 2
M
U U
4 8 8 8 8 4
X X
Cross-Connection Diagram
Create a cross-connection between the internal client-side and ClientLP ports on the TN52TOM
board, as marked (1) in Figure 6-32.
Figure 6-32 Cross-connection diagram for the TN52TOM board (scenario 12: OTU1->ODU1-
>Any->ODU0)
WDM
161(ODU0LP1/ODU0LP1)-1 side
161(ODU0LP1/ODU0LP1)-2
162(ODU0LP2/ODU0LP2)-1
Other board 162(ODU0LP2/ODU0LP2)-2
163(ODU0LP3/ODU0LP3)-1
163(ODU0LP3/ODU0LP3)-2
Cross-connect 164(ODU0LP4/ODU0LP4)-1
module 164(ODU0LP4/ODU0LP4)-2
Client WDM
side side
3(TX1/RX1)-1 201(ClientLP1/ClientLP1)-1 233(AnyLP1/AnyLP1)-1 237(AnyLP5/AnyLP5)-1
1 2 3 4
237(AnyLP5/AnyLP5)-8
4(TX2/RX2)-1 203(ClientLP3/ClientLP3)-1 233(AnyLP1/AnyLP1)-8 238(AnyLP6/AnyLP6)-1
234(AnyLP2/AnyLP2)-1
5(TX3/RX3)-1 205(ClientLP5/ClientLP5)-1 238(AnyLP6/AnyLP6)-8
234(AnyLP2/AnyLP2)-8
6(TX4/RX4)-1 207(ClientLP7/ClientLP7)-1 235(AnyLP1/AnyLP1)-1 241(AnyLP9/AnyLP9)-1
The internal cross-connection of the board, which needs to be configured on the NMS
The straight-through of the board, which does not need to be configured on the NMS
The client side of the TOM board are cross-connected to the WDM side of other boards,
which needs to be configured on the NMS
NOTE
A cross-connection can be configured between any client-side port and any ClientLP port.
Procedure
Step 1 Set the state of the TN52TOM board.
Before configuring the TN52TOM board, set the board status to OOS, which indicates that the
board is out of service.
1. Right-click the board in the Slot Layout pane and choose State > OOS from the shortcut
menu.
1. In the NE Explorer, select the TN52TOM board and choose Configuration > Working
Mode in the navigation tree.
2. In the Board Working Mode pane, double-click the Work Mode field and set it to NON-
CASCADING.
3. Click Apply.
4. In the Port Working Mode pane, set Port Working Mode for a ClientLP port. It is
recommended to set a working mode for the port that is carrying the service channel
specified in the network plan. Double-click the Port Working Mode field and set it to
ODU1_ANY_ODU0 re-encapsulation mode (OTU1->ODU1->Any->ODU0).
5. Click Apply.
6. Click Query. Confirm that the query results are the same as the preset values.
Step 3 Configure the service mode for the ports on the TN52TOM board as OTN.
Because the service type is OTU1, Service Mode must be set to OTN for the ports. It is
recommended to select the port that is carrying the service channel specified in the network plan.
1. In the NE Explorer, select the TN52TOM board and choose Configuration > WDM
Interface in the navigation tree.
2. Click By Card/Channel and choose Channel from the drop-down list.
3. Click the Basic Attributes tab and select a client-side port. Double-click the Service
Mode field and choose OTN.
4. Click Apply.
Step 4 Set the service type to OTU1 for the ClientLP ports. It is recommended to select the ClientLP
port that is carrying the service channel specified in the network plan.
1. Click the Advanced Attributes tab and select a ClientLP port.
2. Double-click the Service Type field and set it to OTU1.
3. Click Apply.
1. In the NE Explorer, select the NE and choose Configuration > Electrical Cross-
Connection Service Management in the navigation tree.
2. In the Electrical Cross-Connection Service Configuration pane, click New. The Create
Cross-Connection Service dialog box is displayed.
3. Set Service Level to OTU1, and set other parameters as required. The following figure
shows an example of configuring a bidirectional OTU1 cross-connection between the 3
(RX1/TX1) port and the 201(ClientLP1/ClientLP1) port.
After these configurations are complete, set the state to IS, which indicates that the board is in
service.
1. Right-click the board in the Slot Layout pane and choose State > IS.
----End
5. Right-click the board in the Slot Layout pane and choose State > IS.
5. Right-click the board in the Slot Layout pane and choose State > IS.
Context
After the initial network configuration of an NE is completed, check the NE communication
status to determine whether the configuration is correct. You can determine that the NE
communication status is normal if information about the NMS or other NEs is displayed in the
TID IP area.
Procedure
Step 1 In the NE Explorer, choose Communication > TID IP from the Function Tree.
Step 2 Click Query.
----End
Follow-up Procedure
If no information about the NMS or other NEs is displayed in the TID IP area, perform the
following checks on NE:
l Check the fiber connections against the fiber connection diagram in the network design.
Correct fiber connections if there are incorrect ones.
l Test the transmit and receive optical power on the line. Handle the line fault if the line
attenuation is abnormal.
l Check the network cable connections against the network cable connection diagram in the
network design. Correct network cable connections if there are incorrect ones.
l Test the transmit and receive optical power of the OSC board or the DAS1 board if OSC
communication is used. Do as follows if the transmit or receive optical power is abnormal:
– Check the fiber connections between the OSC and FIU boards.
– Check the fiber connections between TM and RX ports, and the fiber connections
between RM and TX ports for the DAS1 board.
– If the OSC or DAS1 board receive optical power queried on the Web LCT is remarkably
lower than the IN port input optical power measured using an optical power meter, clean
the fiber connected to the IN port. If the fault persists, replace the board. If the OSC or
DAS1 board receive optical power exceeds the permitted range, add fixed optical
attenuators (FOAs) with reference to OSC commissioning requirements. If the OSC or
DAS1 board transmit optical power exceeds the permitted range, replace the board.
l Check the status of the DCC channels to be used if ESC communication is used. Choose
Communication > DCC Channel Configuration. In the displayed window, check the
value of Channel State for the DCC channels to be used. If RX_F, RX_F&TX_F, or TX_F
is displayed for any channel, perform the following checks:
– Check the WDM-side transmit and receive optical power of the OTU board.
– Check whether electrical cross-connections have been correctly configured for boards
requiring cross-connections to implement ESC communication. An example of such
boards is the TOM board.
– Check whether Protocol is set to TRANSPARENT for all unused ESC channels. If
not, do as follows: Choose Communication > DCC Channel Configuration. In the
displayed window, select all unused ESC channels and set Protocol to
TRANSPARENT. Select GCC0, GCC12, and GCCA for each unused ESC channel to
change Protocol to Transparent.
– Check whether the configuration of the remote NE is completed.
to an SCC board, you actually back up the NE data to the flash memory of the SCC board. After
a power-off reset occurs on the NE, the SCC board automatically reads the configuration data
from the flash memory and applies the data to the boards on this NE.
Prerequisites
You must have logged in to an NE.
The NE must be configured properly.
Precautions
NOTE
After backing up an NE database to an SCC board, you can restore the NE database from the SCC board
by performing a warm or cold reset on the SCC board.
Procedure
1. Select one or more NEs in the NE list. Click Back Up NE Database > Back Up to SCC.
NOTE
The Web LCT takes a few minutes to back up the NE database. Do not perform any operation in the
process of backup.
2. Click OK in the confirmation dialog box.
3. Click Close in the Operation Result dialog box is displayed.
Procedure
Step 1 Highlight the NE that you are logged in to, and click the NE Logout at the bottom of the screen.
Step 2 Physically disconnect the Web LCT from the NE
Step 3 Close the browser.
Step 4 Double-click the stopweblct.bat file at "WebLCT\WebLCT\Tomcat" to stop the Web LCT
application.
----End
NOTE
The OptiX OSN 8800 subrack indicators are on the panel of the fan tray assembly.
The meanings of the board indicators are listed in Table 7-3, Table 7-4, and Table 7-5.
Table 7-7 Meanings of the FAN indicator (OptiX OSN 6800A/OptiX OSN 3800A)
Indicator Name Status Description
STAT Fan indicator On (green) The mode of the fan is IS-NR. The
fan is normal.
Prerequisites
Before the test, make sure that the laser is closed. After the fiber jumper is connected to the
board, open the laser.
Impact on System
The services on the tested board are interrupted.
Precaution
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
WARNING
Wear a well-grounded ESD wrist strap whenever you touch any equipment. Make sure that the
wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD socket in
the subrack.
CAUTION
Keep the optical connector and end face clean. Cover the fiber immediately after the fiber is
removed.
Procedure
Step 1 Turn on the optical power meter, set the unit of the optical power to dBm, and set the operating
wavelength of the meter to 1550 nm.
Step 2 The test of optical power consists of the following two parts:
l Testing the receive optical power: In this test, remove the fiber jumper that is connected to
the receive optical port and connect the fiber jumper to the optical power meter.
l Testing the transmit optical power: In this test, remove the fiber jumper that is connected
to the transmit optical port. Connect one end of a known-good fiber jumper to the transmit
optical port and the other end to the optical power meter.
Step 3 Open the laser, after the optical power value displayed on the meter is stable, record the value.
Step 4 Close the laser, connect the removed fiber jumper back to the optical port, and then open the
laser.
----End
Prerequisites
The light source must exist and the transmit optical power must be stable.
The checked fiber does not have services or services are interrupted.
Impact on System
During the test, the services in the tested fiber are interrupted.
Precaution
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
WARNING
Wear a well-grounded ESD wrist strap whenever you touch any equipment. Make sure that the
wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD socket in
the subrack.
CAUTION
Keep the optical connector and end face clean. Cover the fiber immediately after the fiber is
removed.
Procedure
Step 1 Turn on the optical power meter, set the unit of the optical power to dBm, and set the operating
wavelength of the meter to 1550 nm.
Step 2 Connect one end of a known-good fiber jumper to the light source.
Step 3 Connect the other end of the known-good fiber jumper to the optical power meter.
Step 4 Enable the laser of the light source that is connected to the fiber jumper.
Step 5 Measure the transmit optical power P1 of the light source by using the optical power meter.
Step 7 Connect one end of the tested fiber jumper to the light source.
Step 8 Connect the other end of the tested fiber jumper to the optical power meter.
Step 9 Measure the transmit optical power P2 of the light source by using the optical power meter.
l If the difference between P1 and P2 is less than 1 dB, it indicates that the fiber connection
is normal.
l If the difference between P1 and P2 is greater than 1 dB, it indicates that the fiber connection
is faulty.
----End
Prerequisites
The laser that is connected to the fiber jumper must be disabled before the replacement.
Impact on System
The services on the fiber jumper where the fiber jumper is replaced are interrupted.
Precaution
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
WARNING
Wear a well-grounded ESD wrist strap whenever you touch any equipment. Make sure that the
wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD socket in
the subrack.
CAUTION
Before installing a fiber jumper, attach temporary labels to the two ends for distinguishing.
CAUTION
When replacing the fiber jumper that leads out the open rack, make sure that the new fiber jumper
is routed along the route for the original fiber jumper. In addition, the open corrugated pipe is
used to protect the new fiber jumper.
CAUTION
Keep the optical connector and end face clean. Cover the fiber immediately after the fiber is
removed.
NOTE
The type of the fiber jumper before and after the replacement must be the same.
Procedure
Step 1 Disconnect the two ends of the fiber jumper to be replaced.
Step 2 Insert the new fiber connectors into the corresponding optical ports on the board.
Step 3 Lead the optical fibers out from the subrack through the holder at the subrack bottom and the
hole at the subrack side.
Step 4 Pass the optical fibers to the corresponding subrack side along the space at both sides of the
open rack.
Step 5 Make the optical fibers pass through the hole at the subrack side and the holder at the subrack
bottom.
Step 6 Insert the fiber connectors into corresponding optical ports on the board.
Step 7 Coil the redundant optical fibers around the fiber spool at the side of the subrack.
Step 8 After the fiber installation, insert fiber plugs in idle ports and cover idle fibers with fiber caps.
Step 9 Label the new fiber jumper according to the methods and specifications of labeling for the
original fiber jumper.
Step 10 Bind the new fiber jumper.
NOTE
After replacing the fiber jumper, you should recover the laser status to the status before the replacement.
----End
Prerequisites
The end face of the fiber must be clean.
Wear an ESD wrist strap before carrying out this operation.
Precautions
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to eyes, or even blindness.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
Procedure
Step 1 Remove protective cap on the LC/PC connector.
Step 2 Align the LC/PC connector to the optical port on the board.
Step 3 Push the connector gently in along the guide rail until it clicks.
LC/PC connector
Protective cap
----End
Prerequisites
The end face of the fiber must be clean.
Precautions
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
Procedure
Step 1 Clamp the fiber connector from the up and down sides by hand or with optical fiber extractor.
Press down the hook switch.
NOTE
The LC/PC fiber connector can be directly pulled out by hand. However, if the optical fibers are arranged
densely, a dedicated optical fiber extractor shall be used. Figure 7-2 shows the tweezers-like optical fiber
extractor.
LC/PC connector
Protective cap
----End
Prerequisites
The end face of the fiber must be clean.
Precautions
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
DANGER
Raman amplifier emits strong light. Do not insert or remove the fiber connector when the laser
is working, to avoid damage to human body.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
Procedure
Step 1 Remove dust-proof protection cover on the LSH/APC fiber connector.
Step 2 Align the connector on optical fiber with the optical port of the board.
Protective LSH/APC
slidding cover connector
----End
Prerequisites
The end face of the fiber must be clean.
Precautions
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
DANGER
Raman amplifier emits strong light. Do not insert or remove the fiber connector when the laser
is working, to avoid damage to human body.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
Procedure
Step 1 Clamp the connector by hand.
The LSH/APC fiber connector has a dust-proof protection cover. When the connector is pulled out from
the optical port, the protection cover will be closed automatically so as to protect against dust and intense
light signals output.
Protective LSH/APC
slidding cover connector
----End
Prerequisites
The end face of the fiber must be clean.
Wear an ESD wrist strap before carrying out this operation.
Precautions
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
Procedure
Step 1 Remove protective cap on the FC/PC connector.
Step 2 Align the keyed ridge on the FC/PC fiber connector with the concave slot of the optical port.
Step 3 Push in the connector with proper force not to damage the fiber connector. After the connector
is seated properly, the keyed ridge shall match the concave slot and the optical connector cannot
be turned around.
Step 4 When the optical fiber connector is pushed to the bottom, turn the outer ring of the optical
connector clockwise to secure the optical fiber connector.
Protective cap
FC/PC connector
----End
Prerequisites
The end face of the fiber must be clean.
Precautions
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
Procedure
Step 1 Turn the outer ring of the fiber connector anticlockwise.
Protective cap
FC/PC connector
----End
Prerequisites
The end face of the fiber must be clean.
Precautions
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
Procedure
Step 1 Remove protective cap on the SC/PC connector.
Step 2 Align the keyed ridge on the SC/PC fiber connector with the concave slot of the optical port.
Step 3 Push the connector in with proper force. After the connector is seated properly, the keyed ridge
shall match the concave slot.
Protective cap
SC/PC connector
----End
Prerequisites
The end face of the fiber must be clean.
Precautions
DANGER
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
CAUTION
Wear a well-grounded ESD wrist strap whenever you touch any equipment or board. Make sure
that the wrist strap fully touches your skin. Insert the connector of the ESD strap into the ESD
socket in the subrack.
Procedure
Step 1 Clamp the SC/PC fiber connector from the up and down sides with the optical fiber extractor.
Step 2 Pull out the connector slowly from the optical port with force.
Protective cap
SC/PC connector
----End
7.5.1 Overview
Overview of the purpose and procedure of cleaning optical fiber connectors, the items that may
cause pollution to optical connectors are also described here.
Cleaning optical components is to remove dust or other dirt to avoid performance degradation
of optical transmission systems. Here describes how to inspect and clean fiber connectors used
in fiber optic connections.
The following items should be removed because they pollute optical connectors that are
extensively adopted in optical transmission systems:
l Dust
l Oils (frequently from human hands)
l Film residues (condensed from vapors in the air)
l Powdery coatings (left after water or other solvents evaporate)
Dust is the most common dirt in optical connectors. Even small dust that can be seen only under
a microscope can affect the quality of optical signals, degrade the system performance and cause
potential instability in network operation.
A one-micrometer dust granule on an optical connector of a single mode fiber can block 1%
light and cause 0.05 dB lost. A nine-micrometer dust granule that cannot be seen by human eyes
can block an entire fiber core. Therefore, small dirt even that cannot be seen by human eyes
should be removed.
NOTE
Before you connect any optical component, make sure that you have inspected and cleaned the component.
General Procedure
Table 7-9 below describes the general procedure of how to inspect and clean the optical fiber
connectors.
Table 7-9 General procedure of inspecting and cleaning the optical fiber connectors
Operation Details
Cleaning Optical Fiber Connectors Using See "7.5.5 Cleaning Optical Fiber Connectors
Cartridge Cleaners Using Cartridge Cleaners"
Cleaning Optical Fiber Connectors Using See "7.5.6 Cleaning Optical Fiber Connectors
Lens Tissue Using Lens Tissue"
Cleaning Optical Adapters Using Optical See "7.5.7 Cleaning Optical Adapters Using
Cleaning Sticks Optical Cleaning Sticks"
NOTE
The air filter caps made of soft rubber are not recommended, which tends to collect dust and sundries. This
type of caps provides poor dustproof function.
Figure 7-14 Cleaning stick for the SC and FC optical ports (for reference only)
Precautions
WARNING
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
Use a fiberscope equipped with a safety device or a desktop video fiberscope when you inspect
the optical connectors. If one is not available, turn off the lasers and disconnect both ends of the
fiber before you inspect the optical connectors
CAUTION
Electro static discharge (ESD) is hazardous to the electronic equipment. Use proper handlings
to prevent damage to the electronic equipment. Failure to follow this caution can cause
equipment damage and/or loss of traffic
Procedure
Step 1 Turn off the lasers before the inspection. Disconnect both ends of the fiber to be inspected.
Step 2 Test the optical power using a power meter. Ensure that the laser is turned off.
Step 3 Use a fiberscope to inspect the fiber to check if there is any dirt or damage. See the examples
shown below.
l For an image of the intact fiber optic surface through a fiberscope that can be used
successfully in the equipment, see Figure 7-16.
l For images of fibers through a fiberscope with imperfections that can impair the function of
the assembly, see Figure 7-17. The image on the left shows clearly a damaged fiber. Severely
damaged fibers must not be used in the system equipment. Otherwise, permanent and severe
damage to the assembly can occur. The image on the right shows a fiber that is suspect. If
the output power is within an acceptable range, the fiber might not cause any damage to the
assembly. If the output power is unstable or falls outside the acceptable range, however, the
fiber can cause damage to the assembly and must not be used.
NOTE
The views shown do not represent the entire surface of the fiber optic. Much of the surface is the metal
connector and only the 800-micron core is the actual fiber.
l For details on acceptable and unacceptable fibers, see Figure 7-18, Figure 7-19 and Figure
7-20.
Step 4 If any dirt is detected, clean the optical connector. For details, see "7.5.5 Cleaning Optical Fiber
Connectors Using Cartridge Cleaners" and "7.5.6 Cleaning Optical Fiber Connectors Using
Lens Tissue".
----End
Prerequisites
Before cleaning, inspect the fiber optic surface with a fiberscope or a magnifier to determine the
extent to which the fiber optic might be damaged or dirty. Clean the fiber optic only in the case
that there are flaws on it. If there are not, do not clean it. That is because the cleaning itself might
introduce dust, dirt, or cause potential damage to the fiber optic.
The following procedure provides the steps to clean the fiber connectors using cartridge type
cleaners. There are several types of cartridge cleaners. The following describes a type of
CLETOP cassette cleaner.
Precautions
WARNING
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
CAUTION
ESD is hazardous to the electronic equipment. Use proper handlings to prevent damage to the
electronic equipment. Failure to follow this caution can cause equipment damage and/or loss of
traffic.
Procedure
Step 1 Turn off the lasers before the inspection. Disconnect both ends of the fiber to be inspected.
Step 2 Use a power meter to measure and ensure that there is no laser light on the optical connector.
Step 3 Press down and hold the lever of the cassette cleaner, and the shutter slides back and exposes a
new cleaning area. See Figure 7-21.
Step 4 Place the fiber tip lightly against the cleaning area so that the end face is flat on the cleaning
area
Step 5 Drag the fiber tip lightly on one cleaning area in the direction of the arrow once. See Figure
7-22. Do it again on the other cleaning area in the same direction as the first time once. See
Figure 7-23.
CAUTION
Do not scrub the fiber against fabric or clean over the same cleaning area more than once.
Otherwise, the connector can be dirtied or damaged.
Figure 7-22 Dragging the fiber tip lightly on one cleaning area
Figure 7-23 Dragging the fiber tip lightly on the other cleaning area
Step 6 Release the lever of the cassette cleaner to close the cleaning area.
Step 7 Use a fiberscope to inspect the adapter to check if there is any dirt. For details see the examples
shown in 7.5.4 Inspecting Optical Connectors. If the optical adapter is still dirty, repeat the
Step 1 to Step 6.
Step 9 Turn on the lasers after you connect the fiber to the board.
----End
Prerequisites
Before cleaning, inspect the fiber optic surface with a fiberscope or a magnifier to determine the
extent to which the fiber optic might be damaged or dirty. Clean the fiber optic only in the case
that there are flaws on it. If there are not, do not clean it. That is because the cleaning itself might
introduce dust, dirt, or cause potential damage to the fiber optic.
The following procedure provides the steps to clean the fiber connectors using lens tissue. Use
only the special materials for cleaning the fiber connectors. See the local site practices.
Precautions
WARNING
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
CAUTION
ESD is hazardous to the electronic equipment. Use proper handlings to prevent damage to the
electronic equipment. Failure to follow this caution can cause equipment damage and/or loss of
traffic.
Procedure
Step 1 Turn off the lasers before the inspection. Disconnect both ends of the fiber to be inspected.
Step 2 Use a power meter to measure and ensure that there is no laser light on the optical connector.
CAUTION
Do not scrub the fiber against fabric or clean over the same cleaning area more than once. Failure
to comply can result in connector dirt or damage.
CAUTION
Move the fiber connector in the same direction when you wipe the fiber connector on the lens
tissue.
Figure 7-24 Cleaning the fiber tip with the lens tissue on the desk
Figure 7-25 Cleaning the fiber tip with the lens tissue on the hand
Step 5 Repeat Step 4 several times on the areas of the lens tissue that have not been used.
Step 6 Use the compressed air to blow off the fiber tip.
NOTE
l When you use the compressed air, keep the injector nozzle as close as possible to the fiber connector
surface without touching it.
l When you use the compressed air, first spray it into the air as the initial spray of compressed air can
contain some condensation or propellant. Such condensation leaves behind a filmy deposit.
l If the compressed air is not available, a clean roll can be used.
Step 7 Use a fiberscope to inspect the adapter to check if there is any dirt. For details, see the examples
shown in 7.5.4 Inspecting Optical Connectors. If the optical adapter is still dirty, repeat the
Step 1 to Step 6.
Step 8 Do not touch the fiber connector after you clean it. Connect it to the optical port board at once.
If it is not used for the time being, put a protective cap on it.
NOTE
Step 9 Turn on the lasers after you connect the fiber to the board.
----End
Prerequisites
There are several types of optical cleaning sticks and cotton swabs that can be used. See the local
site practices. You can obtain these tools and materials from a fiber cable and connector
manufacturer.
Precautions
WARNING
Laser is dangerous. The light is not visible to the eyes with or without laser protective glasses.
Do not look into optical connectors or ports. Failure to follow this warning can cause damage
to the eyes, or even blindness.
CAUTION
ESD is hazardous to the electronic equipment. Use proper handlings to prevent damage to the
electronic equipment. Failure to follow this caution can cause equipment damage and/or loss of
traffic.
Procedure
Step 1 Turn off the lasers before the inspection. Disconnect both ends of the fiber to be inspected.
Step 2 Test the optical power using a power meter. Ensure that the laser is turned off.
Step 3 Select the cleaning stick with a proper diameter for a certain type of the adapter.
NOTE
For the SC and FC optical port, use the cleaning stick with a diameter of 2.5 mm( 0.1 in.); for the LC optical
port, use the cleaning stick with a diameter of 1.25 mm( 0.05 in.). See Figure 7-14 and Figure 7-15.
Step 4 Place a small amount of cleaning solvent on the optical cleaning stick.
Step 5 Place the optical cleaning stick lightly on the optical adapters so that cleaning solvent is against
the fiber tip. Hold the stick straight out from the adapter and turn the stick clockwise one circuit.
Make sure that there is direct contact between the stick tip and fiber tip.
Step 6 Use the compressed air to blow off the fiber tip.
NOTE
l When you use the compressed air, keep the injector nozzle close to the connector surface without
touching it.
l When you use the compressed air, first spray it into the air as the initial spray of compressed air can
contain some condensation or propellant. Such condensation leaves behind a filmy deposit.
Step 7 Use a fiberscope to inspect the adapter to check if there is any dirt. For details, see the examples
shown in "7.5.4 Inspecting Optical Connectors". If the optical adapter is still dirty, repeat the
Step 1 to Step 6.
Step 8 Connect the fiber to the board, or put a protective cap on the port.
Step 9 Turn on the lasers after you connect the fiber to the board.
----End
Background Information
Figure 7-26 shows the difference between software loopback and hardware loopback.
Software Hardware
loopback loopback
Receiving module
Precautions
CAUTION
When you perform hardware loopback, add an optical attenuator according to the range of the
optical power received by different boards.
Procedure
Step 1 Before a hardware loopback, use an optical power meter to measure the optical power of the
output optical port (OUT).
Step 2 Based on the received optical power range of boards, select a proper fixed attenuator.
Step 3 Use fiber jumper to connect the output optical port to the input port on the board, to perform a
loopback.
----End
Prerequisites
You must be an NM user with "NE maintainer" authority or higher.
Impact on System
In the case of the SCC board, the impacts of resetting the board are as follows:
l The communication between the U2000 and the SCC board and between the SCC board
and other boards stops.
Background Information
Warm reset of the SCC board:
l After a warm reset of the SCC board, FPGA of the board is not updated, and the
configuration data in the memory of the board remains the same. When a fault is detected,
a warm reset is preferred.
l A warm reset can be performed in any of the following methods:
– By using the U2000: It is applicable to remote maintenance. In this method, the
communication between the U2000 and the SCC board must be normal.
– By pressing the RESET button on the SCC board: It is applicable to field maintenance
or the situation where the communication between the U2000 and the SCC board stops.
l After a warm reset of other boards, FPGA of the boards is not updated, and the configuration
data in the memory of the board remains the same.
l A warm reset can be performed in the following method:
– By using the U2000: It is applicable to remote maintenance. In this method, the
communication between the U2000 and the SCC board and between the SCC board and
other boards must be normal.
Prerequisites
You must be an NM user with "NE maintainer" authority or higher.
Impact on System
If you perform a cold reset of the SCC board, the U2000 stops communicating with the SCC
board, and the SCC board stops communicating with the other boards.
If you perform a cold reset of the TN16XCH board, the U2000 stops communicating with the
TN16XCH board, and the TN16XCH board stops communicating with the other boards.
A cold reset of other boards affects the running services. If a reset of such a board is failing, it
affects the communication between the board and the system control board, or even interrupts
services.
A cold reset on boards other than the SCC board affects the running services. A reset failure on
these boards affects the communication between the board and the system control board, or even
interrupts services.
Background Information
Cold reset of the SCC board:
l When the SCC board is faulty, perform a warm reset of the SCC board. If the fault persists
after a warm reset, perform a cold reset.
l The methods of performing a cold reset of the SCC board are as follows:
– Perform a cold reset by removing and then inserting the SCC board. This method applies
to field maintenance or scenarios where the SCC board fails to communicate with the
U2000.
– Perform a cold reset on the U2000. This method applies to remote maintenance where
the communication between the SCC board and the U2000 is normal.
Cold reset of the TN16XCH board:
l When the TN16XCH board is faulty, perform a warm reset of the TN16XCH board. If the
fault persists after a warm reset, perform a cold reset.
l The methods of performing a cold reset of the TN16XCH board are as follows:
– Perform a cold reset by removing and then inserting the TN16XCH board. This method
applies to field maintenance or scenarios where the TN16XCH board fails to
communicate with the U2000.
– Perform a cold reset on the U2000. This method applies to remote maintenance where
the communication between the TN16XCH board and the U2000 is normal.
Cold reset of the other boards:
l After a cold reset of other boards, FPGA of the boards is updated, which is service-affecting.
Perform a warm reset of the board, if the fault persists after a warm reset, perform a cold
reset.
l A cold reset can be performed in any of the following methods:
– By using the U2000: It is applicable to remote maintenance. In this method, the
communication between the U2000 and the system control board must be normal, and
the communication between the board and the system control board must be normal.
– By removing and then inserting the board: It is applicable to field maintenance or the
situation where the communication between the board and the system control board
stops.
8 Parts Replacement
8.1.1 Prerequisite
For the operations on the NMS, you must be an NMS user with "NE operator " authority or
higher.
When other protection is configured, replacing a board will cause service interruption.
Optical
amplifier board
Variable optical
attenuator board
Optical
protection board
Dispersion
equalizing board
Clock board For OptiX OSN 8800, 1+1 protection is configured for clock boards.
Replacing a clock board will trigger switching on the active and standby
clock boards, therefore, services are not affected.
8.1.4 Precautions
This section describes the precautions to be taken before you replace optical transponder boards,
line boards, tributary boards, and clock boards.
CAUTION
Before connecting a fiber to the input optical port of a board, measure the optical power. You
can directly connect a fiber to the input optical power of the board only when the measured
optical power is within the permitted range of the receive optical power for the optical module
on the board. If the measured optical power is beyond the permitted range, you must add a VOA
before connecting the fiber to prevent the receiver optical module from being burned or damaged.
The overload optical power point of an APD receiver laser is only -9 dBm, which must be
considered with caution to prevent the optical module from being burned or damaged.
l Before replacing the board, ensure that the wavelength of the new board is consistent with
that of the original board.
NOTE
The wavelength of the board is printed on the PCB board.
l Before replacing the board, test the input optical power. Prevent the input optical power
from crossing the overload point; otherwise, the receiver optical module will be burned or
damaged.
l Before replacing the board, query and record the 15-minute BER before FEC at the receive
end of the link.
l If the client 1+1 protection is configured, perform the following steps:
1. Before replacing the board, query the working status of the board to be replaced.
2. If the board to be replaced is the current working board, perform an active/standby
switchover on the U2000.
NOTE
The channel status of the protection board must be normal. Otherwise, replacing the faulty
board causes a service interruption.
At the opposite end of the link, perform a manual switchover on the U2000 at the same time.
3. After replacing the board, query the state of the new board and ensure that it is the
working board.
l If the SNCP protection is configured, perform the following steps:
1. Before replacing the board, query the working status of the board to be replaced.
2. If the board to be replaced is the working board and the service sink does no reside
on the board, perform an active/standby switchover on the U2000.
NOTE
The channel status of the protection board must be normal. Otherwise, replacing the faulty
board causes a service interruption.
At the opposite end of the link, perform a manual switchover on the U2000 at the same time.
3. After replacing the board, query the state of the new board and ensure that it is the
working board.
l After replacing the board, query the wavelength of the new board on the U2000. Make sure
the wavelength is the same as that of the original board.
NOTE
If the replaced board is a tunable OTU, after the board is replaced, the SCC automatically delivers
the wavelength configuration of the original board.
l After replacing the board, query the 15-minute BER before FEC at the receive end of the
link. Make sure that the BER before FEC does not deteriorate greatly from the value before
board replacement.
Line Board
CAUTION
Before connecting a fiber to the input optical port of a board, measure the optical power. You
can directly connect a fiber to the input optical power of the board only when the measured
optical power is within the permitted range of the received optical power for the optical module
on the board. If the measured optical power is beyond the permitted range, you must add a VOA
before connecting the fiber to prevent the receiver optical module from being burned or damaged.
The overload optical power point of an APD receiver laser is only -9 dBm, which must be
considered with caution to prevent the optical module from being burned or damaged.
l Before replacing the board, ensure that the wavelength of the new board is consistent with
that of the original board.
NOTE
The wavelength of the board is printed on the PCB board.
l Before replacing the board, query and record the 15-minute BER before FEC at the receive
end of the link.
l Before replacing the board, test the input optical power. Prevent the input optical power
from crossing the overload point; otherwise, the receiver optical module will be burned or
damaged.
l If the ODUk SNCP protection or ODUk SPRing protection (four-fiber ring) is configured,
perform the following steps:
1. Before replacing the board, query the working status of the board to be replaced.
2. If the board to be replaced is the current working board, perform an active/standby
switchover on the U2000.
NOTE
The channel status of the protection board must be normal. Otherwise, replacing the faulty
board causes a service interruption.
At the opposite end of the link, perform a manual switchover on the U2000 at the same time.
3. After replacing the board, query the state of the new board and ensure that it is the
working board.
l After replacing the board, query the wavelength of the new board on the U2000. Ensure
the wavelength is the same as that of the original board.
l After replacing the board, query the 15-minute BER before FEC at the receive end of the
link. Ensure that the BER before FEC does not deteriorate greatly from the value before
board replacement.
Tributary Board
CAUTION
Before connecting a fiber to the input optical port of a board, measure the optical power. You
can directly connect a fiber to the input optical power of the board only when the measured
optical power is within the permitted range of the received optical power for the optical module
on the board. If the measured optical power is beyond the permitted range, you must add a VOA
before connecting the fiber to prevent the receiver optical module from being burned or damaged.
The overload optical power point of an APD receiver laser is only -9 dBm, which must be
considered with caution to prevent the optical module from being burned or damaged.
l Before replacing the board, test the input optical power. Prevent the input optical power
from crossing the overload point; otherwise, the receiver optical module will be burned or
damaged.
l If the client 1+1 protection or tributary SNCP protection is configured, perform the
following steps:
1. Before replacing the board, query the working status of the board to be replaced.
2. If the board to be replaced is the current working board, perform an active/standby
switchover on the U2000.
NOTE
The channel status of the protection board must be normal. Otherwise, replacing the faulty
board causes a service interruption.
At the opposite end of the link, perform a manual switchover on the U2000 at the same time.
3. After replacing the board, query the state of the new board and ensure that it is the
working board.
Clock Board
Before replacing the board, perform an active/standby switchover on the U2000.
NOTE
For OptiX OSN 8800 T32, assume that the clock board to be replaced is located in slot 42, it is the main
clock board, the clock board in slot 44 works normally and the subrack where it is located has no BUS-
ERR alarm.
For OptiX OSN 8800 T64, assume that the clock board to be replaced is located in slot 75, it is the main
cross-connect board, the clock board in slot 86 works normally and the subrack where it is located has no
BUS-ERR alarm.
LOG
Original Substitute Substitution Rules
Board Board
TN11LOG TN12LOG The TN12LOG can be created as TN11LOG on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN12LOG functions as the
TN11LOG.
NOTE
l When both the receive board and transmit board adopt the FEC
code pattern, the substitution applies; when both the receive board
and transmit board adopt the AFEC code pattern, the substitution
does not apply.
l A board with PIN as the receiver type cannot substitute for a board
with APD as the receiver type, because their ranges of receive
optical power are different.
TN12LOG None -
LOM
Original Substitute Substitution Rules
Board Board
TN11LOM TN12LOM The TN12LOM can be created as TN11LOM on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN12LOM functions as the
TN11LOM.
NOTE
l When both the receive board and transmit board adopt the FEC
code pattern, the substitution applies; when both the receive board
and transmit board adopt the AFEC code pattern, the substitution
does not apply.
l A board with PIN as the receiver type cannot substitute for a board
with APD as the receiver type, because their ranges of receive
optical power are different.
TN12LOM None -
LSX
Original Substitute Substitution Rules
Board Board
TN12LSX TN13LSX The TN13LSX can be created as TN12LSX on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN13LSX functions as the
TN12LSX.
NOTE
l When both the receive board and transmit board adopt the FEC
code pattern, the substitution applies; when both the receive board
and transmit board adopt the AFEC code pattern, the substitution
does not apply.
l A board with PIN as the receiver type cannot substitute for a board
with APD as the receiver type, because their ranges of receive
optical power are different.
TN13LSX None -
TMX
Original Substitute Substitution Rules
Board Board
TN11TMX TN12TMX The TN12TMX can be created as TN11TMX on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN12TMX functions as the
TN11TMX.
NOTE
l When both the receive board and transmit board adopt the FEC
code pattern, the substitution applies; when both the receive board
and transmit board adopt the AFEC code pattern, the substitution
does not apply.
l A board with PIN as the receiver type cannot substitute for a board
with APD as the receiver type, because their ranges of receive
optical power are different.
TN12TMX None -
ND2
Original Substitute Substitution Rules
Board Board
TN11ND2 TN12ND2 The TN12ND2 can be created as TN11ND2 on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN12ND2 functions as the
TN11ND2.
NOTE
When both the receive board and transmit board adopt the FEC code
pattern, the substitution applies; when both the receive board and
transmit board adopt the AFEC code pattern, the substitution does not
apply.
TN12ND2 TN53ND2 The TN53ND2 can be created as TN12ND2 on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN53ND2 functions as the
TN12ND2.
NOTE
The TN53ND2 does not support OTU2e services at rate 11.3 Gbit/s on
the WDM side and it cannot substitute for the TN12ND2 in relay mode
at rate 11.3 Gbit/s.
TN52ND2 TN53ND2 The TN53ND2 can be created as TN52ND2 on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN53ND2 functions as the
TN52ND2.
NOTE
The TN53ND2 does not support OTU2e services at rate 11.3 Gbit/s on
the WDM side and it cannot substitute for the TN52ND2 in relay mode
at rate 11.3 Gbit/s.
TN53ND2 None -
NQ2
Original Substitute Substitution Rules
Board Board
TN54NQ2 TN53NQ2 The TN53NQ2 board can be created as TN54NQ2 on the NMS
to function as a TN54NQ2 board. In this scenario, the
TN53NQ2 board only provides the functions of the TN54NQ2
board, and the board software does not need to be upgraded.
TN53NQ2 None -
NS2
TN12NS2 TN53NS On an OptiX OSN 6800 NE of V100R004C04 or a later version or on an OptiX OSN
2 8800 NE, the TN53NS2 board can substitute for the TN12NS2 board without requiring
any software upgrades. After physically replacing the TN12NS2 board with the
TN53NS2 board, the user must create the TN53NS2 board as TN12NS2 on the U2000
to complete the substitution.
NOTE
The substitution can take place only when the TN12NS2 board uses FEC/AFEC-2.
TN52NS2 TN53NS On an OptiX OSN 6800 NE of V100R004C04 or a later version or on an OptiX OSN
2 8800 NE, the TN53NS2 board can substitute for the TN52NS2 board without requiring
any software upgrades. After physically replacing the TN52NS2 board with the
TN53NS2 board, the user must create the TN53NS2 board as TN52NS2 on the U2000
to complete the substitution.
TN53NS2 None -
NS3
TN11NS3 TN52NS3 The TN52NS3 can be created as TN11NS3 on the NMS. The former can
substitute for the latter, without any software upgrade. After substitution, the
TN52NS3 functions as the TN11NS3.
TN52NS3 None -
TN54NS3 None -
TN55NS3 None -
TDX
TN12TDX TN53TDX The TN53TDX can be created as TN12TDX on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN53TDX functions as the
TN12TDX.
TN52TDX TN53TDX The TN53TDX can be created as TN52TDX on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN53TDX functions as the
TN52TDX.
TN53TDX None -
TQX
TN11TQX TN55TQX The TN55TQX can be created as TN11TQX on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN55TQX functions as the
TN11TQX.
TN52TQX TN55TQX The TN55TQX can be created as TN52TQX on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN55TQX functions as the
TN52TQX.
TN53TQX TN55TQX The TN55TQX can be created as TN53TQX on the NMS. The
former can substitute for the latter, without any software
upgrade. After substitution, the TN55TQX functions as the
TN53TQX.
TN55TQX None -
M40
Original Substitute Substitution Rules
Board Board
TN11M40 TN12M40 The TN12M40 board can be created as TN11M40 on the NMS.
The former can substitute for the latter without any software
upgrade. After the substitution, the TN12M40 board functions
as the TN11M40 board. The TN12M40 board occupies two
physical slots and three logical slots while the TN11M40 board
occupies three physical slots. After the substitution, the
remaining one physical slot cannot be used to house any other
board.
TN12M40 None -
M40V
Original Substitute Substitution Rules
Board Board
TN12M40V None -
D40
Original Substitute Substitution Rules
Board Board
TN11D40 TN12D40 The TN12D40 can be created as TN11D40 on the NMS. The
former can substitute for the latter, without any software
upgrade. After the substitution, the TN12D40 board functions
as the TN11D40 board. The TN12D40 board occupies two
physical slots and three logical slots while the TN11D40 board
occupies three physical slots. After the substitution, the
remaining one physical slot cannot be used to house any other
board.
TN12D40 None -
OAU1
Original Substitute Substitution Rules
Board Board
TN13OAU1 None -
OBU1
Original Substitute Substitution Rules
Board Board
TN12OBU1 None -
OBU2
Original Substitute Substitution Rules
Board Board
TN12OBU2 None -
Procedure
Step 1 Select a spare board. Ensure the name, TNxx version, and type of the new board are the same
as those of the original board.
NOTE
If the TNxx versions of the new board and the original board are not the same, you need to determine
whether the new board can be substituted for the original board. For more information regarding the
substitution relationships between boards of different versions, refer to "Substitution Relationship".
Step 3 Right-click the replaced board on the U2000, and choose State > OOS (out of service) in the
short-cut menu, to set the state of the board to OOS.
Step 4 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 5 Inform the onsite maintenance engineer and remove the fibers and cables on the board to be
replaced.
1. Wear a well-grounded ESD wrist strap. Make sure that the wrist strap fully touches your
skin. Insert the connector of the ESD strap into the ESD socket in the subrack.
2. Record the mapping relationships of the board ports and the fibers.
3. Remove the fiber jumpers connecting to the optical interfaces on the board. Keep the optical
connector and end face clean. Cover the fiber immediately after the fiber is removed. The
cable connector must be sealed to avoid short circuit.
2. Grip the ejector levers and apply an outward force until the ejector levers become horizontal
and the connector of the board leave the backplane.
3. Put the replaced board in an ESD bag and attach a maintenance label on the bag. The label
should contain the NE name and fault description.
1 2
Figure 8-3 Removing a board in the interface area of the OptiX OSN 8800 subrack
1 2 3
1
2
3 4
3. Raise the ejector levers of the board using two hands and align the board with the guide
rail of the slot.
4. Slowly slide the board along the guide rail into the slot until it can no longer move forward.
5. Lower the ejector levers to hold the beam of the subrack.
Figure 8-8 Installing a cross-connect board of the OptiX OSN 8800 subrack
1 2
Figure 8-9 Installing a board in the interface area of the OptiX OSN 8800 Subrack
1 2 3
6. Optional: If there are screws on the front panel, tighten the two captive screws on the panel
of the board.
7. Insert the fibers into the connectors on the board according to the mapping relationship.
NOTE
After the board is replaced, the NE software delivers the configuration of the original board automatically.
Step 8 Review the indicators of the new board. It takes ten minutes for a new board to work normally
after insertion. Ensure that the STAT indicator is steady green. If the indicator gives an abnormal
indication, reinsert the board or replace the board again.
Step 9 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu, to set the state of the board to IS.
Step 10 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances issues are cleared.
----End
NOTE
TNxx indicates the board hardware version that is displayed on the PCB board.
l In the OptiX OSN 8800 T16, the SCC board fills one slot in the subrack. The valid slots
for the SCC board are IU9 and IU10. IU9 is the first choice. If there is 1+1 protection for
the SCC board, IU10 is the default slot for the standby SCC.
l In the OptiX OSN 8800 T32, the SCC board fills one slot in the subrack. The valid slots
for the SCC board are IU11 and IU28. IU28 is the first choice. If there is 1+1 protection
for the SCC board, IU11 is the default slot for the standby SCC.
l In the OptiX OSN 8800 T64, the SCC board fills one slot in the subrack. The valid slots
for the SCC board are IU74 and IU85. IU74 is the first choice. If there is 1+1 protection
for the SCC board, IU85 is the default slot for the standby SCC.
l In the OptiX OSN 6800A, the SCC board fills one slot in the subrack. The valid slots for
the SCC board are IU17 and IU18. IU18 is the first choice. If there is 1+1 protection for
the SCC board, IU17 is the default slot for the standby SCC.
l In the OptiX OSN 3800A, the SCC board fills one slot in the subrack. The valid slots for
the SCC board are IU8 and IU9. IU9 is the first choice. If there is 1+1 protection for the
SCC board, IU8 is the default slot for the standby SCC.
NOTE
If there is SCC 1+1 protection, the data on the active SCC board is synchronized to the standby SCC board
after the standby board is replaced.
CAUTION
Do not replace the EFI1 board on the OptiX OSN 8800 T64, OptiX OSN 8800 T32 or OptiX
OSN 6800A when you replace the SCC board.
CAUTION
To help prevent unsynchronized data, do not remove the SCC board during batch data backup.
You can replace the SCC board on the OptiX OSN 8800/6800A when:
l The SCC board of the master subrack is configured with SCC 1+1 protection.
l There is no protection for the SCC board of the master subrack.
l You are replacing the SCC board of the slave subrack.
You can replace the SCC board on the OptiX OSN 3800A when:
l The SCC board of the master subrack is configured with SCC 1+1 protection.
l There is no protection for the SCC board.
8.2.1 Setting the Jumper and DIP Switch on the SCC Board
This section describes how to set the battery jumpers and BIOS jumpers on the spare SCC board
before replacing the SCC board.
The battery on the SCC helps to ensure that the configuration is kept upon a power failure of
the SCC. If the board is in use, place a jumper cap over the battery jumper to make a short circuit,
which allows the battery to supply power normally.
The BIOS jumper or switch helps clear the system parameter area and database in the flash
memory on the SCC board. Table 8-5 shows the function of the BIOS jumper or switch.
D Clear all the data in the flash memory except the board 1111
manufacturing information. The data includes the
system data, system parameter areas, and extended
BIOS files. The upper layer part of BIOS is not started.
Figure 8-11 shows the position of swiches and jumpers on the TN16SCC board.
Figure 8-12 shows the position of jumpers on the TN22SCC board.
Figure 8-13 shows the jumpers on the TN51SCC board.
Figure 8-14 shows jumpers on the TN52SCC board.
Figure 8-15 shows jumpers on the TNK2SCC board.
Figure 8-11 Position of the switches and jumpers on the TN16SCC board
BIOS Switch Battery Jumper
Binary Value 1010
0 1 0 1
ON DIP 2
Battery is
SW1 used 3 1
State A J1
Battery 1 2 3 4
Jumper
Binary Value 1001
ON DIP 2 1 0 0 1
BIOS DIP SW1 2 ON DIP
Switch 1 234 3 1 2
J1 SW1 Battery is
State B
not used 3 1
1 2 3 4 J1
Binary Value 1011
CF 1 1 0 1
Card ON DIP
SW1
State C
1 2 3 4
Binary Value 1111
1 1 1 1
ON DIP
State D SW1
1 2 3 4
J11
2 4
CPU
2 4
J1
J13
J1
1 0
4
State A State B
0 0 Battery is
1
not used
1
1 1
4
J1
J13 J13
1 1
4
State C State D
0 1
1
2
1
1 1
4
J13 J13
2 J42 10
2 J42 10
9
9
0101
1001
State A State B
1
1
Binary Binary
1 0 1 1 1 1 1 1
value value
2 J42 10
2 J42 10
J12
9
9
1111
1101
2 Sate C State D
J1 Battery Jumper
3 1
1
1
Battery Jumper
3 1 3 1
1001
1
2
State A State B
1
2
10
10
9
9
3
J1 J11 J11
1
Binary Binary
1 0 11 11 11
value value
1011
1111
1
2
10
9
10
9
J11 J11
Battery Jumper
1
Battery Battery is
2
卡
F J1 J1
J9 J41
2 10
3
2
1 9
1
CF Card
3
J9 J9 Battery is
2 10 2 10 used
1
State A State B
1 9 1 9
J41
3
Binary Value 1011 Binary Value 1111 Battery is
2
1 1 0 1 1 1 1 1 not used
1
J9 J9
2 10 2 10
State C State D
1 9 1 9
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
l The SCC replacement board must be the same type as the SCC board being replaced.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
For SCC 1+1 protection, replacing one of the SCC in the protection group does not interrupt
communication between the NE where the SCC board resides and the U2000 after you switch
services from one SCC board to the other SCC board.
Precautions
During the SCC board replacement, do not configure the NE before the new SCC board is started
up.
Procedure
Step 1 Select a spare SCC board as the replacement board. Ensure that the spare SCC board and the
SCC board to be replaced have the same name and are of the same type.
Step 3 Back up the NE database to the NMS server. This is to record the NE database for future reference
when the SCC board is replaced.
1. In the Main Topology view, choose Administration > NE Software Management > NE
Data Backup/Restoration from the Main Menu.
2. Right-click the device(s) that you want to back up in the NE View table.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
3. Select Backup... to open the Backup dialog.
4. Select the option NMS Server or NMS Client to backup the selected device information.
NOTE
By default the NMS Server is selected. If the NMS Server is selected, the selected device information
is stored on the NMS server.
5. Optional: If the NMS Client is selected, click to select the location where the device
data are to be backed up.
6. Click Start to start the backup operation for the selected device(s). On the NE View tab
page, the backup progress is displayed.
7. When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/
yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd"
indicates the date when the backup is created, and "hhmmss" indicates the time when the
backup is created.
Step 4 Follow the steps below to review the working state of the board to be replaced.
1. In the NE Explorer, click the NE and choose Configuration > Board 1+1 Protection from
the Function Tree.
2. Click Query.
Step 5 If the board to be replaced is the active board, go to Step 6. Otherwise, go to Step 7.
Step 6 If the board to be replaced is the working board, complete the following the steps to perform an
active/standby switching on the U2000.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired SCC Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
4. Click Query. If the Working Board is not the board to be replaced, the switching is
successful.
5. Query the alarms and performance events on the U2000. Check if services are normal. If
services are normal, there must be no new abnormal alarms or performances. The switching
is successful.
Step 7 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 8 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 9 Inform the onsite maintenance engineer and replace the board. For details about how to remove
a board, see Procedure of Replacing a Board.
NOTE
If the OptiX OSN 3800A is installed in the 23" open rack, the method of replacing the SCC board is the same
as that of the PIU board. For details, see Step 6 of the "Replacing the PIU Board".
Step 10 Set the four jumpers on the spare SCC board to set the BIOS running mode. Then insert the SCC
board to the slot housing the original SCC board to format the file system of the new SCC board.
1. Set the BIOS running mode of the spare SCC board to status D (1111) to clear all the data
in the flash memory except the board manufacturing information. shows the settings of the
four jumpers on the SCC board.
2. Insert the spare SCC board in the slot housing the original SCC board. When the STAT
indicator on the inserted SCC board is blinking green quickly, the file system is being
formatted. When the STAT indicator is steady green, the formatting is completed. The
formatting takes about 15 minutes.
NOTE
If the spare SCC board is a version earlier than V100R006C01SPC300, the formatting is not indicated on
any board indicators. Wait 15 minutes until the system formatting is completed.
Step 11 After the file system of the SCC board is formatted completely, remove the board. Remove the
jumper caps which you set in Step 10. Reinsert this SCC board to the slot.
NOTE
Step 12 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 13 View the indicators on the front panel of the new board. It takes approximately 90 minutes for
a new board to work normally after insertion. Ensure that the STAT indicator is blinking slowly
(green). If the indicator is not blinking slowly (green), you need to reinsert the board or select a
new replacement board. For details about the indicators, see Board Indicators.
Step 14 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 15 Optional: Follow the steps below to switch the active/standby state of the SCCs back to the
original state.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click SCC Board 1+1 Protection. Select Working/
Protection Switching from the shortcut menu. Click OK in the window displayed.
NOTE
After you start the new SCC board, the system automatically synchronizes the data between the existing
SCC board and the new SCC board. After data backup completes, perform the preceding step to initiate
active/standby switching.
Step 16 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
Table 8-6 Modes of replacing the SCC of the master subrack without protection
The NE is reachable on the Replacing the SCC by The database of the NE must be
U2000. Backing Up Database backed up. After replacing the
Data to the NMS SCC, restore the database to the
NE.
Replacing the SCC by The first mode is recommended.
Backing Up Database
If a slot is available for another
Data to a CF Card
SCC, configure the system to
provide 1+1 SCC protection.
8.2.3.1 Replacing the SCC by Backing Up Database Data from the NMS (NE Is
Unreachable)
If the NE is unreachable because of SCC damage, you can restore the NE database from the
NMS after replacing the SCC board.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
l The SCC replacement board must be the same type as the SCC board being replaced.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
Precautions
CAUTION
l Operations on the U2000 must be performed in the network management center.
l Operations on the Web LCT must be performed on site.
Procedure
Step 1 Select a spare SCC board. Ensure that the spare SCC board and the SCC board to be replaced
have the same name and are of the same type.
Step 2 Inform the onsite maintenance engineer and remove the board. For details about how to remove
a board, see Procedure of Replacing a Board.
NOTE
If the OptiX OSN 3800A is installed in the 23" open rack, the method of replacing the SCC board is the same
as that of the PIU board. For details, see Step 6 of the "Replacing the PIU Board".
Step 3 Set the four jumpers on the spare SCC board so as to set the BIOS running mode of the board
and then insert it to the slot housing the original SCC board. In this manner, the database on the
new SCC board is cleared. 8.2.1 Setting the Jumper and DIP Switch on the SCC Board shows
the settings of the four jumpers on the SCC board.
1. Set the BIOS running mode of the spare SCC board to status C (1011) to clear the database
in the flash memory.
2. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
3. Set the BIOS running mode of the spare SCC board to status A (1010) to clear the system
parameter area.
4. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
Step 4 After the database of the SCC board is cleared completely, remove the board. Remove the jumper
caps which are shown in Step 3. After that, reinsert this SCC board to the slot.
Step 5 After the new SCC board starts, connect the Web LCT to the NE.
1. Disconnect the cables from the NM_ETH1 and NM_ETH2 ports (if connected). That is,
disconnect the NE from the computer where the U2000 (hereinafter the computer is referred
to as U2000) is installed.
2. Connect the Web LCT to NM_ETH1.
3. Set the IP address of the Web LCT to ensure that Web LCT is in the same IP subnet segment
as the NE IP address. If the IP address of the Web LCT and the NE IP address are in different
network segments, the Web LCT cannot be connected to the NE.
NOTE
The new board is initiated at the factory, and the default IP subnet segment of the board is 129.9.*.*.
4. Log in the Web LCT with the user name admin, and the initial password .
Step 6 Create the NE by using the Web LCT.
1. Click NE Search > Advanced Search in the NE List. The Search NE dialog box is
displayed.
2. Click Manage Domain. The Manage Domain Search dialog box is displayed.
3. Click Add. The New Domain dialog box is displayed.
4. Set Domain Type to GNE IP Domain or GNE IP Address. Enter an IP address in the
Domain Address field.
5. Click OK.
NOTE
Repeat step 3 through 5 to add multiple search domains.
6. Close the Manage Domain Search dialog box.
7. Select the appropriate network segment IP addresses within the Domain and click
Search.
NOTE
l The NE search function searches for only the NEs in the specified network segment.
l When the search is in progress, you can click End Search.
8. After the search is complete, select an NE from the list and click Add NE. A prompt
message is displayed, indicating that the NE is successfully added. Click OK.
9. Select the NE to which you want to log in and click NE Login in the lower right corner or
right-click the NE and choose NE Login. In the NE Login dialog box that is displayed,
enter sonet and SONET in the User Name and Password fields.Then click OK.
TIP
Step 7 Modify the NE IP, gateway IP and subnet mask based on the original information using the Web
LCT.
1. In the NE Explorer, select Configuration > NE Attribute from the Function Tree.
2. Enter the NE IP address, gateway IP address and subnet mask, and click Apply.
3. Click OK after the Warning dialog box pops up.
4. Click OK after the Warning dialog box about communication interruption between NEs
pops up.
NOTE
If the NE IP addresses before and after the modification are in different network segments, the Web LCT cannot
be connected to the NE. When this occurs, set the IP address of the Web LCT in the same network segment as
the NE IP address.
Step 8 Modify the OSPF parameters based on the original information using the Web LCT.
1. In the NE Explorer, choose Communication > OSPF Parameter from the function tree.
2. In the OSPF Parameter Management pane, change the OSPF parameters to the original
information about the NE.
3. Click Apply.
Step 9 Modify the NE name based on the original information using the Web LCT.
1. In the NE Explorer, choose Configuration > NE Attribute from the Function Tree.
2. Enter the NE Name, and click Apply.
Step 10 Check the NE attribute using the Web LCT.
1. Select the NE you just created and click the NE Explorer.
2. Select Configuration > NE Attribute from the Function Tree.
3. Check that all NE communication parameters are the same as the original ones.
Step 11 Create a user for an NE using the Web LCT.
NOTE
The created NE user must be included in the activated database and the password must match that recorded
in the database. Otherwise, activating the database fails.
1. In the NE Explorer, select the NE and choose Security > NE User Management from
the function tree.
2. Click New. The Add NE User dialog box is displayed.
3. Refer to Table 8-7 to set attribute values of the new user.
On the Web For example: The name of the NE user being created.
LCT: User USER A string, containing 4 to 16 characters. It must
include at least one letter, and no punctuation is
permitted. It cannot be the same as an existing NE
user name.
On the Web RTRV, PROV, The operations carried out by the NE user are
LCT: Level MAINT and classified into four levels, RTRV, PROV,
SUPER MAINT, and SUPER from the lowest level to the
highest. Higher level users can perform all the
functions that lower level users can. For example, an
operation level user has all the rights of a monitor
level user. The system level user with the highest
level has all rights. The detailed rights settings for
each level are:
RTRV: all query commands, log in, log out, and
modification of its own password.
PROV: all settings for fault and performance, partial
security settings, and partial configuration.
MAINT: partial security settings, partial
configuration, communication settings, and log
management.
SUPER: all security settings, all configurations.
NOTE
For a super user, only one user at a time can log in to an
NE. In the case of an RTRV, PROV, MAINT or user, a
maximum of 16 users can log in to an NE concurrently.
An RTRV, PROV, or MAINT user cannot modify the login
password. The password can be modified only by a super
user.
Time of Any integer This option is in effect only when Yes is selected for
Canceling from 5 to 60 Canceling User Automatically. Set the time to
User Default: 60 automatically cancel the user.
Automatically
(m)
User Valid Any integer The period in which the user's name is in effect. The
Till (days) from 1 to 999 unit measurement is day.
This option is in effect only when No is selected for
User Permanently Valid.
Password Any integer The period in which the password is in effect. The
Valid Till from 25 to 999 unit of measurement is day.
(days) This option is in effect only when No is selected for
Password Permanently Valid.
4. Click Apply.
Step 13 If the software version of the spare SCC board is different from the software version of the SCC
board to be replaced, go to Step 14; otherwise, go to Step 15.
Step 14 Upgrade or downgrade the software of the spare SCC board. For details, see the Upgrade
Guide. Ensure that the software version of the spare SCC board is consistent with that of the
SCC board to be replaced.
l If NMS Client is selected, click to select the backup file from the NMS Client.
The selected backup file path is displayed in the Select File field.
6. Click OK.
NOTE
The selected backup file path from the NMS Server or NMS Client is displayed in the File Name drop-
down list.
7. Click Start, the Operation Confirmation dialog box is displayed.
8. In the Operation Confirmation dialog, click Yes to start the recovery operation. The
recovery operation status is displayed in the NE View table.
NOTE
You must activate the NE database within five minutes after restoring it.
CAUTION
During the process of backing up databases through restoring databases, do not modify the NE
configurations to avoid database inconsistency.
Synchronized Fiber/Cable: Indicates the fibers that exist on both the U2000 and NE sides.
Uncreated Fiber/Cable in NMS: Indicates the fibers that exist only on the NE side.
Uncreated Fiber/Cable in NE: Indicates the fibers that exist only on the U2000 side.
4. If there are fibers in Uncreated Fiber/Cable in NMS or Uncreated Fiber/Cable in NE,
select all the fibers. Click Create Fiber/Cable. The Operation Result dialog box is
displayed. Click Close. The synchronized fibers are displayed on the Synchronized Fiber/
Cable list.
5. If conflicting fibers are configured and you fail to create a fiber, click Delete Fiber/
Cable to delete the incorrect fiber and click Create Fiber/Cable to re-create the failed
fibers.
Step 18 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
NOTE
For details to set these parameters, see iManager U2000 Operator Guide for NG WDM NE Management.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
8.2.3.2 Replacing the SCC by Backing Up Database Data from a CF Card (NE Is
Unreachable)
When the NE is unreachable resulting from a damages SCC board, restore the NE database from
the CF card after replacing the SCC board if there is no backup data on the NMS.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The SCC replacement board must be the same type as the SCC board being replaced.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
Precautions
CAUTION
l After the database of the NE is restored on the CF card, the restoration must be completed
within two hours after you install the replacement SCC. If you wait more than two hours to
restore the database of the NE on the CF card, the data automatically saved on the NE
overwrites the original data stored on the CF card. If the original data is overwritten, the
original database of the NE cannot be restored.
l NE data is backed up every 24 hours by default. The database data restored from the CF card
is the latest data backed up if the NE is unreachable. Therefore, it may be different from the
current actual data.
l Operations on the U2000 must be performed in the network management center.
l Operations on the Web LCT must be performed on site.
Procedure
Step 1 Select a spare SCC board as the replacement board. Ensure that the spare SCC board and the
SCC board to be replaced have the same name and are of the same type.
Step 2 Remove the SCC board to be replaced. For details about how to remove a board, see Procedure
of Replacing a Board.
Step 3 On the SCC board that has been removed, hold the CF card and pull the card out of the CF card
slot. Put the SCC into an ESD bag.
NOTE
Step 4 Set the four jumpers on the spare SCC board so as to set the BIOS running mode of the board
and then insert it to the slot housing the original SCC board. In this manner, the database on the
new SCC board is cleared. 8.2.1 Setting the Jumper and DIP Switch on the SCC Board shows
the settings of the four jumpers on the SCC board.
1. Set the BIOS running mode of the spare SCC board to status C (1011) to clear the database
in the flash memory.
2. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
3. Set the BIOS running mode of the spare SCC board to status A (1010) to clear the system
parameter area.
4. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
Step 5 After the database of the SCC board is cleared completely, remove the board. Remove the jumper
caps which are shown in Step 4. After that, reinsert this SCC board to the slot.
Step 6 After the new SCC board is started, connect the Web LCT to the NE.
1. Disconnect the cables from the NM_ETH1 and NM_ETH2 ports (if connected). That is,
disconnect the NE from the computer where the U2000 (hereinafter the computer is referred
to as U2000) is installed.
2. Connect the Web LCT to NM_ETH1.
3. Set the IP address of the Web LCT to ensure that Web LCT is in the same IP subnet segment
as the NE IP address. If the IP address of the Web LCT and the NE IP address are in different
network segments, the Web LCT cannot be connected to the NE.
NOTE
The new board is initiated at the factory, and the default IP subnet segment of the board is 129.9.*.*.
4. Log in the Web LCT with the user name admin, and the initial password .
l The NE search function searches for only the NEs in the specified network segment.
l When the search is in progress, you can click End Search.
8. After the search is complete, select an NE from the list and click Add NE. A prompt
message is displayed, indicating that the NE is successfully added. Click OK.
9. Select the NE to which you want to log in and click NE Login in the lower right corner or
right-click the NE and choose NE Login. In the NE Login dialog box that is displayed,
enter sonet and SONET in the User Name and Password fields.Then click OK.
TIP
Step 8 Modify the NE IP, gateway IP and subnet mask based on the original information using the Web
LCT.
1. In the NE Explorer, select Configuration > NE Attribute from the Function Tree.
2. Enter the NE IP address, gateway IP address and subnet mask, and click Apply.
3. Click OK after the Warning dialog box pops up.
4. Click OK after the Warning dialog box about communication interruption between NEs
pops up.
NOTE
If the NE IP addresses before and after the modification are in different network segments, the Web LCT cannot
be connected to the NE. When this occurs, set the IP address of the Web LCT in the same network segment as
the NE IP address.
Step 9 Modify the OSPF parameters based on the original information using the Web LCT.
1. In the NE Explorer, choose Communication > OSPF Parameter from the function tree.
2. In the OSPF Parameter Management pane, change the OSPF parameters to the original
information about the NE.
3. Click Apply.
Step 10 Modify the NE name based on the original information using the Web LCT.
1. In the NE Explorer, choose Configuration > NE Attribute from the Function Tree.
2. Enter the NE Name, and click Apply.
Step 11 Check the NE attribute using the Web LCT.
1. Select the NE you just created and click the NE Explorer.
2. Select Configuration > NE Attribute from the Function Tree.
3. Check that all NE communication parameters are the same as the original ones.
Step 12 Create a user for an NE using the Web LCT.
NOTE
The created NE user must be included in the activated database and the password must match that recorded
in the database. Otherwise, activating the database fails.
1. In the NE Explorer, select the NE and choose Security > NE User Management from
the function tree.
2. Click New. The Add NE User dialog box is displayed.
3. Refer to Table 8-8 to set attribute values of the new user.
On the Web For example: The name of the NE user being created.
LCT: User USER A string, containing 4 to 16 characters. It must
include at least one letter, and no punctuation is
permitted. It cannot be the same as an existing NE
user name.
On the Web RTRV, PROV, The operations carried out by the NE user are
LCT: Level MAINT and classified into four levels, RTRV, PROV,
SUPER MAINT, and SUPER from the lowest level to the
highest. Higher level users can perform all the
functions that lower level users can. For example, an
operation level user has all the rights of a monitor
level user. The system level user with the highest
level has all rights. The detailed rights settings for
each level are:
RTRV: all query commands, log in, log out, and
modification of its own password.
PROV: all settings for fault and performance, partial
security settings, and partial configuration.
MAINT: partial security settings, partial
configuration, communication settings, and log
management.
SUPER: all security settings, all configurations.
NOTE
For a super user, only one user at a time can log in to an
NE. In the case of an RTRV, PROV, MAINT or user, a
maximum of 16 users can log in to an NE concurrently.
An RTRV, PROV, or MAINT user cannot modify the login
password. The password can be modified only by a super
user.
Time of Any integer This option is in effect only when Yes is selected for
Canceling from 5 to 60 Canceling User Automatically. Set the time to
User Default: 60 automatically cancel the user.
Automatically
(m)
User Valid Any integer The period in which the user's name is in effect. The
Till (days) from 1 to 999 unit measurement is day.
This option is in effect only when No is selected for
User Permanently Valid.
Password Any integer The period in which the password is in effect. The
Valid Till from 25 to 999 unit of measurement is day.
(days) This option is in effect only when No is selected for
Password Permanently Valid.
4. Click Apply.
Step 14 Query the software version of the spare SCC board, if it is different from the software version
of the SCC board to be replaced, go to Step 15; otherwise, go to Step 16.
Step 15 Upgrade or downgrade the software of the spare SCC board. For details, see the Upgrade
Guide. Ensure that the software version of the spare SCC board is consistent with that of the
SCC board to be replaced.
Step 16 After the SCC board is started, remove the SCC board just inserted. Insert the CF card that has
been removed in Step 3 into the CF card slot on the SCC board. Then insert the SCC.
4. Click Restore NE Database from CF Card. The Confirm dialog box is displayed,
indicating that the restoration of the NE database may lead to service interruption.
5. Click OK to start to restore the NE database.
NOTE
If the database is performing a scheduled backup task, the message "NOT IN VALID STATE, FAILED
TO RECOVER FROM CF" will be displayed on the NMS, indicating that restoring data from the CF card
will fail. In this scenario, you are advised to wait 5 minutes, and restore data again from the CF card after
the database finishes the scheduled backup task.
6. Click Closeafter an Operation Result dialog box is displayed.
NOTE
After the NE databases are restored, the NE software issues the data in the CF card to only the SCC board
but not other boards. To ensure that the configurations in the SCC board and the configurations in other
boards are consistent, you need to perform warm resets on other boards. You can use the TL1 command
to perform warm resets on all the boards, the TL1 command is : init-sys::slot-all:z::warm.
CAUTION
During the process from backing up databases to restoring databases, do not modify the NE
configurations to avoid database inconsistency.
Synchronized Fiber/Cable: Indicates the fibers that exist on both the U2000 and NE sides.
Uncreated Fiber/Cable in NMS: Indicates the fibers that exist only on the NE side.
Uncreated Fiber/Cable in NE: Indicates the fibers that exist only on the U2000 side.
4. If there are fibers in Uncreated Fiber/Cable in NMS or Uncreated Fiber/Cable in NE,
select all the fibers. Click Create Fiber/Cable. The Operation Result dialog box is
displayed. Click Close. The synchronized fibers are displayed on the Synchronized Fiber/
Cable list.
5. If conflicting fibers are configured and you fail to create a fiber, click Delete Fiber/
Cable to delete the incorrect fiber and click Create Fiber/Cable to re-create the failed
fibers.
Step 19 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
NOTE
For details to set these parameters, see iManager U2000 Operator Guide for NG WDM NE Management.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
8.2.3.3 Replacing the SCC by Backing Up Database Data to the NMS (NE Is
Reachable)
Before replacing an SCC board, you can back up the NE database to the NMS if the NE is
reachable and the slot for housing the standby SCC board is occupied by a service board. In this
manner, you can restore the NE database from the NMS after replacing the SCC board.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
l The SCC replacement board must be the same type as the SCC board being replaced.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
Precautions
CAUTION
l Operations on the U2000 must be performed in the network management center.
l Operations on the Web LCT must be performed on site.
Procedure
Step 1 Select a spare SCC board as the replacement board. Ensure that the spare SCC board and the
SCC board to be replaced have the same name and are of the same type.
Step 3 Back up the NE database to the NMS server. This records the NE database for future reference
when the SCC board is faulty.
1. In the Main Topology view, choose Administration > NE Software Management > NE
Data Backup/Restoration from the Main Menu.
2. Right-click the device(s) that you want to back up in the NE View table.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
3. Select Backup... to open the Backup dialog.
4. Select the option NMS Server or NMS Client to backup the selected device information.
NOTE
By default the NMS Server is selected. If the NMS Server is selected, the selected device information
is stored on the NMS server.
5. Optional: If the NMS Client is selected, click to select the location where the device
data are to be backed up.
6. Click Start to start the backup operation for the selected device(s). On the NE View tab
page, the backup progress is displayed.
7. When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/
yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd"
indicates the date when the backup is created, and "hhmmss" indicates the time when the
backup is created.
Step 4 Follow the steps below to query the system to obtain the user management list of the NE.
1. In the NE Explorer, select an NE and choose Security > NE User Management from the
Function Tree.
2. Click Query.
3. Record the NE user data returned by the system for future restoration of the NE user data.
NOTE
Also record the password for each user account of the NE.
Step 7 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 8 Inform the onsite maintenance engineer and remove the board. For details about how to remove
a board, see Procedure of Replacing a Board.
NOTE
If the OptiX OSN 3800A is installed in the 23" open rack, the method of replacing the SCC board is the same
as that of the PIU board. For details, see Step 6 of the "Replacing the PIU Board".
Step 9 Set the four jumpers on the spare SCC board so as to set the BIOS running mode of the board
and then insert it to the slot housing the original SCC board. In this manner, the database on the
new SCC board is cleared. 8.2.1 Setting the Jumper and DIP Switch on the SCC Board shows
the settings of the four jumpers on the SCC board.
1. Set the BIOS running mode of the spare SCC board to status C (1011) to clear the database
in the flash memory.
2. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
3. Set the BIOS running mode of the spare SCC board to status A (1010) to clear the system
parameter area.
4. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
Step 10 After the database of the SCC board is cleared completely, remove the board. Remove the jumper
caps which are shown in Step 9. After that, reinsert this SCC board to the slot.
Step 11 After the new SCC board is started, connect the Web LCT to the NE.
1. Disconnect the cables from the NM_ETH1 and NM_ETH2 ports (if connected). That is,
disconnect the NE from the computer where the U2000 (hereinafter the computer is referred
to as U2000) is installed.
2. Connect the Web LCT to NM_ETH1.
3. Set the IP address of the Web LCT to ensure that Web LCT is in the same IP subnet segment
as the NE IP address. If the IP address of the Web LCT and the NE IP address are in different
network segments, the Web LCT cannot be connected to the NE.
NOTE
The new board is initiated at factory, and the default IP subnet segment of the board is 129.9.*.*.
4. Log in the Web LCT with the user name admin, and the initial password .
Step 12 Create the NE using the Web LCT.
1. Click NE Search > Advanced Search in the NE List. The Search NE dialog box is
displayed.
2. Click Manage Domain. The Manage Domain Search dialog box is displayed.
3. Click Add. The New Domain dialog box is displayed.
4. Set Domain Type to GNE IP Domain or GNE IP Address. Enter an IP address in the
Domain Address field.
5. Click OK.
NOTE
Repeat step 3 through 5 to add multiple search domains.
6. Close the Manage Domain Search dialog box.
7. Select the appropriate network segment IP addresses within the Domain and click
Search.
NOTE
l The NE search function searches for only the NEs in the specified network segment.
l When the search is in progress, you can click End Search.
8. After the search is complete, select an NE from the list and click Add NE. A prompt
message is displayed, indicating that the NE is successfully added. Click OK.
9. Select the NE to which you want to log in and click NE Login in the lower right corner or
right-click the NE and choose NE Login. In the NE Login dialog box that is displayed,
enter sonet and SONET in the User Name and Password fields.Then click OK.
TIP
Step 13 Modify the NE IP, gateway IP and subnet mask based on the original information using the Web
LCT.
1. In the NE Explorer, select Configuration > NE Attribute from the Function Tree.
2. Enter the NE IP address, gateway IP address and subnet mask, and click Apply.
3. Click OK after the Warning dialog box pops up.
4. Click OK after the Warning dialog box about communication interruption between NEs
pops up.
NOTE
If the NE IP addresses before and after the modification are in different network segments, the Web LCT cannot
be connected to the NE. When this occurs, set the IP address of the Web LCT in the same network segment as
the NE IP address.
Step 14 Modify the OSPF parameters based on the original information using the Web LCT.
1. In the NE Explorer, choose Communication > OSPF Parameter from the function tree.
2. In the OSPF Parameter Management pane, change the OSPF parameters to the original
information about the NE.
3. Click Apply.
Step 15 Modify the NE name based on the original information using the Web LCT.
1. In the NE Explorer, choose Configuration > NE Attribute from the Function Tree.
2. Enter the NE Name, and click Apply.
Step 16 Check the NE attribute using the Web LCT.
1. Select the NE you just created and click the NE Explorer.
2. Select Configuration > NE Attribute from the Function Tree.
3. Check that all NE communication parameters are the same as the original ones.
Step 17 According to the NE user management list queried in Step 4, create a user for an NE using the
Web LCT.
1. In the NE Explorer, select the NE and choose Security > NE User Management from
the function tree.
2. Click New. The Add NE User dialog box is displayed.
3. Refer to Table 8-9 to set attribute values of the new user.
On the Web For example: The name of the NE user being created.
LCT: User USER A string, containing 4 to 16 characters. It must
include at least one letter, and no punctuation is
permitted. It cannot be the same as an existing NE
user name.
On the Web RTRV, PROV, The operations carried out by the NE user are
LCT: Level MAINT and classified into four levels, RTRV, PROV,
SUPER MAINT, and SUPER from the lowest level to the
highest. Higher level users can perform all the
functions that lower level users can. For example, an
operation level user has all the rights of a monitor
level user. The system level user with the highest
level has all rights. The detailed rights settings for
each level are:
RTRV: all query commands, log in, log out, and
modification of its own password.
PROV: all settings for fault and performance, partial
security settings, and partial configuration.
MAINT: partial security settings, partial
configuration, communication settings, and log
management.
SUPER: all security settings, all configurations.
NOTE
For a super user, only one user at a time can log in to an
NE. In the case of an RTRV, PROV, MAINT or user, a
maximum of 16 users can log in to an NE concurrently.
An RTRV, PROV, or MAINT user cannot modify the login
password. The password can be modified only by a super
user.
Time of Any integer This option is in effect only when Yes is selected for
Canceling from 5 to 60 Canceling User Automatically. Set the time to
User Default: 60 automatically cancel the user.
Automatically
(m)
User Valid Any integer The period in which the user's name is in effect. The
Till (days) from 1 to 999 unit measurement is day.
This option is in effect only when No is selected for
User Permanently Valid.
Password Any integer The period in which the password is in effect. The
Valid Till from 25 to 999 unit of measurement is day.
(days) This option is in effect only when No is selected for
Password Permanently Valid.
4. Click Apply.
Step 18 Recover the network connection of the NE.
1. Remove the network cable which connected the NM_ETH1 port to the Web LCT.
2. Connect the network cable removed in Step 11.
NOTE
After this procedure, you can use the original user name and password to access the NE using the
U2000.
Step 19 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 20 If the software version of the spare SCC board is different from the software version of the SCC
board to be replaced, go to Step 21; otherwise, go to Step 22.
Step 21 Upgrade or downgrade the software of the spare SCC board. For details, see the Upgrade
Guide. Ensure that the software version of the spare SCC board is consistent with that of the
SCC board to be replaced.
Step 22 Restore the NE database from the NMS server.
NOTE
You must activate the NE database within five minutes after restoring it.
1. In the Main Topology view, choose Administration > NE Software Management > NE
Data Backup/Restoration from the Main Menu.
2. Right click the devices that you want to recover in the NE View table.
3. Select Recover... to open the Recover dialog.
4. In the File Name drop-down list, select the file to be recovered. If the backup file is listed
in the File Name drop-down list, select the file to be recovered, and turn to 22.7. If the
backup file is not listed in the File Name drop-down list, click Browse... to select the backup
file in the Select File dialog box.
5. Select NMS Server or NMS Client to recover the backup file for the selected devices. By
default NMS Server is selected.
l If NMS Server is selected, select the appropriate backup file from the NMS server. The
selected backup file path is displayed in the Select File field.
l If NMS Client is selected, click to select the backup file from the NMS Client.
The selected backup file path is displayed in the Select File field.
6. Click OK.
NOTE
The selected backup file path from the NMS Server or NMS Client is displayed in the File Name drop-
down list.
7. Click Start, the Operation Confirmation dialog box is displayed.
8. In the Operation Confirmation dialog, click Yes to start the recovery operation. The
recovery operation status is displayed in the NE View table.
CAUTION
During the process from backing up databases to restoring databases, do not modify the NE
configurations to avoid database inconsistency.
Synchronized Fiber/Cable: Indicates the fibers that exist on both the U2000 and NE sides.
Uncreated Fiber/Cable in NMS: Indicates the fibers that exist only on the NE side.
Uncreated Fiber/Cable in NE: Indicates the fibers that exist only on the U2000 side.
Step 25 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
NOTE
For details to set these parameters, see iManager U2000 Operator Guide for NG WDM NE Management.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The SCC replacement board must be the same type as the SCC board being replaced.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
Precautions
CAUTION
l After the database of the NE is restored on the CF card, the restoration must be completed
within two hours after you install the replacement SCC. If you wait more than two hours to
restore the database of the NE on the CF card, the data automatically saved on the NE
overwrites the original data stored on the CF card. If the original data is overwritten, the
original database of the NE cannot be restored.
l Operations on the U2000 must be performed in the network management center.
l Operations on the Web LCT must be performed on site.
Procedure
Step 1 Select a spare SCC board as the replacement board. The spare SCC board and the SCC board
to be replaced must have the same name and type.
Step 2 Review and record the current NE alarms.
Step 3 Back up the database on the U2000.
1. In the Main Topology view, choose Configuration > NE Configuration Data
Management from the Main Menu, and the NE Configuration interface is displayed.
Step 8 Remove the SCC board to be replaced. For details about how to remove a board, see Procedure
of Replacing a Board.
Step 9 On the SCC board that has been removed, hold the CF card and pull the card out of the CF card
slot. Put the SCC into an ESD bag.
NOTE
Step 10 Set the four jumpers on the spare SCC board so as to set the BIOS running mode of the board
and then insert it to the slot housing the original SCC board. In this manner, the database on the
new SCC board is cleared. 8.2.1 Setting the Jumper and DIP Switch on the SCC Board shows
the settings of the four jumpers on the SCC board.
1. Set the BIOS running mode of the spare SCC board to status C (1011) to clear the database
in the flash memory.
2. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
3. Set the BIOS running mode of the spare SCC board to status A (1010) to clear the system
parameter area.
4. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
Step 11 After the database of the SCC board is cleared completely, remove the board. Remove the jumper
caps which are shown in Step 10. After that, reinsert this SCC board to the slot.
Step 12 After the new SCC board is started, connect the Web LCT to the NE.
1. Disconnect the cables from the NM_ETH1 and NM_ETH2 ports (if connected). That is,
disconnect the NE from the computer where the U2000 (hereinafter the computer is referred
to as U2000) is installed.
2. Connect the Web LCT to NM_ETH1.
3. Set the IP address of the Web LCT to ensure that Web LCT is in the same IP subnet segment
as the NE IP address. If the IP address of the Web LCT and the NE IP address are in different
network segments, the Web LCT cannot be connected to the NE.
NOTE
The new board is initiated at factory, and the default IP subnet segment of the board is 129.9.*.*.
4. Log in the Web LCT with the user name admin, and the initial password .
l The NE search function searches for only the NEs in the specified network segment.
l When the search is in progress, you can click End Search.
8. After the search is complete, select an NE from the list and click Add NE. A prompt
message is displayed, indicating that the NE is successfully added. Click OK.
9. Select the NE to which you want to log in and click NE Login in the lower right corner or
right-click the NE and choose NE Login. In the NE Login dialog box that is displayed,
enter sonet and SONET in the User Name and Password fields.Then click OK.
TIP
Step 14 Modify the NE IP, gateway IP and subnet mask based on the original information using the Web
LCT.
1. In the NE Explorer, select Configuration > NE Attribute from the Function Tree.
2. Enter the NE IP address, gateway IP address and subnet mask, and click Apply.
3. Click OK after the Warning dialog box pops up.
4. Click OK after the Warning dialog box about communication interruption between NEs
pops up.
NOTE
If the NE IP addresses before and after the modification are in different network segments, the Web LCT cannot
be connected to the NE. When this occurs, set the IP address of the Web LCT in the same network segment as
the NE IP address.
Step 15 Modify the OSPF parameters based on the original information using the Web LCT.
1. In the NE Explorer, choose Communication > OSPF Parameter from the function tree.
2. In the OSPF Parameter Management pane, change the OSPF parameters to the original
information about the NE.
3. Click Apply.
Step 16 Modify the NE name based on the original information using the Web LCT.
1. In the NE Explorer, choose Configuration > NE Attribute from the Function Tree.
2. Enter the NE Name, and click Apply.
Step 18 According to the NE user management list queried in Step 4, create a user of the NE using the
Web LCT.
1. In the NE Explorer, select the NE and choose Security > NE User Management from
the function tree.
2. Click New. The Add NE User dialog box is displayed.
3. Refer to Table 8-10 to set attribute values of the new user.
On the Web For example: The name of the NE user being created.
LCT: User USER A string, containing 4 to 16 characters. It must
include at least one letter, and no punctuation is
permitted. It cannot be the same as an existing NE
user name.
On the Web RTRV, PROV, The operations carried out by the NE user are
LCT: Level MAINT and classified into four levels, RTRV, PROV,
SUPER MAINT, and SUPER from the lowest level to the
highest. Higher level users can perform all the
functions that lower level users can. For example, an
operation level user has all the rights of a monitor
level user. The system level user with the highest
level has all rights. The detailed rights settings for
each level are:
RTRV: all query commands, log in, log out, and
modification of its own password.
PROV: all settings for fault and performance, partial
security settings, and partial configuration.
MAINT: partial security settings, partial
configuration, communication settings, and log
management.
SUPER: all security settings, all configurations.
NOTE
For a super user, only one user at a time can log in to an
NE. In the case of an RTRV, PROV, MAINT or user, a
maximum of 16 users can log in to an NE concurrently.
An RTRV, PROV, or MAINT user cannot modify the login
password. The password can be modified only by a super
user.
Time of Any integer This option is in effect only when Yes is selected for
Canceling from 5 to 60 Canceling User Automatically. Set the time to
User Default: 60 automatically cancel the user.
Automatically
(m)
User Valid Any integer The period in which the user's name is in effect. The
Till (days) from 1 to 999 unit measurement is day.
This option is in effect only when No is selected for
User Permanently Valid.
Password Any integer The period in which the password is in effect. The
Valid Till from 25 to 999 unit of measurement is day.
(days) This option is in effect only when No is selected for
Password Permanently Valid.
4. Click Apply.
Step 20 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 21 Query the software version of the spare SCC board, if it is different from the software version
of the SCC board to be replaced, go to Step 22; otherwise, go to Step 23.
Step 22 Upgrade or downgrade the software of the spare SCC board. For details, see the Upgrade
Guide. Ensure that the software version of the spare SCC board is consistent with that of the
SCC board to be replaced.
Step 23 After the SCC board is started, remove the SCC board just inserted. Insert the CF card that has
been removed in Step 9 into the CF card slot on the SCC board. Then insert the SCC.
Step 24 Restore the initial database of the NE using the U2000.
1. In the Main Topology view, choose Configuration > NE Configuration Data
Management from the Main Menu, and the NE Configuration Data Management
interface is displayed.
CAUTION
During the process from backing up databases to restoring databases, do not modify the NE
configurations to avoid database inconsistency.
Synchronized Fiber/Cable: Indicates the fibers that exist on both the U2000 and NE sides.
Uncreated Fiber/Cable in NMS: Indicates the fibers that exist only on the NE side.
Uncreated Fiber/Cable in NE: Indicates the fibers that exist only on the U2000 side.
4. If there are fibers in Uncreated Fiber/Cable in NMS or Uncreated Fiber/Cable in NE,
select all the fibers. Click Create Fiber/Cable. The Operation Result dialog box is
displayed. Click Close. The synchronized fibers are displayed on the Synchronized Fiber/
Cable list.
5. If conflicting fibers are configured and you fail to create a fiber, click Delete Fiber/
Cable to delete the incorrect fiber and click Create Fiber/Cable to re-create the failed
fibers.
Step 26 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
NOTE
For details to set these parameters, see iManager U2000 Operator Guide for NG WDM NE Management.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
l The SCC replacement board must be the same type as the SCC board being replaced.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
NOTE
The logical board for the SCC board in the default slot cannot be deleted from the U2000; therefore, two spare
SCC boards must be prepared when this method is used to replace the SCC board.
Precautions
CAUTION
l Operations on the U2000 must be performed in the network management center.
l Operations on the Web LCT must be performed on site.
Procedure
Step 1 Select a spare SCC board as the replacement board. Ensure that the spare SCC board and the
SCC board to be replaced have the same name and type.
Step 2 Back up the NE database to the NMS server. This records the NE database for future reference
when the SCC board is replaced.
1. In the Main Topology view, choose Administration > NE Software Management > NE
Data Backup/Restoration from the Main Menu.
2. Right-click the device(s) that you want to back up in the NE View table.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
3. Select Backup... to open the Backup dialog.
4. Select the option NMS Server or NMS Client to backup the selected device information.
NOTE
By default the NMS Server is selected. If the NMS Server is selected, the selected device information
is stored on the NMS server.
5. Optional: If the NMS Client is selected, click to select the location where the device
data are to be backed up.
6. Click Start to start the backup operation for the selected device(s). On the NE View tab
page, the backup progress is displayed.
7. When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/
yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd"
indicates the date when the backup is created, and "hhmmss" indicates the time when the
backup is created.
Step 3 Set the jumpers on the spare SCC board using the following methods and insert it to the specified
slot for a standby SCC board. In this manner, the file system of the new SCC board is formatted.
NOTE
After inserting the spare SCC board to the specified slot for a standby SCC board, you need to add a corresponding
logical board on the U2000. Then, the system automatically configures 1+1 protection for the SCC.
1. Set the BIOS running mode of the spare SCC board to status D (1111) to clear all the data
in the flash memory except the board manufacturing information. shows the settings of the
four jumpers on the SCC board.
2. Insert the spare SCC board in the slot housing the original SCC board. When the STAT
indicator on the inserted SCC board is blinking green quickly, the file system is being
formatted. When the STAT indicator is steady green, the formatting is completed. The
formatting takes about 15 minutes.
NOTE
If the spare SCC board is a version earlier than V100R006C01SPC300, the formatting is not indicated on
any board indicators. Wait 15 minutes until the system formatting is completed.
Step 4 After the file system of the SCC board is formated completely, remove the board. Remove the
jumper caps which are shown in Step 3. After that, reinsert this SCC board to the slot.
NOTE
Step 5 View the indicators on the front panel of the new board. It takes approximately 90 minutes for
a new board to work normally after insertion. Ensure that the STAT indicator is steady green.
If the indicator is not steady green, you need to reinsert the board or select a new replacement
board. For details about the indicators, see Board Indicators.
Step 6 Log in to the U2000 and complete the following steps to perform an active/standby switch
between the SCC boards.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired SCC Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
4. Click Query. If the Working Board is not the board to be replaced, the switching is
successful.
5. Query the alarms and performance events on the U2000. Check if services are normal. If
services are normal, there must be no new abnormal alarms or performances. The switching
is successful.
NOTE
After the new SCC board is started, the system automatically backs up the data on the existing SCC board
to the new SCC board. After the data is backed up, you can perform the preceding step to initiate an active/
standby switching.
Step 7 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
NOTE
For details to set these parameters, see iManager U2000 Operator Guide for NG WDM NE Management.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
Step 9 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 10 Remove the board to be replaced and put it into an ESD bag. Insert a new board in the slot. For
detailed operations, see Step 1 to Step 5.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The SCC replacement board must be the same type as the SCC board being replaced.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
l The communication between the master and slave subracks is normal and the slave subrack
is reachable by the NMS.
l If the following alarms are generated on the NE: SHELF-ID-CONFLICT, SHELF-ID-
MISMATCH, SHELF-WRONG-CONNECT, NEW-SHELF-ID-CONFLICT, SHELF-
LOOP, clear them before board replacement.
l If the TN51SCC board is to be replaced and the board is located in a subrack whose ID is
greater than 8, the software of the spare part for the TN51SCC board must be
V100R005C00SPC900 or a later version; otherwise, services are interrupted.
Procedure
Step 1 Select a spare board. Ensure the name, and the type of the spare board are the same as those of
the original board.
Step 3 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 4 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 5 Remove the board to be replaced. For details about how to remove a board, see Procedure of
Replacing a Board.
Step 6 If the TN51SCC board is to be replaced and the software of the SCC board version is earlier
than V100R005C00SPC900, go to Step 7, otherwise go to Step 9.
Step 7 If the SCC board to be replaced is located in a slave subrack whose ID is in the range of 2 to 8,
do the following:
1. Set the BIOS running mode of the spare SCC board to status D (1111). 8.2.1 Setting the
Jumper and DIP Switch on the SCC Board shows the settings of the four jumpers on
the SCC board.
2. Insert the spare SCC board in the slot housing the original SCC board. Wait for 15 minutes
to format the file system.
3. After the file system is formatted, remove the board. Remove the jumper caps which are
shown in 8.2.1 Setting the Jumper and DIP Switch on the SCC Board and reinsert this
SCC board to the slot.
Step 8 If the SCC board to be replaced is located in a slave subrack whose ID is greater than 8, do the
following to format the file system and upgrade the spare SCC board to V100R005SPC900 or
a later version:
1. Set the BIOS running mode of the spare SCC board to status D (1111). 8.2.1 Setting the
Jumper and DIP Switch on the SCC Board shows the settings of the four jumpers on
the SCC board.
2. Insert the spare SCC board in a vacant slot in a slave subrack whose ID is in the range of
2 to 8. Wait for 15 minutes to format the file system.
NOTE
The active SCC board configured in the slave subrack must be TN51SCC, and the software version of the
SCC board must be V100R005SPC900 or later.
3. After the file system is formatted, remove the board. Remove the jumper caps which are
shown in 8.2.1 Setting the Jumper and DIP Switch on the SCC Board and reinsert this
SCC board to the slot.
4. Wait about 15 minutes for the software of V100R005SPC900 or a later version to be
automatically loaded to the SCC board. If the STAT indicator on the board is steady green,
then the V100R005SPC900 or a later version software is successfully loaded to the SCC
board.
NOTE
You can also format the file system and upgrade the spare SCC board to V100R005SPC900 or a later version
on an idle NE. Reference to the Upgrade Guide for more information. You are advised to upgrade all spare SCC
boards in a unified mode. If required, contact Huawei engineers to provide technical support.
Step 9 Review the indicators of the new board. It takes ten minutes for a new board to work normally
after insertion. Ensure that the STAT indicator is blinking slowly (green). If the indicator gives
an abnormal indication, reinsert the board, or replace the board again. For more information
regarding indicator definitions, refer to "Board Indicators".
Step 10 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 11 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 12 Query the current alarms of the NE using the U2000.
1. In the Main Topology view, choose Fault > Browse Current Alarm from the Main Menu.
2. Click the Basic Setting and Alarm Source tabs in turn on the Filter dialog box to set the
filter conditions for the current alarms.
3. Click OK.
4. Record the current alarms of the NE.
NOTE
You can select the desired alarms and right-click to choose Save > Save Selected Records, or right-
click to choose Save > Save All Records from the shortcut menu to save the current alarms of the
NE.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
NOTE
TNxx indicates a board hardware version displayed on the PCB board.
CAUTION
Do not replace the EFI1 board during the replacement.
TN16SCC None -
TN52SCC None -
TNK2SCC None -
TN22SCC None -
NOTE
If a subrack/chassis uses two SCC boards (one is active and the other is standby), the versions of the two
SCC boards must be the same.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
For SCC 1+1 protection, replacing one SCC in the protection group does not interrupt the
communication between the NE where the SCC resides and the U2000 after a switching from
this SCC to the other SCC is performed.
Precautions
During the SCC board replacement, do not configure the NE before the new SCC board is started
up.
Procedure
Step 1 Select a spare SCC board as the replacement SCC board by referring to "Substitution
Relationships".
Step 3 Back up the NE database to the NMS server. This is to record the NE database for future reference
when the SCC board is replaced.
1. In the Main Topology view, choose Administration > NE Software Management > NE
Data Backup/Restoration from the Main Menu.
2. Right-click the device(s) that you want to back up in the NE View table.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
3. Select Backup... to open the Backup dialog.
4. Select the option NMS Server or NMS Client to backup the selected device information.
NOTE
By default the NMS Server is selected. If the NMS Server is selected, the selected device information
is stored on the NMS server.
5. Optional: If the NMS Client is selected, click to select the location where the device
data are to be backed up.
6. Click Start to start the backup operation for the selected device(s). On the NE View tab
page, the backup progress is displayed.
7. When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/
yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd"
indicates the date when the backup is created, and "hhmmss" indicates the time when the
backup is created.
Step 4 Follow the steps below to query the working state of the board to be replaced.
1. In the NE Explorer, click the NE and choose Configuration > Board 1+1 Protection from
the Function Tree.
2. Click Query.
Step 5 If the board to be replaced is the active board, go to Step 6. Otherwise, go to Step 7.
Step 6 If the board to be replaced is the working board, follow the steps below to perform an active/
standby switching on the U2000.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired SCC Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
4. Click Query. If the Working Board is not the board to be replaced, the switching is
successful.
5. Query the alarms and performance events on the U2000. Check if services are normal. If
services are normal, there must be no new abnormal alarms or performances. The switching
is successful.
Step 7 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 8 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 9 Inform the onsite maintenance engineer and replace the board. For details about how to replace
a board, refer to Procedure of Replacing a Board.
Step 10 Set the four jumpers on the spare SCC board to set the BIOS running mode. Then insert the SCC
board to the slot housing the original SCC board to format the file system of the new SCC board.
1. Set the BIOS running mode of the spare SCC board to status D (1111) to clear all the data
in the flash memory except the board manufacturing information. shows the settings of the
four jumpers on the SCC board.
2. Insert the spare SCC board in the slot housing the original SCC board. When the STAT
indicator on the inserted SCC board is blinking green quickly, the file system is being
formatted. When the STAT indicator is steady green, the formatting is completed. The
formatting takes about 15 minutes.
NOTE
If the spare SCC board is a version earlier than V100R006C01SPC300, the formatting is not indicated on
any board indicators. Wait 15 minutes until the system formatting is completed.
Step 11 After the file system of the SCC board is formatted completely, remove the board. Remove the
jumper caps which you set in Step 10. Reinsert this SCC board to the slot.
NOTE
Step 13 View the indicators on the front panel of the new board. It takes approximately 90 minutes for
a new board to work normally after insertion. Ensure that the STAT indicator is steady green.
If the indicator is not blinking slowly (green), you need to reinsert the board or select a new
replacement board. For details about the indicators, see Board Indicators.
NOTE
After the new board works normally, the MEA alarm will be reported on the U2000.
Step 14 Follow the steps below to switch the active/standby state of the SCC boards back to the original
state.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click SCC Board 1+1 Protection. Select Working/
Protection Switching from the shortcut menu. Click OK in the window displayed.
NOTE
After you start the new SCC board, the system automatically synchronizes the data between the existing
SCC board and the new SCC board. After the data backup is complete, ensure that the STAT indicator is
steady green, you can perform the preceding step to initiate active/standby switching.
Because data backup cannot be automatically performed between TN22SCC and TN23SCC, active/standby
switching can be performed only when the two SCC boards are replaced with TN23SCC.
NOTE
If you click Cancel, the board is successfully upgraded, but you need to manually upload the NE data
later.
5. Click OK to confirm the uploading of the NE data again.
NOTE
If you click Cancel, the board is successfully upgraded, but you need to manually upload the NE data
later.
6. Click Close in the displayed Result dialog box.
NOTE
Step 16 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 17 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
5. Check whether the switching state is correct. Perform a switching test.
NOTE
For details about how to set these parameters, see iManager U2000 Operator Guide for NG WDM NE
Management.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
Step 19 Repeat Step 5 to Step 18 replace the other SCC board in the protection group and ensure that
the two SCC boards are of the same type after the replacement.
----End
8.3.3.1 Replacing the SCC with the Database Backed Up to the NMS
Before replacing an SCC board, you can back up the NE database to the NMS. In this manner,
you can restore the NE database from the NMS after replacing the SCC board.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
l For the OptiX OSN 8800 T32, the SCC is housed in IU28 by default. If another board is
installed in IU11, SCC 1+1 protection cannot be configured. In this case, replacing the SCC
in an NE interrupts the communication between the NE and the U2000.
l For the OptiX OSN 6800A, the SCC is housed in IU18 by default. When IU17 is occupied
by another board, SCC 1+1 protection cannot be configured. In this case, replacing the SCC
in an NE interrupts the communication between the NE and the U2000.
Precautions
CAUTION
l Operations on the U2000 must be performed in the network management center.
l Operations on the Web LCT must be performed on site.
Procedure
Step 1 Select a spare SCC board as the replacement SCC board by referring to "Substitution
Relationships".
Step 2 Review and record the current NE alarms.
Step 3 Back up the NE database to the NMS server. This is to record the NE database for future reference
when the SCC board is faulty.
1. In the Main Topology view, choose Administration > NE Software Management > NE
Data Backup/Restoration from the Main Menu.
2. Right-click the device(s) that you want to back up in the NE View table.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
3. Select Backup... to open the Backup dialog.
4. Select the option NMS Server or NMS Client to backup the selected device information.
NOTE
By default the NMS Server is selected. If the NMS Server is selected, the selected device information
is stored on the NMS server.
5. Optional: If the NMS Client is selected, click to select the location where the device
data are to be backed up.
6. Click Start to start the backup operation for the selected device(s). On the NE View tab
page, the backup progress is displayed.
7. When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/
yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd"
indicates the date when the backup is created, and "hhmmss" indicates the time when the
backup is created.
Step 4 Follow the steps below to query the system to obtain the user management list of the NE.
1. In the NE Explorer, select an NE and choose Security > NE User Management from the
Function Tree.
2. Click Query.
3. Record the NE user data returned by the system for future restoration of the NE user data.
NOTE
Also record the password for each user account of the NE.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 7 Inform the onsite maintenance engineer and remove the board. For details about how to remove
a board, see Procedure of Replacing a Board.
Step 8 Set the four jumpers on the spare SCC board so as to set the BIOS running mode of the board
and then insert it to the slot housing the original SCC board. In this manner, the database on the
new SCC board is cleared. 8.2.1 Setting the Jumper and DIP Switch on the SCC Board shows
the settings of the four jumpers on the SCC board.
1. Set the BIOS running mode of the spare SCC board to status C (1011) to clear the database
in the flash memory.
2. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
3. Set the BIOS running mode of the spare SCC board to status A (1010) to clear the system
parameter area.
4. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
Step 9 After the database of the SCC board is cleared completely, remove the board. Remove the jumper
caps which are shown in Step 8. After that, reinsert this SCC board to the slot.
Step 10 After the new SCC board is started, connect the Web LCT to the NE.
1. Disconnect the cables from the NM_ETH1 and NM_ETH2 ports (if connected). That is,
disconnect the NE from the computer where the U2000 (hereinafter the computer is referred
to as U2000) is installed.
2. Connect the Web LCT to NM_ETH1.
3. Set the IP address of the Web LCT to ensure that Web LCT is in the same IP subnet segment
as the NE IP address. If the IP address of the Web LCT and the NE IP address are in different
network segments, the Web LCT cannot be connected to the NE.
NOTE
The new board is initiated at factory, and the default IP subnet segment of the board is 129.9.*.*.
4. Log in the Web LCT with the user name admin, and the initial password Changme_123.
4. Set Domain Type to GNE IP Domain or GNE IP Address. Enter an IP address in the
Domain Address field.
5. Click OK.
NOTE
Repeat step 3 through 5 to add multiple search domains.
6. Close the Manage Domain Search dialog box.
7. Select the appropriate network segment IP addresses within the Domain and click
Search.
NOTE
l The NE search function searches for only the NEs in the specified network segment.
l When the search is in progress, you can click End Search.
8. After the search is complete, select an NE from the list and click Add NE. A prompt
message is displayed, indicating that the NE is successfully added. Click OK.
9. Select the NE to which you want to log in and click NE Login in the lower right corner or
right-click the NE and choose NE Login. In the NE Login dialog box that is displayed,
enter sonet and SONET in the User Name and Password fields.Then click OK.
TIP
Step 12 Modify the NE IP, gateway IP and subnet mask based on the original information using the Web
LCT.
1. In the NE Explorer, select Configuration > NE Attribute from the Function Tree.
2. Enter the NE IP address, gateway IP address and subnet mask, and click Apply.
3. Click OK after the Warning dialog box pops up.
4. Click OK after the Warning dialog box about communication interruption between NEs
pops up.
NOTE
If the NE IP addresses before and after the modification are in different network segments, the Web LCT cannot
be connected to the NE. When this occurs, set the IP address of the Web LCT in the same network segment as
the NE IP address.
Step 13 Modify the NE name based on the original information using the Web LCT.
1. In the NE Explorer, choose Configuration > NE Attribute from the Function Tree.
2. Enter the NE Name, and click Apply.
Step 15 According to the NE user management list queried in Step 4,create an NE's user using the Web
LCT.
1. In the NE Explorer, select the NE and choose Security > NE User Management from
the function tree.
2. Click New. The Add NE User dialog box is displayed.
3. Refer to Table 8-11 to set attribute values of the new user.
On the Web For example: The name of the NE user being created.
LCT: User USER A string, containing 4 to 16 characters. It must
include at least one letter, and no punctuation is
permitted. It cannot be the same as an existing NE
user name.
On the Web RTRV, PROV, The operations carried out by the NE user are
LCT: Level MAINT and classified into four levels, RTRV, PROV,
SUPER MAINT, and SUPER from the lowest level to the
highest. Higher level users can perform all the
functions that lower level users can. For example, an
operation level user has all the rights of a monitor
level user. The system level user with the highest
level has all rights. The detailed rights settings for
each level are:
RTRV: all query commands, log in, log out, and
modification of its own password.
PROV: all settings for fault and performance, partial
security settings, and partial configuration.
MAINT: partial security settings, partial
configuration, communication settings, and log
management.
SUPER: all security settings, all configurations.
NOTE
For a super user, only one user at a time can log in to an
NE. In the case of an RTRV, PROV, MAINT or user, a
maximum of 16 users can log in to an NE concurrently.
An RTRV, PROV, or MAINT user cannot modify the login
password. The password can be modified only by a super
user.
Time of Any integer This option is in effect only when Yes is selected for
Canceling from 5 to 60 Canceling User Automatically. Set the time to
User Default: 60 automatically cancel the user.
Automatically
(m)
User Valid Any integer The period in which the user's name is in effect. The
Till (days) from 1 to 999 unit measurement is day.
This option is in effect only when No is selected for
User Permanently Valid.
Password Any integer The period in which the password is in effect. The
Valid Till from 25 to 999 unit of measurement is day.
(days) This option is in effect only when No is selected for
Password Permanently Valid.
4. Click Apply.
Step 17 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 18 If the software version of the spare SCC board is different from the software version of the SCC
board to be replaced, go to Step 19; otherwise, go to Step 20.
Step 19 Upgrade or downgrade the software of the spare SCC board. For details, see the Upgrade
Guide. Ensure that the software version of the spare SCC board is consistent with that of the
SCC board to be replaced.
l If NMS Client is selected, click to select the backup file from the NMS Client.
The selected backup file path is displayed in the Select File field.
6. Click OK.
NOTE
The selected backup file path from the NMS Server or NMS Client is displayed in the File Name drop-
down list.
7. Click Start, the Operation Confirmation dialog box is displayed.
8. In the Operation Confirmation dialog, click Yes to start the recovery operation. The
recovery operation status is displayed in the NE View table.
NOTE
You must activate the NE database within five minutes after restoring it.
CAUTION
During the process from backing up databases to restoring databases, do not modify the NE
configurations to avoid database inconsistency.
5. Optional: Click the icon in Deliver To Board Activate. This icon is changed to .
Click Start to start the database activation process. The progress of the database activation
is displayed on the NE View tab.
NOTE
NOTE
After this procedure, you can use the original user name and password to access the NE using the
U2000.
After recovering the NE database, the U2000 will report a MEA alarm.
Synchronized Fiber/Cable: Indicates the fibers that exist on both the U2000 and NE sides.
Uncreated Fiber/Cable in NMS: Indicates the fibers that exist only on the NE side.
Uncreated Fiber/Cable in NE: Indicates the fibers that exist only on the U2000 side.
4. If there are fibers in Uncreated Fiber/Cable in NMS or Uncreated Fiber/Cable in NE,
select all the fibers. Click Create Fiber/Cable. The Operation Result dialog box is
displayed. Click Close. The synchronized fibers are displayed on the Synchronized Fiber/
Cable list.
5. If conflicting fibers are configured and you fail to create a fiber, click Delete Fiber/
Cable to delete the incorrect fiber and click Create Fiber/Cable to re-create the failed
fibers.
Step 23 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
If you click Cancel, the board is successfully upgraded, but you need to manually upload the NE data
later.
5. Click OK to confirm the uploading of the NE data again.
NOTE
If you click Cancel, the board is successfully upgraded, but you need to manually upload the NE data
later.
6. Click Close in the displayed Result dialog box.
NOTE
Step 25 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 26 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
NOTE
For details to set these parameters, see iManager U2000 Operator Guide for NG WDM NE Management.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
l For the OptiX OSN 8800 T32, the SCC is housed in IU28 by default. If another board is
installed in IU11, SCC 1+1 protection cannot be configured. In this case, replacing the SCC
in an NE interrupts the communication between the NE and the U2000.
l For the OptiX OSN 6800A, the SCC is housed in IU18 by default. When IU17 is occupied
by another board, SCC 1+1 protection cannot be configured. In this case, replacing the SCC
in an NE interrupts the communication between the NE and the U2000.
Precautions
CAUTION
l After the database of the NE is restored on the CF card, the restoration must be completed
within two hours after you install the replacement SCC is installed. If you wait more than
two hours to restore the database of the NE on the CF card, the data automatically saved on
the NE overwrites the original data stored on the CF card. If the original data is overwritten,
the original database of the NE cannot be restored.
l Operations on the U2000 must be performed in the network management center.
l Operations on the Web LCT must be performed on site.
Procedure
Step 1 Select a spare SCC board as the replacement SCC board by referring to "Substitution
Relationships".
Step 4 Wait four minutes later, and query the system to obtain the user management list of the NE by
following the steps below.
1. In the NE Explorer, select an NE and choose Security > NE User Management from the
Function Tree.
2. Click Query.
3. Record the NE user data returned by the system for future restoration of the NE user data.
NOTE
Also record the password for each user account of the NE.
Step 6 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 7 Remove the SCC board to be replaced. For details about how to remove a board, see Procedure
of Replacing a Board.
Step 8 On the SCC board that has been removed, hold the CF card and pull the card out of the CF card
slot. Put the SCC into an ESD bag.
NOTE
Step 9 Set the four jumpers on the spare SCC board so as to set the BIOS running mode of the board
and then insert it to the slot housing the original SCC board. In this manner, the database on the
new SCC board is cleared. 8.2.1 Setting the Jumper and DIP Switch on the SCC Board shows
the settings of the four jumpers on the SCC board.
1. Set the BIOS running mode of the spare SCC board to status C (1011) to clear the database
in the flash memory.
2. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
3. Set the BIOS running mode of the spare SCC board to status A (1010) to clear the system
parameter area.
4. Insert the spare SCC board in the slot housing the original SCC board. Wait for 2 minutes
until the database on the spare SCC board is cleared. If the spare SCC board is of
V100R006C03 or a later version, the database is being cleared when the STAT indicator
on the SCC board is quickly blinking and the database clearing is complete when the STAT
indicator is steady green.
Step 10 After the database of the SCC board is cleared completely, remove the board. Remove the jumper
caps which are shown in Step 9. After that, reinsert this SCC board to the slot.
Step 11 After the new SCC board is started, connect the Web LCT to the NE.
1. Disconnect the cables from the NM_ETH1 and NM_ETH2 ports (if connected). That is,
disconnect the NE from the computer where the U2000 (hereinafter the computer is referred
to as U2000) is installed.
2. Connect the Web LCT to NM_ETH1.
3. Set the IP address of the Web LCT to ensure that Web LCT is in the same IP subnet segment
as the NE IP address. If the IP address of the Web LCT and the NE IP address are in different
network segments, the Web LCT cannot be connected to the NE.
NOTE
The new board is initiated at factory, and the default IP subnet segment of the board is 129.9.*.*.
4. Log in the Web LCT with the user name admin, and the initial password Changme_123.
Step 12 Create the NE using the Web LCT.
1. Click NE Search > Advanced Search in the NE List. The Search NE dialog box is
displayed.
2. Click Manage Domain. The Manage Domain Search dialog box is displayed.
3. Click Add. The New Domain dialog box is displayed.
4. Set Domain Type to GNE IP Domain or GNE IP Address. Enter an IP address in the
Domain Address field.
5. Click OK.
NOTE
Repeat step 3 through 5 to add multiple search domains.
6. Close the Manage Domain Search dialog box.
7. Select the appropriate network segment IP addresses within the Domain and click
Search.
NOTE
l The NE search function searches for only the NEs in the specified network segment.
l When the search is in progress, you can click End Search.
8. After the search is complete, select an NE from the list and click Add NE. A prompt
message is displayed, indicating that the NE is successfully added. Click OK.
9. Select the NE to which you want to log in and click NE Login in the lower right corner or
right-click the NE and choose NE Login. In the NE Login dialog box that is displayed,
enter sonet and SONET in the User Name and Password fields.Then click OK.
TIP
Step 13 Modify the NE IP, gateway IP and subnet mask based on the original information using the Web
LCT.
1. In the NE Explorer, select Configuration > NE Attribute from the Function Tree.
2. Enter the NE IP address, gateway IP address and subnet mask, and click Apply.
3. Click OK after the Warning dialog box pops up.
4. Click OK after the Warning dialog box about communication interruption between NEs
pops up.
NOTE
If the NE IP addresses before and after the modification are in different network segments, the Web LCT cannot
be connected to the NE. When this occurs, set the IP address of the Web LCT in the same network segment as
the NE IP address.
Step 14 Modify the NE name based on the original information using the Web LCT.
1. In the NE Explorer, choose Configuration > NE Attribute from the Function Tree.
2. Enter the NE Name, and click Apply.
Step 16 According to the NE user management list queried in Step 4,create an NE's user using the Web
LCT.
1. In the NE Explorer, select the NE and choose Security > NE User Management from
the function tree.
2. Click New. The Add NE User dialog box is displayed.
3. Refer to Table 8-12 to set attribute values of the new user.
On the Web For example: The name of the NE user being created.
LCT: User USER A string, containing 4 to 16 characters. It must
include at least one letter, and no punctuation is
permitted. It cannot be the same as an existing NE
user name.
On the Web RTRV, PROV, The operations carried out by the NE user are
LCT: Level MAINT and classified into four levels, RTRV, PROV,
SUPER MAINT, and SUPER from the lowest level to the
highest. Higher level users can perform all the
functions that lower level users can. For example, an
operation level user has all the rights of a monitor
level user. The system level user with the highest
level has all rights. The detailed rights settings for
each level are:
RTRV: all query commands, log in, log out, and
modification of its own password.
PROV: all settings for fault and performance, partial
security settings, and partial configuration.
MAINT: partial security settings, partial
configuration, communication settings, and log
management.
SUPER: all security settings, all configurations.
NOTE
For a super user, only one user at a time can log in to an
NE. In the case of an RTRV, PROV, MAINT or user, a
maximum of 16 users can log in to an NE concurrently.
An RTRV, PROV, or MAINT user cannot modify the login
password. The password can be modified only by a super
user.
Time of Any integer This option is in effect only when Yes is selected for
Canceling from 5 to 60 Canceling User Automatically. Set the time to
User Default: 60 automatically cancel the user.
Automatically
(m)
User Valid Any integer The period in which the user's name is in effect. The
Till (days) from 1 to 999 unit measurement is day.
This option is in effect only when No is selected for
User Permanently Valid.
Password Any integer The period in which the password is in effect. The
Valid Till from 25 to 999 unit of measurement is day.
(days) This option is in effect only when No is selected for
Password Permanently Valid.
4. Click Apply.
Step 17 Recover the network connection of the NE.
1. Pull out the network cable which connected the NM_ETH1 port to the Web LCT.
2. Connect the network cable removed.
Step 18 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 19 Query the software version of the spare SCC board, if it is different from the software version
of the SCC board to be replaced, go to Step 20, otherwise go to Step 21.
Step 20 Upgrade or downgrade the software of the spare SCC board. For details, see the Upgrade
Guide. Ensure that the software version of the spare SCC board is consistent with that of the
SCC board to be replaced.
Step 21 After the SCC board is started, remove the SCC board inserted just now. Insert the CF card that
has been removed in Step 8 into the CF card slot on the SCC board. Then, insert the SCC.
Step 22 Restore the initial database of the NE using the U2000.
1. In the Main Topology view, choose Configuration > NE Configuration Data
Management from the Main Menu, and the NE Configuration Data Management
interface is displayed.
NOTE
If the database is performing a scheduled backup task, the message "NOT IN VALID STATE, FAILED
TO RECOVER FROM CF" will be displayed on the NMS, indicating that restoring data from the CF card
will fail. In this scenario, you are advised to wait 5 minutes, and restore data again from the CF card after
the database finishes the scheduled backup task.
6. Click Closeafter an Operation Result dialog box is displayed.
NOTE
After the NE databases are restored, the NE software issues the data in the CF card to only the SCC board
but not other boards. To ensure that the configurations in the SCC board and the configurations in other
boards are consistent, you need to perform warm resets on other boards. You can use the TL1 command
to perform warm resets on all the boards, the TL1 command is : init-sys::slot-all:z::warm.
NOTE
After this procedure, you can use the original user name and password to access the NE using the U2000.
After recovering the NE database, the U2000 will report a MEA alarm.
CAUTION
During the process from backing up databases to restoring databases, do not modify the NE
configurations to avoid database inconsistency.
Synchronized Fiber/Cable: Indicates the fibers that exist on both the U2000 and NE sides.
Uncreated Fiber/Cable in NMS: Indicates the fibers that exist only on the NE side.
Uncreated Fiber/Cable in NE: Indicates the fibers that exist only on the U2000 side.
4. If there are fibers in Uncreated Fiber/Cable in NMS or Uncreated Fiber/Cable in NE,
select all the fibers. Click Create Fiber/Cable. The Operation Result dialog box is
displayed. Click Close. The synchronized fibers are displayed on the Synchronized Fiber/
Cable list.
5. If conflicting fibers are configured and you fail to create a fiber, click Delete Fiber/
Cable to delete the incorrect fiber and click Create Fiber/Cable to re-create the failed
fibers.
Step 24 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
3. The dialog box of Replacement Board Type is displayed, select the name of the target
board to be replaced within the Usable Board Type. Click OK.
4. After the replacement, a prompt appears asking you whether to immediately upload the NE
data. Click OK.
NOTE
If you click Cancel, the board is successfully upgraded, but you need to manually upload the NE data
later.
5. Click OK to confirm the uploading of the NE data again.
NOTE
If you click Cancel, the board is successfully upgraded, but you need to manually upload the NE data
later.
6. Click Close in the displayed Result dialog box.
NOTE
Step 26 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 27 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
NOTE
For details to set these parameters, see iManager U2000 Operator Guide for NG WDM NE Management.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
The impact caused by replacing an SCC without protection is as follows: The SCC is housed in
the active slot by default. When the standby slot is not occupied by another board, it is available
for another SCC to implement 1+1 protection with the SCC in the active slot. In this case,
replacing one of the SCC in the protection group does not interrupt the communication between
the NE where the SCC resides and the U2000 after a switching from this SCC to the other SCC
is performed.
NOTE
The logical board for the SCC board in the default slot cannot be deleted from the U2000; therefore, two spare
SCC boards must be prepared when this method is used to replace the SCC board.
Precautions
CAUTION
l Operations on the U2000 must be performed in the network management center.
l Operations on the Web LCT must be performed on site.
Procedure
Step 1 Select a spare SCC board as the replacement SCC board by referring to "Substitution
Relationships".
Step 2 Back up the NE database to the NMS server. This is to record the NE database for future reference
when the SCC board is replaced.
1. In the Main Topology view, choose Administration > NE Software Management > NE
Data Backup/Restoration from the Main Menu.
2. Right-click the device(s) that you want to back up in the NE View table.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
3. Select Backup... to open the Backup dialog.
4. Select the option NMS Server or NMS Client to backup the selected device information.
NOTE
By default the NMS Server is selected. If the NMS Server is selected, the selected device information
is stored on the NMS server.
5. Optional: If the NMS Client is selected, click to select the location where the device
data are to be backed up.
6. Click Start to start the backup operation for the selected device(s). On the NE View tab
page, the backup progress is displayed.
7. When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/
yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd"
indicates the date when the backup is created, and "hhmmss" indicates the time when the
backup is created.
Step 3 Set the jumpers on the spare SCC board using the following methods and insert it to the specified
slot for a standby SCC board. In this manner, the file system of the new SCC board is formatted.
NOTE
After inserting the spare SCC board to the specified slot for a standby SCC board, you need to add a corresponding
logical board on the U2000. Then, the system automatically configures 1+1 protection for the SCC.
1. Set the BIOS running mode of the spare SCC board to status D (1111) to clear all the data
in the flash memory except the board manufacturing information. shows the settings of the
four jumpers on the SCC board.
2. Insert the spare SCC board in the slot housing the original SCC board. When the STAT
indicator on the inserted SCC board is blinking green quickly, the file system is being
formatted. When the STAT indicator is steady green, the formatting is completed. The
formatting takes about 15 minutes.
NOTE
If the spare SCC board is a version earlier than V100R006C01SPC300, the formatting is not indicated on
any board indicators. Wait 15 minutes until the system formatting is completed.
Step 4 After the file system of the SCC board is formated completely, remove the board. Remove the
jumper caps which are shown in Step 3. After that, reinsert this SCC board to the slot.
NOTE
Step 5 View the indicators on the front panel of the new board. It takes approximately 90 minutes for
a new board to work normally after insertion. Ensure that the STAT indicator is steady green.
If the indicator is not steady green, you need to reinsert the board or select a new replacement
board. For details about the indicators, see Board Indicators.
Step 6 Follow the steps below to perform an active/standby switching on the U2000.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired SCC Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
4. Click Query. If the Working Board is not the board to be replaced, the switching is
successful.
5. Query the alarms and performance events on the U2000. Check if services are normal. If
services are normal, there must be no new abnormal alarms or performances. The switching
is successful.
NOTE
After you start the new SCC board, the system automatically synchronizes the data between the existing
SCC board and the new SCC board. After data backup completes, you can perform the preceding step to
initiate active/standby switching.
Step 7 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
NOTE
For details to set these parameters, see iManager U2000 Operator Guide for NG WDM NE Management.
NOTE
You can select the desired alarms and right-click to choose Save > Save Selected Records, or right-
click to choose Save > Save All Records from the shortcut menu to save the current alarms of the
NE.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
Step 9 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 10 Remove the board to be replaced and put it into an ESD bag. Insert a new board in the slot. For
detailed operations, see Step 1 to Step 5.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Before replacing an SCC board with a spare SCC board, the battery jumper on the spare
board must be set. The 1X3 jumper inside the board is used to enable or disable the power
supply from the battery. Ensure that pin 1 and pin 2 on the battery jumper are capped. Then,
cap pin 2 and pin 3 on the battery jumper and use a multimeter to measure the battery
voltage. If the voltage is lower than 3 V, the battery is not working. In this case, the SCC
board needs to be replaced.
l The communication between the master and slave subracks is normal and the slave subrack
is reachable by the NMS.
l If the communication between the master and slave subracks is abnormal, rectify the fault
before replacing the SCC board in the slave subrack.
l If the following alarms are generated on the NE: SHELF-ID-CONFLICT, SHELF-ID-
MISMATCH, SHELF-WRONG-CONNECT, NEW-SHELF-ID-CONFLICT, SHELF-
LOOP, clear them before board replacement.
If the SCC is configured with 1+1 protection, replacing the SCC does not affect the system.
If an SCC is not configured with 1+1 protection, replacing the SCC has the following effects:
l The fan is automatically changed to the "High Speed" mode.
l The ESC and OSC communication of the subrack where the replacement SCC resides fails.
l The PWR-FAIL alarm of the subrack where the replacement SCC resides cannot be
reported.
l Certain optical boards in the slave subrack housing the SCC board to be replaced go offline
and cannot be managed; however, the services on these boards are not affected.
Procedure
Step 1 Select a spare SCC board as the replacement SCC board by referring to "Substitution
Relationships".
Step 3 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 4 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 5 Remove the board to be replaced. For details about how to remove a board, see Procedure of
Replacing a Board.
Step 6 Set the four jumpers on the spare SCC board to set the BIOS running mode. Then insert the SCC
board to the slot housing the original SCC board to format the file system of the new SCC board.
1. Set the BIOS running mode of the spare SCC board to status D (1111) to clear all the data
in the flash memory except the board manufacturing information. shows the settings of the
four jumpers on the SCC board.
2. Insert the spare SCC board in the slot housing the original SCC board. When the STAT
indicator on the inserted SCC board is blinking green quickly, the file system is being
formatted. When the STAT indicator is steady green, the formatting is completed. The
formatting takes about 15 minutes.
NOTE
If the spare SCC board is a version earlier than V100R006C01SPC300, the formatting is not indicated on
any board indicators. Wait 15 minutes until the system formatting is completed.
Step 7 After the file system of the SCC board is formatted completely, remove the board. Remove the
jumper caps which are shown in Step 6. After that, reinsert this SCC board to the slot.
NOTE
If the SCC board is isolated during the software upgrade, you must manually release the board isolation after
the software upgrade is completed. When the SCC board isolation is released, it will be automatically matched
and reset.
Step 9 Review the indicators of the new board. It takes ten minutes for a new board to work normally
after insertion. Ensure that the STAT indicator is steady green. If the indicator gives an abnormal
indication, reinsert the board, or replace the board again. For more information regarding
indicator definitions, refer to Board Indicators.
NOTE
After the new board works normally, the U2000 will report a MEA alarm.
If you click Cancel, the board is successfully upgraded, but you need to manually upload the NE data
later.
5. Click OK to confirm the uploading of the NE data again.
NOTE
If you click Cancel, the board is successfully upgraded, but you need to manually upload the NE data
later.
6. Click Close in the displayed Result dialog box.
NOTE
After changing the board type by setting Replace Board Type on the U2000, the MEA alarm is cleared.
Step 11 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
2. Click the Basic Setting and Alarm Source tabs in turn on the Filter dialog box to set the
filter conditions for the current alarms.
3. Click OK.
4. Record the current alarms of the NE.
NOTE
You can select the desired alarms and right-click to choose Save > Save Selected Records, or right-
click to choose Save > Save All Records from the shortcut menu to save the current alarms of the
NE.
NOTE
After replacing the system control board, ensure that the monitoring of the PWR-FAIL alarm is enabled.
If the PWR-FAIL alarm occurs, check whether the jumper cap is correctly placed over the battery jumper.
If yes, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out.
The board must be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
XCH
TN52XCH and TN16XCH are the versions of this boards. The description of replacing the
TN16XCH board will be described separately because its functions are different from those of
a common cross-connect board.
XCT
Original Substitute Board Substitution Rules
Board
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Impact on System
When cross-connect 1+1 board protection is configured, replacing the cross-connect board
brings no impact on the services in case of a normal switching.
Procedure
Step 1 Select a spare board to use as a replacement board. Ensure the name, version and model number
of the new board are the same as those of the original.
NOTE
If the version is inconsistent, determine if the board with different versions can be replaced. For more information
regarding the replacement relationship between board versions, see "Substitution Relationship".
Step 3 Perform an active/standby switching on the U2000. Check whether the BUS-ERR alarm has
occurred in the standby cross-connect board. If it has occurred, clear the alarm before the
replacement. Otherwise, replacing the board causes a service interruption.
NOTE
For OptiX OSN 8800 T32, assume that the cross-connect board to be replaced in slot 9 is the active cross-
connect board, and that the cross-connect board in slot 10 works normally and no BUS-ERR alarm is
generated on the subrack.
For OptiX OSN 8800 T64, assume that the cross-connect board to be replaced in slot 9 (slot 10) is the
active cross-connect board, and that the cross-connect board in slot 43 (slot 44) works normally and no
BUS-ERR alarm is generated on the subrack.
NOTE
For OptiX OSN 6800A, assume that the XCS board to be replaced is located in slot 9 and it is the main
XCS board, and that the XCS board in slot 10 works normally and the subrack where it is located has no
BUS-ERR alarm.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired XCS Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
4. Click Query. If the Working Board is not the board to be replaced, the switching is
successful.
5. Query the alarms and performance events on the U2000. Check if services are normal. If
services are normal, there must be no new abnormal alarms or performances. The switching
is successful.
Step 4 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 5 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 6 Inform the onsite maintenance engineer and replace the board. For details about how to remove
a board, see Procedure of Replacing a Board.
NOTE
After the board is replaced, the NE software delivers the configuration of the original board automatically.
Step 7 Check the indicators of the new board. It takes four or five minutes for a new board to work
normally after insertion. Ensure that the STAT indicator is steady on green. If the indicator is
not steady on green, you need to reinsert the board or select a new replacement board. For details
about the indicators, see Board Indicators.
Step 8 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 9 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 10 Follow the steps below to cancel the switching.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired XCS Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
Step 11 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Impact on System
When you replace the cross-connect board without protection, that is, the only cross-connect
board (suppose it is in IU9) on an NE.
l For OptiX OSN 6800A,
– When IU10 is occupied by other boards, cross-connect board protection cannot be
configured. Replacement of the cross-connect board causes interruption of services.
– When IU10 is not occupied by other boards, it is available for another cross-connect
board to realize 1+1 protection with the cross-connect board in IU10. When the cross-
connect board has 1+1 protection and when the switching is normal, replacement of the
cross-connect board does not cause service interruption
Procedure
Step 1 Select a spare board to use as a replacement board. Ensure the name, version and model number
of the new board are the same as those of the original board.
NOTE
If the version is inconsistent, determine if the board with different versions can be replaced. For more
information regarding the replacement relationship between board versions, see "Substitution
Relationship".
Step 3 For OptiX OSN 6800A, if IU10 is not occupied by other boards, insert another cross-connect
board in IU10 and add a corresponding logical board on the U2000. Then the system
automatically configures the cross-connect board 1+1 protection. For steps to replace an cross-
connect board that is configured with board 1+1 protection, see 8.4.2 Under Board 1+1
Protection.
Step 4 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 5 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 6 Inform the onsite maintenance engineer and replace the board. For details about how to remove
a board, see Procedure of Replacing a Board.
NOTE
After the board is replaced, the NE software delivers the configuration of the original board automatically.
Step 7 Check the indicators of the new board. It takes four or five minutes for a new board to work
normally after insertion. Ensure that the STAT indicator is steady on green. If the indicator is
not steady on green, you need to reinsert the board or select a new replacement board. For details
about the indicators, see Board Indicators.
Step 8 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 9 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 10 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
----End
8.5.1 Setting the Jumper and DIP Switch on the TN16XCH Board
This section describes how to set the battery jumpers and BIOS DIP switches on the spare
TN16XCH board before replacing the TN16XCH board.
The battery on the TN16XCH helps to ensure that the configuration is kept upon a power failure
of the TN16XCH. If the board is in use, place a jumper cap over the battery jumper to make a
short circuit, which allows the battery to supply power normally. If the board is not in use, use
a jumper cap to disconnect the battery jumper.
The BIOS DIP switches helps clear the system parameter area and database in the flash memory
on the board. Table 8-13 shows the function of the BIOS jumper. The value that can be set by
using each of the DIP switch on the board is a binary value 0 or 1. When the DIP switch is ON,
the value of the corresponding bit is set to 1.
Figure 8-16 shows the position of DIP switches on the TN16XCH board.
1 2 3 4
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
l Before replacing an board, the battery jumper on the spare board must be set. The 1X3
jumper inside the board is used to enable or disable the power supply from the battery.
Ensure that pin 1 and pin 2 on the battery jumper are capped. Then, cap pin 2 and pin 3 on
the battery jumper and use a multimeter to measure the battery voltage. If the voltage is
lower than 3 V, the battery is not working. In this case, the SCC board needs to be replaced.
For TN16XCH 1+1 protection, replacing one of the TN16XCH in the protection group does not
interrupt the communication between the NE where the TN16XCH resides and the U2000 after
a switching from this TN16XCH to the other TN16XCH is performed.
Procedure
Step 1 Select a spare TN16XCH board as the replacement board. Ensure that the spare TN16XCH board
and the TN16XCH board to be replaced have the same name and type.
Step 3 Back up the NE database to the NMS server. This is to record the NE database for future reference
when the TN16XCH board is replaced.
1. In the Main Topology view, choose Administration > NE Software Management > NE
Data Backup/Restoration from the Main Menu.
2. Right-click the device(s) that you want to back up in the NE View table.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
3. Select Backup... to open the Backup dialog.
4. Select the option NMS Server or NMS Client to backup the selected device information.
NOTE
By default the NMS Server is selected. If the NMS Server is selected, the selected device information
is stored on the NMS server.
5. Optional: If the NMS Client is selected, click to select the location where the device
data are to be backed up.
6. Click Start to start the backup operation for the selected device(s). On the NE View tab
page, the backup progress is displayed.
7. When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/
yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd"
indicates the date when the backup is created, and "hhmmss" indicates the time when the
backup is created.
Step 4 Follow the steps below to review the working state of the board to be replaced.
1. In the NE Explorer, click the NE and choose Configuration > Board 1+1 Protection from
the Function Tree.
2. Click Query.
Step 5 If the board to be replaced is the active board, go to Step 6. Otherwise, go to Step 9.
Step 6 If the board to be replaced is the working board, follow the steps below to perform an active/
standby switching on the U2000.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired SCC Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
4. Click Query. If the Working Board is not the board to be replaced, the switching is
successful.
5. Query the alarms and performance events on the U2000. Check if services are normal. If
services are normal, there must be no new abnormal alarms or performances. The switching
is successful.
Step 7 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 8 On the NMS, enable the removal indication function for the board to be replaced.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 9 Inform the onsite maintenance engineer and replace the board. For more information regarding
how to remove a board, refer to Procedure of Replacing a Board.
Step 10 Set the DIP switch on the spare TN16XCH board to set the BIOS running mode and then insert
the TN16XCH board to the slot housing the original TN16XCH board. In this manner, the
database on the new TN16XCH board is cleared.
1. Set the BIOS running mode of the spare TN16XCH board to status D (1111) to format the
file system in the flash memory. 8.5.1 Setting the Jumper and DIP Switch on the
TN16XCH Board shows the settings of the DIP switch on the TN16XCH board.
2. Insert the spare TN16XCH board to the slot housing the original TN16XCH board. Wait
for 15 minutes to allow the database to be cleared.
Step 11 After the database on the new TN16XCH board is cleared, remove it. In addition, reset the DIP
switch to the 0000 state which is shown in Step 10. Then reinsert this TN16XCH board to the
slot.
NOTE
Step 12 Review the indicators of the new board. It takes 90 minutes for a board to work normally after
the board is inserted. If replace a cross-connect board whose name is the same with the name of
the original board, the STAT indicator is blinking slowly (green); If replace a cross-connect
board whose name is different from the name of the original board, the STAT indicator is steady
green. If the indicator gives an abnormal indication, reinsert the board or replace the board again.
For more information regarding indicator definitions, refer to "Board Indicators".
Step 13 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 14 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 15 Optional: Perform a warm reset on the new board, the warm reset takes three to five minutes.
Follow the steps below to switch the active/standby state of the SCCs back to the original state.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click SCC Board 1+1 Protection. Select Working/
Protection Switching from the shortcut menu. Click OK in the window displayed.
NOTE
After the new board is started, the system automatically backs up the data on the existing board to the new
board. After the data is backed up, you can perform the preceding step to initiate an active/standby
switching.
Step 16 Check and set the other parameters on the U2000 to ensure that the parameter values of the new
board are the same as the original data.
1. Check the software information of the new system control board against the original data.
2. Synchronize the NE time with the NMS server time.
3. Check the NE alarm attribute data against the original data.
4. Enable the NE performance monitoring.
5. Check whether the switching state is correct. Perform a switching test.
NOTE
For details about how to set these parameters, see iManager U2000 Operator Guide for NG WDM NE
Management.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Before replacing an board, the battery jumper on the spare board must be set. The 1X3
jumper inside the board is used to enable or disable the power supply from the battery.
Ensure that pin 1 and pin 2 on the battery jumper are capped. Then, cap pin 2 and pin 3 on
the battery jumper and use a multimeter to measure the battery voltage. If the voltage is
lower than 3 V, the battery is not working. In this case, the SCC board needs to be replaced.
l The communication between the master and slave subracks is normal and the slave subrack
is reachable by the NMS.
Replacing the TN16XCH board in the slave subrack may interrupt the services on the slave
subrack when the communication between the master and slave subracks is abnormal.
Procedure
Step 1 Select a spare TN16XCH board as the replacement board. Ensure that the spare TN16XCH board
and the TN16XCH board to be replaced have the same name and type.
Step 3 Follow the steps below to review the working state of the board to be replaced.
1. In the NE Explorer, click the NE and choose Configuration > Board 1+1 Protection from
the Function Tree.
2. Click Query.
Step 4 If the board to be replaced is the active board, go to Step 5. Otherwise, go to Step 8.
Step 5 If the board to be replaced is the working board, follow the steps below to perform an active/
standby switching on the U2000.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired SCC Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
4. Click Query. If the Working Board is not the board to be replaced, the switching is
successful.
5. Query the alarms and performance events on the U2000. Check if services are normal. If
services are normal, there must be no new abnormal alarms or performances. The switching
is successful.
Step 6 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 7 On the NMS, enable the removal indication function for the board to be replaced.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 8 Inform the onsite maintenance engineer and replace the board. For more information regarding
how to remove a board, refer to Procedure of Replacing a Board.
Step 9 Review the indicators of the new board. It takes ten minutes for a new board to work normally
after insertion. Ensure that the STAT indicator is blinking slowly (green). If the indicator gives
an abnormal indication, reinsert the board, or replace the board again. For more information
regarding indicator definitions, refer to "Board Indicators".
Step 10 If the board removal indication function is enabled before board replacement, disable this
function on the U2000 after the board replacement is complete.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 11 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 12 Query the current alarms of the NE by using the U2000.
1. In the Main Topology view, choose Fault > Browse Current Alarm from the Main Menu.
2. Click the Basic Setting and Alarm Source tabs in turn on the Filter dialog box to set the
filter conditions for the current alarms.
3. Click OK.
4. Record the current alarms of the NE.
NOTE
You can select the desired alarms and right-click to choose Save > Save Selected Records, or right-
click to choose Save > Save All Records from the shortcut menu to save the current alarms of the
NE.
NOTE
After the TN16XCH is replaced, ensure that the monitoring of the PWR-FAIL alarm is enabled. If the
PWR-FAIL alarm occurs, determine if the jumper cap is correctly placed over the battery jumper. If yes,
use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is not working.
The board needs to be replaced.
CAUTION
The standard voltage of the battery is 3.6 V. The battery is fixed on the board and cannot be
replaced.
----End
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
When ODUk SNCP protection is configured, replacing a PID board generally brings no service
interruption.
Background
In the following scenarios, when a PID board works with an OBU1P1 board on an NE, check
optical power of the PID board before you replace the PID board to avoid optical power overload
during board replacement:
l When a TN55NPO2L06 or TN55NPO2L08 board needs to be replaced on a 200 Gbit/s NE
configured with a PID board, ensure receive optical power of each channel is lower than 0
dBm.
l When an ENQ2 board needs to be replaced on a 120 Gbit/s NE configured with a PID
board, ensure receive optical power of each channel is lower than 1 dBm.
NOTE
When you replace the NPO2/NPO2E board and the ENQ2 board at the same time, it is recommended to
replace the NPO2/NPO2E board first.
Precautions
CAUTION
When you connect a fiber to the input optical port of an NPO2 or NPO2E board, loosely connect
the fiber to prevent the input optical power from crossing the overload point; otherwise, the
receiver optical module is burnt and damaged.
Procedure
1. Select a spare board. Ensure the name, version, and software version of the new board are
the same as those of the original board. If the version is inconsistent, you need to determine
if the board with different versions can be replaced.
2. Review and record the current alarms on the NE.
3. Test the input optical power. Prevent the input optical power from crossing the overload
point; otherwise, the receiver optical module is burnt and damaged. For the procedure, refer
to the Testing Optical Power by Using an Optical Power Meter.
4. Query the working status of each channel on the board to be replaced.
a. In the NE Explorer, click the NE and choose Configuration > WDM Service
Management from the Function Tree. Click the SNCP Service Control tab.
b. Click Query to obtain the SNCP protection state of each NE. Then, you can learn the
service is working on active path or working on standby path.
5. If the board is the current working board, go to 6. If the board is the current protection
board, go to 9.
6. If the board to be replaced is the current working board, follow the steps below to perform
active/standby switching on the U2000.
NOTE
The channel status of the protection board must be normal. Otherwise, replacing the faulty board
causes a service interruption.
NOTE
If an NPO2/NPO2E board needs to be replaced, switch services on the working channels of PID
boards to protection channels. If an ENQ2 board needs to be replaced, switch services on the working
channel only over the ENQ2 board to the protection channel.
a. In the Main Topology, right-click the desire NE and click NE Explorer from the
shortcut menu. The NE Explorer window is displayed.
b. Choose Configuration > WDM Service Management from the Function Tree.
c. Click SNCP Service Control tab.
d. Click Function on the bottom of the right-hand interface and select Manual to
Protection Channel from the menu displayed. Click OK on the interface displayed.
e. Click Query on the bottom of the right-hand interface. If the value of Current
Status is Manual(from Working to Protection) Switching State, the switching
succeeds.
f. Query the U2000 for the alarms and performance events. Make sure that there are no
new alarms or performance events and services are normal but only protection
switching alarm.
7. At the opposite end perform manual switching on the U2000 to ensure that the working
channel at the opposite end and is consistent with that at the local end. For how to perform
manual switching, see 6.
8. On the NMS, enable the removal indication function for the board to be replaced.
a. In the NE Explorer, select the desired NE and choose Configuration > Card
Removal Indication in the navigation tree.
b. Select the desired board. Double-click Enable Indication and set it to Enabled.
c. Click Apply.
d. Click Query to display the operation result. Verify that the function is successfully
enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the
board and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer
can easily locate the board to be replaced.
9. Inform the onsite maintenance engineer and replace the board.
a. Remove the pigtail connected to the optical port and remove the board to be replaced.
If the PQ2 sub-board also needs to be replaced, go to 9.3. If the PQ2 sub-board does
not need to be replaced, go to 9.2.
b. Loosen the screws on the PQ2 sub-board and remove the board. Install the PQ2 sub-
board on the new board and tighten the screws on the PQ2 sub-board.
c. Insert the new board to the original slot. For details on how to remove and insert a
new board, see Procedure of Replacing a Board.
d. After board replacement is complete, clean the fiber connector using a fiber cleaning
tissue and reconnect the pigtail to the optical port based on the fiber labels.
NOTE
After the board is replaced, the NE software delivers the configuration of the original board
automatically.
10. Review the indicators of the new board. It takes ten minutes for a new board to work
normally after insertion. Ensure that the STAT indicator of the PID board and the PQ2 sub-
board is green. If the indicator gives abnormal indication, you need to reinsert the board,
or replace the board again. For more information regarding indicator definitions, refer to
"Board Indicators".
11. Release the switching on the local and opposite NEs.
a. In the Main Topology, right-click the desire NE and click NE Explorer from the
shortcut menu. The NE Explorer window is displayed.
b. Choose Configuration > WDM Service Management in the Function Tree.
c. Click SNCP Service Control tab.
d. Select the switched service, and click Function on the right-hand interface. Select
Clear from the menu displayed.
e. Click Query, and review Status. If the value is Normal State, the switching succeeds.
12. Query the 15-minute BER before FEC at the receive end of the link. Make sure that the
BER before FEC does not deteriorate greatly from the value before board replacement.
a. Choose Performance > Browse NA WDM Performance from the Main Menu of
the U2000, and then click the Current Performance Data tab.
b. Choose the desired boards in the left pane, and click the double-right-arrow button
(red).
c. Choose the option from the drop-down list next to Monitored Object Filter
Condition.
d. In Monitor Period, select 15-Minute.
e. Click Count option button. Select options under Performance Event Type, and select
Display Zero Data for the Display Options.
f. Click Query to query the performance value for bit error on the NE side.
g. In the Operation Result dialog box, click Close to finish the operation.
h. In the Monitored Object, FEC-BEF-COR-ER represents the BER before FEC.
13. Query alarms and performances of the local NE and of the opposite NE and confirm that
the original alarms or performances are cleared.
NOTE
The ENQ2 board does not support the PQ2 sub-board. To replace an ENQ2 board, perform steps 1, 2, 4–
10, and 12.
For OptiX OSN 8800, when the Restart Mode of PID IPA is set to Manual, a manual restarting at two
stations is required after the board is replaced.
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
Replacing a PID board without protection will interrupt services. Replacing only a PQ2 sub-
board will interrupt channels 5 to 8 on the NPO2 or NPO2E board.
Background
In the following scenarios, when a PID board works with an OBU1P1 board on an NE, check
optical power of the PID board before you replace the PID board to avoid optical power overload
during board replacement:
l When a TN55NPO2L06 or TN55NPO2L08 board needs to be replaced on a 200 Gbit/s NE
configured with a PID board, ensure receive optical power of each channel is lower than 0
dBm.
l When an ENQ2 board needs to be replaced on a 120 Gbit/s NE configured with a PID
board, ensure receive optical power of each channel is lower than 1 dBm.
NOTE
When you replace the NPO2/NPO2E board and the ENQ2 board at the same time, it is recommended to
replace the NPO2/NPO2E board first.
Precautions
CAUTION
When you connect a fiber to the input optical port of an NPO2 or NPO2E board, loosely connect
the fiber to prevent the input optical power from crossing the overload point; otherwise, the
receiver optical module is burnt and damaged.
Procedure
1. Select a spare board. Ensure the name, version, and software version of the new board are
the same as those of the original board. If the version is inconsistent, you need to determine
if the board with different versions can be replaced.
2. Review and record the current alarms on the NE.
3. Test the input optical power. Prevent the input optical power from crossing the overload
point; otherwise, the receiver optical module is burnt and damaged. For the procedure, refer
to the Testing Optical Power by Using an Optical Power Meter.
4. On the NMS, enable the removal indication function for the board to be replaced.
a. In the NE Explorer, select the desired NE and choose Configuration > Card
Removal Indication in the navigation tree.
b. Select the desired board. Double-click Enable Indication and set it to Enabled.
c. Click Apply.
d. Click Query to display the operation result. Verify that the function is successfully
enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the
board and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer
can easily locate the board to be replaced.
5. Inform the onsite maintenance engineer and replace the board.
a. Remove the pigtail connected to the optical port and remove the board to be replaced.
If the PQ2 sub-board also needs to be replaced, go to 5.3. If the PQ2 sub-board does
not need to be replaced, go to 5.2.
b. Loosen the screws on the PQ2 sub-board and remove the board. Install the PQ2 sub-
board on the new board and tighten the screws on the PQ2 sub-board.
c. Insert the new board to the original slot. For details on how to remove and insert a
new board, see Procedure of Replacing a Board.
d. After board replacement is complete, clean the fiber connector using a fiber cleaning
tissue and reconnect the pigtail to the optical port based on the fiber labels.
NOTE
After the board is replaced, the NE software delivers the configuration of the original board
automatically.
6. Review the indicators of the new board. It takes ten minutes for a new board to work
normally after insertion. Ensure that the STAT indicator of the PID board and the PQ2 sub-
board is green. If the indicator gives abnormal indication, you need to reinsert the board,
or replace the board again. For more information regarding indicator definitions, refer to
"Board Indicators".
7. Query the 15-minute BER before FEC at the receive end of the link. Make sure that the
BER before FEC does not deteriorate greatly from the value before board replacement.
a. Choose Performance > Browse NA WDM Performance from the Main Menu of
the U2000, and then click the Current Performance Data tab.
b. Choose the desired boards in the left pane, and click the double-right-arrow button
(red).
c. Choose the option from the drop-down list next to Monitored Object Filter
Condition.
d. In Monitor Period, select 15-Minute.
e. Click Count option button. Select options under Performance Event Type, and select
Display Zero Data for the Display Options.
f. Click Query to query the performance value for bit error on the NE side.
g. In the Operation Result dialog box, click Close to finish the operation.
h. In the Monitored Object, FEC-BEF-COR-ER represents the BER before FEC.
8. Query alarms and performances of the local NE and of the opposite NE and confirm that
the original alarms or performances are cleared.
NOTE
For OptiX OSN 8800, when the Restart Mode of PID IPA is set to Manual, a manual restarting at two
stations is required after the board is replaced.
Methods of replacing the PQ2 sub-board are described under the following scenarios:
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
When ODUk SNCP protection is configured, replacing a PID board generally brings no service
interruption.
Background
In the following scenarios, when a PID board works with an OBU1P1 board on an NE, check
optical power of the PID board before you replace the PID board to avoid optical power overload
during board replacement:
l When a TN55NPO2L06 or TN55NPO2L08 board needs to be replaced on a 200 Gbit/s NE
configured with a PID board, ensure receive optical power of each channel is lower than 0
dBm.
l When an ENQ2 board needs to be replaced on a 120 Gbit/s NE configured with a PID
board, ensure receive optical power of each channel is lower than 1 dBm.
NOTE
When you replace the NPO2/NPO2E board and the ENQ2 board at the same time, it is recommended to
replace the NPO2/NPO2E board first.
Precautions
CAUTION
When you connect a fiber to the input optical port of an NPO2 or NPO2E board, loosely connect
the fiber to prevent the input optical power from crossing the overload point; otherwise, the
receiver optical module is burnt and damaged.
Procedure
1. Review and record the current alarms on the NE.
2. Query the working status of the NPO2/NPO2E board where the PQ2 sub-board resides.
a. In the NE Explorer, click the NE and choose Configuration > WDM Service
Management from the Function Tree. Click the SNCP Service Control tab.
b. Click Query to obtain the SNCP protection state of each NE. Then, you can learn the
service is working on active path or working on standby path.
3. If the board is the working NPO2 or NPO2E board, go to 4. If the board is the protection
NPO2 or NPO2E board, go to 6.
4. If the NPO2/NPO2E board where the PQ2 sub-board to be replaced resides is the working
board, perform manual switching on the NPO2/NPO2E board in U2000.
NOTE
In this step, you need to switch services on all working channels of PID boards to protection channels.
NOTE
The channel status of the protection board must be normal. Otherwise, replacing the faulty board
causes a service interruption.
a. In the Main Topology, right-click the desire NE and click NE Explorer from the
shortcut menu. The NE Explorer window is displayed.
b. Choose Configuration > WDM Service Management from the Function Tree.
c. Click SNCP Service Control tab.
d. Click Function on the bottom of the right-hand interface and select Manual to
Protection Channel from the menu displayed. Click OK on the interface displayed.
e. Click Query on the bottom of the right-hand interface. If the value of Current
Status is Manual(from Working to Protection) Switching State, the switching
succeeds.
f. Query the U2000 for the alarms and performance events. Make sure that there are no
new alarms or performance events and services are normal but only protection
switching alarm.
5. At the opposite end perform manual switching on the U2000 to ensure that the working
channel at the opposite end and is consistent with that at the local end. For how to perform
manual switching, see 4.
6. Inform the onsite maintenance engineer and replace the PQ2 sub-board.
a. Loosen the screws on the PQ2 sub-board and remove the board.
b. Install the new PQ2 sub-board on the original board and tighten the screws on the PQ2
sub-board.
7. Review the indicators of the new board. It takes three minutes for a new board to work
normally after insertion. Ensure that the STAT indicator of the PQ2 sub-board is green. If
the indicator gives abnormal indication, you need to reinsert the board, or replace the board
again. For more information regarding indicator definitions, refer to "Board Indicators".
8. Release the switching on the local and opposite NEs.
a. In the Main Topology, right-click the desire NE and click NE Explorer from the
shortcut menu. The NE Explorer window is displayed.
b. Choose Configuration > WDM Service Management in the Function Tree.
c. Click SNCP Service Control tab.
d. Select the switched service, and click Function on the right-hand interface. Select
Clear from the menu displayed.
e. Click Query, and review Status. If the value is Normal State, the switching succeeds.
9. Query alarms and performances of the local NE and of the opposite NE and confirm that
the original alarms or performances are cleared.
NOTE
For OptiX OSN 8800, when the Restart Mode of PID IPA is set to Manual, a manual restarting at two
stations is required after the board is replaced.
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
Replacing a PID board without protection will interrupt services. Replacing only a PQ2 sub-
board will interrupt channels 5 to 8 on the NPO2 or NPO2E board.
Background
In the following scenarios, when a PID board works with an OBU1P1 board on an NE, check
optical power of the PID board before you replace the PID board to avoid optical power overload
during board replacement:
l When a TN55NPO2L06 or TN55NPO2L08 board needs to be replaced on a 200 Gbit/s NE
configured with a PID board, ensure receive optical power of each channel is lower than 0
dBm.
l When an ENQ2 board needs to be replaced on a 120 Gbit/s NE configured with a PID
board, ensure receive optical power of each channel is lower than 1 dBm.
NOTE
When you replace the NPO2/NPO2E board and the ENQ2 board at the same time, it is recommended to
replace the NPO2/NPO2E board first.
Precautions
CAUTION
When you connect a fiber to the input optical port of an NPO2 or NPO2E board, loosely connect
the fiber to prevent the input optical power from crossing the overload point; otherwise, the
receiver optical module is burnt and damaged.
Procedure
1. Review and record the current alarms on the NE.
2. Inform the onsite maintenance engineer and replace the PQ2 sub-board.
a. Loosen the screws on the PQ2 sub-board and remove the board.
b. Install the new PQ2 sub-board on the original board and tighten the screws on the PQ2
sub-board.
3. Review the indicators of the new board. It takes three minutes for a new board to work
normally after insertion. Ensure that the STAT indicator of the PQ2 sub-board is green. If
the indicator gives abnormal indication, you need to reinsert the board, or replace the board
again. For more information regarding indicator definitions, refer to "Board Indicators".
4. Query alarms and performances of the local NE and of the opposite NE and confirm that
the original alarms or performances are cleared.
NOTE
For OptiX OSN 8800, when the Restart Mode of PID IPA is set to Manual, a manual restarting at two
stations is required after the board is replaced.
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Be aware of the laser security level, potential injuries and protective precautions.
Confirm the amount of the adopted Raman amplifier board. Be familiar with the fiber connection
between the local Raman amplifier board and the remote board. Be familiar with the location of
the connector. Take the drawings into the room.
Precautions
WARNING
When replacing the Raman amplifier board or before removing or inserting the Raman amplifier
board shut down the pump laser on the Raman amplifier board. Otherwise, the laser may bring
damage to human body.
Procedure
Step 1 Select a spare board to use as a replacement board. Ensure the name, version and model number
of the new board are the same as those of the original board.
NOTE
If the version is inconsistent, determine if the board with different versions can be replaced. For more
information regarding the replacement relationship between board versions, see "Substitution
Relationship".
1. In the NE Explorer, select an NE and choose Configuration > IPA Management from
the Function Tree.
2. Click Query to query the created IPA information.
3. Select the IPA that you want to enable or disable, double-click the field of Enable/
Disable, and set the value to Enabled or Disabled.
4. Click Apply.
5. In the NE Explorer of the opposite NE, repeat the steps above.
Step 4 Shutting down the Raman laser.
1. In the NE Explorer, select the desired board and choose Configuration > WDM
Interface from the Function Tree.
2. Click By Card/Channel. Select Channel from the drop-down list.
3. Select the board port. Click State and choose OOS to set the Primary, Secondary State.
4. In the Basic Attributes tab, double-click the desired optical port. In the Laser Status field,
choose On or Off to change the laser state.
5. Click Apply.
6. Select the board port or channel. Click State and choose IS to set the Primary, Secondary
State.
7. Click Query.
Step 5 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 6 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. After you remove the board, select the desired board and set Enable Indication to
Disabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
Step 11 Enable the IPA function and turn on the Raman laser. Check whether the on-off gain of the
Raman amplifier board complies with the specification requirement for the on-off gain of the
board. If not, adjust the on-off gain of the board.
NOTE
On-off gain = Optical power on the SYS interface when the laser is enabled - Optical power on the SYS
interface when the Raman laser is disabled
Step 12 After the laser status is set, the corresponding port state must be set to IS. Click State, and choose
IS.
Step 13 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
Step 14 Check and ensure that the traffic is correct. If there are any anomaly, contact Huawei.
----End
AUX
Original Substitute Substitution Rules
Board Board
TN16AUX None -
TN22AUX None -
TN41AUX None -
TN51AUX - -
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
The replacement does not affect services.
Procedure
Step 1 Select a spare board to use as a replacement board. Ensure the name, version and model number
of the new board are the same as those of the original board.
NOTE
If the version is inconsistent, determine if the board with different versions can be replaced. For more
information regarding the replacement relationship between board versions, see "Substitution
Relationship".
Step 3 Follow the steps below to query the working state of the board to be replaced.
1. Choose Configuration > Board 1+1 Protection from the Function Tree.
2. In Board 1+1 Protection, click Query.
3. If the board to be replaced is the current working board, go to Step 4. Otherwise, go to
Step 5.
Step 4 If the board to be replaced is the working board, follow the steps below to perform an active/
standby switching on the U2000.
1. In the Main Topology, right-click the desire NE and click NE Explorer from the shortcut
menu. The NE Explorer window is displayed.
2. Choose Configuration > Board 1+1 Protection from the Function Tree.
3. In Board 1+1 Protection, right-click the desired AUX Board 1+1 Protection. Select
Working/Protection Switching from the shortcut menu. Click OK in the window
displayed.
4. Click Query. If the Working Board is not the board to be replaced, the switching succeeds.
5. Query the U2000 for the alarms and performance events. Make sure that there are no new
alarms or performances. Check if services are normal.
NOTE
At the opposite end, perform manual switching on the U2000 at the same time.
Step 5 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 6 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 7 Inform the onsite maintenance engineer and replace the board. For details about how to remove
a board, see Procedure of Replacing a Board.
NOTE
After the board is replaced, the NE software delivers the configuration of the original board automatically.
Step 8 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 9 Review the indicators of the new board. It takes ten minutes for a new board to work normally
after insertion. Ensure that the STAT indicator is blinking slowly (green). If the indicator gives
an abnormal indication, reinsert the board, or replace the board again. For more information
regarding indicator definitions, refer to "Board Indicators".
Step 10 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
----End
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
The replacement does not affect services. During the replacement, the communication with the
U2000 stops.
Procedure
Step 1 Select a spare board to use as a replacement board. Ensure the name, version and model number
of the new board are the same as those of the original board.
NOTE
If the version is inconsistent, determine if the board with different versions can be replaced. For more
information regarding the replacement relationship between board versions, see "Substitution
Relationship".
Step 3 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 4 On the NMS, enable the removal indication function for the board to be replaced.
1. In the NE Explorer, select the desired NE and choose Configuration > Card Removal
Indication in the navigation tree.
2. Select the desired board. Double-click Enable Indication and set it to Enabled.
3. Click Apply.
4. Click Query to display the operation result. Verify that the function is successfully enabled.
NOTE
For the boards supporting the removal indication function, see Board Indicators.
NOTE
After the removal indication function is enabled for the board to be replaced, the STAT indicator on the board
and Minor alarm indicator in the subrack slowly blink green so that the onsite maintenance engineer can easily
locate the board to be replaced.
Step 5 Remove the board to be replaced. For details about how to remove a board, see Procedure of
Replacing a Board.
Step 6 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 7 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
----End
Prerequisites
None
Procedure
Step 1 Loosen the screws from below on the DCM frame for fixing the DCM with the phillips
screwdriver. Remove the DCM from the DCM frame.
NOTE
Step 2 Put a new DCM on the DCM frame. Tighten the screws to fix the DCM, as shown in Figure
8-17.
3
4
----End
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
When you replace an eSFP or XFP, query whether the port of the optical module to be replaced
is configured with protection. If it is not, replacement of the optical module causes interruption
of services.
If the port of the optical module to be replaced is configured with protection, module replacement
does not affect services when the protection switching functions properly.
Precautions
CAUTION
Before you connect a fiber to a pluggable optical module, test the input optical power of the
module and confirm that the tested input optical power is within the normal range. Otherwise,
the input optical power might cross the overload point and the receiver optical module is burnt
and damaged.
The overload optical power point of an APD receiver laser is only -9 dBm, which must be taken
with special caution to prevent the optical module from being burnt or damaged.
Procedure
Step 1 Select a spare pluggable optical module. The part number of the new pluggable optical module
must be the same as the part number of the original pluggable optical module.
NOTE
Query the optical module information. For details, see "Querying Optical Module Information".
NOTE
For boards supporting TXFP modules, you can use a TXFP module when replacing the XFP module on
these boards.
WARNING
Cover a fiber with a protection cap immediately after you remove it.
Step 5 Test the input optical power. Prevent the input optical power from crossing the overload point;
otherwise, the receiver optical module is burnt and damaged.
Step 6 Replace the fault optical module. For details, see Figure 8-18.
NOTE
l Before removing an optical module, ensure that the fiber jumpers connecting to the portss of the optical
module are removed.
l Before inserting an optical module, ensure that there are no fiber jumpers on the portss of the optical
module.
port
1
eSFP/SFP+
latch XFP/TXFP
Removing eSFP/SFP+/XFP/TXFP
Inserting eSFP/SFP+/XFP/TXFP
1.Pull out fibre connectors first before removing eSFP/SFP+/XFP/TXFP
1.Insert the eSFP/SFP+/XFP/TXFP into the port.
.
2.Pull the safty latch to pull out eSFP/SFP+/XFP/TXFP from the port.
3.Cover the optical port with cover.
Step 7 Check the wavelength of the new optical module on the U2000. Make sure the wavelength is
the same as that of the original optical module.
1. In the NE Explorer, select the desired board and choose Configuration > WDM
Interface from the Function Tree.
2. Select By Card/Channel, and then select Basic Attributes tab.
3. Click Query to view Configure Wavelength No./Wavelength(nm)/Frequency(THz) of
each optical port.
NOTE
If the replaced optical module is a tunable optical module, after the optical module is replaced, the SCC
delivers the wavelength configuration of the original optical module automatically.
Step 9 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
----End
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
Replacement of the EFI interrupts alarm signal input and output, communication among
subracks, and communication between NE and U2000. In addition, services may be interrupted.
Background Information
NOTE
Do not reset (cold), replace, or upgrade SCC boards when you replace the 51EFI1 boards.
Procedure
Step 1 Select a spare board to use as a replacement board. Ensure the name, version and model number
of the new board are the same as those of the original board.
NOTE
If the version is inconsistent, determine if the board with different versions can be replaced. For more
information regarding the replacement relationship between board versions, see "Substitution
Relationship".
----End
Prerequisite
You must be an NMS user with "NE operator" authority or higher.
Impact on System
When 1+1 backup is provided, replacing the standby PIU brings no impact on services.
Precautions
WARNING
Before replacing a PIU board, you must switch off the input power supply on the PIU board.
If the version is inconsistent, determine if the board with different versions can be replaced. For more
information regarding the replacement relationship between board versions, see "Substitution
Relationship".
Figure 8-19 Remove the PIU board in the 23" open rack
Figure 8-20 Insert the PIU board in the 23" open rack
Step 7 After the replacement, put the power cables back to the new PIU board. Switch on the
corresponding power switch.
Step 8 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 9 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
----End
NOTE
If the version is inconsistent, determine if the board with different versions can be replaced. For more
information regarding the replacement relationship between board versions, see "Substitution
Relationship".
Step 3 Right-click the board to be replaced on the U2000 and choose State > OOS (out of service) in
the short-cut menu to set the state of the board to OOS.
Step 4 Shut down the switch of the input power supply of the PIU board to be replaced.
Step 5 Remove the plastic cover on the power input terminal block on the PIU board by using the cross
screwdrivers.
Step 6 Unfasten the nuts on the power input terminals by using the cross screwdrivers and remove the
power cables.
Step 8 After the replacement, put the power cables back to the new PIU board. Switch on the
corresponding power switch.
Step 9 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 10 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
----End
Prerequisites
You must be an NMS user with "NE operator" authority or higher.
Impact on System
When there is a fault in the fan tray assembly, replace it immediately to avoid any damage to
the equipment due to power heat dissipation.
Replacing the fan tray assembly does not interrupt the service.
Procedure
Step 1 Select a spare board to use as a replacement board. Ensure the name, version and model number
of the new board are the same as those of the original board.
NOTE
If the version is inconsistent, determine if the board with different versions can be replaced. For more
information regarding the replacement relationship between board versions, see "Substitution
Relationship".
Step 5 Right-click the replaced board on the U2000 and choose State > IS (in service) in the short-cut
menu to set the state of the board to IS.
Step 6 Query alarms and performances of the local NE and of the opposite NE. Confirm that the original
alarms or performances are cleared.
----End
Prerequisite
None
Impact on System
None
Precaution
CAUTION
When drawing out the air filter during its replacement, do not draw out the fans.
Pull out the air filter gently to prevent dust disturbance.
NOTE
Figure 8-21 Drawing out the air filter (OptiX OSN 8800)
Figure 8-22 Drawing out the air filter (OptiX OSN 6800A)
Step 2 Gently slide the new air filter into the original position along the guide rails below the fan tray
assembly.
Step 3 Dispose of the replaced filter (whole assembly), according to local disposal regulations.
----End
Step 2 Gently slide the new air filter into the original position along the guide rails on the left part of
the fan tray assembly.
Step 3 Dispose of the replaced filter (whole assembly), according to local disposal regulations
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The TFTP/SFTP server is configured and the TFTP/SFTP service is started.
Precautions
l To ensure a safe subrack installation process, two engineers must work together. One holds
the subrack while the other tightens screws that attach it to the rack.
NOTE
For the installation of OptiX OSN 8800 T32 or T64 subracks, three or four engineers must work together
because the subracks are heavy.
l Before replacing a subrack, prepare backup boards for any boards that are unprotected. If
boards are damaged during subrack replacement, the backup boards can be used to restore
services quickly.
l Before replacing a subrack, ensure that labels with complete and accurate information are
attached to all cables and fibers connected to the subrack.
l During the subrack replacement process, do not power off or perform warm or cold reset
on master or slave subracks related to the subrack being replaced.
Subrack Appearance
6 1
5 2
1
5
3
4
1
6
5
2
3
4
2
7
Procedure
Step 1 Put on an ESD wrist strap or a pair of ESD gloves.
Step 2 Have a new subrack available to replace the target subrack. This new subrack must have the
same name and be the same model as the target subrack.
NOTE
Before replacing the target suback with a new subrack, ensure that there are no bent pins on the backplane
connector of the new subrack.
Step 3 Query and record information on current alarms for the target subrack.
The Backup Information tab is unavailable when multiple devices are selected.
3. Select Backup... to open the Backup dialog.
4. Select the option NMS Server or NMS Client to backup the selected device information.
NOTE
By default the NMS Server is selected. If the NMS Server is selected, the selected device information
is stored on the NMS server.
5. Optional: If the NMS Client is selected, click to select the location where the device
data are to be backed up.
6. Click Start to start the backup operation for the selected device(s). On the NE View tab
page, the backup progress is displayed.
7. When the backup operation is successful, the NMS creates the dbf.pkg file in the NEName/
yyyymmddhhmmss directory. "NEName" indicates the name of the NE, "yyyymmdd"
indicates the date when the backup is created, and "hhmmss" indicates the time when the
backup is created.
Step 5 Use the switch on the power distribution unit (PDU) at the top of the rack to power off the target
subrack.
Step 6 Remove all cables and fibers connected to the target subrack.
NOTE
Keep fiber connectors clear by capping them immediately after fibers are disconnected from the subrack.
Also keep disconnected cables clean for later use.
Step 7 Loosen the screws for securing the target subrack using a Phillips screwdriver and remove the
subrack. Place the subrack on an ESD pad.
Step 8 Install the new subrack into the rack and secure it with screws.
Step 9 Take the boards from the subrack that has been removed and install them on the new subrack.
NOTE
Before installing a board on the new subrack, check that the connectors on the board are in good condition.
Step 10 Use the labels to reconnect the cables and fibers to the new subrack. Restore the original network
cable connections between subracks.
NOTE
Clean the fiber connectors with fiber cleaning tissues before reconnecting fibers.
Step 11 Use the switch on the PDU at the top of the rack to power on the new subrack.
Step 12 Wait 20 minutes. Check that there are no new alarms reporting abnormalities in the new subrack.
Step 13 Operate the subrack for 24 consecutive hours. If no alarm reporting abnormalities are generated
during that period, the replacement process is a success and the new subrack is working properly.
----End
9 Network Reconstruction
CAUTION
A new shelf must be powered off before being connected or cabled to an existing NE. Otherwise,
a shelf ID conflict or service interruption may occur. Once the new shelf is connected to the NE,
power on the new shelf.
Figure 9-1 Flow for expanding NEs of version V100R005 or later when the new shelf software
version is V100R005 or later
Upload NE data
to the U2000.
Mandatory
Verification
Optional
NOTE
In the figure above, the procedures in the dotted-line frame must be performed on the U2000, and the other
procedures must be performed at the site.
9.1.1.2 Connecting the Master and Slave Shelves with Network Cables
Connect the master and slave shelves according to the network plan. Ensure that the network
cables are in good condition and are connected correctly.
Procedure
Step 1 Connect power cables to the slave shelf.
Step 2 Turn on the power switch for the slave shelf.
----End
The new shelf ID is within The new shelf is incorrectly Reconnect the new shelf
the range of 2 to 31. connected. according to the topology
structure defined in the
network plan.
The new shelf ID is 1. The cascading network 1. Power off the new shelf.
cable is faulty. As a result, 2. Replace the cascading
the new shelf fails to network cable to the
communicate with its new shelf.
upstream shelf.
3. Power on the new shelf.
The LED blinks as follows: The shelf ID negotiation Reconnect the network
On with EE displayed -> off fails. cable.
->. On with EE displayed -
> off ->. On with the shelf
ID displayed -> off.
3. Run the following TL1 command to the master shelf using the U2000, to start the shelf ID
negotiation for the NE:
INIT-SYS:::<CTAG>:::SHELFID=AUTO;
NOTE
Normally, before performing expansion, you should ensure that there is no INTERSHELF-
URGCHAN-FAIL, SHELF-ID-CONFLICT, SHELF-ID-MISMATCH, SHELF-WRONG-
CONNECT, NEW-SHELF-ID-CONFLICT, or SHELF-LOOP alarm. If you have not done this
before the expansion, you must ensure that there are no such alarms for the NE before you run the
TL1 command. If you find any of the above-mentioned alarms before running the TL1 command,
do as follows:
1. Physically disconnect the new shelf from its upstream shelf.
2. Wait 10 minutes then view the alarms on the NE using the U2000.
3. If the alarm clears, the alarm was caused by the new shelf, and you do not need to take any action.
Shelf ID negotiation requires about 4 minutes. Observe the shelf ID LED 4 minutes later.
Prerequisites
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management from the main menu of the
U2000.
Step 4 In the Confirm dialog box, click OK to start the upload. The Upload dialog box is displayed
indicating the NE data upload progress.
Step 5 In the Operation Result dialog box, click Close.
----End
Prerequisites
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Double-click the optical NE in the Main Topology. The NE Panel is displayed. Select the NE
in the left-hand pane.
Step 2 Select the unneeded slave shelf, right-click and choose Delete the Shelf.
----End
9.1.1.7 Validation
If the status of the indicators complies with the following descriptions, the expansion succeeds.
Otherwise, the expansion fails, and you are advised to contact Huawei engineers to handle the
issue.
l The shelf ID displayed on the LED on the front panel of the SCC board is the same as the
shelf ID specified in the network plan.
l The PROG indicator of all boards in the shelf is steady on (either green or red).
l The STAT indicator of all boards in the shelf is steady on (green, yellow, or red).
Figure 9-2 Flow for expanding NEs of version V100R005 or later when the new shelf software
version is unknown
Start
Y N
Does the new shelf uses
the TN51SCC board?
Y
Connect the master and slave
shelves with network cables.
Connect the master and slave
shelves with network cables.
Verification
Mandatory
End Optional
NOTE
In the figure above, the procedures in the dotted-line frame must be performed on the U2000, and the other
procedures must be performed at the site.
9.1.2.2 Upgrading the TN51SCC Software of the New Shelf to V100R005C00 or Later
This section describes how to upgrade the TN51SCC software of the new shelf to V100R005C00
or later.
To facilitate the shelf expansion and reduces the expansion time, you are advised to upgrade
spare SCC boards to V100R005C00 or later in either of the following ways before the expansion
is performed:
l Insert a spare SCC board into the idle SCC slot on an NE of V100R005C00 or later in a
laboratory and upgrade the SCC board. If there are multiple NEs that have idle SCC slots
in the laboratory, upgrade the required SCC boards in one batch to improve upgrade
efficiency.
NOTE
During the upgrade, the active and standby SCC boards must be the same hardware version. For example,
if the replacement SCC board is TN51SCC, it must be inserted in the slot that originally holds the active
TN51SCC board.
l Upgrade SCC boards in a laboratory by loading the required software package to the boards.
For details, see Upgrade Guide.
l Send the SCC boards for the new shelves back to Huawei, and request Huawei to upgrade
these SCC boards.
If you have not upgraded the SCC software to V100R005C00 or later before the expansion, there
are two situations:
l If NEs of V100R005C00 or later have an idle SCC slot at the site, you can upgrade spare
SCC boards one by one. This method has low efficiency.
NOTE
During the upgrade, the active and standby SCC boards must be the same hardware version. For example,
if the replacement SCC board is TN51SCC, it must be inserted in the slot that originally holds the active
TN51SCC board.
l If no NEs at the site have an idle SCC slot, expansion cannot be performed. You must
upgrade the spare SCC boards before the expansion is performed.
Use a proper method to upgrade the new shelf software to V100R005SPC900 or later based on
the actual situation. The following methods are available:
l Method 1: Insert the SCC board of a new shelf into a slave shelf on an active NE of version
V100R005SPC900 or later to automatically upgrade the SCC board software. The detailed
operations are as follows:
1. Set the jumper of the SCC board to 1111 to clear the current SCC board software and
database. For information on how to set the jumper, see 9.1.2.4 Powering On the
New Shelf and Clearing the SCC Software and Database.
2. Insert the SCC board into an idle SCC-specific slot of any slave shelf on an active NE
of version V100R005SPC900 or later.
NOTE
After the four jumpers are set and the SCC board is inserted to the slot, wait about 15 minutes
to allow the software and database to be cleared. Do not remove or insert a board during this
process.
3. Remove the SCC board.
4. Restore the original jumper setting for the SCC board and insert the board back to the
slave shelf on the NE of version V100R005 SPC900 or later.
5. Review the indicators of the SCC board. It takes about 15 minutes for the SCC board
to work normally after it is inserted. If the STAT indicator on the board is steady green,
then the NE software of V100R005SPC900 or later is successfully loaded to the SCC
board.
6. Remove the SCC board.
l Method 2: Upgrade the spare SCC boards in a laboratory. For details, see Method 1 or
Upgrade Guide. If any technical issue raises during the upgrade, contact Huawei engineers
for assistance.
l Method 3: Send the spare SCC boards back to Huawei, and request Huawei to upgrade
these SCC boards.
9.1.2.3 Connecting the Master and Slave Shelves with Network Cables
For the detailed procedure, see 9.1.1.2 Connecting the Master and Slave Shelves with
Network Cables.
9.1.2.4 Powering On the New Shelf and Clearing the SCC Software and Database
Procedure
Step 1 Set the four jumpers on the board to enable the SCC board to work in BIOS state. The software
and database of the SCC board are cleared.
1. Remove the SCC board.
2. Set the four jumpers to 1111 to clear the database in the flash memory. Figure 9-3 shows
the settings of the four jumpers on each type of SCC board.
Figure 9-3 Position of the BIOS running mode jumper on the TN51SCC
BIOS running mode
04
03 1010
04 02
03 01
02
01 U45 J42
J42
04
J12 U42 03 1001
J1 02
Battery
01
jumper
CPU J42
321
04
03 1011
CF card 02
01
J42
04
03 1111
02
01
J42
BIOS running
mode
Step 2 Power on the slave shelf. For the detailed procedure, see section 9.1.1.3 Powering On the Slave
Shelf.
NOTE
After the four jumpers are set and the SCC board is inserted to the slot, wait about 15 minutes to allow the
software and database to be cleared. Do not remove or insert a board during this process.
Step 3 After the software and database of the SCC board are cleared, remove the SCC board and restore
the previous jumper setting. Then reinsert this SCC board to the slot.
NOTE
If the shelf ID indicator is lit, the software matching and shelf ID negotiation have been completed.
----End
For the mapping between the values displayed in the shelf ID LED and the actual shelf IDs, see
Front Panel.
New Shelf Uses the TN51SCC Board with Its Shelf ID<=8 and the Master Shelf of
the NE to be Expanded Uses the TN52SCC
1. Disconnect the cascading network cable from the new shelf.
2. Power off the new shelf.
3. Take an action based on the fault symptom. The following table lists actions for possible
fault symptoms.
The new shelf ID is within The new shelf is incorrectly Reconnect the new shelf
the range of 2 to 31. connected. according to the topology
structure defined in the
network plan.
The LED blinks as follows: The shelf ID negotiation Reconnect the network
On with EE displayed -> off fails. cable.
->. On with EE displayed -
> off ->. On with the shelf
ID displayed -> off.
The PROG indicator on the The cascading network Replace the cascading
SCC board in the new shelf cable is faulty. As a result, network cable to the new
is steady red. the new shelf fails to shelf.
communicate with its
upstream shelf. The SCC
board stays in the BIOS
state after it restarts, failing
to read the new shelf
software.
4. Clear the SCC board software and database by properly configuring the jumpers on the
SCC board. For details, see 9.1.2.4 Powering On the New Shelf and Clearing the SCC
Software and Database.
Other Scenarios
1. Disconnect the cascading network cable from the new shelf.
2. Take an action based on the fault symptom. The following table lists actions for possible
fault symptoms.
The new shelf ID is within The new shelf is incorrectly Reconnect the new shelf
the range of 2 to 31. connected. according to the topology
structure defined in the
network plan.
The new shelf ID is 1. The cascading network 1. Power off the new shelf.
cable is faulty. As a result, 2. Replace the cascading
the new shelf fails to network cable to the
communicate with its new shelf.
upstream shelf.
3. Power on the new shelf.
The LED blinks as follows: The shelf ID negotiation Reconnect the network
On with EE displayed -> off fails. cable.
->. On with EE displayed -
> off ->. On with the shelf
ID displayed -> off.
3. Run the following TL1 command to the master shelf using the U2000, to start the shelf ID
negotiation for the NE:
INIT-SYS:::<CTAG>:::SHELFID=AUTO;
NOTE
Normally, before performing expansion, you should ensure that there is no INTERSHELF-
URGCHAN-FAIL, SHELF-ID-CONFLICT, SHELF-ID-MISMATCH, SHELF-WRONG-
CONNECT, NEW-SHELF-ID-CONFLICT, or SHELF-LOOP alarm. If you have not done this
before the expansion, you must ensure that there are no such alarms for the NE before you run the
TL1 command. If you find any of the above-mentioned alarms before running the TL1 command,
do as follows:
1. Physically disconnect the new shelf from its upstream shelf.
2. Wait 10 minutes then view the alarms on the NE using the U2000.
3. If the alarm clears, the alarm was caused by the new shelf, and you do not need to take any action.
Shelf ID negotiation requires about 4 minutes. Observe the shelf ID LED 4 minutes later.
9.1.2.9 Validation
WARNING
Wavelengths to be deleted at a time cannot exceed 1/4 of the existing wavelengths. For example,
if the number of existing wavelengths is less than four, only one wavelength can be deleted at
a time.
Prerequisites
You must be an NM user with "NE operator" authority or higher.
Background Information
Associated trails are the OCh trails that are in the same OMS section as the OCh trail that carries
the wavelength to be deleted.
Before deleting the wavelength, ensure that there are no IN-PWR-LOW, IN-PWR-HIGH, or
BEFFEC-EXC alarms for the associated trial. If there are, clear them.
Procedure
Step 1 Choose Configuration > WDM Commissioning > Commissioning Trail Management from
the main menu of the U2000.
Step 2 In the Set Trail Filter Criteria window, specify the source and sink NEs under Optical NE,
and set NE, Board, and Port for the wavelength to be deleted. Then click Filter All.
Step 3 Select the trail in the upper pane and click the Associated Trail tab in the lower pane.
Step 4 Select all associated trails by pressing Ctrl+A and copy them by pressing Ctrl+C.
Step 5 Paste all the associated trail data into an Excel file by pressing Ctrl+V. Save the file.
----End
9.2.3.1 Disabling the OTU Line-Side Lasers at Both Ends of the Wavelength to Be
Deleted
Prerequisites
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Choose Service > WDM Trail > Manage WDM Trail from the main menu of the U2000.
Step 2 In the Set Trail Browse Filter Criteria window, select OCh in the Service Level area and click
Filter All.
Step 3 In the Manage WDM Trail window, select the wavelength to be deleted.
Step 4 Click the Signal Flow Diagram tab, right-click the OTU or line board on the wavelength to be
deleted and choose WDM Configuration from the shortcut menu.
Step 5 In the displayed dialog box, select a line-side port carrying the wavelength. Click State and
choose OOS.
Step 6 Set Laser Status to Off and click Apply.
Step 7 Repeat Step 3 to Step 6 to disable the line-side laser on the other OTU or line board on the
wavelength.
Step 8 Check alarms for the associated trails, if the IN-PWR-LOW, IN-PWR-HIGH, or BEFFEC-EXC
alarm is reported for the associated trails, contact Huawei for assistance.
----End
Prerequisites
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Choose Configuration > WDM Commissioning > Commissioning Trail Management from
the main menu of the U2000.
Step 2 In the Set Trail Filter Criteria window, specify the source and sink NEs under Optical NE,
and set NE, Board, and Port for the wavelength to be deleted. Then click Filter All.
Step 3 In the upper pane of the Commissioning Trail Management window, select the OCh trail. Then
click Operate and choose Commissioning Report.
Step 4 Select Link Report for Report Type and Include associated trails for Trail, and click
Generate.
Step 5 A dialog box is displayed, asking you to confirm the subnet commissioning parameter settings.
Step 6 After confirming the parameter settings, click Yes to start generating a commissioning report.
A progress bar is displayed.
Step 7 After the progress reaches 100%, you can find a commissioning report in the lower pane of the
Commissioning Report window.
Step 8 Click View to view the content of the report.
NOTE
If a value in the report is in red, the trail needs to be optimized. Record the information about the trail and
optimize the trail by following the instructions provided in 9.2.3.3 Optimization (Optional). In more
severe cases, contact Huawei for assistance.
----End
Prerequisites
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Choose Configuration > WDM Commissioning > Commissioning Trail Management from
the main menu of the U2000.
Step 2 In the Set Trail Filter Criteria window, select the source and sink NEs under Optical NE, and
set NE, Board, and Port for the wavelength to be deleted. Then click Filter All.
Step 3 In the upper pane of the Commissioning Trail Management window, select the OCh trail. Then
click Operate and choose Link Optimization Commissioning.
Step 4 In the Automatic Optical Power Commissioning(Link Optimization) window, click Start.
Step 5 In the two confirmation dialog boxes that are displayed, click OK to start link optimization
commissioning.
NOTE
During the commissioning process, you can obtain the commissioning progress from information in Boards or
from the progress information that is displayed at the bottom of the window.
If there are wavelengths with BERs beyond the acceptable range, the Check Wavelength
Status dialog box is displayed. Determine whether to continue the commissioning according to
the actual situation at the site.
The system checks the BERs of wavelengths for the trail to be commissioned and displays the
wavelengths with BERs beyond the acceptable range in red.
l If existing wavelengths are marked in red, optimize the wavelengths manually to lower the
BER to an acceptable range before commissioning. If you do not lower the BERs, the system
does not monitor the BERs of these wavelengths during commissioning. As a result, services
carried by the existing wavelengths may be interrupted.
l If new wavelengths are marked in red, the system does not monitor the BERs of the
wavelengths during commissioning.
1. Click Continue.
2. In the confirmation dialog box, click OK.
NOTE
In the dialog box that is displayed, the Status column displays the optimization status of the trails. The
values of Status are as follows:
l Not required: The deviation between the monitored optical power and the nominal optical power meet
the requirements of network design requirements. Link optimization is not required.
l In progress: Link optimization is in process.
l Succeeded: Optical power of all OMS sections has been successfully optimized.
l Partially succeeded: Optical power of some OMS sections fails to be optimized, while optical power
of other OMS sections has been successfully optimized or does not need to be optimized.
l Failed: Optical power of all OMS sections fails to be optimized.
l Canceled: You have clicked Stop to cancel link optimization.
----End
Prerequisites
You must be an NM user with "NM operator" authority or higher.
Procedure
Step 1 Double-click an NE in the Main Topology.
Step 2 Right-click the board involved in the deleted wavelength (for example, the TN52NS3) and
choose Browse WDM Trails from the shortcut menu.
NOTE
Select the board according to the actual networking. The board can be the OTU, or the tributary or line
board at the source or sink end of the wavelength.
Step 3 In the WDM Trail Management window, delete the trail with Level set to Client/Client-
Group, ODUk/ODUk-Group, OTUk/OTUk-Group, or OCh/OCh-Group.
1. Right-click the client trail you want to delete, and choose Deactive from the shortcut menu.
2. Click OK in the Confirm dialog box.
3. Click OK in the Reconfirm dialog box.
4. Click Close in the Operation Result dialog box.
5. Right-click the client trail you want to delete, and choose Delete from the shortcut menu.
6. Click OK in the Confirm dialog box.
7. Click OK in the Reconfirm dialog box.
8. Click Close in the Operation Result dialog box.
9. Repeat the preceding operations and delete ODUk, OTUk, and OCh trails in sequence.
Step 4 Close the WDM Trail Management window.
----End
Prerequisites
You must be an NM user with "NM maintainer" authority or higher.
Procedure
Step 1 Identify all OADM NEs that the deleted wavelength traverses.
Step 2 Double-click an NE in the Main Topology.
Step 3 Select an NE and click the NE Explorer icon in the upper-left corner.
Step 4 In the NE Explorer, select the desired MCA/OPM8 board and choose Configuration > WDM
Interface from the Function Tree.
Step 5 Click By Card/Channel, select Channel from the drop-down list, and click Query. The
parameter list of each optical port or channel is displayed.
Step 6 Select Wavelength Monitor from the drop-down list and click Query. The monitoring status
of each optical port or channel is displayed.
Step 7 Select the wavelength to be deleted in the Port column.
NOTE
Be sure to select the wavelength on the correct port. For example, if the wavelength being deleted is on
NE121-24-Shelf1, the OAU on this shelf is connected to MCA8 port 2. Select the port labeled NE121-24-
Shelf1()-11MCA8-2(IN2)-xx.
Step 8 Select N in the Wavelength Monitor Enable Flag column and click Apply.
Step 9 Repeat Step 2 to Step 8 to disable the monitoring function for other related MCA/OPM8 boards
on the deleted wavelength.
----End
Prerequisites
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 Choose Fault > Browse Event logs from the main menu of the U2000. In the Filter dialog box,
click OK. The Browse Events Logs window is displayed.
Step 2 Locate the specified NE and check whether the "APE unbalance" event is generated. If this event
is generated on this NE, rectify the fault by following the instructions provided in 9.2.4.4
Starting APE Adjustment. If this event is not generated on this NE, end the task and do no
perform operations described in 9.2.4.4 Starting APE Adjustment and 9.2.4.5 Querying
Performance Events to Check Whether the APE Adjustment Is Successful.
----End
Prerequisites
You must be an NM user with "NM maintainer" authority or higher.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > APE Management.
Step 3 Select the desired APE pair from the APE Pair list.
Step 4 Click Start Adjustment at the bottom to start APE adjustment. After the operation is successful,
a dialog box is displayed indicating the success.
NOTE
When the U2000 displays a dialog box indicating an APE power exception, you must confirm it to start
the APE adjustment. The APE adjustment takes 5 minutes or less. After the APE adjustment, the "APE
adjust finished" event is reported.
----End
Prerequisites
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 Choose Fault > Browse Event logs from the main menu of the U2000. In the Filter dialog box,
click OK. The Events tab is displayed.
Step 2 Locate the specified NE and check whether the "APE adjust finished" event is generated. If this
event is generated on this NE, the APE adjustment is successful.
NOTE
If the APE adjustment fails, contact Huawei for assistance.
----End
NOTE
C-band 80-wavelength systems consist of even and odd wavelengths. The information about odd and even
wavelengths is provided below:
l C_EVEN: indicates even-numbered wavelengths. In total there are 40 even wavelengths. The center
frequency of the even wavelengths is within the range of 192.100 THz to 196.000 THz (center
wavelength is within the range of 1529.55 nm to 1560.61 nm) and the frequency spacing is 100 GHz.
l C_ODD: indicates odd-numbered wavelengths. In total there are 40 odd wavelengths. The center
frequency of the odd wavelengths is within the range of 192.150 THz to 196.050 THz (center
wavelength is within the range of 1529.16 nm to 1560.20 nm) and the frequency spacing is 100 GHz.
l C-band 40-wavelength systems use C_EVEN wavelengths.
Table 10-1 Wavelengths and frequencies of a C-band 80-channel (spacing of 50 GHz) system
11 1471 15 1551
12 1491 16 1571
13 1511 17 1591
14 1531 18 1611
12 Technical Specifications
NOTE
This section provides the roadmaps of all boards available in different versions for the WDM product series.
l For details on support of these boards on OptiX OSN 8800, see 3.6.4 OptiX OSN 8800 Board
Category.
l For details on support of these boards on OptiX OSN 6800A, see 3.6.5 OptiX OSN 6800A Board
Category.
l For details on support of these boards on OptiX OSN 3800A, see 3.6.6 OptiX OSN 3800A Board
Category.
Table 12-1, Table 12-2, Table 12-3, Table 12-4, and Table 12-5 provide OptiX OSN 8800
T64 subrack specifications.
Table 12-6, Table 12-7, Table 12-8, Table 12-9, and Table 12-10 provide OptiX OSN 8800
T32 subrack specifications.
Item Specification
a: An empty subrack means no boards are installed in the board area, and no fan tray assembly
or air filter is installed.
Table 12-2 Requirements on voltage and current of an OptiX OSN 8800 T64
Item Requirement
Item Value
Item Value
a: The maximum subrack power consumption refers to the theoretical power consumption
obtained when boards with the highest power consumption are installed in every slot on the
subrack.
Table 12-4 Power consumption of the common units in an OptiX OSN 8800 T64
Unit Name Typical Maximum Remarks
Power Power
Consumptio Consumptio
n at 25°C (77° n at 55°C
F) (W)a (131°F) (W)a
a: Indicates that the power consumption of the subrack and open rack is the value in a certain
configuration. The value is for reference only. The actual power consumed by the chassis and
open rack is a calculation based on the power consumption of each module.
NOTE
The power consumption value in the table is the measured value when the ambient temperature is 25 °C
(77 °F). During the starting up of the equipment or in high or low temperature, the power consumption of
the equipment increases. The actual power consumption of the equipment is about 1.2 to 1.5 times of the
value in the table.
Table 12-5 OptiX OSN 8800 T64 system reliability prediction results
0.9999922 4 58.68
NOTE
Item Specification
a: An empty subrack means no boards are installed in the board area, and no fan tray assembly
or air filter is installed.
Table 12-7 Requirements on voltage and current of an OptiX OSN 8800 T32
Item Requirement
Item Value
Item Value
a: The maximum subrack power consumption refers to the theoretical power consumption
obtained when boards with the highest power consumption are installed in every slot on the
subrack.
Table 12-9 Power consumption of the common units in an OptiX OSN 8800 T32
a: Indicates that the power consumption of the subrack is the value in a certain configuration.
The value is for reference only. The actual power consumed by the subrack is a calculation
based on the power consumption of each module.
NOTE
The power consumption value in the table is the measured value when the ambient temperature is 25 °C
(77 °F). During the starting up of the equipment or in high or low temperature, the power consumption of
the equipment increases. The actual power consumption of the equipment is about 1.2 to 1.5 times of the
value in the table.
Table 12-10 OptiX OSN 8800 T32 system reliability prediction results
0.99999244 4 60.40
NOTE
Table 12-11, Table 12-11, Table 12-13, Table 12-14, and Table 12-15 provide OptiX OSN
6800A subrack specifications.
a: An empty subrack means no boards are installed in the board area, and no fan tray assembly
or air filter is installed.
Table 12-14 Power consumption of the common units in an OptiX OSN 6800A
Unit Name Typical Maximum Remarks
Power Power
Consumpti Consumpti
on at 25°C on at 55°C
(77°F)a (131°F)a
a: Indicates that the power consumption of the subrack and cabinet is the value in a certain
configuration. The value is for reference only. The actual power consumption of the chassis
and cabinet is calculation based on the power consumption of each module.
b: Subrack 1 and subrack 2 are used as subracks in the line dimensions at a four-dimension
RADOM station; subrack 3 and subrack 4 are used as subracks for adding/dropping local
services. Service boards can be configured in another subrack.
NOTE
The power consumption value in the table is the measured value when the ambient temperature is 25 °C
(77 °F). During the starting up of the equipment or in high or low temperature, the power consumption of
the equipment increases. The actual power consumption of the equipment is about 1.2 to 1.5 times of the
value in the table.
0.99999098 4 51.64
NOTE
Table 12-16, Table 12-17, Table 12-18, Table 12-19, Table 12-20, Table 12-21, Table
12-22, and Table 12-23 provide OptiX OSN 3800A chassis specifications.
Item Specification
Item Requirement
Item Requirement
Item Value
Table 12-20 DC Power consumption of the chassis in typical configuration in an OptiX OSN
3800A
Unit Name Typical Maximum Remarks
Power Power
Consump Consumpti
tion at 25° on at 55°C
C (77°F) (131°F)
a: Indicates that the power consumption of the chassis is the value in a certain configuration.
The value is for reference only. The actual power consumption of the chassis is calculated
based on the power consumption of each module.
Table 12-22 AC Power consumption of the chassis in typical configuration in an OptiX OSN
3800A
Unit Name Typical Maximum Remarks
Power Power
Consump Consumpti
tion at 25° on at 55°C
C (77°F) (131°F)
a: Indicates that the power consumption of the chassis is the value in a certain configuration.
The value is for reference only. The actual power consumption of the chassis is calculated
based on the power consumption of each module.
NOTE
The power consumption value in the table is the measured value when the ambient temperature is 25 °C
(77 °F). During the starting up of the equipment or in high or low temperature, the power consumption of
the equipment increases. The actual power consumption of the equipment is about 1.2 to 1.5 times of the
value in the table.
0.999983 4 27.35
NOTE
Item Specification
Item Value
Item Value
Dimensions (H x W x D) 64.0 mm (2.5 in.) x 493.7 mm (19.4 in.) x 280.5 mm (11.0 in.)
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 270 W.
Dimensions 493.7 mm (W) x 266.6 mm (D) x 56.1 mm (H) (19.44 in. (W)
x 10.5 in. (D) x 2.21 in. (H))
Item Specification
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 215 W.
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 120 W.
Dimensions 41.0 mm (W) x 262.6 mm (D) x 126.5 mm (H) (1.61 in. (W) x
10.34 in. (D) x 4.98 in. (H))
Item Specification
a: Rotating speed of fans is controlled intelligently. When the system is typically configured,
rotating speed of fans is automatically adjusted to a low level. When the system is fully
configured with boards of high power consumption, and the system is running in a high
ambient temperature, rotating speed of fans may be adjusted to a high level. When rotating
at the maximum speed, power consumption of fan tray assembly may reach 32.7 W.
The power shown in Table 12-30Table 12-31Table 12-32 refers to the reference output power of the laser.
It is achieved when the mode-field diameter of fiber is 10 um at the 1550 nm wavelength.
The laser class complies with IEC 60825-2 laser safety standards.
For the OptiX OSN 6800A, the laser level of the equipment is CLASS 1M.
Under 10 dBm HAZARD L4G, LDX, LEM24, LEX4, LOA, LOG, LOM,
LEVEL 1 LQG, LQM, LQMD, LQMS, LSC, LSQ, LSX,
LSXL, LSXLR, LSXR, LTX, LWXS, TMX, ND2,
NQ2, NS3, NS2, TBE, TDX, TOM, TQM, TOG,
TQX, TSXL, D40, D40V, M40, M40V, RMU9,
WSM9(TN12), SC1, HSC1, SC2, ST2, DCP, SCS,
DCU, TDC
10 - 21.3 dBma HAZARD FIU, ITL, CMR2, CMR4, DMR1, MR2, MR4,
LEVEL 1M MR8, MR8V, SBM2, RDU9, WSMD2, WSD9,
WSM9(TN13), WSMD4, OAU100, OAU101,
OAU102, OAU103, OBU1, OLP, VA1, VA4,
GFU, HBA, OAU105, OBU2, TN13FIU02,
CRPC, RAU1, DAS1, WSMD9
a: For the HBA, OAU105, OBU2, TN13FIU02, CRPC, RAU1 boards, after the IPA function
is enabled, the laser hazard level of the board is HAZARD LEVEL 1M, which indicates that
the maximum power output by the optical port on the board ranges from 10 dBm (10 mW)
to 21.3 dBm (136 mW).
For the OptiX OSN 3800A, the laser level of the equipment is CLASS 1M.
Under 10 dBm HAZARD CMR1, L4G, LDX, LOA, LOG, LOM, LQG, LQM,
LEVEL 1 LQMD, LQMS, LSX, LSXR, LWXS, TMX, NS2,
TBE, TOM, TOG, TQM, SC1, HSC1, SC2, ST2,
DCP, SCS, DCU
10 - 21.3 dBm HAZARD FIU, CMR2, CMR4, DMR1, MR2, MR4, SBM2,
LEVEL 1M OAU100, OAU101, OAU102, OAU103, OAU106,
OBU1, OLP, VA1, VA4, OAU105, OBU2, DAS1,
RAU1
a: For OAU105, OBU2 boards, after the IPA function is enabled, the laser hazard level of the
board is HAZARD LEVEL 1M, which indicates that the maximum power output by the
optical port on the board ranges 10 dBm (10 mW) to 21.3 dBm (136 mW).
For the OptiX OSN 8800, the laser level of the equipment is CLASS 1M.
Under 10 dBm HAZARD LDX, LEM24, LEX4, LOA, LOG, LOM, LQM,
LEVEL 1 LQMD, LQMS, LSC, LSQ, LSX, LSXL, LSXLR,
LSXR, LTX, LWXS, TMX, ND2, NQ2, NS3, NS2,
TEM28, TDX, TOA, TOM, TQX, TOG, D40,
D40V, M40, M40V, RMU9, WSM9(TN11, TN12),
HSC1, SC1, SC2, ST2, DCP, SCS, DCU, TDC
10 - 21.3 dBma HAZARD NPO2, NPO2E, ITL, CMR2, CMR4, DMR1, MR2,
LEVEL 1M MR4, MR8, MR8V, SBM2, RDU9, ROAM,
WSMD2, WSD9, WSM9(TN13), WSMD4,
OAU100, OAU101, OAU102, OAU103, OAU106,
OBU1, OLP, VA1, VA4, GFU, HBA, OAU105,
OBU2, TN13FIU01, TN13FIU02, CRPC, DAS1,
WSMD9, RAU1
a: For the HBA, OAU105, OBU2, TN13FIU02, CRPC, RAU1 boards, after the IPA function
is enabled, the laser hazard level of the board is HAZARD LEVEL 1M, which indicates that
the maximum power output by the optical port on the board ranges 10 dBm (10 mW) to 21.3
dBm (136 mW).
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
Table 12-34 Client-side pluggable optical module specifications (CWDM colored wavelengths)
Parameter Unit Value
Minimum extinction dB 10 10
ratio
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.4 kg (3.1 lb.)
Power Consumption
Board WDM-Side Optical Typical Power Maximum Power
Module Consumption at 25° Consumption at 55°
C ( 77°F ) (W) C ( 131°F ) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
The 10 Gbit/s Multirate-10 km-XFP, 10 Gbit/s Multirate-40 km-XFP, and 10 Gbit/s Multirate-80 km-XFP
optical module can be used to access OC-192, STM-64, 10GE LAN, 10GE WAN, and OTU2/OTU2e
signals.
The 10 Gbit/s Single-Rate-0.3 km-XFP optical module can be used only to access 10GE LAN signals.
Table 12-36 Client-side pluggable optical module specifications (10 Gbit/s services)
Parameter Unit Value
Minimum dB 6 8.2 9 3
extinction
ratio
Minimum dB 30 30 30 30
side mode
suppression
ratio
Minimum dBm -1 -1 -7 -1
receiver
overload
(STM-64)
Table 12-37 Client-side pluggable optical module specifications (DWDM colored wavelengths)
Parameter Unit Value
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.6 kg (3.5 lb.)
Power Consumption
Bo WDM-Side Optical Module Typical Power Maximum Power
ard Consumption at 25° Consumption at 55°
C (77°F) (W) C (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Minimum extinction dB 9 9
ratio
NOTE
The electrical interface specifications comply with IEEE Std 802.3 when receiving 1000 BASE-T services.
Maximum dBm -1 2 4
mean launched
power
Minimum dBm -6 -1 0
mean launched
power
Minimum dB 6 8.2 9
extinction ratio
Minimum side dB 30 30 30
mode
suppression
ratio
Minimum dBm -1 -1 -7
receiver
overload
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (131°F)
TN11LEM24 81 83
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Maximum dBm -1 2 4
mean launched
power
Minimum dBm -6 -1 0
mean launched
power
Minimum dB 6 8.2 9
extinction ratio
Minimum side dB 30 30 30
mode
suppression
ratio
Minimum dBm -1 -1 -7
receiver
overload
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.7 kg (1.5 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (131°F)
TN11LEX4 64 67
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
I-16/SR-1 OC-48-2 km-eSFP module, S-16.1/IR-1 OC-48-15 km-eSFP module, L-16.1/LR-1 OC-48-40 km-
eSFP module and L-16.2/LR-2 OC-48-80 km-eSFP module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, FDDI, FICON, FICON Express, GE, STM-4, OC-12, ESCON, STM-1, OC-3, and DVB-ASI
signals.
Only the S-16.1/IR-1 OC-48-15 km-eSFP optical module supports FE services, and it can only connect to a
100BASE-LX10-eSFP optical module.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
NOTE
1000 BASE-BX10-U-eSFP module, 1000 BASE-BX10-D-eSFP module, 1000 BASE-BX-U-eSFP module, and
1000 BASE-BX-D-eSFP module can be used to access GE signals.
Target km 10 10 40 40
transmission
distance
Maximum dBm -3 -3 3 3
mean launched
power
Minimum dBm -9 -9 -2 -2
mean launched
power
Minimum dB 6 6 6 6
extinction ratio
Minimum dBm -3 -3 -3 -3
receiver
overload
NOTE
2.125 Gbit/s Multi-rate-eSFP module can be used to access FC200, GE, FC100, FDDI, FICON, FICON Express,
and FE signals.
1000 BASE-LX-10 km-eSFP module, 1000 BASE-LX-40 km-eSFP module and 1000 BASE-ZX-80 km-eSFP
module can be used to access GE, FC100, STM-4, OC-12, ESCON, STM-1, OC-3, FDDI, FICON, FE, and
DVB-ASI signals.
When accessing 1000 BASE-T services, the specifications of the electrical interface comply with the IEEE Std
802.3.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
SDI module can be used to access DVB-ASI, SDI, HD-SDI, HD-SDIRBR, 3G-SDI, and 3G-SDIRBR signals.
NOTE
4.25 Gbit/s Multirate-0.3 km-eSFP, 4.25 Gbit/s Multirate-10 km-eSFP module can be used to access FC400,
and FICON4G signals.
NOTE
800-M5E-SA-I-0.3 km-SFP+ and 800-SM-LC-L-10 km-SFP+ module can be used to access FC800 and
FICON8G signals.
NOTE
1.25 Gbit/s Multirate (CWDM)-40 km-eSFP module can be used to access GE, FC100, STM-4, OC-12, ESCON,
STM-1, OC-3, FDDI, FICON, FE, and DVB-ASI signals.
2.67 Gbit/s Multirate (CWDM)-80 km-eSFP module can be used to access OTU1, STM-16, OC-48, FC200,
FC100, FDDI, FICON, FICON Express, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, and FE
signals.
Table 12-55 Client-side pluggable optical module specifications (CWDM colored wavelengths)
NOTE
2.67 Gbit/s Multirate (DWDM)-120 km-eSFP module can be used to access OTU1, STM-16, OC-48, FC200,
FC100, FDDI, FICON, FICON Express, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, and FE
signals.
Table 12-56 Client-side pluggable optical module specifications (DWDM colored wavelengths)
Parameter Unit Value
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.19 kg (2.64b.)
Power Consumption
Board WDM-Side Typical Power Maximum Power
Optical Module Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
When accessing 1000 BASE-T services, the specifications of the electrical interface comply with the IEEE
Std 802.3.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
Target km 10 10 40 40
transmission
distance
Maximum dBm -3 -3 3 3
mean launched
power
Minimum dBm -9 -9 -2 -2
mean launched
power
Minimum dB 6 6 6 6
extinction ratio
Minimum dBm -3 -3 -3 -3
receiver
overload
Table 12-62 Client-side pluggable optical module specifications (CWDM colored wavelengths)
Parameter Unit Value
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Maximum dBm 2 2 2 2 2
mean launched
power
Minimum dBm -3 -3 -3 -3 -3
mean launched
power
Minimum dB 10 10 N/Aa 10 10
extinction ratio
Center GHz ±5 ±5 ±5 ±5 ±5
frequency
deviation
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Minimum side dB 35 35 35 35 35
mode
suppression
ratio
Minimum dBm 0 -9 -9 0 0
receiver
overload
a: The ODB code pattern has three levels, and thus extinction ratio is not needed.
Maximum dBm -1 2 4
mean launched
power
Minimum dBm -6 -1 0
mean launched
power
Minimum dB 6 8.2 9
extinction ratio
Minimum side dB 30 30 30
mode
suppression
ratio
Minimum dBm -1 -1 -7
receiver
overload
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
Power Consumption
Boar WDM-Side Optical Module Typical Power Maximum Power
d Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
When accessing 1000 BASE-T services, the specifications of the electrical interface comply with the IEEE
Std 802.3.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
Target km 10 10 40 40
transmission
distance
Maximum dBm -3 -3 3 3
mean launched
power
Minimum dBm -9 -9 -2 -2
mean launched
power
Minimum dB 6 6 6 6
extinction ratio
Minimum dBm -3 -3 -3 -3
receiver
overload
Minimum dBm 0 0 0 0
receiver
overload
Table 12-71 Client-side pluggable optical module specifications (CWDM colored wavelengths)
Parameter Unit Value
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Maximum dBm 2 2 2 2 2
mean launched
power
Minimum dBm -3 -3 -3 -3 -3
mean launched
power
Minimum dB 10 10 N/Aa 10 10
extinction ratio
Center GHz ±5 ±5 ±5 ±5 ±5
frequency
deviation
Minimum side dB 35 35 35 35 35
mode
suppression
ratio
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Minimum dBm 0 -9 -9 0 0
receiver
overload
a: The ODB code pattern has three levels, and thus extinction ratio is not needed.
Mechanical Specifications
TN11LOM:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.3 kg (5.1 lb.)
TN12LOM:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.1 kg (2.42 lb.)
Power Consumption
Boar WDM-Side Optical Module Typical Power Maximum Power
d Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
Table 12-77 Client-side pluggable optical module specifications (CWDM colored wavelengths)
Parameter Unit Value
Minimum extinction dB 10 10
ratio
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.3 kg (2.9 lb.)
Power Consumption
Board WDM-Side Typical Power Maximum Power
Optical Module Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
The I-16/SR-1 OC-48-2 km-eSFP, S-16.1/IR-1 OC-48-15 km-eSFP, L-16.1/LR-1 OC-48-40 km-eSFP and
L-16.2/LR-2 OC-48-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48, FC200, FC100,
GE, STM-4, OC-12, ESCON, STM-1, OC-3, and DVB-ASI signals.
Only the S-16.1/IR-1 OC-48-15 km-eSFP optical module supports FE services, and it can only connect to a
100BASE-LX10 optical module.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
NOTE
The 2.125 Gbit/s Multirate-0.5 km-eSFP optical module can be used to access FC200, GE, FC100, and FE
signals.
The 1000 BASE-LX-10 km-eSFP, 1000 BASE-LX-40 km-eSFP and 1000 BASE-ZX-80 km-eSFP optical
module can be used to access GE, FC100, STM-4, OC-12, ESCON, STM-1, OC-3, FE and DVB-ASI signals.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
The 1.25 Gbit/s Multirate (CWDM)-40 km-eSFP can be used to access GE, FC100, STM-4, OC-12, ESCON,
STM-1, OC-3, FE, DVB-ASI signals.
The 2.67 Gbit/s Multirate (CWDM)-80 km-eSFP can be used to access OTU1, STM-16, OC-48, FC200, FC100,
GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, FE signals.
Table 12-82 Client-side pluggable optical module specifications (CWDM colored wavelengths)
NOTE
The 2.67 Gbit/s Multirate (DWDM)-120 km-eSFP can be used to access OTU1, STM-16, OC-48, FC200, FC100,
GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, or FE signals.
Table 12-83 Client-side pluggable optical module specifications (DWDM colored wavelengths)
Parameter Unit Value
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.1 kg (2.4 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
The I-16/SR-1 OC-48-2 km-eSFP, S-16.1/IR-1 OC-48-15 km-eSFP, L-16.1/LR-1 OC-48-40 km-eSFP and
L-16.2/LR-2 OC-48-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48, FC200, FC100,
FDDI, FICON, FICON Express, GE, STM-4, OC-12, ESCON, STM-1, OC-3, and DVB-ASI signals.
Only the S-16.1/IR-1 OC-48-15 km-eSFP optical module supports FE services, and it can only connect to a
100BASE-LX10 optical module.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
NOTE
The 2.125 Gbit/s Multirate-0.5 km-eSFP optical module can be used to access FC200, GE, FC100, and FE
signals.
The 1000 BASE-LX-10 km-eSFP, 1000 BASE-LX-40 km-eSFP and 1000 BASE-ZX-80 km-eSFP optical
module can be used to access GE, FC100, STM-4, OC-12, ESCON, STM-1, OC-3, FE and DVB-ASI signals.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
The 1.25 Gbit/s Multirate (CWDM)-40 km-eSFP optical module can be used to access GE, FC100, STM-4,
OC-12, ESCON, STM-1, OC-3, FE, DVB-ASI signals.
The 2.67 Gbit/s Multirate (CWDM)-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, FE signals.
Table 12-88 Client-side pluggable optical module specifications (CWDM colored wavelengths)
Parameter Unit Value
NOTE
The 2.67 Gbit/s Multirate (DWDM)-120 km-eSFP optical module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, FE signals.
Table 12-89 Client-side pluggable optical module specifications (DWDM colored wavelengths)
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.4 kg (3.1 lb.)
Power Consumption
Board WDM-Side Optical Module Typical Power Maximum
Consumption at Power
25°C (77°F) (W) Consumption at
55°C (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
TheI-16/SR-1 OC-48-2 km-eSFP, S-16.1/IR-1 OC-48-15 km-eSFP, L-16.1/LR-1 OC-48-40 km-eSFP and
L-16.2/LR-2 OC-48-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48, FC200, FC100,
FICON, FICON Express, FDDI, GE, STM-4, OC-12, ESCON, STM-1, OC-3, and DVB-ASI signals.
Only the S-16.1/IR-1 OC-48-15 km-eSFP optical module supports FE services, and it can only connect to a
100BASE-LX10 optical module.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
NOTE
The 2.125 Gbit/s Multirate-0.5 km-eSFP optical module can be used to access FC200, GE, FC100, and FE
signals.
The 1000 BASE-LX-10 km-eSFP, 1000 BASE-LX-40 km-eSFP and 1000 BASE-ZX-80 km-eSFP optical
module can be used to access GE, FC100, STM-4, OC-12, ESCON, STM-1, OC-3, FE and DVB-ASI signals.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
The 1.25 Gbit/s Multirate (CWDM)-40 km-eSFP optical module can be used to access GE, FC100, STM-4,
OC-12, ESCON, STM-1, OC-3, FE, or DVB-ASI signals.
The 2.67 Gbit/s Multirate (CWDM)-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, or FE signals.
Table 12-93 Client-side pluggable optical module specifications (CWDM colored wavelengths)
NOTE
The 2.67 Gbit/s Multirate (DWDM)-120 km-eSFP optical module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, or FE signals.
Table 12-94 Client-side pluggable optical module specifications (DWDM colored wavelengths)
Parameter Unit Value
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.3 kg (2.9 lb.)
Power Consumption
Boar WDM-Side Optical Module Typical Power Maximum Power
d Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
1303.54
1308.09
1305.63
1310.19
1303.54
1308.09
1305.63
1310.19
1537
1545
1553
1561
1569
1577
1585
1593
1541
1549
1557
1565
1573
1581
1589
1597
1537
1545
1553
1561
1569
1577
1585
1593
1541
1549
1557
1565
1573
1581
1589
1597
Table 12-98 WDM-side fixed optical module specifications (tunable wavelengths, HFEC, RZ)
Mechanical Specifications
TN12LSC
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 101.6 mm (4.0 in.) x 220
mm (8.7 in.)
l Weight: 4.5 kg (9.9 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.5 kg (5.5 lb.)
Power Consumption
Board WDM-Side Optical Module Typical Power Maximum Power
Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
The 10 Gbit/s multirate 10 km-XFP module, 10 Gbit/s multirate 40 km-XFP module, and 10 Gbit/s multirate
80 km-XFP module can be used to access OC-192, STM-64, 10GE LAN, 10GE WAN, FC1200, and OTU2/
OTU2e signals.
The 10 Gbit/s single-rate 0.3 km-XFP module can be used to access 10GE LAN and FC1200 signals.
Table 12-101 Client-side pluggable optical module specifications (10 Gbit/s services)
Parameter Unit Value
Minimum dB 6 8.2 9 3
extinction
ratio
Minimum dB 30 30 30 30
side mode
suppression
ratio
Minimum dBm -1 -1 -7 -1
receiver
overload
(STM-64)
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Maximum dBm 2 2 2 2 2
mean launched
power
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Minimum dBm -3 -3 -3 -3 -3
mean launched
power
Minimum dB 10 10 N/Aa 10 10
extinction ratio
Center GHz ±5 ±5 ±5 ±5 ±5
frequency
deviation
Minimum side dB 35 35 35 35 35
mode
suppression
ratio
Minimum dBm 0 -9 -9 0 0
receiver
overload
a: The ODB code pattern has three levels, and thus extinction ratio is not needed.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
TN12LSX: 1.4 kg (3.1 lb.)
TN13LSX: 1.1 kg (2.4 lb.)
Power Consumption
Boar WDM-Side Optical Module Typical Power Maximum Power
d Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Mechanical Specifications
TN12LSXL
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 76.2 mm (3.0 in.) x 220 mm
(8.7 in.)
l Weight: 3.75 kg (8.27 lb.)
TN15LSXL
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 76.2 mm (3.0 in.) x 220 mm
(8.7 in.)
l Weight: 3.8 kg (8.4 lb.)
Power Consumption
Board WDM-Side Optical Module Typical Power Maximum
Consumption at Power
25°C (77°F) (W) Consumption at
55°C (131°F) (W)
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Mechanical Specifications
TN12LSXLR
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.5 kg (5.5 lb.)
Power Consumption
Board WDM-Side Optical Module Typical Power Maximum Power
Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Optical Module 1200 ps/ 1200 ps/ 4800 ps/nm- 800 ps/nm-C
Type nm-C nm-C C Band- Band-
Band- Band- Tunable Tunable
Tunable Tunable Wavelengt Wavelength-
Wavelengt Wavelengt h-ODB- DRZ-PIN
h-NRZ- h-NRZ- APD
PIN APD
Minimum dB 10 10 N/Aa 10
extinction ratio
Minimum side dB 35 35 35 35
mode suppression
ratio
a: The ODB code pattern has three levels, and thus extinction ratio is not needed.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.2 kg. (2.6 lb)
Power Consumption
Boar WDM-Side Optical Module Typical Power Maximum Power
d Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
The 10 Gbit/s Multirate-10 km-XFP, 10 Gbit/s Multirate-40 km-XFP, and 10 Gbit/s Multirate-80 km-XFP
optical module can be used to access OC-192, STM-64, 10GE LAN and 10GE WAN signals.
The 10 Gbit/s Single-Rate-0.3 km-XFP optical module can be used only to access 10GE LAN signals.
Table 12-113 Client-side pluggable optical module specifications (10 Gbit/s services)
Minimum dB 6 8.2 9 3
extinction
ratio
Minimum dB 30 30 30 30
side mode
suppression
ratio
Minimum dBm -1 -1 -7 -1
receiver
overload
(STM-64)
Table 12-114 WDM-side fixed optical module specifications (tunable wavelengths, HFEC, RZ)
Parameter Unit Value
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 101.6 mm (4.0 in.) x 220
mm (8.7 in.)
l Weight: 5.8 kg (12.8 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
The I-16/SR-1 OC-48-2 km-eSFP, S-16.1/IR-1 OC-48-15 km-eSFP, and L-16.2/LR-2 OC-48-80 km-eSFP
optical module can be used to access ETR, CLO, STM-16, OC-48, FC200, FC100, GE, STM-4, OC-12, ESCON,
STM-1, OC-3, and DVB-ASI signals.
Only the S-16.1/IR-1 OC-48-15 km optical module supports FE services, and it can only connect to a 100BASE-
LX10 optical module.
The 2.125 Gbit/s Multirate-0.5 km-eSFP optical module is used to access FC200, GE, FC100 and FE signals.
Minimum dBm 0 -3 0 -9
receiver
overload
NOTE
The 1.25 Gbit/s Multirate (CWDM)-40 km-eSFP optical module can be used to access ETR, CLO, GE, FC100,
STM-4, OC-12, ESCON, STM-1, OC-3, FE, or DVB-ASI signals.
The 2.67 Gbit/s Multirate (CWDM)-80 km-eSFP optical module can be used to access ETR, CLO, STM-16,
OC-48, FC200, FC100, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, or FE signals.
Optical 12800 ps/ 12800 ps/ 6500 ps/ 3200 ps/ 12800 ps/ 6400 ps/
Module Type nm-C nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band- Band-
Fixed Fixed Fixed Fixed Tunable Tunable
Waveleng Waveleng Wavelen Waveleng Wavelen Waveleng
th-NRZ- th-NRZ- gth-NRZ- th-NRZ- gth-NRZ- th-NRZ-
PINa APDa PIN APD APD APD
(Four
Channels-
Tunable)
Maximum dBm -1 -1 3 3 3 3
mean launched
power
Minimum side dB 35 35 30 30 35 35
mode
suppression
ratio
Optical 12800 ps/ 12800 ps/ 6500 ps/ 3200 ps/ 12800 ps/ 6400 ps/
Module Type nm-C nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band- Band-
Fixed Fixed Fixed Fixed Tunable Tunable
Waveleng Waveleng Wavelen Waveleng Wavelen Waveleng
th-NRZ- th-NRZ- gth-NRZ- th-NRZ- gth-NRZ- th-NRZ-
PINa APDa PIN APD APD APD
(Four
Channels-
Tunable)
a: The 12800ps/nm-PIN and 12800ps/nm-APD modules do not support pilot tone modulation mode.
NOTE
l When SDH or OTN services are provisioned on the WDM side, the line code on the WDM side must
be NRZ.
l When SDH or OTN services are provisioned on the WDM side, the eye pattern on the WDM side
complies with the template defined in ITU-T G.957.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.1 kg (2.4 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77°F) Consumption at 55°C (131°
(W) F) (W)
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Maximum dBm 2 2 2 2 2
mean launched
power
Minimum dBm -3 -3 -3 -3 -3
mean launched
power
Minimum dB 10 10 N/Aa 10 10
extinction ratio
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Center GHz ±5 ±5 ±5 ±5 ±5
frequency
deviation
Minimum side dB 35 35 35 35 35
mode
suppression
ratio
Minimum dBm 0 -9 -9 0 0
receiver
overload
a: The ODB code pattern has three levels, and thus extinction ratio is not needed.
Maximum dBm -1 2 4
mean launched
power
Minimum dBm -6 -1 0
mean launched
power
Minimum dB 6 8.2 9
extinction ratio
Minimum side dB 30 30 30
mode
suppression
ratio
Minimum dBm -1 -1 -7
receiver
overload
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
TN11TMX: 1.4 kg (3.1 lb.)
TN12TMX: 1.1 kg (2.4 lb.)
Power Consumption
Boar WDM-Side Optical Module Typical Power Maximum Power
d Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
The OTU has the jitter transfer characteristics. Its jitter transfer function should be under the
curve. See Figure 12-1. For its specifications, refer to Table 12-128.
P
-20dB/10 octave
f
0 fc Jitter frequency
The OTU is able to tolerate the input jitter pattern shown in Figure 12-2. The specifications are
provided in Table 12-129.
A2
-20dB/10 octave
A1
f
f0 f1 Frequency
65 1.3 0.1
STM-4/OC-12 1 5 0.3
250 5 0.1
STM-16/OC-48/ 5 20 0.3
OTU1
1000 20 0.1
STM-64/OC-192/ 20 80 0.3
OTU2
4000 80 0.1
TN12ND 800 ps/nm-C Band-Tunable 800 ps/nm-C Band (Odd & Even
2 Wavelength-(D)RZ-PIN Wavelengths)-Fixed Wavelength-
800 ps/nm-C Band-Tunable NRZ-PIN-XFP
Wavelength-NRZ-PIN 10 Gbit/s Multirate-10 km-XFP
10 Gbit/s Multirate-40 km-XFP
10 Gbit/s Multirate-80 km-XFP
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Maximum dBm -1 2 4
mean launched
power
Minimum dBm -6 -1 0
mean launched
power
Minimum dB 6 8.2 9
extinction ratio
Minimum side dB 30 30 30
mode
suppression
ratio
Minimum dBm -1 -1 -7
receiver
overload
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
TN11ND2/TN12ND2: 1.6 kg (3.5 lb. )
TN52ND2: 1.4 kg (3.1 lb.)
TN53ND2: 1.2 kg (2.7 lb.)
Power Consumption
Boar WDM-Side Optical Module Typical Power Maximum
d Consumption at Power
25-C (77-F) (W) Consumption at
55-C (131-F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Maximum dBm -1 2 4
mean launched
power
Minimum dBm -6 -1 0
mean launched
power
Minimum dB 6 8.2 9
extinction ratio
Minimum side dB 30 30 30
mode
suppression
ratio
Minimum dBm -1 -1 -7
receiver
overload
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
– TN51NQ2: 1.6 kg (3.5 lb.)
– TN52NQ2: 2.0 kg (4.4 lb.)
– TN53NQ2: 1.6 kg (3.5 lb.)
– TN54NQ2: 1.6 kg (3.5 lb.)
Power Consumption
Boar WDM-Side Optical Module Typical Power Maximum
d Consumption at Power
25-C (77-F) (W) Consumption at
55-C (131-F) (W)
TN12NS 800 ps/nm-C Band (Odd & Even 800 ps/nm-C Band (Odd & Even
2 Wavelength)-Fixed Wavelength-NRZ- Wavelengths)-Fixed Wavelength-
PIN NRZ-PIN-XFP
1200 ps/nm-C Band-Tunable
Wavelength-NRZ-PIN
1200 ps/nm-C Band-Tunable
Wavelength-NRZ-APD
4800 ps/nm-C Band-Tunable
Wavelength-ODB-APD
800 ps/nm-C Band-Tunable
Wavelength-(D)RZ-PIN
800 ps/nm-C Band-Tunable
Wavelength-NRZ-PIN
NOTE
(D)RZ means DRZ or RZ. These two types of optical modules have the same optical performance and can be
interconnected. The availability of the two type of optical module is subject to PCNs. For PCN information,
consult with the product manager at the local representative office.
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Maximum dBm 2 2 2 2 2
mean launched
power
Minimum dBm -3 -3 -3 -3 -3
mean launched
power
Minimum dB 10 10 N/Aa 10 10
extinction ratio
Center GHz ±5 ±5 ±5 ±5 ±5
frequency
deviation
Minimum side dB 35 35 35 35 35
mode
suppression
ratio
Optical 1200 ps/ 1200 ps/ 4800 ps/ 800 ps/ 800 ps/
Module Type nm-C nm-C nm-C nm-C nm-C
Band- Band- Band- Band- Band-
Tunable Tunable Tunable Tunable Tunable
Wavelen Wavele Wavelen Waveleng Waveleng
gth- ngth- gth- th-DRZ- th-NRZ-
NRZ- NRZ- ODB- PIN PIN
PIN APD APD
Minimum dBm 0 -9 -9 0 0
receiver
overload
a: The ODB code pattern has three levels, and thus extinction ratio is not needed.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
TN12NS2: 1.2 kg (2.64 lb)
TN52NS2: 1.3 kg (2.86 lb.)
TN53NS2: 1 kg (2.2 lb.)
Power Consumption
Board WDM-Side Optical Module Typical Power Maximum
Consumption Power
at 25-C (77-F) Consumption
(W) at 55-C (131-F)
(W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
When using the NRZ module, the TN54NS3 board maps 32 ODU0, 16 ODU1, four ODU2, or one ODU3
signals into one OTU3 service.
When using ODB or DQPSK optical module, the TN54NS3 maps 32 ODU0, or 16 ODU1, four ODU2, or
one ODU3 signals into one OTU3 signals, and also maps four ODU2e into one OTU3e signals.
Mechanical Specifications
TN11NS3:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.2 kg (4.9 lb.)
TN52NS3:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.4 kg (5.2 lb.)
TN54NS3:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.8 kg (3.96 lb.)
TN55NS3:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.6 kg (5.7 lb.)
Power Consumption
Board WDM-Side Optical Typical Power Maximum
Module Consumption Power
at 25-C (77-F) Consumption
(W) at 55-C (131-F)
(W)
40 Gbit/s Multirate-2 km 62 69
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Minimum extinction dB 9 9
ratio
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
When accessing 1000 BASE-T services, the specifications of the electrical interface comply with the IEEE
Std 802.3.
Table 12-151 Client-side pluggable optical module specifications (10 Gbit/s services)
Parameter Unit Value
Minimum dB 6 8.2 9 3
extinction
ratio
Minimum dB 30 30 30 30
side mode
suppression
ratio
Minimum dBm -1 -1 -7 -1
receiver
overload
(STM-64)
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.4 kg (3.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
NOTE
The 10 Gbit/s Multirate-10 km-XFP, 10 Gbit/s Multirate-40 km-XFP, and 10 Gbit/s Multirate-80 km-XFP
optical module can be used to access OC-192, STM-64, 10GE WAN, FC1200, and OTU2/OTU2e signals.
The 10 Gbit/s Single-Rate-0.3 km-XFP optical module can be used to access 10GE LAN and FC1200 signals.
Table 12-152 Client-side pluggable optical module specifications (10 Gbit/s services)
Minimum dB 6 8.2 9 3
extinction
ratio
Minimum dB 30 30 30 30
side mode
suppression
ratio
Minimum dBm -1 -1 -7 -1
receiver
overload
(STM-64)
The 800-SM-LC-L-0.3 km-XFP optical module can be used to access FC800 signals.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
– TN12TDX: 1.4 kg (3.1 lb.)
– TN52TDX: 1.4 kg (3.1 lb.)
– TN53TDX: 1.5 kg (3.3 lb)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Minimum extinction dB 9 9
ratio
NOTE
The electrical interface specifications comply with IEEE Std 802.3 when receiving 1000 BASE-T services.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.5 kg (5.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (131°F)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
I-16/SR-1 OC-48-2 km-eSFP, S-16.1/IR-1 OC-48-15 km-eSFP, L-16.1/LR-1 OC-48-40 km-eSFP and L-16.2/
LR-2 OC-48-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48, FC200, FC100, FICON,
FICON Express, FDDI, GE, STM-4, OC-12, ESCON, STM-1, OC-3, and DVB-ASI signals.
Only the S-16.1/IR-1 OC-48-15 km-eSFP optical module supports FE services, and it can only connect to a
100BASE-LX10 optical module.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
NOTE
Target km 10 10 40 40
transmission
distance
Maximum dBm -3 -3 3 3
mean launched
power
Minimum dBm -9 -9 -2 -2
mean launched
power
Minimum dB 6 6 6 6
extinction ratio
Minimum dBm -3 -3 -3 -3
receiver
overload
NOTE
2.125 Gbit/s Multirate-0.5 km-eSFP optical module can be used to access FC200, GE, FC100, FDDI, FICON,
FICON Express, and FE signals.
1000 BASE-LX-10 km-eSFP, 1000 BASE-LX-40 km-eSFP and 1000 BASE-ZX-80 km-eSFP optical module
can be used to access GE, FC100, STM-4, OC-12, ESCON, STM-1, OC-3, FDDI, FICON, FE and DVB-ASI
signals.
NOTE
When accessing 1000 BASE-T services, the specifications of the electrical interface comply with the IEEE Std
802.3.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
1.25 Gbit/s Multirate (CWDM)-40 km-eSFP optical module can be used to access GE, FC100, STM-4, OC-12,
ESCON, STM-1, OC-3, FDDI, FICON, FE, DVB-ASI signals.
2.67 Gbit/s Multirate (CWDM)-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, FDDI, FICON, FICON Express, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, FE
signals.
NOTE
2.67 Gbit/s Multirate (DWDM)-120 km-eSFP optical can be used to access OTU1, STM-16, OC-48, FC200,
FC100, FDDI, FICON, FICON Express, GE, STM-4, OC-12, ESCON, STM-1, OC-3, and DVB-ASI signals.
NOTE
SDI module can be used to access DVB-ASI, SDI, HD-SDI, HD-SDIRBR, 3G-SDI, and 3G-SDIRBR signals.
NOTE
4.25 Gbit/s Multirate-0.3 km-eSFP and 4.25 Gbit/s Multirate-10 km-eSFP optical module can be used to access
FC400, and FICON4G signals.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.7 kg (1.5 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN54TOA 23 25
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
When accessing 1000 BASE-T services, the specifications of the electrical interface comply with the IEEE
Std 802.3.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.85 kg (1.87 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
I-16/SR-1 OC-48-2 km-eSFP module, S-16.1/IR-1 OC-48-15 km-eSFP module, L-16.1/LR-1 OC-48-40 km-
eSFP module and L-16.2/LR-2 OC-48-80 km-eSFP module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, FICON, FICON Express, FDDI, GE, STM-4, OC-12, ESCON, STM-1, OC-3, and DVB-ASI
signals.
Only the S-16.1/IR-1 OC-48-15 km-eSFP optical module supports FE services, and it can only connect to a
100BASE-LX10 optical module.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
NOTE
1000 BASE-BX10-U-eSFP module, 1000 BASE-BX10-D-eSFP module, 1000 BASE-BX-U-eSFP module, and
1000 BASE-BX-D-eSFP module can be used to access GE signals.
Target km 10 10 40 40
transmission
distance
Maximum dBm -3 -3 3 3
mean launched
power
Minimum dBm -9 -9 -2 -2
mean launched
power
Minimum dB 6 6 6 6
extinction ratio
Minimum dBm -3 -3 -3 -3
receiver
overload
NOTE
2.125 Gbit/s Multi-rate-eSFP module can be used to access FC200, GE, FC100, and FE signals.
1000 BASE-LX-10 km-eSFP module, 1000 BASE-LX-40 km-eSFP module and 1000 BASE-ZX-80 km-eSFP
module can be used to access GE, FC100, STM-4, OC-12, ESCON, STM-1, OC-3, FE and DVB-ASI signals.
When accessing 1000 BASE-T services, the specifications of the electrical interface comply with the IEEE Std
802.3.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
1.25 Gbit/s Multirate (CWDM)-40 km-eSFP can be used to access GE, FC100, STM-4, OC-12, ESCON, STM-1,
OC-3, FE, DVB-ASI signals.
2.67 Gbit/s Multirate (CWDM)-80 km-eSFP can be used to access OTU1, STM-16, OC-48, FC200, FC100,
GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, FE signals.
NOTE
2.67 Gbit/s Multirate (DWDM)-120 km-eSFP can be used to access OTU1, STM-16, OC-48, FC200, FC100,
GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, FE signals.
NOTE
0.1 Gbit/s to 3 Gbit/s Multirate 10 km-Video eSFP module can be used to access DVB-ASI, SDI, and HD-SDI
signals.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
TN11TOM: 1.4 kg (3.1 lb.)
TN52TOM: 1.5 kg (3.3 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11TOM 55 60
TN52TOM 81 89.1
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
The I-16/SR-1 OC-48-2 km-eSFP, S-16.1/IR-1 OC-48-15 km-eSFP, L-16.1/LR-1 OC-48-40 km-eSFP and
L-16.2/LR-2 OC-48-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48, FC200, FC100,
GE, STM-4, OC-12, ESCON, STM-1, OC-3, and DVB-ASI signals.
Only the S-16.1/IR-1 OC-48-15 km-eSFP optical module supports FE services, and it can only connect to a
100BASE-LX10 optical module.
Maximum dBm -3 0 3 3
mean
launched
power
Maximum nm N/A 1 1 1
-20 dB
spectral
width
Minimum dB N/A 30 30 30
side mode
suppression
ratio
Minimum dBm -3 0 -9 -9
receiver
overload
NOTE
The 2.125 Gbit/s Multirate-0.5 km-eSFP optical module can be used to access FC200, GE, FC100, and FE
signals.
The 1000 BASE-LX-10 km-eSFP, 1000 BASE-LX-40 km-eSFP and 1000 BASE-ZX-80 km-eSFP optical
module can be used to access GE, FC100, STM-4, OC-12, ESCON, STM-1, OC-3, FE and DVB-ASI signals.
NOTE
When accessing 1000 BASE-T services, the specifications of the electrical interface comply with the IEEE
Std 802.3.
Minimum dB 9 9 9 9
extinction
ratio
Minimum dBm 0 -3 -3 -3
receiver
overload
NOTE
The 1.25 Gbit/s Multirate (CWDM)-40 km-eSFP optical module can be used to access GE, FC100, STM-4,
OC-12, ESCON, STM-1, OC-3, FE, or DVB-ASI signals.
The 2.67 Gbit/s Multirate (CWDM)-80 km-eSFP optical module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, or FE signals.
NOTE
The 2.67 Gbit/s Multirate (DWDM)-120 km-eSFP optical module can be used to access OTU1, STM-16, OC-48,
FC200, FC100, GE, STM-4, OC-12, ESCON, STM-1, OC-3, DVB-ASI, or FE signals.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.1 kg (2.4 lb)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN12TQM 25 27.5
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
NOTE
The 10 Gbit/s Multirate-10 km-XFP, 10 Gbit/s Multirate-40 km-XFP, and 10 Gbit/s Multirate-80 km-XFP
optical module can be used to access OC-192, STM-64, 10GE WAN, FC1200, and OTU2/OTU2e signals.
The 800-SM-LC-L-0.3 km-XFP optical module can be used to access 10GE LAN and FC1200 signals.
Table 12-178 Client-side pluggable optical module specifications (10 Gbit/s services)
Minimum dB 6 8.2 9 3
extinction
ratio
Minimum dB 30 30 30 30
side mode
suppression
ratio
Minimum dBm -1 -1 -7 -1
receiver
overload
(STM-64)
NOTE
The 800-SM-LC-L-0.3 km-XFP module can be used to access FC800 signals.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
TN11TQX: 1.5 kg (3.3 lb.)
TN52TQX: 1.6 kg (3.5 lb.)
TN53TQX: 1.6 kg (3.5 lb.)
TN55TQX: 1.6 kg (3.5 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN53TQX 45 50
TN55TQX 45 50
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
1304.5
1324.5
1317.5
1337.5
1304.5
1324.5
1317.5
1337.5
Mechanical Specifications
TN11TSXL:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.5 kg (5.5 lb.)
TN53TSXL:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.4 kg (3.1 lb.)
TN54TSXL:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.4 kg (3.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11TSXL 90.2 96
TN53TSXL 75 83
TN54TSXL 58 64
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.9 kg (2.0 lb.)
Power Consumption
Board Typical Power Consumption Maximum Power
at 25°C (77°F) (W) Consumption at 55°C (131°F)
(W)
ENQ2 40 44
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Minimum extinction dB 6 6
ratio
Mechanical Specifications
TN55NPO2:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.7 kg (3.7 lb.)
TN54PQ2:
l Dimensions of front panel: 24.5 mm (W) x 68 mm (D) x 57 mm (H) (0.96 in. (W) x 2.69
in. (D) x 2.24 in. (H))
l Weight: 0.1 kg (0.22 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
NOTE
Margins exist between the default input power low threshold and the receiver sensitivity and between the
default input power high threshold and the overload point. These margins ensure that the system can report
an input power low or high alarm before the actual input power reaches the receiver sensitivity or overload
point.
Minimum extinction dB 6 6
ratio
Table 12-184 Specifications of the red and blue band filters on the TN55NPO2E board
Item Unit Value
Mechanical Specifications
TN55NPO2E:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.7 kg (3.75 lb.)
TN54PQ2:
l Dimensions of front panel: 24.5 mm (W) x 68 mm (D) x 57 mm (H) (0.96 in. (W) x 2.69
in. (D) x 2.24 in. (H))
l Weight: 0.1 kg (0.22 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Mechanical Specifications
TNK2SXM:
l Dimensions of front panel: 34.1 mm (W) x 220 mm (D) x 602.5 mm (H) or 1.4 in. (W) x
8.7 in. (D) x 23.7 in. (H)
l Weight: 3.74 kg (8.2 lb.)
Power Consumption
Board Power Power Typical Power Maximum
Consumption Consumption Consumption Power
at Warm at Warm at 25°C (77°F) Consumption
Backup (25°C, Backup (55°C, (W) at 55°C (131°F)
77°F) (W) 131°F) (W) (W)
Mechanical Specifications
TNK4SXH:
l Dimensions of front panel: 34.1 mm (W) x 220 mm (D) x 602.5 mm (H) or 1.4 in. (W) x
8.7 in. (D) x 23.7 in. (H)
l Weight: 2.68 kg (5.8Ib.)
Power Consumption
Board Power Power Typical Power Maximum
Consumption Consumption Consumption Power
at Warm at Warm at 25°C (77°F) Consumption
Backup (25°C, Backup (55°C, (W) at 55°C (131°F)
77°F) (W) 131°F) (W) (W)
Mechanical Specifications
TNK2XCT:
l Dimensions of front panel: 34.1 mm (W) x 220 mm (D) x 602.5 mm (H) (1.4 in. (W) x 8.7
in. (D) x 23.7 in. (H))
l Weight: 3.6 kg (7.9 lb.)
TNK4XCT:
l Dimensions of front panel: 34.1 mm (W) x 220 mm (D) x 602.5 mm (H) (1.4 in. (W) x 8.7
in. (D) x 23.7 in. (H))
l Weight: 2.9 kg (6.4 lb.)
Power Consumption
Board Power Power Typical Power Maximum
Consumption Consumption Consumption Power
at Warm at Warm at 25°C (77°F) Consumption
Backup (25°C, Backup (55°C, (W) at 55°C (131°F)
77°F) (W) 131°F) (W) (W)
Mechanical Specifications
l Dimensions of the front panel: 27.9 mm (W) x 220 mm (D) x 581.5 mm (H) or 1.1 in. (W)
x 8.7 in. (D) x 22.9 in. (H)
l Weight: 3.40 kg (7.49 lb.)
Power Consumption
Board Power Power Typical Power Maximum
Consumption Consumption Consumption Power
at Warm at Warm at 25°C (77°F) Consumption
Backup (25°C, Backup (55°C, (W) at 55°C (131°F)
77°F) (W) 131°F) (W) (W)
Mechanical Specifications
l Dimensions of the front panel: 37.6 mm (W) x 220 mm (D) x 350.3 mm (H) (1.5 in. (W)
x 8.7 in. (D) x 13.8 in. (H))
l Weight: 1.8 kg (4.0 lb.)
Power Consumption
Board Power Power Typical Power Maximum
Consumption Consumption Consumption Power
at Warm at Warm at 25°C (77°F) Consumption
Backup (25°C, Backup (55°C, (W) at 55°C (131°F)
77°F) (W) 131°F) (W) (W)
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.2 kg (2.65 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Mechanical Specifications
Dimensions of front panel:
l TN16SCC: 37.6 mm (W) x 220 mm x (D) 350.3 mm (H) or 2.1 in. (W) x 8.7 in. (D) x 13.8
in. (H)
l TN22SCC: 25.4 mm (W) x 220 mm (D) ox 118.9 mm (H) or 1.0 in. (W) x 8.7 in. (D) x 4.7
in. (H)
l TN51SCC: 25.4 mm (W) x 220 mm (D) x 264.6 mm (H) or 1.0 in. (W) x 8.7 in. (D) x 10.4
in. (H)
l TN52SCC: 25.4 mm (W) x 220 mm (D) x 264.6 mm (H) or 1.0 in. (W) x 8.7 in. (D) x 10.4
in. (H)
l TNK2SCC: 76.2 mm (W) x 220 mm (D) x 110.0 mm (H) or 3.0 in. (W) x 8.7 in. (D) x 4.4
in. (H)
Weight:
l TN16SCC: 1.3 kg (2.8 lb.)
l TN22SCC: 0.5 kg (1.1 lb.)
l TN51SCC: 1.2 kg (2.6 lb.)
l TN52SCC: 1.0 kg (2.2 lb.)
l TNK2SCC: 0.9 kg (2.0 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Mechanical Specifications
l Dimensions of the front panel:
– TN16AUX: 76.2 mm (W) x 220 mm (D) x 80 mm (H) (3.0 in. (W) x 8.7 in. (D) x 3.1
in. (H))
– TN41AUX: 25.4 mm (W) x 220 mm (D) x 133.4 mm (H) (1.0 in. (W) x 8.7 in. (D) x
5.3 in. (H))
– TN51AUX: 25.4 mm (W) x 220 mm (D) x 107.5 mm (H) (1.0 in. (W) x 8.7 in. (D) x
4.2 in. (H))
– TN22AUX: 25.4 mm (W) x 220 mm (D) x 118.9 mm (H) (1.0 in. (W) x 8.7 in. (D) x
4.7 in. (H))
– TN61AUX: 25.4 mm (W) x 220 mm (D) x 118.9 mm (H) (1.0 in. (W) x 8.7 in. (D) x
4.7 in. (H))
l Weight:
– TN16AUX: 0.6 kg (1.32 lb.)
– TN41AUX: 0.5 kg (1.1 lb.)
– TN51AUX: 0.4 kg (0.88 lb.)
– TN22AUX: 0.5 kg (1.1 lb.)
– TN61AUX: 0.6 kg (1.32 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN41AUX 12.8 14
Optical Specifications
Table 12-185 lists the optical specifications of the D40.
-1 dB bandwidth nm ≥ 0.2
Mechanical Specifications
l Dimensions of front panel:
– TN11D40: 76.2 mm (W) x 220 mm (D) x 264.6 mm (H) (3.0 in. (W) x 8.7 in. (D) x
10.4 in. (H))
– TN12D40: 50.8 mm (W) x 220 mm (D) x 264.6 mm (H) (2.0 in. (W) x 8.7 in. (D) x
10.4 in. (H))
l Weight:
– TN11D40: 2.2 kg ( 4.8 lb.)
– TN12D40: 2.0 kg ( 4.4 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-186 lists the optical specifications of the D40V board.
Insertion loss dB ≤ 8a
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 76.2 mm (3.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.3 kg (5.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Mechanical Specifications
l Dimensions of front panel: 25.4 mm (W) x 220 mm x 118.9 mm (H) (1.0 in. (W) x 8.7 in.
(D) x 4.7 in. (H))
l Weight: 0.8 kg (1.8 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Mechanical Specifications
TN13FIU/TN14FIU:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
TN21FIU:
l Dimensions of front panel: 25.4 mm (W) x 220.0 mm (D) x 118.9 mm (H) (1.0 in. (W) x
8.7 in. (D) x 4.7 in. (H))
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Directivity - dB > 45
a: The input and output ends are defined based on the multiplexing process of the interleaver.
IN-TE dB <3
IN-TO
Directivity - dB > 45
a: The input and output ends are defined based on the multiplexing process of the interleaver.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.2 kg (2.7 lb.)
Power Consumption
Board Typical power Maximum power
consumption at 25°C (77° consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-191 lists the optical specifications of the M40 board.
Mechanical Specifications
l Dimensions of front panel:
– TN11M40: 76.2 mm (W) x 220 mm (D) x 264.6 mm (H) (3.0 in. (W) x 8.7 in. (D) x
10.4 in. (H))
– TN12M40: 50.8 mm (W) x 220 mm (D) x 264.6 mm (H) (2.0 in. (W) x 8.7 in. (D) x
10.4 in. (H))
l Weight:
– TN11M40: 2.2 kg ( 4.8 lb.)
– TN12M40: 2.0 kg ( 4.4 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-192 lists the optical specifications of the M40V board.
Insertion loss dB ≤ 8a
Mechanical Specifications
l Dimensions of front panel:
– TN11M40V: 76.2 mm (W) x 220 mm (D) x 264.6 mm (H) (3.0 in. (W) x 8.7 in. (D) x
10.4 in. (H))
– TN12M40V: 50.8 mm (W) x 220 mm (D) x 264.6 mm (H) (2.0 in. (W) x 8.7 in. (D) x
10.4 in. (H))
l Weight:
– TN11M40V: 2.3 kg (5.1 lb.)
– TN12M40V: 2.3 kg (5.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-193 lists the optical specifications of the CMR1 board.
Isolation dB > 40
Mechanical Specifications
l Dimensions of front panel: 25.4 mm (W) x 220 mm (D) x 118.9 mm (H) (1.0 in. (W) x 8.7
in. (D) x 4.7 in. (H))
l Weight: 0.5 kg (1.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-194 lists the optical specifications of the CMR2 board.
NOTE
The equipment can transmit the 1271 nm wavelength by connecting the CMR2 board to corresponding
third-party equipment, though the equipment does not provide the 1271 nm OTU board and line board.
Mechanical Specifications
The mechanical specifications of TN11CMR2 are as follows.
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.8 kg (1.8 lb.)
l Dimensions of front panel: 25.4 mm (W) x 220 mm (D) x 118.9 mm (H) (1.0 in. (W) x 8.7
in. (D) x 4.7 in. (H))
l Weight: 0.5 kg (1.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-195 lists the optical specifications of the CMR4 board.
NOTE
The equipment can transmit the 1291 nm wavelength by connecting the CMR4 board to corresponding
third-party equipment, though the equipment does not provide the 1291 nm OTU board and line board.
Mechanical Specifications
The mechanical specifications of TN11CMR4 board are as follows:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.9 kg (2.0 lb.)
The mechanical specifications of TN21CMR4 board are as follows:
l Dimensions of front panel: 25.4 mm (W) x 220 mm (D) x 118.9 mm (H) or 1.0 in. (W) x
8.7 in. (D) x 4.7 in. (H)
l Weight: 0.5 kg (1.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Isolation dB ≥40
Isolation dB ≥40
Mechanical Specifications
Mechanical specifications of the TN11DMR1 board:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.7 kg (1.5 lb.)
l Dimensions of front panel: 25.4 mm (W) x 220 mm (D) x 118.9 mm (H) (1.0 in. (W) x 8.7
in. (D) x 4.7 in. (H))
l Weight: 0.7 kg (1.5 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-198 lists the optical specifications of the MR2 board.
Mechanical Specifications
The mechanical specifications of TN11MR2 are as follows:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.9 kg (2.0 lb.)
The mechanical specifications of TN21MR2 are as follows:
l Dimensions of front panel: 118.9 mm (H) x 220 mm (D) x 25.4 mm (W) or 4.7 in. (H) x
8.7 in. (D) x 1 in. (W)
l Weight: 0.5 kg (1.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-199 lists the optical specifications of the MR4 board.
Mechanical Specifications
Mechanical specifications of TN11MR4 board are as follows:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.9 kg (1.98 lb.)
Mechanical specifications of TN21MR4 board are as follows:
l Dimensions of front panel: 118.9 mm (H) x 220 mm (D) x 25.4 mm (W) or 4.7 in. (H) x
8.7 in. (D) x 1 in. (W)
l Weight: 0.5 kg (1.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-201 lists the optical specifications of the MR8 board.
Group 1 2 3 4 5
A1/D1 Waveleng 80 64 48 32 16
th No.
A2/D2 Waveleng 78 62 46 30 14
th No.
A3/D3 Waveleng 76 60 44 28 12
th No.
A4/D4 Waveleng 74 58 42 26 10
th No.
A5/D5 Waveleng 72 56 40 24 8
th No.
A6/D6 Waveleng 70 54 38 22 6
th No.
Group 1 2 3 4 5
A7/D7 Waveleng 68 52 36 20 4
th No.
A8/D8 Waveleng 66 50 34 18 2
th No.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-203 lists the optical specifications of the MR8V board.
A1/D1 Waveleng 80 64 48 32 16
th No.
Group 1 2 3 4 5
A2/D2 Waveleng 78 62 46 30 14
th No.
A3/D3 Waveleng 76 60 44 28 12
th No.
A4/D4 Waveleng 74 58 42 26 10
th No.
A5/D5 Waveleng 72 56 40 24 8
th No.
A6/D6 Waveleng 70 54 38 22 6
th No.
A7/D7 Waveleng 68 52 36 20 4
th No.
Group 1 2 3 4 5
A8/D8 Waveleng 66 50 34 18 2
th No.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-205 lists the optical specifications of the SBM2 board.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.8 kg (1.8 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
IN-EXPO dB ≤ 12.5
IN-TOA dB ≤1
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.1 kg (2.4 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-207 lists the optical specifications of the RMU9 board.
AMxa-TOA dB ≤ 12.5b
ROA-OUT dB ≤ 1.5
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.1 kg (2.4 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11RMU902 8.2 9
Optical Specifications
Table 12-208 lists the optical specifications of the ROAM board.
IN-DM dB ≤7
EXPI-OUT dB ≤ 14b
IN-EXPO dB ≤3
Attenuation range dB 0 to 20
Extinction ratio dB ≥ 30
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 76.2 mm (3.0 in.) x 220 mm
(8.7 in.)
l Weight: 3.2 kg (7.0 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11ROAM 66 72.6
Optical Specifications
Optical channels - 40 80
Extinction ratio dB ≥ 35 ≥ 35
Reconfiguration time s ≤3 ≤3
Directivity dB 35 35
Mechanical Specifications
Dimensions of front panel:
l TN12WSD9: 50.8 mm (W) x 220 mm (D) x 264.6 mm (H) or 2.0 in. (W) x 8.7 in. (D) x
10.4 in. (H)
l TN13WSD9: 76.2 mm (W) x 220 mm (D) x 264.6 mm (H) or 3.0 in. (W) x 8.7 in. (D) x
10.4 in. (H)
Weight:
l TN12WSD9: 2.7 kg (5.94 lb.)
l TN13WSD9: 2.9 kg (6.38 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Optical channels - 40 80
Insertion AMxa-OUT dB ≤ 8b ≤ 8b
loss
EXPI-OUT
Extinction ratio dB ≥ 35 ≥ 35
Reconfiguration time s ≤3 ≤3
Directivity dB 35 35
Mechanical Specifications
Dimensions of front panel:
l TN12WSM9: 50.8 mm (W) x 220 mm (D) x 264.6 mm (H) or 2.0 in. (W) x 8.7 in. (D) x
10.4 in. (H)
l TN13WSM9: 76.2 mm (W) x 220 mm (D) x 264.6 mm (H) or 3.0 in. (W) x 8.7 in. (D) x
10.4 in. (H)
Weight:
l TN12WSM9: 2.7 kg (5.94 lb.)
l TN13WSM9: 2.9 kg (6.38 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-211 lists the optical specifications of the WSMD2 board.
Optical channels - 40
IN-DM ≤ 4.5a
IN-EXPO
Extinction ratio dB ≥ 35
Reconfiguration time s ≤3
Directivity dB 35
a: This value can be reached when the attenuation of the VOA is set to 0 dB.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 3.2 kg (7.0 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
TN11WSMD4 TN12WSMD4
Optical channels - 40 80
TN11WSMD4 TN12WSMD4
IN-DMxa ≤8 ≤8
Extinction ratio dB ≥ 35 ≥ 35
Reconfiguration time s ≤3 ≤3
Directivity dB 35 35
Dimension - 4 4
a: AMx represents the AM1-AM4 interface. DMx represents the DM1-DM4 interface.
b: This value can be reached when the attenuation of the VOA is set to 0 dB.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight:
– TN11WSMD4: 3.2 kg (7.1 lb.)
– TN12WSMD4: 2.6 kg (5.7 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11WSMD4 17 18.7
TN12WSMD4 12 15
Optical Specifications
Optical channels - 80
IN-DMxa/EXPO ≤ 12
Extinction ratio dB ≥ 35
Reconfiguration time s ≤3
Directivity dB 35
Dimension - 9
a: AMx represents the AM1-AM8 interface. DMx represents the DM1-DM8 interface.
b: This value can be reached when the attenuation of the VOA is set to 0 dB.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 3.1 kg (6.8 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11WSMD9 25 30
Optical Specifications
Mechanical Specifications
l Dimensions of board: 345.0 mm (H) x 218.5 mm (D) x 76.0 mm (W) or 13.8 in. (H) x 8.7
in. (D) x 3.0 in. (W)
Weight
l CRPC01: 4.0 kg (8.8 1b.)
l CRPC03: 4.2 kg (9.2 1b.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Nominal single- 40 dB 4 4 4
wavelength input channels m
optical power
80 dB 1 1 1
channels m
Channel gain dB 20 to 31
a: The gain can be adjusted continuously. The noise figure varies with the gain. The previous table lists the noise
figure when the noise figure uses the typical value.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.4 kg (3.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (131°F)
TN11DAS1 22 28.6
Optical Specifications
Type - TN11HBA
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 76.2 mm (3.0 in.) x 220 mm
(8.7 in.)
l Weight: 3.0 kg (6.6 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
HBA 47 75
Optical Specifications
Input power range per 40 channels dBm -32 to -14 -32 to -20 -32 to -23.5
channel
80 channels dBm -32 to -17 -32 to -23 -32 to -26.5
Pump leakage at input dBm < -30 < -30 < -30
Dynamic dB 20
attenuation
range
Adjustment accuracy dB 1
a: The gain can be adjusted continuously. The noise figure varies with the gain. The previous table lists the noise
figure when the noise figure uses the typical value.
Nominal gain dB 20 26 31
Input power range per 40 channels dBm -32 to -16 -32 to -22 -32 to -27
channel
80 channels dBm -32 to -19 -32 to -25 -32 to -30
Channel gain dB 20 to 31
Pump leakage at input dBm < -30 < -30 < -30
Dynamic dB 20
attenuation
range
Adjustment accuracyb dB 1
a: The gain can be adjusted continuously. The noise figure varies with the gain. The previous table lists the noise
figure when the noise figure uses the typical value.
Nominal gain dB 20 26 31
Input power range per 40 channels dBm -32 to -19 -32 to -25 -32 to -30
channel
80 channels dBm -32 to -22 -32 to -28 -32
Channel gain dB 20 to 31
Gain flatness dB ≤2 ≤2 ≤2
Pump leakage at input dBm < -30 < -30 < -30
Dynamic dB 20
attenuation
range
Adjustment accuracyb dB 1
a: The gain can be adjusted continuously. The noise figure varies with the gain. The previous table lists the noise
figure when the noise figure uses the typical value.
Nominal gain dB 24 29 36
Channel gain dB 24 to 36
Gain flatness dB ≤2 ≤2 ≤2
Pump leakage at input dBm < -30 < -30 < -30
Dynamic dB 20
attenuation
range
Adjustment accuracyb dB 1
a: The gain can be adjusted continuously. The noise figure varies with the gain. The previous table lists the noise
figure when the noise figure uses the typical value.
Nominal gain dB 23 30 34
Input power range 40 dBm -32 to -16 -32 to -23 -32 to -27
per channel channels
Channel gain dB 23 to 34
Gain flatness dB ≤2 ≤2 ≤2
Pump leakage at input dBm < -30 < -30 < -30
Dynamic dB 20
attenuation
range
Adjustment accuracyb dB 1
a: The gain can be adjusted continuously. The noise figure varies with the gain. The previous table lists the noise
figure when the noise figure uses the typical value.
Nominal gain dB 16 19 23
Input power range 40 dBm -24 to -12 -24 to -15 -24 to -19
per channel channels
Channel gain dB 16 to 23
Gain flatness dB ≤2 ≤2 ≤2
Pump leakage at input dBm < -30 < -30 < -30
Dynamic dB 20
attenuation
range
Adjustment accuracy dB 1
a: The gain can be adjusted continuously. The noise figure varies with the gain. The previous table lists the noise
figure when the noise figure uses the typical value.
Mechanical Specifications
l Dimensions of front panel:
– TN11OAU1/TN12OAU1: 50.8 mm (W) x 220 mm (D) x 264.6 mm (H) (2.0 in. (W) x
8.7 in. (D) x 10.4 in. (H))
– TN13OAU1: 25.4 mm (W) x 220 mm (D) x 264.6 mm (H) (1.0 in. (W) x 8.7 in. (D) x
10.4 in. (H))
l Weight:
– TN11OAU1/TN12OAU1: 1.8 kg (4.0 lb.)
– TN13OAU1: 1.6 kg (3.5 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (131°F)
Optical Specifications
Nominal gain dB 20 23 17
Pump leakage at input dBm < -30 < -30 < -30
Dynamic dB 20
attenuatio
n range
Adjustment accuracya dB 1
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight:
l TN11OBU1: 1.3 kg (2.9 lb.)
l TN12OBU1: 1.1 kg (2.4 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
OBU205
80 -24 to -19
Channels
Nominal gain dB 23
OBU205
Dynamic dB 20
attenuatio
n range
Adjustment accuracya dB 1
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight:
– TN11OBU2: 1.9 kg (4.2 lb.)
– TN12OBU2: 1.6 kg (3.5 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11OBU205 17 24
TN12OBU205 14 19
Optical Specifications
LEAF fibers 19 to 35
G.653 fibers 19 to 35
TWRS fibers 19 to 35
TW-C fibers 19 to 35
PDG dB ≤ 0.7
PMD ps ≤ 0.7
LEAF fibers 5 to 12
G.653 fibers 5 to 12
TWRS fibers 5 to 12
TW-C fibers 5 to 12
PDG dB ≤ 0.5
PMD ps ≤ 0.5
Output dBm -7 to 20
optical power
Channel gain dB 14 to 23
PDG dB ≤ 0.5
PMD ps ≤ 0.5
a: The gain can be adjusted continuously. The noise figure varies according to the gain. The previous table lists
the noise figure when the noise figure uses the typical value.
b: The gain of the Raman module can be set to the maximum value. The actual gain of the board is a variable and
depends on the fiber type and status.
Mechanical Specifications
l Dimensions of front panel: 50.8 mm (W) x 220 mm (D) x 264.6 mm (H) (2.0 in. (W) x 8.7
in. (D) x 10.4 in. (H))
l Weight: 2.5 kg (5.5 Ib.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11RAU1 55 70
NOTE
A margin of the lower threshold of input optical power compared with the receiver sensitivity of the board
and a margin of the upper threshold of output optical power compared with the overload point of the board
are reserved on the U2000 as a precaution.
Optical Specifications
Table 12-227 lists the optical specifications of the HSC1 board.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-228 lists the optical specifications of the SC1 board.
a: The SC1 board at the receive end can automatically determines the signal rate of the OSC
channel based on the OSC board configured at the transmit end. By default, the signal rate of
the OSC channel is 16 Mbit/s.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-229 lists the optical specifications of the SC2.
a: The SC2 board at the receive end can automatically determines the signal rate of the OSC
channel based on the OSC board configured at the transmit end. By default, the signal rate of
the OSC channel is 16 Mbit/s.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-230 lists the optical specifications of the ST2.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.95 kg (2.09 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Mechanical Specifications
l Dimensions of the front panel:
– TNK2STG: 50.3mm (W) x 220 mm (D) x 107.5 mm (H) (2.0 in. (W) x 8.7 in. (D) x 4.2
in. (H))
– TN52STG: 28.8 mm (W) x 220 mm (D) x 107.5 mm (H) (1.1 in. (W) x 8.7 in. (D) x
4.2 in. (H))
l Weight:
– TN52STG/TNK2STG: 0.5 kg (1.1 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
TN12DCP
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
TN12OLP01 TN12OLP03
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
Weight
l TN12OLP: 1.0 kg (2.20 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-233 lists the optical specifications of the SCS board.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 0.8 kg (1.8 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-234 lists the optical specifications of the MCA4 board.
Detect range for single channel optical power dBm -30 to -10
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.9 kg (4.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-235 lists the optical specifications of the MCA8 board.
Detect range for single channel optical power dBm -30 to -10
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 50.8 mm (2.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.9 kg (4.2 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
Optical Specifications
Table 12-236 lists the optical specifications of the OPM8 board.
Detect range for single channel optical power dBm -30 to -10
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11OPM8 12 15
Optical Specifications
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Optical Module Typical Power Maximum Power
Type Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
TN11WMU - 12 15
Dynamic attenuation dB 20
range
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Optical Module Typical Power Maximum Power
Type Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
Dynamic dB 20
attenuation range
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.0 kg (2.2 lb.)
Power Consumption
Board Optical Module Typical Power Maximum Power
Type Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
Optical Specifications
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 2.0 lb. (0.9 kg)
Power Consumption
Board Optical Module Typical Power Maximum Power
Type Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
Optical Specifications
DC DC DC DC DC DC D DCU0
U0 U0 U0 U0 U0 U06 CU 8
1 2 3 4 5 07
Polarization mode ps 0.4 0.5 0.6 0.7 0.8 0.8 0.3 0.3
dispersion
a: The maximum input power refers to the maximum input optical power permitted by the
optical module on the condition that the optical module is not damaged.
a: The maximum input power refers to the maximum input optical power permitted by the
optical module on the condition that the optical module is not damaged.
Mechanical Specifications
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.5 kg (3.3 lb)
Power Consumption
Board Optical Module Typical Power Maximum Power
Type Consumption at Consumption at
25°C (77°F) (W) 55°C (131°F) (W)
Optical Specifications
Table 12-243 lists the optical specifications of the TDC board.
Optical channels - 80
Mechanical Specifications
The mechanical specifications of the board are as follows:
l Dimensions of front panel (H x W x D): 264.6 mm (10.4 in.) x 25.4 mm (1.0 in.) x 220 mm
(8.7 in.)
l Weight: 1.14 kg (2.51 lb.)
Power Consumption
Board Typical Power Maximum Power
Consumption at 25°C (77° Consumption at 55°C
F) (W) (131°F) (W)
TN11TDC 13 15
Table 12-244 Performance requirements for C-band dispersion compensation optical fibers (G.
652 fibers)
a: The Max. Allowed Power refers to the maximum input optical power that the optical module
can receive without being damaged.
Table 12-245 Performance requirements for C-band dispersion compensation optical fibers (G.
655 LEAF fibers)
a: The Max. Allowed Power refers to the maximum input optical power that the optical module
can receive without being damaged.
Table 12-246 Performance requirements for C-band dispersion compensation optical fibers (G.
653 fibers)
DCM Distance Max. DSC PMD PDL Max. Opera
Module (mi./km) Insert R (ps) (dB) Allowe ting
ion d Wavel
Loss Powera ength
(dB) (dBm) (nm)
a: The Max. Allowed Power refers to the maximum input optical power that the optical module
can receive without being damaged.
Table 12-247 Performance requirements for C-band dispersion compensation optical fibers
(TW-RS fibers)
DCM Module Distance Max. DSC PMD PDL Max. Opera
(mi./km) Insert R (ps) (dB) Allowe ting
ion d Wavel
Loss Powera ength
(dB) (dBm) (nm)
a: The Max. Allowed Power refers to the maximum input optical power that the optical module
can receive without being damaged.
The section lists the commands used to configure the Ethernet system, such as Ethernet interface,
flow, VLAN, protocols, and QoS.
A.14 Configuring OTN Overhead
A.15 Automatic Optical Power Management
This section lists the commands used to configure all types of the automatic optic power
management functions that system supports.
A.16 Configuring MCA
This section lists the commands used to configure the MCA function.
A.17 Configuring Tunable Dispersion Compensator
This section lists the commands used to configure the tunable dispersion compensator (TDC)
function.
A.18 System Monitor
This section lists the commands used to monitor a system.
A.19 Performance Management
This section lists commands which used to manage the system performance.
A.20 Alarm and Event Management
This section lists commands which used to manage alarm and event.
A.21 Configuring LPT
This section lists the commands used to configure the LPT function.
A.22 Configuring Loopback
This section lists the commands used to check the connection between two points by the loopback
method.
A.23 Connection Test
This section lists the commands used to test the connection by transmitting and detecting the bit
sequence between two points.
A.24 System Maintenance
This section lists the commands used to maintain a system.
A.25 Security Management
This section lists the commands which used to configure the security function to control user's
access.
A.26 Backup and Recover
This section lists commands which used to backup and recover the data on the system.
A.27 System Update
This section lists commands which used to update the system.
A.28 Patch Management
This section lists commands which used to manage the patch running on the system.
A.29 Database Management
This section lists commands which used to manage the databases of the system.
A.30 Log Management
This section lists commands which used to manage the log.
A.31 License Management
This section lists commands which used to maintain the License.
General Format
The following is the general structure of TL1 input commands:
<COMMAND_CODE>:<STAGING_PARAMETER_BLOCKS>:<MESSAGE_PAYLOAD_BLOCK(S)>;
l <COMMAND_CODE>
Determines the action (that is, pragmatics) to be taken at the NE as a result of receiving the
input message.
l <STAGING_PARAMETER_BLOCKS>
Determines the target NE and the identifier of the object to be acted upon by the input
message.
l <MESSAGE_PAYLOAD_BLOCK(S)>
The subject matter relating to the action to be performed by the input message.
l semi-colon character (;)
Terminates a TL1 input message.
Command Code
Each command must begin with a command code consisting of a mandatory verb followed by
up to two other optional modifiers, each separated by a hyphen "-".
<COMMAND CODE>::=<VERB>[-<MODIFIER>[-<MODIFIER>]]
l <VERB>
The semantics of the verb are to identify the action to be taken at the NE as a result of
receiving a TL1 message from an OS (for example, ENT, ED, or RTRV).
l <MODIFIER>
Command code modifiers are optional depending upon the specific command and the
application domain. In normal TL1 command usage, the first modifier identifies the object
of the verb where the action is to be applied in the NE. The second modifier further modifies
the object of the verb and may have diverse interpretations in various operation domains.
l <TID>
The target identifier (TID) is a unique name given to each system when it is installed. The
name identifies the particular NE. to which each command is directed. Each TID can have
a maximum of 20 ASCII characters limited to letters, digits, and hyphens, but each TID
must start with an alphabetic character. The presence of the TID is required in all input
commands, but this parameter can be entered with nothing. In this case, the parameter is
represented by two consecutive colons (::). This parameter can be entered with nothing
when the operating system directly communicates with the target NE. The recommended
value for the TID, when it is used, is the common language equipment identification (CLEI)
code of the target NE.
l <AID(s)>
The access identifier (AID) is an access code used to identify and address specific objects
within the system. Typical examples of objects addressed in the AID parameter value are:
individual pieces of equipment, transport spans, and access tributaries
l <CTAG>
The correlation tag (CTAG) is a unique identifier given to each input command by the
operator. When the system responds to a specific command, it includes the command's
CTAG in the reply. The CTAG is included in the system's reply to a specific command.
l [GB]
The general block (GB) includes support parameters whose values affect the way in which
the input command is to be executed in the system. The presence of the GB in all input
commands is a requirement, but this parameter can be entered with nothing. In this case,
the parameter is represented by two consecutive colons (::).
l The general block may be in a format like <parameter=value>. The value may take value1/
value2/value3. This means that value can be value1, value2 or value3.
Message Payload
The remaining part of a TL1 input command is the payload or subject matter of the message.
This section of the message may consist of zero or several data blocks.
The data items within a data block may either be name-defined (of the form
<KEY_WORD>=<VALUE>) or position-defined where the values are specified and the
keyword is implied by its position in the data block. All of the data items must be of the same
type within a given data block. The semantics of the data items are operation domain-specific
and vary with the operation to be performed as a result of the input message.
A.1.2 Acknowledgments
An acknowledgment is a brief output message generated in response to an input command
message.
An acknowledgment is usually followed by an output response message to the command.
However, in some circumstances, an acknowledgment is the only output message triggered by
a command.
Acknowledgments follow the 2-second rule (that is, an acknowledgement is displayed if an
output response message cannot be transmitted within 2 seconds of its receipt).
The following is the format of an acknowledgment:
<ACKNOWLEDGMENT CODE>^<CTAG><cr><lf>
The <ACKNOWLEDGMENT CODE> identifies the reason for the acknowledgment. The
<CTAG> identifies the associated input command. The less than (<) character is the
acknowledgment terminator. The valid values for acknowledgment codes and their meanings
are given in the following subsections.
No Acknowledgment (NA)
Under abnormal conditions, NA should be sent when a command has been accepted but control
of the processing has been lost, making correct acknowledgment impossible. Initiation or
execution of the requested command is uncertain.
This acknowledgment should be used only in dire circumstances since the state of execution
status is unknown.
This acknowledgment can also be used to respond to a command that is garbled during
transmission. If the CTAG value of the command could not be determined, the single character
zero (0) should be used as the acknowledgment CTAG value.
No Good (NG)
The command is valid, but the requested action conflicts with current system or equipment status
(an attempt to restore an in-service unit for example). Repeat Later (RL) is displayed in scenarios
with inadequate system resources.
This acknowledgment is seldom used because specific error codes in output response messages
can be employed to signify the same information. However, it can be used if desired.
General Format
The general structure of a TL1 output response message is as follows:
l <HEADER>
It represents information common to all output response messages; that is, it is independent
of the type of output response.
l <RESPONSE IDENTIFICATION>
It identifies the type of output response message. Five types of output response messages
are defined in this document.
l <TEXT BLOCK>
It represents information specific to the particular output response message. This
component is optional.
l <TERMINATOR>
It indicates the termination or continuation of the output response message.
Header
The form of the header is as follows:
<cr><lf><lf>^^^<SID>^<YEAR>-<MONTH>-<DAY>^<HOUR>:<MINUTE>:<SECOND>
l <SID>
The source identifier (SID) is restricted to 20 characters maximum and identifies the NE
generating the message.
The <SID> value is checked by the NE against the TID parameter of the input command
to verify that the NE's SID matches the command's intended target (that is, TID).
l <YEAR>-<MONTH>-<DAY>
The <YEAR>-<MONTH>-<DAY> construct generally represents the day on which the
command is executed.
l <HOUR>:<MINUTE>:<SECOND>
The <HOUR>:<MINUTE>:<SECOND> construct generally represents the time when the
command is executed.
Response Identification
The form of the response identification is as follows:
<cr><lf>M^^<CTAG>^<COMPLETION CODE>
The character M signifies that the message is the response to an input command message.
The output response message will have the same <CTAG> value as the corresponding input
command message for enabling the OS to associate the received output response message with
a previously-sent command.
The <COMPLETION CODE> will be displayed as COMPLD, DENY, PRTL, DELAY, or
RTRV. The semantics of the completion codes are listed in the following table.
Completion
code Description
Completion
code Description
RTRVa Represents output response of an input retrieve command (that is, with
command verb RTRV) that retrieves extensive amounts of information
from the NE and thus causes lengthy processing in the NE for gathering
all the requested information. For effective operation, the NE may start
returning available information to the OS even before all the requested
information is gathered. The RTRV completion code may be used.
Multiple responses with RTRV completion codes are permitted for the
same RTRV command, but the final response must have a COMPLD
completion code.
Notes:
a: The use of this completion code depends on the application domain.
When the CTAG of an input command cannot be identified (for example, during dial-up
asynchronous connections with noise and errors prevalent), there are two possible results:
l The 2-letter acknowledgment NA is returned.
l A DENY response and error message with CTAG set to the single character zero (0) is
returned.
Text Block
The form of the text block is:
((<cr><lf>^^^<UNQUOTED LINE>)|(<cr><lf>^^^"<QUOTED LINE>")| (<cr><lf>^^^/
*<COMMENT>*/))*
l <UNQUOTED LINE>
The <UNQUOTED LINE> consists of name- or position-defined parameters. The
unquoted line is for representing error codes in some response messages. The error code is
specified by four characters that may contain numerals after the first character, if
appropriate.
l <QUOTED LINE>
The <QUOTED LINE> consists of parsable text and is preceded and followed by quotation
marks (''). The syntax of the parsable text is equivalent to that of an input command message.
l <COMMENT>
The <COMMENT> component is used to allow free format text (that is, human readable,
not machine parsable). The free form text is preceded and followed by a forward slash and
asterisk (/*).
Terminitor
The form of the terminator is:
<cr><lf>(;|>)
The semicolon (;) character is used to indicate the termination of the output response message.
The greater than (>) character is used to indicate that more output associated with this response
will follow under another header.
Output messages cannot exceed 4096 bytes.
General Format
The following is the general structure of a TL1 autonomous message:
<HEADER><AUTO ID>[<TEXT BLOCK>]<TERMINATOR>
l <HEADER>
The <HEADER> represents information common to all output response and autonomous
messages.
l <AUTO ID>
The <AUTO ID> identifies the severity and the nature of the autonomous message. The
severity is indicated through the use of an alarm code, which will be discussed in further
details.
l <TEXT BLOCK>
The <TEXT BLOCK> represents information specific to the particular autonomous
message. This entry is optional and will be discussed in further details.
l <TERMINATOR>
The <TERMINATOR> indicates the completion or continuation of the autonomous
message. This entry is required in all types of TL1 messages.
Header
The <HEADER> is the standard response header that is defined in A.1.3 Output Response
Messages. It contains system identifier SID, date and time stamps. The header is a required entry
in all TL1 output response and autonomous messages. For a more detailed explanation of its
parameters and syntax, see Header.
*C Critical alarm
** Major alarm
*^ Minor alarm
A^ Non-alarm message
Critical, major, and minor correspond to the reporting of alarmed events. The non-alarm
message designation is used when the NE is reporting non-alarmed events, periodic
measurements, or results of previously scheduled diagnostics or audits.
The value of the most severe alarm will be reported in scenarios with multiple alarms.
l Autonomously Generated Correlation Tag (ATAG)
<ATAG> is a decimal number made up of an integer part and an optional fractional
component. The <ATAG> serves two purposes.
– It allows an OS to determine if it has failed to receive any spontaneous outputs by
checking for omissions in the sequence of messages received.
– It allows an OS to correlate spontaneous outputs triggered by a common problem. (To
accomplish this, the NE involved must be capable of recognizing and categorizing
common problems.)
l Verb and Modifier
The <VERB>[^<MODIFIER>[^<MODIFIER>]] entry identifies the nature of the
spontaneous output and allows for quick identification of the semantics of the information
in the text block.
The <VERB> is the autonomous message verb and is a required entry. In most cases, the
verb in an autonomous message will be REPT (Report). The autonomous message verb
can have up to two optional <MODIFIER>s. The first modifier is used to modify the verb.
The second modifier is used to specify the object generating the message.
Text Block
The optional <TEXT BLOCK> is used to represent information specific to the particular
autonomous message. The format of the text block is as follows:
((<cr><lf>^^^<UNQUOTED LINE>)|(<cr><lf>^^^<QUOTED LINE>)| (<cr><lf>^^^<COMMENT>))+
Terminator
The form of the <TERMINATOR> block is as follows:
<cr><lf>(;|>)
It is required as the termination block for all TL1 message types. The semicolon (;) is used to
indicate the termination of the output response message. The greater than sign (>) is used to
indicate that more output associated with this response will follow under another header.
A.2 Configuring NE
This section lists the commands used to edit and retrieve system configurations.
A.2.1 ED-DAT
Sets the time and date.
Function
This command sets the time and date of an NE.
Usage Note
The <TMZONE> setting will not take effect if the time zone parameter is disabled.
Category
System
Security
Maintenance
Command Syntax
ED-DAT:[<TID>]::<CTAG>::[<DATE>],[<TIME>],[<TMZONE>],[<DSTIME>];
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
<TMZONE> Indicates the time zone. The valid values are Eastern, NA
Central, Mountain, Pacific, Alaska, Hawaii, Samoa and
UTC (also including general time zones GMT-n and GMT
+n).
Response Syntax
<cr><lf><lf>
^^^<SID>^<DATE>^<TIME><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^<cr><lf>
;
Response Parameters
None
Example
l Command
ED-DAT:::100::2002-08-26,13-23-45,Eastern,N;
l Response Message
NE 2004-04-09 17:31:00
M 100 COMPLD
;
Related Commands
A.2.2 RTRV-DAT
A.2.2 RTRV-DAT
Retrieves the time and date.
Function
This command retrieves the time and date parameters of an NE.
Usage Note
None
Category
System
Security
Retrieve
Command Syntax
RTRV-DAT:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<DATE>,<TIME>,<TMZONE>,<DSTIME>"<cr><lf>
;
Response Parameters
Parameter Description
<TMZONE> Indicates the time zone. The valid values are Eastern, Central, Mountain,
Pacific, Alaska, Hawaii, Samoa, and UTC (also including general time
zones GMT-n and GMT+n).
NOTE
When <TIMEZONE> is set to UTC, the value of this parameter is displayed as
NON_TZ instead of UTC in the response message.
<DSTIME> Indicates whether DST is enabled. The valid values are Y and N.
Example
l Command
RTRV-DAT:::100;
l Response Message
NE 2004-04-09 17:31:04
M 100 COMPLD
"2004-04-09,17-31-04,PACIFIC,N"
;
Related Commands
A.2.1 ED-DAT
A.2.3 ED-DST
Sets DST.
Function
This command instructs an NE to set DST.
Usage Note
None
Category
MON
Security
Provisioning
Command Syntax
ED-DST:
[<TID>]::<CTAG>::<FLAG>,<ADJMODE>,<ADJWAY
>,<ADJMINUTE>,<STARTMONTH>,<STARTDAY>,<STARTWEEKDAY>,<STARTHOU
R>,<STARTMINUTE>,<ENDMONTH>,<ENDDAY>,<ENDWEEKDAY>,<ENDHOUR>,<
ENDMINUTE>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-DST:::1::enable,BYWEEK,FORWARD, 60, apr, 1, tue, 13, 0, oct, 3, tue, 14, 0;
l Response Message
NE 2005-03-21 09:33:54
M 100 COMPLD
;
Related Commands
A.2.4 RTRV-DST
A.2.4 RTRV-DST
Retrieves the DST settings on an NE.
Function
This command retrieves the DST setting on the NE.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-DST:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"FLAG=<FLAG>,ADJMODE=<ADJMODE>,ADJWAY=<ADJWAY>,ADJ_MINUTE=<ADJMINUTE>,START_MON
TH=<STARTMONTH>,START_DAY=<STARTDAY>,START_WEEKDAY=<STARTWEEKDAY>,START_HOUR=<STAR
THOUR>,START_MINUTE=<STARTMINUTE>,END_MONTH=<ENDMONTH>,END_DAY=<ENDDAY>,END_WEEKDA
Y=<ENDWEEKDAY>,END_HOUR=<ENDHOUR>,<END_MINUTE>=<ENDMINUTE>,DST_STATUS=<DSTSTATUS>"
<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-DST:::100;
l Response Message
NE 2006-05-19 12:12:52
M 100 COMPLD
"FLAG=ENABLE,ADJMODE=BYWEEK,ADJWAY=FORWARD,ADJ_MINUTE=60,START_MONTH=APR,START_DAY
=1,START_WEEKDAY=TUE,START_HOUR=13,START_MINUTE=0,END_MONTH=OCT,END_DAY=3,END_WEEK
DAY=TUE,END_HOUR=14,END_MINUTE=0,DST_STATUS=TRUE"
;
Related Commands
A.2.3 ED-DST
A.2.5 ED-SYS
Edits the attributes of the system.
Function
This command edits the attributes of the system.
Usage Note
None
Category
System
Security
Super
Command Syntax
ED-SYS:[<TID>]::<CTAG>:::[CC=<CC>,][NSC=<NSC>,][OPERSPEC=<OPERSPEC>,]
[BUZZER=<BUZZER>,][AUTOP=<AUTOP>,][PWRMODE=<PWRMODE>,]
[NELOCATION=<NELOCATION>,][NEMEMO=<NEMEMO>,]
[STATELEVEL=<STATELEVEL>,][LPBKAUTORLS=<LPBKAUTORLS>,]
[LPBKTIME=<LPBKTIME>,][IPAAUTOENTIME=<IPAAUTOENTIME>,]
[NODEID=<NODEID>,][ASON=<ASON>];
Command Parameters
Default
Parameter Description Value
<CC> Indicates the country code. The valid value is a three- USA
character ISO 3166 Geographic/Political Country Code (G/
PCC). The code for the United States is "USA" in
uppercase.
The field is used for fault type and fault location (FTFL).
<BUZZER> Indicates whether the buzzer of the NE is turned on. The OFF
valid values are ON and OFF.
Default
Parameter Description Value
<PWRMODE> Indicates the power consumption mode. The valid values NORMAL
are as follows:
l NORMAL: indicates that the NE is in normal running
mode.
l SAVING: indicates that the NE is in energy
conservation mode.
l ENHSAV: indicates that the NE is in enhanced energy
conservation mode.
NOTE
Certain hardware units on the standby cross-connect cards are shut
down in ENHSAV mode. Hence, the faults on the hardware units
cannot be detected.
<STATELEVE Indicates the state level. The valid values are FULL (full FULL
L> state model) and COMPLEX (complex state model). For
details, see A.32.3.19 STATELEVEL.
<LPBKTIME> Indicates the time taken for the loopback to be released 00-05
automatically. It is valid only when the auto-release
loopback function (<LPBKAUTORLS>) is enabled.
The valid format is HH-MM; where: HH ranges from 00
to 48 and MM ranges from 00 to 59. That is, LPBKTIME
ranges from 00-01 to 48-00.
<IPAAUTOEN Indicates the interval for automatically enabling the IPA 01-00
TIME> function. The IPA function is used to control lasers. To
avoid personal injuries caused by lasers, the NE
automatically enables the IPA function after the IPA
function is disabled for a maximum of one hour (01-00).
The valid format is HH-MM; where: HH ranges from 00
to 01 and MM ranges from 00 to 59.
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-SYS:::C:::AUTOP=Y, NELOCATION="NEW YORK",NEMEMO="North-east 4BLSR
ring",STATELEVEL=COMPLEX,LPBKAUTORLS=ENABLE,LPBKTIME=00-06,NODEID=1.1.1.2,ASON=DIS
ABLE;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.2.6 RTRV-SYS
A.2.6 RTRV-SYS
Retrieves the attributes of the system.
Function
This command retrieves the attributes of the system.
Usage Note
None
Category
System
Security
Retrieve
Command Syntax
RTRV-SYS:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"DEVICETYPE=<DEVICETYPE>,SHELFTYPE=<SHELFTYPE>,NEVERSION=<NEVERSION>,CC=<CC>,NS
C=<NSC>,OPERSPEC=<OPERSPEC>,BUZZER=<BUZZER>,AUTOP=<AUTOP>,NELOCATION=<NELOCATION>,
NEMEMO=<NEMEMO>,STATELEVEL=<STATELEVEL>,LPBKAUTORLS=<LPBKAUTORLS>,
[LPBKTIME=<LPBKTIME>],IPAAUTOENTIME=<IPAAUTOENTIME>,PWRMODE=<PWRMODE>,RATEDPWR=<RA
TEDPWR>,ACTPWR=<ACTPWR>,SAVEDPWR=<SAVEDPWR>,[NODEID=<NODEID>],
[ASON=<ASON>],OLSEN=<OLSEN>"<cr><lf>
;
Response Parameters
Parameter Description
<DEVICETYPE> Indicates the device type. The valid values are OSN3800A,
OSN6800A, OSN8800T16, OSN8800T32, and OSN8800T64.
<SHELFTYPE> Indicates the shelf type. The valid values are STDSHELF and
NASHELF.
<NEVERSION> Indicates the NE software and patch package version. The valid value
is a 40-byte string, for example, V100R006C00.
<CC> Indicates the country code. The valid value is a three-character ISO
3166 Geographic/Political Country Code (G/PCC). The code for the
United States is "USA" in uppercase.
The field is used for FTFL.
<NSC> Indicates an ITU carrier code (ICC). This code consists of one to six
left-justified characters, alphabetic, or leading alphabetic with
trailing numeric.
The field is used for FTFL.
<OPERSPEC> Indicates the operator specific. The field is used for FTFL
<BUZZER> Indicates whether the buzzer of the NE is turned on. The valid values
are ON and OFF.
Parameter Description
<PWRMODE> Indicates the power consumption mode. The valid values are as
follows:
l NORMAL: indicates that the NE is in the normal running mode.
l SAVING: indicates that the NE is in the energy conservation
mode.
l ENHSAV: indicates that the NE is in enhanced energy
conservation mode.
<STATELEVEL> Indicates the state level. The valid values are FULL (full state model)
and COMPLEX (complex state model). For details, see A.32.3.19
STATELEVEL.
<IPAAUTOENTIME Indicates the interval for automatically enabling the IPA function.
> The IPA function is used to control lasers. To avoid personal injuries
caused by lasers, the NE automatically enables the IPA function after
the IPA function is disabled for a maximum of one hour (01-00).
The valid format is HH-MM; where: HH ranges from 00 to 01 and
MM ranges from 00 to 59.
<NODEID> Indicates the node ID of the node, for example, 1.1.1.1. If this
parameter is set after the ASON feature is enabled, the NE is
automatically reset.
<ASON> Indicates whether ASON is enabled. The valid values are ENABLE
and DISABLE.
Parameter Description
Example
l Command
RTRV-SYS:::C;
l Response Message
NE 2008-11-11 20:37:10
M C COMPLD
"DEVICETYPE=OSN6800A,SHELFTYPE=NASHELF,NEVERSION=UNKNOWN,CC=,NSC=\"\",OPERSPEC=
\"\",BUZZER=OFF,AUTOP=Y,NELOCATION=\"\",NEMEMO=
\"\",STATELEVEL=FULL,LPBKAUTORLS=DISABLE,LPBKTIME=00-05,IPAAUTOENTIME=01-00,PWRMOD
E=NORMAL,RATEDPWR=161,ACTPWR=161,SAVEDPWR=0,NODEID=1.1.68.23,ASON=DISABLE,OLSEN=N"
"
;
Related Commands
A.2.5 ED-SYS
A.2.7 RTRV-HDR
Retrieves the header information.
Function
This command requests an NE to reply with a normal response indicating COMPLD and header
information, that is, the source identifier, the date, and the time.
Usage Note
None
Category
System
Security
Retrieve
Command Syntax
RTRV-HDR:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
RTRV-HDR:::100;
l Response Message
NE 2004-07-08 16:01:36
M 100 COMPLD
;
Related Commands
None
A.2.8 RTRV-HEALTH-STATE
Retrieves the status of an NE for software loading.
Function
This command is issued upon the user's request. MON sends a health check request to all the
registered modules (with MON health check framework), then collects the responses from those
modules and displays the information to the user.
Usage Note
None
Category
System
Security
Maintenance
Command Syntax
RTRV-HEALTH-STATE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"CONTENT=GCP Contrl Plane State,HEALTH_STATUS=POK,RESULT=ION is stopped or
initializing now!,ADVICE=Please wait and then try again!"<cr><lf>
;
Response Parameters
Parameter Description
<HEALTH_ Indicates the status of the NE. The valid values are as follows:
STATUS> l OK: indicates the normal state of the specific function.
l POK: indicates the state that may affect software loading.
l NG: indicates the abnormal state of the specific function.
<ADVICE> Indicates an advisement that can be applied to clear the fault in situations of
the abnormal status of a specific function.
Example
l Command
RTRV-HEALTH-STATE:::100;
l Response Message
NE 2008-07-19 15:59:52
M 100 COMPLD
"CONTENT=Channel State,HEALTH_STATUS=OK,RESULT=The Channel state is
OK!,ADVICE="
"CONTENT=Master And Slave
State,HEALTH_STATUS=POK,RESULT=Unknown,ADVICE=Unknown"
;
Related Commands
None
A.2.9 RTRV-LOCALIZATION
Retrieves the status of time localization.
Function
This command retrieves the status of time localization.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-LOCALIZATION:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<LOCALIZATION_STATUS> "<cr><lf>
;
Response Parameters
Parameter Description
LOCALIZATION_ Indicates the status of time localization. The valid values are as
STATUS follows:
l 0: indicates that time localization is disabled.
l 1: indicates that time radicalization is enabled (starting year: 1990).
l 2: indicates that time radicalization is enabled (starting year: 1970).
Example
l Command
RTRV-LOCALIZATION:::1;
l Response Message
NE 2007-09-19 11:17:54
M 1 COMPLD
"1"
;
Related Commands
None
A.2.10 RTRV-NETYPE
Retrieves the NE type.
Function
This command retrieves the type of an NE.
Usage Note
None
Category
Equipment
Security
Retrieve
Command Syntax
RTRV-NETYPE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<VENDID>,<DEVICETYPE>,<EQUIPTYPE>,<NEVERSION>"
;
Response Parameters
Parameter Description
<VENDID> Indicates the vendor identifier of the equipment. The valid value is
a string.
<DEVICETYPE> Indicates the device type. The valid values are OSN6800A,
OSN3800A, OSN8800T16, OSN8800T32, and OSN8800T64.
<EQUIPTYPE> Indicates the equipment type. It is a 40-byte string. The valid values
are as follows:
l ADM: indicates an add/drop multiplexer.
l MSPP: indicates a multi-service provisioning platform.
<NEVERSION> Indicates the software release version of the NE. It is a 40-byte string.
Example
l Command
RTRV-NETYPE:::C;
l Response Message
NE 2008-07-10 16:13:16
M C COMPLD
"HUAWEI,OSN8800T32,ADM&MSPP,8800V100R002C00"
;
Related Commands
None
A.2.11 RTRV-TOD
Retrieves the time of day.
Function
This command retrieves the system date and time at the instant when the command was executed.
The time is returned in coordinated universal time (UTC).
Usage Note
None
Category
System
Security
Retrieve
Command Syntax
RTRV-TOD:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<YEAR>,<MONTH>,<DAY>,<HOUR>,<MINUTE>,<SECOND>,<TMTYPE>"<cr><lf>
;
Response Parameters
Parameter Description
<YEAR> Indicates the current calendar year that ranges from 1990 to 2087.
<MONTH> Indicates the month of the year. The valid values are 01, 02, 03, 04, 05, 06,
07, 08, 09, 10, 11, and 12.
Parameter Description
<DAY> Indicates the day of the month, which ranges from 01 to 31.
<HOUR> Indicates the hour of the day, which ranges from 00 to 23.
<MINUTE> Indicates the minute of the hour, which ranges from 00 to 59.
<SECOND> Indicates the second of the minute, which ranges from 00 to 59.
<TMTYPE> Indicates the type of the time value returned. The value of this parameter is
always in UTC.
Example
l Command
RTRV-TOD:::100;
l Response Message
NE 2003-02-28 12:23:20
M 1000 COMPLD
"2003,02,23,12,23,20,UTC"
;
Related Commands
A.2.1 ED-DAT
A.2.2 RTRV-DAT
A.2.12 SET-SID
Sets the system identification.
Function
This command changes the system identification (SID) code to a specified value. Where
appropriate, the value of this SID code is used as the target identifier in an input command and
the source identifier in an output or autonomous message.
Usage Note
None
Category
System
Security
Maintenance
Command Syntax
SET-SID:[<TID>]::<CTAG>::<SID>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
SET-SID:::100::NE;
l Response Message
NE 2004-07-08 16:02:46
M 100 COMPLD
;
Related Commands
None
A.3.1 ED-<GCC/DCC>
Edits GCC/DCC parameters
Function
This command edits the attributes, state, and link protocol types of a GCC/DCC channel.
Usage Note
None
Category
Communication
Security
Provisioning
Command Syntax
ED-<GCC/DCC>:[<TID>]:[<AID>]:<CTAG>:::[NEGO=<NEGO>],[TYPE=<TYPE>],
[RATEMODE=<RATEMODE>],[BIND=<BIND>],[PROTOCOL=<PROTYPE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-GCC::FAC-1-2-1-1:C:::PROTOCOL=TRANSPARENT;
l Response Message
NE 2004-07-08 17:18:06
M C COMPLD
;
Related Commands
A.3.2 RTRV-<GCC/DCC>
A.3.2 RTRV-<GCC/DCC>
Retrieves the GCC/DCC channel parameters.
Function
This command retrieves the GCC/DCC attributes and its protocol type.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-<GCC/DCC>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<AID>:[NEGO=<NEGO>],TYPE=<TYPE>,
[RATEMODE=<RATEMODE>],BIND=<BIND>,PROTOCOL=<PROTYPE>,BANDWIDTH=<BANDWIDTH>,CHANSTA
TE=<CHANSTATE>", "<cr><lf>
Response Parameters
Parameter Description
<AID> The access identifier which indicates the GCC/DCC channel. The
valid formats are as follows:
l For DCC: DCC-<SHELF ID>-<SLOT ID>-<PORT ID>-
<CHANNEL ID>
l For GCC: FAC/CLNT/SRVN-<SHELF ID>-<SLOT ID>-
<PORT ID>-<CHANNEL ID>
DCC is valid for SONET/OSC. The valid values of <CHANNEL ID>
are:
l 1: (SDCC, DCC1-DCC3)
l 2: (LDCC, DCC4-DCC12)
l 3: (ETHA, Ethernet channel A)
l 4: (ETHB, Ethernet channel B)
GCC is valid for OTN. The valid values of <CHANNEL ID> are:
l 1: (GCC0)
l 2: (GCC1-GCC2)
l 3: (RESA)
<TYPE> Indicates the communication type that the channel supports. The
valid values are as follows:
l MANAGE: indicates the management channel, which is used for
the communication of management.
l ASON: indicates the ASON channel, which is used for the
communication of ASON services.
<RATEMODE> Indicates the rate mode. This parameter is only valid for GCC channel
3 of certain ports with a rate of ODU2 or higher. The channel mainly
supports ASON services. The valid values are as follows:
l 9: 9-byte mode with an actual rate of 9 x 64 kbit/s.
l 24: 24-byte mode with an actual rate of 24 x 64 kbit/s.
Parameter Description
<PROTOCOL> Indicates the protocol of the DCC/GCC link layer. The valid values
are as follows:
l TRANSPARENT : There are not any link protocols, and the
channel is free in CRS.
l PPP: IP stack is set in this channel.
<CHANSTATE> Indicates the data sending and receiving state of the CPU channel
which is assigned to the optical interface. The valid values are as
follows:
l OK: The sending and receiving states are okay.
l RX_F: The sending state is okay, but the receiving fails.
l TX_F: The receiving state is okay, but the sending fails.
l RX_F&TX_F: All fail.
Example
l Command
RTRV-DCC::DCC-1-6-2-1:C;
l Response Message
NE 2005-08-10 16:12:51
M C COMPLD
"DCC-1-6-2-1:TYPE=MANAGE,BIND=Y,PROTOCOL=PPP,BANDWIDTH=3*64K,CHANSTATE=OK"
;
Related Commands
A.3.1 ED-<GCC/DCC>
A.3.3 RTRV-DETAIL-<GCC/DCC>
Retrieves the GCC/DCC channel parameters.
Function
This command retrieves the GCC/DCC attributes and its protocol type.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-DETAIL-<GCC/DCC>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<AID>:[NEGO=<NEGO>],TYPE=<TYPE>,
[RATEMODE=<RATEMODE>],BIND=<BIND>,PROTOCOL=<PROTYPE>,BANDWIDTH=<BANDWIDTH>,CHANSTA
TE=<CHANSTATE>,CHANID=<CHANID>", "<cr><lf>
Response Parameters
Parameter Description
<AID> The access identifier which indicates the GCC/DCC channel. The
valid formats are as follows:
l For DCC: DCC-<SHELF ID>-<SLOT ID>-<PORT ID>-
<CHANNEL ID>
l For GCC: FAC/CLNT/SRVN-<SHELF ID>-<SLOT ID>-
<PORT ID>-<CHANNEL ID>
DCC is valid for SONET/OSC. The valid values of <CHANNEL ID>
are:
l 1: (SDCC, DCC1-DCC3)
l 2: (LDCC, DCC4-DCC12)
l 3: (ETHA, Ethernet channel A)
l 4: (ETHB, Ethernet channel B)
GCC is valid for OTN. The valid values of <CHANNEL ID> are:
l 1: (GCC0)
l 2: (GCC1-GCC2)
l 3: (RESA)
<TYPE> Indicates the communication type that the channel supports. The
valid values are as follows:
l MANAGE: indicates the management channel, which is used for
the communication of management.
l ASON: indicates the ASON channel, which is used for the
communication of ASON services.
<RATEMODE> Indicates the rate mode. This parameter is only valid for GCC channel
3 of certain ports with a rate of ODU2 or higher. The channel mainly
supports ASON services. The valid values are as follows:
l 9: 9-byte mode with an actual rate of 9 x 64 kbit/s.
l 24: 24-byte mode with an actual rate of 24 x 64 kbit/s.
Parameter Description
<PROTOCOL> Indicates the protocol of the DCC/GCC link layer. The valid values
are as follows:
l TRANSPARENT : There are not any link protocols, and the
channel is free in CRS.
l PPP: IP stack is set in this channel.
<CHANSTATE> Indicates the data sending and receiving state of the CPU channel
which is assigned to the optical interface. The valid values are as
follows:
l OK: The sending and receiving states are okay.
l RX_F: The sending state is okay, but the receiving fails.
l TX_F: The receiving state is okay, but the sending fails.
l RX_F&TX_F: All fail.
Example
l Command
RTRV-DETAIL-GCC::SRV3-1-13-2-3:A;
l Response Message
NE-91-5 2012-04-15 00:49:27
M A COMPLD
"SRV3-1-13-2-3:NEGO=N,TYPE=ASON,RATEMODE=9,BIND=Y,PROTOCOL=PPP,BANDWIDTH=9*64K,CHA
NSTATE=RX_F,CHANID=27"
;
Related Commands
A.3.2 RTRV-<GCC/DCC>
A.3.4 RTRV-DCC-CHANERR
Retrieves the channel error info of the GCC/DCC channel.
Function
This command instructs an NE to retrieve the channel error info of the GCC/DCC channel.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-DCC-CHANERR:[<TID>]::<CTAG>:::CHANID=<CHANID>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"QFULL=<QFULL>,LG=<LG>,NO=<NO>,CR=<CR>,AB=<AB>,UN=<UN>,MRF=<MRF>,RXF=<RXF>,TXB=
<TXB>,RXERR=<RXERR>,TXERR=<TXERR>", "<cr><lf>
;
Response Parameters
Parameter Description
<QFULL> Indicates the number of times when the GCC/DCC channel's packet
sending queue is full.
<LG> Indicates the number of packets whose length exceed the maximum
packet length the NE can process.
<NO> Indicates the number of packets whose bits length is not multiple of
8.
<UN> Indicates the number of packets which have receive Overrun errors.
Parameter Description
<MRF> Indicates the number of packets which have Maximum receive frame
length violation errors.
<RXERR> Indicates the number of packets which are received with errors.
<TXERR> Indicates the number of packets which are sended with errors.
Example
l Command
RTRV-DCC-CHANERR:::a:::CHANID=27;
l Response Message
NE-91-5 2012-04-15 03:30:24
M A COMPLD
"QFULL=0,LG=0,NO=0,CR=0,AB=0,UN=0,MRF=0,RXF=0,TXB=66,RXERR=0,TXERR=0"
;
Related Commands
A.3.3 RTRV-DETAIL-<GCC/DCC>
A.3.5 RTRV-DCC-CHANINFO
Retrieves the channel info of the GCC/DCC channel.
Function
This command instructs an NE to retrieve the channel info of the GCC/DCC channel.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-DCC-CHANINFO:[<TID>]::<CTAG>:::CHANID=<CHANID>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"CHANID=<CHANID>,STATE=<STATE>,EVENT=<EVENT>,PEER_CHANID=<PEER_CHANID>,TRNS_NUM
S=<TRNS_NUMS>,TRNS_BYTES=<TRNS_BYTES>,RECV_NUMS=<RECV_NUMS>,RECV_BYTES=<RECV_BYTES
>,RX_SR=<RX_SR>,TX_SR=<TX_SR>,LAST_STATE=<LAST_STATE>", "<cr><lf>
;
Response Parameters
Parameter Description
<TRNS_NUMS> Indicates the number of packets sended from the GCC/DCC channel.
<TRNS_BYTES> Indicates the number of bytes sended from the GCC/DCC channel.
<RECV_BYTES> Indicates the number of bytes received from the GCC/DCC channel.
<RX_SR> Indicates the number of packets which are received with errors.
<TX_SR> Indicates the number of packets which are sended with errors.
Example
l Command
RTRV-DCC-CHANINFO:::a:::CHANID=27;
l Response Message
NE-91-5 2012-04-15 04:02:04
M A COMPLD
"CHANID=27,STATE=0,EVENT=0,PEER_CHANID=0,TRNS_NUMS=222,TRNS_BYTES=3996,RECV_NUMS=0
,RECV_BYTES=0,RX_SR=0,TX_SR=0,LAST_STATE=0"
;
Related Commands
A.3.3 RTRV-DETAIL-<GCC/DCC>
A.3.6 DLT-CRS-OHBYTE
Deletes cross overhead bytes.
Function
This command deletes cross overhead bytes.
Usage Note
None
Category
Communication
Security
Provisioning
Command Syntax
DLT-CRS-OHBYTE:[<TID>]:<FROM_AID>:<CTAG>::<FROM_BYTE>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-CRS-OHBYTE::FAC-1-2-1:10::E1;
l Response Message
NE 2004-07-10 15:35:00
M 10 COMPLD
;
Related Commands
A.3.7 ENT-CRS-OHBYTE
A.3.8 RTRV-CRS-OHBYTE
A.3.7 ENT-CRS-OHBYTE
Creates cross overhead bytes.
Function
This command creates cross overhead bytes.
Usage Note
None
Category
Communication
Security
Provisioning
Command Syntax
ENT-CRS-OHBYTE:[<TID>]:<FROM_AID>, <TO_AID>:<CTAG>::<FROM_BYTE>,
<TO_BYTE>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Example
l Command
ENT-CRS-OHBYTE::FAC-1-2-1,FAC-1-6-1:10::D1,D1;
l Response Message
NE 2004-07-10 15:33:17
M 10 COMPLD
;
Related Commands
A.3.8 RTRV-CRS-OHBYTE
A.3.6 DLT-CRS-OHBYTE
A.3.8 RTRV-CRS-OHBYTE
Retrieves the information about cross overhead bytes.
Function
This command retrieves the information about cross overhead bytes.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-CRS-OHBYTE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<FROM_AID>,<TO_AID>,<FROM_BYTE>,<TO_BYTE>"<cr><lf>
;
Response Parameters
Parameter Description
<FROM_BYTE> Indicates the source byte of the cross. Overhead bytes include
D1-D12, E1, E2 and F1.
<TO_BYTE> The destination byte of the cross. Overhead bytes include D1-
D12, E1, E2 and F1.
Example
l Command
RTRV-CRS-OHBYTE:::100;
l Response Message
NE 2004-07-10 15:36:49
M 100 COMPLD
"FAC-1-2-1,FAC-1-6-1,D1,D1"
;
Related Commands
A.3.7 ENT-CRS-OHBYTE
A.3.6 DLT-CRS-OHBYTE
A.3.9 ED-VACANTSLOT
Sets the DCC/GCC channel allocation trigger status for all vacant slots on the current NE to
enable or disable.
Function
This command sets the DCC/GCC channel allocation trigger status for all vacant slots on the
current NE to enable or disable.
Usage Note
None
Category
Communication
Security
Provisioning
Command Syntax
ED-VACANTSLOT:[<TID>]::<CTAG>:::[VACANTSLOT=<VACANTSLOT>];
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-VACANTSLOT:::C:::VACANTSLOT=ENABLE;
l Response Message
NE 2008-11-11 21:32:07 M C COMPLD ;
Related Commands
A.6.9 RTRV-CLNT
A.3.10 RTRV-VACANTSLOT
Retrieves the DCC/GCC channel allocation trigger status of NE level for all vacant slots.
Function
This command retrieves the DCC/GCC channel allocation trigger status of NE level for all vacant
slots.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-VACANTSLOT:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf>
^^^VACANTSLOT=<VACANTSLOT> ;
Response Parameters
Parameters Description
<VACANTSL Indicates the DCC/GCC channel allocation trigger status. Valid values are
OT> enable and disable.
Example
l Command
RTRV-VACANTSLOT:::C;
l Response Message
NE 2005-08-10 16:12:51 M C COMPLD "VACANTSLOT=ENABLE" ;
Related Commands
A.6.8 ED-CLNT
A.4.1.1 ED-LAN
Modifies the LAN parameters.
Function
This command changes the attributes and state of a LAN facility.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ED-LAN:[<TID>]:<LAN_AID>:<CTAG>:::[IP=<IPADDR>], [MASK=<SUBNETMASK>],
[GATEWAY=<GATEWAY>], [ENABLE=<ENABLE>],[ARPPROXY=<ARPSTATE>],
[CONMODE=<CONMODE>],[SNDIP=<SndIpAddr>],[SNDMASK=<SndSubMask>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-
LAN::LAN-1:100:::IP=129.9.0.1,MASK=255.255.255.0,GATEWAY=129.9.0.1,ENABLE=Y,ARPPRO
XY=ENABLE,CONMODE=ALL,SNDIP=130.9.0.22,SNDMASK=255.255.255.0;
l Response Message
NE 2002-03-04 15:23:20
M 100 COMPLD
;
Related Commands
A.4.1.6 RTRV-LAN
A.4.1.2 DLT-ACL
Delete an ACL rule.
Function
This command is issued to delete an ACL rule.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
DLT-ACL:[<TID>]::<CTAG>::RULEID=<RULEID>
Command Parameters
Parameter Description Default
Value
<RULEID> The Index of an exist ACL rule, If the ruleid is set 4294967295, NA
that means delete all ACL rules.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
DLT-ACL:::100::RULEID=10
l Response Message
A.4.1.3 ED-ACL
Modify the ACL rule.
Function
This command is issued to modify an ACL rule.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ED-ACL:
[<TID>]::<CTAG>::RULEID=<RULEID>,OP=<OP>,SOURCE=<SOURCE>,WILDCAR
D=<WILDCARD>
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-ACL:::100::RULEID=10,OP=DENY,SOURCE=128.8.0.0,WILDCARD=0.0.255.255
l Response Message
NEW-NE 2011-05-25 20:23:32
M 100 COMPLD
;
A.4.1.4 ENT-ACL
Add the ACL rule.
Function
This command is issued to add an ACL rule.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ENT-ACL:
[<TID>]::<CTAG>::RULEID=<RULEID>,OP=<OP>,SOURCE=<SOURCE>,WILDCAR
D=<WILDCARD>
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-ACL:::100::RULEID=10,OP=DENY,SOURCE=129.9.0.0,WILDCARD=0.0.255.255
l Response Message
NEW-NE 2011-05-25 20:23:32
M 100 COMPLD
;
A.4.1.5 RTRV-ACL
Retrieves all ACL rules.
Function
This command is issued to retrieve ACL rules.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-ACL:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"RULEID=<RULEID>,OP=<OP>,SOURCE=<SOURCE>,WILDCARD=<WILDCARD>"<cr><lf>
Response Parameters
Parameter Description
Example
l Command
rtrv-acl:::100;
l Response Message
NEW-NE 2011-07-29 19:28:38
M 100 COMPLD
"RULEID=10,OP=PERMIT,SOURCE=129.8.0.0,WILDCARD=0.0.255.255"
A.4.1.6 RTRV-LAN
Retrieves the LAN parameters.
Function
This command retrieves the attributes and state of a LAN facility.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-LAN:[<TID>]:[<LAN_AID>]:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf>
^^^"IP=<IPADDR><cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"IP=<IPADDR>,MASK=<SUBNETMASK>,GATEWAY=<GATEWAY>,MAC=<MAC>,ENABLE=<ENABLE>,ARPP
ROXY=<ARPSTATE>,CONMODE=<CONMODE>,SNDIP=<DCNIPADDR>,SNDMASK=<DCNSUBNETMASK>"<cr><l
f>
;
Response Parameters
Parameter Description
<CONMODE> Indicates the encryption mode. The valid values are SSL,
NOSSL, and ALL.
Example
l Command
RTRV-LAN::LAN-1:100;
l Response Message
NE 2004-07-08 17:16:08
M 10 COMPLD
"IP=129.9.0.1,MASK=255.255.0.0,GATEWAY=129.9.0.1,MAC=08-00-3e-10-00-0b,ENABLE=Y,AR
PPROXY=ENABLE,CONMODE=SSL,SNDIP=0.0.0.0,SNDMASK=0.0.0.0"
;
Related Commands
A.4.1.1 ED-LAN
A.4.1.7 ED-COM-SERVICE
Edit the service status of communication.
Function
This command is issued to open or close communication service.
Usage Note
None
Category
Communication
Security
Super
Command Syntax
ED-COM-SERVICE:[<TID>]::<CTAG>::<COMSERVICE>,<COMSRVSTATE>;
Command Parameters
Parameter Description Default
Value
<COMSRVS The state of service. The valid values are open and close. NA
TATE>
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-COM-SERVICE:::100::FTPCLIENT,OPEN;
l Response Message
NEW-NE 2012-02-07 20:23:32
M 100 COMPLD
;
Related Commands
A.4.1.8 RTRV-COM-SERVICE
A.4.1.8 RTRV-COM-SERVICE
Retrieves the information of the communication service.
Function
This command is issued to retrieve the information of the communication service.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
RTRV-COM-SERVICE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"SERVICE=<COMSERVICE>,STATE=<COMSRVSTATE>"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
Example
l Command
rtrv-com-service:::100;
l Response Message
NEW-NE 2012-02-07 19:28:38
M 100 COMPLD
"SERVICE=FTPCLIENT,STATE=OPEN"
"SERVICE=SFTPCLIENT,STATE=OPEN"
"SERVICE=TELSERVER,STATE=OPEN"
"SERVICE=STELSERVER,STATE=OPEN"
;
Related Commands
A.4.1.7 ED-COM-SERVICE
A.4.1.9 ACT-SSL-CAFILE
Activates the SSL certificate file.
Function
This command is issued to activates the SSL certificate file.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ACT-SSL-CAFILE:[<TID>]::<CTAG>;
Command Parameters
NONE
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ACT-SSL-CAFILE:::100
l Response Message
NEW-NE 2012-02-22 20:23:32
M 100 COMPLD
;
A.4.1.10 ED-SSL-MODE
Modify the SSL mode.
Function
This command is issued to modify the SSL mode.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ED-SSL-MODE:[<TID>]::<CTAG>::SSLMODE=<SSLMODE>
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-SSL-MODE:::100::SSLMODE=BOTH
l Response Message
NEW-NE 2012-02-22 20:23:32
M 100 COMPLD
;
A.4.1.11 RTRV-SSL-MODE
Retrieves the SSL mode.
Function
This command is issued to retrieve the SSL mode.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
RTRV-SSL-MODE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"SSLMODE=<SSLMODE>"<cr><lf>
Response Parameters
Parameter Description
Example
l Command
RTRV-SSL-MODE:::100;
l Response Message
NEW-NE 2012-02-22 19:28:38
M 100 COMPLD
"SSLMODE=BOTH"
A.4.1.12 ED-SSL-ENCRYPTION
Modify the encryption of the SSL private key file.
Function
This command is issued to modify the encryption of the SSL private key file.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ED-SSL-ENCRYPTION:
[<TID>]::<CTAG>::MODE=<SSLENCRYMODE>,PASSWORD=<SSLPASSWORD>
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-SSL-ENCRYPTION:::100::MODE=enable,PASSWORD="111"
l Response Message
NEW-NE 2012-02-22 20:23:32
M 100 COMPLD
;
A.4.1.13 RTRV-SSL-ENCRYPTION
Retrieves the mode of the SSL private key file.
Function
This command is issued to retrieve the encryption mode of the SSL private key file.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
RTRV-SSL-ENCRYPTION:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"MODE=<SSLENCRYMODE>"<cr><lf>
Response Parameters
Parameter Description
Example
l Command
RTRV-SSL-ENCRYPTION:::100;
l Response Message
NEW-NE 2012-02-22 19:28:38
M 100 COMPLD
"MODE=DISABLE"
A.4.1.14 ED-ADVANCED-ACL
Modify the advanced ACL rule.
Function
This command is issued to modify an advanced ACL rule.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ED-ADVANCED-ACL:
[<TID>]::<CTAG>::RULEID=<RULEID>,OP=<OP>,SOURCE=<SOURCE>,SRCWILDC
ARD=<SRCWILDCARD>,DESTINATION=<DESTINATION>,DSTWILDCARD=<DSTW
ILDCARD>,PROTOCOL=<PROTOCOLTYPE>,[SRCPORT=<SRCPORTACL>],
[DSTPORT=<DSTPORTACL>],[ICMPTYPE=<ICMPTYPE>],
[ICMPCODE=<ICMPCODE>]
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-ADVANCEL-ACL:::
100::RULEID=10,OP=DENY,SOURCE=128.9.0.0,SRCWILDCARD=0.0.255.255,DESTINATION=128.8.
0.0,DSTWILDCARD=0.0.255.255,PROTOCOL=IP;
l Response Message
NEW-NE 2012-02-22 20:23:32
M 100 COMPLD
;
A.4.1.15 ENT-ADVANCED-ACL
Add the advanced ACL rule.
Function
This command is issued to add an advanced ACL rule.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ENT-ADVANCED-ACL:
[<TID>]::<CTAG>::RULEID=<RULEID>,OP=<OP>,SOURCE=<SOURCE>,SRCWILDC
ARD=<SRCWILDCARD>,DESTINATION=<DESTINATION>,DSTWILDCARD=<DSTW
ILDCARD>,PROTOCOL=<PROTOCOLTYPE>,[SRCPORT=<SRCPORTACL>],
[DSTPORT=<DSTPORTACL>],[ICMPTYPE=<ICMPTYPE>],
[ICMPCODE=<ICMPCODE>]
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-ADVANCED-ACL:::
100::RULEID=10,OP=DENY,SOURCE=128.9.0.0,SRCWILDCARD=0.0.255.255,DESTINATION=128.8.
0.0,DSTWILDCARD=0.0.255.255,PROTOCOL=IP;
l Response Message
NEW-NE 2012-02-22 20:23:32
M 100 COMPLD
;
A.4.1.16 RTRV-ADVANCED-ACL
Retrieves all advanced ACL rules.
Function
This command is issued to retrieve advanced ACL rules.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-ADVANCED-ACL:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"RULEID=<RULEID>,OP=<OP>,SOURCE=<SOURCE>,SRCWILDCARD=<SRCWILDCARD>,DESTINATION=
<DESTINATION>,DSTWILDCARD=<DSTWILDCARD>,PROTOCOL=<PROTOCOLTYPE>,SRCPORT=<SRCPORTAC
L>,DSTPORT=<DSTPORTACL>,ICMPTYPE=<ICMPTYPE>,ICMPCODE=<ICMPCODE>"<cr><lf>
Response Parameters
Parameter Description
Example
l Command
RTRV-ADVANCED-ACL:::100;
l Response Message
NEW-NE 2012-02-22 19:28:38
M 100 COMPLD
"RULEID=10,OP=PERMIT,SOURCE=128.9.0.0,SRCWILDCARD=0.0.255.255,DESTINATION=128.8.0.
0,DSTWILDCARD=0.0.255.255,PROTOCOLTYPE=ip,SRCPORT=0xffffffff,DSTPORT=0xffffffff,IC
MPTYPE=0xff,ICMPCODE=0xff"
A.4.1.17 DLT-ADVANCED-ACL
Delete an advanced ACL rule.
Function
This command is issued to delete an advanced ACL rule.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
DLT-ADVANCED-ACL:[<TID>]::<CTAG>::RULEID=<RULEID>
Command Parameters
Parameter Description Default
Value
<RULEID> The Index of an exist advanced ACL rule, If the ruleid is set NA
4294967295, that means delete all advanced ACL rules.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
DLT-ADVANCED-ACL:::100::RULEID=10;
l Response Message
NEW-NE 2012-02-22 20:23:32
M 100 COMPLD
;
A.4.2.1 RTRV-IPIF-INFO
Retrieves information about all IP interfaces.
Function
This command retrieves information about all IP interfaces of an NE.
Usage Note
None
Category
TIPS
Security
Retrieve
Command Syntax
RTRV-IPIF-INFO:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"NAME=<INTERFACE_INFO>:INDEX=<INTERFACE_INDEX>:IP=<IP_ADDR>:MASK=<IP_MASK>:FLAG
=<IP_FLAG>:LTYPE=<LINK_TYPE>:LMTU=<LINK_MTU>"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
Example
l Command
RTRV-IPIF-INFO:::100;
l Response Message
NE 2005-03-21 09:33:54
M 100 COMPLD
"NAME=ETH1:INDEX=386:IP=129.9.0.20:MASK=255.255.0.0:FLAG=0:LTYPE=ETHERNET:LMTU=150
0",
"NAME=PPP-0-2-255-1-257-1:INDEX=518:IP=129.9.0.20:MASK=255.255.0.0:FLAG=1:LTYPE=PP
P:LMTU=960"
;
Related Commands
None
A.4.2.2 RTRV-PPPIF-COUNT
Retrieves the message count information about a PPP interface.
Function
This command retrieves the message count information about a PPP interface.
Usage Note
None
Category
TIPS
Security
Retrieve
Command Syntax
RTRV-PPPIF-COUNT:[<TID>]::<CTAG>::<INTERFACE_INDEX>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"INDEX=<INTERFACE_INDEX>:IN=<RECV_IP_NUM>:OUT=<SEND_IP_NUM> "<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-PPPIF-COUNT:::100::1;
l Response Message
NE 2005-03-21 09:33:54
M 100 COMPLD
"INDEX=1:IN=1000:OUT=1500"
Related Commands
None
A.4.2.3 RTRV-PPPIF-STATE
Retrieves the negotiation information about a PPP interface.
Function
This command retrieves the negotiation information about a PPP interface.
Usage Note
None
Category
TIPS
Security
Retrieve
Command Syntax
RTRV-PPPIF-STATE:[<TID>]::<CTAG>::<INTERFACE_INDEX>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"INDEX=<INTERFACE_INDEX>:NEGOSTATE=<NEGO_STATE>:NEGOTYPE=<NEGO_TYPE>:FSMSTATE=<
FSM_STATE> "<cr><lf>
;
Response Parameters
Parameter Description
<NEGO_TYPE> Indicates the negotiation type. The valid values are as follows:
l LCP
l NCP
Parameter Description
<FSM_STATE> Indicates the finite state machine (FSM) state. The valid
values are as follows:
l INITIAL
l STARTING
l CLOSED
l STOPPED
l CLOSING
l STOPPING
l REQSENT
l ACKRCVD
l ACKSENT
l OPENED
Example
l Command
RTRV-PPPIF-STATE:::100::1;
l Response Message
NE 2005-03-21 09:33:54
M 100 COMPLD
"INDEX=1:NEGOSTATE=ESTABLISH:NEGOTYPE=NCP:FSMSTATE=OPENED"
Related Commands
None
A.4.2.4 RTRV-ROUTE-INFO
Retrieves the information about the route table.
Function
This command retrieves the information about the route table.
Usage Note
None
Category
TIPS
Security
Retrieve
Command Syntax
RTRV-ROUTE-INFO:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"IP=<IP_ADDR>:MASK=<IP_MASK>:HOPNEXT=<HOP_NEXT>:INTERFACE=<INTERFACE_INFO>"<cr>
<lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-ROUTE-INFO:::100;
l Response Message
NE 2005-03-21 09:33:54
M 100 COMPLD
"IP=127.0.0.0:MASK=255.0.0.0:HOPNEXT=127.0.0.1:INTERFACE=InLoopBack0"
"IP=129.9.16.2:MASK=255.255.255.255:HOPNEXT=127.0.0.1:INTERFACE=InLoopBack0"
;
Related Commands
None
A.4.3.1 ED-FTP
Edits FTP parameters.
Function
This command is issued to modify the attributes and state of FTP.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ED-FTP:[<TID>]::<CTAG>::<FTP_SWITCH>
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-FTP:::100::CLOSE;
l Response Message
NE 2002-03-04 15:23:20
M 100 COMPLD
;
Related Commands
A.4.3.2 RTRV-FTP
A.4.3.2 RTRV-FTP
Retrieves FTP parameters.
Function
This command retrieves the state of an FTP.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-FTP:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<FTP_SWITCH >"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-FTP:::100;
l Response Message
NE 2004-07-08 17:16:08
M 10 COMPLD
"CLOSE"
;
Related Commands
A.4.3.1 ED-FTP
A.4.4.1 ED-SERIAL
Modifies serial port parameters.
Function
This command modifies the attributes and state of the serial port.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ED-SERIAL:[<TID>]::<CTAG>:::[BAUDRATE=<BAUDRATE>],
[LINKWAY=<LINKWAY>],[WORKSTATE=<WORKSTATE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-SERIAL:::100:::BaudRate=38400;
l Response Message
NE 2004-07-10 15:35:00
M 100 COMPLD
;
Related Commands
A.4.4.2 RTRV-SERIAL
A.4.4.2 RTRV-SERIAL
Retrieves serial interface parameters.
Function
This command retrieves the parameters of a serial interface.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-SERIAL:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^" < BaudRate >,< Linkway >,<WorkState>" <cr><lf>
;
Response Parameters
Parameter Description
<WorkState> Indicates the working status of the serial interface. The valid
values are OPEN and CLOSE.
NOTE
The working status of the serial interface is OPEN by default. The
<WorkState> parameter is stored in the database.
Example
l Command
RTRV-SERIAL:::10;
l Response Message
NE 2004-07-10 16:24:31
M 10 COMPLD
"38400,TL1,OPEN"
;
Related Commands
A.4.4.1 ED-SERIAL
A.4.5 Configuring IP
This section lists commands which used to configure IP to communicate with maintenance
computer.
A.4.5.1 DLT-TIDIPMAP
Deletes a static TID-IP mapping.
Function
This command deletes a static TID-IP mapping.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
DLT-TIDIPMAP:[<TID>]::<CTAG>:::TID=<TID>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-TIDIPMAP:::100:::TID=NE101;
l Response Message
NE 2004-07-10 15:51:13
M 100 COMPLD
;
Related Commands
A.4.5.2 ENT-TIDIPMAP
A.4.5.3 RTRV-TIDIPMAP
A.4.5.2 ENT-TIDIPMAP
Creates a static TID-IP mapping.
Function
This command creates a static TID-IP mapping.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ENT-TIDIPMAP:[<TID>]::<CTAG>:::TID=<TID>,IP=<IPADDR>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-TIDIPMAP:::100:::TID=NE101,IP=192.168.0.101;
l Response Message
NE 2004-07-10 15:39:50
M 100 COMPLD ;
Related Commands
A.4.5.1 DLT-TIDIPMAP
A.4.5.3 RTRV-TIDIPMAP
A.4.5.3 RTRV-TIDIPMAP
Retrieves all the TID-IP mapping information.
Function
This command retrieves all the TID-IP mapping information.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-TIDIPMAP:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^" <TID>,<IPADDR>,<MODE> "<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-TIDIPMAP:::100;
l Response Message
NE 2004-07-10 15:53:04
M 100 COMPLD
"NE,129.9.0.1,MANMODE"
;
Related Commands
A.4.5.2 ENT-TIDIPMAP
A.4.5.1 DLT-TIDIPMAP
A.4.5.4 DLT-IPROUTE-STATIC
Deletes static routes.
Function
This command deletes static routes from the route table.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
DLT-IPROUTE-STATIC:<TID>::<CTAG>:::DESTIP=<DESTIP>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-IPROUTE-STATIC:::100::: DESTIP=129.9.0.2;
l Response Message
NE 2004-07-10 15:57:06
M 100 COMPLD
;
Related Commands
A.4.5.5 ENT-IPROUTE-STATIC
A.4.5.6 RTRV-IPROUTE-STATIC
A.4.5.5 ENT-IPROUTE-STATIC
Adds static routes.
Function
This command adds static routes to the route table.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ENT-IPROUTE-
STATIC:<TID>::<CTAG>:::DESTIP=<DESTIP>,MASK=<SUBNETMASK>,GATEWAY
=<GATEWAY_LAN>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ENT-IPROUTE-STATIC:::10:::DESTIP=129.8.0.0,MASK=255.255.0.0,GATEWAY=129.9.0.1;
l Response Message
NE 2004-07-10 15:57:06
M 10 COMPLD
;
Related Commands
A.4.5.4 DLT-IPROUTE-STATIC
A.4.5.6 RTRV-IPROUTE-STATIC
A.4.5.6 RTRV-IPROUTE-STATIC
Retrieves static routes.
Function
This command retrieves static routes from the route table.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-IPROUTE-STATIC:<TID>::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"[<DESTIP>],[<MASK>],[<GATEWAY>],[<BID>],[<PORT>]"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-IPROUTE-STATIC:::100;
l Response Message
NE 2004-07-10 16:00:08
M 100 COMPLD
"129.8.0.0,255.255.0.0,129.9.0.1,0,0"
;
Related Commands
A.4.5.5 ENT-IPROUTE-STATIC
A.4.5.4 DLT-IPROUTE-STATIC
A.4.5.7 RTRV-IPROUTE
Retrieves all route information.
Function
This command retrieves all route information.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-IPROUTE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<DESTADDR>,<MASK>,<GATEWAY>,<PROTOCOL>,<METRIC>,<IFNAME>"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
Example
l Command
RTRV-IPROUTE:::S;
l Response Message
NE 2008-12-06 16:28:17
M S RTRV
"127.0.0.0,255.0.0.0,127.0.0.1,DIRECT,0,InLoopBack0"
"127.0.0.1,255.255.255.255,127.0.0.1,DIRECT,0,InLoopBack0"
"129.9.0.0,255.255.0.0,129.9.11.19,DIRECT,0,Ethernet1"
"129.9.0.5,255.255.255.255,129.9.11.24,OSPF,120,PPP-0-2-255-1-2-3"
"129.9.0.100,255.255.255.255,129.9.11.24,OSPF,120,PPP-0-2-255-1-2-3"
"129.9.11.15,255.255.255.255,129.9.11.24,OSPF,120,PPP-0-2-255-1-2-3"
"129.9.11.17,255.255.255.255,129.9.11.24,OSPF,120,PPP-0-2-255-1-2-3"
"129.9.11.18,255.255.255.255,129.9.11.24,OSPF,160,PPP-0-2-255-1-2-3"
"129.9.11.19,255.255.255.255,127.0.0.1,DIRECT,0,InLoopBack0"
"129.9.11.21,255.255.255.255,129.9.11.24,OSPF,80,PPP-0-2-255-1-2-3"
"129.9.11.24,255.255.255.255,129.9.11.24,DIRECT,0,PPP-0-2-255-1-0-1"
"129.9.11.24,255.255.255.255,129.9.11.24,DIRECT,0,PPP-0-2-255-1-2-3"
"129.9.11.34,255.255.255.255,129.9.11.24,OSPF,120,PPP-0-2-255-1-2-3"
>
>
NE 2008-12-06 16:28:17
M S COMPLD
"129.9.255.255,255.255.255.255,129.9.11.19,DIRECT,0,Ethernet1"
"255.255.255.255,255.255.255.255,129.9.11.19,DIRECT,0,Ethernet1"
;
>
Related Commands
A.4.5.5 ENT-IPROUTE-STATIC
A.4.5.4 DLT-IPROUTE-STATIC
A.4.5.8 RTRV-STAT-TCP
Retrieves the TCP connection information.
Function
This command retrieves the information about the TCP active sessions.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-STAT-TCP:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"PEERIP=<PEERIPADDR>,PORT=<PORT>,PEERPORT=<PEERPORT>,RECVPACKET=<RECV_PACKET>,R
ECVBYTE=<RECV_BYTE>,SENDPACKET=<SEND_PACKET>,SENDBYTE=<SEND_BYTE>,CONNTIMES=<CONNT
IMES>."<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-STAT-TCP:::100;
l Response Message
NE 2005-12-19 20:21:27
M 100 COMPLD
"PEERIP=129.9.16.17,PORT=1600,PEERPORT=1118,RECVPACKET=25,RECVBYTE=664,SENDPA
CKET=0,SENDBYTE=0,CONNTIMES=1"
;
Related Commands
None
A.4.5.9 RTRV-TCPIP-INFO
Retrieves the TCP/IP information.
Function
This command retrieves the information about the TCP/IP.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
RTRV-TCPIP-INFO:[<TID>]::<CTAG>::<TYPE_STR>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<TYPE_INFO>"<cr><lf>
Response Parameters
Parameter Description
Example
l Command
RTRV-TCPIP-INFO:::100::"TCPIP_ShowNetStatus";
l Response Message
NEW-NE 2011-10-11 00:10:50
M 100 RTRV
"
Proto Local Address Foreign Address State
"
"TCP4 0.0.0.0:23 0.0.0.0:0 Listening
"
"TCP4 0.0.0.0:80 0.0.0.0:0 Listening
"
"TCP4 0.0.0.0:1400 0.0.0.0:0 Listening
"
"TCP4 0.0.0.0:2008 0.0.0.0:0 Listening
"
"TCP4 0.0.0.0:3081 0.0.0.0:0 Listening
"
"TCP4 0.0.0.0:3082 0.0.0.0:0 Listening
"
"TCP4 0.0.0.0:5432 0.0.0.0:0 Listening
"
"TCP4 130.9.0.2:23 130.9.0.130:4864 Established
"
"UDP4 0.0.0.0:0 0.0.0.0:0
"
"UDP4 0.0.0.0:161 0.0.0.0:0
"
>
>
A.4.5.10 IP-PING
Communicates with an NE on a network through the ping command.
Function
This command checks the communication with an NE by using the ping command.
Usage Note
The command sends 3 packets and each packet has 56 bytes. TTL is 255.
Category
Communication
Security
Maintenance
Command Syntax
IP-PING:[<TID>]::<CTAG>::<TARGETIP>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<PINGRESULT>"
<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
IP-PING:::100::129.9.35.210;
l Response Message
NE 2004-07-13 16:11:19
M 100 COMPLD
"\"
PING 129.9.35.210: 56 data bytes\""
"\" Reply from 129.9.35.210: bytes=56 Sequence=1 ttl=128 time=1 ms\""
"\" Reply from 129.9.35.210: bytes=56 Sequence=2 ttl=128 time=1 ms\""
"\" Reply from 129.9.35.210: bytes=56 Sequence=3 ttl=128 time=1 ms\""
"\"
--- 129.9.35.210 ping statistics ---\""
"\" 3 packet(s) transmitted\""
"\" 3 packet(s) received\""
"\" Percent 0.00% packet lost \""
"\" round-trip min/avg/max = 1/1/1 ms\""
"\"\""
;
Related Commands
None
A.4.5.11 IP-TRACERT
Traces the path to an NE on a network.
Function
This command traces the path to an NE on the network.
Usage Note
The user needs to input the maximum number of hops in this command. By default, the system
sends three test data packets for each hop, and the expiration time is five seconds for each packet.
As a result, the proper hop is needed when you input the parameter in the command.
The command does not support the trace of the local IP address, loopback address, network
segment address, and broadcast address.
Category
Communication
Security
Maintenance
Command Syntax
IP-TRACERT:[<TID>]::<CTAG>::<TARGETIP>,[MAX_HOPS];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"< TRACERTRESULT >"
<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
IP-TRACERT:::100::129.9.35.210;
l Response Message
NE 2004-07-13 16:14:42
M 100 CMPLD
"\"
traceroute to 129.9.35.210(129.9.35.210) 30 hops max,40 bytes packet \""
"\"
1 129.9.35.210 0 ms 0 ms 0 ms \""
"\"\""
;
>
Related Commands
None
A.4.6.1 RTRV-OSI-ADJS
Retrieves the information of the OSI neighbor.
Function
This command is issued to retrieve the information of the OSI neighbor.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
RTRV-OSI-ADJS:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<OSI_CIRNAME>:ADJ=<OSI_ADJ>,TYPE=<OSI_ADJSTYPE>,HOLD=<OSI_HOLD>,STATE=<OSI_ADJ
SSTATE>,AREAID=<OSI_AREAID>,SYSID=<OSI_SYSID>,SNPA=<OSI_SNPA>,ATTR=<OSI_ADJSATTR>"
<cr><lf>
;
Response Parameters
NONE
Example
l Command
RTRV-OSI-ADJS:::123456;
l Response Message
NEW-NE 2012-02-07 19:28:38
M 123456 COMPLD
;
A.4.6.2 ED-OSI-DCC
Edit the parameter of OSI.
Function
This command is issued to edit the parameter of OSI.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ED-OSI-DCC:[<TID>]::<CTAG>::[T200=<OSI_T200>],[N200=<OSI_N200>],
[ISHLOTM=<OSI_DCCISHLOTM>],[ESCFGTM=<OSI_DCCESCFGTM>],
[ISCFGTM=<OSI_DCCISCFGTM>],[HLDTM=<OSI_DCCHLDTM>];
Command Parameters
Parameter Description Default
Value
NA
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-OSI-DCC:::3:::T200=1;
l Response Message
NEW-NE 2012-02-07 20:23:32
M 100 COMPLD
;
A.4.6.3 ENT-OSI-DLTUNNEL
Add an OSI tunnel.
Function
This command is issued to add an OSI tunnel.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
ENT-OSI-DLTUNNEL:
[<TID>]::<CTAG>::PEERIP=<PEERIP>,ROLE=<TUN_LAPDROLE>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ENT-OSI-DLTUNNEL:::100::PEERIP=129.9.35.111,ROLE=USER;
l Response Message
NEW-NE 2012-02-7 20:23:32
M 100 COMPLD
;
A.4.6.4 DLT-OSI-DLTUNNEL
Delete an OSI tunnel
Function
This command is issued to delete an OSI tunnel.
Usage Note
None
Category
Communication
Security
Maintenance
Command Syntax
DLT-OSI-DLTUNNEL:[<TID>]::<CTAG>::PEERIP=<PEERIP>;
Command Parameters
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-OSI-DLTUNNEL:::100::PEERIP=129.9.35.111;
l Response Message
NEW-NE 2012-02-06 20:23:32
M 100 COMPLD
;
A.4.7.1 ED-OSPF-DCC
Modifies the DCC-type interface parameters of the OSPF protocol.
Function
This command modifies the DCC-type interface parameters of the OSPF protocol.
Usage Note
This command can be successfully issued only after the OSPF protocol is enabled.
Category
Communication
Security
Maintenance
Command Syntax
ED-OSPF-DCC:[<TID>]::<CTAG>:::[COST=<COST>],[HELLO=<HELLOTIME>],
[DEAD=<DEADTIME>],[RETRANSMIT=<RETRANSMIT_TIME>],
[DELAY=<TRANSIT_DELAY_TIME>],[NOTSILENCE=<NOT_SILENCE>];
Command Parameters
Parameter Description Default
Value
<COST> Indicates the cost. The valid value ranges from 1 to 100
65535. Entering "0" will set this parameter to the
default value.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-OSPF-DCC:::100:::COST=150;
l Response Message
NE 2004-07-10 16:01:49 M 100 COMPLD ;
Related Commands
A.4.7.4 RTRV-OSPF-ALL
A.4.7.2 ED-OSPF-LAN
Modifies the LAN-type interface parameters of the OSPF protocol.
Function
This command modifies the LAN-type interface parameters of the OSPF protocol.
Usage Note
This command can be successfully issued only after the OSPF protocol is enabled.
Category
Communication
Security
Maintenance
Command Syntax
ED-OSPF-LAN:[<TID>]:<AID>:<CTAG>:::[COST=<COST>],[HELLO=<HELLOTIME>],
[DEAD=<DEADTIME>],[RETRANSMIT=<RETRANSMITTIME>],
[DELAY=<TRANSITDELAY>],[DRPRI=<PRIORITY>],
[NOTSILENCE=<NOT_SILENCE>];
Command Parameters
Parameter Description Default
Value
<HELLOTIME> Indicates the hello timer. The valid value ranges from 10
1 to 255. Entering "0" will set this parameter to the
default value.
<DEADTIME> Indicates the dead timer. The valid value ranges from 40
1 to 65535. <DEADTIMER> must be larger than
<HELLOTIMER>. Entering "0" will set this
parameter to the default value.
<TRANSITDELA Indicates the transit delay. The valid value ranges from 1
Y> 1 to 3600. Entering "0" will set this parameter to the
default value.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-OSPF-LAN:::100:::cost=150;
l Response Message
NE 2004-07-10 16:01:49 M 100 COMPLD ;
Related Commands
A.4.7.4 RTRV-OSPF-ALL
A.4.7.3 ED-OSPF-SYS
Modifies the system parameters of the OSPF protocol.
Function
This command modifies the system parameters of the OSPF protocol.
Usage Note
This command can be successfully issued only after the OSPF protocol is enabled.
Category
Communication
Security
Maintenance
Command Syntax
ED-OSPF-SYS:[<TID>]::<CTAG>:::[ENABLE=<OSPF_ENABLE>],[AREA=<AREA>],
[STUB=<STUB_FLAG>],[NSSA=<NSSA_FLAG>],[IMPORTRIP=<IMPORT_RIP>],
[IMPORTSTATIC=<IMPORT_STATIC>],[IMPORTDIRECT=<IMPORT_DIRECT>];
Command Parameters
Parameter Description Default Value
<AREA> Indicates the area ID. The valid values are IP 0.0.0.0
addresses ranging from 0.0.0.0 to 255.255.255.254.
NOTE
Modification of <AREA> initializes other parameters in
area configuration with default values. The parameters
include <STUB_FLAG> and <NSSA_FLAG>. The value
of <STUB_FLAG> or <NSSA_FLAG> cannot be changed
if <AREA> is set to 0.0.0.0 (backbone area).
<STUB_FLAG> Indicates the stub area flag. The valid values are Y N
and N.
<IMPORT_RIP> Indicates the import RIP flag. The valid values are Y N
and N.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-OSPF-SYS:::100:::ENABLE=Y;
l Response Message
NE 2004-07-10 16:01:49 M 100 COMPLD ;
Related Commands
A.4.7.4 RTRV-OSPF-ALL
A.4.7.4 RTRV-OSPF-ALL
Retrieves all parameters of the OSPF protocol (OSPF-SYS, OSPF-DCC, and OSPF-LAN).
Function
This command retrieves all parameters of the OSPF protocol (OSPF-SYS, OSPF-DCC, and
OSPF-LAN).
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-OSPF-ALL:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"
Enable=<OSPF_ENABLE>,AREA=<AREA>,STUB=<STUB_FLAG>,NSSA=<NSSA_FLAG>,IMPORTRIP=<IMPO
RTRIP_FLAG>,IMPORTSTATIC=<IMPORTSTATIC_FLAG>,IMPORTDIRECT=<IMPORTDIRECT_FLAG>,INTE
RFACE=<INTERFACE>,COST=<COST>,HELLO=<HELLOTIMER>,DEAD=<DEADTIMER>,RETRANSMIT=<RETR
ANSMITTIMER>,Delay=<TRANSITDELAY>,NOTSILENCE=<NOT_SILENCE>,DRPRI=<OSPF_DRPRI>,IMPO
RTDEFRT=<IMPORTDEFRT_FLAG>;
Response Parameters
Parameter Description
<AREA> Indicates the area ID. The valid value is an IP address ranging
from 0.0.0.0 (default) to 255.255.255.254.
<STUB_FLAG> Indicates the flag. The valid values are Y and N (default=N).
<NSSA_FLAG> Indicates the flag. The valid values are Y and N (default=N).
<IMPORTRIP_FLAG> Indicates the flag. The valid values are Y and N (default=N).
Parameter Description
<IMPORTSTATIC_FLAG> Indicates the flag. The valid values are Y and N (default=N).
<IMPORTDIRECT_FLAG> Indicates the flag. The valid values are Y and N (default=N).
<INTERFACE> Indicates the type of the interface. The valid values are Y,
DCC and LAN.
<COST> Indicates the cost. The valid value ranges from 1 to 65535.
The default value is 100.
<HELLOTIMER> Indicates the hello timer. The valid value ranges from 1 to
255 (default=1).
<DEADTIMER> Indicates the dead timer. The valid value ranges from 1 to
65535. The default value is 6.
<TRANSITDELAY> Indicates the transmission delay. The valid value ranges from
1 to 3600 (default=1). The default value is 1.
<NOT_SILENCE> Indicates the flag. The valid values are Y and N (default=Y).
<IMPORTDEFRT_FLAG> Indicates the default route import flag. The valid values are
Y and N (default=N).
Example
l Command
RTRV-OSPF-ALL:::100
l Response Message
NE 2004-07-10 16:13:16
M 100 COMPLD
"
ENABLE=Y,AREA=0.0.0.0,STUB=N,NSSA=N,IMPORTRIP=N,IMPORTSTATIC=N,IMPORTDIRECT=N,INTE
RFACE=LAN,COST=10,HELLO=10,DEAD=40,RETRANSMIT=5,DELAY=1,NOTSILENCE=N,
DRPRI=1,IMPORTDEFRT=N"
"
ENABLE=Y,AREA=0.0.0.0,STUB=N,NSSA=N,IMPORTRIP=N,IMPORTSTATIC=N,IMPORTDIRECT=N,INTE
RFACE=DCC,COST=100,HELLO=1,DEAD=6,RETRANSMIT=5,DELAY=1,NOTSILENCE=Y,DRPRI=42949672
95,IMPORTDEFRT=N"
;
Related Commands
A.4.7.3 ED-OSPF-SYS
A.4.7.1 ED-OSPF-DCC
A.4.7.2 ED-OSPF-LAN
A.4.8.1 DLT-NTP-ACCTL
Deletes the access control of NTP.
Function
This command is issued to delete the NTP access control.
Usage Note
This command can be successfully issued only after the NTP protocol is enabled.
Category
NTP
Security
Maintenance
Command Syntax
DLT-NTP-ACCTL:[<TID>]::<CTAG>:::[ACLNUM=<NTP_ACLNUM>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
DLT-NTP-ACCTL:::100:::ACLNUM=1;
l Response Message
NE 2002-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.4.8.2 ENT-NTP-ACCTL
A.4.8.3 RTRV-NTP-ACCTL
A.4.8.2 ENT-NTP-ACCTL
Adds access control information about the NTP.
Function
This command adds the access control information about the NTP.
Usage Note
This command can be successfully issued only after the NTP protocol is enabled.
Category
NTP
Security
Maintenance
Command Syntax
ENT-NTP-ACCTL:[<TID>]::<CTAG>:::[ACLNUM=<NTP_ACLNUM>],
[SRCIP=<SRCIP>],[SRCNSAP=<SRCNSAP>],[ADDRACCESS=<ADDR_ACCESS>],
[NTPACCESS=<NTP_ACCESS>];
Command Parameters
Parameter Description Default Value
<NTP_ACCES Indicates the working mode of the NTP. The valid Peer
S> values are as follows:
l Query: Only responds to the query of other NEs.
l SYN: Only responds to the time request of other
NEs.
l Server: Responds to the query and time request of
other NEs. It cannot be synchronized to remote
servers.
l Peer: Responds to the query and time request of
other NEs. It can be synchronized to remote
servers.
Response Syntax
cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-NTP-ACCTL:::100:::ACLNUM=1,SRCIP=129.9.0.1,ADDRACCESS =ACCEPT, NTPACCESS =SYN;
l Response Message
NE 2002-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.4.8.1 DLT-NTP-ACCTL
A.4.8.3 RTRV-NTP-ACCTL
A.4.8.3 RTRV-NTP-ACCTL
Retrieves the access controls of an NTP.
Function
This command retrieves the information about the NTP access controls.
Usage Note
None
Category
NTP
Security
Retrieve
Command Syntax
RTRV-NTP-ACCTL:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"ACLNUM=<NTP_ACLNUM>,SRCIP=<SRCIP>,SRCNSAP=<SRCNSAP>,ADDRACCESS=<ADDR_ACCESS>,N
TPACCESS=<NTPACCESS>"<cr><lf>
;
Response Parameters
Parameter Description
NTP_ACLNUM Indicates the number of NTP access controls. The valid value
ranges from 1 to 250.
NTP_ACCESS Indicates the working mode of the NTP. The valid values are
as follows:
l QUERY: Only responds to the query of other NEs.
l SYN: Only responds to the time request of other NEs.
l SERVER: Responds to the query and time request of other
NEs. It cannot be synchronized to remote servers.
l PEER: Responds to the query and time request of other
NEs. It can be synchronized to remote servers.
Example
l Command
RTRV-NTP-ACCTL:::100;
l Response Message
NE 2007-05-28 06:51:59
M 100 COMPLD
"ACLNUM=250,SRCIP=129.9.0.1,SRCNSAP=,ADDRACCESS=ACCEPT,NTPACCESS=SERVER"
;
Related Commands
A.4.8.2 ENT-NTP-ACCTL
A.4.8.1 DLT-NTP-ACCTL
A.4.8.4 DLT-NTP-AUTHPARA
Deletes NTP authentication parameters.
Function
This command deletes the NTP authentication parameters.
Usage Note
This command can be successfully issued only after the NTP protocol is enabled.
Category
NTP
Security
Maintenance
Command Syntax
DLT-NTP-AUTHPARA:[<TID>]::<CTAG>:::KEYID=<NTP_KEYID>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
DLT-NTP-AUTHPARA:::100:::KEYID=12;
l Response Message
NE 2002-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.4.8.6 ENT-NTP-AUTHPARA
A.4.8.5 ED-NTP-AUTHPARA
A.4.8.7 RTRV-NTP-AUTHPARA
A.4.8.5 ED-NTP-AUTHPARA
Modifies the parameters of NTP authentication.
Function
This command changes the Network Time Protocol (NTP) authentication information.
Usage Note
This command can be successfully issued only after the NTP protocol is enabled.
Category
NTP
Security
Maintenance
Command Syntax
ED-NTP-AUTHPARA:[<TID>]::<CTAG>:::[AUTHTYPE=<NTP_AUTHTYPE>],
[KEYID=< NTP_KEYID>],[KEY=<NTP_KEY>],[STATE=<NTP_TRUSTSTATE>];
Command Parameters
Parameter Description Defa
ult
Value
<NTP_KEYID Indicates the ID of the key that is verified by the NTP protocol. NA
> The valid values are integers ranging from 1 to 1024.
<NTP_TRUST Indicates the state of NTP authentication. The valid values are Y N
STATE> (authenticated) and N (unauthenticated).
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-NTP-AUTHPARA:::100:::AUTHTYPE=MD5,KEYID=12,KEY="abc",STATE=Y;
l Response Message
NE 2002-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.4.8.6 ENT-NTP-AUTHPARA
A.4.8.4 DLT-NTP-AUTHPARA
A.4.8.7 RTRV-NTP-AUTHPARA
A.4.8.6 ENT-NTP-AUTHPARA
Creates the information about NTP authentication.
Function
This command adds the information about NTP authentication.
Usage Note
This command can be successfully issued only after the NTP protocol is enabled.
Category
NTP
Security
Maintenance
Command Syntax
ENT-NTP-AUTHPARA:[<TID>]::<CTAG>:::[AUTHTYPE=<NTP_AUTHTYPE>],
[KEYID=<NTP_KEYID>],[KEY=<NTP_KEY>],[STATE=<NTP_TRUSTSTATE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-NTP-AUTHPARA:::100:::AUTHTYPE=MD5,KEYID=12,KEY="abc",STATE=Y;
l Response Message
NE 2002-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.4.8.5 ED-NTP-AUTHPARA
A.4.8.4 DLT-NTP-AUTHPARA
A.4.8.7 RTRV-NTP-AUTHPARA
A.4.8.7 RTRV-NTP-AUTHPARA
Retrieves NTP authentication parameters.
Function
This command retrieves NTP authentication parameters.
Usage Note
None
Category
NTP
Security
Maintenance
Command Syntax
RTRV-NTP-AUTHPARA:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"AUTHTYPE=<NTP_AUTHTYPE>,KEYID=<NTP_KEYID>,KEY=<NTP_KEY>,STATE=<NTP_TRUSTSTATE>
"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-NTP-AUTHPARA:::100;
l Response Message
NE 2007-05-28 06:49:58
M 100 COMPLD
"AUTHTYPE=MD5,KEYID=1,KEY=\"wangfei\",STATE=Y"
;
Related Commands
A.4.8.6 ENT-NTP-AUTHPARA
A.4.8.5 ED-NTP-AUTHPARA
A.4.8.4 DLT-NTP-AUTHPARA
A.4.8.8 DLT-NTP-SERVER
Deletes an NTP server.
Function
This command deletes an NTP server.
Usage Note
This command can be successfully issued only after the NTP protocol is enabled.
Category
NTP
Security
Maintenance
Command Syntax
DLT-NTP-SERVER:[<TID>]::<CTAG>:::[SERVERIP=<NTP_SERVERIP>],
[SERVERNSAP=<NTP_SERVERNSAP>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-NTP-SERVER:::100:::SERVERIP=129.9.0.1;
l Response Message
NE 2002-03-04 15:23:20
M 100 COMPLD
;
Related Commands
A.4.8.9 ENT-NTP-SERVER
A.4.8.10 RTRV-NTP-SERVER
A.4.8.9 ENT-NTP-SERVER
Creates the information about an NTP server.
Function
This command adds an NTP server.
Usage Note
This command can be successfully issued only after the NTP protocol is enabled.
Category
NTP
Security
Maintenance
Command Syntax
ENT-NTP-SERVER:[<TID>]::<CTAG>:::[SERVERIP=<NTP_SERVERIP>],
[SERVERNSAP=<NTP_SERVERNSAP>],[VERSION=<NTP_VERSION>],
[TRUSTKEY=<TRUSTKEY>],[PRIORITY=<PRI_SERVER>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-NTP-SERVER:::100:::SERVERIP=129.9.0.1,VERSION=3,PRIORITY=Y;
l Response Message
NE 2002-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.4.8.8 DLT-NTP-SERVER
A.4.8.10 RTRV-NTP-SERVER
A.4.8.10 RTRV-NTP-SERVER
Retrieves NTP servers.
Function
This command retrieves NTP servers.
Usage Note
None
Category
NTP
Security
Retrieve
Command Syntax
RTRV-NTP-SERVER:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"SERVERIP=<NTP_SERVERIP>,SERVERNSAP=<NTP_SERVERNSAP>,VERSION=<NTP_VERSION>,TRUS
TKEY=<TRUSTKEY>,PRIORITY=<PRI_SERVER>"<cr><lf>
;
Response Parameters
Parameter Description
<NTP_SERVERI Indicates the IP address of an NTP server. The valid values are A, B,
P> and C class IP addresses.
<NTP_SERVER Indicates the NSAP address of an NTP server. This parameter contains
NSAP> 40 bytes.
<NTP_VERSION Indicates the version information. The valid value is an integer ranging
> from 1 to 3.
NOTE
Version 1 is not supported in C/S mode.
<TRUSTKEY> Indicates the ID of the key that is verified by the NTP protocol. The
valid value is an integer ranging from 0 to 1024.
<PRI_SERVER> Indicates the priority of an NTP server. The valid values are Y (higher
priority) and N (lower priority).
Example
l Command
RTRV-NTP-SERVER:::100;
l Response Message
NE 2007-05-28 06:49:23
M 100 COMPLD
"SERVERIP=129.9.35.23,SERVERNSAP=,VERSION=3,TRUSTKEY=1,PRIORITY=Y"
;
Related Commands
A.4.8.9 ENT-NTP-SERVER
A.4.8.8 DLT-NTP-SERVER
A.4.8.11 ED-NTP-SYS
Modifies the system parameters of an NTP.
Function
This command modifies system parameters of an NTP.
Usage Note
Switching quickly between enable and disable is not allowed.
This command can be successfully issued only after the NTP protocol is enabled.
Category
NTP
Security
Maintenance
Command Syntax
ED-NTP-SYS:[<TID>]::<CTAG>:::[ENABLE=<NTP_ENABLE>],
[AUTH=<AUTH_ENABLE>];
Command Parameters
Parameter Description Default
Value
<NTP_ENA Indicates whether the NTP is enabled. The valid values are N
BLE> Y (enable NTP) and N (disable NTP).
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-NTP-SYS:::100:::ENABLE=Y,AUTH=Y;
l Response Message
NE 2002-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.4.8.12 RTRV-NTP-SYS
A.4.8.12 RTRV-NTP-SYS
Retrieves system parameters of an NTP.
Function
This command retrieves system parameters of an NTP.
Usage Note
None
Category
NTP
Security
Retrieve
Command Syntax
RTRV-NTP-SYS:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"ENABLE=<NTP_ENABLE>,AUTH=<AUTH_ENABLE>"<cr><lf>
;
Response Parameters
Parameter Description
<NTP_ENABLE> Indicates whether the NTP is enabled. The valid values are Y
(enable) and N (disable).
Example
l Command
RTRV-NTP-SYS:::100;
l Response Message
NE 2007-05-28 06:47:02
M 100 COMPLD
"ENABLE=Y,AUTH=Y"
;
Related Commands
A.4.8.11 ED-NTP-SYS
A.4.8.13 RTRV-NTP-STATUSINFO
Retrieves status information about an NTP.
Function
This command retrieves the status information about an NTP.
Usage Note
None
Category
NTP
Security
Retrieve
Command Syntax
RTRV-NTP-STATUSINFO:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"STATUS=<NTP_SYNSTATUS>,REFIP=<REF_IP>,REFNSAP=<REF_NSAP>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-NTP-STATUSINFO:::100;
l Response Message
NE 2007-05-28 06:50:43
M 100 COMPLD
"STATUS=SYNCHRONIZED,REFIP=129.9.35.23,REFNSAP="
;
Related Commands
None
A.4.9.1 DLT-SNMP-ACCESSIP
Deletes the IP address from the SNMP agent.
Function
This command deletes an allowed/got/set IP address from the SNMP agent.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
DLT-SNMP-ACCESSIP:[<TID>]:<IPAddress>:<CTAG>
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-SNMP-ACCESSIP::129.9.0.100:c;
l Response Message
NE 2006-02-23 16:19:03
M C COMPLD
;
Related Commands
A.4.9.3 ENT-SNMP-ACCESSIP
A.4.9.2 ED-SNMP-ACCESSIP
A.4.9.4 RTRV-SNMP-ACCESSIP
A.4.9.2 ED-SNMP-ACCESSIP
Changes the access level.
Function
This command changes the access level for a legal IP address.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
ED-SNMP-ACCESSIP:[TID]:<IPADDRESS>:<CTAG>:::LEVEL=<ACCESSLEVEL>
Command Parameters
Paramete Description Default Value
r
<IPADDR Indicates the IP address (manager address). The valid values 255.255.255.25
ESS> are 255.255.255.255 and A, B, and C class IP addresses, 5
except the addresses between 127.0.0.0 and
127.255.255.255.
255.255.255.255 means allowing all IP addresses. When the
current IP address is 255.255.255.255, after a new IP address
is entered, the NE will deny this command with an error
message. Users can run the A.4.9.1 DLT-SNMP-
ACCESSIP command to delete the IP address
255.255.255.255 and reenter a new IP address.
<ACCESS Indicates the access level. The valid values are R and RW. R
LEVEL> l R: Indicates the read community.
l RW: indicates the read and write community.
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-SNMP-ACCESSIP::129.9.0.100:C:::LEVEL=R
l Response Message
NE 2006-02-23 15:52:50
M C COMPLD
;
Related Commands
A.4.9.3 ENT-SNMP-ACCESSIP
A.4.9.4 RTRV-SNMP-ACCESSIP
A.4.9.1 DLT-SNMP-ACCESSIP
A.4.9.3 ENT-SNMP-ACCESSIP
Enters the IP address into the SNMP agent.
Function
This command enters the get/set IP address into the SNMP agent so that manager can access to
the SNMP agent. The default value before delivery is null. An IP address of no more than 32
bits is allowed.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
ENT-SNMP-ACCESSIP:[<TID>]:<IPADDRESS>:<CTAG>:::
[LEVEL=<ACCESSLEVEL>]
Command Parameters
Parameter Description Default
Value
<IPADDR Indicates the IP address (manager address). The valid values 255.255.255.2
ESS> are the A, B, and C class IP addresses, and 255.255.255.255, 55
except for the address between 127.0.0.0 and
127.255.255.255.
255.255.255.255 means allowing all IP addresses. When the
current IP address is 255.255.255.255, the NE does not
execute this command and provides an error message after
users enter a new IP address. In this scenario, users can delete
255.255.255.255 by using a command A.4.9.1 DLT-SNMP-
ACCESSIP and then re-enter the new IP address.
<ACCESS Indicates the access level. The valid values are R and RW. R
LEVEL> l R: Indicates the read community.
l RW: indicates the read and write community.
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss><cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-SNMP-ACCESSIP::129.9.0.102:C;
l Response Message
NE 2006-02-23 15:48:59
M C COMPLD ;
Related Commands
A.4.9.4 RTRV-SNMP-ACCESSIP
A.4.9.2 ED-SNMP-ACCESSIP
A.4.9.1 DLT-SNMP-ACCESSIP
A.4.9.4 RTRV-SNMP-ACCESSIP
Retrieves the IP address related information.
Function
This command retrieves the IP address related information.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
RTRV-SNMP-ACCESSIP:[<TID>]:[<IPAddress>]:<CTAG>
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"IPADDRESS=<IPADDRESS>:LEVEL=<ACCESSLEVEL>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-SNMP-ACCESSIP::129.9.0.100:C;
l Response Message
NE 2006-02-23 14:26:01
M C COMPLD
"IPADDRESS=129.9.0.100:LEVEL=RW"
;
Related Commands
A.4.9.3 ENT-SNMP-ACCESSIP
A.4.9.2 ED-SNMP-ACCESSIP
A.4.9.1 DLT-SNMP-ACCESSIP
A.4.9.5 DLT-SNMP-TRAPINFO
Deletes the trap configuration information.
Function
This command deletes the trap configuration information about the specified IP address.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
DLT-SNMP-TRAPINFO:[<TID>]:<IPADDRESS>:<CTAG>
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-SNMP-TRAPINFO::129.9.0.100:C;
l Response Message
NE 2006-02-23 16:57:48
M C COMPLD
;
Related Commands
A.4.9.8 RTRV-SNMP-TRAPINFO
A.4.9.6 ED-SNMP-TRAPINFO
A.4.9.7 ENT-SNMP-TRAPINFO
A.4.9.6 ED-SNMP-TRAPINFO
Modifies the trap configuration information.
Function
This command modifies the trap configuration information, including port number, trap
community, and trap version.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
ED-SNMP-TRAPINFO:[<TID>]:<IPADDRESS>:<CTAG>:::[PORT=<PORTNUMBER>],
[TCOMMUNITY=<TPCOMMUNITY>],[VER=<TRAPVERSION>]
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-SNMP-TRAPINFO::129.9.0.100:C:::PORT=120;
l Response Message
NE 2006-02-23 16:48:25
M C COMPLD
;
Related Commands
A.4.9.8 RTRV-SNMP-TRAPINFO
A.4.9.7 ENT-SNMP-TRAPINFO
A.4.9.5 DLT-SNMP-TRAPINFO
A.4.9.7 ENT-SNMP-TRAPINFO
Adds trap information.
Function
This command adds trap information to the SNMP agent so that the SNMP trap message can be
transmitted to the SNMP manager. A maximum of 32 IP addresses are supported.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
ENT-SNMP-TRAPINFO:[<TID>]:<IPADDRESS>:<CTAG>:::
[PORT=<PORTNUMBER>], [TCOMMUNITY=<TPCOMMUNITY>],
[VER=<TRAPVERSION>]
Command Parameters
Parameter Description Default Value
<TRAPVER Indicates the trap version. The valid values are V1 and V1
SION> V2.
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-SNMP-TRAPINFO::129.9.0.100:C;
l Response Message
NE 2006-02-23 16:40:33
M C COMPLD
;
Related Commands
A.4.9.8 RTRV-SNMP-TRAPINFO
A.4.9.6 ED-SNMP-TRAPINFO
A.4.9.5 DLT-SNMP-TRAPINFO
A.4.9.8 RTRV-SNMP-TRAPINFO
Retrieves the trap configuration information.
Function
This command retrieves the trap configuration information about a specified IP address.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
RTRV-SNMP-TRAPINFO:[<TID>]:[<IPADDRESS >]:<CTAG>
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"
IPADDRESS=<IPADDRESS>,PORT=<PORTNUMBER>,TCOMMUNITY=<TPCOMMUNITY>,VER=<TRAPVERSION>
"<cr><lf>
;
Response Parameters
Parameter Description
<IPADDRESS> Indicates the IP address of SNMP trap. The valid values are
A, B, and C class IP addresses, except 127 network address.
<TRAPVERSION> Indicates the trap version. The valid values are V1 and V2.
Example
l Command
RTRV-SNMP-TRAPINFO:::C;
l Response Message
NE 2006-02-23 16:26:00
M C COMPLD
"IPADDRESS=129.9.0.12,PORT=162,TCOMMUNITY=PUBLIC,VER=V1"
"IPADDRESS=129.9.0.100,PORT=162,TCOMMUNITY=PUBLIC,VER=V1"
;
Related Commands
A.4.9.7 ENT-SNMP-TRAPINFO
A.4.9.6 ED-SNMP-TRAPINFO
A.4.9.5 DLT-SNMP-TRAPINFO
A.4.9.9 ED-SNMP-COMMUNITY
Changes the read community and write community.
Function
This command changes the read community and write community.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
ED-SNMP-COMMUNITY:[<TID>]::<CTAG>:::[RCOMUNITY=<RDCOMMUNITY>,]
[WCOMMUNITY=<WTCOMMUNITY>]
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-SNMP-COMMUNITY:::C:::RCOMMUNITY=readcommunity,WCOMMUNITY=writecommunity
l Response Message
NE 2006-02-23 17:07:36
M C COMPLD
;
Related Commands
A.4.9.10 RTRV-SNMP-COMMUNITY
A.4.9.10 RTRV-SNMP-COMMUNITY
Retrieves the information about all communities.
Function
This command retrieves the information about all communities that have been configured. The
default value of the read community is public and that of the write community is private in NE
factory.
Usage Note
None
Category
SNMP
Security
Super
Command Syntax
RTRV-SNMP-COMMUNITY:[<TID>]::<CTAG>
Command Parameters
None
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"RCOMMUNITY=<RDOMMUNITY>,WCOMMUNITY=<WTCOMMUNITY>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-SNMP-COMMUNITY:::100
l Response Message
NE 2006-02-23 13:10:11
M 100 COMPLD
"RCOMMUNITY=public,WCOMMUNITY=private"
Related Commands
A.4.9.9 ED-SNMP-COMMUNITY
A.5.1 ENT-EQPT
Creates logical equipment.
Function
This command creates a logical shelf, a unit, or an SFP (small form-factor pluggable) on the
unit. It also automatically generates all port facilities supported by the unit and assigns default
values to all port facility attributes.
Usage Note
After a logical card that supports SFP is created (automatically or manually), the associated SFP
and facility objects are created based on the physical SFP module. If the type of the physical
SFP module cannot be recognized, a colorless port is created.
The facility object is gigabit-Ethernet (GETH) by default if an electrical or optical port is created
as an SFP object on cards that support the SFP module and have Layer-2 switching and
processing capability.
Category
Equipment
Security
Provisioning
Command Syntax
ENT-EQPT:[<TID>]:<AID>:<CTAG>::<TYPE>::[<PST>,][<SST>];
Command Parameters
Parameter Description Default Value
<TYPE> Indicates the AID unit type, that is, the shelf type, NA
card type, or SFP type.
The valid values are as follows when this command
is used to create a shelf:
l SHELF6800A: indicates that the shelf type is
OptiX OSN 6800A.
l SHELF8800T16: indicates that the shelf type is
OptiX OSN 8800T16.
l SHELF8800T32: indicates that the shelf type is
OptiX OSN 8800T32.
l SHELF8800T32E: indicates that the shelf type
is OptiX OSN 8800T32E.
l SHELF8800T64: indicates that the shelf type is
OptiX OSN 8800T64.
The card type refers to the type of a specific card
supported.
The valid values are as follows when this command
is used to create an SFP module:
l OCH: indicates a colored optical interface.
l OC: indicates a colorless optical interface.
l EC: indicates an electrical interface.
l OSC: indicates an OSC interface.
l CFP4*10G: indicates a 4*10G CFP interface.
l CFP4*25G: indicates a 4*25G CFP interface.
l CFP10*10G: indicates a 10*10G CFP interface.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Example
l Command
ENT-EQPT::SLOT-1-7:C::13LSX::,AINS;
l Response Message
NE 2008-01-01 11:37:18 M C COMPLD ;
Related Commands
A.5.3 DLT-EQPT
A.5.2 ED-EQPT
A.5.4 RTRV-EQPT
A.5.2 ED-EQPT
Edits attributes of a unit in an NE.
Function
This command edits attributes of a unit in an NE. The following attributes can be modified:
l State of the equipment
l Upper temperature threshold
l Lower temperature threshold
The TYPE/WORKMODE parameter cannot be set with other parameters at the same time.
Parameters other than TYPE/WORKMODE can be set at the same time.
Usage Note
This command is only applicable in modifying the unit type during unit upgrade, not during
normal circumstances.
The state of the unit, the port, or the SFP must be OOS-MA, OOS-AUMA or AINS before TYPE
or interface type is modified.
Category
Equipment
Security
Provisioning
Command Syntax
ED-EQPT:[<TID>]:<AID>:<CTAG>:::[PROVTYPE=<TYPE>,]
[WORKMODE=<WORKMODE>,][SVTPID=<SVTPID>,]
[UPTEMPTH=<UPTEMPTH>,][DOWNTEMPTH=<DOWNTEMPTH>,]
[FANSPEED=<FANSPEED>,][FANSPEEDMODE=<FANSPEEDMODE>,]
[MCASCANSPAN=<MCASCANSPAN>,][MCAMONTYPE=<MCAMONTYPE>],
[PWRTH=<PWRTH>],[SHELFLBL=<SHELFLBL>],[USERLBL=<USERLBL>]:
[[<PST>,][<SST>]];
Command Parameters
Parameter Description Default Value
<FANSPEED> Indicates the fan speed. The valid values are HIGH
HIGH, MID-HIGH, MID, MID-LOW, LOW,
and STOP.
This parameter is only valid for the fan card.
PWRTH The power threshold of the shelf. It is invalid 350 W for an OptiX OSN
for the card or SFP/XFP. 3800 shelf
The unit is watt (W). The power threshold can 1350 W for an OptiX
be a value in the range of: OSN 6800 shelf
l 1-350 W for an OptiX OSN 3800 shelf 2400 W for an OptiX
l 1-1350 W for an OptiX OSN 6800 shelf OSN 8800 T16, T32, or
T64 shelf
l 1-2400 W for an OptiX OSN 8800 T16,
T32, or T64 shelf
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Example
l Command
ED-EQPT::SLOT-1-1-7:C::::IS;
l Response Message
NE 2004-01-01 11:37:18 M C COMPLD ;
Related Commands
A.5.1 ENT-EQPT
A.5.4 RTRV-EQPT
A.5.3 DLT-EQPT
A.5.3 DLT-EQPT
Deletes equipment.
Function
This command deletes a unit.
Usage Note
Before users delete the equipment, the state of the equipment should be set to OOS-MA (OOS-
AUMA) or AINS.
Category
Equipment
Security
Provisioning
Command Syntax
DLT-EQPT:[<TID>]:<AID>:<CTAG>:::[INCL=<INCL>];
Command Parameters
Default
Parameter Description Value
<AID> Indicates the equipment unit identifier. The valid formats are as NA
follows:.
l For shelves: SHELF-<SHELF ID>
l For cards: SLOT-<SHELF ID>-<SLOT ID>
l For SFPs: SLOT-<SHELF ID>-<SLOT ID>-<PORT ID>
l For sub-boards, the valid format of <AID> is SLOT-
<SHELF ID>-<SLOT ID>-<PORT ID>. In the format, the
value of <PORT ID> for the TN55NPO2N board is 2 and
that for the TN55NPO2E board is 5 because both the boards
support only one sub-board (the sub-board type is 54PQ2).
An example of the command is as follows: DLT-
EQPT::SLOT-1-3-2:C
The valid values of <AID> for specific units are provided in A.
32.2.7 EQPT.
NOTE
The shelf can be deleted only after all configurable cards are deleted.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Example
l Command
DLT-EQPT::SLOT-1-2:C:::INCL=Y
l Response Message
NE 2004-01-01 11:37:18 M C COMPLD ;
Related Commands
A.5.1 ENT-EQPT
A.5.2 ED-EQPT
A.5.4 RTRV-EQPT
A.5.4 RTRV-EQPT
Retrieves information about equipment.
Function
This command retrieves all the attributes of a piece of given equipment.
Usage Note
Parameters <SN>, <CLEI>, <DOM>, <PCBVER>, <SWVER>, <FPGAVER>, <BIOSVER>,
<DESCR> are displayed only when the physical unit is online.
In the case of SFP, nothing is entered for parameters <SWVER>, <FPGAVER>, <BIOSVER>,
<PCBVER>, <SVTPID>, <FANSPEEDMODE>, <FANSPEED>, and <MCASCANSPAN>
are null.
When retrieving the attributes of SHELF-<SHELF ID>, the attributes of the slot units and the
SFPs which belong to the shelf will not be displayed. Similarly, when retrieving the attributes
of SLOT-<SHELF ID>-<SLOT ID>, the attributes of the SFPs which are located on the slot
unit will not be displayed.
Category
Equipment
Security
Retrieve
Command Syntax
RTRV-EQPT:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ^^^"<AID>::
[FILTER=<FILTER>,][PROVTYPE=<TYPE>,][ACTTYPE=<TYPE>,][UPTEMPTH=<UPTEMPTH>,]
[DOWNTEMPTH=<DOWNTEMPTH>,][SWITCHSTATE=<SWITCHSTATE>,][SN=<SN>,][CLEI=<CLEI>,]
[PARTNUM=<PARTNUM>,][DOM=<DOM>,][PCBVER=<PCBVER>,][SWVER=<SWVER>,]
[FPGAVER=<FPGAVER>,][BIOSVER=<BIOSVER>,][MODVER=<MODVER>,][WORKMODE=<WORKMODE>,]
[SVTPID=<SVTPID>,][FANSPEED=<FANSPEED>,][FANSPEEDMODE=<FANSPEEDMODE>,]
[MCASCANSPAN=<MCASCANSPAN>,][MCAMONTYPE=<MCAMONTYPE>,][RATEDPWR=<RATEDPWR>,]
[ACTPWR=<ACTPWR>,][PWRTH=<PWRTH>,][USEDCRS=<USEDCRS>,][DESCR=<DESCR>,]
[SHELFLBL=<SHELFLBL>,][USERLBL=<USERLBL>]:<PST>,[<SST>]"<cr><lf> ;
Response Parameters
Parameter Description
<AID> Indicates the equipment unit identifier. The valid formats are as
follows:
l For shelves: SHELF-<SHELF ID>.
l For cards: SLOT-<SHELF ID>-<SLOT ID>.
l For SFPs: SLOT-<SHELF ID>-<SLOT ID>-<PORT ID>
l For sub-boards, the valid format of AID is SLOT-<SHELF ID>-
<SLOT ID>-<PORT ID>.
Parameter Description
<FILTER> Indicates the parameters can be retrieved. The valid values are
CARDTYPE or ALL.
<SN> Indicates the serial number of the equipment/SFP. The valid value
is a string.
Parameter Description
<CLEI> Indicates the CLEI code of the equipment/SFP. The valid value is
a string.
<PARTNUM> Indicates the part number of the unit/SFP. The valid value is a
unique eight-digit number for each unit.
<PCBVER> Indicates the PCB version of the equipment. The valid value is a
string.
<SWVER> Indicates the software version and patch version of the equipment.
The valid value is a string, such as 3.14H001
<FPGAVER> Indicates the FPGA version of the equipment. The valid value is a
string.
<BIOSVER> Indicates the BIOS version of the equipment. The valid value is a
string.
<MODVER> Indicates the module version of the equipment. The valid value is a
string, such as (M1)XXX. If there are multiple modules, the
versions of the modules are displayed together.
<SVTPID> Indicates the service VLAN TPID field of the port. This parameter
is optional. It is only valid for the L4G and TBE.
<FANSPEED> Indicates the fan speed. The valid values are HIGH, MID, LOW,
MID-HIGH,MID-LOW and STOP. This parameter is editable in
MANUAL mode.
The parameter is only valid for the fan card.
<FANSPEEDMODE> Indicates the fan speed control mode. The valid values are AUTO
and MANUAL.
This parameter is only valid for the fan card.
Parameter Description
<MCASCANSPAN> Indicates the scan time span of the multi-channel spectrum analysis.
The valid values are from 5 to 49995; units are in minutes. The value
must be a multiple of five.
This parameter is only valid for the MCA card.
<MCAMONTYPE> Indicates the wavelength monitoring type. The valid values are as
follows:
l NRZDRZ
l 100GCRZ
l 50GCRZ
l 100G40G
l 50G40G
This parameter is only valid for the MCA card.
<RATEDPWR> Indicates the rated power consumption of the shelf and card.
<ACTPWR> Indicates the actual power consumption of the shelf and card.
Example
l Command
RTRV-EQPT::SLOT-1-11:C;
l Response Message
NE 2008-10-12 15:54:55 M C COMPLD
"SLOT-1-11::PROVTYPE=11TQX,ACTTYPE=11TQX,UPTEMPTH=65,DOWNTEMPTH=0,SN=2102316115108
7000012,PARTNUM=02316115,DOM=2008-08-03,DESCR=\"OptiX OSN 6800,TN1M1TQX01,4 x 10G
Tributary Service Processing Board\",PCBVER=VER.B,SWVER=3.13,FPGAVER=(U6)120(U14)
200(U15)200,BIOSVER=2.26/2.62,RATEDPWR=72,ACTPWR=72:IS-NR" ;
Related Commands
A.5.1 ENT-EQPT
A.5.2 ED-EQPT
A.5.3 DLT-EQPT
A.5.5 RTRV-ETH-EQPT
Queries the attributes of Ethernet equipment.
Function
This command queries the attributes of Ethernet equipment.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-ETH-EQPT:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::BDMAC=<BDMAC>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-ETH-EQPT::SLOT-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"SLOT-1-1::BDMAC=00-00-00-00-00-01"
;
Related Commands
A.13.4.1 ENT-VB
A.13.4.2 ED-VB
A.13.4.3 DLT-VB
A.6.1 ED-<FCMOD2>
Edits the attributes of the FC logical facility.
Function
This command edits the attributes of the FC.
Usage Note
<FCMOD2> includes FC100, FC200, FC400, FC800 and FC1200.
Category
Facility
Security
Provisioning
Command Syntax
ED-<FCMOD2>:[<TID>]:<AID>:<CTAG>:::[ EXTERN=<EXTERN>],
[DELAYTIME=<DELAYTIME>]:[<PST>];
Command Parameters
Default
Parameters Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-FC100::CLNT-1-8-1-1:C::::oos;
l Response Message
NE 2008-09-03 09:01:04
M C COMPLD
;
Related Commands
A.6.2 RTRV-<FCMOD2>
A.6.2 RTRV-<FCMOD2>
Retrieves the attributes of the FC logical facility.
Function
This command retrieves the attributes of the FC logical facility.
Usage Note
<FCMOD2> includes FC100, FC200, FC400, FC800 and FC1200.
Category
Facility
Security
Retrieve
Command Syntax
RTRV-<FCMOD2>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parame Description Default
ter Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::[EXTERN=<EXTERN>],[DELAYTIME=<DELAYTIME>],
[SWITCHSTATE=<SWITCHSTATE>]:<PST>,<SST>"<cr><lf>
;
Response Parameters
Parameters Description
<DELAYTIME> This parameter is only valid for the channels in an SNCP group.
Indicates the delay time (hold-off time). It is an integer ranging from
0 to 100, which is expressed in 0.1 seconds.
Delay time is required when multiple protection schemes are
configured. Switching is not initiated until the delay time is expended
when a malfunction is discovered at a port.
Use the default value when only one type of protection is configured.
<SWITCHSTATE Indicates the state of the switching. It is only valid when the port is in
> the protection group. The valid values are provided in A.32.3.20
SWITCHSTATE.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-FC100::CLNT-1-8-1-1:C;
l Response Message
NE 2008-09-03 09:01:12
M C COMPLD
"CLNT-1-8-1-1::EXTERN=DISABLE:OOS-AUMA,SGEO"
;
Related Commands
A.6.1 ED-<FCMOD2>
A.6.3 ED-<OCN/STMN>
Edits the attributes of the SONET OCN/STMN.
Function
This command edits the attributes of the SONET OCN/STMN.
Usage Note
OCN includes OC3, OC12, OC48, OC192 and OC768. STMN includes STM1, STM4, STM16,
STM64 and STM256.
Category
Facility
Security
Provisioning
Command Syntax
ED-<OCN/STMN>:[<TID>]:<AID>:<CTAG>:::[B1SFBER=<B1SFBER>],
[B1SDBER=<B1SDBER>],[TRCJ0MODE=<TRCJ0MODE>],
[TRCJ0FMT=<TRCJ0FMT>],[TRCJ0=<TRCJ0>],[EXPTRCJ0=<EXPTRCJ0>],
[PRBS=<PRBS>],[DELAYTIME=<DELAYTIME>]:[<PST>];
Command Parameters
Default
Parameter Description Value
<B1SFBER> Indicates the SF BER threshold for the overhead byte 1E-3
(B1) on a facility. The valid value ranges from 1E-5 to
1E-3.
<B1SDBER> Indicates the SD BER threshold for the overhead byte 1E-6
(B1) on a facility. The valid value ranges from 1E-9 to
1E-5.
Default
Parameter Description Value
<TRCJ0MODE> Indicates the trace J0 mode. The valid values are as MAN
follows:
l MAN: The manually provisioned string is used as the
expected string.
l DISABLE: Ability to trace the path is disabled so
there is not any reported data.
<PRBS> During a PRBS test in the OCN mode, the transmitted OFF
PRBS code streams are not valid OCN frames. Enable
the PRBS test mode on the receive side so that the test
can be completed. The valid values are as follows:
l OFF: The PRBS test function is disabled.
l ON: The PRBS test function is enabled.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-OC12::CLNT-1-1-1-1:C:::TRCJ0FMT=64,TRCJ0=HWTEST;
l Response Message
NE 2008-06-01 11:37:18
M C COMPLD
;
Related Commands
A.6.4 RTRV-<OCN/STMN>
A.6.4 RTRV-<OCN/STMN>
Retrieves the attributes of the OCN/STMN facility.
Function
This command retrieves the attributes of the OCN/STMN facility.
Usage Note
OCN includes OC3, OC12, OC48, OC192 and OC768. STMN includes STM1, STM4, STM16,
STM64 and STM256.
Category
Facility
Security
Retrieve
Command Syntax
RTRV-<OCN>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::B1SFBER=<B1SFBER>,B1SDBER=<B1SDBER>,TRCJ0MODE=<TRCJ0MODE>,TRCJ0FMT=<TRC
J0FMT>,[TRCJ0=<TRCJ0>],EXPTRCJ0=<EXPTRCJ0>,INCTRCJ0=<INCTRCJ0>,[PRBS=<PRBS>],
[DELAYTIME=<DELAYTIME>],[SWITCHSTATE=<SWITCHSTATE>]:<PST>,<SST>"<cr><lf>
;
Response Parameters
Parameters Description
<B1SFBER> Indicates the SF BER threshold for the overhead byte (B1) on a facility.
The valid value ranges from 1E-5 to 1E-3. The default value is 1E-3.
<B1SDBER> Indicates the SD BER threshold for the overhead byte (B1) on a
facility. The valid value ranges from 1E-9 to 1E-5. The default value
is 1E-6.
<TRCJ0MODE> Indicates the trace J0 mode. The valid values are as follows:
l MAN: The manually provisioned string is used as the expected
string.
l DISABLE: Ability to trace the path is disabled so there is not any
reported data.
Parameters Description
<TRCJ0FMT> Indicates the format of the J0 byte to be transmitted. The valid values
are as follows:
l 1: indicates the 1-byte mode.
l 16: indicates the 16-byte mode.
l 64: indicates the 64-byte mode.
<TRCJ0> Indicates the J0 byte to be transmitted. The valid value depends on the
<TRCJ0FMT>. This parameter is only valid for cards that can generate
the J0 byte.
<PRBS> During a PRBS test in the OCN mode, the transmitted PRBS code
streams are not valid OCN/STMN frames. Enable the PRBS test mode
on the receive side so that the test can be completed.
l OFF: The PRBS test function is disabled.
l ON: The PRBS test function is enabled.
<DELAYTIME> This parameter is only valid for the channels in an SNCP group.
Indicates the delay time. It is an integer ranging from 0 to 100, which
is expressed in 0.1 seconds.
Delay time is required when multiple protection schemes are
configured. Switching is not initiated until the delay time is expended
when a malfunction is discovered at a port.
Use the default value when only one type of protection is configured.
<SWITCHSTATE Indicates the state of the switching. It is only valid when the port is in
> the protection group. The valid values are provided in A.32.3.20
SWITCHSTATE.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-OC3::CLNT-1-7-1-1:C;
l Response Message
NE 1990-01-03 08:34:44
M C COMPLD
"CLNT-1-7-1-1::B1SFBER=1E-3,B1SDBER=1E-6,TRCJ0MODE=DISABLE,TRCJ0FMT=16,EXPTRCJ0=
\" \",INCTRCJ0=\" \",PRBS=OFF,:OOS-AU,SGEO"
;
Related Commands
A.6.3 ED-<OCN/STMN>
A.6.5 RTRV-FECER-<OTUN>
Queries pre-FEC or post-FEC BER.
Function
This command queries pre-FEC or post-FEC BER.
Usage Note
OTUn includes OTU1, OTU2, OTU3, OTU5G, and OTU4.
Category
Facility
Security
Retrieve
Command Syntax
RTRV-FECER-<OTUN>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ^^^"<AID>::
[BEFECBER=<BEFECBER>],[AFTFECBER=<AFTFECBER>]"<cr><lf> ;
Response Parameters
Parameters Description
<BEFECBER> Indicates the pre-FEC BER, in the format of m.xE-n. In the format,
m.x stands for the coefficient, -n stands for the index, and there are at
most two decimal places. The parameter value is INVALID when a
BER is invalid.
<AFTFECBER> Indicates the post-FEC BER, in the format of m.xE-n. In the format,
m.x stands for the coefficient, -n stands for the index, and there are at
most two decimal places. The parameter value is INVALID when a
BER is invalid.
Example
l Command
RTRV-FECER-OTU1::SRV1-1-6-1:D;
l Response Message
NE 2008-01-03 09:18:24 M D COMPLD
"SRV1-1-6-1::BEFECBER=1.5E-6,AFTFECBER=1.5E-6" ;
Related Commands
A.14.3 ED-<OTUN>
A.6.6 ED-<TRAFFICMOD2>
Edits the attributes of the logical facility.
Function
This command edits the attributes of the logical facility.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-<TRAFFICMOD2>:[<TID>]:<AID>:<CTAG>:::[DELAYTIME=<DELAYTIME>]:
[<PST>];
Command Parameters
Default
Parameters Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-FICON::CLNT-1-6-1-1:C::::OOS;
l Response Message
NE 2008-06-01 12:37:18
M C COMPLD
;
Related Commands
A.6.7 RTRV-<TRAFFICMOD2>
A.6.7 RTRV-<TRAFFICMOD2>
Retrieves the attributes of the logical facility.
Function
This command retrieves the attributes of the logical facility.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-<TRAFFICMOD2>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Default
Parameters Description Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ^^^"<AID>::
[DELAYTIME=<DELAYTIME>],[SWITCHSTATE=<SWITCHSTATE>]:<PST>,<SST>"<cr><lf> ;
Response Parameters
Parameters Description
<DELAYTIME> This parameter is only valid for the channels in an SNCP group.
Indicates the delay time. It is an integer ranging from 0 to 100, which
is expressed in 0.1 seconds.
Delay time is required when multiple protection schemes are
configured. Switching is not initiated until the delay time is expended
when a malfunction is discovered at a port.
Use the default value when only one type of protection is configured.
<SWITCHSTATE Indicates the state of switching. It is valid only when the port is in the
> protection group. The valid values are provided in A.32.3.20
SWITCHSTATE.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-FICON::CLNT-1-6-1-1:D;
l Response Message
NE 2008-10-06 18:25:59 M D COMPLD "CLNT-1-6-1-1:::OOS-AUMA,SGEO" ;
Related Commands
A.6.6 ED-<TRAFFICMOD2>
A.6.8 ED-CLNT
Edits the attributes of the logical client facility.
Function
This command edits the attributes of the facility.
Usage Note
When the TQX board accesses services through the LP3 and LP4 optical interfaces on the client
side, it must be housed in slot 1, slot 4, slot 11, or slot 14 when deploying an OSN6800A device.
Category
Facility
Security
Provisioning
Command Syntax
ED-CLNT:[<TID>]:<AID>:<CTAG>:::[WORKMODE=<WORKMODE>],
[PLDTYPE=<PLDTYPE>],[RATE=<RATE>];
Command Parameters
Parameters Description Default Value
OTU1->ODU1->n*ANY->2*ODU0->cross-
connect board.
l OTU1-ANY-ODU0-OTU1: indicates that the
board functions as a line and tributary board
and receives the ODU1 service. The service
mapping trail is OTU1->ODU1->n*ANY-
>2*ODU0->ODU1->OTU1->line side.
l ANY-OTU1: indicates that the board functions
as a line and tributary board and receives the
ODU1 service. In non-cascading mode, the
service mapping trail is OTU1/ANY->ODU1-
>OTU1->line side. In cascading mode, the
service mapping trail is n*ANY->ODU1-
>OTU1->line side.
l ANY-ODUFLEX-NONAGGR:service
package that enables 8 x GE services to be
encapsulated into ODU0 services.
For the 54TOA, 54THA, 11LOA, 55TQX, and
53TDX boards, valid values are as follows:
l NONE: indicates that the port is not used. All
the boards support this mode.
l ANY-ODUFLEX: tributary ODUFlex mode.
In this mode, client-side signals (2.5 Gbit/s to
4.25 Gbit/s for 54TOA and 54THA, 8 Gbit/s to
10 Gbit/s for 53TDX and 55TQX) are
encapsulated into ODUFlex signals and then
output to the WDM side. The 54TOA, 54THA,
55TQX, and 53TDX boards support this mode.
l ANY-ODU2: tributary ODU2 non-
convergency mode. In this mode, 8 Gbit/s to
10 Gbit/s client-side signals are encapsulated
into ODU2 signals and then output to the
WDM side. The 55TQX and 53TDX boards
support this mode.
l OTU1-ODU0: tributary ODU1-ODU0 mode.
In this mode, a board functions as a tributary
board and receives the OTU1 service. The
service mapping trail is OTU1->ODU1-
>2*ODU0->cross-connection board. The
54TOA and 54THA boards support this mode.
l ANY-ODU0-NONAGGR: tributary ODU0
non-convergence mode. The service mapping
trail is Any -> ODU0 -> cross-connection
board. The 54TOA and 54THA boards support
this mode.
l ANY-ODU1-AGGR: tributary ODU1
convergence mode. The service mapping trail
l IBSDR
l CBR10G
l CPRI1
l CPRI2
l CPRI3
l 3GSDI
l HDSDIRBR
l 3GSDIRBR
NOTE
This parameter cannot be set with other parameters at
the same time.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-CLNT::CLNT-1-6-1-4:C:::PLDTYPE=ESCON;
l Response Message
NE 2008-11-11 21:32:07 M C COMPLD ;
Related Commands
A.6.9 RTRV-CLNT
A.6.9 RTRV-CLNT
Retrieves the attributes of the logical client facility.
Function
This command retrieves the attributes of the logical client facility.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-CLNT:[<TID>]:<AID>:<CTAG>;
Command Parameters
Paramet Description Default Value
er
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ^^^"<AID>::
[WORKMODE=<WORKMODE>,][PLDTYPE=<PLDTYPE>,][RATE=<RATE>]"<cr><lf> ;
Response Parameters
Parameters Description
Parameters Description
<WORKMOD Indicates the working mode and is applicable only to the 52TOM board.
E> If the value ends with ODUn, the board functions as a tributary board. In
this mode, the services are transmitted to the cross-connect board. If the
value ends with OTUn, the board functions as a line and tributary board.
In this mode, the service is not transmitted to the cross-connect board but
is output directly. The description of each value is as follows:
l NONE: indicates that the port is not used.
l ANY-ODU0/-ODU1: indicates that the board functions as a tributary
board and receives the ODU0 service. In non-cascading mode, the
service mapping trails is ANY->ODU0->cross-connect board, or
ANY->ODU0->ODU1->cross-connect board. In cascading mode, the
service mapping trail is n*ANY->2*ODU0->cross-connect board, or
n*ANY->2*ODU0->ODU1->cross-connect board.
l ANY-ODU0-OTU1: indicates that the board functions as a line and
tributary board and receives the ODU0 service. In non-cascading mode,
the service mapping trail is ANY->ODU0->ODU1->OTU1->line side.
In cascading mode, the service mapping trail is n*ANY->2*ODU0-
>ODU1->OTU1->line side.
l ANY-ODU1: indicates that the board functions as a tributary board and
receives the ODU1 service. In non-cascading mode, the service
mapping trail is OTU1/ANY->ODU1->cross-connect board. In
cascading mode, the service mapping trail is n*ANY->ODU1->cross-
connect board.
l OTU1-ANY-ODU0-ODU1: indicates that the board functions as a
tributary board and receives the ODU1 service. The service mapping
trails is OTU1->ODU1->n*ANY->2*ODU0->ODU1->cross-connect
board.
l OTU1-ODU0: indicates that the board functions as a tributary board
and receives the ODU1 service. The service mapping trail is OTU1-
>ODU1->2*ODU0->cross-connection board.
l OTU1-ANY-ODU0: indicates that the board functions as a tributary
board and receives the ODU1 service. The service mapping trail is
OTU1->ODU1->n*ANY->2*ODU0->cross-connect board.
l OTU1-ANY-ODU0-OTU1: indicates that the board functions as a line
and tributary board and receives the ODU1 service. The service
mapping trail is OTU1->ODU1->n*ANY->2*ODU0->ODU1-
>OTU1->line side.
l ANY-OTU1: indicates that the board functions as a line and tributary
board and receives the ODU1 service. In non-cascading mode, the
service mapping trail is OTU1/ANY->ODU1->OTU1->line side. In
cascading mode, the service mapping trail is n*ANY->ODU1->OTU1-
>line side.
l ANY-ODUFLEX-NONAGGR:service package that enables 8 x GE
services to be encapsulated into ODU0 services.
For the 54TOA, 54THA, 11LOA, 55TQX, and 53TDX boards, valid
values are as follows:
Parameters Description
l NONE: indicates that the port is not used. All the boards support this
mode.
l ANY-ODUFLEX: tributary ODUFlex mode. In this mode, client-side
signals (2.5 Gbit/s to 4.25 Gbit/s for 54TOA and 54THA, 8 Gbit/s to
10 Gbit/s for 53TDX and 55TQX) are encapsulated into ODUFlex
signals and then output to the WDM side. The 54TOA, 54THA,
55TQX, and 53TDX boards support this mode.
l ANY-ODU2: tributary ODU2 non-convergency mode. In this mode, 8
Gbit/s to 10 Gbit/s client-side signals are encapsulated into ODU2
signals and then output to the WDM side. The 55TQX and 53TDX
boards support this mode.
l OTU1-ODU0: tributary ODU1-ODU0 mode. In this mode, a board
functions as a tributary board and receives the OTU1 service. The
service mapping trail is OTU1->ODU1->2*ODU0->cross-connection
board. The 54TOA and 54THA boards support this mode.
l ANY-ODU0-NONAGGR: tributary ODU0 non-convergence mode.
The service mapping trail is Any -> ODU0 -> cross-connection board.
The 54TOA and 54THA boards support this mode.
l ANY-ODU1-AGGR: tributary ODU1 convergence mode. The service
mapping trail is Any -> ODU1 -> cross-connection board. The 54TOA
and 54THA boards support this mode.
l ANY-ODU1-NONAGGR: tributary ODU1 non-convergence mode.
The service mapping trail is 1.5–2.5 Gbit/s signals (including OTU1
signals) -> ODU1 -> cross-connection board. The 54TOA and 54THA
boards support this mode.
l ANY-ODU0(-ODU1)-OTU2: tributary ODU0 non-convergence
mode. The service mapping trail is ANY -> ODU0 -> [ODU1->]
ODU2-> OTU2 -> line side. The timeslot allocation mode of WDM-
side ports determines whether signals traverse ODU1. When the
consecutive timeslot allocation mode is used, signals traverse ODU1.
The 11LOA board supports the tributary ODU0 non-convergence
mode.
l ANY-ODU1-OTU2: tributary ODU1 non-convergence mode. The
service mapping trail is ANY/OTU1 -> ODU1 –> ODU2 -> OTU2->
line side. The 11LOA board supports this mode.
l OTU1-ODU0(-ODU1)-OTU2: tributary ODU1-ODU0 mode. The
service mapping trail is OTU1 -> ODU1 -> ODU0 ->(ODU1 ->) ODU2
-> OTU2->line side. The timeslot allocation mode of WDM-side ports
determines whether signals traverse ODU1. When the consecutive
timeslot allocation mode is used, signals traverse ODU1. The 11LOA
board supports this mode.
l ANY-ODUFLEX-OTU2: tributary ODUflex non-convergence mode.
The service mapping trail is ANY -> ODUFlex -> ODU2 -> OTU2 ->
line side. The 11LOA board supports this mode.
l ANY-OTU2: tributary ODU2 mode.The service mapping trail is ANY-
>ODU2->OTU2->line side. The 11LOA board supports this mode.
Parameters Description
NOTE
This parameter cannot be set with other parameters at the same time.
Parameters Description
<PLDTYPE> Indicates the service type that the port supports. The valid values are as
follows:
l GETH
l XGETH (For the TBE unit, there are two working modes: 10GE WAN
and 10GE LAN.)
l FETH
l OTU1
l OTU2
l OTU3
l OTU5G
l STM1
l STM4
l STM16
l STM64
l STM256
l OC3
l OC12
l OC48
l OC192
l OC768
l FC100
l FC200
l FC400
l FC800
l FC1200
l FICON
l FICONEXP(FICON Express)
l FICON4G
l HDSDI
l DVBASI(DVB-ASI)
l SDI
l ESCON
l FDDI
l ISC1G
l ISC2G
l ETR
l CLO
l IBSDR
l IBDDR
Parameters Description
l ANY
l IBSDR
l CBR10G
l CPRI1
l CPRI2
l CPRI3
l 3GSDI
l HDSDIRBR
l 3GSDIRBR
<RATE> Indicates the rate of a service type. It is applicable only to Any services.
Example
l Command
RTRV-CLNT::CLNT-1-6-1-4:C;
l Response Message
NE 2008-11-11 21:32:26
M C COMPLD
"CLNT-1-6-1-4::PLDTYPE=ESCON" ;
Related Commands
A.6.8 ED-CLNT
A.6.10 ED-LEDSTATE
Configures the status of the stat indicator on a board.
Function
This command configures the status of the stat indicator on a board.
Usage Note
None.
Category
Facility
Security
Provisioning
Command Syntax
ED-LEDSTATE:[<TID>]:<AID>:<CTAG>:::[LEDSTATE=<LEDSTATE>]
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ed-ledstate::slot-1-9:s:::ledstate=on;
l Response Message
NE 2011-06-13 08:59:05
M S COMPLD;
Related Commands
A.6.11 RTRV-LEDSTATE
A.6.11 RTRV-LEDSTATE
Queries the status of the stat indicator on a board.
Function
This command queries the status of the stat indicator on a board.
Usage Note
None.
Category
Facility
Security
Retrieve
Command Syntax
RTRV-LEDSTATE:[<TID>]:<AID>:<CTAG>
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::[LEDSTATE=<LEDSTATE>]"<cr><lf> ;
Response Parameters
None
Example
l Command
rtrv-ledstate::slot-1-9:s;
l Response Message
NE 2011-06-13 08:59:04
M S COMPLD
"SLOT-1-3::LEDSTATE=OFF";
Related Commands
A.6.10 ED-LEDSTATE
A.6.12 ED-EC
Edits the attributes of the physical electric facility.
Function
This command edits the attributes of the physical electric facility.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-EC:[<TID>]:<AID>:<CTAG>:::[PORTMEMO=<PORTMEMO>],
[PLDTYPE=<PLDTYPE>],[SVTIMER=<SVTIMER>]:[[<PST>],[<SST>]];
Command Parameters
Parameters Description Default Value
<PLDTYPE> Indicates the service type at the port. This parameter GETH
is only valid for cards that support Ethernet layer 2
processing. The valid values are as follows:
l FETH
l GETH
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-EC::FAC-1-8-3:C:::PLDTYPE=FETH;
l Response Message
NE 2008-11-11 21:12:53
M C COMPLD
;
Related Commands
A.6.13 RTRV-EC
A.6.13 RTRV-EC
Retrieves the attributes of the physical electric facility.
Function
This command retrieves the attributes of the physical electric facility.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-EC:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::[PORTMEMO=<PORTMEMO>],[SILKSCREEN=<SILKSCREEN>],TYPE=<TYPE>,
[PLDTYPE=<PLDTYPE>],SVTIMER=<SVTIMER>:<PST>,<SST>"<cr><lf>
;
Response Parameters
Parameters Description
<PORTMEMO> Indicates additional information about the optical port. It is a string that
consists of no more than 64 bytes. Usually it is used to identify the port
name.
<TYPE> Indicates the port type. Electrical ports can only serve as client-side
ports.
The valid value is CLIENT.
<PLDTYPE> Indicates the service type at the port. This parameter is only valid for
cards that support Ethernet layer 2 processing. The valid values are as
follows:
l FETH
l GETH
<SVTIMER> Indicates the signal validation timer; units are expressed in minutes. It
is valid only when Auto In-Service is supported. SVTIMER is a string
in an HH-MM format.
l HH: hour, which is an integer ranging from 0 to 48.
l MM: minute, which is an integer ranging from 0 to 59.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-EC::FAC-1-16-3:C;
l Response Message
AAAAA 1990-01-01 15:22:46
M C COMPLD
"FAC-1-16-3::PORTMEMO=\"\",TYPE=CLIENT,PLDTYPE=GETH,SVTIMER=00-15:OOS-
AU,AINS&SGEO"
;
>
Related Commands
A.6.12 ED-EC
A.6.14 ED-CFP
Edits the attributes of the physical optical carrier facility.
Function
This command edits the attributes of the physical optical carrier facility.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-CFP:[<TID>]:<AID>:<CTAG>:::[PORTMEMO=<PORTMEMO>],
[LSRSTATE=<LSRSTATE>],[ALS=<ALS>],[LOSTH=<LOSTH>],
[DELAYTIME=<DELAYTIME>],[SVTIMER=<SVTIMER>]:[[<PST>],[<SST>]];
Command Parameters
Parameter Description Default Value
<LSRSTATE> Indicates the status of the laser. The valid values are OPEN
OPEN and CLOSE.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-CFP::FAC-1-4-3:D:::ALS=ENABLE;
l Response Message
NE 2008-06-01 11:37:18
M C COMPLD
;
Related Commands
A.6.15 RTRV-CFP
A.6.15 RTRV-CFP
Retrieves the attributes of the physical optical carrier facility.
Function
This command retrieves the attributes of the physical optical carrier facility.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-CFP:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::[PORTMEMO=<PORTMEMO>],SILKSCREEN=<SILKSCREEN>,[LSRSTATE=<LSRSTATE>],
[ALS=<ALS>],[LOSTH=<LOSTH>],[DELAYTIME=<DELAYTIME>],
[SWITCHSTATE=<SWITCHSTATE>],SVTIMER=<SVTIMER>:<PST>,<SST>"<cr><lf>
;
Response Parameters
Parameters Description
Parameters Description
<LSRSTATE> Indicates the status of the laser. The valid values are OPEN and
CLOSE.
<ALS> Indicates the automatic laser shutdown flag. The valid values are
ENABLE and DISABLE.
<LOSTH> Indicates the threshold power value of the LOS. This parameter is only
valid for the DCP/OLP unit.
<LOSTH> is measured in units of 1.0 dBm.
<SWITCHSTATE Indicates the state of the switching. It is only valid when the port is in
> the protection group. The valid values are provided in A.32.3.20
SWITCHSTATE.
<SVTIMER> Indicates the signal validation timer; units are expressed in minutes. It
is valid only when Auto In-Service is supported. SVTIMER is a string
in an HH-MM format.
HH: hour, which is an integer ranging from 0 to 48.
MM: minute, which is an integer ranging from 0 to 59.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-CFP::FAC-1-7-3:C;
l Response Message
NE 1990-01-03 08:37:13
M C COMPLD
"FAC-1-7-3::PORTMEMO=\"\",SILKSCREEN=TX1/RX1
( IP3 ),LSRSTATE=CLOSE,ALS=ENABLE,SVTIMER=00-15:OOS-AU,AINS&SGEO"
;
Related Commands
A.6.14 ED-CFP
A.6.16 ED-OC
Edits the attributes of the physical optical carrier facility.
Function
This command edits the attributes of the physical optical carrier facility.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-OC:[<TID>]:<AID>:<CTAG>:::[PORTMEMO=<PORTMEMO>],
[LSRSTATE=<LSRSTATE>],[ALS=<ALS>],[OFC=<OFC>,][PLDTYPE=<PLDTYPE>],
[CLNTPLDTYPE=<CLNTPLDTYPE>],[MAXSPEED=<MAXSPEED>],
[LOSTH=<LOSTH>],[DELAYTIME=<DELAYTIME>],[TSMODE=<TSMODE>],
[SVTIMER=<SVTIMER>]:[[<PST>],[<SST>]];
Command Parameters
Parameter Description Default Value
<LSRSTATE> Indicates the status of the laser. The valid values are OPEN
OPEN and CLOSE.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-OC::FAC-1-4-3:D:::ALS=ENABLE,PLDTYPE=ANY,MAXSPEED=24700;
l Response Message
NE 2008-06-01 11:37:18
M C COMPLD
;
Related Commands
A.6.17 RTRV-OC
A.6.17 RTRV-OC
Retrieves the attributes of the physical optical carrier facility.
Function
This command retrieves the attributes of the physical optical carrier facility.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-OC:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::[PORTMEMO=<PORTMEMO>],SILKSCREEN=<SILKSCREEN>,[LSRSTATE=<LSRSTATE>],
[TYPE=<TYPE>],[ALS=<ALS>],[OFC=<OFC>],[PLDTYPE=<PLDTYPE>],
[CLNTPLDTYPE=<CLNTPLDTYPE>],[MAXSPEED=<MAXSPEED>],[ACTSPEED=<ACTSPEED>],
[LOSTH=<LOSTH>],[ELAYTIME=<DELAYTIME>],
[SWITCHSTATE=<SWITCHSTATE>],TSMODE=<TSMODE>,SVTIMER=<SVTIMER>:<PST>,<SST>"<cr><lf>
;
Response Parameters
Parameters Description
<LSRSTATE> Indicates the status of the laser. The valid values are OPEN and
CLOSE.
<TYPE> Indicates the port type. Colorless optical ports can only serve as client-
side ports.
The valid values are CLIENT and LINE.
<ALS> Indicates the automatic laser shutdown flag. The valid values are
ENABLE and DISABLE.
Parameters Description
<PLDTYPE> Indicates the service type at the port. This parameter is only valid for
Ethernet Layer 2 processing cards, LSX and transparent transmit cards
(LWX). The valid values are as follows:
l ANY
l GETH
l 10GETH (There are two working modes for TBE units: 10GE
WAN and 10GE LAN.)
l FETH
l OTU1
l OTU2
l OTU3
l OTU5G
l STM1
l STM4
l STM16
l STM64
l STM256
l OC3
l OC12
l OC48
l OC192
l OC768
l FC100
l FC200
l FC400
l FC1200
l FICON
l FICONEXP(FICON Express)
l FICON4G
l HDSDI
l DVBASI(DVB-ASI)
l SDI
l ESCON
l FDDI
l ISC1G
l ISC2G
l ETR
l CLO
Parameters Description
Only FETH, GETH, and 10GETH are valid values for layer 2
processing cards.
All the preceding values are valid for the transparent transmit card.
MAXSPEED is invalid (not displayed upon query) when PLDTYPE
is not set to ANY.
<CLNTPLDTYPE Indicates the service type at the client side. This parameter is only valid
> for cards which support OTUk services on the client side.
<MAXSPEED> Indicates the maximum bearer rate of client services. This parameter
is only valid for transparent transmit cards such as the TN12LWXS.
The value is expressed in Mbit/s. MAXSPEED is valid when
PLDTYPE is set to ANY.
<ACTSPEED> Indicates the actual bit rate of client services. The value is expressed
in Mbit/s.
<LOSTH> Indicates the threshold power value of the LOS. This parameter is only
valid for the DCP/OLP unit.
<LOSTH> is measured in units of 1.0 dBm.
<SWITCHSTATE Indicates the state of the switching. It is only valid when the port is in
> the protection group. The valid values are provided in A.32.3.20
SWITCHSTATE.
<TSMODE> Indicates the timeslot allocation mode. The valid values are as follows:
l FIX: The number of timeslots allocated is fixed.
l RANDOM: The number of timeslots allocated is random.
<SVTIMER> Indicates the signal validation timer; units are expressed in minutes. It
is valid only when Auto In-Service is supported. SVTIMER is a string
in an HH-MM format.
HH: hour, which is an integer ranging from 0 to 48.
MM: minute, which is an integer ranging from 0 to 59.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-OC::FAC-1-7-3:C;
l Response Message
NE 1990-01-03 08:37:13
M C COMPLD
"FAC-1-7-3::PORTMEMO=\"\",SILKSCREEN=TX1/RX1
( IP3 ),LSRSTATE=CLOSE,TYPE=CLIENT,ALS=ENABLE,SVTIMER=00-15:OOS-AU,AINS&SGEO"
;
Related Commands
A.6.16 ED-OC
A.6.18 ED-OCH
Edits the attributes of the physical OCH facility.
Function
This command edits the attributes of the physical OCH facility.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-OCH:[<TID>]:<AID>:<CTAG>:::[PORTMEMO=<PORTMEMO>],
[LSRSTATE=<LSRSTATE>],[TYPE=<TYPE>],[ALS=<ALS>],[OFC=<OFC>],
[BANDTYPE=<BANDTYPE>],[WVNUM=<WVNUM>],
[ADBANDTYPE=<ADBANDTYPE>],[ADWVNUM=<ADWVNUM>],
[EXPBANDTYPE=<EXPBANDTYPE>],[EXPWVNUM=<EXPWVNUM>],
[PLDTYPE=<PLDTYPE>],[CLNTPLDTYPE=<CLNTPLDTYPE>],
[MAXSPEED=<MAXSPEED>],[LOSTH=<LOSTH>],[EXPPWR=<EXPPWR>],
[ATTEN=<ATTEN>],[VOAOFFSET=<VOAOFFSET>],[DELAYTIME=<DELAYTIME>],
[TSMODE=<TSMODE>],[SVTIMER=<SVTIMER>]:[[<PST>],[<SST>]];
Command Parameters
Default
Parameters Description Value
<LSRSTATE> Indicates the status of the laser. The valid values are OPEN
OPEN and CLOSE.
<BANDTYPE> Indicates the working band of the port. The valid values NA
are CBAND and CWDMBAND.
<EXPBANDTYP Indicates the expected receive band at the port. The valid NA
E> values are CBAND, CWDMBAND, and TX. The value
TX indicates that the expected receive band is the same
as the transmit band.
Default
Parameters Description Value
Default
Parameters Description Value
Default
Parameters Description Value
l CLO
Only FETH, GETH, and 10GETH are valid values for
Layer 2 processing cards.
All the preceding values are valid for transparent transmit
cards. MAXSPEED is invalid (not displayed upon query)
unless PLDTYPE is set to ANY.
NOTE
This parameter cannot be set with other parameters at the same
time.
<CLNTPLDTYP Indicates the service type at the client side. This parameter NA
E> is only valid for the card that supports the OTUk services
on the client side.
The valid values are OTN and CLIENT.
Default
Parameters Description Value
<SVTIMER> Indicates the signal validation timer; units are expressed 00-15
in minutes. It is valid only when Auto In-Service is
supported. SVTIMER is a string in an HH-MM
(00-15...48-00) format.
l HH: hour
l MM: minute
<SST> Indicates the secondary state. The valid values are AINS, NA
SB, and SB-DEA. It can be set to SB if the entity is in
OOS-MA; no outgoing traffic is allowed and incoming
traffic is ignored. When PWRMODE is set to SAVING,
the port is in the power-saving state.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-OCH::FAC-1-4-3:C:::PLDTYPE=FETH;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.6.19 RTRV-OCH
A.6.19 RTRV-OCH
Retrieves the attributes of the physical OCH facility.
Function
This command retrieves the attributes of the physical OCH facility
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-OCH:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::[PORTMEMO=<PORTMEMO>],SILKSCREEN=<SILKSCREEN>,[LSRSTATE=<LSRSTATE>],
[TYPE=<TYPE>],[ALS=<ALS>],[OFC=<OFC>],[BANDTYPE=<BANDTYPE>],[WVNUM=<WVNUM>],
[ACTBANDTYPE=<ACTBANDTYPE>],[ACTWVNUM=<ACTWVNUM>],[ADBANDTYPE=<ADBANDTYPE>],
[ADWVNUM=<ADWVNUM>],[ADWV=<ADWV>],[ACTADBANDTYPE=<ACTADBANDTYPE>],
[ACTADWVNUM=<ACTADWVNUM>],[ACTADWV=<ACTADWV>],[WVNUMRANGE=<WVNUMRANGE>],
[PLDTYPE=<PLDTYPE>],[CLNTPLDTYPE=<CLNTPLDTYPE>],[MAXSPEED=<MAXSPEED>],
[ACTSPEED=<ACTSPEED>],[LOSTH=<LOSTH>],[EXPPWR=<EXPPWR>],[ATTEN=<ATTEN>],
[MINATTEN=<MINATTEN>],[MAXATTEN=<MAXATTEN>],[DELAYTIME=<DELAYTIME>],
[SWITCHSTATE=<SWITCHSTATE>],[TSMODE=<TSMODE>],
[SVTIMER=<SVTIMER>]:<PST>,<SST>"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
<PORTMEMO> Indicates the optical port memo. It is a string consists of not more than
64 bytes. Usually it is used to identify the port name.
<LSRSTATE> Indicates the status of the laser. The valid values are OPEN and CLOSE.
<TYPE> Indicates the port type (client-side or line-side). The valid values are as
follows:
l CLIENT
l LINE
<ALS> Indicates whether the automatic laser shutdown is enabled. The valid
values are ENABLE and DISABLE.
<OFC> Indicates whether OFC is enabled. This parameter is only valid to ISC1G
and ISC2G services. The valid values are ENABLE and DISABLE.
<BANDTYPE> Indicates the working band of the port. The valid values are CBAND and
CWDMBAND.
<ACTBANDTYP Indicates the actual working band of the port. The valid values are
E> CBAND and CWDMBAND (Coarse Wavelength Division
Multiplexing Band).
<ADBANDTYP Indicates the band type of add/drop wavelengths. The valid values are
E> CBAND and CWDMBAND. This parameter is only valid for the MR
series card.
<ADWVNUM> Indicates the add/drop wavelength number. This parameter is only valid
for the MR series card.
<ACTADBAND Indicates the actual band type of add/drop wavelengths. The valid values
TYPE> are CBAND and CWDMBAND. This parameter is only valid for the
MR series card.
<ACTADWVNU Indicates the actual add/drop wavelength number. This parameter is only
M> valid for the MR series card.
Parameter Description
<WVNUMRAN Indicates the actual operating wavelength range that the port supports.
GE> The range is expressed by using &&. For example, 1&&40.
<EXPBANDTYP Indicates the expected receive band at the port. The valid values are
E> CBAND, CWDMBAND, and TX. The value TX indicates that the
expected receive band is the same as the transmit band.
<EXPWVNUM> Indicates the number of the expected receive wavelength. The valid
values are from 1 to 80, and TX. The value TX indicates that the number
of the expected receive wavelength is the same as that of the transmit
wavelength.
Parameter Description
<PLDTYPE> Indicates the service type at the port. This parameter is only valid for the
Ethernet Layer 2 processing card (TBE and L4G) and the transparent
transmit card (LWX). The valid values are as follows:
l ANY
l GETH
l 10GETH (There are two working modes for TBE units: 10GE WAN
and 10GE LAN.)
l FETH
l OTU1
l OTU2
l OTU3
l OTU5G
l STM1
l STM4
l STM16
l STM64
l STM256
l OC3
l OC12
l OC48
l OC192
l OC768
l FC100
l FC200
l FC400
l FC1200
l FICON
l FICONEXP(FICON Express)
l FICON4G
l HDSDI
l DVBASI(DVB-ASI)
l SDI
l ESCON
l FDDI
l ISC1G
l ISC2G
l ETR
l CLO
Parameter Description
Only FETH, GETH, and 10GETH are valid values for layer 2 processing
cards.
All the preceding values are valid for transparent transmit cards.
MAXSPEED is invalid (not displayed upon query) unless PLDTYPE is
set to ANY.
<CLNTPLDTYP Indicates the service type at the client side. This parameter is only valid
E> for cards that support OTUk services on the client side.
<LOSTH> Indicates the threshold power value of the LOS. This parameter is only
valid for the DCP/OLP unit.
<LOSTH> is measured in units of 1.0 dBm.
<MAXSPEED> Indicates the maximum bearer rate of client services. This parameter is
only valid for transparent transmit cards such as the LWX. The value is
expressed in Mbit/s. MAXSPEED is valid when PLDTYPE is set to
ANY.
<ACTSPEED> Indicates the actual bit rate of client services. The value is expressed in
Mbit/s.
<ATTEN> Indicates the attenuation applied at the interface. The value is expressed
in dBm and is accurate to 0.1 dBm.
<DELAYTIME> This parameter is only valid for the ports of a protection group.
Indicates the delay time. It is an integer ranging from 0 to 100, which is
expressed in 0.1 seconds.
Delay time is required when multiple protection schemes are configured.
Switching is not initiated until the delay time is expended when a
malfunction is discovered at a port.
Use the default value when only one type of protection is configured.
<SWITCHSTAT Indicates the state of the switching. It is only valid when the port is in
E> the protection group. For the valid values of <SWITCHSTATE>, refer
to A.32.3.20 SWITCHSTATE.
<TSMODE> Indicates the timeslot allocation mode. The valid values are as follows:
l FIX: The number of timeslots allocated is fixed.
l RANDOM: The number of timeslots allocated is random.
Parameter Description
<SVTIMER> Indicates the signal validation timer; units are expressed in minutes. It
is valid only when Auto In-Service is supported. SVTIMER is a string
in an HH-MM format.
HH: hour, which is an integer ranging from 0 to 48.
MM: minute, which is an integer ranging from 0 to 59.
<PST> Indicates the status of the primary state qualifier. The valid values are IS
and OOS.
Example
l Command
RTRV-OCH::FAC-1-2-1:D;
l Response Message
NE 2008-11-17 08:25:01
M D COMPLD
"FAC-1-2-1::PORTMEMO=\"\",SILKSCREEN=OUT1/IN1
( OP1 ),LSRSTATE=OPEN,BANDTYPE=CBAND,WVNUM=1,WV=196.05THz/
1529.16nm,ACTBANDTYPE=CBAND,ACTWVNUM=1,ACTWV=196.05THz/
1529.16nm,WVNUMRANGE=1&&80,SVTIMER=00-15:IS-NR"
;
Related Commands
A.6.18 ED-OCH
A.6.20 ED-OMS
Edits the attributes of the OMS facility.
Function
This command edits the attributes of the OMS facility.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-OMS:[<TID>]:<AID>:<CTAG>::::[[<PST>],[<SST>]];
Command Parameters
Default
Parameters Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-OMS::FAC-1-1-1:100::::OOS;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.6.25 RTRV-OTS
A.6.21 RTRV-OMS
Retrieves the attributes of the OMS facility.
Function
This command retrieves the attributes of the OMS facility.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-OMS:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>:::<PST>,<SST>"<cr><lf>
Response Parameters
Parameters Description
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-OMS::FAC-1-2-1:C;
l Response Message
AAAAA 2008-11-01 20:45:44
M C COMPLD
"FAC-1-2-1:::OOS-AUMA,SGEO"
;
Related Commands
A.6.24 ED-OTS
A.6.22 ED-OSC
Edits optical supervisory channel.
Function
This command edits the attributes of the OSC port.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-OSC:[<TID>]:<AID>:<CTAG>:::[PORTMEMO=<PORTMEMO>],
[LSRSTATE=<LSRSTATE>],[BEFECSDBER=<BEFECSDBER>],[DEGTH=<DEGTH>],
[DEGTIME=<DEGTIME>],[SVTIMER=<SVTIMER>]:[[<PST>],[<SST>]];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-OSC::FAC-1-2-1:C:::LSRSTATE=OPEN;
l Response Message
NE 2008-06-01 11:37:18
M C COMPLD
;
Related Commands
A.6.23 RTRV-OSC
A.6.23 RTRV-OSC
Retrieves optical supervisory channel.
Function
This command retrieves the attribute of the OSC port.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-OSC:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::[PORTMEMO=<PORTMEMO>],SILKSCREEN=<SILKSCREEN>,[LSRSTATE=<LSRSTATE>],
[WV=<WV>],[BEFECSDBER=<BEFECSDBER>],[DEGTH=<DEGTH>],
[DEGTIME=<DEGTIME>],SVTIMER=<SVTIMER>:<PST>,<SST>"<cr><lf>
;
Response Parameters
Parameters Description
<PORTMEMO> Indicates additional information about the optical port. It is a string that
consists of no more than 64 bytes. Usually it is used to identify the port
name.
<LSRSTATE> Indicates the status of the laser. The valid values are OPEN and CLOSE.
<WV> Indicates the operating wavelength information of the port. The valid
format is frequency/wavelength: xxxxTHz/xxxnm.
<BEFECSDBER> Indicates the SD threshold before FEC. The valid value ranges from
1E-12 to 1E-1. The default value is 1E-4.
Parameters Description
<SVTIMER> Indicates the signal validation timer; units are expressed in minutes. It
is valid only when Auto In-Service is supported. SVTIMER is a string
in an HH-MM format.
HH: hour, which is an integer ranging from 0 to 48.
MM: minute, which is an integer ranging from 0 to 59.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS (in-service) and OOS (out-of-service).
Example
l Command
RTRV-OSC::FAC-1-2-1:C;
l Response Message
NE 2008-06-01 11:37:18
M C COMPLD
"FAC-1-2-1::PORTMEMO=\"\",SILKSCREEN=TM1/RM1,SVTIMER=00-15:OOS-AU,AINS&SGEO"
;
Related Commands
A.6.22 ED-OSC
A.6.24 ED-OTS
Edits the attributes of the OTS facility.
Function
This command edits the attributes of the OTS facility.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-OTS:[<TID>]:<AID>:<CTAG>:::[TIMACT=<TIMACT>],
[TIMMODE=<TIMMODE>],[EXPTTISAPI=<EXPTTISAPI>],
[EXPTTIDAPI=<EXPTTIDAPI>],[TTISAPI=<TTISAPI>],[TTIDAPI=<TTIDAPI>],
[TTIOPER=<TTIOPER>]:[[<PST>],[<SST>]];
Command Parameters
Default
Parameters Description Value
Default
Parameters Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-OTS::FAC-1-1-1:100:::TIMACT=ENABLE,TIMMODE=SAPI;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.6.25 RTRV-OTS
A.6.25 RTRV-OTS
Retrieves the attributes of the OTS facility.
Function
This command retrieves the attributes of the OTS facility.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-OTS:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::TIMACT=<TIMACT>,TIMMODE=<TIMMODE>,EXPTTISAPI=<EXPTTISAPI>,EXPTTIDAPI=<E
XPTTIDAPI>,TTISAPI=<TTISAPI>,TTIDAPI=<TTIDAPI>,TTIOPER=<TTIOPER>,INCTTISAPI=<INCTT
ISAPI>,INCTTIDAPI=<INCTTIDAPI>,INCTTIOPER=<INCTTIOPER>:<PST>,<SST>"<cr><lf>
Response Parameters
Parameters Description
Parameters Description
Parameters Description
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-OTS::FAC-1-2-1:C;
l Response Message
AAAAA 2008-11-01 20:45:44
M C COMPLD
"FAC-1-2-1::TIMACT=DISABLE,TIMMODE=OFF,EXPTTISAPI="AA",EXPTTIDAPI="BB",TTISAPI="CC
",TTIDAPI="",TTIOPER="",INCTTISAPI="",INCTTIDAPI="",INCTTIOPER="":OOS-AUMA,SGEO"
;
Related Commands
A.6.24 ED-OTS
A.6.26 ED-WDM
Edits the attributes of the WDM.
Function
This command edits the attributes of the WDM.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-WDM:[<TID>]:<AID>:<CTAG>:::[PORTMEMO=<PORTMEMO>],
[LSRSTATE=<LSRSTATE>],[ALS]=<ALS>,[PROWORKBAND=<PROWORKBAND>],
[AUTOBLCK=<AUTOBLCK>],[RATEDPOWER=<RATEDPOWER>],
[STDGAIN=<STDGAIN>],[SFTH=<SFTH>],[LOSTH=<LOSTH>],
[PWROFFSET=<PWROFFSET>],[ATTEN=<ATTEN>],
[VOAOFFSET=<VOAOFFSET>],[PMDCOEF=<PMDCOEF>],[CDCOEF=<CDCOEF>],
[FIBERTYPE=<FIBERTYPE>],[TXDC=<TXDC>],[RXDC=<RXDC>],
[DELAYTIME=<DELAYTIME>],[RLSTARTUPUPTH=<RLSTARTUPUPTH>],
[RLSTARTUPDOWNTH=<RLSTARTUPDOWNTH>],[RLALMUPTH=<RLALMUPTH>],
[RLALMDOWNTH=<RLALMDOWNTH>],[RLENABLE=<RLENABLE>],
[WORKMODE=<OAWORKMODE>],[OUTPWR=<OALOCKPWR>],
[SVTIMER=<SVTIMER>]:[[<PST>][,<SST>]];
Command Parameters
Default
Parameters Description Value
<LSRSTATE> Indicates the state of the laser. The valid values are OPEN OPEN
and CLOSE.
Default
Parameters Description Value
<FIBERTYPE> Indicates the fiber type. This parameter is only valid for NA
FIU ports and must be consistent with the type of fiber
used. This parameter is required by ASON. The valid
values are as follows:
G652
LEAF
TW-RS
TW-C
TWPLUS
G653
SMF-LS
G654B
G656
G654A
Tera_light
Default
Parameters Description Value
<WORKMODE> Indicates the work mode of the amplifier board.The valid LOCKGAI
value is LOCKGAIN/LOCKPWR/MAXGAIN/ N
PLLOCKPWR.
Default
Parameters Description Value
<SVTIMER> Indicates the signal validation timer; units are expressed 00-15
in minutes. This parameter is only valid if the Auto In-
Service feature is supported. SVTIMER is a string in an
HH-MM format.
l HH: hour, which is an integer ranging from 0 to 48.
l MM: minute, which is an integer ranging from 0 to 59.
The maximum timer setting is 48 hours.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-WDM::FAC-1-1-2:C::::IS;
l Response Message
NE 2004-01-01 11:37:18 M C COMPLD ;
Related Commands
A.6.27 RTRV-WDM
A.6.27 RTRV-WDM
Retrieves the attributes of the WDM.
Function
This command retrieves the attributes of the WDM.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-WDM:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ^^^"<AID>::
[PORTMEMO=<PORTMEMO>],SILKSCREEN=<SILKSCREEN>,[LSRSTATE=<LSRSTATE>],[ALS=<ALS>],
[ACTGAIN=<ACTGAIN>],[STDGAIN=<STDGAIN>],[MAXGAINTH=<MAXGAINTH>],
[MINGAINTH=<MINGAINTH>],[ACTMAXGAINTH=<ACTMAXGAINTH>],
[ACTMINGAINTH=<ACTMINGAINTH>],[AUTOBLCK=<AUTOBLCK>],[RATEDPOWER=<RATEDPOWER>],
[PROWORKBAND=<PROWORKBAND>],[ACTWORKBAND=<ACTWORKBAND>],[SFTH=<SFTH>],
[LOSTH=<LOSTH>],[PWROFFSET=<PWROFFSET>],[ATTEN=<ATTEN>],[MINATTEN=<MINATTEN>],
[MAXATTEN=<MAXATTEN>],[PMDCOEF=<PMDCOEF>],[CDCOEF=<CDCOEF>],
[FIBERTYPE=<FIBERTYPE>],[TXDC=<TXDC>],[RXDC=<RXDC>],[DELAYTIME=<DELAYTIME>],
[RLSTARTUPUPTH=<RLSTARTUPUPTH>],[RLSTARTUPDOWNTH=<RLSTARTUPDOWNTH>],
[RLALMUPTH=<RLALMUPTH>],[RLALMDOWNTH=<RLALMDOWNTH>],[RLENABLE=<RLENABLE>],
[WORKMODE=<OAWORKMODE>],[OUTPWR=<OALOCKPWR>],[SWITCHSTATE=<SWITCHSTATE>],
[SVTIMER=<SVTIMER>]:<PST>,<SST>"<cr><lf>
Response Parameters
Parameters Description
Parameters Description
<LSRSTATE> Indicates the state of the laser. The valid values are OPEN and
CLOSE.
<STDGAIN> Indicates the standard gain of the optical amplifier. This parameter
is only valid for the OA unit. The unit is 1.0 dB.
<MAXGAINTH> Indicates the maximum threshold of the gain. The unit is 1.0 dB.
This parameter is only valid for the OA unit.
<MINGAINTH> Indicates the minimum threshold of the gain. The unit is 1.0 dB.
This parameter is only valid for the OA unit.
<ACTMAXGAINTH The actual maximum threshold of the gain. Only for the OA unit.
> The parameter value INVALID indicates that the dispersion
compensation value exceeds the upper limit.
<ACTMINGAINTH> The actual minimum threshold of the gain. Only for the OA unit.
The parameter value INVALID indicates that the dispersion
compensation value exceeds the lower limit.
<RATEDPOWER> Indicates the rated power of the laser. This parameter only is valid
for the OA unit.
<ACTWORKBAND> Indicates the actual operating wavelength band type. The valid
values are as follows:
l C-ALL: indicates all C band wavelengths.
l C-ODD: indicates all C band odd wavelengths.
l C-EVEN: indicates all C band even wavelengths.
Parameters Description
<SFTH> Indicates the threshold optical power of the SF (signal fail). This
parameter is only valid for the DCP/OLP unit.
<LOSTH> Indicates the threshold power value of the LOS (Loss of Signal).
<LOSTH> is measured in units of 1.0 dBm.
<PWROFFSET> Indicates the original power offset between the working port and
protection port. This parameter is only valid for the DCP/OLP unit.
<FIBERTYPE> Indicates the fiber type. This parameter is only valid for FIU ports
and must be consistent with the type of fiber used. This parameter
is required by ASON. The valid values are as follows:
G652
LEAF
TW-RS
TW-C
TWPLUS
G653
SMF-LS
G654B
G656
G654A
Tera_light
Parameters Description
<DELAYTIME> This parameter is only valid for the ports of a protection group.
Indicates the delay time. It is an integer ranging from 0 to 100, which
is expressed in 0.1 seconds.
Delay time is required when multiple protection schemes are
configured. Switching is not initiated until the delay time is
expended when a malfunction is discovered at a port.
Use the default value when only one type of protection is
configured.
<RLSTARTUPUPTH The upper threshold of RL (Return Loss) to starting the pump. Only
> for the Raman unit.
<RLSTARTUPDOW The down threshold of RL (Return Loss) to starting the pump. Only
NTH> for the Raman unit.
<RLALMUPTH> The upper threshold of RL (Return Loss) alarm. Only for the Raman
unit.
<RLALMDOWNTH> The down threshold of RL (Return Loss) alarm. Only for the Raman
unit. RLALMDOWNTH <= RLSTARTUPDOWNTH <
RLSTARTUPUPTH <= RLALMUPTH.
<WORKMODE> Indicates the work mode of the amplifier board.The valid value is
LOCKGAIN/LOCKPWR/MAXGAIN/PLLOCKPWR
<SWITCHSTATE> Indicates the state of switching. It is only valid when the port is in
the protection group. The valid values are provided in A.32.3.20
SWITCHSTATE.
<SVTIMER> Indicates the signal validation timer; units are expressed in minutes.
This parameter is only valid if the Auto In-Service feature is
supported. SVTIMER is a string in an HH-MM format.
l HH: hour, which is an integer ranging from 0 to 48.
l MM: minute, which is an integer ranging from 0 to 59. The
maximum timer setting is 48 hours.
Example
l Command
RTRV-WDM::FAC-1-5-1:D;
l Response Message
NE 2008-11-13 10:38:47 M D COMPLD "FAC-1-5-1::PORTMEMO=\"\",SILKSCREEN=TO11/
RI11,LOSTH=-35.0,SVTIMER=00-15:OOS-AU,AINS&SGEO" ;
Related Commands
A.6.26 ED-WDM
A.6.28 RMV-<MOD2>
Removes the port or channel from service and places it into the maintenance state.
Function
This command changes the service state of the specified port (optical or electrical port) to Out
of Service - Maintenance (OOS-MA, MT). There are not any alarms generated for the
corresponding facility and the existing alarms must be cleared after this command is issued. All
conditions that are reported as NR and PM continue to be collected and marked as invalid. This
command is required before the loopback or PRBS test command is issued.
Usage Note
None
Category
Facility
Security
Maintenance
Command Syntax
RMV-<MOD2>:[<TID>]:<AID>:<CTAG>
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
RMV-OC::FAC-1-4-1:C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.6.29 RST-<MOD2>
A.6.29 RST-<MOD2>
Restores the port or channel back into service.
Function
This command instructs an NE to restore the facility to service. The entity is changed from a
maintenance state to the original state. Existing alarms are reported.
Usage Note
The WDM-side optical interfaces 1 and 2 have only one laser on the dual fed and selective
receiving unit. A loopback on any of the two interfaces makes the two turn to the loopback state
at the same time. Hence, after the loopback at optical interface 1 is released, modify the state to
IS manually if optical interface 2 is still in the MT or OOS state.
Category
Facility
Security
Maintenance
Command Syntax
RST-<MOD2>:[<TID>]:<AID>:<CTAG>
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
RST-OC::FAC-1-4-1:C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.6.28 RMV-<MOD2>
A.6.30 ED-PL
Edits the attributes of the Raman pump laser.
Function
This command modifies the attributes of the Raman pump laser.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-PL:[<TID>]:<AID>:<CTAG>:::[LOCKPOWER=<LOCKPOWER>],
[LSRSTATE=<LSRSTATE>];
Command Parameters
Parameter Description Default Value
<LSRSTAT Indicates the status of the laser. The valid values are CLOSE
E> OPEN and CLOSE.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-PL::FAC-1-120-1-1:C::: LOCKPOWER=6,LSRSTATE=OPEN;
l Response Message
NE 04-01-01 11:37:18
M C COMPLD
;
Related Commands
A.6.31 RTRV-PL
A.6.31 RTRV-PL
Retrieves the attributes of the Raman pump laser.
Function
This command retrieves the attributes of the Raman pump laser.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-PL:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::[LSRSTATE=<LSRSTATE>],[LOCKPOWER=<LOCKPOWER>],
[UPLOCKPOWERTH=<UPLOCKPOWERTH>],[DOWNLOCKPOWERTH=<DOWNLOCKPOWERTH>]"<cr><lf>
;
Response Parameters
Parameter Description
<AID> Indicates the equipment unit identity. The valid format is FAC-<SHELF
ID>-<SLOT ID>-<PORT ID>-<PATH ID>.
<LSRSTATE> Indicates the status of the laser. The valid values are OPEN and CLOSE.
<LOCKPOWER Indicates the locked power of the pump laser. This parameter only applies
> to Raman units. The valid value ranges from 5.0 to 30.0,and -60.0.
Example
l Command
rtrv-pl::fac-1-127-1-1:c;
l Response Message
NE 2009-01-12 09:17:22
M C COMPLD
"FAC-1-127-1-1::LSRSTATE=CLOSE,LOCKPOWER=20.0,UPLOCKPOWERTH=26.1,DOWNLOCKPOWERTH=2
0.0"
;
Related Commands
A.6.30 ED-PL
A.6.32 ED-VCG
Edits the attributes of the VCG facility.
Function
This command edits the attributes of the VCG facility.
Usage Note
The ED-VCG is used to edit the bandwidth at an inverse multiplexing port of the 10GE card.
Category
Facility
Security
Provisioning
Command Syntax
ED-VCG:[<TID>]:<AID>:<CTAG>::::[<PST>];
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-VCG::CLNT-1-7-1:C::::OOS;
l Response Message
NE 2008-11-13 15:33:04
M C COMPLD
;
Related Commands
A.6.33 RTRV-VCG
A.6.33 RTRV-VCG
Retrieves the attributes of the VCG facility.
Function
This command retrieves the attributes of the VCG facility.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-VCG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::PATHTYPE=<PATHTYPE>,UPPATH=<UPPATH>,DOWNPATH=<DOWNPATH>:<PST>,<SST>"<cr
><lf>
;
Response Parameters
Parameters Description
<PATHTYPE> Indicates the path type of VCG. The valid values are ODU1V and
ODU2V.
<UPPATH> Indicates the time slot number in the uplink direction, which is assigned
for the VCG ID. The initial digit of the value is 0 (0 means that the
path is cleared). The VCG member is changed only when it is set.
The value must be consecutive and start from 1. For example, 1&&4.
<DOWNPATH> Indicates the time slot number in the downlink direction, which is
assigned for the VCG ID. The initial digit of the value is 0 (0 means
that the path is cleared). The VCG member is changed only when it is
set.
The value must be consecutive and start from 1. For example, 1&&4.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-VCG::CLNT-1-7-1:C;
l Response Message
NE 2008-11-13 15:33:04
M C COMPLD
"CLNT-1-7-1::PATHTYPE=ODU2V,UPPATH=1&&4,DOWNPATH=1&&4,:OOS-AUMA,SGEO"
;
Related Commands
A.6.32 ED-VCG
A.6.34 ACT-CFG-TEMP
Sets service packages.
Function
This command sets service packages for a board.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ACT-CFG-TEMP:[<TID>]:<AID>:<CTAG>:::[TEMPNAME=<TEMPNAME>],
[ADDXCFLG=<ADDXCFLG>];
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Example
l Command
ACT-CFG-TEMP::FAC-1-1:D:::TEMPNAME=GE-ODU0-NONAGGR,ADDXCFLG=XC;
l Response Message
NE 2004-01-01 11:37:18 M C COMPLD ;
Related Commands
None
A.6.35 RTRV-PWR
Queries the optical power.
Function
This command queries the optical power of an optical port.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-PWR:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ^^^"<AID>::[OPR=<OPR>],
[OPT=<OPT>]"<cr><lf> ;
Response Parameters
Parameters Description
<OPR> Indicates the input optical power of the current optical port.
<OPT> Indicates the output optical power of the current optical port.
Example
l Command
RTRV-PWR::FAC-1-1-2:D;
l Response Message
NE-91-7 2011-01-22 11:57:11 M D COMPLD "FAC-1-1-2::OPR=-2.2" ;
Related Commands
None
A.6.36 RTRV-OPMOD
Retrieves the type of the optical module.
Function
This command retrieves the type of the optical module.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-OPMOD:[<TID>]:[<AID>]:<CTAG>
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf>
(^^^"<AID>::INBAND=<INBANDNOISE>"<cr><lf>)+
Response Parameters
Parameter Description
Example
l Command
RTRV-OPMOD::FAC-1-2-4:C;
l Response Message
NE 2004-01-01 11:37:18 M C COMPLD "FAC-1-2-4::NAME=TN11RAU1" ;
Related Commands
None
A.7.1 ENT-FIBER
Creates a logical fiber connection.
Function
This command creates a logical fiber connection between cards. The fiber connection is
directional
Usage Note
The source or sink port must be on the local NE.
Category
Facility
Security
Provisioning
Command Syntax
ENT-FIBER:[<TID>]:<SRCPORT>,<DSTPORT>:<CTAG>:::[SRCTID=<SRCTID>,]
[DSTTID=<DSTTID>];
Command Parameters
Parameters Description Default Value
<SRCTID> Indicates the source TID of the NE from which the fiber NA
is connected. If nothing is entered for this parameter, it
indicates that the source NE of the fiber connection to
be created is the local NE.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
Example
l Command
ENT-FIBER::FAC-1-13-1,FAC-1-13-1:C:::SRCTID=NE23,DSTTID=NE26;
l Response Message
NE714 2009-09-21 10:58:17
M C COMPLD
Related Commands
A.7.2 DLT-FIBER
A.7.3 RTRV-FIBER
A.7.2 DLT-FIBER
Deletes a logical fiber connection.
Function
This command deletes a logical fiber connection between cards. The fiber connection is
directional.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
DLT-FIBER:[<TID>]:<SRCPORT>,<DSTPORT>:<CTAG>:::[SRCTID=<SRCTID>,]
[DSTTID=<DSTTID>];
Command Parameters
Parameters Description Default Value
<SRCTID> Indicates the source TID of the NE from which the fiber NA
is connected. If nothing is entered for this parameter, it
indicates that the source NE of the fiber connection to be
deleted is the local NE.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
Example
l Command
DLT-FIBER::FAC-3-9-1,FAC-2-11-1:C:::SRCTID=NE1,DSTTID=NE2;
l Response Message
Related Commands
A.7.1 ENT-FIBER
A.7.3 RTRV-FIBER
A.7.3 RTRV-FIBER
Retrieves information about the logical fiber connection.
Function
This command retrieves information about the logical fiber connection.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-FIBER:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf>
^^^"<SRCPORT>,<DSTPORT>::SRCTID=<SRCTID>,DSTTID=<DSTTID>;" ;
Response Parameters
Parameters Description
<SRCPORT> Indicates the source port from which the fiber is connected.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT ID>.
<SRCTID> Indicates the source TID of the NE from which the fiber is connected.
<DSTTID> Indicates the destination TID of the NE to which the fiber is connected.
Example
l Command
RTRV-FIBER:::C;
l Response Message
NE714 2009-09-21 10:58:27 M C COMPLD
"FAC-2-3-1,FAC-3-2-1::SRCTID=NE1,DSTTID=NE2" ;
Related Commands
A.7.2 DLT-FIBER
A.7.1 ENT-FIBER
A.7.4 ENT-WMU-CONN
Creates the monitoring mapping for the wavelengths between the WMU and OTU.
Function
This command creates the monitoring mapping for the wavelengths between the WMU and
OTU.
Users need to create monitoring mapping for the wavelengths between the WMU and OTU by
running this command when logical connections between the WMU and OTU cannot be learnt
based on the existing fiber connection configuration (for example, no fiber connections are
created or inter-NE fiber connections exist).
When the NE can determine the logical connections between the WMU and OTU, it neglects
the monitoring mapping for the wavelengths between the WMU and OTU created by users.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ENT-WMU-CONN:[<TID>]:<WMUPORT>,<OTUPORT>:<CTAG>:::
[OTUNE=<OTUNE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ENT-WMU-CONN::FAC-2-3-1,FAC-1-2-1:C:::OTUNE=NE01
l Response Message
NE 1990-01-01 15:00:00
M C COMPLD
;
Related Commands
A.7.5 DLT-WMU-CONN
A.7.6 RTRV-WMU-CONN
A.7.5 DLT-WMU-CONN
Deletes a monitoring mapping for the wavelengths between the WMU and OTU.
Function
This command deletes a monitoring mapping for the wavelengths between the WMU and OTU.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
DLT-WMU-CONN:[<TID>]:<WMUPORT>,<OTUPORT>:<CTAG>:::
[OTUNE=<OTUNE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-WMU-CONN::FAC-2-3-1,FAC-1-2-1:C
l Response Message
NE 1990-01-01 15:00:00
M C COMPLD
;
Related Commands
A.7.4 ENT-WMU-CONN
A.7.6 RTRV-WMU-CONN
A.7.6 RTRV-WMU-CONN
Retrieves the monitoring mapping for the wavelengths between the WMU and the OTU.
Function
This command retrieves the monitoring mapping for the wavelengths between the WMU and
the OTU.
If a port number of the WMU is entered in the command, the system retrieves all the monitoring
mapping for the wavelengths between the port on the WMU and the ports/channels on the OTU
and returns the values in separate records.
If a port/channel number is entered in the command, the system retrieves the monitoring mapping
for the wavelengths between the port/channel on the OTU and the corresponding port on the
WMU.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-WMU-CONN:<TID>:[<AID>]:<CTAG>:::[OTUNE=<OTUNE>];
Command Parameters
Parameter Description Default Value
<OTUNE> Indicates the name of the TID of the NE where the OTU NA
is located. If nothing is entered for this parameter, it
indicates that the NE where the OTU is located is the
local NE.
The valid value is a string of less than or equal to 20
characters, which is composed of letters, digits and
hyphens. The string should begin with a letter and
cannot end with a hyphen.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
(^^^"<WMUPORT>,<OTUPORT>:::OTUNE=<OTUNE>" <cr><If>)
;
Response Parameters
Parameter Description
<OTUNE> Indicates the name of the TID of the NE where the OTU is
located.
The valid value is a string of less than or equal to 20
characters, which is composed of letters, digits and hyphens.
The string should begin with a letter and cannot end with a
hyphen.
Example
l Command
RTRV-WMU-CONN::FAC-2-2-1:C
l Response Message
NE 2005-01-01 01:01:00
M C COMPLD
"FAC-2-2-1,FAC-3-2-1:::OTUNE=NE-8;"
;
Related Commands
A.7.4 ENT-WMU-CONN
A.7.5 DLT-WMU-CONN
A.8.1.1 ENT-PXC-OCH
Creates a cross-connection (OCH).
Function
This command creates an OCH layer cross-connection.
Usage Note
None
Category
Cross-connection
Security
Provisioning
Command Syntax
ENT-PXC-OCH:[<TID>]:<FROM>,<TO>:<CTAG>::[<CCT>],[<CRSTYPE>]:
[BANDTYPE=<BANDTYPE>],WVNUM=<WVNUM>,[OPAMODE=<OPAMODE>],
[CONSTR=<CONSTR>][CKTID=<CKTID>]:,[<SST>];
Command Parameters
Parameter Description Default Value
<BANDTYPE> Indicates the type of the wave band. The default and CBAND
only available value for this parameter is CBAND.
<SST> Indicates the red-lined state. The valid values are RDLD-DEA
shown in section A.32.3.17 SST_STATE.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ENT-PXC-OCH::FAC-1-1-1,FAC-1-4-1:C::2WAY,E2E:WVNUM=1,CKTID=A1:,RDLD;
l Response Message
NE 2008-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.8.1.3 DLT-PXC-OCH
A.8.1.2 ED-PXC-OCH
A.8.1.4 RTRV-PXC-OCH
A.8.1.2 ED-PXC-OCH
Edits a cross-connection (OCH).
Function
This command modifies an OCH layer cross-connection.
Usage Note
None
Category
Cross-connection
Security
Provisioning
Command Syntax
ED-PXC-OCH:[<TID>]:<FROM>,<TO>:<CTAG>:::
[BANDTYPE=<BANDTYPE>],WVNUM=<WVNUM>,
[DSTBANDTYPE=<DSTBANDTYPE>],[DSTWVNUM=<DSTWVNUM>],
[OPAMODE=<OPAMODE>,][CKTID=<CKTID>]:,[<SST>];
Command Parameters
Paramete
rs Description Default Value
Paramete
rs Description Default Value
<BANDT Indicates the type of the wave band. The default and CBAND
YPE> only available value for this parameter is CBAND.
<DSTBA Indicates the type of the band to which the sink CBAND
NDTYPE wavelength belongs.
>
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-PXC-OCH::FAC-1-1-1,FAC-1-4-1:C:::WVNUM=1,CKTID=A1:,RDLD;
l Response Message
NE 2008-09-04 15:23:20 M 100 COMPLD ;
Related Commands
A.8.1.3 DLT-PXC-OCH
A.8.1.1 ENT-PXC-OCH
A.8.1.4 RTRV-PXC-OCH
A.8.1.3 DLT-PXC-OCH
Deletes a cross-connection (OCH).
Function
This command deletes an OCH layer cross-connection.
Usage Note
None
Category
Cross-connection
Security
Provisioning
Command Syntax
DLT-PXC-OCH:[<TID>]:<FROM>,<TO>:<CTAG>::[<CRSTYPE>]:
[BANDTYPE=<BANDTYPE>],WVNUM=<WVNUM>,
[DSTBANDTYPE=<DSTBANDTYPE>],[DSTWVNUM=<DSTWVNUM>],
[INCL=<INCL>];
Command Parameters
Parameters Description Default Value
<BANDTY Indicates the type of the wavelength band. The default CBAND
PE> and only available value for this parameter is
CBAND.
<DSTBAN Indicates the type of the band to which the sink CBAND
DTYPE> wavelength belongs.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
DLT-PXC-OCH:FAC-1-1-1,FAC-1-4-1:100::WVNUM=1,INCL=Y;
l Response Message
NE 2008-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.8.1.1 ENT-PXC-OCH
A.8.1.2 ED-PXC-OCH
A.8.1.4 RTRV-PXC-OCH
A.8.1.4 RTRV-PXC-OCH
Retrieves information on a cross-connection (OCH).
Function
This command retrieves the information on an OCH layer cross-connection.
Usage Note
None
Category
Cross-connection
Security
Retrieve
Command Syntax
RTRV-PXC-OCH:[<TID>]:[<AID>]:<CTAG>:::[BANDTYPE=<BANDTYPE>],
[WVNUM=<WVNUM>],[DSTBANDTYPE=<DSTBANDTYPE>],
[DSTWVNUM=<DSTWVNUM>];
Command Parameters
Paramete
rs Description Default Value
<BANDT Indicates the type of the wave band. The default and CBAND
YPE> only available value for this parameter is CBAND.
<DSTBA Indicates the type of the band to which the sink CBAND
NDTYPE wavelength belongs.
>
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf>
("<FROM>,<TO>:<CCT>,<CRSTYPE>:BANDTYPE=<BANDTYPE>,WVNUM=<WVNUM>,
[DSTBANDTYPE=<DSTBANDTYPE>,DSTWVNUM=<DSTWVNUM>],OPAMODE=<OPAMODE>,WV=<WV>,
[DSTWV=<DSTWV>],CKTID=<CKTID>:,<SST>" <cr><lf>)+ ;
Response Parameters
Parameters Description
<CCT> Indicates the type of the cross-connection. The valid values are as
follows:
l 2WAY: indicates that the cross-connection is bidirectional.
l 1WAY: indicates that the cross-connection is unidirectional.
<BANDTYPE> Indicates the type of the wave band. The default and only available
value for this parameter is CBAND.
<DSTBANDTYPE> Indicates the type of the band to which the sink wavelength
belongs.
<OPAMODE> Indicates the optical power adjustment mode. The valid value is
either MAN or AUTO.
NOTE
This parameter is displayed for E2E type cross-connections.
Example
l Command
RTRV-PXC-OCH:::c;
l Response Message
NE 2009-01-16 08:21:44 M C COMPLD
"FAC-2-10-1,FAC-2-10-4:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=4,
DSTBANDTYPE=CBAND,DSTWVNUM=78,WV=195.90THz/1530.33nm, DSTWV=192.20THz/1559.79nm "
"FAC-2-14-1,FAC-2-1-1:1WAY,E2E:BANDTYPE=CBAND,WVNUM=78,
DSTBANDTYPE=CBAND,DSTWVNUM=2,OPAMODE=AUTO,WV=192.20THz/1559.79nm, DSTWV=196.00THz/
1529.55nm " ;
Related Commands
A.8.1.3 DLT-PXC-OCH
A.8.1.2 ED-PXC-OCH
A.8.1.1 ENT-PXC-OCH
A.8.1.5 RTRV-PXCINFO-OCH
Retrieves information on a cross-connection information (OCH).
Function
This command queries the sub-cross-connections in an end-to-end optical cross-connection.
Usage Note
None
Category
Cross connection
Security
Retrieve
Command Syntax
RTRV-PXCINFO-OCH:[<TID>]:<FROM>,<TO>:<CTAG>:::
[BANDTYPE=<BANDTYPE>],WVNUM=<WVNUM>,
[DSTBANDTYPE=<DSTBANDTYPE>],[DSTWVNUM=<DSTWVNUM>];
Command Parameters
Parameters Description Default Value
<BANDTYPE> Indicates the type of the wave band. The default CBAND
and only available value for this parameter is
CBAND.
<DSTBANDTYP Indicates the type of the band to which the sink CBAND
E> wavelength belongs.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf>
("<FROM>,<TO>:<CCT>,<CRSTYPE>:BANDTYPE=<BANDTYPE>,WVNUM=<WVNUM>,
[DSTBANDTYPE=<DSTBANDTYPE>,DSTWVNUM=<DSTWVNUM>];" <cr><lf>)+ ;
Response Parameters
Parameters Description
<CCT> Indicates the type of the cross-connection. The valid values are
2WAY and 1WAY.
<CRSTYPE> Indicates the cross-connection type. The values are E2E and
INTRA. INTRA is the only valid cross-connection type for this
scenario.
<BANDTYPE> Indicates the type of the wave band. The default and only available
value for this parameter is CBAND.
Parameters Description
<DSTBANDTYPE> Indicates the type of the band to which the sink wavelength
belongs.
Example
l Command
RTRV-PXCINFO-OCH::FAC-2-14-1,FAC-2-1-1:C:::wvnum=78;
l Response Message
NE 2009-01-16 08:23:19 M C COMPLD
"FAC-2-16-1,FAC-2-16-4:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=78"
"FAC-2-15-1,FAC-2-15-2:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=78"
"FAC-2-10-1,FAC-2-10-8:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=78"
"FAC-2-13-8,FAC-2-13-11:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=78"
"FAC-2-13-11,FAC-2-13-2:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=78"
"FAC-2-3-1,FAC-2-3-5:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=78"
"FAC-2-3-5,FAC-2-3-4:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=78"
"FAC-2-1-3,FAC-2-1-1:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=78" ;
Related Commands
A.8.1.4 RTRV-PXC-OCH
A.8.1.6 RTRV-PXC-WASTAGE
Queries the line insertion loss that is set.
Function
This command queries the line insertion loss that is set.
Usage Note
None
Category
Cross-connection
Security
Retrieve
Command Syntax
RTRV-PXC-WASTAGE:[<TID>]::<CTAG>:::LOCAID=<LOCAID>,
[SRCNE=<SRCNE>],[DSTNE=<DSTNE>],[OTHAID=<OTHAID>],
[PXCDATA=<PXCDATA>];
Command Parameters
Paramete
rs Description Default Value
<DSTNE Indicates the name of the TID of the NE where the sink NA
> OCh is located
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ("LOCAID=<LOCAID>,
[SRCNE=<SRCNE>,DSTNE=<DSTNE>],OTHAID=<OTHAID>,PXCDATA=<PXCDATA>" <cr><lf>)+ ;
Response Parameters
Parameters Description
<LOCAID> Indicates the optical port number of the local NE for which the
insertion loss is set.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT ID>.
<SRCNE> Indicates the name of the TID of the NE where the source OCh is
located
<DSTNE> Indicates the name of the TID of the NE where the sink OCh is
located
Example
l Command
RTRV-PXC-WASTAGE:::c;
l Response Message
NE 2009-01-16 08:21:44 M C COMPLD
"FAC-2-10-1,FAC-2-10-4:1WAY,INTRA:BANDTYPE=CBAND,WVNUM=4,
DSTBANDTYPE=CBAND,DSTWVNUM=78,WV=195.90THz/1530.33nm, DSTWV=192.20THz/1559.79nm "
"FAC-2-14-1,FAC-2-1-1:1WAY,E2E:BANDTYPE=CBAND,WVNUM=78,
DSTBANDTYPE=CBAND,DSTWVNUM=2,OPAMODE=AUTO,WV=192.20THz/1559.79nm, DSTWV=196.00THz/
1529.55nm " ;
Related Commands
A.8.1.7 DLT-PXC-WASTAGE
A.8.1.8 ED-PXC-WASTAGE
A.8.1.7 DLT-PXC-WASTAGE
Deletes the insertion loss.
Function
This command deletes the insertion loss.
Usage Note
None
Category
Cross-connection
Security
Provisioning
Command Syntax
RTRV-PXC-WASTAGE:[<TID>]::<CTAG>:::LOCAID=<LOCAID>,
[SRCNE=<SRCNE>],[DSTNE=<DSTNE>],[OTHAID=<OTHAID>],
[PXCDATA=<PXCDATA>];
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
DLT-PXC-
WASTAGE:::C:::LOCAID=FAC-1-1-1&FAC-1-3-1&FAC-1-5-1,SRCNE=NE2,OTHAID=FAC-1-2-1,PXCD
ATA=\"WVTOTAL=1,WVNUM=4;
l Response Message
NE 2008-03-04 15:23:20 M 100 COMPLD ;
Related Commands
A.8.1.8 ED-PXC-WASTAGE
A.8.1.6 RTRV-PXC-WASTAGE
A.8.1.8 ED-PXC-WASTAGE
Sets the insertion loss.
Function
This command sets the insertion loss.
Usage Note
None
Category
Cross-connection
Security
Provisioning
Command Syntax
ED-PXC-WASTAGE:[<TID>]::<CTAG>:::LOCAID=<LOCAID>,[SRCNE=<SRCNE>],
[DSTNE=<DSTNE>],[OTHAID=<OTHAID>],[PXCDATA=<PXCDATA>];
Command Parameters
Paramete
rs Description Default Value
<DSTNE Indicates the name of the TID of the NE where the sink NA
> OCh is located
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-PXC-
WASTAGE:::C:::LOCAID=FAC-1-1-1&FAC-1-3-1&FAC-1-5-1,SRCNE=NE2,OTHAID=FAC-1-2-1,PXCD
ATA=\"WVTOTAL=1,WVNUM=4,WASTAGE=3;
l Response Message
NE 2008-09-04 15:23:20 M 100 COMPLD ;
Related Commands
A.8.1.7 DLT-PXC-WASTAGE
A.8.1.6 RTRV-PXC-WASTAGE
A.8.1.9 ED-OXC-NEPORT
Edits the edge port of an NE.
Function
When creating an end-to-end optical cross-connection, users must run this command at the
source and sink interfaces of all units except the OTU and the FIU unit.
Usage Note
None
Category
Cross Connection
Security
Provisioning
Command Syntax
ED-OXC-NEPORT:[<TID>]:<AID>:CTAG:::[IN=<IN>],[OUT=<OUT>],
[MARK=<MARK>];
Command Parameters
Parameter Description Default Value
<IN> Indicates the attribute of the input edge port. The ENABLE
valid values are ENABLE and DISABLE.
This parameter must be set to ENABLE if the AID
port is the source interface when users create an end-
to-end optical cross-connection.
<OUT> Indicates the attribute of the output edge port. The ENABLE
valid values are ENABLE and DISABLE.
This parameter must be set to ENABLE if the AID
port is the sink interface when users create an end-
to-end optical cross-connection.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-OXC-NEPORT::FAC-1-3-1:C:::IN=ENABLE,OUT=DISABLE;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.8.1.10 RTRV-OXC-NEPORT
A.8.1.10 RTRV-OXC-NEPORT
Retrieves the edge port of an NE.
Function
This command instructs the NE to retrieve the edge port status of the optical cross-connection.
Usage Note
The optical interface will not be displayed if the attribute of the edge ports IN and OUT are on
the same optical interface.
Category
Cross Connection
Security
Retrieve
Command Syntax
RTRV-OXC-NEPORT:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::IN=<IN>,OUT=<OUT>,[MARK=<MARK>];"<cr><lf>
;
Response Parameters
Parameter Description
<IN> Indicates the attribute of the edge port IN. The valid values are
ENABLE and DISABLE.
<OUT> Indicates the attribute of the edge port OUT. The valid values are
ENABLE and DISABLE.
Example
l Command
RTRV-OXC-NEPORT:::C
RTRV-OXC-NEPORT::FAC-1-3-ALL:C
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
"FAC-1-3-1::IN=ENABLE,OUT=DISABLE"
;
Related Commands
A.8.1.9 ED-OXC-NEPORT
A.8.1.11 RTRV-OCCUP-WAVE
Queries reserved wavelength resources at the optical layer.
Function
This command queries the wavelength resources reserved for ASON services. In scenarios with
a revertive ASON service, the original trail or wavelength is reserved for restoration when the
service is rerouted. The reserved wavelength cannot be used to carry a static service.
Usage Note
None
Category
Cross-connection
Security
Retrieve
Command Syntax
RTRV-OCCUP-WAVE:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
(^^^"<AID>::BANDTYPE=<BANDTYPE>,WV=<WV>,OCCUP=<OCCUP>"<cr><lf>)+
;
Response Parameters
Parameter Description
<BANDTYPE> Indicates the band of the port. The valid values is CBAND.
Example
l Command
RTRV-OCCUP-WAVE::FAC-1-8-1:C;
l Response Message
NE 2009-11-11 20:37:10
M C COMPLD
"FAC-1-8-1-1::BANDTYPE=CBAND,WV=196.05THz/1529.16nm,OCCUP=Y"
;
Related Commands
None
A.8.2.1 ENT-CRS-<MOD2>
Creates a cross-connection.
Function
This command creates an electrical layer cross-connection.
The symbol "&" can be used in the AID field of this command to indicate multiple objects.
l The following command is used to create a common one-way cross-connection from point
F1 to point T1.
ENT-CRS-<MOD2>:[<TID>]:F1,T1:<CTAG>::1WAY;
l The following command is used to create a common two-way cross-connection from point
F1 to point T1.
ENT-CRS-<MOD2>:[<TID>]:F1,T1:<CTAG>::2WAY;
l The following command is used to create a one-way selector from points F1&F2 to point
T1.
ENT-CRS-<MOD2>:[<TID>]:F1&F2,T1:<CTAG>::SNCPTYPE=<SNCPTYPE>
[,OTNLEVEL=<OTNLEVEL>],1WAY;
l The following command is used to create SNCP (a one-way selector and one-way bridge)
from points F1&F2 to point T1. (Either of the two commands can be used.)
– ENT-CRS-<MOD2>:[<TID>]:F1&F2,T1:<CTAG>::SNCPTYPE=<SNCPTYPE>
[,OTNLEVEL=<OTNLEVEL>],2WAY;
– ENT-CRS-<MOD2>:[<TID>]:T1,F1&F2:<CTAG>::SNCPTYPE=<SNCPTYPE>
[,OTNLEVEL=<OTNLEVEL>],2WAY;
l The following command is used to create two one-way selectors, one from points F1&F2
to point T1 and the other from points F1&F2 to point T2.
ENT-CRS-<MOD2>:[<TID>]:F1&F2,T1&T2:<CTAG>::SNCPTYPE=<SNCPTYPE>
[,OTNLEVEL=<OTNLEVEL>],1WAY;
l The following command is used to create broadcast from point F1 to points
T1&T2&T3&T4.
ENT-CRS-<MOD2>:[<TID>]:F1,T1&T2&T3&T4:<CTAG>::1WAY;
l The following command is used to interconnect two SNCP cross-connections from points
F1&F2 to points T1&T2.
ENT-CRS-<MOD2>:[<TID>]:F1&F2,T1&T2:<CTAG>::SNCPTYPE=<SNCPTYPE>
[,OTNLEVEL=<OTNLEVEL>],2WAY;
l If there is one common one-way cross-connection from F1 to T1, the following command
will convert it to a one-way selector; the preferred path is F1.
ENT-CRS-<MOD2>:[<TID>]:F2,T1:<CTAG>::SNCPTYPE=<SNCPTYPE>
[,OTNLEVEL=<OTNLEVEL>],1WAY;
l If there is one common two-way cross-connection from F1 to T1, the following command
will convert it to SNCP; the preferred path is F1.
ENT-CRS-<MOD2>:[<TID>]:F2,T1:<CTAG>::SNCPTYPE=<SNCPTYPE>
[,OTNLEVEL=<OTNLEVEL>],2WAY;
Usage Note
When an SNCP cross-connection is created, the path presented by the first AID is configured
to be the preferred path by default. For example, the AID (F1) of the cross-connection (created
by ENT-CRS-ODU1::F1&F2,T1:123;) is the preferred path. The user can also set the preferred
path by using parameter <PREFERREDPATH>.
Category
Cross-connection
Security
Provisioning
Command Syntax
ENT-CRS-<MOD2>:[<TID>]:<FROM>,<TO>:<CTAG>::[<CCT>]:[TS=<TS>],
[PLDRATE=<PLDRATE>],[PLDTYPE=<PLDTYPE>],[SNCPTYPE=<SNCPTYPE>]
[,OTNLEVEL=<OTNLEVEL>][,PREFERREDPATH=<PREFERREDPATH>]
[,RVRTV=<RVRTV>][,RVTM=<RVTM>][,SDFLAG=<SDFLAG][,CKTID=<CKTID>]:,
[<SST>];
Command Parameters
Paramete
rs Description Default Value
Paramete
rs Description Default Value
Paramete
rs Description Default Value
<SST> Indicates the red-lined state. The valid states are RDLD-DEA
provided in section A.32.3.17 SST_STATE.
Response Syntax
<cr><lf><lf> ^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf> M^^<CTAG>^COMPLD <cr><lf> ;
Example
l Command
ENT-CRS-ODU1::CLNT-1-7-1,SRV2-1-3-1:C::2WAY:CKTID=A1:,RDLD;
l Response Message
NE 2003-02-28 12:23:20 M 100 COMPLD ;
Related Commands
A.8.2.2 ED-CRS-<MOD2>
A.8.2.3 DLT-CRS-<MOD2>
A.8.2.4 RTRV-CRS-<MOD2>
A.8.2.2 ED-CRS-<MOD2>
Edits a cross-connection.
Function
This command edits the attributes of an electrical layer cross-connection.
l The symbol "&" can be used in the AID field of this command to indicate multiple objects.
l The AIDs must be in the same order as originally entered for the one-way cross-
connections. Either order will work for the two-way cross-connections.
l The AID format in the command is the same as the AID format in the retrieved response
message. For example, if the output of any retrieved AID is "F1&F2,T1:CCT", a command
with the AID format (F1&F2,T1) is required to edit this cross-connection.
l The following command is used to edit the name of the specified cross-connection.
ED-CRS-<MOD2>::F1,T1:<CTAG>:::CKTID=FISTONE;
l The following command is used to edit the red-lined state of the specified cross-connection.
ED-CRS-<MOD2>::F1,T1:<CTAG>::::,RDLD-DEA;
Usage Note
This command edits the preferred path when the switching state is not idle to ensure that the
future automatic switching is performed successfully.
Category
Cross-connection
Security
Provisioning
Command Syntax
ED-CRS-<MOD2>:[<TID>]:<FROM>,<TO>:<CTAG>::: [OTNLEVEL=<OTNLEVEL>,]
[RVRTV=<RVRTV>,][RVTM=<RVTM>,][SDFLAG=<SDFLAG>,][CKTID=<CKTID>]:,
[<SST>];
Command Parameters
Paramete Default
rs Description Value
<MOD2> The <MOD2> includes ODUn, OTUn, STSn, etc. For other NA
<MOD2> values, see the service type parameter in A.6.8 ED-
CLNT.
Paramete Default
rs Description Value
<RVRTV Indicates the revertive mode which only applies to SNCP. The N
> valid values are Y and N.
<SST> Indicates the red-lined state. The valid values are provided in NA
section A.32.3.17 SST_STATE.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Example
l Command
ED-CRS-ODU1::CLNT-3-1-1&CLNT-4-1-1,SRV1-5-1-1:123:::CKTID=SHENZHEN:,RDLD;
l Response Message
NE 2003-02-28 12:23:50
M 100 COMPLD
;
Related Commands
A.8.2.1 ENT-CRS-<MOD2>
A.8.2.3 DLT-CRS-<MOD2>
A.8.2.4 RTRV-CRS-<MOD2>
A.8.2.3 DLT-CRS-<MOD2>
Deletes a cross-connection.
Function
This command deletes a cross-connection.
l The AIDs must be in the same order as originally entered for the one-way cross-
connections. Either order will work for the two-way cross-connections.
l This command does not support deleting multiple cross-connections.
l The AID format in the deletion command is the same as the AID format in the retrieved
response message. For example, if the output of any retrieved AID is "F1&F2, T1: CCT",
the deletion command with the AID format (F1&F2, T1) is required to delete this cross-
connection.
l If there is a common one-way cross-connection from point F1 to point T1, the following
command is used to delete it.
DLT-CRS-<MOD2>:[<TID>]:F1,T1:<CTAG>;
l If there is a common two-way cross-connection from point F1 to point T1, the following
commands are used to delete it. (Either of the two commands can be deleted.)
– DLT-CRS-<MOD2>:[<TID>]:F1,T1:<CTAG>;
– DLT-CRS-<MOD2>:[<TID>]:T1,F1:<CTAG>;
l If there is a selector from points F1& F2 to point T1, the following command is used to
delete it.
DLT-CRS-<MOD2>:[<TID>]:F1&F2,T1:<CTAG>;
l The following command is used to delete two one-way selectors:
– From points F1&F2 to point T1
– From points F1&F2 to point T2
DLT-CRS-<MOD2>:[<TID>]:F1&F2,T1&T2:<CTAG>;
l If there is one one-way selector form F1 and F2 to T1, the following command will convert
it to a common one-way cross-connection from F1 to T1.
DLT-CRS-<MOD2>:[<TID>]:F2,T1:<CTAG>;
l If there is one SNCP from F1 and F2 to T1, the following command will convert it to a
common two-way cross-connection from F1 to T1.
DLT-CRS-<MOD2>:[<TID>]:F2,T1:<CTAG>;
Usage Note
None
Category
Cross-connection
Security
Provisioning
Command Syntax
DLT-CRS-<MOD2>:[<TID>]:<FROM>,<TO>:<CTAG>:::[INCL=<INCL>];
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-CRS-ODU1::SRV1-1-5-1-1,CLNT-1-1-1:C:::INCL=Y;
Related Commands
A.8.2.2 ED-CRS-<MOD2>
A.8.2.1 ENT-CRS-<MOD2>
A.8.2.4 RTRV-CRS-<MOD2>
A.8.2.4 RTRV-CRS-<MOD2>
Retrieves a cross-connection.
Function
This command retrieves the attributes for the cross-connections.
l Symbol "&" is used in the AID field of this command to indicate multiple objects.
l The following command is used to retrieve all level cross-connections with specified path
F1:
RTRV-CRS-<MOD2>::F1:<CTAG>;
l F1&F2 indicates the working path and protection path respectively, so the following
command is used to retrieve all the SNCP cross-connections with the specified two paths
of F1 and F2:
RTRV-CRS-<MOD2>::F1&F2:<CTAG>;
l Use the following commands to retrieve all the cross-connections with any path between
F1 and F2.
For example, create 4 cross-connections by using the following four commands:
– ENT-CRS-ODU1::CLNT-7-1-1,CLNT-10-1-1:S::2WAY:CKTID=CHA9;
– ENT-CRS-ODU1::CLNT-7-1-2,CLNT-10-1-2:S::2WAY:CKTID=CHA9;
– ENT-CRS-ODU1::CLNT-7-1-3,CLNT-10-1-3:S::2WAY:CKTID=CHA9;
– ENT-CRS-ODU1::CLNT-7-1-4,CLNT-10-1-4:S::2WAY:CKTID=CHA9;
The RTRV-CRS-ODU1::STS-7-1-1&&-4:S command can retrieve all the cross-
connections between the two ODU1s.
l The following command is used to retrieve all the cross-connections:
RTRV-CRS-<MOD2>:::<CTAG>;
Usage Note
None
Category
Cross-connection
Security
Retrieve
Command Syntax
RTRV-CRS-<MOD2>:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Default
Parameters Description Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf>
("<FROM>,<TO>:<CCT>,<LEVEL>:[TS=<TS>][,PLDRATE=<PLDRATE>][,PLDTYPE=<PLDTYPE>]
[,SNCPTYPE=<SNCPTYPE>][,OTNLEVEL=<OTNLEVEL>][,PREFERREDPATH=<PREFERREDPATH>]
[,ACTIVEPATH=<ACTIVEPATH>,][,RVRTV=<RVRTV>][,RVTM=<RVTM>][,SDFLAG=<SDFLAG>]
[,AUTOFLAG=<AUTOFLAG>][,CKTID=<CKTID>]:[,<SST>]" <cr><lf>)+ ;
Response Parameters
Parameters Description
Parameters Description
<CCT> Indicates the type of the cross-connection. The valid values are as
follows:
l 2WAY: indicates that the cross-connection is bidirectional.
l 1WAY: indicates that the cross-connection is unidirectional.
<LEVEL> Indicates the level of the cross-connection. The valid values are
as follows:
l FETH/GETH/XGETH
l OTU1/OTU2/OTU3/OTU5G
l ODU0/ODU1/ODU2/ODU3/ODU5G/ODUFLEX
l STS3/STS12/STS48/STS192/STS768
l STM1/STM4/STM16/STM64/STM256
l FC100/FC200/FC400/FC1000/FC1200
l FICON/FICONEXP
l HDSDI
l DVBASI/SDI
l ESCON
l FDDI
l ISCIG
l ISC2G
<PLDRATE> Indicates the rate of a channel service and is valid only when
ODUflex services are configured on the channel.
<PLDTYPE> Indicates the type of a channel service and is valid only when
ODUflex services are configured on the channel.
<SNCPTYPE> Indicates the SNCP protection type The valid values are as
follows:
swsncp: SW SNCP protection
snci: SNC/I
sncn: SNC/N
sncs: SNC/S
NA: Non-SNCP group
Parameters Description
<PREFERREDPATH> Indicates the preferred path. It is only available for SNCP. Two
values separated by "&" are only applicable to SNCP with two
sources or two destinations.
<ACTIVEPATH> Indicates the active path. It is only available for SNCP. Two values
separated by "&" are applicable to only SNCP with 2 sources or
2 destinations. The active path is the actual working path of the
SNCP.
<RVTM> This parameter is available only for SNCP and when <RVRTV>
is enabled.
Indicates the revertive time expressed in minutes. It ranges from
5 to 12. The default value is 5.
Example
l Command
RTRV-CRS-ODU1::CLNT-1-2-1:C;
l Response Message
NGWDM-NE 2003-03-12 07:28:39 M 100 COMPLD
"CLNT-1-3-1&CLNT-1-2-1,SRV1-1-7-1-1:2WAY,ODU1:SNCPTYPE=SNCI,PREFERREDPATH=CLNT-1-3
-1,ACTIVEPATH=CLNT-1-3-1,CKTID=MERRY:,RDLD" ;
Related Commands
A.8.2.2 ED-CRS-<MOD2>
A.8.2.1 ENT-CRS-<MOD2>
A.8.2.3 DLT-CRS-<MOD2>
A.9.1 ENT-CRS-OHFE
Creates a pass-through FE service in the OSC.
Function
This command creates a pass-through FE service in the OSC. After the pass-through FE service
is created in the OSC, the FE port on the ST2 board where the OSC is located cannot be used to
transparently transmit third-party management information.
Usage Note
None
Category
Communication
Security
Provisioning
Command Syntax
ENT-CRS-OHFE:[<TID>]:<FROM>,<TO>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^^COMPLD<cr><lf> ;
Example
l Command
ENT-CRS-OHFE::FAC-1-2-1,FAC-1-3-1:10;
l Response Message
NE 2011-01-25 15:33:17 M 10 COMPLD ;
Related Commands
A.9.2 RTRV-CRS-OHBYTE
A.9.3 DLT-CRS-OHFE
A.9.2 RTRV-CRS-OHBYTE
Retrieves the cross of a transparent FE channel of OSC.
Function
Retrieves the cross of a transparent FE channel of OSC.
Usage Note
None
Category
Communication
Security
Retrieve
Command Syntax
RTRV-CRS-OHFE:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
None
Response Syntax
cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<FROM>,<TO>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-CRS-OHFE:::100;
l Response Message
NE 2011-01-20 15:36:49
M 10 COMPLD
"FAC-1-2-1,FAC-1-6-1"
;
Related Commands
A.9.1 ENT-CRS-OHFE
A.9.3 DLT-CRS-OHFE
A.9.3 DLT-CRS-OHFE
Deletes the cross of a transparent FE channel of OSC.
Function
Deletes the cross of a transparent FE channel of OSC.
Usage Note
None
Category
Communication
Security
Provisioning
Command Syntax
DLT-CRS-OHFE:[<TID>]:<FROM>,<TO>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Example
l Command
DLT-CRS-OHFE::FAC-1-2-1,FAC-1-3-1:10;
l Response Message
NE 2011-01-25 15:33:17
M 10 COMPLD
;
Related Commands
A.9.2 RTRV-CRS-OHBYTE
A.9.1 ENT-CRS-OHFE
A.10.1.1 ENT-EQPT-PG
Creates an equipment level protection group.
Function
This command creates an equipment level protection group. It corresponds to the BPS protection
group function.
Usage Note
None
Category
EQPT protection
Security
Provisioning
Command Syntax
ENT-EQPT-PG:[<TID>]:<AID>:<CTAG>:::WORK=<WORK>,[CTRL=<CTRL>]:
[<PGSTATE>];
Command Parameters
Parameter Description Default
Value
<CTRL> Indicates whether the protection card can disable the service N
output.
l N: indicates that the protection card is not able to disable
the service output. In this scenario, no control unit is
available. (default value).
l Y: indicates that the protection card is able to disable the
service output. In this scenario, the SCS is the control unit.
<PGSTATE Indicates the state of the protection group. The valid values IS
> are IS (In-service) and OOS (out-of-service).
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ENT-EQPT-PG::SLOT-1-4:C:::WORK=SLOT-1-5,CTRL=N:IS;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.10.1.4 RTRV-EQPT-PG
A.10.1.3 DLT-EQPT-PG
A.10.1.2 ED-EQPT-PG
A.10.1.2 ED-EQPT-PG
Edits an equipment level protection group.
Function
This command edits the attributes of an equipment level protection group.
Usage Note
None
Category
EQPT protection
Security
Provisioning
Command Syntax
ED-EQPT-PG:[<TID>]:<AID>:<CTAG>::::[<PGSTATE>];
Command Parameters
Parameter Description Default
Value
<PGSTATE> Indicates the state of the equipment level protection group. The NA
valid values are IS (in-service) and OOS (out-of-service).
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
Example
l Command
ED-EQPT-PG::SLOT-1-4:C::::OOS;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.10.1.4 RTRV-EQPT-PG
A.10.1.3 DLT-EQPT-PG
A.10.1.1 ENT-EQPT-PG
A.10.1.3 DLT-EQPT-PG
Deletes an equipment level protection group.
Function
This command deletes an equipment level protection group.
Usage Note
None
Category
EQPT protection
Security
Provisioning
Command Syntax
DLT-EQPT-PG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Param Description Default
eter Value
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>
;
Example
l Command
DLT-EQPT-PG::SLOT-1-4:C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.10.1.4 RTRV-EQPT-PG
A.10.1.3 DLT-EQPT-PG
A.10.1.1 ENT-EQPT-PG
A.10.1.4 RTRV-EQPT-PG
Retrieves an equipment level protection group.
Function
This command retrieves the parameters for a specified equipment level protection group.
Usage Note
None
Category
EQPT protection
Security
Retrieve
Command Syntax
RTRV-EQPT-PG:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Parame Description Default
ter Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^("<AID>::RVRTV=<RVRTV>,PSTYPE=<PSTYPE>,WORK=<WORK>,CTRL=
<CTRL>,SWSTATE=<SWSTATE>:<PGSTATE>")+<cr><lf>
;
Response Parameters
Parameter Description
<RVRTV> Indicates the revertive mode. The only valid value supported by BPS is N (non-
revertive mode).
<PSTYPE Indicates the protection type. 1+1 indicates the BPS protection.
>
<CTRL> Indicates whether the protection card can disable service output.
l N: indicates that the protection card is not able to disable service output. In
this scenario, no control unit is available. (default value).
l Y: indicates that the protection card is able to disable service output. In this
scenario, the SCS is the control unit.
<SWSTAT Indicates the switching status of the protection group. The valid values are as
E> follows:
l IDLE: The service is running on the working card.
l SWITCHING: The service is running on the protection card.
<PGSTAT Indicates the state of the protection group. The valid values are IS (in-service)
E> and OOS (out-of-service).
Example
l Command
RTRV-EQPT-PG:::C;
l Response Message
NGWDM-NE 2004-01-01 15:54:55
M C COMPLD
"SLOT-1-4::RVRTV=N,PSTYPE=1+1,CTRL=N,WORK=SLOT-1-3,SWSTATE=IDLE:IS"
;
Related Commands
A.10.1.1 ENT-EQPT-PG
A.10.1.2 ED-EQPT-PG
A.10.1.3 DLT-EQPT-PG
A.10.1.5 OPR-PROTNSW-EQPT
Performs an equipment level protection switching.
Function
This command instructs an NE to perform an equipment level protection switching.
Usage Note
None
Category
EQPT protection
Security
Maintenance
Command Syntax
OPR-PROTNSW-EQPT:[<TID>]:<AID>:<CTAG>::<SC>:[<DIRN>];
Command Parameters
Paramete Description Default
r Value
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>
;
Response Parameters
None
Example
l Command
OPR-PROTNSW-EQPT::SLOT-1-5:C::MAN:BTH;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.10.1.6 RLS-PROTNSW-EQPT
A.10.1.6 RLS-PROTNSW-EQPT
Releases an equipment level protection switching.
Function
This command instructs the NE to release an equipment level protection switching.
Usage Note
None
Category
EQPT protection
Security
Maintenance
Command Syntax
RLS-PROTNSW-EQPT:[<TID>]:<AID>:<CTAG>::[<DIRN>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>
;
Example
l Command
RLS-PROTNSW-EQPT::SLOT-1-5:C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.10.1.5 OPR-PROTNSW-EQPT
A.10.2.1 ENT-FFP-<OCH/OC/WDM/CFP>
Creates a facility protection group of the optical level, such as OCH, OC, WDM or CFP.
Function
This command creates an optical facility protection group. It can also be used to input attributes
of the protection group.
Usage Note
None
Category
FFP protection
Security
Provisioning
Command Syntax
ENT-FFP-<OCH/OC/WDM/CFP>:
[<TID>]:<PROTECT>,<WORK>:<CTAG>:::FFPTYPE=<FFPTYPE>,
[PROTNE=<PROTNE>],[WORKNE=<WORKNE>],[MARK=<MARK>],
[RVRTV=<RVRTV>],[RVTM=<RVTM>],[SDFLAG=<SDFLAG>],
[DETECT=<DETECT>],[CTRL=<CTRL>],[CTRLNE=<CTRLNE>]:[<FFPSTATE>];
Command Parameters
Parameter Description Default
Value
<FFPTYPE Indicates the type of protection group. The valid values are as NA
> follows:
l OLP1+1: indicates optical line protection.
l INNER1+1: indicates intra-card 1+1 protection.
l Client1+1: indicates client-side 1+1 protection.
<RVRTV> Indicates the revertive mode. The valid values are as follows: N
l Y: indicates the revertive mode.
l N: indicates the non-revertive mode.
<SDFLAG Indicates the signal degrade flag. The valid values are DISABLE
> ENABLE and DISABLE.
<FFPSTAT Indicates the state of the protection group. The valid values IS
E> are IS (In-service) and OOS (out-of-service).
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ENT-FFP-WDM::FAC-1-11-2,FAC-1-11-1:100:::FFPTYPE=OLP1+1,RVRTV=Y:;
l Response Message
NE 2006-01-07 09:50:17
M 100 COMPLD
;
Related Commands
A.10.2.2 ED-FFP-<OCH/OC/WDM/CFP>
A.10.2.3 DLT-FFP-<OCH/OC/WDM/CFP>
A.10.2.4 RTRV-FFP-<OCH/OC/WDM/CFP>
A.10.2.2 ED-FFP-<OCH/OC/WDM/CFP>
Edits a facility protection group of the optical level, such as OCH, OC ,WDM or CFP.
Function
This command edits the attributes of an optical facility protection group.
Usage Note
None
Category
FFP protection
Security
Provisioning
Command Syntax
ED-FFP-<OCH/OC/WDM/CFP>:[<TID>]:<AID>:<CTAG>:::[NE=<NE>],
[MARK=<MARK>],[RVRTV=<RVRTV>],[RVTM=<RVTM>],[SDFLAG=<SDFLAG>]:
[<FFPSTATE>];
Command Parameters
Paramet Default
er Description Value
Paramet Default
er Description Value
<RVRT Indicates the revertive mode. The valid values are as follows: N
V> l Y: indicates the revertive mode.
l N: indicates the non-revertive mode.
If nothing is entered, the previous value will be retained.
<SDFLA Indicates the signal degrade flag. The valid values are ENABLE DISABLE
G> and DISABLE. If nothing is entered, the previous value will be
retained.
<FFPST Indicates the state of the facility protection group. The valid values NA
ATE> are IS (in-service) and OOS (out-of-service).
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-FFP-OC::FAC-2-2-1:C:::MARK=TEST,RVRTV=Y,RVTM=10;
l Response Message
NE 2006-01-07 09:50:17
M 100 COMPLD
;
Related Commands
A.10.2.1 ENT-FFP-<OCH/OC/WDM/CFP>
A.10.2.3 DLT-FFP-<OCH/OC/WDM/CFP>
A.10.2.4 RTRV-FFP-<OCH/OC/WDM/CFP>
A.10.2.3 DLT-FFP-<OCH/OC/WDM/CFP>
Deletes a facility protection group of the optical level, such as OCH, OC, WDM or CFP.
Function
This command deletes an entire optical facility protection group of a specified optical carrier
(OCH/OC/WDM/CFP) level.
Usage Note
None
Category
FFP protection
Security
Provisioning
Command Syntax
DLT-FFP-<OCH/OC/WDM/CFP>:[<TID>]:<AID>:<CTAG>:::[NE=<NE>];
Command Parameters
Paramet Description Default
er Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
DLT-FFP-OC::FAC-2-2-1:100;
l Response Message
NE 2006-01-07 09:50:17
M 100 COMPLD
;
Related Commands
A.10.2.2 ED-FFP-<OCH/OC/WDM/CFP>
A.10.2.1 ENT-FFP-<OCH/OC/WDM/CFP>
A.10.2.4 RTRV-FFP-<OCH/OC/WDM/CFP>
A.10.2.4 RTRV-FFP-<OCH/OC/WDM/CFP>
Retrieves the attributes of a facility protection group of the optical level, such as OCH, OC,
WDM or CFP.
Function
This command retrieves the attributes of an optical facility protection group.
Usage Note
None
Category
FFP protection
Security
Retrieve
Command Syntax
RTRV-FFP-<OCH/OC/WDM/CFP>:[<TID>]:[<AID>]:<CTAG>:::[NE=<NE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> <SID> <DATE> <TIME> <cr><lf> M CTAG COMPLD<cr><lf>
("<PROTECT>,<WORK>:<MOD2>:FFPTYPE=<FFPTYPE>,[PROTNE=<PROTNE>],[WORKNE=<WORKNE>],
[DETECT=<DETECT>],[CTRL=<CTRL>],[CTRLNE=<CTRLNE>],[MARK=<MARK>],[RVRTV=<RVRTV>],
[RVTM=<RVTM>],SDFLAG=<SDFLAG>,[SWSTATE=<SWSTATE>],[ACTIVE=<ACTIVE>],
[WORKSTATE=<WORKSTATE>],[PROTSTATE=<PROTSTATE>],[CTRL=<CTRL>],[CTRLNE=<CTRLNE>]:
[<FFPSTATE>]"<cr><lf>);
Response Parameters
Parameter Description
Parameter Description
<FFPTYPE> Indicates the type of the protection group. The valid values are as follows:
l OLP1+1: indicates OLP 1+1 protection.
l INNER1+1: indicates inner-unit 1+1 protection.
l CLIENT1+1: indicates client-side 1+1 protection.
<PROTNE> Indicates the NE on which the protection optical facility is located. If the
protection optical facility is local, nothing is entered for this parameter.
<WORKNE Indicates the NE on which the working optical facility is located. If the
> working optical facility is local, nothing is entered for this parameter.
<CTRL> When the client-side inter-subrack 1+1 protection or the extended intra-card
1+1 protection is configured, an additional unit (control unit or detection unit)
is required.
<CTRLNE> The NE on which the control unit (OLP) is located. If the control unit is local,
nothing is entered for this parameter.
<MARK> Indicates the protection group memo information. It is a string with no more
than 64 characters. The default value is NULL.
<RVRTV> Indicates the revertive mode. The valid values are as follows:
l Y: indicates the revertive mode.
l N: indicates the non-revertive mode.
The default value is N.
<SDFLAG> Indicates the signal degrade flag. The valid values are ENABLE and
DISABLE.
<SWSTATE Indicates the switching state of the protection group. The valid values are as
> follows:
l IDLE: indicates that the active card is working.
l SWITCHING: indicates that the standby card is working.
l INIT: indicates that the protection group is in the initial state.
<ACTIVE> Indicates the current active port. The valid values are WORK and PROTECT.
<WORKST Indicates the current state of the working port. The valid values are provided
ATE> in A.32.3.20 SWITCHSTATE.
Parameter Description
<PROTSTA Indicates the current state of the working port. The valid values are provided
TE> in A.32.3.20 SWITCHSTATE.
<FFPSTATE Indicates the state of the facility protection group. The valid values are IS (in-
> service) and OOS (out-of-service).
Example
l Command
RTRV-FFP-WDM::ALL:C;
l Response Message
NE 2008-11-18 14:08:37 M C COMPLD "FAC-1-11-2,FAC-1-11-1:WDM:MARK=
\"\",FFPTYPE=OLP1+1,RVRTV=Y,RVTM=5,SDFLAG=DISABLE,:IS"
"FAC-1-13-2,FAC-1-13-1:WDM:MARK=\"\",FFPTYPE=OLP1
+1,RVRTV=N,RVTM=0,SDFLAG=DISABLE,:IS" ;
Related Commands
A.10.2.2 ED-FFP-<OCH/OC/WDM/CFP>
A.10.2.3 DLT-FFP-<OCH/OC/WDM/CFP>
A.10.2.1 ENT-FFP-<OCH/OC/WDM/CFP>
A.10.2.5 RTRV-FFP-LOG
Retrieves the FFP event records.
Function
This command retrieves the FFP event records.
Usage Note
The logs of deleted protection groups cannot be queried.
Category
FFP protection
Security
Maintenance
Command Syntax
RTRV-FFP-LOG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
(^^^<AID>:EVENT-NO=<EVENT-NO>,PS-EVENT=<PS-EVENT>,EVENT-PARA=<EVENT-
PARA>,Date=<date>,Time=<time>"<cr><lf>)+ ;
Response Parameters
Parameter Description
<AID> Indicates the access identifier that identifies the OCh/OC/WDM/CFP port in
the FFP group.
<EVENT- Indicates the event number that increases from 1 to 65535. The maximum
NO> record number of 1-N is 250 and the limit of the 1+1 protection group is 1250.
<DATE> Indicates the date when the event happens. The valid format is YY-MM-DD.
<TIME> Indicates the time when the event happens. The valid format is HH-MM-SS.
Example
l Command
RTRV-FFP-LOG::FAC-2-2-1:C1;
l Response Message
NE 2006-02-01 11:37:18
M C1 COMPLD
FAC-2-1-1::EVENT-NO=1,PS-EVENT=SFSW,EVENT-
PARA=0x010f0200,Date=2005-11-12,Time=11-33-23;
Related Commands
A.10.2.6 INIT-FFP-LOG
A.10.2.6 INIT-FFP-LOG
Clear the FFP event records.
Function
This command clears the FFP event records.
Usage Note
None
Category
FFP protection
Security
Maintenance
Command Syntax
INIT-FFP-LOG:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
INIT-FFP-LOG:::S;
l Response Message
NE-122-23 2012-08-02 20:11:25
M S COMPLD
;
>
Related Commands
A.10.2.5 RTRV-FFP-LOG
A.10.2.7 OPR-PROTNSW-<OCH/OC/WDM/CFP>
Performs a protection switching of an optical level, such as OCH, OC, WDM or CFP.
Function
This command performs a protection switching.
Usage Note
If this command is successfully executed, the channel indicated by the input parameter AID
turns to a non-working state.
Category
FFP protection
Security
Maintenance
Command Syntax
OPR-PROTNSW-<OCH/OC/WDM/CFP>:[<TID>]:<AID>:<CTAG>::<SC>:[<DIRN>]
[,<NE>];
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
OPR-PROTNSW-OC::FAC-2-2-1:100::FRCD;
l Response Message
NE 2006-01-07 09:50:17
M 100 COMPLD
;
Related Commands
A.10.2.8 RLS-PROTNSW-<OCH/OC/WDM/CFP>
A.10.2.8 RLS-PROTNSW-<OCH/OC/WDM/CFP>
Releases a protection switching (OCH/OC/WDM/CFP).
Function
This command instructs an NE to release (clear) line protection switching between a working
line and an established protection line.
Usage Note
Releasing switching command can release only external switching commands. After a switching
is released, the protection group returns to a proper state. For example, if the working channel
and protection channel are both normal, the group returns to the working channel. If the working
channel is faulty and the protection channel is normal, the group switches to the protection
channel.
Category
FFP protection
Security
Maintenance
Command Syntax
RLS-PROTNSW-<OCH/OC/WDM/CFP>:[<TID>]:<AID>:<CTAG>::[<DIRN>][,<NE>];
Command Parameters
Paramet Description Default Value
er
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
RLS-PROTNSW-OC::FAC-2-2-1:100;
l Response Message
NE 2006-01-07 09:50:17
M 100 COMPLD
;
Related Commands
A.10.2.7 OPR-PROTNSW-<OCH/OC/WDM/CFP>
NOTE
A.10.3.1 RLS-PROTNSW-<MOD2>
Releases a protection switching.
Function
This command instructs the NE to release path protection switching request that is created by
the external command.
Usage Note
None
Category
SNCP
Security
Maintenance
Command Syntax
RLS-PROTNSW-<MOD2>:[<TID>]:<AID>:<CTAG>::[<DIRN>];
Command Parameters
Parameter Description Default Value
<MOD2> The <MOD2> includes ODUn, OTUn, and STSn. For other NA
<MOD2> values, see the service type parameter in A.6.8
ED-CLNT.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Example
l Command
RLS-PROTNSW-ODU1::SRV1-1-2-1-1:C;
l Response Message
NE 2003-02-29 12:24:50
M 100 COMPLD
;
Related Commands
A.10.3.2 OPR-PROTNSW-<MOD2>
A.10.3.2 OPR-PROTNSW-<MOD2>
Performs the protection switching.
Function
This command instructs an NE to execute the external switching command.
Usage Note
None
Category
SNCP
Security
Maintenance
Command Syntax
OPR-PROTNSW-<MOD2>:[<TID>]:<AID>:<CTAG>::<SC>:[<DIRN>];
Command Parameters
Parameter Description Default
Value
<MOD2> The <MOD2> includes ODUn, OTUn, and STSn. For other NA
<MOD2> values, see the service type parameter in A.6.8 ED-
CLNT.
<AID> Indicates the access identifier that identifies the path. This NA
parameter must be a working path or protection path.
The valid format of <AID> depends on the level of the
electrical cross-connection which is specified by <MOD2>.
For example, if the <MOD2> is STS3, refer to A.32.2.18
OCN/STMN for the valid format corresponding to the
desired unit; if the <MOD2> is FC200, refer to A.32.2.9
FCMOD2.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Example
l Command
OPR-PROTNSW-ODU1::SRV1-1-1-1-1:123::MAN:BTH;
l Response Message
NE 2003-02-29 12:23:50
M 100 COMPLD
;
Related Commands
A.10.3.1 RLS-PROTNSW-<MOD2>
A.11.1 ED-AUTOSYNC-ENABLE
Edit the attribute for automatic synchronization.
Function
The command edit the attribute for automatic synchronization.
Usage Note
None
Category
HBU
Security
Maintenance
Command Syntax
ED-AUTOSYNC-ENABLE:[<TID>]:<SLOT_ID>:<CTAG>::<AUTOSYNC>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-AUTOSYNC-ENABLE::SLOT-1-18:100::ENABLE;
l Response Message
M1050 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
None
A.11.2 REPT^SW
Reports the SCC switching.
Function
This event is reported to indicate that an SCC protection switching occurred.
Usage Note
None
Category
Equipment
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
A^^<ctag>^REPT^SW<cr><lf>
^^^"<ACT_SLOT>,<STANDBY_SLOT>"<cr><lf>
;
Response Parameters
Parameter Description
<ACT_SLOT> Indicates the slot of the working card after the switching.
<STANDBY_SLO Indicates the slot of the protection card after the switching.
T>
Example
l Command
None
l Response Message
NE 2004-06-17 18:03:52
A 41 REPT SW
"SLOT-18,SLOT-17"
;
Related Commands
None
A.11.3 RTRV-BACKUP-INFO
Retrieves the backup information about the SCC.
Function
This command retrieves the backup information about the SCC.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-BACKUP-INFO:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"BACKUPINFO=<BACKUP_INFO>"<cr><lf>
;
Response Parameters
Paramete Description
r
Example
l Command
RTRV-BACKUP-INFO:::100;
l Response Message
NE 1990-02-07 07:16:23
M 100 COMPLD
"BACKUPINFO= COMPLETED"
;
Related Commands
None
A.11.4 ALW-SWDX-EQPT
Allows an automatic or manual switching.
Function
This command allows an automatic or manual switching on a system containing duplex
equipment. Use the INH-SWDX-EQPT command to inhibit the switching if necessary.
Usage Note
None
Category
SCC protection switch
Security
Maintenance
Command Syntax
ALW-SWDX-EQPT:[<TID>]:<HSCSLOT_NUM>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^<cr><lf>
;
Response Parameters
None
Example
l Command
ALW-SWDX-EQPT::SLOT-1-9:100;
l Response Message
NE 1990-02-07 07:07:36
M 100 COMPLD
;
Related Commands
A.11.5 INH-SWDX-EQPT
A.11.5 INH-SWDX-EQPT
Inhibits an automatic or manual switching.
Function
This command inhibits an automatic or manual switching on a system containing duplex
equipment. Use the ALW-SWDX-EQPT command to release the inhibition if necessary.
Usage Note
None
Category
SCC protection switch
Security
Maintenance
Command Syntax
INH-SWDX-EQPT:[<TID>]:<HSCSLOT_NUM>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^<cr><lf>
;
Response Parameters
None
Example
l Command
INH-SWDX-EQPT::SLOT-1-9:100;
l Response Message
NE 2004-02-07 07:07:36
M 100 COMPLD
;
Related Commands
A.11.4 ALW-SWDX-EQPT
A.11.6 RTRV-BATCHBAK-CAUSEHIS
Retrieves history records of the batch backup reason.
Function
This command retrieves history records of the batch backup reason.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-BATCHBAK-CAUSEHIS:[<TID>]:<SLOT_ID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"SLOT_ID=<SLOT_ID>,BEGIN_TIME=<HBU_TIME_BEGIN>,BATCH_REASON=<HBU_BATCH_REASON>,
BATCH_TIMES=<HBU_BATCH_TIMES>,TIME_OUT=<HBU_BATCH_TIMEOUT>,RESULT=<HBU_SYNC_RESULT
>,END_TIME=<HBU_TIME_END>"<cr><lf>
;
Response Parameters
Parameter Description
<HBU_BATCH_TIMES> Times from batch time out which result batch backup.
Parameter Description
Example
l Command
RTRV-BATCHBAK-CAUSEHIS::SLOT-9:100;
l Response Message
NE 2006-05-19 11:03:16
M 100 COMPLD
"SLOT_ID=SLOT-9,BEGIN_TIME=\"2006-05-19 07:18:24
\",BATCH_REASON=AFTERSW,BATCH_TIMES=0,TIME_OUT=300000,RESULT=SYNC OK,END_TIME=
\"2006-05-19 07:18:49\""
"SLOT_ID=SLOT-9,BEGIN_TIME=\"2006-05-19 07:31:58
\",BATCH_REASON=AFTERSW,BATCH_TIMES=0,TIME_OUT=300000,RESULT=SYNCING...,END_TIME=
\"1990-00-00 00:00:00\""
Related Commands
None
A.11.7 RTRV-MSCOM-INTRPHIS
Retrieves history interruption due to the active/standby switching.
Function
This command retrieves history interruption due to the active/standby switching.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-MSCOM-INTRPHIS:[<TID>]:<SLOT_ID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"SLOT_ID=<SLOT_ID>,TIME=<HBU_TIME_END>,COM_STATE=<HBU_CMOS_STATE>,STDBY_ONLINE=
<HBU_BDONLINE>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-MSCOM-INTRPHIS::SLOT-1-18:100;
l Response Message
OSP-118 2011-06-23 18:37:04
M 100 COMPLD
"SLOT_ID=SLOT-1-18,TIME=2011-06-22
12-57-54,COM_STATE=OK,STDBY_ONLINE=HBUONLINE"
;
Related Commands
None
A.11.8 RTRV-AUTOSYNC-ENABLE
Retrieves the automatic synchronization status.
Function
This command retrieves the automatic synchronization status.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-AUTOSYNC-ENABLE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AUTOSYNC>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-AUTOSYNC-ENABLE::SLOT-1-17:100;
l Response Message
NE 2005-08-02 18:25:07
M 100 COMPLD
"ENABLE"
;
Related Commands
A.29.4 SET-DBMS-AUTOBACKUP
A.11.9 RTRV-SWITCH-HIS
Retrieves records of the recent active/standby switching actions.
Function
This command retrieves the records of the recent active/standby switching actions.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-SWITCH-HIS:[<TID>]:<HSCSLOT_NUM>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"SLOT_NUM=<HSCSLOT_NUM>,SWITCH_TIME=<HSC_SWITCH_TIME>,MANUAL_SWITCH=<FORCE_LOCK
_SUPPORT>,AUTO_SWITCH=<HSC_SWITCH_AUTO>,"FORCE_SWITCH=<HSC_SWITCH_FORCE>,PLUG_SWIT
CH=<HSC_SWITCH_PLUG>,BIOS_LINGER=<HSC_BIOS_LINGER>,BIOS_RESET=<HSC_BIOS_RESET>,"AS
_ENABLE=<HSCSWENABLE>,SELF_AS=<HSC_AS_TYPE>,PEER_ONLINE=<HSC_BDONLINE>,SELF_WORK=<
STDBY_WORK>,PEER_WORK=<HSC_WORK_PEER>,READY_STATE=<HSC_READY_STATE>,SOFT_DETECT=<H
SC_SOFT_DETECT>,BAD_CODE=<HSC_BAD_CODE>"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
<HSC_BDONLINE> Indicates the online flag before switching of the peer card.
<STDBY_WORK> Indicates the working state of the local card before switching.
<HSC_WORK_PEER> Indicates the working state of the peer card before switching.
Example
l Command
RTRV-SWITCH-HIS::SLOT-9:100;
l Response Message
NE 2006-05-19 11:04:53
M 100 COMPLD
"SLOT_NUM=SLOT-9,SWITCH_TIME=\"2006-05-19 07:31:41
\",MANUAL_SWITCH=YES,AUTO_SWITCH=NO,FORCE_SWITCH=NO,PLUG_SWITCH=NO,BIOS_LINGER=NO,
BIOS_RESET=NO,AS_ENABLE=ENABLE,SELF_AS=ACTIVE,PEER_ONLINE=ONLINE,SELF_WORK=GOOD,PE
ER_WORK=BAD,READY_STATE=DISABLE,SOFT_DETECT=DISABLE,BAD_CODE=0"
"SLOT_NUM=SLOT-10,SWITCH_TIME=\"2006-05-19 07:44:34
\",MANUAL_SWITCH=YES,AUTO_SWITCH=NO,FORCE_SWITCH=NO,PLUG_SWITCH=NO,BIOS_LINGER=NO,
BIOS_RESET=NO,AS_ENABLE=ENABLE,SELF_AS=ACTIVE,PEER_ONLINE=ONLINE,SELF_WORK=GOOD,PE
ER_WORK=BAD,READY_STATE=DISABLE,SOFT_DETECT=DISABLE,BAD_CODE=0"
;
Related Commands
None
A.11.10 RTRV-BAD-INFO
Retrieves bad information about the active/standby switching.
Function
This command retrieves bad information about the active/standby switching.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-BAD-INFO:[<TID>]:<HSCSLOT_NUM>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"SLOT_NUM=<HSCSLOT_NUM>,FILE_NAME=<HSC_FILE_NAME>,FILE_LINE=<HSC_FILE_LINE>"<cr
><lf>
;
Response Parameters
Parameter Description
<HSC_FILE_NAME> Indicates the name of the file that is bad. It is a string with a
maximum of 20 characters.
Example
l Command
RTRV-BAD-INFO::SLOT-9:100;
l Response Message
NE 2006-05-19 11:00:58
M 100 COMPLD
"SLOT_NUM=SLOT-9,FILE_NAME=\"xcs_xcs_harddrv.cpp\",FILE_LINE=3685"
"SLOT_NUM=SLOT-9,FILE_NAME=\"xcs_xcs_harddrv.cpp\",FILE_LINE=3685"
"SLOT_NUM=SLOT-9,FILE_NAME=\"xcs_xcs_harddrv.cpp\",FILE_LINE=3685"
"SLOT_NUM=SLOT-9,FILE_NAME=\"xcs_xcs_harddrv.cpp\",FILE_LINE=3685"
;
Related Commands
None
A.11.11 RTRV-BACKUPMOD-INFO
Retrieves the information about the batch backup module.
Function
This command retrieves the information about the batch backup module.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-BACKUPMOD-INFO:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"
BACKUPMODID=<BACKUP_MOD_ID>,BACKUPSUBMODID=<BACKUP_SUBMODID>,BACKUPNUM=<BACKUP_NUM
>,ENTRYID=<ENTRY_ID>,FILENUM=<HBU_FILENUM>,MODREADY=<MOD_READY>,SMODREADY=<SMOD_RE
ADY>,A2S=<A2S_RECV>,ISPOST=<IS_POST>,POSTRESULT=<POST_RESULT>"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
Example
l Command
RTRV-BACKUPMOD-INFO:::100;
l Response Message
NE 1990-02-07 07:07:36
M 100 COMPLD
"BACKUPMODID=12,BACKUPSUBMODID=0,BACKUPNUM=0,ENTRYID=130,FILENUM=0,MODREADY=READY,
SMODREADY=READY,A2S=RECIEVE,ISPOST=NOTNEED,POSTRESULT=IDLE"
;
Related Commands
None
A.11.12 RTRV-BATCH-PROCESS
Retrieves the batch backup process.
Function
This command retrieves the batch backup process.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-BATCH-PROCESS:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf> ^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf> M^^<ctag>^COMPLD <cr><lf>
^^^"
PEERONLINE=<HBU_BDONLINE>,VERVERIFY=<VERSION_VERIFY>,SYNCENABLE=<SYNC_ENABLE>,NEST
ATE=<NE_STATE>,ASCOM=<AS_COM>,LASTAPPMOD=<LAST_APP_MOD>,DBMSRSPRECV=<DBMS_RSP_RECV
>,DBMSRSPRESLT=<DBMS_RSP_RESULT>,RECORSPRECV=<RECOVER_RSP_RECV>,RECVERLASTAPP=<REC
OVER_LASTMOD>,CFGSTDBYXC=<CFG_STDBY_XC>,POSTRECV=<POST_RECOVER_RECV>,POSTLASTMOD=<
POST_RECOVER_LASTMOD>,SMOOTHLASTAPP=<SMOOTH_LASTMOD>,ACTVERINFO=<ACTIVE_VERINFO>,S
TDVERINFO=<STDBY_VERINFO>"<cr><lf> ;
Response Parameters
Parameter Description
<AS_COM> Indicates the communication status between the active and standby
cards.
<LAST_APP_MOD> Indicates the last module which reponds to the HBU module.
<DBMS_RSP_RECV> Indicates whether the HBU module receives the response of DBMS
about the backup status.
<RECOVER_RSP_RE Indicates whether the HBU module receives the response of DBMS
CV> about the recovery status.
<RECOVER_LASTM Indicates the ID of the last module of the standby card that provides
OD> the HBU module with the response indicating the end of the
recovery.
<CFG_STDBY_XC> Indicates whether the active card receives the response from the
standby card about the total config take effects.
Example
l Command
RTRV-BATCH-PROCESS:::100;
l Response Message
NE 1990-02-07 07:07:36 M 100 COMPLD
"PEERONLINE=0,VERVERIFY=SUCCESS,SYNCENABLE=ENABLE,NESTATE=NE_RUNNING,ASCOM=SUCCESS
,LASTAPPMOD=65535,DBMSRSPRECV=NOTREVEIVE,DBMSRSPRESLT=0,RECORSPRECV=REVEIVE,RECVER
LASTAPP=9,CFGSTDBYXC=RECEIVE,POSTRECV=RECEIVE,POSTLASTMOD=65535,SMOOTHLASTAPP=0,AC
TVERINFO= NeSoft(T) 5.51.04.21T01 Platform(D) 050021B012,STDVERINFO= NeSoft(T)
5.51.04.21T01 Platform(D) 050021B012" ;
Related Commands
None
A.11.13 RTRV-SYNC-ENABLE
Retrieves the reason of synchronization enabling or diabling.
Function
This command retrieves the reason of synchronization enabling or diabling.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-SYNC-ENABLE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"HANDLE=<HANDLE>,FILENAME=<FILE_NAME>,FILELINE=<FILE_LINE>"
<cr><lf>
;
Response Parameters
NA
Example
l Command
RTRV-SYNC-ENABLE:::100;
l Response Message
NE 1990-02-07 07:07:36
M 100 COMPLD
;
Related Commands
None
A.11.14 RTRV-DX-MODE
Retrieves the switching mode.
Function
This command retrieves the switching mode.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-DX-MODE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"SWITCHMODE=<SWITCH_MODE>"<cr><lf>
;
Response Parameters
Parameter Description
<SWITCH_MODE> Indicates the switching mode. The valid values are COLD
(reset occurs after the switching) and WARM (no reset occurs
after the switching).
Example
l Command
RTRV-DX-MODE:::100;
l Response Message
NE 1990-02-07 07:07:36
M 100 COMPLD
"SWITCHMODE=WARM"
;
Related Commands
None
A.11.15 RTRV-DX-WORK
Retrieves the ID and working status of the active SCC card and the ID and working status of the
standby SCC card.
Function
This command retrieves the ID and working status of the active SCC card and the ID and working
status of the standby SCC card.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-DX-WORK:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"
ACTSLOT=<ACT_SLOT>,ACTWORK=<ACT_WORK>,STDBYSLOT=<STDBY_SLOT>,STDBYWORK=<STDBY_WORK
>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-DX-WORK:::100;
l Response Message
NE 2006-05-19 11:00:58
M 100 COMPLD
"ACTSLOT=SLOT-1-17,ACTWORK=GOOD,STDBYSLOT=SLOT-1-18,STDBYWORK=GOOD"
;
Related Commands
None
A.11.16 RTRV-DX-EQPT
Retrieves the ID of the active SCC card and the ID of the standby SCC card.
Function
This command retrieves the ID of the active SCC card and the ID of the standby SCC card.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-DX-EQPT:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^" ACTSLOT=<ACT_SLOT>,STDBYSLOT=<STDBY_SLOT>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-DX-EQPT:::100;
l Response Message
NE 2006-05-19 11:00:58
M 100 COMPLD
"ACTSLOT=SLOT-1-17,STDBYSLOT=SLOT-1-18"
;
Related Commands
None
A.11.17 RTRV-HD-STA
Retrieves the hardware status.
Function
This command retrieves the hardware status.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-HD-STA:[<TID>]:<HSCSLOT_NUM>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^" HDSTA=<HD_STA>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-HD-STA::SLOT-18:100;
l Response Message
NE 2006-05-19 11:00:58
M 100 COMPLD
HDSTA=<HF: 2>
;
Related Commands
None
A.11.18 RTRV-AS-ENABLE
Retrieves whether the switching is enabled or disabled.
Function
This command retrieves whether the switching is enabled or disabled.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-AS-ENABLE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^" ASENABLE=<HSCSWENABLE>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-AS-ENABLE:::100;
l Response Message
NE 2006-05-19 11:00:58
M 100 COMPLD
ASENABLE=ENABLE;
;
Related Commands
None
A.11.19 RTRV-FORCELOCK-SUPPORT
Retrieves the information about whether the forced/locked switching is supported.
Function
This command retrieves the information about whether the forced/locked switching is supported.
Usage Note
Supported by OSP08 and later versions.
Category
SCC protection switch
Security
Retrieve
Command Syntax
RTRV-FORCELOCK- SUPPORT:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<FORCE_LOCK_SUPPORT>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-FORCELOCK-SUPPORT:::100;
l Response Message
NE 1990-02-07 07:07:36
M 100 COMPLD
"YES"
;
Related Commands
None
A.11.20 RTRV-MANU-ENABLE
Retrieves the information about whether the switching is enabled or disabled and the reason.
Function
This command retrieves the information about whether the switching is enabled or disabled and
the reason.
Usage Note
None
Category
SCC protection switching
Security
Retrieve
Command Syntax
RTRV-MANU-ENABLE:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^" HANDLE=<HSC_HANDLE>,FILENAME=<HSCFILE_NAME>,FILELINE=<HSCFILE_LINE>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-MANU-ENABLE:::100;
l Response Message
NE 2006-05-19 11:00:58
M 100 COMPLD
;
Related Commands
None
A.11.21 SW-DX-EQPT
Executes SCC protecting switch.
Function
This command executes SCC protecting switch.
Usage Note
None
Category
SCC protection switching
Security
maintenance
Command Syntax
SW-DX-EQPT:[<TID>]:<HSCSLOT_NUM>:<CTAG>::<HSCSWMODE>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
SW-DX-EQPT::SLOT-1-17:100::MANUAL;
l Response Message
M 100 COMPLD
;
>
Related Commands
None
A.12.1.1 ENT-ERPS
Creates ERPS on a card.
Function
This command creates ERPS on a card.
Usage Note
ERPS defines the APS protocol and a protection switching mechanism for an ETH layer Ethernet
ring.
Category
Configuration
Security
Provisioning
Command Syntax
ENT-ERPS:
[<TID>]:<AID>:<CTAG>:::EASTPORT=<EASTPORT>,WESTPORT=<WESTPORT>,RP
LPORT=<RPLPORT>,RPLOWNER=<RPLOWNER>,CTRLVLAN=<CTRLVLAN>,DMA
C=<DMAC>,[GUARDTIME=<GUARDTIME>],[HOLDTIME=<HOLDTIME>],
[WTRTIME=<WTRTIME>],[MEL=<MEL>],[INTERVAL=<INTERVAL>];
Command Parameters
Parameter Description Default
Value
<AID> ERPS-<SHELF>-<SLOT>-<ERPS> NA
<EASTPORT> Indicates the east port. The valid values are as follows: NA
l 1-MAX_ETH_PORT: indicates an Ethernet port.
l 0x8001-0x8000+MAX_ETH_VCTRUNK:
indicates a VCTRUNK.
The valid formats are as follows:
FAC-<SHELF>-<SLOT>-<PORT>
ACC-<SHELF>-<SLOT>-<PORT>
<WESTPORT> Indicates the west port. The valid values are as follows: NA
l 1-MAX_ETH_PORT: indicates an Ethernet port.
l 0x8001-0x8000+MAX_ETH_VCTRUNK:
indicates a VCTRUNK.
The valid formats are as follows:
FAC-<SHELF>-<SLOT>-<PORT>
ACC-<SHELF>-<SLOT>-<PORT>
<RPLOWNER> Indicates the RPL owner flag. The valid values are as NOTOWNE
follows: R
l NOTOWNER: indicates that it is not an
RPLOWNER.
l OWNER: indicates that it is an RPLOWNER.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-
ERPS::ERPS-1-1-1:100:::EASTPORT=FAC-1-1-2,WESTPORT=FAC-1-1-3,RPLPORT=FAC-1-1-2,RPL
OWNER=OWNER,CTRLVLAN=1,DMAC=01-19-
A7-00-00-01,GUARDTIME=500,HOLDTIME=100,WTRTIME=5,MEL=4,INTERVAL=5;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.1.2 ED-ERPS
A.12.1.4 DLT-ERPS
A.12.1.3 RTRV-ERPS
A.12.1.2 ED-ERPS
Edits ERPS attributes.
Function
This command edits ERPS attributes.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-ERPS:[<TID>]:<AID>:<CTAG>:::[CTRLVLAN=<CTRLVLAN>],[DMAC=<DMAC>],
[GUARDTIME=<GUARDTIME>],[HOLDTIME=<HOLDTIME>],
[WTRTIME=<WTRTIME>],[MEL=<MEL>],[INTERVAL=<INTERVAL>];
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-ERPS::ERPS-1-1-1:100:::CTRLVLAN=1,DMAC=01-19-
A7-00-00-01,GUARDTIME=500,HOLDTIME=100,WTRTIME=5,MEL=4,INTERVAL=5;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.1.1 ENT-ERPS
A.12.1.4 DLT-ERPS
A.12.1.3 RTRV-ERPS
A.12.1.3 RTRV-ERPS
Retrieves ERPS attributes.
Function
This command retrieves ERPS attributes.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-ERPS:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::EASTPORT=<EASTPORT>,WESTPORT=<WESTPORT>,RPLPORT=<RPLPORT>,RPLOWNER=<RPL
OWNER>,CTRLVLAN=<CTRLVLAN>,DMAC=<DMAC>,NODEID=<NODEID>,
[LASTREQUEST=<LASTREQUEST>],[RECVPKTRB=<RECVPKTRB>],[RECVPKTDNF=<RECVPKTDNF>],
[FSMSTATE=<FSMSTATE>],[RECVPKTNODEID=<RECVPKTNODEID>],[GUARDTIME=<GUARDTIME>],
[HOLDTIME=<HOLDTIME>],[WTRTIME=<WTRTIME>],[MEL=<MEL>],
[INTERVAL=<INTERVAL>]"<cr><lf>
;
Response Parameters
Parameter Description
<EASTPORT> Indicates the east port. The valid formats are as follows:
FAC-<SHELF>-<SLOT>-<PORT>
ACC-<SHELF>-<SLOT>-<PORT>
<WESTPORT> Indicates the west port. The valid formats are as follows:
FAC-<SHELF>-<SLOT>-<PORT>
ACC-<SHELF>-<SLOT>-<PORT>
<RPLPORT> Indicates the RPL port. The valid formats are as follows:
FAC-<SHELF>-<SLOT>-<PORT>
ACC-<SHELF>-<SLOT>-<PORT>
0xFFFF: indicates an invalid port.
<RPLOWNER> Indicates the enable status of RPLOwner. The valid values are Y(1)
and N(0). The default value is N(0).
<CTRLVLAN> Indicates the identifier of the VLAN for control message of the ERPS
protocol.
The valid value ranges from 1 to 4094.
<LASTREQUEST Indicates the type of the most recent ERPS switching request. The valid
> values are as follows:
l RAPS(NR): a ring network automatic protection switching (RAPS)
message indicating no request
l RAPS(NR,RB): an RAPS message indicating no request and that
the ring protection link is blocked
l WTR-RUNNING: a message indicating that the WTR timer is in
a running state.
l WTR-EXPIRES: a message indicating that the WTR timer has
timed out
l RAPS(SF): an RAPS message indicating a signal failure
l LOCAL-SF: a message indicating a signal failure on the local node
l LOCAL-CLEAR-SF: a message indicating that the signal failure
on the local node is cleared
l INITIAL-REQUEST: the initial request
Parameter Description
<RECVPKTRB> Indicates the RB status on the current ring. The valid values are as
follows:
l NORB
l RB
<RECVPKTDNF> Indicates whether the DNF status is contained in a remote request. The
valid values are as follows:
l NODNF
l DNF
<FSMSTATE> Indicates the status of the state machine on the current node.
IDLE
PROTECTION
<RECVPKTNODE Indicates the source node of the switching request, that is, the source
ID> MAC address of the switching.
Example
l Command
RTRV-ERPS::ERPS-1-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"ERPS-1-1-1:: EASTPORT=FAC-1-1-2, WESTPORT=FAC-1-1-3, RPLPORT=FAC-1-1-2,
RPLOWNER=OWNER,CTRLVLAN=1,DMAC=01-19-A7-00-00-01, NODEID=01-19-
A7-00-00-01,LASTREQUEST= LOCAL-SF,RECVPKTRB=RB,RECVPKTDNF=DNF,FSMSTATE=
PROTECTION, RECVPKTNODEID =01-80-
C2-00-00-00,GUARDTIME=500,HOLDTIME=100,WTRTIME=5,MEL=4,INTERVAL=5"
;
Related Commands
A.12.1.1 ENT-ERPS
A.12.1.2 ED-ERPS
A.12.1.4 DLT-ERPS
A.12.1.4 DLT-ERPS
Deletes ERPS.
Function
This command deletes ERPS on a card.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-ERPS:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf> ;
Response Parameters
None
Example
l Command
DLT-ERPS::ERPS-1-1-10:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.1.1 ENT-ERPS
A.12.1.2 ED-ERPS
A.12.1.3 RTRV-ERPS
A.12.1.5 REPT^EVT^ERPS
Reports the switching state of ERPS.
Function
This command reports the switching state of ERPS.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
A^^<ATAG>^REPT^EVT^ERPS<cr><lf>
^^^"<AID>:<REQUEST>,<STATE>" <cr><lf>
;
Response Parameters
Parameter Description
<REQUEST> Indicates the type of the most recent ERPS switching request. The valid
values are as follows:
l RAPS(NR): a ring network automatic protection switching (RAPS)
message indicating no request
l RAPS(NR,RB): an RAPS message indicating no request and that
the ring protection link is blocked
l WTR-RUNNING: a message indicating that the WTR timer is in
a running state.
l WTR-EXPIRES: a message indicating that the WTR timer has
timed out
l RAPS(SF): an RAPS message indicating a signal failure
l LOCAL-SF: a message indicating a signal failure on the local node
l LOCAL-CLEAR-SF: a message indicating that the signal failure
on the local node is cleared
l INITIAL-REQUEST: the initial request
Example
l Command
RTRV-ERPS::ERPS-1-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
A 100 REPT EVT ERPS
"ERPS-1-1-2: Local SF, Protection "
;
Related Commands
None
A.12.2.1 ENT-LAG
Creates a link aggregation group (LAG).
Function
This command creates a LAG in the unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-LAG:[<TID>]:<AID>:<CTAG>:::[TYPE=<TYPE>],[BALANCE=<BALANCE>],
[SLVPORTS=<SLVPORTS>],[NAME=<NAME>],
[LAGSHAREMODE=<LAGSHAREMODE>],[LAGHOTIME=<LAGHOTIME>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-
LAG::FAC-1-1-1:100:::TYPE=MANUAL,BALANCE=Y,SLVPORTS=FAC-1-1-2&-3,NAME=HUAWEI,LAGSH
AREMODE=IP,LAGHOTIME=500;
l Response Message
NE 2005-08-05 16:55:00
M 100 COMPLD
;
Related Commands
A.12.2.2 ED-LAG
A.12.2.3 DLT-LAG
A.12.2.4 RTRV-LAG
A.12.2.2 ED-LAG
Edits a LAG (link aggregation group).
Function
This command modifies the attributes of the LAG in the unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-LAG:[<TID>]:<AID>:<CTAG>:::[SLVPORTS=<SLVPORTS>],[NAME=<NAME>],
[LAGSHAREMODE=<LAGSHAREMODE>],[LAGHOTIME=<LAGHOTIME>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-
LAG::FAC-1-1-1:100:::SLVPORTS=FAC-1-1-1&FAC-1-1-2,NAME=HUAWEI,LAGSHAREMODE=IP,LAGH
OTIME=500;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.12.2.1 ENT-LAG
A.12.2.3 DLT-LAG
A.12.2.4 RTRV-LAG
A.12.2.3 DLT-LAG
Deletes a link aggregation group (LAG).
Function
This command deletes a LAG in a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-LAG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-LAG::FAC-1-1-10:100;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.12.2.1 ENT-LAG
A.12.2.2 ED-LAG
A.12.2.4 RTRV-LAG
A.12.2.4 RTRV-LAG
Retrieves the attributes of a link aggregation group (LAG).
Function
This command retrieves the attributes of a LAG in a unit.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-LAG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[TYPE=<TYPE>],[BALANCE=<BALANCE>],[SLVPORTS=<SLVPORTS>],
[REFPORT=<REFPORT>],[LOCSYSPRI=<LOCSYSPRI>],[LOCSYSMAC=<LOCSYSMAC>],
[DSTSYSPRI=<DSTSYSPRI>],[DSTSYSMAC=<DSTSYSMAC>],[SELECTED=<SELECTED>],
[STANDBY=<STANDBY>],[LOCPORT=<LOCPORT>],[WORKSTATE=<WORKSTATE>],
[LOCPORTSTA=<LOCPORTSTA>],[LOCPORTPRI=<LOCPORTPRI>],[LOCOPRKEY=<LOCOPRKEY>],
[LOCLACP=<LOCLACP>],[DSTPORT=<DSTPORT>],[DSTPORTPRI=<DSTPORTPRI>],
[DSTOPRKEY=<DSTOPRKEY>],[DSTLACP=<DSTLACP>],[ACTPORTS=<ACTPORTS>],
[NAME=<NAME>]"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
<WORKSTATE> Indicates the status of the local LAG port. The valid values are Y and
N.
<LOCPORTSTA> Indicates the local port state. The valid values are SELECTED,
STANDBY and UNSELECTED.
<LOCLACP> Indicates the local Link Aggregation Control Protocol (LACP) state.
The valid value ranges from 0 to 255.
Parameter Description
<NAME> Indicates the name of the LAG. The valid value is a string of 0 to 31
bytes.
Example
l Command
RTRV-LAG::FAC-1-1-ALL:100;
l Response Message
NE 2005-08-05 18:05:00
M 100 COMPLD
"FAC-1-1-1::TYPE=MANUAL,BALANCE=Y,SLVPORTS=FAC-1-2-1,REFPORT=FAC-1-3,LOCSYSPRI=327
68,LOCSYSMAC=00-00-00-00-00-01,DSTSYSPRI=32768,DSTSYSMAC=00-00-00-00-00-02,SELECTE
D=1,STANDBY=0,LOCPORT=FAC-1-1-2,WORKSTATE=Y,LOCPORTSTA=SELECTED,LOCPORTPRI=32768,L
OCLACP=ENABLE,DSTPORT=FAC-1-1-2,DSTPORTPRI=32768,DSTLACP=ENABLE,ACTPORTS=FAC-1-1-1
&FAC-1-1-2,NAME=HUAWEI"
;
Related Commands
A.12.2.1 ENT-LAG
A.12.2.2 ED-LAG
A.12.2.3 DLT-LAG
A.12.2.5 ED-LAGSYS
Edits system attributes of a link aggregation group (LAG).
Function
This command modifies the attributes of a LAG.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-LAGSYS:[<TID>]:<AID>:<CTAG>:::[PRIORITY=<PRIORITY>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-LAGSYS::SLOT-1-1:100:::PRIORITY=1;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.12.2.6 RTRV-LAGSYS
A.12.2.6 RTRV-LAGSYS
Retrieves the attributes of a LAG system.
Function
This command retrieves the attributes of a LAG system.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-LAGSYS:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<SLOT>::[PRIORITY=<PRIORITY>],[MAC=<MAC>]"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-LAGSYS::SLOT-1-1:100;
RTRV-LAGSYS::SLOT-ALL:100;
l Response Message
NE 2005-08-05 18:05:00
M 100 COMPLD
"SLOT-1-1::PRIORITY=1,MAC=00-00-00-00-00-01"
;
Related Commands
A.12.2.5 ED-LAGSYS
A.12.2.7 ED-LAGPORT
Edits ports in a link aggregation group (LAG).
Function
This command modifies attributes of ports in a LAG.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-LAGPORT:[<TID>]:<AID>:<CTAG>:::PRIORITY=<PRIORITY>;
Command Parameters
Parameter Para Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-LAGPORT::FAC-1-1-1:100:::PRIORITY=1;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.12.2.8 RTRV-LAGPORT
A.12.2.8 RTRV-LAGPORT
Retrieves the port attributes of a link aggregation group (LAG).
Function
This command retrieves the port attributes of a LAG.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-LAGPORT:<TID>:[<AID>]:<CTAG>:::[FRAMETYPE=<FRAMETYPE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[LOCSYSPRI=<LOCSYSPRI>],[LOCSYSMAC=<LOCSYSMAC>],[PRIORITY=<PRIORITY>],
[KEY=<KEY>],[LOCLACP=<LOCLACP>],[DSTSYSPRI=<DSTSYSPRI>],[DSTSYSMAC=<DSTSYSMAC>],
[DSTPORT=<DSTPORT>],[DSTPRI=<DSTPRI>],[DSTKEY=<DSTKEY>],[DSTLACP=<DSTLACP>],
[<RCVLACPDUNUM>=<RCVLACPDUNUM>],[<RCVERRLACPDUNUM >=<RCVERRLACPDUNUM>],
[<SNDLACPDUNUM>=<SNDLACPDUNUM>]"<cr><lf>
;
Response Parameters
Parameter Description
<AID> Indicates the Ethernet facility which is composed of the slot number
and port ID.
The valid formats are as follows:
l FAC-<SHELF ID>-<SLOT ID>-<PORT ID>
l ACC-<SHELF ID>-<SLOT ID>-<PORT ID>
<LOCLACP> Indicates the local LACP (link aggregation control protocol) state.
The valid value ranges from 0 to 255.
Parameter Description
Example
l Command
RTRV-LAGPORT::FAC-1-1-1:100:::FRAMETYPE=RCVLACPDU;
RTRV-LAGPORT::FAC-1-1-ALL:100:::FRAMETYPE=RCVLACPDU;
l Response Message
NE 2005-08-05 18:05:00
M 100 COMPLD
"FAC-1-1-5::LOCSYSPRI=32768,LOCSYSMAC=00-00-
ef-10-38-10,PRIORITY=32768,KEY=257,LOCLACP=71,DSTSYSPRI=32768,DSTSYSMAC=00-00-00-0
0-00-00,DSTPRI=32768,DSTKEY=0,DSTLACP=48,RCVLACPDUNUM=0,RCVERRLACPDUNUM=0,SNDLACPD
UNUM=0"
;
Related Commands
A.12.2.7 ED-LAGPORT
A.12.2.9 INIT-LAGPORT
Initializes the port attributes of a LAG.
Function
This command initiates the port attributes of a LAG.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
INIT-LAGPORT:[<TID>]:<AID>:<CTAG>:::[FRAMETYPE=<FRAMETYPE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
INIT-LAGPORT::FAC-1-1-1:100:::FRAMETYPE=ALL;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.12.2.7 ED-LAGPORT
A.12.2.8 RTRV-LAGPORT
A.12.2.10 ENT-DLAG
Creates a distributed link aggregation group (DLAG).
Function
This command creates a DLAG between two units.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-DLAG:[<TID>]:<AID>:<CTAG>:::[MSTPORTPRI=<MSTPORTPRI>],
[SLVPORT=<SLVPORT>],[SLVPORTPRI=<SLVPORTPRI>],[NAME=<NAME>],
[SYSPRI=<SYSPRI>],[RVRTV=<RVRTV>];
Command Parameters
Parameter Description Default
Value
<MSTPORTPRI> Indicates the priority of the master port on the LAG. 32768
The port with the higher priority is the master port if a
LAG involves two or more cards.
The valid value ranges from 0 to 65535.
<SLVPORTPRI> Indicates the priority of the salve port on the LAG. 32768
The valid value ranges from 0 to 65535.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-
DLAG::FAC-1-1-3:100:::MSPORTPRI=8,SLVPORT=FAC-1-1-4,SLVPORTPRI=8,NAME=aaa,SYSPRI=9
,RVRTV=N;
l Response Message
NE 2008-08-05 16:55:00
M 100 COMPLD
;
Related Commands
A.12.2.11 ED-DLAG
A.12.2.12 DLT-DLAG
A.12.2.13 RTRV-DLAG
A.12.2.11 ED-DLAG
Edits a distributed link aggregation group (DLAG).
Function
This command modifies the attributes of a DLAG between two units.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-DLAG:[<TID>]:<AID>:<CTAG>:::[MSTPORTPRI=<MSTPORTPRI>],
[SLVPORTPRI=<SLVPORTPRI>],[NAME=<NAME>],[SYSPRI=<SYSPRI>],
[RVRTV=<RVRTV>];
Command Parameters
Parameter Description Default Value
<MSTPORTP Indicates the priority of the master port on the LAG. 32768
RI> The port with the higher priority is the master port if a
LAG involves two or more cards.
The valid value ranges from 0 to 65535.
<SLVPORTP Indicates the priority of the salve port on the LAG. 32768
RI> The valid value ranges from 0 to 65535.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-DLAG::FAC-1-1-3-4:100:::MSTPORTPRI=8,SLVPORTPRI=8,NAME=DLAG-A,SYSPRI=9,RVRTV=n;
l Response Message
NE 2005-08-05 16:55:00
M 100 COMPLD
;
Related Commands
A.12.2.10 ENT-DLAG
A.12.2.12 DLT-DLAG
A.12.2.13 RTRV-DLAG
A.12.2.12 DLT-DLAG
Deletes a distributed link aggregation group (DLAG).
Function
This command deletes a DLAG between two units.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-LAG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-DLAG::FAC-1-1-10:100;
l Response Message
NE 2004-07-10 15:33:17
M 10 COMPLD
;
Related Commands
A.12.2.10 ENT-DLAG
A.12.2.11 ED-DLAG
A.12.2.13 RTRV-DLAG
A.12.2.13 RTRV-DLAG
Retrieves the information about a distributed link aggregation group (DLAG).
Function
This command retrieves the attributes of a DLAG between two units.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-DLAG:[<TID>]:<AID>:<CTAG>:::[FRAMETYPE=<FRAMETYPE>];
Command Parameters
Parameter Description Default
Value
<FRAMET Indicates the frame type. The valid value are as follows: ALL
YPE> l RCVLACPDU
l RCVERRLACPDU
l SNDLACPDU
l ALL
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"::[MSTPORT=<MSTPORT>],[MSTPORTPRI=<MSTPORTPRI>],[SLVPORT=<SLVPORT>],
[SLVPORTPRI=<SLVPORTPRI>],[NAME=<NAME>],[SYSPRI=<SYSPRI>], [SYSMAC=<SYSMAC>],
[RVRTV=<RVRTV>],[WORKPORT=<WORKPORT>],[LOCMSTPORT=<LOCMSTPORT>],
[LOCMSTPORTSTA=<LOCMSTPORTSTA>],[LOCMSTPORTPRI=<LOCMSTPORTPRI>],
[LOCMSTOPRKEY=<LOCMSTOPRKEY>],[LOCMSTLACP=<LOCMSTLACP>], [DSTSYSPRI=<DSTSYSPRI>],
[DSTSYSMAC=<DSTSYSMAC>],[DSTMSTPORT=<DSTMSTPORT>],[DSTMSTPORTPRI=<DSTMSTPORTPRI>],
[DSTMSTOPRKEY=<DSTMSTOPRKEY>],[DSTMSTLACP=<DSTMSTLACP>],[LOCSLVPORT=<LOCSLVPORT>],
[LOCSLVPORTSTA=<LOCSLVPORTSTA>],[LOCSLVPORTPRI=<LOCSLVPORTPRI>],
[LOCSLVOPRKEY=<LOCSLVOPRKEY>],[LOCSLVLACP=<LOCSLVLACP>],[DSTSLVPORT=<DSTSLVPORT>],
[DSTSLVPORTPRI=<DSTSLVPORTPRI>],[DSTSLVOPRKEY=<DSTSLVOPRKEY>],
[DSTSLVLACP=<DSTSLVLACP>],[SHAREMODE=<SHAREMODE>],
[<MSTRCVLACPDUNUM>=<MSTRCVLACPDUNUM>],[<MSTRCVERRLACPDUNUM>=<MSTRCVERRLACPDUNUM>],
[<MSTSNDLACPDUNUM>=<MSTSNDLACPDUNUM>],[<SLVRCVLACPDUNUM>=<SLVRCVLACPDUNUM>],
[<SLVRCVERRLACPDUNUM>=<SLVRCVERRLACPDUNUM>],
[<SLVSNDLACPDUNUM>=<SLVSNDLACPDUNUM>]"<cr><lf>;
Response Parameters
Parameter Para Description
<NAME> Indicates the name of the DLAG. The valid format is a string of 0 to
31 bytes.
<RVRTV> Indicates the revertive mode. The valid values are Y (revertive mode)
and N (non-revertive mode).
<LOCMSTPORTS Indicates the local master port state. The valid values are SELECTED
TA> and STANDBY.
<LOCMSTLACP> Indicates the local master link aggregation control protocol (LACP)
state. The valid values are ENABLE and DISABLE.
<DSTMSTLACP> Indicates the destination master LACP state. The valid values are
ENABLE and DISABLE.
<LOCSLVPORTS Indicates the local slave port state. The valid values are SELECTED
TA> and STANDBY.
<LOCSLVLACP> Indicates the local slave LACP state. The valid values are ENABLE
and DISABLE.
<DSTSLVLACP> Indicates the destination slave LACP state. The valid values are
ENABLE and DISABLE.
<SHAREMODE> Indicates the share mode. The valid values are SHARE and
NONSHARE.
Example
l Command
RTRV-DLAG::FAC-2-5-5:C;
l Response Message
NE 2008-08-25 18:38:24
M C COMPLD
"FAC-3-11::MSPORTPRI=8,SLVPORT=FAC-4-11,SLVPORTPRI=8,NAME=aaa,SYSPRI=9,SYSMAC=00-
ab-ca-
ef-12-34,RVRTV=Y,WORKPORT=FAC-0-0,LOCMSTPORT=FAC-3-11,LOCMSTPORTSTA=UNSELECTED,LOC
MSTPORTPRI=8,LOCMSTOPRKEY=33025,LOCMSTLACP=71,DSTSYSPRI=32768,DSTSYSMAC=00-00-00-0
0-00-00,DSTMSTPORTPRI=32768,DSTMSTOPRKEY=0,DSTMSTLACP=48,LOCSLVPORT=FAC-4-11,LOCSL
VPORTSTA=UNSELECTED,LOCSLVPORTPRI=8,LOCSLVOPRKEY=33025,LOCSLVLACP=71,DSTSLVPORTPRI
=32768,DSTSLVOPRKEY=0,DSTSLVLACP=48,SHAREMODE=NONSHARE"
;
Related Commands
A.12.2.10 ENT-DLAG
A.12.2.11 ED-DLAG
A.12.2.12 DLT-DLAG
A.12.2.14 DLT-MCLAG
Deletes a multi-chassis link aggregation group (MC-LAG).
Function
This command deletes an MC-LAG.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-MCLAG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-MCLAG::FAC-1-1-10:100;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
ENT-MCLAGA.12.2.1 ENT-LAG
ED-MCLAGA.12.2.2 ED-LAG
RTRV-MCLAGA.12.2.4 RTRV-LAG
A.12.2.15 ED-MCLAG
Modifies a multi-chassis link aggregation group (MC-LAG).
Function
This command modifies an MC-LAG.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-MCLAG:[<TID>]:<AID>:<CTAG>:::[MCSP=<MCSP>],[RVRTV=<RVRTV>],
[RVTM=<RVTM>],[ASSPORT=<ASSPORT>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-MCLAG::FAC-1-1-1:100:::MCSP=ACC-1-1-1,RVRTV=Y,RVTM=10,ASSPORT=FAC-1-1-2&-3;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
ENT-MCLAGA.12.2.1 ENT-LAG
RTRV-MCLAGA.12.2.3 DLT-LAG
DLT-MCLAGA.12.2.4 RTRV-LAG
A.12.2.16 ENT-MCLAG
Creates a multi-chassis link aggregation group (MC-LAG).
Function
This command creates an MC-LAG.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-MCLAG:[<TID>]:<AID>:<CTAG>:::RMTLAG=<RMTLAG>,MCSP=<MCSP>,
[PROTTYPE=<PROTTYPE>],[RVRTV=<RVRTV>],[RVTM=<RVTM>],
[ASSPORT=<ASSPORT>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-
MCLAG::FAC-1-1-1:100:::RMTLAG=FAC-1-1-1,MCSP=ACC-1-1-1,PROTTYPE=ERPS,RVRTV=Y,RVTM=
1,ASSPORT=FAC-1-1-2&-3;
l Response Message
NE 2005-08-05 16:55:00
M 100 COMPLD
;
Related Commands
ED-MCLAGA.12.2.2 ED-LAG
RTRV-MCLAGA.12.2.3 DLT-LAG
DLT-MCLAGA.12.2.4 RTRV-LAG
A.12.2.17 RTRV-MCLAG
Queries an MC-LAG.
Function
This command queries an MC-LAG.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MCLAG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::RMTLAG=<RMTLAG>,MCSP=<MCSP>,PROTTYPE=<PROTTYPE>,[RVRTV=<RVRTV>],
[RVTM=<RVTM>],[ASSPORT=<ASSPORT>],[MCLAGSTAT=<MCLAGSTAT>],
[LAGSTAT=<LAGSTAT>]"<cr><lf>
;
Response Parameters
Parameter Description
<PROTTYPE> Indicates the type of protection that can be configured with MC-LAG.
ERPS
MSSNCP
<MCLAGSTAT> Indicates the working status of the MC-LAG. The local LAG
cooperates with the remote LAG when the communication between
them is normal. They work independently and the client equipment
selectively receives services when the communication between them
is abnormal.
COLLABORATIVE: The local LAG cooperates with the remote
LAG.
INDEPENDENT: The local LAG and remote LAG work
independently.
Parameter Description
Example
l Command
RTRV-MCLAG::FAC-1-1-1:100;
RTRV-MCLAG::FAC-1-1-ALL:100;
l Response Message
NE 2005-08-05 18:05:00
M 100 COMPLD
"FAC-1-1-1::RMTLAG=FAC-1-1-1,MCSP=ACC-1-1-1,PROTTYPE=ERPS,RVRTV=Y,RVTM=5,ASSPORT=F
AC-1-1-2&FAC-1-1-3,MCLAGSTAT=COLLABORATIVE,LAGSTAT=ACTIVE"
;
Related Commands
ENT-MCLAGA.12.2.1 ENT-LAG
ED-MCLAGA.12.2.2 ED-LAG
DLT-MCLAGA.12.2.3 DLT-LAG
A.12.2.18 DLT-MCSP
Deletes a multi-chassis service path (MCSP).
Function
This command deletes an MCSP.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-MCSP:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-MCSP::FAC-1-1-10:100;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
ENT-MCSPA.12.2.1 ENT-LAG
ED-MCSPA.12.2.2 ED-LAG
RTRV-MCSPA.12.2.4 RTRV-LAG
A.12.2.19 ED-MCSP
Modifies a multi-chassis service path (MCSP).
Function
This command modifies an MCSP.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-MCSP:[<TID>]:<AID>:<CTAG>:::[MONTM=<MONTM>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-MCSP::FAC-1-1-1:100:::MONTM=10;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
ENT-MCSPA.12.2.1 ENT-LAG
RTRV-MCSPA.12.2.3 DLT-LAG
DLT-MCSPA.12.2.4 RTRV-LAG
A.12.2.20 ENT-MCSP
Creates a multi-chassis synchronization protocol (MCSP).
Function
This command creates an MCSP.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-MCSP:[<TID>]:<AID>:<CTAG>:::COMMFLAG=<COMMFLAG>,
[MONTM=<MONTM>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-MCSP::FAC-1-1-1:100:::COMMFLAG=1,MONTM=10;
l Response Message
NE 2005-08-05 16:55:00
M 100 COMPLD
;
Related Commands
ED-MCSPA.12.2.2 ED-LAG
RTRV-MCSPA.12.2.3 DLT-LAG
DLT-MCSPA.12.2.4 RTRV-LAG
A.12.2.21 RTRV-MCSP
Queries an MCSP.
Function
This command queries an MCSP.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MCSP:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::COMMFLAG=<COMMFLAG>,MONTM=<MONTM>,STAT=<STAT>"<cr><lf>
;
Response Parameters
Parameter Description
<COMMFLAG> Indicates the MCSP number. The MCSP number is unique on each
board. The local MSCP can communicate with the peer MCSP only
when they have the same number.
The value ranges from 1 to MAX_ETH_MCSP.
l Note: MAX_ETH_MCSP indicates the maximum number of
MCSPs that can be configured on a board.
<MONTM> Indicates the interval for sending Hello packets that are used for
monitoring faults.
l The value ranges from 1s to 10s.
Example
l Command
RTRV-MCSP::FAC-1-1-1:100;
RTRV-MCSP::FAC-1-1-ALL:100;
l Response Message
NE 2005-08-05 18:05:00
M 100 COMPLD
"FAC-1-1-1::COMMFLAG=1,MONTM=10,STAT=UP"
;
Related Commands
ENT-MCLAGA.12.2.1 ENT-LAG
ED-MCLAGA.12.2.2 ED-LAG
DLT-MCLAGA.12.2.3 DLT-LAG
A.12.2.22 INIT-LACP-PKT
Clears statistics on the number of transmitted and received Link Aggregation Control Protocol
(LACP) packets.
Function
This command clears statistics on the number of transmitted and received LACP packets.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
INIT-LACP-PKT:[<TID>]:<AID>:<CTAG>:::PKTTYPE=<PKTTYPE>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
INIT-LACP-PKT::FAC-1-1-1:100:::PKTTYPE=1;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
RTRV-LACP-PKTA.12.2.7 ED-LAGPORT
A.12.2.8 RTRV-LAGPORT
A.12.2.23 RTRV-LACP-PKT
Queries statistics on the number of transmitted and received LACP packets.
Function
This command queries statistics on the number of transmitted and received LACP packets.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-LACP-PKT:<TID>:[<AID>]:<CTAG>:::PKTTYPE=<PKTTYPE>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::PKTTYPE=<PKTTYPE>,PKTCNT=<PKTCNT>"<cr><lf>
;
Response Parameters
Parameter Description
<AID> Indicates the Ethernet facility which is composed of the slot number
and port ID.
The valid formats are as follows:
l FAC-<SHELF ID>-<SLOT ID>-<PORT ID>
l ACC-<SHELF ID>-<SLOT ID>-<PORT ID>
Example
l Command
RTRV-LACP-PKT::FAC-1-1-1:100:::PKTTYPE=1;
l Response Message
NE 2005-08-05 18:05:00
M 100 COMPLD
"FAC-1-1-1::PKTTYPE=1,PKTCNT=100"
"FAC-1-1-1::PKTTYPE=2,PKTCNT=0"
"FAC-1-1-1::PKTTYPE=3,PKTCNT=10"
Related Commands
INIT-LACP-PKTA.12.2.7 ED-LAGPORT
A.12.2.24 INIT-LAGSTAST-<FETH/GETH>
Clear the counter of linkagg port.
Function
Clear the counter of linkagg port.
Usage Note
None
Category
Configuration
Security
Debug
Command Syntax
INIT-LAGSTAT-<FETH/GETH>:
[<TID>]:<AID>:<CTAG>:::FRAMETYPE=<FRAMETYPE>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
INIT-LAGSTAT-GETH::FAC-1-1-4:100:::FRAMETYPE=RCVLACPDU;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.2.25 RTRV-LAGSTAT-<FETH/GETH>
A.12.2.25 RTRV-LAGSTAT-<FETH/GETH>
Retrieves the packet content of a port test.
Function
This command instructs the NE to retrieve the packet content of a port test.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-LAGSTAT-<FETH/GETH>:
[<TID>]:<AID>:<CTAG>:::FRAMETYPE=<FRAMETYPE>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::FRAMETYPE=<FRAMETYPE>,[FRAMENUM=<FRAMENUM>]"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-LAGSTAT-GETH::FAC-1-1-4:100:::FRAMETYPE=ALL;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FAC-1-1-1::FRAMETYPE=RCVLACPDU,FRAMENUM=5000"
;
Related Commands
A.12.2.24 INIT-LAGSTAST-<FETH/GETH>
A.12.2.26 RTRV-STATE-LAGPORT
Retrieve the state of the state machine in a LAGPORT.
Function
This command retrieves the state of the state machine in a LAGPORT.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-STATE-LAGPORT:<TID>:[<AID>]:<CTAG>:::[SMTYPE=<SMTYPE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[SMTYPE=<SMTYPE>],[CURSTATE=<CURSTATE>],[PRESTATE=<PRESTATE>],
[REASON=<REASON>]"<cr><lf>
;
Response Parameters
Parameter Description
<AID> Indicates the Ethernet facility which is composed of the slot number
and port ID.
The valid formats are as follows:
l FAC-<SHELF ID>-<SLOT ID>-<PORT ID>
l ACC-<SHELF ID>-<SLOT ID>-<PORT ID>
<REASON> Indicates why the state of the state machine changes into
<CURSTATE>.
Example
l Command
RTRV-STATE-LAGPORT::FAC-1-1:100:::SMTYPE=RX;
RTRV-STATE-LAGPORT::FAC-1-ALL:100:::SMTYPE=RX;
l Response Message
NE 2005-08-05 18:05:00
M 100 COMPLD
"FAC-1-1::SMTYPE=RX,CURSTATE=RXINIT,LSTSTATE=RXINIT,REASON=INITIALIZE"
;
Related Commands
A.12.2.7 ED-LAGPORT
A.12.3.1 ED-STP-VB
Edits the spanning tree protocol (STP) of a virtual bridge.
Function
This command modifies the spanning tree protocol of a virtual bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-STP-VB:[<TID>]:<AID>:<CTAG>:::[STPENABLE=<STPENABLE>],
[STPMODE=<STPMODE>],[BPRI=<BPRI>],[HELLOTIME=<HELLOTIME>],
[MAXAGE=<MAXAGE>],[FWDDELAY=<FWDDELAY>];
Command Parameters
Parameter Description Default Value
<STPMODE Indicates the working mode of the rapid spanning tree RSTP
> protocol (RSTP). The valid values are as follows:
l STP: The RSTP operates in the STP compatibility
mode.
l RSTP: The RSTP operates normally.
This parameter is required only if the equipment
supports RSTP.
<FWDDELA Indicates the time interval for switching the port state, 15
Y> the port state includes: discarding, learning and
forwarding. <FWDDELAY> is a integer. The valid
value ranges from 4(s) to 30(s).
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-STP-
VB::VB-1-4-1:100:::STPENABLE=Y,STPMODE=STP,BPRI=1,HELLOTIME=2,MAXAGE=20,FWDDELAY=1
5;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.3.2 RTRV-STP-VB
A.12.3.3 INIT-STP-VB
A.12.3.2 RTRV-STP-VB
Retrieves the attributes of the Spanning Tree Protocol (STP) within a virtual bridge
Function
This command retrieves the attributes of the STP protocol within a virtual bridge.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-STP-VB:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::STPENABLE=<STPENABLE>,STPMODE=<STPMODE>,BPRI=<BPRI>,BMAC=<BMAC>,HELLOTI
ME=<HELLOTIME>,ACTHELLOTIME=<ACTHELLOTIME>,MAXAGE=<MAXAGE>,ACTMAXAGE=<ACTMAXAGE>,F
WDDELAY=<FWDDELAY>,ACTFWDDELAY=<ACTFWDDELAY>,DROOTPRI=<DROOTPRI>,DROOTMAC=<DROOTMA
C>,ROOTPATH=<ROOTPATH>,ROOTPORTID=<ROOTPORTID>,HOLDTIME=<HOLDTIME>"<cr><lf>
;
Response Parameters
Parameter Description
<STPENABLE> Indicates whether the STP protocol is enabled. The valid values are Y
and N.
<STPMODE> Indicates the work mode of the Rapid Spanning Tree Protocol (RSTP).
The valid values are as follows:
l STP: The RSTP operates in STP Compatibility mode.
l RSTP: The RSTP operates normally.
This parameter is required only if the equipment supports RSTP.
<BPRI> Indicates the priority of a virtual bridge. The valid value ranges from
0 to 65535, among which "0" is the highest priority.
<ACTHELLOTIM Indicates the actual HELLOTIME. The valid value ranges from 1(s)
E> to 10(s).
<MAXAGE> Indicates the aging time of the BPDU. It is an integer. The valid value
ranges from 6(s) to 40(s). The initial value is 20(s).
<ACTMAXAGE> The actual MAXAGE. The valid value ranges from 6(s) to 40(s).
Parameter Description
<FWDDELAY> Indicates the time interval for switching the port state, the port state
includes: discarding, learning and forwarding. <FWDDELAY>It is an
integer. The valid value ranges from 4(s) to 30(s). The initial value is
15(s).
<ACTFWDDELA Indicates the actual FWDDELAY. The valid value ranges from 4(s) to
Y> 30(s).
<HOLDTIME> Indicates the period from the latest reset or initialization till the current
time.
The valid value ranges from 1 to 10.
Example
l Command
RTRV-STP-VB::VB-1-4-1:100;
RTRV-STP-VB::VB-1-4-ALL:101;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VB-1-4-1::STPENABLE=Y,STPMODE=STP,BPRI=1,BMAC=00-32-0B-0E-10-0D,HELLOTIME=1,ACTHE
LLOTIME=1,MAXAGE=20,ACTMAXAGE=20,FWDDELAY=10,ACTFWDDELAY=10,MAXINC=2,DROOTPRI=1,DR
OOTMAC=00-32-0B-0E-10-0E,ROOTPATH=1,ROOTPORTID=12,HOLDTIME=5"
;
Related Commands
A.12.3.1 ED-STP-VB
A.12.3.3 INIT-STP-VB
A.12.3.3 INIT-STP-VB
Initializes the spanning tree protocol (STP) of a VB.
Function
This command is used to initialize the STP.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
INIT-STP-VB:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
INIT-STP-VB::VB-1-4-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.3.1 ED-STP-VB
A.12.3.2 RTRV-STP-VB
A.12.3.4 ED-STP-VBLP
Edits parameters of the spanning tree protocol within a VBLP.
Function
This command modifies the parameters of the spanning tree protocol within a VBLP.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-STP-VBLP:[<TID>]:<AID>:<CTAG>:::[STPPORTENABLE=<STPPORTENABLE>],
[PORTPRI=<PORTPRI>],[PATHCOST=<PATHCOST>],[ADMEDGE=<ADMEDGE>],
[AUTOEDGEDETECTEN =<AUTOEDGEDETECTEN>];
Command Parameters
Parameter Description Default Value
<PORTPRI> Indicates the priority of the port. The valid value ranges 128
from 0 to 240,and can be divided by 16.among which
"0" is the highest priority.
<PATHCOST Indicates the path cost of the root bridge. For Ethernet
> For cards compliant with [802.1w] standard, the valid interface: 19
value ranges from 1 to 65535. For VC-Trunk
For cards compliant with [802.1D] standard, the valid interface: 4
value ranges from 1 to 200000000.
The default values vary depending on the interfaces.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-STP-VBLP::VBLP-1-1-1-3:100:::STPPORTENABLE=Y,PORTPRI=128,PATHCOST=19,ADMEDGE=N;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.3.5 RTRV-STP-VBLP
A.12.3.5 RTRV-STP-VBLP
Retrieves parameters of the STP protocol within a VBLP.
Function
This command instructs an NE to retrieve the parameters of the STP protocol within a VBLP.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-STP-VBLP:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::STPPORTENABLE=<STPPORTENABLE>,PORTPRI=<PORTPRI>,PATHCOST=<PATHCOST>,ACT
PATHCOST=<ACTPATHCOST>,ADMEDGE=<ADMEDGE>,ACTADMEDGE=<ACTADMEDGE>,PORTID=<PORTID>,P
ORTSTATE=<PORTSTATE>,DPORTID=<DPORTID>,DROOTPRI=<DROOTPRI>,DROOTMAC=<DROOTMAC>,DCO
ST=<DCOST>,DBPRI=<DBPRI>,DBMAC=<DBMAC>,UPTIME=<UPTIME>,AUTOEDGEDETECTEN=<AUTOEDGED
ETECTEN>"<cr><lf>
;
Response Parameters
Parameter Description
<STPPORTENABLE> Indicates whether the VBLP is enabled. The valid value can be
Y or N.
<PORTPRI> Indicates the priority of a VBLP. The valid value ranges from
0 to 255, among which "0" is the highest priority and "128" is
the initial value.
Parameter Description
<PORTSTATE> Indicates the current state of a VBLP. The valid values are as
follows:
l DISABLE
l LISTENING
l LEARNING
l FORWARDING
l BLOCKING
l DISCARDING
<UPTIME> Indicates the time elapsed since the port was last reset or
initialized. The value is expressed in seconds.
Example
l Command
RTRV-STP-VBLP::VBLP-1-1-1-3:100;
RTRV-STP-VBLP::VBLP-1-1-1-ALL:101;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VBLP-1-1-1-3::STPPORTENABLE=Y,PORTPRI=128,PATHCOST=19,ACTPATHCOST=19,ADMEDGE=N,AC
TADMEDGE=N,PORTID=10,PORTSTATE=FORWARDING,DPORTID=12,DROOTPRI=1,DROOTMAC=00-32-0B-
0E-10-0D,DCOST=30,DBPRI=4,DBMAC=00-32-0B-0E-10-0E,UPTIME=50,AUTOEDGEDETECTEN=DISAB
LE"
;
Related Commands
A.12.3.4 ED-STP-VBLP
A.12.3.6 SW-STP-VBLP
Switches the STP state of the VBLP.
Function
This command switches the STP state of the VBLP to send bridge protocol data unit (BPDU)
of the rapid spanning tree protocol (RSTP) to the interconnected network.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
SW-STP-VBLP:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
SW-STP-VBLP::VBLP-1-1-1-3:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
None
A.12.3.7 REPT^EVT^VBLP
Reports the STP state of a virtual bridge logical port (VBLP).
Function
This command is used for an NE to report the STP state of a VBLP.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
A^^<ATAG>^REPT^EVT^VBLP<cr><lf>
^^^"<AID>:<CONDYPE>,<CONDEFF>" <cr><lf> ;
Response Parameters
Parameter Description
<CONDYPE> Indicates the type of the event. The valid values are as follows:
l STPPORT-DISABLE (0)
l STPPORT-LISTENING (1)
l STPPORT-LEARNING (2)
l STPPORT-FORWARDING (3)
l STPPORT-BLOCKING (4)
l STPPORT-DISCARDING (5)
<CONDEFF> Indicates the impact of the event on the NE. The valid value is
TC.
Example
l Command
None
l Response Message
NE 2003-02-28 12:23:20
A 100 REPT EVT VBLP
"VBLP-1-1-1-2-3:STPPORT-DISABLE,TC"
;
Related Commands
None
A.12.4.1 ENT-VLANSNCP-PG
Creates a VLAN SNCP group.
Function
This command creates a VLAN SNCP protection group.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-VLANSNCP-PG:
[<TID>]::<CTAG>:::WORKLINKFROM=<WORKLINKFROM>,WORKLINKTO=<WOR
KLINKTO>,[WORKLINKINTAG=<WORKLINKINTAG>],
[WORKLINKINSTAG=<ORKLINKINSTAG>],BACKUPLINKFROM=<BACKUPLINKF
ROM>,BACKUPLINKTO=<BACKUPLINKTO>,
[BACKUPLINKINTAG=<BACKUPLINKINTAG>],
[BACKUPLINKINSTAG=<BACKUPLINKINSTAG>],[SOURCEIP =<SOURCEIP>],
[RVRTV =<RVRTV>],[RVTM=<RVTM>],[HOLDOFFTIME=<HOLDOFFTIME>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-VLANSNCP-PG:::
100:::WORKLINKFROM=FAC-1-3-4,WORKLINKTO=FAC-1-3-5,WORKLINKINTAG=1,BACKUPLINKFROM=F
AC-1-3-6,BACKUPLINKTO=FAC-1-3-5,BACKUPLINKINTAG=1,RVRTV=N,RVTM=0;
l Response Message
NE 2008-08-25 18:54:51
M 100 COMPLD
;
Related Commands
A.12.4.2 ED-VLANSNCP-PG
A.12.4.4 DLT-VLANSNCP-PG
A.12.4.3 RTRV-VLANSNCP-PG
A.12.4.2 ED-VLANSNCP-PG
Edits the parameters of a VLAN SNCP group.
Function
This command edits the parameters of a VLAN SNCP group.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-VLANSNCP-PG:
[<TID>]::<CTAG>:::LINKFROM=<LINKFROM>,LINKTO=<WORKLINKTO>,
[LINKINTAG=<LINKINTAG>],[LINKINSTAG=<LINKINSTAG>],[RVRTV=<RVRTV>],
[RVTM=<RVTM>],[HOLDOFFTIME=<HOLDOFFTIME>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-VLANSNCP-PG:::
10:::LINKFROM=FAC-1-3-4,LINKTO=FAC-1-3-5,LINKINTAG=1,RVRTV=Y,HOLDOFFTIME=100;
l Response Message
NE 2003-02-28 12:23:20
M 10 COMPLD
;
Related Commands
A.12.4.1 ENT-VLANSNCP-PG
A.12.4.4 DLT-VLANSNCP-PG
A.12.4.3 RTRV-VLANSNCP-PG
A.12.4.3 RTRV-VLANSNCP-PG
Retrieves the parameters of a VLAN SNCP group.
Function
This command retrieves the parameters of a VLAN SNCP group.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-VLANSNCP-PG:[<TID>]::<CTAG>:::LINKFROM =<LINKFROM>,LINKTO
=<LINKTO>,[LINKINTAG =<LINKINTAG>],[LINKINSTAG =<LINKINSTAG>]
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<WORKLINKFROM>,<WORKLINKTO>,<BACKUPLINKFROM>,<BACKUPLINKTO>::
[WORKLINKINTAG=<WORKLINKINTAG>],[WORKLINKINSTAG=<WORKLINKINSTAG>],
[WORKLINKSTATE=<WORKLINKSTATE>],[BACKUPLINKINTAG=<BACKUPLINKINTAG>],
[BACKUPLINKINSTAG=<BACKUPLINKINSTAG>],[BACKUPLINKSTATE=<BACKUPLINKSTATE>],
[RVRTV=<RVRTV>],[RVTM=<RVTM>],[HOLDOFFTIME=<HOLDOFFTIME>],[SWSTATE=<SWSTATE>],
[ACTIVELINK=<ACTIVELIKE>]"<cr><lf>
Response Parameters
Parameter Description
<WORKLINKFRO Indicates the source of the working link. The valid format is FAC/
M> ACC-<SHELF ID>-<SLOT ID>-<PORT ID>.
<WORKLINKTO> Indicates the sink of the working link. The valid format is FAC/ACC-
<SHELF ID>-<SLOT ID>-<PORT ID>.
<BACKUPLINKF Indicates the source of the backup link. The valid format is FAC/ACC-
ROM> <SHELF ID>-<SLOT ID>-<PORT ID>.
<BACKUPLINKT Indicates the sink of the backup link. The valid format is FAC/ACC-
O> <SHELF ID>-<SLOT ID>-<PORT ID>.
<WORKLINKINT Indicates the tag of incoming packets over the working link. It can be
AG> a VLAN ID. This parameter is optional and denotes an EPL in this
document. See A.13.3.1 ENT-ETHLINK.
<WORKLINKINS Indicates the incoming service VLAN tag of the working link.
TAG> This parameter is optional. See A.13.3.1 ENT-ETHLINK.
<WORKLINKSTA Indicates the status of the working link. The valid values are NORMAL
TE> and SF (signal fail).
<BACKUPLINKI Indicates the tag of incoming packets from the backup link. It can be
NTAG> a VLAN ID. This parameter is optional and denotes an EPL in this
document.
<BACKUPLINKI Indicates the incoming service VLAN tag of the backup link.
NSTAG> This parameter is optional. See A.13.3.1 ENT-ETHLINK.
<BACKUPLINKS Indicates the status of the backup link. The valid values are NORMAL
TATE> and SF (signal fail).
<RVRTV> Indicates the revertive mode. The valid values are Y (revertive mode)
and N (non-revertive mode).
Parameter Description
<HOLDOFFTIME Indicates the hold-off time (units in 0.1s) of VLAN SNCP protection.
>
<SWSTATE> Indicates the protection switching status. The valid values of switching
status are as follows:
l IDLE
l AUTO_SW
l WTR
l MANUAL
l FRCD
l LOCKOUT
Example
l Command
RTRV-VLANSNCP-PG:::C:::LINKFROM=FAC-1-11-3,LINKTO=ACC-1-11-1,LINKINTAG=1;
l Response Message
NE 2008-08-02 21:20:39
M C COMPLD
"ACC-2-4-15,FAC-2-4-11,ACC-2-4-16,FAC-2-4-11::WORKLINKINTAG=200,WORKLINKSTATE=SF,B
ACKUPLINKINTAG=200,BACKUPLINKSTATE=NORMAL,RVRTV=Y,RVTM=6,HOLDOFFTIME=0,SWSTATE=AUT
O_SW,ACTIVELINK=ACC-2-4-16"
;
Related Commands
A.12.4.1 ENT-VLANSNCP-PG
A.12.4.2 ED-VLANSNCP-PG
A.12.4.4 DLT-VLANSNCP-PG
A.12.4.4 DLT-VLANSNCP-PG
Deletes a VLAN SNCP group.
Function
This command deletes a VLAN SNCP protection group.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-VLANSNCP-PG:[<TID>]::<CTAG>:::LINK_FROM =<LINKFROM>,LINKTO
=<LINKTO>,[LINKINTAG =<LINKINTAG>][LINKINSTAG =<LINKINSTAG>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
Response Parameters
None
Example
l Command
DLT-VLANSNCP-PG:::10:::LINKFROM=FAC-1-3-4,LINKTO=FAC-1-3-5,LINKINTAG=1
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.4.1 ENT-VLANSNCP-PG
A.12.4.2 ED-VLANSNCP-PG
A.12.4.3 RTRV-VLANSNCP-PG
A.12.4.5 OPR-PROTNSW-VLANSNCP
Operates the protection switching of a VLAN SNCP group.
Function
This command is used to operate the protection switching of a VLAN SNCP group.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
OPR-PROTNSW-VLANSNCP:
[<TID>]::<CTAG>:::LINK_FROM=<LINKFROM>,LINKTO =<LINKTO>,[LINKINTAG
=<LINKINTAG>],[LINKINSTAG=<LINKINSTAG>],SC=<SC>,[DIRN=<DIRN>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
Response Parameters
None
Example
l Command
OPR-PROTNSW-VLANSNCP:::
100:::LINKFROM=FAC-1-3-4,LINKTO=FAC-1-3-5,LINKINTAG=1,SC=FRCD,DIRN=BTH;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.12.4.6 RLS-PROTNSW-VLANSNCP
A.12.4.6 RLS-PROTNSW-VLANSNCP
Releases the protection switching of a VLAN SNCP group.
Function
This command releases the protection switching of a VLAN SNCP group.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
RLS-PROTNSW-VLANSNCP:
[<TID>]::<CTAG>:::LINKFROM=<LINKFROM>,LINKTO=<LINKTO>,
[LINKINTAG=<LINKINTAG>],[LINKINSTAG=<LINKINSTAG>],[DIRN=<DIRN>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
Response Parameters
None
Example
l Command
RLS-PROTNSW-VLANSNCP:::
10:::LINKFROM=FAC-1-3-4,LINKTO=FAC-1-3-5,LINKINTAG=1,DIRN=BTH;
l Response Message
NE 2003-02-28 12:23:20
M 10 COMPLD
;
Related Commands
A.12.4.5 OPR-PROTNSW-VLANSNCP
A.13.1.1 ED-<FETH/GETH/XGETH/100GETH/40GETH>
Edits the attributes of the Ethernet port.
Function
This command modifies the attributes of an FE, GE, 10GE, 100GE or 40GE port.
Usage Note
When a TQX card is used, the client-side optical interfaces (LP1-LP4) must comply with the
following configuration rules when 10GE LAN services are accessed and the GFP encapsulation
format is adopted:
l If the service type for the LP1 optical interface is configured as 10GE LAN, the LP2 optical
interface is invalid (the service type must be set to None).
NOTE
When the configured service (for example, 10GE LAN, OC-192, STM64, and OTU2E) for the LP1 optical
interface is not encapsulated based on the GFP format, the LP2 optical interface is not affected.
l The data encapsulation format for the LP2 optical interface cannot be GFP.
l Optical interfaces LP3 and LP4 are independent from optical interfaces LP1 and LP2. The
relationship between optical interfaces LP3 and LP4 is the same as the relationship between
optical interfaces LP1 and LP2.
When 10GE LAN services are accessed and the GFP encapsulation format is adopted on a TDX
card, the relationship between optical interfaces LP1 and LP2 is the same as the relationship
between optical interfaces LP1 and LP2 of the TQX card.
Category
Configuration
Security
Provisioning
Command Syntax
ED-<FETH/GETH/XGETH/100GETH/40GETH>:[<TID>]:<AID>:<CTAG>:::
[WORKMODE=<WORKMODE>],[FLOWCTRL=<FLOWCTRL>],
[FLOWCTRLAUTO=<FLOWCTRLAUTO>],[MTU=<MTU>],
[PTPMODE=<PTPMODE>],[PORTENABLE=<PORTENABLE>],
[PORTCHECK=<PORTCHECK>],[TAGTYPE=<TAGTYPE>],[PVID=<PVID>],
[PVPRI=<PVPRI>],[BCSENABLE=<BCSENABLE>],[BCSTH=<BCSTH>],
[PPTENABLE=<PPTENABLE>],[PORTTYPE=<PORTTYPE>],
[LABELTYPE=<LABELTYPE>],[PSVID=<PSVID>],[PSVPRI=<PSVPRI>],
[STAGTYPE=<STAGTYPE>],[SVENABLE=<SVENABLE>],
[ROUTEMAC=<ROUTEMAC>],[MDIMODE=<MDIMODE>], [B1SFBER=<B1SFBER>],
[B1SDBER=<B1SDBER>],[TRCJ0MODE=<TRCJ0MODE>],
[TRCJ0FMT=<TRCJ0FMT>],[TRCJ0=<TRCJ0>],[EXPTRCJ0=<EXPTRCJ0>],
[MAPMODE=<MAPMODE>],[DELAYTIME=<DELAYTIME>],
[SVTIMER=<SVTIMER>]:[<PST>],[<SST>];
Command Parameters
Parameter Description Default Value
<TAGTYPE> Indicates the tag attribute of the port. The valid TAGAWARE
values are as follows:
l TAGAWARE
l HYBRID
l ACCESS
This parameter is optional.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf> ;
Response Parameters
None
Example
l Command
ED-
FETH::FAC-1-1-5-2:100:::WORKMODE=AUTO,FLOWCTRLAUTO=DISABLE,MTU=1522,PTPMODE=AUTO,P
ORTENABLE=Y,PORTCHECK=Y,TAGTYPE=ACCESS,PVID=22,PVPRI=2,BCSENABLE=Y,BCSTH=3,PPTENAB
LE=N,PORTTYPE=UNI,PSVID=1000,PSVPRI=7,STAGTYPE=TAGAWARE,SVENABLE=Y:OOS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD ;
Related Commands
A.13.1.3 RTRV-<FETH/GETH/XGETH/100GETH/40GETH>
A.13.1.2 RMV-<FETH/GETH/XGETH>
Removes the Ethernet port from service an places it into the maintenance (MT) state.
Function
This command is used for a specified Ethernet port to enter the MT state.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
RMV-<FETH/GETH/XGETH>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
RMV-FETH::FAC-1-5-2:100;
l Response Message
NE 2005-07-06 10:23:20
M 100 COMPLD
;
Related Commands
A.13.1.4 RST-<FETH/GETH/XGETH>
A.13.1.3 RTRV-<FETH/GETH/XGETH/100GETH/40GETH>
Retrieves the attributes of an Ethernet port.
Function
This command retrieves the attributes of an Ethernet port.
Usage Note
None.
Category
Configuration.
Security
Retrieve
Command Syntax
RTRV-<FETH/GETH/XGETH/100GETH/40GETH>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::WORKMODE=<WORKMODE>,ACTWORKMODE=<ACTWORKMODE>,FLOWCTRL=<FLOWCTRL>,FLOWC
TRLAUTO=<FLOWCTRLAUTO>,ACTFLOWCTRL=<ACTFLOWCTRL>,MTU=<MTU>,[PTPMODE=<PTPMODE>],
[ACTPTPMODE=<ACTPTPMODE>], [PORTENABLE=<PORTENABLE>],[PORTCHECK=<PORTCHECK>],
[TAGTYPE=<TAGTYPE>],[PVID=<PVID>],[PVPRI=<PVPRI>],[BCSENABLE=<BCSENABLE>],
[BCSTH=<BCSTH>],[PPTENABLE=<PPTENABLE>],[PORTTYPE=<PORTTYPE>],
[LABELTYPE=<LABELTYPE>],[PSVID=<PSVID>],[PSVPRI=<PSVPRI>],[STAGTYPE=<STAGTYPE>],
[SVENABLE=<SVENABLE>],[SVTPID=<SVTPID>],[MACADDR=<MACADDR>],[ROUTEMAC=<ROUTEMAC>],
[MDIMODE=<MDIMODE>],[B1SFBER=<B1SFBER>],[B1SDBER=<B1SDBER>],
[TRCJ0MODE=<TRCJ0MODE>],[TRCJ0FMT=<TRCJ0FMT>],[TRCJ0=<TRCJ0>],
[EXPTRCJ0=<EXPTRCJ0>],[INCTRCJ0=<INCTRCJ0>],[MAPMODE=<MAPMODE>],
[DELAYTIME=<DELAYTIME>],[SWITCHSTATE=<SWITCHSTATE>],
[SVTIMER=<SVTIMER>]:<PST>,<SST>"<cr><lf>
Response Parameters
Parameter Description
<WORKMODE> Indicates the working mode of the port. The valid values are as follows:
l AUTO: Auto Negotiation
l HALF10M: 10Mbps half-duplex mode
l FULL10M: 10Mbps full-duplex mode
l HALF100M: 100Mbps half-duplex mode
l FULL100M: 100Mbps full-duplex mode
l FULL1000M: 1000Mbps full-duplex mode
l 10GFULLLAN: 10GE LAN full-duplex mode
l 10GFULLWAN: 10GE WAN full-duplex mode
<FLOWCTRLAUT Indicates the auto-negotiation flow control attribute of the port and
O> whether the automatic flow control is enabled. The valid values are in
section "FLOWCTRLAUTO" of TL1 Parameters.
<PORTENABLE> Indicates whether the port is enabled. The valid values are Y (enable)
and N (disable).
<PVPRI> Indicates the priority of the default VLAN for the port.
<TAGTYPE> Indicates the tag attribute of the port. The valid values are as follows:
l TAGAWARE
l HYBRID
l ACCESS
Parameter Description
<BCSTH> Indicates the threshold for broadcast ; that is, the percentage of the total
planned bandwidth that broadcast packets occupy.
<PPTENABLE> Indicates whether flow control frames are transmitted to the next hop
transparently.
<PORTTYPE> Indicates the type of the port identified by AID. The valid values are
as follows:
l User to network interface (UNI)
l NUNI
l Network to network interface (NNI)
l Customer VLAN tag aware (CAWARE)
l Service VLAN tag aware (SAWARE)
<PSVPRI> Indicates the priority of the default service VLAN for the port.
NOTE
This parameter is not valid for NGWDM equipment.
<ROUTEMAC> Indicates the MAC address of the remote router in the DBPS protection
group.
Parameter Description
<B1SFBER> Indicates the SF BER threshold for the overhead byte (B1) on a facility.
The valid value ranges from 1E-5 to 1E-3.
This parameter is valid only when the <WORKMODE> is
10GFULLWAN.
<B1SDBER> Indicates the SD BER threshold for the overhead byte (B1) on a
facility.
The valid value ranges from 1E-9 to 1E-5.
This parameter is valid only when the <WORKMODE> is
10GFULLWAN.
<DELAYTIME> Indicates the delay time, that is, hold-off time. The valid value is an
integer ranging from 0 to 255 in units of 100 ms.
Delay time is required when multiple protection schemes are
configured. Switching is not initiated until the delay time is expended
when a malfunction is discovered at a port.
Parameter Description
<SWITCHSTATE Indicates the protection switching status. It is only valid when the port
> is in the protection group.
For the valid values of this parameter, refer to A.32.3.20
SWITCHSTATE.
<SVTIMER> Indicates the signal validation timer; units are expressed in minutes. It
is valid only when Auto In-Service is supported. SVTIMER is a string
in an HH-MM format.
l HH: hour, which is an integer ranging from 0 to 48.
l MM: minute, which is an integer ranging from 0 to 59.
l The maximum timer setting is 48 hours.
Example
l Command
RTRV-FETH::FAC-5-2:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FAC-5-2::WORKMODE=AUTO,ACTWORKMODE=FULL100M,FLOWCTRL=DISABLE,FLOWCTRLAUTO=DISABLE
,ACTFLOWCTRL=DISABLE,MTU=1522,PTPMODE=AUTO,PORTENABLE=Y,PORTCHECK=Y,TAGTYPE=ACCESS
,PVID=22,PVPRI=2,BCSENABLE=Y,BCSTH=3,PPTENABLE=N,PORTTYPE=UNI,PSVID=1000,PSVPRI=7,
STAGTYPE=TAGAWARE,SVENABLE=Y,SVTPID=34832,MACADDR=00-e0-fc-59-b2-70:IS"
;
Related Commands
A.13.1.1 ED-<FETH/GETH/XGETH/100GETH/40GETH>
A.13.1.4 RST-<FETH/GETH/XGETH>
Restores the Ethernet port into service.
Function
This command is used for a specified Ethernet port of the NE to exit the maintenance state.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
RST-<FETH/GETH/XGETH>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
RST-FETH::FAC-1-5-2:100;
l Response Message
NE 2005-07-06 10:23:20
M 100 COMPLD
;
Related Commands
A.13.1.2 RMV-<FETH/GETH/XGETH>
A.13.1.5 OPR-LPBK-<FETH/GETH/XGETH>
Operates a loopback on the Ethernet port.
Function
This command is used for an NE to operate a loopback on a specified Ethernet port.
Usage Note
The loopback can be performed only when the Ethernet port is in the MT state.
Category
Configuration
Security
Maintenance
Command Syntax
OPR-LPBK-<FETH/GETH/XGETH>:
[<TID>]:<AID>:<CTAG>::<LPBKMODEETH>:LPBKTYPE=<LPBKTYPE>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
OPR-LPBK-GETH::FAC-1-2-5:100::MAC:LPBKTYPE=TERMINAL;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.1.6 RLS-LPBK-<FETH/GETH/XGETH>
A.13.1.6 RLS-LPBK-<FETH/GETH/XGETH>
Releases the loopback of an Ethernet port.
Function
This command is used for an NE to release the loopback of a specified Ethernet port.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
RLS-LPBK-<FETH/GETH/XGETH>:[<TID>]:<AID>:<CTAG>::<LPBKMODEETH>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
RLS-LPBK-FETH::FAC-1-5-2:100::MAC;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.1.5 OPR-LPBK-<FETH/GETH/XGETH>
A.13.1.7 RTRV-LPBK-<FETH/GETH/XGETH>
Retrieves the loopback information about a specified Ethernet port
Function
This command instructs the NE to retrieve the loopback information about a specified Ethernet
port.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-LPBK-<FETH/GETH/XGETH>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::LOCN=<LOCN>,LPBKTYPE=<LPBKTYPE>"<cr><lf> ;
Response Parameters
Parameter Description
<LOCN> Indicates the loopback mode. The valid values are MAC (MAC
loopback) and PHY (physical loopback).
<LPBKTYPE> Indicates the loopback type. The valid values are FACILITY and
TERMINAL.
Example
l Command
RTRV-LPBK-GETH::FAC-1-3-4:100;
l Response Message
NE 2009-01-01 11:37:18
M C COMPLD
"FAC-1-3-4::LOCN=MAC,LPBKTYPE=TERMINAL"
Related Commands
A.13.1.5 OPR-LPBK-<FETH/GETH/XGETH>
A.13.1.8 ED-ETH-VCG
Edits the attributes of an Ethernet VCG port.
Function
This command modifies the attributes of an Ethernet VCG port.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-ETH-VCG:[<TID>]:<AID>:<CTAG>:::[ENCPROTOCOL=<ENCPROTOCOL>],
[SCRAMBLER=<SCRAMBLER>],[EXTHDR=<EXTHDR>],[REVCRC=<REVCRC>],
[FCSTYPE=<FCSTYPE>],[ENDIAN=<ENDIAN>]:[<PST>],[<SST>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf> ;
Response Parameters
None
Example
l Command
ED-ETH-VCG::ACC-1-5-3:100:::ENCPROTOCOL=GFP-
F,SCRAMBLER=X43,FCSTYPE=FCS32,ENDIAN=LITTLE,EXTHDR=Y:OOS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD ;
Related Commands
RTRV-ETH-VCGA.13.1.3 RTRV-<FETH/GETH/XGETH/100GETH/40GETH>
A.13.1.9 RTRV-ETH-VCG
Queries the attributes of an Ethernet VCG port.
Function
This command queries the attributes of an Ethernet VCG port.
Usage Note
None.
Category
Configuration.
Security
Retrieve
Command Syntax
RTRV-ETH-VCG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::ENCPROTOCOL=<ENCPROTOCOL>,SCRAMBLER=<SCRAMBLER>,EXTHDR=<EXTHDR>,REVCRC=
<REVCRC>,FCSTYPE=<FCSTYPE>,ENDIAN=<ENDIAN>:<PST>,<SST>"<cr><lf>
Response Parameters
Parameter Description
<SCRAMBLER> Indicates the scrambling mode that is used by the scrambler of the
encapsulation protocol.
l The valid values are DISABLE, X43, and X48.
Example
l Command
RTRV-ETH-VCG::ACC-5-2:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"ACC-5-2::ENCPROTOCOL=GFP-
F,SCRAMBLER=X43,FCSTYPE=FCS32,ENDIAN=LITTLE,EXTHDR=Y:IS"
;
Related Commands
ED-ETH-VCGA.13.1.1 ED-<FETH/GETH/XGETH/100GETH/40GETH>
A.13.1.10 ED-PORT-TRAFFIC
Edits the traffic attribute of a port.
Function
This command modifies the traffic attribute of a port.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-PORT-TRAFFIC:[<TID>]:<AID>:<CTAG>:::[NTMENABLE=<NTMENABLE>],
[NTMTIME=<NTMTIME>],[TRFCTH=<TRFCTH>],[TRFCTIME=<TRFCTIME>],
[FLUXMON=<FLUXMON>]:[<PST>],[<SST>];
Command Parameters
Parameter Description Default Value
<TRFCTH> Indicates the maximum traffic that is allowed 100 (FE port), 1000
by a port. An alarm is reported when the traffic (GE port), 10000
receives at a port exceeds this parameter. (10GE port)
The value ranges from 1 Mbit/s to 100 Mbit/s
for an FE port, ranges from 1 Mbit/s to 1000
Mbit/s for a GE port, and ranges from 1 Mbit/
s to 10000 Mbit/s for a 10GE port.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf> ;
Response Parameters
None
Example
l Command
ED-PORT-TRAFFIC::FAC-1-5-2:100:::NTMENABLE=Y,NTMTIME=15,
TRFCTH=100,TRFCTIME=30,FLUXMON=Y:OOS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD ;
Related Commands
RTRV-PORT-TRAFFICA.13.1.3 RTRV-<FETH/GETH/XGETH/100GETH/40GETH>
RTRV-PORT-TRFFLUXA.13.1.3 RTRV-<FETH/GETH/XGETH/100GETH/40GETH>
A.13.1.11 RTRV-PORT-TRAFFIC
Queries the traffic attribute of a port.
Function
This command queries the traffic attribute of a port.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-ETH-VCG:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::NTMENABLE=<NTMENABLE>,NTMTIME=<NTMTIME>,TRFCTH=<TRFCTH>,TRFCTIME=<TRFCT
IME>,FLUXMON=<FLUXMON>:<PST>,<SST>"<cr><lf>
Response Parameters
Parameter Description
Parameter Description
<NTMTIME> Indicates the time that allows a port to receive no traffic. An alarm is
reported when the time that a port does not receive any traffic exceeds
this parameter.
The value ranges from 1 minute to 30 minutes.
<TRFCTIME> Indicates the time that allows a port to receive traffic exceeding the
value of TRCTH. An alarm is reported when the time that a port
receives traffic higher than the value of TRCTH exceeds this
parameter.
The value ranges from 0 minute to 30 minutes.
Example
l Command
RTRV-PORT-TRAFFIC::FAC-5-2:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FAC-5-2::NTMENABLE=ENABLE,NTMTIME=15,TRFCTH=100,TRFCTIME=10,FLUXMON=Y:IS"
;
Related Commands
ED-PORT-TRAFFICA.13.1.1 ED-<FETH/GETH/XGETH/100GETH/40GETH>
RTRV-PORT-TRFFLUXA.13.1.1 ED-<FETH/GETH/XGETH/100GETH/40GETH>
A.13.1.12 RTRV-PORT-TRFFLUX
Queries historical traffic records of a port.
Function
This command queries historical traffic records of a port.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-PORT-TRFFLUX:
[<TID>]:<AID>:<CTAG>:::<BGNDATE>:<BGNTIME>:<ENDDATE>:<ENDTIME>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::BGNDATE=<BGNDATE>,BGNTIME=<BGNTIME>,ENDDATE=<ENDDATE>,ENDTIME=<ENDTIME>
:<PST>,<SST>"<cr><lf>
Response Parameters
Parameter Description
<RECFLAG> Indicates the flag that represents whether flow records are generated.
The valid values are Y and N.
<RXRATE> Indicates the flow receiving rate at the time specified by RECDATE
and RECTIME. The unit is Kbit/s. The value of this parameter is 0
when RECFLAG is N.
<TXRATE> Indicates the flow transmitting rate at the time specified by RECDATE
and RECTIME. The unit is Kbit/s. The value of this parameter is 0
when RECFLAG is N.
Example
l Command
RTRV-PORT-TRFFLUX::FAC-1-1-2:100:::2003-02-28,09-00-00,2003-02-28,12-00-00;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FAC-1-1-2::RECDATE=2003-02-28,RECTIME=10-00-00,RECFLAG=Y,RXRATE=10,TXRATE=10:IS"
"FAC-1-1-2::RECDATE=2003-02-28,RECTIME=10-15-00,RECFLAG=Y,RXRATE=10,TXRATE=10:IS"
"FAC-1-1-2::RECDATE=2003-02-28,RECTIME=10-30-00,RECFLAG=Y,RXRATE=10,TXRATE=10:IS"
;
Related Commands
ED-PORT-TRAFFICA.13.1.1 ED-<FETH/GETH/XGETH/100GETH/40GETH>
RTRV-PORT-TRAFFICA.13.1.1 ED-<FETH/GETH/XGETH/100GETH/40GETH>
A.13.2.1 ENT-FLOW
Creates a flow.
Function
This command creates a flow entity of the unit. Currently, the flow can be classified as follows:
l By the incoming port (FAC or ACC).
l By the incoming port and incoming tag.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-FLOW:[<TID>]:<AID>:<CTAG>:::PORT=<PORT>,[INTAG=<INTAG>],
[INSTAG=<INSTAG>],[TAGPRI=<TAGPRI>],[LABEL=<LABEL>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-FLOW::FLOW-1-1-1:100:::PORT=FAC-2-1-1;
ENT-FLOW::FLOW-1-1-2:100:::PORT=ACC-2-1-1,INTAG=3;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.2.3 DLT-FLOW
A.13.2.2 ED-FLOW
A.13.2.4 RTRV-FLOW
A.13.2.2 ED-FLOW
Edits a flow.
Function
This command modifies a flow entity of the unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-FLOW:[<TID>]:<AID>:<CTAG>:::[CARID=<CARID>],[COSID=<COSID>],
[PKTSTATEN=<PKTSTATEN>],[PKTSTATCLR=<PKTSTATCLR>],
[FLUXMONEN=<FLUXMONEN>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-
FLOW::FLOW-1-1-1:100:::CARID=CAR-1-1-20,COSID=COS-1-1-10,PKTSTATEN=Y,PKTSTATCLR=Y,
FLUXMONEN=N;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.2.1 ENT-FLOW
A.13.2.3 DLT-FLOW
A.13.2.4 RTRV-FLOW
A.13.2.3 DLT-FLOW
Deletes the flow.
Function
This command deletes a flow entry of the unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-FLOW:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-FLOW::FLOW-1-1-10:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.2.1 ENT-FLOW
A.13.2.2 ED-FLOW
A.13.2.4 RTRV-FLOW
A.13.2.4 RTRV-FLOW
Retrieves a flow entry of the unit.
Function
This command retrieves a flow entry of a unit.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-FLOW:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[PORT=<PORT>],[INTAG=<INTAG>],[INSTAG=<INSTAG>],[TAGPRI=<TAGPRI>],
[CARID=<CARID>],[COSID=<COSID>],[PKTSTATEN=<PKTSTATEN>],[PKTRIGHTH4=<PKTRIGHTH4>],
[PKTRIGHTL4=<PKTRIGHTL4>],[PKTERRH4=<PKTERRH4>],[PKTERRL4=<PKTERRL4>],
[PKTTOTALH4=<PKTTOTALH4>],[PKTTOTALL4=<PKTTOTALL4>],[PKTBYTEH4=<PKTBYTEH4>],
[PKTBYTEL4=<PKTBYTEL4>],[FLUXMONEN=<FLUXMONEN>]"<cr><lf>
;
Response Parameters
Parameter Description
<INTAG> Indicates the incoming tag. The tag can be a VLAN tag.
<TAGPRI> Indicates the priority of <INTAG>. The valid value ranges from 0 to
7.
This parameter is optional and has no default value.
<CARID> Indicates the associated CAR. The valid format is CAR-<SLOT ID>-
<CAR ID>.
<COSID> Indicates the identifier of CoS. The valid format is COS-<SHELF ID>-
<SLOT ID>-<COS ID>.
<PKTRIGHTH4> Indicates the most significant four bytes in the number of correct flow
packets. This parameter is displayed only when users set
PKTSTATEN to Y.
<PKTRIGHTL4> Indicates the least significant four bytes in the number of correct flow
packets. This parameter is displayed only when users set
PKTSTATEN to Y.
<PKTERRH4> Indicates the most significant four bytes in the number of error flow
packets. This parameter is displayed only when users set
PKTSTATEN to Y.
<PKTERRL4> Indicates the least significant four bytes in the number of error flow
packets. This parameter is displayed only when users set
PKTSTATEN to Y.
<PKTTOTALH4> Indicates the most significant four bytes in the number of all flow
packets. This parameter is displayed only when users set
PKTSTATEN to Y.
<PKTTOTALL4> Indicates the least significant four bytes in the number of all flow
packets. This parameter is displayed only when users set
PKTSTATEN to Y.
Parameter Description
<PKTBYTEH4> Indicates the most significant four bytes in the total length of all flow
packets. This parameter is displayed only when users set
PKTSTATEN to Y.
<PKTBYTEL4> Indicates the least significant four bytes in the total length of all flow
packets. This parameter is displayed only when users set
PKTSTATEN to Y.
<FLUXMONEN> Indicates whether traffic monitoring is enabled for a flow. The system
starts to periodically record the traffic of a flow after users set this
parameter to Y.
The valid values are N and Y.
Example
l Command
RTRV-FLOW::FLOW-1-1-1:100;
RTRV-FLOW::FLOW-1-1-ALL:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FLOW-1-1-1::PORT=FAC-1-1-2,INTAG=3,CARID=CAR-1-1-10,COSID=COS-1-1-20,PKTSTATEN=N,
FLUXMONEN=Y";
Related Commands
A.13.2.2 ED-FLOW
A.13.2.1 ENT-FLOW
A.13.2.3 DLT-FLOW
A.13.3.1 ENT-ETHLINK
Creates an Ethernet link.
Function
This command creates an Ethernet link in the unit.
Usage Note
The relation between action and TAG parameters required by the action is listed in the following
table. "MUST" means the parameter must be entered, "MAY" means the parameter is optional,
hyphen("-") means the parameter cannot be entered.
Category
Provision
Security
Provisioning
Command Syntax
ENT-ETHLINK:[<TID>]:<LINKFROM>,<LINKTO>:<CTAG>:::[INTAG=<INTAG>],
[OUTTAG=<OUTTAG>],[INSTAG=<INSTAG>],[OUTSTAG=<OUTSTAG>],
[OUTTAGPRI=<OUTTAGPRI>],[OUTSTAGPRI=<OUTSTAGPRI>],
[CTYPE=<CTYPE>],[OAMFLAG=<OAMFLAG>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
Example for VLAN switch link:
ENT-ETHLINK::FAC-1-1-2,ACC-1-1-4:100:::INTAG=3,OUTTAG=5,CTYPE=1WAY;
NOTE
ENT-ETHLINK::FAC-1-1-1-2,ACC-1-1-1-4:100:::OUTTAG=3,OUTSTAG=10,CTYPE=1WAY;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.3.2 ED-ETHLINK
A.13.3.3 DLT-ETHLINK
A.13.3.4 RTRV-ETHLINK
A.13.3.2 ED-ETHLINK
Edits the Ethernet link.
Function
This command modifies the attributes of an Ethernet link in the unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-ETHLINK:[<TID>]:<LINKFROM>,<LINKTO>:<CTAG>:::[INTAG=<INTAG>],
[INSTAG=<INSTAG>],[OUTTAGPRI=<OUTTAGPRI>],
[OUTSTAGPRI=<OUTSTAGPRI>],[CTYPE=<CTYPE>],
[BANDWIDTH=<BANDWIDTH>],[OAMFLAG =<OAMFLAG >];
Command Parameters
Parameter Description Default Value
<OAMFLAG> Indicates the enabling state of the link OAM (for DISABLE
the VLANSNCP protection). The valid values are
ENABLE and DISABLE.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-ETHLINK::FAC-1-1-2,ACC-1-1-4:100:::CTYPE=2WAY;
l Response Message
NE 2005-07-14 09:55:00
M 100 COMPLD
;
Related Commands
A.13.3.1 ENT-ETHLINK
A.13.3.3 DLT-ETHLINK
A.13.3.4 RTRV-ETHLINK
A.13.3.3 DLT-ETHLINK
Deletes the Ethernet link.
Function
This command deletes an Ethernet link in the unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-ETHLINK:[<TID>]:<LINKFROM>,<LINKTO>:<CTAG>:::[INTAG=<INTAG>],
[INSTAG=<INSTAG>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.3.1 ENT-ETHLINK
A.13.3.2 ED-ETHLINK
A.13.3.4 RTRV-ETHLINK
A.13.3.4 RTRV-ETHLINK
Retrieves the information about an Ethernet link.
Function
This command retrieves the information about an Ethernet link in a unit.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-ETHLINK:[<TID>]:[<LINK_FROM>,<LINK_TO>]:<CTAG>:::
[INTAG=<INTAG>],[INSTAG=<INSTAG>];
Command Parameters
Parameter Description Default Value
<LINKTO> Indicates the sink end of the Ethernet link. The valid NA
values are as follows:
l PORT: FAC/ACC-<SHELF ID>-<SLOT ID>-
<PORT ID>
l VBLP: VBLP-<SHELF ID>-<SLOT ID>-<VB
ID>-<VBLP ID>
l SLOT: SLOT-<SHELF>-<SLOT>
Enter SLOT-<SHELF>-<SLOT> to retrieve the
link information about the specified card.
The values of source <SLOT> and end <SLOT>
must be same.
If the value of <SLOT> is ALL, all of the link
information for the cards on the shelf will be
retrieved.
Supports ALL, which means to retrieve the
information at the NE level.
The Ethernet link from VBLP to VBLP is not
supported.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<LINK_FROM>,<LINK_TO>:: [INTAG=<INTAG>],[OUTTAG=<OUTTAG>], [INSTAG=<INSTAG>],
[OUTSTAG=<OUTSTAG>],[OUTTAGPRI=<OUTTAGPRI>],[OUTSTAGPRI=<OUTSTAGPRI>],
[CTYPE=<CTYPE>],[BANDWIDTH=<BANDWIDTH >],[OAMFLAG=<OAMFLAG>]"<cr><lf>
;
Response Parameters
Parameter Para Description
<INTAG> Indicates the incoming tag. The tag can be a VLAN tag.
This parameter is optional and denotes an EPL in this document.
<OUTTAG> Indicates the out tag. The tag can be a VLAN tag.
This parameter is optional and denotes an EPL in this document.
<OUTTAGPRI> Indicates the default priority of the VLAN tag of outgoing client services.
This parameter is optional. See "Usage Note" in A.13.3.1 ENT-
ETHLINK.
<OUTSTAGPRI Indicates the default priority of the VLAN tag of outgoing services.
> This parameter is optional. See "Usage Note" in A.13.3.1 ENT-
ETHLINK.
<OAMFLAG> Indicates whether the OAM is enabled for the link (used for the VLAN
SNCP protection). The valid values are as follows:
DISABLE: disabled (default)
ENABLE: enabled
Example
l Command
Retrieves the link according to specified FROM and TO:
RTRV-ETHLINK::FAC-1-1-2,ACC-1-1-4:100;
RTRV-ETHLINK::FAC-1-1-2,ACC-1-1-4:100:::INTAG=1;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FAC-1-1-2,ACC-1-1-4::INTAG=2,OUTTAG=2,CTYPE=1WAY"
"FAC-1-1-1,ACC-1-1-1::INTAG=2,OUTTAG=NULL,INSTAG=10,OUTSTAG=NULL,CTYPE=1WAY"
"FAC-1-1-1,ACC-1-1-1::OUTTAG=10,OUTSTAG=20,OUTTAGPRI=0,OUTSTAGPRI=7,CTYPE=1WAY"
;
Related Commands
A.13.3.1 ENT-ETHLINK
A.13.3.2 ED-ETHLINK
A.13.3.3 DLT-ETHLINK
A.13.3.5 ENT-PW
Creates the PW.
Function
This command creates PW.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-PW:[<TID>]:<ENT_PWID>:<CTAG>:::INPORT=<INPORT>,
[INACPORT=<ENT_ACPORTID>],[FWINLABEL=<FWINLABEL>],
[FWOUTLABEL=<FWOUTLABEL>],[OUTPORT=<OUTPORT>],
[TUNNEL=<ENT_TUNNELID>],[BWINLABEL=<BWINLABEL>],
[BWOUTLABEL=<BWOUTLABEL>],[BWOUTLABEL=<BWOUTLABEL>],
[NHIP=<NHIP>],[EXPVALUE=<EXPVALUE>],[BANDWIDTH=<BANDWIDTH>];
Command Parameters
Parameter Description Default Value
<ENT_PWID PW index. NA
>
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-
PW::PW-1-1:100:::INPORT=FAC-1-1,INACPORT=ACPORT-1-1,FWOUTLABEL=1000,TUNNEL=TUNNEL-
1-10,BWINLABEL=16,EXPVALUE=0,BANDWIDTH=64;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.3.6 ED-PW
A.13.3.8 DLT-PW
A.13.3.7 RTRV-PW
A.13.3.6 ED-PW
Edits the specified pw.
Function
This command modifies the attributes of the specified pw.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-PW:[<TID>]:[<TID>]:<ED_PWID>:<CTAG>:::[EXPVALUE=<EXPVALUE>],
[BANDWIDTH=<BANDWIDTH>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-PW::PW-1-10:100:::EXPVALUE=0,BANDWIDTH=64;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.3.5 ENT-PW
A.13.3.8 DLT-PW
A.13.3.7 RTRV-PW
A.13.3.7 RTRV-PW
Retrieves the information about PW.
Function
This command retrieves the information about PW.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-PW:[<TID>]:<RTRV_PWID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<RTRV_PWID>::TYPE=<PWTYPE>,[INPORT=<INPORT>],[INACPORT=<ENT_ACPORTID>],
[FWINLABEL=<FWINLABEL>],[FWOUTLABEL]=<FWOUTLABEL>,[OUTPORT]=<OUTPORT>,[TUNNEL]
=<ENT_TUNNELID>,[BWINLABEL]=<BWINLABEL>,[BWOUTLABEL]=<BWOUTLABEL>,[NHIP]=<NHIP>,
[EXPVALUE]=<EXPVALUE>,[BANDWIDTH]=<BANDWIDTH>;"<cr><lf>
;
Response Parameters
Parameter Description
<PWTYPE> PW type
Example
l Command
RTRV-PW::PW-1-10:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"PW-1-1:100:::INPORT=FAC-1-1,INACPORT=ACPORT-1-1,FWOUTLABEL=1000,TUNNEL=TUNNEL-1-1
0,BWINLABEL=16,EXPVALUE=0,BANDWIDTH=64"
;
Related Commands
A.13.3.5 ENT-PW
A.13.3.6 ED-PW
A.13.3.8 DLT-PW
A.13.3.8 DLT-PW
Deletes the specified pw.
Function
This command deletes a specified pw.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-PW:[<TID>]:<ENT_PWID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-PW::PW-1-10:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.3.5 ENT-PW
A.13.3.6 ED-PW
A.13.3.7 RTRV-PW
A.13.3.9 ENT-TUNNEL
Creates the TUNNEL.
Function
This command creates TUNNEL.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-TUNNEL:[<TID>]:<ENT_TUNNELID>:<CTAG>:::INPORT=<INPORT>,
[INTNLABEL=<INTNLABEL>],[OUTPORT=<OUTPORT>],
[OUTTNLABEL=<OUTTNLABEL>],[NHIP=<NHIP>],[RETTUNNEL=<RETTUNNEL>],
[EXPMODE=<EXPMODE>],[EXPVALUE=<EXPVALUE>],
[TTSILSRID=<TTSILSRID>],[TTSITUNNELID=<TTSITUNNELID>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-
TUNNEL::TUNNEL-1-1:100:::OUTPORT=VCG-1-4,OUTTNLABEL=20,NHIP=10.11.12.13,EXPMODE=VA
LUE,EXPVALUE=0,TTSILSRID=192.168.0.1,TTSITUNNELID=1;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.3.12 ED-TUNNEL
A.13.3.10 DLT-TUNNEL
A.13.3.11 RTRV-TUNNEL
A.13.3.10 DLT-TUNNEL
Deletes the specified tunnel.
Function
This command deletes a specified tunnel.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-TUNNEL:[<TID>]:<ENT_TUNNELID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-TUNNEL::TUNNEL-1-10:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.3.9 ENT-TUNNEL
A.13.3.12 ED-TUNNEL
A.13.3.11 RTRV-TUNNEL
A.13.3.11 RTRV-TUNNEL
Retrieves the information about tunnel.
Function
This command retrieves the information about tunnel.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-TUNNEL:[<TID>]:<RTRV_TUNNEL>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<RTRV_TUNNEL>::TYPE=<TUNNELTYPE>,[INPORT=<INPORT>],[INTNLABEL=<INTNLABEL>],
[OUTPORT]=<OUTPORT>,[OUTTNLABEL]=<OUTTNLABEL>,[NHIP]=<NHIP>,[RETTUNNEL]
=<RETTUNNEL>,[EXPMODE]=<EXPMODE>[EXPVALUE]=<EXPVALUE>,[TTSILSRID]=<TTSILSRID>,
[TTSITUNNELID]=<TTSITUNNELID>;"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-TUNNEL::TUNNEL-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"TUNNEL-1-1::TYPE=ENGRESS, INPORT=FAC-1-1, INTNLABEL=20,OUTPORT=
VCG-1-4,OUTTNLABEL=20,NHIP=10.11.12.12,RETTUNNEL=TUNNEL-1-2,EXPMODE=VALUE,EXPVALUE
=0,TTSILSRID=192.168.0.1,TTSITUNNELID=1"
;
Related Commands
A.13.3.9 ENT-TUNNEL
A.13.3.12 ED-TUNNEL
A.13.3.10 DLT-TUNNEL
A.13.3.12 ED-TUNNEL
Edits the information of a tunnel.
Function
This command modifies the attributes of the specified tunnel.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-TUNNEL:[<TID>]:[<TID>]:<ENT_TUNNELID>:<CTAG>:::
[RETTUNNEL=<RETTUNNEL>],[EXPMODE=<EXPMODE>],
[EXPVALUE=<EXPVALUE>],[TTSILSRID=<TTSILSRID>],
[TTSITUNNELID=<TTSITUNNELID>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-
TUNNEL::TUNNEL-1-10:100:::EXPMODE=VALUE,EXPVALUE=0,TTSILSRID=192.168.0.1,TTSITUNNE
LID=2;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.3.9 ENT-TUNNEL
A.13.3.10 DLT-TUNNEL
A.13.3.11 RTRV-TUNNEL
A.13.4.1 ENT-VB
Creates a virtual bridge (VB).
Function
This command creates a VB.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-VB:[<TID>]:<AID>:<CTAG>:::[VBNAME=<VBNAME>],
[FDBAGTM=<FDBAGTM>],[MACAGETIMEUNIT=<MACAGETIMEUNIT>],
[FILTER=<FILTER>],[LEARNMODE=<LEARNMODE>],[TYPE=<TYPE>],
[STPTXHOLDCOUNT=<STPTXHOLDCOUNT>],
[IGMPSNPDISCAR=<IGMPSNPDISCAR>];
Command Parameters
Parameter Description Default Value
<FDBAGTM Indicates the filtering database aging time, that is, the 5
> aging time of the MAC address. The valid value ranges
from 1 to 120, which is expressed in minutes.
NOTE
Currently, all VBs share the same FDBAGTM.
<MACAGET Indicates the unit used for the aging time of the MAC MIN
IMEUNIT> address. The valid values are as follows:
l MIN: minute
l HOUR: hour
l DAY: day
<TYPE> Indicates the VB type. The valid values are as follows: 802.1q
l 802.1q VB
l 802.1d VB
l 802.1ad VB
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-VB::VB-1-1-1:100:::VBNAME="VB-
HW",FDBAGTM=20,FLTREN=Y,LEARNMODE=IVL,IGMPSNPDISCAR=N;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.4.2 ED-VB
A.13.4.3 DLT-VB
A.13.4.4 RTRV-VB
A.13.4.2 ED-VB
Edits the parameters of a virtual bridge (VB).
Function
This command modifies a VB on the unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-VB:[<TID>]:<AID>:<CTAG>:::[VBNAME=<VBNAME>],
[FDBAGTM=<FDBAGTM>],[MACAGETIMEUNIT=<MACAGETIMEUNIT>],
[FLTREN=<FLTREN>],[LEARNMODE=<LERANMODE>],[TYPE=<TYPE>],
[STPTXHOLDCOUNT =<STPTXHOLDCOUNT>],
[IGMPSNPDISCAR=<IGMPSNPDISCAR>];
Command Parameters
Parameter Description Default Value
<MACAGETIMEU Indicates the unit used for the aging time of the MIN
NIT> MAC address. The valid values are as follows:
l MIN: minute
l HOUR: hour
l DAY: day
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-VB::VB-1-1-2:100:::VBNAME="VB-
HW",FDBAGTM=20,FLTREN=N,LEARNMODE=SVL,IGMPSNPDISCAR=N;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.4.1 ENT-VB
A.13.4.3 DLT-VB
A.13.4.4 RTRV-VB
A.13.4.3 DLT-VB
Deletes a virtual bridge (VB).
Function
This command deletes a virtual bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-VB:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-VB::VB-1-1-2:101;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.4.1 ENT-VB
A.13.4.2 ED-VB
A.13.4.4 RTRV-VB
A.13.4.4 RTRV-VB
Retrieves the information about a virtual bridge (VB).
Function
This command retrieves the information about a VB.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-VB:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<VBID>::VBNAME=<VBNAME>,VBLPNUM=<VBLPNUM>,FDBAGTM=<FDBAGTM>,
[MACAGETIMEUNIT=<MACAGETIMEUNIT>],FLTREN=<FLTREN>,LEARNMODE=<LEARNMODE>,
[TYPE=<TYPE>],[STPTXHOLDCOUNT=<STPTXHOLDCOUNT>],
[IGMPSNPDISCAR=<IGMPSNPDISCAR>]"<cr><lf>
;
Response Parameters
Parameter Description
<FDBAGTM> Indicates the filtering database aging time, that is, the aging time of the
MAC address. The valid value ranges from 1 to 120, which is expressed
in minutes. The initial value is 5.
NOTE
Currently, all VBs share the same FDBAGTM.
<MACAGETIM Indicates the unit used for the aging time of the MAC address. The valid
EUNIT> values are as follows:
l MIN: minute
l HOUR: hour
l DAY: day
<FLTREN> Indicates whether the ingress filter is enabled. The valid values are Y and
N.
This parameter is optional. The initial value is Y.
<LEARNMODE Indicates the VLAN learning constraints. The valid values are as follows:
> l SVL (shared virtual local area network learning): In this mode, the
VB learns the MAC address of only the message source. The VLAN
ID in the MAC address table is uniformly set.
l IVL (independent virtual local area network learning): In this mode,
the VB learns the MAC address of the message source and the carried
VLAN ID, and then stores them into the MAC address table.
This parameter is optional. The initial value is IVL.
Parameter Description
Example
l Command
RTRV-VB::VB-1-1-2:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VB-1-1-2::VBNAME="VB-HW",FDBAGTM=20,FLTREN=N,LEARNMODE=SVL,IGMPSNPDISCAR=Y"
;
Related Commands
A.13.4.1 ENT-VB
A.13.4.2 ED-VB
A.13.4.3 DLT-VB
A.13.4.5 ENT-VLANENTRY-VB
Creates a VLAN filter entry of a VB.
Function
This command creates a VLAN filter entry of a VB.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-VLANENTRY-VB:[<TID>]:<AID>:<CTAG>:::VLANID=<VLANID>,
[VBLPLIST=<VBLPLIST>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-VLANENTRY-VB::VB-1-1-1:100:::VLANID=2,VBLPLIST=VBLP-1-1-1-1&&-4;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.13.4.6 ED-VLANENTRY-VB
A.13.4.7 DLT-VLANENTRY-VB
A.13.4.8 RTRV-VLANENTRY-VB
A.13.4.6 ED-VLANENTRY-VB
Edits the VLAN filtering entry of a virtual bridge.
Function
This command edits the VLAN filtering entry of a virtual bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-VLANENTRY-VB:[<TID>]:<AID>:<CTAG>:::VLANID=<VLANID>,
[VBLPLIST=<VBLPLIST>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-VLANENTRY-
VB::VB-1-1-1:100:::VLANID=2,VBLPLIST=VBLP-1-1-1-1&VBLP-1-1-1-2&VBLP-1-1-1-6;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.4.5 ENT-VLANENTRY-VB
A.13.4.7 DLT-VLANENTRY-VB
A.13.4.8 RTRV-VLANENTRY-VB
A.13.4.7 DLT-VLANENTRY-VB
Deletes the VLAN filtering entry of a virtual bridge.
Function
This command deletes the VLAN filtering entry of a virtual bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-VLANENTRY-VB:[<TID>]:<AID>:<CTAG>:::VLANID=<VLANID>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-VLANENTRY-VB::VB-1-1-1:100:::VLANID=2;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.4.5 ENT-VLANENTRY-VB
A.13.4.6 ED-VLANENTRY-VB
A.13.4.8 RTRV-VLANENTRY-VB
A.13.4.8 RTRV-VLANENTRY-VB
Retrieves the VLAN entry of a virtual bridge.
Function
This command retrieves the VLAN entry of a virtual bridge.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-VLANENTRY-VB:[<VLANID>]:<AID>:<CTAG>:::[VLANID=<VLANID>];
Command Parameters
Parameter Description Default Value
<AID> VB-<SHELF>-<SLOT>-<VB> NA
Supports the "&" and "&&" symbols.
Supports ALL, which indicates all values will be
retrieved.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::VLANID=<VLANID>,VBLPLIST=<VBLPLIST>"<cr><lf>
;
Response Parameters
Parameter Description
<VBLPLIST> Indicates the list of VB logical ports. The valid format is VBLP-
<SHELF ID>-<SLOT ID>-<VB ID>-<VBLP ID>.
Supports the "&" and "&&" symbols.
Example
l Command
RTRV-VLANENTRY-VB::VB-1-4-1:100:::VLANID=2;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VB-1-4-1::VLANID=2,VBLPLIST=VBLP-1-4-1-1&VBLP-1-4-1-2&VBLP-1-4-1-6"
;
Related Commands
A.13.4.5 ENT-VLANENTRY-VB
A.13.4.6 ED-VLANENTRY-VB
A.13.4.7 DLT-VLANENTRY-VB
A.13.4.9 ED-VBLP
Edits a virtual bridge logical port (VBLP).
Function
This command modifies the attributes of a logic port in a virtual bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-VBLP:[<TID>]:<AID>:<CTAG>:::[MACLIMIT=<MACLIMIT>],
[ISOLATION=<ISOLATION>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-VBLP::VBLP-1-1-2-1:100:::MACLIMIT=100,ISOLATION=HUB;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
Related Commands
A.13.4.10 RTRV-VBLP
A.13.4.10 RTRV-VBLP
Retrieves the information about a virtual bridge logical port (VBLP).
Function
This command instructs the NE to retrieve the information about the logical port in a virtual
bridge.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-VBLP:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[ISOLATION=<ISOLATION>]"<cr><lf>
;
Response Parameters
Parameter Description
<ISOLATION> Indicates the isolation mode of a VBLP. The valid values are HUB and
SPOKEN.
This parameter is optional.
NOTE
l If the <ISOLATION> of a port is configured as HUB, this port can
interconnect to other HUB ports or SPOKEN ports.
l If the <ISOLATION> of a port is configured as SPOKEN, this port can only
interconnect to other HUB ports.
Example
l Command
RTRV-VBLP::VBLP-1-1-2-1:100;
RTRV-VBLP::VBLP-1-1-1-ALL:101;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VBLP-1-1-2-1::ISOLATION=HUB"
;
Related Commands
A.13.4.9 ED-VBLP
A.13.4.11 INIT-MACENTRY
Initialize the MAC-address forwarding entry of a card.
Function
This command initializes the MAC-address forwarding entry of a card.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
INIT-MACENTRY:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
INIT-MACENTRY::SLOT-1-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
None
A.13.5.1 ENT-PORT-VLANGROUP
Edit a VLAN group for a port.
Function
This command creates a VLAN group for a port.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-PORT-VLANGROUP:
[<TID>]:<AID>:<CTAG>:::TOPID=<TOPID>,CVLANNUM=<CVLANNUM>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-PORT-VLANGROUP::FAC-1-3-4:100:::TOPID=1,CVLANNUM=1
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.5.2 ED-PORT-VLANGROUP
A.13.5.3 DLT-PORT-VLANGROUP
A.13.5.4 RTRV-PORT-VLANGROUP
A.13.5.2 ED-PORT-VLANGROUP
Edits the VLAN group of a port.
Function
This command modifies the VLAN group of a port.
Usage Note
For NGWDM equipment, this command is only valid for the TBE.
Category
Configuration
Security
Provisioning
Command Syntax
ED-PORT-VLANGROUP:
[<TID>]:<AID>:<CTAG>:::TOPID=<TOPID>,CVLANNUM=<CVLANNUM>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-PORT-VLANGROUP::FAC-1-3-4:100:::TOPID=8,CVLANNUM=2
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.5.1 ENT-PORT-VLANGROUP
A.13.5.3 DLT-PORT-VLANGROUP
A.13.5.4 RTRV-PORT-VLANGROUP
A.13.5.3 DLT-PORT-VLANGROUP
Deletes the VLAN group of a port.
Function
This command deletes the port VLAN group.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-PORT-VLANGROUP:[<TID>]:<AID>:<CTAG>::TOPID=<TOPID>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-PORT-VLANGROUP::FAC-1-3-4:100:::TOPID=1
l Response Message
NE 2005-11-02 09:48:24
M 100 COMPLD
;
Related Commands
A.13.5.1 ENT-PORT-VLANGROUP
A.13.5.2 ED-PORT-VLANGROUP
A.13.5.4 RTRV-PORT-VLANGROUP
A.13.5.4 RTRV-PORT-VLANGROUP
Retrieves the VLAN group information about a port
Function
This command retrieves the VLAN group information about a port.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-PORT-VLANGROUP:[<TID>]:<AID>:<CTAG>::[TOPID=<TOPID>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[TOPID=<TOPID>],[CVLANNUM=<CVLANNUM>]"<cr><lf>
Response Parameters
Parameter Description
Parameter Description
Example
l Command
RTRV-PORT-VLANGROUP::FAC-1-5-4:100:::TOPID=1
l Response Message
NE 2008-10-16 03:43:01
M 100 COMPLD
"FAC-1-5-4::TOPID=1,CVLANNUM=7"
;
Related Commands
A.13.5.1 ENT-PORT-VLANGROUP
A.13.5.2 ED-PORT-VLANGROUP
A.13.5.3 DLT-PORT-VLANGROUP
A.13.6.1 ENT-MACENTRY-VB
Creates a static MAC filter entry of a virtual bridge (VB).
Function
This command creates a static MAC filter entry of the VB.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-MACENTRY-VB:
[<TID>]:<AID>:<CTAG>:::VLANID=<VLANID>,MACADDR=<MACADDR>,FLTRMO
DE=<FILTMODE>,[FWDVBLP=<FWDVBLP>];
Command Parameters
Parameter Description Default
Value
<VLANID> Indicates the identifier of the VLAN entry. The valid value NA
ranges from 1 to 4095. This parameter is optional and the
default VLAN ID can be used only when <LEARNMODE>
of the VB is set to SVL (see A.13.4.1 ENT-VB).
<FLTRMODE Indicates the filter mode. The valid values are SA, DA, FORWAR
> BOTH, and FORWARD. D
l SA: discards the data whose source MAC address is the
same as the specified MAC address. The entry functions
as a MAC address blacklist.
l DA: discards the data whose sink MAC address is the
same as the specified MAC address. The entry functions
as a MAC address blacklist.
l BOTH: discards the data whose source MAC address or
sink MAC address is the same as the specified MAC
address. The entry functions as a MAC address blacklist.
l FORWARD: forwards the data packets whose source
MAC address is the specified MAC address
(<MACADDR>) at the specified VBLP
(<FWDVBLP>). The entry functions as the entry of the
static MAC address.
NOTE
The SA and DA are not valid for NGWDM equipment.
<FWDVBLP> Indicates that the data packets whose source MAC address NA
is the specified MAC address (<MACADDR>) will be
forwarded at the VBLP.
The valid format is VBLP-<SHELF ID>-<SLOT ID>-<VB
ID>-<VBLPID>.
This parameter is available only when <FLTRMODE> is set
to FORWARD.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-MACENTRY-
VB::VB-1-4-1:100:::VLANID=2,MACADDR=00-32-0B-0E-10-0D,FLTRMODE=FORWARD,FWDVBLP=VBL
P-1-4-1-2;
ENT-MACENTRY-VB::VB-1-4-1:100:::VLANID=2,MACADDR=00-32-0B-0E-10-0E,FLTRMODE=BOTH;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.6.2 DLT-MACENTRY-VB
A.13.6.3 RTRV-MACENTRY-VB
A.13.6.2 DLT-MACENTRY-VB
Deletes a static MAC filtering entry of a virtual bridge.
Function
This command deletes a static MAC filtering entry.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-MACENTRY-VB:[<TID>]:<AID>:<CTAG>:::
[VLANID=<VLANID>],MACADDR=<MACADDR>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-MACENTRY-VB::VB-1-4-1:100:::VLANID=2,MACADDR=00-32-0B-0E-10-0D;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.6.1 ENT-MACENTRY-VB
A.13.6.3 RTRV-MACENTRY-VB
A.13.6.3 RTRV-MACENTRY-VB
Retrieves the static MAC filtering entry of a virtual bridge.
Function
This command retrieves a static MAC filtering entry of a virtual bridge.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MACENTRY-VB:[<TID>]:[<AID>]:<CTAG>:::[VLANID=<VLANID>]
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[VLANID=<VLANID>,]MACADDR=<MACADDR>,FLTRMODE=<FLTRMODE>,
[FWDVBLP=<VBLP>]"<cr><lf>
;
Response Parameters
Parameter Para Description
<VLANID> Indicates the identifier of the VLAN entry. The valid value ranges from
0 to 4095.
<VLANID> will not be displayed if the <LEARNMODE> of the VB
is SVL (see A.13.4.1 ENT-VB).
<MACADDR> Indicates the 48-bit MAC address. The valid format is XX-XX-XX-
XX-XX-XX.
This parameter is optional. If not specified, it outputs the MAC entries
of all MAC addresses.
This parameter is required only if <FLAG> (see A.13.6.4 RTRV-
FWDTABPHY-VB) is set to STATIC.
<FLTRMODE> Indicates the filter mode. The valid values are SA, DA, BOTH, and
FORWARD.
l SA: discards the data whose source MAC address is the same as
the specified MAC address. The entry functions as a MAC address
blacklist.
l DA: discards the data whose sink MAC address is the same as the
specified MAC address. The entry functions as a MAC address
blacklist.
l BOTH: discards the data whose source MAC address or sink MAC
address is the same as the specified MAC address. The entry
functions as a MAC address blacklist.
l FORWARD: forwards the data packets whose source MAC
address is the specified MAC address (<MACADDR>) at the
specified VBLP (<FWDVBLP>). The entry functions as the entry
of the static MAC address.
NOTE
The SA and DA are not valid for NGWDM equipment.
Example
l Command
RTRV-MACENTRY-VB::VB-1-4-1:100:::VLANID=2;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VB-1-4-1::VLANID=2,MACADDR=00-32-0B-0E-10-0D,FLTRMODE=FORWARD,FWDVBLP=VBLP-1-4-1-
2"
;
Related Commands
A.13.6.1 ENT-MACENTRY-VB
A.13.6.2 DLT-MACENTRY-VB
A.13.6.4 RTRV-FWDTABPHY-VB
Queries the physical forwarding tables of the VB in batches.
Function
The command queries the physical forwarding tables of the VB in batches.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-FWDTABPHY-VB:[<TID>]:[<AID>]:<CTAG>:::[VLANID=<VLANID>],
[MACADDR=<MACADDR>],[FLAG=<FLAG>],[MAXNUM=<MACMAXNUM>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[VLANID=<VLANID>],MACADDR=<MACADDR>,[FWDVBLP=<VBLP>],
[MACSTATE=<MACSTATE>]"<cr><lf>
;
Response Parameters
Parameter Para Description
<VLANID> Indicates the identifier of the VLAN entry. The valid value ranges from
0 to 4095.
<MACADDR> Indicates the 48-bit MAC address. The valid format is XX-XX-XX-
XX-XX-XX.
This parameter is optional. If not specified, it outputs the MAC entries
of all MAC addresses.
This parameter is required only if <FLAG> is set to STATIC.
<MACSTATE> Indicates the MAC address state. The valid values are as follows:
l STATIC: indicates the MAC address is manually specified.
l DYNAMIC: indicates the MAC address is self-learned.
l STATIC-END: indicates the MAC address is the last one of the
static MAC addresses.
l DYNAMIC-END: indicates the MAC address is the last one of the
dynamic MAC addresses.
Example
l Command
RTRV-FWDTABPHY-VB::VB-1-4-1:100:::VLANID=2,FLAG=BEGIN,MAXNUM=100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VB-1-4-1::VLANID=2,MACADDR=00-32-0B-0E-10-0D,FWDVBLP=VBLP-4-1-2,MACSTATE=DYNAMIC
"
;
Related Commands
A.13.6.1 ENT-MACENTRY-VB
A.13.6.2 DLT-MACENTRY-VB
A.13.6.5 RTRV-MACSTAT
Retrieves the number of the MAC addresses which are learned by a card.
Function
The command queries the number of the MAC addresses which are learned by a card.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MACSTAT:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::DYNAMIC_NUM=<DYNAMIC_NUM>,STATIC_NUM=<STATIC_NUM>,BLACKLIST_NUM=<BLACKL
IST_NUM>"<cr><lf>
;
Response Parameters
Parameter Para Description
<AID> Indicates the equipment unit identifier. The valid format is SLOT-
<SHELF>-<SLOT>.
Example
l Command
RTRV-MACSTAT::SLOT-1-4:100;
l Response Message
NE 2005-08-29 10:30:00
M 100 COMPLD
"SLOT-1-4::DYNAMIC_NUM=200,STATIC_NUM=100,BLACKLIST_NUM=50";
Related Commands
None
A.13.7.1 ED-IGMP-VB
Edits the Internet Group Management Protocol (IGMP) snooping attributes of a virtual bridge.
Function
This command modifies the IGMP snooping attributes of a virtual bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-IGMP-VB:[<TID>]:<AID>:<CTAG>:::[IGSPENABLE=<IGSPENABLE>],
[ROUTERAGTM=<ROUTERAGTM>],[NORSPTIMES=<NORSPTIMES>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-IGMP-VB::VB-1-4-1:100:::IGSPENABLE=Y,ROUTERAGTM=5,NORSPTIMES=2;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.7.2 RTRV-IGMP-VB
A.13.7.2 RTRV-IGMP-VB
Retrieves the IGMP snooping attributes of a virtual bridge (VB).
Function
This command retrieves the IGMP snooping attributes of a VB.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-IGMP-VB:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[IGSPENABLE=<IGSPENABLE>],[ROUTERAGTM=<ROUTERAGTM>],
[NORSPTIMES=<NORSPTIMES>]"<cr><lf>
;
Response Parameters
Parameter Description
<IGSPENABLE> Indicates whether IGMP snooping is enabled. The valid values are Y
and N.
<ROUTERAGTM Indicates the aging time of the Router port. The valid value ranges from
> 1 (min) to 120 (min).
NOTE
Currently, all VBs share the same ROUTERAGTM.
<NORSPTIMES> Indicates the maximum number of times for a member not responding
to IGMP query packets before the member is aging. The value ranges
from 1 to 4.
Example
l Command
RTRV-IGMP-VB::VB-1-4-1:100;
RTRV-IGMP-VB::VB-1-4-ALL:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VB-4-1::IGSPENABLE=Y,ROUTERAGTM=8,NORSPTIMES=3"
;
Related Commands
A.13.7.1 ED-IGMP-VB
A.13.7.3 ENT-IGMPTABLE-VB
Creates the IGMP table within a VLAN of a virtual bridge.
Function
This command creates the multicast group member of an IGMP within a VLAN of a virtual
bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-IGMPTABLE-VB:[<TID>]:<AID>:<CTAG>:::VLANID=<VLANID>,MACADDR
=<MACADDR>,[VBLPLIST=<VBLPLIST>]
Command Parameters
Parameter Para Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-IGMPTABLE-VB::VB-1-1-1:100:::VLANID=2,MACADDR=01-00-5e-45-e5-
f6,VBLPLIST=VBLP-1-1-1-1;
l Response Message
NE 2007-11-02 09:48:24
M 100 COMPLD
;
Related Commands
A.13.7.4 ED-IGMPTABLE-VB
A.13.7.5 DLT-IGMPTABLE-VB
A.13.7.6 RTRV-IGMPTABLE-VB
A.13.7.4 ED-IGMPTABLE-VB
Edits the IGMP table within a VLAN of a virtual bridge.
Function
This command modifies the multicast group of an IGMP within a VLAN of a virtual bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-IGMPTABLE-VB:[<TID>]:<AID>:<CTAG>:::VLANID =<VLANID>,MACADDR
=<MACADDR>,[<VBLPLIST>=<VBLPLIST>]
Command Parameters
Parameter Para Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-IGMPTABLE-VB::VB-1-7-1:100:::VLANID=2,MACADDR=01-00-5e-45-e5-f6;
ED-IGMPTABLE-VB::VB-1-7-1:100:::VLANID=2,MACADDR=01-00-5e-45-e5-
f6,VBLPLIST=VBLP-1-7-1-1;
ED-IGMPTABLE-VB::VB-1-7-1:100:::VLANID=2,MACADDR=01-00-5e-45-e5-
f6,VBLPLIST=VBLP-1-7-1-1&VBLP-1-7-1-2;
l Response Message
NE 2008-10-16 02:32:56
M 100 COMPLD
;
Related Commands
A.13.7.3 ENT-IGMPTABLE-VB
A.13.7.5 DLT-IGMPTABLE-VB
A.13.7.6 RTRV-IGMPTABLE-VB
A.13.7.5 DLT-IGMPTABLE-VB
Deletes an item of the IGMP table within a VLAN of a virtual bridge.
Function
This command deletes the multicast group members of an IGMP within a VLAN of a virtual
bridge.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-IGMPTABLE-VB:[<TID>]:<AID>:<CTAG>:::VLANID=<VLANID>,MACADDR
=<MACADDR>;
Command Parameters
Parameter Para Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-IGMPTABLE-VB::VB-1-1-1:100:::VLANID=2,MACADDR=01-00-5e-45-e5-f6;
l Response Message
NE 2008-09-22 21:01:29
M 100 COMPLD
;
Related Commands
A.13.7.3 ENT-IGMPTABLE-VB
A.13.7.4 ED-IGMPTABLE-VB
A.13.7.6 RTRV-IGMPTABLE-VB
A.13.7.6 RTRV-IGMPTABLE-VB
Retrieves the IGMP table within a VLAN of a virtual bridge.
Function
This command retrieves all the multicast group members of an IGMP within a VLAN of a virtual
bridge.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-IGMPTABLE-VB:[<TID>]:<AID>:<CTAG>:::[VLANID=<VLANID>];
Command Parameters
Parameter Para Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::VLANID=<VLANID>,MACADDR=<MACADDR>,VBLPLIST=<VBLPLIST>"<cr><lf>
;
Response Parameters
Parameter Description
<VBLPLIST> Indicates the list of the VB logical ports, the valid format is VBLP-
<SHELF ID>-<SLOT ID>-<VB ID>-<VBLP ID>.
Supports the "&" and "&&" symbols.
Example
l Command
RTRV-IGMPTABLE-VB::VB-1-1-1:100:::VLANID=2;
RTRV-IGMPTABLE-VB::VB-1-1-1:100;
l Response Message
NE 2008-09-22 20:57:57
M 100 COMPLD
"VB-1-1-1::VLANID=2,MACADDR=01-00-5e-45-e5-f6,VBLPLIST=VBLP-1-1-1-1"
;
Related Commands
A.13.7.3 ENT-IGMPTABLE-VB
A.13.7.4 ED-IGMPTABLE-VB
A.13.7.5 DLT-IGMPTABLE-VB
A.13.7.7 RTRV-MCGROUP-VB
Retrieves the multicast group parameters within a virtual bridge.
Function
This command retrieves the actual multicast group parameters within a virtual bridge.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MCGROUP-VB:[<TID>]:<AID>:<CTAG>:::[VLANID=<VLANID>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::VLANID=<VLANID>,[ROUTERPORTLIST=<ROUTERPORT>],[MACADDR=<MACADDR>],
[VBLPLIST=<VBLPLIST>]"<cr><lf>;
Response Parameters
Parameter Description
<MACADDR> Indicates the 48 bit MAC address. The valid format is XX-XX-XX-
XX-XX-XX.
<VBLPLIST> Indicates the list of the VB logical ports, the format is VBLP-<SLOT
ID>-<VB ID>-<VBLP ID>
Supports the "&" and "&&" symbols.
Example
l Command
RTRV-MCGROUP-VB::VB-1-4-1:100:::VLANID=100;
l Response Message
NE 2008-09-10 00:54:11
M 100 COMPLD
"
VB-1-4-1::VLANID=100,ROUTERPORTLIST=VBLP-1-4-1-4,MACADDR=01-00-5e-00-29-65,VBLPLIS
T=VBLP-1-4-1-4"
;
Related Commands
None
A.13.7.8 ED-IGMP-QKLV
Edits the quick leaving attribute of the Internet Group Management Protocol (IGMP).
Function
This command modifies the quick leaving attribute of the IGMP.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-IGMP-QKLV:
[<TID>]:<AID>:<CTAG>:::VLANID=<VLANID>,VBLPLIST=<VBLPLIST>,QKLVEN=<
QKLVEN>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-IGMP-
QKLV::VB-1-1-1:100:::VLANID=2,VBLPLIST=VBLP-1-1-1-1&VBLP-1-1-1-2&VBLP-1-1-1-6,QKLV
EN=Y;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
RTRV-IGMP-QKLVA.13.4.5 ENT-VLANENTRY-VB
A.13.4.7 DLT-VLANENTRY-VB
A.13.4.8 RTRV-VLANENTRY-VB
A.13.7.9 RTRV-IGMP-QKLV
Queries the quick leaving attribute of the IGMP.
Function
This command queries the quick leaving attribute of the IGMP.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-IGMP-QKLV:
[<TID>]:<AID>:<CTAG>:::VLANID=<VLANID>,VBLPLIST=<VBLPLIST>;
Command Parameters
Parameter Description Default Value
<AID> VB-<SHELF>-<SLOT>-<VB> NA
Supports the "&" and "&&" symbols.
Supports ALL, which indicates all values will be
retrieved.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::VLANID=<VLANID>,VBLPLIST=<VBLPLIST>"<cr><lf>
;
Response Parameters
Parameter Description
<QKLVEN> Indicates whether quick leaving is enabled for the IGMP. The valid
values are Y and N.
Example
l Command
RTRV-IGMP-QKLV::VB-1-4-1:100:::VLANID=2,VBLP-1-4-1-1&&VBLP-1-4-1-3;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"VB-1-4-1::VLANID=2,VBLP=VBLP-1-4-1-1,QKLVEN=Y"
"VB-1-4-1::VLANID=2,VBLP=VBLP-1-4-1-2,QKLVEN=N"
"VB-1-4-1::VLANID=2,VBLP=VBLP-1-4-1-3,QKLVEN=N"
;
Related Commands
ED-IGMP-QKLVA.13.4.5 ENT-VLANENTRY-VB
A.13.4.6 ED-VLANENTRY-VB
A.13.4.7 DLT-VLANENTRY-VB
A.13.7.10 REPT^EVT^IGMPMEMFULL
Reports an event indicating that the number of dynamic members in the IGMP reaches the
maximum.
Function
This commands reports an event indicating that the number of dynamic members in the IGMP
reaches the maximum. When the event is reported, no new members can be added to the IGMP.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
A^^<ATAG>^REPT^EVT^VBLP<cr><lf>
^^^"<AID>:<CONDYPE>,<CONDEFF>" <cr><lf> ;
Response Parameters
Parameter Description
Example
l Command
None
l Response Message
NE 2003-02-28 12:23:20
A 100 REPT EVT IGMPMEMFULL
"SLOT-1-1:256,TC"
;
Related Commands
None
A.13.8.1 ENT-CAR
Creates the committed access rate (CAR).
Function
This command creates an entry for the CAR within a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-CAR:[<TID>]:<AID>:<CTAG>:::[CARENABLE=<CARENABLE>],[CIR=<CIR>],
[PIR=<PIR>],[DCBS=<DCBS>],[DMBS=<DMBS>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-CAR::CAR-1-1-10:100:::CARENABLE=Y,CIR=10240,PIR=20480;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.8.2 ED-CAR
A.13.8.3 DLT-CAR
A.13.8.4 RTRV-CAR
A.13.8.2 ED-CAR
Edits the committed access rate (CAR).
Function
This command modifies the attributes of the specified CAR within a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-CAR:[<TID>]:[<TID>]:<AID>:<CTAG>:::[CARENABLE=<CARENABLE>],
[CIR=<CIR>],[PIR=<PIR>],[DCBS=<DCBS>],[DMBS=<DMBS>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-CAR::CAR-1-1-10:100:::CARENABLE=Y,CIR=10240,PIR=20480;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.8.1 ENT-CAR
A.13.8.3 DLT-CAR
A.13.8.4 RTRV-CAR
A.13.8.3 DLT-CAR
Deletes the committed access rate (CAR).
Function
This command deletes an entry of the CAR within a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-CAR:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-CAR::CAR-1-1-10:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.8.1 ENT-CAR
A.13.8.2 ED-CAR
A.13.8.4 RTRV-CAR
A.13.8.4 RTRV-CAR
Retrieves the information about committed access rate (CAR).
Function
This command retrieves the information about CAR.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-CAR:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<CARID>::CARENABLE=<CARENABLE>,CIR=<CIR>,PIR=<PIR>,DCBS=<DCBS>,DMBS=<DMBS>"<cr
><lf>
;
Response Parameters
Parameter Description
<CIR> Indicates the committed information rate of the CAR. Unit is 1 kbit/s.
<DCBS> Indicates the delta committed burst size. The unit is 1 KB.
<DMBS> Indicates the delta maximum burst size. The unit is 1 KB.
Example
l Command
RTRV-CAR::CAR-1-1-10:100;
RTRV-CAR::CAR-1-1-ALL:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"CAR-1-1-10::CARENABLE=Y,CIR=10240,PIR=20480,DCBS=0,DMBS=0"
;
Related Commands
A.13.8.1 ENT-CAR
A.13.8.2 ED-CAR
A.13.8.3 DLT-CAR
A.13.8.5 ENT-COS
Creates the class of service (CoS).
Function
This command creates an entry for the CoS within an unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-COS:[<TID>]:<AID>:<CTAG>:::[COSTYPE=<COSTYPE>];
Command Parameters
Parameter Description Default Value
<COSTYPE> Indicates the type of CoS. The valid values are as SIMPLE
follows:
l SIMPLE
l TAGPRI
l IPTOS
l MPLSEXP
l DSCP
This parameter is optional and the default value is
SIMPLE.
NOTE
l IAGPRI is not valid for L4G.
l IPTOS, MPLSEXP and DSCP are not valid for
NGWDM equipment.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-COS::COS-1-1-1:100:::COSTYPE=SIMPLE;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.8.6 ED-COS
A.13.8.7 DLT-COS
A.13.8.8 RTRV-COS
A.13.8.6 ED-COS
Edits the class of service (CoS).
Function
This command modifies an entry of the CoS within a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-COS:[<TID>]:<AID>:<CTAG>:::[SIMPLEPRI=<SIMPLEPRI>],
[TAGPRI0=<TAGPRI0>],[TAGPRI1=<TAGPRI1>],[TAGPRI2=<TAGPRI2>],
[TAGPRI3=<TAGPRI3>],[TAGPRI4=<TAGPRI4>],[TAGPRI5=<TAGPRI5>],
[TAGPRI6=<TAGPRI6>],[TAGPRI7=<TAGPRI7>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-COS::COS-1-1-1:100:::SIMPLEPRI=1;
ED-
COS::COS-1-1-1:100:::TAGPRI0=0,TAGPRI1=0,TAGPRI2=0,TAGPRI3=0,TAGPRI4=1,TAGPRI5=1,T
AGPRI6=1,TAGPRI7=1;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.8.5 ENT-COS
A.13.8.7 DLT-COS
A.13.8.8 RTRV-COS
A.13.8.7 DLT-COS
Deletes the class of service (CoS).
Function
This command deletes an entry of the CoS within a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-COS:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-COS::COS-1-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.8.5 ENT-COS
A.13.8.6 ED-COS
A.13.8.8 RTRV-COS
A.13.8.8 RTRV-COS
Retrieves the class of service (CoS).
Function
This command retrieves the information about the CoS within a unit.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-COS:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::COSTYPE=<COSTYPE>,[SIMPLEPRI=<SIMPLEPRI>],[TAGPRI0=<TAGPRI0>],
[TAGPRI1=<TAGPRI1>],[TAGPRI2=<TAGPRI2>],[TAGPRI3=<TAGPRI3>],[TAGPRI4=<TAGPRI4>],
[TAGPRI5=<TAGPRI5>],[TAGPRI6=<TAGPRI6>],[TAGPRI7=<TAGPRI7>]"<cr><lf>
;
Response Parameters
Parameter Description
<AID> Indicates the identifier of the CoS. The valid format is COS-<SHELF
ID>-<SLOT ID>-<COS ID>.
<COSTYPE> Indicates the type of the CoS. The valid values are as follows:
l SIMPLE
l TAGPRI
This parameter is optional. The default value is SIMPLE.
<SIMPLEPRI> Indicates the simple priority. The valid value ranges from 0 to 7. This
parameter is optional. <SIMPLEPRI> does not have a default value
and is available only when <COSTYPE> is set to SIMPLE (See A.
13.8.5 ENT-COS).
<TAGPRIn> Indicates the priority corresponding to tag priority n. The valid value
ranges from 0 to 7. This parameter is optional. This parameter is valid
only when <COSTYPE> is set to TAGPRI (See A.13.8.5 ENT-
COS).
Example
l Command
RTRV-COS::COS-1-1-1:100;
RTRV-COS::COS-1-2-ALL:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"COS-1-1-11::COSTYPE=SIMPLE,SIMPLEPRI=1"
;
NE 2003-02-28 12:23:20
M 100 COMPLD
"COS-1-2-11::COSTYPE=TAGPRI,TAGPRI0=0,TAGPRI1=0,TAGPRI2=0,TAGPRI3=0,TAGPRI4=1,TAGP
RI5=1,TAGPRI6=1,TAGPRI7=1"
;
Related Commands
A.13.8.5 ENT-COS
A.13.8.6 ED-COS
A.13.8.7 DLT-COS
A.13.8.9 ED-QUEUE
Edits the queue.
Function
This command edits the parameters of the queue.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-QUEUE:[<TID>]:<AID>:<CTAG>:::QUEUEID=<QUEUEID>,
[SHAPINGENABLE=<SHAPINGENABLE>],[CIR=<CIR>],[PIR=<PIR>],
[DCBS=<DCBS>],[DMBS=<DMBS>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-QUEUE::fac-1-10-1:100:::QUEUEID=1,SHAPINGENABLE=Y,CIR=10240,PIR=20480;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.8.10 RTRV-QUEUE
A.13.8.10 RTRV-QUEUE
Retrieves the parameters of a queue.
Function
This command retrieves the parameters of a queue.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-QUEUE:[<TID>]:<AID>:<CTAG>:::[<QUEUEID>=<QUEUEID>];
Command Parameters
Parameter Description Default Value
<QUEUEID Indicates the ID of the port queue. The valid value ranges NA
> from 1 to 8 or it can be ALL.
"ALL" means to retrieve the information about all
queues.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::<QUEUEID>=<QUEUEID>,<SHAPINGENABLE>=<SHAPINGENABLE>,CIR=<CIR>,PIR=<PIR>
,DCBS=<DCBS>,DMBS=<DMBS>"<cr><lf>
;
Response Parameters
Parameter Description
<QUEUEID> Indicates the ID of the port queue. The valid value ranges from 1 to 8.
<SHAPINGENAB Indicates whether shaping is enabled. The valid values are Y and N.
LE>
<CIR> Indicates the committed information rate of shaping. The unit is 1 kbit/
s and generally the step length is 64 kbit.
<PIR> Indicates the peak information rate. The unit is 1 kbit/s and generally
its step length is 64.
<DCBS> Indicates the delta committed burst size. The unit is 1 KB.
<DMBS> Indicates the delta maximum burst size. The unit is 1 KB.
Example
l Command
RTRV-QUEUE::FAC-1-1-10:100;
l Response Message
M1050 2003-02-28 12:23:20
M 100 COMPLD
"FAC-1-1-10::QUEUEID=1,SHAPINGENABLE=Y,CIR=10240,PIR=20480,DCBS=0,DMBS=0"
;
Related Commands
A.13.8.9 ED-QUEUE
A.13.8.11 ED-PORT-SHAPING
Edits the shaping attribute of a port.
Function
This command modifies the shaping attribute of a port.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-PORT-SHAPING:[<TID>]:<AID>:<CTAG>:::[SHAPINGEN=<SHAPINGEN>],
[CIR=<CIR>],[PIR=<PIR>],[DCBS=<DCBS>],[DMBS=<DMBS>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-PORT-SHAPING::fac-1-10-1:100:::SHAPINGEN=Y,CIR=10240,PIR=20480;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
RTRV-PORT-SHAPINGA.13.8.10 RTRV-QUEUE
A.13.8.12 RTRV-PORT-SHAPING
Queries the shaping attribute of a port.
Function
This command queries the shaping attribute of a port.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-PORT-SHAPING:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::<SHAPINGEN>=<SHAPINGEN>,CIR=<CIR>,PIR=<PIR>,DCBS=<DCBS>,DMBS=<DMBS>"<cr
><lf>
;
Response Parameters
Parameter Description
<SHAPINGEN> Indicates whether shaping is enabled. The valid values are Y and N.
<CIR> Indicates the committed information rate of the shaping. The unit is 1
kbit/s and generally the step length is 64 kbit.
<PIR> Indicates the peak information rate. The unit is 1 kbit/s and generally
its step length is 64 kbit/s.
<DCBS> Indicates the delta committed burst size. The unit is 1 KB.
<DMBS> Indicates the delta maximum burst size. The unit is 1 KB.
Example
l Command
RTRV-PORT-SHAPING::FAC-1-1-10:100;
l Response Message
M1050 2003-02-28 12:23:20
M 100 COMPLD
"FAC-1-1-10::SHAPINGEN=Y,CIR=10240,PIR=20480,DCBS=0,DMBS=0"
;
Related Commands
ED-PORT-SHAPINGA.13.8.9 ED-QUEUE
A.13.8.13 RTRV-FLUX-FLOW
Queries the traffic record of a flow.
Function
This command queries the traffic record of a flow.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-FLUX-FLOW:
[<TID>]:<AID>:<CTAG>:::<BGNDATE>,<BGNTIME>,<ENDDATE>,<ENDTIME>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::BGNDATE=<BGNDATE>,BGNTIME=<BGNTIME>,ENDDATE=<ENDDATE>,ENDTIME=<ENDTIME>
"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
<RECFLAG> Indicates the flag that represents whether flow records are generated.
The valid values are Y and N.
<RATE> Indicates the rate of the flow at the time specified by RECDATE and
RECFLAG. The unit is Kbit/s. The value of this parameter is 0 when
RECFLAG is N.
Example
l Command
RTRV-FLUX-FLOW::FLOW-1-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FLOW-1-5-2::RECDATE=2003-02-28,RECTIME=10-00-00,RECFLAG=Y,RATE=10";
"FLOW-1-5-2::RECDATE=2003-02-28,RECTIME=10-15-00,RECFLAG=Y,RATE=10";
"FLOW-1-5-2::RECDATE=2003-02-28,RECTIME=10-30-00,RECFLAG=Y,RATE=10";
"FLOW-1-5-2::RECDATE=2003-02-28,RECTIME=10-45-00,RECFLAG=Y,RATE=100";
"FLOW-1-5-2::RECDATE=2003-02-28,RECTIME=11-00-00,RECFLAG=Y,RATE=100"
Related Commands
ED-FLOWA.13.2.2 ED-FLOW
RTRV-FLOWA.13.2.1 ENT-FLOW
A.13.2.3 DLT-FLOW
A.13.9.1 ENT-MIRROR
Creates a mirror port.
Function
This command creates a mirror port in the unit. All packets of the mirror port can be duplicated
to another specified port, which then can collect and analyze the traffic of the mirror port.
Usage Note
If any service is running on the monitored port, an error message will be displayed.
Category
Configuration
Security
Provisioning
Command Syntax
ENT-MIRROR:[<TID>]:<AID>:<CTAG>:::[INGRESS=<INGRESS>],
[EGRESS=<EGRESS>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-MIRROR::FAC-1-1-1:100:::INGRESS=FAC-1-1-2,EGRESS=FAC-1-1-4;
ENT-MIRROR::FAC-1-1-1:102:::INGRESS=ACC-1-1-2,EGRESS=ACC-1-1-3;
ENT-MIRROR::FAC-1-1-1:102:::INGRESS=ACC-1-1-2;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.9.2 ED-MIRROR
A.13.9.4 DLT-MIRROR
A.13.9.3 RTRV-MIRROR
A.13.9.2 ED-MIRROR
Edits a mirror port.
Function
This command modifies the attributes of a mirror port in the unit.
Usage Note
If there is a service existing on the observing port, an error result will be returned.
Category
Configuration
Security
Provisioning
Command Syntax
ED-MIRROR:[<TID>]:<AID>:<CTAG>:::[INGRESS=<INGRESS>],
[EGRESS=<EGRESS>];
Command Parameters
Parameter Description Default Value
<EGRESS> Indicates the egress mirror port. The packets sent are NA
copied to the specified observing port (<AID>).
The valid format is FAC/ACC-<SHELF ID>-<SLOT
ID>-<PORT ID>.
This parameter is optional. An egress mirror port will
not be indicated unless this parameter is set.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-MIRROR::FAC-1-1-1:100:::INGRESS=FAC-1-1-2,EGRESS=FAC-1-1-4;
ED-MIRROR::FAC-1-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.9.1 ENT-MIRROR
A.13.9.4 DLT-MIRROR
A.13.9.3 RTRV-MIRROR
A.13.9.3 RTRV-MIRROR
Retrieves information about a mirror port.
Function
This command retrieves information about a mirror port in a unit.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MIRROR:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[INGRESS=<INGRESSMIRROR>],[EGRESS=<EGRESSMIRROR>]"<cr><lf>
;
Response Parameters
Parameter Description
<INGRESS> Indicates the ingress mirror port. The packets received are copied
to a specified observing port (<AID>).
The valid format is FAC/ACC-<SHELF ID>-<SLOT ID>-<PORT
ID>.
This parameter is optional. An ingress mirror port will not be
indicated unless this parameter is set.
<EGRESS> Indicates the egress mirror port. The packets sent are copied to the
specified observing port(<AID>).
The valid format is FAC/ACC-<SHELF ID>-<SLOT ID>-<PORT
ID>.
This parameter is optional. An egress mirror port will not be
indicated unless this parameter is set.
Example
l Command
RTRV-MIRROR::FAC-1-1-1:100;
RTRV-MIRROR::FAC-1-1-ALL:100;
RTRV-MIRROR::ALL:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FAC-1-1-1::INGRESS=FAC-1-1-2,EGRESS=FAC-1-1-4"
;
Related Commands
A.13.9.1 ENT-MIRROR
A.13.9.2 ED-MIRROR
A.13.9.4 DLT-MIRROR
A.13.9.4 DLT-MIRROR
Deletes a mirror port.
Function
This command deletes a mirror port in a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-MIRROR:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-MIRROR::FAC-1-1-1:100;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.13.9.1 ENT-MIRROR
A.13.9.2 ED-MIRROR
A.13.9.3 RTRV-MIRROR
A.13.9.5 DLT-SRVMIRROR-ETHLINK
Delete service mirror of an ethernet link.
Function
This command delete service mirror of an ethernet link.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-SRVMIRROR-ETHLINK:[<TID>]:<LINK_FROM>,<LINK_TO>:<CTAG>:::
[INTAG=<INTAG>],[INSTAG=<INSTAG>],[PORTPOSITION=<PORTPOSITION>],
[SRVDIR=<SRVDIR>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-SRVMIRROR-
ETHLINK::fac-1-1,vcg-1-2:100:::INTAG=10,PORTPOSITION=OUT,SRVDIR=INGRESS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.9.6 ENT-SRVMIRROR-ETHLINK
A.13.9.7 RTRV-SRVMIRROR-ETHLINK
A.13.9.6 ENT-SRVMIRROR-ETHLINK
Creates service mirror of an ethernet link.
Function
This command creates service mirror of an ethernet link.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-SRVMIRROR-ETHLINK:[<TID>]:<LINK_FROM>,<LINK_TO>:<CTAG>:::
[INTAG=<INTAG>],[INSTAG=<INSTAG>],[PORTPOSITION=<PORTPOSITION>],
[SRVDIR=<SRVDIR>],[OBSERPORT=<ETN_PORT>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-SRVMIRROR-
ETHLINK::FAC-1-1,VCG-1-2:100:::INTAG=10,PORTPOSITION=OUT,SRVDIR=INGRESS,OBSERPORT=
FAC-1-3;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.9.5 DLT-SRVMIRROR-ETHLINK
A.13.9.7 RTRV-SRVMIRROR-ETHLINK
A.13.9.7 RTRV-SRVMIRROR-ETHLINK
Retrieves the information about service mirror.
Function
This command retrieves the information about service mirror.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-SRVMIRROR-ETHLINK:[<TID>]:<LINK_FROM>,<LINK_TO>:<CTAG>:::
[INTAG=<INTAG>],[INSTAG=<INSTAG>],[PORTPOSITION=<PORTPOSITION>],
[SRVDIR=<SRVDIR>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<SPEC_FROM>,<SPEC_TO>::[INTAG=<INTAG>],[INSTAG=<INSTAG>],
[PORTPOSITION=<PORTPOSITION>],[SRVDIR=<SRVDIR_GET>],[OBSERPORT=<ETN_PORT>],
[BYTENULL=<BYTE_NULL>]"<cr><lf>
;
Response Parameters
Parameter Description
Parameter Description
<BYTE_NULL> NO use.
Example
l Command
RTRV-SRVMIRROR-
ETHLINK::FAC-1-1,VCG-1-2:100:::INTAG=10,PORTPOSITION=IN,SRVDIR=INGRESS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FAC-1-1,VCG-1-2:100:::INTAG=10,PORTPOSITION=OUT,SRVDIR=INGRESS,OBSERPORT=FAC-1-3"
;
Related Commands
A.13.9.6 ENT-SRVMIRROR-ETHLINK
A.13.9.5 DLT-SRVMIRROR-ETHLINK
A.13.9.8 DLT-SRVMIRROR-PW
Delete service mirror of an ethernet PW.
Function
This command delete service mirror of an ethernet PW.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-SRVMIRROR-PW:[<TID>]:<ENT_PWID>:<CTAG>:::
[PORTPOSITION=<PORTPOSITION>],[SRVDIR=<SRVDIR>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-SRVMIRROR-PW::PW-1-1:100:::PORTPOSITION=IN,SRVDIR=INGRESS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.9.9 ENT-SRVMIRROR-PW
A.13.9.10 RTRV-SRVMIRROR-PW
A.13.9.9 ENT-SRVMIRROR-PW
Creates service mirror of an ethernet PW.
Function
This command creates service mirror of an ethernet PW.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-SRVMIRROR-PW:[<TID>]:<ENT_PWID>:<CTAG>:::
[PORTPOSITION=<PORTPOSITION>],[SRVDIR=<SRVDIR>],
[OBSERPORT=<ETN_PORT>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-SRVMIRROR-PW::PW-1-1:100:::PORTPOSITION=IN,SRVDIR=INGRESS,OBSERPORT=FAC-1-3;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.9.8 DLT-SRVMIRROR-PW
A.13.9.10 RTRV-SRVMIRROR-PW
A.13.9.10 RTRV-SRVMIRROR-PW
Retrieves the information about service mirror of PW.
Function
This command retrieves the information about service mirror of PW.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-SRVMIRROR-PW:[<TID>]:<RTRV_PWID>:<CTAG>:::
[PORTPOSITION=<PORTPOSITION>],[SRVDIR=<SRVDIR>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<RTRV_PWID>::[PORTPOSITION=<PORTPOSITION_GET>],[SRVDIR=<SRVDIR_GET>],
[OBSERPORT=<ETN_PORT>],[OBSERPORT=<ETN_PORT>]"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-SRVMIRROR-PW::PW-1-1:100:::PORTPOSITION=IN,SRVDIR=INGRESS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"PW-1-1:100:::PORTPOSITION=IN,SRVDIR=INGRESS,OBSERPORT=FAC-1-3;"
;
Related Commands
A.13.9.9 ENT-SRVMIRROR-PW
A.13.9.8 DLT-SRVMIRROR-PW
A.13.9.11 DLT-SRVMIRROR-TUNNEL
Delete service mirror of an ethernet TUNNEL.
Function
This command delete service mirror of an ethernet TUNNEL.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-SRVMIRROR-TUNNEL:[<TID>]:<ENT_TUNNELID>:<CTAG>:::
[PORTPOSITION=<PORTPOSITION>],[SRVDIR=<SRVDIR>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-SRVMIRROR-TUNNEL::TUNNEL-1-1:100:::PORTPOSITION=IN,SRVDIR=INGRESS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.9.12 ENT-SRVMIRROR-TUNNEL
A.13.9.13 RTRV-SRVMIRROR-TUNNEL
A.13.9.12 ENT-SRVMIRROR-TUNNEL
Creates service mirror of an ethernet TUNNEL.
Function
This command creates service mirror of an ethernet TUNNEL.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-SRVMIRROR-TUNNEL:[<TID>]:<ENT_TUNNELID>:<CTAG>:::
[PORTPOSITION=<PORTPOSITION>],[SRVDIR=<SRVDIR>],
[OBSERPORT=<ETN_PORT>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-SRVMIRROR-
TUNNEL::TUNNEL-1-1:100:::PORTPOSITION=IN,SRVDIR=INGRESS,OBSERPORT=FAC-1-3;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.9.11 DLT-SRVMIRROR-TUNNEL
A.13.9.13 RTRV-SRVMIRROR-TUNNEL
A.13.9.13 RTRV-SRVMIRROR-TUNNEL
Retrieves the information about service mirror of TUNNEL.
Function
This command retrieves the information about service mirror of TUNNEL.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-SRVMIRROR-TUNNEL:[<TID>]:<RRTRV_TUNNELID>:<CTAG>:::
[PORTPOSITION=<PORTPOSITION>],[SRVDIR=<SRVDIR>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<RTRV_TUNNELID>::[PORTPOSITION=<PORTPOSITION_GET>],[SRVDIR=<SRVDIR_GET>],
[OBSERPORT=<ETN_PORT>],[OBSERPORT=<ETN_PORT>]"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-SRVMIRROR-TUNNEL::TUNNEL-1-1:100:::PORTPOSITION=IN,SRVDIR=INGRESS;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"TUNNEL-1-1:100:::PORTPOSITION=IN,SRVDIR=INGRESS,OBSERPORT=FAC-1-3"
;
Related Commands
A.13.9.12 ENT-SRVMIRROR-TUNNEL
A.13.9.11 DLT-SRVMIRROR-TUNNEL
A.13.10.1 OPR-OAM-LB
Operates an Ethernet OAM loopback test.
Function
This command is used to operate an Ethernet OAM loopback test.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
OPR-OAM-LB:[<TID>]:<AID>:<CTAG>:::LBTYPE=<LBTYPE>,
[DSTMPID=<DSTMPID>],[DSTMACADDR =<DSTMACADDR >];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::LBTYPE=<MPSTDTYPE>,[DSTMPID=<DSTMPID>],[DSTMACADDR=<DSTMACADDR>],
[OAMRESULT=<OAMRESULT>]"<cr><lf>
;
Response Parameters
Parameter Description
<LBTYPE> Indicates the type of an LB test. The valid values are as follows:
l MP: LB test based on MP
l MACADDR: LB test based on MAC address
<OAMRESULT> Indicates the test result. The valid values are FAIL and SUCCESS.
Example
l Command
OPR-OAM-LB::MP-1-1-10:100:::LBTYPE=MP,DSTMPID=2;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
"MP-1-1-10::DSTMPID=2,OAMRESULT=SUCCESS"
;
Related Commands
A.13.10.3 ENT-MD
A.13.10.4 DLT-MD
A.13.10.5 RTRV-MD
A.13.10.2 OPR-OAM-LT
Operates an Ethernet OAM link trace test.
Function
This command is used to operate an Ethernet OAM link trace test.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
OPR-OAM-LT:[<TID>]:<AID>:<CTAG>:::DSTMPID=<DSTMPID>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[DSTMPID=<DSTMPID],[RSPMPID=<RSPMPID>],[RSPMACADDR=<RSPMACADDR>],
[RSPMPTYPE=<RSPMPTYPE>],[HOPNUM=<HOPNUM>],[OAMRESULT=<OAMRESULT>]"<cr><lf>
;
Response Parameters
Parameter Description
<RSPMACADDR> Indicates the RSP MP address. This parameter is valid for standard
MP.
Parameter Description
<RSPMPTYPE> Indicates the RSP MP type. The valid values are as follows:
l MEP: maintenance end point.
l MIP: maintenance intermediate point.
l NULL: unknown MP type.
<HOPNUM> Indicates the hop number. The valid value ranges from 0 to 255.
<OAMRESULT> Indicates test result. The valid values are FAIL and SUCCESS.
Example
l Command
OPR-OAM-LT::MP-1-1-10:100:::DSTMPID=2;
l Response Message
NE 2008-08-05 17:50:00
M 100 COMPLD
"MP-1-1-10::DSTMPID=2,RSPMPID=3,RSPMPTYPE=MEP,HOPNUM=1,OAMRESULT=SUCCESS"
;
Related Commands
A.13.10.3 ENT-MD
A.13.10.4 DLT-MD
A.13.10.5 RTRV-MD
A.13.10.3 ENT-MD
Creates a maintenance domain (MD).
Function
This command creates an MD of Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-MD[<TID>]:<AID>:<CTAG>:::LEVEL=<LEVEL>,NAMETYPE=<NAMETYPE>,
[NAME=<NAME>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-MD::MD-1-2-1:1:::LEVEL=0,NAMETYPE=STRING,NAME="MD1"
l Response Message
NE 2008-08-25 18:54:51
M 1 COMPLD
;
Related Commands
A.13.10.4 DLT-MD
A.13.10.5 RTRV-MD
A.13.10.4 DLT-MD
Deletes an MD (maintenance domain).
Function
This command deletes a MD for Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-MD:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-MD::MD-1-1-10:100;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.13.10.3 ENT-MD
A.13.10.5 RTRV-MD
A.13.10.5 RTRV-MD
Retrieves the maintenance domain (MD).
Function
This command retrieves an MD for Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MD:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[LEVEL=<LEVEL>],[NAMETYPE=<NAMENAME>],[NAME=<NAME>],
[MALIST=<MAID>]"<cr><lf>
;
Response Parameters
Parameter Description
<LEVEL> Indicates the level of the MD, which is used to identify different
customers.
The valid value ranges from 0 to 7. The value "0" indicates the highest
priority.
Parameter Description
Example
l Command
RTRV-MD::MD-1-1-10:100;
RTRV-MD::MD-1-1-ALL:100;
RTRV-MD::ALL:100;
l Response Message
NE 2008-08-05 18:05:00
M 100 COMPLD
"MD-1-1-10:: LEVEL=7,NAMETYPE=NONAME,NAME=,MALIST=MA-1-11-1&MA-1-11-2"
;
Related Commands
A.13.10.3 ENT-MD
A.13.10.4 DLT-MD
A.13.10.6 ENT-MA
Creates a maintenance association (MA).
Function
This command creates an MA for Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ENT-MA:[<TID>]:<AID>:<CTAG>:::MDID=<MD_AID>,NAME=<MANAME>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-MA::MA-1-2-1:1:::MDID=MD-1-2-1,NAME=MA1;
l Response Message
NE 2008-08-25 18:54:51
M 1 COMPLD
;
Related Commands
A.13.10.7 DLT-MA
A.13.10.8 RTRV-MA
A.13.10.7 DLT-MA
Deletes a maintenance association (MA).
Function
This command deletes an MA for Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-MA:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-MA::MA-1-1-10:100;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.13.10.6 ENT-MA
A.13.10.8 RTRV-MA
A.13.10.8 RTRV-MA
Retrieves the maintenance association (MA).
Function
This command retrieves the MA for Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MA:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[MD=<SPEC_MDID>],[NAME=<MANAME>]"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-MA::MA-1-1-10:100;
RTRV-MA::MA-1-1-ALL:100;
RTRV-MA::ALL:100;
l Response Message
NE 2005-08-05 18:05:00
M 100 COMPLD
"MA-1-1-10::MD=MD-1-1-1,NAME=HUAWEI"
;
Related Commands
A.13.10.6 ENT-MA
A.13.10.7 DLT-MA
A.13.10.9 ENT-MP
Creates a maintenance point (MP).
Function
This command creates an MP for Ethernet OAM in a unit.
Usage Note
For NGWDM equipment, the OAM function is not supported by the L4G.
Category
Configuration
Security
Provisioning
Command Syntax
ENT-MP:
[<TID>]:<AID>:<CTAG>:::STANDARDTYPE=<STANDARDTYPE>,SRVTYPE=<SRVTY
PE>,LINKFROM=<LINKFROM>,LINKTO=<LINKTO>,[INTAG=<INTAG>],
[INSTAG=<INSTAG>],[VLANID=<VLANID>],
[LEVEL=<LEVEL>],MPTYPE=<MPTYPE>,MPDIR=<MPDIR>,
[CCTIMER=<CCTIMER>],[LBTIME=<LBTIME>],[LTTIME=<LTTIME>],
[MCCCSTATUS=<MCCCSTATUS>],[MD=<MD>],[MA=<MA>],
[MACADDR=<MACADDR>],[IPADDR=<IPADDR>],
[PINGFRAMELENGTH=<PINGFRAMELENGTH>],
[PINGOVERTIME=<PING_OVER_TIME>],
[PDFRAMELENGTH=<PDFRAMELENGTH>],[PDOVERTIME=<PDOVERTIME>],
[AISSTATE=<AISSTATE>],[CLIENTLAYER=<CLIENTLAYER>],
[AISPERIOD=<AISPERIOD>];
Command Parameters
Parameter Description Default
Value
<STANDARDTY Indicates the type of the MP. The valid values are as NA
PE> follows:
l NOSTANDARDMP: draft 3 MP
l STANDARDMP: standard MP
<LBTIME> Indicates the period when an LB test times out. This 5000 (ms)
parameter is used for the LB test.
The valid value ranges from 3000 to 60000 (units in
milliseconds with the step length of 100).
<LTTIME> Indicates the period when an LT test times out. This 5000(ms)
parameter is used for the LT test that serves the same
purpose as that of the LB test.
The valid value ranges from 3000 to 60000 (units in
milliseconds with the step length of 100).
<CLIENTLAYER Indicates the client layer. The valid value ranges from 7
> 1 to 7.
Sets the alarm suppression level of a node. This level
should be higher than the level of the MD where the
node resides.
This parameter is valid only for standard MP.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ENT-
MP::MP-1-12-2:C:::STANDARDTYPE=STANDARDMP,SRVTYPE=LINK,LINKFROM=FAC-1-12-3,LINKTO=
ACC-1-12-1,VLANID=2,MPTYPE=MEP,MPDIR=INGRESS,CCTIMER=4,LBTIME=5000,LTTIME=5000,MCC
CSTATUS=INACTIVE,MD=MD-1-12-1,MA=MA-1-12-1,MACADDR=01-80-
c2-00-00-30,IPADDR=10.1.1.2,PINGFRAMELENGTH=64,PINGOVERTIME=3,PDFRAMELENGTH=64,PDO
VERTIME=3,AISSTATE=ACTIVE,CLIENTLAYER=7,AISPERIOD=60000;
l Response Message
NE 2008-08-25 18:54:51
M C COMPLD
;
Related Commands
A.13.10.10 ED-MP
A.13.10.11 DLT-MP
A.13.10.12 RTRV-MP
A.13.10.10 ED-MP
Edits the maintenance point (MP).
Function
This command modifies the MP for Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-MP:[<TID>]:<AID>:<CTAG>:::[CCTIMER=<CCTIMER>],[LBTIME=<LBTIME>],
[LTTIME=<LTTIME>],[MCCCSTATUS=<MCCCSTATUS>],
[MACADDR=<MPCCMAC>],[IPADDR=<MPIP>],
[PINGFRAMELENGTH=<MPPINGFRMLEN>],
[PINGOVERTIME=<MPPINGOVERTIME>],
[PDFRAMELENGTH=<MPPDFRMLEN>],[PDOVERTIME=<MPPDOVERTIME>],
[AISSTATE=<AISSTATE>],[CLIENTLAYER=<CLIENTLAYER>],
[AISPERIOD=<AISPERIOD>];
Command Parameters
Parameter Description Default Value
<CLIENTLA Indicates the client layer. The valid value ranges from 7
YER> 1 to 7.
Sets the alarm suppression level of a node. This level
should be higher than the level of the MD in which the
node resides.
This parameter is valid only for standard MP.
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-
MP::MP-1-12-2:C:::CCTIMER=4,LBTIME=5000,LTTIME=5000,MCCCSTATUS=INACTIVE,MD=MD-1-12
-1,MA=MA-1-12-1,MACADDR=01-80-
c2-00-00-30,IPADDR=10.1.1.2,PINGFRAMELENGTH=64,PINGOVERTIME=3,PDFRAMELENGTH=64,PDO
VERTIME=3,AISSTATE=ACTIVE,CLIENTLAYER=7,AISPERIOD=60000;
l Response Message
NE 2008-08-25 18:54:51
M C COMPLD
;
Related Commands
A.13.10.9 ENT-MP
A.13.10.11 DLT-MP
A.13.10.12 RTRV-MP
A.13.10.11 DLT-MP
Deletes a maintenance point (MP).
Function
This command deletes an MP for Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
DLT-MP:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
DLT-MP::MP-1-1-10:100;
l Response Message
NE 2005-08-05 17:50:00
M 100 COMPLD
;
Related Commands
A.13.10.9 ENT-MP
A.13.10.10 ED-MP
A.13.10.12 RTRV-MP
A.13.10.12 RTRV-MP
Retrieves a maintenance point (MP).
Function
This command retrieves an MP for Ethernet OAM in a unit.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-MP:[<TID>]:<AID>:<CTAG>;
Command Parameters
Paramet Description Default
er Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::STANDARDTYPE=<STANDARDTYPE>,SRVTYPE=<SRVTYPE>,LINKFROM=<LINKFROM>,LINKT
O=<LINKTO>,[INTAG=<INTAG>],[INSTAG=<INSTAG>],[VLANID=<VLANID>],
[LEVEL=<LEVEL>],MPTYPE=<MPTYPE>,MPDIR=<MPDIR>,CCTIMER=<CCTIMER>,LBTIME=<LBTIME>,LT
TIME=<LTTIME>,MCCCSTATUS=<MCCCSTATUS>,[MD=<MD>],[MA=<MA>],[ MACADDR=<MACADDR>],
[IPADDR=<IPADDR>],[PINGFRAMELENGTH=<PINGFRAMELENGTH>],
[PINGOVERTIME=<PINGOVERTIME>],[PDFRAMELENGTH=<PDFRAMELENGTH>],
[PDOVERTIME=<PDOVERTIME>],[AISSTATE=<AISSTATE>],[CLIENTLAYER=<CLIENTLAYER>],
[AISPERIOD=AISPERIOD]"<cr><lf>
;
Response Parameters
Parameter Description
<STANDARDTYP Indicates the type of the MP. The valid values are as follows:
E> l NOSTANDARDMP: draft 3 MP
l STANDARDMP: standard MP
Parameter Description
<INTAG> Indicates the tag of incoming packets. The tag can be a VLAN ID. This
parameter is optional and indicates an EPL in this response.
<INSTAG> Indicates the VLAN tag of the incoming service. This parameter is
optional.
<LEVEL> Indicates the level of OAM frames, which is used to identify different
customers.
The valid value ranges from 0 to 7. The value "0" indicates the highest
priority.
<CCTIMER> Indicates the transmission cycle of the continuity check (CC) message.
This parameter is used for the CC test.
<LBTIME> Displays the LB test timeout time. This parameter is used for the LB
test.
The valid value ranges from 3000 to 60000. Units are in milliseconds
and the step length is 100.
Parameter Description
<LTTIME> Displays the LT test timeout time. This parameter is used for the LT
test, which serves the same purpose as that of the LB test.
The valid value ranges from 3000 to 60000. Units are in milliseconds
and the step length is 100.
<CLIENTLAYER> Indicates the client layer. The valid value ranges from 1 to 7.
Sets the alarm suppression level of a node. This level should be higher
than the level of the MD in which the node resides.
<AISPERIOD> Indicates the AIS period (units are in milliseconds and there are not
any step lengths).
Example
l Command
RTRV-MP::MP-1-12-1:C;
l Response Message
NE 2008-08-25 00:27:16
M C COMPLD
"MP-1-12-1::STANDARDTYPE=STANDARDMP,SRVTYPE=LINK,LINKFROM=FAC-1-12-3,LINKTO=ACC-1-
12-1,VLANID=1,LEVEL=0,MPTYPE=MEP,MPDIR=INGRESS,CCTIMER=5000,LBTIME=5000,LTTIME=500
0,MCCCSTATUS=INACTIVE,MD=MD-1-12-1,MA=MA-1-12-1,MACADDR=01-80-
c2-00-00-30,IPADDR=10.1.1.1,PINGFRAMELENGTH=64,PINGOVERTIME=3,PDFRAMELENGTH=64,PDO
VERTIME=3,AISSTATE=ACTIVE,CLIENTLAYER=7,AISPERIOD=60000"
;
Related Commands
A.13.10.9 ENT-MP
A.13.10.11 DLT-MP
A.13.10.10 ED-MP
A.13.10.13 REPT^EVT^OAMSERVICELOOP
Reports service loop events.
Function
When the OAM service loop is detected by the ETHOAM protocol, the MP service loop events
will be reported.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
A^^<ATAG>^REPT^EVT^OAMSERVICELOOP<cr><lf>
^^^"<AID>:<PORT>,<VLANID>,<LEVEL>,<DIR>" <cr><lf>
;
Response Parameters
Parameter Description
<PORT> Indicates the channel on which the service loop occurred. The valid
format is FAC/ACC-<SHELF>-<SLOT>-<PORT>.
Example
l Command
None
l Response Message
NE 2008-12-11 15:11:53
* 667681 REPT EVT OAMSERVICELOOP
"MP-1-3-1:FAC-1-3-1,1,0,EGRESS"
;
>
Related Commands
None
A.13.10.14 STA-OAM-PING
Starts an OAM ping test.
Function
This command instructs an NE to start a ping test.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
STA-OAM-PING:[<TID>]:<AID>:<CTAG>:::DSTIP=<DSTIP>,PINGTIME
=<PINGTIME>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STA-OAM-PING::MP-1-12-2:a:::dstip=129.9.0.100,pingtime=100;
l Response Message
NE 1990-01-03 10:36:49
M A COMPLD
;
Related Commands
None
A.13.10.15 STP-OAM-PING
Stops an Ethernet OAM ping test.
Function
This command instructs an NE to stop a ping test.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
STP-OAM-PING:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS>
<cr><lf>M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STP-OAM-PING::MP-1-12-2:a;
l Response Message
NE 2008-01-03 10:36:49
M A COMPLD
;
Related Commands
None
A.13.10.16 STA-OAM-PERDECT
Starts Ethernet OAM performance detection
Function
This command instructs an NE to start Ethernet OAM performance detection.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
STA-OAM-PERDECT:
[<TID>]:<AID>:<CTAG>:::DSTMP=<DSTMP>,PDTIME=<PDTIME>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STA-OAM-PERDECT::MP-1-12-1:1:::DSTMP=2,PDTIME=10;
l Response Message
NE 1990-01-03 12:59:28
M 1 COMPLD
;
Related Commands
None
A.13.10.17 STP-OAM-PERDECT
Stops Ethernet OAM performance detection.
Function
This command instructs an NE to stop Ethernet OAM performance detection.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
STP-OAM-PERDECT:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STP-OAM-PERDECT::MP-1-12-1:1;
l Response Message
NEW-NE 1990-01-03 12:59:28
M 1 COMPLD
;
Related Commands
None
A.13.10.18 ED-P2POAM-ADMIN
Edits the administration parameters of the point-to-point OAM.
Function
This command modifies the administration parameters of the point-to-point OAM.
Usage Note
None
Category
Configuration
Security
Provisioning
Command Syntax
ED-P2POAM-ADMIN:[<TID>]:<AID>:<CTAG>:::
[P2POAMENABLE=<P2POAMENABLE>],[P2POAMMODE=<P2POAMMODE>],
[LNKEVTNTFY=<LNKEVTNTFY>],[RSPRMTLB=<RSPRMTLB>],
[ERRFRMWINDOW=<ERRFRMWINDOW>],[ERRFRMTH=<ERRFRMTH>],
[ERRFRMPRDWINDOW=<ERRFRMPRDWINDOW>],
[ERRFRMPRDTH=<ERRFRMPRDTH>],
[ERRFRMSECWINDOW=<ERRFRMSECWINDOW>],
[ERRFRMSECTH=<ERRFRMSECTH>],[UNIOPEREN=<UNIOPEREN>],
[RMTLBCNTL=<RMTLBCNTL>],[LDPORTBLOCK=<LDPORTBLOCK>],
[LDENABLE=<LDENABLE>];
Command Parameters
Parameter Description Default Value
<ERRFRMPRD Indicates the monitoring time window of the error Maxpps (The
WINDOW> frame period (units in frames). value varied
The value is determined as follows: with different
units.)
l 1. Based on the MaxSpeed (units are in bits and
valid values are: 10M, 100M, 1000M, or 10000M)
that the specific card supports, the following
formula is used to compute the maximum number
of frames that the port can receive per second at
the maximum speed. (The frames are computed at
64 bytes; preambles at 8 bytes; and IPG*Speed 96
bits.).
Maxpps (number of frames received per second)
= MaxSpeed/(Frame*8 + Preamble*8 +
IPG*Speed) = MaxSpeed/(64*8 + 8*8 + 96). The
result should be an integer.
NOTE
The values of Maxpps at each rate are as follows:
l 10 Mbit/s: 14880
l 100 Mbit/s: 148800
l 1000 Mbit/s: 1488000
l 10 Gbit/s: 14880000
l 2. The step length is 1.
l 3. According to the preceding computation, the
range of the monitoring window is as follows:
Maxpps/10 to Maxpps*60
Default value: Maxpps
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-P2POAM-
ADMIN::FAC-1-2-4:100:::P2POAMENABLE=DISABLE,P2POAMMODE=ACTIVE,LNKEVTNTFY=ENABLE,RS
PRMTLB=DISABLE,ERRFRMWINDOW=1000,ERRFRMTH=1,ERRFRMPRDWINDOW=14880000,ERRFRMPRDTH=1
,ERRFRMSECWINDOW=60,ERRFRMSECTH=1,UNIOPEREN=DISABLE,LDPORTBLOCK=ENABLE,LDENABLE=DI
SABLE
l Response Message
NE 2005-08-05 16:55:00
M 100 COMPLD
;
Related Commands
A.13.10.19 RTRV-P2POAM-ADMIN
A.13.10.19 RTRV-P2POAM-ADMIN
Retrieves the administration parameters of the point-to-point OAM
Function
This command retrieves the administration parameters of the point-to-point OAM.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-P2POAM-ADMIN:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::[P2POAMENABLE=<P2POAMENABLE>],[P2POAMMODE=<P2POAMMODE>],
[LNKEVTNTFY=<LNKEVTNTFY>],[RSPRMTLB=<RSPRMTLB>],[ERRFRMWINDOW=<ERRFRMWINDOW>],
[ERRFRMTH=<ERRFRMTH>],[ERRFRMPRDWINDOW=<ERRFRMPRDWINDOW>],
[ERRFRMPRDTH=<ERRFRMPRDTH>],[ERRFRMPRDTH=<ERRFRMPRDTH>],
[ERRFRMSECWINDOW=<ERRFRMSECWINDOW>],[ERRFRMSECTH=<ERRFRMSECTH>],
[UNIOPEREN=<UNIOPEREN>],[RMTLBSTATE=<RMTLBSTATE>],[LDPORTBLOCK=<LDPORTBLOCK>],
[LDENABLE =<LDENABLE>]"<cr><lf>
;
Response Parameters
Parameter Description
<P2POAMMODE> Indicates the working mode of Ethernet OAM. The valid values
are PASSIVE and ACTIVE.
Parameter Description
<LDPORTBLOCK> Indicates whether port blocking is enabled. The valid values are
DISABLE and ENABLE.
Parameter Description
<RMTP2POAMMODE> Indicates the Ethernet OAM work mode of the opposite port.
The valid values are PASSIVE and ACTIVE.
Example
l Command
RTRV-P2P0AM-ADMIN::FAC-1-2-4:C;
l Response Message
NE 2008-01-06 20:25:54
M C COMPLD
"FAC-1-2-4::P2POAMENABLE=ENABLE,P2POAMMODE=ACTIVE,LNKEVTNTFY=ENABLE,RSPRMTLB=DISAB
LE,ERRFRMWINDOW=1000,ERRFRMPRDWINDOW=14880000,ERRFRMPRDTH=1,ERRFRMSECWINDOW=60,ERR
FRMSECTH=1,LDPORTBLOCK=ENABLE,LDENABLE=DISABLE"
;
>
Related Commands
A.13.10.18 ED-P2POAM-ADMIN
A.13.11.1 STA-PING-<FETH/GETH/XGETH>
Starts sending Ethernet test frames.
Function
This command instructs an NE to start sending Ethernet test frames.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
STA-PING-<FETH/GETH/XGETH>:[<TID>]:<AID>:<CTAG>:::
[PKTNUM=<PKTNUM>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STA-PING-GETH::ACC-1-1-2:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.11.2 STP-PING-<FETH/GETH/XGETH>
A.13.11.3 RTRV-PING-<FETH/GETH/XGETH>
A.13.11.2 STP-PING-<FETH/GETH/XGETH>
Stops sending Ethernet test frames.
Function
This command instructs an NE to stop sending Ethernet test frames.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
STP-PING-<FETH/GETH/XGETH>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STP-PING-GETH::ACC-1-1-2:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.11.1 STA-PING-<FETH/GETH/XGETH>
A.13.11.3 RTRV-PING-<FETH/GETH/XGETH>
A.13.11.3 RTRV-PING-<FETH/GETH/XGETH>
Retrieves the parameters of a ping test.
Function
This command instructs the NE to retrieve the state and count of Ethernet test frames.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-PING-<FETH/GETH/XGETH>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::TESTMODE=<TESTMODE>,[PKTNUM=<PKTNUM>],TOTALSEND=<TOTALSEND>,
[RESPONDRECV=<RESPONDRECV>,NORMALRECV=<NORMALRECV>]"<cr><lf>
;
Response Parameters
Parameter Description
<PKTNUM> Indicates the number of test packets. By default, packets are continuously
sent until a user changes this parameter.
This parameter is optional. It is required only when <TESTMODE> is set
to BURST.
Example
l Command
RTRV-PING-GETH::ACC-1-1-2:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"ACC-1-1-2::TESTMODE=BURST,PKTNUM=200,TOTALSEND=200,RESPONDRECV=200,NORMALRECV=0"
;
Related Commands
A.13.11.1 STA-PING-<FETH/GETH/XGETH>
A.13.11.2 STP-PING-<FETH/GETH/XGETH>
A.13.11.4 INIT-PING-<FETH/GETH/XGETH>
Initializes the ping test parameters.
Function
This command initializes the counter for Ethernet test frames.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
INIT-PING-<FETH/GETH/XGETH>:[<TID>]:<AID>:<CTAG>:::
[COUNTERTYPE=<COUNTERTYPE>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
INIT-PING-GETH::ACC-1-1-1:100:::COUNTERTYPE=NORM-RECV;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.11.1 STA-PING-<FETH/GETH/XGETH>
A.13.11.3 RTRV-PING-<FETH/GETH/XGETH>
A.13.11.5 REPT^EVT^PING
Reports the frame test event.
Function
This command reports the result of the frame test.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
A^^<ATAG>^REPT^EVT^PING<cr><lf>
^^^"<AID>:<RESPONDRECV>,<NORMALRECV>,<TOTALSEND>,<IPFLAG>" <cr><lf> ;
Response Parameters
Parameter Description
Example
l Command
None
l Response Message
NE 2003-02-28 12:23:20
A 100 REPT EVT PING
"ACC-1-5-3:100,100,100,COMPLD"
;
Related Commands
None
A.13.11.6 STA-CAPT
Create port capture rules.
Function
This command instructs an NE create port capture rules.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
STA-CAPT:[<TID>]:<STA_PCSN>:<CTAG>:::PORT=<INPORT>,
[VLANID=<PKTVLANID>],[CAPTDIR=<CAPTDIR>],[PKTTYPE=<DFTPKTTYPE>],
[CAPTNUM=<CAPTNUM>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STA-CAPT::PCSN-1-1:100:::PORT=FAC-1-1,VLANID=1,CAPTDIR=RX,PKTTYPE=RSTP,CAPTNUM=10;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.11.7 STP-CAPT
A.13.11.8 RTRV-CAPT
A.13.11.7 STP-CAPT
Delete port capture rules.
Function
This command instructs an NE delete port capture rules.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
STP-CAPT:[<TID>]:<STA_PCSN>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STP-CAPT::PCSN-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.11.6 STA-CAPT
A.13.11.8 RTRV-CAPT
A.13.11.8 RTRV-CAPT
Retrieve port capture rules.
Function
This command instructs the NE to retrieve port capture rules.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-CAPT:[<TID>]:<RTRV_PCSN>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::PORT=<INPORT>,[VLANID=<PKTVLANID>],CAPTDIR=<CAPTDIR>,[PKTTYPE]
=<DFTPKTTYPE>,[CAPTNUM]=<CAPTNUM>,[PKTLEN]=<DFTPKTLEN>,[PACKET]
=<DFTPKT>;"<cr><lf>
;
Response Parameters
Parameter Description
<PKTVLANID> Indicates the identify of a vlan.Valid value can range from 0 to 4095.
Default to capture packet from the port.
<CAPTDIR> Indicates the direction from which the user will capture packet. Valid
value can be as follows:TX: 1 RX: 2 ,Optional, default value is TX.
Example
l Command
RTRV-CAPT::PCSN-1-1:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"PCSN-1-1::PORT=FAC-1-1-1,VLANID=100,CAPTDIR=TX,PKTTYPE=GFPCMF,CAPTNUM=10,PKTLEN=1
0,PACKET=10"
;
Related Commands
A.13.11.6 STA-CAPT
A.13.11.7 STP-CAPT
A.13.11.9 INIT-TEST-<FETH/GETH/VCG>
Initialize all the ethernet test packet counter.
Function
This command initializes the ethernet test packet counter.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
INIT-TEST-<FETH/GETH/VCG>:
[<TID>]:<AID>:<CTAG>:::COUNTERTYPE=<COUNTERTYPE>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
INIT-TEST-FETH::FAC-1-2-3:102:::COUNTERTYPE=ALL;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.11.11 STA-TEST-<FETH/GETH/VCG>
A.13.11.12 STP-TEST-<FETH/GETH/VCG>
A.13.11.10 RTRV-TEST-<FETH/GETH/VCG>
A.13.11.10 RTRV-TEST-<FETH/GETH/VCG>
Retrieves the packet content of a port test.
Function
This command instructs the NE to retrieve the packet content of a port test.
Usage Note
None
Category
Configuration
Security
Retrieve
Command Syntax
RTRV-PING-<FETH/GETH/VCG>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
^^^"<AID>::TESTMODE=<TESTMODE>,[PKTNUM=<PKTNUM>],TOTALSEND=<TOTALSEND>,
[CURRENTSEND]=<CURRENTSEND>,[PKTLEN]=<PKTLEN>,[PKTTYPE]=<PKTTYPE>,[STUFFTYPE]
=<PKTDATATYPE>,[PKTMACDA]=<PKTMACDA>,[PKTMACSA]=<PKTMACSA>,[PKTIPDA]=<PKTIPDA>,
[PKTIPSA]=<PKTIPSA>,[PKTVLANID]=<PKTVLANID>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-TEST-FETH::FAC-1-2:100;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
"FAC-1-1::TESTMODE=BURST,PKTNUM=6000,TOTALSEND=3000,CURRENTSEND=500,PKTLEN=128,PKT
TYPE=CUSTOM,STUFFTYPE=0xAA,PKTMACDA=01-02-03-04-05-06,PKTMACSA=06-05-04-03-02-01"
;
Related Commands
A.13.11.11 STA-TEST-<FETH/GETH/VCG>
A.13.11.12 STP-TEST-<FETH/GETH/VCG>
A.13.11.11 STA-TEST-<FETH/GETH/VCG>
Starts Ethernet port test.
Function
This command instructs an NE to start sending Ethernet port test frames.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
STA-TEST-<FETH/GETH/VCG>:[<TID>]:<AID>:<CTAG>:::[PKTNUM=<PKTNUM>],
[PKTLEN=<PKTLEN>],[PKTTYPE=<PKTTYPE>],[STUFFTYPE=<PKTDATATYPE>],
[PKTMACDA=<PKTMACDA>],[PKTMACSA=<PKTMACSA>],
[PKTIPDA=<PKTIPDA>],[PKTIPSA=<PKTIPSA>],[PKTVLANID=<PKTVLANID>];
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STA-TEST-
GETH::FAC-1-2-3:100:::PKTNUM=200,PKTLEN=128,PKTTYPE=IP,STUFFTYPE=4,PKTMACDA=01-02-
03-04-05-06,PKTMACSA=01-02-03-04-05-06,PKTIPDA=10.11.12.13,PKTIPSA=10.11.12.13,PKT
VLANID=1;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.11.12 STP-TEST-<FETH/GETH/VCG>
A.13.11.10 RTRV-TEST-<FETH/GETH/VCG>
A.13.11.12 STP-TEST-<FETH/GETH/VCG>
Stops Ethernet port test.
Function
This command instructs an NE to stop Ethernet port test.
Usage Note
None
Category
Configuration
Security
Maintenance
Command Syntax
STP-TEST-<FETH/GETH/VCG>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<SID>^<YYYY-MM-DD>^<HH:MM:SS> <cr><lf>
M^^<CTAG>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
STP-TEST-FETH::FAC-1-2-3:102;
l Response Message
NE 2003-02-28 12:23:20
M 100 COMPLD
;
Related Commands
A.13.11.11 STA-TEST-<FETH/GETH/VCG>
A.13.11.10 RTRV-TEST-<FETH/GETH/VCG>
A.14.1 ED-<ODUN>
Edits the attributes of ODUn logical facility.
Function
This command edits the attributes of the ODUn logical facility.
Usage Note
ODUn includes ODU0,ODU1,ODU2,ODU5G,ODU3,ODU4 and ODUflex.
Category
Facility
Security
Provisioning
Command Syntax
ED-<ODUN>:[<TID>]:<AID>:<CTAG>:::[TYPE=<TYPE>],
[SPEEDCHG=<SPEEDCHG>],[ENCAP=<ENCAP>],[BIP8MODE=<BIP8MODE>],
[DEGTH=<DEGTH>],[DEGTIME=<DEGTIME>],
[DEGINTERVAL=<DEGINTERVAL>],[SFBER=<SFBER>],[SDBER=<SDBER>],
[TIMACT=<TIMACT>],[TIMMODE=<TIMMODE>],[EXPTTISAPI=<EXPTTISAPI>],
[EXPTTIDAPI=<EXPTTIDAPI>],[TTISAPI=<TTISAPI>],[TTIDAPI=<TTIDAPI>],
[TTIOPER=<TTIOPER>],[EXPPT=<EXPPT>],[FTFLOPER=<FTFLOPER>],
[LCKEN=<LCKEN>],[NONINTRMON=<NONINTRMON>],
[LTCACTEN=<LTCACTEN>],[DELAYTIME=<DELAYTIME>],
[PLM2AIS=<PLM2AIS>],[MSIM2AIS=<MSIM2AIS>],[VCPLM2AIS=<VCPLM2AIS>],
[GCCTRANS=<GCCTRANS>],[RESTRANS=<RESTRANS>],[RATETOL=<RATETOL>]:
[<PST>];
Command Parameters
Parameter Default
s Description Value
<TYPE> ODU2 and ODU3 have a standard mode and a high-speed The default
mode. This parameter is only valid for ODU2 and ODU3. The value varies
valid values are as follows: with different
l STD: indicates the standard mode; the rate is 10.7 Gbit/s units.
(ODU2) or 43 Gbit/s (ODU3).
l ODU2E: The bit rate is 11.1 Gbit/s.
l ODU3E: The bit rate is 44 Gbit/s.
Parameter Default
s Description Value
<BIP8MOD Indicates the BIP8 error detection mode of an OTN. The valid The default
E> values are as follows: value varies
l POISSON with different
units.
l BURST
<DEGTH> Indicates the SD threshold for bit errors in BURST mode. This ODU0:3050
parameter is valid only when <BIP8MODE> is set to BURST. ODU1: 6126
The value ranges are as follows: ODU5G:
l ODU0: 1-10167 12303
l ODU1: 1-20420 ODU2:
l ODU5G: 1-41012 24607
l ODU2: 1-82025 ODU3:
98847
l ODU3: 1-329491
ODU4:
l ODU4: 1-856387 256916
l ODUFLEX: For ODUFlex (N = 1), the DEG value range
is the same as that of ODU0; for ODUFlex (N = 2), the
maximum DEG threshold is 2 x ODU0 maximum
threshold. For ODUFlex (N = [3,7]), the maximum DEG
threshold is (N – 0.5) x ODU0 maximum threshold.
<DEGINTE Indicates the DEG detection time. Valid values include 10 ms, 1000 ms
RVAL> 100 ms, and 1000 ms.
Parameter Default
s Description Value
Parameter Default
s Description Value
<FTFLOPE Indicates the operator-specific field that contains the fault type NA
R> and fault location information. It is a string with no more than
118 bytes.
Parameter Default
s Description Value
Parameter Default
s Description Value
<PST> Indicates the status of the primary state qualifier. The valid NA
values are IS and OOS.
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-ODU1::CLNT-1-1-1-1:100:::BIP8MODE=POISSON;
l Response Message
NE 2008-06-01 10:30:18 M 100 COMPLD ;
Related Commands
A.14.2 RTRV-<ODUN>
A.14.2 RTRV-<ODUN>
Retrieves the attributes of the ODUn logical facility.
Function
This command retrieves the attributes of the ODUn logical facility.
Usage Note
ODUn includes ODU0, ODU1, ODU2, ODU5G, ODU3, ODU4 and ODUflex.
Category
Facility
Security
Retrieve
Command Syntax
RTRV-<ODUN>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ^^^"<AID>::
[TYPE=<TYPE>],[SPEEDCHG=<SPEEDCHG>],[ENCAP=<ENCAP>],[BIP8MODE=<BIP8MODE>],
[DEGTH=<DEGTH>],[DEGTIME=<DEGTIME>],[DEGINTERVAL=<DEGINTERVAL>],[SFBER=<SFBER>],
[SDBER=<SDBER>],[TIMACT=<TIMACT>],[TIMMODE=<TIMMODE>],[EXPTTISAPI=<EXPTTISAPI>],
[EXPTTIDAPI=<EXPTTIDAPI>],[TTISAPI=<TTISAPI>],[TTIDAPI=<TTIDAPI>],
[TTIOPER=<TTIOPER>],[INCTTISAPI=<INCTTISAPI>],[INCTTIDAPI=<INCTTIDAPI>],
[INCTTIOPER=<INCTTIOPER>],[EXPPT=<EXPPT>],[INCPT=<INCPT>],[EXPVCPT=<EXPVCPT>],
[INCVCPT=<INCVCPT>],[FTFLOPER=<FTFLOPER>],[INCFWFT=<INCFWFT>],[INCFWOI=<INCFWOI>],
[INCFWOPER=<INCFWOPER>],[INCBWFT=<INCBWFT>],[INCBWOI=<INCBWOI>],
[INCBWOPER=<INCBWOPER>],[LCKEN=<LCKEN>],[NONINTRMON=<NONINTRMON>],
[DELAYTIME=<DELAYTIME>],[SWITCHSTATE=<SWITCHSTATE>],[PLM2AIS=<PLM2AIS>],
[MSIM2AIS=<MSIM2AIS>],[VCPLM2AIS=<VCPLM2AIS>],[GCCTRANS=<GCCTRANS>],
[RESTRANS=<RESTRANS>],[TS=<TS>],[RATETOL=<RATETOL>]:<PST>,<SST>"<cr><lf> ;
Response Parameters
Parameters Description
<TYPE> ODU2 and ODU3 have a standard mode and a high-speed mode. This
parameter is only valid for ODU2 and ODU3.
l STD: indicates standard mode; the bit rate is 10.7 Gbit/s (ODU2)
or 43 Gbit/s (ODU3).
l ODU2E: The bit rate is 11.1 Gbit/s.
l ODU3E: The bit rate is 44 Gbit/s.
<SPEEDCHG> Indicates whether the rate of ODUN is variable. The valid values are
as follows:
l ENABLE: the rate of ODUN is variable.
l DISABLE: the rate of ODUN is fixed.
<ENCAP> Indicates the encapsulation mode. It is only valid for channels where
the encapsulation mode is configurable.
l ODU2: ODU2 cross-connection is configurable on this channel.
l ODU2_TMUX_ODU1: ODU1 signals are encapsulated into
ODU2 signals, and the inner ODU1 cross-connection is
configurable on this channel.
l ODU1_TMUX_ODU0: ODU0 signals are encapsulated into
ODU1 signals, and the inner ODU0 cross-connection is
configurable on this channel.
l ODU3_TMUX: ODU1 and ODU2 signals are encapsulated into
ODU3 signals. The inner ODU1 and ODU2 cross-connections are
configurable on this channel.
l ODU3: ODU3 cross-connection is configurable on this channel.
l AUTO: AUTO mode
<BIP8MODE> Indicates the BIP8 error detection mode of an OTN. The valid values
are as follows:
l POISSON
l BURST
Parameters Description
<DEGTH> Indicates the signal degrade (SF) threshold for bit errors in BURST
mode. This parameter is only valid when the BIP8MODE is set to
BURST.
The value ranges are as follows:
l ODU0: 1-10167
l ODU1: 1-20420
l ODU5G: 1-41012
l ODU2: 1-82025
l ODU3: 1-329491
l ODU4: 1-856387
l ODUFLEX: For ODUFlex (N = 1), the DEG value range is the
same as that of ODU0; for ODUFlex (N = 2), the maximum DEG
threshold is 2 x ODU0 maximum threshold. For ODUFlex (N =
[3,7]), the maximum DEG threshold is (N – 0.5) x ODU0 maximum
threshold.
<DEGTIME> Indicates the DEG detection time expressed in seconds. This parameter
is valid only when BIP8MODE is set to BURST.
The value range is 1-10.
<DEGINTERVAL Indicates the DEG detection time. Valid values include 10 ms, 100 ms,
> and 1000 ms.
Parameters Description
Parameters Description
<EXPPT> Indicates the expected PT byte. The value is Hexagonal integera with
single byte. Some of the values are defined in the OTN specifications
as follows.
0x01: Experimental mapping
0x02: Asynchronous CBR mapping
0x03: Bit synchronous CBR mapping
0x04: ATM mapping
0x05: GFP mapping
0x06: Virtual Concatenated signal
0x07: PCS codeword transparent Ethernet mapping
0x08: FC-1200 into OPU2e mapping
0x09: GFP mapping into Extended OPU2 payload
0x0A: STM-1 mapping into OPU0
0x0B: STM-4 mapping into OPU0
0x0C: FC-100 mapping into OPU0
0x0D: FC-200 mapping into OPU1
0x0E: FC-400 mapping into OPUflex
0x0F: FC-800 mapping into OPUflex
0x10: Bit stream with octet timing mapping
0x11: Bit stream without octet timing mapping
0x20: ODU multiplex structure supporting ODTUjk only
0x21: ODU multiplex structure supporting ODTUk.ts or ODTUk.ts
and ODTUjk
0xFD: NULL test signal mapping
0xFE: PRBS test signal mapping
<INCPT> Indicates the incoming PT byte. The value is a Hexagonal integera with
single byte, the meaning of each parameter is the same with the
<EXPPT>.
<INCVCPT> Indicates the incoming PT byte. This parameter is only valid for the
virtually concatenated ODU channels.
<FTFLOPER> Indicates the operator-specific field that contains the fault type and
fault location information.
Parameters Description
<DELAYTIME> This parameter is only valid for the channels in an SNCP group.
Indicates the delay time. It is an integer ranging from 0 to 100, which
is expressed in 0.1 seconds.
Delay time is required when multiple protection schemes are
configured. Switching is not initiated until the delay time is expended
when a malfunction is discovered at a port.
Use the default value when only one type of protection is configured.
<SWITCHSTATE Indicates the state of the switching. It is only valid when the port is in
> the protection group. The valid values are provided in A.32.3.20
SWITCHSTATE.
Parameters Description
<TS> Indicates the bandwidth occupied by the ODUflex service when the
ODUflex service is configured on this channel. This parameter is
invalid when other services or no service is configured on this channel.
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-ODU1::CLNT-1-8-1:C;
l Response Message
Related Commands
A.14.1 ED-<ODUN>
A.14.3 ED-<OTUN>
Edits the attributes of OTUn logical facility.
Function
This command edits the attributes of the OTUn.
Usage Note
OTUn includes OTU1, OTU2, OTU3, OTU5G and OTU4.
Category
Facility
Security
Provisioning
Command Syntax
ED-<OTUN>:[<TID>]:<AID>:<CTAG>:::[AUTOADAPT=<AUTOADAPT>],
[FEC=<FEC>],[BEFECSDBER=<BEFECSDBER>],[TYPE=<TYPE>],
[BIP8MODE=<BIP8MODE>],[DEGTH=<DEGTH>],[DEGTIME=<DEGTIME>],
[DEGINTERVAL=<DEGINTERVAL>],[SFBER=<SFBER>],[SDBER=<SDBER>],
[TIMACT=<TIMACT>],[TIMMODE=<TIMMODE>],[EXPTTISAPI=<EXPTTISAPI>],
[EXPTTIDAPI=<EXPTTIDAPI>],[TTISAPI=<TTISAPI>],[TTIDAPI=<TTIDAPI>],
[TTIOPER=<TTIOPER>]:[<PST>];
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
<FEC> Indicates the forward error correction (FEC). The valid The default
values are as follows: value varies
l OFF: indicates that FEC is disabled. with the
different
l STDFEC: indicates that standard FEC is enabled. units.
l AFEC: indicates that advanced FEC is enabled.
l AUTO: Automatically detects the FEC mode.
l HFEC: indicates that High performance FEC is
enabled.
<BEFECSDBER> Indicates the signal degrade (SD) threshold before For standard
FEC. The valid value ranges from 1E-12 to 1E-1. FEC, the
default value
is 1E-6. For
advanced
FEC, the
default value
is 1E-4. For
high
performance
FEC, the
default value
is 8.5E-4.
<BIP8MODE> Indicates the BIP8 error detection mode of an OTN. The default
The valid values are as follows: value varies
l POISSON with the
different
l BURST units.
Default
Parameter Description Value
<DEGTH> Indicates the SD threshold for bit errors in BURST OTU1: 6126
mode. This parameter is only valid when BIP8MODE OTU5G:
is set to BURST. The valid values are as follows: 12303
l OTU1: 1-20420 OTU2:
l OTU5G: 1-41012 24607
l OTU2: 1-82025 OTU3:
98847
l OTU3: 1-329491
OTU4:
l OTU4: 1-856387 256916
Default
Parameter Description Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
ED-OTU1::CLNT-1-1-1:100:::FEC=OFF;
l Response Message
NE 2004-01-01 11:37:18 M 100 COMPLD ;
Related Commands
A.14.4 RTRV-<OTUN>
A.14.4 RTRV-<OTUN>
Retrieves the attributes of the OTUn logical facility.
Function
This command retrieves the attributes of the OTUn logical facility.
Usage Note
OTUn includes OTU1,OTU2,OTU3,OTU5G and OTU4.
Category
Facility
Security
Retrieve
Command Syntax
RTRV-<OTUN>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::AUTOADAPT=<AUTOADAPT>,FEC=<FEC>,BEFECSDBER=<BEFECSDBER>,TYPE=<TYPE>,BIP
8MODE=<BIP8MODE>,DEGTH=<DEGTH>,DEGTIME=<DEGTIME>,DEGINTERVAL=<DEGINTERVAL>,SFBER=<
SFBER>,SDBER=<SDBER>,TIMACT=<TIMACT>,TIMMODE=<TIMMODE>,EXPTTISAPI=<EXPTTISAPI>,EXP
TTIDAPI=<EXPTTIDAPI>,TTISAPI=<TTISAPI>,TTIDAPI=<TTIDAPI>,TTIOPER=<TTIOPER>,INCTTIS
API=<INCTTISAPI>,INCTTIDAPI=<INCTTIDAPI>,INCTTIOPER=<INCTTIOPER>:<PST>,<SST>"<cr><
lf> ;
Response Parameters
Parameters Description
<BEFECSDBER> Indicates the SD threshold before FEC. The valid value ranges from
1E-12 to 1E-1.
the default value is 1E-4 when <FEC> is set to AFEC, 1E-6 when
<FEC> is set to STDFEC, 8.5E-4 when <FEC> is set to HFEC.
<TYPE> OTU2 and OTU3 have a standard and high-speed mode. This
parameter is only valid for OTU2 and OTU3.
l STD: indicates the standard mode; the bit rate is 10.7 Gbit/s (OTU2)
or 43 Gbit/s (OTU3).
l OTU2E: The bit rate is 11.1 Gbit/s.
l OTU3E: The bit rate is 44 Gbit/s.
<BIP8MODE> Indicates the BIP8 error detection mode of an OTN. The valid values
are as follows:
l POISSON
l BURST
<DEGTH> Indicates the SD threshold for bit errors in BURST mode. This
parameter is only valid when BIP8MODE is set to BURST.
The valid values are as follows:
l OTU1: 1-20420
l OTU5G: 1-41012
l OTU2: 1-82025
l OTU3: 1-329491
l OTU4: 1-856387
Parameters Description
<DEGTIME> Indicates the DEG detection time expressed in seconds. This parameter
is only valid when BIP8MODE is set to BURST.
The valid value ranges from 1 to 10.
<DEGINTERVAL Indicates the DEG detection time. Valid values include 10 ms, 100 ms,
> and 1000 ms.
Parameters Description
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-OTU1::SRV1-1-6-1:D;
l Response Message
NE 2008-01-03 09:18:24 M D COMPLD
"SRV1-1-6-1::AUTOADAPT=Y,FEC=STDFEC,BEFECSDBER=1E-6,BIP8MODE=POISSON,DEGTH=3064,DE
GTIME=7,SFBER=1E-3,SDBER=1E-6,TIMACT=DISABLE,TIMMODE=OFF,EXPTTISAPI=
\"\",EXPTTIDAPI=\"\",TTISAPI=\"\",TTIDAPI=\"\",TTIOPER=\"\",:OOS-AU,SGEO" ;
Related Commands
A.14.3 ED-<OTUN>
A.14.5 ED-<TCMMOD2>
Edits the attributes of TCM.
Function
This command edits the attributes of the TCM.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-<TCMMOD2>:[<TID>]:<AID>:<CTAG>:::[BIP8MODE=<BIP8MODE>],
[DEGTH=<DEGTH>],[DEGTIME=<DEGTIME>],
[DEGINTERVAL=<DEGINTERVAL>],[SFBER=<SFBER>],[SDBER=<SDBER>],
[TIMACT=<TIMACT>],[TIMMODE=<TIMMODE>],[EXPTTISAPI=<EXPTTISAPI>],
[EXPTTIDAPI=<EXPTTIDAPI>],[TTISAPI=<TTISAPI>],[TTIDAPI=<TTIDAPI>],
[TTIOPER=<TTIOPER>],[SRCEN=<SRCEN>],[SRCMODE=<SRCMODE>],
[SINKEN=<SINKEN>],[SINKMODE=<SINKMODE>],[LCKEN=<LCKEN>],
[NONINTRMON=<NONINTRMON>],[LTCACTEN=<LTCACTEN>]:[<PST>];
Command Parameters
Default
Parameters Description Value
Default
Parameters Description Value
<BIP8MODE> Indicates the BIP8 error detection mode of an OTN. The The default
valid values are as follows: value varies
l POISSON with the
different
l BURST units.
<DEGTH> Indicates the SD threshold for bit errors in BURST mode. ODU1TCM
This parameter is only valid when BIP8MODE is set to i: 6126
BURST. ODU5GTC
The value ranges are as follows: Mi: 12303
l ODU1TCMi: 1-20420 ODU2TCM
i: 24607
l ODU5GTCMi: 1-41012
ODU3TCM
l ODU2TCMi: 1-82025
i: 98847
l ODU3TCMi: 1-329491 ODU0TCM
l ODU0TCMi: 1-10167 i: 1000
<DEGINTERVA Indicates the DEG detection time. Valid values include 1000 ms
L> 10 ms, 100 ms, and 1000 ms.
Default
Parameters Description Value
<SRCEN> Indicates whether the source is enabled. The valid values DISABLE
are as follows:
l ENABLE
l DISABLE
<SRCMODE> Indicates the source mode. The valid values are as TRAN
follows:
l OPER: operational
l TRAN: transparent
<SINKEN> Indicates whether the sink is enabled. The valid values DISABLE
are as follows:
l ENABLE
l DISABLE
Default
Parameters Description Value
<SINKMODE> Indicates the sink mode. The valid values are as follows: TRAN
l OPER: operational
l MON: monitoring
l TRAN: transparent
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Example
l Command
ED-ODU1TCM1::CLNT-1-1-1:C:::LTCACTEN=ENABLE;
l Response Message
NE 2004-01-01 11:37:18 M C COMPLD ;
Related Commands
A.14.6 RTRV-<TCMMOD2>
A.14.6 RTRV-<TCMMOD2>
Retrieves the attributes of the TCM.
Function
This command retrieves the attributes of the TCM.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-<TCMMOD2>:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::BIP8MODE=<BIP8MODE>,DEGTH=<DEGTH>,DEGTIME=<DEGTIME>,DEGINTERVAL=<DEGINT
ERVAL>,SFBER=<SFBER>,SDBER=<SDBER>,TIMACT=<TIMACT>,TIMMODE=<TIMMODE>,EXPTTISAPI=<E
XPTTISAPI>,EXPTTIDAPI=<EXPTTIDAPI>,TTISAPI=<TTISAPI>,TTIDAPI=<TTIDAPI>,TTIOPER=<TT
IOPER>,INCTTISAPI=<INCTTISAPI>,INCTTIDAPI=<INCTTIDAPI>,INCTTIOPER=<INCTTIOPER>,SRC
EN=<SRCEN>,SRCMODE=<SRCMODE>,SINKEN=<SINKEN>,SINKMODE=<SINKMODE>,LCKEN=<LCKEN>,NON
INTRMON=<NONINTRMON>,LTCACTEN=<LTCACTEN>:<PST>,<SST>"<cr><lf>+ ;
Response Parameters
Parameters Description
<DEGTH> Indicates the SD threshold for bit errors in BURST mode. This
parameter is only valid when BIP8MODE is set to BURST.
<DEGTIME> Indicates the DEG detection time expressed in seconds. This parameter
is only valid when BIP8MODE is set to BURST.
The valid value ranges from 1 to 10.
<DEGINTERVAL Indicates the DEG detection time. Valid values include 10 ms, 100 ms,
> and 1000 ms.
Parameters Description
<SRCMODE> Indicates the source mode. The valid values are as follows:
l OPER: operational
l TRAN: transparent
<SINKMODE> Indicates the sink mode. The valid values are as follows:
l OPER: operational
l MON: monitoring
l TRAN: transparent
Parameters Description
<PST> Indicates the status of the primary state qualifier. The valid values are
IS and OOS.
Example
l Command
RTRV-ODU1TCM1::SRV1-1-7-1:C;
l Response Message
NEW-NE 2008-09-03 08:41:25 M C COMPLD
"SRV1-1-7-1::BIP8MODE=POISSON,SFBER=1E-3,SDBER=1E-6,TIMACT=DISABLE,TIMMODE=OFF,EXP
TTISAPI=\"\",EXPTTIDAPI=\"\",TTISAPI=\"\",TTIDAPI=\"\",TTIOPER=\"\",INCTTISAPI=
\" \",INCTTIDAPI=\" \",INCTTIOPER=
\"
\",SRCEN=DISABLE,SRCMODE=TRAN,SINKEN=DISABLE,SINKMODE=TRAN,LCKEN=DISABLE,NONINTRMO
N=DISABLE,LTCACTEN=DISABLE:IS-NR" ;
Related Commands
A.14.5 ED-<TCMMOD2>
A.15.1.1 ENT-IPA
Creates an IPA group.
Function
This command creates an IPA group.
Usage Note
An error message will be returned when an existing IPA group is entered.
Category
IPA
Security
Provisioning
Command Syntax
ENT-IPA:[<TID>]:<DECT>,<OPRT>:<CTAG>:::[BAND=<BAND>]
[,RAMANTID=<RAMANTID>,RAMANBID =<RAMANBID>];
Command Parameters
Default
Parameter Description Value
<BAND> Indicates the band type of a line. The only available value CBAND
for this parameter is CBAND.
<RAMANT Indicates the name of the NE TID in which the Raman unit NA
ID> lies.
The valid value is a string of less than or equal to 20
characters which is composed of letters, digits and hyphens.
The string should begin with a letter and cannot end with a
hyphen.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ENT-IPA::FAC-1-1-1,FAC-1-5-2:C:::BAND=CBAND;
l Response Message
NE 2005-11-02 09:48:24
M C COMPLD
;
Related Commands
A.15.1.2 ED-IPA
A.15.1.4 RTRV-IPA
A.15.1.3 DLT-IPA
A.15.1.2 ED-IPA
Edits an IPA group.
Function
This command edits the control attributes of an IPA group.
Usage Note
None
Category
IPA
Security
Provisioning
Command Syntax
ED-IPA:[<TID>]:<DECT>,<OPRT>:<CTAG>:::[RESTART=<RESTART>]
[,LSROFF=<LSROFF>][,LSRON=<LSRON>][,TESTTM=<TESTTM>]
[,RXLOSTH=<RXLOSTH>][,SAFE=<SAFE>][,RSPULSE=<RSPULSE>]
[,RMNALMFLAG=<RMNALMFLAG>][,ENABLE=<ENABLE>]
[,ROPOPRT=<ROPOPRT>][,RAMANOPRT=<RAMANOPRT>];
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
<RESTART Indicates the restart mode. The valid values are as follows: MAN
> l MAN: restarts the laser switch manually.
l AUTO: restarts the laser switch automatically.
<TESTTM> Indicates the time the laser switch is held on when the test 80
mode is active..
Range: 80-1000 (units in seconds).
<RXLOSTH The card detects the input optical power of the Raman card. -30.0
> If the optical power is less than the <RXLOSTH>, a LOS
event is reported to the SCC card. The SCC card determines
whether to enable the IPA function.
Range: -35.0 to -14.0 (unit is 1.0 dBm).
NOTE
After the detection card is configured with a Raman card, the LOS
threshold changes. The LOS threshold with a single wavelength is
different from one with multiple wavelengths. Hence, the LOS
threshold should be set according to the actual situation of the
network.
<SAFE> Uses the safe-level power when users open the laser switch. N
The valid values are Y and N.
Sets the security control mode of the IPA. The IPA security
switch is set to meet the requirements for long-distance
networking. Do not restrain the output optical power to a
very low value.
l When the security control switch is shut down, it
indicates that the IPA is restarted, and all the optical
power detection cards are enabled.
l When the security control switch is open, it indicates
that the IPA is restarted, and the optical power is
restrained to less than 10 dBm.
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-IPA::FAC-1-1-1,FAC-1-2-2:C:::RESTART=AUTO,LSROFF=100,LSRON=40,SAFE=Y;
l Response Message
NE 2005-11-02 09:48:24
M C COMPLD
;
Related Commands
A.15.1.1 ENT-IPA
A.15.1.4 RTRV-IPA
A.15.1.3 DLT-IPA
A.15.1.3 DLT-IPA
Deletes an IPA group.
Function
This command deletes an IPA group.
Usage Note
This command deletes all information about an IPA group including the ASTDECT.
When the communication between subracks fails and the IPA group has Raman parameters that
belong to another rack, this command does not delete the IPA parameters and returns a
communication failure.
Category
IPA
Security
Provisioning
Command Syntax
DLT-IPA:[<TID>]:<DECT>,<OPRT>:<CTAG>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-IPA::FAC-1-1-1,FAC-1-2-2:C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.1.2 ED-IPA
A.15.1.4 RTRV-IPA
A.15.1.1 ENT-IPA
A.15.1.4 RTRV-IPA
Retrieves an IPA group.
Function
This command retrieves the control attributes of an IPA group.
Usage Note
If ALL is input for this parameter, all the IPA groups will be retrieved. If only DECT or OPRT
are entered, then this command will retrieve the related IPA group.
Category
IPA
Security
Retrieve
Command Syntax
RTRV-IPA:[<TID>]:[<DECT>,<OPRT>]:<CTAG>;
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
(^^^"<DECT>,<OPRT>::BAND=<BAND>[,RAMANTID=<RAMANTID>]
[,RAMANBID=<RAMANBID>],RESTART=<RESTART>,LSROFF=<LSROFF>,LSRON=<LSRON>,TESTTM=<TES
TTM>,RXLOSTH=<RXLOSTH>,SAFE=<SAFE>,RSPULSE=<RSPULSE>
[,RMNALMFLAG=<RMNALMFLAG>],ENABLE=<ENABLE>,STATE=<STATE>")
;
Response Parameters
Parameter Description
<RAMANTID> Indicates the name of the NE where the Raman unit is located. The
<RAMANTID> is string of less than or equal to 20 characters which
is composed of letters, digits and hyphens. The string should begin
with a letter and cannot end with a hyphen.
NOTE
This parameter is not displayed if the IPA pair is not configured with
<RAMANTID>.
<RAMANBID> Indicates the slot where the Raman unit is located. The valid format
is SLOT-<SHELF ID>-<SLOT ID>.
NOTE
This parameter is not displayed if the IPA pair is not configured with
<RAMANBID>.
Parameter Description
<TESTTM> Indicates the time the laser switch is held on when the test mode is
active.
Range: 80-100 (units in seconds).
The default value is 80 seconds.
<RXLOSTH> The card detects the input optical power of the Raman card. If the
optical power is less than the <RXLOSTH>, a LOS event is reported
to the SCC card. The SCC card determines whether to enable the IPA
function.
Range: -35.0 to -14.0 (unit is 1.0 dB). The default value is -30.0.
NOTE
After the detection card is configured with a Raman card, the LOS threshold
changes. The LOS threshold with a single wavelength is different from one
with multiple wavelengths. Hence, the LOS threshold should be set according
to the actual situation of the network.
<SAFE> Indicates whether a safe level power is used when a laser switch is
open.
The valid values are Y and N.
The default value is N.
Parameter Description
<RSPULSE> Indicates whether a restart pulse is used when the timer or a command
requires opening the laser switch.
The valid values are Y and N.
The default value is Y.
NOTE
The RSPULSE value must be Y if the IPA pair does not set the OSC auxiliary
detection equipment.
<RMNALMFLAG> Indicates whether the detecting function of the IPA pair is enabled.
The valid values are Y or N. The default value is N.
NOTE
When <RMNALMFLAG> is set to Y, alarms of the Raman card are set as
trigger conditions for starting IPA. The Raman card acts like a detection card.
<STATE> Indicates the current state of an IPA group. The valid values are as
follows:
l END: A detection period has been completed.
l LSRON: The laser switch is open.
l LSROFF: The laser switch is closed.
l ALM: Alarms are present.
l RESTART: The IPA restarts.
l SAFEDECT: It indicates to perform detection in security mode.
l BEGIN: It indicates to wait to begin a new IPA control period.
Example
l Command
RTRV-IPA:::C;
l Response Message
NE 2006-05-08 16:44:52
M C COMPLD
"FAC-1-11-1,FAC-1-3-4::BAND=CBAND,RESTART=AUTO,LSROFF=100,LSRON=2.00,TESTTM=80,SAF
E=N,RSPULSE=Y,ENABLE=Y,STATE=BEGIN"
"FAC-1-3-1,FAC-1-11-4::BAND=CBAND,RESTART=AUTO,LSROFF=100,LSRON=2.00,TESTTM=80,SAF
E=N,RSPULSE=Y,ENABLE=Y,STATE=BEGIN" ;
Related Commands
A.15.1.2 ED-IPA
A.15.1.1 ENT-IPA
A.15.1.3 DLT-IPA
A.15.1.5 ED-IPA-WDM
Edits the IPA attributes of a port.
Function
This command is used to edit the IPA attributes of a port.
Usage Note
None
Category
IPA
Security
Provisioning
Command Syntax
ED-IPA-WDM:[<TID>]:<AID>:<CTAG>:::[ENABLE=<ENABLE>]
[,RESTART=<RESTART>][,LSROFF=<LSROFF>];
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-IPA-WDM::FAC-2-1-1:C100:::ENABLE=Y,RESTART=AUTO,LSROFF=100;
l Response Message
NE 05-01-01 00:00:00
M C100 COMPLD
;
Related Commands
A.15.1.7 RTRV-IPA-WDM
A.15.1.6 OPR-IPA-WDM
A.15.1.6 OPR-IPA-WDM
Manually restarts port IPA.
Function
This command is used to manually restart port IPA.
Usage Note
None
Category
IPA
Security
Provisioning
Command Syntax
OPR-IPA-WDM:[<TID>]:<AID>:<CTAG>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
OPR-IPA-WDM::FAC-2-1-1:C100;
l Response Message
NE 05-01-01 00:00:00
M C100 COMPLD
;
Related Commands
A.15.1.5 ED-IPA-WDM
A.15.1.7 RTRV-IPA-WDM
A.15.1.7 RTRV-IPA-WDM
Retrieves the IPA attributes of a port.
Function
This command is used to retrieve the IPA attributes of a port.
Usage Note
None
Category
IPA
Security
Retrieve
Command Syntax
RTRV-IPA-WDM:[<TID>]:<AID>:<CTAG>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-IPA-WDM::FAC-2-1-1:C100;
l Response Message
NE 05-01-01 00:00:00
M C100 COMPLD
"FAC-2-1-1::ENABLE=Y,RESTART=AUTO,LSROFF=100";
Related Commands
A.15.1.5 ED-IPA-WDM
A.15.1.6 OPR-IPA-WDM
A.15.1.8 OPR-IPA
Operates an IPA group.
Function
This command is used to operate an IPA group.
If RESTART is set to AUTO, IPA automatically enables the laser periodically. When RESTART
is set to MAN, use this command to enable the laser manually.
This command can be used only when <RESTART> is set to MAN, <ENABLE> is set to Y,
and <STATE> is set to LSROFF.
Usage Note
None
Category
IPA
Security
Provisioning
Command Syntax
OPR-IPA:[<TID>]:<DECT>,<OPRT>:<CTAG>::<FLAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
OPR-IPA::FAC-1-1-1,FAC-1-2-2:C::TEST;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.1.2 ED-IPA
A.15.1.9 ENT-IPA-ASTDECT
Creates an auxiliary detection unit for an IPA group.
Function
This command creates an auxiliary detection unit for an IPA group.
Usage Note
One command creates only one ASTDECT unit. The maximum number of ASTDECT units is
4.
Category
IPA
Security
Provisioning
Command Syntax
ENT-IPA-ASTDECT:[<TID>]:<DECT>,<OPRT>:<CTAG>::<ASTDECT>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ENT-IPA-ASTDECT::FAC-1-4-1,FAC-1-1-2:C::FAC-1-2-1;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.1.11 RTRV-IPA-ASTDECT
A.15.1.10 DLT-IPA-ASTDECT
A.15.1.10 DLT-IPA-ASTDECT
Deletes an auxiliary detection unit of an IPA group.
Function
This command deletes an auxiliary detection unit for an IPA group.
Usage Note
One command deletes only one ASTDECT unit.
Category
IPA
Security
Provisioning
Command Syntax
DLT-IPA-ASTDECT:[<TID>]:<DECT>,<OPRT>:<CTAG>::<ASTDECT>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
DLT-IPA-ASTDECT::FAC-1-1-1,FAC-1-2-2:C::FAC-1-6-1;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.1.11 RTRV-IPA-ASTDECT
A.15.1.9 ENT-IPA-ASTDECT
A.15.1.11 RTRV-IPA-ASTDECT
Retrieves all auxiliary detection units of an IPA group.
Function
This command retrieves all auxiliary detection units of an IPA group.
Usage Note
None
Category
IPA
Security
Retrieve
Command Syntax
RTRV-IPA-ASTDECT:[<TID>]:<DECT>,<OPRT>:<CTAG>;
Command Parameters
Paramete Default
r Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
Response Parameters
Parameter Description
Example
l Command
RTRV-IPA-ASTDECT::FAC-1-4-1,FAC-1-1-2:C;
l Response Message
NE 2008-11-22 14:18:50
M C COMPLD
"FAC-1-4-1,FAC-1-1-2::FAC-1-2-1"
;
Related Commands
A.15.1.9 ENT-IPA-ASTDECT
A.15.1.10 DLT-IPA-ASTDECT
A.15.1.12 REPT^EVT^IPA
Reports an IPA group event.
Function
This autonomous message is generated by an NE to inform the OS or maintenance personnel
about IPA information.
Usage Note
None
Category
IPA
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr> <lf> <lf>^^^<rsphdr> <cr> <lf>
A^^<atag>^REPT^EVT^IPA <cr> <lf>
(^^^"[<DECT>,<OPRT>]:<EVENTID>" <cr> <lf>)+
;
Response Parameters
Parameter Description
Example
l Command
None
l Response Message
NE 2004-01-01 11:37:18
A 1 REPT EVT IPA
"FAC-1-1-2,FAC-1-2-2:START"
;
Related Commands
None
A.15.2.1 ENT-APE
Creates an APE group.
Function
This command creates an APE group.
Usage Note
None
Category
APE
Security
Provisioning
Command Syntax
ENT-APE:[<TID>]:<AID>:<CTAG>:::[BAND=<BAND>][,ODDNE=<ODDNE>]
[,ODDBD=<ODDBD>][,EVENNE=<EVENNE>][,EVENBD=<EVENBD>];
Command Parameters
Default
Parameter Description Value
<AID> Indicates the AID of the analyzer equipment, for example, the NA
port of an MCA.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT
ID>.
The valid value is provided in A.32.2.2 APE.
<ODDNE> Indicates the TID of the odd wave adjustment equipment. NULL
When the <ODDNE> is NULL, it indicates that the odd wave
adjustment equipment does not exit.
<EVENNE> Indicates the TID of the even wave adjustment equipment. NULL
When the <EVENNE> is NULL, it indicates that the even
wave adjustment equipment does not exit.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ENT-
APE::FAC-1-2-1:C:::BAND=CBAND,ODDNE=ShenZhen1,ODDBD=SLOT-1-2,EVENNE=ShenZhen2,EVEN
BD=SLOT-1-9;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.2.2 ED-APE
A.15.2.5 RTRV-APE
A.15.2.3 DLT-APE
A.15.2.4 OPR-APE
A.15.2.2 ED-APE
Edits an APE group.
Function
This command edits the control attributes of an APE group.
Usage Note
None
Category
APE
Security
Provisioning
Command Syntax
ED-APE:[<TID>]:<AID>:<CTAG>:::[AUTOADJ=<AUTOADJ>][,TH=<TH>];
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-APE::FAC-1-2-1:C:::AUTOADJ=Y,TH=2.0;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.2.5 RTRV-APE
A.15.2.3 DLT-APE
A.15.2.4 OPR-APE
A.15.2.1 ENT-APE
A.15.2.3 DLT-APE
Deletes an APE group.
Function
This command deletes an APE group.
Usage Note
None
Category
APE
Security
Provisioning
Command Syntax
DLT-APE:[<TID>]:<AID>:<CTAG>
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-APE::FAC-1-2-1:C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.2.2 ED-APE
A.15.2.5 RTRV-APE
A.15.2.4 OPR-APE
A.15.2.1 ENT-APE
A.15.2.4 OPR-APE
Operates an APE group.
Function
This command starts/stops the adjustment of an APE group.
Usage Note
None
Category
APE
Security
Maintenance
Command Syntax
OPR-APE:[<TID>]:<AID>:<CTAG>::<OPRT>
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>
;
Example
l Command
OPR-APE::FAC-1-2-1:C::START;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.2.2 ED-APE
A.15.2.5 RTRV-APE
A.15.2.3 DLT-APE
A.15.2.1 ENT-APE
A.15.2.5 RTRV-APE
Retrieves an APE group.
Function
This command retrieves the control attributes of an APE group.
Usage Note
None
Category
APE
Security
Retrieve
Command Syntax
RTRV-APE:[<TID>]:[<AID>]:<CTAG>
Command Parameters
Default
Parameter Description Value
<AID> Indicates the AID of an analyzer port, for example, the port NA
of an MCA.
The valid format is FAC-<SHELF ID>-<SLOT ID>-
<PORT ID>
When nothing is entered for this parameter, it indicates all
APE groups are retrieved.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
(^^^"<AID>::BAND=<BAND>[,ODDNE=<ODD_NEID>][,ODDBD=<ODDBD>][,EVENNE=<EVENNE>]
[,EVENBD=<EVENBD>],AUTOADJ=<AUTOADJ>,TH=<TH>,STATE=<STATE>"<cr><lf>)+
Response Parameters
Parameter Description
<AID> Indicates the AID of an analyzer port, for example, the port of an
MCA.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT ID>.
Parameter Description
<STATE> Indicates the state of an APE pair. The valid values are as follows:
l NORMAL: The pair is in the normal state.
l ABNORMAL: The pair detects that the waves are in a state of un-
equilibrium.
l ADJUSTING: The APE pair is adjusting the waves for pre-
equilibrium.
l PREV_ADJUSTING: The upstream pair is adjusting the waves
for pre-equilibrium.
Example
l Command
RTRV-APE:::C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
"FAC-1-12-1::BAND=CBAND,ODDNE=SHENZHEN1,ODDBD=SLOT-2,EVENNE=SHENZHEN2,EVENBD=SLOT-
9,AUTOADJ=Y,TH=1.5,STATE=NORMAL"
"FAC-1-12-4::BAND=CBAND,ODDNE=SHENZHEN10,ODDBD=SLOT-3,EVENNE=SHENZHEN20,EVENBD=SLO
T-10,AUTOADJ=Y,TH=1.3,STATE=NORMAL"
;
Related Commands
A.15.2.2 ED-APE
A.15.2.3 DLT-APE
A.15.2.4 OPR-APE
A.15.2.1 ENT-APE
A.15.2.6 ED-APE-WCH
Edits a channel of an APE group.
Function
This command edits the attributes of a channel of an APE group.
Usage Note
None
Category
APE
Security
Provisioning
Command Syntax
ED-APE-WCH:[<TID>]:<AID>:<CTAG>:::[BANDTYPE=<BANDTYPE>]
[,STDBIAS=<STDBIAS>][,ENABLE=<ENABLE>];
Command Parameters
Default
Parameter Description Value
<AID> Indicates the AID of an analyzer port, for example, the port NA
of an MCA.
The valid format is FAC-<SHELF ID>-<SLOT ID>-
<PORT ID>-<CHANNEL ID>.
<BANDTYP Indicates the type of wave band. The only available value CBAND
E> for this parameter is CBAND.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-APE-WCH::FAC-1-2-1-1:C:::BANDTYPE=CBAND,STDBIAS=1.0,ENABLE=Y;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.2.7 RTRV-APE-WCH
A.15.2.7 RTRV-APE-WCH
Retrieves the wavelengths of an APE group.
Function
This command retrieves the attributes of each channel.
Usage Note
None
Category
APE
Security
Retrieve
Command Syntax
RTRV-APE-WCH:[<TID>]:<AID>:<CTAG>:::[BANDTYPE=<BANDTYPE>];
Command Parameters
Default
Parameter Description Value
<AID> Indicates the AID of an analyzer port, for example, the port NA
of an MCA.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT
ID>-<CHANNEL ID>.
Support the "&" and "&&" symbol.
<BANDTYP Indicates the type of wave band. The only available value for CBAND
E> this parameter is CBAND.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
(
^^^"<AID>::BANDTYPE=BANDTYPE,ENABLE=<ENABLE>,STDBIAS=<STDBIAS>,FACTBIAS=<FACTBIAS>
" <cr><lf>)+
;
Response Parameters
Parameter Description
<AID> Indicates the AID of a channel. This parameter supports the "&" and
"&&" symbols.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT ID>-
<CHANNEL ID>. The <CHANNEL ID> supports ALL.
<BANDTYPE> Indicates the type of wave band. The default and only available value
for this parameter is CBAND.
Example
l Command
RTRV-APE-WCH::fac-1-11-4-80&FAC-1-11-4-72:C;
l Response Message
NE 1990-01-01 11:59:46
M C COMPLD
"FAC-1-11-4-72::BAND=CBAND,ENABLE=Y,STDBIAS=12.7,FACTBIAS=12.7"
"FAC-1-11-4-80::BAND=CBAND,ENABLE=Y,STDBIAS=-0.8,FACTBIAS=-1.0"
;
Related Commands
A.15.2.6 ED-APE-WCH
A.15.2.8 REPT^EVT^APE
Reports an APE group event.
Function
This autonomous message is generated by an NE to inform the OS or maintenance personnel
about the APE information.
Usage Note
None
Category
APE
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr> <lf> <lf>^^^<rsphdr> <cr> <lf>
A^^<atag>^REPT^EVT^APE <cr> <lf>
(^^^"<AID>:<EVENTID>:[WAVE=<WAVE>][,REASON=<REASON>][,NE=<NE>][,EQPT=<EQPT>]
[,BDERR=<BDERR>]" <cr> <lf>)+
;
Response Parameters
Parameter Description
<AID> Indicates the AID of an analyzer port, for example, the port of an MCA.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT ID>.
<EVENTID> Indicates the event type. The valid values are as follows:
l UNEQ: The channel power is unequal.
l SUCC: The adjustment was successful.
l FAIL: The adjustment failed.
l ADDWAVE: Wavelengths were added.
l DROPWAVE: Wavelengths were dropped.
Parameter Description
<REASON> Indicates why the adjustment failed. This parameter is valid when
<EVENTID> is set to FAIL.
The valid values are as follows:
l UNKNOWN: Unknown failure
l STOP_MANUALLY: Adjustment was stopped by the user.
l NO_REACH_EQ: Equilibrium cannot be reached after adjustment.
l COMM_FAIL: The communication failed.
l CARD_UNINSTALL: The unit is not installed.
l CARD_TYPE_ERR: It indicates the unit type error.
l CARD_OFFLINE: The unit is offline.
l VMUX_CARRY_ERR: The VMUX attenuation adjusting failed.
l BOARD_RESP_ERR: The unit responded with an error.
l BOARD_SYS_ERR: It indicates a system error.
l ADJNE_NOT_FOUND: The adjustment subrack was not found.
l DROP_WAVE: Wavelength was dropped.
<NE> Indicates the TID of a failed NE. It is a string with no more than 20 bytes.
This parameter is valid when <EVENTID> is set to FAIL.
<EQPT> Indicates the AID of the failed equipment. It indicates which equipment
reports an error. The valid format is SLOT-<SHELF ID>-<SLOT ID>.
This parameter is valid when <EVENTID> is set to FAIL.
<BDERR> Indicates the error code responded from a unit, if the failure is caused by
unit operation failure.
This parameter is valid when <EVENTID> is set to FAIL.
The valid values are as follows:
l CMD-INVALID: The parameters in the command are incorrect.
l PARA-ERR: The parameter length is incorrect.
l OPR-FAIL: Execution of the command failed.
l NOT-SUPPORTED: This command is not supported.
l DISCARDED: The command is discarded.
l BUSY: The command is being executed. The result cannot be returned
yet.
l NOT-READY: The card is not prepared and the command cannot be
executed yet.
l OVERTIME: Command execution times out.
Example
l Command
None
l Response Message
NE 2004-01-01 11:37:18
A 1 RETP EVT APE
"FAC-1-12-3:UNEQ:WAVE=ADDWAVE,"
;
Related Commands
None
A.15.3.1 ENT-ALC-NODE
Creates an ALC node.
Function
This command creates an ALC node on an NE.
Usage Note
None
Category
ALC
Security
Provisioning
Command Syntax
ENT-ALC-NODE:[<TID>]:<CHAIN>:<CTAG>:::[REFER=<REFER>]
[,PREVNE=<PREVNE>][,NEXTNE=<NEXTNE>][,DETECTOR=<DETECTOR>]
[,VOA=<VOA>][,AUTOFLAG=<AUTOFLAG>][,TH=<THRESHOLD>]
[,DEGTH=<DEGTH>][,BIAS=<BIAS>];
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
<REFER> Indicates the AID of the reference device on the node. NULL
The valid format is FAC-<SHELF ID>-<SLOT ID>-
<PORT ID>.
NULL indicates that the node does not have a reference
device.
Refer to A.32.2.1 ALC for the valid values of <REFER>
for specific units.
<DETECTO Indicates the AID of the detection device on the node. NULL
R> The valid format is FAC-<SHELF ID>-<SLOT ID>-
<PORT ID>.
NULL indicates that the node does not have a detection
device.
Refer to A.32.2.1 ALC for the valid values of
<DETECTOR> for specific units.
<VOA> Indicates the AID of the VOA (variable optical attenuator) NULL
device on the node.
The valid format is FAC-<SHELF ID>-<SLOT ID>-
<PORT ID>.
NULL indicates that the node does not have a VOA device.
Refer to A.32.2.1 ALC for the valid values of <VOA> for
specific units.
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ENT-ALC-
NODE::ALC-1:C:::PREVNE=NE-01,NEXTNE=NE-03,DETECTOR=FAC-1-3-4,VOA=FAC-1-1-1,TH=1.5;
l Response Message
NE 05-01-01 00:00:00
M C COMPLD
;
Related Commands
A.15.3.4 RTRV-ALC-NODE
A.15.3.2 ED-ALC-NODE
A.15.3.3 DLT-ALC-NODE
A.15.3.2 ED-ALC-NODE
Edits the parameters of an ALC node.
Function
This command edits the parameters of an ALC node on an NE.
Usage Note
None
Category
ALC
Security
Provisioning
Command Syntax
ED-ALC-NODE:[<TID>]:<CHAIN>:<CTAG>:::[AUTOFLAG=<AUTOFLAG>]
[,TH=<THRESHOLD>][,DEGTH=<DEGTH>][,BIAS=<BIAS>];
Command Parameters
Default
Parameter Description Value
Default
Parameter Description Value
<DEGTH> Indicates the threshold for reporting a line degradation alarm. 2.0
When the line degrades to a certain degree so that the
difference between the actual attenuation and the reference
attenuation exceeds the threshold, an alarm indicating that
the line degradation exceeds expectation is reported.
Range: 0.5 to 15 (unit is 1.0 dB). The default value is 2.0.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-ALC-NODE::ALC-1:C:::TH=1.0,BIAS=-5;
l Response Message
NE 2005-01-01 00:00:00
M C COMPLD
;
Related Commands
A.15.3.3 DLT-ALC-NODE
A.15.3.1 ENT-ALC-NODE
A.15.3.4 RTRV-ALC-NODE
A.15.3.3 DLT-ALC-NODE
Deletes an ALC node.
Function
This command deletes an ALC node on an NE.
Usage Note
None
Category
ALC
Security
Provisioning
Command Syntax
DLT-ALC-NODE:[<TID>]:<CHAIN>:<CTAG>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
DLT-ALC-NODE::ALC-1:C;
l Response Message
NE 05-01-01 00:00:00
M C COMPLD
;
Related Commands
A.15.3.2 ED-ALC-NODE
A.15.3.1 ENT-ALC-NODE
A.15.3.4 RTRV-ALC-NODE
A.15.3.4 RTRV-ALC-NODE
Retrieves the information of an ALC node.
Function
This command retrieves the information of an ALC node on an NE.
Usage Note
None
Category
ALC
Security
Retrieve
Command Syntax
RTRV-ALC-NODE:[<TID>]:[<CHAIN>]:<CTAG>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> (^^^"<CHAIN>:
[IDX=<NODE>],REFER=<REFER>,PREVNE=<PREVNE>,NEXTNE=<NEXTNE>,DETECTOR=<DETECTOR>,VOA
=<VOA>[,AUTOFLAG=<AUTOFLAG">],TH=<THRESHOLD>,DEGTH=<DEGTH>,BIAS=<BIAS>
[,LINEATTEN=<LINEATTEN>][,REFATTEN=<REFATTEN>][,GAIN=<GAIN>][,REFGAIN=<REFGAIN>]
[,NODEATTEN=<NODEATTEN>][,ACCBIAS=<ACCBIAS>],STATE=<STATE>"<cr><If>)+ ;
Response Parameters
Parameter Description
Parameter Description
<THRESHOLD The power is considered abnormal when the difference between the actual
> power and the reference power exceeds this value.
Range: 0.5 to 3.0 (unit is 1.0 dB).
<DEGTH> Indicates the threshold for reporting a line degradation alarm. When the
line degrades to a certain degree so that the difference between the actual
attenuation and the reference attenuation exceeds the threshold, an alarm
indicating that the line degradation exceeds expectation is reported.
Range: 0.5 to 15 (unit is 1.0 dB). The default value is 2.0.
Parameter Description
<REFATTEN> Indicates the reference line attenuation in the transmission. This parameter
serves as a nominal attenuation value for monitoring the line degradation.
An alarm is reported when the difference between the actual attenuation
and the value of this parameter exceeds the value of <DEGTH>. The value
of this parameter can be changed by using the OPR-ALC-NODE
command. The attenuation does not include the attenuation of the
attenuators on the ALC link but the attenuation of other attenuators that
are not configured on the ALC link.
The valid format is unsigned float (unit is 1.0 dB).
The parameter is not displayed is the <REFATTEN> value is invalid.
<GAIN> Indicates the gain of the local node <DETECTOR>. The valid format is
unsigned float (unit is 1.0 dB).
This parameter is not displayed is the <GAIN> value is invalid.
<REFGAIN> Indicates the reference gain for an amplifier in the ALC function. When
the ALC function is used for adjusting the optical power, the attenuation
or gain is adjusted with the presumption that there is minimal deviation of
the amplifier gain from <REFGAIN>.
The valid format is unsigned float (unit is 1.0 dB).
This parameter is not displayed if the <REFGAIN> value is invalid.
<NODEATTE Indicates the current attenuation of the VOA unit of the local node. The
N> valid format is unsigned float (unit is 1.0 dB).
The parameter is not displayed if the <NODEATTEN> value is invalid.
<ACCBIAS> Indicates the accumulated optical power deviation of the local node. The
valid format is signed float (unit is 1.0 dB).
<ACCBIAS> of the reference node is 0.
This parameter is not displayed if the <ACCBIAS> value is invalid.
Example
l Command
RTRV-ALC-NODE:::C;
l Response Message
NE 05-01-01 00:00:00 M C COMPLD
"ALC-1:IDX=NO-1,REFER=FAC-1-3-4,PERVID=NULL,NEXTNE=NE-02,DETECTOR=NULL,VOA=NULL,AU
TOFLAG=N,TH=2.5,DEGTH=2.0,BIAS=0.5,ACCBIAS=0,STATE=IDLE" ;
"ALC-2:IDX=NO-5,REFER=NULL,PREVNE=NE-04,NEXTNE=NE-06,DETECTOR=FAC-1-9-2,VOA=FAC-1-
1-1,TH=2.0,DEGTH=2.0,BIAS=1.5,LINEATTEN=19.2,REFATTEN=15.0,GAIN=23.0,REFGAIN=23.0,
NODEATTEN=3.2,ACCBIAS=0.3,STATE=IDLE"; ;
Related Commands
A.15.3.3 DLT-ALC-NODE
A.15.3.2 ED-ALC-NODE
A.15.3.1 ENT-ALC-NODE
A.15.3.7 OPR-ALC-NODE
A.15.3.5 OPR-ALC-CHAIN
Operates an ALC chain.
Function
This command manually starts or stops the adjustment process on the chain.
This operation only be carried out on the first node of the ALC chain.
Usage Note
None
Category
ALC
Security
Maintenance
Command Syntax
OPR-ALC-CHAIN:[<TID>]:<CHAIN>:<CTAG>::<OPRT>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
OPR-ALC-CHAIN::ALC-1:C::START;
l Response Message
NE 05-01-01 00:00:00
M C COMPLD
;
Related Commands
A.15.3.6 RTRV-ALC-CHAIN
A.15.3.6 RTRV-ALC-CHAIN
Retrieves an ALC chain.
Function
This command retrieves the information of all ALC nodes on a chain.
Usage Note
None
Category
ALC
Security
Retrieve
Command Syntax
RTRV-ALC-CHAIN:[<TID>]:<CHAIN>:<CTAG>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
(^^^"
<CHAIN>:[IDX=<NODE>][,NENAME=<NENAME>][,LINEATTEN=<LINEATTEN>][,GAIN=<GAIN>]
[,NODEATTEN=<NODEATTE>][,ACCBIAS=<ACCBIAS>][,STATE=<NODESTATE>][,COMM=<COMM>]
[,CHAINSTATE=< CHAINSTATE>]
" <cr><If>)
;
Response Parameters
Parameter Description
<IDX> Indicates the statistic result of node index. The valid format is NO-
<N>.
This parameter is not displayed if the node response is not received
or the node does not exist.
Parameter Description
<NODEATTEN> Indicates the current attenuation of the VOA unit of the local node.
The valid format is unsigned float (unit is 1.0 dB). NODEATTEN
equals zero if the node does not have a VOA device.
This parameter is not displayed if the node response is not received
or the node does not exist.
<ACCBIAS> Indicates the accumulated optical power deviation of the local node.
The valid format is signed float (unit is 1.0 dB).
This parameter is not displayed if the node response is not received
or the node does not exist.
Parameter Description
<CHAINSTATE> Indicates the current state of a chain, which is displayed on only the
first node.
The valid values are as follows:
l IDLE: It indicates that the chain is idle, and it is not abnormally
occupied on any node.
l INVALID: It indicates that the chain is invalid.
l ADJUSTING: It indicates that the chain started the adjustment,
but the adjustment is not complete.
l ABNR: It indicates that some nodes have anomalies on the chain,
but the adjustment is not started.
l COMMFAIL: The communication is abnormally occupied, and
the chain state is unclear.
This parameter is not displayed if the node response is not received
or the node does not exist.
Example
l Command
RTRV-ALC-CHAIN::ALC-1:C;
l Response Message
NE 05-01-01 00:00:00
M C COMPLD
"
ALC-1:IDX=NO-1,NENAME=NE-01,LINEATTEN=0,GAIN=21.0,NODEATTEN=0,ACCBIAS=0.0,STATE=ID
LE,COMM=SUCCESS,CHAINSTATE=COMMFAIL;
ALC-1:IDX=NO-2,NENAME=NE-02,LINEATTEN=18.0,GAIN=20.2,NODEATTEN=2.0,ACCBIAS=0.1,STA
TE=IDLE,COMM= SUCCESS;
ALC-1:IDX=NO-3,NENAME=NE-03,LINEATTEN=20.0,GAIN=22.0,NODEATTEN=1.2,ACCBIAS=0.2,STA
TE=IDLE,COMM= SUCCESS;
ALC-1:IDX=NO-4,NENAME=NE-04,LINEATTEN=19.8,GAIN=23.0,NODEATTEN=3.1,ACCBIAS=0.5,STA
TE=IDLE,COMM= SUCCESS;
ALC-1:NENAME=NE-05,STATE=NOEXIST,COMM= SUCCESS; "
;
Related Commands
A.15.3.5 OPR-ALC-CHAIN
A.15.3.7 OPR-ALC-NODE
Samples the ALC reference value.
Function
This command collects the current attenuation of the optical power and gain of the amplifier on
the line as reference values REFATTEN and REFGAIN. The value REFATTEN is used for
determining whether an alarm is generated and REFGAIN is used as a reference value in priority
for ALC adjustment.
Usage Note
None
Category
ALC
Security
Provisioning
Command Syntax
OPR-ALC-NODE:[<TID>]:<CHAIN>:<CTAG>::<OPRT>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ;
Response Parameters
None
Example
l Command
OPR-ALC-NODE::ALC-1:C::SAMP;
l Response Message
NE 05-01-01 00:00:00 M C COMPLD ;
Related Commands
A.15.3.4 RTRV-ALC-NODE
A.15.3.8 INIT-ALC-LOG
Clears the records of an ALC event.
Function
This command clears the records of an ALC event.
Usage Note
None
Category
ALC
Security
Maintenance
Command Syntax
INIT-ALC-LOG:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
INIT-ALC-LOG:::C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.15.3.9 RTRV-ALC-LOG
A.15.3.9 RTRV-ALC-LOG
Queries the records of an ALC event.
Function
This command queries the records of an ALC event.
Usage Note
None
Category
ALC
Security
Retrieve
Command Syntax
RTRV-ALC-LOG:[<TID>]:[CHAIN]:<CTAG>;
Command Parameters
Default
Parameter Description Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
(^^^"<CHAIN>,<EVENT>,<EVTINFO>:DATA=<DATE>,TIME=<TIME>""<cr><lf>)+
;
Response Parameters
Parameter Description
Parameter Description
<EVENT> Indicates the event identifier. Possible events are listed as follows:
l ABSTRACT: The abstract that contains all the basic information
about the chain adjustment.
l NODE-ABNR: The node state is abnormal.
l NODE-RESU: The node state restored to normal.
l NODE-FAIL: The node adjustment failed.
l NODE-SUCC: The node adjustment succeeded.
l NODE-ACK: It indicates the node adjustment response event.
l CHAIN-START: The chain adjustment process started.
l CHAIN-STOP: The chain adjustment process stopped.
l CHAIN-FINISH: The chain adjustment process is complete.
l CHAIN-FAIL: The chain state is unknown.
l CHAIN-ABNR: The chain state is abnormal.
l CHAIN-RESU: The chain or node state was restored.
Example
l Command
RTRV-ALC-LOG:::C;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
"ALC-1,NODE-FAIL,CHAIN-TIME-OUT,OUTTIME=10: DATA=2006-02-27,TIME=16-47-45"
"ALC-1,CHAIN-FAIL,IDX=NO-1,NENAME=HEXING: DATA=2006-02-27,TIME=16-47-45"
;
Related Commands
A.15.3.8 INIT-ALC-LOG
A.15.3.10 REPT^EVT^ALC
Reports an ALC event.
Function
This autonomous message is generated by an NE to inform maintenance personnel of the ALC
information.
Usage Note
None
Category
ALC
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr> <lf> <lf>^^^<rsphdr> <cr> <lf>
A^^<atag>^REPT^EVT^ALC <cr> <lf>
^^^"< CHAIN>::EVENT=<EVTTYPE>,<EXTPARA>" <cr> <lf>
;
Response Parameters
Parameter Description
Parameter Description
<EVTTYPE> Indicates the ALC event type. Possible ALC events are as follows:
l ABSTRACT: The abstract that contains all the basic information
about the chain adjustment.
l NODE-ABNR: The state of the current node is abnormal.
l NODE-FAIL: The node adjustment failed.
l NODE-SUCC: The node adjustment succeeded.
l NODE-RESU: The node state restored to normal.
l NODE-ACK: It indicates the chain node adjustment response
event. Only the first chain node can report this event.
l CHAIN-START: The chain adjustment started.
l CHAIN-STOP: The chain adjustment stopped.
l CHAIN-FINISH: The chain adjustment is complete.
l CHAIN-FAIL: The communication is abnormal in the current
chain. The current chain state is unknown.
l CHAIN-ABNR: The current chain state is abnormal. Some node
states are abnormal.
l CHAIN-RESU: The current chain communication or state was
restored.
ABSTRACT ABNRIDX Indicates the index of the first chain node if its state is
abnormal.
NENAME Indicates the NE name of the last chain node if its state
is abnormal. ABNRIDX and NENAME are not
displayed when the chain does not detect an abnormal
node.
NODE-ABNR IDX Indicates the index number of the current node. The
valid format is NO-<N>.
NODE-FAIL REASON Indicates the cause of event possibly. The causes are
listed as follow:
l NODE-STATE-ERR: There is an error in the state
of the current node.
l CARD-RSP-ERR: It indicates an error in the unit
command response.
l DEVICE-ALM-EXIST: A device alarm exists.
l CHAIN-NO-EXIST: The chain does not exist.
l CHAIN-CHAOS: It indicates the chaotic chain
configuration.
l NODE-TIME-OUT: The node adjustment process
timed out.
l NO-PERMIT-ERR: The current node is still
abnormal after the adjustment is complete.
NODE-SUCC NULL Indicates there are not any extended parameters in this
event.
NODE-RESU IDX Indicates the index number of the current node. The
valid format is NO-<N>.
ACCBIAS Indicate the cumulative value of the gain bias of all the
upstream-node amplifiers.
The valid format is signed float (unit is 1.0 dB). The
reference node is not displayed.
CHAIN- NULL Indicates there are not any extended parameters in this
START event.
IDX Indicates the index of the node that requested the chain
adjustment interruption. The valid format is NO-<N>.
NENAME Indicates the index of the node that requested the chain
adjustment interruption.
CHAIN- NULL Indicates there are not any extended parameters in this
FINISH event.
CHAIN-FAIL IDX Indicates the index of the node that detected the chain
communication was abnormal. The valid format is
NO-<N>.
Example
l Command
None
l Response Message
NE 2004-01-01 11:37:18
A 1 REPT EVT ALC
"ALC-1::CHAIN START"
;
Related Commands
None
A.16.1 ED-MCACHN
Edits the channel monitor attributes of the MCA.
Function
This command edits the channel monitor attributes of the multi-channel spectrum analyzer unit
(MCA), which helps to analyze the optical wavelength, optical power, and OSNR of a specific
channel.
Usage Note
None
Category
MCA
Security
Provisioning
Command Syntax
ED-MCACHN:
[<TID>]:<AID>:<CTAG>:::BANDTYPE=<BANDTYPE>,MONFLAG=<MONFLAG>;
Command Parameters
Parameters Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-MCACHN::FAC-1-1-1-1:C:::BANDTYPE=CBAND,MONFLAG=Y;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.16.2 RTRV-MCACHN
A.16.3 RTRV-MCADATA
A.16.2 RTRV-MCACHN
Retrieves the channel monitor attributes of the MCA.
Function
This command retrieves the channel monitor attributes of the MCA, which helps to analyze the
optical wavelength, optical power, and OSNR of a specific channel.
Usage Note
None
Category
MCA
Security
Retrieve
Command Syntax
RTRV-MCACHN:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::BANDTYPE=<BANDTYPE>,MONFLAG=<MONFLAG>"<cr><lf>
;
Response Parameters
Parameters Description
AID Indicates the MCA channel access identifier. The valid format is
FAC-<SHELF ID>-<SLOT ID>-<PORT ID>-<PATH ID>.
Refer to A.32.2.15 MCA for the valid values of <AID>
corresponding to specified units.
Example
l Command
RTRV-MCACHN::FAC-1-8-1-1:C;
l Response Message
NE 2005-10-12 15:54:55
M C COMPLD
" FAC-1-8-1-1::BANDTYPE=CBAND,MONFLAG=Y"
;
Related Commands
A.16.1 ED-MCACHN
A.16.3 RTRV-MCADATA
Retrieves results from monitoring the MCA.
Function
This command retrieves results from monitoring the MCA, such as the optical power, central
wavelength, OSNR, and number of channels.
Usage Note
None
Category
MCA
Security
Retrieve
Command Syntax
RTRV-MCADATA:[<TID>]:[<AID>]:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^"<AID>::BANDTYPE=<BANDTYPE>,WVTOTAL=<WVTOTAL>,WVNUM=<WVNUM>,WVCENTER=<WVCENTER>
,WVOFFSET=<WVOFFSET>,WVPOWER=<WVPOWER>,WVOSNR=<WVOSNR>"<cr><lf>
;
Response Parameters
AID Indicates the MCA port access identifier. The valid format is FAC-
<SHELF ID>-<SLOT ID>-<PORT ID>.
WVPOWER Indicates the optical power of the wavelength in units of 1.0 dBm.
For example, -27.3 indicates that the optical power is -27.3 dBm.
Example
l Command
RTRV-MCADATA::FAC-1-12-1:C;
l Response Message
NE 2005-10-12 15:54:55
M C COMPLD
"FAC-1-12-1::BANDTYPE=CBAND,WVTOTAL=0,WVNUM=1,WVCENTER=1529.16,WVOFFSET=0.00,WVPOW
ER=-60.0,WVOSNR=-60.0"
Related Commands
A.16.1 ED-MCACHN
A.16.2 RTRV-MCACHN
A.17.1 ED-TDC
Edits the attributes of the tunable dispersion compensator (TDC).
Function
This command edits the TDC attributes.
Usage Note
None
Category
Facility
Security
Provisioning
Command Syntax
ED-TDC:[<TID>]:<AID>:<CTAG>:::[AUTOADJ=<AUTOADJ>],[TDCVAL=<TDCVAL>];
Command Parameters
Paramete Default
r Description Value
<AID> Indicates the TDC access identifier. The valid value is provided NA
in A.32.2.27 TDC.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT
ID>.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
ED-TDC::FAC-1-16-1:C:::AUTOADJ=DISABLE;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.17.3 RTRV-TDC
A.17.2 OPR-TDC
A.17.2 OPR-TDC
Modifies the status of the TDC scan.
Function
This command modifies the status of the TDC scan.
Usage Note
None
Category
Facility
Security
Maintenance
Command Syntax
OPR-TDC:[<TID>]:<AID>:<CTAG>::<OPRT>;
Command Parameters
Default
Parameter Description Value
<OPRT> Indicates the TDC scan status. The valid values are NA
STARTSCAN and STOPSCAN.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Example
l Command
OPR-TDC::FAC-1-1-1:C::STARTSCAN;
l Response Message
NE 2004-01-01 11:37:18
M C COMPLD
;
Related Commands
A.17.3 RTRV-TDC
A.17.1 ED-TDC
A.17.3 RTRV-TDC
Retrieves the attributes of the TDC.
Function
This command retrieves the attributes of the TDC.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
RTRV-TDC:[<TID>]:<AID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf> ^^^<rsphdr><cr><lf> M^^<ctag>^COMPLD<cr><lf> ^^^"<AID>::
[TDCSTATE=<TDCSTATE>],[AUTOADJ=<AUTOADJ>],[TDCVAL=<TDCVAL>],[TDCMAX=<TDCMAX>],
[TDCMIN=<TDCMIN>],[TDCSTEP=<TDCSTEP>],[ACTDCVAL=<ACTDCVAL>]"<cr><lf> ;
Response Parameters
Parameters Description
<TDCSTATE> Indicates the current state of dispersion adjustment. The valid values are
IDLE, SUCCESS, FAIL, and ADJUSTING.
<AUTOADJ> Indicates whether dispersion fine adjustment is enabled. The valid values
are ENABLE and DISABLE (default).
Parameters Description
Example
l Command
RTRV-TDC::FAC-1-1-1:C;
l Response Message
NE 1990-01-01 11:22:19 M C COMPLD "FAC-1-1-1::AUTOADJ=DISABLE,TDCVAL=-1" ;
Related Commands
A.17.2 OPR-TDC
A.17.1 ED-TDC
A.17.4 REPT-EVT-TDCSCAN
Reports an event that indicates the scan state of a TDC.
Function
This command reports an event that indicates the scan state of a TDC.
Usage Note
None
Category
Facility
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr> <lf> <lf>^^^<rsphdr> <cr> <lf>
A^^<atag>^REPT^ TDCSCAN <cr> <lf>
Response Parameters
Parameter Description
<AID> Indicates the TDC access identifier. The valid value is provided in
A.32.2.27 TDC.
The valid format is FAC-<SHELF ID>-<SLOT ID>-<PORT ID>.
<STATE> Indicates the scan state of the TDC. The valid values are as follows:
l START: indicates that the search has started.
l SUCCESS: indicates that the search is complete and objects were
found.
l FAIL: indicates that the search is complete but no objects were
found.
Example
l Command
None
l Response Message
NE 2004-01-01 11:37:18
A 1 REPT EVT TDCSCAN
"FAC-1-4-1:::STATE=START"
;
Related Commands
None
A.18.1 ED-DST-V2
Sets DST for the new DST standard.
Function
This command sets DST for the new DST starndard.
Usage Note
None
Category
MON
Security
Provisioning
Command Syntax
ED-DST-V2:
[<TID>]::<CTAG>::<FLAG>,<BEGINADJMODE>,<ENDADJMODE
>,<ADJMINUTE>,<STARTMONTH>,<STARTDAY>,<STARTHOUR
>,<STARTMINUTE>,<STARTWEEK>,<STARTWEEKDAY>,<ENDMONTH>,<ENDDAY
>,<ENDHOUR>,<ENDMINUTE>,<ENDWEEK>,<ENDWEEKDAY>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
;
Response Parameters
None
Example
l Command
ED-DST-V2:::1::enable,DATE,WEEK_FORWORD,60,apr,1,13,0,1,fri,oct,3,14,0,2,mon;
l Response Message
NE 2005-03-21 09:33:54
M 100 COMPLD
;
Related Commands
A.2.4 RTRV-DST
A.18.2 RTRV-DST-V2
Retrieves DST information setted by ED-DST-V2.
Function
This command retrieves DST information setted by ED-DST-V2.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-DST-V2:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-
dd>^<"FLAG=<FLAG>,BEGINADJMODE=<BEGINADJMODE>,ENDADJMODE=<ENDADJMODE>,ADJ_MINUTE=<
ADJMINUTE>,START_MONTH=<STARTMONTH>,START_DAY=<STARTDAY>,START_HOUR=<STARTHOUR>,ST
ART_MINUTE=<STARTMINUTE>,START_WEEK=<STARTWEEK>,START_WEEKDAY=<STARTWEEKDAY>,END_M
ONTH=<ENDMONTH>,END_DAY=<ENDDAY>,END_HOUR=<ENDHOUR>,END_MINUTE=<ENDMINUTE>,END_WEE
K=<ENDWEEK>,END_WEEKDAY=<ENDWEEKDAY>,DST_STATUS=<DSTSTATUS>"> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
;
Response Parameters
Example
l Command
RTRV-DST-V2:::1;
l Response Message
DESMOINESPH-6800A-2 2012-05-15 22:23:14
M 1 COMPLD
"FLAG=ENABLE,BEGINADJMODE=DATE,ENDADJMODE=WEEK_FORWARD,ADJ_MINUTE=120,START_MONTH=
JAN,START_DAY=1,START_HOUR=0,START_MINUTE=0,START_WEEK=1,START_WEEKDAY=SUN,END_MON
TH=SEP,END_DAY=4,END_HOUR=14,END_MINUTE=0,END_WEEK=1,END_WEEKDAY=SAT,DST_STATUS=TR
UE"
;
Related Commands
A.2.4 RTRV-DST
A.18.3 RTRV-CHECK-PERIOD
Get the mon internal period of the CPU and VFS check.
Function
Get the mon internal period of the CPU and VFS check.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-CHECK-PERIOD:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"CPUCHECKPERIOD=<cpuperiod>,VFSCHECKPERIOD=<vfsperiod>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-CHECK-PERIOD::SLOT-1-8:100;
l Response Message
NE 2000-01-03 15:08:11
M 100 COMPLD
"CPUCHECKPERIOD=60,VFSCHECKPERIOD=3600"
;
Related Commands
None
A.18.4 RTRV-CPU-PEAKINFO
Query CPU occupancy peak value and current value
Function
Query CPU occupancy peak value and current value
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-CPU-PEAKINFO:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"TASKNAME=<CPUTH_TASKNAME>,TASK_CUR=<CPUTH_CUR>,TASK_PEAK=<CPUTH_PEAK>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-CPU-PEAKINFO::SLOT-1-8:100;
l Response Message
NE 2011-12-19 15:43:38
M 100 RTRV
"TASKNAME=BOX,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=_TIL,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=_EXC,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=VIDL,TASK_CUR=74,TASK_PEAK=74"
"TASKNAME=TICK,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tFtpServer,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=ECCPING,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tVos100ms,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tVos1s,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tVfsWorker,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tVfsSender,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tVfsSchemer,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tRackId,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tSrlmSend,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tBDMLow1S,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tDmmCCardSend,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tDmmCardRecv,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tDmmCtrlTimer,TASK_CUR=0,TASK_PEAK=0"
>
>
"TASKNAME=00018tLBDF,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=TPTH,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=TPTHPKG,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=PMTK,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=TPM,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=TBDPM18,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tHbuShell,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tHscShell,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tEthTest,TASK_CUR=0,TASK_PEAK=0"
>
>
"TASKNAME=tGspDebug,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tLimLibm,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tIpStack,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tTrans,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tFwd,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tFcl,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=TSCFG,TASK_CUR=2,TASK_PEAK=2"
"TASKNAME=00018TPDTCFG,TASK_CUR=2,TASK_PEAK=2"
"TASKNAME=TSCCLED,TASK_CUR=0,TASK_PEAK=0"
>
>
"TASKNAME=TOLSREC,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=00019tBDFL,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=00019tBDAlm,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=TBDPM19,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=00019VIRTUALCFG,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=00019TBDMcmd,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=00019TBDMcmdrst,TASK_CUR=0,TASK_PEAK=0"
>
>
"TASKNAME=tNbioLog,TASK_CUR=0,TASK_PEAK=0"
"TASKNAME=tAioWait,TASK_CUR=0,TASK_PEAK=0"
>
>
Related Commands
None
A.18.5 RTRV-CPUUSAGE
Query the CPU information of all tasks
Function
Query the CPU information of all tasks
Usage Note
None
Category
MON
Security
Super
Command Syntax
RTRV-CPUUSAGE:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"TASKNAME=<TASKNAME>,SWITCHCNT=<SWITCHCNT>,MINTIME=<MINTIME>,MAXTIME=<MAXTIME>,
RECENTTIME=<RECENTTIME>,SECTIME=<SECTIME>,MSECTIME=<MSECTIME>,CPUUSAGE=<CPUUSAGE>"
<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-CPUUSAGE::SLOT-1-18:100;
l Response Message
NE 2000-01-03 14:37:02
M 100 RTRV
"TASKNAME=BOX,SWITCHCNT=1906346,MINTIME=2,MAXTIME=7750,RECENTTIME=11,SECTIME=0,MSE
CTIME=41711889,CPUUSAGE= 0.00%"
"TASKNAME=_TIL,SWITCHCNT=0,MINTIME=0,MAXTIME=0,RECENTTIME=0,SECTIME=0,MSECTIME=0,C
PUUSAGE= 0.00%"
"TASKNAME=_EXC,SWITCHCNT=0,MINTIME=0,MAXTIME=0,RECENTTIME=0,SECTIME=0,MSECTIME=0,C
PUUSAGE= 0.00%"
;
Related Commands
None
A.18.6 RTRV-LIST
This command displays the task or semaphore or timer or message queue information based on
the key.
Function
Displays the task or semaphore or timer or message queue information based on the key.
Usage Note
None
Category
MON
Security
Maintenance
Command Syntax
RTRV-LIST:[<TID>]:<MON_BOARD_ID>:<CTAG>::<resourcetype>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"<MonListInfo>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-LIST::SLOT-1-18:100::sem;
l Response Message
WEBSTERCITY-6800A-1 2012-06-06 16:52:57
M 100 RTRV
" ******************************************************"
" Max Semaphore = 2000"
" Total binary Semaphore = 67"
" Total count Semaphore = 20"
" Total mutex Semaphore = 288"
" ------------------------------------------------------"
" Sema4Name Sema4ID OSSemID Count Mode Type"
" ------------------------------------------------------"
" cbr 1 113338224 1 FIFO Binary"
" cbn 2 113338352 1 FIFO Binary"
" sSTLPool 3 115140536 1 FIFO Binary"
" sVos100ms 4 115140720 1 FIFO Mutex "
" sVos1s 5 115140848 1 FIFO Mutex "
" sVFSFileStub 6 115142112 1 FIFO Mutex "
>
>
M 100 RTRV
" SDBW4508 73 115465752 1 FIFO Mutex "
" SDBR4508 74 115465880 16 FIFO Count "
" SDBW4509 75 115466008 1 FIFO Mutex "
" SDBR4509 76 116296936 16 FIFO Count "
" SDBW4510 77 116297064 1 FIFO Mutex "
" SDBR4510 78 116297192 16 FIFO Count "
" SDBW4512 79 116297320 1 FIFO Mutex "
" SDBR4512 80 116297448 16 FIFO Count "
" sSMNG 81 116297576 1 FIFO Mutex "
" PickSftmSem 82 116297704 1 FIFO Mutex "
" sSBKUP 83 116320632 1 FIFO Mutex "
>
>
>
>
Related Commands
None
A.18.7 RTRV-SCCID
This command obtains the SCC board id.
Function
Obtains the SCC board id.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-SCCID:[<TID>]::<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"SccID=<SCCID>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-SCCID:::100;
l Response Message
WEBSTERCITY-6800A-1 2012-06-06 15:20:26
M 100 COMPLD
"SCCID=18"
;
>
Related Commands
None
A.18.8 RTRV-MEMPEAK-INFO
Get memory peak usage info
Function
Get memory peak usage info.
Usage Note
None
Category
MON
Security
Maintenance
Command Syntax
RTRV-MEMPEAK-INFO:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"PTNumber=<MEM_PTNUM>,Peak=<MEM_PEAK>,Current=<MEM_CUR>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-MEMPEAK-INFO::SLOT-1-18:100;
l Response Message
DESMOINESPH-6800A-2 2012-05-15 22:36:27
M 100 COMPLD
"PTNUMBER=PT1,PEAK=17284348,CURRENT=17283896"
"PTNUMBER=PT2,PEAK=99299188,CURRENT=95935292"
;
Related Commands
None
A.18.9 RTRV-MEMUSAGE-INFO
Get memory usage info
Function
Get memory usage info.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-MEMUSAGE-INFO:
[<TID>]:<MON_BOARD_ID>:<CTAG>::<MON_MODULE_ID>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"PARTITIONID=<PRT_ID>,ALLOCSIZE=<ALLOC_SIZE>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-MEMUSAGE-INFO::SLOT-1-8:100::9;
l Response Message
NE 2000-01-03 15:35:52
M 100 COMPLD
"PARTITIONID=0,ALLOCSIZE=0"
"PARTITIONID=1,ALLOCSIZE=21139307"
;
Related Commands
None
A.18.10 RTRV-MEMUTIL-INFO
Get memory utilization of the system.
Function
Get memory utilization of the system in all the memory partitions.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-MEMUTIL-INFO:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"PARTID=<PART_ID>,TOTALSIZE=<TOTAL_SIZE>,USEDSIZE=<USED_SIZE>,FREESIZE=<FREE_SI
ZE>,USERATIO=<USE_RATIO>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-MEMUTIL-INFO::SLOT-1-8:100;
l Response Message
NE 2000-01-03 15:27:35
M 100 COMPLD
"PARTID=0,TOTALSIZE=58717476,USEDSIZE=14014388,FREESIZE=44703088,USERATIO=23"
"PARTID=1,TOTALSIZE=278804488,USEDSIZE=103849020,FREESIZE=174955468,USERATIO=37"
Related Commands
None
A.18.11 RTRV-MODULE-DUMPINFO
Query dump information of a module.
Function
Query dump information of a module.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-MODULE-DUMPINFO:
[<TID>]:<MON_BOARD_ID>:<CTAG>::<MM_CLASSID>,<MM_FUNCID>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"INFO=<MODULE_INFO>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-MODULE-DUMPINFO::slot-1-8:100::\"HSC.IHSC.CHSCModule\",\"00018\";
l Response Message
NE118 2000-01-03 15:15:55
M 100 COMPLD
"INFO=CHSCModule"
"INFO= m_dwHscTimerID = 0x8d4cebc"
"INFO= m_wTwoLogicBoardIDSum = 35"
"INFO= m_wTwoPhyBoardIDSum = 35"
"INFO= m_dwManualCmdFlag = 40321"
"INFO= m_dwCount = 0"
"INFO= m_dwHandleMaker = 3"
"INFO= g_dwHscPrint = 0"
;
Related Commands
None
A.18.12 RTRV-MODULE-LISTINFO
Query module information of the given module
Function
Query module information of the given module
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-MODULE-LISTINFO:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"CLASS_ID=<MM_CLASSID>,FUNC_ID=<MM_FUNCID>,PTR_ADDR=<MM_PTRADDR>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-MODULE-LISTINFO::SLOT-1-8:100;
l Response Message
NE 2000-01-03 15:21:38
M 100 RTRV
"CLASS_ID=DMM.IDMM.CDMM,FUNC_ID=DMM,PTR_ADDR=205613964"
"CLASS_ID=CRM.ICRM.CCRM,FUNC_ID=CRM,PTR_ADDR=205850008"
"CLASS_ID=BDM.IBDManager.CBDMManager,FUNC_ID=BDM,PTR_ADDR=205864132"
"CLASS_ID=Sm.ISmReg.CSmReg,FUNC_ID=00018,PTR_ADDR=205603528"
"CLASS_ID=MMI.IMMI.CMmiModule,FUNC_ID=00018,PTR_ADDR=205939548"
"CLASS_ID=HSC.IHSC.CHSCModule,FUNC_ID=00018,PTR_ADDR=205948916"
"CLASS_ID=HBU.IHBU.CHBUModule,FUNC_ID=00018,PTR_ADDR=205961136"
"CLASS_ID=PE.IPeManager.CPeManager,FUNC_ID=00018,PTR_ADDR=205988444"
;
Related Commands
None
A.18.13 RTRV-QUELENALM-STATE
Get Queue length alarm flag
Function
Get Queue length alarm flag
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-QUELENALM-STATE:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"<State>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-QUELENALM-STATE::SLOT-1-8:100;
l Response Message
NEW-NE 1990-01-01 14:46:42
M 100 COMPLD
"STATUS=DISABLE"
;
>
Related Commands
None
A.18.14 RTRV-REBOOT-LOG
Get the reboot records of board
Function
Get the reboot records of board
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-REBOOT-LOG:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"<MonMemDmgInfo>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-REBOOT-LOG::SLOT-1-8:100;
l Response Message
NE 2000-01-03 15:40:28
M 100 RTRV
"
****************************************************************
System startup time : 2005.07.27 11:02:05.000
System startup cputick : 0x00000000 e39940e8
System reboot at file : Unknow, Line: 0
System reboot by task : tShell0, VID: -1, OsalID: 0x63fa430
NE 2000-01-03 15:40:28
M 100 COMPLD
"<-- 0x01adedb8(shellInterpCparse)
<-- 0x01ae3888(shellExec) <-- 0x01ae3e44(shellTask)
<-- 0x01a0bde4(vxTaskEntry)
****************************************************************
"
Related Commands
None
A.18.15 RTRV-RESERVEMEM
Query configuration information of general reserved memory
Function
Query configuration information of general reserved memory
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-RESERVEMEM:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"BLOCK_NUM=<RESVMEM_BLKNUM>,BLOCK_NAME=<RESVMEM_BLKNAME>,BLOCK_SIZE=<RESVMEM_BL
KSIZE>"<cr><lf>
^^^"POSITION=<RESVMEM_BLKPOS>,ISCONFIG=<RESVMEM_CFGFLAG>,ISALLOC=<RESVMEM_ALLOCFLA
G>"<cr><lf>
^^^"FILE=<RESVMEM_FILE>",LINE=<RESVMEM_LINE><cr><lf>
Response Parameters
Parameter Description
Example
l Command
RTRV-RESERVEMEM::SLOT-1-8:100;
l Response Message
NE 2000-01-03 14:43:43
M 100 COMPLD
"BLOCK_NUM=0,BLOCK_NAME=MDBG,BLOCK_SIZE=102400,POSITION=534776376,ISCONFIG=0,ISALL
OC=1,FILE=vos_callstack.cpp,LINE=1157"
"BLOCK_NUM=1,BLOCK_NAME=NUSE,BLOCK_SIZE=102400,POSITION=534878776,ISCONFIG=0,ISALL
OC=1,FILE=vos_callstack.cpp,LINE=1201"
"BLOCK_NUM=2,BLOCK_NAME=C_PK,BLOCK_SIZE=14408,POSITION=534981176,ISCONFIG=0,ISALLO
C=1,FILE=mon_thr.cpp,LINE=1181"
"BLOCK_NUM=3,BLOCK_NAME=F_PK,BLOCK_SIZE=12,POSITION=534995584,ISCONFIG=0,ISALLOC=1
,FILE=mon_thr.cpp,LINE=1225"
;
Related Commands
None
A.18.16 RTRV-SWTTHRINFO
Retrieves status of memory usage threshold check, VFS usage threshold check cpu usage
threshold check and message over check.
Function
Retrieves status of memory usage threshold check, VFS usage threshold check cpu usage
threshold check and message over check.
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-SWTTHRINFO:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"name=<MSGTH_FIELD>,value=<MSGTH_VALUE>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-SWTTHRINFO::SLOT-1-8:100;
l Response Message
NE 2000-01-03 14:57:46
M 100 COMPLD
"NAME=MsgOverThrVal,VALUE=85"
"NAME=MsgOverThrSwt,VALUE=disable"
"NAME=MemOverThrVal,VALUE=85"
"NAME=MemOverThrSwt,VALUE=disable"
"NAME=VFSOverThrVal,VALUE=85"
"NAME=VFSOverThrSwt,VALUE=disable"
"NAME=CPUOverThrVal,VALUE=85"
"NAME=CPUOverThrSwt,VALUE=disable"
;
Related Commands
None
A.18.17 RTRV-SYMADDR
Retrieves the current function's call stack of the specified task
Function
Retrieves the current function's call stack of the specified task
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-SYMADDR:
[<TID>]:<MON_BOARD_ID>:<CTAG>::<MON_FILE_NAME_SIXTY>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"SYMBOL_NAME=<MON_FILE_NAME_SIXTY>,SYMBOL_ADDRESS=<MON_SYMBOL_ADDR>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-SYMADDR::SLOT-1-18:100::\"VOS_Entry\";
l Response Message
NE 2000-01-03 14:16:14
M 100 COMPLD
"SYMBOL_NAME=VOS_Entry,SYMBOL_ADDRESS=19913448"
;
Related Commands
None
A.18.18 RTRV-TASKSTACK
Retrieves the symbol address of the symbol name given
Function
Retrieves the symbol address of the symbol name given
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-TASKSTACK:[<TID>]:<MON_BOARD_ID>:<CTAG>::<TaskName>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"StackDepth=<StackDepth>,FuncAddr=<FuncAddr>,FuncName=<FuncName>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-TASKSTACK::SLOT-1-8:100::\"tTL1CmdRsp\";
l Response Message
NE 2000-01-03 14:04:46
M 100 COMPLD
"STACKDEPTH=0,FUNCADDR=26093876,FUNCNAME=OSAL_TaskDelay"
"STACKDEPTH=1,FUNCADDR=25975788,FUNCNAME=VOS_TaskDelay"
;
Related Commands
None
A.18.19 RTRV-TASKONMSGQUE
Retrives the list of tasks on a message queue.
Function
This command retrives the list of tasks on a message queue.
Usage Note
None
Category
MON
Security
Maintenance
Command Syntax
RTRV-TASKONMSGQUE:
[<TID>]:<MON_BOARD_ID>:<CTAG>::<MON_MSGQUE_NAME_FTN>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"<MonTaskInfo>"
;
Response Parameters
Parameter Description
Example
l Command
RTRV-TASKONMSGQUE::SLOT-1-18:100::"qTL1Auto";
l Response Message
DESMOINESPH-6800A-2 2012-05-15 22:52:38
M 100 RTRV
" *******************************************************"
" Queue ID = 31"
" Queue Name = qTL1Auto "
" Queue Mode = FIFO SYN"
" Total Length = 4096"
" Current Length = 0"
" Used Percent = 0%"
" Peak Length = 103"
" Peak Time = 2012.05.14 15:40:18"
" Max Msg Size = 16"
" Queue Msg Start Addr = 0x903cf80"
" Queue Msg Head Index = 200"
" Queue Msg Tail Index = 200"
" Total Write Count = 37064"
" Total Read Count = 57394"
" Total Overload Alarm Count = 0"
" Queue Overload Flag = 0"
" Total OverLoad Recover Count = 0"
>
Related Commands
None
A.18.20 RTRV-TASKONSEM
Retrives the list of tasks on a semaphore.
Function
This command retrives the list of tasks on a semaphore.
Usage Note
None
Category
MON
Security
Maintenance
Command Syntax
RTRV-TASKONSEM:[<TID>]:<MON_BOARD_ID>:<CTAG>::<MON_SEM_NAME>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"<MonTaskInfo>"
;
Response Parameters
Parameter Description
Example
l Command
RTRV-TASKONSEM::SLOT-1-18:100::"CSMMsgMId";
l Response Message
DESMOINESPH-6800A-2 2012-05-15 23:02:50
M 100 RTRV
" ******************************************************"
" Semaphore Name = CSMMsgMId"
" Semaphore ID = 38"
" Semaphore Count = 1"
" Semaphore Mode = FIFO"
" Semaphore Type = Mutex "
" Create Task ID = 6"
" Last P Task ID = 124"
" Last V Task ID = 124"
" P Block Task ID = 0"
" Total Syn P Number = 9"
" Total Asy P Number = 0"
" Total V Number = 9"
" Syn P Timeout Number = 0"
" Syn P Fail Number = 0"
" Asy P Fail Number = 0"
" V Fail Number = 0"
" Mutex Recur Lock Number = 0"
Related Commands
None
A.18.21 RTRV-VFS-PEAKINFO
Query the available peak value of file system and current value
Function
Query the available peak value of file system and current value
Usage Note
None
Category
MON
Security
Retrieve
Command Syntax
RTRV-VFS-PEAKINFO:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr><lf>
^^^"VFS_REGION=<VFS_REGION>,VFSTH_CURVAL=<VFSTH_CURVAL>,VFSTH_PEAKVAL=<VFSTH_PEAKV
AL>"<cr><lf>
;
Response Parameters
Parameter Description
Example
l Command
RTRV-VFS-PEAKINFO::SLOT-1-8:100;
l Response Message
NE 2000-01-03 14:37:02
M 100 COMPLD
"VFS_REGION=mfs,VFSTH_CURVAL=2107392,VFSTH_PEAKVAL=2107392"
"VFS_REGION=ofs1,VFSTH_CURVAL=23363584,VFSTH_PEAKVAL=23363584"
"VFS_REGION=ofs2,VFSTH_CURVAL=4177920,VFSTH_PEAKVAL=4177920"
;
Related Commands
None
A.18.22 RTRV-BDINFO-EQPT
Retrieves ELabel.
Function
This command retrieves the hardware and software information about the equipment.
Usage Note
None
Category
System
Security
Retrieve
Command Syntax
RTRV-BDINFO-EQPT:[<TID>]:<SFTM_SLOT>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr> <lf> <lf>
^^^<sid>^<yyyy-mm-dd>^<hh:mm:ss> <cr><lf>
M^^<ctag>^COMPLD <cr> <lf>
^^^"<contents>" <cr> <lf>
;
Response Parameters
None
Example
l Command
RTRV-BDINFO-EQPT::SLOT-1-7:100
l Response Message
NE 1990-02-18 21:57:41
M 100 COMPLD
"\"/$[ArchivesInfo Version]
/$ArchivesInfoVersion=2.0
/$[Log]
/$Log1=26817,030376730,2006-02-23
[Board Properties]
BoardType=SSC6SCC01
BarCode=0376731062000342
BOM=BOM0303767301
\""
"\"/$Item=03037673
/cDescription=
/eDescription=OptiX Metro 6100,SSC6SCC01,System Control&Communication Board
/$PCBVersion=
Manufactured=2006-02-23
ManufactureCode=1
/$CLEICode=
\""
"\"
/$[Daughter Board Properties]
/$Daughter_BoardNum=0
/$[Software]
/$SoftwareNum=0
\""
;
Related Commands
None
A.18.23 SET-CPUTESTSTA
Sets the switch flag to monitor the running status of all tasks.
Function
This command sets the switch flag to monitor the running status of all tasks.
Usage Note
None
Category
MON
Security
Super
Command Syntax
SET-CPUTESTSTA:[<TID>]:<MON_BOARD_ID>:<CTAG>::<CPUSTA>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
SET-CPUTESTSTA::SLOT-1-18:100::ENABLE;
l Response Message
NE 2005-08-02 17:52:45
M 100 COMPLD
;
Related Commands
A.29.3 RTRV-DBMS-AUTOBACKUP
A.18.24 WRT-BB
This command backs up the black box to flash.
Function
Backs up the black box to flash.
Usage Note
None
Category
MON
Security
Debug
Command Syntax
WRT-BB:[<TID>]:<MON_BOARD_ID>:<CTAG>;
Command Parameters
Parameter Description Default Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
WRT-BB::SLOT-1-18:100
l Response Message
WEBSTERCITY-6800A-1 2012-06-06 15:29:56
M 100 COMPLD
;
>
Related Commands
A.29.3 RTRV-DBMS-AUTOBACKUP
A.19.1 ED-PMALMCTRL-<MOD2>
Edits the parameters of the alarm table that affect the condition of reporting events.
Function
This command edits the parameters of the alarm table.
Usage Note
None
Category
Performance
Security
Provisioning
Command Syntax
ED-PMALMCTRL-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<MONTYPE>],[<LOCN>],
[<DIRN>],[<RPTMODE>],[<INTERVAL>],[<RTHR>],[<FTHR>],[<ENFLAG>];
Command Parameters
Parameter Description Default Value
<RPTMODE Indicates the report mode. The valid value are as RPTALL
> follows:
l RPTUP: indicates that only rising events are
reported.
l RPTDOWN: indicates that only falling events
are reported.
l RPTALL: indicates that rising and falling
events are reported.
The null value indicates that the last setting of the
value does not change.
<ENFLAG> Indicates the state flag. The valid values are DISABLE
ENABLE and DISABLE. By default, <ENFLAG>
is DISABLE if <PRDTP> is 30s and prdvar. If
<PRDTP> is 30m, <ENFLAG> is ENABLE.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-PMALMCTRL-FETH::FAC-4-1:500::ETHDROP,,,,,ENABLE;
l Response Message
NE 2004-07-12 20:16:29
M 500 COMPLD
;
Related Commands
A.19.2 RTRV-PMALMCTRL-<MOD2>
A.19.2 RTRV-PMALMCTRL-<MOD2>
Retrieves parameters of the alarm table.
Function
This command retrieves parameters of the alarm table.
Usage Note
None
Category
Performance
Security
Retrieve
Command Syntax
RTRV-PMALMCTRL-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<MONTYPE>],[<LOCN>],
[<DIRN>];
Command Parameters
Paramete Description Default Value
r
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<AID>,<AIDTYPE>:<MONTYPE>,[<LOCN>],
[<DIRN>],<RPTMODE>,<INTERVAL>,<RTHR>,<FTHR>,<ENFLAG>"<cr><lf>
;
Response Parameters
Parameter Description
<LOCN> Indicates the location, in reference to the entity identified by the <AID>,
being performance monitored. The valid values are as follows:
l NEND (near end condition, alarm, or event occurred at the near end of
the system)
l FEND (far end condition, alarm, or event occurred at the far end of the
system)
<RPTMODE> Indicates the report mode. The valid value are as follows:
l RPTUP: indicates that only rising events are reported.
l RPTDOWN: indicates that only falling events are reported.
l RPTALL: indicates that rising and falling events are reported.
<INTERVAL Indicates the alarm sample interval. By default, the interval is 10 seconds.
> The valid value ranges from 5 to 600 seconds.
<RTHR> Indicates the rising threshold. The valid value ranges from 1 to 4294967295
(0xFFFFFFFF). The rising threshold must be higher than the falling
threshold.
<FTHR> Indicates the falling threshold. The valid value ranges from 0 to 4294967294
(0xFFFFFFFE). The falling threshold must be lower than the rising
threshold.
<ENFLAG> Indicates the state flag. The valid values are ENABLE and DISABLE.
Example
l Command
RTRV-PMALMCTRL-FETH::FAC-4-1:400::ETHDROP;
l Response Message
NE 2004-07-12 20:20:45
M 400 COMPLD
"FAC-4-1,FETH:ETHDROP,,,RPTALL,10,1,0,ENABLE"
;
Related Commands
A.19.1 ED-PMALMCTRL-<MOD2>
A.19.3 ED-PMHISTCTRL
Modifies all history control parameters.
Function
This command modifies all history control parameters.
Usage Note
None
Category
Performance
Security
Provisioning
Command Syntax
ED-PMHISTCTRL:[<TID>]::<CTAG>::<PRDTP>, [<RECNUM>],[<PRD>],[<ENFLAG>]
Command Parameters
Parameter Description Default
Value
<PRDTP> Indicates the period type. The valid values are 30 seconds, 30 30m
minutes, prdvar, and prdvar2. <PRD> must be null unless the
parameter is prdvar.
<PRD> Indicates the period. The valid value ranges from 300 seconds NA
to 43200 seconds, that is, 5 minutes to 12 hours. And the value
must be the multiple of 30.<PRDTP> must be prdvar unless
the parameter is null. If <PRDTP> is prdvar, this parameter
may be not null.
<ENFLAG Indicates the state flag. The valid values are enable and NA
> disable. By default, <ENFLAG> is disable, if <PRDTP> is 30
seconds or prdvar. If <PRDTP> is 30 minutes, <ENFLAG> is
enable.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
;
Response Parameters
None
Example
l Command
ED-PMHISTCTRL:::100::30S,,,ENABLE;
l Response Message
NE 2004-07-12 19:41:28
M 100 COMPLD
;
Related Commands
A.19.4 RTRV-PMHISTCTRL
A.19.4 RTRV-PMHISTCTRL
Retrieves parameters of the history control table.
Function
This command retrieves parameters of the history control table.
Usage Note
None
Category
Performance
Security
Retrieve
Command Syntax
RTRV-PMHISTCTRL:[<TID>]::<CTAG>::[<PRDTP>];
Command Parameters
Parameter Description Default
Value
<PRDTP> Indicates the period type. The valid values are 30s, 30m, PRDALL
prdvar, prdvar2, and PRDALL.
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^^COMPLD<cr><lf>
^^^"<PRDTP>,<RECNUM>,<PRD>,<ENFLAG>"<cr><lf>
;
Response Parameters
Parameter Description
<PRDTP> Indicates the period type. The valid values are 30s, 30m, prdvar, and
prdvar2.
<RECNUM> Indicates the maximum number of records. The valid value ranges
from 1 to 50.
<PRD> Indicates the period. The valid values are 300-43200 seconds, that is,
5 minutes to 12 hours.
<ENFLAG> Indicates the state flag. The valid values are ENABLE and
DISABLE. By default, <ENFLAG> is DISABLE if <PRDTP> is 30s
and prdvar. If <PRDTP> is 30m, <ENFLAG> is ENABLE.
Example
l Command
RTRV-PMHISTCTRL:::120::;
l Response Message
NE 2004-07-12 20:05:41
M 120 COMPLD
"30S,16,30,DISABLE"
"30M,16,1800,ENABLE"
"PRDVAR,16,900,DISABLE"
"PRDVAR2,6,86400,DISABLE"
;
Related Commands
A.19.3 ED-PMHISTCTRL
A.19.5 INIT-REG-<MOD2>
Initializes storage registers.
Function
This command initializes one or more storage registers or event counters associated with an
equipment unit or facility on the NE to a specific value. In the most cases, these registers contain
the PM information accumulated in previous intervals.
Usage Note
When <MONDAT> and <MONTM> are both null, it indicates that the current PM data is
cleared. If one of them is not null, it indicates that the history PM data is cleared.
Category
Performance
Security
Provisioning
Command Syntax
INIT-REG-<MOD2>:[<TID>]:[<AID>]:<CTAG>::<MONTYPE>,[<MONVAL>],[<LOCN>],
[<DIRN>],[<TMPER>],[<MONDAT>][,<MONTM>];
Command Parameters
Paramete Description Default Value
r
<AID> Indicates the access identifier that identifies the equipment ALL
unit, facility, subscriber line, trunk, link, packet link, or
signaling link on the NE. This parameter depends on the
command code modifier and what kind of performance
monitoring data is being retrieved.
<MONDA Indicates the date that the requested PM period specified in Current date
T> <TMPER> began. The valid format is MM-DD.
<MONTM Indicates the time of the day that the requested PM period Current time
> specified in <TMPER> began. (HH-MM)
Response Syntax
<cr><lf> <lf>
^^^<rsphdr><cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>
;
Response Parameters
None
Example
l Command
INIT-REG-OC3::FAC-1-3-1:100::ALL,10,,,15-MIN,7-1,0-0;
l Response Message
NE 2004-07-08 15:57:49
M 100 COMPLD
;
Related Commands
None
A.19.6 RTRV-PM-<MOD2>
Retrieves the performance of <MOD2>.
Function
This command sends the current setting of PM data associated with one or more equipment units,
facilities, links, or signaling links within the NE.
Usage Note
None
Category
Performance
Security
Retrieve
Command Syntax
RTRV-PM-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<MONTYPE>],[<MONLEV>],
[<LOCN>],[<DIRN>],[<TMPER>],[<MONDAT>][,<MONTM>];
Command Parameters
Parameter Description Default Value
<MONDA Indicates the date that the requested PM period specified in The current date
T> <TMPER> began. The valid format is MM-DD.
<MONTM Indicates the time of day that the requested PM period The current time
> specified in <TMPER> began. (HH-MM)
Response Syntax
The response format depends on whether any specified PM values exist.
NOTE
The normal response MUST contain at least one occurrence of <rspblk>. It is allowed to contain multiple
<rspblk>s if applicable.
Response Parameters
Parameter Description
<AID> Indicates the access identifier that identifies the equipment unit, facility,
subscriber line, trunk, link, packet link, or signaling link on the NE. This
parameter depends on the command code modifier and what kind of
performance monitoring data is being retrieved.
<MONTYPE Indicates the type of monitored performance for which a value is requested.
>
<MONVAL Indicates the discriminating level for the requested monitored parameter.
>
<VLDTY> Indicates the validity indicator for the reported PM data. It indicates whether
the information for the specified time period is accumulated over the entire
time period or some portion of it.
The valid values are VALID and INVALID.
Parameter Description
<LOCN> Indicates the location, in reference to the entity identified by <AID>, being
performance monitored. NEND (near end) refers to PM values obtained at
the identified entity. FEND (far end) refers to PM values obtained at a distant
entity that is connected to the identified entity.
<MONDAT Indicates the date that the requested PM period specified in <TMPER> began.
> The valid format is MM-DD.
<MONTM> Indicates the time of day that the requested PM period specified in <TMPER>
began.
Example
l Command
RTRV-PM-OC48::FAC-1-4-1:123::CV-S,0-UP,NEND,,15-MIN,04-09,17-00;
l Response Message
NE 2003-04-09 17:25:12
M 123 COMPLD
"FAC-1-4-1,OC48:CV-S,2,VALID,NEND,RCV,15-MIN,04-09,17-15"
Related Commands
None
A.19.7 REPT^PM^<MOD2>
Reports information about the performance monitoring.
Function
This event is generated by an NE to inform the OS or maintenance personnel about the PM.
Parameters are provided to report the PM data from multiple data collection intervals in a single
message for NEs that store a history of the PM information. The REPT PM parameter is an
automatic message that is generated by the NE. Performance monitoring data can also be
retrieved on demand by using a RTRV-PM-<MOD2> command. However,
REPT^PM^<MOD2> is not used to respond to a RTRV-PM-<MOD2> command.
Usage Note
None
Category
Performance
Security
Retrieve
Command Syntax
None
Command Parameters
None
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
A^^<atag>^REPT^PM^<MOD2>
<cr> <lf> <rspblk> + ;
where <rspblk> has the format:
^^^"[<AID>]:<MONTYPE>,<MONVAL>,[<VLDTY>],
[<LOCN>],[<DIRN>],[<TMPER>],[<MONDAT>]
[,<MONTM>]" <cr> <lf>
Response Parameters
Parameter Description
<MOD2> The valid values are EQPT, rr, LINK, PLK, SLK, and COM.
<AID> Indicates the access identifier for a single equipment unit, facility, link, packet
link, or signaling link on the NE to which the retrieved monitored parameter
value pertains.
<MONTYP Indicates the type of the monitored parameter whose value is being reported.
E>
<VLDTY> Indicates the validity indicator for the reported PM data. It indicates whether
the information for the specified time period is accumulated over the entire
time period or some portion of it.
The valid values are VALID and INVALID.
<LOCN> Indicates the location, in reference to the entity identified by <AID>, from
which the PM value is being retrieved. NEND (near end) refers to PM values
obtained at the identified entity. FEND (far end) refers to PM values obtained
at a distant entity that is connected to the identified entity.
<DIRN> Indicates the direction of PM relative to the entity identified by <AID>. The
valid values are TRMT (transmit direction only) and RCV (receive direction
only).
Parameter Description
<TMPER> Indicates the accumulation time period for the PM information. The valid
values are 15-MIN and 1-DAY.
<MONTM Indicates the time that the PM period specified in <TMPER> began.
>
Example
l Command
None
l Response Message
NE 2004-07-08 16:14:01
A 335 REPT PM EQPT
"SLOT-1-3:BDTEMPMAX,312,INVALID,NEND,RCV,1-DAY,07-08,16-12"
;
Related Commands
A.24.12 ALW-PMREPT-ALL
A.24.13 INH-PMREPT-ALL
A.19.8 RTRV-PMDAY
Retrieves the start time for the daily collection of PM data.
Function
This command retrieves the start time of the daily PM data collection period of an NE. The
current start time of the daily data collection period can be set by using the SET-PMDAY
command.
Usage Note
None
Category
Performance
Security
Retrieve
Command Syntax
RTRV-PMDAY:[<TID>]::<CTAG>;
Command Parameters
None
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>
^^^"<pm-day-start>" <cr> <lf>
;
Response Parameters
Parameter Description
<PM-DAY- The valid format is HOD, (hour-of-day) and ranges from 0 to 23.
START>
Example
l Command
RTRV-PMDAY:::123456;
l Response Message
NE 2004-07-08 16:10:19
M 123456 COMPLD
"7"
;
Related Commands
A.19.9 SET-PMDAY
A.19.9 SET-PMDAY
Sets time of day that the performance monitoring starts.
Function
This command allows the start time of the daily PM data collection period to begin at any hour
of the day.
Usage Note
None
Category
Performance
Security
Provisioning
Command Syntax
SET-PMDAY:[<TID>]::<CTAG>::<PM-DAY-START>;
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>;
Response Parameters
None
Example
l Command
SET-PMDAY:::C::7;
l Response Message
NE 2004-07-08 16:07:50
M C COMPLD
;
>
Related Commands
A.19.8 RTRV-PMDAY
A.19.10 RTRV-TH-<MOD2>
Retrieves a threshold.
Function
This command instructs an NE to send the current threshold level of one or more monitored
parameters that triggers an automatic message if the threshold is exceeded. These threshold
levels may apply to one or more equipment units, facilities, subscriber lines, trunks, links, packet
links, or signaling links on the NE.
Usage Note
None
Category
Performance
Security
Retrieve
Command Syntax
RTRV-TH-<MOD2>:[<TID>]:[<AID>]:<CTAG>[::[<MONTYPE>],[<LOCN>]
[,<TMPER>]];
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr><lf><lf>
^^^<rsphdr><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
<rspblk>+;
NOTE
The normal response must contain at least one occurrence of <rspblk>. It is allowed to contain multiple
<rspblk>s.
Response Parameters
Parameter Description
<AID> Indicates the access identifier that identifies the equipment unit, facility,
subscriber line, trunk, link, packet link, or signaling link on the NE. This
parameter depends on the command code modifier and what kind of
performance monitoring data is being retrieved.
<MONTYP Indicates the type of monitored performance for which a value is requested.
E>
<LOCN> Indicates the location, in reference to the entity identified by <AID>, being
performance monitored. NEND (near end) refers to PM values obtained at the
identified entity. FEND (far end) refers to PM values obtained at a distant
entity that is connected to the identified entity.
<DIRN> Indicates the direction of monitoring relative to the entity identified by <AID>.
<DIRN> defaults to BTH, which indicates both directions. The valid values
are TRMT (transmit direction only) and RCV (receive direction only).
<THLEV> Indicates the current threshold level for the monitored parameter.
Parameter Description
Example
l Command
RTRV-TH-OC192::CLNT-1-1-1:C::ES-S,NEND,RCV,15-MIN;
l Response Message
NE 2004-07-08 16:05:44
M C COMPLD
"CLNT-1-1-1,OC192:ES-S,NEND,RCV,65,15-MIN"
;
Related Commands
A.19.11 SET-TH-<MOD2>
A.19.11 SET-TH-<MOD2>
Sets the threshold.
Function
This command instructs an NE to set the threshold level for a monitored parameter that, when
exceeded, triggers an automatic message. The threshold level may apply to one or more
equipment units or facilities on the NE.
Usage Note
None
Category
Performance
Security
Provisioning
Command Syntax
SET-TH-<MOD2>:[<TID>]:<AID>:<CTAG>::<MONTYPE>,<THLEV>,[<LOCN>],
[<DIRN>],[<TMPER>];
Command Parameters
Paramete Description Default
r Value
<AID> Indicates the access identifier that identifies the equipment unit, ALL
facility, subscriber line, trunk, link, packet link, or signaling link
on the NE. This parameter depends on the command code
modifier and what kind of performance monitoring data is being
retrieved.
<MONTY Indicates the type of monitored performance for which a value ALL
PE> is requested. All values will be retrieved if nothing is entered for
this parameter.
<TMPER Indicates the accumulation time period for the PM information. 15-MIN
> The parameter defaults to 15-MIN if nothing is entered.
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>
;
Response Parameters
None
Example
l Command
SET-TH-OCH::FAC-1-1-1:C::LBCMAX,0x100100,NEND,TRMT,15-MIN;
l Response Message
NE 2004-07-08 16:00:01
M C COMPLD
;
Related Commands
A.19.10 RTRV-TH-<MOD2>
A.19.12 RTRV-ATTRTCA-<MOD2>
Retrieve attributes of threshold-crossing alerts (TCA).
Function
This command queries the report mode of performance threshold violation and the alarm
severity.
Usage Note
None
Category
Alarms and Conditions
Security
Retrieve
Command Syntax
RTRV-ATTRTCA-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<NTFCNCDE>],
[<CONDTYPE>],[<LOCN>],[<DIRN>],[<TMPER>],[<SRVEFF>],[<CONDEFF>];
Command Parameters
Parameter Description Default
Value
Response Syntax
<cr> <lf> <lf>
^^^<rsphdr> <cr> <lf>
M^^<ctag>^COMPLD <cr> <lf>
<rspblk> + ;
where <rspblk> has the format:
^^^"<AID>[,<AIDTYPE>]:[<NTFCNCDE>],<CONDTYPE>,
[<LOCN>],[<DIRN>],[<TMPER>][,<SRVEFF>],<CONDEFF>" <cr> <lf>
;
Response Parameters
Parameter Description
<NTFCNCDE Indicates the notification code that specifies the type of notification to be
> generated by an NE upon the occurrence of the event described in
<CONDTYPE>.
<CONDTYPE Indicates the type of TCA for which the notification attributes
> (<NTFCNCDE>and <CONDEFF>) are being changed.
<LOCN> Indicates the single location for which an alarm condition is being reported
and refers to the entity identified by the AID. NEND (near end) refers to
PM values obtained at the identified entity. FEND (far end) refers to PM
values obtained at a remote entity that is connected to the identified entity.
Likewise, LINE[-x] refers to an intermediate point.
<DIRN> Indicates the direction of the alarm condition and is relative to the entity
identified by the AID.
<TMPER> Indicates the accumulation time period for the PM information if the
<CONDTYPE> is in a T-x format for a threshold violation.
This parameter is invalid at present and is not displayed in the query result.
Parameter Description
<SRVEFF> Indicates whether the alarms impact services. The valid values are as
follows:
l NSA: The condition does not affect the services.
l SA: The condition affects the services.
All values will be retrieved if nothing is entered for this parameter.
Example
l Command
RTRV-ATTRTCA-OC48::CLNT-1-3-1-1:1::,T-CV-S,NEND,RCV,,NSA,SC;
l Response Message
NE 2004-11-09 06:27:05
M 1 COMPLD
"CLNT-1-3-1-1,OC48:1:MJ,T-CV-S,NEND,RCV,,NSA,SC"
;
Related Commands
A.19.13 SET-ATTRTCA-<MOD2>
A.19.13 SET-ATTRTCA-<MOD2>
Edits the attributes of threshold-crossing alert (TCA).
Function
This command sets the report mode of performance threshold violation to TC or SC and sets the
alarm severity.
Usage Note
When the report mode of performance threshold violation is set to SC, the alarm severity can
be set and the alarms are reported according to the preset alarm severity.
Category
Alarms and Conditions
Security
Provisioning
Command Syntax
SET-ATTRTCA-<MOD2>: [<TID>]:[<AID>]:<CTAG>::[<NTFCNCDE>],
[<CONDTYPE>],[<LOCN>],[<DIRN>],[<TMPER>],[<SRVEFF>],[<CONDEFF>];
Command Parameters
Parameter Description Default
Value