Symptom

Need meaningful syslog messages when FLOGIs fail.

Conditions

All.

Workaround

None.

Further Problem Description

Resolution Summary

The following new syslog messages are added to cover all the cases when a FLOGI fails: Notice that logging level flogi 5 is needed for informational messages to be displayed in the syslog (show logging log) The following is an example of an implicit logout for a PWWN already logged in on a different(or same in the case of an NPV connection) interface of the same switch, same VSAN: Notice there will be a FLOGI reject of the new FLOGI while the PWWN is implicitly logged out. The device should send another FLOGI and once the PWWN has been logged out of the previous interface, the new FLOGI will be accepted. %FLOGI-5-MSG_FLOGI_IMPLICIT_DEVICE_LOGOUT: %$VSAN 1%$ [VSAN 1, Interface port-channel1: mode[F]] FLOGI/FDSIC (pwwn: 40:00:00:00:00:0a:00:01) has been logged out because it tried to login on a different interface fc2/3 %FLOGI-5-MSG_FLOGI_DUPLICATE_PWWN_ON_DIFFERENT_INTERFACE: %$VSAN 1%$ [VSAN 1, Interface fc2/3: mode[F]] FLOGI (pwwn: 40:00:00:00:00:0a:00:01) has been rejected because it is already logged in on interface port-channel1 %FLOGI-5-MSG_PORT_LOGGED_IN: %$VSAN 1%$ [VSAN 1, Interface fc2/3: mode[F]] Nx Port 40:00:00:00:00:0a:00:01 with FCID 0xef0280 logged IN. Example of a FLOGI Reject due to timeout of the Routing Information Base (RIB) component. %FLOGI-5-MSG_FLOGI_REJECTED_DUE_TO_PROCESS_TIMEOUT: %$VSAN 1%$ [VSAN 1, Interface fc2/3: mode[F]] FLOGI (pwwn: 40:00:00:00:00:0a:00:01) has been rejected because RIB failed to respond to the request on time Example of a FLOGI Reject due to the pwwn is already logged in on a different switch in the VSAN. %FLOGI-5-MSG_FLOGI_REJECTED_DUPLICATE_PWWN_IN_FABRIC: %$VSAN 1%$ [VSAN 1, Interface fc2/3: mode[F]] FLOGI (pwwn: 40:00:00:00:00:0e:00:17) has been rejected because name server detected duplciate PWWN in the fabric