6.3.0 release documentation #676

Chr1st0ph3rTurn3r · 2024-02-21T19:10:53Z

No description provided.

…e docs.

leo-128t-liu · 2024-02-23T16:09:40Z

docs/config_dnat.md

+[`dynamic-source-nat`](config_command_guide.md#configure-authority-router-node-device-interface-network-interface-dynamic-source-nat): Defines the prefixes that need to be dynamically source natted for packets ingressing this interface. 
+
+- [`local-ip`](config_command_guide.md#configure-authority-router-node-device-interface-network-interface-dynamic-source-nat-local-ip): For packets ingressing this interface, the IP that is source NAT'ed to the `remote-ip`. 
+- [`remote-ip`](config_command_guide.md#configure-authority-router-node-device-interface-network-interface-dynamic-source-nat-remote-ip): For packets ingressing this interface, the IP where the `local-ip` will be source NAT'ed. 


Maybe worth mentioning remote-ip need to be /32 prefix.

leo-128t-liu · 2024-02-23T16:14:46Z

docs/config_dnat.md

@@ -0,0 +1,76 @@
+---
+title: Dynamic Source NAT


Maybe more a question for @avinashbhat80 and @MichaelBaj, shall we use Dynamic Ingress Source NAT to be more accurate naming for this feature?

I do believe Dynamic Ingress Source NAT is more descriptive.

leo-128t-liu · 2024-02-23T16:21:11Z

docs/config_static_nat.md

@@ -0,0 +1,109 @@
+---
+title: Static NAT


I think this came from the func-spec. But I would like to propose this feature to be updated Static Bidirectional NAT because the content is referring to bidirectional NAT often.

chao-128t

The static NAT and dynamic source NAT parts look good 👍.

chao-128t · 2024-02-23T16:37:13Z

docs/config_static_nat.md

+
+### Non-SVR Traffic
+
+In order for non-SVR traffic (for example, LAN-to-LAN traffic traversing a single SSR) to take advantage of static-NAT addressing, you must disable egress source-nat at the service level by setting `service > source-nat` to `disabled` as shown below. 


There are two more ways to disable egress source nat that we want to include here

disable egress source-nat at the network-interface level by setting network-interface > source-nat to false and not configuring network-interface > egress-source-nat-pool

authority router SSR-router name SSR-router node SSR-node name SSR-node device-interface egress-LAN name egress-LAN network-interface egress-LAN name egress-LAN source-nat false egress-source-nat-pool <DON'T CONFIGURE> exit exit exit exit exit

disable egress source-nat at the service-route level by not configuring service-route > next-hop > source-nat-pool

authority router SSR service-route LAN-to-LAN-route name LAN-to-LAN-route service-name LAN-to-LAN next-hop node egress-LAN node-name SSR-node interface egress-LAN source-nat-pool <DON'T CONFIGURE> exit exit exit exit

chao-128t · 2024-02-23T16:51:31Z

docs/config_dnat.md

+
+Dynamic Source NAT translates multiple source IP addresses into a smaller pool of translated addresses and dynamic ports, which conserves public IP address space and provides the flexibility to source NAT a specific IP range. This supports scaling up sessions for an internal service. For example, in a corporate office with a SIP phone service where all phones have different IPs on port 5060, these internal IP addresses are source NAT’ed to a single external IP address. 
+
+Dynamic Source NAT may also provide solutions for IP address conflicts, but because it is not mapping NAT one-to-one, it is not required to facilitate the destination NAT mapping for network connections from the external client to the internal client.


Maybe more clearer to the reader that they should not be confused or expect this to work like bidirectional-nat.

Dynamic Source NAT may also provide solutions for IP address conflicts, but the IP mapping is not one-to-one and does NOT provide destination NAT in the reverse direction. To facilitate the destination NAT mapping for network connections from the external client to the internal client, use bidirectional-nat (add a link here).

… make it more usable.

…adding network interface info.

…ld issue.

…added the \ delimiter.

…change for the Uiso doc.

Co-authored-by: Kaushik Agrawal <[email protected]>

…y/docs into 6.3.0-release-documentation

haberkornsam · 2024-09-25T16:02:05Z

docs/initialize_u-iso_other.md

The url of this page still says initialize_u-iso_other instead of the `advanced workflows name

haberkornsam · 2024-09-25T16:03:19Z

docs/initialize_u-iso_other.md

+"dns-servers": [
+	"8.8.8.8",
+	"1.1.1.1"
+	]


nit: the indentation of this isn't consistent

haberkornsam · 2024-09-25T16:04:12Z

docs/initialize_u-iso_other.md

+
+1. Serial Number (via dmidecode)
+2. Hostname
+3. UUID (via dmidecode)


@agrawalkaushik would the proper name for this be DMI Decode or just via DMI?

Additionally, these defaults apply to mist managed

haberkornsam · 2024-09-25T16:05:37Z

docs/initialize_u-iso_other.md

+
+`/etc/128T-hardware-bootstrapper/onboarding-config.json`
+`/etc/128T-hardware-bootstrapper/pre-bootstrap`
+`/etc/128T-hardware-bootstrapper/post-bootstrap`


From the web these are not showing up on multiple lines. Not sure what needs to be done to fix that

haberkornsam · 2024-09-25T16:07:15Z

docs/initialize_u-iso_other.md

+	- path: /etc/128T-hardware-bootstrapper/onboarding-config.json
+		content: |
+			{
+				"registration_code": "RegistrationCode",


should actually be registration-code

MichaelBaj · 2024-09-24T20:42:13Z

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) | September 19, 2024 | [6.3.0](release_notes_128t_6.3.md) | June 19, 2025 | March 19, 2026 |


Release date needs to be updated. Should be 9/30

MichaelBaj · 2024-09-24T20:44:10Z

docs/releases.table.js

+  {
+    version: '6.3.0',
+    url: 'release_notes_128t_6.3#release-630-1',
+    releaseDate: 'September 19, 2024',


Release date should be updated to 9/30.

MichaelBaj · 2024-09-25T15:05:19Z

docs/bcp_per-adjacency_traffic_engineering.md

+
+### 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. 


I don't like the way this is worded. Suggestion:

Enabling traffic engineering will introduce a performance impact to the packet-per-second processing rate as the QoS engine works to ensure fairness of packet distribution under congestion scenarios. When used in conjunction with other traffic engineering settings (e.g., adjacency traffic engineering configured alongside device interface traffic engineering), performance may be further impacted.

MichaelBaj · 2024-09-25T15:05:58Z

docs/bcp_per-adjacency_traffic_engineering.md

+==================================================== ============== ============ ============== ============= ====== ==================
+ 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


Is the value 7077545161474020 accurate? That seems like a bogus number.

MichaelBaj · 2024-09-25T15:18:11Z

docs/cc_fips_otp_router_install.md

+config authority router RTR_EAST_COMBO node combo-east-2 ssh-settings inter-node host-key-checking yes
+```
+
+To configure a new authorized key for ssh inter-node communitcation, use the [`create system connectivity authorized-keys`](cli_reference.md#create-system-connectivity-authorized-keys) command. This command adds an entry to the ssh authorized keys file.


Typo. Please run through a spell checker for this large PR.
communitcation = communication

MichaelBaj · 2024-09-26T01:35:48Z