# SPECTRUM Load_In SpectroWatch attribute evaluating a value of "0" (Legacy KB ID CNC TS31920 )

**Document ID :**KB000051908

**Last Modified Date :**14/02/2018

SPECTRUM Load_In SpectroWatch attribute evaluating a value of "0"

SPECTRUM Load_In SpectroWatch attribute evaluating a value of "0" when displayed in the SpectroGRAPH Interface Performance View, Command Line Interface, SpectroGRAPH Attribute Browser, SSLOGGER/SRG reports and OneClick Attribute Editor.

Problem Environment:

SPECTRUM 08.01.00.00

SPECTRUM 09.00.00.00

Load_In

SpectroWatch

Causes of this problem:

The Load_In is of an Integer Data Type. The SpectroWatch was evaluating to a value of less than 1. Since the In_Load Data Type is Integer and the evaluating value is less than 1, the value displayed is zero.

Additional Information:

For this issue, this was confirmed by manually computing Load_In value based on the expressions from the Load_In SpectroWatch.

Load_In:

Expression: MAX( 0, INTEGER( ( ( ( ( ( INTEGER( isEther ) * COUNTER_DELTA( Sum_IN_Packets ) ) * REAL( 1600000 ) ) + ( COUNTER_DELTA( X_InOctets ) * REAL( 80000 ) ) ) / COUNTER_DELTA( X_sysUpTime ) ) / Internal_BandWidth ) ) )

Take two samples of the following attributes at 1 minute intervals for the interface model. This can be done using the Command Line Interface, SpectroGRAPH Attribute Browser or OneClick Attribute Editor:

Sum_IN_Packets

X_InOctets

For this example, in the first sample, the values for the attributes were as follows:

Sum_IN_Packets - 0

X_InOctets - 3137247655

In the second sample taken 60 seconds later, the values for the attributes were as follows:

Sum_IN_Packets - 0

X_InOctets - 3149881961

The value of Internal_Bandwidth is 622080000

Again, assuming the data in these files was collected 1 minute (60) seconds apart, we can then use the watch expression to compute the value of Load_In manually

The COUNTER_DELTA of both Sum_IN_Packets will be zero.

The COUNTER_DELTA of ifInOctets is 12634303.

The value of 80000 comes from computing X_InOctets (octets - 8) to bits. Multiplying by 100 so the result is an integer value for percentage and multiplying 100 again because X_SysUpTime is in time-ticks.

The value of sysUpTime has to be entered in Time Ticks. Assuming 60 seconds, we would need to multiply 60 by 100 for Time Ticks (6000).

When you then compute based on the above data, the result for Load_In is .27.

(((( 0 * 1600000 ) + ( 12634303 * 80000 )) / 6000) / 622080000 )

(((0 + 1010744240000) / 6000) / 622080000)

168457373 / 622080000

.27

.(Legacy KB ID CNC TS31920 )