Implement IS-IS as underlay option in eos_l3ls_evpn #184
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Initial implementation of ISIS to support protocol as underlay in L3LS environement. Supported options: ------------------ - ISIS Router options: ``` router_isis: instance: <ISIS Instance Name> net: < CLNS Address to run ISIS | format 49.0001.0001.0000.0001.00 > router_id: < IPv4_address > no_passive_interfaces: < List no-passive-interface > is_type: < level-1 | level-1-2 | level-2 > address_family: < List of Address Families > ``` - ISIS Interface confituguration (Ethernet / Loopback / Vlans) ``` isis_enable: < ISIS Instance > isis_passive: < boolean > isis_metric: < integer > isis_network_point_to_point: < boolean > ``` Outputs: -------- - Device documentation - Device Configuration ``` interface Loopback0 description EVPN_Overlay_Peering ip address 192.168.255.3/32 isis enable EVPN_UNDERLAY isis passive ! interface Vlan4093 description MLAG_PEER_L3_PEERING ip address 10.255.251.0/31 isis enable EVPN_UNDERLAY isis metric 50 isis network point-to-point ! router isis EVPN_UNDERLAY net 49.0001.0001.0001.0001.00 is-type level-2 router-id ipv4 192.168.255.3 log-adjacency-changes ! address-family ipv4 unicast ! ! ```
Initial implementation of ISIS abstraction to run as underlay protocol.
Inputs:
-------
DC1_FABRIC.yml
```
underlay_routing_protocol: ISIS
isis_area_id: "49.0001"
isis_site_id: "0001"
```
Outputs:
--------
- Data structure compatible with eos_cli_config_gen role
```
router_isis:
instance: EVPN_UNDERLAY
net: 49.0001.0001.0001.0001.00
router_id: 192.168.255.3
no_passive_interfaces:
- Ethernet1
- Ethernet2
- Vlan4093
is_type: level-2
address_family: ['ipv4 unicast']
```
- Fabric documentation: List of CLNS addresses configured on devices.
Implement initial scenario for ISIS underlay testing in CI ``
Add statement maximum-paths under isis/af-ipv4-unicast
Device data model:
```
address_family: ['ipv4 unicast']
isis_af_defaults:
- maximum-paths {{ spine.nodes | length * max_l3leaf_to_spine_links }}
```
Configuration output
```
router isis EVPN_UNDERLAY
net 49.0001.0001.0001.0001.00
is-type level-2
router-id ipv4 192.168.255.3
log-adjacency-changes
!
address-family ipv4 unicast
maximum-paths 2
!
!
```
Create IS-IS configuration for Loopback1 to announce VTEP IP address throughout fabric underlay. Configuration is similar to loopback0: - Enable on EVPN_UNDERLAY instance - Run in passive mode
carlbuchmann
approved these changes
Jul 9, 2020
carlbuchmann
added
role: eos_cli_config_gen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial Implementation for ISIS as underlay (#127)
EOS_L3LS_EVPN
Inputs:
DC1_FABRIC.yml
Outputs:
EOS_CLI_CONFIG_GEN
Initial implementation of ISIS to support protocol as underlay in L3LS
environment.
Supported options:
Outputs:
Review
eos_l3ls_evpnreadme fileeos_cli_config_genreadme file