What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Dell PowerVault MDi Sensor errors

Votes:

0

I am trying to use the MDi sensor but I am finding that the physical disk are going up and down all the time.

I have the latest Dell Disk Manager software installed on the remote probe machine and the latest PRTG.

I find that the report is OK for a scan then next it's "Failed to Execute SMCli Command". Each channel flip/flops between the two states.

Running the following command on the remote probe: smcli <MDi managment IP> -c "show allControllers summary; show allPhysicalDisks summary; show allVirtualDisks summary;" -quick -S -e

Returns this after a delay:

RAID Controller Module in Enclosure 0, Slot 0

Status: Online

Current configuration Firmware version: 07.84.44.60 Appware version: 07.84.44.60 Bootware version: 07.84.44.60 NVSRAM version: N26X0-784890-004 Pending configuration Firmware version: None Appware version: None Bootware version: None NVSRAM version: None Transferred on: None Model name: 2660 Board ID: 2660 Submodel ID: 136 Product ID: MD32xx Revision: 0784 Replacement part number: A02 Part number: 0N98MP Serial number: 324002S Vendor: DELL Date of manufacture: March 7, 2013 Trunking supported: No

Data Cache Total present: 1696 MB Total used: 1696 MB Processor cache: Total present: 352 MB Cache Backup Device Status: Optimal Type: SD flash physical disk Location: RAID Controller Module 0, Connector SD 1 Capacity: 7,639 MB Product ID: Not Available Part number: Not Available Serial number: a03f43c8 Revision level: 10 Manufacturer: Lexar Date of manufacture: January 1, 2013 Host Interface Board Status: Optimal Location: Slot 1 Type: SAS Number of ports: 2 Board ID: 0601 Replacement part number: PN 0N98MPA02 Part number: PN 0N98MP Serial number: SN 324002S Vendor: VN 13740 Date of manufacture: Not available Date/Time: Sun Sep 16 01:09:12 BST 2018

Associated Virtual Disks (* = Preferred Owner): Dev_DS_Unit2*, DMZ_DS_Unit2*, ISO_DS_Unit1*, Production_DS_Unit1*, RST_DS_Unit2*, Template_DS_Unit1*, Template_DS_Unit2*, TFS01_D_Drive_Unit1*

RAID Controller Module DNS/Network name: BDL8WX1 Remote login: Disabled

Ethernet port: 1 Link status: Up MAC address: 90:b1:1c:41:c9:b2 Negotiation mode: Auto-negotiate Port speed: 1000 Mbps Duplex mode: Full duplex Network configuration: Static IP address: 10.1.254.250 Subnet mask: 255.255.0.0 Gateway: 10.1.1.1

RAID Controller Module in Enclosure 0, Slot 1

Status: Removed

SUMMARY Number of physical disks: 24 Current media type(s): Physical Disk (24) Current interface type(s): Serial Attached SCSI (SAS) (24)

BASIC:

ENCLOSURE, SLOT STATUS CAPACITY MEDIA TYPE INTERFACE TYPE CURRENT DATA RATE PRODUCT ID FIRMWARE VERSION CAPABILITIES 0, 0 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 1 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 2 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 3 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 4 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 5 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 6 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 7 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 8 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 9 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 10 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 0, 11 Optimal 465.761 GB Physical Disk SAS 6 Gbps ST500NM0001 PS08 1, 0 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 1 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 2 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 3 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 4 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 5 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 6 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 7 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 8 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 9 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 10 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08 1, 11 Optimal 1,863.016 GB Physical Disk SAS 6 Gbps ST2000NM0001 PS08

DRIVE CHANNELS (RAID Controller Module 0):

ENCLOSURE, SLOT PREFERRED CHANNEL REDUNDANT CHANNEL 0, 0 1 Physical Disk path consistency: 0 0, 1 1 Physical Disk path consistency: 0 0, 2 1 Physical Disk path consistency: 0 0, 3 1 Physical Disk path consistency: 0 0, 4 1 Physical Disk path consistency: 0 0, 5 1 Physical Disk path consistency: 0 0, 6 1 Physical Disk path consistency: 0 0, 7 1 Physical Disk path consistency: 0 0, 8 1 Physical Disk path consistency: 0 0, 9 1 Physical Disk path consistency: 0 0, 10 1 Physical Disk path consistency: 0 0, 11 1 Physical Disk path consistency: 0 1, 0 1 Physical Disk path consistency: 1 1, 1 1 Physical Disk path consistency: 1 1, 2 1 Physical Disk path consistency: 1 1, 3 1 Physical Disk path consistency: 1 1, 4 1 Physical Disk path consistency: 1 1, 5 1 Physical Disk path consistency: 1 1, 6 1 Physical Disk path consistency: 1 1, 7 1 Physical Disk path consistency: 1 1, 8 1 Physical Disk path consistency: 1 1, 9 1 Physical Disk path consistency: 1 1, 10 1 Physical Disk path consistency: 1 1, 11 1 Physical Disk path consistency: 1

Any STANDARD VIRTUAL DISKS SUMMARY Number of standard virtual disks: 8

Name Thin Provisioned Status Capacity Accessible by Source Dev_DS_Unit2 No Optimal 10.000 TB Host Group ist-vmCluster01 Disk Pool Disk_Pool_2 DMZ_DS_Unit2 No Optimal 1,024.000 GB Host Group ist-vmCluster01 Disk Pool Disk_Pool_2 ISO_DS_Unit1 No Optimal 500.000 GB Host Group ist-vmCluster01 Disk Pool Disk_Pool_1 Production_DS_Unit1 No Optimal 3,072.000 GB Host Group ist-vmCluster01 Disk Pool Disk_Pool_1 RST_DS_Unit2 No Optimal 1,024.000 GB Host Group ist-vmCluster01 Disk Pool Disk_Pool_2 Template_DS_Unit1 No Optimal 300.000 GB Host Group ist-vmCluster01 Disk Pool Disk_Pool_1 Template_DS_Unit2 No Optimal 724.000 GB Host Group ist-vmCluster01 Disk Pool Disk_Pool_2 TFS01_D_Drive_Unit1 No Optimal 60.000 GB Host Group ist-vmCluster01 Disk Pool Disk_Pool_1

I am wondering if the sensor is sensitive to the time it takes to collect this data.. it's taking 17 seconds.

dell mdi physicaldisk

Created on Sep 16, 2018 12:17:42 AM



6 Replies

Votes:

0

Hi there,

Please activate the "Write Sensor result to disk" option in the sensor's settings and post the log files (Result of Sensor XXX.Data.txt and Result of Sensor XXX.txt) located on the corresponding probe under "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)". Please post them when you see that the sensor errors with the "Failed to Execute SMCli Command"-error.

Best regards.

Created on Sep 17, 2018 10:46:28 AM by Dariusz Gorka [Paessler Support]

Last change on Sep 17, 2018 10:46:34 AM by Dariusz Gorka [Paessler Support]



Votes:

0

Looks like the guessed at timeout

Command "C:\Program Files\Dell\MD Storage Manager\client\SMcli.exe" censored -c "show PhysicalDisk[0,1];" -quick -S -e
Start time 17/09/2018 11:12:27
Aquired semaphore after 0 seconds
(Re)Try 0
Time 17/09/2018 11:12:27
(Meta)Scan Failed
Semaphore timeout
End time 17/09/2018 11:12:32


Data['accesskey'].asString := '';
Data['addomainpass'].asString := '';
Data['authtoken'].asString := '';
Data['authuserpwd'].asString := '';
Data['awssk'].asString := '';
Data['blockedsens'].asString := '';
Data['canlinux'].asString := '0';
Data['checkfailed'].asString := '0';
Data['dbpassword'].asString := '';
Data['elevationpass'].asString := '';
Data['environment'].asString := '';
Data['esxpassword'].asString := '';
Data['evapassword'].asString := '';
Data['fastcount'].asString := '0';
Data['ftppassword'].asString := '';
Data['host'].asString := 'censored';
Data['hostv6'].asString := '';
Data['httppassword'].asString := '';
Data['imappassword'].asString := '';
Data['inerror'].asString := '1';
Data['interval'].asString := '60';
Data['ipversion'].asString := '0';
Data['isexesensor'].asString := '1';
Data['lastmsg'].asString := '#O230';
Data['lastuptime'].asString := '0';
Data['linuxloginpassword'].asString := '';
Data['mailpassword'].asString := '';
Data['notonpod'].asString := '0';
Data['oauthrefreshtoken'].asString := '';
Data['oauthtoken'].asString := '';
Data['password'].asString := '';
Data['pingdompassword'].asString := '';
Data['pop3password'].asString := '';
Data['privatekey'].asString := '';
Data['proxypass'].asString := '';
Data['proxypassword'].asString := '';
Data['prtg_linuxpassword'].asString := '';
Data['prtg_windowspassword'].asString := '';
Data['reboot'].asString := '43359.4511833333';
Data['reqmsginterval'].asString := '60';
Data['restpassword'].asString := '';
Data['resttoken'].asString := '';
Data['resultfile'].asString := 'Result of Sensor 4677.txt';
Data['secret'].asString := '';
Data['secretaccesskeyid'].asString := '';
Data['sensorid'].asString := '4677';
Data['simulate'].asString := '0';
Data['slot'].asString := '1';
Data['smspassword'].asString := '';
Data['smtppassword'].asString := '';
Data['smtppassword2'].asString := '';
Data['snmpauthpass'].asString := '';
Data['snmpcommv1'].asString := '';
Data['snmpcommv2'].asString := '';
Data['snmpencpass'].asString := '';
Data['socksproxypass'].asString := '';
Data['sshelevationpass'].asString := '';
Data['tlsexplicit_default'].asString := '';
Data['tlsexplicit_ftp'].asString := '';
Data['tlsexplicit_imap'].asString := '';
Data['tlsexplicit_pop3'].asString := '';
Data['tlsexplicit_port'].asString := '';
Data['tlsexplicit_smtp'].asString := '';
Data['tray'].asString := '0';
Data['uptimecount'].asString := '0';
Data['usednstime'].asString := '0';
Data['windowsloginpassword'].asString := '';
Data['xmlhttppassword'].asString := '';

Created on Sep 17, 2018 11:15:02 AM

Last change on Sep 17, 2018 11:35:21 AM by Dariusz Gorka [Paessler Support]



Votes:

0

Hi there,

Are there multiple sensors of the same type under one device? This usually happens when the sensor/PRTG is unable to use the Mutex any further, which then results in a timeout of the semaphore. There are logs that can tell us more. Please follow these steps which will generate additional logs:

  1. Within PRTG head to Setup > System Administration > Administrative Tools and press button "Write Probe Status Files".
  2. To upload the Probe State files and the PRTG system logs to our FTP server, open "PRTG Administration Tool" on the affected probe and use the button "Send Logs to Paessler..." on tab "Logs and Infos". Make sure to enter this ticket's id there (PAE1091085) before uploading. See also:
    https://www.paessler.com/manuals/prtg/prtg_server_administrator#logs

If the server does not have an active Internet connection, then please manually ZIP the "C:\ProgramData\Paessler\PRTG Network Monitor\Logs\"-folder and forward it to use via mail to [email protected] and by using "PAE1091085" in the subject.

Best regards.

Created on Sep 17, 2018 11:38:09 AM by Dariusz Gorka [Paessler Support]



Votes:

0

Yes there are.. I have 24 Physical Disks and 5 Virtual to monitor...

Created on Sep 17, 2018 12:34:07 PM



Votes:

0

Hi there,

What scanning interval do you use for these sensors? Could you try to increase it to 5 minutes and check if the issue persists?

Best regards.

Created on Sep 17, 2018 12:38:05 PM by Dariusz Gorka [Paessler Support]



Votes:

0

That's fixed it :-)

Created on Sep 17, 2018 12:48:12 PM




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.