FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private Routed Network Service
Issue: 13 3HH-11985-AAAA-TQZZA 429
In order to enable a VPRN BGP instance, the BGP protocol must be enabled in the
configure>router>bgp context on each participating ISAM router.
The autonomous system number and router ID configured in the VPRN context only
applies to that particular service.
The minimal parameters that should be configured for a VPRN BGP instance are:
• Specify an autonomous system number for the router. See “Configuring Global
VPRN Parameters”.
• Specify a router ID - Note that if a new or different router ID value is entered in the
BGP context, then the new valuestakes precedence and overwrites the
router-level router ID. See “Configuring Global VPRN Parameters”.
• Specify a VPRN BGP peer group.
• Specify a VPRN BGP neighbor with which to peer.
• Specify a VPRN BGP peer-AS that is associated with the above peer.
VPRN BGP is administratively enabled upon creation. Minimally, to enable VPRN
BGP in a VPRN instance, you must associate an autonomous system number and
router ID for the VPRN service, create a peer group, neighbor, and associate a peer
AS number. There are no default VPRN BGP groups or neighbors. Each VPRN BGP
group and neighbor must be explicitly configured.
All parameters configured for VPRN BGP are applied to the group and are inherited
by each peer, but a group parameter can be overridden on a specific basis. VPRN
BGP command hierarchy consists of three levels:
• The global level
• The group level
• The neighbor level
CLI syntax:
configure>service>vprn>bgp# (global level)
group (group level)
neighbor (neighbor level)
For more information about the BGP protocol, refer to the ISAM Router Configuration
Guide.
Note — Careful planning is essential to implement commands
that can affect the behavior of VPRN BGP global, group, and
neighbor levels. Because the BGP commands are hierarchical,
analyze the values that can disable features on a particular
level.
To Next Page
Loading...
