HPE EVA Storage
1757728 Members
2268 Online
108863 Solutions
New Discussion юеВ

Re: Brocade Switch Addition - Incompatible

 
Pshedges
Trusted Contributor

Brocade Switch Addition - Incompatible

We have dual fabrics.
Each contains Brocade Director 12000.

We have recently added a Brocade 4/16 switch to the fabric, on 1 ISL with no problems.

We have recently connected 3 more ISL's so that we can then trunk the 4 link's (when all cabled all connection will be on the same quad as required for trunking).

The issue is the ISL's that have been recently added are coming up as Segmented and Incompatible, all are E_Ports at both ends.

The PID format is the same on both switches:
fabric.ops.mode.pidFormat:1

I get the following output from a fabstatsshow:

Description Count
-----------------------------------------
Domain ID forcibly changed: 0
E_Port offline transitions: 0
Reconfigurations: 6
Segmentations due to:
Loopback: 0
Incompatibility: 4 <
Overlap: 0
Zoning: 0
E_Port Segment: 0
Licensing: 0
Disabled E_Port: 0
Platform DB: 0
Sec Incompatibility: 0
Sec Violation: 0
ECP Error: 0
Duplicate WWN: 0
Eport Isolated: 0

Does anyone know how to find out what could be causing this incompatability?



8 REPLIES 8
Bill Costigan
Honored Contributor

Re: Brocade Switch Addition - Incompatible

What licenses are installed on all switches?

Just to clarify - The two switches are already in the same fabic and the single ISL between them is happy. Correct?

It is the additional 3 ISL connections between the same pair of switches that are have the problem. Correct?

Pshedges
Trusted Contributor

Re: Brocade Switch Addition - Incompatible

F2HEXSW41:admin> licenseshow
RQeyQSedddYRfzRw:
Web license
Zoning license
Fabric license
Fabric Watch license
Performance Monitor license
RddzQdSRSeSee0Rt:
Extended Fabric license

Yes, 1 ISL connected on each fabric and working fine.

It is the additional ISL's between the 12000 Director and the 4/16 Edge switches, on Fabric 1 the issue is with 3 additional ISL's and on Fabric 2 1 additional ISL (there is only 1 additional connected on this fabric due to lack of cables at the moment).
Pshedges
Trusted Contributor

Re: Brocade Switch Addition - Incompatible

Sorry - the previous licenses were fromthe 12000, the below is from the edge switch.

F2HEXSW42:admin> licenseshow
RQebdRQyeQhRfced:
Web license
Zoning license
Fabric license
Extended Fabric license
Fabric Watch license
Performance Monitor license
Trunking license
cQDyyezcStdhXzzu:
Full Ports on Demand license - additional 8 port upgrade license
Bill Costigan
Honored Contributor

Re: Brocade Switch Addition - Incompatible

The 1200 doesn't seem to have a trunking license. perhaps the edge switch is trying to set up the ISLs in a trunk and the 1200 doesn't support that.

If you connect a second ISL using a differnet quad on each switch, does that work? Note: that would keep the edge switch from trying to trunk the ISLs
Pshedges
Trusted Contributor

Re: Brocade Switch Addition - Incompatible

On Fabric 2 we have the following:

Director 12000
Blade 1 Port 7 - Working ISL - connected to port 0 on the 4/16 Switch

Blade 10 Port 1 - ISL Connected to Port 13 on the 4/16 Switch with Incompatible error.

This is the same on Fabric 1, except we have 3 ISL's plugged into Blade 10 Ports 1,2,3 and connected to Ports 13,14,15 on the edge switch and these are showing an Incompatible error.

Bill Rothanburg
Trusted Contributor

Re: Brocade Switch Addition - Incompatible

Run the portcfgshow command on both switches and check to see if the ports in question have the Disabled E_Port flag set. The portcfgeport command will allow you to change the setting.
Pshedges
Trusted Contributor

Re: Brocade Switch Addition - Incompatible

I have just checked.

None of the ports on any switch have the E_Port Disable Flag set.

Bill Rothanburg
Trusted Contributor

Re: Brocade Switch Addition - Incompatible

It could be due to the fact that the 12000 does not have a trunking license, but that doesn't make sense as the ISL on the 12000 side is on a different blade, thus a different quad. Disabling trunking on the 4/16 port with the portcfgtrunk command will prove this correct or not.

Before doing that, I would look at the output of the switchs' error logs (errshow or errdump commands) to see the reason why the ISL is not comming online. The switchshow command may also indicate what the problem is while the ISL is connected.

You might also try to reset the ports to their default configurations with the portcfgdefault command.