Monthly Archives: October 2011

Upgrade Brocade Fabric OS FOS firmware Brocade 4424 in Dell M1000e Blade Chassis Guide

It appears there is a lack of information on upgrading the Brocade Fabric Operating System (FOS) on an I/O Module within Dell PowerEdge M1000e Blade Chassis. This guide will show you the step-by-step on how to upgrade your internal Brocade switch in a Dell Blade Chassis and what can be expected.

First, you will need to setup a temporary FTP site so that the firmware updater can retrieve the unzipped files. Let me recommend FileZilla FTP Server which can be downloaded at http://filezilla-project.org. Setup a user name and password to the directory where the extracted contents are. Now you can begin the upgrade process.

I was instructed by the Dell Technician to update the FOS in series meaning perform the v6.0.1 update, then the v6.1.1 update and finally perform the v6.2.0c update. I was unable to perform the v6.0.1 update but went directly to v6.1.1 then to v6.2.0c without any issues making this a two step process instead of three step process.

First lets get started by logging into the Blade Chassis CMC and lunch the administration interface for the Brocade I/O Module. After that, find Switch Administration on the left, click it and then click on the Firmware Download tab.

Enter the information
Brocade Fabric OS Upgrade Step 1

Brocade Fabric OS Upgrade Step 2

At this moment, the firmware upgrade process will kick you out of your session. Close the window and re-lunch a new session.

Brocade Fabric OS Upgrade Step 3a

After you’ve restarted the session go back to the Switch Administration under the Firmware Download tab. The firmware will finally commit the last changes.

Brocade Fabric OS Upgrade Step 3b

Brocade Fabric OS Upgrade Step 4

Brocade FOS Downloads
Brocade FOS v6.0.1v6.0.1 Release Notes
Brocade FOS v6.1.1v6.1.1 Release Notes
Brocade FOS v6.2.0cv6.2.0c Release Notes

Advertisements
Tagged , , , , , , , , , , , ,

Lethal Enforcers KONAMI 054986A Capacitor Replacement & Audio Fix Schematic

The Lethal Enforcers Konami 054986A is an ‘special’ audio processor on select Konami arcades. Lethal Enforcers made by Konami has this audio processor. When I purchased the arcade the audio was fine but by the time the arcade was transferred to a different location the audio became low, muffled and it clearly sounded like there was an issue. After a bit of research, I found out that capacitors looks their ability to hold energy.

Below is the schematic of the top side of the 054986A audio processor. Their is a bottom side and I hope you do not need to replace anything on the bottom side because it will result in un-solidering 64 pins just to get to the bottom. I hope you do not have to do that. If you do need to do that make sure you have a 6-pack of Great Lakes Dortmunder Gold on hand.

KONAMI 054986A Schematic

This is what it looks like repaired!

KONAMI 054986A Fixed

Tagged , , , ,

Enable VMware EVC with Workloads Running!

As of ESX/ESXi 4.1, you can now enable Enhanced VMotion Compatibility (EVC) on a live cluster if you meet a specific criteria. EVC historically speaking required all virtual machines to be powered off in your cluster before enabling. You can enable EVC now if all your processors in your cluster are already using the same processor baseline. If there are different processor baselines in your cluster already you will not be able to enable EVC on a running cluster. This will require down-time to enable this feature. This is why it is recommended to set EVC on a new cluster prior to any VMs being added.

To enable EVC, right click on your cluster in vSphere and select Edit Settings. In the left panel, select VMware EVC then click Change. Select your desired EVC mode and the Compatibility box will indicate whether you can enable EVC with or without downtime. Below is a screenshot allowing us to enable EVC on a running VMware Cluster.

VMware Enable EVC

Reference: Enhanced vMotion Compatibility (EVC) processor support

Tagged , , , , ,

Cisco MAC Address Flapping Causing High CPU Utilization

A MAC flap is caused when a switch receives packets from two different physical/logical interfaces with the same source MAC address. The switch then learns where the MAC address is and puts in to a table. This table has the physical/logical interface and the MAC address. When flapping occurs it causes this table to be updated whenever a packet is sent/received. The more data flowing through the interface that is flapping the higher your CPU Utilization is going to be which can have serious potential negative side effects. Such as dropped packets, laggy terminal session and complete drop of network connectivity.

The following will give you the commands you need to help identify MAC Address Flapping and High CPU Utilization on Cisco Catalyst series switch. This was performed to troubleshoot CPU utilization issues on a Cisco Catalyst 4500 series switch but the same commands should be available to other Cisco switches which run the IOS firmware.

cisco4500#show processes cpu
CPU utilization for five seconds: 38%/1%; one minute: 32%; five minutes: 32%
PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process
27         524    250268          2  0.00%  0.00%  0.00%   0 TTY Background
28         816    254843          3  0.00%  0.00%  0.00%   0 Per-Second Jobs
29      101100      5053      20007  0.00%  0.01%  0.00%   0 Per-minute Jobs
30    26057260  26720902        975 12.07% 11.41% 11.36%   0 Cat4k Mgmt HiPri
31    19482908  29413060        662 24.07% 19.32% 19.20%   0 Cat4k Mgmt LoPri
32        4468    162748         27  0.00%  0.00%  0.00%   0 Galios Reschedul

The following will give you a Target CPU percent and the Actual Percent. Look for percents that greatly exceed the Target CPU percent. This will help identify what is eating your processing power on your device. This is used to troubleshoot other items than MAC Address Flapping such as Routing Loops and other bad things that can bring your network to a halt.

cisco4500#show platform health
%CPU   %CPU    RunTimeMax   Priority  Average %CPU  Total
Target Actual Target Actual   Fg   Bg 5Sec Min Hour  CPU
Protocol-aging-revie   0.20   0.00      2      0  100  500    0   0    0  0:01
Acl-Flattener          1.00   0.00     10      5  100  500    0   0    0  0:04
KxAclPathMan create/   1.00   0.00     10      5  100  500    0   0    0  0:21
KxAclPathMan update    2.00   0.00     10      6  100  500    0   0    0  0:05
KxAclPathMan reprogr   1.00   0.00      2      1  100  500    0   0    0  0:00
TagMan-InformMtegRev   1.00   0.00      5      0  100  500    0   0    0  0:00
TagMan-RecreateMtegR   1.00   0.00     10     14  100  500    0   0    0  0:18
K2CpuMan Review       30.00  91.31     30     92  100  500  128 119   84  13039:02
K2AccelPacketMan: Tx  10.00   2.30     20      0  100  500    2   2    2  1345:30
K2AccelPacketMan: Au   0.10   0.00      0      0  100  500    0   0    0  0:00

First enter enabled mode then configure terminal mode. Issue the following command to ensure there is logging for mac-move which will identify MAC Address Flapping.

cisco4500(config)#mac address-table notification mac-move

After a period of time, view the log to identify the MAC address that is flapping.

cisco4500(config)#do show log
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
...
*Oct  3 08:51:28.149: %SYS-5-CONFIG_I: Configured from console by admin on vty0 (10.10.10.236)
*Oct  3 09:43:46.437: %C4K_EBM-4-HOSTFLAPPING: Host 00:60:48:1B:01:15 in vlan 400 is moving from port Gi2/40 to port Gi2/30
*Oct  3 09:43:48.629: %C4K_EBM-4-HOSTFLAPPING: Host 00:60:48:1B:01:15 in vlan 400 is moving from port Gi2/30 to port Gi2/40
*Oct  3 09:43:48.717: %C4K_EBM-4-HOSTFLAPPING: Host 00:60:48:1B:01:15 in vlan 400 is moving from port Gi2/40 to port Gi2/30
*Oct  3 09:43:49.581: %C4K_EBM-4-HOSTFLAPPING: Host 00:60:48:1B:01:15 in vlan 400 is moving from port Gi2/30 to port Gi2/40

Furthermore, issue the following command at random periods of time to illustrate the MAC address bouncing between two different physical ports.

cisco4500#sh mac address-table address 00:60:48:1B:01:15

Unicast Entries
vlan   mac address     type        protocols               port
-------+---------------+--------+---------------------+--------------------
400    0060.481b.0115   dynamic ip                    GigabitEthernet2/30

cisco4500#sh mac address-table address 00:60:48:1B:01:15
Unicast Entries
vlan   mac address     type        protocols               port
-------+---------------+--------+---------------------+--------------------
400    0060.481b.0115   dynamic ip                    GigabitEthernet2/40

It depends on how your configuration is but it is generally a good idea to disable one of the two interfaces or fix an issue with a logical interface such as EtherChannel/LACP.

For furhter information and Cisco official documentation, http://www.cisco.com/c/en/us/support/docs/switches/catalyst-4000-series-switches/65591-cat4500-high-cpu.html

Tagged , , , , , , , ,