Cisco Cisco UCS B230 M2 Blade Server Guia De Resolução De Problemas

If you are able to ping the KVM IP address, but still not able to connect to the KVM, you may have a
duplicate IP address in the network. One way to verify this is to statically assign a new IP address that
you know is not in use to the blade. If the host can be taken down, decommission the blade in
question and then try to ping the KVM IP address again. If it is still successful, that IP is duplicated in
the network. Remove the IP from the other device, or adjust the UCS MGMT IP Pool to not include
that address.

5. 

Verify that the proper Java version is installed. The UCS Manager web page lists the requirements
and links for tested java versions.

1. 

Monitor and collect Java logs from the Java Control Panel when you launch KVM. Click Start >
Enter Run > Enter javaws −viewer.

2. 

Clear Java cache  In the Java Control Panel > Click General > Temporary Internet Files > Click
View. It launches a Java Cache Viewer. Delete all the KVM Viewer.

3. 

Does the standalone KVM launcher work? You can bypass the KVM launcher and UCS Manager
with the kvm.zip.

First, you must create an Intelligent Platform Management Interface (IPMI) policy/user and
add this to the affected blades service profile (this is under policies).

a. 

Go to http://<ucs manager ip address>/kvm.zip to download the kvm.zip file.

b. 

Unzip and run the launchkvm.bat file. It then prompts you for an IP address of the server
(KVM address found in UCS Manager), and the IPMI user name and password you
configured.

c. 

4.