- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: portDisableReason: Zone member of (d, peer ind...
HPE EVA Storage
1752604
Members
4454
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2009 06:02 AM
11-02-2009 06:02 AM
portDisableReason: Zone member of (d, peer index) is on a pre-5.2 switch
Hi ,
At our SAN we are using DCX , 48000 and 12000 SAN switchs. On the DCX , we see that two ports are disabled with the reason below. Do anyone has an idea ? ( Ports are not zoned as far as we could find. )
260 1 36 058c80 id 4G In_Sync Disabled (Zone member of (d, peer index) is on a pre-5.2 switch)
At our SAN we are using DCX , 48000 and 12000 SAN switchs. On the DCX , we see that two ports are disabled with the reason below. Do anyone has an idea ? ( Ports are not zoned as far as we could find. )
260 1 36 058c80 id 4G In_Sync Disabled (Zone member of (d, peer index) is on a pre-5.2 switch)
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2009 08:32 AM
11-03-2009 08:32 AM
Re: portDisableReason: Zone member of (d, peer index) is on a pre-5.2 switch
Hi,
this looks like a port numbering problem. Every port has a 24-bit address.
Example: 010F00 - the first byte (01) is the Domain ID of the switch - in this case 1
The second byte (0F) is the "Area" or Port number. Here this is 15 (0F Hex). The third byte used to be zero, except for Loop Devices. In this address format, you could only have 256 ports on a single switch (2nd byte is 00 to FF). With 48-Port blades, which are supported in Fabric OS 5.2.0 and higher in the 48000 and DCX, one bit is "borrowed" from the 3rd byte, to allow another 128 Ports. So you can have ports with PID 058C00 (Area 140) and 058C80 (Area 260). All ports with an Area of 256 or higher have 80-Hex as the 3rd byte.
The Brocade 12000 can only go to FOS 5.0.5f, so I don't think it supports zoning to devices attached to a port higher than 255 anywhere in the fabric (I'm not sure about this, though).
Are there devices attached to this 12000 that could be zoned to the device that is on port 260 on the DCX?
Can you move the device from port 260 to another port (number 255 or lower)? You would have to be careful if port 260 is a storage device, and you have it zoned to Unix (especially HPUX pre-11.31) Servers. I don't know if this will solve the problem, but you could try.
In the medium term, you should plan to get rid of the 12000 Switches. I still have some in my SAN, and I am in the middle of replacing them. They're too old, and cause too many inconveniences.
Regards,
Stephen
this looks like a port numbering problem. Every port has a 24-bit address.
Example: 010F00 - the first byte (01) is the Domain ID of the switch - in this case 1
The second byte (0F) is the "Area" or Port number. Here this is 15 (0F Hex). The third byte used to be zero, except for Loop Devices. In this address format, you could only have 256 ports on a single switch (2nd byte is 00 to FF). With 48-Port blades, which are supported in Fabric OS 5.2.0 and higher in the 48000 and DCX, one bit is "borrowed" from the 3rd byte, to allow another 128 Ports. So you can have ports with PID 058C00 (Area 140) and 058C80 (Area 260). All ports with an Area of 256 or higher have 80-Hex as the 3rd byte.
The Brocade 12000 can only go to FOS 5.0.5f, so I don't think it supports zoning to devices attached to a port higher than 255 anywhere in the fabric (I'm not sure about this, though).
Are there devices attached to this 12000 that could be zoned to the device that is on port 260 on the DCX?
Can you move the device from port 260 to another port (number 255 or lower)? You would have to be careful if port 260 is a storage device, and you have it zoned to Unix (especially HPUX pre-11.31) Servers. I don't know if this will solve the problem, but you could try.
In the medium term, you should plan to get rid of the 12000 Switches. I still have some in my SAN, and I am in the middle of replacing them. They're too old, and cause too many inconveniences.
Regards,
Stephen
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP