Interfaces
Page 354 7750 SR Interface Configuration Guide
mismatch-reaction
Syntax mismatch-reaction {none | squelch-rx}
Context config>port>otu>psi-payload
Description This command allows the user to configure the consequent action to a psi-payload type mismatch.
Default None
Parameters none — The received traffic is passed through.
squelch-rx — The received traffic is blocked.
async-mapping
Syntax [no] async-mapping
Context config>port>otu
Description This command allows the user to configure the port to support asynchronous mapping of the payload inside
the OTU. If the port is configured for async-mapping and the payload clock is asynchronous to the OTU
clock, there will be positive or negative pointer justification that will show up in the OTU statistics and the
data will be received error free. If the port is configured for synchronous mapping and the received data is
asynchronously mapped, there will be errors in the received data.
async-mapping is the only mode of operation that is supported on the OTU3 encapsulated 40-Gigabit Ether-
net and therefore the 'no async-mapping' is not supported on that port type and the default on the is async-
mapping.
The no form of this command configures the port to receive synchronously mapped data.
Default no async-mapping
report-alarms
Syntax [no] no report-alarms [loc] [los] [lof] [lom] [otu-ais] [otu-ber-sf] [otu-ber-sd] [otu-bdi] [otu-tim]
[otu-iae] [otu-biae] [fec-sf] [fec-sd] [fec-fail] [fec-uncorr] [odu-ais] [odu-oci] [odu-lck] [odu-bdi]
[odu-tim] [opu-tim] [opu-plm]
Context config>port>otu
Description This command enables OTU alarms. Specify specific alarms to add to the list of reported alarms.
The no form of the command disables OTU alarm reporting.
Default loc, los, lof, lom, otu-ais, otu-bdi, fec-sf, fec-sd, odu-ais, odu-oci, odu-lck, odu-bdi, opu-plm
Parameters alarms — Refer to the following table for alarm descriptions.
To Next Page
Loading...
