Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

NCM HP-2524 models reboot with config download attempts

I opened a case with S/W on this. No resolve.

I have several hundred HP-2524 class switches.

When I run a config-download job (or manually do the config download) using NCM Job, if the login/enable password is incorrect on the HP system (does not match what is set up as device login credentials in NCM).. these systems REBOOT/RELOAD. The S/W support said to use one of the defined device command settings.. there are only two defined in there : HP and HP J4865A.

I tried both of these, auto-determin, generic, etc.. but if the enable password does not match, the switches reload. This does no occur on any other model of HP switches (I have several models).

Does anyone have any info on how to modify/create a device command template ? Anyone have HP-2524s having this issue.

Note: if the enable password matches, the switch does not reload. The problem is if field admin does not update with the latest enable pass, when I run the NCM jobs, these 2524 switches reload during the config-download script from NCM.

Find more posts tagged with

Accepted answers

juan_kaliente

Worked with problem with SW support,, using different device templates. The resolve for the HP-2524 switches was to add in to the Solarwinds registry settings 'Transfer Attempts Count' = 1. Apparently more than one try with incorrect enable password rebooted these switches. This only occured using the NCM config download. However, when manually trying to login with incorrect enable password (several times), these switches did not reboot.. only with the config download script.

All comments

mleinio

Do you use SSH or telnet? I have bad experiences in ProCurve SSH support (see for example).

I haven't noticed this incorrect password problem, but I will definitely test it. The installation we manage has currently about 1600 ProCurves in NCM and NPM, most of them are 2512/2524 and 2510-24.

One problem in NCM ProCurve support is that NCM does not understand very well the output of ProCurve switches. ProCurve CLI sends lots of cursor control codes while you enter the commands and NCM is confused about them. I have reported this to SolarWinds at some point. This is something that you cannot fix in device templates, it should be fixed in NCM code. Result of this is that commanding ProCurve switches with NCM is painfully slow (NCM just waits for timeout before proceeding to next command).

Combined to the fact that ProCurve 2512/2524 sometimes reboot when logging in with SSH this means that commanding ProCurve switches with NCM is very challenging.

Markku

juan_kaliente

mleinio

This sounds interesting, can you provide more detailed information about the solution? What is the exact registry setting?

We shouldn't have any problems with the passwords but it is still worth of trying.

Markku

juan_kaliente

regedit: HKEY_LOCAL_MACHINE / SOFTWARE / SOLARWINDS.NET / Configuration Manager / Settings.

Transfer Attempts Count = 1

That's it.

m_roberts

Hi Juan,

Are these switches running in Menu or CLI mode?

I ask as I have switches running in Menu mode I need to create a template for and am having trouble identifying the prompt, as the last output after the login is the date/time stamp.

If you have created a custom template, could you share in the content portal?

thanks

juan_kaliente

CLI Mode.