Skip to content

Commit 2f05e5b

Browse files
committed
Merge branch '517' into stage
2 parents 1ef4ad3 + 77b6a47 commit 2f05e5b

6 files changed

Lines changed: 76 additions & 13 deletions

File tree

content/cumulus-linux-517/Layer-2/Link-Layer-Discovery-Protocol.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -463,7 +463,13 @@ A profile overrides system defaults for an interface.
463463

464464
### BGP Unreachable Prefix TLV
465465

466-
The BGP unreachable prefix TLV allows LLDP to send prefix information learned from {{<link url="FRRouting/" text="FRRouting">}} to connected hosts. This is required in certain use cases such as EVPN unreachability signaling in disjoined planes. The following example enables the BGP unreachable prefix TLV globally:
466+
The BGP unreachable prefix TLV allows LLDP to send prefix information learned from {{<link url="FRRouting/" text="FRRouting">}} to connected hosts. This is required in certain use cases such as EVPN unreachability signaling in disjoined planes.
467+
468+
{{%notice note%}}
469+
BGP unreachable prefix TLV is a Beta feature.
470+
{{%/notice%}}
471+
472+
The following example enables the BGP unreachable prefix TLV globally:
467473

468474
```
469475
cumulus@leaf01:mgmt:~$ nv set system lldp tlv egress-policy unreachable-prefix state enabled
@@ -478,6 +484,7 @@ cumulus@leaf01:mgmt:~$ nv set system lldp tlv profile unreachable-prefix-only eg
478484
cumulus@leaf01:mgmt:~$ nv set interface swp1-3 lldp tlv profile unreachable-prefix-only
479485
cumulus@leaf01:mgmt:~$ nv config apply
480486
```
487+
481488
{{%notice note%}}
482489
You can only enable the unreachable prefix TLV in the `egress-policy` of a TLV profile; it is not supported on ingress.
483490
{{%/notice%}}

content/cumulus-linux-517/Monitoring-and-Troubleshooting/Open-Telemetry-Export.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -495,7 +495,7 @@ cumulus@switch:~$ nv config apply
495495
{{< /tab >}}
496496
{{< tab "Platform Information">}}
497497

498-
To enable platform information statistics, such as the time of last reboot, the last reboot reason, or firmware version:
498+
To enable platform information statistics, such as the time of last reboot, the last reboot reason, or hardware details such as the chasis version, model name, part number, serial number, and type:
499499

500500
```
501501
cumulus@switch:~$ nv set system telemetry platform-stats class platform-info state enabled
@@ -3298,6 +3298,7 @@ CPU statistics include the CPU core number and operation mode (user, system, idl
32983298
| `nvswitch_platform_info_last_reboot_time` | Time of last reboot in ns since epoch.|
32993299
| `nvswitch_platform_info_last_reboot_reason` | Information about the last reboot reason of a component.|
33003300
| `nvswitch_platform_info_firmware_version` | Information about the firmware version of a component.|
3301+
| `nvswitch_platform_info_hw_details` | *Component hardware details such as the version, model name, part number, serial number, and type.|
33013302
33023303
{{< /tab >}}
33033304
{{< /tabs >}}

content/cumulus-linux-517/Monitoring-and-Troubleshooting/gNMI Streaming.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -670,8 +670,11 @@ An asterisk (*) in the `Description` column of the tables below indicates that m
670670

671671
| Name | Description |
672672
|------ | ----------- |
673-
| `/components/component[name]/state/serial-no` | Serial number of the component, keyed by component name.|
674-
| `/components/component[name]/state/part-no` | Part number of the component, keyed by component name.|
673+
| `/components/component[name]/state/serial-no` | *Serial number of the chasis, keyed by component name.|
674+
| `/components/component[name]/state/part-no` | *Part number of the chasis, keyed by component name.|
675+
| `/components/component[name]/state/model-name`| *Model name of the chasis.|
676+
| `/components/component[name]/state/hardware-version`| *Hardware version of the chasis.|
677+
| `/components/component[name]/state/type`| *Chasis type.|
675678
| `/components/component[name]/storage/state/counters/rotation-rate-rpm` | Disk rotation rate in RPMs (supported only on SATA disks). |
676679
| `/components/component[name]/storage/state/counters/write-cache` | Indicates whether the disk has a write cache (supported only on SATA disks). |
677680
| `/components/component[name]/storage/state/counters/write-cache-enabled` | Indicates whether the disk write cache is enabled. (supported only on SATA disks) |

content/cumulus-linux-517/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/EVPN-Enhancements.md

Lines changed: 44 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -232,19 +232,23 @@ address-family l2vpn evpn
232232

233233
## EVPN Unreachability in Disjoined Planes
234234

235-
In EVPN disjoined multi-plane topologies, each GPU in a cluster connects to multiple independent network planes. Leaf switches perform route aggregation per tenant VRF for scalability, but this suppresses visibility of individual host link failures. EVPN unreachability signaling in a tenant VRF sends a route to advertise host unreachability after a link failure, enabling leaf switches to send LLDP TLVs informing connected NICs to avoid unreachable paths.
235+
In EVPN disjoined multi-plane topologies, each GPU in a cluster connects to multiple independent network planes. Leaf switches perform route aggregation per tenant VRF for scalability but this suppresses visibility of individual host link failures. EVPN unreachability signaling in a tenant VRF sends a route to advertise host unreachability after a link failure, enabling leaf switches to send LLDP TLVs informing connected NICs to avoid unreachable paths.
236+
237+
{{%notice note%}}
238+
EVPN unreachability in disjoined planes is a Beta feature.
239+
{{%/notice%}}
236240

237241
To enable EVPN unreachability signaling for disjoined multi-plane topologies on each leaf switch tenant VRF:
238242

239-
1. Configurate route aggregation in the tenant VRFs to summarize relevant network IPv4 and/or IPv6 prefixes
243+
1. Configurate route aggregation in the tenant VRFs to summarize relevant network IPv4 and, or IPv6 prefixes:
240244

241245
```
242246
cumulus@leaf01:mgmt:~$ nv set vrf TENANT1 router bgp address-family ipv4-unicast aggregate-route 10.1.0.0/16 summary-only enabled
243247
cumulus@leaf01:mgmt:~$ nv set vrf TENANT1 router bgp address-family ipv6-unicast aggregate-route 2001:db8::/64 summary-only enabled
244248
cumulus@leaf01:mgmt:~$ nv config apply
245249
```
246250

247-
2. Configure `bgp advertise-unreach interfaces-match <prefix>` under each IPv4 and/or IPv6 unreachability address-family to match interface prefixes attached to GPU NICs:
251+
2. Configure `bgp advertise-unreach interfaces-match <prefix>` under each IPv4 and, or IPv6 unreachability address-family to match interface prefixes attached to GPU NICs:
248252

249253
```
250254
cumulus@leaf01:mgmt:~$ nv set vrf TENANT1 router bgp address-family ipv4-unreachability advertise-unreach interfaces-match 10.1.0.0/16
@@ -260,7 +264,7 @@ cumulus@leaf01:mgmt:~$ nv set vrf TENANT1 router bgp address-family ipv6-unreach
260264
cumulus@leaf01:mgmt:~$ nv config apply
261265
```
262266

263-
4. Enable `bgp export lldp` in tenant VRFs to configure FRR to LLDP integration to send IPv4 and/or IPv6 prefix information to LLDP
267+
4. Enable `bgp export lldp` in tenant VRFs to configure FRR to LLDP integration to send IPv4 and, or IPv6 prefix information to LLDP
264268

265269
```
266270
cumulus@leaf01:mgmt:~$ nv set vrf TENANT1 router bgp address-family ipv4-unreachability export-lldp state
@@ -270,6 +274,42 @@ cumulus@leaf01:mgmt:~$ nv config apply
270274

271275
5. Enable the LLDP {{<link url="Link-Layer-Discovery-Protocol/#bgp-unreachable-prefix-tlv" text="BGP unreachable prefix TLV">}} to distribute unreachable prefix information to connected hosts.
272276

277+
### Show EVPN Unreachability Information
278+
279+
To show EVPN unreachability signaling information, run the `nv show vrf <vrf-id> router bgp address-family l2vpn-evpn route` command:
280+
281+
```
282+
cumulus@leaf01:mgmt:~$ nv show vrf TENANT1 router bgp address-family l2vpn-evpn route
283+
```
284+
285+
To show EVPN unreachability signaling for a specific IPv4 route, run the `nv show vrf <vrf-id> router bgp address-family ipv4-unreachability <route>` command:
286+
287+
```
288+
cumulus@leaf01:mgmt:~$ nv show vrf TENANT1 router bgp address-family ipv4-unreachability 10.1.0.0/16
289+
```
290+
291+
To show EVPN unreachability signaling for a specific IPv6 route, run the `nv show vrf <vrf-id> router bgp address-family ipv6-unreachability <route>` command:
292+
293+
```
294+
cumulus@leaf01:mgmt:~$ nv show vrf TENANT1 router bgp address-family ipv6-unreachability 2001:db8::/64
295+
```
296+
297+
### Known Limitations
298+
299+
Be aware of the following limitations when configuring EVPN unreachability in disjoined planes.
300+
301+
#### switchd Restart
302+
303+
Restarting `switchd` results in network churn. FRR sees interfaces going down, which triggers BGP to start advertising EVPN unreachable routes and brings down peering. BGP withdraws the EVPN unreachable routes and re-establishes BGP sessions after the interfaces are back up operationally.
304+
305+
#### Link Down with Dynamic VRF Assignment on 802.1X Interfaces
306+
307+
When a link with a configured IP address goes down operationally on the leaf switch on only one plane, BGP on the leaf advertises the EVPN unreachable route type for the IP prefix of the interface that is operationally down. However, because the interface is unassigned from the VRF, BGP withdraws the EVPN unreachable route type from the remote leaf switch. Because the remote node still has the aggregate summary route, the leaf switch where the link is down attracts traffic and blocks it instead of rerouting traffic through other healthy planes.
308+
309+
#### Redistributed Route Overlapping with the Interface Match Command
310+
311+
If an interface address redistributed by BGP falls within the IP address range configured in the `bgp advertise-unreach interfaces-match` command and the interface goes down operationally, BGP withdraws the type-5 route and advertise the EVPN unreachable route type for the interface IP address.
312+
273313
## Enable EVPN in an iBGP Environment with an OSPF Underlay
274314

275315
You can use EVPN with an {{<link url="Open-Shortest-Path-First-OSPF" text="OSPF">}} or static route underlay. This is a more complex configuration than using <span class="a-tooltip">[eBGP](## "external BGP")</span>. In this case, <span class="a-tooltip">[iBGP](## "internal BGP")</span> advertises EVPN routes directly between <span class="a-tooltip">[VTEPs](## "Virtual Tunnel End Points")</span> and the spines are unaware of EVPN or BGP.

content/cumulus-linux-517/Whats-New/New-and-Updated-Telemetry-Metrics.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,14 @@ The following tables list the new, updated, and deprecated gNMI and OTEL metrics
159159
| `/interfaces/interface[name]/phy/local_reason_opcode` | Opcode of link down reason at the local end.|
160160
| `/interfaces/interface[name]/phy/remote_reason_opcode` | Opcode of link down reason at the remote end.|
161161

162+
{{< /tab >}}
163+
{{< tab "Platform">}}
164+
| `/components/component[name]/state/serial-no` | Component serial number, keyed by component name.|
165+
| `/components/component[name]/state/part-no` | Component part number, keyed by component name.|
166+
| `/components/component[name]/state/model-name`| Component model name.|
167+
| `/components/component[name]/state/hardware-version`| Component hardware version.|
168+
| `/components/component[name]/state/type`| Component type.|
169+
162170
{{< /tab >}}
163171
{{< /tabs >}}
164172

@@ -169,7 +177,6 @@ The following tables list the new, updated, and deprecated gNMI and OTEL metrics
169177

170178
| Name | Description |
171179
|------ | ----------- |
172-
173180
| `node_netstat_Ip_InReceives` | |
174181
| `node_netstat_Ip_InAddrErrors` | |
175182
| `node_netstat_Ip_InDelivers` | |
@@ -314,5 +321,10 @@ The following tables list the new, updated, and deprecated gNMI and OTEL metrics
314321
| `nvswitch_interface_phy_stats_link_down_reason_code_local ` | Opcode of link down reason at the local end.|
315322
| `nvswitch_interface_phy_stats_link_down_reason_code_remote ` | Opcode of link down reason at the remote end. |
316323

324+
{{< /tab >}}
325+
{{< tab "Platform">}}
326+
327+
| `nvswitch_platform_info_hw_details` | Hardware details such as the version, model name, part number, serial number, and type.|
328+
317329
{{< /tab >}}
318330
{{< /tabs >}}

content/cumulus-linux-517/Whats-New/_index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,17 +26,17 @@ Cumulus Linux 5.17 contains new features and improvements, and provides bug fixe
2626
- {{<link url="Link-Layer-Discovery-Protocol/#lldp-tlvs" text="Granular LLDP TLV definition and control">}}
2727
- {{<link url="Automatic-Configuration-Backup" text="Automatic configuration backup">}}
2828
- {{<link url="Syslog/#thermal-control-logs" text="Thermal logging in syslog (sensor and fan state and errors)">}}
29-
- BGP/LLDP X-Plane multi-plane'd GPUs with disjoined planes (EVPN based deployments) (Beta)
30-
- LLDP BGP Route Redistribution Extension (Beta)
29+
- {{<link url="EVPN-Enhancements/#evpn-unreachability-in-disjoined-planes" text="EVPN Unreachability in Disjoined Planes">}} (Beta)
30+
- {{<link url="Link-Layer-Discovery-Protocol/#bgp-unreachable-prefix-tlv" text="BGP unreachable prefix TLV">}} (Beta)
3131
- NVUE
3232
- {{<link url="Installing-a-New-Cumulus-Linux-Image-with-ONIE/#show-secure-boot-details" text="NVUE command to show secure boot status and details">}}
3333
- {{<link url="RDMA-over-Converged-Ethernet-RoCE/#verify-roce-configuration" text="nv show interface <interface-id> qos roce counters supports multiple interfaces, including ranges">}}
3434
- {{<link url="NVUE-CLI/#configuration-commands" text="NVUE prevents configuration changes during long background operations">}}
3535
- {{<link url="NVUE-CLI/#verify-configuration-before-applying" text="NVUE command">}} and {{<link url="NVUE-API/#verify-configuration-before-applying" text="NVUE API option">}} to verify configuration before applying
3636
- {{<link url="System-Power-and-Switch-Reboot/#show-reboot" text="NVUE command to show warm boot status ">}}
3737
- Telemetry
38-
- New OTEL metrics: {{<link url="Open-Telemetry-Export/#interface-statistic-format" text="link debounce">}}, {{<link url="Open-Telemetry-Export/#interface-statistic-format" text="PHY link down">}}, and {{<link url="Open-Telemetry-Export/#control-plane-statistic-format" text="control plane">}}
39-
- New gNMI metrics: {{<link url="gNMI-Streaming/#metrics" text="PHY link down, link debounce, control plane, and systemd service">}}
38+
- New OTEL metrics: {{<link url="Open-Telemetry-Export/#interface-statistic-format" text="link debounce">}}, {{<link url="Open-Telemetry-Export/#interface-statistic-format" text="PHY link down">}}, {{<link url="Open-Telemetry-Export/#control-plane-statistic-format" text="control plane">}}, and {{<link url="Open-Telemetry-Export/#platform-statistic-format" text="platform information">}}
39+
- New gNMI metrics: {{<link url="gNMI-Streaming/#metrics" text="PHY link down, link debounce, control plane, platform information, and systemd service">}}
4040
- {{<link url="Open-Telemetry-Export/#granular-metric-selection" text="OTEL granular metric selection">}} (Beta)
4141
- {{<link url="High-Frequency-Telemetry/#streaming-hft-export" text="High frequency telemetry streaming over IPFIX">}}
4242
- Security

0 commit comments

Comments
 (0)