Specifications
Known issues with
firmware v4.7 fdr 35
83
6.22.11. Multi-CO mode: LIN does not react for CPE trunk
Tx cut
(BZ#: 8439)
Description: When just the Tx fiber from the CPE trunk port is cut, LIN does not react on the CPE by
disabling the user port. This is because the 10G8SW-XY SFP port does not operate in uni-directional mode
so its fault indication is not sent. Link remains up on the CPE trunk Rx fiber so it thinks the communication
path is still operational.
Suggested Work-Around: When it is necessary that the CPE user port transmitter be disabled due
to disrupted path, the 10G8SW-XY SFP port may be temporarily configured down with the "shutdown"
command. This will cause link down on the CPE trunk port and LIN will react by disabling the CPE user
port transmitter. Once the trunk fibers are fully restored, the 10G8SW-XY SFP port must be reconfigured
with "no shutdown" in order to resume normal service.
Customer Impact: Depends.
Corrective Action: None; information only.
6.22.12. Multi-CO mode: 100FX user port should not
support auto neg
(BZ#: 8444)
Description: An EUSM (CPE) module configured for 100 Mbps service does not support auto-
negotiation on the fiber user port. However, the NM provides commands to enable and disable it.
Suggested Work-Around: When it is necessary that the CPE user port transmitter be disabled due
to disrupted path, the 10G8SW-XY SFP port may be temporarily configured down with the "shutdown"
command. This will cause link down on the CPE trunk port and LIN will react by disabling the CPE user
port transmitter. Once the trunk fibers are fully restored, the 10G8SW-XY SFP port must be reconfigured
with "no shutdown" in order to resume normal service.
Customer Impact: Depends.
Corrective Action: None; information only.
6.22.13. Multi-CO mode: unexpected OAM traffic
(BZ#: 8469)
Description: When the CO is reset and reboots, it assumes that OAM service is enabled to all remotes.
The configuration for 'no OAM' service comes from LNXNM. Thus there is a small amount of time where
OAM frames may be sent to a remote device when they should not be.
Suggested Work-Around: None.
Customer Impact: There is a potential for a few unwanted OAM frames.
Corrective Action: This issue will be addressed in future software upgrades.