This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.
[Critical] From: BMA-NET@server.xxx.local "MSL2024 Ultrium5 dri" Time: 16.5.2016 16:53:38
Invalid block sequence number: 184934 expected 184935.
There are cases were certain block is sent twice which should not be the issue since at restore duplicated blocks are ignored.
When OB2MACHECKBLKSEQNO variable is set to 1, BMA checks if block sequence numbers are in the correct order.
If block numbers aren't in the correct order, BMA sends message indicating wrong seq no and aborts session.
When this variable is set to 0, block sequence numbers are not checked for correct order.
In case block numbers aren't in the correct order session is not aborted.
Critical situation would be if there would be missing blocks what could lead to corrupted/missing data .
On omnirc file set OB2MACHECKBLKSEQNO=0
This will turn off the block sequence check