F.1.6 GDS Management View Abnormality

PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System)

F.1.6 GDS Management View Abnormality

In this section, how to resolve problems related to Web-Based Admin View and GDS Management View is explained.

For problems described in (1) to (18), see "Web-Based Admin View Operation Guide" and follow the troubleshooting procedures.

(1) 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.

(2) 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.

(3) The following message may be displayed on the management server or the Java console screen of the monitor node.
FJSVwvbs:OutOfMemoryError

(4) 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.

(5) Web-Based Admin View stopped operating after changing the IP address of the public LAN.

(6) When using the PRIMECLUSTER Operation Management View, existing cluster nodes are not displayed on the each product's node list screen.

(7) The screen does not change even after confirming the dialog message.

(8) 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 can not be started.

(9) 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.

(10) 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.

(11) When starting or restarting the Web-Based Admin View, or rebooting the node, the message "FJSVwvbs:webview.cnf abnormal" or "Node process abnormal end." are displayed, and Web-Based Admin View does not start.

(12) When starting or restarting the Web-Based Admin View, message "WARNING:unrelated 'httpip' property." is displayed.

(13) 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.

(14) 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.

(15) Start button for products that are the target of management have disappeared from the Web-Based Admin View top menu.

(16) Even after disconnecting from the management server, messages 0002, 0003 or 0007 are not displayed on the client.

(17) When trying to access the management server from the browser, message 0006 appears, and the top menu is not displayed.

(18) When entering the user ID and the password for authentication, error message 0016 appears, and authentication fails.

(19) GDS Management View cannot be started.

[Resolution]

a. When GDS is not installed.

Install GDS.

b. 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.

(20) Disk information such as mphd and mplb is not displayed on GDS Management View. Or, the disk sizes for disk units are not displayed correctly.

[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 configuration of devices such as mphd and mplb was changed during system operation.
The disk unit became unavailable for some kind of problem 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.

Contents