Specifications
Issues fixed with firmware v4.7 fdr 35
10
5.4.4. EM316EUSM: 'traffic-gen-load' command changes
'Frame Size Type'.
(BZ#: 8575)
Description: When using the traffic generation 'load' command to specify percentage traffic load for
traffic generation, the translation of this value to a fixed inter-packet-gap requires a fixed frame size. If
'frame-size-type' is set to 'random', the run-time setting is changed to 'fixed' to allow for the load-to-ipg
translation.
Suggested Work-Around: If running a test that requires random sized packets, use the inter-packet-
gap command to set the traffic load, not the load command.
Customer Impact: Minimal.
Corrective Action: This issue has been fixed.
5.5. EM316GRMAHSH issues
5.5.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.5.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.6. EM316EFRMAHSH issues
5.6.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.