Top
ServerView Resource Orchestrator Cloud Edition V3.1.0 Operation Guide
ServerView

9.5.3 Procedure for Addition of Network Devices

This section explains the operation for adding network devices.


9.5.3.1 Adding L2 Switches to Handle Insufficient Numbers of Ports when Adding Servers

This section explains the procedure for addition, assuming a case where it is necessary to add L2 switches, since the LAN ports of the L2 switch to connect to are insufficient when adding servers.

The explanation is mainly about operations related to L2 switches.

When there is no description, the following operations are performed by an infrastructure administrator.

Figure 9.5 Image of L2 Switches to Add

  1. Design additional configurations. (Network device administrator)

  2. Provide the additional network device information to the infrastructure administrator. (Network device administrator)

    Add a network device in the state where the following operations have been completed.

    • Initial configuration

    • Operation test

    • Integration of the device into a physical network configuration

  3. Register the resources of the server.

    It is necessary to register chassis or LAN switch blades for a blade server.

  4. Create network configuration information (XML definition) using the acquired network device information.

  5. Register an additional L2 switch as a network device.

    Use the rcxadm netdevice create command to register as a network device.

  6. When the following applies to the additional network device, create and register rulesets.

    • When adding an L2 switch of a model for which sample scripts are not prepared, or an L2 switch of a model that has not been used in the system until now.

      In this case, it is necessary to create a directory to allocate rulesets to.

    • When using a model for which sample scripts are not prepared, or even when using a model which has been used in the system until now, by configuring definitions using the different rules (scripts)

    • Even when using a model for which sample scripts are prepared, and when using a model with definitions configured using different rules (scripts)

    Note

    Details of sample scripts may be reviewed and modified. When using rulesets modified from prepared sample scripts, the modified details will be cleared by replacing the modified scripts with the sample scripts, when updating sample scripts.
    In order to prevent this type of problem, when creating scripts by referring to sample scripts, create the new rulesets after copying the rulesets of the sample script, and perform necessary modifications.

  7. Change all resources using the additional network devices.

    It is necessary to add the information about uplink ports of the added chassis, when adding a blade server.

    Use the rcxadm network modify command to modify a network resource.

  8. Register the added server as a resource in the necessary resource pool.

See

  • For details on the initial configurations of network devices, refer to "9.2.3 Settings for Managed Network Devices" in the "Design Guide CE".

  • For details on how to create network configuration information (XML definition), refer to "14.6 Network Configuration Information" in the "Reference Guide (Command/XML) CE".

  • For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".

  • For details on ruleset creation and the registration destinations, refer to "F.3 Creating a Folder for Registering Rulesets" in the "Setup Guide CE".

  • For details on the rcxadm network command, refer to "3.9 rcxadm network" in the "Reference Guide (Command/XML) CE".

  • For details on how to register a resource in a resource pool, refer to "Chapter 19 Resource Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".


9.5.3.2 Adding Firewalls, Server Load Balancers, and L2 Switches for Additional Tenants

This section explains the procedure for addition, assuming a case where it is necessary to add a network device or a server in order to add a tenant.

The explanation is mainly about operations related to firewalls, server load balancers, and L2 switches.

When there is no description, the following operations are performed by an infrastructure administrator.

Figure 9.6 Image of Tenants to Add

  1. Design additional configurations. (Network device administrator)

  2. Provide the additional network device information to the infrastructure administrator. (Network device administrator)

    Add a network device in the state where the following operations have been completed.

    • Initial configuration

    • Operation test

    • Integration of the device into a physical network configuration

  3. Register the resources of the server.

    It is necessary to register chassis or LAN switch blades for a blade server.

  4. Create network configuration information (XML definition) using the acquired network device information.

  5. Register the added firewall, server load balancer, and L2 switch as network devices.

    Use the rcxadm netdevice create command to register as a network device.

  6. When the following applies to the additional network device, create and register rulesets.

    • When adding a firewall, server load balancer, or L2 switch of a model for which sample scripts are not provided, or those of a model that has not been used in the system until now

      In this case, it is necessary to create a directory to allocate rulesets to.

    • When using a model for which sample scripts are not prepared, or even when using a model which has been used in the system until now, by configuring definitions using the different rules (scripts)

    • Even when using a model for which sample scripts are prepared, and when using a model with definitions configured using different rules (scripts)

    Note

    Details of sample scripts may be reviewed and modified. When using rulesets modified from prepared sample scripts, the modified details will be cleared by replacing the modified scripts with the sample scripts, when updating sample scripts.
    In order to prevent this type of problem, when creating scripts by referring to sample scripts, create the new rulesets after copying the rulesets of the sample script, and perform necessary modifications.

  7. Create a tenant and register a tenant administrator.

  8. Back up environments using the functions provided by the firewall and server load balancer.

    Backups can be used for restoration when replacing firewalls or server load balancers due to device failure.

    For details on how to back up environments, refer to the manuals of the firewall and server load balancer being used.

  9. Register additional servers, firewalls and server load balancers in a resource pool for tenants as resources.

See

  • For details on the initial configurations of network devices, refer to "9.2.3 Settings for Managed Network Devices" in the "Design Guide CE".

  • For details on how to create network configuration information (XML definition), refer to "14.6 Network Configuration Information" in the "Reference Guide (Command/XML) CE".

  • For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".

  • For details on ruleset creation and the registration destinations, refer to "F.3 Creating a Folder for Registering Rulesets" in the "Setup Guide CE".

  • For details on how to create a tenant, refer to "11.3 Creating Tenants" in the "User's Guide for Infrastructure Administrators CE".

  • For details on how to register tenant administrators, refer to "Chapter 3 Operating User Accounts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

  • For details on how to register a resource in a resource pool, refer to "Chapter 19 Resource Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".