routeros.RoutingBgpTemplate
Explore with Pulumi AI
# routeros.RoutingBgpTemplate (Resource)
[!WARNING] Using this resource you may happen unexpected behavior, for example, some of the attributes may not be removable after adding them to the TF configuration. Please report this to GitHub and it may be possible to fix it. Use the resource at your own risk as it is!
Create RoutingBgpTemplate Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new RoutingBgpTemplate(name: string, args: RoutingBgpTemplateArgs, opts?: CustomResourceOptions);
@overload
def RoutingBgpTemplate(resource_name: str,
args: RoutingBgpTemplateArgs,
opts: Optional[ResourceOptions] = None)
@overload
def RoutingBgpTemplate(resource_name: str,
opts: Optional[ResourceOptions] = None,
as_: Optional[str] = None,
keepalive_time: Optional[str] = None,
cluster_id: Optional[str] = None,
address_families: Optional[str] = None,
___path_: Optional[str] = None,
as_override: Optional[bool] = None,
cisco_vpls_nlri_len_fmt: Optional[str] = None,
___id_: Optional[float] = None,
comment: Optional[str] = None,
disabled: Optional[bool] = None,
hold_time: Optional[str] = None,
add_path_out: Optional[str] = None,
input: Optional[RoutingBgpTemplateInputArgs] = None,
remove_private_as: Optional[bool] = None,
name: Optional[str] = None,
nexthop_choice: Optional[str] = None,
output: Optional[RoutingBgpTemplateOutputArgs] = None,
multihop: Optional[bool] = None,
router_id: Optional[str] = None,
routing_bgp_template_id: Optional[str] = None,
routing_table: Optional[str] = None,
save_to: Optional[str] = None,
templates: Optional[Sequence[str]] = None,
use_bfd: Optional[bool] = None,
vrf: Optional[str] = None)
func NewRoutingBgpTemplate(ctx *Context, name string, args RoutingBgpTemplateArgs, opts ...ResourceOption) (*RoutingBgpTemplate, error)
public RoutingBgpTemplate(string name, RoutingBgpTemplateArgs args, CustomResourceOptions? opts = null)
public RoutingBgpTemplate(String name, RoutingBgpTemplateArgs args)
public RoutingBgpTemplate(String name, RoutingBgpTemplateArgs args, CustomResourceOptions options)
type: routeros:RoutingBgpTemplate
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args RoutingBgpTemplateArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args RoutingBgpTemplateArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args RoutingBgpTemplateArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args RoutingBgpTemplateArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args RoutingBgpTemplateArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
RoutingBgpTemplate Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The RoutingBgpTemplate resource accepts the following input properties:
- As string
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- Add
Path stringOut - Address
Families string - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- As
Override bool - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- Cisco
Vpls stringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- Cluster
Id string - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- Comment string
- Disabled bool
- Hold
Time string - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- Input
Routing
Bgp Template Input - A group of parameters associated with BGP input.
- Keepalive
Time string - How long to keep the BGP session open after the last received 'keepalive' message.
- Multihop bool
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- Name string
- Name of the BGP template.
- Nexthop
Choice string - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- Output
Routing
Bgp Template Output - A group of parameters associated with BGP output.
- Remove
Private boolAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- Router
Id string - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- Routing
Bgp stringTemplate Id - The ID of this resource.
- Routing
Table string - Name of the routing table, to install routes in.
- Save
To string - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- Templates List<string>
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- Use
Bfd bool - Whether to use the BFD protocol for faster connection state detection.
- Vrf string
- The VRF table this resource operates on.
- ___
id_ double - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ string - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- As string
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- Add
Path stringOut - Address
Families string - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- As
Override bool - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- Cisco
Vpls stringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- Cluster
Id string - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- Comment string
- Disabled bool
- Hold
Time string - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- Input
Routing
Bgp Template Input Type Args - A group of parameters associated with BGP input.
- Keepalive
Time string - How long to keep the BGP session open after the last received 'keepalive' message.
- Multihop bool
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- Name string
- Name of the BGP template.
- Nexthop
Choice string - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- Output
Routing
Bgp Template Output Type Args - A group of parameters associated with BGP output.
- Remove
Private boolAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- Router
Id string - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- Routing
Bgp stringTemplate Id - The ID of this resource.
- Routing
Table string - Name of the routing table, to install routes in.
- Save
To string - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- Templates []string
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- Use
Bfd bool - Whether to use the BFD protocol for faster connection state detection.
- Vrf string
- The VRF table this resource operates on.
- ___
id_ float64 - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ string - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- as String
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- ___
id_ Double - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ String - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- add
Path StringOut - address
Families String - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- as
Override Boolean - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- cisco
Vpls StringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- cluster
Id String - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- comment String
- disabled Boolean
- hold
Time String - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- input
Routing
Bgp Template Input - A group of parameters associated with BGP input.
- keepalive
Time String - How long to keep the BGP session open after the last received 'keepalive' message.
- multihop Boolean
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- name String
- Name of the BGP template.
- nexthop
Choice String - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- output
Routing
Bgp Template Output - A group of parameters associated with BGP output.
- remove
Private BooleanAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- router
Id String - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- routing
Bgp StringTemplate Id - The ID of this resource.
- routing
Table String - Name of the routing table, to install routes in.
- save
To String - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- templates List<String>
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- use
Bfd Boolean - Whether to use the BFD protocol for faster connection state detection.
- vrf String
- The VRF table this resource operates on.
- as string
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- ___
id_ number - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ string - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- add
Path stringOut - address
Families string - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- as
Override boolean - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- cisco
Vpls stringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- cluster
Id string - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- comment string
- disabled boolean
- hold
Time string - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- input
Routing
Bgp Template Input - A group of parameters associated with BGP input.
- keepalive
Time string - How long to keep the BGP session open after the last received 'keepalive' message.
- multihop boolean
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- name string
- Name of the BGP template.
- nexthop
Choice string - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- output
Routing
Bgp Template Output - A group of parameters associated with BGP output.
- remove
Private booleanAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- router
Id string - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- routing
Bgp stringTemplate Id - The ID of this resource.
- routing
Table string - Name of the routing table, to install routes in.
- save
To string - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- templates string[]
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- use
Bfd boolean - Whether to use the BFD protocol for faster connection state detection.
- vrf string
- The VRF table this resource operates on.
- as_ str
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- ___
id_ float - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ str - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- add_
path_ strout - address_
families str - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- as_
override bool - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- cisco_
vpls_ strnlri_ len_ fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- cluster_
id str - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- comment str
- disabled bool
- hold_
time str - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- input
Routing
Bgp Template Input Args - A group of parameters associated with BGP input.
- keepalive_
time str - How long to keep the BGP session open after the last received 'keepalive' message.
- multihop bool
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- name str
- Name of the BGP template.
- nexthop_
choice str - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- output
Routing
Bgp Template Output Args - A group of parameters associated with BGP output.
- remove_
private_ boolas - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- router_
id str - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- routing_
bgp_ strtemplate_ id - The ID of this resource.
- routing_
table str - Name of the routing table, to install routes in.
- save_
to str - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- templates Sequence[str]
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- use_
bfd bool - Whether to use the BFD protocol for faster connection state detection.
- vrf str
- The VRF table this resource operates on.
- as String
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- ___
id_ Number - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ String - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- add
Path StringOut - address
Families String - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- as
Override Boolean - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- cisco
Vpls StringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- cluster
Id String - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- comment String
- disabled Boolean
- hold
Time String - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- input Property Map
- A group of parameters associated with BGP input.
- keepalive
Time String - How long to keep the BGP session open after the last received 'keepalive' message.
- multihop Boolean
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- name String
- Name of the BGP template.
- nexthop
Choice String - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- output Property Map
- A group of parameters associated with BGP output.
- remove
Private BooleanAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- router
Id String - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- routing
Bgp StringTemplate Id - The ID of this resource.
- routing
Table String - Name of the routing table, to install routes in.
- save
To String - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- templates List<String>
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- use
Bfd Boolean - Whether to use the BFD protocol for faster connection state detection.
- vrf String
- The VRF table this resource operates on.
Outputs
All input properties are implicitly available as output properties. Additionally, the RoutingBgpTemplate resource produces the following output properties:
Look up Existing RoutingBgpTemplate Resource
Get an existing RoutingBgpTemplate resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: RoutingBgpTemplateState, opts?: CustomResourceOptions): RoutingBgpTemplate
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
___id_: Optional[float] = None,
___path_: Optional[str] = None,
add_path_out: Optional[str] = None,
address_families: Optional[str] = None,
as_: Optional[str] = None,
as_override: Optional[bool] = None,
cisco_vpls_nlri_len_fmt: Optional[str] = None,
cluster_id: Optional[str] = None,
comment: Optional[str] = None,
default: Optional[bool] = None,
disabled: Optional[bool] = None,
hold_time: Optional[str] = None,
input: Optional[RoutingBgpTemplateInputArgs] = None,
keepalive_time: Optional[str] = None,
multihop: Optional[bool] = None,
name: Optional[str] = None,
nexthop_choice: Optional[str] = None,
output: Optional[RoutingBgpTemplateOutputArgs] = None,
remove_private_as: Optional[bool] = None,
router_id: Optional[str] = None,
routing_bgp_template_id: Optional[str] = None,
routing_table: Optional[str] = None,
save_to: Optional[str] = None,
templates: Optional[Sequence[str]] = None,
use_bfd: Optional[bool] = None,
vrf: Optional[str] = None) -> RoutingBgpTemplate
func GetRoutingBgpTemplate(ctx *Context, name string, id IDInput, state *RoutingBgpTemplateState, opts ...ResourceOption) (*RoutingBgpTemplate, error)
public static RoutingBgpTemplate Get(string name, Input<string> id, RoutingBgpTemplateState? state, CustomResourceOptions? opts = null)
public static RoutingBgpTemplate get(String name, Output<String> id, RoutingBgpTemplateState state, CustomResourceOptions options)
resources: _: type: routeros:RoutingBgpTemplate get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Add
Path stringOut - Address
Families string - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- As string
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- As
Override bool - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- Cisco
Vpls stringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- Cluster
Id string - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- Comment string
- Default bool
- It's the default item.
- Disabled bool
- Hold
Time string - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- Input
Routing
Bgp Template Input - A group of parameters associated with BGP input.
- Keepalive
Time string - How long to keep the BGP session open after the last received 'keepalive' message.
- Multihop bool
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- Name string
- Name of the BGP template.
- Nexthop
Choice string - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- Output
Routing
Bgp Template Output - A group of parameters associated with BGP output.
- Remove
Private boolAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- Router
Id string - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- Routing
Bgp stringTemplate Id - The ID of this resource.
- Routing
Table string - Name of the routing table, to install routes in.
- Save
To string - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- Templates List<string>
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- Use
Bfd bool - Whether to use the BFD protocol for faster connection state detection.
- Vrf string
- The VRF table this resource operates on.
- ___
id_ double - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ string - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- Add
Path stringOut - Address
Families string - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- As string
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- As
Override bool - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- Cisco
Vpls stringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- Cluster
Id string - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- Comment string
- Default bool
- It's the default item.
- Disabled bool
- Hold
Time string - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- Input
Routing
Bgp Template Input Type Args - A group of parameters associated with BGP input.
- Keepalive
Time string - How long to keep the BGP session open after the last received 'keepalive' message.
- Multihop bool
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- Name string
- Name of the BGP template.
- Nexthop
Choice string - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- Output
Routing
Bgp Template Output Type Args - A group of parameters associated with BGP output.
- Remove
Private boolAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- Router
Id string - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- Routing
Bgp stringTemplate Id - The ID of this resource.
- Routing
Table string - Name of the routing table, to install routes in.
- Save
To string - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- Templates []string
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- Use
Bfd bool - Whether to use the BFD protocol for faster connection state detection.
- Vrf string
- The VRF table this resource operates on.
- ___
id_ float64 - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ string - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- ___
id_ Double - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ String - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- add
Path StringOut - address
Families String - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- as String
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- as
Override Boolean - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- cisco
Vpls StringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- cluster
Id String - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- comment String
- default_ Boolean
- It's the default item.
- disabled Boolean
- hold
Time String - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- input
Routing
Bgp Template Input - A group of parameters associated with BGP input.
- keepalive
Time String - How long to keep the BGP session open after the last received 'keepalive' message.
- multihop Boolean
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- name String
- Name of the BGP template.
- nexthop
Choice String - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- output
Routing
Bgp Template Output - A group of parameters associated with BGP output.
- remove
Private BooleanAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- router
Id String - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- routing
Bgp StringTemplate Id - The ID of this resource.
- routing
Table String - Name of the routing table, to install routes in.
- save
To String - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- templates List<String>
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- use
Bfd Boolean - Whether to use the BFD protocol for faster connection state detection.
- vrf String
- The VRF table this resource operates on.
- ___
id_ number - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ string - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- add
Path stringOut - address
Families string - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- as string
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- as
Override boolean - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- cisco
Vpls stringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- cluster
Id string - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- comment string
- default boolean
- It's the default item.
- disabled boolean
- hold
Time string - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- input
Routing
Bgp Template Input - A group of parameters associated with BGP input.
- keepalive
Time string - How long to keep the BGP session open after the last received 'keepalive' message.
- multihop boolean
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- name string
- Name of the BGP template.
- nexthop
Choice string - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- output
Routing
Bgp Template Output - A group of parameters associated with BGP output.
- remove
Private booleanAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- router
Id string - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- routing
Bgp stringTemplate Id - The ID of this resource.
- routing
Table string - Name of the routing table, to install routes in.
- save
To string - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- templates string[]
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- use
Bfd boolean - Whether to use the BFD protocol for faster connection state detection.
- vrf string
- The VRF table this resource operates on.
- ___
id_ float - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ str - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- add_
path_ strout - address_
families str - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- as_ str
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- as_
override bool - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- cisco_
vpls_ strnlri_ len_ fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- cluster_
id str - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- comment str
- default bool
- It's the default item.
- disabled bool
- hold_
time str - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- input
Routing
Bgp Template Input Args - A group of parameters associated with BGP input.
- keepalive_
time str - How long to keep the BGP session open after the last received 'keepalive' message.
- multihop bool
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- name str
- Name of the BGP template.
- nexthop_
choice str - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- output
Routing
Bgp Template Output Args - A group of parameters associated with BGP output.
- remove_
private_ boolas - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- router_
id str - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- routing_
bgp_ strtemplate_ id - The ID of this resource.
- routing_
table str - Name of the routing table, to install routes in.
- save_
to str - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- templates Sequence[str]
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- use_
bfd bool - Whether to use the BFD protocol for faster connection state detection.
- vrf str
- The VRF table this resource operates on.
- ___
id_ Number - Resource ID type (.id / name). This is an internal service field, setting a value is not required.
- ___
path_ String - Resource path for CRUD operations. This is an internal service field, setting a value is not required.
- add
Path StringOut - address
Families String - List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
- as String
- 32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats. The parameter is also used to set up the BGP confederation, in the following format: confederation_as/as . For example, if your AS is 34 and your confederation AS is 43, then as configuration should be as =43/34.
- as
Override Boolean - If set, then all instances of the remote peer's AS number in the BGP AS-PATH attribute are replaced with the local AS number before sending a route update to that peer. Happens before routing filters and prepending.
- cisco
Vpls StringNlri Len Fmt - VPLS NLRI length format type. Used for compatibility with Cisco VPLS.
- cluster
Id String - In case this instance is a route reflector: the cluster ID of the router reflector cluster to this instance belongs. This attribute helps to recognize routing updates that come from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; in this case, 'cluster-id' does not need to be configured and BGP router ID is used instead.
- comment String
- default Boolean
- It's the default item.
- disabled Boolean
- hold
Time String - Specifies the BGP Hold Time value to use when negotiating with peers. According to the BGP specification, if the router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed. The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other value) infinity - never expire the connection and never send keepalive messages.
- input Property Map
- A group of parameters associated with BGP input.
- keepalive
Time String - How long to keep the BGP session open after the last received 'keepalive' message.
- multihop Boolean
- Specifies whether the remote peer is more than one hop away. This option affects outgoing next-hop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation). It also affects: whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check); whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection; the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their next-hops through IGP routes by default.
- name String
- Name of the BGP template.
- nexthop
Choice String - Affects the outgoing NEXTHOP attribute selection. Note that next-hops set in filters always take precedence. Also note that the next-hop is not changed on route reflection, except when it's set in the filter. default - select the next-hop as described in RFC 4271 force-self - always use a local address of the interface that is used to connect to the peer as the next-hop; propagate - try to propagate further the next-hop received; i.e. if the route has BGP NEXTHOP attribute, then use it as the next-hop, otherwise, fall back to the default case.
- output Property Map
- A group of parameters associated with BGP output.
- remove
Private BooleanAs - If set, then the BGP AS-PATH attribute is removed before sending out route updates if the attribute contains only private AS numbers. The removal process happens before routing filters are applied and before the local, AS number is prepended to the AS path.
- router
Id String - BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying the reference name, or set the ID directly by specifying IP. Equal router-ids are also used to group peers into one instance.
- routing
Bgp StringTemplate Id - The ID of this resource.
- routing
Table String - Name of the routing table, to install routes in.
- save
To String - Filename to be used to save BGP protocol-specific packet content (Exported PDU) into pcap file. This method allows much simpler peer-specific packet capturing for debugging purposes. Pcap files in this format can also be loaded to create virtual BGP peers to recreate conditions that happened at the time when packet capture was running.
- templates List<String>
- List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
- use
Bfd Boolean - Whether to use the BFD protocol for faster connection state detection.
- vrf String
- The VRF table this resource operates on.
Supporting Types
RoutingBgpTemplateInput, RoutingBgpTemplateInputArgs
- Accept
Comunities string - A quick way to filter incoming updates with specific communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- Accept
Ext stringCommunities - A quick way to filter incoming updates with specific extended communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- Accept
Large stringComunities - A quick way to filter incoming updates with specific large communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- Accept
Nlri string - Name of the ipv4/6 address-list. A quick way to filter incoming updates with specific NLRIs. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session restart.
- Accept
Unknown string - A quick way to filter incoming updates with specific 'unknown' attributes. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- Affinity string
- Configure input multi-core processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session are processed in its own process, most likely the best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multi-core devices with a small amount of cores) input - run output in the same process as input (can be set only for output affinity)
- Allow
As double - Indicates how many times to allow your own AS number in AS-PATH, before discarding a prefix.
- Filter string
- Name of the routing filter chain to be used on input prefixes. This happens after NLRIs are processed. If the chain is not specified, then BGP by default accepts everything.
- Ignore
As boolPath Len - Whether to ignore the AS_PATH attribute in the BGP route selection algorithm
- Limit
Process doubleRoutes Ipv4 - Try to limit the amount of received IPv4 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- Limit
Process doubleRoutes Ipv6 - Try to limit the amount of received IPv6 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- Accept
Comunities string - A quick way to filter incoming updates with specific communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- Accept
Ext stringCommunities - A quick way to filter incoming updates with specific extended communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- Accept
Large stringComunities - A quick way to filter incoming updates with specific large communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- Accept
Nlri string - Name of the ipv4/6 address-list. A quick way to filter incoming updates with specific NLRIs. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session restart.
- Accept
Unknown string - A quick way to filter incoming updates with specific 'unknown' attributes. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- Affinity string
- Configure input multi-core processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session are processed in its own process, most likely the best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multi-core devices with a small amount of cores) input - run output in the same process as input (can be set only for output affinity)
- Allow
As float64 - Indicates how many times to allow your own AS number in AS-PATH, before discarding a prefix.
- Filter string
- Name of the routing filter chain to be used on input prefixes. This happens after NLRIs are processed. If the chain is not specified, then BGP by default accepts everything.
- Ignore
As boolPath Len - Whether to ignore the AS_PATH attribute in the BGP route selection algorithm
- Limit
Process float64Routes Ipv4 - Try to limit the amount of received IPv4 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- Limit
Process float64Routes Ipv6 - Try to limit the amount of received IPv6 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- accept
Comunities String - A quick way to filter incoming updates with specific communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Ext StringCommunities - A quick way to filter incoming updates with specific extended communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Large StringComunities - A quick way to filter incoming updates with specific large communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Nlri String - Name of the ipv4/6 address-list. A quick way to filter incoming updates with specific NLRIs. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session restart.
- accept
Unknown String - A quick way to filter incoming updates with specific 'unknown' attributes. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- affinity String
- Configure input multi-core processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session are processed in its own process, most likely the best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multi-core devices with a small amount of cores) input - run output in the same process as input (can be set only for output affinity)
- allow
As Double - Indicates how many times to allow your own AS number in AS-PATH, before discarding a prefix.
- filter String
- Name of the routing filter chain to be used on input prefixes. This happens after NLRIs are processed. If the chain is not specified, then BGP by default accepts everything.
- ignore
As BooleanPath Len - Whether to ignore the AS_PATH attribute in the BGP route selection algorithm
- limit
Process DoubleRoutes Ipv4 - Try to limit the amount of received IPv4 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- limit
Process DoubleRoutes Ipv6 - Try to limit the amount of received IPv6 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- accept
Comunities string - A quick way to filter incoming updates with specific communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Ext stringCommunities - A quick way to filter incoming updates with specific extended communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Large stringComunities - A quick way to filter incoming updates with specific large communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Nlri string - Name of the ipv4/6 address-list. A quick way to filter incoming updates with specific NLRIs. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session restart.
- accept
Unknown string - A quick way to filter incoming updates with specific 'unknown' attributes. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- affinity string
- Configure input multi-core processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session are processed in its own process, most likely the best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multi-core devices with a small amount of cores) input - run output in the same process as input (can be set only for output affinity)
- allow
As number - Indicates how many times to allow your own AS number in AS-PATH, before discarding a prefix.
- filter string
- Name of the routing filter chain to be used on input prefixes. This happens after NLRIs are processed. If the chain is not specified, then BGP by default accepts everything.
- ignore
As booleanPath Len - Whether to ignore the AS_PATH attribute in the BGP route selection algorithm
- limit
Process numberRoutes Ipv4 - Try to limit the amount of received IPv4 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- limit
Process numberRoutes Ipv6 - Try to limit the amount of received IPv6 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- accept_
comunities str - A quick way to filter incoming updates with specific communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept_
ext_ strcommunities - A quick way to filter incoming updates with specific extended communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept_
large_ strcomunities - A quick way to filter incoming updates with specific large communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept_
nlri str - Name of the ipv4/6 address-list. A quick way to filter incoming updates with specific NLRIs. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session restart.
- accept_
unknown str - A quick way to filter incoming updates with specific 'unknown' attributes. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- affinity str
- Configure input multi-core processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session are processed in its own process, most likely the best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multi-core devices with a small amount of cores) input - run output in the same process as input (can be set only for output affinity)
- allow_
as float - Indicates how many times to allow your own AS number in AS-PATH, before discarding a prefix.
- filter str
- Name of the routing filter chain to be used on input prefixes. This happens after NLRIs are processed. If the chain is not specified, then BGP by default accepts everything.
- ignore_
as_ boolpath_ len - Whether to ignore the AS_PATH attribute in the BGP route selection algorithm
- limit_
process_ floatroutes_ ipv4 - Try to limit the amount of received IPv4 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- limit_
process_ floatroutes_ ipv6 - Try to limit the amount of received IPv6 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- accept
Comunities String - A quick way to filter incoming updates with specific communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Ext StringCommunities - A quick way to filter incoming updates with specific extended communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Large StringComunities - A quick way to filter incoming updates with specific large communities. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- accept
Nlri String - Name of the ipv4/6 address-list. A quick way to filter incoming updates with specific NLRIs. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session restart.
- accept
Unknown String - A quick way to filter incoming updates with specific 'unknown' attributes. It allows filtering incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefixes which means that it will still eat memory and will be visible in /routing route table as 'not active, filtered'. Changes to be applied required session refresh.
- affinity String
- Configure input multi-core processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session are processed in its own process, most likely the best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multi-core devices with a small amount of cores) input - run output in the same process as input (can be set only for output affinity)
- allow
As Number - Indicates how many times to allow your own AS number in AS-PATH, before discarding a prefix.
- filter String
- Name of the routing filter chain to be used on input prefixes. This happens after NLRIs are processed. If the chain is not specified, then BGP by default accepts everything.
- ignore
As BooleanPath Len - Whether to ignore the AS_PATH attribute in the BGP route selection algorithm
- limit
Process NumberRoutes Ipv4 - Try to limit the amount of received IPv4 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
- limit
Process NumberRoutes Ipv6 - Try to limit the amount of received IPv6 routes to the specified number. This number does not represent the exact number of routes going to be installed in the routing table by the peer. BGP session 'clear' command must be used to reset the flag if the limit is reached.
RoutingBgpTemplateOutput, RoutingBgpTemplateOutputArgs
- Affinity string
- Configure output multicore processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session is processed in its own process, the most likely best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores) input - run output in the same process as input (can be set only for output affinity).
- Default
Originate string - Specifies default route (0.0.0.0/0) distribution method.
- Default
Prepend double - The count of AS prepended to the AS path.
- Filter
Chain string - Name of the routing filter chain to be used on the output prefixes. If the chain is not specified, then BGP by default accepts everything.
- Filter
Select string - Name of the routing select chain to be used for prefix selection. If not specified, then default selection is used.
- Keep
Sent boolAttributes - Store in memory sent prefix attributes, required for ' dump-saved-advertisements ' command to work. By default, sent-out prefixes are not stored to preserve the router's memory. An option should be enabled only for debugging purposes when necessary to see currently advertised prefixes.
- Network string
- Name of the address list used to send local networks. The network is sent only if a matching IGP route exists in the routing table.
- No
Client boolTo Client Reflection - Disable client-to-client route reflection in Route Reflector setups.
- No
Early boolCut - The early cut is the mechanism, to guess (based on default RFC behavior) what would happen with the sent NPLRI when received by the remote peer. If the algorithm determines that the NLRI is going to be dropped, a peer will not even try to send it. However such behavior may not be desired in specific scenarios, then then this option should be used to disable the early cut feature.
- Redistribute string
- Enable redistribution of specified route types.
- Affinity string
- Configure output multicore processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session is processed in its own process, the most likely best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores) input - run output in the same process as input (can be set only for output affinity).
- Default
Originate string - Specifies default route (0.0.0.0/0) distribution method.
- Default
Prepend float64 - The count of AS prepended to the AS path.
- Filter
Chain string - Name of the routing filter chain to be used on the output prefixes. If the chain is not specified, then BGP by default accepts everything.
- Filter
Select string - Name of the routing select chain to be used for prefix selection. If not specified, then default selection is used.
- Keep
Sent boolAttributes - Store in memory sent prefix attributes, required for ' dump-saved-advertisements ' command to work. By default, sent-out prefixes are not stored to preserve the router's memory. An option should be enabled only for debugging purposes when necessary to see currently advertised prefixes.
- Network string
- Name of the address list used to send local networks. The network is sent only if a matching IGP route exists in the routing table.
- No
Client boolTo Client Reflection - Disable client-to-client route reflection in Route Reflector setups.
- No
Early boolCut - The early cut is the mechanism, to guess (based on default RFC behavior) what would happen with the sent NPLRI when received by the remote peer. If the algorithm determines that the NLRI is going to be dropped, a peer will not even try to send it. However such behavior may not be desired in specific scenarios, then then this option should be used to disable the early cut feature.
- Redistribute string
- Enable redistribution of specified route types.
- affinity String
- Configure output multicore processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session is processed in its own process, the most likely best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores) input - run output in the same process as input (can be set only for output affinity).
- default
Originate String - Specifies default route (0.0.0.0/0) distribution method.
- default
Prepend Double - The count of AS prepended to the AS path.
- filter
Chain String - Name of the routing filter chain to be used on the output prefixes. If the chain is not specified, then BGP by default accepts everything.
- filter
Select String - Name of the routing select chain to be used for prefix selection. If not specified, then default selection is used.
- keep
Sent BooleanAttributes - Store in memory sent prefix attributes, required for ' dump-saved-advertisements ' command to work. By default, sent-out prefixes are not stored to preserve the router's memory. An option should be enabled only for debugging purposes when necessary to see currently advertised prefixes.
- network String
- Name of the address list used to send local networks. The network is sent only if a matching IGP route exists in the routing table.
- no
Client BooleanTo Client Reflection - Disable client-to-client route reflection in Route Reflector setups.
- no
Early BooleanCut - The early cut is the mechanism, to guess (based on default RFC behavior) what would happen with the sent NPLRI when received by the remote peer. If the algorithm determines that the NLRI is going to be dropped, a peer will not even try to send it. However such behavior may not be desired in specific scenarios, then then this option should be used to disable the early cut feature.
- redistribute String
- Enable redistribution of specified route types.
- affinity string
- Configure output multicore processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session is processed in its own process, the most likely best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores) input - run output in the same process as input (can be set only for output affinity).
- default
Originate string - Specifies default route (0.0.0.0/0) distribution method.
- default
Prepend number - The count of AS prepended to the AS path.
- filter
Chain string - Name of the routing filter chain to be used on the output prefixes. If the chain is not specified, then BGP by default accepts everything.
- filter
Select string - Name of the routing select chain to be used for prefix selection. If not specified, then default selection is used.
- keep
Sent booleanAttributes - Store in memory sent prefix attributes, required for ' dump-saved-advertisements ' command to work. By default, sent-out prefixes are not stored to preserve the router's memory. An option should be enabled only for debugging purposes when necessary to see currently advertised prefixes.
- network string
- Name of the address list used to send local networks. The network is sent only if a matching IGP route exists in the routing table.
- no
Client booleanTo Client Reflection - Disable client-to-client route reflection in Route Reflector setups.
- no
Early booleanCut - The early cut is the mechanism, to guess (based on default RFC behavior) what would happen with the sent NPLRI when received by the remote peer. If the algorithm determines that the NLRI is going to be dropped, a peer will not even try to send it. However such behavior may not be desired in specific scenarios, then then this option should be used to disable the early cut feature.
- redistribute string
- Enable redistribution of specified route types.
- affinity str
- Configure output multicore processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session is processed in its own process, the most likely best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores) input - run output in the same process as input (can be set only for output affinity).
- default_
originate str - Specifies default route (0.0.0.0/0) distribution method.
- default_
prepend float - The count of AS prepended to the AS path.
- filter_
chain str - Name of the routing filter chain to be used on the output prefixes. If the chain is not specified, then BGP by default accepts everything.
- filter_
select str - Name of the routing select chain to be used for prefix selection. If not specified, then default selection is used.
- keep_
sent_ boolattributes - Store in memory sent prefix attributes, required for ' dump-saved-advertisements ' command to work. By default, sent-out prefixes are not stored to preserve the router's memory. An option should be enabled only for debugging purposes when necessary to see currently advertised prefixes.
- network str
- Name of the address list used to send local networks. The network is sent only if a matching IGP route exists in the routing table.
- no_
client_ boolto_ client_ reflection - Disable client-to-client route reflection in Route Reflector setups.
- no_
early_ boolcut - The early cut is the mechanism, to guess (based on default RFC behavior) what would happen with the sent NPLRI when received by the remote peer. If the algorithm determines that the NLRI is going to be dropped, a peer will not even try to send it. However such behavior may not be desired in specific scenarios, then then this option should be used to disable the early cut feature.
- redistribute str
- Enable redistribution of specified route types.
- affinity String
- Configure output multicore processing. Read more in Routing Protocol Multi-core Support article. alone - input and output of each session is processed in its own process, the most likely best option when there are a lot of cores and a lot of peers afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores) input - run output in the same process as input (can be set only for output affinity).
- default
Originate String - Specifies default route (0.0.0.0/0) distribution method.
- default
Prepend Number - The count of AS prepended to the AS path.
- filter
Chain String - Name of the routing filter chain to be used on the output prefixes. If the chain is not specified, then BGP by default accepts everything.
- filter
Select String - Name of the routing select chain to be used for prefix selection. If not specified, then default selection is used.
- keep
Sent BooleanAttributes - Store in memory sent prefix attributes, required for ' dump-saved-advertisements ' command to work. By default, sent-out prefixes are not stored to preserve the router's memory. An option should be enabled only for debugging purposes when necessary to see currently advertised prefixes.
- network String
- Name of the address list used to send local networks. The network is sent only if a matching IGP route exists in the routing table.
- no
Client BooleanTo Client Reflection - Disable client-to-client route reflection in Route Reflector setups.
- no
Early BooleanCut - The early cut is the mechanism, to guess (based on default RFC behavior) what would happen with the sent NPLRI when received by the remote peer. If the algorithm determines that the NLRI is going to be dropped, a peer will not even try to send it. However such behavior may not be desired in specific scenarios, then then this option should be used to disable the early cut feature.
- redistribute String
- Enable redistribution of specified route types.
Package Details
- Repository
- routeros terraform-routeros/terraform-provider-routeros
- License
- Notes
- This Pulumi package is based on the
routeros
Terraform Provider.