Skip to content

Commit 3ac7933

Browse files
Merge pull request #283447 from aprilbrinkmeyer/291732-remove-centos
291732 and 291757 - removing references to CentOS
2 parents 38dc7dc + 2dbe220 commit 3ac7933

File tree

2 files changed

+9
-35
lines changed

2 files changed

+9
-35
lines changed

articles/virtual-network/virtual-network-optimize-network-bandwidth.md

Lines changed: 3 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,19 @@
11
---
22
title: Optimize Azure VM network throughput
3-
description: Optimize network throughput for Microsoft Azure Windows and Linux virtual machines, including major distributions such as Ubuntu, CentOS, and Red Hat.
3+
description: Optimize network throughput for Microsoft Azure Windows and Linux virtual machines, including major distributions such as Ubuntu and Red Hat.
44
services: virtual-network
55
author: asudbring
66
manager: Gerald DeGrace
77
ms.service: virtual-network
88
ms.custom: linux-related-content
99
ms.topic: how-to
10-
ms.date: 03/24/2023
10+
ms.date: 08/02/2024
1111
ms.author: allensu
1212
---
1313

1414
# Optimize network throughput for Azure virtual machines
1515

16-
> [!CAUTION]
17-
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
18-
19-
Azure Virtual Machines (VMs) have default network settings that can be further optimized for network throughput. This article describes how to optimize network throughput for Microsoft Azure Windows and Linux VMs, including major distributions such as Ubuntu, CentOS, and Red Hat.
16+
Azure Virtual Machines (VMs) have default network settings that can be further optimized for network throughput. This article describes how to optimize network throughput for Microsoft Azure Windows and Linux VMs, including major distributions such as Ubuntu and Red Hat.
2017

2118
## Windows virtual machines
2219

@@ -108,26 +105,6 @@ sudo apt-get install "linux-azure"
108105
sudo reboot
109106
```
110107

111-
### CentOS
112-
113-
In order to get the latest optimizations, we recommend that you create a virtual machine with the latest supported version by specifying the following parameters:
114-
115-
```json
116-
"Publisher": "OpenLogic",
117-
"Offer": "CentOS",
118-
"Sku": "7.7",
119-
"Version": "latest"
120-
```
121-
122-
Both new and existing VMs can benefit from installing the latest Linux Integration Services (LIS). The throughput optimization is in LIS, starting from 4.2.2-2. Later versions contain further improvements. Enter the following
123-
commands to install the latest LIS:
124-
125-
```bash
126-
sudo yum update
127-
sudo reboot
128-
sudo yum install microsoft-hyper-v
129-
```
130-
131108
### Red Hat
132109

133110
In order to get the optimizations, we recommend that you create a virtual machine with the latest supported version by specifying the following parameters:

articles/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,16 +5,13 @@ description: Name resolution scenarios for Azure IaaS, hybrid solutions, between
55
author: asudbring
66
ms.service: virtual-network
77
ms.topic: how-to
8-
ms.date: 04/02/2024
8+
ms.date: 08/02/2024
99
ms.author: allensu
1010
ms.custom: fasttrack-edit, linux-related-content
1111
---
1212

1313
# Name resolution for resources in Azure virtual networks
1414

15-
> [!CAUTION]
16-
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
17-
1815
Azure can be used to host IaaS, PaaS, and hybrid solutions. In order to facilitate communication between the virtual machines (VMs) and other resources deployed in a virtual network, it may be necessary to allow them to communicate with each other. The use of easily remembered and unchanging names simplifies the communication process, rather than relying on IP addresses.
1916

2017
When resources deployed in virtual networks need to resolve domain names to internal IP addresses, they can use one of four methods:
@@ -148,9 +145,9 @@ The default Windows DNS client has a DNS cache built-in. Some Linux distribution
148145

149146
There are many different DNS caching packages available (such as dnsmasq). Here's how to install dnsmasq on the most common distributions:
150147

151-
# [RHEL, CentOS](#tab/redhat)
148+
# [RHEL](#tab/redhat)
152149

153-
**RHEL/CentOS (uses NetworkManager)**:
150+
**RHEL (uses NetworkManager)**:
154151

155152
1. Install the dnsmasq package with the following command:
156153

@@ -238,9 +235,9 @@ options timeout:1 attempts:5
238235

239236
The resolv.conf file is autogenerated, and shouldn't be edited. The specific steps for adding the *options* line vary by distribution:
240237
241-
# [RHEL, CentOS](#tab/redhat)
238+
# [RHEL](#tab/redhat)
242239
243-
**RHEL/CentOS (uses NetworkManager)**:
240+
**RHEL (uses NetworkManager)**:
244241
245242
1. Use a text editor to add the line **`RES_OPTIONS="options timeout:1 attempts:5"`** to the file **/etc/sysconfig/network-scripts/ifcfg-eth0**.
246243
@@ -285,7 +282,7 @@ This section covers VMs, role instances, and web apps.
285282
286283
### VMs and role instances
287284
288-
Your name resolution needs might go beyond the features provided by Azure. For example, you might need to use Microsoft Windows Server Active Directory domains, resolve DNS names between virtual networks. To cover these scenarios, Azure enables you to use your own DNS servers.
285+
Your name resolution needs might go beyond the features provided by Azure. For example, you might need to use Microsoft Windows Server Active Directory domains to resolve DNS names between virtual networks. To cover these scenarios, Azure enables you to use your own DNS servers.
289286
290287
DNS servers within a virtual network can forward DNS queries to the recursive resolvers in Azure. This procedure enables you to resolve host names within that virtual network. For example, a domain controller (DC) running in Azure can respond to DNS queries for its domains, and forward all other queries to Azure. Forwarding queries allows VMs to see both your on-premises resources (via the DC) and Azure-provided host names (via the forwarder). Access to the recursive resolvers in Azure is provided via the virtual IP 168.63.129.16.
291288

0 commit comments

Comments
 (0)