Brocade Virtual ADX Administration Guide (Supporting ADX v03.1.00) - Manual (Page 141)

Brocade Virtual ADX Administration Guide 129
53-1003249-01
Appendix
A
Management Port: Key Functional Specifications
The Management Port interface functions as follows:
• When the mgmt1 interface receives a packet, Linux kernel receives it first. The Netfilter
framework provided in Linux is used to isolate the packets that are destined to the Brocade
Virtual ADX management interface and the packets that are destined to Linux Kernel.
The Brocade Virtual ADX management interface reads the ARP entries during its initialization
from Kernel and listens to the ARP table events for further updates in the Kernel.
• The Brocade Virtual ADX management interface reads the routes from the Linux Kernel during
its initialization and listens to the Routing table events for further updates in the Kernel.
• The Brocade Virtual ADX management interface reads the IP address from the Linux Kernel
during its initialization and listens to the Interface events for updates (link status and IP
address) in the Kernel.
NOTE
Linux allows multiple primary and secondary addresses on a particular interface. Hence, if
multiple primary IP addresses are configured on the management interface, only first IP
address is considered. Also, Linux allows you to configure multiple default routes. Even in this
case, only the first default route is considered in Brocade Virtual ADX
• The IP address of the management interface can be configured statically or dynamically
assigned through a DHCP Server. Linux Kernel will act as DHCP client and maintains the IP
address that is assigned dynamically. You can either use the dhclient command or modify the
interface network script file in Linux to enable or disable the DHCP client on the management
interface.
• Different port numbers are used to differentiate between SSH to Brocade Virtual ADX
management console and SSH to Linux shell. SSHD on Brocade Virtual ADX runs on standard
port 22. On Linux, it runs on port 2222.
• Packets coming on the management interface are copied to the Brocade Virtual ADX
management interface buffer from nfnetlink_queue using libnfnetlink_queue library for
classification. Packets are destined to Linux or Brocade Virtual ADX management console
based on criteria.
• Brocade Virtual ADX will try to resolve the hostname through Linux kernel if the DNS
configuration does not exist on Brocade Virtual ADX.