Inner Range has released Integriti V25.1, and for facilities managers, IT managers, and integrators running High Availability access control architectures across commercial buildings, strata complexes, or multi-venue club sites, two changes in particular are worth understanding before your next maintenance window. The update introduces automatic controller load balancing for HA deployments and a redesigned Firmware Update dialog that makes version hygiene across distributed controller networks significantly more manageable. Neither change is cosmetic \u2014 both address real operational friction points that anyone maintaining a mid-to-large Integriti site will recognise immediately.<\/p>\n\n
According to Inner Range’s release announcement, V25.1 delivers two headline changes:<\/p>\n\n
Automatic Controller Load Balancing for High Availability Architectures.<\/strong> HA configurations in Integriti pair redundant servers so that if the primary fails, the secondary takes over without dropping access control or alarm monitoring. The challenge with HA has always been that in practice, one server tends to carry a disproportionate processing load during normal operation \u2014 controllers connect to whatever they connected to first, and they stay there. V25.1 introduces automatic load balancing that distributes controllers more evenly across the HA pair. This feature requires firmware version 25.1.0 or later on the controllers themselves, which ties directly into the second change.<\/p>\n\n Redesigned Firmware Update Dialog.<\/strong> The updated interface now surfaces recommended firmware versions for connected hardware and actively flags controllers and LAN Modules that are running out-of-date firmware across the site. Rather than requiring a technician to manually cross-reference each device against a version matrix, the system presents that information in a consolidated view and identifies what needs attention.<\/p>\n\n If you operate an Integriti HA deployment, the load balancing improvement has a direct prerequisite: controller firmware must be at 25.1.0 or above before the feature activates. That means a firmware update campaign across your controllers is not optional if you want the benefit. For large sites with many controllers and LAN Modules distributed across floors, plant rooms, and car park levels, that has historically been a time-consuming and error-prone process \u2014 which is exactly why the redesigned Firmware Update dialog matters. The two features are operationally linked.<\/p>\n\n For facilities and IT managers, the practical implications worth discussing with your integrator include:<\/p>\n\n Sites not running HA configurations will see less immediate operational impact from the load balancing feature, but the improved Firmware Update dialog is relevant to any Integriti deployment of meaningful scale. Version consistency across controllers is a security hygiene requirement, not just a performance consideration \u2014 outdated firmware can carry unpatched vulnerabilities, and in an access control system, that has direct physical security consequences.<\/p>\n\n From where we sit \u2014 planning, installing, and maintaining Integriti systems across NSW commercial, strata, and club sites day to day \u2014 the firmware update tooling improvement is the change we’re most immediately glad to see. Keeping controller and LAN Module firmware consistent across a site with dozens of devices has always required disciplined record-keeping on our end and careful sequencing on-site. Anything that reduces the risk of a technician missing a device, or a client site drifting into a mixed-firmware state that creates unexpected behaviour, is a genuine operational improvement. The new dialog consolidating that visibility into the software itself is the right place for it.<\/p>\n\n On the load balancing side, HA deployments are increasingly common as building owners and strata managers come to treat access control uptime with the same seriousness they apply to fire and CCTV. An HA system that quietly concentrates load on one node isn’t fully delivering on its resilience promise. Automatic balancing closes that gap \u2014 provided the firmware prerequisite is met, which reinforces the point that firmware maintenance isn’t a background task to defer indefinitely. If your Integriti site is running HA and you haven’t had a firmware review in the past twelve months, this release is a reasonable prompt to schedule one.<\/p>\n\n Original source: https:\/\/www.innerrange.com\/post\/integriti-v25-1-smarter-load-balancing-and-streamlined-firmware-updates<\/p>","protected":false},"excerpt":{"rendered":" What Changed in Integriti V25.1 Inner Range has released Integriti V25.1, and for facilities managers, IT managers, and integrators running High Availability access control architectures across commercial buildings, strata complexes, or multi-venue club sites, two changes in particular are worth…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-34","post","type-post","status-publish","format-standard","hentry","category-vendor-industry-news"],"yoast_head":"\nOperational Implications for Your Site<\/h2>\n\n
The Mallen Perspective<\/h2>\n\n