Fixes two major OSPF bugs if you are still on any version of code prior to 5.1.3.1.
The first one was fixed in 5.1.3.1, the next is in 5.1.7.
"The “BAD_LS_REQ_EVENT” is a known issue and in the release that you have already installed (5.1.1.1) there is a work around. I’m attaching to this email the 5.1.6 release notes and you can see on page 29 the command to solve this issue and an explanation about why and when is required to use it. By the way Ive seen a lot of improvements made in further releases. If you read this release note or the release notes from the 5.1.5.1 (I’m attaching too to this email and the command to do the workaround is on page 73-74)"
Look at this issue solved in the 5.1.6
“An OSPF network configured with non-unique OSPF router id may trigger the ERS8600 to reset if it receives a NET_LINKS packet from a remote router whose ID is the same as one directly connected to the ERS8600. (wi00858330) “
Solved in the 5.1.3.1
"After an upgrade it is now ensured that the OSPF Md5 keys are no longer lost. (Q02127996) “
Solved in the 5.1.1.1
“For an MSTP enabled system, port disable and enable scenarios, where the cistforceport state is disabled on the port, will now be handled properly and in turn OSPF will behave normally. (Q02064812)”
Quotes are from the Avaya tech on a ticket we opened.
TankII
