| PRIMECLUSTER Web-Based Admin View Operation Guide |
|
Contents
Index
|
| Appendix B Troubleshooting |
This section explains the actions to be taken in the event of a Web-Based Admin View failure.
Be sure to check "Symptom 1" before working on each problem.
|
Symptom No |
Content of Symptom |
|---|---|
|
The Web-Based Admin View screen cannot be started. Even though it was started, the screen is not displayed properly, or a dialog message from 0001-0005 appears. |
|
|
The screen is not switched when clicking the confirmation button for 0003 or 0007 dialog message. The browser is hung up when attempting to reconnect to the management server that was previously connected. |
|
|
The message "FJSVwvbs: OutOfMemoryError" may be output to the Java console screen of the management server or monitoring node. |
|
|
When the browser accesses the management server, dialog message 0005 is displayed, and the Web-Based Admin View screen and dialog message are not displayed. |
|
|
When the IP address of the LAN was changed, the operation of Web-Based Admin View was disabled. |
|
|
With the operation management view, the monitoring node cannot be displayed in the node list for each product. |
|
|
The screen is not switched when clicking the confirmation button of dialog message. |
|
|
It takes a few minutes to show the Web-Based Admin View screen. Even the menu is displayed, the client gets hung up, or the dialog message 0001 appears. |
|
|
When a Java Plug-in is used for the client browser, garbage data are jumbled up or the screen display is distorted after accessing the Web-Based Admin View screen or operation management view of each product. |
|
|
The message "FJSVwvbs: webview.cnf abnormal" or "Node process abnormal end" is output when starting up or restarting Web-Based Admin view, or starting up a node. |
|
|
The message "WARNING: unrelated 'httpip' property." is output when the Web-Based Admin View is started or restarted. |
|
|
The manual title is not displayed by manual reference operation after the manual package is installed, or the manual title remains after the package is deleted. |
|
|
The dialog message 0023 is displayed when starting the operation management product from the Web-Based Admin View screen. |
|
|
The start button of the operation management product gets out of the Web-Based Admin View screen. |
|
|
The 0003 or 0007 dialog message may not appear when the management server is disconnected. |
|
|
The 0006 dialog message is displayed, and the Web-Based Admin View screen is not displayed when accessing to the management server from the browser. |
|
|
The server is unable to login with the user ID and password, and the 0016 dialog message is output. |
|
|
"PRIMECLUSTER Global File Services Configuration and Administration Guide" is not displayed in the manual menu. |
|
|
When starting Netscape Navigator or Netscape Communicator, the proper screen is not displayed. (When the user exited the Web browser last, either the upper right [X] button or [Close] on the Window menu.) |
|
|
The cluster node is not displayed, or an access error occurs when the operation management screen is activated for the first time after Web-Based Admin View installation. |
|
|
When reading the URL of Java Plug-in by using Netscape Communicator or Netscape Navigator, the message "Click here to get the plugin" is displayed in the Web browser. |
|
|
When reading the URL of Java Plug-in by using Internet Explorer, the message "Welcome to Web-Based Admin View" is not displayed or the dialog of "Security Warning" (If the Java Plug-in should be installed and executed) is displayed in the Web browser. |
|
|
The Japanese character turns into garbage or is not displayed on a screen. |
|
|
The URL modification and input is not allowed when using Netscape 6.X. |
|
|
The message of 0032 dialog message is displayed in the Web browser when you refer the manual or help. |
|
|
Web-Based Admin View or each operation management view (such as GDS operation management view and GFS operation management view) on Web-Based Admin View becomes unusable in process of the operation, or the connection to the management server is cut in process of the operation. |
|
|
During the displaying of each operation management view (such as GDS operation management view and GFS operation management view), if the hardware of the client machine is reset or the network of the client machine is cut, you will become to not able to login Web-Based Admin View after it is recovered. |
|
|
Monitored nodes might not be displayed on a list of nodes for each product after the network disconnection between the management servers and monitored nodes is recovered. |
|
No |
Corrective action |
|
1 |
Check the followings;
|
|
2 |
Refer to "http port number" and confirm the http port number that is currently set up. |
|
3 |
Check whether Web-Based Admin View is started on the management server. Execute the ps(1) command to check whether the following process is started correctly. [When the monitoring node acts as the management server] /usr/java1.2/bin/../jre/bin/../bin/sparc/native_threads/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs -mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX [When the monitoring node does not act as the management server] wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX If even one process is not running, take actions as described in the following action 7. |
|
4 |
The browser might be hung up depending on the client OS or the browser version. In such a case, restart the browser and retry accessing the management server. |
|
5 |
Refer to the installation guide for the product and make sure all the required packages are correctly installed. |
|
6 |
Check the proxy setting of the browser not using a proxy server. For the proxy setting, refer to "Proxy setting" in "Preparing the Web browser." Both the host name and corresponding IP address must be set not using a proxy server. |
|
7 |
Check mip, httpip, and that for the management server in all nodes. - IP address for identifying own host # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip local:mip xxx.xxx.xxx.xxx - IP address used for the client # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip local:httpip xxx.xxx.xxx.xxx - IP address of the primary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server sys:primary-server xxx.xxx.xxx.xxx - IP address of the secondary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server sys:secondary-server xxx.xxx.xxx.xxx If these parameters are not set up correctly, set correct addresses. Refer to "Network address", or "Management server", and "Multi-network between server and client by classified use." |
|
8 |
Take the following steps to check if Web-Based Admin View supports the Java environment: 1.Defined Java environment # /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home local:java_home <path> 2.Version Use the following version display command to check if the Java environment in the <path> obtained by the command above is available on Web-Based Admin View: # <path>/bin/java -version java version "X.X.X" If the version is "1.2.X," it is available. If other than version "1.2.X" is set up, reset an appropriate Java environment. Refer to "JavaVM run time environment". |
|
9 |
Check if the specified port number has not already been used. Refer to "Network service port number." |
|
10 |
Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes. The following is an example of the webview.cnf file: [Example of /etc/opt/FJSVwvbs/etc/webview.cnf] usr:out-time:0 usr:c-tlog-debug:off usr:locale:japanese usr:look-and-feel:Metal sys:_serialID:XXX.XXX.XXX.XXX@XXXX.XX.XX XX:XX:XX.XXX sys:http-home: sys:s-tlog-debug:on sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar sys:health-time:10 sys:keep-time:10 sys:tophtml-suffix:html sys:httpdif:hme0 sys:n-tlog-debug:on sys:s-llog-vol:100 sys:n-tlog-vol:200 sys:s-tlog-vol:200 sys:acsif:hme0 sys:s-olog-vol:100 sys:s-elog-vol:100 sys:rmi-cmdread-timer:900 sys:n-pending-events:100 sys:retry-time:30 sys:cluster-lib-path:/etc/opt/FJSVcluster/lib sys:cluster-path:/etc/opt/FJSVcluster/bin:/etc/opt/FJSVcluster/sys sys:s-llog-num:2 sys:n-tlog-num:5 sys:s-tlog-num:5 sys:group-addr:XXX.XXX.XXX.XXX sys:s-olog-num:5 sys:s-elog-num:2 sys:rmi-cmdwait-timer:900 sys:server-ha:off sys:secondary-server:XXX.XXX.XXX.XXX sys:primary-server:XXX.XXX.XXX.XXX sys:n-java-option:-mx128m sys:s-java-option:-mx128m The following is an example of the wvlocal.cnf file: [Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf] local:classpath: local:cluster-path: local:cluster-lib-path: local:mip:XXX.XXX.XXX.XXX local:httpip:XXX.XXX.XXX.XXX local:server-election:on local:java_home:/usr/java1.2 local:s-log-path:/var/opt/FJSVwvbs/logs/server local:n-log-path:/var/opt/FJSVwvbs/logs/node If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi). If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset the node specific parameter on all the management servers and monitoring nodes.
|
|
No |
Corrective action |
|
1 |
Enter the URL of the connected management server in the URL field of the browser and switch the screen manually, or restart the browser, and then retry accessing the server. |
|
No |
Corrective action |
|
1 |
Restart Web-Based Admin View on the management server or monitoring node on which the message appeared. Shut down/restart the client Web browser and then reaccess.
For restarting Web-Based Admin View, refer to "Restart." |
|
2 |
1. Stop Web-Based Admin View.
Refer to "Stop." 2. Change a heap size. # /etc/opt/FJSVwvbs/etc/bin/wvSetparam s-java-option -mx<heap-size>m # /etc/opt/FJSVwvbs/etc/bin/wvSetparam n-java-option -mx<heap-size>m <heap-size>: Heap size. The initial value is 128Mbyte. For example,When changing a heap size to 256Mbyte. # /etc/opt/FJSVwvbs/etc/bin/wvSetparam s-java-option -mx256m # /etc/opt/FJSVwvbs/etc/bin/wvSetparam n-java-option -mx256m 3. Restart Web-Based Admin View.
Refer to "Restart." |
|
No |
Corrective action |
|
1 |
If a name is specified as the host name of the management server in the URL field of the browser, designate the IP address used for the client of the management server. If the authentication dialog box is displayed then, the client DNS settings may be incorrect. In that case, follow the procedure shown below: The default value of httpip set to the IP address, which is assigned to the displayed node name as a result of executing "uname -n." If it does not appear, go to Corrective Action 2. - If the client is running Windows(R) 98 Select [Start]-[Settings]-[Control Panel]-[Network]. Select the [TCP/IP properties] from [Configuration], and then select [DNS configuration]. If "Do not use DNS" is selected, go to Corrective Action 3. If "Use DNS" is selected, [Host] and [Domain] should be configured in the DNS and mapped to an IP address by the DNS server. So, you need to set up the mapping in DNS for [Host] and [Domain] to the IP address. - If Windows NT(R) is installed in the client Select [Start]-[Settings]-[Control Panel]-[Network]. Select the [TCP/IP protocol] property from [Protocols], and then select [DNS]. If values are not set for both [Host name] and [Domain], go to Corrective Action 3. If values are specified for [Host name] and [Domain], both should be configured in the DNS and mapped to an IP address by the DNS server. So, you need to set up the mapping in DNS for [Host] and [Domain] to the IP address. - If Windows(R) 2000 is installed in the client Select [Start]-[Settings]-[Control Panel]-[ Network and dialup connection]- [Local area connection]- [Properties]. From the list on the [General] tag, select [Internet protocol (TCP/IP)] and then display [Properties]. If either [Automatically acquire DNS server address] or [Use the next DNS server address] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3. - If Solaris OE or Linux(R) is installed in the client Check if the mapping in DNS is set up for host name. Execute the following command. If 'dns' appears as following, the system might adopt DNS. [Example] # egrep '^hosts:' /etc/nsswitch.conf hosts: files dns In that case, execute the following command, and check if the host name designated in the URL is configured in the DNS. [Example] # nslookup www.fujitsu.co.jp Server: foo.fujitsu.co.jp Adress: XXX.XXX.XXX.XXX Name: www.fujitsu.co.jp Address: XXX.XXX.XXX.XXX If an error is displayed, the DNS setting is incorrect. Report the problem to the network administrator. |
|
2 |
Confirm whether a combination of the host name (local host name) displayed as a result of executing "uname -n" and the IP address is registered either in the "/etc/inet/hosts" file or DNS. If not, you need to register either in the /etc/inet/hosts file or in DNS for host name to be mapped to the IP address. |
|
3 |
Check whether Web-Based Admin View is started on the management server. Execute the ps(1) command to check whether the following process is started correctly. [When the monitoring node acts as the management server] /usr/java1.2/bin/../jre/bin/../bin/sparc/native_threads/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs -mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX [When the monitoring node does not act as the management server] wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX If even one process is not running, take actions as described in the following action 7. |
|
4 |
Check mip, httpip, and that for the management server in all nodes. - IP address for identifying own host # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip local:mip xxx.xxx.xxx.xxx - IP address used for the client # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip local:httpip xxx.xxx.xxx.xxx - IP address of the primary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server sys:primary-server xxx.xxx.xxx.xxx - IP address of the secondary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server sys:secondary-server xxx.xxx.xxx.xxx If these parameters are not set up correctly, set correct addresses. Refer to "Network address", or "Management server", and "Multi-network between server and client by classified use." |
|
5 |
1.Edit and access the following file on the management server: File: /etc/opt/FJSVwvbs/etc/WebView.html Record: < PARAM NAME=Port VALUE="????" > 2.Execute the following command: # /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv_c If the VALUE in 2 is ????, the same as that in 1, go to Corrective action 6. If the VALUE in 2 is nor the same as that in 1, change the RMI port number of fjwv_c, according to "RMI port number." # /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv_c=<RMI port number> The initial value is 9399. After changing the port number, be sure to restart Web-Based Admin View . Refer to "Restart". |
|
6 |
Edit the following file in the management server and retry accessing the management server: File: /etc/opt/FJSVwvbs/etc/WebView.html File: /etc/opt/FJSVwvbs/etc/Plugin.html Record: < PARAM NAME=Initial_wait VALUE="??"> Specify 60 or more in "??". After editing a file, be sure to restart Web-Based Admin View. Refer to "Restart". |
|
7 |
Take the following steps to check if Web-Based Admin View supports the Java environment: 1.Defined Java environment # /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home local:java_home <path> 2.Version Use the following version display command to check if the Java environment in the <path> obtained by the command above is available on Web-Based Admin View: # <path>/bin/java -version java version "X.X.X" If the version is "1.2.X," it is available. If other than version "1.2.X" is set up, reset an appropriate Java environment. Refer to "JavaVM run time environment". |
|
8 |
Check if the specified port number has not already been used. Refer to "Network service port number." |
|
9 |
Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes. The following is an example of the webview.cnf file: [Example of /etc/opt/FJSVwvbs/etc/webview.cnf] usr:out-time:0 usr:c-tlog-debug:off usr:locale:japanese usr:look-and-feel:Metal sys:_serialID:XXX.XXX.XXX.XXX@XXXX.XX.XX XX:XX:XX.XXX sys:http-home: sys:s-tlog-debug:on sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar sys:health-time:10 sys:keep-time:10 sys:tophtml-suffix:html sys:httpdif:hme0 sys:n-tlog-debug:on sys:s-llog-vol:100 sys:n-tlog-vol:200 sys:s-tlog-vol:200 sys:acsif:hme0 sys:s-olog-vol:100 sys:s-elog-vol:100 sys:rmi-cmdread-timer:900 sys:n-pending-events:100 sys:retry-time:30 sys:cluster-lib-path:/etc/opt/FJSVcluster/lib sys:cluster-path:/etc/opt/FJSVcluster/bin:/etc/opt/FJSVcluster/sys sys:s-llog-num:2 sys:n-tlog-num:5 sys:s-tlog-num:5 sys:group-addr:XXX.XXX.XXX.XXX sys:s-olog-num:5 sys:s-elog-num:2 sys:rmi-cmdwait-timer:900 sys:server-ha:off sys:secondary-server:XXX.XXX.XXX.XXX sys:primary-server:XXX.XXX.XXX.XXX sys:n-java-option:-mx128m sys:s-java-option:-mx128m The following is an example of the wvlocal.cnf file: [Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf] local:classpath: local:cluster-path: local:cluster-lib-path: local:mip:XXX.XXX.XXX.XXX local:httpip:XXX.XXX.XXX.XXX local:server-election:on local:java_home:/usr/java1.2 local:s-log-path:/var/opt/FJSVwvbs/logs/server local:n-log-path:/var/opt/FJSVwvbs/logs/node If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi). If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset the node specific parameter on all the management servers and monitoring nodes.
|
|
No |
Corrective action |
|
1 |
Change the network address used for Web-Based Admin View in accordance with "Network address." Then, reset the IP address available to management server setup and the clients, Refer to "Management server" and "Multi-network between server and client by classified use". |
|
No |
Corrective action |
|
1 |
Follow the Corrective Action of Symptom 5, and then, restart Web-Based View in accordance with "Restart". |
|
No |
Corrective action |
|
1 |
When the picture on the right of the Web-Based Admin View screen is red, the hidden message dialog behind other windows might appear by clicking it. In order to recognize such a hidden dialog, show the picture on the display at all time. |
|
No |
Corrective action |
|
1 |
Set up longer time than the existing [Connection monitoring time between client and server] in the system environment. |
|
2 |
If a name is specified as the host name of the management server in the URL field of the browser, designate the IP address used for the client of the management server. If the authentication dialog box is displayed then, the client DNS settings may be incorrect. In that case, follow the procedure shown below: The default value of httpip set to the IP address, which is assigned to the displayed node name as a result of executing "uname -n." If it does not appear, go to Corrective Action 2. - If the client is running Windows(R) 98 Select [Start]-[Settings]-[Control Panel]-[Network]. Select the [TCP/IP properties] from [Configuration], and then select [DNS configuration]. If "Do not use DNS" is selected, go to Corrective Action 3. If "Use DNS" is selected, [Host] and [Domain] should be configured in the DNS and mapped to an IP address by the DNS server. So, you need to set up the mapping in DNS for [Host] and [Domain] to the IP address. - If Windows NT(R) is installed in the client Select [Start]-[Settings]-[Control Panel]-[Network]. Select the [TCP/IP protocol] property from [Protocols], and then select [DNS]. If values are not set for both [Host name] and [Domain], go to Corrective Action 3. If values are specified for [Host name] and [Domain], both should be configured in the DNS and mapped to an IP address by the DNS server. So, you need to set up the mapping in DNS for [Host] and [Domain] to the IP address. - If Windows(R) 2000 is installed in the client Select [Start]-[Settings]-[Control Panel]-[ Network and dialup connection]- [Local area connection]- [Properties]. From the list on the [General] tag, select [Internet protocol (TCP/IP)] and then display [Properties]. If either [Automatically acquire DNS server address] or [Use the next DNS server address] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3. - If Solaris OE or Linux(R) is installed in the client Check if the mapping in DNS is set up for host name. Execute the following command. If 'dns' appears as following, the system might adopt DNS. [Example] # egrep '^hosts:' /etc/nsswitch.conf hosts: files dns In that case, execute the following command, and check if the host name designated in the URL is configured in the DNS. [Example] # nslookup www.fujitsu.co.jp Server: foo.fujitsu.co.jp Adress: XXX.XXX.XXX.XXX Name: www.fujitsu.co.jp Address: XXX.XXX.XXX.XXX If an error is displayed, the DNS setting is incorrect. Report the problem to the network administrator. |
|
3 |
Confirm whether a combination of the host name (local host name) displayed as a result of executing "uname -n" and the IP address is registered either in the "/etc/inet/hosts" file or DNS. If not, you need to register either in the /etc/inet/hosts file or in DNS for host name to be mapped to the IP address. |
|
4 |
Check whether Web-Based Admin View is started on the management server. Execute the ps(1) command to check whether the following process is started correctly. [When the monitoring node acts as the management server] /usr/java1.2/bin/../jre/bin/../bin/sparc/native_threads/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs -mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX [When the monitoring node does not act as the management server] wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX If even one process is not running, take actions as described in Corrective action 5 or Corrective action8. |
|
5 |
Check mip, httpip, and that for the management server in all nodes. - IP address for identifying own host # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip local:mip xxx.xxx.xxx.xxx - IP address used for the client # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip local:httpip xxx.xxx.xxx.xxx - IP address of the primary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server sys:primary-server xxx.xxx.xxx.xxx - IP address of the secondary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server sys:secondary-server xxx.xxx.xxx.xxx If these parameters are not set up correctly, set correct addresses. Refer to "Network address", or "Management server", and "Multi-network between server and client by classified use." |
|
6 |
1.Edit and access the following file on the management server: File: /etc/opt/FJSVwvbs/etc/WebView.html Record: < PARAM NAME=Port VALUE="????" > 2.Execute the following command: # /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv_c If the VALUE in 2 is ????, the same as that in 1, go to Corrective action 6. If the VALUE in 2 is nor the same as that in 1, change the RMI port number of fjwv_c, according to "RMI port number." # /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv_c=<RMI port number> The initial value is 9399. After changing the port number, be sure to restart Web-Based Admin View . Refer to "Restart". |
|
7 |
Edit the following file in the management server and retry accessing the management server: File: /etc/opt/FJSVwvbs/etc/WebView.html File: /etc/opt/FJSVwvbs/etc/Plugin.html Record: < PARAM NAME=Initial_wait VALUE="??"> Specify 60 or more in "??". After editing a file, be sure to restart Web-Based Admin View. Refer to "Restart". |
|
8 |
Take the following steps to check if Web-Based Admin View supports the Java environment: 1.Defined Java environment # /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home local:java_home <path> 2.Version Use the following version display command to check if the Java environment in the <path> obtained by the command above is available on Web-Based Admin View: # <path>/bin/java -version java version "X.X.X" If the version is "1.2.X," it is available. If other than version "1.2.X" is set up, reset an appropriate Java environment. Refer to "JavaVM run time environment". |
|
9 |
Check if the specified port number has not already been used. Refer to "Network service port number." |
|
10 |
Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes. The following is an example of the webview.cnf file: [Example of /etc/opt/FJSVwvbs/etc/webview.cnf] usr:out-time:0 usr:c-tlog-debug:off usr:locale:japanese usr:look-and-feel:Metal sys:_serialID:XXX.XXX.XXX.XXX@XXXX.XX.XX XX:XX:XX.XXX sys:http-home: sys:s-tlog-debug:on sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar sys:health-time:10 sys:keep-time:10 sys:tophtml-suffix:html sys:httpdif:hme0 sys:n-tlog-debug:on sys:s-llog-vol:100 sys:n-tlog-vol:200 sys:s-tlog-vol:200 sys:acsif:hme0 sys:s-olog-vol:100 sys:s-elog-vol:100 sys:rmi-cmdread-timer:900 sys:n-pending-events:100 sys:retry-time:30 sys:cluster-lib-path:/etc/opt/FJSVcluster/lib sys:cluster-path:/etc/opt/FJSVcluster/bin:/etc/opt/FJSVcluster/sys sys:s-llog-num:2 sys:n-tlog-num:5 sys:s-tlog-num:5 sys:group-addr:XXX.XXX.XXX.XXX sys:s-olog-num:5 sys:s-elog-num:2 sys:rmi-cmdwait-timer:900 sys:server-ha:off sys:secondary-server:XXX.XXX.XXX.XXX sys:primary-server:XXX.XXX.XXX.XXX sys:n-java-option:-mx128m sys:s-java-option:-mx128m The following is an example of the wvlocal.cnf file: [Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf] local:classpath: local:cluster-path: local:cluster-lib-path: local:mip:XXX.XXX.XXX.XXX local:httpip:XXX.XXX.XXX.XXX local:server-election:on local:java_home:/usr/java1.2 local:s-log-path:/var/opt/FJSVwvbs/logs/server local:n-log-path:/var/opt/FJSVwvbs/logs/node If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi). If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset the node specific parameter on all the management servers and monitoring nodes.
|
|
No |
Corrective action |
|
1 |
The graphics hardware of the client might be failed. Modify the operation method (see below) or update the graphics driver. If the problem is not solved, contact your local Customer Support. [For Windows(R) 98 and For Windows(R) Me]
[For Windows(R) 2000]
[For Windows(R) XP]
[For Windows NT(R)] Modification is not available.
|
|
No |
Corrective action |
|
1 |
Take the following steps to check if Web-Based Admin View supports the Java environment: 1.Defined Java environment # /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home local:java_home <path> 2.Version Use the following version display command to check if the Java environment in the <path> obtained by the command above is available on Web-Based Admin View: # <path>/bin/java -version java version "X.X.X" If the version is "1.2.X," it is available. If other than version "1.2.X" is set up, reset an appropriate Java environment. Refer to "JavaVM run time environment". |
|
2 |
Check whether Web-Based Admin View is started on the management server. Execute the ps(1) command to check whether the following process is started correctly. [When the monitoring node acts as the management server] /usr/java1.2/bin/../jre/bin/../bin/sparc/native_threads/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs -mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX [When the monitoring node does not act as the management server] wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX If even one process is not running, take actions as described in the following action 3. |
|
3 |
Check mip, httpip, and that for the management server in all nodes. - IP address for identifying own host # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip local:mip xxx.xxx.xxx.xxx - IP address used for the client # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip local:httpip xxx.xxx.xxx.xxx - IP address of the primary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server sys:primary-server xxx.xxx.xxx.xxx - IP address of the secondary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server sys:secondary-server xxx.xxx.xxx.xxx If these parameters are not set up correctly, set correct addresses. Refer to "Network address", or "Management server", and "Multi-network between server and client by classified use." |
|
4 |
Check if the specified port number has not already been used. Refer to "Network service port number." |
|
5 |
Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes. The following is an example of the webview.cnf file: [Example of /etc/opt/FJSVwvbs/etc/webview.cnf] usr:out-time:0 usr:c-tlog-debug:off usr:locale:japanese usr:look-and-feel:Metal sys:_serialID:XXX.XXX.XXX.XXX@XXXX.XX.XX XX:XX:XX.XXX sys:http-home: sys:s-tlog-debug:on sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar sys:health-time:10 sys:keep-time:10 sys:tophtml-suffix:html sys:httpdif:hme0 sys:n-tlog-debug:on sys:s-llog-vol:100 sys:n-tlog-vol:200 sys:s-tlog-vol:200 sys:acsif:hme0 sys:s-olog-vol:100 sys:s-elog-vol:100 sys:rmi-cmdread-timer:900 sys:n-pending-events:100 sys:retry-time:30 sys:cluster-lib-path:/etc/opt/FJSVcluster/lib sys:cluster-path:/etc/opt/FJSVcluster/bin:/etc/opt/FJSVcluster/sys sys:s-llog-num:2 sys:n-tlog-num:5 sys:s-tlog-num:5 sys:group-addr:XXX.XXX.XXX.XXX sys:s-olog-num:5 sys:s-elog-num:2 sys:rmi-cmdwait-timer:900 sys:server-ha:off sys:secondary-server:XXX.XXX.XXX.XXX sys:primary-server:XXX.XXX.XXX.XXX sys:n-java-option:-mx128m sys:s-java-option:-mx128m The following is an example of the wvlocal.cnf file: [Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf] local:classpath: local:cluster-path: local:cluster-lib-path: local:mip:XXX.XXX.XXX.XXX local:httpip:XXX.XXX.XXX.XXX local:server-election:on local:java_home:/usr/java1.2 local:s-log-path:/var/opt/FJSVwvbs/logs/server local:n-log-path:/var/opt/FJSVwvbs/logs/node If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi). If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset the node specific parameter on all the management servers and monitoring nodes.
|
|
No |
Corrective action |
|
1 |
Confirm if the IP address of the open network is correctly set up in the management server. Refer to "Multi-network between server and client by classified use." |
|
No |
Corrective action |
|
1 |
The installation or deletion of the manual contents while Web-Based Admin View is active will not take effect. You need to restart to make it valid. Refer to "Restart" . Restart the Web-Based Admin View, and then retry accessing from the client. |
|
No |
Corrective action |
|
1 |
Since the access method may vary depending on the operation management product, recheck by referring to the manual of operation management products. In case of the concurrent use of operation management products with different access methods, refer to "Concurrent use of operation management products with different access methods". |
|
No |
Corrective action |
|
1 |
If the incorrect access method is applied to start an optional operation management product, the system might show the 0022 dialog message, and then automatically re-access by a correct access method. In such a case, the Web-Based Admin View screen that was displayed by the first incorrect method is exited. If you need to display this first Web-Based Admin View screen again, start the Web browser and access on the screen. For details refer to "Concurrent use of operation management products with different access methods". |
|
No |
Corrective action |
|
1 |
Restart the browser and retry accessing the management server |
|
No |
Corrective action |
|
1 |
Check whether Web-Based Admin View is started on the management server. Execute the ps(1) command to check whether the following process is started correctly. [When the monitoring node acts as the management server] /usr/java1.2/bin/../jre/bin/../bin/sparc/native_threads/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs -mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX [When the monitoring node does not act as the management server] wvAgent /opt/FJSVwvbs wvAgent /opt/FJSVwvbs /opt/FJSVwvcnf/bin/wvcnfd -b XXX.XXX.XXX.XXX -p XXXX If even one process is not running, take actions as described in the following action 2. |
|
2 |
Check mip, httpip, and that for the management server in all nodes. - IP address for identifying own host # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip local:mip xxx.xxx.xxx.xxx - IP address used for the client # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip local:httpip xxx.xxx.xxx.xxx - IP address of the primary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server sys:primary-server xxx.xxx.xxx.xxx - IP address of the secondary management server # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server sys:secondary-server xxx.xxx.xxx.xxx If these parameters are not set up correctly, set correct addresses. Refer to "Network address", or "Management server", and "Multi-network between server and client by classified use." |
|
3 |
Take the following steps to check if Web-Based Admin View supports the Java environment: 1.Defined Java environment # /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home local:java_home <path> 2.Version Use the following version display command to check if the Java environment in the <path> obtained by the command above is available on Web-Based Admin View: # <path>/bin/java -version java version "X.X.X" If the version is "1.2.X," it is available. If other than version "1.2.X" is set up, reset an appropriate Java environment. Refer to "JavaVM run time environment". |
|
4 |
Check if the specified port number has not already been used. Refer to "Network service port number." |
|
5 |
Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes. The following is an example of the webview.cnf file: [Example of /etc/opt/FJSVwvbs/etc/webview.cnf] usr:out-time:0 usr:c-tlog-debug:off usr:locale:japanese usr:look-and-feel:Metal sys:_serialID:XXX.XXX.XXX.XXX@XXXX.XX.XX XX:XX:XX.XXX sys:http-home: sys:s-tlog-debug:on sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar sys:health-time:10 sys:keep-time:10 sys:tophtml-suffix:html sys:httpdif:hme0 sys:n-tlog-debug:on sys:s-llog-vol:100 sys:n-tlog-vol:200 sys:s-tlog-vol:200 sys:acsif:hme0 sys:s-olog-vol:100 sys:s-elog-vol:100 sys:rmi-cmdread-timer:900 sys:n-pending-events:100 sys:retry-time:30 sys:cluster-lib-path:/etc/opt/FJSVcluster/lib sys:cluster-path:/etc/opt/FJSVcluster/bin:/etc/opt/FJSVcluster/sys sys:s-llog-num:2 sys:n-tlog-num:5 sys:s-tlog-num:5 sys:group-addr:XXX.XXX.XXX.XXX sys:s-olog-num:5 sys:s-elog-num:2 sys:rmi-cmdwait-timer:900 sys:server-ha:off sys:secondary-server:XXX.XXX.XXX.XXX sys:primary-server:XXX.XXX.XXX.XXX sys:n-java-option:-mx128m sys:s-java-option:-mx128m The following is an example of the wvlocal.cnf file: [Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf] local:classpath: local:cluster-path: local:cluster-lib-path: local:mip:XXX.XXX.XXX.XXX local:httpip:XXX.XXX.XXX.XXX local:server-election:on local:java_home:/usr/java1.2 local:s-log-path:/var/opt/FJSVwvbs/logs/server local:n-log-path:/var/opt/FJSVwvbs/logs/node If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi). If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset the node specific parameter on all the management servers and monitoring nodes.
|
|
No |
Corrective action |
|
1 |
Check if the user ID and password provided are correctly registered. |
|
2 |
If no password is assigned for the user ID, set the password. |
|
3 |
The password might have been entered wrong several times in a row. Check the environment setup variable for authentication (login-retry). For details, refer to "Authentication environment setup." |
|
4 |
If you continue to login, follow the corrective action 4 below. |
|
5 |
If the problem is not improved, reconnect from a client after restarting the management server of Web-Based Admin View. Refer to "Restart." |
|
No |
Corrective action |
|
1 |
The English and Japanese versions of "PRIMECLUSTER Global Disk Services Configuration and Administration Guide" cannot be displayed at the same time. Reinstall the manual package of GFS. Refer to "Common menu functions". |
|
No |
Corrective action |
|
1 |
Note that different actions have to be taken depending on the type of client OS. [In case of Windows NT(R) 4.0, Windows(R) 2000, Windows(R) Me, or Windows(R) XP] 1.Press the <Ctrl> + <Alt> + <Delete> keys at the same time to launch the "task manager." 2.Select the "Process" tab, and then select netscape.exe. 3.Right-click, and then select the "end process" menu. Enter "Yes" in the dialog. 4.Exit from every instance of netscape.exe. 5.Start the Web browser. [In case of Windows(R) 98] 1.Press the <Ctrl> + <Alt> + <Delete> keys at the same time to open the "Close Program" screen. 2.Select Netscape from the list box , and then click the "End" button. 3.Exit from every instance of Netscape. 4.Start the Web browser. [In case of Solaris OE] 1.Check the process ID of java_vm_native. # ps -ef | grep java_vm_native 2.Stop the process of java_vm_native by force. # kill -9 <java_vm_native process ID> <java_vm_native process ID>: Process ID acquired at No.1 3.Check the process ID of the netscape process. # ps -ef | grep netscape 4.Stop the process of Netscape by force. # kill -9 <Netscape process ID> <Netscape process ID>:Process ID acquired at No.3 5.Start the Web browser. [In case of Linux(R)] 1.Check the process ID of jre process. # ps -ef | grep IBMJava2-131 2.Terminate the jre process forcibly # kill -9 <jre_process_id> <jre_process_id>: Process ID acquired at No.1 3.Check the Process ID of Netscape process # ps -ef | grep netscape 4.Terminate the Netscape process forcibly # kill -9 <Netscape_process_ id> <Netscape_process_ id >: Process ID acquired at No.3 5.Restart the Web browser. |
|
No |
Corrective action |
|
1 |
Take the following steps to check if the setup for primary and secondary management server is properly done. For your reference, you can see "Primary management server", "Secondary management server". 1.Check the provided [Secondary] information in the upper right of the Web-Based Admin View screen. 2.Take proper actions according to the information. - In case of non-display Check if there's any failure or damage in the secondary management server.
- In case of displaying "Down" Check if there's any failure or damage in the nodes and if the package is correctly installed for each product. If any, take corrective actions. |
|
No |
Corrective action |
|
1 |
Verify the followings; - If the Java Plug-in is installed. - If the supported version is updated. If there is any problem, install Java Plug-in according to "Setting up Java Plug-in" in "Required for the Web Browser Environmen". Note that the dialogue box appears when clicking the icon on "Click here to get the plugin", so select [Cancel]. |
|
No |
Corrective action |
|
1 |
Verify the followings; - If the Java Plug-in is installed. - If the supported version is updated. If there is any problem, install Java Plug-in according to "Setting up Java Plug-in" in "Required for the Web Browser Environmen". Note that the dialogue box appears when clicking the icon on "Click here to get the plugin", so select [Cancel]. |
|
No |
Corrective action |
|
1 |
The client might be used where Japanese environment is not set up. Check the environment , and then use the client with proper environment. For details about the recommended display language on your environment, refer to "Display setup." |
|
No |
Corrective action |
|
1 |
In such a case, resize Netscape by using [Minimize], and then [Restore]. Otherwise, restart the Web browser. Since this problem is due to Netscape, it's under verification. |
|
No |
Corrective action |
|
1 |
Change the settings of the Web browser according to "Preparing the Web browser". |
|
No |
Corrective action |
|
1 |
Check whether the port number which uses in Web-Based Admin View overlaps with one in other products. Check the port numbers which use in Web-Based Admin View. # /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv-h=8081 fjwv_s=9398 fjwv_n=9397 fjwv_c=9399 fjwv_g=9396 If the above port numbers are repeatedly used by other products, refer to "Network service port number " to change them. |
|
No |
Corrective action |
|
1 |
Restart Web-Based Admin View. Refer to "Restart." |
|
No |
Corrective action |
|
1 |
Restart Web-Based Admin View. Refer to "Restart." |
|
Contents
Index
|
