02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

BFD sessions<br />

BFD must be enabled on both sides of a link in order to establish a session. The two participating systems<br />

can assume ei<strong>the</strong>r of two roles:<br />

• Active—The active system initiates <strong>the</strong> BFD session. Both systems can be active <strong>for</strong> <strong>the</strong> same session.<br />

• Passive—The passive system does not initiate a session. It only responds to a request <strong>for</strong> session<br />

initialization from <strong>the</strong> active system.<br />

A BFD session has two modes:<br />

• Asynchronous mode—In Asynchronous mode, both systems send periodic control messages at an<br />

agreed upon interval to indicate that <strong>the</strong>ir session status is Up.<br />

• Demand mode—If one system requests Demand mode, <strong>the</strong> o<strong>the</strong>r system stops sending periodic<br />

control packets; it only sends a response to status inquiries from <strong>the</strong> Demand mode initator. Ei<strong>the</strong>r<br />

system (but not both) can request Demand mode at any time.<br />

Note: <strong>FTOS</strong> supports currently supports asychronous mode only.<br />

A session can have four states: Adminstratively Down, Down, Init, and Up.<br />

• Administratively Down—The local system will not participate in a particular session.<br />

• Down—The remote system is not sending any control packets or at least not within <strong>the</strong> detection time<br />

<strong>for</strong> a particular session.<br />

• Init—The local system is communicating.<br />

• Up—The both systems are exchanging control packets.<br />

The session is declared down if:<br />

• A control packet is not received within <strong>the</strong> detection time.<br />

• Sufficient echo packets are lost.<br />

• Demand mode is active and a control packet is not received in response to a poll packet.<br />

BFD three-way handshake<br />

A three-way handshake must take place between <strong>the</strong> systems that will participate in <strong>the</strong> BFD session. The<br />

handshake shown in Figure 420 assumes that <strong>the</strong>re is one active and one passive system, and that this is <strong>the</strong><br />

first session established on this link. The default session state on both ports is Down.<br />

1. The active system sends a steady stream of control packets that indicates that its session state is Down,<br />

until <strong>the</strong> passive system responds. These packets are sent at <strong>the</strong> desired transmit interval of <strong>the</strong> Active<br />

system, and <strong>the</strong> Your Discriminator field is set to zero.<br />

2. When <strong>the</strong> passive system receives any of <strong>the</strong>se control packets, it changes its session state to Init, and<br />

sends a response that indicates its state change. The response includes its session ID in <strong>the</strong> My<br />

Discriminator field, and <strong>the</strong> session ID of <strong>the</strong> remote system in <strong>the</strong> Your Discriminator field.<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 601

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!