======rfc1583 compatibility======
To minimize the chance of routing loops, all Open Shortest Path First (OSPF) routers in an OSPF routing domain should have RFC compatibility set identically.

Because of the introduction of RFC 2328, OSPF Version 2, the method used to calculate summary route costs has changed. Use the //no rfc1583compatibility// command to enable the calculation method used per RFC 2328.

===Example config===

campus01-b02-access01 and campus01-b02-access02 are the two reference devices which we are using for this example.  One has rfc1583 configuration and other does not. 

==campus01-b02-access01#==
{{:guides:user:compliance:compliance:howto:cpl6_1.png}}

==campus01-b02-access02#==
{{:guides:user:compliance:compliance:howto:cpl6_2.png}}


===How its done===

Below are the steps to create new policy.

//Operate -> Compliance -> Policies -> New->//

{{:guides:user:compliance:compliance:howto:cpl6_3.png}}

Click on the Node Group to select the relevant group of devices to add.
Node group named "building2_access" holds the nodes of both the nodes:
{{:guides:user:compliance:compliance:howto:cpl2_4.png}}

Rule -> New

{{:guides:user:compliance:compliance:howto:cpl6_5.png}}



===Report/test results:===

Below is how to create reports to see the results of the compliance policies.

//Operate -> Compliance -> Reports -> New -> Report Name “test” -> Report type “Policies” -> Policy Name “Sample6 : rfc1583compatibility” -> Show Report//

{{:guides:user:compliance:compliance:howto:cpl6_6.png}}

This was a simple example to understand how to implement compliance policy to verify rfc1583 configuration.