Forum Discussion
Aug 08, 2013
management interface configuration
I know that the management interface must be in a separate subnet/VLAN than the other interfaces ( internal , external , HA ).
But re config of the management interface :
Q1 : In f5...
Hamish
Aug 09, 2013Cirrocumulus
To expand a bit. The management interface is controlled directly by the host itself. This supports plain old unencapsulated packets only. (An access port only in cisco terms). (The Linux OS your interact with). The TMM interfaces for which you see configuration options for in the GUI are actually connected to a separate ethernet switch. This switch is under the control of the TMM micro-kernel that runs the load-balancing on the unit (You can see this from the host as a process running an executable called tmm. There's one per CPU core usually).
The host OS doesn't really have access to this, and the TMM kernel doesn't have access to the management interface. The TMM switchboard can do 802.1Q VLAN tagging (Cisco Trunking, not to be confused with BigIP Trunking) OR operate as an access port (Which appears on bigip as a pseudo VLAN tag > 4096).
As nitas said... Static IP's for management. SLightly more config to do to set a static IP vs leaving it dynamic, but you don't have to rely on DHCP servers and DDNS.
H
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects