Hi Tulasi, You definitely shouldn’t generate the netMaskMismatch trap as this is for mask mismatch detection on hello packets. You could generate the ospfIfRxBadPacket but many do not for this case. Thanks, Acee
From: Lsr <[email protected]> on behalf of Tulasi Rami Reddy N <[email protected]> Date: Wednesday, December 9, 2020 at 6:11 AM To: "[email protected]" <[email protected]> Subject: Re: [Lsr] RFC4750: OSPF Version 2 Management Information Base [ Sorry, My previous mail was truncated] Hi , OSPFv2 adjacency will be formed on a numbered LAN only below both conditions are met: 1. Common IP subnet 2. Matching network mask. From the OSPFv2 MIB, there is only one error defined. ospfConfigErrorType OBJECT-TYPE SYNTAX INTEGER { netMaskMismatch (7), } I believe this is for the case 2 (when mask is mismatched). Let's take below example: RTA (11.1.1.2/24<http://11.1.1.2/24>) -------- (10.1.1.1/24<http://10.1.1.1/24>) RTB Here, src IP is not matching to the Rx interface IP subnet, then what is the error type to be set? Should this be considered as generic input processing error and only generate ospfIfRxBadPacket notification or netMaskMismatch notification? Should we need a new type here? " The generic input processing of OSPF packets will have checked the validity of the IP header and the OSPF packet header." Thanks, Tulasi. On Wed, Dec 9, 2020 at 4:27 PM Tulasi Rami Reddy N <[email protected]<mailto:[email protected]>> wrote: Hi , OSPFv2 adjacency will be formed on a numbered LAN only when 1. Common IP subnet 2.matching network mask. From the Thanks, TUlasi.
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
