Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation

Solutions

Featured solutions AI Campus and branch Data center WAN Security Service provider Cloud operator Industries
Campus and Branch

Welcome to the NOW Way to Wi-Fi

Take your networking performance to new heights with a modern, cloud-native, AI-Native architecture. Only Juniper can help you unleash the full potential of Wi-Fi 7 with our AI-Native platform for innovation.
Prepare for liftoff
Business intelligence analyst dashboard on virtual screen. Big data Graphs Charts.

AI Data Center Networking

Juniper’s AI data center solution is a quick way to deploy high performing AI training and inference networks that are the most flexible to design and easiest to manage with limited IT resources.
Find out more
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Zero trust security

Ops4AI Lab

Visit our lab in Sunnyvale, CA and see our AI data center solution for yourself. You can try out your own model’s functionality and performance, too.
Visit the lab
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Higher Education

Shaping Student Experiences: The NOW Way to Build Higher Education Networks

Juniper Networks CIO Sharon Mandell and a virtual summit of C-level IT leaders from prestigious institutions discuss ongoing efforts to support digital transformation on campus.
Watch now
Hand on tablet with healthcare overlay of graphics

Security in healthcare

In this IDC Spotlight report, discover how AI networking can automate and strengthen a healthcare ecosystem to defeat criminals and prevent loss. 
Gain insights into ecosystem security
Retail

The Future of In-Store Technologies

Retail experts Kevin McCartan, Senior IT Service Delivery Engineer at Musgrave; Jack Stratten of Insider Trends; and Christian Gilby, Senior Director of Product Marketing at Juniper Networks, discuss customer experiences.
See the future

Products

Wireless access Wired access SD-WAN / SASE Routing and switching Security Mist AI™ Management software Network operating system Blueprint for AI-Native Acceleration Optics
  • Operations
ACX7020 router

Juniper ACX7020 Cloud Metro Access Router

Legacy networks simply cannot meet the demands of today’s rapidly evolving metro landscape. Unlock a new generation of highly scalable architectures and automated operations with the Juniper ACX7020. 
Learn more
EX4000 Ethernet Switch

Next-gen AI-Native EX4000 line of switches

Lack of AI innovation from your current networking vendor slowing you down? Embrace Juniper’s cloud-native, AI-Native access switches that support every level and layer, across nearly every deployment.
Discover how
The Q and AI text with an image of Bob Friday and Kedar Dhuru.

The Q&AI Podcast

Delivering practical solutions and enriching discussions, this podcast series is a vital resource for those seeking an in-depth exploration of AI's transformative potential.
Catch the latest episode

Services

Services
Services AI Care

Juniper AI Care Services Revolutionize Your Service Experience

Our industry-first AI-Native services couple AIOps with our deep expertise across the full network life cycle. You can move from reactive response to proactive insight and action.
Explore AI Care Services
Services AI Data Center

Juniper AI Data Center Deployment Services Optimize Your AI Model Runs

We use our expertise and validated designs to help design, deploy, validate and tune networks, including GPUs and storage, to get the most from your AI infrastructure operation.
Learn about AI Data Center Deployment Services

Partners

Partners

Support and Documentation

Support and Documentation

Learn

About Juniper Training Events The Feed Resources Technology learning topics Thought leadership and insights
Audience raising hands up while businessman is speaking in training at the office.

Juniper certification and training news

See the latest
Ringing of the bell

All global events

See the latest
AI-native-now

AI-Native NOW event series

Explore events
AINN AI Innovation Impact Virtual Event

AI-Native NOW: AI Innovation and Impact

Register NOW
Juniper's Christina Hendrix at the head of a conference table. With the text "The NOW Way to Network" overlayed, with "NOW" emphasizing the "O" in green color.

The NOW Way to Network

Watch the video series
AI Native Now

Executive insights

Dive deep with leading experts and thought leaders on all the topics that matter most to your business, from AI to network security to driving rapid, relevant transformation for your business.
Learn more
A keynote speaker giving a presentation at a conference. There are dozens of people sitting around them. The presentation is displayed via projector on all the walls in the room.

Leadership voices

Juniper Networks’ leaders operate on the front lines of creating the network of the future. Take a look around to see what’s on their minds.
Watch now
Bob Friday and Jessica Garrison speaking

Bob Friday Talks

Join Bob as he ventures into all the knowns -- and -- unknowns -- of AI.
Catch the latest episode
Documentation
Menu
License Guide
Quick Starts
Validated Designs
Home Documentation Junos OS Storage User Guide Fibre Channel and FCoE-FC Gateways Using Fibre Channel and FCoE-FC Gateways

Storage User Guide

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
ON THIS PAGE
keyboard_arrow_right

Monitoring Fibre Channel Interface Load Balancing

date_range 23-Nov-23
arrow_backward
arrow_forward

You can use operational mode commands to monitor load balancing when the switch is in FCoE-FC gateway mode:

Monitoring the Interface Load-Balancing State

Purpose

Monitor the number of sessions, whether load balancing is enabled or disabled, and the load-balancing weight for each native Fibre Channel (FC) interface.

Note:

A session is a FLOGI or FDISC login to the FC SAN fabric. Session does not refer to end-to-end storage sessions.

Action

To monitor the load-balancing state of the native FC interfaces in the CLI, enter the following CLI command:

user@switch> show fibre-channel proxy np-port

For example:

content_copy zoom_out_map
user@switch> show fibre-channel proxy np-port
Fabric: sanfab1, Fabric-id: 10
NP-Port     State              Sessions       LB state   LB weight
fc-0/0/0.0  online             5              ON         4
fc-0/0/1.0  online             5              ON         4
fc-0/0/2.0  online             10             ON         8

Fabric: fc_fab2, Fabric-id: 200
NP-Port     State              Sessions       LB state   LB weight
fc-0/0/44.0 isolated           0              OFF        0         

Fabric: fc_fabric_100, Fabric-id: 100
NP-Port     State              Sessions       LB state   LB weight
fc-0/0/46.0 online             1              ON         8

Meaning

Table 1 summarizes key output fields for the FC interface load-balancing state.

Table 1: Summary of Key FC Interface Load-Balancing Output Fields

Field

Values

Fabric

Name of the fabric.

Fabric-id

Fabric ID number.

NP-Port

NP_Port interface connected to the FCoE forwarder (FCF) or the FC switch.

State

FCID state of the NP_Port interface:

  • online—The port is online and connected to the FC switch. FCoE devices can log in to the FC switch using this port.

  • isolated—The port is isolated and is not part of the load-balancing function. FCoE devices cannot log in to the FC switch using this port.

  • offline—The port is offline.

Sessions

Number of active sessions on the NP_Port interface.

LB state

Load-balancing state:

  • On—Load balancing is on

  • Off—Load balancing is off.

LB weight

Load-balancing weight, which reflects the port speed:

  • 2—Port speed is 2 Gbps.

  • 4—Port speed is 4 Gbps.

  • 8—Port speed is 8 Gbps.

The gateway determines the least-loaded interface using the following weighted round-robin (WRR) algorithm:

(number-of-sessions * max-weight) / weight

where max-weight is an internal constant. If the load on the FC interfaces is equal, the session is assigned to the interface with the highest link speed (the greatest weight).

Monitoring the Fabric Load-Balancing Algorithm

Purpose

Monitor the type of load-balancing algorithm (simple, ENode-based, or FLOGI-based) used on the native FC interfaces, whether or not automated load rebalancing is enabled, and the load rebalancing state of the fabric.

Action

To monitor the load-balancing algorithm used on the native FC interfaces and the load rebalancing state in the CLI, enter the following CLI command:

user@switch> show fibre-channel proxy fabric-state

For example:

content_copy zoom_out_map
user@switch> show fibre-channel proxy fabric-state
Fabric: sanfab1, Fabric-id: 10
Proxy load balance algorithm: Simple, Fabric WWN verification: Yes
Auto load rebalance enabled  : No
Last rebalance start-time    : Never
Last rebalance end-time      : Never
Last rebalance trigger       : Link-up
Last rebalance trigger-time  : Mon Sep 10 21:42:30 2012 usec: 814602
Last rebalance trigger-result: Not-configured

Fabric: fc_fab2, Fabric-id: 200
Proxy load balance algorithm: ENode based, Fabric WWN verification: Yes
Auto load rebalance enabled  : No
Last rebalance start-time    : Never
Last rebalance end-time      : Never
Last rebalance trigger       : Link-up
Last rebalance trigger-time  : Mon Sep 17 17:23:35 2012 usec: 619684
Last rebalance trigger-result: Not-configured

Fabric: fc_fabric_100, Fabric-id: 100
Proxy load balance algorithm: FLOGI based, Fabric WWN verification: No
Auto load rebalance enabled  : Yes
Last rebalance start-time    : Never
Last rebalance end-time      : Never
Last rebalance trigger       : Config-CLI
Last rebalance trigger-time  : Fri Nov  2 08:56:16 2012 usec: 004487
Last rebalance trigger-result: Not-required

Meaning

You can configure each local FC fabric on an FCoE-FC gateway to use one of three types of load-balancing algorithms, simple, ENode-based, or FLOGI-based. All of the native FC interfaces (NP_Ports) in a particular gateway FC fabric use the same load-balancing algorithm (the load-balancing algorithm is applied on a per-fabric basis).

Table 2 summarizes key output fields for the FC interface load-balancing algorithm and state.

Table 2: show fibre-channel proxy fabric-state Output Fields

Field Name

Field Description

Fabric

Name of the fabric.

Fabric-id

Fabric ID number.

Proxy load balance algorithm

Load-balancing algorithm used on the FCoE-FC gateway FC fabric:

  • Simple—Load balancing is based on the weighted utilization (load) of the NP_Ports connected to an FC fabric. Each new FLOGI or FDISC is assigned to the least-loaded link.

    On a link load rebalance, only the sessions that need to be moved to another link are logged out. When those sessions log in again, they are placed on active NP_Port interfaces in a balanced manner.

  • ENode-based—Load balancing is based on the ENode FLOGI. When an ENode logs in to the fabric, all subsequent FDISC sessions (VN_Port sessions) associated with that ENode are placed on the same link as the ENode FLOGI session, regardless of the link load. New ENode FLOGIs are placed on the least-loaded link.

    On a link load rebalance, all sessions are logged out. When the sessions log in again, they are placed on active NP_Port interfaces in a balanced manner.

  • FLOGI-based—Load balancing is based on the ENode FLOGI. When an ENode logs in to the fabric, all subsequent FDISC sessions (VN_Port sessions) associated with that ENode are placed on the same link as the ENode FLOGI session, regardless of the link load. New ENode FLOGIs are placed on the least-loaded link.

    On a link load rebalance, only the sessions that need to be moved to another link are logged out. When those sessions log in again, they are placed on active NP_Port interfaces in a balanced manner.

Fabric WWN verification

Fabric worldwide name (WWN) verification check state on the FCoE-FC gateway fabric:

  • Yes—Fabric WWN verification check is enabled.

  • No—Fabric WWN verification check is disabled.

Auto load rebalance enabled

Automated link load rebalancing configuration for the FCoE-FC gateway fabric:

  • No—Automated load balancing is disabled (default state).

  • Yes—Automated load balancing is enabled.

Last rebalance start-time

Time that the last link load rebalance began on the FCoE-FC gateway fabric:

  • Never—The link load has never been rebalanced.

  • Timestamp value—Time the last link load rebalancing started.

Last rebalance end-time

Time that the last link load rebalance ended on the FCoE-FC gateway fabric:

  • Never—The link load has never been rebalanced.

  • Timestamp value—Time the last link load rebalancing ended.

Last rebalance trigger

Event that triggered the last link load rebalance on the FCoE-FC gateway fabric:

  • None—The link load has never been rebalanced.

  • Config-CLI—Configure (enable) automated load balancing.

  • Request-CLI—Rebalance requested from the CLI using the request fibre-channel proxy load-rebalance fabric fabric-name operational command.

  • Preview-CLI—Rebalancing dry run requested from the CLI using the request fibre-channel proxy load-rebalance dry-run fabric fabric-name operational command. Indicates that the switch completed the dry run. A dry run simulates a link load rebalance and displays a list of sessions that might be affected if you request an actual rebalance.

  • Link-up—New FC link (NP_Port) up on the FCoE-FC gateway fabric, which causes a rebalance to distribute sessions to the new link.

  • Restore-complete—If the FC process on the switch restarts, the switch attempts to restore the session state that existed before the restart. When automated rebalance is enabled, restore-complete indicates that the sessions have been restored and rebalanced.

Last rebalance trigger-time

Time that the last link load rebalance was triggered on the FCoE-FC gateway fabric:

  • Never—Link load rebalancing has never been triggered.

  • Timestamp value—Time the last link load rebalancing was triggered.

Last rebalance trigger-result

Result of the last trigger event on the FCoE-FC gateway fabric:

  • Never—Link load rebalancing has never been triggered.

  • Not-configured—Automated rebalancing is not configured on the FCoE-FC gateway fabric.

  • Not-required—Last rebalance trigger did not require rebalancing the link load (the link load was already balanced across the active NP_Port links).

  • In-progress—Link load rebalancing is in progress and has not finished yet.

  • Restore-in-progress—The switch is recovering from an FC process restart and is in the process of restoring the sessions to the active NP_Port links.

  • Success—Link load rebalancing was successful.

  • Logged-out-all—All sessions have been logged out.

  • Preview-complete—The switch has finished simulating a dry run rebalancing request from the CLI (request fibre-channel proxy load-rebalance dry-run fabric fabric-name operational command) and reported the sessions that might be affected if you request an actual link load rebalance.

  • Fabric-deletion-in-progress—FCoE-FC gateway fabric is in the process of being deleted.

Note:

A trigger event does not necessarily result in a rebalance action. Link load rebalancing only occurs if the NP_Port interface session load is not balanced at the time of the trigger event.

Related Documentation

arrow_backward PREVIOUS Setting the Maximum Number of FIP Login Sessions per Node Device
NEXT arrow_forward Troubleshooting Dropped FIP Traffic
footer-navigation

© 1999 - 2025 Juniper Networks, Inc. All rights reserved.

Scroll to top