Brocade MAPS “non-management”

Ok this may seem a bit of me having a go at Brocade’s successor to Fabric Watch but it isn’t. This week I ran into a couple of cases where switches were upgraded to FOS 7.2.x and Fabric Watch was converted to MAPS. Nothing wrong with that but it seems that many administrators blindly kick off some rule-sets via BNA and leave it at that. Whilst I applaud the move to the latest and greatest code levels (mainly because the majority of known bugs are fixed) it also means that updated and/or new functionality needs to be reviewed and actively managed.

The example below shows you the lack of active management of one of the switches. Its an abbreviated listing of an errorlog from a Brocade switch.

2014/04/08-07:49:58, [MAPS-1003], 33463, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/08-08:01:58, [MAPS-1003], 33466, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/08-08:13:58, [MAPS-1003], 33469, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/08-08:31:58, [MAPS-1003], 33473, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/08-08:43:58, [MAPS-1003], 33476, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/08-08:49:58, [MAPS-1003], 33477, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/08-09:01:58, [MAPS-1003], 33480, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/08-09:13:58, [MAPS-1003], 33485, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/08-09:19:58, [MAPS-1003], 33486, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

<snip>

2014/04/11-04:07:58, [MAPS-1003], 34501, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/11-04:25:58, [MAPS-1003], 34505, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/11-04:37:58, [MAPS-1003], 34508, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/11-04:49:58, [MAPS-1003], 34510, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/11-04:55:58, [MAPS-1003], 34512, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/11-05:07:58, [MAPS-1003], 34515, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/11-05:25:58, [MAPS-1003], 34519, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,28.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

2014/04/11-05:37:58, [MAPS-1003], 34524, SLOT 7 | FID 128, WARNING, CORE_CHASSIS, Chassis, Condition=CHASSIS(MEMORY_USAGE>0), Current Value:[MEMORY_USAGE,29.00 %], RuleName=fw_MemRuleTh3_0, Dashboard Category=Switch Resource .

As the above shows there is a MAPS ruleset active which triggers an event being logged if the meory usage is above 0% (?!?!?! (I don’t know who came up with that idea but the moment you switch on the box the boolean obviously returns true.) Irrespective if this rules being total nonsens it should be turned off or replaced with a different setting.

Given the fact the events occur over a long time-period I assume that these switches are not actively managed. What the above shows is that these event log 3 to 4 times an hour but nobody looks at it and raises any questions on the validity of these events and start to make adjustments. Not only is the above rule-set useless it also obfuscates real problems that might be logged sporadically. Such an event could be discarded simply because the eventlog wraps after a certain amount of entries. Troubleshooting issues that happen infrequently becomes very difficult this way.

In short. Even though the code is up to date it does not relieve you from actively managing the device and take appropriate actions based on events you see. Not only will you be able to identify and differentiate between garbage and useful info, it also provides much more evidence in case a serious problem has occurred. This is not only true for the example above but obviously applies to every piece of equipment/software out there. Remember, you business relies on it.

Regards,

Erwin

Print Friendly, PDF & Email

About Erwin van Londen

Master Technical Analyst at Hitachi Data Systems
Brocade, Config Guide, Troubleshooting , ,