Summary

No traffic can be seen in the real time monitor. The optimizer is not QOSing. This is due to phantom bridges in the configuration that are configured in the running configuration but they are not physically installed in the device.

Overview

No traffic can be seen in the Real Time Monitor. The Optimizer is not QOSing. This is due to the phantom bridges in the configuration that are configured in the running configuration but they are not physically installed in the device.

This scenario is characterized by the following log entries:

May 12 15:08:16 ViaWest-MPLS-10862-310 mgmtd[2844]: [mgmtd.ERR]: md_ip_mode_update_bridge_flags(), md_ip_mode.c:1733, build 1: Error code 14002 (assertion failed) returned
May 12 15:08:16 ViaWest-MPLS-10862-310 mgmtd[2844]: [mgmtd.ERR]: md_ip_mode_update_all_bridge_flags(), md_ip_mode.c:1776, build 1: Error code 14002 (assertion failed) returned
May 12 15:08:16 ViaWest-MPLS-10862-310 mgmtd[2844]: [mgmtd.ERR]: md_ip_mode_commit_apply(), md_ip_mode.c:2413, build 1: Error code 14002 (assertion failed) returned
May 12 15:08:16 ViaWest-MPLS-10862-310 mgmtd[2844]: [mgmtd.ERR]: Error 14002 (assertion failed) returned from apply function for module: ip_mode_module
May 12 15:08:16 ViaWest-MPLS-10862-310 mgmtd[2844]: [mgmtd.WARNING]: Apply error without explicit commit return code for module ip_mode_module

Root Cause

This is usually caused by importing configuration from one Exinda appliance to another. The reason would be because depending on the hardware model, the Bridge/Ethernet port numbers can be different. The configuration for the ports will still import successfully from the first device onto the second device, and can cause the above error.

Resolution

There is a newer section of the configuration called bridging configuration.

1. Log in to the WebUI.
2. Navigate to system/network to see the installed interfaces/bridges
3. Download the system diagnostic or a copy of the running configuration.
4. Open the system info file in the dump
5. Examine which interfaces are showing enabled and are not physically installed in the appliance.
   
   1. Log into the CLI on the device.
   2. en
   3. conf t
   4. no interface br# create
   5. Repeat for every phantom bridge
   
   You may need to try:
   
   1. Log into the cli
   2. en
   3. conf t
   4. no bridge #
   
   Repeat for all phantom bridges
   
   Additional steps that might be needed:
   You may run into difficulty with the commands not working or not being accepted by the CLI. In this case:
   
   1. Log into the webui
   2. Go to system/maintenance/import config
   3. Copy the below text and use the appropriate bridge number:
   
   *** You may only need to copy and paste "no br# enable" into the Webui. I suggest trying that first.
   no bridge br22 ageing-time -1
   no bridge br22 enable
   no bridge br22 forward-time -1
   no bridge br22 hello-time -1
   no bridge br22 max-age -1
   no bridge br22 mq mode auto-license
   no bridge br22 mq switch-bandwidth 1850000000
   no bridge br22 priority -1
   
   4. Repeat this and substitute each phantom bridge into the commands.
   5. It will prompt for an optimizer restart. Once you have entered the commands for all the phantom bridges, restart the optimizer and the traffic came back.
   6. Don't forget to save the changes to the system.