For more details, please see ourCookie Policy.

Fibre Channel (SAN)

Posts: 24
Registered: ‎06-25-2015

How to update the portIndex sequence for 2109-M48

Hello Community,


I am trying to fix a PortIndex issue at 2109-M48, but I only found a portswap as a valid fix, but I would like to know if there are another command or configuration to update those ports.

today Slot1 have this configuration


1           0(0x0)   0(0x0)

1           1(0x1)   1(0x1)

1           2(0x2)   2(0x2)

1           3(0x3)   3(0x3)

1           4(0x4)   4(0x4)

1           5(0x5)   5(0x5)

1           6(0x6)   6(0x6)

1           7(0x7)   7(0x7)

1           8(0x8)   8(0x8)

1           9(0x9)   9(0x9)

1           10(0xA)   10(0xA)

1           11(0xB)   11(0xB)

1           12(0xC)   12(0xC)

1           13(0xD)   130xD)

1           14(0xE)   140xE)

1           15(0xF)   15(0xF)

1           16(0x10) 128(0x80)




1           31(0x1F) 143(0x8F)

2           0(0x0)   16(0x10)


I know that doing a portswap between 1-16(0x10) and 2-0(0x00) can put this sequence as I need, but seems this is not the correct action for this problem.


Does anybody can help me with this issue?




Carlos Magno


Occasional Contributor
Posts: 13
Registered: ‎06-14-2004

Re: How to update the portIndex sequence for 2109-M48

[ Edited ]

Avoid updating the port index sequence for standard 2109-M48 user blades.  The SAN FC blade physical ports are designed to be portindexed in this way

  1. to be legacy compatible
  2. to be expansion compatible

The Brocade SAN port swap feature is only designed for use in harder to modify hard-zoned fabrics like Mainframe FICON Fabrics to temporarily swap two existing physical ports (eg a faulty port to a good port) without having to also modify the mainframe IODFs at the same time.

There is actaully another FOS command "portaddress --bind <slot>/<port> <hhhh>" that can be used to change a physical SAN FC port's assigned port index to an new unused port index <hhhh>value.  We've had to use this command on a 2498-B80 (Brocade 5300) to correct some really strange port index numbering on this new unit when the 80 FC port switch was to be used as a FICON director.

NOTE - if you do  modify the physical FC port indexes then you may be unable to install any additional SAN port or SAN router blades in your free 2109-M48 user slots afterwards due to FC port index conflicts.

Posts: 24
Registered: ‎06-25-2015

Re: How to update the portIndex sequence for 2109-M48

[ Edited ]

Hi Jonathan,

thanks for these explanation and help.

I had the same problem with a 2499 model and after configure the addressing mode from 0 to 1, all portIndex were fixed, but this 2109 doesn't have the same option to update using the "configure" command.

Trying to use the PortAddress --bind command I am facing a problem that I also had at the 2499 when I tried to use the same command and as I said before, it was fixed only updating the addressing mode.... look that...


SW_2022:admin> portshow 1/16
portIndex: 128
portHealth: OFFLINE

Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x1     PRESENT U_PORT
LocalSwcFlags: 0x0
portType:  10.0
portState: 2    Offline  
Protocol: FC
portPhys:  4    No_Light     portScn:   2    Offline   
port generation number:    0
state transition count:    1          

portId:    228000
portIfId:    4312002a
portWwn:   20:80:00:05:1e:36:40:8e
portWwn of device(s) connected:

Distance:  normal
portSpeed: N4Gbps

LE domain: 0
FC Fastwrite: OFF
Interrupts:        2          Link_failure: 0          Frjt:         0          
Unknown:           0          Loss_of_sync: 0          Fbsy:         0          
Lli:               2          Loss_of_sig:  2          
Proc_rqrd:         0          Protocol_err: 0          
Timed_out:         0          Invalid_word: 0          
Rx_flushed:        0          Invalid_crc:  0          
Tx_unavail:        0          Delim_err:    0          
Free_buffer:       0          Address_err:  0          
Overrun:           0          Lr_in:        0          
Suspended:         0          Lr_out:       0          
Parity_err:        0          Ols_in:       0          
2_parity_err:      0          Ols_out:      0          
CMI_bus_err:       0          

Port part of other ADs: No
SW_2022:admin> portaddress --bind 1/16 1000
portAddress --bind failed:
The indicated partition does not support this operation.

SW_2022:admin> portaddress --bind 1/16 0x221000
portAddress --bind failed:
The indicated partition does not support this operation.


Do you know how to bypass/fix this "the indicated partition does not support this operation"?


Text copied from Fabric OS Administrator's Guide pag 27 reference 53-1001336-01...


Port identification by port area ID
The relationship between the port number and area ID depends upon the PID format used in the
fabric. When Core PID format is in effect, the area ID for port 0 is 0, for port 1 is 1, and so forth.
For 32-port blades (FC4-32, FC8-32), the numbering is contiguous up to port 15; from port 16, the
numbering is still contiguous, but starts with 128. For example, port 15 in slot 1 has a port number
and area ID of 15; port 16 has a port number and area ID of 128; port 17 has a port number and
area ID of 129.


Is it possible update this concept and change port 16 to have 10 as port ared ID instead 128?




Carlos Magno

Join the Broadcom Support Community

Get quick and easy access to valuable resources across the Broadcom Community Network.