Interfaces List (Cluster)

What Is Interfaces List?

Interfaces List are the physical or virtual connection points that allow the TR7 device to communicate with the network. Each interface forms the fundamental building block for IP addresses, routing rules and the network configuration.

In the TR7 architecture, network management is designed around the Route Table. This structure allows isolated virtual routing domains (VRF-like) to be created on the same device and different network segments to be managed independently.

The Interfaces screen is the central management point for all the network interfaces defined on the TR7 device. From this screen:

• The status of physical and virtual interfaces is monitored,
• IP address assignments are made,
• Static routing rules are defined,
• Route tables are created and managed,
• The network topology is reviewed visually.

Cluster / Standalone

This page describes the screen that is seen while clustering (cluster) is enabled. All the functions of the standalone screen are valid here as well; the clustering screen extends it with the peer device column, two-colored status indicators, VIP rows and per-device operations. For the standalone version see the Interfaces (Standalone) page.

8 Interface Types

Flexible structure

ETH · VLAN · VXLAN · V-ETH · V-ETH(Peer) · Bond · LACP · Bridge

Route Table

Network isolation

VRF-like, multi-tenancy

Status Monitoring

Color-coded

Up · No link · Down · Absent · the VIP statuses

Topology

Visual map

Hierarchical interface view

Why Is Interfaces List Important?

In modern data center environments, network interfaces are not merely physical connection points; they are the fundamental building blocks of traffic management, security isolation and high availability architectures.

Correctly configuring network interfaces on TR7 has a direct impact on load balancing performance, firewall effectiveness and overall system stability. A misconfigured interface can lead to traffic interruptions, security holes or performance problems.

TR7's route table based network architecture offers flexibility beyond traditional network configurations:

• Multi-Tenancy: Secure multi-tenant architectures can be built by fully isolating different customers' traffic from one another on the same physical device,
• Traffic Segmentation: Management, production and test traffic can be separated into different route tables to provide security and performance isolation,
• VRF-Like Configurations: Each route table can have its own routing rules and DNS configuration,
• Flexible Interface Types: Complex network topologies are supported through various virtual interface types such as VLAN, LACP, Bond and Bridge.

Thanks to correctly configured network interfaces, service interruptions are minimized, firewall and load balancing policies are enforced effectively, network traffic can be monitored and rapid intervention is possible in maintenance/failure scenarios.

The Differences of Cluster Mode

When clustering is enabled, the interface list screen extends so as to monitor the two devices in a single view. The devices are referred to on the screen by their machine names (hostname); a label such as "device 1 / device 2" is not used.

• The two-device IP view: The IP column is split in two; the header of the first column is the machine name of this device and that of the second one the machine name of the peer device. The Interface IPs show a separate address for every device; the VIPs appear in both columns with the same address, with the (M) / (S) suffix.
• Two-colored status indicators: The interface, route and topology indicators consist of two half circles: the left half is this device and the right half the peer device. When the indicator is hovered over, the tooltip starts with the name of the related device.
• Per-device operations: The IP addresses can be enabled and disabled separately for every device (Enable for / Disable for <device name>); from the Details tab of the preview panel the interface can be turned on and off on a single device only.
• The VIP fields: In the IP form the Ip type = VIP option, and in the interface editing form the VIP Communication / VIP Transition fields are seen.
• While the peer device is unreachable: The indicators in the peer device column become Host Is Down (gray) and the VIPs Cluster Connection Is Down (red); the VIP in the column of this device, on the other hand, shows Both VIP Might Be Active (yellow; risk of a collision) if it is active and VIP Must Have Been Activated (red) if it is not.

The IP addresses assigned to the interfaces in cluster mode can be of two types:

Ip type	Description
Interface IP	A device-specific address pair assigned to every device separately (this device / the peer device). It is used for management and device-based access
VIP	A virtual IP address shared between the two devices, running on the active (Master) device; the Slave device waits in reserve. It is used for the service traffic

The VIP Transition Mechanisms

The VIP addresses work based on VRRP; the failover behavior is determined by the fields in the Edit Interface form of the interface the VIP is on:

Field	Description
VIP Communication / VIP Communication (v6)	The Interface IP pair to be used for the VRRP communication between the devices (separate for IPv4 and IPv6). A free address is not entered; in the list only the Interface IPs whose address is defined for both devices on this interface are offered in the form ip/cidr - peer ip/cidr; None can be selected. Without a pair being selected, the VIPs on the interface do not become active
VIP Transition Duration (s)	The VRRP advertisement interval; the default is 3, the range is 1 – 1000 seconds. A low value provides faster failover but may lead to unnecessary transitions in temporary network fluctuations
VIP Transition Method	Only VRRP (VRRP heartbeat only) · TR7 Link Check (interface link check) · TR7 GW Check (default gateway check) · TR7 Link and GW Check (both); the default is Only VRRP

The virtual router ID is not entered in the form; when a VIP communication pair is selected, it is assigned automatically by TR7. A misconfigured VIP communication may lead to both devices being Master (split-brain); this situation appears in the list as Both VIP Is Active.

Supported Interface Types

TR7 supports various interface types to meet different network requirements. Each type is optimized for specific scenarios.

Type	Description	Use Case
ETH	Physical Ethernet interfaces. Interfaces that exist physically on the device or are assigned in a virtualization environment	Basic network connectivity, management access
VLAN	IEEE 802.1Q VLAN interfaces. Creates logical segments on a physical interface (ID: 2–4094)	Network segmentation, traffic isolation
VXLAN	VXLAN (Virtual Extensible LAN) overlay interface; it tunnels a Layer-2 network over Layer-3	Overlay networks, L2 extension between locations
V-ETH	Virtual Ethernet interfaces (macvtap). A virtual interface with an independent MAC address on a physical interface	Container/VM connectivity, network virtualization
V-ETH(Peer)	Virtual Ethernet pair. A two-ended virtual interface connection	Communication between route tables
Bond	A bonding interface that combines multiple physical interfaces (Balance-rr / round-robin)	Bandwidth, simple load distribution
LACP	IEEE 802.3ad Link Aggregation. Dynamic load balancing and redundancy	High bandwidth, active-active redundancy
Bridge	Software network bridge. Connects multiple interfaces to the same Layer-2 domain	Transparent bridging, VM networking

Attention

ETH (physical) interfaces cannot be deleted through the TR7 interface. These interfaces depend on the device's hardware or virtualization environment.

Virtual interface hierarchy: VLAN interfaces can only be created on top of physical (ETH), Bond or LACP interfaces; V-ETH (macvtap) interfaces can be created on top of ETH, VLAN, Bond or LACP. Bond and LACP combine multiple physical interfaces in a single logical interface; for LACP the LACPDU transmission rate can be set as fast (1 sec) or slow (30 sec).

Interface and IP Statuses

On the Interfaces screen the status indicators make the network connection status instantly visible with color codes. In cluster mode every indicator consists of two half circles (left: this device, right: the peer device); an interface that is Up on one device and No Link on the other appears in two colors and points to a physical cable/port problem.

Interface Connection Statuses

Up · greenThe interface is active and a physical connection (carrier) is present.

No link · yellowThe interface is up but there is no physical connection (carrier); the cable is unplugged, the other side is off, etc.

Down · grayThe interface has been shut down administratively (down).

Absent in system · redThe interface is not present in the system.

While the Peer Device Is Unreachable

When the cluster connection with the peer device is broken, all the interface and route indicators in the peer device column become Host Is Down (gray) and the VIPs Cluster Connection Is Down (red). The VIPs in the column of this device, on the other hand, since the status of the peer device cannot be known, show Both VIP Might Be Active (yellow; a possible collision) if the VIP is active on this device and VIP Must Have Been Activated (red) if it is not; while the cluster connection is broken, the Slave device is also evaluated over the Master row.

The Interface IP Statuses

The Interface IPs are colored separately according to the device of the column they are in: Up (green), No Link (yellow), Down and Host Is Down (gray), Absent in System (red), Disabled (light gray, struck through). Since an Interface IP can be disabled on a single device only, the struck-through display may differ per column.

The VIP Statuses

The VIP addresses are listed in both columns with the same address; there is the (M) suffix on the Master side and the (S) suffix on the Slave side. The color and the tooltip text reflect the VIP status of the two devices evaluated together:

Status	Color	Meaning
Master VIP Is Active	green	The VIP is active on the Master device (the expected stable state)
Slave VIP Is Active	green	The VIP is active on the Slave device as a result of a failover
Slave VIP	light gray	The VIP is waiting in reserve on this device (a stable state)
Master VIP Is Absent	yellow	The VIP is not present on the Master device; it is active on the Slave side
Both VIP Might Be Active	yellow	Since the peer device cannot be reached, there is a possibility of a collision
Neither VIP Is Active	red	The VIP is not active on any device
Both VIP Is Active	red	The VIP is active on both devices; a collision or split-brain
VIP Must Have Been Activated	red	The peer device cannot carry the VIP but it has not become active on this device either
Cluster Connection Is Down	red	The cluster connection is broken
Service Communication Problem	red	Communication cannot be established with the zone service on the device of the related column
Interface Is Absent / Interface Is Down	red / gray	The interface the VIP is bound to is not present in the system / is down
No Link	yellow	There is no physical connection on the interface the VIP is bound to
Host Is Down	gray	The related device is off
Disabled	light gray	The VIP has been disabled for this device

If the VIP Transition Method value of the interface is a method other than Only VRRP and the IPv4 VIP Communication pair is defined, when the VIP is hovered over, a sentence that explains the VIP evaluation of TR7 is added to the tooltip text as well (e.g. "Both interfaces are healthy for VIP ...", "Master interface is unhealthy for VIP ...", "VIP ... is disabled for this device.").

Route Statuses

Route active · green dotThe route has been applied to the system and is active.

Gateway reachableThe default gateway monitoring is successful; the ✓ check mark is shown.

Gateway unreachableThe gateway monitoring has failed; the ✕ mark is shown.

The gateway indicator appears only in the row of a default gateway on which a gateway monitor profile is defined and in cluster mode a separate indicator appears for every device: ✓ (successful), ✕ (failed), orange while the evaluation continues and a gray dot if no result has been recorded yet. The tooltip text states from which device it is polled ("... is successful at <device name>"). If no monitor is defined, the indicator is not seen at all.

When the left and the right half of the status indicators are hovered over, a separate tooltip that starts with the name of the related device is displayed for each.

The Route Table Concept

TR7 can create network environments on the same device that are completely isolated from one another. Each route table can have;

• Its own interface assignments,
• Its own IP addresses,
• Its own routing tables,
• Its own DNS configuration,
• Optional dynamic routing protocols (BGP, OSPF, RIP, etc.)

associated with it.

The Default Route Table (DEFAULT): All the physical interfaces are initially assigned to the DEFAULT route table. When no additional route table is created, all the network traffic is managed through this table.

Multiple Route Table Scenarios:

• Customer Isolation (Multi-Tenancy): Isolating different customers' traffic from one another,
• Traffic Separation: Running management and production traffic in different network domains,
• VRF Configuration: Creating virtual routing and forwarding instances,
• Test Environments: Running test and production environments in isolation on the same device.

If more than one route table is defined, the interfaces in a specific table can be displayed with the Route Table filter on the listing screen. For detailed information about creating and managing route tables see the Route Tables page.

The Network Topology View

The Network Topology feature visually presents the hierarchical relationships between the interfaces. Thanks to this view;

• Which virtual interfaces (VLAN, LACP, V-ETH, etc.) are created on top of which physical interface,
• The dependencies between the interfaces,
• The members of the Bond or LACP groups,
• The interfaces attached to a Bridge

can easily be understood. In the topology diagram the interface types are shown with icons and filtering can be done according to the route table; in cluster mode the status background of every node is split in two so as to show the status of the two devices. In complex network configurations the topology view makes it easier to detect configuration errors and to verify the network architecture.

Technical Limits and Rules

The technical limits that apply when creating interfaces and sub-components:

Parameter	Value / Rule
Interface name	1 – 15 characters; it starts with a letter or a digit and can then contain a–z, 0–9, _, . and - (case-insensitive; the validation rule in the interface adding form)
VLAN ID	2 – 4094
MTU	No lower/upper limit is enforced in the form; the common value 1500 is used, 9000 for jumbo frames
LACP transmission rate	fast (1 sec) or slow (30 sec)
VLAN parent interface	ETH, Bond or LACP
V-ETH parent interface	ETH, VLAN, Bond or LACP

How to View?

The following steps are followed in order to list and examine the network interfaces defined on the TR7 device:

1. The Configuration Menu is opened by clicking the TR7 logo at the bottom left.
2. The Network → Interfaces steps are followed.
3. On the screen that opens, all the interfaces defined on the device are listed in table format.
4. By selecting an interface from the list, the details, IP addresses, routes and operation records of that interface are displayed in the preview panel on the right.

TIP

Reaching the page via quick search

Instead of navigating the menu step by step, the related page is reached directly by using the search bar in the bottom left corner of the screen. The search bar opens with the Alt + T shortcut on Windows and Opt + T on macOS; typing the name of the feature being searched for is then sufficient.

For the interfaces that belong to different route tables the Route Table filter, and in order to see the hierarchical structure between the interfaces the Network Topology view, can be used.

Best Practices

• Synchronize the network after a change. After making interface, IP or route changes, synchronize the configuration with the system with Actions → Synchronize Network Config with System; the disappearance of the "Network is under action. Please wait..." warning in the toolbar shows that the operation has been completed.
• Manage the management interface carefully. Making the management interface (usually MGMT) or an interface that carries active traffic Down may cause access to the device to be cut off. Before shutting an interface down, check the IP addresses and the routes on it.
• Verify the structure with the network topology. After adding virtual interfaces such as VLAN, LACP or Bridge, check from the Network Topology view that the hierarchical structure has been formed correctly.
• Use the route table filter. In environments where more than one route table is defined, use the Route Table filter in order to see only the interfaces in the related table.
• Use the device-based operations in order to take a device out of traffic in maintenance. Disable the IPs with Disable for <device name> only on the device to be taken into maintenance; in order to turn the interface off on a single device, use the Up/Down buttons in the Details tab of the preview panel. Restart VIP Service may trigger a failover; use it only when necessary.
• Disabling an IP address vs. deleting it. In order to take an IP address out of use temporarily, use Disable (the configuration is preserved and it can be enabled again); Delete removes the configuration completely.
• Monitor the interface statistics regularly. Open the historical view with Stats by right-clicking the route table cell; for the interface-based dashboard, the Dashboard of the related interface can be reached from the Interfaces tab on the Left Monitor Panel. Abnormal traffic patterns, packet losses or increases in the error counters may point to network problems.

The Interfaces List Screen

The list of all the interfaces defined on the TR7 device is reached by following the Network → Interfaces path. The screen consists of the (A) listing area in which the interfaces are listed and the (B) preview panel in which the details of the selected interface are displayed; the operations of adding, editing and deleting an interface, an IP address and a route are done from this screen.

The Interfaces List Screen (A: the list, B: the preview)

The Listing Area and the Toolbar

The table opens with the following columns by default:

Column	Description
Route Table	The route table the interface is bound to (in the form 1 DEFAULT). While there is a single route table on the device, this column is not seen.
Status	The two-colored indicator that shows the status of the interface on the two devices.
Interface Name	The name of the interface.
Type	The interface type (ETH, VLAN, VXLAN, V-ETH, V-ETH(Peer), Bond, LACP, Bridge).
The name of this device	The header of the column is the Server Name value of this device; the counterparts on this device of the IP addresses assigned to the interface are listed as sub-rows with the status colors. The VIPs appear with the (M) or (S) suffix.
The name of the peer device	The header of the column is the Server Name value of the peer device; it lists the counterparts on the peer device of the same IP records. It is present only in a cluster setup and can be hidden from the column selector.
Routes	The routes defined on the interface as sub-rows in the form destination/CIDR -> gateway; on the default gateway a gateway indicator per device.

The following column is hidden by default and is added from the column selector:

Column	Description
IP Description	The descriptions of the IP addresses assigned to the interface.

The IPs and the routes of an interface are not split into separate rows; they are stacked as sub-rows inside the interface row. The list is offered on a single page without pagination. In narrow windows the Route Table, Type and Routes columns can be hidden automatically in order to make room.

The items in the toolbar are arranged from left to right in the following order; item number 10 is the IP address cell in the table and the last item (Page Information) is located in the information strip below the table.

Columns

Which columns will be shown in the table is selected; the columns other than IP Description are on by default. In the same panel the columns are reordered by dragging and the alignment is selected per column; with the Fit rows to the page button the row height is fitted to the page and with the Reset button the column layout is returned to the default. The layout is stored per user.

Route Table

It is used in order to filter the interfaces in a specific route table. All Route Tables is selected by default. This filter is seen only when more than one route table is defined. For detailed information see the Route Tables page.

Network Topology

It opens the hierarchical topology view of the interfaces in the Network Topology tab. The physical interfaces and the virtual interfaces created on them (VLAN, LACP, etc.) are shown visually; at the top right, filtering based on the route table can be done.

Network Topology

Actions

Actions

The Actions button opens the operation menu for interface management; the forms in the menu open in separate tabs on the same screen:

Operation	Description
Add Interface	Opens the new interface adding form → Add Interface
Add IP	Opens the IP address adding form → Add IP Address
Add Route	Opens the static routing adding form → Add Static Routing
Add Route Table	Opens the new route table creation form → Add Route Table
Delete Interface(s)	Deletes the selected interface(s); it is passive while there is no selection (physical ETH interfaces cannot be deleted)
Edit Interface	Opens the editing form of the selected interface; it is active only while a single row is selected → Edit Interface
Synchronize Network Config with System	Synchronizes the network configuration with the operating system

Synchronization: When Synchronize Network Config with System is selected, the network settings in the TR7 configuration are synchronized with the operating system. While the synchronization continues, the Syncing Network... progress indicator and, when it is completed, All synced is displayed in the status bar of the interface (next to the WEB-CLI button).

WARNING

While a network operation continues, the "Network is under action. Please wait..." warning is seen in the toolbar; until the operation is completed, the delete, edit and synchronize options in the Actions menu and the IP/route adding options in the right-click menu stay passive.

Senkronizasyon - 1

Senkronizasyon - 2

Filter

The Filter button is used in order to filter the interfaces shown in the list according to certain criteria; the button shows the number of active filters with a badge. The strip comes open by default and contains two cards: Route Table (only while there is more than one route table) and Type (the interface type). In the card header there are the filter name and the number of values; when the card is clicked, the values are listed below it with their row counts.

Export

The table is exported as Excel, CSV or PDF by clicking the Export button. In the window that opens, the Filename, Format and Data Source, together with the Columns to be exported, are determined; the remaining fields are displayed according to the format: CSV Separator for CSV, Excel Sheet Name for Excel, and Page Orientation and Page Size for PDF.

Search

Used to search all information in the table.

RegExp Search

Used to search all information in the table with a regular expression (RegExp).

Column Based Search

Used to perform a column-based search on the information in the table.

Display of Interface and IP Addresses

The statuses of the interfaces and the IP addresses are shown for both devices with color codes (Up / No link / Down / Host is down / Absent in system and the VIP statuses; disabled IPs are dimmed and struck through in the related column). For the details see the Interface and IP Statuses section. When the status icon is hovered over, detailed information is displayed as a tooltip; with the copy icon that appears when the IP is hovered over, the address can be copied to the clipboard.

Page Information

Information about the total number of defined interfaces and the number of interfaces displayed in the list takes place: Showing N-M of T records and the number of selected interfaces (N selected, Nothing selected while there is no selection). The list is offered on a single page without pagination; there is no Page Size selector on this screen.

Right-Click Menu

When the interface row, the IP address, the route or the route table cell is right-clicked in the listing table, an operation menu that belongs to that object opens. The operations are applied only to the object that is right-clicked; the selection made in the list does not affect the menu.

Right-Clicking an Interface

Right-Clicking an Interface

In the menu header there is the name of the interface.

Operation	What it does
Edit Interface	Opens the interface editing form
Down	Disables the interface on both devices
Up	Puts the interface into service on both devices
Add IP	Adds an IP address to the interface
Add Route	Adds a static route to the interface

On an interface that is a Bond/LACP member, Add IP and Add Route are passive.

Right-Clicking an IP Address

Right-Clicking an IP Address

Operation	What it does
Delete IP	Deletes the IP address (from both devices)
Edit IP	Opens the IP address editing form
Enable for [This device]	Enables the IP address on this device
Disable for [This device]	Disables the IP address on this device
Enable for [Peer device]	Enables the IP address on the peer device
Disable for [Peer device]	Disables the IP address on the peer device

The menu header is in the form ip - peer ip Interface IP@interface in the Interface IPs and ip VIP@interface in the VIPs.

The Cluster Difference

The IP addresses can be enabled and disabled separately for every device; this is used in order to take a device out of traffic during maintenance. The management access IPs cannot be disabled.

In the lower part of the menu, in the second group whose header is the name of the interface, all the operations in the interface menu (Edit Interface, Down, Up, Add IP, Add Route) take place.

Right-Clicking a Route

Right-Clicking a Route

In the header of the menu that opens when a static route or the default gateway is right-clicked there is the route (in the form Default gateway -> 172.16.102.1):

Operation	What it does
Edit Route	Opens the route editing form
Delete Route(s)	Deletes the route

In the lower part of the menu, in the second group whose header is the name of the interface, all the operations in the interface menu (Edit Interface, Down, Up, Add IP, Add Route) take place.

Right-Clicking a Route Table

When the cell in the Route Table column is right-clicked, the operations for the related route table are listed:

Operation	What it does
Edit	Opens the route table editing form
Delete	Deletes the route table (the DEFAULT table cannot be deleted)
Stats	Opens the historical view of the route table in a closable tab

The Preview of the Selected Interface

When a row is clicked in the list, the preview of the interface opens on the right of the screen. When the panel is closed, it is opened again with the handle with the tool icon that carries the status color of the interface, at the top right of the listing area.

In the header of the panel there are the name of the interface; below it the description that summarizes its type and its bonds (e.g. ETH (DEFAULT), VLAN100@eth0, BOND[eth1,eth2], V-ETH@eth0; if there is more than one route table, the table name is added as well: VLAN100@eth0 (DEFAULT)) and the two-colored indicator that shows the status of the two devices.

The Preview of the Selected Interface

In the header of the panel there are two operations and below it the tabs; in the header of the IP and Routes tabs the number of related records is shown as a badge.

Edit Interface

It is the pencil icon at the top right of the header; it opens the Edit Interface form of the selected interface in the Edit Interface tab.

The Actions Menu

It is the ⋮ menu next to the pencil icon. Inside it there are the Delete Interface, Up and Down operations; the Up and Down done from here affect the interface on both devices at once.

Details

The rows are displayed in two columns, one for every device; which device the columns belong to is understood from the Device row. Above every column there are the two buttons that turn the interface on and off on that device only:

Operation	What it does
Up	Puts the interface into service (turns it on) on the related device only.
Down	Disables the interface (turns it off) on the related device only.

The Up and Down buttons in this tab are the only place that can turn the interface on and off on a single device; the right-click menu and the Up/Down in the panel header affect both devices together.

The rows in the tab are as follows in order:

Row	Description	Visibility condition
Device	The name of the related device (hostname).	Always, per device
Status	The instant status of the interface on the related device (Up, Down, No Link, Host Is Down, Absent in System, etc.).	Always, per device
Interface Traffic	The instant incoming (↓) and outgoing (↑) traffic on the related device.	Always, per device
VIP Communication	The address of the related device in the IPv4 Interface IP pair selected for the VRRP communication of the interface.	Always, per device
VIP Communication (v6)	The same information for IPv6; - if it has not been selected.	Always, per device
VIP Transition Duration (s)	The VRRP advertisement interval.	If a VIP communication pair is selected; common to the two devices
VIP Transition Method	The VIP transition method (Only VRRP, TR7 Link Check, TR7 GW Check, TR7 Link and GW Check).	Common to the two devices
MAC Address	The MAC address on the related device (it is read from the live system information).	Always, per device
MTU	The Maximum Transmission Unit value.	Always, per device
Speed	The connection speed (1 Gbps, 10 Gbps, etc.); -1 in the interfaces whose speed cannot be read.	Always, per device
Description	The description of the interface.	If a description is defined
Route Table	The route table the interface belongs to; in the window that opens with the information icon next to it there are the Reload VIP Service and Restart VIP Service buttons per device (see below).	Always

IP

The IP addresses assigned to the interface are listed in two columns whose headers are the device names (the IP/CIDR value and the status indicator); the VIPs appear with the (M) / (S) suffix. In the toolbar of the tab there is the Add IP button; the other operations that depend on the selection are gathered in the Actions menu:

Operation	What it does
Add IP	Adds a new IP address → Add IP Address
Delete IP	Deletes the selected IP address (from both devices)
Edit IP	Opens the editing form of the selected IP address
Enable for [This device]	Enables the selected IP address on this device
Disable for [This device]	Disables the selected IP address on this device
Enable for [Peer device]	Enables the selected IP address on the peer device
Disable for [Peer device]	Disables the selected IP address on the peer device

The same operations can be reached by right-clicking the rows. On an interface that is a Bond/LACP member, Add IP is passive.

Routes

The static routes defined on the interface are listed with the Status (two-colored), Destination Network (CIDR) and Gateway columns; if a monitor is defined on the default gateway, a ✓/✕ indicator per device shows the reachability. In the toolbar of the tab there is the Add Route button; the other operations that depend on the selection are gathered in the Actions menu:

Operation	What it does
Add Route	Adds a new static route → Add Static Routing
Delete Route(s)	Deletes the selected route(s)
Edit Route	Opens the editing form of the selected route

The Network Topology tab is conditional

If the interface has a hierarchical bond with other interfaces (if a VLAN/V-ETH is defined on it, if it is a member of a bond or a bridge, etc.), a Network Topology tab is also added to the tab strip between Routes and Log; it shows the topology of the interface itself. On the interfaces that have no such bond this tab is never displayed, and for this reason it is not seen in the image above either.

Log

It lists the user operations on the interface (adding, editing, deleting) as a timeline.

Delete Confirmations and Protection Mechanisms

The delete and edit operations on network objects are not applied blindly; before running the operation, TR7 calculates its side effects and lists them in the confirmation window.

Confirmation with an impact preview

• The delete operations always ask for confirmation; in the confirmation window the side effects of the operation are listed marked according to their level of importance: 🔴 destructive, 🟠 warning, ℹ️ information. Examples: "${count} attached interface(s) will also be deleted" (the attached virtual interfaces), "${count} IP address(es) will be deleted", "Route table '${name}' will lose its IPv${v} default gateway".
• If there is an item at the 🔴 level in the list, a second confirmation window opens: "This action has destructive consequences. Are you REALLY sure?"; in order to prevent confirming by mistake, the confirmation button stays locked for a short time.
• In the edit operations confirmation is asked only if there is a side effect; the adding operations are applied without confirmation.

Protected objects

• Physical (ETH) interfaces cannot be deleted. They can be moved to a different route table; if their table is deleted, they are moved automatically to the DEFAULT table.
• The DEFAULT route table cannot be deleted.
• The IP addresses used in the management access lists (HTTP, HTTPS, SSH, SNMP) of the device are protected; when an attempt is made to delete them, the "${ip} is protected. (${reason})" error is returned and the interface that carries this IP is taken under protection as well.
• Bond/LACP member interfaces cannot have an IP or a route added to them.
• The cluster synchronization (sync) interface is protected: it cannot be deleted, cannot be moved outside DEFAULT, an IP and a route cannot be added to it and it cannot be turned on and off ("Interface '...' is protected (Sync interface)").

The cluster behaviors

• IP deletion: If the deleted IP is used as the VIP Communication pair of an interface, the 🟠 "The cluster IP pair of the following interfaces will be cleared: ..." warning is listed in the confirmation window; the VIP configuration of the related interface is emptied.
• A change of the IP type: When the type of an IP is changed as Interface IP ↔ VIP, its effects are listed in the confirmation window; the destructive effects (e.g. "... its entire VIP configuration will be torn down") ask for a second confirmation.
• Synchronize Network Config with System: If the cluster connection is open, the synchronization versions are compatible and automatic synchronization is enabled (if the manual synchronization mode is off), the configuration is applied on both devices; otherwise it is applied on this device only. The operations that target the peer device (Up/Down on the peer device, the VIP service buttons) are silently not applied while the cluster connection is broken.
• Reload VIP Service / Restart VIP Service: They are offered per device in the route table information window; Reload reloads the VRRP service and Restart restarts the service and may lead to a VIP failover.
• The network lock warning reflects only the operations on this device; a network operation continuing on the peer device is not shown on this screen.