FD 100/320Gbps NT and FX NT IHub Services Guide
In order to enable a VPRN RIP instance, the RIP protocol must be enabled in the
configure>router> rip context on each participating ISAM. VPRN RIP is
administratively enabled upon creation. Configuring other RIP commands and
parameters are optional.
The parameters configured on the VPRN RIP global level are inherited by the group
and neighbor levels. Many of the hierarchical VPRN RIP commands can be modified
on different levels. The most specific value is used. That is, a VPRN RIP
group-specific command takes precedence over a global VPRN RIP command. A
neighbor-specific statement takes precedence over a global VPRN RIP and
group-specific command. For example, if you modify a VPRN RIP neighbor-level
command default, the new value takes precedence over VPRN RIP group- and
global-level settings. There are no default VPRN RIP groups or neighbors. Each
VPRN RIP group and neighbor must be explicitly configured.
The minimal parameters that should be configured for a VPRN instance are:
•
•
•
VPRN RIP command hierarchy consists of three levels:
•
•
•
For example:
configure>service>vprn>rip#
7.7.5.1
The following example displays a VPRN RIP configuration:
*A:ALA-1>configure>service# info
----------------------------------------------
...
Issue: 13
Careful planning is essential to implement commands
Note —
that can affect the behavior of VPRN RIP global, group, and
neighbor levels. Because the RIP commands are hierarchical,
analyze the values that can disable features on a particular
level.
Specify a VPRN RIP peer group.
Specify a VPRN RIP neighbor with which to peer.
Specify a VPRN RIP peer-AS that is associated with the above peer.
The global level
The group level
The neighbor level
group
neighbor
VPRN RIP CLI Syntax
vprn 1 customer 1 create
vrf-import "vrfImpPolCust1"
vrf-export "vrfExpPolCust1"
3HH-11985-AAAA-TQZZA
Virtual Private Routed Network Service
(global level)
(group level)
(neighbor level)
431