Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Performance Monitoring

 

The ACX6160 supports the Open ROADM performance monitoring YANG data model for reporting current PM data. It also provides support for retrieving historical PM data by way of file transfer, and support for clearing PM data.

There are two main categories of performance monitoring parameter types:

  • Counter performance monitors (PMs)

  • Gauge PMs

Counter type PMs are collected for current 15-minute and 1-day granularities. You can also retrieve historical counter bins by way of file transfer. You can retrieve up to the last ninety-six 15-minute bins, as well as the previous 1-day bin.

Gauge type PMs report the current instantaneous value, as well as the minimum, maximum, and average value over the duration of the reported interval (15-minute or 1-day). For gauge type PMs, only the minimum, maximum and average values are reported for historical bins.

Note

For current instantaneous gauge-type PM values, use the bin granularity type of “notApplicable”.

Performance Monitoring

This section provides the list of supported performance metrics (PMs) for each type of entity on the ACX6160 that supports performance monitoring.

The ACX6160 supports the following PMs:

Table 1 lists the OpenRoadm performance monitoring parameters that are supported for transponder ports on the ACX6160.

Table 1: Open ROADM Port Performance Monitor Support on ACX6160

Open ROADM PM Name

Location

Direction

Support

Line/Client

Comments

opticalPowerOutput

Near-end

Transmit

Yes/No

 

opticalPowerOutputMin

Near-end

Transmit

Yes/No

 

opticalPowerOutputMax

Near-end

Transmit

Yes/No

 

opticalPowerOutputAvg

Near-end

Transmit

Yes/No

 

totalOpticalPowerInput

Near-end

Receive

Yes/No

These PMs report on total optical input power, including signal and noise power.

totalOpticalPowerInputMin

Near-end

Receive

Yes/No

totalOpticalPowerInputMax

Near-end

Receive

Yes/No

totalOpticalPowerInputAvg

Near-end

Receive

Yes/No

Table 2 lists the OpenRoadm performance monitoring parameters that are supported for optical channel interfaces on the ACX6160.

Table 2: Open ROADM OCH Interface Performance Monitor Support

Open ROADM PM Name

Location

Direction

Support

Comments

opticalPowerInput

Near-end

Receive

Yes

These PMs report on signal optical input power.

opticalPowerInputMin

Near-end

Receive

Yes

opticalPowerInputMax

Near-end

Receive

Yes

opticalPowerInputAvg

Near-end

Receive

Yes

Table 3 lists the OpenRoadm performance monitoring parameters that are supported for OTU interfaces on the ACX6160.

Table 3: Open ROADM OTU Interface Performance Monitor Support on ACX6160

Open ROADM PM Name

Location

Direction

Support

Line/Client

Comments

preFECCorrectedErrors

Near-end

Receive

Yes/No

These FEC PMs are available only when FEC is not set to “off”. FECCorrectableBlocks PM is not supported.

FECCorrectableBlocks

Near-end

Receive

No/No

FECUncorrectableBlocks

Near-end

Receive

Yes/No

erroredBlockCount

Near-end

Receive

Yes/Yes

Count of BIP-8 errors. Counting suppressed during SES seconds.

backgroundBlockErrors

Near-end

Receive

Yes/Yes

Reported as a vendor extension.

erroredSeconds

Near-end

Receive

Yes/Yes

Count of seconds with BIP-8 errors or SES.

severelyErroredSeconds

Near-end

Receive

Yes/Yes

Count of seconds in which signal failure observed.

unavailableSeconds

Near-end

Receive

No/No

Not supported this release.

erroredBlockCount

Far-end

Receive

Yes/Yes

Count of BIP-8 errors. Counting suppressed during SES seconds.

backgroundBlockErrors

Far-end

Receive

Yes/Yes

Reported as a vendor extension.

erroredSeconds

Far-end

Receive

Yes/Yes

Count of seconds with BIP-8 errors or SES.

severelyErroredSeconds

Far-end

Receive

Yes/Yes

Count of seconds in which signal failure observed.

unavailableSeconds

Far-end

Receive

No/No

Not supported this release.

Table 4 lists the OpenRoadm performance monitoring parameters that are supported for ODU interfaces on the ACX6160.

Table 4: Open ROADM ODU Interface Performance Monitors on ACX6160

Open ROADM PM Name

Location

Direction

Supported

Line/Client

Comments

erroredBlockCount

Near-end

Receive

Yes/yes

Count of BIP-8 errors. Counting suppressed during SES seconds.

backgroundBlockErrors

Near-end

Receive

Yes/yes

Reported as a vendor extension.

erroredSeconds

Near-end

Receive

Yes/yes

Count of seconds with BIP-8 errors or SES.

severelyErroredSeconds

Near-end

Receive

Yes/yes

Count of seconds in which signal failure observed.

unavailableSeconds

Near-end

Receive

No/no

Not supported this release.

erroredBlockCount

Far-end

Receive

Yes/yes

Count of BIP-8 errors. Counting suppressed during SES seconds.

backgroundBlockErrors

Far-end

Receive

Yes/yes

Reported as a vendor extension.

erroredSeconds

Far-end

Receive

Yes/yes

Count of seconds with BIP-8 errors or SES.

severelyErroredSeconds

Far-end

Receive

Yes/yes

Count of seconds in which signal failure observed.

unavailableSeconds

Far-end

Receive

No/no

Not supported this release.

delay

Near-end

Transmit

No/no

Not supported this release.

Table 5 lists the OpenRoadm performance monitoring parameters that are supported for 100GE Client interfaces on the ACX6160.

Table 5: Open ROADM Ethernet Interface Performance Monitors on ACX6160

Open ROADM PM Name

Location

Direction

Support

Comments

erroredBlockCount

Near-end

Receive

No

(Ref IEEE 802.3ba: 45.2.3.12.4)

BIPErrorCounter

Near-end

Receive

Yes

(Ref IEEE 802.3ba: 45.2.3.36)

erroredSecondsEthernet

Near-end

Receive

Yes

Count of seconds with errored blocks or BIP errors or SES.

severelyErroredSecondsEthernet

Near-end

Receive

Yes

Count of seconds in which signal failure observed.

unavailableSecondsEthernet

Near-end

Receive

No

Not supported this release.

erroredBlockCount

Near-end

Transmit

No

(Ref IEEE 802.3ba: 45.2.3.12.4)

BIPErrorCounter

Near-end

Transmit

Yes

(Ref IEEE 802.3ba: 45.2.3.36)

erroredSecondsEthernet

Near-end

Transmit

Yes

Count of seconds with errored blocks or BIP errors or SES.

severelyErroredSecondsEthernet

Near-end

Transmit

Yes

Count of seconds in which signal failure observed.

unavailableSecondsEthernet

Near-end

Transmit

No

Not supported this release.

Open ROADM Performance Monitor YANG Model Support

The columns in Table 6 are defined as:

  • YANG node — The node from the Open ROADM YANG model.

  • Access — Access properties of the node. Can be:

    • rw — read/write

    • ro — read-only

    • x — rpc function

    • n — notification

  • Supported — Indicates ACX6160 support for the node.

    • Yes — ACX6160 supports the node

    • No — ACX6160 does not support the node

    • N/A — Node is not applicable to transponder device

  • Supported Values — Describes the range of supported values on ACX6160.

Table 6 describes ACX6160 compliance with the content of the current-pm-list list definition within the org-openroadm-pm YANG module. The location within the Open ROADM YANG model of the nodes listed in the table is /org-openroadm-pm/current-pm-list/current-pm-entry.

Table 6: Open ROADM Current Performance Monitoring YANG Model Support

YANG Node

Access

Supported

Supported Values

pm-resource-instance

ro

yes

Identifies specific resource instance reporting the PM data.

pm-resource-type

ro

yes

Port, interface

pm-resource-type-extension

ro

yes

None

retrieval-time

ro

yes

Time when data was read, does not include bin start or end time.

current-pm

ro

yes

List of PMs collected for this resource

- type

ro

yes

Enumerated value from Open ROADM pm-names-enum

- extension

ro

yes

Identifies ACX6160-specific extension to pm-names-enum or “none” if Open ROADM defined pm-name-enum reported for type value above.

- location

ro

yes

notApplicable, nearEnd, farEnd

- direction

ro

yes

tx, rx, bidirectional, notApplicable

- measurement

ro

yes

List of PM measurements for different granularities

-- granularity

ro

yes

notApplicable, 15min, 24Hour

-- pmParameterValue

ro

yes

  • Union uint64

  • int64

  • decimal64

-- pmParameterUnit

ro

yes

String-valued indicator of units of the value reported, if applicable, for example “dBm”, “count”

-- validity

ro

yes

partial, suspect

Open ROADM Historical Performance Monitoring YANG Model Support

The ACX6160 provides support for retrieval of historical PM data through the collect-historical-pm-file RPC, defined in the org-openroadm-pm.yang module. Open ROADM users can invoke this RPC to generate an output file containing the historical PM data that is queried, then download this file using the Open ROADM file transfer RPC.

See, File System Operations

Note

The ACX6160 does not provide support for retrieving historical PM data by Netconf get requests that target the historical-pm-list container.

Table 7 describes ACX6160 compliance with the collect-historical-pm-file RPC definition within the org-openroadm-pm YANG module.

Table 7: Open ROADM Historical Performance Monitoring RPC YANG Model Support

YANG Node

Access

Supported

Supported Values

collect-historical-pm-file

x

Yes

Input

- from-bin-number

w

Yes

1 through 96

- to-bin-number

w

Yes

1 through 96

- granularity

w

Yes

15min, 24Hour

Output

- pm-filename

ro

Yes

Name of file in which rpc output data is recorded

- status

ro

Yes

Successful, Failed

- status-message

ro

Yes

Textual description of rpc execution result

The output of the collect-historical-pm-file RPC is saved to a file in XML format based on the historical-pm-list definition, and the file is gzip compressed, as per the definition of the collect-historical-pm-file RPC.

Table 8 describes ACX6160 compliance with the defined output data content as defined within the org-openroadm-pm YANG module.

Table 8: Open ROADM Defined Output Data Content Support

YANG Node

Access

Supported

Supported Values

historical-pm-list

ro

Yes

- historical-pm-entry

ro

Yes

-- pm-resource-instance

ro

Yes

Name of port or interface instance

-- pm-resource-type

ro

Yes

Port, interface

-- pm-resource-type-extension

ro

Yes

-- historical-pm

ro

Yes

--- type

ro

Yes

Enumerated value from Open ROADM pm-names-enum

--- extension

ro

Yes

Identifies ACX6160-specific extension to pm-names-enum or “none” if Open ROADM defined pm-name-enum reported for type value above.

--- location

ro

Yes

notApplicable, nearEnd, farEnd

--- direction

ro

Yes

tx, rx, bidirectional, notApplicable

--- measurement

ro

Yes

---- granularity

ro

Yes

15min, 24Hour

---- bin-number

ro

Yes

1 through 96

---- pmParameterValue

ro

Yes

Union of uint64, int64 and descimal64

---- pmParameterUnit

ro

Yes

String-valued indicator of units of the value reported, if applicable, for example “dBm”, “count”

---- validity

ro

Yes

complete, suspect

---- completion-time

ro

Yes

Timestamp of end of bin time

Open ROADM Clearing Performance Monitoring Data YANG Model Support

The ACX6160 provides support for clearing current and historical PM data through the clear-pm RPC defined in the org-openroadm-pm.yang module.

Table 9 describes ACX6160 compliance with the clear-pm RPC definition within the org-openroadm-pm YANG module.

Table 9: Open ROADM Clearing Performance Monitoring Data RPC YANG Model Support

YANG Node

Access

Supported

Supported Values

clear-pm

x

Yes

Input

- device/node-id

w

Yes

If specified, must match configured ACX6160 node-id - resource/port

-- circuit-pack-name

w

Yes

If targeting a port, this field must be specified to match the name of a configured pluggable transceiver with traffic-bearing port, with name matching pattern xcvr-0/X/Y

-- port-name

w

Yes

If targeting a port, this field must be specified to match the name of a configured port on a pluggable transceiver, with name matching pattern port-0/X/Y

- resource/interface-name

w

Yes

If targeting an interface, this field must match the name of the interface as configured in the interface list

- resource-type

w

Yes

-- type

w

Yes

Port, interface

-- extension

w

Yes

None, or leave unspecified

- pm-type

w

Yes

Current, all

- granularity

w

Yes

15min, 24Hour

Output

- status

ro

Yes

Successful, Failed

- status-message

ro

Yes

Textual description of rpc execution result