FAQs (Mist Wired)

What does the Inactive wired VLANs warning on the Mist dashboard mean?

When your APs do not detect incoming traffic from a particular VLAN that is used in either an AP or a WLAN configuration, Mist suspects that this VLAN is not configured on the switch port where the APs are connected. The Inactive wired VLANs warning appears on the AP list page to indicate this issue, and an icon is displayed next to the APs experiencing the inactive wired VLAN issue.

How to check which VLAN is missing on the switch port?

To find out which VLANs are missing on the switch port:

1. Go to the Marvis Actions page (Marvis > Actions).

2. From the actions tree, select Switch > Missing VLAN to see the VLANs that are missing.

How to verify if Marvis is detecting the correct case of missing VLANs?

To verify whether the Marvis AI is detecting the correct case of missing VLANs, do a packet capture or port mirroring on the switch port to which the AP is connected, and use the Wireshark tool to analyze the traffic. You can also use the VLAN filter to verify if any traffic is coming from that VLAN. See Dynamic and Manual Packet Captures for more help on setting up Wireshark.

How to fix the missing VLAN error?

Once you have identified the VLAN that is missing from the switch port but is being used in your AP or WLAN configuration, you can configure that VLAN on your switch. After the VLAN is correctly configured on your switch and the AP starts detecting traffic from it, Mist takes some time to verify the fix and ensure that the issue is resolved. After that, the warning disappears automatically.

In an EX Series switch-based Virtual Chassis (VC) system, how do I convert the DAC-attached VC port to a trunk port?

You can do this by converting the VC port on the Virtual Chassis to network port by using the following CLI commands in the Additional CLI Commands section on the switch details page (Switches > Switch Name):

After saving the above configuration, reboot the switch using the Reboot option on the Utilities menu on the switch details page (Switches > Switch Name). This behavior applies to the EX Series switches that come with a default VC port.

Upgrade Required: Upgrading Junos or the BIOS for EX4400 Switches From the Mist Dashboard

For Juniper EX Series switches that are managed by Mist, you can identify and upgrade the Junos version and/or switch BIOS to the current version from the Mist dashboard. To alert you to a version mismatch and to recent releases, a notification appears at both the switch list, and on the configuration page of individual switch. When more than one switch is affected, you can select all to perform a simultaneous upgrade.

Figure 1: Upgrade Notification

When you see an upgrade notification, we recommend that you perform the update as soon as convenient to prevent "silent," or unexpected, device reboots that can result in the case of new Mist features not being supported by a previous version of the switch firmware. Note that for BIOS upgrades and some Junos upgrades, the switch will be taken offline to reboot or restart a given line card.

The Upgrade BIOS option appears:

For switches configured for virtual chassis (VC), all members are automatically upgraded together; you do not need to perform separate BIOS upgrades. Likewise, in the case where different FPCs are running different BIOS versions, only those FPCs that need the newer BIOS will be upgraded.

Tip: You can find the switch BIOS by opening a remote shell (Utilities > Remote Shell at the top of the switch configuration page) and running the following Junos command from the CLI:

show chassis firmware

The exact output will depend on the switch and hardware configuration, as shown in the following sample:

The following tables provide upgrade recommendations with regards to a known, and since September, 2023 fixed, issue with silent reboots on the EX4400 platform. If you have a device that is effected, upgrade the BIOS and/or Junos version as instructed in the following tables.