Made some edits based on comments. Thanks!

hyperledger · Oct 31, 2023 · a7aa3c3 · a7aa3c3
1 parent 11b8777
commit a7aa3c3
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/docs/source/install-docs/Physical-NodeInstall-20.04 b/docs/source/install-docs/Physical-NodeInstall-20.04
@@ -63,6 +63,8 @@ The following steps are one way to adhere to the Indy Node guidelines for instal
                                 - 8.8.8.8
                                 - 8.8.4.4
                                 - 1.1.1.1
+                        dhcp6: no
+                        link-local: [ ]
                     ens6:
                         addresses:
                            - 172.31.128.159/24
@@ -83,6 +85,8 @@ The following steps are one way to adhere to the Indy Node guidelines for instal
                                 - 8.8.8.8
                                 - 8.8.4.4
                                 - 1.1.1.1
+                        dhcp6: no
+                        link-local: [ ]
     7. Please double and triple check that all of the information in the above file is correct before proceeding. Mistakes in the netplan file can cause you to lose access to your VM and you might have to start over.
     8. `netplan generate`
     9. If no output appears (no errors) run:

diff --git a/docs/source/node-add-troubleshooting.md b/docs/source/node-add-troubleshooting.md
@@ -1,12 +1,12 @@
 # Troubleshooting - Adding or Upgrading Indy Nodes
-Many things can go wrong while adding or upgrading nodes on an existing Indy network and this guide will cover symptoms and issues encountered and some steps you might take to recover from those. The steps listed are likely just possible remedies to the listed issues. Feel free to add more remedies or issues if you don't see your's included here. As bugs are fixed, the issues noted below might not occur any more, or might have a different remedy.
+Things can go wrong while adding or upgrading nodes on an existing Indy network and this guide will cover symptoms and issues encountered and some steps you might take to recover from those. The steps listed are likely just possible remedies to the listed issues. Feel free to add more remedies or issues if you don't see your's included here. As bugs are fixed, the issues noted below might not occur any more, or might have a different remedy.
 
 ## Adding a Node
 This section covers troubleshooting the addition of a node to a network.  This can occur either as part of an upgrade (e.g. the 20.04 upgrade) or as part of a new node being added to an existing network.
 
 ### Symptom 1 - Node is unresponsive  
 - Cause #1 - Node is performing catchup. (Large Network)
-If your node appears unresponsive after adding it to a network (i.e. validator-info shows non-incrementing subledger counts) and no other symptoms are evident, then the first thing to do is wait. While smaller networks with a low number of transactions seem to perform "catchup" quite fast (within a minute or two for a domain ledger with 15K transactions) larger networks or networks that have been running for a long time can take 3 hours or more. Networks do not respond or recover well if you restart a node while it is performing catchup, so please be patient. To verify that this is the cause first check that the node is connected to the Primary Node (if not, see Cause #2), then check the logs to verify that normal "catchup" operations are in process. 
+If your node appears unresponsive after adding it to a network (i.e. validator-info shows non-incrementing subledger counts) and no other symptoms are evident, then the first thing to do is wait. While smaller networks with a low number of transactions seem to perform "catchup" quite fast (within a minute or two for a domain ledger with 15K transactions) larger networks or networks that have been running for a long time can take 3 hours or more. Networks do not respond or recover well if you restart a node while it is performing catchup, so please be patient. To verify that this is the cause first check that the node is connected to the Primary Node (if not, see Cause #2), then check the logs to verify that normal "catchup" operations are in process. The best remedy for this would be to apply the "Best Practice" listed in the Validator Preparation Guide which suggests to "pre-fill" the data directory, especially on large networks, before starting a node for the first time. 
 - Cause #2 - Node is not connected to the Primary Node 
 If the added node cannot reach the primary node, then it sometimes has problems with catchup. Further symptoms in this case include Out Of Consensus (OOC) for your node and possibly others. 
 If you realize the issue quickly, you might be able to recover from this by simply a) stopping the node, b) repairing the connection and then c) restarting the node. Otherwise, to recover you will need to perform the following: