Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Storage Resource Monitor (SRM) > SRM 6.5 Administrator Guide > SRM solutions > Automatic end-to-end mapping

Automatic end-to-end mapping

Created by Nigel, last modified by Nigel on Mar 14, 2017

Views: 43 Votes: 0 Revisions: 1

Automatic end-to-end 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

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:

  • Edit the node using the List Resources feature of the Orion Web Console Node Management utility where you can select the Network Storage Topology Resource option.
  • Run a network discovery on existing nodes to add the Network Storage Topology Resource. Please note the resource 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.

 
Last modified
08:56, 14 Mar 2017

Tags

Classifications

Public