ip addressess updated to RFC1166

Author: eedugon

deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet-self.md

@@ -27,8 +27,8 @@ PUT /_cluster/settings
       "remote": {
         "alias-for-my-remote-cluster": { // Align the alias with the remote cluster name used when adding the API key.
           "mode":"proxy",
-          "proxy_address": "a542184a7a7d45b88b83f95392f450ab.192.168.44.10.ip.es.io:9400",
-          "server_name": "a542184a7a7d45b88b83f95392f450ab.192.168.44.10.ip.es.io"
+          "proxy_address": "a542184a7a7d45b88b83f95392f450ab.192.0.2.10.ip.es.io:9400",
+          "server_name": "a542184a7a7d45b88b83f95392f450ab.192.0.2.10.ip.es.io"
         }
       }
     }

deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet.md

@@ -35,8 +35,8 @@ PUT /_cluster/settings
       "remote": {
         "alias-for-my-remote-cluster": { // Remote cluster alias
           "mode":"proxy",
-          "proxy_address": "a542184a7a7d45b88b83f95392f450ab.192.168.44.10.ip.es.io:9400",
-          "server_name": "a542184a7a7d45b88b83f95392f450ab.192.168.44.10.ip.es.io"
+          "proxy_address": "a542184a7a7d45b88b83f95392f450ab.192.0.2.10.ip.es.io:9400",
+          "server_name": "a542184a7a7d45b88b83f95392f450ab.192.0.2.10.ip.es.io"
         }
       }
     }

deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md

@@ -146,11 +146,11 @@ A deployment can be configured to trust all or specific deployments in any envir
     instances:
       - name: "node1"
         dns: ["node1.mydomain.com"]
-        ip: ["192.168.1.1"]
+        ip: ["192.0.2.1"]
         cn: ["node1.node.1234567abcd.cluster.myscope.account"]
       - name: "node2"
         dns: ["node2.mydomain.com"]
-        ip: ["192.168.1.2"]
+        ip: ["192.0.2.2"]
         cn: ["node2.node.1234567abcd.cluster.myscope.account"]
     ```
 

deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md

@@ -146,11 +146,11 @@ A deployment can be configured to trust all or specific deployments in any envir
     instances:
       - name: "node1"
         dns: ["node1.mydomain.com"]
-        ip: ["192.168.1.1"]
+        ip: ["192.0.2.1"]
         cn: ["node1.node.1234567abcd.cluster.myscope.account"]
       - name: "node2"
         dns: ["node2.mydomain.com"]
-        ip: ["192.168.1.2"]
+        ip: ["192.0.2.2"]
         cn: ["node2.node.1234567abcd.cluster.myscope.account"]
     ```
 

deploy-manage/remote-clusters/remote-clusters-api-key.md

@@ -76,7 +76,7 @@ If a remote cluster is part of an {{ech}} (ECH) deployment, the remote cluster s
     3. Generate a certificate and private key pair for the nodes in the remote cluster:
 
         ```sh
-        ./bin/elasticsearch-certutil cert --out=cross-cluster.p12 --pass=CERT_PASSWORD --ca-cert=ca/ca.crt --ca-key=ca/ca.key --ca-pass=CA_PASSWORD --dns=example.com --ip=127.0.0.1
+        ./bin/elasticsearch-certutil cert --out=cross-cluster.p12 --pass=CERT_PASSWORD --ca-cert=ca/ca.crt --ca-key=ca/ca.key --ca-pass=CA_PASSWORD --dns=example.com --ip=192.0.2.1
         ```
 
         * Replace `CA_PASSWORD` with the CA password from the previous step.
@@ -158,7 +158,7 @@ To add a remote cluster from Stack Management in {{kib}}:
 2. Select **Add a remote cluster**.
 3. Select **API keys** as the connection type.
 4. Enter a name (*cluster alias*) for the remote cluster.
-5. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster followed by the remote cluster port (defaults to `9443`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9443` or `192.168.1.1:9443`.
+5. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster followed by the remote cluster port (defaults to `9443`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9443` or `192.0.2.1:9443`.
 
     Starting with {{kib}} 9.2, you can also specify IPv6 addresses.
 

deploy-manage/remote-clusters/remote-clusters-cert.md

@@ -68,7 +68,7 @@ To add a remote cluster from Stack Management in {{kib}}:
 2. Select **Add a remote cluster**.
 3. Select **Certificates** as the connection type.
 4. Enter a name (*cluster alias*) for the remote cluster.
-5. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster followed by the transport port (defaults to `9300`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9300` or `192.168.1.1:9300`.
+5. Specify the {{es}} endpoint URL, or the IP address or host name of the remote cluster followed by the transport port (defaults to `9300`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9300` or `192.0.2.1:9300`.
 
     Starting with {{kib}} 9.2, you can also specify IPv6 addresses.
 

deploy-manage/remote-clusters/remote-clusters-migrate.md

@@ -69,7 +69,7 @@ On the remote cluster:
     3. Generate a certificate and private key pair for the nodes in the remote cluster:
 
         ```sh
-        ./bin/elasticsearch-certutil cert --out=cross-cluster.p12 --pass=CERT_PASSWORD --ca-cert=ca/ca.crt --ca-key=ca/ca.key --ca-pass=CA_PASSWORD --dns=example.com --ip=127.0.0.1
+        ./bin/elasticsearch-certutil cert --out=cross-cluster.p12 --pass=CERT_PASSWORD --ca-cert=ca/ca.crt --ca-key=ca/ca.key --ca-pass=CA_PASSWORD --dns=example.com --ip=192.0.2.1
         ```
 
         * Replace `CA_PASSWORD` with the CA password from the previous step.