6.3.0 release documentation

docs/about_releases.mdx

@@ -24,6 +24,7 @@ Version `6.1.0` introduces changes to the SSR software release model. Every six
 
 | Version | Initial GA Version | First Release Shipping Date | Latest GA Version | End of Software Engineering support | End of Support |
 | --| -- | -- | -- | -- | -- |
+| Release 6.3 | [6.3.0](release_notes_128t_6.3.md) | May 9, 2024 | [6.3.0](release_notes_128t_6.3.md) | February 9, 2025 | August 9, 2025 |
 | Release 6.2 | [6.2.0](release_notes_128t_6.2.md#release-620-39) | November 16, 2023 | [6.2.4](release_notes_128t_6.2.md#release-624-14r2) | August 16, 2024 | November 3, 2024 |
 | Release 6.1 | [6.1.0](release_notes_128t_6.1.md#release-610-55) | April 14, 2023 | [6.1.8](release_notes_128t_6.1.md#release-618-15) | September 22, 2025 | June 22, 2026 |
 | Release 5.6 | [5.6.7](release_notes_128t_5.6.md#release-567-4) | March 16, 2023 | [5.6.12](release_notes_128t_5.6.md#release-5612-1) | June 16, 2024 | December 16, 2024 |

docs/bcp_per-adjacency_traffic_engineering.md

@@ -1,13 +1,13 @@
 ---
-title: Per Adjacency Traffic Engineering
-sidebar_label: Per Adjacency Traffic Engineering
+title: Adjacency Traffic Engineering
+sidebar_label: Adjacency Traffic Engineering
 ---
 
-Packet loss due to congestion in networks, particularly over WAN links, is inevitable. Depending on where drops occur, it can have a major impact on perceived quality of experience. Packet loss due to exceeding transmit caps between instances of SSR should be avoided. Per-adjacency traffic engineering can be enabled to regulate the upload and download rates between peers.  
+ Adjacency traffic engineering can be enabled to regulate the upload and download rates between peers.  
 
 ## Overview 
 
-Per-adjacency traffic engineering provides targeted traffic engineering for both directions on a bandwidth restricted link between two SSR instances. Traffic engineering on the device interface continues to be associated with the upload rate of a connected link; the `transmit-cap`. Traffic engineering at the adjacency level is associated with the download limit of the adjacent SSR instance; the `receive-cap`.  
+Adjacency traffic engineering provides targeted traffic engineering for both directions on a bandwidth restricted link between two SSR instances. While device interface traffic engineering is associated with the upload rate (`transmit-cap`) of a connected link, traffic engineering at the adjacency level is associated with the download limit of the adjacent SSR instance; the `receive-cap`.  
 
 For example, in the following hub and spoke diagram the Datacenter router has 5 adjacencies off of the individual device interface with a `transmit-cap` upload speed configured at 50Mb. The adjacent branch routers have 10Mb, 5Mb, 1Mb, 5Mb, and 2.5Mb configured as their device interface transmit caps. With such a large `transmit-cap` at the Datacenter, traffic rates exceeding the allowed download speeds (10Mb, 5Mb, 1Mb, 5Mb, and 2.5Mb) on each of the paths to the branch routers will result in traffic being dropped by the ISP. 
 
@@ -64,10 +64,48 @@ network-interface foo
     exit
 exit
 ```
+
+### Limitations
+
+Traffic engineering includes a performance impact to the packet-per-second processing rate of the worker cores. When used in conjunction with other traffic engineering settings, performance is further impacted; each level of traffic engineering requires buffering for their scheduled objects. 
+
 ### Gathering Statistics
 
 To gather information about Per-Adjacency Traffic Engineering, query the following statistics using the `show stats traffic-eng device-interface peer-path` command within the CLI. These statistics are specific to the peer-path and provide insight into how the adjacency schedulers are operating.
 
+```
+admin@combo-east-a.combo-east# show stats traffic-eng device-interface peer-path
+Tue 2024-03-19 13:39:58 UTC
+Retrieving statistics...
+
+Peer Path Traffic Engineering Stats
+-----------------------------------
+
+==================================================== ============== ============ ============== ============= ====== ==================
+ Metric                                               Node           Peer-name    Peer-host      Device-name   Vlan              Value
+==================================================== ============== ============ ============== ============= ====== ==================
+ dequeue-cycle-count                                  combo-east-a   combo-west   172.16.102.2   11-red           0   7077545161474020
+ enqueue-cycle-count                                  combo-east-a   combo-west   172.16.102.2   11-red           0   7077545161474020
+ packets-queued                                       combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class buffer-capacity-exceeded-bytes     combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class buffer-capacity-exceeded-packets   combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class dequeue-aqm-drop-bytes             combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class dequeue-aqm-drop-packets           combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class dequeue-max-latency-drop-bytes     combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class dequeue-max-latency-drop-packets   combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class dequeue-success-bytes              combo-east-a   combo-west   172.16.102.2   11-red           0           94918726
+ per-traffic-class dequeue-success-packets            combo-east-a   combo-west   172.16.102.2   11-red           0             244021
+ per-traffic-class schedule-failure-bandwidth         combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class schedule-failure-bytes             combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class schedule-failure-packets           combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+ per-traffic-class schedule-success-bandwidth         combo-east-a   combo-west   172.16.102.2   11-red           0            1201245
+ per-traffic-class schedule-success-bytes             combo-east-a   combo-west   172.16.102.2   11-red           0           94918726
+ per-traffic-class schedule-success-packets           combo-east-a   combo-west   172.16.102.2   11-red           0             244021
+ scheduler-reset                                      combo-east-a   combo-west   172.16.102.2   11-red           0                  0
+```
+
+### Statistics Descriptions
+
 - `enqueue-cycle-count`: The current enqueue cycle count in traffic engineering for this peer path.
 - `dequeue-cycle-count`: The current dequeue cycle count in traffic engineering for this peer path.
 - `packets-queued`: The current number of packets queued in traffic engineering for this peer path.