-
Bug
-
Resolution: Unresolved
-
Medium
-
J-Release
-
VES-Collector Docker image = nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector:1.12.3
I couldn't locate the traget in our smo. We used the it/dep/smo-install/scripts to deploy the smo. I will reference https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=blob;f=solution/README.md;h=036b803495245f0b1b8043fb43317840574037b8;hb=HEAD, thank you.
VES-Collector Docker image = nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector:1.12.3 I couldn't locate the traget in our smo. We used the it/dep/smo-install/scripts to deploy the smo. I will reference https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=blob;f=solution/README.md;h=036b803495245f0b1b8043fb43317840574037b8;hb=HEAD , thank you.
We're encountering an issue testing O1-VES functionality between OSC [Rel.G] O-DU and OSC [Rel.I] SMO. The VES Collector in SMO lacks the necessary certificate files, preventing a successful connection.
Previously, the VES Collector relied on built-in certificates. However, the new version requires an external certificate method, which is not yet integrated in it/dep.
Given this situation, I have two questions:
- Is there any reference on how to use O1VES with external certificates?
- If above is unavailable, do you have a workaround for this?