This section explains the procedure for registering network resources.
Network resources are registered as operation and quarantine networks.
Point
For SBC Servers
When registering an SBC server, it is necessary to create the following three network resources:
Management Network (The network resource of the admin LAN directly connected to the manager)
Business Network
Quarantine Network
For both the business network and the quarantine network, select [public LAN] for the type. For the management network, select [admin LAN] for the type.
A management network resource with the name "AdminLan", and the VLAN ID "1" is automatically created during installation of Resource Orchestrator.
Delete "AdminLan", and then create network resources following the procedure described in "2.8.4.2 Registering Management Network Resources Using the GUI (ROR Console)".
Point
For Virtual PCs
When registering a virtual PC, it is necessary to create network resources for the business network and the quarantine network.
For both the business network and the quarantine network, select [public LAN] for the type.
For the name of the business network resource, specify the name that you specified in the "Definition File for Configuring the Business and Quarantine Networks".
For the name of the quarantine network resource, specify a name that you specified in the "Definition File for Configuring the Business and Quarantine Networks".
Prerequisites (SBC Servers)
It is necessary to register rulesets (scripts) for the L2 switches corresponding to network resources in folders of Resource Orchestrator.
For details on rulesets (scripts), refer to "Appendix D Preparing for Automatic Configuration and Operation of Network Devices".
Prerequisites (Virtual PCs)
The prerequisites for registering network resources are as follows.
For the prerequisites for loading IP addresses of virtual PCs to L-Servers, refer to the prerequisites in "2.10 Linking Virtual L-Servers with Configured Virtual PCs".
The network resources satisfy all of the following conditions:
The network resources are registered in resource pools that users can access
The IP address assigned to the virtual PC is within the range of IP addresses configured for the network resources
The VLAN ID of the virtual PC matches that of the L-Server
There are not multiple network resources registered with different VLAN IDs and the same subnet address
In environments in which the VLAN ID cannot be obtained from the virtual PC, there is only a single network resource that is included in the range of the IP addresses assigned to the virtual PC registered in an accessible resource pool
In the above situation, ensure that there are not multiple network resources configured with overlapping IP address ranges.
The network information of the VM hosts is up to date
Perform the following for each VM host.
To update the network information, perform the following procedure using the virtualization software (vSphere Client):
From the Inventory, move to [Hosts and Clusters].
Select the VM host to update the information for.
Click the [Configuration] tab.
Under [Hardware], click [Networking].
Click [Refresh], and then wait for the updating of network information to complete.
To update the network information, perform the following procedure using vSphere Web Client:
From the Inventory, move to [Hosts and Clusters].
Select the VM host to update the information for.
Click the [Configure] tab.
Click [Networking]-[Virtual Switches].
Click the [Refresh the host's network system] icon, and then wait for the update of network information to complete.
To update the network information, perform the following procedure using the virtualization software (VMM console):
Open the [VMs and Services] work space.
From [All Hosts], select the VM host to update the information of.
Select [Refresh] from the pop-up menu.
Wait for the "Refresh host cluster" job to complete.
In [VMs], select all virtual machines and then right-click.
Select [Refresh] from the pop-up menu.
Wait for the "Refresh virtual machine" job to complete.
The most recent information of the VM management software is reflected on the configuration definition information of Resource Orchestrator
Execute the following command on the admin server.
[Windows Manager]
> rcxadm vmmgr refresh <RETURN>This section explains the procedure for registering business network resources using the GUI (ROR console).
Procedure
Perform the following procedure:
In the orchestration tree of the GUI (ROR console), right-click the target network pool, and select [Create Network Resource]-[New] from the displayed menu.
The [Create a network resource] dialog is displayed.
Configure the following items:
Enter a name for the network resource.
If a type other than [Admin LAN] is selected
Enter up to 32 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), or hyphens ("-").
Set the network resources type to create using the following option button.
Public LAN
When creating the public LAN, a network resource name and a VLAN ID must be entered.
Configure as follows.
Use configured virtual switches
Select this checkbox to use a virtual switch that was set up beforehand.
Perform the settings for VLAN IDs and uplink ports.
Specify the VLAN ID to allocate to the LAN switch blade and virtual switch. Select a VLAN ID allocated to the uplink port of the LAN switch blade, or enter a number. Specify a pre-designed VLAN ID.
Enter an integer between "1" and "4094".
For internal networks or external networks with rack mount servers only
Enter a VLAN ID.
Specifying VLAN IDs and clicking [Setting] displays the [Define VLAN ID/Uplink port settings] dialog.
Do not specify for internal networks or external networks with rack mount servers only.
This setting can be omitted if [Public LAN] is specified for the type.
Enter if you want to automatically set a network and IP address for the NIC connected to the network resource when deploying an image on an L-Server. IP addresses included in subnet addresses are allocated to L-Servers, but it is possible to specify a range of addresses to exclude. Clicking the [Add] button will display the [Define start and end IP addresses] dialog, specify the range of IP addresses to exclude, and click the [Add] button. To reactivate excluded IP addresses, check the appropriate checkboxes on the list, and click the [Delete] button. Clicking the [OK] button displays the original dialog with the entered settings.
Network addresses and broadcast addresses are automatically excluded.
Information
If a subnet address has been set for the network resource, the IP address can be automatically set when deploying an image to an L-Server.
If no subnet address is set, the DHCP settings are adopted.
Enter the subnet address and subnet mask to set using the "xxx.xxx.xxx.xxx" format.
The maximum value for a subnet mask is 255.255.255.255 (32-bit mask) and the minimum value is 255.255.0.0 (16-bit mask). However, 255.255.255.254 cannot be specified.
Note
- Specifying the same subnet between network resources for an admin LAN is not possible. For details, refer to "Chapter 9 Defining and Configuring the Network Environment" in the "Design Guide CE".
This setting can be omitted if something other than [Admin LAN] is selected.
Enter the IP address for the default gateway to use when communicating externally of the subnet.
IP addresses that you do not want to automatically allocate to an L-Server (because they are being used or are planned to be used for other devices) can be specified.
Information
The IP addresses that are being used by configured physical servers, virtual PCs, and other devices must be specified for this item to prevent them from being used for L-Servers.
Note
Of the IP addresses specified for the Subnet address/mask, the following addresses are automatically excluded from the target of allocation. They cannot be specified for Exclusion IP range.
- Admin server
- Network address and broadcast address
When using SBC servers, select a ruleset to use from the rulesets available for network resources.
Register the ruleset to use in the common folder on the network device for the network resource. For the folders to register the rulesets for network resources in, refer to "D.3.1 Folders for Network Resources".
A custom label can be defined for the network resource. User-defined labels make it easier to identify the resource.
Enter a string of up to 32 alphanumeric characters (Both double-byte and single-byte characters can be used).
A custom comment can be defined for the network resource. For example, registering detailed work content, troubleshooting, and recovery procedures can speed up recovery.
Enter a string of up to 256 alphanumeric characters (Both double-byte and single-byte characters can be used).
Click the [OK] button.
The network resource is created and registered in a network pool.
Confirmation of Results
In the [Resource List] tab, confirm that the operation network resource has been registered in the target network pool.
This section explains the procedure for registering management network resources using the GUI (ROR console).
Registration of management network resources is necessary when using SBC servers.
Prerequisites
A management network resource with the name "AdminLan", and the VLAN ID "1" is automatically created during installation of Resource Orchestrator.
Delete "AdminLan" in advance.
Procedure
Use the following procedure to create a network resource using an admin LAN subnet, and register it in a network pool:
In the ROR console orchestration tree, right-click the target network pool, and select [Create Network Resource]-[Using existing admin subnet] from the popup menu.
The [Create a network resource] dialog is displayed.
Enter the following items:
Clicking the [Select] button displays the [Select a subnet for the admin LAN] dialog.
Select an already configured admin LAN subnet.
When the selected admin LAN subnet has no name, enter the name of a network resource for "Network resource name".
Enter up to 32 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), or hyphens ("-").
Click the [OK] button.
"Admin LAN" is displayed.
Refer to "VLAN ID/Uplink port settings" in "2.8.4.1 Registering Business Network Resources Using the GUI (ROR Console)".
Refer to "Subnet settings (Optional)" in "2.8.4.1 Registering Business Network Resources Using the GUI (ROR Console)".
Refer to "Ruleset (Optional)" in "2.8.4.1 Registering Business Network Resources Using the GUI (ROR Console)".
Refer to "Label (Optional)" in "2.8.4.1 Registering Business Network Resources Using the GUI (ROR Console)".
Refer to "Comment (Optional)" in "2.8.4.1 Registering Business Network Resources Using the GUI (ROR Console)".
Click the [OK] button.
The network resource is created and registered in a network pool.
When the [Automatically configure VLANs for the uplink ports.] checkbox in the VLAN ID/Uplink port settings is checked, a tagged VLAN is automatically configured in the uplink port of LAN switch blade, when creating a network resource.
Confirmation of Results
In the [Resource List] tab, confirm that the management network resources have been registered in the target network pool.
This section explains the procedure for registering quarantine network resources using the GUI (ROR console).
Procedure
Confirmation of Results
In the [Resource List] tab, confirm that the quarantine network resource has been registered in the target network pool.