Specifications

4-19
Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide, R3.3
May 2002
Chapter 4 TL1 Command Components
Parameter Types
4.3.4 Parameter Notes
1. If a parameter is set to a value that is inconsistent with something already in the database, and that
value is not changed to a consistent value then the command will be denied.
2. If a parameter is set to a value that is consistent with what is already in the database, but another
parameter in the same command is incompatible, then the command will be denied.
3. The correct way to issue a command where parameters may be in conflict is to:
a. First issue that command and change all relevant parameters to compatible values,
b. Then issue the command again to change the target values.
For example, OC-N is syncmsg=y, to change SDH to y, ED-OCN needs to be called to set
syncmsg=N, then called again to set SDH=y.
4. The attribute defaults have also been presented under RTRV commands, and they can be retrieved
only if the RTRV commands follow the card/entity original provision.
5. The default for an optional field of an ED command is either the provisioned default value or the
last provisioned value in the previous ED command.
4.3.5 ALL_MONTYPE
Monitoring type list
Table 4-38 ALL_MONTYPE Values
ALL_MONTYPE
Values Description
AISSP Alarm Indication Signal Seconds - Path
CVCPP Coding Violations - CP-Bit Path
CVL Coding Violations - Line
CVP Coding Violations - Path
CVS Coding Violations - Section
CVV Coding Violations - Section
ESCPP Errored Seconds - CP- Bit Path
ESL Errored Seconds - Line
ESP Errored Seconds - Path
ESS Errored Seconds - Section
ESV Errored Seconds - VT Path
FCL Failure Count - Line
FCP Failure Count - Path
LOSSL Loss of Signal Seconds - Line
NPJC-PDET PPJC-PDET:Negative Pointer Justification
NPJC-PGEN PPJC-PGEN:Negative Pointer Justification
PPJC-PDET PPJC-PDET:Positive Pointer Justification