We are using the V-Block Converged Infra (HP, Cisco & EMC all products to gather )in our client environment.
To monitor it we are using VCE Vision.
We had a requirement to integrate the VCE vision with another Microsoft monitorign tool.
We got a solution for the same, But the solution is trying to access VCE Vision over its URL with port 8443.
Now once it uses that it lands with HTTP 404 Error.
Any idea does VCE Vision work with 404 & Which components of VCE Vision work with port 8443.
I am new to this as well.
Solved! Go to Solution.
Can you advise what version of VCE Vision and what Microsoft tool you are running? I'd like to direct you to the VCE Vision Administration Guide and API documentation which contain port and integration information but the version is an important bit of data to know first.
We want to Integrate the VCE Vision with Microsoft SCOM (System Center 2012 R2 Operationsmanager).
There is a Integration KIT Provided by VCE developed by there partner Avnet in the below Link:
But the Proxy Agent provided by them tries to connect ot VCE Vision via port 8443 and i get error 404.
The normal VCE Vision page works for us when i open it in web browser i.e https://myvision.mydomain.com
But when i try to open the VCE Vision via https://myvision.mydomain.com:8443 then the web brwser says 404 and the Proxy Agent which communicates with SCOM Connects to vision via https://myvision.mydomain.com:8443 and then collects the data.
So i am not able to identify if the issue is with Vision not working with port 8443.
I am able to telnet 8443 from my Vision proxy agent which collects data from vision and send it to SCOM. So telnet from proxy server to VCE Vision via 8443 is working and is listening.
The user manual provided my Avente have mentioned to use it with 8443 and even if i don't mention 8443 in the config file still the proxy will forcefully use it.
Hope i dint confuse you with the above.
Thank you for the additional information. I also need to know what version of VCE Vision you are trying to connect to. The Microsoft SCOM connector from Avnet was written for the VCE Vision 2.5/2.6 and has not been updated for the current versions, which are 3.x. There were significant changes between the 2.x and 3.x versions, thus you may be running into issues related to the underlying architecture changes.
Thank you for the explanation, From the VCE Vision --> About i got this as the version 3.3.0-5194
So is there any way i can make the VCE Vision proxy work with this V3.3.0-5194 of VCE Vision ?
Any idea on this or has any other customer as well has faced this kind of a issue ?
I think you may be running into an issue because we have not updated the connector to work with VCE Vision 3.x. There is not a current support path to work through this with either VCE or Avnet. I did verify the port number for the inbound call is 8443, as is documented in the Admin Guide. There is also a Programmers Guide in our Technical Resource Center that may be helpful on the use of our APIs. The Admin Guide is also located there. https://docs.vce.com . You will need to set up a login to access this content.
There is some good news on this front. A new SCOM adapter is being developed for 3.x and we expect it to be available in Q12017. I do not have a list of features to share yet, but will come back and advise when it is launched.