Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide, Release 4.6
Chapter: Chapter 3, TL1 Command Descriptions
- 3.1 TL1 Commands by Category
- 3.2 TL1 Commands by Card (Cisco ONS 15454)
- 3.3 TL1 Commands by Card (ONS 15327)
- 3.4 TL1 Commands
- 3.4.1 ACT-USER: Activate User
- 3.4.2 ALW-MSG-ALL: Allow Message All
- 3.4.3 ALW-MSG-DBCHG: Allow Database Change Message
- 3.4.4 ALW-MSG-SECU: Allow Message Security
- 3.4.5 ALW-PMREPT-ALL: Allow Performance Report All
- 3.4.6 ALW-SWDX-EQPT: Allow Switch Duplex Equipment
- 3.4.7 ALW-SWTOPROTN-EQPT: Allow Switch to Protection Equipment
- 3.4.8 ALW-SWTOWKG-EQPT: Allow Switch to Working Equipment
- 3.4.9 ALW-USER-SECU: Allow User Security
- 3.4.10 APPLY: Apply
- 3.4.11 CANC: Cancel
- 3.4.12 CANC-USER: Cancel User
- 3.4.13 CANC-USER-SECU: Cancel User Security
- 3.4.14 CHG-ACCMD-<MOD_TACC>: Change Test Access Mode (DS1, DS3I, E1, E3, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.15 CONN-TACC-<MOD_TACC>: Connect Test Access (DS1, DS3I, E1, E3, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.16 COPY-IOSCFG: Copy IOS Config File
- 3.4.17 COPY-RFILE: Copy RFILE
- 3.4.18 DISC-TACC: Disconnect Test Access
- 3.4.19 DLT-<MOD_RING>: Delete (BLSR)
- 3.4.20 DLT-CRS-<PATH>: Delete Cross Connection (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
- 3.4.21 DLT-EQPT: Delete Equipment
- 3.4.22 DLT-FFP-<OCN_TYPE>: Delete Facility Protection Group (OC3, OC12, OC48, OC192)
- 3.4.23 DLT-FFP-CLNT: Delete Facility Protection Group Client
- 3.4.24 DLT-LNK-<MOD2O>: Delete Optical Link (OCH, OMS, OTS)
- 3.4.25 DLT-OSC: Delete OSC
- 3.4.26 DLT-UCP-CC: Delete Unified Control Plane Control Channel
- 3.4.27 DLT-UCP-IF: Delete Unified Control Plane Interface
- 3.4.28 DLT-UCP-NBR: Delete Unified Control Plane Neighbor
- 3.4.29 DLT-USER-SECU: Delete User Security
- 3.4.30 DLT-VCG: Delete Virtual Concatenated Group
- 3.4.31 DLT-WLEN: Delete Wavelength
- 3.4.32 ED-<MOD_PATH>: Edit (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
- 3.4.33 ED-<MOD_RING>: Edit Bidirectional Line Switched Ring
- 3.4.34 ED-<OCN_TYPE>: Edit (OC3, OC12, OC48, OC192)
- 3.4.35 ED-BITS: Edit Building Integrated Timing Supply
- 3.4.36 ED-CLNT: Edit Client
- 3.4.37 ED-CMD-SECU: Edit Command Security
- 3.4.38 ED-CRS-<PATH>:ED Cross Connect (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS 48C, STS192C, VT1, VT2)
- 3.4.39 ED-DAT: Edit Date and Time
- 3.4.40 ED-DS1: Edit DS1
- 3.4.41 ED-DWDM: Edit Dense Wavelength Division Multiplexing
- 3.4.42 ED-EC1: Edit Electrical Carrier
- 3.4.43 ED-EQPT: Edit Equipment
- 3.4.44 ED-FC: Edit Fiber Channel Facility
- 3.4.45 ED-FFP-<OCN_TYPE>: Edit Facility Protection Group (OC3, OC12, OC48, OC192)
- 3.4.46 ED-FFP-CLNT: Edit Facility Protection Group Client
- 3.4.47 ED-FFP-OCH: Edit Facility Protection Group OCH
- 3.4.48 ED-G1000: Edit G1000
- 3.4.49 ED-LNK-<MOD2O>: Edit Link (OCH, OMS, OTS)
- 3.4.50 ED-NE-GEN: Edit Network Element General
- 3.4.51 ED-NE-PATH: Edit Network Element Paths
- 3.4.52 ED-NE-SYNCN: Edit Network Element Synchronization
- 3.4.53 ED-OCH: Edit Optical Channel
- 3.4.54 ED-OMS: Edit Optical Multiplex Section
- 3.4.55 ED-OSC: Edit Optical Service Channel
- 3.4.56 ED-OTS: Edit OTS
- 3.4.57 ED-PID: Edit Password
- 3.4.58 ED-SYNCN: Edit Synchronization
- 3.4.59 ED-T1: Edit T1
- 3.4.60 ED-T3: Edit T3
- 3.4.61 ED-TRC-CLNT: Edit Trace Client
- 3.4.62 ED-TRC-OCH: Edit Trace Optical Channel Facilities
- 3.4.63 ED-UCP-CC: Edit Unified Control Plane Control Channel
- 3.4.64 ED-UCP-IF: Edit Unified Control Plane Interface
- 3.4.65 ED-UCP-NBR: Edit Unified Control Plane Neighbor
- 3.4.66 ED-UCP-NODE: Edit Unified Control Plane Node
- 3.4.67 ED-USER-SECU: Edit User Security
- 3.4.68 ED-WDMANS: Edit Wavelength Division Multiplexing Automatic Node Setup
- 3.4.69 ED-WLEN: Edit Wavelength
- 3.4.70 ENT-<MOD_RING>: Enter BLSR
- 3.4.71 ENT-CRS-<PATH>: Enter Cross Connection (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
- 3.4.72 ENT-EQPT: Enter Equipment
- 3.4.73 ENT-FFP-<OCN_TYPE>: Enter Facility Protection Group (OC3, OC12, OC48, OC192)
- 3.4.74 ENT-FFP-CLNT: Enter Facility Protection Group Client
- 3.4.75 ENT-LNK-<MOD2O>: Enter Optical Link (OCH, OMS, OTS)
- 3.4.76 ENT-OSC: Enter Optical Service Channel
- 3.4.77 ENT-UCP-CC: Enter Unified Control Plane Control Channel
- 3.4.78 ENT-UCP-IF: Enter Unified Control Plane Interface
- 3.4.79 ENT-UCP-NBR: Enter Unified Control Plane Neighbor
- 3.4.80 ENT-USER-SECU: Enter User Security
- 3.4.81 ENT-VCG: Enter Virtual Concatenated Group
- 3.4.82 ENT-WLEN: Enter Wavelength
- 3.4.83 EX-SW-<OCN_BLSR>: Operate Protection Switch (OC12, OC48, OC192)
- 3.4.84 INH-MSG-ALL: Inhibit Message All
- 3.4.85 INH-MSG-DBCHG: Inhibit Database Change Message
- 3.4.86 INH-MSG-SECU: Inhibit Message Security
- 3.4.87 INH-PMREPT-ALL: Inhibit Performance Report All
- 3.4.88 INH-SWDX-EQPT: Inhibit Switch Duplex Equipment
- 3.4.89 INH-SWTOPROTN-EQPT: Inhibit Switch to Protection Equipment
- 3.4.90 INH-SWTOWKG-EQPT: Inhibit Switch to Working Equipment
- 3.4.91 INH-USER-SECU: Inhibit User Security
- 3.4.92 INIT-REG-<MOD2>: Initialize Register (CLNT, DS1, DS3I, EC1, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.93 INIT-SYS: Initialize System
- 3.4.94 OPR-ACO-ALL: Operate Alarm Cutoff All
- 3.4.95 OPR-EXT-CONT: Operate External Control
- 3.4.96 OPR-LASER-OTS: Operate Laser Optical Transport Section
- 3.4.97 OPR-LNK: Operate Link
- 3.4.98 OPR-LPBK-<MOD2>: Operate Loopback (CLNT, DS1, DS3I, EC1, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.99 OPR-PROTNSW-<OCN_TYPE>: Operate Protection Switch (OC3, OC12, OC48, OC192)
- 3.4.100 OPR-PROTNSW-<PATH>: Operate Protection Switch (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
- 3.4.101 OPR-PROTNSW-CLNT: Operate Protection Switch Client
- 3.4.102 OPR-PROTNSW-OCH: Operate Protection Switch OCH
- 3.4.103 OPR-SYNCNSW: Operate Synchronization Switch
- 3.4.104 OPR-WDMANS: Operate Wavelength Division Multiplexing Automatic Node Setup
- 3.4.105 REPT ALM <MOD2ALM>: Report Alarm (CLNT, DS1, DS3I, E100, E1000, EC1, FSTE, G1000, GIGE, OC12, OC192, OC3, OC48, OCH, OMS, OSC, OTS, POS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, UDCDCC, UDCF, VT1, VT2, WLEN)
- 3.4.106 REPT ALM BITS: Report Alarm Building Integrated Timing Supply
- 3.4.107 REPT ALM COM: Report Alarm COM
- 3.4.108 REPT ALM ENV: Report Alarm Environment
- 3.4.109 REPT ALM EQPT: Report Alarm Equipment
- 3.4.110 REPT ALM SECU: Report Alarm Security
- 3.4.111 REPT ALM SYNCN: Report Alarm Synchronization
- 3.4.112 REPT ALM UCP: Report Alarm Unified Control Plane
- 3.4.113 REPT DBCHG: Report Database Change Message
- 3.4.114 REPT EVT <MOD2ALM>: Report Event (CLNT, DS1, DS3I, FSTE, G1000, GIGE, OC12, OC192, OC3, OC48, OCH, OMS, OSC, OTS, POS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, UDCDCC, UDCF, VT1, VT2, WLEN)
- 3.4.115 REPT EVT BITS: Report Event BITS
- 3.4.116 REPT EVT COM: Report Event COM
- 3.4.117 REPT EVT ENV: Report Event Environment
- 3.4.118 REPT EVT EQPT: Report Event Equipment
- 3.4.119 REPT EVT FXFR: Report Event Software Download
- 3.4.120 REPT EVT IOSCFG: Report Event IOS Config File
- 3.4.121 REPT EVT SECU: Report Event Security
- 3.4.122 REPT EVT SESSION: Report Event Session
- 3.4.123 REPT EVT SYNCN: Report Event Synchronization
- 3.4.124 REPT EVT UCP: Report Event Unified Control Plane
- 3.4.125 REPT PM <MOD2>: Report Performance Monitoring (CLNT, DS1, DS3I, EC1, FC, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.126 REPT SW: Report Switch
- 3.4.127 RLS-EXT-CONT: Release External Control
- 3.4.128 RLS-LASER-OTS: Release Laser Optical Transport Section
- 3.4.129 RLS-LPBK-<MOD2>: Release Loopback (CLNT, DS1, DS3I, EC1, FC, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.130 RLS-PROTNSW-<OCN_TYPE>: Release Protection Switch (OC3, OC12, OC48, OC192)
- 3.4.131 RLS-PROTNSW-<PATH>: Release Protection Switch (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
- 3.4.132 RLS-PROTNSW-CLNT: Release Protection Switch Client
- 3.4.133 RLS-PROTNSW-OCH: Release Protection Switch OCH
- 3.4.134 RLS-SYNCNSW: Release Synchronization Switch
- 3.4.135 RMV-<MOD2_IO>: Remove (CLNT, DS1, DS3I, EC1, FC, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, T1, T3)
- 3.4.136 RST-<MOD2_IO>: Restore (CLNT, DS1, DS3I, EC1, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, T1, T3)
- 3.4.137 RTRV-<MOD_RING>: Retrieve Bidirectional Line Switched Ring
- 3.4.138 RTRV-<OCN_TYPE>: Retrieve (OC3, OC12, OC48, OC192)
- 3.4.139 RTRV-<PATH>: Retrieve (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
- 3.4.140 RTRV-ALM-<MOD2ALM>:Retrieve Alarm (CLNT, DS1, DS3I, EC1, FC, FSTE, G1000, GIGE, OC12, OC192, OC3, OC48, OCH, OMS, OSC, OTS, POS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, UDCDCC, UDCF, VT1, VT2, WLEN)
- 3.4.141 RTRV-ALM-ALL: Retrieve Alarm All
- 3.4.142 RTRV-ALM-BITS: Retrieve Alarm Building Integrated Timing Supply
- 3.4.143 RTRV-ALM-ENV: Retrieve Alarm Environment
- 3.4.144 RTRV-ALM-EQPT: Retrieve Alarm Equipment
- 3.4.145 RTRV-ALM-SYNCN: Retrieve Alarm Synchronization
- 3.4.146 RTRV-ALM-UCP: Retrieve Alarm Unified Control Plane
- 3.4.147 RTRV-ALMTH-<MOD2>: Retrieve Alarm Threshold (CLNT, DS1, DS3I, EC1, FC, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STM1E, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.148 RTRV-ALMTH-EQPT: Retrieve Alarm Threshold Equipment
- 3.4.149 RTRV-ATTR-CONT: Retrieve Attribute Control
- 3.4.150 RTRV-ATTR-ENV: Retrieve Attribute Environment
- 3.4.151 RTRV-BITS: Retrieve Building Integrated Timing Supply
- 3.4.152 RTRV-CLNT: Retrieve Client
- 3.4.153 RTRV-CMD-SECU: Retrieve Command Security
- 3.4.154 RTRV-COND-<MOD2ALM>: Retrieve Condition (CLNT, DS1, EC1, FC, FSTE, G1000, GIGE, OC12, OC192, OC3, OC48, OCH, OMS, OSC, OTS, POS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, UDCDCC, UDCF, VT1, VT2, WLEN)
- 3.4.155 RTRV-COND-ALL: Retrieve Condition All
- 3.4.156 RTRV-COND-BITS: Retrieve Condition Building Integrated Timing Supply
- 3.4.157 RTRV-COND-ENV: Retrieve Environmental Condition
- 3.4.158 RTRV-COND-EQPT: Retrieve Condition Equipment
- 3.4.159 RTRV-COND-SYNCN: Retrieve Condition Synchronization
- 3.4.160 RTRV-COND-UCP: Retrieve Condition Unified Control Plane
- 3.4.161 RTRV-CRS: Retrieve Cross Connect
- 3.4.162 RTRV-CRS-<PATH>: Retrieve Cross Connect (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
- 3.4.163 RTRV-DFLT-SECU: Retrieve Default Security
- 3.4.164 RTRV-DS1: Retrieve DS1
- 3.4.165 RTRV-DWDM: Retrieve Dense Wavelength Division Multiplexing
- 3.4.166 RTRV-EC1: Retrieve EC1
- 3.4.167 RTRV-EQPT: Retrieve Equipment
- 3.4.168 RTRV-EXT-CONT: Retrieve External Control
- 3.4.169 RTRV-FC: Retrieve Fiber Channel Facility
- 3.4.170 RTRV-FFP-<OCN_TYPE>: Retrieve Facility Protection Group (OC3, OC12, OC48, OC192)
- 3.4.171 RTRV-FFP-CLNT: Retrieve Facility Protection Group Client
- 3.4.172 RTRV-FFP-OCH: Retrieve Facility Protection Group OCH
- 3.4.173 RTRV-FSTE: Retrieve Fast Ethernet
- 3.4.174 RTRV-G1000: Retrieve G1000 Facility
- 3.4.175 RTRV-GIGE: Retrieve Gigabit Ethernet
- 3.4.176 RTRV-HDR: Retrieve Header
- 3.4.177 RTRV-INV: Retrieve Inventory
- 3.4.178 RTRV-LNK: Retrieve Link
- 3.4.179 RTRV-LNK-<MOD2O>: Retrieve Optical Link (OCH, OMS, OTS)
- 3.4.180 RTRV-LOG: Retrieve Log
- 3.4.181 RTRV-MAP-NETWORK: Retrieve Map Network
- 3.4.182 RTRV-NE-GEN: Retrieve Network Element General
- 3.4.183 RTRV-NE-IPMAP: Retrieve Network Element IPMAP
- 3.4.184 RTRV-NE-PATH: Retrieve Network Element Path
- 3.4.185 RTRV-NE-SYNCN: Retrieve Network Element Synchronization
- 3.4.186 RTRV-NE-WDMANS: Retrieve NE Wavelength Division Multiplexing Automatic Node Setup
- 3.4.187 RTRV-OCH: Retrieve Optical Channel
- 3.4.188 RTRV-OMS: Retrieve Optical Multiplex Section
- 3.4.189 RTRV-OSC: Retrieve Optical Service Channel
- 3.4.190 RTRV-OTS: Retrieve Optical Transport System
- 3.4.191 RTRV-PM-<MOD2>: Retrieve Performance (CLNT, DS1, DS3I, EC1, FC, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.192 RTRV-PMMODE-<STS_PATH>: Retrieve Performance Mode of PM Data Collection (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C)
- 3.4.193 RTRV-PMSCHED-<MOD2>:Retrieve Performance Monitoring Schedule (CLNT, DS1, DS3I, EC1, FC, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.194 RTRV-PMSCHED-ALL: Retrieve Performance Schedule All
- 3.4.195 RTRV-POS: Retrieve Packet Over SONET
- 3.4.196 RTRV-PROTNSW-<OCN_TYPE>: Retrieve Protection Switch (OC3, OC12, OC48, OC192)
- 3.4.197 RTRV-PROTNSW-<PATH>: Retrieve Protection Switch (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
- 3.4.198 RTRV-PROTNSW-CLNT: Retrieve Protection Switch Client
- 3.4.199 RTRV-PROTNSW-OCH: Retrieve Protection Switch OCH
- 3.4.200 RTRV-PTHTRC-<STS_PATH>: Retrieve Path Trace (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C)
- 3.4.201 RTRV-STS: Retrieve STS
- 3.4.202 RTRV-SYNCN: Retrieve Synchronization
- 3.4.203 RTRV-T1: Retrieve T1 Facility
- 3.4.204 RTRV-T3: Retrieve T3
- 3.4.205 RTRV-TACC: Retrieve Test Access
- 3.4.206 RTRV-TH-<MOD2>: Retrieve Threshold (CLNT, DS1, DS3I, EC1, FC, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.207 RTRV-TH-ALL: Retrieve Threshold ALL
- 3.4.208 RTRV-TOD: Retrieve Time of Day
- 3.4.209 RTRV-TRC-<OCN_BLSR>: Retrieve Trace Client (OC12, OC192, OC48)
- 3.4.210 RTRV-TRC-CLNT: Retrieve Trace Client
- 3.4.211 RTRV-TRC-OCH: Retrieve Trace Optical Channel
- 3.4.212 RTRV-UCP-CC: Retrieve Unified Control Plane Control Channel
- 3.4.213 RTRV-UCP-IF: Retrieve Unified Control Plane Interface
- 3.4.214 RTRV-UCP-NBR: Retrieve Unified Control Plane Neighbor
- 3.4.215 RTRV-UCP-NODE: Retrieve Unified Control Plane Node
- 3.4.216 RTRV-USER-SECU: Retrieve User Security
- 3.4.217 RTRV-VCG: Retrieve Virtual Concatenated Group
- 3.4.218 RTRV-VT: RTRV VT
- 3.4.219 RTRV-WDMANS: Retrieve Wavelength Division Multiplexing Automatic Node Setup
- 3.4.220 RTRV-WLEN: Retrieve Wavelength
- 3.4.221 SCHED-PMREPT-<MOD2>: Schedule Performance Monitoring Report (CLNT, DS1, DS3I, FC, EC1, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STM1E, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.222 SET-ALMTH-<MOD2>: Set Alarm Threshold (CLNT, DS1, DS3I, FC, EC1, G1000, OC12, OC192, OC3, OC48, OCH, OMS, OTS, STM1E, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
- 3.4.223 SET-ALMTH-EQPT: Set Alarm Equipment
- 3.4.224 SET-ATTR-CONT: Set Attribute Control
- 3.4.225 SET-ATTR-ENV: Set Attribute Environment
- 3.4.226 SET-ATTR-SECUDFLT: Set Attribute Security Default
- 3.4.227 SET-PMMODE-<STS_PATH>: Set Performance Mode of PM Data Collection (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C)
- 3.4.228 SET-TH-<MOD2>: Set Threshold (CLNT, DS1, DS3I, EC1, FC, G1000, OC3, OC12,OC48, OC192, OCH, OMS, OTS, STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C,T1, T3, VT1)
- 3.4.229 SET-TOD: Set Time of Day
- 3.4.230 SW-DX-EQPT: Switch Duplex Equipment
- 3.4.231 SW-TOPROTN-EQPT: Switch to Protection Equipment
- 3.4.232 SW-TOWKG-EQPT: Switch to Working Equipment
TL1 Command Descriptions
This chapter provides specific information on TL1 commands and autonomous messages for the
Cisco ONS 15454 and Cisco ONS 15327, Release 4.6, including:
•
TL1 commands by category
•TL1 commands by card
•TL1 commands
For information on command components, such as parameters, see Chapter 4, "TL1 Command Components."
Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
3.1 TL1 Commands by Category
3.2 TL1 Commands by Card (Cisco ONS 15454)
3.3 TL1 Commands by Card (ONS 15327)
3.4 TL1 Commands
The commands and autonomous messages used for ONS 15454 and ONS 15327 are described in detail in this section and are listed alphabetically according to the first alpha character of the command string.
Each TL1 command must be less than or equal to 255 characters. Any command larger than 255 characters must be split into multiple commands. For example, if you use the ED-<MOD_PATH> command to edit the J1 EXPTRC/TRC message, path protection attributes, and TACC attributes and the command exceeds 255 characters the command will not be processed. You must use multiple ED-<MOD_PATH> commands instead.
Note The CTAG of any TL1 line mode command is a mandatory field in this TL1 release.
Note The AID definitions provided are supersets of the actual AID definitions.
Note TL1 commands that are entered incorrectly are not completed.
Note In release 3.3 and later, the ACT-USER command will return a DENY without any error message. Any other command will return DENY with the PLNA (Login Not Active) error message.
3.4.1 ACT-USER: Activate User
This command set-ups a session with the Network Element (NE).
Notes:
1. Passwords are masked for the following security commands: ACT-USER, COPY-RFILE, COPY-IOSCFG, ED-PID, ENT-USER-SECU and ED-USER-SECU. Access to a TL1 session via any means will have the password masked. The CTC Request History and Message Log will also show the masked commands. When a password-masked command is re-issued by double-clicking the command from CTC Request History, the password will still be masked in the CTC Request History and Message Log. The actual password that was previously issued will be sent to the NE. To use a former command as a template only, single-click the command in CTC Request History. The command will be placed in the Command Request text box, where you can edit the appropriate fields prior to re-issuing it.
2. This command is backwards compatible with userids and passwords from ONS 15454 2.X software versions according to the following rules:
ACT-USER:[TID]:[STRING]:CTAG::[STRING]
a. The syntax of the userid (first [STRING]) and the password (second [STRING]) are not checked.
b. Invalid syntax for both the userid and password is permitted, but the user can only log in if the userid/password match what is in the database.
c. The userid and password cannot exceed 10 characters.
3. For the ACT-USER command, it is required that no error code be transmitted except to convey that the login is granted or denied. Per TR-835, Appendix A, Section A.2:
"... the error codes corresponding to ACT ... do not apply to the ACT-USER command because this command requires that no error code be provided to the session request except to indicate that it has been denied. Before a session is established, a specific error code may reveal clues to an intruder attempting unauthorized entry."
Note Starting with this release (R4.6) the following feature can be turned on or off and the default is off: A new user must change his or her password after establishing a session for the first time before continuing. All TL1 commands except for ED-PID and CANC-USER will be denied until the password is changed. Once the password has been changed, a user can execute any command that his security level allows. If the user logs out without changing his password each following session will DENY all commands, except ED-PID and CANC-USER, until the password is changed.
|
|
|
|
|---|---|---|
Category |
System |
|
Security |
N/A |
|
Related Messages |
|
|
Input Format |
ACT-USER:[<TID>]:<UID>:<CTAG>::<PID>; where: • • Note |
|
Input Example |
ACT-USER:PETALUMA:TERRI:100::MYPASSWD; |
|
Output Format |
SID DATE TIME where: • • • |
|
Output Example |
TID-000 1998-06-20 14:30:00 |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.2 ALW-MSG-ALL: Allow Message All
This command instructs the NE to enter a mode in which all the REPT ALM and REPT EVT autonomous messages are transmitted. See the INH-MSG-ALL command to inhibit these autonomous messages. When a TL1 session starts, the REPT ALM and REPT EVT messages are allowed by default.
Note If this command is issued twice in the same session, the SAAL (Status, Already Allowed) error message will be returned. The optional fields in the e block are not supported.
|
|
|
|
|---|---|---|
Category |
System |
|
Security |
Retrieve |
|
Related Messages |
|
|
Input Format |
ALW-MSG-ALL:[<TID>]::<CTAG>[::,,]; |
|
Input Example |
ALW-MSG-ALL:PETALUMA::549; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.3 ALW-MSG-DBCHG: Allow Database Change Message
This command enables REPT DBCHG. When a TL1 session starts, the REPT DBCHG messages are not allowed by default.
Note This command is not defined in the GR.
|
|
|
|
|---|---|---|
Category |
Log |
|
Security |
Retrieve |
|
Related Messages |
|
|
Input Format |
ALW-MSG-DBCHG:[<TID>]::<CTAG>[::,,]; |
|
Input Example |
ALW-MSG-DBCHG:CISCO::123; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.4 ALW-MSG-SECU: Allow Message Security
This command enables REPT EVT SECU and REPT ALM SECU
|
|
|
|
|---|---|---|
Category |
Security |
|
Security |
Superuser |
|
Related Messages |
|
|
Input Format |
ALW-MSG-SECU:[<TID>]::<CTAG>; |
|
Input Example |
ALW-MSG-SECU:PETALUMA::123; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.5 ALW-PMREPT-ALL: Allow Performance Report All
This command resumes processing all the PM reports that are inhibited. The allowance of the PM reporting is session-based, which means the command is only effective to the TL1 session that issues this command. REPT PM messages are inhibited by default for a session.
|
|
|
|
|---|---|---|
Category |
Performance |
|
Security |
Retrieve |
|
Related Messages |
|
|
Input Format |
ALW-PMREPT-ALL:[<TID>]::<CTAG>; |
|
Input Example |
ALW-PMREPT-ALL:CISCONODE::123; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.6 ALW-SWDX-EQPT: Allow Switch Duplex Equipment
(Cisco ONS 15454 only)
This command allows automatic or manual switching on a duplex system containing duplexed or redundant equipment. To inhibit an NE switching to duplex, use the INH-SWDX-EQPT command.
ALW-SWDX-EQPT is not used for SONET line or electrical card protection switching. For SONET line or path protection switching commands, see OPR-PROTNSW and RLS-PROTNSW commands. For the electrical card protection switching, see the SW-TOWKG-EQPT and SW-TOPROTN-EQPT commands.
Note This command applies to the XC, XCVT, or XC10G equipment units only in this release.
|
|
|
|
|---|---|---|
Category |
Equipment |
|
Security |
Maintenance |
|
Related Messages |
|
|
Input Format |
ALW-SWDX-EQPT:[<TID>]:<AID>:<CTAG>[::]; where: • |
|
Input Example |
ALW-SWDX-EQPT:CISCO:SLOT-8:1234; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.7 ALW-SWTOPROTN-EQPT: Allow Switch to Protection Equipment
(Cisco ONS 15454 only)
This command allows automatic or manual switching of an equipment unit back to a protection status. Use the INH-SWTOPROTN-EQPT command to inhibit an NE from switching to protection.
ALW-SWTOPROTN-EQPT is used for non-SONET line cards (e.g. DS1, DS3, DS3XM, and EC1). DS1 and DS3 cards have 1:1 and 1:N equipment protection. DS3XM and EC1 cards have only 1:1 equipment protection. When this command is given to a working unit, the working unit will be allowed to switch to the protection unit. When this command is given to a protection unit, any working unit in the protection group is allowed to switch to the protection unit.
The standing condition of INHSWPR on the unit specified by the AID will be cleared.
Notes:
1. This command only supports one value of the <DIRN> parameter - BTH. A command with any other value is considered an incorrect use of the command. An IDNV (Input, Data Not Valid) error message should be responsed.
2. This command is not used for the common control (TCC2 or XC/XCVT/XC10G) cards. A command on a common control card will receive an IIAC (Input, Invalid Access Identifier) error message. To use the common control card switching commands, use the SW-DX-EQPT and ALW-SWDX-EQPT commands.
3. This command is not used for SONET (OCN) cards. A command on a SONET card will receive an IIAC (Input, Invalid Access identifier) error message. To use a SONET card switching command, use OPR-PROTNSW and RLS-PROTNSW commands.
4. If this command is used on a card that is not in a protection group, the SNVS (Status, Not in Valid State) error message should be responsed.
5. If this command is used on a card that is not in the inhibit state, the SAAL (Status, Already Allowed) error message should be responsed.
6. The following situation(s) are allowed and will not generate any error response: Sending this command to missing cards so long as none of the previous error conditions apply.
|
|
|
|
|---|---|---|
Category |
Equipment |
|
Security |
Maintenance |
|
Related Messages |
|
|
Input Format |
ALW-SWTOPROTN-EQPT:[<TID>]:<AID>:<CTAG>[::<DIRN>]; where: • • |
|
Input Example |
ALW-SWTOPROTN-EQPT:CISCO:SLOT-2:123::BTH; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.8 ALW-SWTOWKG-EQPT: Allow Switch to Working Equipment
(Cisco ONS 15454 only)
This command allows automatic or manual switching of an equipment unit back to a working status. Use the INH-SWTOWKG-EQPT command to inhibit an NE from switching to working. ALW-SWTOWKG-EQPT is used for non-SONET line cards (e.g. DS1, DS3, DS3XM, and EC1). DS1 and DS3 cards have 1:1 and 1:N equipment protection. DS3XM and EC1 cards have only 1:1 equipment protection.
When this command is given to a working unit, the working unit will be allowed to carry traffic. In the case of revertive protection, the traffic will switch immediately from the protection unit to the working unit regardless of the reversion time setting.
When this command is given to a protection unit, the protection unit will be allowed to switch back to the working unit currently protected as long as the working unit has not raised INHSWWKG. In the case of revertive protection, the traffic will switch immediately from the protection unit to the working unit regardless of the reversion time setting. In the case of non-revertive protection, the protection unit will continue to carry the traffic.
The standing condition of INHSWWKG on the unit specified by the AID will be cleared.
Notes:
1. This command only supports one value of the <DIRN> parameter - BTH. A command with any other value is considered an incorrect use of the command. An IDNV (Input, Data Not Valid) error message should be responsed.
2. This command is not used for the common control (TCC2 or XC/XCVT/XC10G) cards. A command on a common control card will receive an IIAC (Input, Invalid Access Identifier) error message. To use the common control card switching commands, use the SW-DX-EQPT and ALW-SWDX-EQPT commands.
3. This command is not used for SONET (OCN) cards. A command on a SONET card will receive an IIAC (Input, Invalid Access Identifier) error message. To use a SONET card switching command, use the OPR-PROTNSW and RLS-PROTNSW commands.
4. If this command is used on a card that is not in a protection group, the SNVS (Status, Not in Valid State) error message should be responsed.
5. If this command is used on a card that is not in the inhibit state, the SAAL (Status, Already Allowed) error message should be responsed.
6. The following situation(s) are allowed and will not generate any error response: sending this command to missing cards as long as none of the previous error conditions apply.
|
|
|
|
|---|---|---|
Category |
Equipment |
|
Security |
Maintenance |
|
Related Messages |
|
|
Input Format |
ALW-SWTOWKG-EQPT:[<TID>]:<AID>:<CTAG>[::<DIRN>]; where: • • |
|
Input Example |
ALW-SWTOWKG-EQPT:CISCO:SLOT-2:123::BTH; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.9 ALW-USER-SECU: Allow User Security
This command enables a userid that has been disabled (e.g., via the INH-USER-SECU command) so the user can establish a session with the NE.
|
|
|
|
|---|---|---|
Category |
Security |
|
Security |
Superuser |
|
Related Messages |
|
|
Input Format |
ALW-USER-SECU:[<TID>]::<CTAG>::<UID>; where: • |
|
Input Example |
ALW-USER-SECU:PETALUMA::123::UID; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.10 APPLY: Apply
This command activates or reverts a software load during a software upgrade or downgrade process.
Note An error will be generated if you attempt to activate an older software load or attempt to revert to a newer software load.
|
|
|
|
|---|---|---|
Category |
File Transfer |
|
Security |
Superuser |
|
Related Messages |
|
|
Input Format |
APPLY:[<TID>]::<CTAG>[::<MEM_SW_TYPE>]; where: • |
|
Input Example |
APPLY:CISCO::123::ACT; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.11 CANC: Cancel
Reports the occurrence of a session timeout event.
CANC is an autonomous message transmitted by the NE to a user when a session established by that user is terminated because no messages were exchanged for a long period of time, a timeout. There is a default timeout period based on the user's privilege/security level, and starting with Release 4.0 timeouts can be provisioned. The default timeouts based on privilege/security level are: superuser [SUPER] has the timeout period of 15 minutes., the Provision user [PROV] has the timeout period of 30 minutes, the Maintenance [MAINT] user has the timeout period of 60 minutes, the Retrieve user [RTRV] has no timeout.
When a timeout occurs, the corresponding port drops and the next session initiation at that port requires the regular login procedure.
The CANC message is only used to indicate that a session has been terminated because of a timeout. If a session is terminated for a different reason (e.g., forced logout, loss of communication), the REPT EVT SESSION message is used.
3.4.12 CANC-USER: Cancel User
This command logs a user out of an active session with the NE.
Note The USERID field of this command is a mandatory field.
For the CANC-USER command: CANC-USER:[TID]:[STRING]:CTAG
the syntax of the userid (first [STRING]) is not checked. Invalid syntax for the userid is permitted and the userid must not exceed 10 characters.
|
|
|
|
|---|---|---|
Category |
Security |
|
Security |
Retrieve |
|
Related Messages |
|
|
Input Format |
CANC-USER:[<TID>]:<USERID>:<CTAG>; where: • Note |
|
Input Example |
CANC-USER:PETALUMA:TERRI:101; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.13 CANC-USER-SECU: Cancel User Security
This command forces a user off of the NE.
The UID specified can be a single userid or a list of userids separated by `&'. The keyword ALL is not permitted. The UID specified cannot be the userid of the administrator issuing the command.
Note This command will log out ALL sessions on the NE (TL1 and CTC) of a user whose userid matches the UID specified in the command.
|
|
|
|
|---|---|---|
Category |
Security |
|
Security |
Superuser |
|
Related Messages |
|
|
Input Format |
CANC-USER-SECU:[<TID>]:<UID>:<CTAG>; where: • |
|
Input Example |
CANC-USER-SECU:PETALUMA:CISCO10:100; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.14 CHG-ACCMD-<MOD_TACC>: Change Test Access Mode (DS1, DS3I, E1, E3, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
See Table 4-11 on page 4-5 for supported modifiers by platform.
This command changes the test access (TACC) mode for the circuit being tested. For more information on TACC, refer to the "Test Access" section on page 1-21.
This may be a change from monitoring the data to inserting data into the STS. This command can only be applied to an existing TAP connection.
For this command to be applicable, you must first create the TAP using the ED-<MOD_PATH> command. Intrusive test access modes are traffic-affecting. If a facility/path is connected to a TAP in an intrusive test access mode, it is forced to go into the OOS-MT state. The forced transition could be traffic-affecting. The present state of the facility/path is stored by the NE and is restored when the TAP connection is brought down. Test access connections are dropped automatically if the TL1 session is terminated or is timed out.
Notes:
1. If there is no TAP connection, a DENY error message is returned.
2. If a requested condition already exists, a SRCN error message is returned.
3. If a requested access configuration is invalid, a SRAC error message is returned
4. If a requested TAP does not exist, a RTEN error message is returned.
|
|
|
|
|---|---|---|
Category |
Test Access |
|
Security |
Maintenance |
|
Related Messages |
|
|
Input Format |
CHG-ACCMD-<MOD_TACC>:[<TID>]:<TAP>:<CTAG>::<MD>; where: • Note • |
|
Input Example |
CHG-ACCMD-STS1:CISCO:8:123::MONE; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.15 CONN-TACC-<MOD_TACC>: Connect Test Access (DS1, DS3I, E1, E3, STS1, STS12C, STS192C, STS24C, STS3C, STS48C, STS6C, STS9C, T1, T3, VT1, VT2)
See Table 4-11 on page 4-5 for supported modifiers by platform.
This command connects the STS or VT defined by AID to the STS specified by the TAP number. For more information on TACC, refer to the "Test Access" section on page 1-21.
For this command to be applicable, you must first create the TAP using the ED-<MOD_PATH> command. Intrusive test access modes are traffic-affecting. If a facility/path is connected to a TAP in an intrusive test access mode, it is forced to go into the OOS-MT state. The forced transition could be traffic-affecting. The present state of the facility/path is stored by the NE and is restored when the TAP connection is brought down. Test access connections are dropped automatically if the TL1 session is terminated or is timed out.
Notes:
1. If all TAPs are busy, a RABY error message is returned.
2. If a requested TAP is busy, a RTBY error message is returned.
3. If a requested TAP does not exist, a RTEN error message is returned.
4. If a circuit is already connected to another TAP, a SCAT error message is returned.
5. If a requested condition already exists, a SRCN error message is returned.
6. If the AID is invalid, an IIAC (Input, Invalid Access Identifier) error message is returned.
7. If an access is not supported, an EANS error message is returned.
8. If a requested access configuration is invalid, a SRAC error message is returned.
9. A connection can be made to a cross-connection in which case all modes of access are supported. A connection to an Unmapped AID (AID without a cross-connect on it) will allow only MONE, SPLTE, and LOOPE modes.
10. A connection to the protect path of a 1+1, 1:1, or 1:N is not allowed; however, connecting to the PCA path of a two-fiber or four-fiber is supported. This will be preempted when a BLSR switch occurs.
|
|
|
|
|---|---|---|
Category |
Test Access |
|
Security |
Provisioning |
|
Related Messages |
CHG-ACCMD-<MOD_TACC> |
|
Input Format |
CONN-TACC-<MOD_TACC>:[<TID>]:<SRC>:<CTAG>::<TAP>:MD=<MD>; where: • • • |
|
Input Example |
CONN-TACC-STS1:CISCO:STS-2-1-4:123::8:MD=MONE; |
|
Output Format |
SID DATE TIME where: • |
|
Output Example |
TID-000 1998-06-20 14:30:00 |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.16 COPY-IOSCFG: Copy IOS Config File
(Cisco ONS 15454 only)
This command supports the following types of operations on the IOS configuration file of ML-series Ethernet cards:
1. Uploading of startup IOS configuration file from the network to the node.
FTP is the only protocol allowed for uploading. When doing this operation, the SRC field must be a FTP URL string specifying the user name and password for FTP authentication, and specifying the host and the directory to locate the startup config file from the network. The DEST field must be a string of "STARTUP".
2. Downloading of startup IOS configuration file from the node to the network.
FTP is the only protocol allowed for downloading. When doing this operation, the SRC field must be a string of "STARTUP". The DEST field must be a FTP URL string specifying the user name and password for FTP authentication, and specifying the host and the directory to store the startup config file.
Notes:
1. The IOS configuration file is unique for each ML-series card, and is specified by the SLOT number in the AID field of the command.
2. In the GNE/ENE environment, if the GNE firewall exists, the download (backup) of IOS configuration file via TL1 is not allowed. Any such attempt will receive a "Data Connection Error" from the GNE. For the upload of IOS configuration file via TL1, GNE will allow it to go through the firewall only if the file contains the header "! Cisco IOS config <text>". If the configuration file does not contain this header, GNE will block the uploading with "Data Connection Error".
3. The format of the FTP URL string used in the SRC or DEST field of the command is as follows:
In a non-firewall environment, the format of the URL should be
"FTP://[FTPUSER[:FTPPASSWORD]]@FTPHOST/PACKAGE_PATH" where:
<FTPUSER> is the userid to connect to the computer with the package file
<FTPPASSWORD> is the password used to connect to the computer with the package file
<FTPHOST> is the IP address of the computer with the package file, DNS lookup of hostnames is not supported
<PACKAGE_PATH> is the long path name to the package file
Note Note that USERID and PASSWORD are optional if the user does not need to log into the host computer. Also note that the password may be optional if the user does not need to log in. All the other portions of the URL are required, including the initial "FTP:\\" string.
In a firewall environment, the hostname should be replaced with a list of IP addresses each separated by a @ character. The first IP address should be for the machine where the package file is stored. Subsequent IP addresses should then be for firewall machines moving outwards towards the edge of the network, until the final IP address listed was the machine that outside users first access the network.
For example: if your topology is "FTPHOST <-> GNE3 <->GNE2 <-> GNE1 <-> ENE", your FTP URL will be: FTP://FTPUSER:FTPPASSWORD@FTPHOST@GNE3@GNE2@GNE1/PACKAGE_PATH
|
|
|
|
|---|---|---|
Category |
IOS |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
COPY-IOSCFG:[<TID>]:<AID>:<CTAG>::SRC=<SRC>,DEST=<DEST>; where: • • • |
|
Input Example |
COPY-IOSCFG::SLOT-1:CTAG::SRC="LONG_FTP_PATH",DEST="STARTUP"; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.17 COPY-RFILE: Copy RFILE
This command downloads a new software package from the location specified by the FTP URL. It is also used to backup and restore the system database.
In order to upload package files or restore databases from a host, the host must be running an FTP server application. If the host is not running an FTP server application, the command fails indicating that the NE was unable to connect to the remote IP address (host). A host can either be a PC or a workstation running an FTP Server Application.
•Userid is the userid to connect to the computer with the package file or system database.
•Password is the password used to connect to the computer with the package file or system database.
Note Both the userid and password are optional if the user does not need to log into the host computer. The password may be optional if the user does not need to log in.
•Hostname is the hostname or IP address of the computer with the package file or system database.
•Package_path is the long path name to the package file or system database.
All the other portions of the URL are required, including the initial "FTP://" string.
Example:
COPY-RFILE:TID:RFILE-PKG:703::TYPE=SWDL,SRC="FTP://USERID:
PASSWORD@HOSTIP:21/DIR1/DIR2/DIR3/PACKAGE.PKG";
Notes:
1. The SWDL type is used for software package uploads. The RFBU type is used for system database backups, and the RFR type is used for system database restores. The SRC input is required when the type is SWDL or RFR. The DEST input is needed when the type is RFBU. The SRC and DEST inputs cannot both be used in the same command.
2. FTP is the only allowed file transfer method.
3. The extended FTP URL syntax is required by the COPY-RFILE syntax.
4. Port number (21) is optional. 21 is the only supported Port Number. Leaving this field blank defaults to 21.
|
|
|
|
|---|---|---|
Category |
File Transfer |
|
Security |
Superuser |
|
Related Messages |
|
|
Input Format |
COPY-RFILE:[<TID>]:[<SRC>]:<CTAG>::TYPE=<XFERTYPE>, where: • • • – – – – Note In a firewall environment, the hostname should be replaced with a list of IP addresses each separated by a @ character. The first IP address should be for the machine where the package file is stored. Subsequent IP addresses should then be for firewall machines moving outwards towards the edge of the network, until the final IP address listed is the machine that outside users first access the network. |
|
Input Format (continued) |
For example, if the topology is "FTP_HOST_IP <-> GNE3 <->GNE2 <-> GNE1 <-> ENE", the FTP URL is: FTP://FTP_USER:FTP_PASSWORD@FTP_HOST_IP@GNE3@GNE2@ <SRC1> is a string. • • |
|
Input Example |
COPY-RFILE:HERNDON:RFILE-PKG:703::TYPE=SWDL, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.18 DISC-TACC: Disconnect Test Access
This command disconnects the TAP and puts the connection back to its original state (no splits). For more information on TACC, refer to the "Test Access" section on page 1-21.
For this command to be applicable, you must first create the TAP using the ED-<MOD_PATH> command.
Notes:
1. If you send this command to an already disconnected connection, a SADC error message is returned.
2. If the system cannot release TAP, an SRTN error message is returned.
|
|
|
|
|---|---|---|
Category |
Test Access |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DISC-TACC:[<TID>]:<TAP>:<CTAG>; where: • Note |
|
Input Example |
DISC-TACC:CISCO:8:123; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.19 DLT-<MOD_RING>: Delete (BLSR)
This command deletes the BLSR of the NE.
Note ONS 15327 does not support four-fiber BLSR.
Error conditions:
1. If the system fails on getting IOR, a SROG (Status, Get IOR Failed) error message is returned.
2. If the AID is invalid, an IIAC (Invalid AID) error message is returned.
3. If the BLSR does not exist, a SRQN (BLSR Does Not Exist) error message is returned.
4. The ALL AID is invalid for this command.
5. The list AID format is supported in this release (R4.6).
6. The SROF (Facility Not Provisioned) or (Cannot Access BLSR) error message will be returned for the invalid query.
7. If the BLSR is in use, a SROF (BLSR In Use) error message is returned.
8. The SRQN (BLSR Deletion Failed) error message is returned for the invalid deletion query.
|
|
|
|
|---|---|---|
Category |
BLSR |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-<MOD_RING>:[<TID>]:<AID>:<CTAG>[:::]; where: • |
|
Input Example |
DLT-BLSR:PETALUMA:BLSR-2:123; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.20 DLT-CRS-<PATH>: Delete Cross Connection (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
See Table 4-11 on page 4-5 for supported modifiers by platform.
This command deletes a cross-connection between STS and VT paths. STS paths are specified using their STS AID.
Notes:
1. The fields after CTAG (trailing colons) are optional.
2. For the 1-way cross-connections the AIDs must be in the same order as originally entered; for the 2-way cross-connections, either order will work.
3. This command does not support deleting multiple STS cross-connections.
4. Using "&" in the AID field of this command can delete an path protection STS cross-connection.
a. The following command is used to delete a 1-way selector or 2-way selector and bridge with:
from points: F1, F2
to points: T1
DLT-CRS-{STS_PATH}:[<TID>]:F1&F2,T1:<CTAG>;
b. The following command is used to delete a 1-way bridge or 2-way selector and bridge with:
from point: F1
to points: T1, T2
DLT-CRS-{STS_PATH}:[<TID>]:F1,T1&T2:<CTAG>;
c. The following command is used to delete a 1-way or 2-way subtending path protection connection with:
from point: F1, F2
to points: T1, T2
DLT-CRS-{STS_PATH}:[<TID>]:F1&F2,T1&T2:<CTAG>;
d. 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,STS3C", the deletion command with the AID format (F1&F2,T1) is required to delete this cross-connection.
e. The following command is used to create a path protection IDRI Cross-Connection:
ENT-CRS-{STS_PATH}:[<TID>]:A&B,C&D:<CTAG>::2WAYDC;
A-Path on ring X to which traffic from ring Y is bridged
B-Path on ring X to which traffic from the same ring is bridged
C-Path on ring Y to which traffic from ring X is bridged
D-Path on ring Y to which traffic from the same ring is bridged
A, B, C, and D have a positional meaning. Connection type 2WAYDC is used for path protection IDRI cross-connections.
f. The following command is used to create a path protection DRI Cross-Connection:
ENT-CRS-{STS_PATH}:[<TID>]:A&B,C:<CTAG>::2WAYDC;
A-Path on ring X to which traffic from ring Y is bridged
B-Path on ring X to which traffic from the same ring is bridged
C-Traffic to and from ring Y
A, B, C, and D have a positional meaning. Connection type 2WAYDC is used for path protection DRI cross-connections.
5. All A&B AIDs in the TL1 cross-connection command are in the format of WorkingAID&ProtectAID.
6. You can experience some implementation behavior problems if additional drops have been added to the connection object.
7. The facility AID is only valid for slots holding the G1000-4 card.
8. The virtual facility AID (VFAC) is only valid on slots holding an ML-series card.
9. A TL1 cross-connect that has been upgraded to a CTC circuit can no longer be managed by TL1. For example, if you issue a DLT-CRS-<PATH> command to delete a circuit, you will see that the circuit still appears in CTC as "incomplete". The reason for this is because in addition to creating cross-connects (as TL1 does), CTC creates another object on the source node that stores network-level circuit attributes. CTC will continue to see that object after the cross-connect is deleted which is why it shows an incomplete circuit.
|
|
|
|
|---|---|---|
Category |
Cross Connections |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-CRS-<PATH>:[<TID>]:<SRC>,<DST>:<CTAG>[:::]; where: • • |
|
Input Example |
DLT-CRS-STS12C:VINBURG:STS-1-1-1,STS-12-1-1:102; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.21 DLT-EQPT: Delete Equipment
This command deletes a card from the NE.
This command removes the card type and attributes that were entered for a particular slot. If any facilities are assigned, they are deleted too. The command will be denied if the card is part of a protection group or has a cross-connect end-point.
To delete a card that is part of a protection group, it has to be removed from the protection group first using the ED-EQPT command.
Error conditions for deleting equipment may be:
1. If a card in a protection group that has a cross-connection, DCC or is a synchronization source, the SPLD (Equipment in use) error message will be returned.
2. If a card is not provisioned, an error message will be returned.
|
|
|
|
|---|---|---|
Category |
Equipment |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-EQPT:[<TID>]:<AID>:<CTAG>[:::]; where: • |
|
Input Example |
DLT-EQPT:SONOMA:SLOT-1:104; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.22 DLT-FFP-<OCN_TYPE>: Delete Facility Protection Group (OC3, OC12, OC48, OC192)
See Table 4-11 on page 4-5 for supported modifiers by platform.
This command deletes an OCN facility protection group in a 1+1 architecture.
Note If the protection group does not exist, an error message will be returned.
|
|
|
|
|---|---|---|
Category |
Facility Protection |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-FFP-<OCN_TYPE>:[<TID>]:<WORK>,<PROTECT>:<CTAG>[:::]; where: • • |
|
Input Example |
DLT-FFP-OC3:PETALUMA:FAC-2-1,FAC-1-1:1; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.23 DLT-FFP-CLNT: Delete Facility Protection Group Client
(Cisco ONS 15454 only)
This command deletes Y cable protection on client facilities.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-FFP-CLNT:[<TID>]:<WORKAID>,<PROTAID>:<CTAG>[:::]; where: • • |
|
Input Example |
DLT-FFP-CLNT:CISCO:FAC-1-1,FAC-2-1:100; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.24 DLT-LNK-<MOD2O>: Delete Optical Link (OCH, OMS, OTS)
(Cisco ONS 15454 only)
This command deletes an optical link between two optical connection points. Optical link is specified by using the AID of the involved Optical Connection points.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-LNK-<MOD2O>:[<TID>]:<FROM>,<TO>:<CTAG>; where: • • |
|
Input Example |
DLT-LNK-OMS:PENNGROVE:BAND-6-1-TX,BAND-13-1-RX:114; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.25 DLT-OSC: Delete OSC
(Cisco ONS 15454 only)
This command deletes the OSC group of the NE.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-OSC:[<TID>]:<AID>:<CTAG>; where: • |
|
Input Example |
DLT-OSC:PENNGROVE:OSC-1:114; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.26 DLT-UCP-CC: Delete Unified Control Plane Control Channel
(Cisco ONS 15454 only)
This command deletes a UCP IP control channel.
1. If you send this command to a control channel that is in use, a SRQN (Status, Invalid Request) error message is returned.
2. If sending this command to delete an SDCC IPCC with a complete result, the SDCC of the specified SONET line is deleted (or disabled) automatically with a DB change reporting (if the DB change report is enabled).
3. If sending this command to delete an IPCC which is in use by a UCP Interface, an SROF (Delete UCP IPCC Failed - Object Is In Use) error message is returned.
|
|
|
|
|---|---|---|
Category |
UCP |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-UCP-CC:[<TID>]:<AID>:<CTAG>[::::]; where: • |
|
Input Example |
DLT-UCP-CC:CISCO:CC-9:CTAG; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.27 DLT-UCP-IF: Delete Unified Control Plane Interface
This command deletes a UCP interface.
Note If the UCP interface is not found or in use, a SRQN (Status, Invalid Request) error message is returned.
|
|
|
|
|---|---|---|
Category |
UCP |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-UCP-IF:[<TID>]:<AID>:<CTAG>[::::]; where: • |
|
Input Example |
DLT-UCP-IF:CISCO:FAC-2-1:CTAG; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.28 DLT-UCP-NBR: Delete Unified Control Plane Neighbor
This command deletes a UCP neighbor.
Notes:
1. If the neighbor is in use, an SRQN (Status, Invalid Request) error message is returned.
2. If sending this command to delete a neighbor which is in use by IPCC, an SROF (Delete UCP neighbor Failed - Object Is In Use) error message is returned.
|
|
|
|
|---|---|---|
Category |
UCP |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-UCP-NBR:[<TID>]:<AID>:<CTAG>[::::]; where: • |
|
Input Example |
DLT-UCP-NBR:CISCO:NBR-8:CTAG; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.29 DLT-USER-SECU: Delete User Security
This command deletes a user and can only be performed by a Superuser. Privilege levels are described in the ENT-USER-SECU command.
This command cannot be used to delete a user that is currently logged on.
For the DLT-USER-SECU command:
DLT-USER-SECU:[TID]:<UID>:[CTAG];
the syntax of <UID> is not checked. The user is deleted if the <UID> exists in the database.
|
|
|
|
|---|---|---|
Category |
Security |
|
Security |
Superuser |
|
Related Messages |
|
|
Input Format |
DLT-USER-SECU:[<TID>]:<UID>:<CTAG>; where: • Note |
|
Input Example |
DLT-USER-SECU:PETALUMA:CISCO15:123; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.30 DLT-VCG: Delete Virtual Concatenated Group
(Cisco ONS 15454 only)
This command deletes a VCG object.
|
|
|
|
|---|---|---|
Category |
VCAT |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-VCG:[<TID>]:<SRC>:<CTAG>:::[CMDMDE=<CMDMDE>][:]; where: • • |
|
Input Example |
DLT-VCG:NODE1:FAC-1-1:1234:::CMDMDE=FRCD; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.31 DLT-WLEN: Delete Wavelength
(Cisco ONS 15454 only)
This command deletes the provisioned wavelength (WLEN).
Note:
1. The fields after CTAG (trailing colons) are the optional.
2. This command does not support multiple deleting WLEN provisioning.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
DLT-WLEN:[<TID>]:<AID>:<CTAG>[:::CMDMDE=<CMDMDE>]; where: • • |
|
Input Example |
DLT-WLEN:PENNGROVE:WLEN-W_E-1530.33:114:::CMDMDE=NORM; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.32 ED-<MOD_PATH>: Edit (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS48C, STS192C, VT1, VT2)
This command edits the attributes associated with STS and VT paths.
The SFBER, SDBER, RVRTV, and RVTM parameters only apply to path protection.
The path trace message is a 64 character string including the terminating CR (carriage return) and LF (line feed) that is transported in the J1 byte of the SONET STS Path overhead. Both the EXPTRC and TRC string can be provisioned by user with up to 62 character string.
The EXPTRC indicates the contents of the expected incoming path trace are provisioned by the user. The TRC indicates the contents of the outgoing path trace message. The INCTRC indicates the contents of the incoming path trace message.
The path trace mode has three modes: OFF, MANUAL, and AUTO. The path trace mode defaults to OFF. The MANUAL mode performs the comparison of the received string with the user-entered expected string. The AUTO mode performs the comparison of the present received string with an expected string set to a previously received string. If there is a mismatch, TIM-P alarm is raised. When the path trace mode is in OFF mode, there is no path trace processing, and all the alarm and state conditions are reset.
The TACC parameter edits an existing single STS or VT and changes it to a test access point. When an editing command on TACC is executed, it assigns the STS for the first 2-way connection and STS=1 as the second 2-way connection. For STS3C and STS12C, the next available STS of the same width is chosen. For more information on TACC, refer to the "Test Access" section on page 1-21.
J1 is implemented on the DS1/DS1N, DS3E/DS3NE, DS3XM, EC1, OC3, OC12, OC48AS and OC192 cards.
DS3/DS3N, OC48, E100, and E1000 cards do not support path trace.
DS1/DS1N, DS3E/DS3NE, and DS3XM support both TRC and EXPTRC in the ED-STS-PATH command.
EC1, OC3, OC48AS, and OC192 only support EXPTRC in the ED-STS-PATH command.
Note Each TL1 command must be less than or equal to 255 characters. Any command larger than 255 characters must be split into multiple commands. For example, if you use the ED-<MOD_PATH> command to edit the J1 EXPTRC/TRC message, path protection attributes, and TACC attributes and the command exceeds 255 characters the command will not be processed. You must use multiple ED-<MOD_PATH> commands instead.
Error conditions:
1. If sending this command to edit SFBER or SDBER or RVRTV or RVTM for the non-path protection STS path, an error message will be returned.
2. If sending this command to edit the EXPTRC string with the AUTO path trace mode (TRCMODE=AUTO), an error message will be returned.
3. If sending this command to edit TRC on any card other than DS3(N)E, DS1(N), and DS3XM cards, an error message (TRC-not allowed for monitor paths. Incorrect card type.) will be returned.
4. This command is allowed to edit EXPTRC on DS1(N), DS3(N)E, DS3XM, EC1, OC3, OC48AS, and OC192 cards.
5. If sending this command to edit both TACC and any other attribute(s), the (Parameters Not compatible) error message will be returned.
6. If sending this command to edit TACC on an AID with cross-connections, an error message (STS in Use) will be returned.
7. TACC creation will also be denied on the protect ports/cards for 1:1, 1:N, and 1+1.
8. The VFAC AID is only valid on slots containing an ML1000-2 or ML100T-12 card. TACC is not supported for the ML1000-2 or ML100T-12 cards.
9. After the BLSR switching, provisioning of the J1 trace string or trace mode is not allowed on the protection path.
10. TACC creation is allowed on PCA for two-fiber and four-fiber BLSR.
11. TACC is not supported on G1000, MXP_2.5_10G/TXP_MR-10G, ML1000-2 and ML100T-12 cards.
12. HOLDOFFTIMER is not specific to a path. It is applicable to the path protection selector. If HOLDOFFTIMER is changed on one path associated with the selector, the HOLDOFFTIMER of the other path associated with the same selector is also changed.
|
|
|
|
|---|---|---|
Category |
Paths |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-<MOD_PATH>:[<TID>]:<AID>:<CTAG>:::[SFBER=<SFBER>,] where: • • • • • • • • • • • • • • |
|
Input Example |
ED-STS3C:FERNDALE:STS-2-1-4:115:::SFBER=1E-3,SDBER=1E-5, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.33 ED-<MOD_RING>: Edit Bidirectional Line Switched Ring
This command edits the BLSR attributes.
Notes:
1. ONS 15327 does not support four-fiber BLSR.
2. Only the RVRTV, RVTM, SRVRTV, SRVTM attributes can be edited for the 4-Fiber BLSR.
3. Only the RVRTV and RVTM attributes can be edited for the 2-Fiber BLSR.
Error conditions:
1. If the system fails on getting IOR, a SDBE (Status, Internal Data Base Error) error message will be returned.
2. If the AID is invalid, an IIAC (Invalid AID) error message is returned.
3. If the BLSR does not exist, a SRQN (BLSR Does Not Exist) error message is returned.
4. The ALL AID is invalid for this command.
5. The list AID format is supported in this release (R4.6).
6. The SROF (Facility Not Provisioned) or Cannot Access BLSR) error message will be returned for the invalid query.
7. The SRQN (BLSR Edition Failed) error message is returned for the invalid edition query.
8. If sending this command to modify SRVRTV or SRVTM on a two-fiber BLSR, an IDNV (Invalid Data For 2F-BLSR) error message will be returned.
9. Is sending this command to modify the nodeid with invalid data, an IIAC (Invalid NodeId) error message is returned.
10. If sending this command to change the ringid into invalid data, an IIAC (Invalid RingId) error message is returned.
11. If changing the BLSR nodeid with a duplicated ID, a SROF (Cannot Set NodeId) error message is returned.
12. If changing the BLSR ringid with a duplicated ID, a SROF (Cannot Set RingId) error message is returned.
|
|
|
|
|---|---|---|
Category |
BLSR |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-<MOD_RING>:[<TID>]:<AID>:<CTAG>:::[RINGID=<RINGID>,] where: • • • • • • • |
|
Input Example |
ED-BLSR:PETALUMA:BLSR-43:123:::RINGID=43,NODEID=3,RVRTV=Y, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.34 ED-<OCN_TYPE>: Edit (OC3, OC12, OC48, OC192)
See Table 4-11 on page 4-5 for supported modifiers by platform.
This command edits the attributes (i.e., service parameters) and state of an OC-N facility. Allowable states for a facility are Out Of Service (OOS), Out Of Service with Automatic In Service transitioning (OOS-AINS), Out Of Service for Maintenance (OOS-MT), and In Service (IS).
The DCC transmit is bridged to both working and protect in a 1+1 configuration. On the receive side, the active one is selected for DCC. The DCC is provisioned on the working port only in a 1+1 configuration.
All lines in a 1+1 BLSR must have the same mode. If you change the mode of a line that is in a 1+1 BLSR, an error message will be returned.
UNI-C DCC provisioning notes:
1. The attributes DCC(Y/N) and mode (SONET/SDH) remain the same in the ED/RTRV-OCN commands when the DCC is used for UNI-C, in which case the port attribute UNIC is enables (UNIC=Y).
2. UNI-C DCC termination cannot be deleted by the regular DCC de-provisioning command.
3. If the DCC is created under regular SONET provisioning, and this port is used by UNI-C, the port is converted as a UNI-C DCC automatically.
4. De-provisioning UNI-C IF/IB IPCC will free up DCC termination automatically.
5. The parameters ALSMODE, ALSCRINT and ALSRCPW are valid only for OC3-8, OC-192, and OC48ELR cards.
|
|
|
|
|---|---|---|
Category |
Ports |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>:::[DCC=<DCC>,] where: • • • • • • • • • • • • • • • |
|
Input Format (continued) |
• • • • |
|
Input Example |
ED-OC48:PENNGROVE:FAC-6-1:114:::DCC=Y,AREA=10.92.63.1, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.35 ED-BITS: Edit Building Integrated Timing Supply
This command edits the BITS reference attributes.
Note SYNC-BITS1 and SYNC-BITS2 AIDs can be used for setting the port state of BITS-OUT ports.
|
|
|
|
|---|---|---|
Category |
Synchronization |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-BITS:[<TID>]:<AID>:<CTAG>:::[LINECDE=<LINECDE>,][FMT=<FMT>,] where: • • • • • • • • • |
|
Input Example |
ED-BITS:SONOMA:BITS-2:779:::LINECDE=AMI,FMT=ESF,LBO=0-133, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.36 ED-CLNT: Edit Client
(Cisco ONS 15454 only)
This command edits client facility attributes.
Note Primary=OOS and secondary=AINS states do not apply to Ethernet mode.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-CLNT:[<TID>]:<AID>:<CTAG>:::[NAME=<PORTNAME>,] where: • • • • • • • • • • |
|
Input Format (continued) |
• • • • • • |
|
Input Example |
ED-CLNT:CISCO:FAC-1-1:100:::NAME="NY PORT",SFBER=1E-4,SDBER=1E-5,ALSMODE=Y,ALSRCINT=30, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.37 ED-CMD-SECU: Edit Command Security
This command edits the command security level of a particular command.
|
|
|
|
|---|---|---|
Category |
Security |
|
Security |
Administrator |
|
Related Messages |
ENT-USER-SECU |
|
Input Format |
ED-CMD-SECU:[<TID>]:<AID>:<CTAG>::<CAP>; where: • • |
|
Input Example |
ED-CMD-SECU::INIT-REG:1::SU; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.38 ED-CRS-<PATH>:ED Cross Connect (STS1, STS3C, STS6C, STS9C, STS12C, STS24C, STS 48C, STS192C, VT1, VT2)
This command edits the state of an STS or VT cross-connection.
See Table 4-11 on page 4-5 for supported modifiers by platform.
|
|
|
|
|---|---|---|
Category |
Cross Connections |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-CRS-<PATH>:[<TID>]:<SRC>,<DST>:<CTAG>:::[ADD=<ADD>,] where: • • • • • • |
|
Input Example |
ED-CRS-STS3C::STS-1-1-1,STS-2-1-1:1:::ADD=STS-13-1-1, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.39 ED-DAT: Edit Date and Time
This command edits the date and the time
|
|
|
|
|---|---|---|
Category |
System |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-DAT:[<TID>]::<CTAG>::[<DATE>],[<TIME>]; where: • • |
|
Input Example |
ED-DAT:CISCO::1234::99-12-21,14-35-15; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.40 ED-DS1: Edit DS1
(Cisco ONS 15454 only)
This command edits the test access attribute for DS1 access on a DS3XM card.
Note This command is not allowed if the card is a protecting card.
|
|
|
|
|---|---|---|
Category |
Ports |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-DS1:[<TID>]:<AID>:<CTAG>:::[TACC=<TACC>,] where: • • • |
|
Input Example |
ED-DS1:PETALUMA:DS1-2-1-6-12:123:::TACC=8,TAPTYPE=DUAL; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.41 ED-DWDM: Edit Dense Wavelength Division Multiplexing
(Cisco ONS 15454 only)
The command edits an already pre-provisioned/provisioned MXP_2.5G_10G/TXP_MR_10G card. It changes the operating parameters for the card.
The rules for provisioning a regeneration group are: a regeneration group can be created only between a pair of TXP cards. The peer slot should contain a card of the same type, and should not have an existing regeneration group for the same slot. The termination mode should be identical for the cards. All the client port level settings should be identical for the cards. Setting the PEERID=Null will remove an existing regeneration group. The two TXP cards should be set to transparent termination mode to successfully create a regeneration group.
The rules for provisioning the payload field are as follows: For a TXP_MR_10G card, the SONET/10GE (Ethernet) applies. For a TXP_MR_2.5G card or TXPP_MR_2.5G card, the options of SONET/10GE are not applicable. Instead, the actual protocol; for example, OC3/OC12/OC48/STM1 should be used. The port has to be in OOS state for a payload change to be successful. There should be no Trace enabled for the port. To set the Payload to 10GE, the termination mode should already be in Transparent mode.
The MXP_2.5_10G card does not support 10GE payload. To change the payload type for the MXP_2.5_10G card, all the ports should be in OOS state.
See the "Provisioning Rules for MXP_2.5G_10G and TXP_MR_10G Cards" section on page 1-8 and "Provisioning Rules for TXP_MR_2.5G and TXPP_MR_2.5G Cards" section on page 1-13 for specific card provisioning rules.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-DWDM:[<TID>]:<AID>:<CTAG>:::[PEERID=<PEERID>,] where: • • • • • • |
|
Input Example |
ED-DWDM:VA454-22:SLOT-1:100:::PEERID=SLOT-2, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.42 ED-EC1: Edit Electrical Carrier
(Cisco ONS 15454 only)
This command edits the attributes of an EC1.
Note This command is not allowed if the card is a protecting card.
|
|
|
|
|---|---|---|
Category |
Ports |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-EC1:[<TID>]:<AID>:<CTAG>:::[PJMON=<PJMON>,][LBO=<LBO>,] where: • • • • • • • • |
|
Input Example |
ED-EC1:CISCO:FAC-1-1:123:::PJMON=0,LBO=0-225,SOAK=10,SFBER=1E-4, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.43 ED-EQPT: Edit Equipment
This command edits the attributes for a given equipment slot in the NE. If the card is in an equipment slot, this command is allowed only on the working AID.
The PROTID parameter indicates the unique identifier of the protection group (the protect card). "NULL" is a special value of the PROTID parameter and indicates absence of a protection group. For 1:1 protection type, RVRTV and RVTM parameters can be changed. For 1:1 protection type, if the PROTID parameter is entered as "NULL", the protection group is deleted.
ED-EQPT:[<TID>]:SLOT-2:<CTAG>:::PROTID=NULL;
For 1:N protection type, if the PROTID is "NULL", the AIDs in the list are removed from the protection group. If all the working cards are in the AID list, the protection group is deleted.
Example: if Slot-1, Slot-2 and Slot-4 were the only working cards in the protection group. The following command will remove Slot-4 from the protection group:
ED-EQPT:[<TID>]:SLOT-4:<CTAG>:::PROTID=NULL;
The protection group still has Slot-1 and Slot-2 as working cards.
The following command will remove all the other working cards in the above example and consequently, delete the protection group itself:
ED-EQPT:[<TID>]:SLOT-2&SLOT-1:<CTAG>:::PROTID=NULL;
The ED-EQPT command can be successfully executed on an already provisioned card to add a working card to or remove one from a protection group. This command is not valid on a protect card. Only cards can be added to or removed from a protection group. Protection type is immutable and is determined at the time of creation of a protection group (while adding the first working card). Once provisioned, the equipment type cannot be edited either.
Examples of adding an existing card to a protection group using the ED-EQPT command:
1:1 protection group
ED-EQPT::SLOT-2:12:::PROTID=SLOT-1,RVRTV=Y,RVTM=9.0;
1:N protection group
ED-EQPT::SLOT-2:12:::PROTID=SLOT-3,PRTYPE=1-N,RVTM=6.5;
Error conditions for editing a 1:1 or 1:N protection group may be:
1. Editing the PRTYPE or PROTID (non-NULL value) parameters.
2. Editing RVRTV or RVTM when no protection group exists.
3. Editing RVRTV for 1:N protection.
4. Failed to remove, currently switched to protect.
5. If the command mode (CMDMDE) is set to forced (FRCD) during the creation of a 1:1 or 1:N protection group, all cards must be physically plugged in and in the ready state (IS). If the cards are not physically plugged in, then the command is denied with an appropriate error message. When the command mode is set to normal (NORM) (which is the default) the cards do not have to be physically plugged in and in the ready state.
6. If the command mode is set to forced (FRCD) during the removal of a card in a 1:1 or 1:N protection group, there must be no cross-connects (i.e., services) present on the card. If there are cross-connects present on the card, the command is denied with an appropriate error message. If the command mode is set to normal (NORM) (which is the default), it does not require that cross-connects be deleted on the card.
|
|
|
|
|---|---|---|
Category |
Equipment |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-EQPT:[<TID>]:<AID>:<CTAG>:::[PROTID=<PROTID>,] where: • • • • • • |
|
Input Example |
ED-EQPT:CISCO:SLOT-2:123:::PROTID=SLOT-1,PRTYPE=1-1,RVRTV=Y, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.44 ED-FC: Edit Fiber Channel Facility
This command edits the attributes related to the fiber channel facility.
Note The OOS,AINS is not supported on the FC port.
|
|
|
|
|---|---|---|
Category |
Ports |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-FC:[<TID>]:<AID>:<CTAG>:::[PAYLOAD=<PAYLOAD>,] where: • • • • • |
|
Input Example |
ED-FC:CISCO1:FAC-6-1:1:::PAYLOAD=2GFC,LINKRCVRY=Y:OOS,MT; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.45 ED-FFP-<OCN_TYPE>: Edit Facility Protection Group (OC3, OC12, OC48, OC192)
See Table 4-11 on page 4-5 for supported modifiers by platform.
This command edits the optical facility protection.
Note This command can be used on both protecting and working AIDs.
|
|
|
|
|---|---|---|
Category |
SONET Line Protection |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-FFP-<OCN_TYPE>:[<TID>]:<AID>:<CTAG>:::[PROTID=<PROTID>,] where: • • • • • |
|
Input Example |
ED-FFP-OC3:PETALUMA:FAC-1-1:1:::PROTID=PROT_NAME,RVRTV=Y, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.46 ED-FFP-CLNT: Edit Facility Protection Group Client
(Cisco ONS 15454 only)
This command edits a Y cable protection group on client facilities.
See the "Provisioning Rules for MXP_2.5G_10G and TXP_MR_10G Cards" section on page 1-8 and the "Provisioning Rules for TXP_MR_2.5G and TXPP_MR_2.5G Cards" section on page 1-13 for specific card provisioning rules.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-FFP-CLNT:[<TID>]:<AID>:<CTAG>:::[PROTID=<PROTID>,] where: • • • • • |
|
Input Example |
ED-FFP-CLNT:CISCO:FAC-1-1:100:::PROTID=DC-METRO,RVRTV=N, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.47 ED-FFP-OCH: Edit Facility Protection Group OCH
(Cisco ONS 15454 only)
This command changes the provisioning for the default protection group on the DWDM port of a TXP_MR_2.5G and TXPP_MR_2.5G card.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-FFP-OCH:[<TID>]:<AID>:<CTAG>:::[PROTID=<PROTID>,] where: • • • • • |
|
Input Example |
ED-FFP-OCH:VA454-22:CHAN-2-2:100:::PROTID="FIXED PROTECTION",RVRTV=N,RVTM=1.0,PSDIRN=BI; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.48 ED-G1000: Edit G1000
This command edits the attributes related to a G1000 port.
Note The state OOS-AINS is not supported on the G1000.
|
|
|
|
|---|---|---|
Category |
Ports |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-G1000:[<TID>]:<AID>:<CTAG>:::[MFS=<MFS>,][FLOW=<FLOW>,] where: • • • • • • • |
|
Input Example |
ED-G1000:TID:FAC-1-1:CTAG:::MFS=1548,FLOW=Y,LOWMRK=20, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.49 ED-LNK-<MOD2O>: Edit Link (OCH, OMS, OTS)
(Cisco ONS 15454 only)
This command edits an optical link state.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-LNK-<MOD2O>:[<TID>]:<FROM>,<TO>:<CTAG>::::<PST>,[<SST>]; where: • • • • |
|
Input Example |
ED-LNK-OMS:PENNGROVE:BAND-6-1-TX,BAND-13-1-RX:114::::OOS,AINS; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.50 ED-NE-GEN: Edit Network Element General
This command edits the node attributes of the NE.
Notes:
1. Only the IPADDR, IPMASK, DEFRTR, IIOP PORT and node name can be modified with this command.
2. The node name can be a maximum of 20 characters. If the entered name exceeds 20 characters, an IPNV (Node Name Too Long) error message is returned.
3. An existing timing source can be removed by setting the address to 0.0.0.0.
Changing the IPADDR, IPMASK, or IIOP Port will cause a reset of the TCC2.
|
|
|
|
|---|---|---|
Category |
System |
|
Security |
Superuser |
|
Related Messages |
|
|
Input Format |
ED-NE-GEN:[<TID>]::<CTAG>:::[NAME=<NAME>,][IPADDR=<IPADDR>,] where: • • • • • • |
|
Input Example |
ED-NE-GEN:CISCO::123:::NAME=NODENAME,IPADDR=192.168.100.52, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.51 ED-NE-PATH: Edit Network Element Paths
This command edits the path attributes of the NE.
|
|
|
|
|---|---|---|
Category |
System |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-NE-PATH:[<TID>]::<CTAG>[:::PDIP=<PDIP>]; where: • |
|
Input Example |
ED-NE-PATH:::CTAG:::PDIP=Y; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.52 ED-NE-SYNCN: Edit Network Element Synchronization
This command edits the synchronization attributes of the NE.
Notes:
1. Although mixed mode timing is supported in this release, it is not recommended. See the "Mixed Mode Timing Support" section on page 1-19 for more information.
2. The existing external and line modes have the same functionality in all ONS 15454 4.x releases:
External mode: the node derives its timing from the BITS inputs.
Line mode: the node derives its timing from the SONET line(s).
Mixed mode: the node derives its timing from the BITS input or SONET lines.
|
|
|
|
|---|---|---|
Category |
Synchronization |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-NE-SYNCN:[<TID>]::<CTAG>:::[TMMD=<TMMD>,] where: • • • • • |
|
Input Example |
ED-NE-SYNCN:CISCO::123:::TMMD=LINE,SSMGEN=GEN1, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.53 ED-OCH: Edit Optical Channel
(Cisco ONS 15454 only)
This command edits the attributes (service parameters) and state of an OCH facility.
See the "Provisioning Rules for MXP_2.5G_10G and TXP_MR_10G Cards" section on page 1-8 and the "Provisioning Rules for TXP_MR_2.5G and TXPP_MR_2.5G Cards" section on page 1-13 for specific card provisioning rules.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-OCH:[<TID>]:<AID>:<CTAG>:::[RDIRN=<RDIRN>,] where: • • • • • • |
|
Input Format (continued) |
• • • • • • • • • • |
|
Input Format (continued) |
• • • • • • • • • • |
|
Input Example |
ED-OCH:CISCO:CHAN-6-2:114:::RDIRN=W-E,EXPWLEN=1530.32, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.54 ED-OMS: Edit Optical Multiplex Section
(Cisco ONS 15454 only)
This command edits the attributes (service parameters) and state of an OMS facility.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-OMS:[<TID>]:<AID>:<CTAG>:::[RDIRN=<RDIRN>,] where: • • • • • • • • • |
|
Input Example |
ED-OMS:PENNGROVE:BAND-6-1:114:::RDIRN=W-E, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.55 ED-OSC: Edit Optical Service Channel
(Cisco ONS 15454 only)
This command edits the OSC (optical service channel) group attributes.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-OSC:[<TID>]:<AID>:<CTAG>:::[RINGID=<RINGID>,] where: • • • |
|
Input Example |
ED-OSC:PENNGROVE:OSC-1:114:::RINGID=1,NODEID=10; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.56 ED-OTS: Edit OTS
(Cisco ONS 15454 only)
This command edits the attributes (service parameters) and state of an OTS facility.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-OTS:[<TID>]:<AID>:<CTAG>:::[RDIRN=<RDIRN>,] where: • • • • • • • • • • • • • |
|
Input Example |
ED-OTS:PENNGROVE:LINE-6-1:114:::RDIRN=W-E,VOAATTN=5.0, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.57 ED-PID: Edit Password
This command allows a user to change his or her own password.
Notes:
1. Passwords are masked for the following security commands: ACT-USER, ED-PID, ENT-USER-SECU and ED-USER-SECU. Access to a TL1 session via any means will have the password masked. The CTC Request History and Message Log will also show the masked commands. When a password-masked command is re-issued by double-clicking the command from CTC Request History, the password will still be masked in the CTC Request History and Message Log. The actual password that was previously issued will be sent to the NE. To use a former command as a template only, single-click the command in CTC Request History. The command will be placed in the Command Request text box, where you can edit the appropriate fields prior to re-issuing it.
2. The password will not appear in the TL1 log on the NE.
3. For the ED-PID command:
ED-PID:[TID]:<UID>:[CTAG]::<OLDPID>,<NEWPID>;
the syntax of <OLDPID> is not checked. The <NEWPID> is required to follow Telcordia standards (i.e., 10 characters maximum including 1 letter, 1 number, and any one of the following characters: #, %, or +). The <OLDPID> must match what is in the database.
|
|
|
|
|---|---|---|
Category |
Security |
|
Security |
Retrieve |
|
Related Messages |
|
|
Input Format |
ED-PID:[<TID>]:<UID>:<CTAG>::<OLDPID>,<NEWPID>; where: • • • Note |
|
Input Example |
ED-PID:CISCO:UID:123::OLDPWD,NEWPWD; |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.58 ED-SYNCN: Edit Synchronization
This command edits the synchronization reference list used to determine the sources for the NE's reference clock and the BITS output clock. For each clock, up to three synchronization sources may be specified (e.g., PRIMARY, SECOND, THIRD).To view or edit the system timing mode, use the RTRV-NE-SYNCN or ED-NE-SYNCN commands.
Note To retrieve/set the timing mode, SSM message Set or Quality of RES information, use the RTRV-NE-SYNCN and ED-NE-SYNCN commands.
|
|
|
|
|---|---|---|
Category |
Synchronization |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-SYNCN:[<TID>]:<AID>:<CTAG>:::[PRI=<PRI>,][SEC=<SEC>,] where: • • • • |
|
Input Example |
ED-SYNCN:BOYES:SYNC-NE:112:::PRI=INTERNAL,SEC=INTERNAL, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.59 ED-T1: Edit T1
This command edits the attributes related to a DS1/T1 port.
Notes:
1. The T1 facilities on the ONS 15327 are on the XTC card.
2. This command is not allowed if the card is a protecting card.
3. If sending this command to edit TACC and any other attribute(s), and the port having the cross-connection, the (Parameters Not compatible) error message will be returned.
4. Editing TACC via an ED-xxx command is only allowed when there is no circuit/cross-connection on this port and the port/VT does not have a test access point (TAP or TACC number). Otherwise, an error message (e.g. VT in Use) will be returned.
5. TACC creation will also be denied on the protect ports/cards.
|
|
|
|
|---|---|---|
Category |
Ports |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-T1:[<TID>]:<AID>:<CTAG>:::[LINECDE=<LINECDE>,][FMT=<FMT>,] where: • • • • • • • • • • • |
|
Input Example |
ED-T1:CISCO:FAC-2-1:1223:::LINECDE=AMI,FMT=ESF,LBO=0-131, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.60 ED-T3: Edit T3
This command edits the attributes related to a DS3/T3 port.
Notes:
1. T3 facilities on the ONS 15327 are on the XTC card.
2. This command is not allowed if the card is a protecting card.
3. Both FMT and Line code are not supported for T3/DS3 facility. They are supported on both the DS3XM and DS3E card. The unframed value of the framing format is only supported on the DS3E facility.
4. If sending this command to edit TACC and any other attribute(s), and the port having the cross-connection or the port/VT has a test access point (TAP or TACC number), the (Parameters Not compatible) error message will be returned.
5. Editing TACC via an ED-xxx command is only allowed when there is no circuit/cross-connection on the port and the port/VT does not have a test access point (TAP or TACC number). Otherwise, an error message (e.g. VT in Use) will be returned.
6. TACC creation will also be denied on the protect ports/cards.
7. Automatic application of loopbacks originating from the far end can be initiated on the T3 ports of a DS3E, DS3NE, or DS3XM card.
|
|
|
|
|---|---|---|
Category |
Ports |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-T3:[<TID>]:<AID>:<CTAG>:::[FMT=<FMT>,][LINECDE=<LINECDE>,] where: • • • • • • • • • • • • |
|
Input Example |
ED-T3:CISCO:FAC-1-2:123:::FMT=C-BIT,LINECDE=B3ZS,LBO=0-225, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.61 ED-TRC-CLNT: Edit Trace Client
(Cisco ONS 15454 only)
This command edits trace-related attributes on client facilities.
See the "Provisioning Rules for MXP_2.5G_10G and TXP_MR_10G Cards" section on page 1-8 and the "Provisioning Rules for TXP_MR_2.5G and TXPP_MR_2.5G Cards" section on page 1-13 for specific card provisioning rules.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-TRC-CLNT:[<TID>]:<SRC>:<CTAG>:::[EXPTRC=<EXPTRC>,] where: • • • • • • |
|
Input Example |
ED-TRC-CLNT:CISCO:FAC-6-1:10:::EXPTRC="AAA",TRC="AAA", |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.62 ED-TRC-OCH: Edit Trace Optical Channel Facilities
(Cisco ONS 15454 only)
The command edits trace-related optical channel facilities.
See the "Provisioning Rules for MXP_2.5G_10G and TXP_MR_10G Cards" section on page 1-8 and the "Provisioning Rules for TXP_MR_2.5G and TXPP_MR_2.5G Cards" section on page 1-13 for specific card provisioning rules.
|
|
|
|
|---|---|---|
Category |
DWDM |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-TRC-OCH:[<TID>]:<SRC>:<CTAG>:::[EXPTRC=<EXPTRC>,] where: • • • • • • |
|
Input Example |
ED-TRC-OCH:CISCO:CHAN-6-2:10:::EXPTRC="AAA",TRC="AAA", |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.63 ED-UCP-CC: Edit Unified Control Plane Control Channel
(Cisco ONS 15454 only)
This command edits UCP IP control channel attributes.
Notes:
1. If sending this command with invalid data, an IIAC (Status, Invalid Data) error message is returned.
2. If sending this command to provision MTU, CRCMD, or both while the IPCC type is routed (CCTYPE=ROUTED), an IIAC (Routed CC Is Not Allowed to Provision MTU & CRCMD) error message is returned.
|
|
|
|
|---|---|---|
Category |
UCP |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-UCP-CC:[<TID>]:<AID>:<CTAG>:::[LOCALIPCC=<LOCALIPCC>,] where: • • • • • • • |
|
Input Example |
ED-UCP-CC:CISCO:CC-9:CTAG:::LOCALIPCC=172.20.209.31, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.64 ED-UCP-IF: Edit Unified Control Plane Interface
(Cisco ONS 15454 only)
This command edits UCP interface attributes.
Note If you send invalid data with this command, an IIAC (Status, Invalid Data) error message is returned.
|
|
|
|
|---|---|---|
Category |
UCP |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-UCP-IF:[<TID>]:<AID>:<CTAG>:::[TNATYPE=<TNATYPE>,] where: • • • • |
|
Input Example |
ED-UCP-IF:CISCO:FAC-2-1:CTAG:::TNATYPE=IPV4, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.65 ED-UCP-NBR: Edit Unified Control Plane Neighbor
(Cisco ONS 15454 only)
This command edits a UCP neighbor.
The default value of the node name can be overwritten by the TL1 user to a string in a maximum size of 20 characters. If the node name includes non-identified TL1 characters (e.g. space), the text string format with the double quotes is required.
Example:
ENT-UCP-NBR::NBR-18:CTAG:::NBRIX=18,NODEID=192.168.101.18,
NAME=NeibhgorName,NDEN=N,HELLOEN=Y,HELLOINT=5, REFREDEN=Y;
Notes:
1. If this command is sent twice or input with invalid data, a SRQN (Status, Invalid Request) error message is returned.
2. If sending this command without neighbor node name in the "NAME" field, an IIAC (Neighbor Name Cannot Be Empty) error message is returned.
3. If sending this command to set the hello interval while the RSVP hello is disabled, an IIAC (HELLOINT Is Not Allowed If HELLOEN Is Disabled) error message is returned.
|
|
|
|
|---|---|---|
Category |
UCP |
|
Security |
Provisioning |
|
Related Messages |
|
|
Input Format |
ED-UCP-NBR:[<TID>]:<AID>:<CTAG>:::[NAME=<NAME>,] where: • • • • • |
|
Input Example |
ED-UCP-NBR:CISCO:NBR-8:CTAG:::NAME=NODE-B,HELLOEN=Y, |
|
Errors |
Errors are listed in Table 7-33 on page 7-27. |
|
3.4.66 ED-UCP-NODE: Edit Unified Control Plane Node
(Cisco ONS 15454 only)
This command edits the UCP node level attributes.
The nodeid is the unique number used to identify the local node in LMP, RSVP messages sent to the neighbors. It defaults to the local ethernet interface address (ISA).
The retry initial interval (in seconds) is used for that have been released by the net work side. This interval has a range of 60 seconds (1 minute) to 1800 seconds (30 minutes), with a default value of 180 seconds.
The retry max interval (in seconds) is used for released circuits. The node will back off exponentially from the initial retry interval to this maximum value of 600 seconds (10 minutes).
The restart time is used to be signaled to neighbors. It indicates the time taken by this node (in seconds) to restart. This timer has a range of 1 second to 10 seconds with a default of 5 seconds.
The recovery time is used to be signaled to neighbors. It indicates the time taken by this node (in seconds) to re-sync path, reservation state with a given neighbor. This timer has a range of 300 seconds (5 minutes) to 1800 seconds (30 minutes) and a default value of 600 seconds (10 minutes).
The transmit interval is used to retransmit un-acknowledged messages. This timer has a range of 1 second to 7 seconds with a default value of 1 second.
The refresh interval is used to refresh path, reservation state. This interval has a range of 30 seconds to 4060800 seconds (47 days) with a default value of 30 seconds.
The timeout RESV CONF interval is used to wait for a RESV CONF message in response to a RESV message. This interval has a range of 10-180 seconds with a default value of 60 seconds.
The Source Deletion in Progress is a timeout interval while the source is in the process of cleanly deleting a call. This interval has a range of 1--180 seconds with a default value of 60 seconds.
The Destination Deletion progress is a timeout interval while the destination is in the progress of cleanly deleting a call. This interval has a range of 1-180 seconds with a default value of 60 seconds.
Notes:
1. If the retry initial interval is set to zero, it will be interpreted as having the retry procedure disable.
2. The retry maximum interval has to be set to a higher value than the initial retry interval.
|
|
|
|
|---|---|---|