Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

check-zero

Syntax

(check-zero | no-check-zero);

Hierarchy Level

[edit logical-systems logical-system-name protocols rip],[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name],[edit protocols rip],[edit protocols rip group group-name neighbor neighbor-name],[edit routing-instances routing-instance-name protocols rip],[edit routing-instances routing-instance-name protocols rip group group-name neighbor neighbor-name]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Statement introduced in Junos OS Release 12.1 for the QFX Series.

Description

Some of the reserved fields in RIP version 1 packets must be zero, whereas in RIP version 2 packets, most of these reserved fields can contain nonzero values. By default, RIP discards version 1 packets that have nonzero values in the reserved fields and version 2 packets that have nonzero values in the fields that must be zero. This default behavior implements the RIP version 1 and version 2 specifications.

If you find that you are receiving RIP version 1 packets with nonzero values in the reserved fields or RIP version 2 packets with nonzero values in the fields that must be zero, you can configure RIP to receive these packets even though they are being sent in violation of the specifications in RFC 1058 and RFC 2453.

Check whether the reserved fields in a RIP packet are zero:

  • check-zero—Discard version 1 packets that have nonzero values in the reserved fields and version 2 packets that have nonzero values in the fields that must be zero. This default behavior implements the RIP version 1 and version 2 specifications.
  • no-check-zero—Receive RIP version 1 packets with nonzero values in the reserved fields or RIP version 2 packets with nonzero values in the fields that must be zero. This is in spite of the fact that they are being sent in violation of the specifications in RFC 1058 and RFC 2453.

Default

check-zero

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

 

Related Documentation

 

Published: 2014-07-23

 

Related Documentation

 

Published: 2014-07-23