In-band Management Overview

RBFS is mostly deployed on the RtBrick Host Operating System as a Linux container. The RtBrick Host is only reachable through the out-of-band management interface. In order to use services like NTP, and TACACS, which are run on RtBrick Host, or to use services like ssh, snmpd running in LXC container, one must use an out-of-band management connection. In-band management provides a way to access these services which are running in RtBrick Host and LXC containers via physical traffic ports.

The RBFS creates a Linux kernel interface named inband-mgmt-0 when in-band management is enabled on an instance. The loopback IPs of the in-band instance are then assigned to this Linux interface, and the routes of this instance are downloaded to the LXC container, then to RtBrick Host. Trap rules are installed in the hardware depending on the in-band service enabled.

inbandmgmtoverview
Figure 1. In-band Management Overview

Support for Non-Loopback Interfaces

In-band management is supported on non-loopback interfaces. It allows you to use the non-loopback interfaces for management protocols such as SSH. Supported management protocols can connect to and from physical interface addresses, enabling physical data interfaces to be used as primary or secondary management interfaces.

In the configuration, when loopback-only is set to true, management protocols such as SSH, CTRLD, and other management services can be accessed only through loopback interfaces that belong to the in-band management instance. Non-loopback interface addresses are not used for management access.

Supported Platforms

Not all features are necessarily supported on each hardware platform. Refer to the Platform Guide for the features and the sub-features that are or are not supported by each platform.