How to monitor Dell PowerVault MD32xx (SAS attached to ESXi hosts)?
How to monitor Dell PowerVault MD32xx?
Votes:
0
10 Replies
Votes:
0
Please review our article on how to set this up in PRTG.
Votes:
0
Hi, Can you be more specific? On our probe device we have tried to add the MDi sensor. Error is Needs the IP address of the Storage Area Network (SAN) defined in the parent device settings. Can you explain to define the IP of the SAN in the parent device settings?
Votes:
0
It means that you simply need to create a device with the IP of the SAN configured as its address :) Then you can add the powervault sensor to it.
Votes:
0
We have added a new device with the IP of the SAN, and attempted to add the powervault sensor, but we receive the error that no virtual disk is found. We are using a PowerVault MD3420 SAS. Are you aware of any issues using this sensor with SAS?
Votes:
0
The Dell Modular Disk Storage Manager is installed on the probe device? Have you tried both the physical and the logical disk variants of the powervault sensors?
The sensor "Dell PowerVault MDi Logical Disk" may not work with the SAS MD3200 model. In order to check that, please perform the following:
- Go to registry and open HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\storage\SMclient and copy the value from "path"
- Open the path in a command prompt
- Run smcli.exe <host> -c "show allControllers summary; show allVirtualDisks summary;" -quick -S -e
Created on Aug 31, 2015 12:27:52 PM by
Stephan Linke [Paessler Support]
Last change on Aug 31, 2015 12:42:53 PM by
Stephan Linke [Paessler Support]
Votes:
0
Hi, We have been able to deploy the physical sensor, and it does return the basics like up/down on the disks. We are unable to deploy the logical sensor, as the error returns "no virtual disk found".
The smcli.exe <host> -c "show allControllers summary; show allVirtualDisks summary;" -quick -S -e command did return the logical information. So it looks like our device is configured correctly to send out SNNP data.
Status: Online Current configuration Firmware version: 08.20.09.60 Appware version: 08.20.09.60 Bootware version: 08.20.09.60 NVSRAM version: N2701-820890-006 Pending configuration Firmware version: None Appware version: None Bootware version: None NVSRAM version: None Transferred on: None Model name: 2732 Board ID: 2701 Submodel ID: 218 Product ID: MD34xx Revision: 0820 Replacement part number: 0F3P10 Part number: 0F3P10 Serial number: Vendor: DELL Date of manufacture: August 30, 2070 Trunking supported: No Data Cache Total present: 3487 MB Total used: 2048 MB Data Cache Module Status: Optimal Location: RAID Controller Module 0, Slot 1 Capacity: 4,096 MB Replacement Part number: Not Available Manufacturer Part Number: Part Number: Not Available Serial number: Manufacturer: Unknown Date of manufacture: March 5, 2015 Shared: Yes Revision Code: 0x00 0x00 Processor cache:
Created on Sep 17, 2015 2:01:06 PM
Last change on Feb 17, 2016 6:21:43 AM by
Luciano Lingnau [Paessler]
Votes:
0
Are you using the iDRACs IP or the servers IP? Could you try either one to see if it works?
Votes:
0
Rob, did you get any further with this? I'm in the same position. Monitoring a MD3200i, can pick up the physical drives but not the logical.
The smcli.exe <host> -c "show allControllers summary; show allVirtualDisks summary;" -quick -S -e also retrieves the virtual disk information, and the PRTG sensor finds the name of the disk group but will not show any information.
STANDARD VIRTUAL DISKS SUMMARY Number of standard virtual disks: 8 NAME STATUS CAPACITY RAID LEVEL DISK GROUP LUN ACCESSIBLE BY MEDIA TYPE INTERFACE TYPE diskgroup1_lun10 Optimal 558.385 GB 10 diskgroup1_raid10 10 Host Group Vmware Physical Disk Serial Attached SCSI (SAS) diskgroup1_lun11 Optimal 837.500 GB 10 diskgroup1_raid10 11 Host Group Vmware Physical Disk Serial Attached SCSI (SAS) diskgroup1_lun4 Optimal 930.684 GB 10 diskgroup1_raid10 4 Host Group Vmware Physical Disk Serial Attached SCSI (SAS) diskgroup1_lun5 Optimal 1,768.335 GB 10 diskgroup1_raid10 5 Host Group Vmware Physical Disk Serial Attached SCSI (SAS) diskgroup1_lun6 Optimal 930.685 GB 10 diskgroup1_raid10 6 Host Group Vmware Physical Disk Serial Attached SCSI (SAS) diskgroup1_lun7 Optimal 558.405 GB 10 diskgroup1_raid10 7 Host Group Vmware Physical Disk Serial Attached SCSI (SAS) diskgroup1_lun8 Optimal 558.415 GB 10 diskgroup1_raid10 8 Host Group Vmware Physical Disk Serial Attached SCSI (SAS) diskgroup1_lun9 Optimal 558.399 GB 10 diskgroup1_raid10 9 Host Group Vmware Physical Disk Serial Attached SCSI (SAS)
SNMP is setup OK. We can't monitor this via iDrac as it's a remote probe on a virtual machine.
Any suggestions???
Created on Feb 17, 2016 12:32:30 AM
Last change on Feb 17, 2016 6:21:08 AM by
Luciano Lingnau [Paessler]
Votes:
0
I'll forward it to our devs so they can have a look.
Votes:
0
The problem is caused by the underscores in your disk names. This should work with v16.1.22 (i.e. the latest version available). Can you try to update and see if the sensors work then?
Add comment