* Added new jumps to scan-ipmitool to make it less likely to trigger a jump alert for 'Temp{1..4}' sensors.

Signed-off-by: Digimer <digimer@alteeve.ca>

scancore-agents/scan-ipmitool/scan-ipmitool

@@ -130,6 +130,7 @@ $anvil->data->{'scan-ipmitool'} = {
 			buffer				=>	2,
 			weight				=>	1,
 		},
+		### TODO: Support wild-card sensor names.
 		# If the user wants to assign manual values for a given sensor, they can do 
 		# so by creating an entry hear where the key is the IPMI-returned sensor 
 		# name.
@@ -178,6 +179,19 @@ $anvil->data->{'scan-ipmitool'} = {
 		'RAID Controller'		=>	{
 			jump				=>	15,
 		},
+		# On Dells, 'Temp{1..4}' change a lot, so we bump the jump.
+		'Temp1'				=>	{
+			jump				=>	20,
+		},
+		'Temp2'				=>	{
+			jump				=>	20,
+		},
+		'Temp3'				=>	{
+			jump				=>	20,
+		},
+		'Temp4'				=>	{
+			jump				=>	20,
+		},
 	},
 	# TODO: Remove this and have Striker pull the list of thermal sensors read in the 
 	#       last $timestamp.

tools/anvil-update-states

@@ -884,7 +884,7 @@ ORDER BY
 			{
 				# Mark it as deleted.
 				my $query = "UPDATE network_interfaces SET network_interface_operational = 'DELETED' WHERE network_interface_uuid = ".$anvil->Database->quote($network_interface_uuid).";";
-				$anvil->Log->entry({source => $THIS_FILE, line => __LINE__, level => 1, key => "log_0124", variables => { query => $query }});
+				$anvil->Log->entry({source => $THIS_FILE, line => __LINE__, level => 2, key => "log_0124", variables => { query => $query }});
 				$anvil->Database->write({query => $query, source => $THIS_FILE, line => __LINE__});
 			}