Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error connecting to Juniper MX480 #8

Closed
GoogleCodeExporter opened this issue Jun 11, 2015 · 1 comment
Closed

Error connecting to Juniper MX480 #8

GoogleCodeExporter opened this issue Jun 11, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

I'm trying to establish a Netconf session with a Juniper MX480 router. I'm 
getting errors during initial negotiation.

I have followed these steps:

1. Open client example with:

$ netconf-client 


2. Establish verbosity level with:

netconf> verbose
Verbose level set to VERBOSE


3. Connect and authenticate to the Juniper MX480 router:

netconf> connect --login <user> <ip_address> 
libnetconf VERBOSE: Keyboard-interactive authentication
libnetconf ERROR: Authentication failed (Authentication failed 
(keyboard-interactive))
libnetconf VERBOSE: Password authentication (host <ip_address>, user <user>)
<user>@<ip_address> password: 


4. Getting the following errors:

libnetconf ERROR: No base capability found in the capabilities intersection.
libnetconf ERROR: Unsupported NETCONF protocol version (-1)
libnetconf ERROR: Malformed message received, closing the session 22273.
connect: connecting to the <ip_address> failed.
netconf> 


I don't know how to get logging of my session to see actual Netconf messages, 
but I was using netopeer and these was my issue:
http://code.google.com/p/netopeer/issues/detail?id=8&can=1

Original issue reported on code.google.com by juliocar...@i2cat.net on 28 Jun 2013 at 11:09

@GoogleCodeExporter
Copy link
Author

To get more detailed log, run configure script with --enable-debug option:

./configure --enable-debug --with-examples

and in the netconf-client's shell, use debug command:

netconf> debug


I checked the log you posted to the netopeer project. You were right, problem 
is in the namespace of the juniper's <hello> message, which is completely 
missing. Juniper breaks RFC 6241 (appendix B) - libnetconf checks all messages 
(hello, rpc, rpc-reply, notification) to be in the 
urn:ietf:params:xml:ns:netconf:base:1.0 namespace as NETCONF protocol 
specification defines.

Original comment by rkre...@cesnet.cz on 28 Jun 2013 at 2:17

  • Changed state: NotBug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant