This is happening because the new switch have the same Domain ID as the existing one. Well first of all, we need to go to the Web Management for our Brocade switch which is usually (change ip_address with your own IP, duh!) and login. The following message can be shown in the event log : Warning port 0, domain IDs overlap. In my case, the other IDs are 115 and 116, so we will give this one another ID of 17 for example. OK! So now that we have our physical connection in place, let’s go into the Brocade and configure those ports.Īnother very important step is to make sure the Switch ID is different from the others.
If you are using patch panels in the middle, make sure you are connecting to the correct ports. Switch A -> Port 15 to Switch B -> port 15 where again the modules are the same and the cables are the same. The physical connection would look like this: Usually we would connect the same port number on both switches, but that’s not required. If our switches are in different locations and the distance is over 400m or 1300ft or 0.2mi (yeah I love that distance conversion), we will need to use a LW (Long Wave) module, which in general has as blue latch, and to use SM cables (Single-Mode) for long distances. If not, they will be more like Etherchannel.If the switches are close to one another, we can use a standard SW (Short Wave) module with a minimum of a OM3 (Blue) cable or Multi-Mode cable. If you have a trunking license, this bandwidth will fully aggregate. It's also worth mentioning that you can have multiple ISLs for redundancy and increased bandwidth between the switches. I know it seems to be a bit particular, but it's better to be controlled than let the switches try to do the thinking for you and ending up with a mess of zones and interoperability issues. Check all connections, bring up any hosts you needed to have down, etc. Once all is well, start re-enabling your switch ports on the secondary switch, and you should be good. Switchshow, islshow, trunkshow, all helpful here. types of zoning in san, cisco zoning commands, vmax3 provisioning steps, snapvx, san zoning, unix flavors, timefinder snapvx, san storage explained. This more or less means, that if you put a bunch of people in a room, and the only thing in common is that they speak 10 words of swahili, that they try to communicate in swahili, regardless of how little they will succeed. Eg o/p would be (010000) where 01 is switch domain ID, 00 is port no. NOTE: Switch type output displays these values with 1.x for the Brocade 1000 family, 2.x for Brocade 2800, and so on. Be careful of enterring "Interoperability mode". If you do not know the model, you can use this table to map the switch ID to the name. Next, disable all the secondary switch ports, connect your ISL and ensure that you have all of the zones across both switches.
You can also for pricipality by using "fabricprincipal". before you connect your switches, back up their configs, and create up a single zoning set on the principal switch (lowest domain ID, highest model). I can't recall, but I believe it's done with "configure".Īfter all this. You will need to switchdisable to change this (offline change). If the switchDomain on both switches is "1", one must be changed to something else. At the top of a switchshow, you will see ad Domain ID: If you don't have this set to 1, the nPort addressing will be formatted differently and when you mix multiple switch domains, the domain will not be part of the nPort, which will cause problems for your naming services. To find this, do a "configshow" at the switch and look for the following text:
Next, you need to ensure the PID format is set to 1. You will need to look at the B-Series Connectivity Stream ( )ĭo not connect your switches until you have done this and checked a few other things. You can do this from the support matrices in SPOCK. HPE Blog, Austria, Germany & Switzerlandįirst, you need to ensure that the version of firmware on both switches is interoperable.