Automatic end-to-end mapping
Automatic end-to-end (E2E) mapping has the following supported relations:
- SRM LUNs <> Volumes (for physical machines - windows servers polled via Windows Management Instrumentation (WMI) and using FC/SCSI protocol)
- SRM LUNs <> Virtualization Manager (VMAN) Datastores
- SRM LUNs <> Virtualization Manager (VMAN) Virtual Machines (RDM mapping)
- SRM FileShares <> Virtualization Manager (VMAN) Datastores
Automatic end-to-end mapping of your physical servers
Prior to SRM 6.7, automatic end-to-end mapping was only available for Master Boot Record (MBR) drives. With SRM 6.7, support had been added for GUID Partition Table (GPT) drives in E2E mapping.
When installing SRM with SAM, the Network Storage Topology Resource is enabled automatically for any Windows device added after the install.
Any Windows device monitored by SAM prior to the installation of SRM will have the Network Storage Topology Resource disabled. To make SRM recognize the Windows servers added before the SRM installation, you must do one of the following:
- Select the node, go to Node Details and select List Resource on the Management widget. Here you can enable the Network Storage Topology Resource option.
- Run a network discovery on existing nodes to add the Network Storage Topology Resource. Please note the widget is not enabled after it is added.
The Network Storage Topology Resource does not work for Windows servers monitored with SNMP. All Windows servers must be monitored via Windows Management Instrumentation (WMI) to use this feature. Windows Server 2003 and above can be monitored using WMI.
Automatic end-to-end mapping of virtual servers using VMware or Hyper V
Mapping your storage devices to your virtual environment requires SolarWinds Virtualization Manager (VMAN 6.2 or later) and the Virtualization Manager Orion Platform module (2.0 or later). After you install VMAN, the mapping is automated for virtual devices and no modifications are needed in SRM.