Skip to content

Commit 219bc2e

Browse files
RoRoJLaure-di
authored andcommitted
fix(em): add info for reserved IP (scaleway#3998)
* fix(em): add info for reserved IP * fix(em): wording * Apply suggestions from code review
1 parent bd0d7bd commit 219bc2e

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

bare-metal/elastic-metal/how-to/use-private-networks.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,8 @@ You can attach/detach Elastic Metal servers to a Private Network from either the
6666
- It is created in your [default VPC](/network/vpc/concepts/#default-vpc) for the region
6767
- It has an auto-generated [CIDR block](/network/vpc/concepts/#cidr-block) used to allocate private IP addresses to servers attached to the network. Each attached Elastic Metal server will get an IPv4 and an IPv6 address on the Private Network.
6868
</Message>
69-
6. Click **Attach Private Network** to confirm.
69+
6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/network/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a [reserved IP address](/network/ipam/concepts/#reserved-ip-address) for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Elastic Metal server will have on this Private Network.
70+
7. Click **Attach to Private Network** to confirm.
7071

7172
### From the VPC section of the console
7273

0 commit comments

Comments
 (0)