After Snapcenter install port 8145 is not active on NAS file indexing server.

Chiatan — Wed, 04 Jun 2025 14:57:05 GMT

Hello Gent's,

Snapcenter 2.0 issue communicating to NAS file indexing server on port 8145, port on the liux server is not opened, any reason why it's not active ?

2017-06-17T23:02:22.9232329+01:00 ERROR SnapManagerWeb_20 PID=[5288] TID=[ApisJobNotificationHandler:210] Exception in method: InvokeXML. System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.0.000.000:8145 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6,

ERROR SnapManagerWeb_19 PID=[5288] TID=[ApisJobNotificationHandler:210] System.InvalidCastException: Unable to cast object of type 'SnapMgrContracts.SmJobData' to
type 'SMCoreContracts.SmApplyProtectionRequest'. at SnapManager.SMSDAL.Job.JobHelper.GetJobData[T](Int64 jobId)

Any other port to be used ?

var/opt/snapcenter/spl/etc/spl.properties

SPL_PORT=8145

Thanks

Chaitan

Re: Issues with Backing up volume to cloud through altavault using snapcenter

Chiatan — Fri, 16 Jun 2017 22:44:35 GMT

topic Re: Issues with Backing up volume to cloud through altavault using snapcenter in NetApp Console

After Snapcenter install port 8145 is not active on NAS file indexing server.

Re: Issues with Backing up volume to cloud through altavault using snapcenter