Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Storage User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Setting the Maximum Number of FIP Login Sessions per ENode

date_range 23-Nov-23

When the switch acts as an FCoE-FC gateway, FCoE node (ENode) devices in the Ethernet network use the gateway to connect to the Fibre Channel (FC) storage area network (SAN). You can limit the maximum number of FIP login sessions permitted on each ENode. Limiting the number of login sessions can prevent login session rejections caused when the connected FC switch port configuration limits the number of FIP login sessions.

The maximum number of FIP sessions per ENode is 2000 sessions (FLOGI plus FDISC sessions). The limit you set applies to every ENode in the specified gateway fabric. Each ENode in the fabric can have up to the maximum number of sessions, but the total number of active sessions cannot exceed the session limits you apply to the fabric or the Node device.

There are also configurable FIP login session limits that you can apply to the gateway FC fabric, to the QFX3500 switch or QFabric system Node device, and to the interfaces in each FC fabric.

  • To set a maximum number of FIP login sessions per ENode using the CLI:

    content_copy zoom_out_map
    [edit fc-fabrics fc-fabric-name protocols fip]
    user@switch# set max-sessions-per-enode max-login-sessions

    For example, to configure the ENodes on an FC fabric named sanfab1 with a maximum FIP login session limit of 250 sessions:

    content_copy zoom_out_map
    [edit fc-fabrics sanfab1]
    user@switch# set protocols fip max-sessions-per-enode 250 
footer-navigation