Skip to content

Commit 2ae4858

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ip-peering
2 parents 508876e + 6472c1b commit 2ae4858

20 files changed

+170
-293
lines changed

articles/internet-peering/walkthrough-communications-services-partner.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Internet peering for Peering Service Voice walkthrough
3-
description: Learn about Internet peering for Peering Service Voice Services, its requirements, the steps to establish direct interconnect, and how to register and activate a prefix.
3+
description: Learn about Internet peering for Peering Service Voice Services, its requirements, the steps to establish direct interconnect, and how to register a prefix.
44
author: halkazwini
55
ms.author: halkazwini
66
ms.service: internet-peering
77
ms.topic: how-to
8-
ms.date: 08/09/2023
8+
ms.date: 10/23/2024
99
---
1010

1111
# Internet peering for Peering Service Voice walkthrough

articles/internet-peering/walkthrough-direct-peering-type-conversions.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: internet-peering
88
ms.topic: how-to
9-
ms.date: 08/11/2023
9+
ms.date: 10/23/2024
1010
---
1111

1212
# Direct peering type conversion request walkthrough
@@ -28,7 +28,7 @@ A direct peering type conversion for a peering connection can only be requested
2828
## Configure the new type on a Direct Peering
2929

3030
### Convert from PNI to Voice
31-
A peering with standard PNI(s) or PNI(s) enabled for Azure Peering Service can be converted to Voice PNI(s). This conversion must be made at the peering level, which means all the connections within the peering are converted.
31+
A peering with standard PNI or PNI enabled for Azure Peering Service can be converted to Voice PNI. This conversion must be made at the peering level, which means all the connections within the peering are converted.
3232

3333
1. Go to the **Configuration** page of your peering.
3434

@@ -40,7 +40,7 @@ A peering with standard PNI(s) or PNI(s) enabled for Azure Peering Service can b
4040

4141
A standard PNI within a peering can be enabled for Peering Service and can be requested per connection.
4242

43-
You need to be a Peering Service partner to enable Peering Service on a connection. See the [partner requirements page](prerequisites.md) and make sure you have signed the agreement with Microsoft. For questions, reach out to [Azure Peering group](mailto:[email protected]).
43+
You need to be a Peering Service partner to enable Peering Service on a connection. See the [partner requirements page](prerequisites.md) and make sure you sign the agreement with Microsoft. For questions, reach out to [Azure Peering group](mailto:[email protected]).
4444

4545
1. Go to the **Connection** page of your peering.
4646

@@ -58,7 +58,7 @@ Once the request is received, the **Connection State** on each of the connection
5858

5959
Your request is reviewed and approved by someone from the internal team.
6060

61-
Connections remain in the **TypeChangeRequested** state until they're approved. After approval, the connections converted one at a time to ensure that the redundant connection(s) are always up and carrying traffic. The **Connection State** on the connection(s) changes to **TypeChangeInProgress**.
61+
Connections remain in the **TypeChangeRequested** state until they're approved. After approval, the connections converted one at a time to ensure that the redundant connections are always up and carrying traffic. The **Connection State** changes to **TypeChangeInProgress**.
6262
You can see this state in the Connection page.
6363

6464
## Monitor the conversion
@@ -117,7 +117,7 @@ Once the conversion is completed its state returns to **Active**.
117117

118118
**A.** This state could be either due to a configuration or an internal error or the process could be waiting for the peering partner side of configurations. We monitor and catch these issues and give you an email notification promptly. If you have further questions, contact the [Azure Peering group](mailto:[email protected]) for resolution.
119119

120-
**Q.** I have two different peerings, Peering A with standard PNI(s) connections and peering B with Voice connections. I would like to convert the standard PNI peering connections to Voice. What happens to the peering resources in this case?
120+
**Q.** I have two different peerings, Peering A with standard PNI connections and peering B with Voice connections. I would like to convert the standard PNI peering connections to Voice. What happens to the peering resources in this case?
121121

122122
**A.** Once Peering A is converted from PNIs to Voice, the connections from Peering A are moved to Peering B, and Peering A is deleted. For example: If Peering A with two PNI connections are converted to Voice, and Peering B already has two connections, the process results in Peering B (the Voice peering) having four connections now and the Peering A resource will be removed. This is by design so that we maintain only one peering for a given peering provider and type of direct peering at a given location.
123123

articles/internet-peering/walkthrough-monitoring-telemetry.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: internet-peering
88
ms.topic: how-to
9-
ms.date: 08/11/2023
9+
ms.date: 10/23/2024
1010
---
1111

1212
# Peering Service monitoring and telemetry walkthrough
@@ -63,6 +63,6 @@ All Peering Service prefix resources display the following metrics for their Pee
6363

6464
:::image type="content" source="./media/walkthrough-monitoring-telemetry/peering-service-prefix-latency-telemetry.png" alt-text="Screenshot shows how to view the peering service prefix latency under a specific peering service prefix in the Azure portal." lightbox="./media/walkthrough-monitoring-telemetry/peering-service-prefix-latency-telemetry.png":::
6565

66-
- Peering service prefix events: shows various BGP events like route announcements, withdrawals and routes becoming active on the primary or backup links for each prefix in the **Prefix events** page of the Peering Service prefix.
66+
- Peering service prefix events: shows various BGP events like route announcements, withdrawals, and routes becoming active on the primary or backup links for each prefix in the **Prefix events** page of the Peering Service prefix.
6767

68-
:::image type="content" source="./media/walkthrough-monitoring-telemetry/peering-service-prefix-events.png" alt-text="Screenshot shows how to view the prefix events under a specific peering service prefix in the Azure portal." lightbox="./media/walkthrough-monitoring-telemetry/peering-service-prefix-events.png":::
68+
:::image type="content" source="./media/walkthrough-monitoring-telemetry/peering-service-prefix-events.png" alt-text="Screenshot shows how to view the prefix events under a specific peering service prefix in the Azure portal." lightbox="./media/walkthrough-monitoring-telemetry/peering-service-prefix-events.png":::

0 commit comments

Comments
 (0)