In-band Management Overview

RBFS is mostly deployed on an ONL host as a Linux container. The ONL host is only reachable through the out-of-band management interface. In order to use services like NTP, and TACACS, which are run on ONL, 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 ONL 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 ONL. Trap rules are installed in the hardware depending on the in-band service enabled.

inbandmgmtoverview

  • It is recommended to use a separate, dedicated instance for Inband Management, limiting the number of routes to fewer than 1,000.

  • When Inband Management is enabled on a router, the routes in the Inband Management instance are downloaded to the host ONL. To prevent disruptions in Out-of-Band (OOB) management, it is essential to ensure there are no conflicting routes. Therefore, it is recommended to configure specific routes in ONL for OOB management.

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.