Difference between revisions of "Honeycomb/Releases/1609/Honeycomb and ODL"

From fd.io
Jump to: navigation, search
(Initial version)
 
(→‎Unable to open SSH session due to invalid crypto configuration)
Line 27: Line 27:
  
 
It probably means BouncyCastle provider is not properly configured on the ODL side.
 
It probably means BouncyCastle provider is not properly configured on the ODL side.
−
As a workaround start honeycomb with -Dorg.apache.sshd.registerBouncyCastle=false
+
As a workaround start honeycomb with
 +
 
 +
  -Dorg.apache.sshd.registerBouncyCastle=false
 +
 
 
As a result 1024 bit DH group will be used for SSH key exchange.
 
As a result 1024 bit DH group will be used for SSH key exchange.

Revision as of 12:08, 13 September 2016

Honeycomb and ODL

Honeycomb can be managed using ODL as any NETCONF-enabled device. Please follow https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf for detailed instructions how to mount and connect to a NETCONF device

Troubleshooting

Unable to open SSH session due to invalid crypto configuration

If ODL fails to open ssh session due to InvalidAlgorithmParameterException, e.g.: 

 2016-09-13 13:52:34,852 | WARN  | NioProcessor-3   | ClientSessionImpl | 180 -
 org.apache.sshd.core - 0.14.0 | Exception caught
 java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64,
   and can only range from 512 to 2048 (inclusive)
     at com.sun.crypto.provider.DHKeyPairGenerator.initialize(DHKeyPairGenerator.java:120)
       [sunjce_provider.jar:1.8.0_45]
     at java.security.KeyPairGenerator$Delegate.initialize(KeyPairGenerator.java:674)
       [:1.8.0_45-internal]
     at java.security.KeyPairGenerator.initialize(KeyPairGenerator.java:411)
       [:1.8.0_45-internal]
     at org.apache.sshd.common.kex.DH.getE(DH.java:65)[180:org.apache.sshd.core:0.14.0]
 [...]
 2016-09-13 13:52:34,852 | DEBUG | NioProcessor-3   | ClientSessionImpl | 180 -
 org.apache.sshd.core - 0.14.0 | Closing ClientSessionImpl[admin@/127.0.0.1:2835] immediately

It probably means BouncyCastle provider is not properly configured on the ODL side. As a workaround start honeycomb with 

 -Dorg.apache.sshd.registerBouncyCastle=false

As a result 1024 bit DH group will be used for SSH key exchange.

Retrieved from "https://wiki.fd.io/index.php?title=Honeycomb/Releases/1609/Honeycomb_and_ODL&oldid=2960"