Add link to the troubleshoot section (#1503)

* add link to troubleshoot section Signed-off-by: Joan Edwards <[email protected]> * update link Signed-off-by: Joan E <[email protected]> * update language Signed-off-by: Joan E <[email protected]> * reword deprecation Signed-off-by: Joan E <[email protected]> * remove space Co-authored-by: Alexandra Tran Carrillo <[email protected]> Signed-off-by: Joan E <[email protected]> * Update manage-peers.md Signed-off-by: Joan E <[email protected]> * remove spaces Signed-off-by: Joan E <[email protected]> * update text Signed-off-by: Joan E <[email protected]> * Update peering.md Signed-off-by: Joan E <[email protected]> * fix link Signed-off-by: Joan E <[email protected]> * status Signed-off-by: Joan E <[email protected]> * Update Signed-off-by: Joan E <[email protected]> * errors in link Signed-off-by: Joan E <[email protected]> * rewrite Signed-off-by: Joan E <[email protected]> * I must get the correct link Signed-off-by: Joan E <[email protected]> * spelling error Signed-off-by: Joan E <[email protected]> * reword and check build Signed-off-by: Joan E <[email protected]> * Update relative link Signed-off-by: Joan E <[email protected]> * Update docs/public-networks/how-to/connect/manage-peers.md Co-authored-by: Alexandra Tran Carrillo <[email protected]> Signed-off-by: Joan E <[email protected]> * Add note for AWS ports Signed-off-by: Joan E <[email protected]> * Update pwith link Signed-off-by: Joan E <[email protected]> * remove AWS node config mention Signed-off-by: Joan E <[email protected]> * Add AWS info as note Signed-off-by: Joan E <[email protected]> --------- Signed-off-by: Joan Edwards <[email protected]> Signed-off-by: Joan E <[email protected]> Co-authored-by: Alexandra Tran Carrillo <[email protected]>
hyperledger · Feb 14, 2024 · c4d727c · c4d727c
1 parent a88fa90
commit c4d727c
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 8 deletions.
diff --git a/docs/public-networks/how-to/connect/configure-ports.md b/docs/public-networks/how-to/connect/configure-ports.md
@@ -9,12 +9,18 @@ tags:
 
 # Configure ports
 
-To enable communication you must expose Hyperledger Besu ports appropriately. The following shows an example port configuration for a Besu node on AWS.
+To enable communication you must expose Hyperledger Besu ports appropriately. The following shows an example port configuration for a Besu node on AWS. 
 
 ![Port Configuration](../../../assets/images/PortConfiguration.png)
 
 When running Besu from the [Docker image](../../get-started/install/run-docker-image.md), [expose ports](../../get-started/install/run-docker-image.md#exposing-ports).
 
+:::info
+
+If your nodes are running in AWS, ensure you have appropriate `SecurityGroups` to allow access to the required ports.
+
+:::
+
 :::tip
 
 Besu supports [UPnP](specify-nat.md) for home or small office environments where a wireless router or modem provides NAT isolation.

diff --git a/docs/public-networks/how-to/connect/manage-peers.md b/docs/public-networks/how-to/connect/manage-peers.md
@@ -31,8 +31,7 @@ To reduce the maximum number of peers, use the [`--max-peers`](../../reference/c
 
 The minimum number of peers is set by the `--Xp2p-peer-lower-bound` option, which also has a default of 25. If you reduce the `--max-peers` from the default, you must also set the `--Xp2p-peer-lower-bound` option to the same value or lower. For example, if you decrease `--max-peers` to 20, set `--Xp2p-peer-lower-bound` to 20 or lower.
 
-Note, `Xp2p-peer-lower-bound` is an early access option.
-
+The `--Xp2p-peer-lower-bound` option is an early access feature.
 :::
 
 ## Limit remote connections
@@ -81,8 +80,4 @@ With discovery disabled, peers can't open connections with the node unless they
 
 ## Troubleshoot
 
-If your nodes fail to connect, ensure the [required ports are open](configure-ports.md).
-
-If your nodes are running in AWS, check you have appropriate `SecurityGroups` to allow access to the required ports.
-
-Check that the [enode URLs](../../concepts/node-keys.md#enode-url) specified for [bootnodes](../../../private-networks/how-to/configure/bootnodes.md) or [static nodes](static-nodes.md) match the enode URLs displayed when starting the remote nodes.
+If you encounter issues with peering, see the [troubleshoot peering documentation](../../how-to/troubleshoot/peering.md), which helps you identify and resolve common problems that can occur during the peering process.
diff --git a/docs/public-networks/how-to/troubleshoot/peering.md b/docs/public-networks/how-to/troubleshoot/peering.md
@@ -42,6 +42,10 @@ Check the following settings:
 - The appropriate ports should be open on your router, or your router should have UPNP enabled. See the next FAQ for more information on router settings.
 - If you use [Docker](https://docs.docker.com/network/network-tutorial-host/) or virtualization, the container should be able to create outbound connections on the host machine.
 
+### "Which URLs should I check?"
+
+Check that the [enode URLs](../../concepts/node-keys.md#enode-url) specified for [bootnodes](../../../private-networks/how-to/configure/bootnodes.md) or [static nodes](../connect/static-nodes.md) match the enode URLs displayed when starting the remote nodes.
+
 ### "How do I open/forward my ports?"
 
 If you’re behind NAT, you probably need to set up port forwarding in your router. You might also need to configure your firewall. Forward and open `30303` (if using the default p2p port) for both UDP and TCP. If your router supports UPNP, you can set [`--nat-method`](../../reference/cli/options.md#nat-method) to [`UPNPP2PONLY`](../connect/specify-nat.md#upnp).