This section explains how to use peripheral devices from an L-Server.
When installing an OS after creating an L-Server and performing L-Server maintenance, the L-Server console can be obtained.
When performing usual operations, or the console cannot be obtained, log in to an L-Server through the network.
Example
Network Connection Example
[Windows]
Remote desktop connection
[Linux]
SSH connection
Prerequisites for Console Connections
When using a console connection, the prerequisites differ depending on the server type of the L-Server used.
For Physical L-Servers
When the hardware is PRIMERGY, and the iRMC video console redirection function can be used, connection to the console is possible.
Note
For console connection, use functions of ServerView Operations Manager.
For details on ServerView Operations Manager, refer to "6.1.2.4 Required Software" in the "Overview".
For Virtual L-Servers
On VMware and Hyper-V, when an admin client is installed, and communication between admin clients and VM hosts is possible, connection of the console is possible.
Note
For console connection, use admin client functions. Check if the console connection is possible from the admin client in advance.
[VMware]
Normally, the admin server notifies the admin client of the IP address of the admin LAN of the VM host registered with the admin server to use as the connection destination for the console. For this reason, the console cannot be connected to by admin clients that exist on networks that are not connected to the admin LAN.
To connect to the console from a admin client that is connected only to the public LAN, in the definition file on the admin server, set the VM host connection destination that can be connected from the admin client. The admin server notifies of the VM host connection destination that can be connected from the public LAN and the admin client can connect to the console.
Note
If the destination for connection of a public LAN that has been set for a VM host is specified in the definition file, a console connection from the admin LAN will be unavailable.
Further, the VM host connection can be specified for each tenant. The L-Server console connection stored in tenants makes requests to the VM host connection set in the definition file. One VM host can be shared by multiple tenants in an environment where there is a separate public LAN for each tenant.
Preparations for using a console connection from a public LAN
Preparations are necessary in order to use a console connection from a public LAN.
For details, refer to "E.1 VMware" in the "Design Guide CE".
Setting the VM host connection for each tenant
Set the VM host connection for when the console window for the L-Server stored in the tenant is started.
For details, refer to "8.2 VMware" in the "Setup Guide CE".
Setting the console connection of VMware vSphere virtual L-Servers (VMware vSphere 5.1 or later)
Setting the admin client
In order to use the console of VMware vSphere, VMware Remote Console Plug-in must be installed on the admin client beforehand.
For details, refer to "6.1.2.4 Required Software" in the "Overview".
The console of VMware vSphere communicates with the VM host where the L-Server operates using the proxy settings of the browser. Set the proxy setting of the browser to allow communication with the VM host where the L-Server operates.
Setting the proxy server
When using the console of VMware vSphere through a proxy server, it is necessary to configure the proxy server so the admin client can communicate with VM host where the L-Server operates.
Configure the proxy server so the IP addresses and network addresses of admin clients are able to connect to the proxy server.
Configure the proxy server so the following port numbers used by the console connection of VMware vSphere 5.1 are able to connect to the proxy server.
- 443
- 902
For details of the proxy server settings, refer to the manual of the proxy server.
Note
When the admin client OS is Windows, the 64-bit version of the browser cannot be used to connect to the console.
[Hyper-V]
Admin clients must be in the same domain as SCVMM or VM hosts. It is necessary to install the VMM management console for SCVMM that is of the same version as the SCVMM registered as VM management software.
Note
When using console connection function in Firefox, it is necessary to upgrade JDK to 1.6 or later after ROR manager is installed.
Console
This section explains the L-Server console connection.
Use the following procedure to connect the console:
Right-click the target L-Server in the orchestration tree, and select [Console Screen] from the popup menu.
The confirmation dialog is displayed.
When using a virtual L-Server, click the [OK] button.
The L-Server console window is displayed in another window.
Note
When using virtual L-Servers, it is necessary to permit the starting of the console screen using the policy settings of Java Plug-in.
Use the following procedure to permit the starting of the console screen:
When starting of the console screen is not allowed, the [Download] dialog of the Java policy setup script is displayed.
Click the [OK] button.
The Java policy setup script is downloaded. Save the file.
Execute the Java policy setup script to configure the settings for permitting the console screen startup.
After performing the configuration, close the web browser.
Log in to Resource Orchestrator again using a web browser, and the console screen can then be started from the ROR console.
[VMware]
When starting the console screen in the following environment, it is not necessary to configure policy settings of the Java Plug-in.
VMware vSphere 5.1
VMware vSphere 5.5
VMware vSphere 6.0
In cases where the following VM products are used for a virtual L-Server, starting the ROR console turns the L-Server "ON" when the selected L-Server was "OFF".
VMware vSphere 4.0
VMware vSphere 4.1
For physical L-Servers, when opening the L-Server console screen at the second time or later, a window for iRMC management may be opened instead of the console screen.
If an iRMC management screen is displayed, close that screen and then start the console screen again.
For details, refer to "3.3 When Opening the Physical L-Server Console Screen, the iRMC Management Window may be Opened." in "Troubleshooting".
