- Publication Number: -03 Publication Date: March, 2008 Brocade 5000 Hardware Reference Manual Supporting Fabric OS v5.3 Supporting Brocade 5000.
- The Brocade 300 operates seamlessly with existing Brocade switches through native EPort connectivity into Brocade Fabric OS® (FOS) or M-Enterprise OS (M-EOS)1 environments. In addition, the Brocade 300 can enable future expansion to larger core-to-edge network architectures as business needs dictate. To facilitate deployment, the Brocade 300.
- The Brocade should be able to work as a standalone SAN switch. The problem will show up if you want to form a fabric with 2 or more switches. Then you need a fabric license, and you need to contact the vendor of the Brocade 300 to purchase the fabric license.
AuthorSheaTotal downloads 665UploadedChecked Dr.Web No virusesLink:DOWNLOAD NOW Searched brocade switch license key generator keygen? To download the “brocade switch license key generator keygen” one file you must go to one of the links on file sharing.
Sometimes you need to convert a Brocade model name to an IBM model name (or the other way around). One way to assure yourself with scientific accuracy which type of switch you are working on, is to telnet or SSH to a switch and issue a switchshowHumko tumse pyaar hai 2006 hindi movie download hd 720p. command. You will get a switchType value. In this example, my switch is a switchtype 27.2.
Type 99 arisaka serial numbers. Or if you are using the Web GUI, you can also see the switch type on the opening screen. In this example the switch is a type 34.0. Om dhun.
Having scientifically determined the type of switch, we can now use my decoder ring to determine the IBM machine type, IBM model name and the Brocade model name. I have ordered the switches by Type number. There are three things to note:
- Brocade have dropped the Silkworm branding, so I have dropped it too.
- Each switch type has sub-types, for example 34.0 and 34.1. The difference is a sub-version number which is normally not published or documented.
- IBM announced 16 Gbps SAN switches on August 16, 2011 so I updated the chart on that date.
If you use Data Center Fabric Manager (DCFM), it actually displays the Switch Type using Brocade model names. Here is an example report from the DCFM we are running in my lab. This level of information is very helpful.
Brocade switches have the ability to automatically assign licenses from a license pool with the Dynamic Ports on Demand (POD) feature. Once a server blade with an HBA is installed, the Dynamic POD feature will assign port license(s) as they come online. When the active ports have exhausted the current POD license pool, additional ports will not be assigned a license. Ports not assigned a license can be identified by a state of (No POD License) Disabled. After a port is assigned a license, the port is licensed until it is manually removed. That being the case, there are times when an administrator may need to move licenses from unused ports to a newly used port.
Release and Reserve a Brocade Port License from CLI
To kick this process off, SSH to your Brocade switch and run the licensePort –show command.
A couple of items to take note of here. First, we can see that we have 12 licenses for use on our switch. In addition, we can see we have three ports that are offline but are licensed. In our instance, we want to assign one of the offline port licenses to a different port.
To do so, we will disable a licensed offline port, release the license from that port, and assign/reserve the new port with a license.
To start, we will verify details for the port where we will eventually disable and remove the license. Run the portShow <portnumber> command. For our example, the port in question is 8.
portShow 8
Here we can see that the port is licensed and already disabled. If the port had not been disabled, run the portDisable <portnumber> command.
Next, we will release the port from the POD set, effectively releasing the license back into the pool. This is achieved by running the licensePort –release <portnumber> command.
licensePort –release 8
Run the licensePort –show command to verify the license has been removed from the port.
We now see port 8 is not assigned a license and we have 1 license reservation for use by unassigned ports.
Now, we will assign/reserve the freed up license for port 5. To do so, run the licensePort –reserve <portnumber> command.
licensePort –reserve 5
Run the portShow command to ensure the port is licensed.
We see the port is licensed, but still disabled.
Let’s enable the port by running the portEnable <portnumber> command.
Executing the portShow command, we can verify the port is Active and Online.
Ensure you perform this process on both Brocades.
Release and Reserve Brocade Port License from GUI
If the GUI is more your speed, you can also move licenses via the management console.
To begin, log into the Brocade management console. Next, enable the Advanced View by clicking the View menu item and selecting the Advanced radio button.
From the Port Admin tab, we can gather the pertinent information. In our example, we know we want to license and enable port 6. Here we can see the port is disabled and not licensed. Additionally, we know we want to release the license from an unused/disabled port; specifically port 9.
First, we will remove the license from port 9 by right-clicking the port and selecting Release License.

You will be prompted to release the POD license for the selected ports. Click Yes to continue.
Next, apply the available license to the new port by right-clicking the port and selecting Reserve License.
Lastly, enable the port by right-clicking the port and selecting Persistent Enable.
Brocade License Add
Select Yes to enable the port.
Perform this process on both Brocades.
Brocade License Show
NOTE – If you are zoning on a Brocade SAN Switch and you are unable to see the HBA WWN of a newly installed blade, port licensing is a good place to check.
Brocade 300 License Activation
Related Posts
