Version Found: v5.5
When the core is generated by selecting 'Additional Link Requests Before Fatal' parameter as '1', the core goes into the fatal error state immediately, asserting lnk_porterr_n after the LRESP timeout counter expires while waiting for an LRESP for the first LREQ. The core should have sent two LREQs before going into the fatal error state for not receiving an LRESP from the link partner.
The wording in the core configuration GUI is misleading. When the 'Additional Link Requests Before Fatal' parameter is set to '1', the core will send exactly one LREQ and times out if it does not receive the corresponding LRESP. If it is set to '2', it will send exactly two LREQs.
NOTE: "Version Found" refers to the version where the problem was first discovered. The problem might also exist in earlier versions, but no specific testing has been performed to verify earlier versions.
12/03/2012 - Initial release