Highlighted
Absent Member.
Absent Member.
263 views

Alerts in NNM : clustering

Jump to solution
Hi,

I have a system that has 2 interfaces(2 LAN Cards in a single system), but configured with a single IP, and if any of the LAN goes down, switchover happens to the other LAN card. If I have to generate alert for both these interfaces if either of them/both stop working, then does NNM 7.51 has the capacity to do this?
0 Likes
1 Solution

Accepted Solutions
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
hi,

you can do the following :

In order to add a new alarm category
1.Go to Options -> Event Configuration.
2.Select Edit -> Alarms Categories
3.Type the new Category Name and Click Add.
4.Click Close.
5.Click File -> Save

In order to reach this functionality, the following steps were followed.
1.Select Options -> Event Configuration.
2.Browse to the OpenView Enterprise.
3.Select the Event interested for customization, for example; OV_Node_down and Click Edit -> Events -> Copy.
Rename the new Event to a meaningful name that you may easily track in the future
4.On the Sources Tab, Enter the sources that you would like to handle for this specific event. For example, Core 1&2 Switches and Click Add.

5.On the Event Message Tab, Select the Category and the Severity of this event.
6.Click Ok.
7.Click File -> Save

you will find some attached snap shots for the steps will help you.

wish this helps

thanks
Abdou

View solution in original post

6 Replies
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
hi,

first, the devices must be discovered and monitored by the NNM and the SNMP is configured on the node and loaded to the NNM.

then if you case happened, two alerts will received in the NNM stating that the interface went down and the other one is up.

you can configure/modify this alerts as you wish ( from the event configuration).


hint,
better to upgrade the NNM 7.51 to NNM 7.53, this will solve a lot of issues.

wish this will help.

thanks
Abdou
0 Likes
Highlighted
Absent Member.
Absent Member.
Hey,
Awesome suggestion.If u can elaborate a little bit more wil be of great help.
0 Likes
Highlighted
Absent Member.
Absent Member.
all NNM is going to monitor is the IP address through ping or SNMP. If the IP is not responding you will receive an alert.

If the node doesnt have SNMP, NNM will never know about the second card anyway.

You can probably set up a trap alarm to NNM when an IF goes down on that box- but it'll only be sent if the other is working (and the mechanism for making it primary NIC is working also..)

hth
aaron
0 Likes
Highlighted
Absent Member.
Absent Member.
Thanks for the reply. If u can slightly elaborate on the procedure to monitor them, will be a great help
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
hi,

you can do the following :

In order to add a new alarm category
1.Go to Options -> Event Configuration.
2.Select Edit -> Alarms Categories
3.Type the new Category Name and Click Add.
4.Click Close.
5.Click File -> Save

In order to reach this functionality, the following steps were followed.
1.Select Options -> Event Configuration.
2.Browse to the OpenView Enterprise.
3.Select the Event interested for customization, for example; OV_Node_down and Click Edit -> Events -> Copy.
Rename the new Event to a meaningful name that you may easily track in the future
4.On the Sources Tab, Enter the sources that you would like to handle for this specific event. For example, Core 1&2 Switches and Click Add.

5.On the Event Message Tab, Select the Category and the Severity of this event.
6.Click Ok.
7.Click File -> Save

you will find some attached snap shots for the steps will help you.

wish this helps

thanks
Abdou

View solution in original post

Highlighted
Absent Member.
Absent Member.
Hey Abdou,

Thanks a ton. This is marvellous.

Thanks again
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.