Skip to content

Commit d031862

Browse files
Update headers in Azure VMware documentation
1 parent 1ac2ece commit d031862

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-vmware/architecture-network-design-considerations.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,11 @@ For AS-Path Prepend, consider the following prerequisites:
3232
* Use either 2-byte or 4-byte public ASN numbers.
3333

3434

35-
### Reserved Private ASNs in Azure VMware Solution
35+
## Reserved Private ASNs in Azure VMware Solution
3636

3737
Azure VMware Solution utilizes specific private Autonomous System Numbers (ASNs) for its underlay network infrastructure. To prevent conflicts and ensure seamless network integration, customers **must not** use the following ASNs within their network configurations:
3838

39-
#### Reserved ASNs for Underlay Networking
39+
### Reserved ASNs for Underlay Networking
4040

4141
The following ASNs are reserved for internal Azure VMware Solution infrastructure and should be avoided by customers:
4242

@@ -48,7 +48,7 @@ The following ASNs are reserved for internal Azure VMware Solution infrastructur
4848

4949
- **Management ASNs:** 65000 – 65412
5050

51-
#### Impact of Using Reserved ASNs
51+
### Impact of Using Reserved ASNs
5252

5353
Using any of the ASNs listed above in your environment may lead to BGP session failures, network routing conflicts, or service disruptions. Ensure that your ASN assignments do not overlap with these reserved values.
5454

0 commit comments

Comments
 (0)