Missing relationships for NetApp NAS file systems to Storage ServersOverview In our previous Storage discovery product documentation, ServiceNow indicated that relationship between NAS (Network Attached Storage) file systems and File Share from NetApp are discovered as shown below. CIRelationship typeCINAS File System [cmdb_ci_nas_file_system]Allocated from::Allocated toStorage File Share [cmdb_ci_storage_fileshare] However, hosts consuming the NAS storage from NetApp storage servers see what's known as junction-paths and not the storage file shares. Currently, we do not discover the junction-paths and cannot resolve the relationships between NAS File Systems and corresponding Storage File Shares. Here we provide a workaround to connect NAS file systems to the storage servers while we cannot resolve the relationships to the storage servers which we hope to alleviate analyses for dependent CIs or impacted services. How it works While Discovery does not detect junction-paths as part of NetApp cluster discovery, it does create interfaces associated with storage servers. By applying the attached update set, it will provide, 1. Extension section for the Linux Server pattern which resolves the nas_ip_address attribute of NAS File System CIs (needed as sometimes host name is captured instead) 2. Pre Sensor script that locates the interface CI using the nas_ip_address attribute of NAS File System CIs. If an interface with the nas_ip_address is found in the CMDB, the script checks the CI type of the Configureation Item reference attribute. If it matches with "Storage File Share" then the associated relationship between the file system and the storage server is created. An example of created relationship is shown below. How to deploy 1. Download the attached update set - sys_remote_update_set_PRB1457190_NetApp_NAS_FS.xml 2. Import it in the target instance. 3. Run Linux Server discovery after NetApp discovery.