VNA Viptela Plugin Configuration Fails with "Possible Invalid Protocol Specified" error
search cancel

VNA Viptela Plugin Configuration Fails with "Possible Invalid Protocol Specified" error

book

Article ID: 199727

calendar_today

Updated On:

Products

CA Virtual Network Assurance

Issue/Introduction

When configuring the Virtual Network Assurance (VNA) Viptela plugin it fails with an error.

The error observed is "Possible Invalid Protocol Specified".

The error appears when trying to use REST to post the plugin configuration.

Environment

All supported Virtual Network Assurance (VNA) releases r20.2.4 and older

Cause

The system was running an IBM Java JDK.

An example of an IBM Java version that might cause this issue:

[[email protected]]# java -version
java version "1.8.0_251"
Java(TM) SE Runtime Environment (build 8.0.6.10 - pxa6480sr6fp10-20200408_01(SR6 FP10))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20200402_443261 (JIT enabled, AOT enabled)
OpenJ9 - 35ef566
OMR - 4bca4f4
IBM - 55acf4a)
JCL - 20200407_01 based on Oracle jdk8u251-b08

Resolution

The Virtual Network Assurance (VNA) product requires an Open or Oracle based JDK.

It does not work with, and does not support, IBM or other manufacturer JDK implementations.

It does not work with, and does not support, JRE java installs, only Open or Oracle based JDK installs.

An example of an appropriate supported Java JDK for use with VNA is:

[[email protected]]# java -version
openjdk version "1.8.0_212"
OpenJDK Runtime Environment (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)

Additional Information

When using the engineering and support provided testing script viptool:

  • The error is seen when running it without the --disable-ssl-verify option.
  • The error is not seen when running it with the --disable-ssl-verify option.

Per engineering request defect ID DE478257 has been created. Through this defect the VNA installation script will be updated to no longer succeed in the presence of a Java JRE, or an unsupported JDK type. This was implemented starting with the following releases.

  • r20.2.5
  • r21.2.1

Upgrade to r21.2.1 or newer releases to resolve this issue.

Attachments