Network Storage Protocols Discussions

OnCommand Plug-in : Controler HA Status monitor warning at connected state

regis_graf

Hello everyone.

We are checking every health monitor, and if most works fine, some of them are giving us strange status.

For Controller HA Status monitor, we have a warning on all ous systems, but there is no real error .

This is what I have in Scom :

Context:

  

Date and Time: 19/03/2012 15:24:52

Log Name: OnCommand

Source: Data ONTAP MP

Event Number: 1011

Level: 2

Logging Computer: XXXXXXXXXXX

User: N/A

Description:

Controller cluster state is CONNECTED. Controller xxxxxxxx Address: 10.10.10.10. 

  

Event Data:

< DataItem type =" System.XmlData " time =" 2012-03-19T15:24:52.3632821+01:00 " sourceHealthServiceId =" xxxxxx-E373-EE4A-3A5E-xxxxxxxxxx " >

< EventData >

  < Data > Controller cluster state is CONNECTED. Controllerxxxxxxx Address: 10.10.10.10. </ Data >

  </ EventData >

  </ DataItem >

Status connected, but this monitor is in "warning" state.

Is there anyone that know if you do something wrong ?

thanks in advanced.

Regis

7 REPLIES 7

crocker

is this one your team handles or should this question go in the NetApp Support Community?

Mike

mharding

The product team monitors the community, but if this is a critical issue you should open a Support ticket.

adaikkap

OnCommand Plug-in is not same as oncommand 5.0

regis_graf

It was not a critical issue. This is not something that works before, and not in production now.

We want to be sure that there is no false alarm, and thath we will not missed real alarm if we disable some counters.

By the way thanks for your answer.

Regis

watan

This looks like a cluster interconnet latency warning.  You can try to playing with the default vaule to adjust to your environment.  Also here is another thread with some more info .

https://communities.netapp.com/message/73452#73452

STEFANDELFS

Hi,

we got exactly the same message and some more (Network Data Received and NFS Operations per Second) which are not very helpful because there is no problem and we do not use CIFS or NFS by the way.

Did you find a solution for that?

kid regards

/Stefan

ramdass

Hi,

Those 3 issues are known issues (Cluster CONNECTED, Network Data Received and NFS) which have been addressed in the latest release (3.1) which works on SCOM 2012 only. As a workaround in 3.0, you may override the monitor threshold values, or disable them accordingly to avoid the spurious alerts. Sorry for the inconvenience.

Cheers,

Dennis

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public