CTR 8500-8300 3.0 BFD Config July2015 260-668256-010

CTR 8300/8500 CONFIGURATION
BFD
Version 3.0
260-668256-010
Copyright & Terms of Use
July 2015
This documentation incorporates features and functions provided with CTR 8540 and CTR 8300 for software
release 3.0
Copyright © 2015 by Aviat Networks, Inc.
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a
retrieval system, or translated into any language or computer language, in any form or by any means, elec-
tronic, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Aviat Net-
works Inc. To request permission, contact techpubs@aviatnet.com.
Warranty
Aviat Networks makes no representation or warranties with respect to the contents hereof and specifically dis-
claims any implied warranties or merchantability or fitness for any particular purpose. Further, Aviat Net-
works reserves the right to revise this publication and to make changes from time to time in the content
hereof without obligation of Aviat Networks to notify any person of such revision or changes.
Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons and/or damage to the
equipment:
1. Installation and Service Personnel: Installation and service must be carried out by authorized personnel who
have the technical training and experience necessary to be aware of any hazardous operations during install-
ation and service, and of measures to avoid any danger to themselves, to any other personnel, and to the equip-
ment.
2. Access to the Equipment: Access to the equipment in use must be restricted to service personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety sections of this guide.
Local safety regulations must be used if mandatory. Safety instructions in this guide should be used in addi-
tion to the local safety regulations. In the case of conflict between safety instructions stated in this guide and
those indicated in local regulations, mandatory local norms will prevail. Should local regulations not be man-
datory, then the safety norms in this guide will prevail.
4. Service Personnel Skill: Service personnel must have received adequate technical training on tele-
communications and in particular on the equipment this guide refers to.
Trademarks
All trademarks are the property of their respective owners.
End User License Agreement and Open Source
By using this product you agree to the terms of the CTR 8540 End User License Agreement; to view this, log
into a CTR 8540 or CTR 8300 using the CLI command window and enter the CLI command “show EULA”.
The CTR 8540 and CTR 8300 use free and open source software components, which can be viewed by using
the CLI command “show system acknowledgments”. This command also details the licenses associated with
each component and describes the methods available to acquire the open source software.
260-668256-005 JULY 2015 I

LA CONFIGURATION CTR 8300 AND 8500
Aviat Networks Technical & Sales

Support
Technical Service and Support
For customer service and technical support, contact one of the regional Technical Help Desks listed below, or
for 24/7 (all day, every day of the year) there is the Global Technical Help Desk (GTHD). A call will be answered
by GTHD support staff who will resolve the issue, if possible, or quickly pass the call to the appropriate TAC
engineer for resolution. Contact information is available below or on the Aviat Networks web site.
Global Technical Help Desk
The GTHD number is: +1-210-526-6345, or toll free 1-800-227-8332 within USA
For 24/7 access you will need your Support Assurance PIN. Without a PIN you will still receive support, but the
support process will require an additional screening step. After-hours calls to Paris are routed to the GTHD,
with the existing number left in place during business hours.
Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help Desk
Aviat Networks Aviat Networks Aviat Networks
5200 Great America Parkway 4 Bell Drive Bldg 10, Units A&B
Santa Clara CA 95054 Hamilton International Technology Philexcel Industrial Park
U.S.A. Park M. Roxas Hi-way
Blantyre, Glasgow, Scotland Clark Freeport Zone
G72 0FB Philippines 2023
United Kingdom
Toll Free (Canada/USA): 800 227 Phone: Phone: +63 45 599 5192
8332 Hamilton: +44 (0) 1698 717 230 Fax: +63 45 599 5196
Phone: 210 561 7400 Paris: +33 (0) 1 77 31 00 33
Fax: 210 561 7399 Fax: +44 (0) 1698 717 204
Cus- Cus- CustomerCare.Asia@aviatnet.com
tomerCare.Americas@aviatnet.com tomerCare.EMEA@aviatnet.com
Sales and Sales Support

Contact one of the Aviat Networks headquarters, or find your regional sales office on the Aviat Networks web
site.
Corporate Headquarters, California, USA International Headquarters , Singapore
Aviat Networks, Inc. Aviat Networks(S) Pte. Ltd.
5200 Great America Parkway 17, Changi Business Park Central 1
Santa Clara CA 95054 Honeywell Building, #04-01
U.S.A. Singapore 486073
Phone: + 408 567 7000 Phone: +65 6496 0900
Fax: + 408 567 7001 Fax: + 65 6496 0999
Sales Inquiries: +1-321-674-4252
II AVIAT NETWORKS
Product Compliance Notes

CTR 8540, CTR 8312, and CTR 8311 have been tested for and meet EMC Directive 2004/108/EC. The equipment
was tested using screened cable; if any other type of cable is used, it may violate compliance.
CTR 8540, CTR 8312, and CTR 8311 are Class A products. In a domestic environment these products may
cause radio interference in which case the user may be required to take adequate measures. This equipment
is intended to be used exclusively in telecommunications centers.
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of IRU 6 0 0 i s n ot s u p p or ted .
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of ODU 6 0 0 or ODU 3 0 0 h p on ANSI f r eq u en c y b an d s
i s n ot s u p p or ted .
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of ODU 6 0 0 on th e l i c en s e- f r ee 5 . 8 GHz b an d i s n ot
s u p p or ted .
International Use of 5.8GHz

ODU 600 or IRU 600 with CTR 8540, CTR 8312, or CTR 8311 on the 5.8 GHz license-free band do not employ
DFS, and as such the equipment cannot be deployed within Europe or any country where DFS is a regulatory
requirement for protection of radars.
WEEE Directive
In accordance with the WEEE Directive (2002/96/EC), CTR 8540, CTR 8312, and CTR 8311 are marked with the
following symbol:
This symbol indicates that this equipment should be collected separately for the purposes of recovery and/or
recycling.
For information about collection and recycling of Aviat Networks equipment please contact your local Aviat
Networks sales office. If you purchased your product via a distributor please contact the distributor for inform-
ation regarding collection and recovery/recycling.
More information on the WEEE Directive is available at our website:
http://www.aviatnetworks.com/products/compliance/weee/.
(WEEE is the acronym for Waste Electrical and Electronic Equipment)
RoHS Directive
CTR 8540, CTR 8312, and CTR 8311 meet the requirements of ROHS directive 2011/65/EU.
260-668256-005 JULY 2015 III

Declaration of Conformity, R&TTE Directive, 1999/5/EC

The reference to CTR in this declaration denotes intended use of the CTR 8540, CTR 8312, or CTR 8311, with
one or more of the following Aviat Networks ODUs: ODU 600, ODU 600sp, ODU 300hp.
IV AVIAT NETWORKS
The CTR 8540, CTR 8312, or CTR 8311 with an ODU 600, ODU 600sp, or ODU 300hp radio is classified under the
R&TTE Directive 99/5/EC as a class 2.8 radio (microwave fixed link) product.
Point-to-point radio relay equipment is intended to be used for:
- Interconnecting private and public networks.
- Interconnecting mobile base stations back to the PSTN point of presence (POP).
For details of where the equipment is intended to be used, see the country matrix below.
- AVIAT NETWORKS intends to market this equipment where a cross (X) is shown in the table below.
- The information contained in this table has been gathered from the relevant government authorities and
relates only to European countries participating in the R&TTE directive.
It s h ou l d b e n oted th at a l i c en s e to op er ate th i s eq u i p men t i s l i kel y to b e n ec es s ar y, an d
th e ap p r op r i ate r eg u l ator y ad mi n i s tr ati on s h ou l d b e c on tac ted .
260-668256-005 JULY 2015 V

VI AVIAT NETWORKS
Chapter 1. BFD Introduction
Purpose and Scope

The Aviat Networks BFD software is a portable implementation of the Bidirectional Forwarding
Detection Protocol which provides fast forwarding-path failure detection times for media types,
encapsulations, topologies and routing protocols. It detects forwarding path failure at a uniform
rate, rather than the variable rates for different protocol hello mechanisms.
This document explains the configurations for Aviat Networks BFD running as a part of Aviat
Networks AOS. The reader is expected to have a basic knowledge of the protocol as a pre-requis-
ite.
This document is intended for users involved in using the Aviat Networks BFD product with
other protocols in the router-stack.
Acronyms
Acronyms
Acronym Explanation
BFD Bi-directional Forwarding Detection
CC Continuity Check
CV Connection Verification
FRR Fast-Re-Route
GACH Generic Associated Channel Header
GAL Generalized Alert Label
LER Label Edge Router
LSP Label Switched Path
LSR Label Switch Router
ME Maintenance Entity
MEG Maintenance Entity Group
MEP Maintenance Entity Group End Point
MIP Maintenance Entity Group Intermediate Point
MPLS-OAM MPLS Operations, Administration and Maintenance
MPLS-TP MPLS Transport Profile
260-668256-005 JULY 2015 VII

MPLS-TP LSP Uni-directional or Bidirectional Label Switched Path

OSPF Open Shortest Path First
P2P Point-to-point
PDU Packet Data Unit
PW Pseudowire
RDI Remote Defect Indication
SLA Service Level Agreement
SPME Sub-Path Maintenance Element
TTL Time To Live
VCCV Virtual Circuit Connectivity Verification
References
1. RFC 5654 – Requirements of an MPLS Transport Profile
2. draft-ietf-mpls-tp-framework-12 – A framework for MPLS in Transport Networks
3. draft-ietf-mpls-tp-oam-framework-06 – MPLS-TP OAM Framework
4. draft-ietf-mpls-tp-framework-12 – A Framework for MPLS in Transport Network
5. rfc5586 - G-ACh and GAL
6. RFC 5881 - BFD for IPv4 and IPv6 (Single Hop)
7. RFC 5880 - Generic Application of Bidirectional Forwarding
8. RFC 5883 - BFD for Multihop Paths
9. RFC 5885 - Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual
Circuit Connectivity Verification (VCCV)
10. PICS document for Aviat Networks BFD
Document Conventions
Table 1-1. Conventions Used in this Document
Convention Usage
Code text CLI (Command Line Interface) Com-
mands
Code Italics User Inputs to Command
Blue code CLI Command output
Red code Output of the configured value
General Configurations
VIII AVIAT NETWORKS
The Aviat Networks BFD is configurable and managed by CLI anterfaces. This section describes
the preliminary configurations of Aviat Networks BFD.
Basic CLI Command Modes

This section describes the various command modes available in the CLI configuration for BGP.
Table 1-2. CLI Command Modes
Command Mode Access Method Prompt Exit method
User EXEC This is the initial mode aos> The logout
to start a session. method is used.
Privileged EXEC The User EXEC mode aos# The command
command enable, is disable is used to
used to enter the Priv- return to the
ileged EXEC mode. User EXEC
mode.
Global Con- The Privileged EXEC aos(config)# The command
figuration mode command con- exit / end is used
figure terminal, is used to exit to the
to enter the Global Con- Privileged EXEC
figuration Mode. mode.
Interface Con- The Global Con- aos(config-if)# The command
figuration figuration Mode com- exit is used to
mand interface exit to the
<interface-type><in- Global Con-
terface-id>, is used to figuration mode.
enter the Interface Con- The command
figuration Mode. end is used to
exit to the Priv-
ileged EXEC
mode.
Switch Con- The Global Con- aos(config-switch) The command
figuration figuration mode com- # exit is used to
mand switch <switch exit to the
name> is used to enter Global Con-
the Switch Con- figuration mode.
figuration mode The command
end is used to
exit to the Priv-
ileged EXEC
mode.
BFD Session The Global Con- aos(config-bfd- The command
Configuration figuration mode com- sess)# exit is used to
mand bfd session exit to the
<session-index> is used Global Con-
to enter the BFD Ses- figuration mode.
sion Configuration The command
mode. end is used to
exit to the Priv-
ileged EXEC
260-668256-005 JULY 2015 IX

mode.
Default Configurations
Table 1-3. Default Configurations
Parameter Default Setting
BFD Administrative System Control Status start
BFD Global Operational Mode Asynchronous Mode without Echo func-
tion.
BFD Global Minimum Tranmit Interval 1 second
BFD Global Minimum Reception Interval 1 second
BFD Global Detection Time Multiplier 3 seconds
BFD Global Slow Transmaosion Interval 1 second
BFD Session Role Active
BFD Session Mode CC (Continuity Check)
BFD Session Timer Negotiation Enabled
BFD Session Offloading Disabled
BFD Trap Notifications Session UP and DOWN notifications
enabled
BFD Session Admin Status Enabled
BFD Version Number BFD Version 1 (RFC5880)
BFD Session State DOWN
BFD Demand Mode Disabled
BFD Control Plane Independency Disabled
BFD Generalized TTL Security Mechanism Disabled
(GTSM)
BFD Session Authentication Disabled
X AVIAT NETWORKS
Protocol Description
Aviat Networks BFD implements the Bi-directional Forwarding Detection described in the RFC
5880. BFD is a detection protocol designed to provide fast forwarding-path failure detection
times for media types, encapsulations, topologies and routing protocols. BFD can be used to
detect forwarding path failures at a uniform rate, rather than the variable rates for different pro-
tocol hello mechanisms.
BFD makes network profiling and planning easier and reconvergence time consistent and pre-
dictable. BFD provides subsecond failure detection between two adjacent devices and can be less
CPU-intensive than protocol hello messages because some of the BFD load can be distributed
onto the data plane on supported modules.
Aviat Networks BFD supports path monitoring for the following protocols:
l Static IPv4
l BGP
l OSPF
l MPLS
260-668256-005 JULY 2015 XI

Chapter 2. BFD Topologies and

Configurations
This section provides sample deployment scenarios used for the configuration steps given in
this document.
The following sub sections depict sample topologies that can be used for configuring and testing
the basic features of Aviat Networks BFD.
Configuration and Testing Topologies
Sample Topology Scenarios for Configuring and

Testing BFD
This figure depicts the sample topology used for configuring and testing BFD.
Figure 2-1. BFD Configuration and Testing Topology

The description is as follows:
l R1, R2 and R3 represent routers in which AOS is installed.
l VLAN2 and VLAN3 represent the VLAN interfaces of the AOS routers.
lEach AOS switch has a router ID.
Table 2-1. IPv4 Addresses of Interfaces in the Routers and Hosts
Router / Host Interface Slot IPv4 Address /
Mask
R1 Vlan2 0/2 20.0.0.1 / 255.0.0.0
R2 Vlan2 0/2 20.0.0.2 / 255.0.0.0
Vlan3 0/3 30.0.0.2 / 255.0.0.0
R3 Vlan3 0/2 30.0.0.3 / 255.0.0.0
260-668256-005 JULY 2015 XII

CHAPTER 2. BFD TOPOLOGIES AND CONFIGURATIONS
BFD Configurations
The Aviat Networks BFD software has been designed in accordance with the FSAP2 (Flexible
Software Architecture for Portability) to ensure a high level of portability
This section describes the configuration of the following Aviat Networks BFD features using CLI
interfaces.
l Configuring BFD over Static IPv4 path
l Configuring BFD over OSPF
l Configuring BFD over BGP
Preliminary Configurations
This section describes the preliminary configurations and the configurations for the topologies
of Aviat Networks BFD. Configuration of Aviat Networks BFD feature is done by accessing the
Global configuration mode or the Interface configuration mode. The configuration steps
described in this document begin with accessing one or both of these modes. The following
points are part of the preliminary configurations.
Configuring AOS1 in Topology for Testing Aviat

Networks BFD
F or enterpri se package, ports are automati cal l y mapped to defaul t swi tch.
Execute the following commands to configure AOS1 in Topology for Testing Aviat Networks
BFD:
aos# configure terminal
aos(config)# interface vlan 3
aos(config-if)# shutdown
aos(config-if)# ip address 12.0.0.1 255.0.0.0
aos(config-if)# no shutdown
aos(config-if)# end

aos(config)# interface gigabitethernet 0/1
aos(config-if)# map switch default
aos(config-if)# end

aos(config-switch)# vlan 3
aos(config-switch-vlan)# ports gigabitethernet
0/1
aos(config-switch-vlan)# end
XIII AVIAT NETWORKS


aos(config-if)# switchport pvid 1
aos(config-if)# end

aos(config-if)# end

aos(config-if)# end

0/2
aos(config-if)# end
Verify the VLAN configurations using the
following command:
aos# show ip interface
Vlan1 is up, line protocol is up
Internet Address is 12.0.0.1/8
Broadcast Address 12.255.255.255


Networks BFD
Execute the following commands to configure AOS2
in Topology for testing Aviat Networks BFD.
260-668256-005 JULY 2015 XIV


aos(config-if)# end

aos(config-if)# end

0/1
aos(config-if)# end

aos(config-if)# end

aos(config-if)# end

0/2
aos(config-if)# end
XV AVIAT NETWORKS

aos(config-if)# end

aos(config-if)# end

0/3
aos(config-if)# end
Verify the VLAN configurations using the following command:

Networks BFD
Execute the following commands to configure AOS3 in Topology for testing Aviat Networks
BFD.
260-668256-005 JULY 2015 XVI


aos(config-if)# end

aos(config-if)# end

0/1
aos(config-if)# end

aos(config-if)# end

aos(config-if)# end

0/2
aos(config-if)# end
Verify the VLAN configurations using the following command:
XVII AVIAT NETWORKS


Configuring BFD over Static IP path

This feature allows user to monitor IP neighbor reachability using BFD. User can configure the
neighbor statically. IP will move static routes (with next hop as neighbor) to pending state
when BFD notifies the neighbor is not reachable.
CLI Configurations
AOS can be configured with BFD over both singlehop and multihop static IP path.
Execute the following commands at R1:
Adding a static route at R1 to reach R3 via R2
aos(config)# ip route 30.0.0.0 255.0.0.0
20.0.0.2
aos(config)# exit
aos#
Configuring BFD Session:
aos(config)# bfd session 1
aos(config-bfdsess)# bfd ipv4 20.0.0.2 vlan 2
aos(config-bfdsess)# bfd enable
aos(config-bfdsess)# end
Configuring BFD session:
aos(config-bfdsess)# bfd ipv4 20.0.0.1 vlan 2
260-668256-005 JULY 2015 XVIII

Adding a static route at R3 to reach R1 via R2:

aos(config)# ip route 20.0.0.0 255.0.0.0
30.0.0.2
aos(config)# exit
aos#
Verify the BFD session state by executing the following show command.
aos# show bfd session details
Switch default
Session Index:1
Session Status : enabled, Session Admin Status :
start
Version:1, desired tx interval:1s , required rx
interval:1s
Multiplier:3, diag:0, My discr:1, your discr:1,
state UP, D/C/M/A:0/0/0/0
Role: Active, Sess Mode: CC, Exp: 0
Oper Mode:Asynchronous Without Echo Function
Sess Type: Single hop
Timer Negotiation:Enabled
Local negotiated async tx interval:1s , Negotiated
Detect Multiplier:3
Dest UDP port: 0, Src UDP port: 0
Remote Heard Flag: True
Authentication : disabled, Authentication
Type:None
Authentication Key:None
Authentication Key ID:None
Offload:Disabled, Card Number:0, Slot Number:0
Src Ip Addr:20.0.0.1, Dest Ip Addr:20.0.0.2
Admin Ctrl Required:Disabled,Admin Ctrl Err
Reason:None
Switch default
Session Index:2
start
interval:1s
XIX AVIAT NETWORKS


Detect Multiplier:3
Type:None

Reason:None
Shutdown interface gi 0/2 at R2:
aos(config)# int gi 0/2
aos(config)# shutdown
aos(config)# exit
Verify the BFD session state by executing the following show command.
Switch default
Session Index:1
start
interval:1s
state DOWN, D/C/M/A:0/0/0/0
Detect Multiplier:3
Type:None
260-668256-005 JULY 2015 XX


Reason:None
Switch default
Session Index:2
start
interval:1s
Detect Multiplier:3
Type:None
Reason:None
Configuring BFD over OSPF

This feature allows OSPF to detect its unreachable neighbor devices faster. As soon as the device
detects BFD failure, BFD notifies about neighbors that cannot be reached via OSPF. This will
provide faster convergence. See the OSPF manuals for more information.
CLI Configurations
BFD can be used to monitor the IP path between OSPFv2 neighbors.
Configuring OSPF router
aos(config)# router ospf
XXI AVIAT NETWORKS

aos(config-router)# network 20.0.0.1 area

0.0.0.0
aos(config-if)# end
aos#
Configuring BFD on OSPF router
aos(config-router)# enable bfd
aos(config-router)# bfd all-interface
aos(config)# end
Configuring OSPF router
aos(config-router)# network 20.0.0.2 area
0.0.0.0
aos(config-router)# end
aos#
Configure BFD on OSPF router
aos(config)# enable bfd
aos(config)# bfd all-interface
aos(config)# end
View the BFD status:
aos# show ip ospf neighbor
Vrf default
Neighbor-ID Pri State DeadTime Address
Interface Helper
----------- --- ----- -------- -------
--------- --------- ------------ --------- ----
-
12.0.0.2 1 FULL/DR 33 20.0.0.2
vlan1 Not Helping
HelperAge HelperER Bfd
--------------- --------------- --------
0 None enabled
Switch default
Session Index:1
start
260-668256-005 JULY 2015 XXII


interval:1s
Detect Multiplier:3
Type:None
Registered Protocols: OSPF
Reason:None
Shutdown the interface gi 0/2 at R2:
aos(config)# exit
Verify if the BFD status becomes disabled and the
BFD session session goes down.
aos# show ip ospf neighbor
Vrf default
Neighbor-ID Pri State DeadTime Address
Interface Helper
----------- --- ----- -------- -------
--------- --------- ------------ --------- ----
-
12.0.0.2 1 FULL/DR 33 20.0.0.2
vlan1 Not Helping
HelperAge HelperER Bfd
--------------- --------------- --------
0 None disabled
Switch default
XXIII AVIAT NETWORKS

Session Index:1
start
interval:1s
Local negotiated async tx interval:0s, Negotiated
Detect Multiplier:0
Remote Heard Flag: False
Type:None
Registered Protocols: OSPF
Reason:None
Configuring BFD Monitoring for BGP Neighbors

This feature allows BGP to detect its remote neighbors faster. BFD notifies neighbors that can-
not be reached by BGP as soon as it detects BFD packet failure. This provides faster con-
vergence.
By default BFD monitoring is disabled for the BGP peers. When BFD monitoring is enabled,
BGP registers with BFD for monitoring the particular neighbor path after the BGP session
becomes ESTABLISHED.
When BFD detects the path failure, it informs BGP about the path status change.
CLI Configuration
Execute the following commands to configure BGP routing.
Configuring BGP neighbor in R1 and enabling BFD for it
aos(config)# router bgp 100
aos(config-router)# neighbor 20.0.0.2 remote-as
200
260-668256-005 JULY 2015 XXIV

aos(config-router)# neighbor 20.0.0.2 fall-over

bfd
Configuring BGP neighbor in R2 and enabling BFD for it
aos(config)# router bgp 200
aos(config-router)# neighbor 20.0.0.1 remote-as
100
aos(config-router)# neighbor 20.0.0.1 fall-over
bfd
View the output using the show command mentioned
below at R1;
aos# show ip bgp neighbor
Context Name : default
BGP neighbor is 20.0.0.2, remote AS 200, external
link
BGP version 4, remote router ID 20.0.0.2
Network Address: None
BGP state = Established, up for 7 seconds, un-
authenticated session
Configured BGP Maximum Prefix Limit 5000
AutomaticStart DISABLED
AutomaticStop DISABLED
DampPeer Oscillations DISABLED
DelayOpen DISABLED
Configured Connect Retry Count 5
Current Connect Retry Count 0
Default-originate : DISABLED
Peer Passive : DISABLED
Peer Status : NOT DAMPED
GateWay Address : NONE
Rcvd update before 5 secs, hold time is 90,
keepalive interval is 30 secs
Neighbors Capability:
Route-Refresh: Advertised and received
4-byte ASN: Advertised and received
Address family IPv4 Unicast: Advertised and
received
AF-dependant capabilities:
Outbound Route Filter (ORF) type : (64)
Address Prefix based ORF
Send-mode : not supported
Receive-mode : not supported
XXV AVIAT NETWORKS

BFD Monitoring : Enabled

Received 3 messages, 1 Updates
Sent 3 messages, 0 Updates
Route refresh: Received 0, sent 0.
Minimum time between advertisement runs is 30
seconds
Connections established 1 time(s)
Graceful Restart Capability: advertised and
recevied
Remote Restart timer is 90
Local host: 20.0.0.1, Local port: 179
Foreign host: 20.0.0.2, Foreign port: 52696
Last Error: Code 0, SubCode 0.
Update Source 20.0.0.1
Next-Hop is automatic
MultiHop Status - disabled
Send-Community is standard,extended

Switch default
Session Index:1
start
interval:1s
Detect Multiplier:3
Type:None
260-668256-005 JULY 2015 XXVI

Registered Protocols: BGP

Reason:None
View the output using the show command mentioned below at R2;
------------
link
BGP state = Established, up for 2 minutes 10
seconds, un-authenticated session
DelayOpen DISABLED
Neighbors Capability:
Route-Refresh: Advertised and received
4-byte ASN: Advertised and received
Address family IPv4 Unicast: Advertised and
received
AF-dependant capabilities:
Outbound Route Filter (ORF) type : (64)
Address Prefix based ORF
Send-mode : not supported
Receive-mode : not supported
seconds
XXVII AVIAT NETWORKS


Graceful Restart Capability: advertised and
recevied
Remote Restart timer is 90
Switch default
Session Index:1
start
interval:1s
Detect Multiplier:3
Type:None
Reason:None
Shutdown interface gi 0/2 at R2:
aos(config)# exit
260-668256-005 JULY 2015 XXVIII

View the output using the show command mentioned

below at R1;

------------

link
BGP state = Connect
DelayOpen DISABLED
seconds
Graceful Restart Capability: advertised
XXIX AVIAT NETWORKS


Switch default
Session Index:1
start
interval:1s
Detect Multiplier:3
Type:None
Reason:None
View the output using the show command mentioned below at R2;
------------

link
BGP state = Idle
DelayOpen DISABLED
260-668256-005 JULY 2015 XXX


seconds
Graceful Restart Capability: advertised
Switch default
Session Index:1
start
interval:1s
Detect Multiplier:3
XXXI AVIAT NETWORKS


Type:None
Reason:None
260-668256-005 JULY 2015 XXXII

260-668256-010
WWW.AVIATNETWORKS.COM

CTR 8500-8300 3.0 BFD Config July2015 260-668256-010

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CTR 8500-8300 3.0 BFD Config July2015 260-668256-010

Uploaded by

Copyright:

Available Formats

CTR 8300/8500 CONFIGURATION

260-668256-005 JULY 2015 I

Aviat Networks Technical & Sales

Sales and Sales Support

Product Compliance Notes

International Use of 5.8GHz

260-668256-005 JULY 2015 III

Declaration of Conformity, R&TTE Directive, 1999/5/EC

260-668256-005 JULY 2015 V

Chapter 1. BFD Introduction

Purpose and Scope

260-668256-005 JULY 2015 VII

MPLS-TP LSP Uni-directional or Bidirectional Label Switched Path

Red code Output of the configured value

Basic CLI Command Modes

260-668256-005 JULY 2015 IX

260-668256-005 JULY 2015 XI

Chapter 2. BFD Topologies and

Configuration and Testing Topologies

Sample Topology Scenarios for Configuring and

Figure 2-1. BFD Configuration and Testing Topology

260-668256-005 JULY 2015 XII

Configuring AOS1 in Topology for Testing Aviat

aos# configure terminal

aos# configure terminal

XIII AVIAT NETWORKS

aos(config)# interface gigabitethernet 0/1

aos# configure terminal

aos# configure terminal

aos# configure terminal

Vlan2 is up, line protocol is up

Configuring AOS2 in Topology for Testing Aviat

260-668256-005 JULY 2015 XIV

aos# configure terminal

aos# configure terminal

aos# configure terminal

aos# configure terminal

aos# configure terminal

aos# configure terminal

aos# configure terminal

aos# configure terminal

aos# configure terminal

Configuring AOS3 in Topology for Testing Aviat

260-668256-005 JULY 2015 XVI

aos(config-if)# ip address 12.0.0.3 255.0.0.0

aos# configure terminal

aos# configure terminal

aos# configure terminal

aos# configure terminal

aos# configure terminal

XVII AVIAT NETWORKS

Internet Address is 12.0.0.3/8

Configuring BFD over Static IP path

260-668256-005 JULY 2015 XVIII

Adding a static route at R3 to reach R1 via R2:

XIX AVIAT NETWORKS

Oper Mode:Asynchronous Without Echo Function

Admin Ctrl Required:Disabled,Admin Ctrl Err

260-668256-005 JULY 2015 XX

Offload:Disabled, Card Number:0, Slot Number:0

Configuring BFD over OSPF

XXI AVIAT NETWORKS

aos(config-router)# network 20.0.0.1 area