You log in as follows:
ServerView RAID Manager must be installed on the system to be administered. If this has not been done, please install ServerView RAID Manager.
Note: Under Windows you find or start the local application by clicking on Start > Programs > Fujitsu > ServerView Suite > RAID Manager > RAID Manager.
If ServerView RAID Manager is already installed on the target system, you can also start the RAID Manager directly via the browser from an arbitrary client. In the address bar, enter the FQDN (Fully Qualified Domain Name) followed by TCP port number 3173 (e.g. https://<FQDN>:3173). Confirm your input using the CR key to get access to the desired system. This works both locally and from a remote system.
Note: If there is an intervening firewall in the environment, you need to configure the network settings so that the port used by ServerView RAID Manager will not be blocked.
Note: When you run ServerView RAID Manager for the first time after installation, you must install a security certificate. Information on doing this is provided under Security Certificate.
If you have not turned on Single Sign On and Role Based Access Control the following login screen is displayed in the browser, after a connection has been successfully set up to the system.
Note: By the Help button at the top right the online help can be opened directly without the user needing to log in.
If required, choose a different language in the login screen by selecting the related national flag.
Enter the user name and the password which are to be used to log into this system. Then click on Login to enter ServerView RAID Manager.
![]() |
For authentication and authorization purposes ServerView RAID Manager uses the interfaces provided by the operating system of the server to be monitored. Users who have been set up with administration rights can perform configuration via ServerView RAID Manager. Non-privileged users can obtain a read-only view of the RAID configuration on the server as well as get write access rights for ServerView RAID Manager. To grant certain users without administration rights the possibility to take over configuration tasks or a read-only access, this can be done as follows:
To get more flexibility the names for the two user groups described above can be freely defined by editing the properties Admin group and User group. These properties can be found on the Settings tab of System category. If no group name is given there will be no check for membership in a user group during authentication. The settings are activated immediately. On Windows the search order for group membership is fixed. First the local user groups of the system are checked, then the global groups in an active directory, and finally the local groups in an active directory. On Linux the search order is defined in PAM configuration. On systems with very restrictive access control it may be necessary to configure PAM access by editing /etc/security/access.conf additionally. All other users even though they can authenticate at the server have no authorization for the ServerView RAID Manager functionality. The first user automatically has read/write authorization. Every subsequent user only has read authorization, but – provided they have appropriate administration rights – can obtain write authorization. The user who had write authorization up to this point is then informed of this. |
Please check and if necessary change the following settings for
Add zone settings of browser as following:
If you use a proxy server for the Internet you must bypass it to enable you to access the server. If you know the IP address of the system that you wish to administer remotely, you might select the following, for example, for
![]() |
Do not use "Back", "Foward", or "Refresh" button of the browser. There is no working web browser in Core Editions of Windows Server 2008 and newer installations. |
If your server management environment is built around ServerView Operations Manager 5.0 or newer and the Single Sign On infrastructure (CAS - Central Authentication Service) and directory services extensions for Role Based Access Control (RBAC) are configured you can participate with ServerView RAID Manager.
After the first login to ServerView RAID Manager as described above switch to the Settings tab of your system where you can enable CAS and RBAC.
Edit either the CAS or the LDAP entry to enabled. Both entries are related at the moment so if you turn on CAS the setting for LDAP will be enabled automatically.
![]() |
After turning on CAS and LDAP do not logout from ServerView RAID Manager until connection to CAS and LDAP is working correct or CAS and LDAP are turned off again. Otherwise you will not be able to login again. If CAS and LDAP are mistakenly enabled with incorrect settings it is possible to turn them off again by using amCLI: amCLI -s 21/3 CAS disabled |
If you have enabled CAS and LDAP you see a few properties that have to be adapted to the existing environment. This information is available on the Central Management Station (CMS) where ServerView Operations Manager is installed.
Up to and including version 6.00 of ServerView Operations Manager open the following file on that system in your favorite editor:
Starting with version 6.10 of ServerView Operations Manager JBoss 7 is used. Open the following file on that system in an editor:
The XML tags in that file approximately match the properties in the Settings tab of ServerView RAID Manager. Change the properties accordingly.
CAS:
CAS server
CAS port
CAS base URL
LDAP:
LDAP server
LDAP port
Base DN
User search base User search filter Role DN Username Password |
...
|
![]() |
The names of the configured servers must match exactly. |
![]() |
In newer version of ServerView Operations Manager the securityCredentials entry is encrypted. Ask your ServerView Operations Manager administrator for the password. |
To test the connection to CAS you can execute the action "Test CAS connection". To test the connection to the directory service it is best practice to allow an unsecure communication first. Enable property "Allow non-secure access" and set port as configured. Now execute action "Test LDAP connection".
If both tests pass you have to set up the environment for secure connection to the directory service. You need a certificate file from the Central Management Station. This file can be either obtained manually or downloaded from the CMS.
The file containing the certificate can be found in the following directory on the CMS:
To download the file direct your browser to https://<system_name>:3170/Download/pki where you have to login by Central Authentication Service. Then store the certificate file <system_name>.scs.pem on your local system import it into your system's certificate store.
On Windows systems follow these steps to import the certificate:
Click Start, click Run, type mmc, and then click OK.
On the File menu, click Add/Remove Snap-in, and then click Add.
In the Add Standalone Snap-in dialog box, click Certificates, click Add, click Computer account, click Next, and then click Finish.
Click Close, and then click OK.
Expand Certificates (Local Computer), expand Trusted Root Certification Authorities.
Right-click Certificates, click All Tasks, click Import, and then click Next.
In the File name box, type the file name or browse for your stored certificate file, and then click Next.
Click Finish, and then click OK.
On Linux systems you need to copy the certificate file into the CA certificate directory (often /etc/ssl/certs/) and reindex all certificates with "c_rehash".
After successful installation return to ServerView RAID Manager, disable the unsecure access to LDAP, and execute "Test LDAP connection" again. If CAS and LDAP connection tests were successful ServerView RAID Manager is now prepared to participate in Single Sign On and Role Based Access Control.
If you logout now the following screen will be displayed:
After clicking the link on the right side of the logout screen the login screen from CAS will be displayed: