NetBox 4.7.2 adds InfiniBand interface types and cable hooks
NetBox v4.7.2 released September 29 with enhancements including Cable.update_dependent_objects() hook for cable path rebuilding and InfiniBand 2X interface types (HDR100, NDR200, XDR400). v4.7 required PostgreSQL 15+ and Redis 6.0+, unified Service port mappings, and introduced cooling infrastructure modeling and channelized subinterfaces.
Why it matters NetBox 4.7 series adds production-scale features—cooling/power tracking, HPC interface types, and REST API background processing—critical for data center and AI cluster modeling in enterprise NSoT deployments.
NetBox v4.7 (September 2026) introduced cooling infrastructure modeling, channelized subinterfaces, multi-protocol application services, module bay types, relocating installed modules, background processing for REST API requests, per-object errors for bulk operations, pre-rendered config context data, and snapshot-aware event rule conditions. Breaking changes require infrastructure upgrades: PostgreSQL 14 support dropped (15+ required), Redis 5.x dropped (6.0+ required). The protocol/ports unification on ipam.Service models to port_mappings supports multiple protocols per service, improving IPAM flexibility for multi-protocol environments. v4.7.1 added default module type profiles for transceivers and InfiniBand 2X interface types including HDR100, NDR200, and XDR400, directly addressing next-gen HPC and AI data center requirements. The Cable.update_dependent_objects() hook fixes a critical issue where cable-write operations bypassing ORM save() would orphan dependent objects, a common pain point in large inventory imports.
Read the original at netboxlabs.com ↗