The following description shows resolutions to problems relevant to Web-Based Admin View and GDS Management View.
In one of the following circumstances, take action as indicated for the relevant situation.
(1) Web-Based Admin View abnormality
Explanation
The following problems may occur in Web-Based Admin View.
Web-Based Admin View top menu is not displayed. Or, even if it is, the screen is not displayed properly, or messages such as 0001 to 0050 are displayed.
The screen does not change even after confirming 0002, 0003, or 0007 message. Or, the browser freezes when trying to reconnect to a previously-connected management server.
The following message may be displayed on the management server or the Java console screen of the monitor node.
FJSVwvbs:OutOfMemoryError
When trying to access the management server from browser, message 0005 appears and the top menu is not displayed, or the message itself may not appear.
Web-Based Admin View stopped operating after changing the IP address of the public LAN.
When using the PRIMECLUSTER Operation Management View, existing cluster nodes are not displayed on the each product's node list screen.
The screen does not change even after confirming the dialog message.
The following message is displayed on the browser status bar, and top menu is not displayed.
Applet com.fujitsu.webview.base.WebViewMain
error:java.lang.NoClassDefFoundError: com/sun/java/swing/Japplet
Or, the Operation Management View for each product cannot be started.
It takes more than a few minutes before the Web-Based Admin View top menu is displayed. Or, even if it is, it freezes or message "0001 Cannot call Management server" may be displayed.
When using a Java Plug-in on a client browser, and using a mouse on the Web-Based Admin View top menu or Operation Management View for each product, the screen has problems such as displaying small flecks in the area where the mouse has been used.
When starting or restarting the Web-Based Admin View, or rebooting the node, the message "FJSVwvbs:webview.cnf abnormal" or "Node process abnormal end." is displayed, and Web-Based Admin View does not start.
When starting or restarting the Web-Based Admin View, message "WARNING:unrelated 'httpip' property." is displayed.
After installing the manual package, the title menu for the manual is not displayed. Or, even after removing the manual package, the title menu for the manual is still displayed.
When trying to start the menu for products that are the target of management from the Web-Based Admin View top menu, the message "0023 This application must be started at the following URL" is displayed.
Start button for products that are the target of management have disappeared from the Web-Based Admin View top menu.
Even after disconnecting from the management server, messages 0002, 0003 or 0007 are not displayed on the client.
When trying to access the management server from the browser, message 0006 appears, and the top menu is not displayed.
When entering the user ID and the password for authentication, error message 0016 appears, and authentication fails.
Resolution
See "Web-Based Admin View Operation Guide" and follow the troubleshooting procedures.
(2) GDS Management View cannot be started.
Resolution
When GDS is not installed.
Install GDS.
When GDS is installed.
Check for the following possible causes:
Wrong URL specified.
Wrong method caused due to specifying host name.
Environment cannot use Swing.
Different browser type and level than recommended.
(3) Disk device information is not displayed correctly in GDS Management View.
Explanation
GDS does not recognize disks properly. Possible causes are as follows.
The power of the disk unit was turned on after the system was booted.
The disk device became unavailable for some kind of problem during system operation.
The configuration of devices such as mphd and mplb was changed during system operation.
Resolution
Perform the following steps 1. through 2.
Use the format(1M) command and check whether the OS recognizes the disk unit. If it does not recognize, identify the cause based on log messages of disk drivers stored in the /var/adm/messages file and such.
Execute [Update Physical Disk Information] in the [Operation] menu.
(4) Insufficient memory error is displayed at Java console in the environment with a number of SDX objects.
Explanation
The memory of Java VM may become insufficient when using the GDS management view in the environment with a number of SDX objects.
A number of disks are registered in GDS
A number of volumes are created
There are many scope nodes of the shared class
When applying the above-mentioned cases, change the size of the memory allocation pool of Java VM.
Resolution
Estimate the size to be added according to the following description and change the setting of Java VM.
Add 2 MB per 1000 of the value of "(the number of disks + the number of volumes) x the number of scope nodes."
Add 5 MB per 1000 of the value of "(the number of disks + the number of volumes) x the number of scope nodes."
The value less than 1000 is rounded up.
Example
The estimates of the size to be added are as follows.
(500 + 400) x 2 = 1800
The size is 2000, since the value less than 1000 is rounded up.
For the management server
For the management server, 2 MB is added per 1000. Based on the calculation formula 2000 / 1000 x 2, add 4 MB.
For clients
For clients, 5 MB is added per 1000. Based on the calculating formula 2000 / 1000 x 5, add 10 MB.
Based on the above-mentioned estimates, change the setting of Java VM.
Display the shell prompt with the root administration.
Check the current setting value with the wvGetparam command.
# /etc/opt/FJSVwvbs/etc/bin/wvGetparam s-java-option
sys:s-java-option -mx128m |
Add the calculated value (4 MB) to the confirmed result and set it with the wvSetparam command.
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam s-java-option -mx132m
sys:s-java-option -mx132m |
Check that no client is connected and restart the management server.
# /etc/opt/FJSVwvbs/etc/bin/wvCntl restart |
Select [Java] from [Control Panel] of the [Start] menu and click it to display [Java Control Panel].
Select the [Java] tab from [Java Control Panel] and click the <View> button to display the [Java Runtime Environment Settings] screen.
Select the value of [Runtime Parameters] and add it to the calculated value (10 MB), and then set the total value.
If the default value is -Xmx80m, set -Xmx90m.
If the default value is not set, assuming that the default value is -Xmx64m, add the calculated value.
Click the <OK> button of the [Java Runtime Environment Settings] screen.
Click the <OK> button of [Java Control Panel].
The setting works from the session which uses browsers started after performing the above-mentioned procedures.
