-
Notifications
You must be signed in to change notification settings - Fork 258
feat(em): understanding em networking #5060
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
a9926cb
feat(em): understanding em networking
bene2k1 ee3a910
feat(em): networking
bene2k1 659e8de
fix(em): fix typo
bene2k1 cb6430b
fix(em): fix typo
bene2k1 4283c5d
Apply suggestions from code review
bene2k1 9d8ecea
feat(em): update wording
bene2k1 24a643d
Apply suggestions from code review
bene2k1 3b606d7
Apply suggestions from code review
bene2k1 06dc427
Update pages/elastic-metal/reference-content/elastic-metal-networking…
bene2k1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file added
BIN
+183 KB
...ic-metal/reference-content/assets/scaleway-elastic-metal-networking-schema.webp
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
63 changes: 63 additions & 0 deletions
63
pages/elastic-metal/reference-content/elastic-metal-networking.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| --- | ||
| meta: | ||
| title: Understanding Elastic Metal networking | ||
| description: This page provides insights into the network setup of your Elastic Metal server. | ||
| content: | ||
| h1: Understanding Elastic Metal networking | ||
| paragraph: This page provides insights into the network setup of your Elastic Metal server. | ||
| tags: elastic-metal networking | ||
| dates: | ||
| validation: 2025-06-03 | ||
| posted: 2025-06-03 | ||
| categories: | ||
| - bare-metal | ||
| --- | ||
|
|
||
| Each Scaleway Elastic Metal server is configured with a single physical Network Interface Card (NIC), pre-configured by default. This NIC handles both public internet traffic and private network communication, sharing the total available bandwidth. | ||
|
|
||
| <Message type="note"> | ||
| A second physical Network Interface Card (NIC) might be installed in your server, however it is not in use. | ||
| </Message> | ||
|
|
||
| <Lightbox src="scaleway-elastic-metal-networking-schema.webp" size="large" alt="Schema displaying a theoretical network configuration of an Elastic Metal server" /> | ||
|
|
||
| ## Public bandwidth and flexible IPs | ||
|
|
||
| Public bandwidth on Elastic Metal servers is limited by default and is typically lower than the maximum capacity of the NIC. This limit can be increased based on your server plan and configuration. | ||
|
|
||
| A public IPv4 address is provided by default with each Elastic Metal server and is configured automatically on the machine during OS installation via the Scaleway console. | ||
| If you choose to manually install your OS, you can allow it to configure the network settings automatically using DHCP. | ||
| The default IPv4 address is statically assigned to the physical machine and cannot be transferred to another Elastic Metal server. | ||
|
|
||
| [How to adjust the available public bandwidth for an Elastic Metal server](/elastic-metal/how-to/adjust-available-bandwidth/) | ||
|
|
||
| ### Flexible IPs | ||
|
|
||
| Flexible IPs are IPs that are unrelated to the physical machine and can be assigned to your Elastic Metal resources. Flexible IPs can either be an IPv4 (/32 subnet - one IPv4 address) or an IPv6 subnet (/64 subnet). | ||
|
|
||
| There are two scenarios for additional flexible IPs: | ||
|
|
||
| * Without virtualization: Assign the additional IP directly to the host OS interface. No virtual MAC or interface is required. | ||
| * With virtualization: A virtual interface must be added to the network interface using a hypervisor (e.g. QEMU/KVM), and attached to a single virtual MAC address. | ||
|
|
||
| Refer to the documentation on [how to configure a flexible IP on Elastic Metal](/elastic-metal/how-to/configure-flexible-ip/) for more information. | ||
|
|
||
| ### Flexible IPv6 | ||
|
|
||
| Scaleway supports flexible IPv6 addresses on Elastic Metal servers. These operate similarly to flexible IPv4 addresses and must also be manually configured. | ||
|
|
||
| [How to configure a flexible IPv6 on Elastic Metal](/elastic-metal/how-to/configure-flexible-ipv6/) | ||
|
|
||
| ## Private Networks | ||
|
|
||
| Private Networks are an optional feature that can be enabled per server. For each attached Private Network, a dedicated VLAN with a private IP is created on the network. Once created, the private IP and VLAN need to be [configured manually](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) on the server. This setup enables secure, isolated communication between Elastic Metal servers and other resources (e.g. Instances, Load Balancers) within the same Private Network or VPC. | ||
|
|
||
| [How to use Private Networks with Elastic Metal servers](/elastic-metal/how-to/use-private-networks/) | ||
|
|
||
| ## KVM public IP | ||
|
|
||
| The KVM public IP is the IP address used to access the KVM-over-IP device of the machine. | ||
| This IP address is used to provide remote access to the server in case the machine can no longer be reached on the public IP, or to install a custom OS using the KVM over IP device. It is configured on the same physical NIC, but is not visible from the OS. | ||
| The KVM public IP uses a special connection handled by the Baseboard Management Controller (BMC) and Scaleway's internal network. | ||
|
|
||
| [How to activate remote access on an Elastic Metal server](/elastic-metal/how-to/activate-remote-access/) | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.