Skip to content

Replace divergent text for the same issue with same text #1035

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MichaelBaj wants to merge 10 commits into
base: master
Choose a base branch
from
Open

Replace divergent text for the same issue with same text #1035

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
34ba2f6
Replace divergent text for the same issue with same text
MichaelBaj Jun 4, 2026
f7daec4
reverting some of the removed text
MichaelBaj Jun 4, 2026
b450b84
replaced removed text
MichaelBaj Jun 4, 2026
bae1e21
replace removed text
MichaelBaj Jun 4, 2026
363ec96
replace removed text
MichaelBaj Jun 4, 2026
c368110
replace removed text
MichaelBaj Jun 4, 2026
d7f5eb1
replace removed text
MichaelBaj Jun 4, 2026
0b46b41
replace removed text
MichaelBaj Jun 4, 2026
cf7f3bb
removing unnecessarily added text
MichaelBaj Jun 4, 2026
4b101d9
replacing removed text
MichaelBaj Jun 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/release_notes_128t_4.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ sidebar_label: '4.0'

- **I95-25356** Device and network Interface graphs are rendering as having no data when data is traversing links.

- **I95-25425** DHCP relay service defined as /32 causes traffic to be black-holed.
- **I95-25425** DHCP Relay with `/32` and FIB next-hop set to none requires additional service configuration

- **I95-25454** Forwarding interfaces are not able to come up when deployed in AWS.

Expand Down
39 changes: 19 additions & 20 deletions docs/release_notes_128t_4.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ sidebar_label: 4.1

### Issues Fixed

- **I95-30610** RTP is not properly classified for subsequent 128T routers
- **I95-30610** RTP is not properly classified for subsequent 128T routers.
------
- **I95-33279** Path MTU discovery unresolvable when no ICMP is generated
------
Expand Down Expand Up @@ -35,7 +35,7 @@ sidebar_label: 4.1
------
- **I95-34310** Secure fields from the 128T configuration are in the commit audit events from config diff operations.
------
- **I95-34744** highway process can fault when a DHCP server assigns the IP address 0.0.0.0 to the 128T router
- **I95-34744** highway process can fault when a DHCP server assigns the IP address 0.0.0.0 to the 128T router.

## Release 4.1.9

Expand Down Expand Up @@ -76,7 +76,7 @@ The 4.1.8 release is a superset of the 4.1.7 release. Features and corrections i

_**Corrective Action:**_ This condition is rare and is exacerbated by DNS responses that change for the same request. Typically the order of the A records have changed for load balancing purposes. This can be mitigated by ensuring the DNS responses are consistent, or removing the FQDN from the service configuration.
------
- **I95-33296** Removing a redundant device-interface and its corresponding redundancy-group as part of the same commit will cause the commit operation to fail.
- **I95-33296** Removing a redundant interface and its corresponding redundancy-group within the same commit would terminate the commit

_**Symptom:**_ Unable to commit configuration changes

Expand All @@ -96,9 +96,9 @@ The 4.1.7 release is a superset of the 4.1.6 release. Features and corrections i

### Issues Fixed

- **I95-31170** NodeMonitor Application fault on shutdown.
- **I95-29801, I95-31170, I95-31116** NodeMonitor application fault when sysLimitsOverride parameters are set
------
- **I95-32449,I95-25567,I95-31060,I95-31675** failed to reserve ports for WayPoint resulting in loss of traffic
- **I95-32449** WayPoint allocation failures resulting in session setup failures


## Release 4.1.6
Expand Down Expand Up @@ -131,11 +131,11 @@ The 4.1.6 release is a superset of the 4.1.5 release. Features and corrections i
------
- **I95-29821** Packet fragmentation for SVR paths is larger than configured MTU by the L4 packet header size
------
- **I95-29990** When a KNI interface starts as operationally down, the state remains the default of unknown and never transition to down.
- **I95-29990** When a KNI interface starts as operationally down, either due to oper status or monitoring script or a watched interface down for T1, the state remains the default of unknown and never transition to down.
------
- **I95-30002** Service route generation skipped for generation set to true if another service with the same name is set to generation false
------
- **I95-30078, I95-30268** Traffic does not switch to standby interface on management path communication failure
- **I95-30078** - HA node communication failure results in two systems both taking control of a shared (redundant) interface
------
- **I95-30315** DHCP Server fails to start after system power failure and power recovery
------
Expand All @@ -155,7 +155,7 @@ The 4.1.6 release is a superset of the 4.1.5 release. Features and corrections i
------
- **I95-30742** Incorrect packet fragmentation when first packet is a jumbo packet
------
- **I95-30781** Warning not provided when neighborhood does not have an end port range
- **I95-30781** Invalid configuration accepted when adjacency or neighborhood port-range does not have end-port configured
------
- **I95-30833** BGP over SVR neighbor not connecting due to missing route
------
Expand All @@ -167,7 +167,7 @@ The 4.1.6 release is a superset of the 4.1.5 release. Features and corrections i
------
- **I95-31208** continuous configuration updates do to network anomalies lead to increased memory usage
------
- **I95-31232** Highway application may fault during network port scanning of the router
- **I95-31232** Peer router highwayManager faults when pinhole traffic originating from this peer is sent to a remote peer that is restarting.
------
- **I95-31244** When a pinhole session is restored upon failover, if the routing table is not up-to-date, the packet will incorrectly be routed to the same interface from which it came from.
------
Expand Down Expand Up @@ -264,7 +264,7 @@ Prior versions of the 128T software did not support two routers with the same WA
------
- **I95-30143** High state is applied to nodes when configuration has changed, causing unnecessary Conductor to router communication. This has been changed to only apply high state when necessary. (Note: when a node is disconnected and reconnects high state is always applied)
------
- **I95-30011** SVR packets dropped briefly when standby node in an HA router pair is restarted.
- **I95-30011** System hostnames that cannot be resolved cause two HA nodes to achieve quorum after DNS lookup times out (approximately 40 seconds)


## Release 4.1.4
Expand Down Expand Up @@ -347,7 +347,7 @@ Prior versions of the 128T software did not support two routers with the same WA
------
- **I95-27763** BGP neighbor local-as is ignored when set to neighbor remote-as
------
- **I95-27830** System can fault when multiple "first" packets are processed simultaneously
- **I95-27830** 2 or more ICMP packets within milliseconds resulted in a software fault
------
- **I95-27878** Database process can consume large amount of CPU due to internal debugging data. This database has been removed
------
Expand Down Expand Up @@ -450,7 +450,7 @@ The 4.1.3 release requires the 128T-installer 2.3.0 or greater. By default, the

- **I95-27792** Asset status not updated correctly
------
- **I95-27339** DHCP stuck flows
- **I95-27339** Sessions for a DHCP relay service can linger, causing subsequent DHCP request failures


## Release 4.1.2
Expand All @@ -471,7 +471,7 @@ The 4.1.2 release requires the 128T-installer 2.3.0 or greater. By default, the
------
- **I95-25790** Peer path statistics on PCLI may be missing for routers with multiple paths
------
- **I95-26021** WEB/GUI page scrolling stops working after router AP upgrade
- **I95-26021** Window scroll bar become inoperable requiring a complete browser page reload
------
- **I95-26154** System can fault when executing `save tech-support-info`
------
Expand Down Expand Up @@ -574,7 +574,7 @@ The 4.1.2 release requires the 128T-installer 2.3.0 or greater. By default, the
------
- **I95-27604** FIB Next Hops is `<none>` when there are only service-routes with services with application-name
------
- **I95-27614** The 128T would send ICMP unreachable responses for destination MACs that were not its own
- **I95-27614** When operating in promiscuous mode, the 128T can send ICMP unreachables for dest macs that are not its own
------
- **I95-27799** Per-router services fail validation when a service applies to more than one router-group
------
Expand Down Expand Up @@ -725,7 +725,7 @@ The 4.1.0 release requires the 128T-installer 2.2.0 or greater. By default, this
------
- **I95-25311** GUI FIB table is inconsistent with output of `show fib` on PCLI.
------
- **I95-25329** PCLI in Conductor GUI creates nested navigation bars
- **I95-25329** Nested navigation bars are created when launching the PCLI from within the GUI
------
- **I95-25425** DHCP Relay with `/32` and FIB next-hop set to none requires additional service configuration
------
Expand Down Expand Up @@ -803,7 +803,7 @@ The 4.1.0 release requires the 128T-installer 2.2.0 or greater. By default, this

## Caveats

- **I95-30103** Entering flat configuration into PCLI does not always create the configuration
- **I95-30103** Creating tenants using output of `show config running flat` does not work (Entering flat configuration into PCLI does not always create the configuration)

_**Symptom:**_ - When performing configuration using flat (or cut and paste of the complete flat configuration line) the configuration is not applied

Expand All @@ -813,7 +813,6 @@ The 4.1.0 release requires the 128T-installer 2.2.0 or greater. By default, this
```

If the "tenant one" configuration object does not exist, the tenant object will not be created. If it does exist then the command will set the attribute "name" to "one"

_**Corrective Action:**_ - On initial creation, do not use flat configuration operations for creating the configuration.
------
- **I95-29842** Nodes with Overlapping DHCP addresses will not be displayed when 'show peers' command is run
Expand All @@ -824,7 +823,7 @@ The 4.1.0 release requires the 128T-installer 2.2.0 or greater. By default, this

_**Corrective Action:**_ After upgrading the Conductors perform a commit operation from either the PCLI or the Conductor GUI
------
- **I95-29733** Conductor UI may not provide an indication that a refresh is in progress (flashing blue dot)
- **I95-29733** Conductor UI may not provide an indication that a software version check is in progress

_**Symptom:**_ When selecting the Router to fresh the available versions to upgrade, the flashing blue indicator may not be present

Expand All @@ -851,7 +850,7 @@ The 4.1.0 release requires the 128T-installer 2.2.0 or greater. By default, this

_**Corrective Action:**_ N/A, no user corrective action is required.
------
- **I95-29134** `save tech-support-info` fails to create tech support file
- **I95-29134** `save tech-support-info` indicates the failure `%Error: Failed to execute the 'save tech-support-info' RPC: Fatal error creating tarball` when files being archived contain spaces; even though the operation completes successfully

_**Symptom:**_ `save tech-support-info` fails with the following error message:
```
Expand Down Expand Up @@ -908,7 +907,7 @@ The 4.1.0 release requires the 128T-installer 2.2.0 or greater. By default, this
_**Conditions:**_ Unknown, seen after system upgrade

_**Corrective Action:**_ NA, The alarms will clear within 15 minutes.
------
------
- **I95-25947** The upgrade to 4.1 can take upwards of 40 minutes to complete. The increase in installation time is due to the underlying OS upgrade.
------
- **I95-25828** Rollback to the previous version of software is not supported due to the underlying operating system upgrade.
Expand Down
Loading