Nokia 7330 - Table 581 Check-Zero Command; Table 582 Split-Horizon Command

FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private Routed Network Service
Issue: 13 3HH-11985-AAAA-TQZZA 545
7.10.11.4 check-zero
Table 581 check-zero command
7.10.11.5 split-horizon
Table 582 split-horizon command
Item Description
Syntax check-zero {enable | disable}
no check-zero
Context configure>service>vprn>rip
configure>service>vprn>rip>group
configure>service>vprn>rip>group>neighbor
Description This command enables checking for zero values in fields specified to be zero by the RIPv1
and RIPv2 specifications.
The no form of the command disables this check and allows the receipt of RIP messages even
if the mandatory zero fields are non-zero.
Default no check-zero
Parameters enable — Enables checking of the mandatory zero fields in the RIPv1 and RIPv2
specifications and rejecting non-compliant RIP messages.
disable — Disables the checking and allows the receipt of RIP messages even if the
mandatory zero fields are non-zero.
Item Description
Syntax split-horizon {enable | disable}
no split-horizon
Context configure>service>vprn>rip
configure>service>vprn>rip>group
configure>service>vprn>rip>group>neighbor
Description This command enables the use of split-horizon. RIP uses split-horizon with poison-reverse to
protect from such problems as “counting to infinity”. Split-horizon with poison reverse means
that routes learned from a neighbor through a given interface are advertised in updates out of
the same interface but with a metric of 16 (infinity).
The split-horizon disable command enables split horizon without poison reverse. This allows
the routes to be re-advertised on interfaces other than the interface that learned the route, with
the advertised metric equaling an increment of the metric-in value.
This configuration parameter can be set at three levels: global level (applies to all groups and
neighbor interfaces), group level (applies to all neighbor interfaces in the group) or neighbor
level (only applies to the specified neighbor interface). The most specific value is used. In
particular if no value is set (no split-horizon), the setting from the less specific level is inherited
by the lower level.
The no form of the command disables split-horizon command which allows the lower level to
inherit the setting from an upper level.
(1 of 2)