netlab launch 2.0.0 is out. I spent the entire week fixing bugs and operating integration exams, so I’m too brain-dead to enter the main points. These are the main options we added (extra about them in just a few days; the main points are within the launch notes):
Different modifications embrace:
- netlab is gathering utilization statistics into an area file that’s not shared with anybody, however will be inspected or managed with netlab utilization
- We use the routing module to configure static routes on host gadgets. VRF-aware gadgets can use a default route; different gadgets get extra particular routes for tackle swimming pools and named prefixes.
- A number of EVPN import/export route targets can help you construct complicated EVPN-based companies like frequent companies or hub-and-spoke connectivity
- I wished to have higher graphs, so I applied node/hyperlink types for D2 graphs
- Lastly, we applied ‘delete communities matching a listing’ in routing insurance policies
Then again, there’s time for just a few retirements:
However wait, there’s extra:
- Names of defaults.const.validate constants can be utilized as wait instances within the validation wait parameter
- You should utilize all and machine varieties within the node choice expressions utilized in netlab examine, netlab report and netlab exec instructions
- We use a special Ansible process record when reloading machine configuration, which provides you the flexibility to reload machine configuration on SR Linux
- Should you insist (however you shouldn’t), you should use int values as offset of administration IP addresses within the administration subnet.
- You possibly can mix default tcpdump flags with consumer filter within the netlab seize command
- We moved to Vagrant model to 2.4.3-1
- netlab checks reserved ranges (native community, multicast) throughout IPv4/IPv6 tackle/prefix validation. It additionally warns about EBGP ‘bgp’ attributes used on intra-AS hyperlinks/vlans
Not sufficient? How about new machine options? Listed below are only a few of them:
- Unnumbered interfaces on Aruba CX
- You possibly can configure a half-dozen new BGP options on Chicken, and use it in LAG and VLAN environments
- We began supporting quite a few BGP options and routing insurance policies on Dell OS10 and Junos
- There’s additionally MAC-VRF implementation for Junos
- Lastly, there’s SRv6 with IS-IS and L3VPN companies over SRv6 on FRRouting
Upgrading or Ranging from Scratch?
netlab launch 2.0.0 is out. I spent the entire week fixing bugs and operating integration exams, so I’m too brain-dead to enter the main points. These are the main options we added (extra about them in just a few days; the main points are within the launch notes):
Different modifications embrace:
- netlab is gathering utilization statistics into an area file that’s not shared with anybody, however will be inspected or managed with netlab utilization
- We use the routing module to configure static routes on host gadgets. VRF-aware gadgets can use a default route; different gadgets get extra particular routes for tackle swimming pools and named prefixes.
- A number of EVPN import/export route targets can help you construct complicated EVPN-based companies like frequent companies or hub-and-spoke connectivity
- I wished to have higher graphs, so I applied node/hyperlink types for D2 graphs
- Lastly, we applied ‘delete communities matching a listing’ in routing insurance policies
Then again, there’s time for just a few retirements:
However wait, there’s extra:
- Names of defaults.const.validate constants can be utilized as wait instances within the validation wait parameter
- You should utilize all and machine varieties within the node choice expressions utilized in netlab examine, netlab report and netlab exec instructions
- We use a special Ansible process record when reloading machine configuration, which provides you the flexibility to reload machine configuration on SR Linux
- Should you insist (however you shouldn’t), you should use int values as offset of administration IP addresses within the administration subnet.
- You possibly can mix default tcpdump flags with consumer filter within the netlab seize command
- We moved to Vagrant model to 2.4.3-1
- netlab checks reserved ranges (native community, multicast) throughout IPv4/IPv6 tackle/prefix validation. It additionally warns about EBGP ‘bgp’ attributes used on intra-AS hyperlinks/vlans
Not sufficient? How about new machine options? Listed below are only a few of them:
- Unnumbered interfaces on Aruba CX
- You possibly can configure a half-dozen new BGP options on Chicken, and use it in LAG and VLAN environments
- We began supporting quite a few BGP options and routing insurance policies on Dell OS10 and Junos
- There’s additionally MAC-VRF implementation for Junos
- Lastly, there’s SRv6 with IS-IS and L3VPN companies over SRv6 on FRRouting
![Linux community tunneling through VXLAN or Geneve [closed]](https://cyberdefensego.com/wp-content/uploads/2025/05/ED2zTWrZ.png)
![[5 Mins Docker] Deploy Nexterm (open-source server administration software program) to Handle Cloud Servers – 51 Safety](https://cyberdefensego.com/wp-content/uploads/2025/05/chrome_PHAYH3GBKS.png){kind=small}
