In traditional ADC architectures, a network interface change — adding a VLAN, creating a bond, switching MTU to jumbo frame — typically requires a device restart or a planned maintenance window. This turns every network change into a project: approval cycle, application freeze, late-night window, post-change verification.
Live LACP bond setup is not supported in many products; you either configure it at deployment or stop services to change it. MTU changes can reset active connections. SR-IOV virtual functions require an external tool to manage, adding operational overhead outside the ADC.
Tenant isolation is a separate problem. Moving an interface from the default network domain to a tenant domain is unsupported on most ADCs; traffic must be separated through extra routing layers outside the device, increasing architectural complexity and error risk.
The right model decouples interface changes from service disruption. Changes should be applied live, only what changes should be touched, and all interface types should be accessible from a single management model.
TR7 Dynamic Interface Management closes this gap: network interface changes no longer require a maintenance window, and delta sync ensures only what needs to change is touched.
TR7 treats interface management not as a separate configuration step but as a natural part of the management model operators use while services are running.
TR7 presents interfaces to the operator with their real operational meaning: Physical, VLAN, Bond, LACP, Bridge, V-ETH, V-ETH(peer) and VXLAN. The operator selects the interface type they need; TR7 applies the required steps in the background.
When a configuration changes, TR7 does not rebuild the entire network. Added, deleted and edited interfaces are separated; only the necessary steps are applied. This reduces the risk of unnecessary contact with live services.
An interface can be moved between TR7 Route Tables. For example, a physical interface in the default domain can be dedicated to a tenant; a tenant's V-ETH(peer) can be paired with a different Route Table. This makes it explicit which routing domain traffic enters and exits through.
VXLAN interfaces enable overlay segments across different physical networks. For multi-tenant, inter-data-center extended networking and isolated service segment scenarios, TR7 delivers the overlay network within the same interface management model.
TR7 Dynamic Interface Management unifies eight interface types in a single management model and applies all changes live.
Physical network interfaces are managed directly in the TR7 UI. Up/down control, MTU change, MAC editing, interface rename and Route Table migration can all be done live.
A VLAN interface can be created on top of a Physical, Bond or LACP interface. Multiple tenant or service subnets can be separated over a trunk port. VLAN ID, parent interface and Route Table binding are managed from the UI.
Multiple physical interfaces can be grouped under a Bond. In redundancy-focused scenarios such as active-backup, traffic continues over the remaining member if a link goes down. Bond members are selected from the UI.
An LACP interface can be created for link aggregation. Multiple physical ports operate as a single logical link in sync with the switch side. LACP and bonding parameters are manageable from the UI.
Multiple interfaces can be grouped under a Bridge for L2 bridging. Used for transparent deployment, VM/container connectivity or controlled L2 transit between two segments.
Used as a virtual Ethernet interface. Provides a virtual endpoint separated from the parent interface in virtualized or tenant-based networks. Particularly useful for VM or isolated service egress scenarios.
Provides a two-ended virtual connection. One end can reside in one Route Table and the other in a different Route Table. This establishes a controlled, firewall-filterable connection between two isolated domains.
With VXLAN, the same logical segment can be extended across different physical networks. For multi-tenant data center, service segmentation and remote environment connectivity scenarios, interfaces are managed from the UI.
Interfaces can be moved to different TR7 Route Tables based on tenant or service requirements. This simplifies the management of different routing domains on the same device and ensures traffic flows through the correct isolation domain.
MTU can be changed live. Switching to jumbo frame for high-throughput, storage, backup or direct backend connections does not require a device reboot.
Interface MAC address can be changed from the UI. This simplifies operations in migration, compatibility and tenant isolation scenarios.
Interface admin state can be toggled from the UI. Interface names can be changed. Operators complete maintenance, testing or temporary deactivation without dropping to the CLI.
Management, cluster sync or system-critical interfaces can be placed on a protected list. Accidental deletion or migration of these interfaces is blocked.
Parent/child relationships are tracked for VLAN, V-ETH, VXLAN and Bridge interfaces. When a parent interface is deleted or changed, dependent child interfaces are evaluated safely.
TR7 monitors separately whether an interface is administratively up and whether the physical link is connected. Conditions such as "interface up but no cable" become visible.
Hardware virtual functions are configured and managed from the UI. A VF can be assigned to a specific tenant or to a service that requires high packet rates.
Dynamic interface management is not just UI convenience — delta computation, fault tolerance, telemetry and system safety all work together.
On a configuration change, TR7 computes the current state and applies only added, deleted or edited interfaces. The entire network stack is not rebuilt. This is both faster and reduces the risk of unnecessary impact on active services.
Interface, IP and route addition operations run in parallel. If one step fails, the others continue. This behavior prevents the system from halting entirely on partial configuration changes.
If the SR-IOV VF count is entered as 1, the system automatically normalizes to 0; a minimum of 2 VFs is required. Trust and spoof-check settings are applied automatically for each VF.
Additional parameters such as LACP rate, miimon and xmit_hash_policy can be passed for LACP interfaces through the UI. Operators complete switch-compatible link configuration without dropping to the CLI.
If the loopback interface (lo) is down, TR7 brings it up automatically. This ensures that the loopback connectivity critical for system isolation and internal service communication remains uninterrupted.
TR7 tracks whether an interface is administratively up and whether the physical cable is connected as separate parameters. The "admin up but no carrier" condition can be detected and surfaced to operations teams.
A new VLAN can be created from the UI without bringing down running services. New subnets are added over a trunk on existing interfaces; no maintenance window needs to be scheduled.
Two physical interfaces are grouped under an LACP bond. LACP negotiates with the switch; automatic failover fires the moment a link drops. Redundancy configuration is completed live.
Multiple VFs are opened on a hardware NIC and each VF can be dedicated to a tenant or service. Software overhead is minimized for hardware-speed packet processing.
A V-ETH(peer) pair is established between two isolated network domains. Each end is kept in a different Route Table; the connection can be filtered by a firewall. Controlled inter-tenant transit is achieved.
MTU is raised live for backend connections that need high throughput, storage or backup performance. Jumbo frame is activated without a device reboot or service interruption.
Two backend segments are bridged into the same L2 domain, and the ADC behaves transparently. Isolated L2 transit is provided for VM or container network connectivity.
Physical, VLAN, Bond, LACP, Bridge, V-ETH and VXLAN interfaces managed live from the TR7 UI. Let us walk you through a live setup on your own infrastructure.