No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-Why the Queried BB_SCN Is Zero on the LOM Board

Publication Date:  2012-07-25 Views:  35 Downloads:  0
Issue Description
Q:
Why the queried BB_SCN is zero on the LOM board? 
 
Alarm Information
Null 
Handling Process
A:
The LOM board does not support the BB Recovery function, and thus changes the BB_SCN of the received frames to 0. Otherwise, the equipment connected to the LOM may consider that the LOM supports this function and the BB Recovery function fails.
The BB_CREDIT_CNT is not cleared to 0 during multiple logins. As described in FC-LS, if one login is identical with the former one, the LOM board preserves the information formerly established; if the login is different from the former one, the login is certainly accompanied by an implicit LOGOUT (NOS or OLS).
“6.2.2.5 Relogin with the Fabric During a Login with the Fabric, if the Nx_Port was previously logged in with the Fabric and the N_Port_ID, F_Port_Name, and the Fabric_Name are the same as the previous login, the Nx_Port may continue current communications with other Nx_Ports that it has established logins with; if the Nx_Port detects that the N_Port_ID, F_Port_Name, and/or the fabric_Name has changed since the last Fabric Login, the Nx_Port shall implicitly logout with all Nx_Ports and wait an R_A_TOV timeout period before initiating or accepting communication with other Nx_Ports. The timeout period shall start when the Nx_Port detects the change. After waiting the timeout period, new N_Port Logins are required before the Nx_Port may communicate with other Nx_Ports.”
The LOM board does not support BB Recovery. Therefore, leave the current processing unchanged. 
 
Root Cause
  
Suggestions
Null 

END