Session Trace - SSH ?

Is this an option as my devices that I am having issue with does not allow telnet. I can't seem to get Juniper MX80 router to download config, I am using the out of box device template, its able to test connect and I have verified the XML config. I am out of ideas as I get error "Connectivity issues, discarding configuration (or configuration is too short)"

Find more posts tagged with

juniper

ncm

Accepted answers

tdanner

That's weird. I would just open a ticket with SolarWinds support for that one.

All comments

wlipford

Got the trace to work - here is the output.

nmsinfra@NYC06>

nmsinfra@NYC06> set cli complete-on-space off

set cli complete-on-space off

Disabling complete-on-space

nmsinfra@NYC06> set cli screen-width 0

set cli screen-width 0

Screen width set to 0

nmsinfra@NYC06> set cli screen-length 0

set cli screen-length 0

Screen length set to 0

nmsinfra@NYC06> show ${configuration | display set}

show ${configuration

syntax error, expecting <command>.

nmsinfra@NYC06> show ${configuration |

syntax error, expecting <command>.

nmsinfra@NYC06> show ${configuration| display

syntax error, expecting <command>.

nmsinfra@NYC06> show ${configuration|display set}

syntax error, expecting <command>.

nmsinfra@NYC06>

********************************************************************

here is the base juniper template.

<Configuration-Management Device="Juniper Devices" SystemOID=" 1.3.6.1.4.1.2636">

</Commands>

</Configuration-Management>

tdanner ?

tdanner

That's weird. I would just open a ticket with SolarWinds support for that one.

jemertz

Somewhere you're adding some extraneous characters to the command as listed in the template.
First I'd verify that the template that you pasted for us is the template being used on the device. Edit Properties on the device and under NCM -> Communication choose this template instead of letting it autodetermine.
I'm not able to locate a place where downloading the config specifies to use ${DownloadConfig} but it seems like somewhere this isn't being parsed right. If you can't locate it either, Solarwinds Support might be the only one who can help as it sounds like a bug in NCM template parsing.

wlipford

Turns out the "Generic Juniper" Template and my Custom Juniper Template were both being applied. Once I turned off the Auto detect for the Generic one and made sure the Custom template was set for the Juniper devices in question it worked.

I still see duplicate commands being sent, just the correct ones. I don't have time to figure that out just needed it to work. Now on to the next 10,000 devices.

jemertz

Glad I could help identify the problem.