ONTAP Discussions

LIF are administravely up but operationally down

chinchillaking
2,432 Views

Hello,

 

Just for reference. when setup new FAS and new NetApp (Brocade) SAN switch, the SVM LIF administravely up but operationally down and OnTap event display below messages.

 

fct_tpd_work_thread_0: scsitarget.ispfct.configChanged:notice]: FCP target 0f reported a port configuration change. FDISC RJT - FDISC failed because a LS_RJT was received for virtual port

 

When initial troubleshoot, refer below KB and we suspect SAN switch firmware problem even did not mention Brocade SAN switch, afte upgrade SAN switch to latest suppor tversion still cannot fix.

 

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/Logical_Interfaces_(LIF)_up_down_after_ONTAP_node_Reboot

 

After review Brocade SAN switch errdump display warning "2021/05/18-11:15:04, [SWCH-1046], 67, FID 128, WARNING, Brocade_G610_A, Configured NPIV Login Limit of 0 exceeded on port index 1", check portcfgshow display all port "NPIV PP Limit 0".

 

We don't know why both new SAN switch setting with "NPIV PP Limit 0", after reset port to default "NPIV PP Limit 126",  problem fixed.

 

1 ACCEPTED SOLUTION

chinchillaking
2,388 Views

Hello,

 

No assistance and I mark the "Accept the Solution" already. Just want to post this issue and let every body aware.

View solution in original post

8 REPLIES 8

Reverett
2,418 Views

Have you seen the issue return since you have made the corrective changes?

 

Were there any changes made prior to the port configuration change was reported/noticed?

chinchillaking
2,415 Views

Hello,

 

Just for reference, even same error messages display in OnTap event and the KB, please review all devices error mesages first, do not trust the new device come with default setting. 

Reverett
2,404 Views

Hi @chinchillaking,

 

Could you explain what you meant by "please review all devices error mesages first, do not trust the new device come with default setting. "?

 

Also,

Have you seen the issue return since you have made the corrective changes?

 

Were there any changes made prior to the port configuration change was reported/noticed?

 

 

chinchillaking
2,400 Views

Hello,

 

 

Could you explain what you meant by "please review all devices error mesages first, do not trust the new device come with default setting. "?

 

We are missing review the SAN switch event and error messages when initial troubleshoot. Because it was new SAN switch and we assume the setting come with default.

 

Also,

Have you seen the issue return since you have made the corrective changes?

 

Issue did not return after change the SAN switch port config to default.

 

Were there any changes made prior to the port configuration change was reported/noticed?

 

Two SAN switch are fresh, but the port setting with NVIP PP limit is 0, this setting will not allow LIF login to SAN switc because the limit is 0. Check with Fabric OS port NPIV default setting should not 0.

 

 

Reverett
2,391 Views

Hello,

 

If the issue has not returned is there further assistance you are needing regarding this topic?

chinchillaking
2,389 Views

Hello,

 

No assistance and I mark the "Accept the Solution" already. Just want to post this issue and let every body aware.

ttran
2,376 Views

Hello @chinchillaking,

 

Thank you for sharing your experience, it will be very helpful to the Community that we should check all settings as the default might not be the desired setting. I can confirm that the NPIV capability does need to be enabled and NPIV PP Limit configured to 126 per port on fabric switches. It is odd that the NPIV PP Limit was set to 0 as by default from Brocade it should be 126 and NPIV capability "disabled", so users only have to enable/disable the feature.

 

This KB can also be used as a reference FCP/FCoE LIF reports operationally down.

 

Thank you again for sharing!

 

 

Regards,

 

Team NetApp

Team NetApp

chinchillaking
2,373 Views

Hello,

 

At initial troubleshoot, we check all port NPIV Enabled but missing review the PP Limit. After review errdump and display warning relative NPIV PP limit, change the limit and the problem fixed.

Public