Smarts IP: Interface with ifType 30 (DS3) is not showing any performance instrumentation even though its in the list for ifTypePattern
search cancel

Smarts IP: Interface with ifType 30 (DS3) is not showing any performance instrumentation even though its in the list for ifTypePattern

book

Article ID: 331827

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:


Interface with ifType=30 , better known as E3 or DS3 interfaces, do not show any performance instrumentation

In tpmgr-param.conf it is included in the list to have performance instrumentation:

fault ifTypePattern = "30|37|134|135|32";

Environment

VMware Smart Assurance - SMARTS

Cause

ifType=30 this is a E3 interface or better known as DS3. This interface does not have Performance Instrumentation enabled by default.

The reason is as follows:

When a device supports 32bit counters only, for interfaces with very high speeds, the counters like ifInOctets, ifOutOctets may run a full max value between the polling intervals and can result in wrong computation of CurrentUtilization. This is the basis of choosing not to monitor interfaces at speeds up to 100Mbps with 32bit counters only.

By default we monitor interfaces up to 20Mbps using MIB2 instrumentation.

Resolution

The flag FallbackInterfaceMonitoringToMIB2 set to TRUE can be used to monitor interfaces with speeds up to 100Mbps with MIB2 instrumentation,

1. Set the below flag to TRUE from tpmgr-param.conf (use ../smart/bin/sm_edit ../conf/discovery/tpmgr-param.conf )

FallbackInterfaceMonitoringToMIB2 TRUE

2. load the conf file through the below command after making the above modification.

./sm_tpmgr.exe -s <server_name> --load-conf=tpmgr-param.conf

6. Now re-discover the device and you should observe the performance instrumentation getting created for this interface

NOTE: if the CurrentUtilization calculation appears to be incorrect then the above flag may need to be set to FALSE. Consult with Customer Service to check.