This section explains how to modify specifications of network resources.
The availability of modification for each item depending on the network resource type is shown below:
Category | Item | Admin LAN Network Resources Directly Connecting with Manager | Network Resources of Additionally Created Admin LAN | Network Resources of iSCSI or Public LAN |
|---|---|---|---|---|
General Area | Network resource name | Yes | Yes | Yes |
Label | Yes | Yes | Yes | |
Comment | Yes | Yes | Yes | |
Connection Information | VLAN ID | No | No | No |
External Connection Ports | Yes (*1) | Yes (*1) | Yes (*1) | |
Automatic configuration | No | No | No | |
physical LAN segment | Yes (*2) | Yes (*2) | Yes (*2) | |
Auto-configuration of VLAN on external ports | No | No | No | |
Subnet information | Subnet address/subnet mask | Yes (*3, *4) | Yes (*3) | Yes |
IP address to exclude | Yes | Yes | Yes | |
Default gateway | Yes (*4) | Yes | Yes | |
Network resource type | - | No | No | No |
Auto-configuration of network devices (L2 switches) (*5) | VLAN IDs, connection ports, etc. | No | No | Yes |
Yes: Modification is possible
No: Modification is not possible
*1: Even after changing external connection ports, virtual switches, port groups, and virtual bridges that have been deployed can be used as is. New information on the external connection ports will be reflected on the configuration of virtual switches, port groups, and virtual bridges deployed after modification of the network resource. When modifying the deployed network according to the external connection port, server virtualization software must be operated directly to do so.
*2: Even after changing physical LAN segments, virtual switches, port groups, and virtual bridges that have been deployed can be used as is. New information on the physical LAN segments will be reflected on the configuration of virtual switches, port groups, and virtual bridges deployed after modification of the network resource. When modifying the deployed network according to the physical LAN segment, server virtualization software must be operated directly to do so.
*3: The subnet address and subnet mask of admin LAN can be changed, when there are no physical servers or L-Servers using the network resources of the target of modification.
*4: Modification can be performed by executing the rcxadm mgrctl modify command.
*5: Possible when the network resource has been created specifying auto="true" for the "<SwitchConfiguration>" element in the XML definition file.
Use the following procedure to change network resource specifications.
Right-click the target network resource in the orchestration tree, and select [Change Settings]-[Modify Specification] from the popup menu.
The [Modify a network resource] dialog is displayed.
Change the items you want to modify.
Click the [OK] button.
The network resource is changed.
Note
The default gateway address of an admin LAN resource that is the same subnet address as that of the manager cannot be changed.
The IP address of the L-Server is managed using an index from the start address of the network resources.
Therefore, when modifying the subnet, the IP address of the L-Server is allocated as follows:
When the start address of the network resource remains the same even after the subnet is changed
The IP address of the L-Server is not changed.
When the start address of the network resource changes after the subnet is changed
The IP address of the L-Server is changed automatically.
After a subnet address of a network resource (segment) included in an L-Platform is changed, when the IP address of an L-Server on the L-Platform is changed, it is necessary to have the L-Platform recognize the changed IP address of the L-Server. For this reason, release the L-Server from the L-Platform before importing the L-Server back into the L-Platform.
If the IP address exceeds the end address of the network resource due to expansion of the subnet mask, the corresponding IP address of the L-Server will be "Unallocated".
Before modifying the subnet, change the IP address of the L-Server to one within the index of the changed end address, or set the IP address as unallocated.
When the IP address of an L-Server on an L-Platform is changed, it is necessary to have the L-Platform recognize the changed IP address of the L-Server. For this reason, release the L-Server from the L-Platform before importing the L-Server back into the L-Platform.
When the subnet is changed, the OS configuration is not changed.
Manually change the OS configuration to match the detailed information of the L-Server.
Making the following change to the network resource for which automatic configuration of VLAN on the external connection port is specified may cause a network loop.
Adding another external connection port on a LAN switch blade which has been already specified as an external connection port
In this case, take action to prevent a network loop first, such as disconnecting the cable for the external connection port to be added, before making changes to the network resource.
