diff --git a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc index 7b9ae4a7..fb15a374 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc @@ -90,7 +90,4 @@ After your application starts, logs start flowing to your custom Log4j appender, == See Also * xref::ch2-deploy-private-space.adoc[] -* xref::ch2-deploy-shared-space.adoc[] -* https://help.mulesoft.com/s/global-search/%40uri#q=log4j&t=SalesforceArticle&f:@sfdcproduct=[CloudHub Log4j Knowledge Articles^] - - +* xref::ch2-deploy-shared-space.adoc[] \ No newline at end of file diff --git a/cloudhub-2/modules/ROOT/pages/ch2-networking-guide.adoc b/cloudhub-2/modules/ROOT/pages/ch2-networking-guide.adoc index f12ca84f..32333d79 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-networking-guide.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-networking-guide.adoc @@ -121,7 +121,7 @@ If you use BGP routing protocols, you can publish these CIDR blocks to your gate Because of this, `100.64.0.0/10` is xref:ps-gather-setup-info.adoc#unusable-cidr[not a supported range] for private spaces. -You can filter these prefixes from the route map. For more information, see https://help.mulesoft.com/s/article/Received-Extra-BGP-routes-from-CloudHub-2-0-VPN[Received Extra BGP routes from CloudHub 2.0 VPN]. +You can filter these prefixes from the route map. You can also indicate a reserved range for your on-prem network upon creating your private space. CloudHub 2.0 doesn’t use reserved ranges indicated by customers. For more information, see xref:ps-gather-setup-info.adoc#reserved-cidr[Reserved Corporate CIDR]. @@ -131,7 +131,7 @@ Private spaces support two types of connections: Virtual Private Network (VPN) a Each Anypoint VPN connection consists of two tunnels that enable you to connect to a single public IP address at a remote location. VPNs are highly available if you configure both tunnels on your endpoint. -Additionally, you can define redundant VPN connections for increased resiliency. As a managed service, the underlying VPN service is often upgraded. Routine maintenance can briefly disable one of the two tunnels of your VPN connection. Your VPN connection automatically fails over to the second tunnel during this time, so access isn’t interrupted. For this reason, you must configure both tunnels on your endpoint. For more information, see https://help.mulesoft.com/s/article/Tunnel-Switch-in-an-Anypoint-Dynamic-BGP-VPN-Update[Tunnel Switch in an Anypoint Dynamic (BGP) VPN Update]. +Additionally, you can define redundant VPN connections for increased resiliency. As a managed service, the underlying VPN service is often upgraded. Routine maintenance can briefly disable one of the two tunnels of your VPN connection. Your VPN connection automatically fails over to the second tunnel during this time, so access isn’t interrupted. For this reason, you must configure both tunnels on your endpoint. By design, TGW connections are highly available. Don’t create redundant TGW connections. For more information, see xref:ps-tgw-about.adoc[]. diff --git a/cloudhub-2/modules/ROOT/pages/ch2-patch-updates.adoc b/cloudhub-2/modules/ROOT/pages/ch2-patch-updates.adoc index 74ae4fb5..bb31be12 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-patch-updates.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-patch-updates.adoc @@ -122,7 +122,7 @@ The following table shows the Mule runtime release cadence support for CloudHub include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[tags=MuleIntro1A2] [NOTE] -If you are a CloudHub or a CloudHub 2.0 customer and you want to create or test Mule 4.6 applications in Anypoint Studio, the Studio version required is the next upcoming release in March. Meanwhile, MuleSoft enables you to deploy new apps in Mule runtime 4.5e version via API, Mule Maven plugin, and Anypoint Platform CLI starting February 14 until April 19. Auto-upgrade from Mule 4.5 Edge to Mule 4.6 Edge for CloudHub and CloudHub 2.0 applications will be performed in April instead of February. See https://help.mulesoft.com/s/article/Mule-Runtime-4-6-release-temporary-changes-to-auto-upgrade-and-new-app-deployment[Temporary changes to auto-upgrade and new app deployment for Mule 4.5 Edge]. +If you are a CloudHub or a CloudHub 2.0 customer and you want to create or test Mule 4.6 applications in Anypoint Studio, the Studio version required is the next upcoming release in March. Meanwhile, MuleSoft enables you to deploy new apps in Mule runtime 4.5e version via API, Mule Maven plugin, and Anypoint Platform CLI starting February 14 until April 19. Auto-upgrade from Mule 4.5 Edge to Mule 4.6 Edge for CloudHub and CloudHub 2.0 applications will be performed in April instead of February. See https://help.salesforce.com/s/articleView?id=001117251&type=1[Temporary changes to auto-upgrade and new app deployment for Mule 4.5 Edge]. include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[tags=MuleIntro2] diff --git a/cloudhub-2/modules/ROOT/pages/ps-create-configure-tgw.adoc b/cloudhub-2/modules/ROOT/pages/ps-create-configure-tgw.adoc index d167a1e2..0573cfa8 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-create-configure-tgw.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-create-configure-tgw.adoc @@ -164,7 +164,7 @@ After you connect to a transit gateway, test the connectivity from CloudHub 2.0 to your networks. To test the connection, use the Network Tools application. -For download and usage information about the Network Tools application, see https://help.mulesoft.com/s/article/How-To-Use-Network-Tools-Application[How To Use Network Tools Application^] (KB article). +For download and usage information about the Network Tools application, see https://help.salesforce.com/s/articleView?id=001115029&type=1[How To Use Network Tools Application]. [[best-practices]] == Maintain the Transit Gateway diff --git a/cloudhub-2/modules/ROOT/pages/ps-create-configure-vpn.adoc b/cloudhub-2/modules/ROOT/pages/ps-create-configure-vpn.adoc index 2b44cb76..1391db41 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-create-configure-vpn.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-create-configure-vpn.adoc @@ -181,7 +181,7 @@ After you create the VPN, test the connectivity from CloudHub 2.0 to your networks. To test the connection, use the Network Tools application. -For download and usage information about the Network Tools application, see https://help.mulesoft.com/s/article/How-To-Use-Network-Tools-Application[How To Use Network Tools Application^]. +For download and usage information about the Network Tools application, see https://help.salesforce.com/s/articleView?id=001115029&type=1[How To Use Network Tools Application]. == See Also diff --git a/cloudhub-2/modules/ROOT/pages/ps-vpn-about.adoc b/cloudhub-2/modules/ROOT/pages/ps-vpn-about.adoc index fe94eeea..15098878 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-vpn-about.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-vpn-about.adoc @@ -172,7 +172,7 @@ You can locate your VPN Gateways in the same data center, or in different physic image::vpn-ha-topology.png[VPN High Availability Topology] -Use BGP routing to advertise the same routes via VPN-1 and VPN-2. See https://help.mulesoft.com/s/article/Anypoint-VPN-Path-Selection-using-BGP-Routing[Anypoint VPN Path Selection using BGP Routing^] for instructions on how to control path selection via the routing protocol. +Use BGP routing to advertise the same routes via VPN-1 and VPN-2. See https://help.salesforce.com/s/articleView?id=001116889&type=1[Anypoint VPN Path Selection using BGP Routing] for instructions on how to control path selection via the routing protocol. In this scenario, the VPN Gateways are configured to prefer: VPN-1 Tunnel-1, then VPN-1 Tunnel-2, then VPN-2 Tunnel-1, and finally VPN-2 Tunnel-2. This configuration produces an automatic failover to another tunnel, and to another VPN in the event of a VPN connectivity issue. This makes the Anypoint VPN solution more resilient and robust. diff --git a/hybrid-standalone/modules/ROOT/pages/configure-ports-ips.adoc b/hybrid-standalone/modules/ROOT/pages/configure-ports-ips.adoc index 90f25877..174059e4 100644 --- a/hybrid-standalone/modules/ROOT/pages/configure-ports-ips.adoc +++ b/hybrid-standalone/modules/ROOT/pages/configure-ports-ips.adoc @@ -68,13 +68,6 @@ Configure your firewall to allow outbound connections to these ports and hostnam For network environments that require IP-based firewall rules, use these static IP addresses to allow Runtime Manager connectivity. -[IMPORTANT] -==== -As part of continuous infrastructure improvement, MuleSoft introduces new static IP addresses in Runtime Manager to augment existing ones. To avoid service disruption, configure your firewall to allow these IP addresses before February 1st, 2024. - -For detailed information, see https://help.mulesoft.com/s/article/New-IP-addresses-in-Runtime-Manager-2024-February[KB: New IP addresses in Runtime Manager 2024 February ^]. -==== - * Allowlist these static IPs in the `US` region to access the `runtime-manager` hosts: + [%header,cols="10a,60a,30a"] diff --git a/hybrid-standalone/modules/ROOT/pages/creating-servers.adoc b/hybrid-standalone/modules/ROOT/pages/creating-servers.adoc index df4da08f..a13e3e4a 100644 --- a/hybrid-standalone/modules/ROOT/pages/creating-servers.adoc +++ b/hybrid-standalone/modules/ROOT/pages/creating-servers.adoc @@ -70,6 +70,7 @@ When creating a server using the IBM Java Virtual Machine (JVM), you must use a . Download the custom truststore from this knowledge base article: + +// Remove this entire section since the KA no longer exists? https://help.mulesoft.com/s/article/Connectivity-issues-between-Mule-Runtime-and-Anypoint-Runtime-manager-using-an-IBM-JVM[Connectivity issues between Mule and Anypoint Runtime Manager using an IBM JVM] . Depending on your Mule version, rename the `truststore` file in `$MULE_HOME/conf` to one of these file names: * `anypoint-truststore.jks` (Mule 4.1.3 with Agent 2.1.4 and later) diff --git a/hybrid-standalone/modules/ROOT/pages/managing-servers.adoc b/hybrid-standalone/modules/ROOT/pages/managing-servers.adoc index 803ebcb8..b45aa100 100644 --- a/hybrid-standalone/modules/ROOT/pages/managing-servers.adoc +++ b/hybrid-standalone/modules/ROOT/pages/managing-servers.adoc @@ -294,7 +294,7 @@ Make sure you disable MFA before implementing these steps. To renew the agent key pair: -. Download the appropriate `agent-certificate-renewer-{version}.jar` file for your Mule version from https://help.mulesoft.com/s/article/Applications-and-Servers-showing-as-Unknown-and-Disconnected-state-in-Anypoint-Runtime-Manager-due-to-expired-key-pair[Applications and Servers Displayed as `unknown` or `disconnected` in Anypoint Runtime Manager Due to an Expired Key Pair]. +. Download the appropriate `agent-certificate-renewer-{version}.jar` file for your Mule version from https://help.salesforce.com/s/articleView?id=001118268&type=1[Applications and Servers showing as Unknown and Disconnected state in Anypoint Runtime Manager due to expired key pair]. . Move the JAR file to `$MULE_HOME/bin` and make sure that you have execute permission. + For example, on Linux, enter `chmod +xx agent-certificate-renewer-{version}.jar`.