We have a technical problem with testing our device I was wondering you could help us with that (or point us to the right direction for help).
Our device is under OSPFv3 conformance test in a laboratory with Spirent OSPFv3 Conformance Test-Suite. We developed fully functional OSPFv3 daemon in our device with full compliance with RFC 5340. but in Laboratory's Spirent test results, all tests gets FAILED. we investigated a little (as far as laboratory permitted us to do) and found out that we fail because of below happening:
in Two-Way state of OSPF neighbor negotiations, Spirent device sends a Database Description packet with Link-LSA header with its "length" field set to 40. but according to RFC, Link-LSA's minimum length is 44 (20B LSA-Header and 24B minimum Link-LSA data), thus our device recognizes packet as erroneous and ignores it.
My question is, is there a protocol-based reason for this? Or is there any configurations on Spirent device for this, that we can tell laboratory to set?
Thank you for your time.