IMC 5: Error occurred when accessing the MIB on device


This error can be viewed in IMC when the software is not able to get any data using SNMP. This error does NOT mean that your SNMP credentials are wrong. It simply means that server is not able to receive any data using SNMP. Things you can check are:

  1. Can you ping the device from server
  2. If you can ping, then verify your SNMP credentials. Recheck again.
  3. You can use an awesome tool called “SNMP Tester” by Paessler from here. Use this tool to check if you can communicate using SNMP from your server to the device. (To keep it simple, use “Read Device Uptime” under “Select Request Type” in SNMP Tester and put your credentials).
  4. If you get an Error message while testing using SNMP Tester, it should give you good idea where you are going wrong.
  5. If you get error “Value: No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003)” then 
a.       Check the firewall rules, in case if you have a firewall in the path
b.     You are possible getting a reply from different interface of the device than the one on which you are sending the request. (You can verify this using Wireshark).

In this case, make sure that the device will send the SNMP packets from a dedicated interface only.

In case you have HP E-series switch (like 8200 or 5400), you can issue command: 

core-swtich# snmp-server response-source <source-ip>

Comments

Post a Comment

Popular posts from this blog

Show tech command in H3C

Normally we use " show tech " (show tech-support) command to gather ALL the information from a switch or a router. This applies to all Cisco networking devices as well as HP Procurve switches (I don't know about other vendors). The show tech command in H3C is display diagnostic-information . It does exactly the same thing as show tech, except that it will ask you if you want to save the output in a file [(inside flash), so that you can copy it using tftp], or display it on screen (as usual).
Read more

Telnet failed: Can't send after socket shutdown

Telnet failed: Can't send after socket shutdown. If you are getting this error on HP Procurve switch, it means that the Procurve switch is not accepting telnet sessions. A common reason for this is that you might have enabled SSH (and disabled telnet), or telnet on the swtich is not enabled at all (by default, telnet is disabled on Procurve switches). Telnet can be enabled on a Procurve switch as follows: Procurve-Switch (config)# telnet-server Thats it. Now you should be able to telnet your Procurve switch. Note: If you are in a different vlan than the management IP address of the switch, you need to set the correct default-gateway on the switch (only for edge switches).
Read more

3Com switches Password Recovery procedure

Use the password recovery method outlined below to define a new password for the admin username:  (This method works for most of the 3-Com switches) 1. Access the Command Line Interface and enter the user name "recover" and password "recover" to place your unit in password recovery mode. The unit will remain in password recovery mode for a maximum of 30 seconds, before it returns to the CLI login prompt.  2. During these 30 seconds, perform a hard reboot on the unit while it is still in password recovery mode by turning it off, waiting for a few seconds, and then switching it on again.  3. When the unit has rebooted following the hard reboot enter a new password for the "admin" user account.  4. Enter enable to leave password recovery enabled (to enable recovery of the password next time if you forget), or enter disable to turn it off (not recommended). You are now logged in as the default "admin" user. 
Read more