Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 5
Registered: ‎05-05-2014

Sfc Was Rejected: Remote Switch Unable To Process

[ Edited ]

Hi All!

We have 2 fabrics on Brocade 6520 core and Brocade 16Gbps edges (IBM chassiss switches):
(ip, wwn and names are fake here)
> fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
-------------------------------------------------------------------------
1: fffc01 10:00:00:00:f8:00:9e:11 192.168.1.61 0.0.0.0 "core01"
2: fffc02 10:00:00:00:f8:00:a0:12 192.168.1.191 0.0.0.0 >"core02_principal"
21: fffc15 10:00:00:00:f8:00:17:10 192.168.1.137 0.0.0.0 "edge01"
22: fffc16 10:00:00:00:f8:00:c8:09 192.168.1.177 0.0.0.0 "edge02"
23: fffc17 10:00:00:00:f8:00:a2:08 192.168.1.117 0.0.0.0 "edge03"
24: fffc18 10:00:00:00:f8:00:3e:07 192.168.1.234 0.0.0.0 "edge04"
25: fffc19 10:00:00:00:f8:00:23:06 192.168.1.59 0.0.0.0 "edge05"
26: fffc1a 10:00:50:00:1a:00:6e:05 192.168.1.214 0.0.0.0 "edge06"
27: fffc1b 10:00:00:00:f8:00:ce:04 192.168.1.54 0.0.0.0 "edge07"
28: fffc1c 10:00:00:00:f8:00:b4:03 192.168.1.74 0.0.0.0 "edge08"
29: fffc1d 10:00:00:00:f8:00:43:02 192.168.1.41 0.0.0.0 "edge09"
30: fffc1e 10:00:00:00:f8:00:88:01 192.168.1.43 0.0.0.0 "edge10"
31: fffc1f 10:00:00:00:f8:00:de:00 192.168.1.30 0.0.0.0 "edge11"
The Fabric has 13 switches

 

Topology:

Host - edge - core - storage
                   \   | |     /
                    \ core /

 

Each edge switch connected to each core switch by 1 ISL, cores have 2x2x16Gbps trunks between them.

 

I have upgraded switches from 7.4.1c to 8.1.1a through 8.0.2c - everythink goes fine without problems.

 

Next day i had a sutuation where all switches in fabric, except principal, lost all configs except active. And after i made changes on principal switch to active config and tried to enable it i recieved an error from cfgenable:

Sfc Was Rejected: Remote Switch Unable To Process

 

errdump from core02_principal:
2017/10/31-07:46:46, [RCS-1006], 5325, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 1 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5326, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 21 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5327, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 22 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5328, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 24 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5329, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 23 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5330, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 25 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5331, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 26 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5332, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 28 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5333, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 27 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5334, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 30 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5335, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 31 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [RCS-1006], 5336, FID 128, INFO, core02_principal, State 2, Application Zoning AD0, RCS CM. Domain 29 returned 0x8. App Response Code 3.
2017/10/31-07:46:46, [ZONE-1019], 5337, FID 128, ERROR, core02_principal, Transaction Commit failed. Reason code 3 (3) - "Sfc Was Rejected: Remote Switch Unable To Process".

 

errdump from core01:
2017/10/31-07:38:42, [RCS-1005], 241148, FID 128, INFO, core01_principal, Phase 9, Zoning Application returned Sfc Was Rejected: Remote Switch Unable To Process, 0x3000008.

 

cfgactvshow shows different members in principal and other switches.
Traffig goes normally, except those diffs.

 

I disabeld all links on edge01 (traffic disruptive action) and enabled only edge01->core02_principal i saw Zone Conflict on that port in switchshow. Then i rejoined switch to fabric (cleared its config).
After that i went to core02_principal end reenabled my config - and that works!

 

I don't know what problem in FOS 8.1 or upgrade process led to that situation.
Community should know that its possible - all info that i saw in google goes to FOS 6.2 and earlier.

Broadcom Moderator
Posts: 70
Registered: ‎03-29-2010

Re: Sfc Was Rejected: Remote Switch Unable To Process

Check for valid licensing on all switches for applications that you are enabling.

 

licenseshow, licenseIDshow - for the WWN which is used to process the license keys on each switch. If it's not a license issue, insure there are no pending transactions using 'cfgtransshow', and 'cfgtransabort' to get rid of the cfg changes that may be pending.

 

Use 'defzone --show' to check for access, and use '--allaccess' as required to allow zone transactions.

 

If all else fails, and it's neither of these issues. The next phase is pretty drastic. For each switch except the principal, 'cfgdisable', 'cfgclear', 'cfgsave' to commit it, 'cfgdelete <cfgname>' if there are any remaining cfgs. Then disable and enable each ISL E_port one at a time and see if the cfg propagates to each switch.

 

Most likely is a license mismatch on one or more switch(es).

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".

Highlighted
Occasional Contributor
Posts: 5
Registered: ‎05-05-2014

Re: Sfc Was Rejected: Remote Switch Unable To Process

I have revered FOS to 7.4 and there's no such problems.

 

Do you know what license should i check on my swiches before update to 8.0 or 8.1 ?

Broadcom Moderator
Posts: 455
Registered: ‎03-29-2011

Re: Sfc Was Rejected: Remote Switch Unable To Process

Hi,

 

So, you updated from 7.4.1c to 8.1.1 via 8.0.2c in one step. And without issues.

Further,all switches (all of them at 8.1.1?) the following day:

 

- had lost their defined configuration and active configuration except the principal switch which had an active configuration.

 

No user action - CLI or Webtools or BNA - done before the lost configuration?

 

Can you share the output from the following, if it was certain member and not all?

 

- cfgactvshow shows different members in principal and other switches




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".


Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, 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.

vADC is now Pulse Secure
Download FREE NVMe eBook