Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Brocade Loopback and E-port notes #52

Open
bluecmd opened this issue Sep 10, 2020 · 0 comments
Open

Brocade Loopback and E-port notes #52

bluecmd opened this issue Sep 10, 2020 · 0 comments
Labels
documentation Improvements or additions to documentation fc Affects the Fibre Channel part question Further information is requested

Comments

@bluecmd
Copy link
Owner

bluecmd commented Sep 10, 2020

This is a bug/feature-request/documentation issues for documenting what is know about Brocade Loopback and E-port behaviour.

Quest

This is a side-quest for acquiring more knowledge. No feature currently depends on this. It would be cool to understand how this is implemented by Brocade to deepen the understanding of real-world FC equipment.

Status

Observed behavior is that the port links up to AC state just fine, but is then sent a Link Reset (LR) at which point the idle-word seems to switch to ARB(AL_PA) with AL_PA=0xEF.

What needs to be done?

  • Map the 8b/10b traffic that is sent between two different Brocade switches (E-ports)
# TODO: No port status dump for this
  • Map the 8b/10b traffic that is sent between a loopback on a Brocade switch. (Loopback)
Index Port Address Media Speed       State   Proto
==================================================
  27  27   010000   id    8G	   Online      FC  Loopback->Port 31 
  31  31   010100   id    8G	   Online      FC  Loopback->Port 27
  • Map the 8b/10b traffic that is sent between two virtual switches on a single Brocade switch. (
  27  27   010000   id    8G	   Online      FC  E-Port  segmented,10:00:00:05:1e:eb:e1:80 (ESC mismatch, Fabric ID)(Trunk master)  

Extra questions

  • What is this ESC missmatch Fabirc Id message about? Is it because we are linking up the same switch to itself? Try with another switch to figure out maybe.
@bluecmd bluecmd added documentation Improvements or additions to documentation question Further information is requested labels Sep 10, 2020
@bluecmd bluecmd added the fc Affects the Fibre Channel part label Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation fc Affects the Fibre Channel part question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant