Clustered Data ONTAP MetroCluster: MetroCluster Node Interconnect Monitoring Rule

DataONTAP.Cluster.MetroCluster.Monitoring.Node.Interconnect.Rule (Rule)

The MetroCluster Node Interconnect Monitoring Rule checks that each interconnect adapter has two links and that each link is up.

Knowledge Base article:

Summary

The MetroCluster Node Interconnect Monitoring Rule checks that each interconnect adapter has two links and that each link is up.

Configuration

Three overrides are available for this rule. Sync Time and Interval Seconds determine when and how often the rule runs. Timeout Seconds determines how long System Center Operations Manager waits for the rule to complete.

Resolutions

If you suspect a problem with this rule, check the OnCommand and System Center Operations Manager event logs on the management server running the rule.

Additional Information

Event ID

Severity

Description

20001

INFO

OK - indicates that the link status is up

20002

ERR

Critical - indicates that the link status is down

20010

INFO

OK - indicates that the link mirror status is up

20012

ERR

Critical - indicates that the link mirror status is offline

20020

INFO

OK - indicates that the interconnect adapter physical link status is up

20022

ERR

Critical - indicates that the interconnect adapter physical link status is down

Element properties:

TargetDataONTAP.Cluster.MetroCluster.Node
CategoryAvailabilityHealth
EnabledTrue
Alert GenerateFalse
RemotableTrue

Member Modules:

ID Module Type TypeId RunAs 
SimpleSchedulerDataSource DataSource System.SimpleScheduler Default
RunMonitoringPowershellScript WriteAction DataONTAP.Cluster.MetroCluster.Monitoring.WriteActionModuleType Default

Source Code:

<Rule ID="DataONTAP.Cluster.MetroCluster.Monitoring.Node.Interconnect.Rule" Target="DataONTAP.Cluster.MetroCluster.Node" Enabled="true" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>AvailabilityHealth</Category>
<DataSources>
<DataSource ID="SimpleSchedulerDataSource" TypeID="System!System.SimpleScheduler">
<!-- IntervalSeconds specifies how often we will run the rule. -->
<IntervalSeconds>3600</IntervalSeconds>
<!-- SyncTime specifies the minutes after the hour to synchronize execution of the rule. -->
<SyncTime>00:03</SyncTime>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="RunMonitoringPowershellScript" TypeID="DataONTAP.Cluster.MetroCluster.Monitoring.WriteActionModuleType">
<TimeoutSeconds>600</TimeoutSeconds>
<MonitoringMethodName>GetMCCNodeInterconnectStatus</MonitoringMethodName>
<VserverUUID>$Target/Property[Type="DC!DataONTAP.Cluster.AbstractVserver"]/UUID$</VserverUUID>
</WriteAction>
</WriteActions>
</Rule>