RPC error "expecting </configuration>" returned on use of GetConfig about go-junos HOT 10 OPEN

It might be a bug. Thanks for catching this and I'll take a look at it!

from go-junos.

Actually, I see the problem. You have the parameters backwards. The "section" is supposed to be the second (optional) parameter. If you just specify the following:

config, err := jnpr.GetConfig("text")

Then you will get the entire config, vs something like:

config, err := jnpr.GetConfig("text", "interfaces")

I will have to work on the MX parsing, as it's not coming through as it should. Everything else should work ok - I tested it on a QFX, EX, and SRX.

from go-junos.

OK, I think I know what might have happened. I stumbled upon your library from this blog entry. One of the examples on the page is the following:

routing, _ := jnpr.GetConfig("routing-instances", "text")  
fmt.Println(routing)

I just used that example as a start for my program and didn't double check with the GoDoc documentation. The RPC error returned wasn't obviously clear (to me), so it didn't dawn on me to double-check the docs to make sure I was using the function correctly.

Switching the argument order in my function call made it work, as you explained. Thanks for looking into it!

Do you need me to test anything with an MX?

Thanks,
-Martin

from go-junos.

Ah...forgot to update my blog when I changed the function parameters around :) Thanks a lot!

Yeah, if you wouldn't mind testing, that would be great. I spent just a couple minutes diving into it yesterday, and apparently the XML response on the "get-software-information" RPC call is different than that of the other platforms.

from go-junos.

I tested using routing, err := jnpr.GetConfig("text") on an MX960 running 14.1R4.10 and was able to retrieve the config without any error. XML format retrieval also worked fine.

from go-junos.

Do you have dual routing engines?

from go-junos.

Yes.

from go-junos.

I'm running 14.2R5.8 on our MX104's and get an error. Must be tied to the model. I'll dig into it more. Thanks for the continued effort!

from go-junos.

My pleasure!

from go-junos.

@scottdware if you can provide me with the sanitized XML output of the equivalent SSH command, and the error you get from go-junos, I can try to fix it. I don't have access to any dual-RE MX gear, though.

from go-junos.