Hello Vimal-Kumar,

without the logs, it will be hard to tell what is going wrong. I didn't find the G400 and G800 explicit listed in the SOM Device Support Matrix, but assume they can work, but I'm not 100% sure about using the SVP with Hitachi. SOM needs to be able to open the ports 1099, 51100 and 51099 on the Array side. If these ports are open and it still not works, I recommend to raise a support ticket.

Regards,

Dieter

Please find the logs below, if it helps

Discovery logs for 172.30.10.190
Auto Refresh: 60 Sec
Start Date:
End Date:
Severity:
Recent Only

[2017-09-16 08:15:03] INFO Entering InventoryExecutor.serviceCall(job=1505562037241)
[2017-09-16 08:15:03] INFO URI: 172.30.10.190
[2017-09-16 08:15:03] INFO User name: Hitachi
[2017-09-16 08:15:03] INFO Password: ***
[2017-09-16 08:15:03] INFO Comment: null
[2017-09-16 08:15:03] INFO WBEM Collector gathering inventory on 172.30.10.190
[2017-09-16 08:15:04] INFO root/pg_interop[FAIL]
[2017-09-16 08:15:04] INFO https://172.30.10.190 Error CIM_ERR_INVALID_NAMESPACE while grabbing data from namespace root/pg_interop
[2017-09-16 08:15:04] INFO https://172.30.10.190 0 devices found in root/pg_interop namespace
[2017-09-16 08:15:05] INFO Found this interesting profile Array with version 1.7.0 via https://172.30.10.190
[2017-09-16 08:15:05] INFO Found toplevel system HITACHI_StorageSystem.VSP G400.441644 via https://172.30.10.190
[2017-09-16 08:15:05] INFO Found this interesting profile Array with version 1.5.0 via https://172.30.10.190
[2017-09-16 08:15:05] INFO Found toplevel system HITACHI_StorageSystem.VSP G400.441644 via https://172.30.10.190
[2017-09-16 08:15:05] INFO Found this interesting profile Array with version 1.6.0 via https://172.30.10.190
[2017-09-16 08:15:05] INFO Found toplevel system HITACHI_StorageSystem.VSP G400.441644 via https://172.30.10.190
[2017-09-16 08:15:05] INFO https://172.30.10.190 0 devices found in interop namespace
[2017-09-16 08:15:06] INFO root/cimv2[FAIL]
[2017-09-16 08:15:06] INFO https://172.30.10.190 Error CIM_ERR_INVALID_NAMESPACE while grabbing data from namespace root/cimv2
[2017-09-16 08:15:06] INFO https://172.30.10.190 0 devices found in root/cimv2 namespace
[2017-09-16 08:15:24] INFO Is NOT a APPIQ_HdsProvider
[2017-09-16 08:15:48] INFO root/pg_interop[FAIL]
[2017-09-16 08:15:48] INFO http://172.30.10.190 Error XMLERROR while grabbing data from namespace root/pg_interop
[2017-09-16 08:15:48] INFO http://172.30.10.190 0 devices found in root/pg_interop namespace
[2017-09-16 08:16:30] INFO interop[FAIL]
[2017-09-16 08:16:30] INFO http://172.30.10.190 Error XMLERROR while grabbing data from namespace interop
[2017-09-16 08:16:30] INFO http://172.30.10.190 0 devices found in interop namespace
[2017-09-16 08:17:12] INFO root/cimv2[FAIL]
[2017-09-16 08:17:12] INFO http://172.30.10.190 Error XMLERROR while grabbing data from namespace root/cimv2
[2017-09-16 08:17:12] INFO http://172.30.10.190 0 devices found in root/cimv2 namespace
[2017-09-16 08:17:12] INFO The following ports did NOT respond for 172.30.10.190. If you expected them to respond -- please check that the remote agent is functional
2001 used by [HDS]
5988 used by [BNA (Brocade/McData), BNA AccessGateway(Brocade), Symmetrix, Symmetrix-VMAX, EVA, Clariion]
The following ports DID respond
1099 used by [HDS]
51099 used by [HDS]
5989 used by [BNA (Brocade/McData), BNA AccessGateway(Brocade), Symmetrix, Symmetrix-VMAX, EVA, Clariion]
[2017-09-16 08:17:12] INFO WBEM_COLLECTOR: Discovery complete: No supported devices were found.

Well if the SVP can be used for HDS in SOM (which I need to check) the the appiq_hds provider would be used by SOM.
From your logs I can see for this provider:
[2017-09-16 08:15:24] INFO Is NOT a APPIQ_HdsProvider
The following ports DID respond
1099 used by [HDS]
51099 used by [HDS] (note port 51100 might also be used and is not printed in the logs)

[2017-09-16 08:17:12] INFO The following ports did NOT respond for 172.30.10.190. If you expected them to respond -- please check that the remote agent is functional
2001 used by [HDS]

Nevertheless the SOM Deployment Guide states in section "Device Specific Ports used by SOM":
Device:
Hitachi AMS, Hitachi Unified
Storage, Hitachi VSP
Device Interface:
XML
Port (SOM Outbound/DeviceInbound):
1099, 2001, 51099, 51100

so I'm not sure if port 2001 or 51100 are causing this.

Dieter

Well if the SVP can be used for HDS in SOM (which I need to check) the the appiq_hds provider would be used by SOM.
From your logs I can see for this provider:
[2017-09-16 08:15:24] INFO Is NOT a APPIQ_HdsProvider
The following ports DID respond
1099 used by [HDS]
51099 used by [HDS] (note port 51100 might also be used and is not printed in the logs)

[2017-09-16 08:17:12] INFO The following ports did NOT respond for 172.30.10.190. If you expected them to respond -- please check that the remote agent is functional
2001 used by [HDS]

Nevertheless the SOM Deployment Guide states in section "Device Specific Ports used by SOM":
Device:
Hitachi AMS, Hitachi Unified
Storage, Hitachi VSP
Device Interface:
XML
Port (SOM Outbound/DeviceInbound):
1099, 2001, 51099, 51100

so I'm not sure if port 2001 or 51100 are causing this.

Dieter