Smarts IP: Can IPStoragePaths be discovered in IP; how can I enable the discovery of IPStoragePaths in Smarts IP 9.3
search cancel

Smarts IP: Can IPStoragePaths be discovered in IP; how can I enable the discovery of IPStoragePaths in Smarts IP 9.3

book

Article ID: 332049

calendar_today

Updated On:

Products

VMware Smart Assurance

Environment

VMware Smart Assurance - SMARTS

Resolution

How to enable the discovery of IPStoragePaths.
 

Smarts IP 9.3 introduces a new IPStoragePath class for IP Manager that enables you to discover and monitor the topology in network paths from an ESX Host instance to a file server instance for Network attached storage (NAS) data transfer.





Discovery for IPStoragePath:

In Smarts IP, perform the following steps How to enable:

  1. Set the DisableIPStoragePathDiscovery parameter to False in the BASEDIR/smarts/local/conf/discovery/discovery.conf file.
  2. For VLANs: (If VLAN checking is not needed, ignore this step.)\
    1. If VLAN checking is needed, set the DisableIPStoragePathVLANCheck parameter to False in the BASEDIR/smarts/conf/discovery/discovery.conf file.
    2. If you want to ignore a VLAN, add the VLAN to the IgnoreVlanList parameter in the BASEDIR/smarts/local/conf/discovery/tpmgr-param.conf file.
  3. If the FileServer and the ESX host are more than ten hops away, increase the value of the IPStoragePathHopCount parameter in the discovery.conf file from 10 to any other suitable value.
  4. iscover the two-end points of IPStoragePath FileServer and ESX Host in IP Manager.
  5. Discover all of the relay devices (Router/Switches/Firewall/LoadBalancer etc.) which are in the path of the IPStoragePath.
  6. Discover the host (vCenter in which this particular ESX is using NAS Datastore).

In Server Manager do the following:
  1. Configure the credentials for the above mentioned vCenter.
  2. Discover the vCenter.

The EMC Smarts Server Manager User and Configuration Guide provides information about configuring the vCenter credentials and discovery.

Example of IPStoragePath instance discovered from within the IP Manager: