BGP4 is an extension
of BGP-3 (BGP version 3) and is the current version of BGP. BGP4 was
published as per RFC 4271 in 2006. Its major enhancement is the
support for Classless Inter-Domain Routing (CIDR) and
the use of route aggregation for decreasing the size of routing
tables. The RFC allows BGP4 to
carry a wide range of IPv4 and IPv6 "address families".
BGP4 (Border
Gateway Protocol) provides a set of mechanisms for supporting CIDR (Classless Inter - Domain
Routing). These mechanisms include support for advertising a set
of destinations as an IP prefix and eliminating the concept of network
class within BGP. BGP4 also introduces mechanisms
which allow aggregation of routes, including aggregation of AS paths.
To access BGP4 screens, go to
Confederation Settings
Figure 1. Confederation Settings
Screen Objective |
This screen allows the user to configure the
confederation status of the BGP peer
for the specified VRF instance. |
Navigation |
|
Fields |
- Select—select
the Peer ASN and delete the confederation.
- Peer AS NO—enter the peer ASN for which the confederation
status needs to be configured. This value ranges from 1 to 65535.
The ASN identifies the BGP router
to other routers and tags the routing information passed along.
- Confederation status / Status—select
the status of the BGP confederation
identifier which specifies the confederation to which the autonomous
systems belong to. The default option is enable. The list contains:
- Enable—configures the BGP confederation
identifier which specifies the confederation to which the autonomous
systems belong.
- Disable—deletes the configured BGP confederation
identifier.
- VRF Name / Context Name —default.
|
Buttons |
- Add—adds and
saves new configuration.
- Reset—resets to default value for respective
fields and discards all user inputs.
- Delete—deletes the selected entry.
|
BGP RFD Settings
Figure 2. BGP RFD Settings
Screen Objective |
This screen allows the user to configure RFD (Route Flap Dampening) parameters. |
Note |
The RFD parameters can be configured only
if,
- Global admin status of the BGP4 is
set as disabled using the screen.
- Local AS of BGP4 is configured using the
|
Navigation |
|
Fields |
- Half life time—enter
the time duration in seconds after which a penalty is decreased
by half. Once a route has been assigned a penalty, the penalty is
decreased for every 5 seconds. BGP’s route flap dampening algorithm
calculates penalty for all routes. This penalty increases by a fixed
value when a flap occurs and decreases exponentially when the route
is stable. This value ranges from 600 to 2700 seconds. The default
value is 900.
- Reuse Value—enter the reuse value below
which the suppressed route will be reused. This value ranges from
100 to 1999. If the penalty for a flapping route falls below this
value, the route is reused. The unsuppressing of routes occurs at
10-seconds increments. The default value is 750.
Note: Reuse Value
can be configured only if the Half Life Time value is configured.
- Suppress Value—enter the suppress value
above which the route will be suppressed. The route is suppressed
if the penalty associated with the route exceeds this value. This
value ranges from 2000 to 3999 seconds. The default value is 2000.
Note: Suppress
value can be configured only if the Half Life Time and Reuse value
are set.
- Maximum Suppress Value—enter the maximum
time (in seconds) a route can be suppressed. This value ranges from
1800 to 10800 seconds. The default value is 3600.
Note: Max-Suppress
Time can be configured only if the half life time, reuse value and
suppress value are set.
- Decay timer granularity—enter the timer
granularity (in seconds) for performing all decay calculations.
This value ranges from 1 to 10800 seconds. The default value is
1.
- Reuse timer granularity—enter the time
interval between evaluations of the reuse lists. This value ranges
from 15 to 10800 seconds. The default value is 15.
- Reuse Array index—enter the size of reuse
index arrays. This size determines the accuracy with which suppressed
routes can be placed within the set of reuse lists when suppressed
for a long time. This value ranges from 256 to 65535. The default
value is 1024.
- VRF Name—default.
|
Buttons |
- Apply—modifies
attributes for the selected entry and saves the changes.
- Reset—resets to default value for respective
fields and discards all user inputs.
|
Community Filter Configuration
Figure 3. Community
Filter Configuration
Screen Objective |
This screen allows the user to configure the
incoming / outgoing filter status for a given community value. This
filter status allows/ filters the community attribute while receiving
or advertising. The rules to filter out the updates are based on
the AS from which it is received, NLRI and AS through
which it had passed. |
Navigation |
|
Fields |
- Select—select
the Peer ASN and delete the confederation.
- Community value—enter the community value
for which the incoming / outgoing filtering policy is to be updated.
This value ranges from 65536 to 4294901759 and 4294967041 to 4294967043.
|
Fields (cont) |
- Filter Status—select
the incoming / outgoing filtering policy for the community. The
default option is Permit. The list contains:
- Permit—allows
a particular community attributes to be received or advertised in
updates.
- Deny—filters the routes containing the community attribute value
in received or advertised updates.
- Filter Table/ Filter Type—select to configure
the incoming filter status or outgoing filter status for a given
community value. The default option is In. The list contains:
- In—configures
the direction of route-updates on which the community filter policy
needs to be applied as in. This indicates that the community filter
needs to be applied on received routes.
- Out—configures the direction of route-updates on which the community
filter policy needs to be applied as out. This indicates that the
community filter needs to be applied on routes advertised to peers.
- VRF Name / Context Name—default.
|
Buttons |
- Add—adds and
saves new configuration.
- Reset—resets to default value for respective
fields and discards all user inputs.
- Apply—modifies attributes for the selected
entry and saves the changes.
- Delete—deletes the selected entry.
|
Routes Community Set Status Table
Figure 4. Routes
Community Set Status Table
Screen Objective |
This screen allows the user to configure the
community attribute advertisement policy for a given destination. |
Navigation |
|
Fields |
- Select—select
the community value for which the policy needs to be deleted.
- IP Address—enter the IP Address for which
the community policy needs to be applied.
- Prefix Length—enter the IP prefix length
for the destination. This IP prefix length configures the number
of high-order bits in the IP address. These bits are common among
all hosts within a network. This value ranges from 1 to 32.
- Community set Status—select the community
set status for the route. The default option is Modify. The list
contains:
- Set—sends only the configured additive communities
with associated route
- SetNone—sends the associated route without communities.
- Modify—removes the associated route with received delete communities
and adds the configured additive communities.
Note: This field
can be set only if the local AS is
configured for the BGP4.
- VRF Name—default.
|
Buttons |
- Add—adds and
saves new configuration.
- Reset—resets to default value for respective
fields and discards all user inputs.
- Delete—deletes the selected entry.
|
Community Routes
Figure 5. Community Routes
Screen Objective |
This screen allows the user to configure additive
/ delete communities for a given destination. |
Navigation |
|
Fields |
- Select—select
the community value for which the community route needs to be deleted.
- Ip Address—enter the IP Address of the
destination.
- Prefix Length—enter the IP prefix length
for the destination. This IP prefix length configures the number
of high-order bits in the IP address. These bits are common among
all hosts within a network. This value ranges from 1 to 32.
- Community Value—enter the community value
for which the additive / delete communities need to be configured.
This value ranges from 65536 to 4294901759 and 4294967041 to 4294967043.
- Route Table—select to configure the additive
communities or delete communities for a given destination. The default
option is Addition. The list contains:
- Addition—adds associated
community value to the already existing communities in the route
update.
- Deletion—removes the community attribute from the route-prefix
when it passes through the filter process.
- VRF Name—default.
|
Buttons |
- Add—adds and
saves new configuration.
- Reset—resets to default value for respective
fields and discards all user inputs.
- Delete—deletes the selected entry.
|
Extended Community Filter Configuration
Figure 6. Extended
Community Filter Configuration
Screen Objective |
This screen allows the user to configure the
incoming / outgoing filter status for a given extended community
value. |
Navigation |
|
Fields |
- Select—select
the Extended Community value for which the filter status needs to
be modified or deleted.
- Community Value—the extended Community
Value for which the input / outgoing filtering policy is to be updated.
This field is an Octet string of maximum size 8.
- Filter Status—select the incoming / outgoing
filtering policy for the extended community. The default option
is Permit. The list contains:
- Permit—allows a particular
extended community attributes to be received or advertised in updates.
- Deny—filters the routes containing the extended community attribute
value in received or advertised updates.
- Filter Table/ Filter Type—select to configure
the incoming filter status or outgoing filter status for a given
extended community value. The default option is In. The list contains:
- In—configures the direction of route-updates on which the extended
community filter policy needs to be applied as in. This indicates
that the community filter needs to be applied on received routes.
- Out—configures the direction of route-updates on which the extended
community filter policy needs to be applied as out. This indicates
that the community filter needs to be applied on routes advertised
to peers.
- VRF Name / Context Name —default.
|
Buttons |
- Add—adds and
saves new configuration.
- Reset—resets to default value for respective
fields and discards all user inputs.
- Delete—deletes the selected entry.
|
Extended Community Set Status Table
Figure 7. Extended
Community Set Status Table
Screen Objective |
This screen allows the user to configure the
extended community attribute advertisement policy for a given destination. |
Navigation |
|
Fields |
- Select—select
the community value for which the policy needs to be deleted.
- IP Address—enter the IP Address of the
destination.
- Prefix Length—enter the IP prefix length
for the destination. This field configures the number of high-order
bits in the IP address. These bits are common among all hosts within
a network. This value ranges from 1 to 32.
- Community set Status—select the extended
community set status for the route. The default option is Modify.
The list contains:
- Set—sends only the configured additive
communities with associated route.
- SetNone—sends the associated route without communities.
- Modify—removes the associated route with received delete communities
and adds the configured additive communities.
Note: This
field can be set only if the local AS is configured for the BGP4.
- VRF Name—default.
|
Buttons |
- Add—adds and
saves new configuration.
- Reset—resets to default value for respective
fields and discards all user inputs.
- Delete—deletes the selected entry.
|
Routes Extended Community Table
Figure 8. Routes
Extended Community Table
Screen Objective |
This screen allows the user to configure additive
/ deletive extended communities for a given destination. |
Navigation |
|
Fields |
- Select—select
the IP Address for which the policy needs to be deleted.
- IP Address—enter the IP Address of the
destination.
- Prefix Length—enter the IP prefix length
for the destination. This field configures the number of high-order
bits in the IP address. These bits are common among all hosts within
a network. This value ranges from 1 to 32.
- Community value—enter the extended community
value for which the additive / delete communities need to be configured.
This field is an octet string of maximum size 8.
- Route Table—select to configure the additive
/ delete extended communities for a given destination. The default
option is Additive. The list contains:
- Additive—adds associated
extended community value with the already existing communities in
the route update.
- Deletive—removes the extended community attribute from the route-prefix
when it passes through the filter process.
- VRF Name / Context Name—default.
|
Buttons |
- Add—adds and
saves new configuration.
- Reset—resets to default value for respective
fields and discards all user inputs.
- Delete—deletes the selected entry.
|