How to connect MAAS networks

Errors or typos? Topics missing? Hard to read? Let us know.

Network discovery

Network discovery scans your environment to identify all connected devices, including non-deployable devices such as routers and switches. To enable or disable discovery:

• In the MAAS 3.4 UI, select Networking > Network discovery > Configuration; in the Network discovery drop-down, choose “Enabled” or “Disabled”; Save your changes.

• For all other MAAS UI versions, select Canonical MAAS > Configuration; in the Network discovery drop-down, choose “Enabled” or “Disabled”; Save your changes.

• In the MAAS CLI, enter the following command:

    maas $PROFILE maas set-config name=network_discovery value="enabled"

Managed allocation

Allocation of IP addresses and subnet routes can be MAAS-managed or manual.

• For the MAAS UI, choose Subnets > > Edit > Managed allocation > Save.

• Using the CLI to toggle subnet management, enter this command, using the subnet ID in place of CIDR, if desired:

    maas $PROFILE subnet update $SUBNET_CIDR managed=false|true

Network panel (UI only)

In the MAAS UI, the network dashboard displays everything MAAS knows about its connected networks:

• In the 3.4 UI, select Networking > Subnets to access the dashboard. This view can also be filtered with the ‘Filters’ drop-down.

• For all other MAAS versions, select Subnets to access the dashboard. This view can also be filtered via the Group by drop-down.

While in the network panel:

• Select a subnet to view its details.

• Subnet utilisation figures are near the bottom.

• Near the bottom of the Subnet summary, you can manage reserved IP ranges.

• At the very bottom of the Subnet summary, you can track DHCP snippets and used IP addresses.

Static routes

You can create static IP routes as desired.

• With the MAAS 3.4 UI, select Networking > Subnets > > Subnet summary > Add static route; enter a Gateway IP address, Destination subnet, and routing Metric. Don’t forget to Save.

• Using the UI for all other MAAS versions, choose Add static route; enter a Gateway IP address, Destination subnet, and routine Metric; click ‘Add’ to activate the route. Routes can be edited and removed using the icons to the right of each entry.

• With the CLI, it’s simple create a static route between two subnets:

    maas admin static-routes create source=$SOURCE_SUBNET destination=$DEST_SUBNET \
    gateway_ip=$GATEWAY_IP

Here’s the guide without any bolding:

---

Configure loopback

Configuring the loopback interface (lo) in MAAS can be a bit tricky, especially when you need it for advanced networking tasks like Free Range Routing (FRR) and BGP. Here’s how you can do it:

1. Understand the loopback interface
   The loopback interface is used for internal routing within the node and doesn’t need a MAC address. It’s important for network functions like BGP in more advanced setups.

2. Manually add the loopback interface
   After commissioning a node in MAAS, you’ll need to manually add the loopback interface. If the MAAS web UI asks for a MAC address, you can use a placeholder like 00:00:00:00:00:00. Just make sure this placeholder doesn’t match any other MAC addresses in your network.

3. Avoid duplicate MAC addresses
   MAAS doesn’t allow duplicate MAC addresses on different nodes, so each node should have a unique MAC address. If needed, you can manually configure the loopback interface on each node to avoid the MAC address requirement.

4. Consider other methods
   If adding the loopback interface in MAAS is causing problems, you might want to configure it outside of MAAS using post-deployment scripts. First, set up the basic configuration with MAAS, then use tools like cloud-init to add your custom network settings, including the loopback interface.

5. Ask for help if needed
   If you’re still having trouble, you can ask MAAS support or your internal teams for more help. They might have new solutions or workarounds that fit your needs.

By following these steps, you can set up loopback interfaces on nodes managed by MAAS, allowing you to use advanced networking features like L3 routing and BGP.

Bridging

To configure a bridge with the MAAS UI, select Machines > machine > Network > hosting network > Create bridge > details > Save interface. You can then deploy machines using this bridge. Note that you can create an “Open switch” bridge if desired, and MAAS will create the netplan model for you.

You can also use the MAAS CLI/API to configure a bridge via the following procedure:

1. Select the interface on which you wish to configure the bridge. This example uses the boot interface, since the boot interface must be connected to a MAAS controlled network – but any interface is allowed:

        INTERFACE_ID=$(maas $PROFILE machine read $SYSTEM_ID | jq .boot_interface.id)

2. Create the bridge:

         BRIDGE_ID=$(maas $PROFILE interfaces create-bridge $SYSTEM_ID name=br0 parent=$INTERFACE_ID | jq .id)

3. Select the subnet where you want the bridge (this should be a MAAS controlled subnet):

        SUBNET_ID=$(maas $PROFILE subnets read | jq -r '.[] | select(.cidr == "10.0.0.0/24" and .managed == true).id')

4. Connect the bridge to the subnet:

          maas $PROFILE interface link-subnet $SYSTEM_ID $BRIDGE_ID subnet=$SUBNET_ID mode="STATIC" ip_address="10.0.0.101"

Bridging with Netplan

Building a bridge with netplan is independent of MAAS UI or CLI. You can configure a bridge like this:

1. Open your netplan configuration file. This should be in /etc/netplan. It could be called 50-cloud-init.yaml, netplan.yaml, or something else.

2. Modify the file to add a bridge, using the following example as a guide:

    network:
        bridges:
            br0:
                addresses:
                - 10.0.0.101/24
                gateway4: 10.0.0.1
                interfaces:
                - enp1s0
                mac address: 52:54:00:39:9d:f9
                mtu: 1500
                name servers:
                    addresses:
                    - 10.0.0.2
                    search:
                    - maas
                parameters:
                    forward-delay: 15
                    stp: false
        Ethernet's:
            enp1s0:
                match:
                    mac address: 52:54:00:39:9d:f9
                mtu: 1500
                set-name: enp1s0
            enp2s0:
                match:
                    mac address: 52:54:00:df:87:ac
                mtu: 1500
                set-name: enp2s0
            enp3s0:
                match:
                    mac address: 52:54:00:a7:ac:46
                mtu: 1500
                set-name: enp3s0
        version: 2

3. Apply the new configuration with netplan apply.

Here’s a simpler version of the guide:

---

Configure two NICs on one machine

Suppose that you need to set up a machine with two network interface cards (NICs): one for a private subnet managed by MAAS and another for a public subnet used for internet access. Configuring the second NIC through the MAAS UI can be tricky, but these steps will help.

First, make sure MAAS detects both NICs. You should see both network interfaces (like ens18 and ens19) listed in the machine’s network configuration in the MAAS UI.

Next, go to the MAAS UI and select the machine. Navigate to the “Network” tab. For the first NIC (ens18), make sure it’s set to use DHCP on the private subnet (like 192.168.10.0/24).

For the second NIC (ens19), you’ll need to edit the interface settings manually for the public subnet (like 192.168.1.0/24). In the “Edit Physical” settings for ens19, select the right fabric and subnet, set the IP address manually or use DHCP if your public network has a DHCP server, and enter the gateway and DNS settings needed for internet access.

Make sure the netplan configuration on the machine matches the settings from MAAS. Here’s an example of how the 50-cloud-init.yaml file might look:

network:
    version: 2
    ethernets:
        ens18:
            addresses:
            - 192.168.10.5/24
            match:
                macaddress: 8e:57:8a:55:d4:2d
            mtu: 1500
            nameservers:
                addresses:
                - 192.168.10.10
                search:
                - maas
            set-name: ens18
        ens19:
            addresses:
            - 192.168.1.10/24  # Set this according to your network
            gateway4: 192.168.1.1  # Default gateway for internet access
            nameservers:
                addresses:
                - 8.8.8.8  # Google's DNS or your preferred DNS
                - 8.8.4.4
            match:
                macaddress: c6:11:fb:c9:5e:e2
            mtu: 1500
            set-name: ens19

After that, apply the network configuration using the netplan apply command or reboot the machine to make sure the settings take effect.

One thing to note is that there might be a bug when selecting a fabric in the “Edit Physical” settings, which can cause it to reset. Be sure the correct fabric and subnet are selected before you save the configuration.

By following these steps, you’ll be able to set up both NICs on your machine, allowing it to connect to both the private MAAS-managed network and the public internet.

Find fabric IDs (CLI)

You’ll need the “fabric ID” to manipulate some networking parameters in the CLI. To determine a fabric ID based on a subnet address:

    FABRIC_ID=$(maas $PROFILE subnet read $SUBNET_CIDR \
        | grep fabric | cut -d ' ' -f 10 | cut -d '"' -f 2)

This may come in handy when you need a fabric ID for other CLI calls.

Set the default gateway (CLI)

To set the default gateway for a subnet, just use this command:

maas $PROFILE subnet update $SUBNET_CIDR gateway_ip=$MY_GATEWAY

Set up DNS (CLI)

You can set the DNS server for a subnet very easily, with the CLI, like this:

maas $PROFILE subnet update $SUBNET_CIDR dns_servers=$MY_NAME SERVER

List subnets (CLI)

From time to time, you may want to view the list of available subnets. Do that with the following command:

maas admin subnets read | \
jq -r '(["FABRIC", "VLAN", "DHCP", "SUBNET"]
| (., map(length*"-"))),
(.[] | [.vlan.fabric, .vlan.name, .vlan.dhcp_on, .cidr])
| @tsv' \
| column -t

View subnet details (CLI)

Via the CLI, you can view the details of an individual subnet with the command:

maas $PROFILE subnet read $SUBNET_ID \
| jq -r '(["NAME","CIDR","GATEWAY","DNS","DISCOVERY","FABRIC","VLAN"]
| (., map(length*"-"))), ([.name,.cidr,.gateway_ip // "-", .allow_dns,.active_discovery,.vlan.name,.vlan.fabric]) | @tsv' | column -t

Look up the subnet ID like this:

maas $PROFILE subnets read \
| jq -r '(["NAME", "SUBNET_ID"]
| (., map(length*"-"))), (.[] | [.name, .id]) | @tsv' \
| column -t | grep $SUBNET_NAME

For example, using the “admin” profile with a subnet name containing “192.168.123,” find the subnet ID with this command:

maas admin subnets read \
| jq -r '(["NAME", "SUBNET_ID"]
| (., map(length*"-"))), (.[] | [.name, .id]) | @tsv' \
| column -t | grep 192.168.123

Edit machine interfaces

To edit a machine interface via the 3.4 UI, select Machines > machine > Network > interface > Actions > Edit physical > edit parameters > select IP mode > Save interface.

To edit a machine interface with the UI for all other MAAS versions, select Machines > machine > Interfaces > interface icon > Edit Physical > IP mode > Save.

To edit the IP assignment mode of a network interface with the CLI, perform the following steps:

1. Find the interface ID and subnet link ID with the command:

    maas $PROFILE node read $SYSTEM_ID

2. Unlink the old interface:

    maas $PROFILE interface unlink-subnet $SYSTEM_ID $INTERFACE_ID id=$SUBNET_LINK_ID

3. Link the new interface:

    maas $PROFILE interface link-subnet $SYSTEM_ID $INTERFACE_ID mode=$IP_MODE subnet=$SUBNET_CIDR [$OPTIONS]

See the glossary for the definitions of reserved range types.

Create bonds

To create bonds with the MAAS UI, select more than one interface > Create bond > rename bond > select mode as follows:

• balance-rr: Transmit packets in sequential order from the first available follower through to the last. This mode provides load balancing and fault tolerance.

• active-backup: Only one follower in the bond is active. A different follower becomes active if, and only if, the active follower fails. The bond’s MAC address is externally visible on only one port (network adaptor) to avoid confusing the switch.

• balance-xor: Transmit based on the selected transmit hash policy. The default policy is simple, which means that an XOR operation selects packages. This XOR compares the source MAC address and the resultant XOR between the destination MAC address, the packet type identifier, and the modulo follower count.

• broadcast: Transmit everything on all follower interfaces. This mode provides fault tolerance.

• 802.3ad: Creates aggregation groups that share the same speed and duplex settings. This mode utilises all followers in the active aggregation, following the IEEE 802.3ad specification.

• balance-tlb: Adaptive transmit load balancing, channel bonding that does not require any special switch support.

• balance-alb: Adaptive load balancing, includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic. This mode does not require any special switch support. ARP negotiation achieves load balancing in this case.

Having selected a mode, to finish up, assign a MAC address > attach Tags > select Primary > Save.

The MAC address defaults to the MAC address of the primary interface.

To create a bond with the MAAS CLI, execute the following command:

maas $PROFILE interfaces create-bond $SYSTEM_ID name=$BOND_NAME \
parents=$IFACE1_ID mac_address=$MAC_ADDR \ 
parents=$IFACE2_ID bond_mode=$BOND_MODE \
bond_updelay=$BOND_UP bond_downdelay=$BOND_DOWN mtu=$MTU

Note that:

• The parents parameters define which interfaces form the aggregate interface.

• The bond_updelay and bond_downdelay parameters specify the number of milliseconds to wait before either enabling or disabling a follower after a failure has been detected.

• There are a wide range of bond parameters you can choose when creating a bond:

• Supported bonding modes include:

Create bridges

To create a bridge interface via the MAAS UI:

1. Select Machines > machine > Network > interface > Create bridge.

2. Define Bridge type, MAC address, Fabric, and VLAN.

3. Optionally define Bridge name, Subnet, Tags and turn on STP.

4. Register your new bridge by selecting Save interface.

To create a bridge interface with the CLI:

maas $PROFILE interfaces create-bridge $SYSTEM_ID name=$BRIDGE_NAME \
parent=$IFACE_ID

Use parent to define the primary interface used for the bridge:

maas admin interfaces create-bridge 4efwb4 name=bridged0 parent=4

The following parameters may be applied when creating a bridge:

• name: Optional string. Name of the interface.

• mac_address: Optional string. MAC address of the interface.

• tags: Optional string. Tags for the interface.

• vlan: Optional string. VLAN the interface is connected to.

• parent: Optional integer. Parent interface id for this bridge interface.

• bridge_type: Optional string. The type of bridge to create. Possible values are: standard, ovs.

• bridge_stp: Optional Boolean. Turn spanning tree protocol on or off. (Default: False).

• bridge_fd: Optional integer. Set bridge forward delay to time seconds. (Default: 15).

• mtu: Optional integer. Maximum transmission unit.

• accept_ra: Optional Boolean. Accept router advertisements. (IPv6 only)

• autoconf: Optional Boolean. Perform stateless autoconfiguration. (IPv6 only)

Delete an interface (CLI)

Interfaces can only be deleted via the CLI. The “delete” command can be used to delete a bridge interface, a bond interface or a physical interface:

maas $PROFILE interface delete $SYSTEM_ID $IFACE_ID

For example:

maas admin interface delete 4efwb4 15

The following is output after the successful deletion of an interface:

Success.
Machine-readable output follows:

Note that while the label is presented, there is no machine-readable output expected after the successful execution of the delete command.

Assign an interface (CLI)

You can only assign an interface to a fabric with the MAAS CLI. This task is made easier with the aid of the jq utility. It filters the maas command (JSON formatted) output and prints it in the desired way, which allows you to view and compare data quickly. Go ahead and install it:

sudo apt install jq

In summary, MAAS assigns an interface to a fabric by assigning it to a VLAN. First, we need to gather various bits of data.

List some information on all machines:

maas $PROFILE machines read | jq ".[] | \
    {hostname:.hostname, system_id: .system_id, status:.status}" --compact-output

Example output:

{"hostname":"machine1","system_id":"dfgnnd","status":4}
{"hostname":"machine2","system_id":"bkaf6e","status":6}
{"hostname":"machine4","system_id":"63wqky","status":6}
{"hostname":"machine3","system_id":"qwkmar","status":4}

You can only edit an interface when the corresponding machine has a status of ‘Ready’. This state is numerically denoted by the integer ‘4’.

List some information for all interfaces on the machine in question (identified by its system id ‘dfgnnd’):

maas $PROFILE interfaces read dfgnnd | jq ".[] | \
    {id:.id, name:.name, mac:.mac_address, vid:.vlan.vid, fabric:.vlan.fabric}" --compact-output

Example output:

{"id":8,"name":"eth0","mac":"52:54:00:01:01:01","vid":0,"fabric":"fabric-1"}
{"id":9,"name":"eth1","mac":"52:54:00:01:01:02","vid":null,"fabric":null}

List some information for all fabrics:

maas $PROFILE fabrics read | jq ".[] | \
    {name:.name, vlans:.vlans[] | {id:.id, vid:.vid}}" --compact-output

Example output:

{"name":"fabric-0","vlans":{"id":5001,"vid":0}}
{"name":"fabric-1","vlans":{"id":5002,"vid":0}}
{"name":"fabric-2","vlans":{"id":5003,"vid":0}}

This example will show how to move interface ‘8’ (on machine ‘dfgnnd’) from ‘fabric-1’ to ‘fabric-0’. Based on the gathered information, this will consist of changing the interface’s VLAN from ‘5002’ to ‘5001’:

maas $PROFILE interface update dfgnnd 8 vlan=5001 >/dev/null

Verify the operation by relisting information for the machine’s interface:

maas $PROFILE interfaces read dfgnnd | jq ".[] | \
    {id:.id, name:.name, mac:.mac_address, vid:.vlan.vid, fabric:.vlan.fabric}" --compact-output

The output shows that the interface is now on fabric-0:

{"id":8,"name":"eth0","mac":"52:54:00:01:01:01","vid":0,"fabric":"fabric-0"}
{"id":9,"name":"eth1","mac":"52:54:00:01:01:02","vid":null,"fabric":null}

Discover identifiers (CLI)

Interface identifiers can only be discovered via the MAAS CLI. The MAAS CLI uses a numeric interface identifier for many interface operations. Use the following command to retrieve the identifier(s):

maas $PROFILE interfaces read $SYSTEM_ID

Look for either id or the number at the end of an interface’s resource URI, such as 15 in the following example output:

"id": 15,
"mac_address": "52:54:00:55:06:40",
...
"name": "ens9",
...
"resource_uri": "/MAAS/api/2.0/nodes/4efwb4/interfaces/15/"

Create VLANs (CLI)

VLAN interfaces can only be created via the MAAS CLI. To create a VLAN interface, use the following syntax:

maas $PROFILE vlans create $FABRIC_ID name=$NAME vid=$VLAN_ID

For example, the following command creates a VLAN called 'Storage network:

maas admin vlans create 0 name="Storage network" vid=100

The above command generates the following output:

Success.
Machine-readable output follows:
{
    "vid": 100,
    "mtu": 1500,
    "dhcp_on": false,
    "external_dhcp": null,
    "relay_vlan": null,
    "name": "Storage network",
    "space": "undefined",
    "fabric": "fabric-0",
    "id": 5004,
    "primary_rack": null,
    "fabric_id": 0,
    "secondary_rack": null,
    "resource_uri": "/MAAS/api/2.0/vlans/5004/"
}

Be aware that the $VLAN_ID parameter does not indicate a VLAN ID that corresponds to the VLAN tag. You must first create the VLAN and then associate it with the interface:

maas $PROFILE interfaces create-vlan $SYSTEM_ID vlan=$OUTPUT_VLAN_ID \
parent=$IFACE_ID

OUTPUT_VLAN_ID corresponds to the id value output when MAAS created the VLAN.

The following example contains values that correspond to the output above:

maas admin interfaces create-vlan 4efwb4 vlan=5004 parent=4

The above command generates the following output:

Success.
Machine-readable output follows:
{
    "tags": [],
    "type": "vlan",
    "enabled": true,
    "system_id": "4efwb4",
    "id": 21,
    "children": [],
    "mac_address": "52:54:00:eb:f2:29",
    "params": {},
    "vlan": {
        "vid": 100,
        "mtu": 1500,
        "dhcp_on": false,
        "external_dhcp": null,
        "relay_vlan": null,
        "id": 5004,
        "secondary_rack": null,
        "fabric_id": 0,
        "space": "undefined",
        "fabric": "fabric-0",
        "name": "Storage network",
        "primary_rack": null,
        "resource_uri": "/MAAS/api/2.0/vlans/5004/"
    },
    "parents": [
        "ens3"
    ],
    "effective_mtu": 1500,
    "links": [
        {
            "id": 55,
            "mode": "link_up"
        }
    ],
    "discovered": null,
    "name": "ens3.100",
    "resource_uri": "/MAAS/api/2.0/nodes/4efwb4/interfaces/21/"
}

Deleting VLANs (CLI)

VLAN interfaces can only be deleted via the MAAS CLI. The following command outlines the syntax required to delete a VLAN interface from the command line:

maas $PROFILE vlan delete $FABRIC__ID $VLAN_ID

Using the values from previous examples, you executed this step as follows:

maas admin vlan delete 0 100

Set up proxies

MAAS lets you set up a proxy for managed machines to access web resources. Your choices:

1. Internal proxy (default)
2. External proxy
3. No proxy

Toggle these options and control proxy use by subnet. This section will show you how.

To toggle the proxy in the MAAS UI, go to Settings > Network services > Proxy, and choose:

• To enable the internal proxy, ensure that the checkbox adjacent to ‘MAAS Built-in’ is selected. This internal proxy is the default configuration.

• To enable an external proxy, activate the ‘External’ checkbox and use the new field that is displayed to define the proxy’s URL (and port if necessary).

• An upstream cache peer can be defined by enabling the ‘Peer’ checkbox and entering the external proxy URL into the field. With this enabled, machines will be configured to use the MAAS built-in proxy to download cached APT packages.

• To prevent MAAS machines from using a proxy, enable the ‘Don’t use a proxy’ checkbox.

You can also toggle proxies with the CLI. Enabling and disabling proxies in the CLI is done via a Boolean option (‘true’ or ‘false’). The following command will disable proxying completely:

maas $PROFILE maas set-config name=enable_http_proxy value=false

To set an external proxy, ensure proxying is enabled (see above) and then define it:

maas $PROFILE maas set-config name=http_proxy value=$EXTERNAL_PROXY

For example,

maas $PROFILE maas set-config name=enable_http_proxy value=true
maas $PROFILE maas set-config name=http_proxy value=http://squid.example.com:3128/

Enabling and disabling proxying per subnet is also done via a Boolean option (‘true’ or ‘false’). Here is how you can disable proxying on a per-subnet basis:

maas $PROFILE subnet update $SUBNET_CIDR allow_proxy=false

For example,

maas $PROFILE subnet update 192.168.0.0/22 allow_proxy=false

NOTE that the proxy service will still be running.

Sync time with NTP

MAAS provides managed NTP services (with Chrony^) for all region and rack controllers. This arrangement allows MAAS to both keep its controllers synchronised, and keep deployed machines synchronised as well. You can configure NTP on the ‘Network services’ tab of the ‘Settings’ page.

The region controller configures the NTP service to keep its time synchronised from one or more external sources. By default, the MAAS region controller uses ntp.ubuntu.com. Rack controllers also configure the NTP service, synchronising their time with the region controllers. Rack controllers also configure DHCP with the correct NTP information, so that the DHCP servers can manage the NTP clients for the rack. Any machine on the network that obtains a DHCP lease from MAAS will benefit from NTP support.

Set up external NTP

External sites, such as an existing NTP infrastructure, can be used directly as a time source for both rack controllers and machines.

You can specify an external NTP site site with the MAAS UI by choosing the NTP server(s) and selecting the External Only option. To do so, go to Settings > Network services > NTP and enter the address of the desired NTP server.

Note that the region controller always uses an external site.

You can specify an external NTP server via the CLI, with two successive commands:

maas $PROFILE maas set-config name=ntp_servers value=$NTP_IP_ADDRESS

followed by:

maas admin maas set-config name=ntp_external_only value=true

Here’s the guide rewritten at an eighth-grade reading level:

---

Fix VLAN issues

Sometimes, VLANs don’t work on any rack controller, which can cause problems with DHCP and network connections.

Follow these steps to troubleshoot and fix VLAN issues in MAAS:

1. Configure VLAN interfaces
   Make sure the VLAN interfaces on the rack controller are set up with the correct VLAN IDs, links, and IP addresses. After setting them up, apply the changes using this command:

   sudo netplan apply
   

2. Define subnets correctly
   Check that the subnets for each VLAN are set up correctly in MAAS. Make sure the network, gateway, and DNS information is entered accurately.

3. Check physical connections
   Make sure the rack controller is physically connected to the right networks and VLANs. If you’re using a managed switch, make sure the ports are set up for the correct VLANs.

4. Review MAAS logs
   Look at the MAAS logs for any errors related to VLANs or DHCP that might help you find the problem.

5. Force network re-detection
   To make MAAS detect the networks and VLANs again, remove the rack controller from MAAS and then add it back.

6. Test DHCP on one VLAN at a time
   Turn on DHCP for one VLAN at a time to see which ones are working correctly. This can help you find issues with specific VLANs.

7. Set a static IP address
   You might want to set a static IP address on the VLAN interface to avoid problems with DHCP.

8. Restart the rack controller
   Restart the rack controller to make sure it reconnects properly to MAAS and the VLANs. This can sometimes fix connection issues.

9. Reinstall the rack controller if needed
   If these steps don’t solve the problem, you might need to reinstall the rack controller by following the official MAAS documentation. Make sure the rack controller isn’t installed on the same machine as the region controller.

10. Consider DHCP forwarding
    If you’re using DHCP forwarding on your router, make sure the rack servers on the VLAN can still communicate with the DHCP server.

By following these steps, you should be able to fix VLAN issues on rack controllers in MAAS and ensure everything is connected properly.

---

Last updated 29 days ago.