Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 6
Registered: ‎05-19-2016

Building a Fabric

Hello All,

 

I am trying to build a fabric between two Brocade 8000 switches. I have them connected via a cable between two FC ports (The port leds are green). If I do the "fabricshow" command both siwtches appear, and I can see the target from the initiator and send traffic to it successfully (they are on different switches). The problem I am having is when I look in the name server of each of the switches, only the devices that are directly connected to the switch appear in the name server. The switches do not share name servers. 

 

I also took a trace between the two switches to see what is happening and the two switches are just sending LIPs back and forth.

 

I am wondering if there is some command that I need to do, or configure the ports that are connecting the two switches in some way.

 

Thanks,

Philip

Brocade Moderator
Posts: 36
Registered: ‎03-29-2010

Re: Building a Fabric

[ Edited ]

Lets try this. From each switch, run the 'nscamshow' command. This should display the cached entries of the remote name server devices.

 

Alternately, you can run the 'nsallshow', which will give you all of the PIDs logged into the name server for the entire fabric. Then, run the 'switchshow' command on each switch and hunt down the PIDs to see who is logged in.

 

Finally, lets hope that the E ports are not sending LIPs back and forth as this would be a Loop Init Process. They will be sending a few ELPs(Exchange Link Parameters) to get synchronized. If they are sending a bunch of ELPs back and forth, something is wrong. Take a look in the portlogdumpport <portnum> for whats going on with the E ports on each switch.

 

It's useful to copy and paste the output form the commands you are running so we can get a better idea of what's happening. If you want to obscure the device entries, or name entries, that's fine, but the state of the devices and E ports would be real handy.

 

Best of luck.

doc

Any and all information provided by me is for entertainment value and should not be relied upon as a guaranteed solution or warranty of mechantability. All systems and all networks are different and unique. If you have a concern about data loss, or network disconnection, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, Please mark it with the button at the bottom "Accept as solution".

External Moderator
Posts: 4,907
Registered: ‎02-23-2004

Re: Building a Fabric

@pkessler9

 

are you on FOS 6.x.x_cee or FOS 7.1.x ?

TechHelp24
Occasional Contributor
Posts: 6
Registered: ‎05-19-2016

Re: Building a Fabric

Hi,

 

Using the 'nscamshow' command I get:

nscam show for remote switches:
Switch entry for 3
state rev owner cap_available
known v701 0xfffc01 1
Device list: count 1
Type Pid COS PortName NodeName
N 030000; 3;20:91:9c:74:1a:e5:82:0c;ff:ff:0c:82:e5:1a:74:9d;
FC4s: FCP
PortSymb: [28] "-----(Removed Name)------ "
Fabric Port Name: 20:00:00:05:1e:76:c8:80
Permanent Port Name: 20:91:9c:74:1a:e5:82:0c
Port Index: 0
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No

 

Using the 'nsallshow' command I get that there are 3 Nx_Ports in the fabric. This is correct as there are two devices attached to the switch then the thrid port attaches to the other switch.

 

When I use the 'portlogdump' command with the port that is attached to the other switch I get:

09:33:45.205 PORT Rx 1 40 02fffffd,00fffffd,0f10ffff,14000000
09:33:45.205 PORT Tx 1 0 c0fffffd,00fffffd,0f100f33,00000001
09:33:45.205 FCPH read 1 40 02fffffd,00fffffd,c4000000,00000000,0f100f33
09:33:45.205 FCPH seq 1 28 22380000,0f100f33,00000666,0000001c,00000000
09:34:05.126 FCPH write 1 40 00fffffd,00fffffd,00000000,00000000,00000000
09:34:05.126 FCPH seq 1 28 00300000,00000000,000006dc,00020182,00000000
09:34:05.126 PORT Tx 1 40 02fffffd,00fffffd,0f34ffff,14000000
09:34:05.126 PORT Rx 1 0 c0fffffd,00fffffd,0f340f11,00000001
09:34:05.205 PORT Rx 1 40 02fffffd,00fffffd,0f12ffff,14000000

And this pattern just repeats itself.

 

Also, when I look at the 'switchshow' command I notice that FC Router is set to off. Is this something that is causing my problem? I have tried looking for a command to turn it on but have been unseccessful.

V_E05:admin> switchshow
switchName: V_E05
switchType: 76.7
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:05:1e:76:91:00
zoning: OFF
switchBeacon: OFF
FC Router: OFF
FC Router BB Fabric ID: 1
Address Mode: 0

Index Port Address Media Speed State Proto
==============================================
0 0 010000 id N8 Online FC F-Port 10:00:00:9c:02:24:83:9d
1 1 010100 id N4 Online FC E-Port 10:00:00:05:1e:76:c8:80 "swd77" (downstream)
2 2 010200 -- N8 No_Module FC
3 3 010300 id N2 Online FC F-Port 50:06:01:61:30:21:4f:c0
4 4 010400 -- N8 No_Module FC.

 

 

Also, the version I am running is V 6.4.0 if that helps.

 

Regular Contributor
Posts: 164
Registered: ‎05-11-2011

Re: Building a Fabric

Hi,

 

you do not have a problem with your Fabric !

 

nsshow gives you only the output of the local connected devices, nscamshow all connetcted devices to remote switches.

 

 

 

Kind Regards
Ralf
Brocade Moderator
Posts: 36
Registered: ‎03-29-2010

Re: Building a Fabric

[ Edited ]

Alrighty then. Your switches are connected on an ISL, shown on port 1 in the switchshow output as 'E-Port' to downstream swd77 switch. The portlogdump shows normal FC traffic, just writes and reads, etc. Three devices are logged in to the name server, which appears correct, and they are functionally communicating together in an un-zoned open switch format(note the output of zoning is OFF).

 

The FC Router: OFF is normal for the Brocade 8000 as it does not support the layer 3, FC routing protocol, just the CEE, FC, or FCoE protos. There is no command to turn it on, as it's not capable.

 

Moving forward, a few things you may want to investigate. The B8000 switch supports 8GB speeds, but the ISL between the two switches appears to be negotiated down to 4GB speed. If you would run the sfpshow 1 for that switch V_E05 and see which type/speed of SFP is installed, then do the same for the other switch, this will discover if the SFPs will support 8GB. If they will, run the portloginshow command for each port and check the login history for each of the ports.

 

Next, Brocade best practice is to use zoning to logically segregate devices which will communicate together, rather than an 'ad-hoc' all-to-all type of communication matrix. If you would download the FOS Admin guide from the My Brocade website 'documents' tab, you can investigate the process of using aliases, zones, and a zone database to configure who may 'talk' to whom based on the zoning membership. Some folks say that zoning is best done with the WebTool interface from a browser pointed at your switch IP, example: http://192.168.10.1 which will load the WebTool client and allow you to do some basic management functions, incuding zoning, and it also gives a nice interactive GUI to see what's what on the switches.

 

Finally, there are several improvements and defects solved in later versions of FOS. You may want to consider upgrading your Fabric OS to a later version if you are supporting CEE or FC0E protos, They can be found under the 'downloads' tab at M Brocade by loading the Fabric OS versions from the drop down.

 

Best of luck,

doc

Any and all information provided by me is for entertainment value and should not be relied upon as a guaranteed solution or warranty of mechantability. All systems and all networks are different and unique. If you have a concern about data loss, or network disconnection, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, Please mark it with the button at the bottom "Accept as solution".

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.