Network Management

 View Only
  • 1.  Error collecting personalized information.

    Posted Jan 27, 2026 04:20 PM

    I'm trying to collect the information from the inserted MIB, but it's only showing an error on the final OID .15. However, in the test, it receives the information normally.
    Can someone help me?
    image
    image


    -------------------------------------------


  • 2.  RE: Error collecting personalized information.

    Posted Jan 28, 2026 02:02 AM

    Hello,

    check the way how custom index is added in the Aruba configuration guide - HPE_iMC_HowTo. In the guide they explain adding a temperature monitoring where adding a customer index in  global indexes is necessary. There are some steps where you should pay special attention to.

    Thank you,

    Best Regards,

    Ivaylo

    -------------------------------------------



  • 3.  RE: Error collecting personalized information.

    Posted Jan 28, 2026 10:36 AM

    Hello, in this case it's not a temperature sensor but a power sensor that can report "0 or 1", as per OID 1.3.6.1.4.1.17095.1.3.15.0 (in the photo). It works in SNMP WALK tests; I configured it similarly to the documentation, but it doesn't work in the tests, showing "Failed to get SNMP index" (as shown in the photos). However, everything else is correct because the other OIDs work, and this same OID (1.3.6.1.4.1.17095.1.3.15.0) works in other applications, including Zabbix. Only in IMC does this OID show this error. Is there an option to "Skip" this test? The MIB is also correct.

    -------------------------------------------



  • 4.  RE: Error collecting personalized information.

    Posted Jan 28, 2026 11:02 AM

    Hello,

    I would recommend opening a case with the TAC if you have a support contract for your iMC.

    -------------------------------------------



  • 5.  RE: Error collecting personalized information.

    Posted Jan 29, 2026 08:15 AM

    Hello,

    The problem is likely that you are using the OID + index. 1.3.6.1.4.1.17095.1.3.15.0 - dot zero at the end in your case is the index, which IMC failed to get because it's now looking for 1.3.6.1.4.1.17095.1.3.15.0.0 1.3.6.1.4.1.17095.1.3.15.0.1, 1.3.6.1.4.1.17095.1.3.15.0.2 etc...

    Custom Index in IMC is looking for just the Base OID here - so you should try 1.3.6.1.4.1.17095.1.3.15 instead.



    ------------------------------
    Justin Guse
    ------------------------------



  • 6.  RE: Error collecting personalized information.

    Posted Jan 30, 2026 08:41 AM

    Hello,

    About using IMC custom index for SNMP polling, general question:

    My intention is to get values loggedOnCallbackUsers 1.3.6.1.4.1.32804.1.1.1.2.2 MIB (OID) SEN-OSCC-MIB
    I will get error "Failure, Unsupported feature or lack of necessary configuration"  when I try to build custom index pollling
     
    Could this be the problem:
     
    I am trying to add custom index to poll windows server which has sysOID is 1.3.6.1.4.1.311.1.1.3.1.2 => Enterprise ID:1.3.6.1.4.1.311 (Microsoft Windows)
     
    SEN-OSCC-MIB which I am using for Custom Index => Enterprise ID: 1.3.6.1.4.1.32804 (Siemens)
     
    Is it so that custom index polling only works when index is "under" 1.3.6.1.4.1.311 ? Enterprise ID:1.3.6.1.4.1.311 (Microsoft Windows)
    I can load SEN-OSCC-MIB to IMC without any problems and poll that 1.3.6.1.4.1.311.1.1.3.1.2 from MIB Management window.
    Building custom index polling is the issue....
     
     
    Brgds,
     
     
    Anssi Laitinen




  • 7.  RE: Error collecting personalized information.

    Posted Jan 28, 2026 07:45 PM

    We no longer have a support contract, but before it ended, the engineers (HPe) informed us that the problem was in the MIB, which is not true, as it works perfectly in any other program, including the IMC's own SNMP, as you can see in the images, where it works normally. We needed an alternative to bypass this test and make it work directly through the OID, mainly because the other OIDs work normally, only this one doesn't.

    -------------------------------------------



  • 8.  RE: Error collecting personalized information.

    Posted Jan 29, 2026 08:56 AM

    Hello Justin

    I've already tried that and the error persists.

    -------------------------------------------