Table Of Contents
TL1 Performance Monitoring
6.1 Performance Monitoring by Card
6.2 PM Parameters by Line Type
6.3 Scheduled PM Report
6.3.1 Create a PM Schedule and Receive an Autonomous PM Report
6.3.2 Manage PM Schedules
6.3.3 Enable or Disable a TL1 Session to Receive Autonomous PM Reports
TL1 Performance Monitoring
Performance information is continuously monitored and stored in individual performance monitoring (PM) registers and can be retrieved upon request or when a preset threshold is exceeded. For more detailed information on performance monitoring, refer to the Cisco ONS 15454 Reference Guide and the Cisco ONS 15327 User Documentation for more information on performance monitoring.
This chapter provides TL1 performance monitoring information for the Cisco ONS 15454 and the Cisco ONS 15327, including:
•
Performance monitoring by card
•PM parameters by line type
•Scheduled PM report provisioning
6.1 Performance Monitoring by Card
Table 6-1 Near-End Section PMs
Parameter
|
DS1, DS1N
|
DS3, DS3N
|
DS3-12E, DS3N-12E
|
DS3XM
|
OC3
|
OC12, OC48, OC192
|
EC1
|
CV-S
|
|
|
|
|
X
|
X
|
X
|
ES-S
|
|
|
|
|
X
|
X
|
X
|
SES-S
|
|
|
|
|
X
|
X
|
X
|
SEFS-S
|
|
|
|
|
X
|
X
|
X
|
Table 6-2 Near-End Line PMs
Parameter
|
DS1, DS1N
|
DS3, DS3N
|
DS3-12E, DS3N-12E
|
DS3XM
|
OC3
|
OC12, OC48, OC192
|
EC1
|
Near-End Line
|
|
|
|
|
|
|
|
CV-L
|
|
|
|
|
X
|
X
|
X
|
ES-L
|
|
|
|
|
X
|
X
|
X
|
SES-L
|
|
|
|
|
X
|
X
|
X
|
UAS-L
|
|
|
|
|
X
|
X
|
X
|
FC-L
|
|
|
|
|
X
|
X
|
X
|
PSC
|
|
|
|
|
X
(1+1)
|
X
(1+1, 2F BLSR)
|
|
PSC-R
|
|
|
|
|
|
X
(4F BLSR)
|
|
PSC-S
|
|
|
|
|
|
X
(4F BLSR)
|
|
PSC-W
|
|
|
|
|
|
X
(4F BLSR)
|
|
PSD
|
|
|
|
|
X
(1+1)
|
X
(1+1, 2F BLSR)
|
|
PSD-R
|
|
|
|
|
|
X
(4F BLSR)
|
|
PSD-S
|
|
|
|
|
|
X
(4F BLSR)
|
|
PSD-W
|
|
|
|
|
|
X
(4F BLSR)
|
|
Far-End Line
|
|
|
|
|
|
|
|
CV-L FE
|
|
|
|
|
X
|
X
|
X
|
ES-L FE
|
|
|
|
|
X
|
X
|
X
|
FC-L FE
|
|
|
|
|
X
|
X
|
X
|
SES-L FE
|
|
|
|
|
X
|
X
|
X
|
UAS-L FE
|
|
|
|
|
X
|
X
|
X
|
Table 6-3 Near-End DS1 Line PMs
Parameter
|
DS1, DS1N
|
DS3, DS3N
|
DS3-12E, DS3N-12E
|
DS3XM
|
OC3
|
OC12, OC48, OC192
|
EC1
|
DS1 CV-L
|
X
|
|
|
|
|
|
|
DS1 ES-L
|
X
|
|
|
|
|
|
|
DS1 SES-L
|
X
|
|
|
|
|
|
|
DS1 LOSS-L
|
X
|
|
|
|
|
|
|
Table 6-4 Near-End DS3 Line PMs
Parameter
|
DS1, DS1N
|
DS3, DS3N
|
DS3-12E, DS3N-12E
|
DS3XM
|
OC3
|
OC12, OC48, OC192
|
EC1
|
DS3 CV-L
|
|
X
|
X
|
X
|
|
|
|
DS3 ES-L
|
|
X
|
X
|
X
|
|
|
|
DS3 SES-L
|
|
X
|
X
|
X
|
|
|
|
DS3 LOSS-L
|
|
X
|
X
|
X
|
|
|
|
Table 6-5 SONET Path PMs
Parameter
|
DS1, DS1N
|
DS3, DS3N
|
DS3-12E, DS3N-12E
|
DS3XM
|
OC3
|
OC12, OC48, OC192
|
EC1
|
Near-End SONET Path
|
|
|
|
|
|
|
|
STS CV-P
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
STS ES-P
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
STS FC-P
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
STS SES-P
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
STS UAS-P
|
X
|
X
|
X
|
X
|
X
|
X
|
X
|
PPJC-Pdet
|
|
|
|
|
X
|
X
|
|
NPJC-Pdet
|
|
|
|
|
X
|
X
|
|
PPJC-Pgen
|
|
|
|
|
X
|
X
|
|
NPJC-Pgen
|
|
|
|
|
X
|
X
|
|
Far-End SONET Path
|
|
|
|
|
|
|
|
STS CV-P FE
|
X
|
X
|
X
|
X
|
X
(15454 only)
|
|
X
|
STS ES-P FE
|
X
|
X
|
X
|
X
|
X
(15454 only)
|
|
X
|
STS FC-P FE
|
X
|
X
|
X
|
X
|
X
(15454 only)
|
|
X
|
STS SES-P FE
|
X
|
X
|
X
|
X
|
X
(15454 only)
|
|
X
|
STS UAS-P FE
|
X
|
X
|
X
|
X
|
X
(15454 only)
|
|
X
|
Table 6-6 DS1 Path PMs
Parameter
|
DS1, DS1N
|
DS3, DS3N
|
DS3-12E, DS3N-12E
|
DS3XM
|
OC3
|
OC12, OC48, OC192
|
EC1
|
DS1 Path (Rx and Tx)
|
|
|
|
|
|
|
|
DS1 Rx AISS-P
|
X
|
|
|
|
|
|
|
DS1 Rx CV-P
|
X
|
|
|
|
|
|
|
DS1 Rx ES-P
|
X
|
|
|
|
|
|
|
DS1 Rx SAS-P
|
X
|
|
|
|
|
|
|
DS1 Rx SES-P
|
X
|
|
|
|
|
|
|
DS1 Rx UAS-P
|
X
|
|
|
|
|
|
|
DS1 Tx AISS-P
|
X
|
|
|
|
|
|
|
DS1 Tx CV-P
|
X
|
|
|
|
|
|
|
DS1 Tx ES-P
|
X
|
|
|
|
|
|
|
DS1 Tx SAS-P
|
X
|
|
|
|
|
|
|
DS1 Tx SES-P
|
X
|
|
|
|
|
|
|
DS1 Tx UAS-P
|
X
|
|
|
|
|
|
|
Near-End DS1 Path
|
|
|
|
|
|
|
|
DS1 AISS-P
|
|
|
|
X
|
|
|
|
DS1 ES-P
|
|
|
|
X
|
|
|
|
DS1 SAS-P
|
|
|
|
X
|
|
|
|
DS1 SES-P
|
|
|
|
X
|
|
|
|
DS1 UAS-P
|
|
|
|
X
|
|
|
|
Table 6-7 DS3 Path PMs
Parameter
|
DS1, DS1N
|
DS3, DS3N
|
DS3-12E, DS3N-12E
|
DS3XM
|
OC3
|
OC12, OC48, OC192
|
EC1
|
Near-End DS3 Path
|
|
|
|
|
|
|
|
DS3 AISS-P
|
|
|
X
|
X
|
|
|
|
DS3 CVP-P
|
|
|
X
|
X
|
|
|
|
DS3 ESP-P
|
|
|
X
|
X
|
|
|
|
DS3 SASP-P
|
|
|
X
|
X
|
|
|
|
DS3 SESP-P
|
|
|
X
|
X
|
|
|
|
DS3 UASP-P
|
|
|
X
|
X
|
|
|
|
Near-End C-bit DS3 Path
|
|
|
|
|
|
|
|
DS3 CVCP-P
|
|
|
X
|
X
|
|
|
|
DS3 ESCP-P
|
|
|
X
|
X
|
|
|
|
DS3 SESCP-P
|
|
|
X
|
X
|
|
|
|
DS3 UASCP-P
|
|
|
X
|
X
|
|
|
|
Far-End C-bit DS3 Path
|
|
|
|
|
|
|
|
DS3 CVCP-P FE
|
|
|
X
|
X
|
|
|
|
DS3 ESCP-P FE
|
|
|
X
|
X
|
|
|
|
DS3 SASCP-P FE
|
|
|
X
|
X
|
|
|
|
DS3 SESCP-P FE
|
|
|
X
|
X
|
|
|
|
DS3 UASCP-P FE
|
|
|
X
|
X
|
|
|
|
Table 6-8 VT Path PMs
Parameter
|
DS1, DS1N
|
DS3, DS3N
|
DS3-12E, DS3N-12E
|
DS3XM
|
OC3
|
OC12, OC48, OC192
|
EC1
|
Near-End VT Path
|
|
|
|
|
|
|
|
CV-V
|
X
|
|
|
X
|
|
|
|
ES-V
|
X
|
|
|
X
|
|
|
|
SES-V
|
X
|
|
|
X
|
|
|
|
UAS-V
|
X
|
|
|
X
|
|
|
|
Far-End VT Path
|
|
|
|
|
|
|
|
CV-V FE
|
X
|
|
|
X
|
|
|
|
ES-V FE
|
X
|
|
|
X
|
|
|
|
SES-V FE
|
X
|
|
|
X
|
|
|
|
UAS-V FE
|
X
|
|
|
X
|
|
|
|
6.2 PM Parameters by Line Type
Table 6-9 PM Parameters by Line Type
Parameter
|
OC-N
|
T1
|
T3
|
STS
|
VT1.5
|
CVL
|
Y
|
Y
|
Y
|
|
|
CVP
|
|
Y
|
Y
|
Y
|
|
CVS
|
Y
|
|
|
|
|
CVV
|
|
|
|
|
Y
|
ESL
|
Y
|
Y
|
Y
|
|
|
ESP
|
|
Y
|
Y
|
Y
|
|
ESS
|
Y
|
|
|
|
|
ESV
|
|
|
|
|
Y
|
FCP
|
|
|
|
Y
|
|
FCL
|
Y
|
|
|
|
|
PJNEG
|
Y
|
|
|
|
|
PJPOS
|
Y
|
|
|
|
|
PSC
|
Y
|
|
|
|
|
PSD
|
Y
|
|
|
|
|
SASP
|
|
Y
|
Y
|
|
|
SEFS
|
Y
|
|
|
|
|
SESL
|
Y
|
Y
|
Y
|
|
|
SESP
|
|
Y
|
Y
|
Y
|
|
SESS
|
Y
|
|
|
|
|
SESV
|
|
|
|
|
Y
|
UASL
|
Y
|
|
|
|
|
UASP
|
|
Y
|
Y
|
Y
|
|
UASV
|
|
|
|
|
Y
|
AISSP
|
|
Y
|
Y
|
|
|
CVCPP
|
|
|
Y
|
|
|
ESCPP
|
|
|
Y
|
|
|
LOSSL
|
|
|
Y
|
|
|
SASCPP
|
|
|
Y
|
|
|
SESCPP
|
|
|
Y
|
|
|
UASCPP
|
|
|
Y
|
|
|
6.3 Scheduled PM Report
Scheduled performance monitoring (PM) report is a feature that extends the capability of PM reporting for the ONS 15454 and the ONS 15327. With scheduled PM report the system automatically and periodically generates the PM report of any specified facility or cross-connection.
Note The current maximum number of schedules allowed to be created for an NE is 1000. If this number of schedules has been created for the NE, an error message "Reach Limits Of MAX Schedules Allowed. Can Not Add More" will be returned if trying to create more schedules on the NE.
Note Identical schedules for an NE is not allowed. Two schedules are considered identical if they have the same AID, MOD2 type, performance monitor type, performance monitor level, location, direction and time period.
Note An error message "Duplicate Schedule" is returned if you create a schedule which is a duplicate of an existing schedule. However, if the existing schedule expires (with the parameter <NUMINVL> equal to zero when retrieved by the RTRV-PMSCHED command which means no more performance monitoring report to be sent), then the new schedule with the identical parameter will replace the existing schedule.
Note When you create a PM schedule, the minimum report interval should not be less than five minutes.
See each command description for command formats and syntax:
•SCHED-PMREPT-<MOD2>
•ALW-PMREPT-ALL
•RTRV-PMSCHED-<MOD2>
•RTRV-PMSCHED-ALL
•INH-PMREPT-ALL
•REPT PM <MOD2>
6.3.1 Create a PM Schedule and Receive an Autonomous PM Report
1. Issue the SCHED-PMREPT-<MOD2> command to create a PM schedule.
2. Issue the ALW-PMREPT-ALL command to allow the current TL1 session to be able to receive the autonomous PM report.
6.3.2 Manage PM Schedules
1. Create a PM schedule by issuing the SCHED-PMREPT-<MOD2> command.
2. Delete a PM schedule by issuing the SCHED-PMREPT-<MOD2> command with the <NUMREPT> parameter equal to zero.
Note The PM schedules created on a facility or a cross-connect will be automatically deleted if the card or the cross-connect are unprovisioned.
3. Retrieve all the PM schedules created on the node by issuing the RTRV-PMSCHED-ALL command. Retrieve a particular MOD2 type of PM schedule by issuing the RTRV-PMSCHED-<MOD2> command.
Note The system will not automatically delete the schedules that are expired (for example, a schedule is created to report PM 10 times. After 10 PM reports are sent, the schedule is expired). The expired schedule can be identified by its <NUMINVL> field (equal to zero) in the response of RTRV-PMSCHED.
6.3.3 Enable or Disable a TL1 Session to Receive Autonomous PM Reports
1. Enable a TL1 session to receive a scheduled PM report by issuing the ALW-PMREPT-ALL command.
Note By default, a TL1 session is disabled to receive PM reports. The ALW-PMREPT-ALL command enables a TL1 user to receive all the scheduled PM reports from the system, regardless of whether or not the schedule is created by this TL1 user or by any other TL1 user.
2. Disable a TL1 session to receive any scheduled PM report by issuing the INH-PMREPT-ALL command.
