There is a possibility that the following event will occur if you perform specific target operation.
We will inform you what to do when each event occurs.
Target operation
Performing off / on (* 2) (including rebooting with HA) after adding / deleting interfaces and attaching / detaching the volume (* 1).
* 1. We recommend adding / deleting interfaces, attaching / detaching volumes with the instance "stopped", and confirming after startup.
* 2. Performing shut down on the OS, confirm that the status of the instance has stopped, and then start the instance with the portal or API. (Please note that "reboot" on OS is not effective as this action.)
Recommended operation
1. Stop the instance(OS shutdown would be recommended)
2. Add/delete the interface or attach/detach the volume
3. Start the instance
4. Confirm the status of the interface or the volume
4-1 Whether the correspondence between the device name of the interface and IP address is correct, or not
-> If it is not correct, follow the steps described below in "Event and Workaround".
4-2.Whether the volume is online(Windows) or mounted properly(Linux), or not
-> If it is not correct, follow the steps described below in "Event and Workaround".
Once you perform off / on (* 2), these issues never occur again unless you newly add/delete the interface or attach/detach the volume.
# After you perform the above recommended operation, if you newly add/delete the interface or attach/detach the volume, the issues might occur again. In that case you need to follow the steps described below in "Event and Workaround" again.
# The above is the specification of OpenStack.
Event and Workaround
Windows Series
1. If the DHCP function of the connected logical network is disabled and a fixed IP address is set, the correspondence between the device name of the interface and the IP address may be replaced with another logical network connected .
The correspondence between the device name of the interface and the IP address can be confirmed by the following procedure.
· Check the fixed IP address assigned to each logical network on the portal "cloud computing" -> "server" -> "virtual server"> - "instance" screen
· Click the name of the logical network on the "Network" -> "Logical Network" screen of the portal and check the MAC address of the logical network to be connected in "Port" field
· Access instances to the console and check the fixed IP address set for each MAC address on the "Network and Sharing Center" screen of the control panel to see if it is consistent with the display on the portal.
* Workaround
Please reset the correct static IP address from the "Network and Sharing Center" screen of the control panel.
* We recommend that DHCP of logical network be enabled unless there is a special reason to use your own DHCP server.
2. The state of the connected volume may be offline.
The status of the volume can be confirmed from "File service and storage service" -> "volume" -> "disk" of the server manager.
* Workaround
In the Server Manager's "File Service and Storage Service" -> "Volume" -> "Disk" screen, right click on the volume and select "Bring Online" to bring it online. (See the figure below)
Linux Series
1. If the DHCP function of the connected logical network is disabled and a fixed IP address is set, the correspondence between the device name of the interface and the IP address may be changed.
The correspondence between the device name of the interface and the IP address can be confirmed by the following procedure.
· Check the fixed IP address assigned to each logical network on the portal "cloud computing" -> "server" -> "virtual server"> - "instance" screen
· Click the name of the logical network on the "Network" -> "Logical Network" screen of the portal and check the MAC address of the logical network to be connected in "Port" field
· Access the instance on the console, check the fixed IP address set for each MAC address by ifconfig, and check whether it is consistent with the display on the portal
* Workaround
Please reset the correct static IP address.
<Ubuntu Series>
Edit `/etc/network/interfaces`, set the correct static IP address, and execute `service networking restart`.
<CentOS Series>
Edit `/etc/sysconfig/network-scripts/ifcfg-ethx`, set the correct static IP address, then execute `service network restart`. (※ ethx depends on the interface name for setting fixed IP address)
* We recommend that DHCP of logical network be enabled unless there is a special reason to use your own DHCP server.
2. If you do not add the reboot mount setting in / etc / fstab, the mounted volume will be unmounted.
A list of mounted devices can be checked with the `df` command or the `mount` command.
* Workaround
Please mount the volume again with the `mount` command.
In terms of Linux specifications, volumes will be unmounted each time it is restarted unless you add mount settings to `/etc/fstab` so please be sure to add mount settings in advance.