This post is more than 5 years old
4 Posts
0
956
July 27th, 2012 05:00
brocade switches
Hi,
Howmany domain ids can create on a brocade 7500 switch and how domain ids used in a fabric?
Thanks,
Vibes.
No Events found!
This post is more than 5 years old
4 Posts
0
956
July 27th, 2012 05:00
Hi,
Howmany domain ids can create on a brocade 7500 switch and how domain ids used in a fabric?
Thanks,
Vibes.
Top
Phukon
337 Posts
0
August 3rd, 2012 00:00
Hi,
Domain Port identification uses the switch domain ID and switch port to identify zone members.
Until Fabric OS 5.2.0, the “P” in Domain Port is equal to the port area ID and ranged in value from 0 to 255.
Since the Brocade 48000 48-port blade requires the value of P to range from 0 to 383, P is now equal to the port index for a port. Since the use of port index instead of area ID is required when using Domain Port identification on a 48-port blade, all switches in the fabric must be running Fabric OS 5.2.0 or greater. Note that Domain Port identification is not globally unique, since every fabric can have duplicate domain IDs and every switch has a port index of 1, 2, 3, and so on.
Any device cabled to a zoned Domain Port can communicate as defined by the zone configuration. The only identification method that is unique for all fabrics is pWWN.
regards,
phukon
Phukon
337 Posts
1
August 3rd, 2012 00:00
Hi ,
Also Note:
Fibre Channel Routing (FCR) and Fibre Channel Write Acceleration, use pWWN identification. For example, FCR allows zones to be created between independent fabrics using the Brocade 7500 SAN Router and/or Brocade FR4-18i Routing Blade. The routers analyze the zones in each fabric and allow nodes to communicate between the fabrics only if zones exist in both fabrics containing the relevant pWWNs. Since Brocade FCR technology uses Zoning, pWWNs must be used to uniquely identify the members of the routed zones. D,P identification cannot be used since non-unique pairs of nodes cannot be zoned, for example, domain ID 1, port ID 1 in fabric 1 cannot be zoned with domain ID 1, port ID 1, in fabric 2. Even if a fabric does not use FCR today, you should still use pWWN identification in the event that FCR is ever introduced to the fabric.
In this way, a single, consistent identification method can be used for local, non-routed zones and zones that are routed between fabrics.
Regards,
phukon.