Unable to match NULL value for Interface PeerSystemName in Polling and Thresholds in Smarts
search cancel

Unable to match NULL value for Interface PeerSystemName in Polling and Thresholds in Smarts

book

Article ID: 304287

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:




Unable to match NULL value for Interface PeerSystemName in Polling and Threasholds
Unable to match NULL value for PeerSystemName, PeerSystemType or CurrentUtilization in Polling and Thresholds group

Environment

VMware Smart Assurance - SMARTS

Cause

A NULL value match cannot be made. The match is on string only and cannot be matched against instrumented objects for NULL. The values cannot be matched on PeerSystemType and CurrentUtilization for NULL either.

Resolution

Matching can only performed for non NULL value.

You can see the instrumented objects when excuting dmctl command on the interface/port.

Example:

<BASEDIR>/IP/smarts/bin/dmctl -s INCHARGE-AM-PM get Interface::<instance>

If return contains:

CurrentUtilization = <unknown>
PeerSystemName = <unknown>
PeerSystemType = <unknown>

Any attributes that have <unknown> return cannot be tested for NULL in Thresholds group when setting up Matching Criteria.

This is a limitation of Wildcard matching.