[BETA] 1.7.0 beta thread

[Tomas]

Sorry for the late reply, was waiting for fixes to a few of these issues in Beta3, which is now available.
(so a few of these issues should already be fixed)

One enhancement that would be AWESOME is if when you select devices that you could pick NetXMS container names and then it would maintain that list of devices that this applies to based on that. Would just help to provide us with more reliable automation as the containers we use / import would insure that all devices are there and over time we do not miss any or leave ones that are not valid any longer.

We talked with the team today on how to best implement this.
(since this needs to work not just for NetXMS, but also for Zabbix, and other future importers we want to add)

We decided on this:
- Importer will be able to Tag devices (using already present Tag features) that they import
like with the NetXMS importer, it would tag devices per container they were imported from.
for Zabbix, it would tag from Device Groups in Zabbix, etc.

- you will be able to run a Mass Config Push on a Tag
so setting up a confg push preset to work on a Tag would push it to all devices in the tag

- since Tags will automatically be updated by importers, this should do what you outlined

Would this be acceptable?

How about widening the command entry window as well from the web site. Much easier to visualize if there is not so much wrapping taking place. Likely most people these days have pretty decent resolution displays for this stuff and not the sort of thing you are likely (though I am sure some will) do mobile.

Will do.

Also, assuming that we will at some point be able to schedule these items to run?

We didn't include scheduling functionality with Config Push because after discussing it, we agreed that most users will just want to push on-demand.
If you have some use-cases where a scheduled push would be wanted, we would be glad to hear them

What about options to create some sort of script repository as well or add a forum section so that people can discuss this and share what is working.

Agreed, will create a new "Automation" forum section.

Yes, I agree you need to show the log for the failed ones as well as the ones that do not fail so we have something to go on.

Done, now present in the Beta3.

This morning that job was now IDLE, but nothing more got logged including the list of devices that were not updated. My guess is that the other standard backup jobs running pushed the status to IDLE.

We think we found the bug, should be fixed in Beta3.

However, this brings me to another feature suggestion for this and that is the ability for Run Now to run against only failed / skipped devices via some sort of option. This was you can run the job multiple times without updating the working units over and over since this may cause a failure as it would here since the host is already added for the package source.

I think these 2 features should solve that:
1) implement a right-click menu on output groups (including error groups)
2) in the right-click menu, add 2 options:
- rerun on these devices
- set these devices as Config Push target (would over-write currently selected devices)

Do you think that would be good enough?

[Tomas]

1.7.0-beta3 is released today.
Original post updated to reflect this.

Changes from beta2:

Code: Select all

Features:
  "Network scan" feature upgrades:
    - fixed scanning IPs even after a scan has been stopped
    - fixed not showing "Last run:" when a scan was stopped
    - fixed ping result not being correct in certain cases

  "Mass config push" feature upgrades:
    - Added "Expand output window" to config push output
    - Output is now shown even for error output groups
    - fixed errors saving opened tabs state on logout
    - fixed not showing "Last run:" when a push was stopped

Fixes:
  "enable passwords" feature fixes:
    - fixed enable password discovery not working
    - fixed multiple other issues around enable password functionality

  Fixed backup failing for some vendors
  Added missing texts in "Credentials"
  Fixed account with READ_ONLY role could access 'Adding the first device' screen

[SeanCTS]

Can we get more info when Discovery / backups fail?

The popup as well as the email notifications only provide the number of devices that succeed or fail... but not which ones that fail. Would be useful to know.

I have close to 100 devices in my Unimus and having to check the info on each one is brutal. Could have sworn the 1.6x had that. If this is a feature request, I'll pop the request/question in the right forum.

[Tomas]

Could have sworn the 1.6x had that. If this is a feature request, I'll pop the request/question in the right forum.

On the Dashboard, there is a failed jobs log.
That will have a list of all devices that failed, and the reason the job failed.

Is that sufficient, or should we do something more in that regards?

[SeanCTS]

On the Dashboard, there is a failed jobs log.
That will have a list of all devices that failed, and the reason the job failed.

Is that sufficient, or should we do something more in that regards?

Ahh, there it is. That works for me. However, if you could have the 'option' to send the verbose failure log as an email, that'd be a nice touch.

[lweidig]

We talked with the team today on how to best implement this.
(since this needs to work not just for NetXMS, but also for Zabbix, and other future importers we want to add)

We decided on this:
- Importer will be able to Tag devices (using already present Tag features) that they import
like with the NetXMS importer, it would tag devices per container they were imported from.
for Zabbix, it would tag from Device Groups in Zabbix, etc.

- you will be able to run a Mass Config Push on a Tag
so setting up a confg push preset to work on a Tag would push it to all devices in the tag

- since Tags will automatically be updated by importers, this should do what you outlined

Would this be acceptable?

Yes, this can definitely be made to work in our environment and will assist with automating things.

We didn't include scheduling functionality with Config Push because after discussing it, we agreed that most users will just want to push on-demand.
If you have some use-cases where a scheduled push would be wanted, we would be glad to hear them

This is simple, we want the ability to upgrade the firmware in our routers at off peak time which is about 3:00am. We would also like to remain sleeping while this takes place and therefore need the ability to update via a schedule

I think these 2 features should solve that:
1) implement a right-click menu on output groups (including error groups)
2) in the right-click menu, add 2 options:
- rerun on these devices
- set these devices as Config Push target (would over-write currently selected devices)

Do you think that would be good enough?

Yes, that would allow us the ability to run through devices that did not get the update properly.


We will head out and get beta3 installed so that we are able to provide additional feedback. Thanks!

[Tomas]

1.7.0-beta4 is released today.
Original post updated to reflect this.

Changes from beta3:

Code: Select all

Features:
  "Mass config push" feature upgrades:
    - increased Commands max length to 65k characters
    - improved handling of too many characters im "Commands" area
    - added support for line splitting commands on MikroTik RouterOS ('\' at end of the line)
    - "Save" and "Run now" buttons will now properly update immediatelly on "Commands" text change
      (previously it required the "Commands" area to lose focus)

  Added support for:
    - HP 1950 switches

Fixes:
  Fixed "Mass config push" not working on PostgreSQL

[Tomas]

1.7.0 has been released, and this topic is getting locked:
viewtopic.php?p=1110#p1110

A warning to Beta users, due to cross-database (in)compatibility issues, we had to drop your commands from each Mass config push preset. Presets themselves will not be lost, just the commands inside each preset.

We are sorry about this, but migration was not possible from the Beta builds.