Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

show fibre-channel proxy fabric-state

 

Syntax

Release Information

Command introduced in Junos OS Release 12.1.

Description

Display Fibre Channel (FC) proxy fabric state information.

Options

fabric fabric-name(Optional) Display output only for the specified fabric.

Required Privilege Level

view

List of Sample Output

show fibre-channel proxy fabric-state

show fibre-channel proxy fabric-state fabric

Output Fields

Table 1 lists the output fields for the show fibre-channel proxy fabric-state command. Output fields are listed in the approximate order in which they appear.

Table 1: 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 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 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.

Sample Output

show fibre-channel proxy fabric-state

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

show fibre-channel proxy fabric-state fabric

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