Specifications

Issues fixed with firmware v4.7 fdr 35
11
5.6.2. Loopback timer does not work on ports in remote
CPE modules
(BZ#: 5862)
Description: The loopback-timeout command has no effect on loopback status on ports in
remote CPE modules. Ports on remote CPE modules remain in loopback even after loopback timer expires.
Corrective Action: This issue has been fixed.
5.7. EM316EFE1RM, EM316EFT1RM,
EM316EFE1RJRM, EM316EFE1MUXRJ,
EM316EFE1MUX4, EFT1MUX4 issues
5.7.1. restart cold did not clear loopback
(BZ#: 5841,5845)
Description: Even though the expected behavior, after a restart cold, is the same as a 'power-up'
behavior, loopback status seems to be one of the exceptions. If the loopback was ON, on a CO user port or
a CPE trunk port before issuing restart cold, it will remain in loopback, even after the system comes
back from a restart cold. This will almost always cause CPE to be in a never ending not-ready state.
Corrective Action: This issue has been fixed.
5.7.2. Loopback timer does not work on ports in remote
CPE modules
(BZ#: 5862)
Description: The loopback-timeout command has no effect on loopback status on ports in
remote CPE modules. Ports on remote CPE modules remain in loopback even after loopback timer expires.
Corrective Action: This issue has been fixed.
5.8. EM316E1MUX4RJRM, EM316E1MUX4RM,
EM316T1MUX4RM issues
5.8.1. restart cold did not clear loopback
(BZ#: 5841,5845)
Description: Even though the expected behavior, after a restart cold, is the same as a 'power-up'
behavior, loopback status seems to be one of the exceptions. If the loopback was ON, on a CO user port or
a CPE trunk port before issuing restart cold, it will remain in loopback, even after the system comes
back from a restart cold. This will almost always cause CPE to be in a never ending not-ready state.
Corrective Action: This issue has been fixed.