Configuring VLAN interfaces - BlueCat Address Manager - 8.3.0

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
8.3.0

This section describes how to configure VLAN interfaces from the Address Manager user interface (recommended for most scenarios) and optionally, how to configure a VLAN interface directly from the DNS/DHCP Server Administration Console. Additional topics include configuring VLAN interfaces with xHA and configuring bonding interfaces.

BlueCat advises all customers to use the Address Manager user interface for configuring and maintaining VLANs. However, there are some scenarios that require VLAN configuration from the DNS/DHCP Server Administration Console. They are as follows:
  • Configuring dedicated management with VLAN tagging
  • Changing the Primary Service IP from one address to another
  • Configuring default gateways in both IPv4 and IPv6 address-families
  • Configuring static routes in both IPv4 and IPv6 address-families
  • Reset factory defaults on physical interfaces
  • Reset gateway/routing configuration to factory defaults
  • Replacing a Server
For details, refer to Configuring a VLAN interface from the Administration Console.

Impact on services

  • DHCPv4 and DHCPv6 do not automatically reconfigure themselves to VLAN changes. You must manually restart DHCPv4 and DHCPv6 when adding or removing a VLAN interface. For more information on this issue, refer to Knowledge Base article 15300 on BlueCat Customer Care.
  • DNS and NTP automatically reconfigure themselves without disruption to start serving new VLANs and stop serving removed VLANs.
  • SNMP, TFTP, and Anycast do not need to be reconfigured for VLAN changes because they listen to all IP addresses on certain ports. Any new VLAN interfaces will automatically be covered with these services. Anycast's coverage for changed VLANs will only depend on and be restricted by the deployed configuration.
  • Syslog redirection is more about initiating connections with remote nodes rather than listening for incoming connections. This means changes to a VLAN configuration will not disrupt this service. However, the behavior of syslog redirection might be impacted by changes in routing tables caused by changes in a VLAN configuration.