17.2.4 Troubleshooting problems related to logging on to PFM - Web Console
- Organization of this subsection
(1) The specified Performance Management user name is not recognized during logon.
A specified Performance Management user account might not exist. Use the user name ADMINISTRATOR to log on to PFM - Web Console from the monitoring console, and then use the Users window to confirm whether a Performance Management user account has been created. If no Performance Management user account has been created, create one now.
If the user name that failed for logon was a business group user name, the business group might not be assigned to the user. Use the user name ADMINISTRATOR to log on to PFM - Web Console from the monitoring console, and then use the Users window to check whether the business group has been assigned to the user. If no business group has been assigned, assign one now.
For details on how to create Performance Management user accounts and assign business groups, see 2. Managing User Accounts and Business Groups.
(2) A connection from PFM - Web Console to PFM - Manager (View Server service) cannot be established.
Possible causes and solutions:
-
There is an error in the host name or port number specified in the Windows initialization file (config.xml).
Confirm whether the host name and port number are correct. Correct any incorrect settings, restart PFM - Web Console, and then re-execute the operation.
-
The View Server service has not been initialized.
The services or processes required to start the View Server service might not have been started. Wait a moment and then re-execute the operation.
-
The PFM - Manager host is using an IP address that does not enable a connection from the PFM - Web Console host.
When multiple IP addresses are set for the PFM - Manager host or an IP address translation (such as NAT) is performed between PFM - Manager and PFM - Web Console, a connection might not be established. In this case, the host name must be for with PFM - Manager. For details on how to set host names, see the list of port numbers in an appendix of the manual JP1/Performance Management Reference.
-
PFM - Web Console is connected to a PFM - Manager that has a function enabled on it that PFM - Web Console does not support.
If the version of the connected PFM - Manager is newer than that of PFM - Web Console, check that there are no functions enabled on the PFM - Manager that are not supported by PFM - Web Console.
If such a function is enabled, disable the function or consider upgrading the PFM - Web Consoler to a newer version.
The following table lists the corresponding functionality and PFM - Web Console versions that support the functionality.
Functionality
Supported in
Functionality for binding multiple alarm tables
PFM - Web Console 09-00 or later
Functionality for controlling access using business groups
PFM - Web Console 10-00 or later
Monitoring suspension function
PFM - Web Console 10-50 or later
(3) The login window is not displayed in the web browser
Possible causes and solutions:
-
The URL is invalid.
If encrypted communication is enabled, specify a URL that begins with https.
If encrypted communication is not enabled, specify a URL that begins with http.
-
If encrypted communication is enabled, web browser settings are invalid.
Enable TLS communication in the web browser settings.
For details on how to enable TLS communication when Internet Explorer is used as the web browser, see the description about how to configure a web browser to use the monitoring console in the JP1/Performance Management Planning and Configuration Guide.
When Google Chrome is used as the web browser, you can enable TLS communication by following the same procedure described above for Internet Explorer. When you use Firefox as the web browser, TLS communication is always enabled.
(4) A security warning window is displayed in the web browser
If encrypted communication is enabled, a security warning window is displayed according to the specified certificates.
The following are possible causes and examples of corrective actions and warning messages:
-
The root certificate has not been imported into the web browser or the wrong root certificate has been imported.
Import the root certificate issued by the certificate authority from which you acquired the server certificate.
A warning message such as the following is displayed in the window:
-
Internet Explorer
The security certificate on this Web site was not issued by a trusted certificate authority
-
Firefox
The certificate is not trusted because no issuer chain was provided or The certificate does not come from a trusted source
-
Google Chrome
Your connection is not private
Attackers might be tring to steal your information from name-of-host-on-which-PFM-Web-Console(+domain-name)-in-URL (for example, password, messages, or credit cards).
NET::ERR_CERT_COMMON_NAME_INVALID
-
-
The server certificate stored in the folder for storing encrypted communication files on PFM - Web Console has expired.
Renew the server certificate and update the settings. For details, see the section on changing the settings for encrypted communication between a web browser and the monitoring console server in the JP1/Performance Management Planning and Configuration Guide.
A warning message such as the following is displayed in the window:
-
Internet Explorer
The security certificate on this Web page has either expired or is invalid
-
Firefox
The certificate expired on (date)
-
Google Chrome
Your connection is not private
Attackers might be tring to steal your information from name-of-host-on-which-PFM-Web-Console(+domain-name)-in-URL (for example, password, messages, or credit cards).
NET::ERR_CERT_DATE_INVALID
-
-
The host name (Common Name) specified in the server certificate does not match the host name of the URL in the login window.
Make sure that the host name (Common Name) specified in the server certificate matches the host name of the URL in the login window. If a host name in FQDN format is specified in Common Name, the URL in the login window must also be in the format host-name + domain-name.
You can use the jpcwtool https output certtext command to check the host name (Common Name) specified in the server certificate. For details about the command, see the section that describes the command in the manual JP1/Performance Management Reference.
A warning message such as the following is displayed in the window:
-
Internet Explorer
The security certificate on this Web site was issued for the address of another Web site.
-
Firefox
This certificate is valid only for the host name (Common Name) that is configured in the server certificate.
-
Google Chrome
Your connection is not private
Attackers might be tring to steal your information from name-of-host-on-which-PFM-Web-Console(+domain-name)-in-URL (for example, password, messages, or credit cards).
NET::ERR_CERT_COMMON_NAME_INVALID
-
-
The server certificate lacks a definition.
The server certificate lacks the Subject Alternative Name (SAN) definition. Get a server certificate with the SAN definition added to it, and then install it on the Web browser.
You can use the jpcwtool https output certtext command to check Common Name and SAN specified in the server certificate. For details about the command, see the section that describes the command in the manual JP1/Performance Management Reference.
On the other hand, the jpcwtool https output certtext command does not output SANs. You therefore have to create a server certificate by using OpenSSL or other tools capable of creating a certificate signing request with a SAN definition added to it. When you create a server certificate, you have to not only specify the entries that need to be set in the jpcwtool https output certtext command but also set a SAN as the Common Name (CN).
-
Internet Explorer, Firefox
This phenomenon does not occur.
-
Google Chrome
Your connection is not private
Attackers might be tring to steal your information from name-of-host-on-which-PFM-Web-Console(+domain-name)-in-URL (for example, password, messages, or credit cards).
NET::ERR_CERT_COMMON_NAME_INVALID
Detailed information
This server could not prove that it is name-of-host-on-which-PFM-Web-Console(+domain-name)-in-URL; its security certificate does not specify Subject Alternative Names. This may be caused by a misconfiguration or an attacker intercepting your connection.
-