eos_routemap¶
Options¶
| parameter | required | default | choices | comments |
|---|---|---|---|---|
| action | yes | permit |
|
The action associated with the routemap name. (added in 1.2.0) |
| continue | no |
The statement defines the next routemap clause to evaluate. (added in 1.2.0) |
||
| description | no |
The description for this routemap entry. (added in 1.2.0) |
||
| match | no |
The list of match statements that define the routemap entry. The match statements should be a comma separated list of match statements without the word match at the beginning of the string. See the example below for more information. (added in 1.2.0) |
||
| name | yes |
The name of the routemap to manage. (added in 1.2.0) |
||
| seqno | yes |
The sequence number of the rule that this entry corresponds to. (added in 1.2.0) |
||
| set | no |
The list of set statements that define the routemap entry. The set statements should be a comma separated list of set statements without the word set at the beginning of the string. See the example below for more information. (added in 1.2.0) |
Important
Requires Arista EOS 4.13.7M or later with command API enabled
Important
Requires Python Client for eAPI 0.4.0 or later
Examples¶
- eos_routemap: name=rm1 action=permit seqno=10
description='this is a great routemap'
match='as 50,interface Ethernet2'
set='tag 100,weight 1000'
continue=20
Note
All configuration is idempotent unless otherwise specified
Note
Supports eos metaparameters for using the eAPI transport
Note
Supports stateful resource configuration.