Re: Best way of managing devices that do not send any traps (638 Views)
Reply
Frequent Advisor
tanish
Posts: 119
Registered: ‎12-08-2011
Message 1 of 12 (702 Views)
Accepted Solution

Best way of managing devices that do not send any traps

hello Exports

 

Can you suggest if there is any best pratice for managing the devices that do not have trap sending facility ?

 

I got a list of MIBS from the vendor and i hve loaded them to the console.

 

What is best monitoring we can provide to those devices ? 

 

Any help will be appreciated

Valued Contributor
Vikramsingh_03
Posts: 43
Registered: ‎01-23-2013
Message 2 of 12 (698 Views)

Re: Best way of managing devices that do not send any traps

Hi,

 

  What kind of monitoring you are looking for ? can you please explain me through steps ?

 

regards,

Vik

 

Appreciate my efforts by hitting Kudos.

Frequent Advisor
tanish
Posts: 119
Registered: ‎12-08-2011
Message 3 of 12 (693 Views)

Re: Best way of managing devices that do not send any traps

Let me clarify my requirement again

 

here is the senario:

 

Node will not send traps.

I have been provide with a list of mibs.

My goal is  to manage the device ( for eg : create an alert for a module down, or an X occurence in the mib value)

 

How can i achieve this goal ?

 

 

NNMi 9.22 running on windows

Valued Contributor
Vikramsingh_03
Posts: 43
Registered: ‎01-23-2013
Message 4 of 12 (681 Views)

Re: Best way of managing devices that do not send any traps

Hi Tanish,

 

  Ok. What you do is first upload all the MIBs and then load all the traps. After that you can see those traps in the SNMP Event Configuration under the Confiiguration Table. Please make a note that after loading the MIBs, you have to load their traps too for each MIB you have loaded.

 

 After that, open the trap, and make it enabled. Because, if you are not enabling those traps, those traps can be discarded when coming through the end devices. So, it is better to enable those traps which you want to see. If you want to display asa root cause, check as a root cause, that will become as a key incident and will show up on the console.

 

If you want any clearifications, please feel free to ask.

 

Regards,

Vik

 

Appreciate my efforts by hitting Kudos.

 

Valued Contributor
Vikramsingh_03
Posts: 43
Registered: ‎01-23-2013
Message 5 of 12 (672 Views)

Re: Best way of managing devices that do not send any traps

Hi,

 

  If this information is useful, please mark it as " Accept as a Solution " and hit the Kudos. I always appreciate your point given to me.

 

And, this will help other users to find an answer, if they are having the same problem.

 

Regards,

Vik

Honored Contributor
ramesh9
Posts: 1,150
Registered: ‎04-19-2011
Message 6 of 12 (657 Views)

Re: Best way of managing devices that do not send any traps

Hello Tanish

 

From your replies I can understand that you want NNM to do the custom polling on the device and report based on Custom Poller collection.

 

And you do not want the device to send any traps to NNM.

 

Best way according to me is 

 

1.   Enable firewall port 161 for NNM to Device communication

1.   Disable firewall port 162 for Device to NNM communication ( Traps been sent )

 

Or if you do not want to do that you can also have filtering based on Device IP so all traps sent from the device would be filtered. Please have a look at how to configure "trapfilter.conf" file in NNM reference page document on how to achive this.

 

Regards

Ramesh

Frequent Advisor
tanish
Posts: 119
Registered: ‎12-08-2011
Message 7 of 12 (649 Views)

Re: Best way of managing devices that do not send any traps

Hello Ramesh,

 

Even i reach the same point you were saying i.e custom poller collections.

 

Is there any refernce document in the hp dcos for these custom collections and incident generation ?

 

I want to know the limitations of these collection before i do a signoff :)

Honored Contributor
ramesh9
Posts: 1,150
Registered: ‎04-19-2011
Message 8 of 12 (638 Views)

Re: Best way of managing devices that do not send any traps

Please have a look at Step by Step Guide on Custom Poller Collections.

Frequent Advisor
tanish
Posts: 119
Registered: ‎12-08-2011
Message 9 of 12 (612 Views)

Re: Best way of managing devices that do not send any traps

Hello Ramesh,

 

Thanks for the shared document.

 

I hve a "SysStateOperational" to collect. it has only 2 values 2 and 1.

 

2- is normal

1- is critical

 

i have created a mib expression for this oid.

i have created a custom poller, with generate incident.

 

Any idea on what should i specify for threshold setting, so that i get an incident if the value is 1 ?

 

Valued Contributor
Vikramsingh_03
Posts: 43
Registered: ‎01-23-2013
Message 10 of 12 (605 Views)

Re: Best way of managing devices that do not send any traps

Hi Tanish,

 

  After enabling the custom poller, go to the "Comparison maps", create a new comparing method, in that, enter the ordering, the operator that will help you to evaluate, and now the Comparison value which is 1. At last, select the status as Critical.

 

So, now when your value compares with the value coming by polling the MIB for that device, it will generate an incident accordingly.

 

Thanks,

Vikram

 

Appreciate by hitting Kudos.

Frequent Advisor
tanish
Posts: 119
Registered: ‎12-08-2011
Message 11 of 12 (595 Views)

Re: Best way of managing devices that do not send any traps

Thanks vikram,

 

I have acheived the goal and was able to genrate incident as well .  i had some error due to not defining mib filter, but finally i make it  through.

 

The help documents really helped :)

 

And i thank you all for your valuable inputs and suggestions.

 

 

Thanks a lot.

Valued Contributor
Vikramsingh_03
Posts: 43
Registered: ‎01-23-2013
Message 12 of 12 (569 Views)

Re: Best way of managing devices that do not send any traps

Hi Tanish,

 

  Say thanks by hitting Kudos please.

 

Regards,

Vikram

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.