Switch Actions
SUMMARY Use the Actions dashboard to resolve issues affecting your switches.
When you click the Switch button on the Actions dashboard, you'll see a list of all available actions. You can then click an action to investigate further. Available actions are described later in this topic.
Your subscriptions determine the actions that you can see on the Actions dashboard. For more information, see Subscription Requirements for Marvis Actions.
Missing VLAN
The Missing VLAN action indicates that a VLAN is configured on an AP but not on the switch port. As a result, clients are unable to communicate on a specific VLAN and are also unable to get an IP address from the DHCP server. Marvis compares the VLAN on the AP traffic with the VLAN on the switch port traffic and determines which device is missing the VLAN configuration.
In the following example, Marvis identifies two APs that do not see any incoming traffic due to a missing VLAN configuration. Marvis also identifies the specific switches that are missing the VLAN configuration and provides the port information, thereby enabling you to mitigate this issue with ease.
If you need more information, you also can use the left menu to go to the Switches page. There, click on the switch to view the information for each port, including VLANs.
After you fix the issue in your network, Mist AI monitors the switch for a certain period and ensures that the missing VLAN issue is indeed resolved. Hence, it might take up to 30 minutes for the Missing VLAN action to automatically resolve and appear in the Latest Updates section.
For more information about the Missing VLAN action, watch the following video:
Negotiation Mismatch
The Negotiation Mismatch action detects instances on switch ports where negotiation is incomplete. This issue can occur when Marvis detects a duplex mismatch between devices due to the autonegotiation failing to set the correct duplex mode. Marvis provides details about the affected port. You can check the configuration on the port and the connected device to resolve the issue.
The following example shows the details for the Negotiation Mismatch action. Notice that Marvis lists the switch and the port on which the negotiation mismatch occurred.
After you fix the issue in your network, the Negotiation Mismatch action automatically resolves and appears in the Latest Updates section within an hour.
Loop Detected
The Loop Detected action indicates a loop in your network resulting in the switch receiving the same packet that it sent out. A loop occurs when multiple links exist between devices. Redundant links are a common cause for L2 loops. A redundant link serves as a backup link for the primary link. If both links are active at the same time and protocols such as the Spanning Tree Protocol (STP) are not deployed properly, a switching loop occurs.
Marvis identifies the exact location at your site where the traffic loop is occurring and shows you the affected switches. Here's an example:
Port Flap
The Port Flap action identifies ports that bounce persistently over a short time interval, indicating that a port or client has an issue. Port flapping can occur due to unreliable connections, continuous rebooting of a device connected to the port, or incorrect duplex configurations. The following example shows the details that Marvis Actions provides for a Port Flap action:
You can disable a persistently flapping port directly from the Marvis Actions page. In the Port Flap actions section, select the switch on which you want to disable a port and click the DISABLE PORT button.
The Disable Port page appears, listing the ports that you can disable. You cannot select a port if it is already disabled (either previously through the Actions page or manually from the Switch Details page).
When you disable a port, the port configurations on the selected ports change to disabled and the ports go down. After you fix the issue, you can re-enable these ports by editing the port configuration on the Switch Details page. After you re-enable the ports, you can reconnect the devices to the ports.
After you fix the issue in your network, the Port Flap action automatically resolves and appears in the Latest Updates section within an hour.
High CPU
Marvis detects switches that constantly have high CPU utilization. Various factors can cause high CPU utilization: multicast traffic, network loops, hardware issues, device temperature, and so on. The High CPU action lists the switches, the processes running on the switch along with the CPU utilization rate, and the reason for the high utilization. In the following example, you see that the fxpc process has high CPU utilization, and the cause for the high utilization is the use of noncertified optics on the switch:
Port Stuck
The Port Stuck action detects a difference in traffic pattern on a switch port, such as no transmitted or received packets, indicating that the client connected to the port is not operating normally. In the following example, you'll see that Marvis Actions recommends that you bounce the port and verify if the client starts operating normally. Notice that in addition to the port number, Marvis also lists the client (in this case, a camera) that is connected to the port and the associated VLAN.
Traffic Anomaly
Marvis detects an unusual drop or increase in broadcast and multicast traffic on a switch. It also detects any unusually high transmit or receive errors. Like the Anomaly Detection view for connectivity failures, the Details view shows a timeline, the description of the anomaly, and details of the affected ports. If the issue affects an entire site, Marvis displays the details of the affected switches and port details for each affected switch.
