About limits for the line, router, and switch

What is the approximate line bandwidth of the shared segment? / Are there any bandwidth limits?

  • The only plan for bandwidth is a 100Mbps shared line (no bandwidth guarantee). When using a bandwidth exceeding this size, please use router + switch.
  • The outbound bandwidth limit from the virtual server is 100Mbps. There is no inbound bandwidth limit.

Are there packets which cannot pass through shared segments?

The following conditions apply to packets that are sent to shared segments from the server.

  • Passthrough occurs when the source IP address is an IP address assigned to the server.
  • Passthrough occurs when the ARP packet Sender IP address is an IP address assigned to the server.
  • Passthrough does not occur when the source MAC address is different from the one assigned at the time of server creation.
  • Passthrough does not occur for multicast packets and broadcast packets other than ARP.
  • Passthrough does not occur for packets which do not satisfy the conditions listed above.

Is there a bandwidth limit for the switch?

 As shown below, line bandwidth between the server and switch is limited depending on the memory space installed on the server.

Note

There are no limits on line bandwidth for devices (load balancer, bridge, etc.) other than the server or if the server is a private host.

Memory space installed on server Bandwidth limit value
Less than 32GB 1.0Gbps
32GB to less than 128GB 2.0Gbps
128GB to less than 224GB 5.0Gbps
224GB or higher 10.0Gbps

▼Example of bandwidth limit for each line connected to the switch

How many servers or appliances can be connected to the switch?

There are no limits on the number of devices that can be connected. However, we recommend an upper limit of about 200 devices due to concern for occurrence of ARP storm.
When connecting more than the recommended number of devices, please consider implementing measures such as tuning of the ARP aging time and ARP table size at the server, or segmentation using the VPC router.

Is there a bandwidth limit for router + switch?

  • A bandwidth limit is applied between the server and switch using the same conditions as the previous item (Is there a bandwidth limit for the switch?).
  • There is no bandwidth limit for devices other than servers, or between the router and switch.
  • Bandwidth between the global network and router is secured for both inbound and outbound.

*When using connection bandwidth of 500Mbps, please use 500Mbps (shared) bandwidth for inbound/outbound during peak times.

▼Example of bandwidth limit for each line connected to router + switch

What kinds of fees are incurred when changing the plan (bandwidth change) for router + switch?

Each time that settings are specified to change the bandwidth, the router + switch for the current line speed is cancelled, and a new contract is consummated for router + switch for the line speed.

When bandwidth is changed in units of 1 hour or 1 day, fees are calculated in the same way as other resources such as servers and disks. For details, please refer to Payment of fees.

Are there traffic limits depending on the volume of transferred data?

For each connected line, when significantly exceeding the estimate for transferred data volume listed below, bandwidth limits are implemented on each customer server depending on conditions for backbone bandwidth at SAKURA internet.

Line Approximate data transfer threshold at which limits are applied
Shared segment (100Mbps) Monthly 1.6TB (average 5Mbps)
Router + switch (100Mbps) Monthly 3.2TB (average 10Mbps)
Router + switch (250Mbps) Monthly 8.1TB (average 25Mbps)
Router + switch (500Mbps) Monthly 16.2TB (average 50Mbps)
Router + switch (1,000Mbps) Monthly 32.4TB (average 100Mbps)
Router + switch (1,500Mbps) Monthly 48.6TB (average 150Mbps)
Router + switch (2,000Mbps) Monthly 64.8TB (average 200Mbps)
Router + switch (2,500Mbps) Monthly 81.0TB (average 250Mbps)
Router + switch (3,000Mbps) Monthly 97.2TB (average 300Mbps)
Router + switch (5,000Mbps) Monthly 162TB (average 500Mbps)

*For shared segment lines, the data transfer volume per server is the total transfer volume for servers where router + switch is connected.
*The data transfer volume calculated as the threshold is calculated separately for both inbound and outbound.
*For [Router + Switch] and [Switch], there is no limit on communication completed in the switch.
*Calculation of the monthly data transfer volume takes place at 0:00 AM on the 1st of each month. When creating a router + switch or server that is connected to a shared segment in the middle of the month, the time of creation is used at the time of calculation.

How is the bandwidth limit decided when exceeding the estimate for the data transfer volume?

When the estimate for the monthly data transfer volume discussed above is significantly exceeded, bandwidth limits are implemented on each customer server depending on conditions for backbone bandwidth at SAKURA Internet. When setting a bandwidth limit, an upper limit is set to prevent exceeding the average bandwidth in the estimate for monthly data transfer volume.

After traffic limits have been applied to a shared line, when switching to router + switch, limits for the shared line are not applied due to communication being conducted on the router + switch line. These limits are continually applied after returning to connection with a shared line.

Limits are removed sequentially starting from 0:00 AM on the 1st day of each month.

When SAKURA internet implements bandwidth limits, an email notification is sent one business day in advance to the registered email address “Emergency contact email address”. (However, email notifications may not be sent in the event of an emergency.)

Is there a plan that guarantees line bandwidth?

Currently, there is no schedule for providing a plan that guarantees line bandwidth.

Is there a limit on connection to switch/router + switch from the server?

These following types of limits are applied based on the NIC type (standard installation NIC/additional NIC) at the server.

  Shared segment Router + switch Switch
Standard installation NIC
(1st NIC card)
Connection possible Connection possible Connection possible
Additional NIC
(2nd to 10th NIC card)
Connection not possible Connection not possible Connection possible

Is there a limit on the number of servers that can be connected to switch or router + switch?

There is no limit on the number of servers that can be connected.

Is there a packet that cannot pass through the switch or router + switch?

The following conditions apply to packets sent from the server to the switch or router + switch.

  • The IPv6 packet passes through.
  • The DHCP packet passes through (limited to port No. 68 for UDP source and port No. 67 for the address).
  • The ARP packet passes through.
  • Packets that use VRRP virtual MAC address (VRID is 1 to 4) for the source MAC address pass through.
  • Unicast packets pass through.
  • Broadcast packets and multicast packets only pass through under the following protocol.
    • ARP
    • DHCP
    • IPv6
    • VRRP
    • OSPF
    • RIP
  • In the case of router + switch, there is passthrough of packets with an IP address range in which the source IP address is assigned to the router + switch.
  • Passthrough does not occur when the source MAC address is different from the one assigned at the time of server creation.
  • Passthrough does not occur for packets which do not satisfy the conditions listed above.

Is it possible to use hybrid connection and bridge connection at the same switch?

Bridge connection cannot be performed for switches on clouds that have already been configured for hybrid connection.
Similar connection can be achieved by specifying the cloud switch as one hybrid connection destination.

When using promiscuous mode at lines connected to the shared segment, it is possible to acquire packets addressed to other users. Is this a problem?

Normally, even when operating in promiscuous mode, packets addressed to other users do not reach the interface.
However, due to the L2 network flooding mechanism, if abnormal packets are generated due to incorrectly configured users, attacks, etc., there are cases in which packets addressed to other users are sometimes received.

This phenomenon does not occur for router + switch because it is a private segment. Please consider using router + switch if you want to prevent leakage of packages to other users.

How many seconds is the MAC address aging time for the switch?

The aging time is 86,400 seconds (24 hours). The virtual switch in SAKURA Cloud does not have a fixed physical port. Consequently, it is resistant to connection changes for the device and suppresses network load caused by flooding. This means that settings are longer when compared to normal physical networks.

I am having trouble using L2TPv3/IPsec to connect between server which I constructed in SAKURA Cloud and the network at my company. What could be causing this problem?

Connection is not possible because the SAKURA Cloud network filters L2TPv3/IPsec. We apologize for the inconvenience, but please use a different protocol.

Is mirroring of packets possible?

Mirroring of an NIC port installed in a server is not possible in the SAKURA Cloud environment. Also, we do not provide a port mirroring function for switch or router + switch.

What is the difference between hybrid connection and bridge connection?

Please refer to the chart comparing each service that is available Here .

Is virtual NIC multi-queue (CPU core balancing) supported?

It is supported for servers where the NIC driver runs in the paravirtualization mode (Virtio). (This excludes servers in the Ishikari Zone No. 1 old plan environment.)
You can improve network processing performance by starting the irqbalance daemon on the customer server. (It is enabled by default on servers created using the CentOS public archive provided by our company.)

*For servers which have run continually since before 12:00 PM on March 14, 2019, it will be applied when the power to the server is turned off and then turned on again.