12.07.2015 Views

Cisco IOS Wide-Area Networking Configuration Guide - Free Books

Cisco IOS Wide-Area Networking Configuration Guide - Free Books

Cisco IOS Wide-Area Networking Configuration Guide - Free Books

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.

Customizing Frame Relay for Your NetworkConfiguring Frame RelayThe send side sends out a keepalive request and waits for a reply to its request. If a reply is receivedbefore the timer expires, a send-side Frame Relay end-to-end keepalive is recorded. If no reply isreceived before the timer expires, an error event is recorded. A number of the most recently recordedevents are examined. If enough error events are accumulated, the keepalive status of the VC is changedfrom up to down, or if enough consecutive successful replies are received, the keepalive status of the VCis changed from down to up. The number of events that will be examined is called the event window.The receive side is similar to the send side. The receive side waits for requests and sends out replies tothose requests. If a request is received before the timer expires, a success event is recorded. If a requestis not received, an error event is recorded. If enough error events occur in the event window, the PVCstate will be changed from up to down. If enough consecutive success events occur, the state will bechanged from down to up.End-to-end keepalives can be configured in one of four modes: bidirectional, request, reply, orpassive-reply.• In bidirectional mode, both the send side and the receive side are enabled. The send side of thedevice sends out and waits for replies to keepalive requests from the receive side of the other PVCdevice. The receive side of the device waits for and replies to keepalive requests from the send sideof the other PVC device.• In request mode, only the send side is enabled, and the device sends out and waits for replies to itskeepalive requests.• In reply mode, only the receive side is enabled, and the device waits for and replies to keepaliverequests.• In passive-reply mode, the device only responds to keepalive requests, but does not set any timersor keep track of any events.Because end-to-end keepalives allow traffic flow in both directions, they can be used to carry control andconfiguration information from end to end. Consistency of information between end hosts is critical inapplications such as those relating to prioritized traffic and Voice over Frame Relay. Whereas SVCs canconvey such information within end-to-end signalling messages, PVCs will benefit from a bidirectionalcommunication mechanism.End-to-end keepalives are derived from the Frame Relay LMI protocol and work between peer <strong>Cisco</strong>communications devices. The key difference is that rather than running over the signalling channel, asis the case with LMI, end-to-end keepalives run over individual data channels.Encapsulation of keepalive packets is proprietary; therefore, the feature is available only on <strong>Cisco</strong>devices running a software release that supports the Frame Relay End-to-End Keepalive feature.You must configure both ends of a VC to send keepalives. If one end is configured as bidirectional, theother end must also be configured as bidirectional. If one end is configured as request, the other end mustbe configured as reply or passive-reply. If one end is configured as reply or passive-reply, the other endmust be configured as requestTo configure Frame Relay end-to-end keepalives, use the following commands beginning in globalconfiguration mode:CommandPurposeStep 1 Router(config)# map-class frame-relay map-class-name Specifies a map class for the VC.Step 2Router(config-map-class)# frame-relay end-to-end keepalivemode {bidirectional | request | reply | passive-reply}Specifies Frame Relay end-to-endkeepalive mode.The four modes determine the type of keepalive traffic each device sends and responds to:28

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

Saved successfully!

Ooh no, something went wrong!