4.5.1 bgpd.peer.X.as #
Mandatory for each iBGP session definition.
Parameter changes cause reset of BGP session.Defines the Autonomous System Number for the iBGP session.
- Possible values:
1-4294967295
4.5.2 bgpd.peer.X.blackholing.ipv4.next_hop #
Defines IPv4 address which will be used as next_hop in BGP UPDATE for Blackholing routes sent to this router.
The next-hop address should be known by the router.
- Possible values:
IPv4 address
4.5.3 bgpd.peer.X.blackholing.ipv6.next_hop #
Defines IPv6 address which will be used as next_hop in BGP UPDATE for Blackholing routes sent to this router.
The next-hop address should be known by the router.
- Possible values:
IPv6 address
4.5.4 bgpd.peer.X.blackholing.localpref #
Defines localpref value used by IRP in BGP UPDATE for Blackholing routes sent to this router.
Avoid collisions of localpref values assigned to IRP both within its configuration and/or on customer’s network.- Possible values:
0-4294967295 - Default value:
100
4.5.5 bgpd.peer.X.cap_4byte_as #
Parameter changes cause reset of BGP session.Defines usage of 16 or 32-bit autonomous system numbers. Capability can be negotiated during session setup or forced to either 16 or 32 bits.
- 1 – Negotiated on OPEN
- 2 – Always 16-bit AS path
- 3 – Always 32-bit AS path
When the router is operating in legacy mode and does not negotiate capabilities but still sends 32-bit AS Path then Bgpd considers this a malformed AS_PATH attribute and disconnects the session. To avoid this the parameter must be set to force use of 32bit AS numbers.
For example: A BGP session with IRP with “disable-capability-negotiation” option configured on Vyatta router.
As a result, the BGP session is established and then teared down with log messages:
Listing 4.1: Error log
Jan 29 10:20:40.777965 WARN: BGP session RTR/IPv4 (10.0.0.1 AS 65530) Incoming UPDATE error: Invalid elements ignored. Malformed AS_PATH Jan 29 10:20:40.778021 ERROR: BGP session RTR/IPv4 (10.0.0.1 AS 65530) Incoming UPDATE error: malformed AS_PATH xxxxxxx
The solution is to set
bgpd.peer.RTR.cap_4byte_as = 3, then the BGP session succeeds.- Possible values:
1 (Negotiate), 2 (Force 16bit), 3 (Force 32bit) - Default value:
1
4.5.6 bgpd.peer.X.flowspec #
Enables/disables FlowSpec capability for BGP session.
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
0
4.5.7 bgpd.peer.X.flowspec.redirect_type #
The parameter defines the protocol dialect used to specify FlowSpec redirect.
Typically, Huawei routers use the IETF dialect, while Cisco routers use the Simpson dialect.
Nokia dialect has been implemented as described in the Unicast Routing Protocols Guide Release 22.2.R1.
- Possible values:
0 (IETF), 1 (Simpson), 2 (Nokia) - Default value:
1
4.5.8 bgpd.peer.X.inbound.ipv4.next_hop #
Defines IPv4 address which will be used as next_hop in BGP UPDATE for inbound improvements/announcements towards this router.
The next-hop address should be known by the router.
An inbound rule can be configured with a rule-specific next-hop. Refer to inbound.rule.X.next_hop.
- Possible values:
IPv4 address
4.5.9 bgpd.peer.X.inbound.ipv6.next_hop #
Defines IPv6 address which will be used as next_hop in BGP UPDATE for inbound improvements/announcements towards this router.
The next-hop address should be known by the router.
An inbound rule can be configured with a rule-specific next-hop. Refer to inbound.rule.X.next_hop.
- Possible values:
IPv6 address
4.5.10 bgpd.peer.X.inbound.master_localpref #
Defines localpref value used by IRP for inbound improvements for this router.
Assigned localpref value should allow Inbound Improvement to become best route.
Avoid colisions of localpref values assigned to IRP both within its configuration and/or on customer’s network.- Possible values:
0-4294967295 - Default value:
102
4.5.11 bgpd.peer.X.inbound.slave_localpref #
Defines localpref value used by IRP for inbound improvements for this router.
Assigned localpref value should allow Inbound Improvement to become best route.
Avoid colisions of localpref values assigned to IRP both within its configuration and/or on customer’s network.- Possible values:
0-4294967295 - Default value:
101
4.5.12 bgpd.peer.X.keepalive #
Defines the session keepalive time (sec). See RFC1771 for details. Hold time is calculated as keepalive * 3.
- Possible values:
1-600 - Default value:
60 - Recommended value: 1/3 holdtime
4.5.13 bgpd.peer.X.listen #
Instructs the BGP daemon to listen for incoming sessions. It must be set to 1 to be RFC1771 compliant. It can be set to 0 to resolve specific issues.
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
1 - Recommended value:
1
4.5.14 bgpd.peer.X.master_communities #
Defines the BGP Community that will be appended by Bgpd to all advertised prefixes. The format is: “
X:Y”.Avoid colisions of communities values assigned to IRP both within its configuration and/or on customer’s network.When failover is enabled (global.failover) slave’s BGP Community (bgpd.peer.X.slave_communities) must be configured too.
In case Bgpd receives the full or partial RIB (Routing Information Base), values for: MED, Origin, LocalPref and Communities are taken from a less-specific Aggregate route. If values for MED, Origin, LocalPref are set in config, it will override any value from Aggregate route. If value for Communities is set in config, it will be appended to communities from Aggregate route.
4.5.15 bgpd.peer.X.master_localpref #
Defines the local-preference value for prefixes (improvements) announced by Bgpd.
Avoid colisions of localpref values assigned to IRP both within its configuration and/or on customer’s network.When failover is enabled (global.failover) slave’s BGP LocalPref (bgpd.peer.X.slave_localpref) must be configured too.
If failover is enabled, master’s LocalPref value must be greater than slave’s LocalPref value.In case Bgpd received the full or partial RIB (Routing Information Base), values for MED, Origin, LocalPref and Communities will be taken from less-specific Aggregate route. If values for MED, Origin, LocalPref are set in config, it will override any value from Aggregate route. If value for Communities is set in config, it will be appended to communities from Aggregate route.
- Possible values:
0-4294967295 - Default value:
4.5.16 bgpd.peer.X.master_our_ip #
Mandatory for IPv4 BGP session.Parameter changes cause reset of BGP session.Defines IPv4 address of IRP server end of this iBGP session. When failover is enabled (global.failover) slave’s IP address (bgpd.peer.X.slave_our_ip) must be configured too.
- Possible values:
IPv4 address
4.5.17 bgpd.peer.X.master_our_ipv6 #
Mandatory for IPv6 BGP session.Parameter changes cause reset of BGP session.Defines IPv6 address of IRP server end of this iBGP session. When failover is enabled (global.failover) slave’s IPv6 address (bgpd.peer.X.slave_our_ipv6) must be configured too.
- Possible values: IPv6 address
4.5.18 bgpd.peer.X.master_password #
Defines iBGP session’s password. When failover is enabled (global.failover) slave’s local IPv6 address (bgpd.peer.X.slave_communities) must be configured too.
- Possible values:
up to 80 alphanumeric characters
4.5.19 bgpd.peer.X.master_peer_ip #
Mandatory for IPv4 BGP session.Parameter changes cause reset of BGP session.Defines iBGP session’s router’s IPv4 address.
- Possible values:
IPv4 address
4.5.20 bgpd.peer.X.master_peer_ipv6 #
Mandatory for IPv6 BGP session.Parameter changes cause reset of BGP session.Defines iBGP session’s router’s IPv6 address.
- Possible values:
IPv6 address
4.5.21 bgpd.peer.X.master_router_id #
Mandatory for IPv6 BGP session either as standalone master or when failover is enabled and the value should be different from bgpd.peer.X.slave_router_id.Parameter changes cause reset of BGP session.Defines IRP server’s router ID. The BGP router ID is used in the BGP algorithm for determining the best path to a destination where the preference is given to the BGP router with the lowest router ID.
- Possible values:
4-byte value in the IPv4 address format. Any valid IPv4 address can be used.
4.5.22 bgpd.peer.X.med #
Defines the Multi-Exit Discriminator (MED) value for prefixes (improvements) announced by Bgpd.
In case Bgpd received the full or partial RIB (Routing Information Base), values for MED, Origin, LocalPref and Communities will be taken from less-specific Aggregate route. If values for MED, Origin, LocalPref are set in config, it will override any value from Aggregate route. If value for Communities is set in config, it will be appended to communities from Aggregate route.
- Possible values:
0-4294967295
4.5.23 bgpd.peer.X.origin #
Defines the Origin value for prefixes announced by Bgpd.
- Possible values:
0 (IGP), 1 (EGP), 2 (INCOMPLETE)
4.5.24 bgpd.peer.X.shutdown #
Parameter changes cause reset of BGP session.Defines whether the corresponding iBGP session is active or shutdown.
- Possible values:
0 (Active), 1 (Shutdown) - Default value:
0
4.5.25 bgpd.peer.X.slave_communities #
Defines the BGP Community that will be appended by Bgpd on the slave node of a failover configuration to all advertised prefixes. The format is: “
X:Y”.See also bgpd.peer.X.master_communities.
4.5.26 bgpd.peer.X.slave_localpref #
Defines the local-preference value for prefixes announced by Bgpd.
See also bgpd.peer.X.master_localpref.
- Possible values:
0-4294967295 - Default value:
4.5.27 bgpd.peer.X.slave_our_ip #
Mandatory for IPv4 BGP session.Parameter changes cause reset of BGP session. Affects only BGP session of slave node in a failover configuration.Defines IPv4 address of IRP server end of this iBGP session of slave node in a failover configuration.
See also bgpd.peer.X.master_our_ip.
- Possible values:
IPv4 address
4.5.28 bgpd.peer.X.slave_our_ipv6 #
Mandatory for IPv6 BGP session in failover configuration.Parameter changes cause reset of BGP session. Affects only BGP session of slave node in a failover configuration.Defines IPv6 address of IRP server end of this iBGP session of slave node in a failover configuration.
See also bgpd.peer.X.master_our_ipv6.
- Possible values:
IPv6 address
4.5.29 bgpd.peer.X.slave_password #
Defines iBGP session’s password for slave node in a failover configuration.
See also bgpd.peer.X.master_password.
- Possible values:
up to 80 alphanumeric characters
4.5.30 bgpd.peer.X.slave_peer_ip #
Optionally distinct router IPv4 address may be specified in the parameter to be used in order to establish the BGP session from slave instance.
Mandatory for IPv4 BGP session.Parameter changes cause reset of BGP session.Defines iBGP session’s router’s IPv4 address.
See also bgpd.peer.X.master_peer_ip.
- Possible values:
IPv4 address
4.5.31 bgpd.peer.X.slave_peer_ipv6 #
Optionally distinct router IPv6 address may be specified in the parameter to be used in order to establish the BGP session from slave instance.
Mandatory for IPv6 BGP session.Parameter changes cause reset of BGP session.Defines iBGP session’s router’s IPv6 address.
See also bgpd.peer.X.master_peer_ipv6.
- Possible values:
IPv6 address
4.5.32 bgpd.peer.X.slave_router_id #
Mandatory for IPv6 BGP session either as standalone slave or when failover is enabled and the value should be different from bgpd.peer.X.master_router_id.Parameter changes cause reset of BGP session. Affects only BGP session of slave node in a failover configuration.Defines IRP server’s router ID. The BGP router ID is used in the BGP algorithm for determining the best path to a destination where the preference is given to the BGP router with the lowest router ID.
- Possible values:
4-byte value in the IPv4 address format. Any valid IPv4 address can be used.
4.5.33 bgpd.peer.X.transit.mib #
Parameter changes cause reset of BGP session.Defines the MIB used by transit improvements monitors. Refer Optimization of transiting traffic, Optimization of transiting traffic.
- 0 – Generic (BGP4-MIB)
- Default value:
0
4.5.34 bgpd.peer.X.transit.snmp #
Parameter changes cause reset of BGP session.Points to the SNMP host (and its parameters) used for transit improvements monitor on this session. Refer Optimization of transiting traffic, Optimization of transiting traffic.
- Possible values:
valid SNMP host identifier
4.5.35 bgpd.peer.X.transit.status #
Parameter changes cause reset of BGP session.Enables or disables transit improvements through this BGP session (router). Refer Optimization of transiting traffic, Optimization of transiting traffic.
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
0
4.5.36 bgpd.peer.X.updates.limit.max #
Represents a maximum number of prefixes that can be announced simultaneously in one session.
If bgpd.updates.split is ON, the number of announced prefixes is twice the number of the improvements. If the BGP neighbor (typically – the edge router) has any hardware/software limitation for the number of routes in active routing table, then Bgpd can be instructed not to announce more than a specified amount of prefixes. Value 0 means no limit for current iBGP session.
Values less than maximum allowed improvements, can cause not all the improved prefixes to be injected into such peer.
Higher values can be incompatible with the router (please consult the router’s vendor regarding the maximum amount of entries in routing table as well as the BGP table).
- Possible values:
0-100000 - Default value:
0 - Recommended value:
0
4.5.37 bgpd.peer.X.updates.limit.ps #
Defines the maximum number of updates per second that will be sent to the current BGP neighbor. Low values will slow down the improvements injection. High values can cause router to drop the improvement without installing it into the routing database.
- Possible values:
1-1000000 - Default value:
500
