Dell Brocade G620 Brocade 8.0.1 Fabric OS Administratiors Guide - Page 419
General limitations and considerations for D_Port tests
![]() |
View all Dell Brocade G620 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 419 highlights
Diagnostic Port TABLE 82 D_Port configuration mode and nature of test D_Port mode/nature of test Description Mode Static You must configure the port explicitly. Port remains a D_Port until you remove the configuration. Dynamic No user configuration is required. D_Port mode is initiated by external request/event from the remote port. The remote port can either be a static or on-demand D_Port. On-demand No user configuration is required. D_Port mode is initiated by internal request within the local switch. The remote port should be a dynamic D_Port. Nature of test Automatic Test automatically starts when the port comes online. Manual User starts test from the switch or Access Gateway side (using the portdporttest command with either the -start or --restart keyword), or from the HBA side (refer to "BCU D_Port commands" in this guide) for Brocade HBAs. When the tests complete, the port behavior depends on the mode: ∙ For static D_Ports, you must remove the D_Port configuration at either or both ends of the link to bring up the port as a regular E_Port or F_Port. ∙ For a switch port in dynamic D_Port mode, the port automatically reverts back to an E_Port or an F_Port if the port at the other end reverts to a regular port. ∙ For a switch in on-demand D_Port mode, the port automatically reverts back to an E_Port after the tests are completed successfully. ∙ Beginning with Fabric OS 8.0.1, the following test options are available for electrical and optical loopback tests: -framesize, nframes, -pattern, -payload, -time. Both ends must be running the same release (Fabric OS 8.0.1 or later) or the test reverts to legacy behavior. ∙ To support 32-Gbps testing, Forward Error Correction (FEC) is enabled by default. General limitations and considerations for D_Port tests Consider the following issues when running D_Port tests: ∙ The link to be tested must be marginally functional and able to carry a minimal number of frames before it can become a D_Port link. ∙ D_Port testing is useful for diagnosing marginal faults only. A complete failure of any component cannot be detected. ∙ D_Port configuration is not supported on mezzanine cards. ∙ D_Ports do not support a loop topology. ∙ D_Port testing is not supported on adapter ports configured in CNA mode. ∙ Toggling the port on either side of the link restarts the test. ∙ On ICL ports and FC16-64 blade ports that are configured as D_Ports, only link traffic tests can be run. Electrical loopback and optical loopback tests are not supported. A connection between a QSFP port of an FC16-64 and a core blade is not a valid connection. ∙ When a large number of D_Ports are configured, the test is run on one port per blade at a time, and other ports wait until the test is completed. No test begins until the fabric is stable. ∙ Before running On-demand D_Port tests on the links having Dense Wavelength Division Multiplexing (DWDM) or Course Wavelength Division Multiplexing (CWDM), you must provision the port by using the portcfgdport command with -dwdm option. Optical loopback tests are skipped for D_Ports with DWDM. ∙ The D_Port DWDM provisioning is applicable to static D_Ports, On-demand D_Ports, and Dynamic D_Ports. During the configuration of the Static D_Port using portcfgdport --enable, DWDM is automatically configured if the port was previously provisioned for DWDM. Brocade Fabric OS Administration Guide, 8.0.1 53-1004111-02 419
![](/manual_guide/products/dell-brocade-g620-brocade-801-fabric-os-administratiors-guide-fdaf46d/419.png)