|  |         It's in the BL2.2 release notes as "delayed datalink enable", and
    the reasons for it are discussed elsewhere in this notes conference,
    most likely under the failover-configurations or dual-homing-failover
    keywords.
    
        The basic idea is that it allows a customer to control when the
    "failback" of an M port occurs.
    
        With normal dual homing, the B->A failover occurs fairly quickly,
    but after the B path is restored, the A->B transition may encounter a
    long outage.  By using this feature on the M port connected to the B
    port, the network manager can prevent the A "failback" from happening
    automatically.
    
        The "bad" scenario happens when the linecard connected to the B
    port reboots.  The FDDI port is ready before the bridge port is ready,
    so failback happens, but no traffic can take place until the bridge
    port initialization completes.
    
    MDL
 |