Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
cfgenable does not work. It goes into hung state. switch-2:FID54: admin> cfgenable TEST_LEFT You are about to enable a new zoning configuration. This action will replace the old zoning configuration with the current configuration selected. If the update includes changes to one or more traffic isolation zones, the update may result in localized disruption to traffic on ports associated with the traffic isolation zone changes. Do you want to enable 'TEST_LEFT' configuration (yes, y, no, n): [no] y errdump : 2021/12/12-15:00:39, [RTWR-1003], 85795, SLOT 1 | FID 54, INFO, switch-2, rcsd0: RTWR retry 100 to domain 37, iu_data 7c000070. 2021/12/12-15:00:52, [RTWR-1002], 85796, SLOT 1 | FID 54, WARNING, switch-2, RTWR Maxretries exhausted: 0x4c1, 0x25, 0x65, 0x0, 0x996. 2021/12/12-15:00:52, [RCS-1006], 85797, SLOT 1 | FID 54, INFO, switch-2, State 4, Application Zoning AD0, RCS CM. Domain 37 returned 0x0. App Response Code 0. 2021/12/12-15:00:52, [ZONE-1019], 85798, SLOT 1 | FID 54, ERROR, switch-2, Transaction Commit failed. Reason code 2 (0) - "Aca Was Rejected: Remote Switch Busy, Retry in a few seconds". All the RTWR entries are pointing to switch with domain 37 (switch-7): switch-7:FID1: admin> cfgtransshow There is no outstanding zoning transaction switch-7:FID1:admin> cfgtransshow --opentrans There is no outstanding zoning transaction Transactions Detect: Capable Current Open Transactions Domain List: ------------ These RTWR errors date back to around 21:08 on Dec. 2nd when it looks like one of the XISLs went offline due to fabwide policy conflict: 2021/12/02-21:08:36, [SEC-1326], 59592, SLOT 1 | FID 54, INFO, switch-7, Event: fddcfg --fabwideset, Status: success, Info: Fabric wide configuration set to SCC:S;FCS. 2021/12/02-21:08:36, [SEC-1319], 59593, SLOT 1 | FID 54, INFO, switch-7, fabwideset updated SCC FCS FABWIDE dbs(s). 2021/12/02-21:08:38, [SEC-1335], 59594, SLOT 2 | FID 54, WARNING, switch-7, Strict Fabric wide policy is conflicting with domain 42. 2021/12/02-21:08:42, [MAPS-2318], 59595, SLOT 2 | FID 54, WARNING, switch-7, Switch, Condition=SWITCH(EPORT_DOWN/min>=1), Current Value:[EPORT_DOWN, 1 Ports], RuleName=FAB_E_PORT_DOWN_AH_1, Dashboard Category=Fabric State Changes. 2021/12/02-21:11:43, [ESS-2001], 59596, SLOT 2 | FID 54, WARNING, switch-7, Fabric Hello Timeout: Inter-switch Frame Delivery problem - remote Switch Domain 42, port 1245. 2021/12/02-21:12:48, [RTWR-1003], 59597, SLOT 2 | FID 54, INFO, switch-7, msd3: RTWR retry 8 to domain 42, iu_data 1000000. 2021/12/02-21:13:36, [RTWR-1003], 59598, SLOT 2 | FID 54, INFO, switch-7, msd3: RTWR retry 12 to domain 42, iu_data 1000000. 2021/12/02-21:14:22, [RTWR-1003], 59599, SLOT 2 | FID 54, INFO, switch-7, msd3: RTWR retry 16 to domain 42, iu_data 1000000. >>>> Domain 42 belongs to switch-2 21:08:47.617036 SCN Port Offline;rsn=0x10000,g=0x2baa A2,P3 A2,P0 1252 NA 21:08:47.617040 *Snd port state: P0 A2,P0 A2,P0 1252 NA 21:08:47.617071 *Removing all nodes from port A2,P0 A2,P0 1252 NA LISL port 1252 went disabled at that time: CURRENT CONTEXT -- 3, 54 /fabos/bin/switchshow : switchName: switch-7 .. Allow XISL Use: ON LS Attributes: [FID: 54, Base Switch: No, Default Switch: No, Ficon Switch: No, Address Mode 0] Index Slot Port Address Media Speed State Proto ============================================================ 1252 -1 1252 ------ -- -- Offline FC Disabled (FDD conflict - Strict Fabric Wide policy conflict) lfcfg --showall -lisl -v: FID Port# Remote Domain Name State Associated Physical Ports 54 1252 42 switch-2 Create Failed 7/8 7/9 7/10 7/11 8/0 8/1 8/2 8/3
LISL disabled (FDD conflict - Strict Fabric Wide policy conflict).
Brocade engineering suggested that getting the LISL back online solves the issue.Issue below command in FID 54 of switch-7 and the port comes online and we are able to successfully perform a 'cfgenable' on switch-2: lfcfg –lislenable The command reenables all LISLs in the fabric that were disabled either due to '-lisldisable' option used during logical switch creation or by some conflict or error condition in the fabric. This command provides the option of manually reestablishing the LISLs after the error condition is resolved.This is non-disruptive to already online ISLs.