This post is more than 5 years old
1 Rookie
•
51 Posts
0
562
Unregistering paths
We recently rewired our SAN to provide for better redundancy, so that our pair of Brocade 5100s now each have access to both CX-4 SPs.
This will be hard to explain without a diagram.. but here goes..
Before, they didn't,Each 5100 went direct to one SP only: A-1 or B-1. Hosts on a Dell chassis had access to both SPs however via a pair of crosswired m5424s to the 5100s, such that their HBAs registered at the time saw both A-1 and B-1; however, they did not see A-0 and B-0 as these were not connected at the time.
With the new wiring, all hosts use either port pair A-1 and B-0, OR pair B-1 and A-0.
But, for many of these HBAs, they're now registered to the old and new paths A-1, B-1, A-0, and B-0, but those connected via A-1 and B-0 are still registered with a dead path B-1 which they don't need, and likewise, those with B-1 and A-0 are still registered with A-1 too.
Is there a way to remove just those defunct paths without disruptively re-registering the entire HBA?
Thanks
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 30th, 2014 08:00
yes, slowly and very carefully
If path is listed as registered but not logged-in and you have validated that it should not be logged-in, you can simply de-register it.
lpphiggp
1 Rookie
1 Rookie
•
51 Posts
0
May 30th, 2014 09:00
So that definitely doesn't do the entire HBA then, I can definitely single out a discrete path? For clarity's sake, I prefer working in Unisphere than NacvSECcli. I just need to be careful because we have critical oracle dbs on the line.
Sorry if I'm asking redundantly, I just need to be absolutely clear and sure. On the plus side, yep, these path ports are not logged in, and couldn't be as the physical connection no longer exists.. rewired it myself.
lpphiggp
1 Rookie
1 Rookie
•
51 Posts
0
May 30th, 2014 09:00
Thanks, gave this a shot and it worked without issues.
Being that these are all linux boxes, I'd read that I should enable single initiator/single target zoning, so I did
separate zones below:
Fab A
HBA1 <-> SPA-1
HBA1 <-> SPB-0
Fab B
HBA2 <-> SPB-1
HBA2 <-> SPA-0
Which looks like what you suggested, just described differently I think.
(where backend SPA-1 is frontend SlotA port 3, SPA-0 is SlotA port 2; and SPB-1 is SlotB port 3, SPB-0 is SlotB port 2)
dynamox
2 Intern
2 Intern
•
20.4K Posts
1
May 30th, 2014 09:00
what you see in Unisphere under Connectivity Status/Initiators is a logical path between initiator (HBA) and target (SP port) . If that path is no longer there (due to zoning) you can de-register it without issue. Best practices recommends that each HBA is zoned to SPA and SPB, IE
Fabric A
host1-zone1-hba1-SPA0
host1-zone2-hba1-SPB2
Fabric B
host1-zone1-hba2-SPB0
host1-zone2-hba2-SPA2
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 30th, 2014 10:00
looks good