can't open the kvm


1.Use a third-party tool (such as PuTTY) to run the telnet IP address:8208 command to check whether the KVM interface is normal. (The default port number is 8208. You can query the port number by checking the VMM port number on the Configuration > Service page of the iMana WebUI or the Service Settings page of the iBMC WebUI.) If the login fails, directly log in to iMana 200 or iBMC from a PC.
2.Clear all browsers and Java cache, and close all the browsers. Then re-log in to iMana 200 or iBMC.
3.Adjust the Java security level to medium or lower, or add the KVM address to the Java exception sites.
4.Check the operating system (OS), Java, and browser versions on the client. Firefox 23.0 is recommended. For details about the operating environment requirements, see the iMana 200 or iBMC Help.

Other related questions:
Unavailability of the KVM
The browser or Java version does not meet requirements. For details about version requirements, see the iBMC user guide or iMana user guide of your server model.

Why cannot an AR router send trap messages

SNMP provides the trap function to control the output of trap messages. An AR router generates trap messages only when the trap function has been enabled on the AR router.

Perform the following operations to enable the trap function on an AR router:

  1. Run the system-view command to enter the system view.
  2. Run the snmp-agent trap enable command to enable the AR router to send trap messages to the NMS.
  3. Run the snmp-agent target-host trap-paramsname paramsname v1 securityname securityname [ binding-private-value ] [ trap-filterprofilename filterprofilename ] [ private-netmanager ] command to set parameters for sending trap messages.
    • V200R001C01 and later versions support binding-private-value.
    • V200R002C00 and later versions support private-netmanager.
  4. Run the snmp-agent target-host trap-hostname hostname address ipv4-addr [ udp-port udp-portid ] [ public-net | vpn-instance vpn-instance-name ] trap-paramsname paramsname command to specify the destination host for receiving trap messages and error codes.

    The default destination UDP port number is 162. To ensure secure communication between the NMS and managed devices, run the udp-port command to change the UDP port number to a non-well-known port number.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top