BGP

BGP (Border Gateway Protocol) is used to build an AS connectivity graph that is used to prune routing loops and enforce policies at AS level.

BGP (Border Gateway Protocol) is an Inter AS (Autonomous Systems) Routing Protocol that manages the distribution of Network Layer Reachability Information (NLRI) across AS.

To access BGP screens, go to Layer 3 Management > BGP.

BGP Creation

Figure 1. BGP Creation


Screen Objective This screen allows the user to configure the basic settings of BGP.
Navigation

Layer 3 Management > BGP > BGP Context

Fields
  • AS Number—enter the local AS number (ASN). The default value is 1.
    Note:

    This field can be configured only if the state of the BGP system is set as Disabled in the Basic Settings screen.

    Note: When four-byte ASN is enabled, this value ranges from 1 to 4294967295.
    Note:

    When four-byte ASN is disabled, this value ranges from 1 to 65535.

    Note:

    Four-byte ASN can be enabled/disabled using Layer 3 Management > BGP > BGP Basic Settings screen.

  • BGP Context—default.
  • BGP State—select the status of the BGP system:
    • Enabled—enables the BGP system.
    • Disabled—disables the BGP system.
Buttons
  • Add—adds and saves new configuration.

BGP Basic Settings

Figure 2. BGP Basic Settings




Screen Objective This screen allows the user to configure the basic parameters of BGP in the system.
Note

To enable BGP, Route Redistribution must be enabled.

Use Layer 3 Management > RRD. The BGP system can be enabled and the basic BGP parameters for a context can be configured, only if the local AS Number is configured for the context using the Layer 3 Management > BGP > BGP Context > BGP Creation screen.
Navigation

Layer 3 Management > BGP > BGP Basic Settings

Fields
  • Select—select the context id for which the configurations need to be reapplied.
  • Context Id—0.
  • Status—select the status of BGP in the system. The default option is Disabled. The list contains.
    • Enabled—enables the BGP system.
    • Disabled—disables the BGP system.
  • Router Identifier—enter the BGP identifier of the local system. This router-id is advertised to other peers and identifies the BGP speaker uniquely. If loopback interface exists, the router ID is set to the highest address for loopback interface; otherwise, it is set to the highest IP configured on the IP interfaces.
    Note:

    This field can be configured explicitly only if the BGP speaker is administratively active. The explicitly configured value will be preserved even after the restart of the BGP.

    Note:

    Peering sessions will be reset if the BGP identifier is changed.

    Note:

    This field can be set only if the local AS number is configured.

    Note:

    To restore the default value for BGP identifier, this field must be configured as 0.0.0.0.

  • Synchronization—select the synchronization status within an AS. The default option is Disabled. The list contains:
    • Enabled—enables the synchronization between BGP and IGP. This allows routers and access servers within an autonomous system to have the route before BGP makes it available to other autonomous systems.
    • Disabled—disables the synchronization between BGP and IGP.
  • Default Local Preference—enter the default local preference value that is to be sent in updates to internal peers. The preference is sent to all routers and access servers in the local AS. This value ranges from 0 to 2147483647 with a default of 100.
  • Advertisement of Non-BGP routes—elect the peer type to which non-BGP routes must be sent. The default option is External and internal. The list contains:
    • External—sends non-BGP routes only to external peers.
    • External and internal—sends non-BGP routes to both external and internal peers.
Fields (cont)
  • Trace Level—enables the traces in BGP module. This value ranges from 0 to 16. This value represents the tracing levels as follows:
    • 0—All Failures
    • 1—All Resource Allocation Failures
    • 2—Init and Shutdown Trace
    • 3—Management Trace
    • 4—Control Path Trace
    • 5—Data Path Trace
    • 6—Peer Connection Trace
    • 7—Update Message Trace
    • 8—FDB Update Trace
    • 9—Keep-Alive Trace
    • 10—All Transmission Trace
    • 11—All Reception Trace
    • 12—Dampening Trace
    • 13—Events Trace
    • 14—High level Packet Dump
    • 15—Low level packet Dump
    • 16—Hex Dump
  • Debug Level—enables the debug dynamically in BGP module. This value ranges from 0 to 4294967295. This is a four-byte integer value specified for enabling the level of debugging. Each bit in the four-byte integer variable represents a level of debug.
  • Overlap Router Policy—select to set the overlap policy which configures the BGP speaker's policy for handling the overlapping routes. When an overlapping route is received, depending upon the configured policy, either the less-specific routes or more-specific routes or both routes are installed in the RIB tree. The default option is both. This list contains:
    • More-Specific—installs more specific routes in the RIB tree.
    • Less Specific—installs more specific routes in the RIB tree.
    • Both—installs both more specific and less specific routes in the RIB tree.
    Note:

    This field can be set only if Local ASN is configured and Global Admin Status is down

Fields (cont)
  • Always Compare MED—select the status of comparison of Multi Exit Discriminator (MED) for routes received from different autonomous systems. MED is one of the parameters considered for selecting the best path among many alternative paths. The path with a lower MED is preferred over a path with a higher MED. The default option is disable. The list contains:
    • Enabled—enables the comparison of MED for routes received from different autonomous system. This implies that MED is compared irrespective of the autonomous system from which the routes are received.
    • Disabled—disables the comparison of MED for routes received from different autonomous system. This implies that MED is compared only between routes received from the same autonomous system.
  • Default route redistribution—select the redistribution and advertisement status of the default route (0.0.0.0/0). The default option is Disable. The list contains:
    • Enable—enables redistribution and advertisement of default route to BGP peers. The default route advertisement is possible only if the default route is present in the IP FDB or is received from any peers.
    • Disable—disables redistribution and advertisement of the default route.
  • Default IPv4 unicast—select the status of default routing to IPv4-unicast. The default option is Enable. The list contains:
    • Enable—enables the negotiation of MP IPv4 Unicast Address Family Capability for that peer if a neighbor is created.
    • Disable—disables default routing to IPv4 unicast which implies that if a neighbor is created, IPv4 unicast capability will not be negotiated unless IPv4 unicast capability is explicitly configured for that neighbor.
    Note:

    This affects the negotiation of the MP IPv4 Unicast Address Family Capability for newly created peers but will not affect the MP IPV4 Unicast negotiation status of the already existing peers.

  • Client to client reflection—select the desired support of the Route Reflector in the cluster. By default, the Client to client reflection value is set as client support. By default, the clients of a route reflector are not required to be fully meshed and the routes from a client are reflected to other clients. If the clients are fully meshed, route reflection is not required. The list contains:
    • None—sets Route Reflector support in the cluster as none. This is a read only field when set as none.
    • Client support—sets Route Reflector support in the cluster as client support.Non-client Support—sets Route Reflector support in the cluster as Non-client support
  • AS Confed Best-path compare MED—enter the Local Confederation Identification number of the AS confederation. This value ranges from 0 to 4264697295. The default value is 0.
    Note:

    When confed id is set to a non-zero value, this value must be reset to zero before reconfiguring confed id.

Fields (cont)
  • Capability support—select the status of the Capability Advertisement Support.
    • True—enables Capability Advertisement Support
    • False—disables Capability Advertisement Support
    Note:

    This field can be set only if Global Admin Status is down and Local AS is configured.

  • Bgp Trap—select the trap status to be set for BGP. This status is used to control the sending of BGP notification messages to SNMP manager. The BGP notification messages are sent when any error is detected in input BGP messages received from peer or in the BGP state event machine. These notification messages are used to close an active session and to provide information about the closure of the session. The default option is Enabled. The list contains:
    • Enabled—enables the trap notification for the BGP system.
    • Disabled—disables the trap notification for the BGP system.
  • Internal BGP Routes Redistribution—elect the status of the IBGP routes redistribution to other IGP protocols. The default option is Disabled. The list contains:
    • Enabled—enables IBGP routes to be redistributed to other IGP protocols.
    • Disabled—disables IBGP routes to be redistributed to other IGP protocols.
    Note:

    This field can be set only if Global Admin Status is down and Local AS is configured.

  • 4 Byte ASN Support Status—select the 4 Byte ASN Support status in the BGP system. The default option is Enabled. The list contains:
    • Enable—enables 4-byte ASN support in BGP. If this is enabled, the Remote As value ranges between 1 and 4294967295.
    • Disable—disables 4-byte ASN support in BGP. If this is disabled, the Remote As value ranges between 1 and 65535.
    Note:

    This field can be set only if Global Admin Status is down and Local AS is configured.

  • VPN4 Capability—select the standard VPNv4 address prefixes carrying capability. The default value is Disable. The list contains:
    • Enable—enables configuration of the session that carries standard vpnv4 address prefixes. BGP4 VPN allows the Service Providers to use their IP backbone to provide VPN services to their customers. BGP distributes VPN routing information across the provider’s backbone, and MPLS is used to forward VPN traffic from one VPN site to another.
    • Disable—disables configuration of the session that carries standard VPNv4 address prefixes.
Fields (cont)
  • Label Allocation policy—select the label allocation policy which is used for allocating the VPN label to be used for advertising the VPN routes. The default value is per-vrf. The list contains
    • per-vrf—sets label allocation policy as per vrf to advertise all routes learnt in the router with the same label.
    • per-route—sets label allocation policy as per route to advertise all routes learnt in the router with the unique label.
Buttons
  • Add—adds and saves new configuration.

BGP Settings

Figure 3. BGP Settings


Screen Objective This screen allows the user to configure the BGP Settings.
Note This screen can be configured only when the BGP status is enabled using Layer 3 Management > BGP > Basic Settings > BGP Basic Settings screen.
Navigation

Layer 3 Management > BGP > BGP Settings

Fields
  • Select—select the Cluster ID for which the configurations need to be modified.
  • Cluster ID—enter the Cluster ID of the Router Reflector of the BGP cluster which has more than one route reflector. By default, when the BGP speaker acts as Route Reflector, the BGP Identifier is used as the cluster ID. To increase redundancy and avoid a single point of failure, a cluster might have more than one route reflector. In this case, all route reflectors in the cluster must be configured with the 4-byte cluster ID so that a route reflector can recognize updates from route reflectors in the same cluster.
  • BGP Next Hop Processing Interval—enter the interval at which next hops are monitored for reachability. This value ranges from 1 to 120. The default value is 60.
  • Default Metric—enter the default metric value for the IGP routes and static route. If configured to 0, the metric received from the IGP route will be used. If configured to other value, the MED value of the redistributed routes takes this value. This value has no effect on direct routes. This value ranges from 1 to 2147483647. The default value is 0.
  • Admin Status—select the admin status of BGP. The default option is Disable. The list contains:
    • Enabled—enables the BGP system.
    • Disabled—disables the BGP system.
  • Capability Support—select the Capability Advertisement Support status. The default option is True. The list contains:
    • True—enables Capability Advertisement Support.
    • Disabled—disables the BGP system.
    EBGP Multipath Count—enter the maximum number of external BGP (EBGP) multipath routes to be added per destination network in the routing table. This value ranges from 1 to 64.
  • IBGP Multipath Count—enter the maximum number of IBGP multipath routes to be added per destination network in the routing table. This value ranges from 1 to 64.
  • EIBGP Multipath Count—enter the maximum number of external plus internal BGP (EIBGP) multipath routes (with same AS PATH) to be added per destination network in Routing table. This value ranges from 1 to 64.
  • Table version—displays the table version which is the total number of valid routes learnt in the system. This is an integer value which is incremented by 1 when a valid route is learnt.
  • Context Id—0.
Buttons
  • Add—adds and saves new configuration.

Neighbor Configuration

Figure 4. Neighbor Configuration


Screen Objective This screen allows the user to configure the BGP Neigbors.
Note This screen can be configured only if the Route Re-distribution (RRD) status is enabled with valid ASN and router ID from the Layer 3 Management > RRD.
Navigation

Layer 3 Management > BGP > Neighbors

Fields
  • Select—select the neighbor for which the configurations need to be modified.
  • Peer Address—enter the remote IP address of the BGP peer.
    Note:

    For a peer address with external AS, route reflector client cannot be set as Client.

  • Remote AS—enter the remote ASN of the peer. This value ranges from 1 to 4294967295.
    Note:

    The admin status of the peer can be made up only if this field is configured for a valid ASN.

    Note:

    When four-byte ASN is enabled, this value ranges from 1 to 4294967295.

    Note:

    When four-byte ASN is disabled, this value ranges from 1 to 65535.

    Note:

    Four-byte ASN can be enabled/disabled using Layer3 Management > BGP > Basic Setting>BGP Basic settings screen.

  • Configured BGP Maximum Prefix Limit—enter the prefix limit value to set upper bound on the number of address prefixes to be accepted by BGP speaker from a neighbor. The system will not process the prefixes exceeding the upper limit. This value ranges from 1 to 2147483647. The default value is 100.
    Note:

    The default value is calculated based on the following formula: Maximum number of routes in the routing table / Maximum number of peers supported by BGP.

  • Configured Connect Retry Count—enter the retry count to specify the maximum number of times a BGP peer should try for issuing a TCP-Connect with its neighboring peers. This value ranges from 1 to 50. The default value is 5.
  • Automatic Start—select the automatic start status for the BGP session with the associated peer. The automatic start will not occur, if the IdleHold timer value of the peer exceeds its maximum threshold value. The default option is Disable. The list contains:
    • Disable—disables automatic initiation of the BGP session with the peer for starting the peer status.
    • Enable—enables automatic starting of peer session from the idle state after peer idle hold time once the BGP peer session is brought down either by the following:
      • Automatic stop feature
      • Reception of invalid BGP message
Fields (cont)
  • Automatic Stop—select the automatic stop status for the BGP connection with the associated peer. The default option is Disable. The list contains:
    • Disable—disables automatic stopping of BGP connection with the associated peer, as the connect retry count will be set as 0.
    • Enable—enables automatic stopping of BGP connection with the associated peer after the BGP peer attains configured maximum number of TCP connect retry count value. The allocated resources are released, and the peer remains in idle state. The peer session initiation is once again started based on the automatic start status, peer idle hold timer and damp peer oscillation status.
  • Damp Peer Oscillations—select the damp peer oscillation status that controls the usage of additional logic to dampen peer oscillations in states other than established. The default option is Disable. The list contains:
    • Disable—disables utilization of any logic to dampen the oscillations of BGP peers by BGP connection (disables peer connection damping).
    • Enable—utilization additional logic to dampen the oscillations of BGP peers by BGP connection during a series of automatic start and stop operations in the IDLE state. For each successive damp oscillations, the current idle hold timer value will be increased twice its previous value. This happens through internal logic.
  • Delay OPEN—select the delay open status that controls the option to apply delay in sending of open messages. The open message is the initial message sent by the BGP peers after establishing a TCP connection to open a BGP session between them. The default option is Disable. The list contains:
    • Disable—disables the delay option for sending open messages, which implies that open messages are sent to the remote BGP peer without any delay.
    • Enable—delay in sending open messages to the remote BGP peer for a configured open delay time period. This delay allows the remote peer to send the first open message.
Fields (cont)
  • EBGP MultiHop—select the EBGP MultiHop option which enables/disables the BGP4 speaker to establish connections to external peers residing on network that are not directly connected. The default option is Disable. The list contains:
    • Disable—disables BGP to establish connection with external peers residing on networks that are not directly connected. If EBGP MultiHop is disabled and external BGP peers are indirectly connected, then BGP peer session will not be established.
    • Enable—enables BGP to establish connection with external peers residing on networks that are not directly connected. If external BGP peer are not connected directly, then EBGP MultiHop is enabled to initiate the connection with that external peer.
    Note:

    This field is applicable only for the directly connected EBGP peers and not applicable for the internal peers.

  • Next Hop—whether the next hop attribute sent in the update message to the peer has to be generated automatically or self. This is useful in non-meshed networks where BGP neighbors may not have direct access to all other neighbors on the same IP subnet. The default option is automatic. The list contains:
    • automatic—generates the next hop based on the IP address of the destination and the present next hop in the route information.
    • self—sets the sender local address as the next hop attribute.
  • Source Address—enter the address to be used as the source address for the TCP session initiated with the peer.
    Note:

    The configured peer address is set as the source address, if no value is configured for the source address

  • Gateway Address—enter the gateway router’s address to be used as NextHop in the routes advertised to the peer.
  • Default originate—select he status of the advertisement of the default route to the peer or neighbor for use as a default route. The default option is Disable. The list contains:
    • Disable—disables the advertisement of the default route.
    • Enable—enables the advertisement of the default route.
    Note:

    This field overrides the global default route configuration and always sends a default route to the peer with self next-hop. This advertisement occurs irrespective of the presence of default route in FDB.

Fields (cont)
  • Community Send status—select the status of the send community attribute to a BGP neighbor. The default option is send. The list contains:
    • none—sets Community Send status as none.
    • send—sends community attribute to a BGP neighbor and enables advertisement of community attributes (standard/extended) to peer
    • dontSend—disables advertisement of standard community attributes to peer the advertisement of the default route.
  • Extended Community Send status—select the status of extended community send attribute of the BGP peer. The BGP extended community is used to label BGP routing information for controlling the distribution of the information. The default option is send. The list contains:
    • none—sets extended Community Send status as none.
    • send—sends extended community attribute to a BGP neighbor and enables advertisement of community attributes (standard/extended) to peer
    • dontSend—disables advertisement of standard community attributes to peer the advertisement of the default route.
  • Route Reflector Client—the Route Reflector Client status of the peer. This status is used to define client and non-client peers for implementing route reflection. The default option is nonClient. The list contains:
    • nonClient—Configures the peer as non-client peer, which denotes that the peer is outside the cluster
    • Client—Configures the peer as client peer, which denotes that the peer is within the clustr.

    The route reflection mechanism operates as follows:

    • A cluster system acting as route reflector sends a route to all client peers within the cluster, if the route is received from a nonclient peer.
    • The cluster system acting as route reflector sends a route to all nonclient peers and all client peers except the originator, if the route is received from a client peer.
    Peer Connection passive—select the BGP peer connection status to control the initiation of session from remote peer or speaker. The default option is Enable. The list contains:
    • Enable—sets the peer connection as passive. BGP speaker waits for the remote peer to initiate the session with the peer.
    • Disable—sets the peer connection as active. BGP speaker initiates the session with the peer.
Fields (cont)
  • TCP Send Buffer Size—enter the TCP send window buffer size. This value ranges from 4096 to 65536. The default value is 65536.
  • TCP Receive Buffer Size—enter the TCP Receive window buffer size. This value ranges from 4096 to 65536. The default value is 65536.
  • EBGP Hop Limit—enter the maximum hop limit value that is used during connection with external peers. This value does not have any effect on connection with internal peers. This value ranges from 1 to 255. The default value is 1.
    Note:

    BGP speaker accepts or attempts connection to external peers residing on network that are not directly connected but separated by the configured hop limit value.

  • Authentication—select the desired authentication mode for the BGP connection. The default option is None. The list contains:
    • None—indicates no authentication is set.
    • MD5—sets authentication type as Message Digest 5 (MD5) where authentication is set on a TCP connection between two BGP peers where each segment sent on the TCP connection between the peers is verified.
    • TCP-AO—indicates TCP-AO configurations for the specified BGP Peer.
  • Password—enter the TCP MD5 Authentication Password that has to be sent with all TCP packets originated from the peer. This value is a string of maximum size 80.
    Note:

    This field is enabled only when Authentication type is set as MD5

  • TCP-AO MKT—enter the TCP-AO MKT key-id which needs to be associated with this peer. This value’s range is from 0 to 255.
    Note:

    This field is enabled only when Authentication type is set as TCP AO.

    Note:

    This value should be the MKT id created using the Layer3 Management > BGP > TCP-AO Authentication > TCP-AO MKT Configuration screen

Fields (cont)
  • Peer Status—select the desired state of the BGP peer connection. This is used to manually start or stop a BGP peer connection. The default option is start. The list contains:
    • stop—generates BGP stop event to manually stop the BGP session with the peer. The BGP stop event is automatically generated:
      • once the automatic stop feature is enabled and
      • the peer idle hold time exceeds its maximum threshold value.
    • start—generates BGP start event to manually initiate the BGP session with the peer. The BGP start event is generated only after configured peer idle hold time. The manual start is required for the peers damped using damp peer oscillation feature. The BGP start event is automatically generated after peer idle hold time to start BGP session in idle state when
      • Automatic start feature is enabled, and
      • BGP session is brought down either by automatic stop feature or through reception of invalid BGP message.
    Note:

    The peer status is internally set as auto-start when automatic start feature is enabled.

  • BFD Monitoring—select the BFD monitoring status for the BGP peer. The default value is set as disable. The list contains:
    • Disable—specifies that BFD monitoring is disabled. The BGP deregisters with BFD if it is already registered.
    • Enable—specifies that BFD monitoring is enabled. When enabled, BGP will register with BFD for IP path monitoring when the session state becomes Established.
  • VRF 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.

BGP MED Configuration

Figure 5. BGP Creation


Screen Objective This screen allows the user to configure the Multi-Exit Discriminators (MED) values that are to be assigned to routes learnt from BGP peers.
Navigation

Layer 3 Management > BGP > Multi-Exit Discriminators

Fields
  • Select—select the MED entry for which the configurations need to be modified.
  • MED ID—enter the MED Index value which is the index value of the BGP MED Table. This value ranges from 1 to 100.
  • Remote AS—enter the remote ASN with which BGP MED is to be associated. This value ranges from 0 to 4294967295. The default value is 0.
    Note:

    When four-byte-ASN is enabled, this value ranges from 0 to 4294967295.

    Note:

    When four-byte-ASN is disabled, this value ranges from 0 to 65535.

    Note:

    Four-byte ASN can be enabled/disabled using Layer3 Management > BGP > Basic Setting> BGP Basic settings screen

  • Address Family / AFI—select the type of IP address prefix in the NLRI field in the update. The list contain:
    • ipv4—sets the type of IP address prefix as IP version 4.
    • ipv6—sets the type of IP address prefix as IP version 6.
    Note:

    This field should be configured before configuring the IP Address Prefix.

  • Sub-Address Family / SAFI—select the sub-sequent address family of IP address prefix in the NLRI field in the update. The default option is unicast. The list contains:
    • unicast—sets the sub-sequent address family of IP address prefix as unicast.
    • labelledIpv4—sets the sub-sequent address family of IP address prefix as labeled IP version 4.
    • vpnv4—sets the sub-sequent address family of IP address prefix as VPN version 4.
    Note:

    This field should be configured before configuring the IP Address Prefix.

  • IP Address Prefix—enter the IP address prefix in the NLRI field on which local-preference policy needs to be applied.
  • IP Address Prefix Length—enter the length (in bits) of the IP address prefix in the NLRI field. This value ranges from 0 to 32 bits. The default value is 0.
Fields (cont).
  • Intermediate AS—enter a list of intermediate AS numbers through which the route update is expected to travel. This is a comma separated list of AS numbers that are to be checked against the AS_PATH attribute of the updates. This value is a string of maximum size 100.
  • Direction—select the direction of application of the MED Policy. The default option is In. The list contains:
    • In—indicates the updates on the received routes
    • Out—indicates the updates that needs to be advertised to peers on the route
  • Value—enter the MED value assigned to the MED attribute for the route present in NLRI. This value ranges from 0 to 2147483647. The default value is 0.
  • Preference—select the preference status which denotes whether the value present in this entry takes precedence when the attribute is already present in the update message that has been received. The default option is False. The list contains:
    • True—indicates that the value present in this entry takes precedence when the attribute is already present in the update message that has been received
    • False—indicates that the value present in this entry does not take precedence
  • Status—select the preference status which denotes whether the value present in this entry takes precedence when the attribute is already present in the update message that has been received. The default option is False. The list contains:
    • Up—sets MED Status as UP.
    • Down—sets MED Status as Down.
  • 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.

BGP Local Preference Configuration

Figure 6. BGP Local Preference Configuration


Screen Objective This screen allows the user to configure the Local Preference values for the routes.
Navigation

Layer 3 Management > BGP > Local Preferences

Fields
  • Select—select the Local Preference Identifier entry for which the configurations need to be modified (this is a radio button in the first column of the table).
  • Local preference ID—enter t Local Preference ID for the route This value ranges from 1 to 100.
  • Remote AS—enter the enter the Remote ASN that identifies the BGP router to other routers and tags the routing information passed along. This value ranges from 0 to 4294967295. The default value is 0.
    Note:

    When four-byte-ASN is enabled, this value ranges from 0 to 429496729.

    Note:

    When four-byte-ASN is disabled, this value ranges from 0 to 65535.

    Note:

    Four Byte ASN can be enabled/disabled using Layer3 Management > BGP > Basic Setting > BGP Basic settings screen.

  • Address Family / AFI—select the type of IP address prefix in the NLRI field in the update. The list contain:
    • ipv4—sets the type of IP address prefix as IP version 4.
    • ipv6—sets the type of IP address prefix as IP version 6.
    Note:

    This field should be configured before configuring the IP Address Prefix.

  • Sub-Address Family / SAFI—select the sub-sequent address family of IP address prefix in the NLRI field in the update. The default option is unicast. The list contains:
    • unknown—sets the sub-sequent address family of IP address prefix as unknown which implies that any sub-sequent address family can be used for IP address prefix.
    • unicast—sets the sub-sequent address family of IP address prefix as unicast.
    • labelledIpv4—sets the sub-sequent address family of IP address prefix as labeled IP version 4.
    • vpnv4—sets the sub-sequent address family of IP address prefix as VPN version 4.
    Note:

    This field should be configured before configuring the IP Address Prefix.

  • IP Address—enter the IP address prefix in the NLRI field. The default value is 0.0.0.0.
  • IP Address Prefix Length / Prefix Length—enter length (in bits) of the IP address prefix in the NLRI field. This value ranges from 0 to 32 bits for ipv4 address and 0 to 128 for ipv6 address type. By default, IP Address Prefix Length is set as 0 bits.
Fields (cont)
  • Intermediate AS—enter a list of intermediate Autonomous system numbers through which the route update is expected to travel. This is a comma separated list of ASNs that are to be checked against the AS_PATH attribute of the updates. This value is a string of maximum size 10.
  • Direction—select the direction of application of the Local Preference Policy with which the entry is to be associated. The default option is In. The list contains:
    • In—indicates the updates on the received routes.
    • Out—indicates the updates that needs to be advertised to peers on the route
  • Value—enter the value assigned to the LP (Local Preference) Attribute for the route present in NLRI. This value ranges from 0 to 2147483647. The default value is 100.
  • Preference—select the preference status which denotes whether the value present in this entry takes precedence when the attribute is already present in the update message that has been received. The default option is false. The list contains:
    • True—indicates that the value present in this entry takes precedence when the attribute is already present in the update message that has been received.
    • False—indicates that the value present in this entry does not take precedence
  • Status—select the status of the Local Preference routes learnt by BGP peers. The default option is Down. The list contains:
    • Up—sets Local Preference Status as UP.
    • Down—sets Local Preference Status as Down.
  • 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.

BGP Filter Configuration

Figure 7. BGP Filter Configuration


Screen Objective This screen allows the user to configure an entry in Update Filter Table which contains rules to filter out updates based on the AS from which they are received, NLRI, and AS through which it had passed.
Navigation

Layer 3 Management > BGP > Filters

Fields
  • Select—select the Filter Identifier entry for which the configurations need to be modified (this is a radio button in the first column of the table).
  • Filter ID—enter the filter index. This value ranges from 1 to 100.
  • Remote AS—enter the remote ASN that identifies the BGP router to other routers and tags the routing information passed along. This value ranges from 0 to 4294967295. The default value is 0.
    Note:

    When four-byte-ASN is enabled, this value ranges from 0 to 429496729.

    Note:

    When four-byte-ASN is disabled, this value ranges from 0 to 65535.

    Note:

    Four byte ASN can be enabled/disabled using Layer3 Management > BGP > Basic Setting>BGP Basic settings screen.

  • Address Family / AFI—select the type of IP address prefix in the NLRI field in the update. The list contain:
    • ipv4—sets the type of IP address prefix as IP version 4.
    • ipv6—sets the type of IP address prefix as IP version 6.
    Note:

    This field should be configured before configuring the IP Address Prefix.

  • Sub-Address Family / SAFI—select the sub-sequent address family of IP address prefix in the NLRI field in the update. The default option is unicast. The list contains:
    • unknown—sets the sub-sequent address family of IP address prefix as unknown which implies that any sub-sequent address family can be used for IP address prefix.
    • unicast—sets the sub-sequent address family of IP address prefix as unicast.
    • labelledIpv4—sets the sub-sequent address family of IP address prefix as labeled IP version 4.
    • vpnv4—sets the sub-sequent address family of IP address prefix as VPN version 4.
    Note:

    This field should be configured before configuring the IP Address Prefix.

  • IP Address—enter the IP address prefix in the NLRI field. The default value is 0.0.0.0.
  • IP Address Prefix Length / Prefix Length—enter length (in bits) of the IP address prefix in the NLRI field. This value ranges from 0 to 32 bits for ipv4 address and 0 to 128 for ipv6 address type. By default, IP Address Prefix Length is set as 0 bits.
Fields (cont)
  • Intermediate AS—enter a list of intermediate AS numbers through which the route update is expected to travel. This is a comma separated list of AS numbers that are to be checked against the AS_PATH attribute of the updates. This value is a string of maximum size 10.
  • Direction—select the direction of application of filters with which the entry is to be associated. The default option is In. The list contains:
    • In—indicates the updates on the received routes
    • Out—indicates the updates that needs to be advertised to peers on the route
  • Action—select the status that controls addition or deletion of the non bgp routes. The default option is Deny. The list contains:
    • Allow—allows addition of non-BGP routes.
    • Deny—denies addition of non-BGP routes.
  • Status—select the status of the routes learnt by BGP peers. The default option is Down. The list contains:
    • Up—sets BGP Filter Status as UP
    • Down—sets BGP filter Status as Down.
  • 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.

BGP Route Aggregation Configuration

Figure 8. BGP Route Aggregation Configuration


Screen Objective This screen allows the user to configure the aggregation of the routing information. This creates an aggregate entry in a BGP or multiprotocol BGP routing table if any more-specific BGP or multiprotocol BGP routes are available that fall in the specified range. The entries in the table specify the IP address based on which the routing information has to be aggregated. The aggregate route will be advertised as coming from autonomous system. The atomic aggregate attribute will be set only if some of the information in the AS PATH is missing in the aggregated route; otherwise, it will not be set.
Navigation

Layer 3 Management > BGP > Route Aggregation

Fields
  • Select—select the neighbor for which the configurations need to be reapplied.
  • ID—enter the index to BGP Route Aggregation table. This value ranges from 1 to 100.
  • Address Family / AFI—select the type of IP address prefix in the NLRI field in the update. The list contain:
    • ipv4—sets the type of IP address prefix as IP version 4.
    • ipv6—sets the type of IP address prefix as IP version 6.
    Note:

    This field should be configured before configuring the IP Address Prefix.

  • Sub-Address Family / SAFI—select the sub-sequent address family of IP address prefix in the NLRI field in the update. The default option is unicast. The list contains:
    • unknown—sets the sub-sequent address family of IP address prefix as unknown which implies that any sub-sequent address family can be used for IP address prefix.
    • unicast—sets the sub-sequent address family of IP address prefix as unicast.
    • labelledIpv4—sets the sub-sequent address family of IP address prefix as labeled IP version 4.
    • vpnv4—sets the sub-sequent address family of IP address prefix as VPN version 4.
    Note:

    This field should be configured before configuring the IP Address Prefix.

  • IP Address—enter the IP address prefix in the NLRI field.
  • IP Address Prefix Length / Prefix Length—enter the length (in bits) of the IP address prefix in the NLRI field. This value ranges from 0 to 32 for ipv4 address and 0 to 128 bits for ipv6 address.
  • Route Advertise—select the route updates that should be sent to the peers. The default option is Summary-only. The list contains:
    • Summary Only—indicates that only the summarized route has to be advertised to peers.
    • All—indicates that both the summary and the more-specific routes based on which the summary entry was generated, have to be advertised to the peers.
Fields (cont)
  • As-Set—select the generation status of autonomous system set path information. The default option is Disable. The list contains
    • Enable—enables the generation of AS set path information.
    • Disable—disables the generation of AS set path information.
  • Suppress-Map—enter the name for suppress route-map. The route map contains the rules for suppressing the routes while aggregation. When suppress-map configuration is used along with summary-only option, summary-only configuration does not have any effect. And the more-specific routes that the suppress-map suppresses are not advertised. Other routes are advertised in addition to the aggregated route This value is a string of maximum size 20.
  • Advertise-Map—enter the name for advertise route-map. The route map contains the rules for advertising the routes during aggregation. When advertise-map is used, only advertise-map influences the creation of aggregate entry. In absence of advertise-map, the aggregate route inherits the attributes of the more specific routes, both suppressed and unsuppressed. This value is a string of maximum size 20.
  • 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.

BGP Timer Configuration

Figure 9. BGP Timer Configuration


Screen Objective This screen allows the user to configure the timer related parameters for the peer.
Note The BGP peer timer entry is created ONLY for the peer entries created in the Neighbor Configuration screen. Generate peer entries before creating BGP Timer configuration.
Navigation

Layer 3 Management > BGP > Timer

Fields
  • Address Type—displays the address type of the remote peer. This is a read-only field. The type can be:
    • ipv4—denotes the remote peer IP address type as IP version 4.
    • ipv6—denotes the remote peer IP address type as IP version 6.
  • Ip Address—displays the IP address of the BGP peer; a read-only field.
  • Keep Alive—enter the maximum time interval between successive keepalive messages exchanged between two peers. This value ranges from 0 to 21845 seconds. The optimal value is 30 seconds.
    Note:

    Periodical KEEPALIVE messages will be sent to the peer after the BGP connection is established.

  • Hold time—enter the timer interval that a BGP will wait, before it decides that a connection to the peer is to be turned down. The system declares a peer as dead, after ensuring that a keepalive message is not received within this time period from the peer. This value ranges from 3 to 65535 seconds or 0. The optimal value is 90.
  • Route Advertisement interval—enter the minimum interval between router advertisements (in seconds). This value ranges from 1 to 65535 seconds. The optimal value is 30 seconds. This is a read-only field.
  • Min As Origination interval—enter minimum time between advertisements of changes within the speaker’s AS (in seconds). This value ranges from 1 to 65535 seconds. The default value is 15.
  • Connect retry interval—enter the time (in seconds) for waiting before the router attempts to reconnect with the BGP neighbor after failing to connect. This value ranges from 1 to 65535 seconds. The default value is 120.
  • Idle Hold interval—enter the time interval during which the BGP peer is held in idle state prior to the next automatic restart. This value ranges from 1 to 65535 seconds. The default value is 60. For each successive damp oscillations, the current IdleHold time value will be increased twice its previous value. This will happen through internal logic.
    The IdleHold Interval can be configured if either:
    • Automatic start feature is enabled, or
    • Damp peer oscillation feature is enabled
    Note:

    If both damp peer oscillation and automatic start features are disabled, the existing value is always set instead of the newly configured value.

Fields (cont)
  • Delay Open interval—enter the amount of time the BGP peer should postpone sending open message to the remote peer. This delay allows the remote peer to send the first open message. This value ranges from 0 to 65535 seconds. The default value is 0 seconds.
    Note:

    This time can be configured only if the Delay Open status is set as enabled. Otherwise, the existing value is always set instead of the newly configured value.

  • Context Name—default.
Buttons
  • Apply—modifies attributes for the selected entry and saves the changes.

BGP GR Settings

Figure 10. BGP GR Settings


Screen Objective This screen allows the user to configure the Graceful Restart (GR) settings of the BGP. GR capability in a router which allows forwarding of data packets to continue along known routes, while the routing protocol information is being restored following a processor switchover. When GR is enabled, peer networking devices are informed, through protocol extensions prior to the event, of the stateful switch over-capable routers ability to perform GR. When a switch over occurs, the peer will continue to forward to the switching over router as instructed by the GR process for each particular protocol, even though in most cases the peering relationship needs to be rebuilt. Essentially, the peer router will give the switching over router a "grace" period to re-establish the neighbor relationship, while continuing to forward to the routes from that peer.
Navigation

Layer 3 Management > BGP > GR Settings

Fields
  • GR Admin Status—select the GR capability status in the BGP speaker. The default option is Disabled. The list contains:
    • Enabled—enables the GR capability in the BGP speaker.
    • Disabled—disables the GR capability in the BGP speaker.
    Note:

    To set the GR parameters, the BGP GR admin status should be disabled.

  • Restart Time—enter the time, in seconds, for the BGP session to be re-established after a restart. The default value should be less than or equal to Hold Time carried in open message. This value ranges from 1 to 4096 seconds. The default value is 90 seconds.
  • Selection Deferral timer Value—enter the upper limit time until which a router defers its route selection. This timer value should be large enough for providing all peers of the Restarting Speaker with enough time to send all routes to the Restarting Speaker. This value ranges from 60 to 1800 seconds. The default value is 60.
  • Stale Timer Interval—enter the time, in seconds, for the BGP session to be re-established after a restart. The default value should be less than or equal to Hold Time carried in open message. This value ranges from 1 to 4096 seconds. The default value is 90 seconds.
  • Restart support—select the router support for the BGP graceful restart feature. The default option is None. The list contains:
    • None—sets Restart Support as None which implies that Restart support is not provided for the Graceful Restart feature.
    • Planned—sets Restart Support as Planned.
    • Both—sets Restart Support as both planned and unplanned.
  • Restart Reason—select the router restart reason code of the BGP graceful restart feature. The default option is Software restart. The list contains:
    • Unknown—sets Restart Reason as unknown e.g. this code is to be used when a system restarts due to unplanned events (restarting after a crash).
    • Software restart—sets Restart Reason as Software restart; this is to be used where a system restarts due to software restart.
    • Software upgrade—sets restart reason as software upgrade; to be used where a system restarts due to reloading / upgrading of software.
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.

TCP-AO MKT Configuration

Figure 11. TCP-AO MKT Configuration


Screen Objective This screen allows the user to configure TCP-AO MKT (Authentication Option Master Key Tuple) in the specified BGP instance.
Navigation

Layer 3 Management > BGP > TCP-AO Authentication

Fields
  • Select—select the neighbor for which the configurations need to be modified.
  • KEY-ID—enter the local ASN. This value ranges from 1 to 4294967295. The default value is 1.
  • Receive-Key-ID—enter the Receive Key-id of the MKT. The MKT that is ready at the sender to be used to authenticate received segments is indicated to the peer by filling the receive key id of the MKT of the TCP-AO OPTION in the TCP header. This value ranges from 0 to 255.
  • Crypto Algorithm—select the crypto Algorithm used for TCP-AO (Authentication Option Master Key Tuple) in the specified BGP instance. MAC or KDF calculation. TCP-AO uses cryptographic algorithms to convert MKTs, which can be shared across connections into unique traffic keys for each connection. These are called Key Derivation Functions (KDFs) and are specified in RFC5926. The default option is hmac-sha-1. The list contains:
    • HMAC-SHA-1—sets algorithm type as HMAC-SHA-1.
    • AES-128—sets algorithm type as AES-128.
Fields (cont)
  • Password—enter the password/ Master Key corresponding to the MKT. This is an octet string value with the maximum size 80
  • TCP-OPTIONS—sets the exclude TCP option which excludes the options other than TCP-AO during MAC calculation. If this is not set, TCP-AO MAC will be calculated on TCP segment including all other TCP options.
    • Exclude –excludes TCP options other than TCP-AO during MAC calculation.
    • Include—includes all TCP options; while calculating TCP-AO, MAC will be calculated on TCP segment including all other TCP options.
  • 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.

Peer Group Configuration

Figure 12. Peer Group Configuration


Screen Objective This screen allows the user to create a BGP peer group and configure its parameters. The peer group configurations are applicable to all peers present in the peer group.
Navigation

Layer 3 Management > BGP (cont.) > Peer Group 1

Fields
  • Select—select the neighbor for which the configurations need to be modified.
  • Peer Group Name—enter the Peer Group Name for configuring BGP peer group. The members of this peer group will inherit the characteristics configured with this screen. This value is a string of maximum size 20.
    Note:

    For Peer Address with external AS, route reflector client cannot be set as Client.

  • Remote AS—enter the Remote ASN associated with the BGP peer group. This value ranges from 1 to 4294967295.
    Note:

    When four-byte ASN is enabled, this value ranges from 1 to 4294967295.

    Note:

    When four-byte ASN is disabled, this value ranges from 1 to 65535.

    Note:

    Four-byte ASN can be enabled/disabled using Layer3 Management > BGP > Basic Setting > BGP Basic settings screen.

  • Hold time—enter the timer interval for the Hold Time configured for the BGP speaker with all peers configured for this peer group. This value is placed in an OPEN message sent to the peers by the BGP speaker. This value ranges from 3 to 65535 seconds or can be configured as zero. If it is configured as 0, the Hold Time will be not established with the peer. The default value is 90 seconds.
  • Keep Alive Time—enter the Keep Alive Time (in seconds) for the BGP speaker with all peers configured for this peer group. The value of this object will only determine the KEEPALIVE messages frequency relative to the Hold Time. The keep-alive value must always be less than the configured hold-time value A reasonable maximum value for this timer is one third of the Hold Time value. If this value is zero (0), no periodical KEEPALIVE messages are sent to the peers after the BGP connection is established. This value ranges from 1 to 21845 seconds. The default value is 30.
  • Connect Retry Interval—enter the Connect Retry Interval (in seconds) for the peers in this peer group. This is the time interval after which a transport connection with a peer is re-initiated. This value ranges from 1 to 65535 seconds. The default value is 30.
  • Min AS Originator Interval—enter the AS Originator Interval for the peers in this peer group. This is the time-interval (in seconds) for spacing successive route-updates originating within the same AS. The default value is 15 seconds.
Fields (cont)
  • Min Route Advertisement Interval—enter the Min Route Advertisement Interval for the peers in this peer group. This is the time-interval (in seconds) for spacing advertisement of successive external route-updates to the same destination. This value ranges from 1 to 65535 seconds. The default value is 30 seconds for EBGP connections and 5 seconds for IBGP connections.
  • Automatic Start—select the Automatic Start status for the BGP session with the associated peers in the peer group. The default option is Disable. The list contains:
    • Disable—disables the BGP session with the associated peer automatically. The BGP session with the peer has to be manually initiated.
    • Enable—starts the BGP session with the associated peer automatically. The peer session is automatically started in idle state, after a BGP Peer session is brought down either by Auto stop or through reception of invalid BGP message. The BGP session is automatically started after an interval specified by idle hold timer.
  • Automatic Stop—select the status to enable/disable the auto stop option for stopping the BGP peer and BGP connection automatically. The default option is Disable. The list contains:
    • Disable—disables the BGP session with the associated peer automatically. When Automatic Stop is disabled, the Connect Retry Count Value is set to 0.
    • Enable—stops the BGP session with the associated peer automatically. After an automatic stop, the peer connection needs to be re-initiated manually by the administrator.
  • IdleHold interval—enter the time interval during which the BGP peer is held in idle state prior to the next automatic restart. This value ranges from 1 to 65535 seconds. The default value is 60.
    The IdleHold Interval can be configured if either:
    • Automatic start feature is enabled, or
    • Damp peer oscillation feature is enabled
    Note:

    If both damp peer oscillation and automatic start features are disabled, the existing value is always set instead of the newly configured value.

  • Damp Peer Oscillations—select the status of the Damp Peer Oscillation option that specifies that the implementation engages additional logic to dampen the oscillations of BGP peers in the face of series of automatic start and automatic stop operations in the IDLE state. The default option is Disable. The list contains:
    • Disable—disables the Damp Peer Oscillation option.
    • Enable—enables the Damp Peer Oscillation option.
Fields (cont)
  • Delay Open—select the status of the delay in sending the first OPEN message to the BGP peer for a specific time period. The default option is Disable. The list contains:
    • Disable—disables the Delay Open option for sending open messages, which implies that open messages are sent to the remote BGP peer without any delay.
    • Enable—enables Delay Open option for sending open messages to the remote BGP peer for a configured open delay time period. This delay allows the remote peer to send the first open message.
  • Delay Open Interval—enter the Delay Open Interval which is the amount of time for which the BGP peer should postpone sending the OPEN message to the remote peer. This value ranges from 0 to 65535. The default value is 0.
    Note:

    This field can be configured only if the Delay Open option is enabled.

  • Max Prefix Limit—enter the maximum number of address prefixes that the BGP Peer is willing to accept from the neighbor. This value ranges from 1 to 2147483647. The default value is 100.
    Note:

    The default value is calculated based on the following formula: Maximum number of routes in the routing table / Maximum number of peers supported by BGP.

  • Connect Retry Count—enter the retry count which specifies the number of times the BGP peer should try to establish a TCP-connect issue with its neighboring peers. If the BGP Peer exceeds the maximum count value, automatic stop event takes place and the BGP Peer is brought to the Idle State. This value ranges from 1 to 50. The default value is 5.
  • 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.

Neighbor Configuration—Peer Group 2

Figure 13. Neighbor Configuration—Peer Group 2




Screen Objective This screen allows the peer group name to configure the parameters for BGP peer associated with the peer group.
Navigation

Layer 3 Management > BGP (cont.) > Peer Group 2

Fields
  • Select—select the neighbor for which the configurations need to be modified.
  • Peer Group Name—enter the Peer Group Name for configuring BGP peer group. The members of this peer group will inherit the characteristics configured with this screen. This value is a string of maximum size 20.
  • EBGP Multi HOP—select the status of the EBGP Multi HOP. The default option is Disable. The options include:
    • Disable—disables BGP to establish connection with external peers residing on networks that are not directly connected. If EBGP—Multi HOP is disabled and external BGP peers are indirectly connected, BGP peer session will not be established.
    • Enable—enables BGP to establish connection with external peers residing on networks that are not directly connected. If EBGP peer are not connected directly, EBGP—Multi HOP is enabled to initiate the connection with that external peer.
    Note:

    This configuration is effective only when EBGP peers are added to this peer group.

    EBGP Hop Limit—enter the EBGP Hop Limit value that is used during connection with external peers. BGP speaker accepts or attempts connection to external peers residing on network that are not directly connected but separated by the configured Hop Limit value. This value ranges from 0 to 255. The default value is 1.
    Note:

    This configuration is effective only when EBGP peers are added to this peer group.

  • NEXT HOP—select whether the next hop attribute sent in the update message to the peers in this peer group has to be generated automatically or self. This is useful in non-meshed networks where BGP neighbors may not have direct access to all other neighbors on the same IP subnet. The default option is AUTOMATIC. The list contains:
    • AUTOMATIC—generates the next hop based on the IP address of the destination and the present next hop in the route information.
    • SELF—enables BGP to send itself as the next hop for advertised routes.
Fields (cont)
  • RFL—select Route Reflector Client (RFL) status of the peer. This status is used to define client and non-client peers when implementing route reflection. The default option is NONCLIENT. The list contains:
    • NONCLIENT—configures the peer as non-client peer, which denotes that the peer is outside the cluster.
    • CLIENT—configures the peer as client peer, which denotes that the peer is within the cluster

    The route reflection mechanism operates as follows:

    • A cluster system acting as route reflector sends a route to all client peers within the cluster if the route is received from a non-client peer.
    • The cluster system acting as route reflector sends a route to all non-client peers and all client peers except the originator if the route is received from a client peer.
  • TCP Send Buffer Size—enter the TCP window size on the sender side for all peers in this peer group. This value ranges from 4096 to 65536. The default value is 65536.
  • TCP Receive Buffer Size—enter the TCP window size on the receiver side for all peers in this peer group. This value ranges from 4096 to 65536. The default value is 65536.
  • Community Send Status—select the Community Send Status attribute for the peers in this peer group. The default option is Send. The list contains:
    • None—sets Community Send Status as none.
    • Send—sends a community attribute to a BGP neighbor and enables advertisement of community attributes (standard/extended) to peers
    • DontSend—disables advertisement of standard community attributes to peer.
  • Extended Community Send Status—select the status of Extended Community Send attribute for the peers in this peer group. The BGP extended community is used to label BGP routing information for controlling the distribution of the information. The default option is send. The list contains:
    • None—sets Extended Community Send Status as none.
    • Send—sends a Extended Community attribute to a BGP neighbor and enables advertisement of community attributes (standard/extended) to peers
    • DontSend—disables advertisement of Extended Community attributes to peer.
Fields (cont)
  • Peer Group Connection Passive—select the status of the Peer Group Connection Passive. The default option is Disable. The options include:
    • Enable—sets the Peer Group Connection as passive. BGP speaker waits for the remote peer to initiate the session with the peer.
    • Disable—sets the Peer Group Connection as active. BGP speaker initiates the session with the peer.
  • Default Originator—select the status of the advertisement of the default route to all peers in this peer group. The default option is Disable. The options include:
    • Enable—enables the advertisement of the default route to all peers in this peer group.
    • Disable—disables the advertisement of the default route to all peers in this peer group.
    Note:

    This field overrides the global default route configuration and always sends a default route to the peer with self next-hop. This advertisement occurs irrespective of the presence of default route in FDB.

  • Activate MP Capability—select the option to activate corresponding MP Capability. If any MP Capability is activated, then this capability should be negotiated while establishing session with the peers in this group. The default option is IPV4unicast. The list contains:
    • IPV6unicast—activates the corresponding MP Capability for IPV6 unicast address.
    • IPV4unicast—activates the corresponding MP Capability for IPV4 unicast address.
  • Deactivate MP Capability—select the option to Deactivate corresponding MP Capability. If any MP Capability is deactivated, then this capability should be negotiated while establishing session with the peers in this group. The default option is IPV4unicast. The list contains:
    • IPV6unicast—deactivates the corresponding MP Capability for IPV6 unicast address.
    • IPV4unicast—deactivates the corresponding MP Capability for IPV4 unicast address.
  • In RouteMap Name—enter the name of the route map for this peer group entry. This value is a string of maximum size 20.
  • Out RouteMap Name—enter the name of the out route map for this peer group entry. This value is a string of maximum size 20.
  • In PrefixList Name—enter the In PrefixList Name for the neighbor. This value is a string of maximum size 20.
  • Out PrefixList Name—enter the Out PrefixList Name for the neighbo. This value is a string of maximum size 20.
Fields (cont)
  • ORF Type—click to enable address prefix-based Outbound Route Filter (ORF) for the specified BGP peer group.
  • ORF Mode—select the ORF Capability Support Mode for the specified peer group entry. The default option is none. The list contains:
    • none—disables ORF capability.
    • receive—enables ORF receive capability.
    • send—enables ORF send capability.
    • both—enables both send and receive ORF Capability.
  • BFD Monitoring—select the BFD monitoring status for the BGP peer. The default value is set as disable. The list includes:
    • Enable—specifies that BFD monitoring is enabled. When enabled BGP will register with BFD for IP path monitoring when the session state becomes established.
    • Disable—specifies that BFD monitoring is disabled. The BGP de-registers with BFD if it is already registered.
  • 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.

Peer Addition

Figure 14. Peer Addition


Screen Objective This screen allows the user to add a configured peer to a peer group.
Note

This screen can be configured only if a peer and a peer group are created.

  • To create a Peer, go to Layer 3 Management > BGP > Neighbors > Neighbor Configuration screen.
  • To create a Peer group, go to Layer 3 Management > BGP (cont.) > Peer 1 or Layer 3 Management > BGP (cont.) > Peer Group 2 > Neighbor Configuration
Navigation

Layer 3 Management > BGP (cont.) > Peer Addition with Peer Group

Fields
  • Select—enter a Peer Group Name.
  • Peer Group Name—enter the Peer Group Name to which the peer has to be added. This value is a string of maximum size 20.
  • Address Family/ Peer Address Family—select the Address Family of the peer. The default option is IPV4.
    • IPV6—specifies that the peer belongs to the IPV6 Address Family
    • IPV4—specifies that the peer belongs to the IPV4 Address Family.
  • Peer Address—enter the remote IP address of the BGP peer.
  • VRF Name / Context Name—default.
Buttons
  • Add—adds and saves new configuration.
  • Delete—deletes the selected entry.

Clear BGP

Figure 15. Clear BGP


Screen Objective This screen allows the user to reset the BGP connection dynamically for inbound and outbound route policy. The inbound routing tables are updated dynamically or by generating new updates using stored update information.
Navigation

Layer 3 Management > BGP (cont.) > Clear BGP

Fields
  • IPV4—click to reset the BGP connection dynamically for all IPv4 address family peers.
  • IPV6—click to reset the BGP connection dynamically for all IPv6 address family peers.
  • ALL—click to reset all BGP peers.
  • EXTERNAL—click to reset all external peers.
  • Address Family—select the address family for which the BGP connection needs to be reset.
    • IPV6—clears all BGP connections in IPv6 Address Family.
    • IPV4—clears all BGP connections in the IPv4 Address Family.
  • PEER ADDRESS—click the option button to select the PEER ADDRESS for which the BGP Connection needs to be reset and enter the Peer Address.
Fields
  • PEER GROUP—click the option button to select the PEER GROUP for which the BGP Connection needs to be reset and enter the Peer Group name. This value is a string of maximum size 20.
  • AS NUM—click the option button to select the AS number for which the BGP Connection needs to be reset and enter the AS number.
  • Flap Statistics—click to select the option to clear the route Flap Statistics for the BGP. Enter the required IPv4 / IPv6 address and the Prefix Length to clear the route Flap Statistics.
  • Dampening—click to select the option to clear the dampening configuration for the BGP. Enter the required IPv4 / IPv6 address and the Prefix Length to clear the Dampening statistics.
  • Soft—select the Soft clear which is automatically assumed when the route refresh capability is supported.
    • None—does not initiate inbound soft reconfiguration.
    • In—initiates inbound soft reconfiguration which causes the software to store all received updates without modification regardless of whether an update is accepted by the inbound policy
    • Out—initiates outbound soft configuration which does not have any memory overhead and does not require any pre-configuration. An outbound reconfiguration can be triggered on the other side of the BGP session to make the new inbound policy take effect.
    • Both—initiates both inbound and outbound soft reconfiguration.
    • In Prefix-filter—initiates soft reconfiguration of in Prefix-filter.
  • VRF Name—default.
Buttons
  • Add—adds and saves new configuration.

BGP Route Map Settings

Figure 16. BGP Route Map Settings


Screen Objective This screen allows the user to configure the BGP route map for a neighbor.
Note

Route map can be configured only if a neighbor is created using the Layer 3 Management > BGP > Neighbors > Neighbor Configuration screen.

Navigation

Layer 3 Management > BGP (cont.) > Route Map

Fields
  • Select—click to select the Peer Address for which the configuration needs to be modified or the route map to be deleted.
  • Peer Address—enter the remote IP address of the BGP peer.
  • Route Map Direction—select the direction of the route map. The default option is IN. The list contains.
    • IN—enables Route Map for inbound routes. This applies the route map rules for incoming routes from the peer.
    • OUT—enables Route Map for outbound routes. This applies the route map for the advertising routes to the peer.
  • Route Map Name—enter the remote IP address of the BGP peer.
  • 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.

Peer Orf Config

Figure 17. Peer Orf Config


Screen Objective This screen allows the user to configure the Outbound Route Filter (ORF) filters.
Navigation

Layer 3 Management > BGP (cont.) > Peer ORF Config

Fields
  • Select—click to select the peer address for which the ORF configuration needs to be applied.
  • Peer Address—enter the remote IP address of the BGP peer.
  • ORF Type—displays outbound route filter (ORF) Type as address prefix-based for the specified BGP peer group.
  • Send Mode—select the send mode status for the specified remote IP address of the BGP peer. The default option is enable. The list contains:
    • enable—enables the ORF filter send mode.
    • disable—disables the ORF filter send mode.
  • Receive Mode—select the receive mode status for the specified remote IP address of the BGP peer. The default option is enable. The list contains:
    • enable—enables the ORF filter receive mode.
    • disable—disables the ORF filter receive mode.
  • Send Mode Rx-Status—displays the send mode Rx-Status for the specified remote IP address of the BGP peer.
  • Receive Mode Rx-Status—displays the receive mode Rx-Status for the specified remote IP address of the BGP peer.
  • In Prefix List Name—enter In Prefix List Name for neighbor. This value is a string of maximum size 20.
  • Out Prefix List Name—enter Out Prefix List Name for neighbor. This value is a string of maximum size 20.
  • VRF Name / Context Name—default.
Buttons
  • Apply—modifies attributes for the selected entry and saves the changes.

ORF Filters

Figure 18. ORF Filters


Screen Objective This screen displays the ORF (Outbound Route Filtering) entries created already in the system.
Navigation

Layer 3 Management > BGP (cont.) > ORF Filters

Fields
  • Peer Addr—displays the remote IP address of the BGP peer.
  • Seq No—displays the sequence number of an entry. This value ranges from 1 to 4294967295.
  • Action—displays the filter action of the packet route-update for the associated sequence number. The default option is permit. The list contains:
    • Permit—allows packet route-update with the associated sequence number value to pass the filter.
    • Deny—denies the packet route-update with the associated sequence number value to pass the filter
  • Address Prefix—displays the IPv4 / IPv6 address prefix for the ip prefix-list entry.
  • Prefix-Len—displays the prefix length for IPv4 / IPv6 address prefix for the IP prefix-list entry. This value ranges from 1 to 32 for IPv4 address and from 0 to 128 for IPv6 address.
  • Min Prefix-Len—displays the minimum prefix length to be matched. This value ranges from 1 to 32 for IPv4 address and from 0 to 128 for IPv6 address. Minimum prefix length must be greater than prefix length and less than or equal to max prefix length.
  • Max Prefix-Len—displays the maximum prefix length to be matched. This value ranges from 1 to 32 for IPv4 address and from 0 to 128 for IPv6 address. Maximum prefix length must be greater than prefix length and greater than or equal to min prefix length.
  • VRF Name / Context Name—default.

Filtering

Figure 19. BGP Filtering Configuration


Screen Objective This screen displays the BGP Filtering Configuration.
Navigation

Layer 3 Management > BGP (cont.) > Filtering

Fields
  • Common Preference Value—displays the Common Preference Value.
  • Route Map Name—displays the sequence number of an entry. This value ranges from 1 to 4294967295.
  • Filter type—displays the filter type. The default option is permit. The list contains:
    • Distance
    • Distribute in
    • Distribute out
  • Preference Value (distance only*)—displays the IPv4 / IPv6 address prefix for the ip prefix-list entry.
  • 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.