When are "EALP" events observed on Brocade switch?
Applies to
Brocade Switch
Answer
EALP
stand for "Exchange Active Link Parameters" and this is supported only on the version that has Traffic Optimizer (FOS v9.1 and above).- The EALP events are exchanged during port group operation by the traffic optimizer or when a switch joins or rejoins a fabric and are informational in nature.
Additional Information
EALP
mesaages logged underfabric
log on switch end as shown below:
Switch 0; Tue Dec 5 21:38:17 2023 IST (GMT+5:30)
21:38:17.258931 SCN T_PORT g=0x36 A2,P3 A2,I4 288 NA
21:38:17.259728 Node Add:nd=0x19ed5e28,iu=0x19ed7830 A2,P3 A2,P3 288 0xa1
21:38:17.259729 AsyncCmd:nd=0x19ed5e28,iu=0x19ed7830 A2,P3 A2,P3 288 0xa1
21:38:17.259731 EALP Send:sz=3648,len=2560,vc=64 A2,P3 A2,P3 288 0xa1
21:38:17.259745 SCN T_PORT g=0x38 A2,I4 A2,I4 289 NA
21:38:17.259745 EALP exchange skipped:f=2 A2,I4 A2,I4 289 NA
21:38:17.259765 SCN T_PORT g=0x3a A2,P3 A2,I4 430 NA
21:38:17.260383 Node Add:nd=0x19dfff50,iu=0x19ed8708 A2,P3 A2,P3 430 0x9f
21:38:17.260384 AsyncCmd:nd=0x19dfff50,iu=0x19ed8708 A2,P3 A2,P3 430 0x9f
21:38:17.260385 EALP Send:sz=3648,len=2560,vc=64 A2,P3 A2,P3 430 0x9f
21:38:17.260399 SCN T_PORT g=0x3c A2,I4 A2,I4 431 NA
21:38:17.260399 EALP exchange skipped:f=2 A2,I4 A2,I4 431 NA
21:38:17.273176 EALP ACC Rcv:flow=4,flen=2560,size=3648 A2,P3 A2,P3 288 0xa1
21:38:17.283655 Node Free:nd=0x19ed5e28,iu=0x19ed7830 A2,P3 A2,P3 288 0xa1
21:38:17.285601 EALP ACC Rcv:flow=4,flen=2560,size=3648 A2,P3 A2,P3 430 0x9f
21:38:17.304160 Node Free:nd=0x19dfff50,iu=0x19ed8708 A2,P3 A2,P3 430 0x9f
21:38:17.315757 SCN T_PORT g=0x36 A2,P3 A2,I4 288 NA
21:38:17.324069 Node Add:nd=0x19dfff50,iu=0x19ed7830 A2,P3 A2,P3 288 0xa0
21:38:17.324070 AsyncCmd:nd=0x19dfff50,iu=0x19ed7830 A2,P3 A2,P3 288 0xa0
21:38:17.324072 EALP Send:sz=3648,len=2560,vc=64 A2,P3 A2,P3 288 0xa0
- The Traffic Optimizer feature tries to optimise the SAN traffic.
- From Fabric OS 9.1.0 and above, the Traffic Optimizer feature is enhanced to provide the following advanced features to efficiently optimize SAN traffic:
1. Protocol-based (SCSI/NVMe) traffic flow classification
2. Oversubscribed device isolation (OS)