Known issues with the Probe for Cisco APIC
This section explains some known issues with the Probe for Cisco APIC.
Probe requires operating systems that support 32-bit system libraries
The OIDK Framework 2.0 (
which is required by the probe, does not support the 64-bit binary
The current OIDK implementation
is hard coded to use the 32-bit binary in
which may cause issues for operating systems that do not support a
32-bit runtime environment.
Console error occurs when the probe shuts down due to invalid credentials
Java stack traces may appear in the standard output console that is used to run the probe process when an error is encountered during the initial connection attempt.
Best practice to minimize the risk of the probe losing subscriptions against Cisco APIC
If the probe is deployed in an environment where intermittent network issues could happen due to network instability, you should set to a lower time interval the values set for the loginRefreshInterval property (whose default is 180) and the subscribeRefreshInterval property (whose default is 30). This allows the probe to attempt an additional refresh request before the subscription times out in case the earlier attempts failed due to connection issues. The loginRefreshInterval and subscribeRefreshInterval properties are set in the ciscoApicTransport.properties file.
Recommendation When Using TLS 1.2
If the probe is running on Java 6, it does not support the TLS 1.2 SecurityProtocol. To support TLS 1.2 SecurityProtocol, the probe requires Java 7.
You have the following options:
- Install OMNIbus 8.1 (because it comes with JRE 7).
- Or, install a separate JRE 7.