Fibre Channel (SAN)

Reply
Contributor
Posts: 23
Registered: ‎05-27-2013
Accepted Solution

Fabric segmentation on default logical switch

[ Edited ]

Hello Everyone,

 

I have a default logical switch on a DCX8510-8 (Fabric OS:  v7.1.0c) with all its ports persistently disabled but somehow it generated an allert:

 

Fabric Segmentation, is above high boundary(High=1, Low=0). Current value is 3 Segmentation(s)/minute.

 

 

I'm having trouble understanding how such fabric (single switch, no ISLs, all ports persist-disabled) can segment at all. Errdump, auditdump and clihistory don't show any other events around the time segmentation was reported.

 

Anybody having an idea what to look for and where?

 

Thanks in advance.

Valued Contributor
Posts: 761
Registered: ‎06-11-2010

Re: Fabric segmentation on default logical switch

Hi,

 

can you paste the complete event?

Contributor
Posts: 23
Registered: ‎05-27-2013

Re: Fabric segmentation on default logical switch

Hi, thank you for taking interest.

 

Here's the details of the event:

 

Property	Value 	
Probable Cause	Indicates that the number of segmentations has risen above the high boundary. Segmentation changes might occur due to the following reasons: Zone conflicts.  Domain conflicts.  Segmentation of the principal link between two switches.  Incompatible link parameters. During E_Port initialization, ports exchange link parameters. Rarely, incompatible parameters result in segmentation.	
Description	Fabric Segmentation, is above high boundary(High=1, Low=0). Current value is 3 Segmentation(s)/minute.	
Count	1	
Origin	SNMP Trap	
Port Name	N/A	
Message ID	FW-1127	
First Event Server Time	Tue Dec 16 03:59:52 CET 2014	
Fabric Name	 ANZ_SAN768_1-DEFAULT	
Product Address	172.23.148.145	
Audit	N/A	
Category	Product Event	
Last Event Product Time	Tue Dec 16 03:59:52 CET 2014	
Last Event Server Time	Tue Dec 16 03:59:52 CET 2014	
Severity	Info	
Source Name	 ANZ_SAN768_1	
Virtual Fabric ID	128	
Contributor	None	
Recommended Action	No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.	
First Event Product Time	Tue Dec 16 03:59:52 CET 2014	
Node WWN	10:00:00:27:F8:56:1A:00	
Operational Status	Healthy	
Source Address	172.23.148.145	
Module Name	Product Event	
Acknowledged	No	

 And the associated FabricWatch alert:

 

Property	Value 	
Probable Cause	N/A	
Description	Fabric Watch has generated an event:Threshold fabricSC000 in Class/Area swFwFabricSc at index 1 has generated event 3 with warning	
Count	1	
Origin	SNMP Trap	
Port Name	N/A	
Message ID	N/A	
First Event Server Time	Tue Dec 16 03:59:52 CET 2014	
Fabric Name	 ANZ_SAN768_1-DEFAULT	
Product Address	172.23.148.145	
Audit	N/A	
Category	Product Event	
Last Event Product Time	Tue Dec 16 03:59:52 CET 2014	
Last Event Server Time	Tue Dec 16 03:59:52 CET 2014	
Severity	Alert	
Source Name	 ANZ_SAN768_1	
Virtual Fabric ID	128	
Contributor	None	
Recommended Action	N/A	
First Event Product Time	Tue Dec 16 03:59:52 CET 2014	
Node WWN	10:00:00:27:F8:56:1A:00	
Operational Status	Healthy	
Source Address	172.23.148.145	
Module Name	Product Event	
Acknowledged	No	

 

Frequent Contributor
Posts: 130
Registered: ‎02-05-2014

Re: Fabric segmentation on default logical switch

Most likley related to some known defects. Your FOS level should be brought up to scratch with current GA levels. Will very likely solve your problem as well.

Kind regards,
Erwin van Londen
Brocade Distinguished Architect
http://www.erwinvanlonden.net The Fibre Channel blog


Contributor
Posts: 23
Registered: ‎05-27-2013

Re: Fabric segmentation on default logical switch

Hi,

 

upgrades are on the way, should happen within next month. We'll see if it keeps happening then.

 

Regards,

Mika

Join the Community

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