BSR64K-R6 3 1-RoutingGuide

BSR 64000 Routing
Configuration and
Management Guide
Compass ID: 389959760 Version 4
Release 6.3.1
Notice
EXCEPT AS INDICATED IN THE APPLICABLE SYSTEM PURCHASE AGREEMENT, THE SYSTEM,
DOCUMENTATION AND SERVICES ARE PROVIDED "AS IS", AS AVAILABLE, WITHOUT WARRANTY OF
ANY KIND. MOTOROLA MOBILITY, INC. DOES NOT WARRANT THAT THE SYSTEM WILL MEET
CUSTOMER'S REQUIREMENTS, OR THAT THEIR OPERATION WILL BE UNINTERRUPTED OR
ERROR-FREE, OR THAT ANY ERRORS CAN OR WILL BE FIXED. MOTOROLA MOBILITY, INC. HEREBY
DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, ORAL OR WRITTEN, WITH RESPECT
TO THE SYSTEM AND SERVICES INCLUDING, WITHOUT LIMITATION, ALL IMPLIED WARRANTIES OF
TITLE, NON-INFRINGEMENT, INTEGRATION, MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR
PURPOSE AND ALL WARRANTIES ARISING FROM ANY COURSE OF DEALING OR PERFORMANCE OR
USAGE OF TRADE.
EXCEPT AS INDICATED IN THE APPLICABLE SYSTEM PURCHASE AGREEMENT, MOTOROLA
MOBILITY, INC. SHALL NOT BE LIABLE CONCERNING THE SYSTEM OR SUBJECT MATTER OF THIS
DOCUMENTATION, REGARDLESS OF THE FORM OF ANY CLAIM OR ACTION (WHETHER IN
CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE), FOR ANY (A) MATTER BEYOND ITS
REASONABLE CONTROL, (B) LOSS OR INACCURACY OF DATA, LOSS OR INTERRUPTION OF USE, OR
COST OF PROCURING SUBSTITUTE TECHNOLOGY, GOODS OR SERVICES, (C) INDIRECT, PUNITIVE,
INCIDENTAL, RELIANCE, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING, BUT
NOT LIMITED TO, LOSS OF BUSINESS, REVENUES, PROFITS OR GOODWILL, OR (D) DIRECT
DAMAGES, IN THE AGGREGATE, IN EXCESS OF THE FEES PAID TO IT HEREUNDER FOR THE SYSTEM
OR SERVICE GIVING RISE TO SUCH DAMAGES DURING THE 12-MONTH PERIOD PRIOR TO THE DATE
THE CAUSE OF ACTION AROSE, EVEN IF COMPANY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. THESE LIMITATIONS ARE INDEPENDENT FROM ALL OTHER PROVISIONS OF THIS
AGREEMENT AND SHALL APPLY NOTWITHSTANDING THE FAILURE OF ANY REMEDY PROVIDED
HEREIN.
All Motorola Mobility, Inc. products are furnished under a license agreement included with the product. If you are
unable to locate a copy of the license agreement, please contact Motorola Mobility, Inc.
No part of this publication may be reproduced in any form or by any means or used to make any derivative work (such
as translation, transformation, or adaptation) without written permission from Motorola Mobility, Inc.
Motorola Mobility reserves the right to revise this publication and to make changes in content from time to time
without obligation on the part of Motorola Mobility to provide notification of such revision or change. Motorola
Mobility provides this guide without warranty of any kind, implied or expressed, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose. Motorola Mobility may make
improvements or changes in the product(s) described in this manual at any time.
MOTOROLA and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings,
LLC. All other trademarks are the property of their respective owners.
2011 Motorola Mobility, Inc. All rights reserved.
Release 6.3.1
Published: 12/11
Compass ID: 389959760 Version 4 iii
Contents
Contents
Preface
Scope ............................................................................................................................................ xv
Audience....................................................................................................................................... xv
Documentation Set ....................................................................................................................... xv
Conventions...............................................................................................................................xviii
Notes, Cautions, Warnings .......................................................................................................... xix
If You Need Help.......................................................................................................................... xx
Telephone Support............................................................................................................. xx
Online Support.................................................................................................................. xxi
Motorola BSR Customer Website...................................................................... xxi
1 Introduction
2 Configuring Policy-based Routing
Overview.....................................................................................................................................2-1
About Policy-based Routing .......................................................................................................2-2
Route-maps .................................................................................................................................2-2
Access Lists and Groups ..................................................................................................2-3
Configuring Access Lists ...................................................................................2-3
Configuring an IP Access Group .......................................................................2-4
Configuring Route-maps .................................................................................................2-4
BSR 64000 Routing Configuration and Management Guide Release 6.3.1
iv Compass ID: 389959760 Version 4
Match Statements...............................................................................................2-5
Set Statements ...................................................................................................2-6
Enabling Policy-based Routing .......................................................................................2-8
Enabling Local Policy-based Routing .............................................................................2-8
Monitoring Routing Policy Information ....................................................................................2-9
3 Configuring IP Multicast Routing
Overview ....................................................................................................................................3-1
About Multicast Routing.............................................................................................................3-2
Enabling IP Multicast Routing on the BSR ................................................................................3-2
Hardware Assisted Multicast .....................................................................................................3-3
Specifying Fastpath Multicast Flow Priority ...................................................................3-3
Displaying Hardware Assisted Multicast Information.....................................................3-3
Configuring PIM ........................................................................................................................3-4
About PIM........................................................................................................................3-5
Enabling PIM....................................................................................................................3-5
Configuring PIM Rendezvous Points...............................................................................3-6
Configuring a Static PIM Rendezvous Point .....................................................3-6
Configuring Candidate RPs ..............................................................................3-7
Configuring PIM Designated Routers..............................................................................3-8
Setting the Designated Router Priority ..............................................................3-8
Modifying the PIM Router-Query Message Interval .........................................3-9
Configuring Bootstrap Routers ........................................................................................3-9
Defining the PIM Domain Border ................................................................................. 3-11
Accepting Select Join and Prune Messages.................................................................... 3-11
Delaying Shortest Path Tree Usage for Better Throughput ...........................................3-12
Configuring the Type of PIM Packet Checksum ...........................................................3-13
Retrieving PIM Unicast Routes .....................................................................................3-13
Configuring PIM-SSM ..................................................................................................3-14
Configuring PIM-SSM IP Address Range.......................................................3-14
Configuring IGMP V3 Static Group for PIM-SSM ........................................3-15
Configuring DVMRP ...............................................................................................................3-16
About DVMRP...............................................................................................................3-16
Enabling DVMRP on the Router....................................................................................3-17
Release 6.3.1 Contents
Compass ID: 389959760 Version 4 v
Configuring the DVMRP Route Expiration Threshold..................................................3-18
Configuring the DVMRP Route Reporting Threshold...................................................3-18
Setting the DVMRP Prune Lifetime Value ....................................................................3-18
Configuring DVMRP on a Routing Interface ................................................................3-19
Filtering Incoming DVMRP Reports...............................................................3-19
Filtering Outgoing DVMRP Routing Reports .................................................3-19
Distributing the Default DVMRP Network to Neighbors ..............................3-19
Adding a Metric Offset to the DVMRP Route.................................................3-20
Setting the DVMRP Neighbor Time-out Interval ............................................3-20
Delaying DVRMP Reports ..............................................................................3-21
Setting the DVMRP Probe Interval .................................................................3-21
Rejecting a DVMRP Non-pruning Neighbor...................................................3-22
Configuring a DVMRP Summary Address ....................................................3-22
Configuring IGMP on an Interface ..........................................................................................3-23
About IGMP...................................................................................................................3-23
IGMP Version 3 .............................................................................................................3-24
Enabling IGMP...............................................................................................................3-24
Controlling Access to IP Multicast Groups ...................................................................3-24
Changing the IGMP Version .........................................................................................3-25
Modifying the IGMP Host-Query Message Interval .....................................................3-26
Specifying the IGMP Querier Time-out Interval ..........................................................3-26
Changing the Maximum Query Response Time ............................................................3-27
Configuring the BSR as a Static Multicast Group Member ..........................................3-27
Managing IP Multicast Routing on the BSR ............................................................................3-28
Configuring an IP Multicast Static Route .....................................................................3-28
Changing the Distance for a Unicast Multicast Route ..................................................3-28
Changing the Distance for a Static Multicast Route ......................................................3-29
Clearing IP Multicast Information..................................................................................3-29
Removing a DVMRP Prune.............................................................................3-29
Removing a DVMRP Route ............................................................................3-30
Clearing IGMP Statistics .................................................................................3-30
Removing the IP Multicast Cache ...................................................................3-30
Gathering IP Multicast Information .........................................................................................3-31
Displaying General IP Multicast Information................................................................3-31
vi Compass ID: 389959760 Version 4
Displaying PIM Information .........................................................................................3-33
Displaying DVMRP Information ..................................................................................3-33
Displaying IGMP Information ......................................................................................3-34
Displaying Reverse Path Forwarding Information ........................................................3-35
4 Configuring RIP
Overview ....................................................................................................................................4-1
About RIP ...................................................................................................................................4-2
Specifications ...................................................................................................................4-3
Enabling RIP ..............................................................................................................................4-3
Configuring RIP Optional Parameters ........................................................................................4-4
Specifying a RIP Version .................................................................................................4-4
Enabling or Disabling Split Horizon ...............................................................................4-5
Enabling Route Summarization .......................................................................................4-6
Applying an Offset List ...................................................................................................4-6
Enabling RIP Authentication ...........................................................................................4-7
Configuring MD5 Authentication for RIP V2 ...................................................4-8
Configuring Interpacket Delay ........................................................................................4-9
Configuring Timers .........................................................................................................4-9
Example ...........................................................................................................4-10
Configuring a Passive Interface for RIP ........................................................................4-10
Redistributing Routes into RIP ................................................................................................ 4-11
Assigning a Default Metric Value for Redistributed Routes .........................................4-12
Gathering RIP Information .......................................................................................................4-13
5 Configuring RIP over VRF
Introduction .................................................................................................................................5-1
RIP Over VRF.............................................................................................................................5-1
Entering/Exiting RIP IPv4 VRF Address Family Configuration Mode ....................................5-2
Specifying an MPLS-BGP Network ...........................................................................................5-3
Enabling Route Summarization .................................................................................................5-3
Redistributing Routes into RIP ..................................................................................................5-4
Assigning a Default Metric Value for Redistributed Routes ...........................................5-5
Displaying RIP over VRF Information .......................................................................................5-5
Compass ID: 389959760 Version 4 vii
show ip protocols ...............................................................................................5-5
show ip rip database vrf .....................................................................................5-6
show ip route vrf ................................................................................................5-6
6 Configuring OSPF
Overview.....................................................................................................................................6-1
About OSPF ...............................................................................................................................6-2
Specifications ...................................................................................................................6-2
Enabling OSPF............................................................................................................................6-2
OSPF Graceful Restart ...............................................................................................................6-3
Enabling OSPF Graceful Restart......................................................................................6-4
Enabling Helper Mode on the BSR..................................................................................6-5
Redistributing Routes into OSPF ....................................................................................6-5
Assigning a Default Metric Value for Redistributed Routes .............................6-6
Configuring OSPF Area Parameters ..........................................................................................6-7
Configuring OSPF Area Authentication Parameters........................................................6-7
Configuring OSPF Stub Areas ........................................................................................6-9
Configuring OSPF Not-So-Stubby Area .......................................................................6-10
Configuring Route Summarization between OSPF Areas ............................................ 6-11
Configuring Route Summarization into OSPF Areas ...................................................6-12
Managing OSPF on the BSR ....................................................................................................6-13
Establishing a Virtual Link ............................................................................................6-13
Monitoring OSPF Virtual Links ......................................................................6-16
Assign a Default Route for an ASBR.............................................................................6-16
Controlling OSPF Link Cost Metrics ............................................................................6-17
Allowing Dynamic OSPF Virtual Links ........................................................................6-17
Changing OSPF Administrative Distances ...................................................................6-17
Configuring Route Calculation Timers .........................................................................6-18
Configuring OSPF on an Interface ...........................................................................................6-19
Configuring General OSPF Interface Parameters .........................................................6-19
Blocking OSPF LSA Flooding ......................................................................................6-22
Configuring a Passive Interface for OSPF ....................................................................6-23
Gathering OSPF Information ....................................................................................................6-23
Displaying OSPF Routing Information..........................................................................6-24
viii Compass ID: 389959760 Version 4
Displaying Network Information.....................................................................6-24
Displaying Border Routers...............................................................................6-24
Displaying Neighboring Routers .....................................................................6-24
Displaying Virtual Links..................................................................................6-25
Displaying OSPF Interface Information.........................................................................6-26
Displaying OSPF Memory Information.........................................................................6-28
Displaying OSPF Database Information ........................................................................6-28
7 Configuring BGP
Overview.....................................................................................................................................7-1
About BGP .................................................................................................................................7-2
BGP Neighbors ................................................................................................................7-4
BGP Updates ...................................................................................................................7-4
BGP Sessions ...................................................................................................................7-5
Specifications ...................................................................................................................7-5
BGP Basic Configuration............................................................................................................7-5
Enabling BGP ..................................................................................................................7-6
Configuring a BGP Neighbor ..........................................................................................7-6
Advertising Networks in an AS........................................................................................7-8
BGP Peer Groups .......................................................................................................................7-9
Configuring BGP Peer Groups.......................................................................................7-10
Enabling EBGP Multihop for Neighbor and Peer Groups ............................................7-12
Shutting Down a Neighbor or Peer Group .....................................................................7-13
BGP Routing Policy .................................................................................................................7-14
Configuring Route-maps ...............................................................................................7-15
Match and Set Statements ................................................................................7-15
Configuring Access Lists ..............................................................................................7-17
Configuring a Standard Access List.................................................................7-17
Configuring an AS-Path Access List ...............................................................7-18
Configuring the Community Attribute ..........................................................................7-19
Creating Community Lists .............................................................................................7-20
BGP Path Selection and Configuration ....................................................................................7-24
BGP Path Selection Algorithm.......................................................................................7-24
Configuring Next Hop Processing .................................................................................7-25
Compass ID: 389959760 Version 4 ix
neighbor remote-as Command.........................................................................7-25
neighbor next-hop-self Command ...................................................................7-27
Configuring Aggregate Addresses ................................................................................7-28
Configuring BGP Administrative Weights.....................................................................7-30
Using the neighbor weight Command .............................................................7-31
Using Filter-lists and AS-Path Access Lists ....................................................7-32
Using a Route-map and Access Lists...............................................................7-33
Configuring the Local Preference .................................................................................7-33
Understanding the Origin Attribute................................................................................7-35
Understanding the AS-path Attribute.............................................................................7-38
Configuring the MED Attribute ....................................................................................7-39
Managing BGP .........................................................................................................................7-40
Configuring a Default Route .........................................................................................7-41
Assigning a Loopback Interface to a BGP Session .......................................................7-43
Enabling Message Digest 5 Authentication Between Peers ..........................................7-44
Adjusting BGP Timers ..................................................................................................7-45
Setting the Routing Updates Interval .............................................................................7-46
Controlling the Number of Prefixes ...............................................................................7-47
Setting the Administrative Distance for a Route............................................................7-48
Disabling Route Summarization ....................................................................................7-49
Enabling and Disabling Synchronization ......................................................................7-51
Redistributing Routes into BGP ....................................................................................7-53
Assigning a Default Metric Value for Redistributed Routes............................7-55
Configuring Route Flap Dampening ..............................................................................7-55
Global Route Flap Dampening ........................................................................7-56
Policy-based Route Flap Dampening...............................................................7-56
Clearing Route Flap Dampening......................................................................7-57
Reconfiguring BGP ........................................................................................................7-58
Soft Reconfiguration........................................................................................7-58
Large Scale Asynchronous Systems...............................................................................7-59
Configuring a Confederation .........................................................................................7-59
Configuring a Route Reflector ......................................................................................7-62
Configuring a Cluster-ID.................................................................................7-63
Restoring Route Reflection from a Route Reflection Client..........................................7-64
x Compass ID: 389959760 Version 4
8 Configuring VRRP
Overview ....................................................................................................................................8-1
About VRRP ...............................................................................................................................8-1
Configuring VRRP......................................................................................................................8-2
Enabling VRRP ...............................................................................................................8-3
Creating a Virtual Router .................................................................................................8-3
Configuring a Virtual IP Address ....................................................................................8-3
Configuring a Primary IP Address ...................................................................................8-4
Enabling a Virtual Router.................................................................................................8-4
Enabling Authentication ..................................................................................................8-5
Specifying Priority ...........................................................................................................8-6
Pre-empting a Master .......................................................................................................8-7
Specifying an Advertisement Interval .............................................................................8-7
Clearing Statistic Counters ...............................................................................................8-8
Gathering Virtual Router Information ........................................................................................8-9
Monitoring Critical Link States........................................................................................8-9
Monitoring Virtual Router Information..........................................................................8-10
Monitoring Ethernet Virtual Routers ............................................................... 8-11
Obtaining Summary Information.....................................................................8-12
9 Configuring MPLS
Overview ....................................................................................................................................9-1
About MPLS ...............................................................................................................................9-2
About RSVP ....................................................................................................................9-2
Configurable MPLS Entries ........................................................................................................9-3
Enabling MPLS and Basic Configuration Tasks ........................................................................9-4
Creating a Static LSP .................................................................................................................9-5
Deleting a Static LSP ........................................................................................9-7
Configuring MPLS with RSVP...................................................................................................9-7
Enabling RSVP on an Interface .......................................................................................9-7
Disabling RSVP on an Interface .......................................................................9-7
Creating a Dynamic LSP Using RSVP ...........................................................................9-8
Configuring an Explicit Route Using RSVP ...................................................................9-8
Configuring RSVP Routing Messages ............................................................................9-9
Compass ID: 389959760 Version 4 xi
Accessing MPLS and RSVP Information ................................................................................ 9-11
10 Configuring Packet Over SONET
Overview ..................................................................................................................................10-1
About SONET/SDH .................................................................................................................10-2
Specifications .................................................................................................................10-2
POS Features ..................................................................................................................10-2
POS Interface Configuration Tasks ..........................................................................................10-3
Configuring the POS Interface .......................................................................................10-3
Configuring PPP ............................................................................................................10-4
Configuring the Network Clock Source for SONET ....................................................10-6
Setting the Primary BITS Network Clocking Source ......................................10-7
Setting the Secondary BITS Network Clocking Source ..................................10-8
Deriving the Network Clocking Source from a POS Interface........................10-9
Setting Clock Recovery from the Received SONET Signal............................10-9
Configuring SONET ...............................................................................................................10-10
Optionally Disabling SONET Payload Scrambling ....................................................10-12
Changing the SONET Framing Type ..........................................................................10-12
Changing the CRC Function on the POS Interface .....................................................10-13
Defining SONET Frame Overhead Bytes ....................................................................10-13
Configuring SONET Alarms ..................................................................................................10-16
Setting Alarm Thresholds.............................................................................................10-17
Setting Alarm Reporting...............................................................................................10-18
Setting the Line Alarm Indication Signal .....................................................................10-19
Changing the POS Signal Rate ...............................................................................................10-19
Specifying the POS Loopback Mode Type ............................................................................10-20
Configuring POS Automatic Protection Switching ...............................................................10-21
Defining APS Groups for Working and Protection Interfaces .....................................10-23
Configuring an APS Interface for Bi-directional Operation..........................10-25
Defining APS Groups for Working and Protection Modules.......................................10-26
Configuring an APS Module for Bi-directional Operation............................10-28
Managing APS Interface-based Redundancy...............................................................10-29
Manually Switching an Interface ...................................................................10-29
Setting the Revert Timer ................................................................................10-30
xii Compass ID: 389959760 Version 4
Forcing an Interface to Switch.......................................................................10-31
Locking Out a Protection APS Interface........................................................10-31
Managing APS Module-based Redundancy.................................................................10-32
Manually Switching a Module.......................................................................10-32
Setting the Revert Timer ................................................................................10-34
Forcing a Module to Switch...........................................................................10-34
Locking Out a Protection APS Module .........................................................10-35
Setting APS Alarm Thresholds ....................................................................................10-36
Gathering POS Network Information ....................................................................................10-37
Displaying PPP Link and Statistics Information..........................................................10-37
Displaying POS Interface Information.........................................................................10-38
Displaying Physical SONET Link and Alarm Information .........................................10-42
Displaying APS Information .......................................................................................10-45
11 Configuring IS-IS
Introduction .............................................................................................................................. 11-1
Enabling IS-IS .......................................................................................................................... 11-2
Setting the IS-IS Operational Mode .............................................................................. 11-5
IPv4 Only ......................................................................................................... 11-5
IPv6 Only ......................................................................................................... 11-5
IPv4 and IPv6 Together.................................................................................... 11-5
Entering/Exiting IPv6 Address Family Configuration Mode ................................................... 11-6
Redistributing Routes into IS-IS .............................................................................................. 11-6
IS-IS Authentication................................................................................................................ 11-10
Specifying IS-IS Global Authentication Mode ............................................................ 11-11
Assigning IS-IS Area or Domain Passwords................................................................ 11-11
Specifying IS-IS Interface Authentication Mode......................................................... 11-12
Configuring an Interface Message Digest Key ............................................................ 11-12
Assigning a Password to an IS-IS Interface ................................................................. 11-12
Managing IS-IS on the BSR.................................................................................................... 11-13
Specifying Router-Level Support ................................................................................. 11-13
Configuring a Default Route into an IS-IS Domain..................................................... 11-14
Configuring the Administrative Distance for IS-IS...................................................... 11-14
Configuring Maximum Paths for IS-IS IPv6 ................................................. 11-14
Compass ID: 389959760 Version 4 xiii
Summarizing IP Address Ranges ................................................................................. 11-15
Enabling the LSP Overload Bit ................................................................................... 11-15
Configuring the SPF Hold Time .................................................................................. 11-16
Configuring a Passive Interface for IS-IS ................................................................... 11-16
Configuring IS-IS on an Interface .......................................................................................... 11-17
Specifying the Interface Circuit Type........................................................................... 11-18
Configuring IS-IS Link-State Cost Metrics.................................................................. 11-18
Setting the Advertised Hello Interval ........................................................................... 11-19
Specifying the Advertised Hello Multiplier ................................................................. 11-19
Setting the Advertised CSNP Interval .......................................................................... 11-20
Setting the LSP Interval................................................................................................ 11-20
Setting the LSP Retransmission Interval ...................................................................... 11-21
Setting the LSP Retransmit Throttle Interval ............................................................... 11-21
Setting the Designated Router Priority......................................................................... 11-21
Displaying IS-IS Information ................................................................................................. 11-22
show clns interface......................................................................................... 11-22
show clns is-neighbors ................................................................................... 11-23
show clns neighbors ....................................................................................... 11-23
show clns protocols........................................................................................ 11-23
show clns traffic ............................................................................................. 11-23
show ip redistribute........................................................................................ 11-24
show ipv6 protocols ....................................................................................... 11-24
show ipv6 route isis........................................................................................ 11-24
show isis database .......................................................................................... 11-24
show isis hostname......................................................................................... 11-25
show isis neighbors ........................................................................................ 11-25
show isis spf-log............................................................................................. 11-25
show isis topology.......................................................................................... 11-25
Index
Compass ID: 389959760 Version 4 xv
Preface
Scope
This document describes how to configure and manage the Motorola Broadband
Services Router 64000 (BSR 64000) for connectivity to your IP network.
Various routing options are available for configuring the BSR 64000 as a router.
Audience
This document is for use by those persons who will configure and manage the
BSR 64000 product. Only trained service personnel should configure and maintain
the BSR 64000.
Documentation Set
The following documents comprise the BSR 64000 documentation set:
n BSR 64000 Quick Start Guide
The quick start guide provides a "roadmap" to the tasks involved in physically
installing the BSR 64000 product, physically connecting it to your network/HFC
infrastructure, and performing configuration tasks to enable the BSR 64000 to
operate in your networking environment.
xvi Compass ID: 389959760 Version 4
n BSR 64000 Chassis Installation Guide
This guide provides detailed instructions for physically installing the BSR 64000
product including: procedures for rack mounting, making physical network cable
connections, connecting DC power, and for determining the status of the BSR
64000 after applying power to it. This document also provides a description of the
BSR 64000 chassis, its hardware components and modules.
n BSR 64000 Module Installation Guide
This guide contains procedures for installing additional and replacement
Resource and I/O Modules in a BSR 64000 chassis and for making physical cable
connections to the modules.
n BSR 64000 Command Line Interface Users Guide
For users, this guide describes the structure of the BSR 64000 Command Line
Interface (CLI) and its various command modes. It also provides rules and
guidelines for navigating through the CLI.
n BSR 64000 Command Reference Guide
This guide contains individual descriptions of the entire set of commands that
comprise the BSR 64000 Command Line Interface (CLI). These commands are
used to interface with, configure, manage, and maintain the BSR 64000.
n BSR 64000 System Administration Guide
For system administrators, this guide provides detailed procedures for performing
initial configuration tasks including setting up: user accounts and passwords;
telnet and console access; system logging; and associated servers such as DHCP,
DNS, etc.
n BSR 64000 CMTS Configuration and Management Guide
This guide provides the instructions and procedures for configuring and
managing BSR 64000 CMTS operation.
n BSR 64000 Routing Configuration and Management Guide
This guide contains the instructions and procedures for configuring and managing
BSR 64000 routing operation, including RIP, OSPF, and BGP.
Release 6.3.1 Preface
Compass ID: 389959760 Version 4 xvii
n BSR 64000 SNMP Configuration and Management Guide
managing BSR 64000 Simple Network Management Protocol (SNMP) operation.
It also describes SNMP MIBs; provides information that describes standard and
proprietary MIB support; describes how to walk MIBs; and how to compile and
load SNMP MIBs.
n BSR 64000 BGP/MPLS VPN Configuration Guide
managing the BSR 64000 to support and implement Border Gateway Protocol/
MultiProtocol Label Switching Virtual Private Networks (BGP/MPLS VPNs).
n BSR 64000 Troubleshooting Guide
This guide contains instructions and procedures for troubleshooting typical
configuration problems that might be encountered using the BSR 64000. It also
offers suggestions for information to record, and have available should the need
arise to call Motorola support for assistance with BSR 64000 operational
problems.
n BSR 64000 Release Notes
These documents are specific to each release of the BSR 64000 product (software
and hardware). Release notes provide information about features not documented
or incorrectly documented in the main documentation set; known problems and
anomalies; product limitations; and problem resolutions.
xviii Compass ID: 389959760 Version 4
Conventions
This document uses the conventions in the following table:
Convention Example Explanation
angle brackets < > ping <ip-address>
ping 54.89.145.71
Arguments in italic and enclosed by angle
brackets must be replaced by the text the
argument represents. In the example,
54.89.145.71 replaces <ip-address>. When
entering the argument, do not type the angle
brackets.
bar brackets [ ] disable [level] Bar brackets enclose optional arguments. The
example indicates you can use the disable
command with or without specifying a level.
Some commands accept more than one
optional argument. When entering the
argument, do not type the bar brackets.
bold text cable relay-agent-option Boldface text must be typed exactly as it
appears.
brace brackets {} page {on | off} Brace brackets enclose required text. The
example indicates you must enter either on or
off after page. The system accepts the
command with only one of the parameters.
When entering the text, do not type the brace
brackets.
italic text boot system <filename> Italic type indicates variables for which you
supply values in command syntax descriptions.
It also indicates file names, directory names,
document titles, or emphasized text.
screen display Wed May 6 17:01:03
2000
This font indicates system output.
vertical bar | page {on | off} A vertical bar separates the choices when a
parameter is required. The example indicates
you can enter either command:
page on or page off
When entering the parameter, do not type the
vertical bar or the brace brackets.
Compass ID: 389959760 Version 4 xix
Notes, Cautions, Warnings
The following icons and associated text may appear in this document.
Note: A note contains tips, suggestions, and other helpful information, such
as references to material not contained in the document, that can help you
complete a task or understand the subject matter.
Caution: The exclamation point, within an equilateral triangle, is intended to
alert the user to the presence of important installation, servicing, and
operating instructions in the documents accompanying the equipment.
Warning: This symbol indicates that dangerous voltage levels are present
within the equipment. These voltages are not insulated and may be of
sufficient strength to cause serious bodily injury when touched. The symbol
may also appear on schematics.
xx Compass ID: 389959760 Version 4
If You Need Help
Support for your BSR 64000 hardware and software is available via telephone and the
Internet.
Telephone Support
If you need assistance while working with the BSR 64000, contact the Motorola
Technical Response Center (TRC):
The Motorola TRC is on call 24 hours a day, 7 days a week.
When calling for technical support, please have the following information available:
n Your customer information, including location, main contact, and telephone
number
n BSR product and modules
n Detailed description of the issue
n Specific information to assist with resolving the problem, including:
BSR hostname
BSR error messages and logs
Output of BSR show tech command
Cable modem information
n List of troubleshooting steps you have performed before calling the TRC.
n Current state of your BSR 64000 product
n Severity of the issue you are reporting
When calling for repair or Advanced Component Exchange (ACE) replacement,
please provide the following additional information:
n Output of BSR show version command, with part numbers and serial numbers of
BSR components
n Shipping information for the replacement, including contact name, company
name, address, phone number, and email address
U.S. 1-888-944-HELP (1-888-944-4357)
International +215-323-0044
Compass ID: 389959760 Version 4 xxi
Online Support
Motorola BSR Customer Website
The BSR customer website, http://bsr.motorola.com, is available for BSR customers
with active service contracts to access the latest product information, software
updates, troubleshooting information, and technical publications for the BSR 64000,
BSR 2000, and BSR 1000 product line.
You may request access to the site by emailing the BSR product support team at
bsrsupportonline@motorola.com with the following information:
n Company name
n Contact name, phone number, and email address
n Motorola Support contact
n BSR product under service contract
The BSR product support team will email an invitation to you with further
instructions on how to set up an account on the BSR customer information website.
Compass ID: 389959760 Version 4 1-1
1
Introduction
The BSR 64000 system provides for centralized routing and distributed forwarding of
network traffic. Deployed in a distribution hub, the BSR provides an interchange
point between the regional fiber network and the cable plant. In a regional headend, it
interconnects the regional network with a backbone network and allows connectivity
to local content servers and management systems.
This guide describes the various routing options available for configuring the BSR
64000 as a router. The following topics are discussed:
Configuring Policy-based Routing
Configuring IP Multicast Routing
Configuring RIP
Configuring OSPF
Configuring BGP
Configuring VRRP
Configuring MPLS
Configuring Packet Over SONET
Configuring IS-IS
2
Configuring Policy-based
Routing
Overview
This chapter describes how to configure Policy-based Routing on the BSR 64000
using the Command Line Interface (CLI). For a complete description of the CLI
commands discussed in this chapter, refer to the BSR 64000 Command Reference
Guide.
This chapter discusses the following topics:
About Policy-based Routing
Route-maps
Monitoring Routing Policy Information
2-2 Compass ID: 389959760 Version 4
About Policy-based Routing
Policy-based routing routes network traffic by establishing protocol-independent data
paths for forwarding data based on policies defined by a network administrator.
Network administrators use policy-based routing to implement routing policies that
allow or deny data paths based on the identity of a particular system or a particular
application. Policy-based routing also provides a mechanism to mark packets so that
certain kinds of traffic receive differentiated, preferential service.
Policy-based routing is applied to incoming packets. All packets received on an
interface with policy-based routing enabled are considered for policy-based routing
regardless of other routing protocol configurations. The router passes the packets
through a route-map. Based on the information defined in the route-map, packets are
forwarded to the appropriate next hop.
Route-maps
Route-maps establish the conditions for redistributing routes from one routing
protocol to another, and for advertising and learning routes from one router to
another. Route-maps contain a combination of match and set commands. The match
commands define the criteria for whether or not packets meet a particular policy.
They use access lists to configure and control the flow of routing information and
traffic. The set commands define how the packets should be routed if they have met
the match criteria.
This section describes the following:
Access Lists and Groups
Configuring Route-maps
Enabling Policy-based Routing
Enabling Local Policy-based Routing
Note: Policy-based routing is implemented in hardware on the BSR family of
routers. Implementing policy-based routing in hardware instead of software
causes no degradation in device performance.
Release 6.3.1 Configuring Policy-based Routing
Access Lists and Groups
Access lists are used within a route-map match statement. They are used on the BSR
to control entry or exit access to or from the BSR. Access lists can be configured for
all routed network protocols to filter packets as the packets pass through the BSR. The
access list criteria can be defined by the source or the destination address, upper-layer
protocol, or other routing information.
Use the following sections to configure access lists and access groups on the BSR:
Configuring Access Lists
Configuring an IP Access Group
Use the standard access-list command, in Global Configuration mode, to configure an
access list:
MOT:7A(config)#access-list <1-99> <1300-1999> {deny | permit} {<A.B.C.D>
[<A.B.C.D>] | any | host <A.B.C.D>}
where:
1-99 is the standard access list number.
1300-1999 is the expanded range standard access list number.
deny denies access if conditions are matched.
permit permits access if conditions are matched.
A.B.C.D is the source IP address to match.
A.B.C.D is the wildcard bits of the source address.
any specifies any source host.
host A.B.C.D is the single source host IP address.
Example
This configuration example configures Access List 4 by specifying its permit and
deny conditions. Access list 4 prohibits the propagation of networks specified in the
deny statements (10.0.0.0, 162.15.0.0, and 180.10.0.0) and permits all others.
access-list 4 deny 10.0.0.0 0.255.255.255
access-list 4 deny 162.15.0.0 0.0.255.255
access-list 4 deny 180.10.0.0 0.0.255.255
access-list 4 permit any
Configuring an IP Access Group
Use the ip access-group command, in Interface Configuration mode, to configure an
interface to use an access list:
MOT:7A(config-if)#ip access-group <1-199> <1300-2699> {in | out}
where:
1-199 is the standard access list
1300-2699 is the expanded access list
in incoming packet is processed only if the access-list permits the packet.
out outgoing packet is processed only if the access-list permits the packet.
Each route-map consists of a route-map command with associated match statements
that define the conditions that a route must meet and set statements that define the
conditions that apply to a route.
Use the route-map command, in Global Configuration mode, to define a route-map:
MOT:7A(config)#route-map <WORD> [permit | deny] <0-65535>
Note: All lists have an assumed deny all entry as the last statement. If no
matches exist, the route or set is denied.
Note: Use the no ip access-group command to delete an access group on
an interface.
where:
WORD is the name that uniquely identifies a route-map.
permit specifies perform set operations, if the match conditions are met.
deny specifies deny set operations.
0-65535 identifies an instance of the route-map; instances with lower sequence
numbers are parsed first.
Once the route-map is created using the route-map command, you enter Route-map
Configuration mode to define parameters using match and set statements for your
route-map.
Match Statements
Match statements define the conditions that a route must meet. Each route-map
instance may contain multiple match statements. If all match statements in an
route-map instance match for a given route, the route meets the conditions of the
instance. The order of match statements within an instance is not relevant. If an
instance contains no match statements, all routes meet the conditions of the instance,
however, they can be denied by an instance with a lower sequence number.
Use the following match commands, in Route-map Configuration mode, to define the
conditions for a route:
1. match ip address matches the destination IP address that is permitted by one or
more standard or extended access lists:
MOT:7A(config-rmap)#match ip address [<1-199> | <1300-2699>]
where:
1300-2699 is the extended access list number.
2. match ip next-hop matches one or more next-hop IP addresses:
MOT:7A(config-rmap)#match ip next-hop [<1-199> | <1300-2699>]
where:
1300-2699 is the extended access list number.
3. match ip route-source matches source IP addresses specified in an access list:
MOT:7A(config-rmap)#match ip route-source [<1-199> | <1300-2699>]
where:
1300-2699 is the extended access list number.]
Set Statements
Set statements define the routing actions to perform if a route meets the criteria of the
match commands. Some or all set statements are applied, depending on the usage of
the route-map. The order of match statements within an instance is not relevant since
either all or none are applied.
If an instance has no set statements and all the match statements match, nothing is set
for the route. The route is simply redistributed, advertised, or learned as is (depending
on where the route-map is applied).
Use the following set commands, in Route-map Configuration mode, to change
attributes of a route:
1. set interface sets the forwarding interface for a packet:
MOT:7A(config-rmap)#set interface {null0 | pos <X/Y> | tunnel <0-255>}
The set interface null0 command, in Route-map Configuration mode, is used to
force packets to be dropped and not routed with the default destination-based
routing process.
2. set default interface sets the default output interface for a packet. If there is no
explicit route available to the destination address of the packet being considered
for policy routing, then it is sent to the specified default interface:
MOT:7A(config-rmap)#set default interface {null0 | pos <X/Y> | tunnel
<0-255>}
3. Use the set ip next-hop command, in Route-map Configuration mode, to set the
next-hop attribute of a route:
MOT:7A(config-rmap)#set ip next-hop <A.B.C.D>
Note: If no match parameters are specified in the route-map, then all
incoming packets are considered for policy-based routing.
4. Use the set ip next-hop default command, in Route-map Configuration mode, to
set the default next-hop attribute of a route. Routing to the interface or the next
hop specified by this set command occurs only if there is no route for the
destination address of the packet in the routing table. The presence of a default
route in the routing table will ensure that destination-based forwarding will
always be applied and policy will be ignored.
MOT:7A(config-rmap)#set ip next-hop default <A.B.C.D>
Example
The configuration example below creates route-map rmap and access-list 105 to
route tftp packets with source network 15.15.15.0 and destination network 7.7.7.0
to next-hop address 6.6.6.6:
MOT:7A(config)#access-list 1 permit host 225.2.2.2
MOT:7A(config-pim)#pim rp-address 147.106.6.22 1
route-map rmap permit 10
match ip address 105
set ip next-hop 6.6.6.6
access-list 105 permit udp 15.15.15.0 0.0.0.255 7.7.7.0
0.0.0.255 eq tftp
Note: Apply the set commands, described previously, in the following order:
1. set interface
2. set ip next-hop
3. set default interface
4. set ip default next-hop
The first applicable set command will be applied. For example, if the interface
specified by set interface is unreachable, then set ip next-hop will be
applied.
Enabling Policy-based Routing
Use the ip policy route-map command, in Interface Configuration mode, to enable
policy-based routing on an interface and to indicate which route-map the router
should use:
MOT:7A(config-if)# ip policy route-map <WORD>
where:
WORD is the name that identifies a route-map.
All packets arriving on the interface will be subject to policy-based routing. Use the
no ip policy route-map command to disable policy-based routing on the interface.
Example
This example enables the route-map rmap, from the previous example, on a gigaether
interface:
interface gigaether 14/0
ip address 222.1.1.4 255.255.0.0
no shutdown
ip policy route-map rmap
Enabling Local Policy-based Routing
Local policy-based routing is applied to all packets originating from your router. Use
the ip local policy route-map command, in Global Configuration mode, to enable
local policy-based routing on a router and to indicate which route-map the router
should use:
MOT:7A(config)# ip local policy route-map <WORD>
All packets originating on the router will now be subject to local policy-based routing.
Use the no ip local policy route-map command to disable local policy-based routing
on the router. Use the show ip local policy command to display the route-map used
for local policy-based routing, if one exists.
Monitoring Routing Policy Information
Use the following show commands to monitor routing policies:
1. show access-lists displays an access list or all access lists. The resulting display
includes the instances of each access list.
MOT:7A#show access-lists [<1-199> <1300-2699>]
where:
1-199 and 1300-2699 are the access list numbers.
2. show ip as-path-access-list displays the configured AS-path access lists. The
resulting display includes the instances of each AS-path access list.
MOT:7A#show ip as-path-access-list [<1-199>]
where:
1-199 is the access list number.
3. show ip community-list displays the configured community access list.
MOT:7A(config)#show ip community-list [<1-199>]
where:
4. show ip traffic displays policy forwarding and drop counts information.
MOT:7A#show ip traffic
5. show ip route displays the routing table entries.
MOT:7A#show ip route [<A.B.C.D> | bgp | connected | <hostname> | ospf |
rip | static | summary ]
where:
A.B.C.D display routes for this IP address.
bgp display BGP routes.
connected displays connected routes.
hostname display routes for this Internet host name.
ospf displays OSPF routes.
rip displays RIP routes.
static displays static routes.
summary displays a summary of all routes.
6. show ip redistribute displays the routing protocols that are redistributed to other
routing domains:
MOT:7A#show ip redistribute [bgp | ospf | rip]
where:
bgp displays routing domains redistributed into BGP.
ospf displays routing domains redistributed into OSPF.
rip displays routing domains redistributed into RIP.
7. show route-map displays the configured route-maps. The display includes the
instances of each access list.
MOT:7A#show route-map [<WORD>]
where:
WORD is the name of the route-map.
3
Configuring IP Multicast
Routing
Overview
This chapter describes how to configure Multicast Routing on the BSR 64000
system using the Command Line Interface (CLI). For a complete description of the
CLI commands discussed in this chapter, refer to the BSR 64000 Command Reference
Guide.
About Multicast Routing
Enabling IP Multicast Routing on the BSR
Hardware Assisted Multicast
Configuring PIM
Configuring DVMRP
Configuring IGMP on an Interface
Managing IP Multicast Routing on the BSR
Gathering IP Multicast Information
About Multicast Routing
The IP multicast routing environment allows a host to send a packet to multiple hosts
within a group. Multicast packets delivered to group members are identified by a
single multicast group address.
Hosts can be both senders and receivers. Any host, regardless of whether it is a
member of a group, can send to a group. However, only the members of a group
receive the message. A multicast address is chosen for the receivers in a multicast
group. Senders use that address as the destination address of a datagram to reach all
members of the group.
Multicast group membership is active; hosts can join and leave at any time. There is
no restriction on the location or number of members in a multicast group. A host can
be a member of more than one multicast group at a time.
How active a multicast group is and what members it has can vary from group to
group and from time to time. A multicast group can be active for long or brief time
periods. Group membership can change constantly and have inactive members.
To forward multicast packets between routers, multicast routing protocols, such as
Protocol-Independent Multicast (PIM) and Distance Vector Multicast Routing
Protocol (DVMRP) are used to maintain forwarding tables. The BSR automatically
enables the Internet Group Management Protocol (IGMP) on PIM and DVMRP
interfaces to learn whether members of a group are present on their directly attached
networks. Source hosts join multicast groups by sending IGMP report messages.
Use the following sections to enable IP multicast routing, enable and configure PIM
and DVMRP, configure IGMP, and display multicast routing information on the
BSR:
Enabling IP Multicast Routing on the BSR
IP multicast routing allows the BSR to forward IP multicast packets over the network.
Use the ip multicast-routing command, in Global Configuration mode, to enable IP
multicast routing on the BSR:
MOT:7A(config)#ip multicast-routing
Release 6.3.1 Configuring IP Multicast Routing
Hardware Assisted Multicast
The hardware-assisted multicast feature is an enhancement to the current architecture
where multicast flows will now be forwarded in the fast path. Previous
implementations only handled Multicast traffic in the SRM (slow path).
Which flow is forwarded in the fast path depends on the user configuration. A flow or
a range of flows can be configured with an extended access list (eACL). If no eACL
configured flows are present, all flows will be forwarded through the slow path in
SRM. When the traffic for these eACL configured flows is active, they will be
forwarded in the fast path. Only the maximum allowed 512 path entries can be
forwarded even though there might be more active flows configured. When an active
flow is deleted, either due to a timeout or forced removal, the next active eACL
configured flow, if any, will be forwarded in the fast path.
Specifying Fastpath Multicast Flow Priority
The ip multicast fastpath command is used to specify which multicast flow or flows
will be given preferential treatment for forwarding in the fast path. Use the ip
multicast fastpath command, in Global Configuration mode, to specify which
multicast flow or flows will be given preferential treatment for programming in the
fast path. as follows:
MOT:7A(config)# ip multicast fastpath {<100-199> | <2000-2699>} [ queue
<0-7>]
where:
100-199 is the multicast acceleration eligibility list.
2000-2699 is the extended ACL range.
queue 0-7 is the HSIM transmit queue number.
Displaying Hardware Assisted Multicast Information
Use the show ip multicast fastpath command to display multicast entries in the fast
path
MOT:7A# show ip multicast fastpath
Refer to the BSR 64000 Command Reference Guide to see typical screen output for
the show ip multicast fastpath command.
Use the show ip multicast fwd-cache command to display the multicast forwarding
cache on a source group basis.
MOT:7A# show ip multicast fwd-cache [<A.B.C.D> [<A.B.C.D>]] | <A.B.C.D> |
physical ]
where:
A.B.C.D only displays the cache for this source or group address.
A.B.C.D only displays the cache for this specified source and group.
physical displays the cache only in relation to the physical interface. If physical
is not specified, the command output relates to the logical interface.
Refer to the BSR 64000 Command Reference Guide command description to see
typical screen output for the show ip multicast fwd-cache command.
Configuring PIM
Use the following sections to configure PIM on the BSR:
About PIM
Enabling PIM
Configuring PIM Rendezvous Points
Configuring PIM Designated Routers
Configuring Bootstrap Routers
Defining the PIM Domain Border
Accepting Select Join and Prune Messages
Delaying Shortest Path Tree Usage for Better Throughput
Configuring the Type of PIM Packet Checksum
Retrieving PIM Unicast Routes
Configuring PIM-SSM
About PIM
Protocol-Independent Multicast (PIM) is used to efficiently route multicast traffic to
multicast groups that span wide-area and inter-domain networks. PIM is IP routing
protocol independent because it can use any unicast routing information to forward
multicast traffic. It uses the unicast routing table to perform Reverse Path Forwarding
(RPF), instead of creating an independent multicast routing table. However, unlike
most unicast routing protocols, PIM does not send and receive multicast routing
updates between routers.
The BSR supports PIM in Sparse Mode Version 2 (PIM SM V2) with the PIM
Source-specific Multicast (PIM SSM) extension. Sparse mode routing protocols use
shared trees for the distribution of message packets. Sparse mode routers must join
and leave multicast groups explicitly. Upstream routers do not forward multicast
traffic out a PIM interface unless the router has sent an explicit request, called a Join
message, to receive multicast traffic from a downstream router or if group members
are directly connected to the interface. When a host joins a multicast group, its first
hop router sends a Join message upstream to a directly connected router, the
Designated Router (DR). The DR encapsulates the message and unicasts it to an
assigned Rendezvous Point (RP) for the group. The RP serves as the root of the shared
tree and is responsible for forwarding multicast data from different sources toward the
receivers.
Shared trees minimize traffic on the PIM network, however the routes on a shared tree
may be longer than routes on a source tree, or shortest path tree (SPT). To improve
network efficiency, the DRs on the network can be configured to determine when the
source hosts switch from shared tree to SPT for transmitting multicast packets. PIM
sparse-mode routers send Join messages toward the source when joining the SPT and
send Prune messages to the RP when they move from the shared tree onto the SPT.
PIM-SSM is backward compatible with PIM-SM, unless a router is a last hop router.
Therefore, routers that are not last hop routers can run PIM-SM for SSM groups if
they do not yet support SSM, since it already handles the processing of IP unicast
source address and multicast group address channels.
Enabling PIM
Follow these steps to configure general PIM parameters:
1. Use the router pim command, in Global Configuration mode, to enter Router
Configuration mode:
MOT:7A(config)#router pim
2. Use the network command, in Router Configuration mode, to specify the
network IP address and subnet mask for the PIM network:
MOT:7A(config-pim)#network <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the IP address of the PIM network.
A.B.C.D is the wildcard mask for the PIM network.
Configuring PIM Rendezvous Points
Use the following sections to configure Rendezvous Point parameters:
Configuring a Static PIM Rendezvous Point
Configuring Candidate RPs
Configuring a Static PIM Rendezvous Point
If a static PIM Rendezvous Point (RP) is used for a particular multicast group, the RP
IP address must be configured on all routers in the PIM domain. First-hop routers
send registration packets to the RP IP address on behalf of source multicast hosts.
PIM routers also use this IP address on behalf of multicast hosts that want to become
members of a multicast group. These routers send Join and Prune messages to the RP.
The RP must be a PIM router; however, it does not require any special configuration
to recognize that it is the RP. Also, RPs are not members of the multicast group;
rather, they serve as a "meeting place" for multicast sources and group members.
A single RP can be configured for more than one group. The conditions specified by
access lists determine which PIM multicast groups use the RP. A statically configured
RP takes precedence over any dynamically learned RP.
At least one RP needs to be configured in a PIM domain. Follow these steps to
configure a static PIM RP:
Configuration mode:
2. Use the pim rp-address command, in Router Configuration mode, to specify the
static PIM RP IP address for a particular multicast group:
MOT:7A(config-pim)#pim rp-address <A.B.C.D> [<1-99>]
where:
A.B.C.D is the IP address of a PIM RP.
1-99 is a standard access list number that defines the multicast group for the
RP. If no number is entered, the multicast group defaults to the entire Class D
IP address group range.
The following example sets the PIM RP address to 200.63.25.35 for all multicast
groups:
MOT:7A(config-pim)#pim rp-address 200.63.25.35
The following example sets the PIM RP address to 147.106.6.22 for the multicast
group 225.2.2.2:
MOT:7A(config-pim)#pim rp-address 147.106.6.22 1
Configuring Candidate RPs
One or more rendezvous points (RPs) can be configured to serve as candidates in a
PIM domain to avoid a single point of failure. Candidate RPs should be configured on
the backbone portion of the network to help improve the efficiency of the multicast
network.
Candidate RPs send candidate RP advertisements to the Bootstrap Router (BSR) and
the Bootstrap Router then distributes all RP information to the PIM domain. Each
router determines which RP has the highest priority and which RP to use for a
multicast group range. An RP can serve the entire IP multicast address space or a
portion of it.
Select from the following options, in Interface Configuration mode, to configure one
or more candidate RPs in the PIM domain:
If you want to advertise the router as an RP candidate covering all groups on the
PIM domain, use the ip pim rp-candidate command:
MOT:7A(config-if)#ip pim rp-candidate
Use the ip pim rp-candidate group-list command to configure a specific group
range for the RP candidate:
Note: If you are configuring routers from other vendors as candidate RPs,
ensure that they support PIM Version 2.
MOT:7A(config-if)#ip pim rp-candidate group-list <1-99>
where:
1-99 is the access list reference number for group prefixes.
The default interval for an RP candidate advertisement is 60 seconds. To change
the RP candidate advertisement interval, use the ip pim rp-candidate interval
command:
MOT:7A(config-if)#ip pim rp-candidate interval <1-200>
where:
1-200 is the interval in seconds.
To advertise the IP address of the candidate RP, use the ip pim rp-candidate
ip-address command:
MOT:7A(config-if)#ip pim rp-candidate ip-address <A.B.C.D>
where:
A.B.C.D is an IP address of the candidate RP.
The RP candidate priority is 0 by default. If you want to change the candidate RP
priority for the router, use the ip pim rp-candidate priority command:
MOT:7A(config-if)#ip pim rp-candidate priority <0-255>
where:
0-255 is the assigned priority of the candidate RP.
Configuring PIM Designated Routers
Use the following sections to configure Designated Router parameters:
Setting the Designated Router Priority
Modifying the PIM Router-Query Message Interval
The router with the highest priority is elected as the Designated Router (DR) in
the PIM network. The DR priority is configured on the routers interface. If a DR
priority is assigned on multiple router interfaces, then the interface with the
highest IP address is used as the DR.
If a router does not advertise its priority in "hello" messages, then that router is
elected as the DR. If multiple routers have the same highest priority status, then
the router with the highest IP address configured on an interface is elected to be
the DR.
The default DR priority for the BSR is 1. Use the ip pim dr-priority command,
in Interface Configuration mode, to change the priority for determining which
router is elected as the DR:
MOT:7A(config-if)#ip pim dr-priority <1-255>
where:
1-255 is the priority of the router to be considered for the DR.
Modifying the PIM Router-Query Message Interval
Router-query messages ("hello" messages) are used to elect a PIM Designated Router
(DR). The DR is responsible for sending PIM join and PIM register packets to the RP.
By default, multicast PIM routers send router-query messages every 30 seconds. Use
the ip pim query-interval command, in Interface Configuration mode, to modify the
router-query message interval:
MOT:7A(config-if)#ip pim query-interval <0-65535>
where:
0-65535 is the router-query message interval, in seconds.
Configuring Bootstrap Routers
One or more Bootstrap Routers (BSRs) can be configured to serve as candidates in a
PIM domain to avoid a single point of failure. Candidate Bootstrap Routers should be
configured on the backbone portion of the network to help improve the efficiency of
the multicast network.
A Bootstrap Router is elected among the candidate Bootstrap Routers automatically
by using bootstrap messages to determine which Bootstrap Router has the highest
priority. This router then announces to all PIM routers in the PIM domain that it is the
Bootstrap Router.
Select from the following options to configure candidate Bootstrap Routers:
If you want to configure the router to be a candidate Bootstrap Router with the
default hash mask length of 30 bits for an RP selection, use the ip pim
bsr-candidate command in Interface Configuration mode:
MOT:7A(config-if)#ip pim bsr-candidate
When the default hash mask is used for the candidate Bootstrap Router, the router
takes the first rendezvous point (RP) address from the local RP-mapping cache.
If you want to configure the router to be a candidate Bootstrap Router and adjust
the hash mask length in order to avoid having two RPs for the same multicast
group, use the ip pim bsr-candidate command in Interface Configuration mode:
MOT:7A(config-if)#ip pim bsr-candidate <0-32>
where:
0-32 is the hash mask length in bits.:
If you want to configure another interface on the router to be a candidate
Bootstrap Router, use the ip pim bsr-candidate ip-address command in
Interface Configuration mode:
MOT:7A(config-if)#ip pim bsr-candidate ip-address <A.B.C.D>
where:
A.B.C.D is the IP address of another interface on the router that is designated
as a Bootstrap Router candidate.
If you want to configure another interface on the router to be a candidate
Bootstrap Router and adjust the hash mask length value in order to avoid having
two RPs for the same multicast group, use the ip pim bsr-candidate ip-address
command in Interface Configuration mode:
MOT:7A(config-if)#ip pim bsr-candidate ip-address <A.B.C.D> <0-32>
where:
A.B.C.D is the IP address of another interface on the router that is designated
as a Bootstrap Router candidate.
Note: It is recommended (but not required) that the hash mask length be the
same across all candidate Bootstrap Routers.
0-32 is the hash mask length in bits.
Defining the PIM Domain Border
A border can be configured to define the boundary of a PIM domain, so that bootstrap
messages do not cross the border in either direction. Creating a border allows different
Bootstrap Routers (BSRs) to be elected on both sides of the PIM border.
Use the ip pim border command, in Interface Configuration mode, to configure a
PIM domain boundary on the interface of a border router that peers with one or more
neighbors outside the PIM domain:
MOT:7A(config-if)#ip pim border
Accepting Select Join and Prune Messages
All Join and Prune messages are processed by default when PIM is enabled on a
router. The PIM router can be configured to only accept Join and Prune messages
destined for a specified PIM RP and multicast group, which is specified by an access
list. If no access list is provided, it defaults to all class D multicast group addresses.
If the PIM RP IP address belongs to the local router, the router is the PIM RP only for
the specified multicast group range specified by the access list. If the multicast group
IP address is not in the specified multicast group range specified by the access list, the
PIM RP does not accept Join or Register messages and responds immediately to
Register-Stop registration messages.
Follow these steps to configure the PIM router to accept specific Join and Prune
messages:
Configuration mode:
2. Use the pim accept-rp command, in Router Configuration mode, to configure
the router to accept Join or Prune messages destined for the specified RP and for
the specific list of multicast groups:
MOT:7A(config-pim)#pim accept-rp <A.B.C.D> [<1-99>]
where:
A.B.C.D is the RP IP address of the RP allowed to send Join messages to
groups in the range specified by the group access list.
1-99 is a standard IP access list number that defines the multicast group for
the RP. If no number is entered, the multicast group defaults to the entire
Class D IP address group range.
Example
The following example configures the router to accept Join or Prune messages
destined for the RP IP address 100.1.1.1 for the multicast group 224.2.2.2:
MOT:7A(config-pim)#pim accept-rp 100.1.1.1 3
MOT:7A(config-pim)#end
Delaying Shortest Path Tree Usage for Better Throughput
PIM routers use a shared distribution tree to control the path of IP multicast traffic. In
order to enhance throughput on your multicast network, you can control the threshold
when the PIM rendezvous point (RP) switches to the Shortest Path Tree (SPT)
distribution tree. SPT creates the optimal path between source and receiver hosts. If
the RP sends multicast traffic at a rate greater than or equal to the specified kbps rate,
the router or RP router triggers a PIM Join message to the PIM source router to
construct an SPT.
To specify the multicast traffic threshold that must be reached on the RP router
before the multicast traffic is switched over to the SPT, use the ip pim
spt-threshold rp command in Global Configuration mode:
MOT:7A(config)#ip pim spt-threshold rp <0-4294967294> [infinity]
where:
0-4294967294 is the multicast traffic rate in kilobytes per second (kbps).
infinity indicates that the RP always uses shared tree distribution and never
switches to SPT.
To specify the multicast traffic threshold that must be reached on the last-hop
router before multicast traffic is switched over to the SPT, use the ip pim
spt-threshold lasthop command in Global Configuration mode:
Note: The default setting for the ip pim spt-threshold rp command is 0
kbps, which allows the RP to join the SPT immediately.
MOT:7A(config)#ip pim spt-threshold lasthop <0-4294967294> [infinity]
where:
0-4294967294 is the multicast traffic rate in kilobytes per second (kbps).
infinity indicates that the last-hop router always uses shared tree distribution;
never switch to SPT.
Configuring the Type of PIM Packet Checksum
The default checksum type that a PIM packet uses to calculate a checksum is the
complete IP packet length. Use the pim register-checksum command, in Router
Configuration mode, to change the checksum type:
MOT:7A(config-pim)#pim register-checksum [ new | old ]
where:
new use only the IP and PIM Control Headers.
old use the complete IP packet length.
Retrieving PIM Unicast Routes
Use the pim unicast-route-lookup command, in Router Configuration mode, to
retrieve PIM unicast routes from the BSRs unicast routing table:
MOT:7A(config-pim)#pim unicast-route-lookup
Note: The default setting for the ip pim spt-threshold lasthop command is
1024 kbps, which allows the last-hop router to join the SPT when the 1024
Kbps threshold is reached.
Configuring PIM-SSM
PIM-SSM supports one-to-many IP multicast solutions, such as targeted audio and
video broadcasting or television channel distribution. PIM-SSM is used in
conjunction with DOCSIS Digital Set-top Gateway (DSG) protocol and IGMP V3.
Configuring PIM-SSM IP Address Range
PIM-SSM operation uses information found on a source IP address, relayed to the last
hop router by IGMP, for a multicast group provided by a receiver and performs source
filtering on the multicast traffic. An SSM receiver must be able to subscribe or
unsubscribe to a IP unicast source address and the multicast group address channel to
either receive or not receive traffic from a specific source.
Follow these steps to configure the PIM-SSM IP address range so that only Source
Specific Join Message within this specified range can be generated by a single
subscriber that wants to do multicast:
1. Use the router pim command in Global Configuration mode to enter Router
Configuration mode for the PIM routing process.
2. Use the ip pim ssm command in Router Configuration mode to select the SSM
range so that IP unicast source address and the multicast group address channel
subscriptions from IGMP are ignored for groups outside the selected range.
MOT:7A(router-pim)#ip pim ssm [default | range {<1-99> |
<1300-1999>}]
where:
default selects the default address range 232.0.0.0 through 232.255.255.255
(232/8) for SSM applications and protocols.
range selects a range that uses a standard or extended access-list number.
Note: Refer to the Configuring DSG chapter in the BSR 64000 CMTS
Configuration and Management Guide for more information on DSG.
Once the SSM range is defined, existing IP multicast receiver applications will not
receive any traffic when they try to use addresses in the SSM range (unless the
application is modified to use an explicit IP unicast source address and the multicast
group address channel subscription).
Configuring IGMP V3 Static Group for PIM-SSM
IGMP V3 is used on routers and hosts that receive IP multicasts. An IGMP Version 3
static group must be configured so that PIM-SSM routing can send an IP unicast
source address and the multicast group address Join message to an upstream PIM
neighbor. For more information on IGMP, refer to Configuring IGMP on an Interface.
Follow these steps to configure an IGMP V3 static group for PIM-SSM:
1. Use the interface command in Global Configuration mode to select any
administratively enabled interface (including a bundled CMTS slave interface).
MOT:7A(config)#interface {cable <X/Y> | ethernet <X/Y> | gigaether <X/Y>
| loopback <1-255> | pos <X/Y> | tunnel <0-255>}
where:
cable X/Y is the slot and MAC Domain number of the CMTS module.
ethernet X/Y is the Ethernet module number and 10/100 Mbps port number.
gigaether is the Gigabit Ethernet module number and 1000 Mbps optical port
number.
pos X/Y is the Packet-Over-SONET module number and optical port number.
loopback <1-255> is the loopback interface.
tunnel <0-255> is the tunnel interface.
2. Use the ip igmp static-group command in Interface Configuration mode to allow
an IP unicast source address and the multicast group address channel to join an
upstream PIM neighbor.
MOT:7A(config-if)#ip igmp static-group <A.B.C.D> [source <A.B.C.D>]
where:
A.B.C.D is the multicast group IP address for which the router is configured
to be a member. This is a Class D IP address range (224.0.0.0 through
232.255.255.255).
A.B.C.D is the unicast source IP address.
3. Use the show ip igmp interface group command to display the multicast groups
that have been requested on each interface.
MOT:7A(config-if)#show ip igmp interface group
Configuring DVMRP
Use the following sections to configure the Distance Vector Multicast Routing
Protocol (DVMRP) on the BSR:
About DVMRP
Enabling DVMRP on the Router
Configuring the DVMRP Route Expiration Threshold
Configuring the DVMRP Route Reporting Threshold
Setting the DVMRP Prune Lifetime Value
About DVMRP
The Distance Vector Multicast Routing Protocol (DVMRP) delivers connectionless
data to a group of hosts across a network. DVMRP is designed to be used as an
interior gateway protocol (IGP) within a multicast domain.
Note: Packet forwarding of this IP unicast source address and the multicast
group address channel will only be sent onto physical interfaces that have
this static IP unicast source address and the multicast group address channel
Join message.
DVMRP is often referred to as a flood and prune protocol. DVMRP dynamically
creates IP multicast delivery trees by using Reverse Path Forwarding (RPF) to
forward multicast traffic away from the source to downstream interfaces. RPF uses
the DVMRP routing table to determine the upstream and downstream neighbors. A
source host sends traffic to a group of hosts that are represented by a multicast group
address. The multicast router must determine which direction is upstream (towards
the source) and which directions are downstream. If there are multiple downstream
paths, the router replicates the packet and forwards it to the appropriate downstream
paths (which may not be all paths). The router forwards a multicast packet once it is
received on the upstream interface.These methods allow the formation of
shortest-path trees, which are used to reach all group members from each network
source of multicast traffic.
DVMRP routers dynamically discover their neighbors by sending neighbor probe
messages periodically to an IP multicast group address that is reserved for all
DVMRP routers.
In a DVMRP network, routers advertise its routing table to neighbors in a DVMRP
report message. The receiving DVMRP router picks the neighbor advertising the
lowest cost and adds that entry to its routing table for future advertising. Hop count is
the cost metric for DVMRP.
Enabling DVMRP on the Router
Follow these steps to enable DVMRP:
1. Use the router dvmrp command, in Global Configuration mode, to enable
DVMRP and enter Router Configuration mode:
MOT:7A(config)#router dvmrp
2. Use the network command, in Router Configuration mode, to define the network
IP address and subnet mask for the DVMRP network:
MOT:7A(config-dvmrp)#network <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the IP address of the DVMRP network.
A.B.C.D is the wild-card mask for the DVMRP network.
Configuring the DVMRP Route Expiration Threshold
Use the route expire-interval command, in Router Configuration mode, to set the
DVMRP route expiration interval:
MOT(config-dvmrp)#route expire-interval <5-3600>
where:
5-3600 is the route expiration interval in seconds.
Configuring the DVMRP Route Reporting Threshold
Use the route report-interval command, in Router Configuration mode, to set how
often DVMRP routes are reported:
MOT:7A(config-dvmrp)#route report-interval <5-3600>
where:
5-3600 is the route reporting interval in seconds.
Setting the DVMRP Prune Lifetime Value
DVMRP uses a basic multicast model to build a parent-child database. This database
is used to create a forwarding tree that originates at the source where multicast
packets are generated. Multicast packets are initially flooded down the forwarding
tree making parent-child links. If there are redundant paths (parent-child links) on the
forwarding tree, packets are not forwarded along those paths. Forwarding occurs until
prune messages are received on the forwarding tree, which further holds back
multicast packet broadcasts. Pruning is initiated from the leaf router, where there are
no multicast members.
The prune lifetime is the amount of time a prune state is maintained on a router before
it times out. Use the prune lifetime command, in Router Configuration mode, to set
the lifetime value for DVMRP prune messages that are received on parent-child links
to improve throughput:
MOT:7A(config-dvmrp)#prune lifetime <5-7200>
where:
5-7200 is the prune lifetime value in seconds.
Configuring DVMRP on a Routing Interface
Use the following sections to configure DVMRP on a BSR routing interface:
Filtering Incoming DVMRP Reports
Filtering Outgoing DVMRP Routing Reports
Distributing the Default DVMRP Network to Neighbors
Adding a Metric Offset to the DVMRP Route
Setting the DVMRP Neighbor Time-out Interval
Delaying DVRMP Reports
Setting the DVMRP Probe Interval
Rejecting a DVMRP Non-pruning Neighbor
Configuring a DVMRP Summary Address
Filtering Incoming DVMRP Reports
Use the ip dvmrp accept-filter command, in Interface Configuration mode, to filter
incoming routes:
MOT:7A(config-if)#ip dvmrp accept-filter <1-99>
where:
1-99 is the access list for filtering routes.
Filtering Outgoing DVMRP Routing Reports
Use the ip dvmrp out-report-filter command, in Interface Configuration mode, to
stop advertising a route, by filtering the outgoing DVMRP report:
MOT:7A(config-if)#ip dvmrp out-report-filter <1-99>
where:
1-99 is the access list for filtering outgoing routes.
Distributing the Default DVMRP Network to Neighbors
The default DVMRP network is 0.0.0.0. Use the following options to advertise the
default DVMRP network to neighboring routers and the multicast backbone (MBone)
or to neighboring routers only for a DVMRP Version 3.6 device:
If you want the default DVMRP route distributed to the MBone and neighboring
routers, use the ip dvmrp default-information originate command in Interface
Configuration mode:
MOT:7A(config-if)#ip dvmrp default-information originate
If you want the default DVMRP route distributed to the neighbor only, use the ip
dvmrp default-information originate only command in Interface Configuration
mode:
MOT:7A(config-if)#ip dvmrp default-information originate only
Adding a Metric Offset to the DVMRP Route
The DVMRP metric is the hop count. The DVMRP route metric can be changed using
the ip dvmrp metric-offset command. The metric is the increment or hop count used
to measure the span between the router originating the report and the source network.
The source network becomes unreachable when it reaches a metric of 32. It is also
associated with the unicast route being reported for each source network that is
reported.
Use the following options to add a metric offset to both incoming and outgoing
routing reports:
Use the ip dvmrp metric-offset in command, in Interface Configuration mode,
to add an increment to the incoming DVMRP reports:
MOT:7A(config-if)#ip dvmrp metric-offset in <0-31>
where:
0-31 is the increment number; default is 1.
Use the ip dvmrp metric-offset out command, in Interface Configuration mode,
to add an increment to outgoing DVMRP reports:
MOT:7A(config-if)#ip dvmrp metric-offset out <0-31>
where:
0-31 is the increment number; default is 0.
Setting the DVMRP Neighbor Time-out Interval
The DVMRP neighbor time-out interval is the amount of time allowed before a
neighbor is removed from the DVMRP neighbor table, if the neighbor does not send a
probe (query) or report.
Use the ip dvmrp neighbor-timeout command, in Interface Configuration mode, to
set the DVMRP neighbor time-out interval:
MOT:7A(config-if)#ip dvmrp neighbor-timeout <5-3600>
where:
5-3600 is the time interval in seconds.
Delaying DVRMP Reports
The inter-packet delay of a DVMRP report is the time that elapses between
transmissions of sets of packets that constitute a report. The number of packets in the
set is determined by the burst value, which defaults to 2 packets.
Use the ip dvmrp output-report-delay command, in Interface Configuration
mode, to configure the delay between each DVMRP route report burst:
MOT:7A(config-if)#ip dvmrp output-report-delay <1-10>
where:
1-10 is the amount of delay in seconds.
Use the ip dvmrp output-report-delay command, in Interface Configuration
mode, to configure the delay between each DVMRP route report burst and the
number of packets contained in each burst:
MOT:7A(config-if)#ip dvmrp output-report-delay <1-10> [<1-100>]
where:
1-10 is the amount of delay in seconds.
1-100 is the number of packets in a set.
Setting the DVMRP Probe Interval
The DVMRP probe interval indicates how often queries are sent to neighboring
DVMRP routers. Use the ip dvmrp probe-interval command, in Interface
Configuration mode, to set the DVMRP probe interval:
MOT:7A(config-if)#ip dvmrp probe-interval <5-3600>
where:
5-3600 is the probe interval, in seconds.
Rejecting a DVMRP Non-pruning Neighbor
The BSR accepts all DVMRP neighbors as peers by default. Routers that have old
versions of DVMRP, that cannot prune or graft, waste bandwidth by forwarding
packets unnecessarily.
If there is a non-pruning version of DVMRP running on a neighbor, use the ip dvmrp
reject-non-pruners command, in Interface Configuration mode, to prevent this
DVMRP router from peering with the neighbor:
MOT:7A(config-if)#ip dvmrp reject-non-pruners
Configuring a DVMRP Summary Address
Use the ip dvmrp summary-address command, in Interface Configuration mode, to
create a summary address for a group of DVMRP routes:
MOT:7A(config-if)#ip dvmrp summary-address <A.B.C.D> <A.B.C.D>
[metric <1-31>]
where:
A.B.C.D is the DVMRP IP summary address.
A.B.C.D is the DVMRP subnetwork mask.
1-31 is the metric value advertised with the summary address.
Note: The ip dvmrp reject-non-pruners command prevents peering with
neighbors only. If there are any non-pruning routers multiple hops away
(downstream toward potential receivers) that are not rejected, then a
non-pruning DVMRP network may still exist.
Note: One or more specific routes must exist in the unicast routing table
before a summary address is advertised.
Configuring IGMP on an Interface
Use the following sections to configure the Internet Group Management Protocol
(IGMP) on an interface:
About IGMP
Enabling IGMP
Controlling Access to IP Multicast Groups
Changing the IGMP Version
Modifying the IGMP Host-Query Message Interval
Specifying the IGMP Querier Time-out Interval
Changing the Maximum Query Response Time
Configuring the BSR as a Static Multicast Group Member
About IGMP
IGMP is an integral part of IP and must be enabled on all routers and hosts that want
to receive IP multicasts. The BSR automatically enables IGMP on
Protocol-Independent Multicast (PIM) and Distance Vector Multicast Routing
Protocol (DVMRP) enabled interfaces.
IGMP manages the membership of hosts and routers in multicast groups. IP hosts use
IGMP to report their multicast group memberships to any immediately neighboring
multicast routers. Multicast routers use IGMP to learn, for each of their attached
physical networks, which groups have members.
For each attached network, a multicast router can be either a querier or a non-querier.
The querier router periodically sends general query messages to solicit group
membership information. Hosts on the network that are members of a multicast group
send report messages. When a host leaves a group, it sends a leave group message.
IP hosts use IGMP to report their group membership to directly connected multicast
routers. IGMP uses class D IP addresses for its group addresses that range from
225.0.0.0 to 239.255.255.255.
The following multicast addressing rules apply to IGMP:
The 224.0.0.0 IP address is guaranteed not to be assigned to any group.
The address 224.0.0.1 is assigned to all systems on a subnetwork.
The address 224.0.0.2 is assigned to all routers on a subnetwork.
IGMP Version 3
IGMP allows multicast routers to learn, from each of there directly attached networks,
which multicast addresses are of interest to the neighboring systems. IGMPv3 adds
the capability for a multicast router to also learn which sources are of interest to
neighboring systems. IGMPv3 provides support for source filtering which gives the
protocol the ability to specify multicast traffic from a specific traffic source. This is
attractive to cable operators for broadcast-type IP multicast application as it offers
additional security due to the single source nature of SSM.
Enabling IGMP
By default, IGMP is enabled on all interfaces on which DVMRP or PIM is
configured.
Controlling Access to IP Multicast Groups
The BSR learns about multicast group members that are connected to local networks
by sending IGMP host-query messages. IP multicast group access is determined by
associating the IGMP access group to an access list. Refer to Chapter 2 for more
information on configuring access lists.
Follow these steps to configure access for IP multicast groups:
1. Use the interface command, in Global Configuration mode, to enter the IGMP
interface:
MOT:7A(config-if)#interface {cable | ethernet | gigaether | pos} <X/Y>
where:
cable is the cable interface.
ethernet is the Ethernet interface.
gigaether is the 1000 Mbps optical Ethernet interface.
pos is the Packet over SONET interface.
Note: IGMP recognizes the physical interfaces on which an IGMP query
message has been received or which have been statically configured. When
a multicast packet is forwarded, the packet will skip any physical interface
that has no IGMP association with the corresponding multicast group.
X is the module slot number.
Y is the port number.
2. Use the ip igmp access-group command, in Interface Configuration mode, to
control the multicast groups that hosts are allowed to join:
MOT:7A(config-if)#ip igmp access-group <1-99>
where:
1-99 is the access list-number.
Changing the IGMP Version
The BSR supports IGMP Versions 1, 2, and 3. By default, the BSR enables IGMP
Version 2 which supports the IGMP query time-out and the maximum query response
time features. To change the version of IGMP on the BSR, use the ip igmp version
command. All hosts connected to an interface must support the same version of
IGMP. For example, if hosts connected to a particular interface only support IGMP
Version 1, IGMP Version 1 must be selected for the interface.
Use the ip igmp version 1 command, in Interface Configuration mode, to change the
version of IGMP on the BSR to IGMP Version 1:
MOT:7A(config-if)#ip igmp version 1
If you need to return to IGMP Version 2, use the ip igmp version 2 command, in
IGMP Version 3 is used to configure a static multicast group so that hosts can signal
their membership with a last hop PIM-SSM enabled router. Use the ip igmp version 3
command, in Interface Configuration mode, to change the version of IGMP on the
BSR to IGMP Version 3:
Modifying the IGMP Host-Query Message Interval
When the BSR is configured for multicast routing, it periodically sends IGMP
host-query messages to connected networks in order to refresh multicast group
member information or discover new multicast group members. These messages are
sent to the all-systems group address of 224.0.0.1 with a time-to-live (TTL) of 1.
The BSR uses the highest IP address for its multicast network and is responsible for
sending IGMP host-query messages to all hosts on the subnetwork. By default, the
BSR sends IGMP host-query messages every 125 seconds to keep the IGMP
overhead low on hosts and networks connected to the BSR.
Use the ip igmp query-interval command, in Interface Configuration mode, to
change the IGMP host-query message interval:
MOT:7A(config-if)#ip igmp query-interval <1-3600>
where:
1-3600 is the time interval, in seconds, that the BSR sends IGMP host-query
messages to connected networks.
Specifying the IGMP Querier Time-out Interval
IGMP Version 2 allows a time interval to be specified for when the BSR becomes the
querier for the attached network. After the timeout interval during which no queries
have been received from a previous querier, the BSR then becomes the querier for the
interface.
Use the ip igmp querier-timeout command, in Interface Configuration mode, to
specify the IGMP querier timeout interval:
MOT:7A(config-if)#ip igmp querier-timeout <60-3600>
where:
60-3600 is the time interval in seconds.
Note: The time interval should be twice the number of seconds as the IGMP
query interval.
Changing the Maximum Query Response Time
IGMP Version 2 allows the maximum query response time advertised in IGMP
queries to be changed. The maximum query response time allows a router to quickly
detect changes in group members on an attached network. Decreasing the value
allows the BSR to add and remove groups more quickly.
The query response interval is the maximum amount of time that can elapse between
when the querier router sends a host-query message and when it receives a response
from a host.
Use the ip igmp query-max-response-time command to change the query response
interval specified in IGMP messages. By default, the query response time is 10
seconds.
MOT:7A(config-if)#ip igmp query-max-response-time <1-255>
where:
1-255 is the query response time in seconds.
Configuring the BSR as a Static Multicast Group Member
An interface is configured with a static multicast group for the following reasons:
Performance increases by allowing the BSR to forward multicast packets over the
interface to directly connected networks without processing the multicast packets.
A multicast group member is not associated with a specific network.
A host cannot report its multicast group membership using IGMP.
Use the ip igmp static-group command, in Interface Configuration mode, to
configure the BSR to become a statically connected multicast group member:
MOT:7A(config-if)#ip igmp static-group <A.B.C.D> [source <A.B.C.D>]
where:
A.B.C.D is the multicast group IP address for which the router is configured to be
a member. This is a Class D IP address range (224.0.0.0 through
232.255.255.255).
A.B.C.D is the unicast source IP address.
Managing IP Multicast Routing on the BSR
The following sections are used to manage multicast routing on the BSR:
Configuring an IP Multicast Static Route
Changing the Distance for a Unicast Multicast Route
Changing the Distance for a Static Multicast Route
Clearing IP Multicast Information
Configuring an IP Multicast Static Route
IP multicast static routes (mroutes) enable unicast and multicast packets to take
different paths over combined multicast and unicast network topologies. mroutes
allow multicast packets to travel from the router that is configured with the static
multicast route to the next multicast router, even if there are one or more unicast
routers in the path. Routers with multicast static routes use the IP static multicast route
configuration instead of the unicast routing table to determine the path. No
information about this IP multicast static route is advertised or redistributed to any
other router on the network.
Use the ip mroute command, in Global Configuration mode, to configure a multicast
static route:
MOT:7A(config)#ip mroute <A.B.C.D> <A.B.C.D> <A.B.C.D> [<1-255>]
where:
A.B.C.D is the source IP address of the multicast static route.
A.B.C.D is the source network mask of the multicast static route.
A.B.C.D is the Reverse Path Forwarding neighbor IP address or route.
1-255 is the optional administrative distance of the multicast static route.
Changing the Distance for a Unicast Multicast Route
The distance value is used when comparing routes with the same source in the unicast
routing table. The route that is configured with the lower administrative distance
(which can be either the route in the unicast or DVMRP routing table) takes
precedence when determining the Reverse Path Forwarding (RPF) interface for the
source of a multicast packet.
Use the ip mroute unicast distance command, in Global Configuration mode, to
change the default administrative distance for the unicast multicast routes:
MOT:7A(config)#ip mroute unicast distance <1-255>
where:
1-255 is the administrative distance number for unicast multicast routes.
Changing the Distance for a Static Multicast Route
Use the ip mroute static distance command, in Global Configuration mode, to set
the default administrative distance for a multicast static route:
MOT:7A(config)#ip mroute static distance <1-255>
where:
1-255 is the administrative distance number for static multicast routes.
Clearing IP Multicast Information
Use the following sections to remove the contents of a particular cache, table, or
database when the contents are suspected to be invalid:
Removing a DVMRP Prune
Removing a DVMRP Route
Clearing IGMP Statistics
Removing the IP Multicast Cache
Removing a DVMRP Prune
Use the following options to remove a DVMRP prune:
Use the clear ip dvmrp prune * command, in Privileged EXEC mode, to clear
all DVMRP prunes:
MOT:7A#clear ip dvmrp prune *
Use the clear ip dvmrp prune group command, in Privileged EXEC mode, to
clear prunes from a specific DVMRP group:
MOT:7A#clear ip dvmrp prune group <A.B.C.D>
Note: The default administrative distance for a multicast route is 0.
where:
A.B.C.D is the IP address of the DVMRP group.
Use the clear ip dvmrp prune neighbor command, in Privileged EXEC mode,
to clear prunes from a specific neighbor:
MOT:7A#clear ip dvmrp prune neighbor <A.B.C.D>
where:
A.B.C.D is the IP address of the DVMRP neighbor.
Removing a DVMRP Route
Use the following options to remove a DVMRP route:
If you want to remove a specific DVMRP route, use the clear ip dvmrp route
command in Privileged EXEC mode:
MOT:7A#clear ip dvmrp route <A.B.C.D>
where:
A.B.C.D is the IP address of the DVMRP route.
If you want to clear all DVMRP routes, use the clear ip dvmrp route * command
in Privileged EXEC mode:
MOT:7A#clear ip dvmrp route *
Clearing IGMP Statistics
Use the clear ip igmp counters command, in Privileged EXEC mode, to remove
IGMP statistics:
MOT:7A#clear ip igmp counters
Removing the IP Multicast Cache
Use the following options to remove IP multicast routing information:
To clear the entire IP multicast forwarding cache, use the clear ip multicast
fwd-cache command in Privileged EXEC mode:
MOT:7A#clear ip multicast fwd-cache
To clear the entire IP multicast protocol cache and the IP multicast forwarding
cache, use the clear ip multicast proto-cache command in Privileged EXEC
mode:
MOT:7A#clear ip multicast proto-cache
Gathering IP Multicast Information
Use the following sections to gather information for your multicast network:
Displaying General IP Multicast Information
Displaying PIM Information
Displaying DVMRP Information
Displaying IGMP Information
Displaying Reverse Path Forwarding Information
Displaying General IP Multicast Information
Use the following options to view IP multicast cache information in Privileged EXEC
mode:
Use the show ip multicast cache-summary command to display the total
number of protocol cache and forwarding cache entries:
MOT:7A#show ip multicast cache-summary
Use the show ip multicast fwd-cache command to display multicast forwarding
cache entries:
MOT:7A#show ip multicast fwd-cache
Figure 3-1 displays typical show ip multicast fwd-cache command output:
Figure 3-1 Output for the show ip multicast fwd-cache Command.
Use the show ip multicast interface command to list the IP address, multicast
protocol (PIM, DVMRP, or IGMP), and time-to-live (TTL) information that is
associated with each multicast interface:
MOT:7A#show ip multicast interface
For example:
Figure 3-2 Output for the show ip multicast interface Command.
Use the show ip multicast no-oi-fwd-cache command to display multicast
forwarding cache entries that have no outgoing interfaces (OIs):
MOT:7A#show ip multicast no-oi-fwd-cache
Legend (L): D = DVMRP accept, d = DVMRP drop, P = PIM accept, p = PIM drop
N = None/Drop, U = unknown
Source/ (L) Incoming/ # in pkts # out pkts # OI Entry
Group Outgoing Timeout
------------------ --- ------------------ ---------- ---------- ---- --------
20.2.2.24/ N 20.2.2.1/ 6 0 181
224.2.158.205 NULL
20.2.2.34/ N 20.2.2.1/ 14 0 144
224.2.158.205 NULL
20.2.2.24/ N 20.2.2.1/ 12 0 151
224.2.173.27 NULL
20.2.2.34/ N 20.2.2.1/ 12 0 155
224.2.216.243 NULL
20.2.2.24/ N 20.2.2.1/ 14 0 141
224.2.216.243 NULL
20.2.2.34/ N 20.2.2.1/ 12 0 158
224.2.226.187 NULL
Interface Address Protocol TTL
----------------- -------- ---
60.6.6.4 PIM 1
20.2.2.1 PIM 1
Use the show ip multicast oi-fwd-cache command to display multicast
forwarding cache entries that have outgoing interfaces (OIs):
MOT:7A#show ip multicast oi-fwd-cache
Use the show ip multicast proto-cache command to display multicast protocol
cache entries:
MOT:7A#show ip multicast proto-cache
Displaying PIM Information
Use the following options to view PIM information in Privileged EXEC mode:
Use the show ip pim bsr-router command to display information about the
Version 2 PIM bootstrap router (bsr):
MOT:7A#show ip pim bsr-router
Use the show ip pim interface command to display PIM interface information:
MOT:7A#show ip pim interface
Use the show ip pim neighbor command to display the PIM neighboring router
information:
MOT:7A#show ip pim neighbor
Use the show ip pim rp command to display the PIM Rendezvous Point (RP)
information:
MOT:7A#show ip pim rp
Use the show ip pim rp-hash command to display the RP to be chosen based on
the selected group:
MOT:7A#show ip pim rp-hash
Use the show ip pim unresolved-groups command to display any unresolved
PIM multicast groups:
MOT:7A#show ip pim unresolved-groups
Displaying DVMRP Information
Use the following options to view DVMRP information in Privileged EXEC mode:
Use the show ip dvmrp information command to display general DVMRP
information:
MOT:7A#show ip dvmrp information
Use the show ip dvmrp interface command to display information for all the
DVMRP enabled interfaces:
MOT:7A#show ip dvmrp interface
Use the show ip dvmrp neighbor command to display DVMRP neighbor
information:
MOT:7A#show ip dvmrp neighbor
Use the show ip dvmrp network command to display DVMRP network
information:
MOT:7A#show ip dvmrp network
Use the show ip dvmrp route command to display DVMRP routing table
information:
MOT:7A#show ip dvmrp route
Use the show ip dvmrp summary-route command to display DVMRP summary
route information for each DVMRP interface:
MOT:7A#show ip dvmrp summary-route
Displaying IGMP Information
Use the following options to view IGMP information in Privileged EXEC mode:
Use the show ip igmp groups command to display IGMP group membership
information such as group address, interface, uptime, expires, and last reporter:
MOT:7A#show ip igmp groups
Use the show ip igmp interface command to display IGMP information for each
interface:
MOT:7A#show ip igmp interface
Use the show ip igmp statistics command to display IGMP statistics
information:
MOT:7A#show ip igmp statistics
Displaying Reverse Path Forwarding Information
Use the following options to display Reverse Path Forwarding (RPF) information in
Privileged EXEC mode:
Use the show ip rpf command to display RPF information for a specific multicast
source address:
MOT:7A#show ip rpf <A.B.C.D>
where:
A.B.C.D is the IP address of a multicast source address.
Use the show ip rpf command to display all RPF information:
MOT:7A#show ip rpf
4
Configuring RIP
Overview
This chapter describes how to configure the Routing Information Protocol (RIP) on
the BSR 64000 system using the Command Line Interface (CLI). For a complete
description of the CLI commands discussed in this chapter, refer to the BSR 64000
Command Reference Guide.
About RIP
Enabling RIP
Configuring RIP Optional Parameters
Redistributing Routes into RIP
Gathering RIP Information
About RIP
Routing Information Protocol (RIP) is an Interior Gateway Protocol (IGP) that uses a
distance-vector routing algorithm to measure the shortest path between two points on
a network. Distance-vector routing requires that each router inform its neighbors of its
routing table. For each network path, the receiving router selects the neighbor
advertising the lowest cost, and adds this entry to its routing table for
re-advertisement. A host using RIP should have interfaces to one or more networks,
which are known as directly connected networks.
RIP uses broadcast User Datagram Protocol (UDP) data packets to exchange routing
information. RIP listens for these broadcasts on UDP port 520. Routing information
updates are sent every 30 seconds. If a router does not receive an update from another
router for 180 seconds, it marks the routes served by the non-updating router as
unusable. If the router does not receive an update after 300 seconds, it removes all
routing table entries for the non-updating router.
RIP uses the hop count to rate the value of different routes. A directly connected
network has a hop count of one; an unreachable network has a hop count of 16. This
small range of metrics makes RIP unsuitable for large networks.
The route tag field in a RIP message allows boundary routers in an autonomous
system (AS) to exchange information about external routes. Route tags separate
internal RIP routes from external RIP routes that were imported from an Exterior
Gateway Protocol (EGP) or another IGP. Routers that support protocols other than
RIP should allow configuration of route tags for routes imported from different
sources.
The subnet mask field in a RIP (RIPv2 only) message contains the subnet mask
applied to the IP address to set the non-host portion of the address. If the subnet mask
field is not used, the subnet mask is calculated. On an interface where a RIPv1 router
operates on information in a RIPv2 routing entry, the following rules apply:
Information internal to one network must never be advertised to another network.
Information about a more specific subnet may not be advertised where RIPv1
routers would consider it a host route.
Supernet routes (routes where a subnet mask is less specific than the natural
network mask) must not be advertised where they could be misinterpreted by RIP
routers.
Release 6.3.1 Configuring RIP
The next hop field in a RIP (RIPv2 only) message contains the next destination IP
address. To reduce unnecessary load on hosts that do not listen to RIPv2 messages, a
value of zero in next hop field indicates that the next destination is the origin of the
RIP message. RIPv2 update packets use IP multicast address 224.0.0.9.
Specifications
The BSR supports the following Request for Comment (RFC) specifications:
RFC 1058, Routing Information Protocol
RFC 2453, RIP Version 2
Enabling RIP
In order to use RIP on the BSR, RIP must be enabled and a network must be specified.
Configuring RIP optional parameters is described in Configuring RIP Optional
Parameters on page 4-4.
Follow these steps to enable RIP and specify a network on the BSR:
1. Use the router rip command, in Global Configuration mode, to enable a RIP
routing process on the BSR:
MOT:7A(config)#router rip
This enables RIP and places you in Router Configuration mode. Use the no
router rip command to disable RIP.
2. RIP routing updates are sent and received only through interfaces on the networks
that you specify. If you do not specify the IP address related to the interface, RIP
updates do not advertise the network associated with this interface. Use the
network command, in Router Configuration mode, to associate a network with
the RIP routing process:
MOT:7A(config-rip)#network <A.B.C.D> [<A.B.C.D>]
where:
A.B.C.D is the IP address of a directly connected network.
A.B.C.D is the network mask.
You may specify multiple network commands.
Example
The following example configures RIP as the routing protocol to be used on all
interfaces connected to networks 138.82.0.0, 182.41.4.0, and 10.10.10.0:
router rip
network 138.82.0.0 255.255.0.0
network 182.41.5.0 255.255.255.0
network 10.10.10.0 255.255.255.0
Configuring RIP Optional Parameters
The following sections describe RIP commands for configuring optional RIP
parameters:
Specifying a RIP Version
Enabling or Disabling Split Horizon
Enabling Route Summarization
Applying an Offset List
Enabling RIP Authentication
Configuring Interpacket Delay
Configuring Timers
Configuring a Passive Interface for RIP
Specifying a RIP Version
By default, the software receives RIPv1 and RIPv2 packets, but sends only RIPv2
packets. You can configure the software to receive and send only RIPv1 packets. You
can also configure the software to receive and send only RIPv2 packets.
Use the version command, in RIP Router Configuration mode, to configure the
software to receive and send only RIPv1 packets or only RIPv2 packets:
MOT:7A(config-rip)#version {1 | 2}
where:
1 configures an interface to receive and send only RIPv1 packets.
2 configures an interface to receive and send only RIPv2 packets.
The version command specifies a RIP version used globally by the router. This
controls only the RIP default. You can configure a particular interface to behave
differently. To control the RIP version an interface sends or receives, use the ip rip
send version or ip rip receive version command in Interface Configuration mode.
1. To configure an interface to receive only RIPv1 packets and/or RIPv2 packets,
use the ip rip receive version command in Interface Configuration mode:
MOT:7A(config-if)#ip rip receive version {0 | 1 | 2}
where:
0 configures an interface to receive RIPv1 and RIPv2 packets.
1 configures an interface to receive only RIPv1 packets.
2 configures an interface to receive only RIPv2 packets.
2. Use the ip rip send version command, in Interface Configuration mode, to
configure an interface to send only RIPv1 or RIPv2 packets:
MOT:7A(config-if)#ip rip send version {0 | 1 | 2 | 3}
where:
0 configures an interface to send only RIPv1 and RIPv2 packets.
1 configures an interface to send only RIPv1 packets.
2 configures an interface to send only RIPv2 packets.
3 configures an interface not to send RIP packets.
Examples
The following example configures the interface to send RIPv1 packets from the
interface:
ip rip send version 1
This example configures the interface to receive only RIPv1 packets:
ip rip receive version 1
Enabling or Disabling Split Horizon
Distance-vector routing protocols, such as RIP, use the split horizon (with limited
poison reverse) mechanism to prevent routing loops. Split horizon prevents the router
from advertising route information on any interface from which that information
originated. This usually optimizes communications among multiple routers,
particularly when links are broken. Split horizon is enabled by default.
Follow these steps to enable or disable split horizon:
1. Use the ip split-horizon command, in Interface Configuration mode, to enable
split horizon:
MOT:7A(config-if)#ip split-horizon
2. To disable split horizon, use the no ip split-horizon command in Interface
Configuration mode:
MOT:7A(config-if)#no ip split-horizon
RIPv2 supports route summarization, which condenses routing information and
reduces the router load and the perceived network complexity. The larger the
network, the more important route summarization is. Without route summarization, a
router retains a route to every subnet in its network. With summarization, the router
can reduce some sets of routes to a single advertisement. Route propagation and
routing information are reduced significantly.
1. To enable route summarization, use the auto-summary command in Router RIP
Configuration mode. It is disabled by default.
MOT:7A(config-rip)#auto-summary
2. If you disconnect subnetworks, disable automatic route summarization, using the
no auto-summary command. When route summarization is disabled, the
software transmits subnet and host routing information across classful network
boundaries.
Applying an Offset List
An offset list is used to add an offset value to the incoming and outgoing metrics on
routes learned via RIP. You can also limit the offset list to an interface. To increase
the value of routing metrics using an offset list, use the offset-list command in RIP
Router Configuration mode:
MOT:7A(config-rip)#offset-list {<1-99>} [any] {in | out} <0-16> [cable <X/Y> |
ethernet <X/Y>| gigaether <X/Y> | pos <X/Y>]
where:
1-99 is the standard access list number to be applied.
any applies the offset to all incoming and outgoing metrics.
in applies the access list to incoming metrics.
out applies the access list to outgoing metrics.
0-16 is the positive offset to be applied to metrics for networks matching the
access list. If the offset is 0, no action is taken.
cable X/Y is the cable interface slot number and port number to which the
offset-list is applied.
ethernet X/Y is the Ethernet interface slot number and port number to which the
offset-list is applied.
gigaether X/Y is the Gigabit Ethernet interface slot number and port number to
which the offset-list is applied.
pos X/Y is the POS interface slot number and port number to which the offset-list
is applied.
Examples
1. In the following example, the router applies an offset of 3 to a metric defined by
access list 13:
offset-list 13 out 3
2. In the following example, the router applies an offset of 4 to routes learned from
Ethernet interface 1/0:
offset-list 13 in 3 ethernet 1/0
Enabling RIP Authentication
RIPv1 does not support authentication. If you send and receive RIPv2 packets, you
can enable RIP authentication on a particular interface. The BSR supports two RIP
authentication options, plain-text password authentication and Message Digest Five
(MD5) encrypted password authentication.
Use the ip rip authentication key command, in Interface Configuration mode, to
enable plain text password authentication:
MOT:7A(config-if)#ip rip authentication key <password>
where:
password specifies the 16 character password authentication key.
Configuring MD5 Authentication for RIP V2
Up to 10 Message Digest 5 (MD5) keys per interface can be configured for Routing
Information Protocol (RIP) Version 2 at the same time. MD5 keys increase security
between RIP V2 interfaces. In past releases, only one MD5 digest key per interface
was supported.
Each RIP V2 router interface using MD5 authentication must be configured with the
same MD5 keys. During RIP V2 periodic and triggered routing updates, one RIP
message is sent for each configured MD5 key. For example, if ten keys are configured
for a particular interface, then 10 RIP V2 updates are sent, one for each encrypted key.
When RIP V2 route updates are received on an interface, the update is authenticated
against the same MD5 key configured on this interface. For example, if a particular
interface receives RIP V2 updates that contain a key ID of 6, the message is then
authenticated against the encrypted password for this key (key 6) that is configured
for this local RIP V2 routing interface.
Follow these steps to configure Message Digest 5 (MD5) Authentication for a RIP V2
interface:
1. Use the interface command in Global Configuration mode to select the RIP V2
interface.
MOT:7A(config)#interface {cable <X/Y> | ethernet <X/Y> | gigaether <X/Y>
| loopback <1-255> | pos <X/Y> | tunnel <0-255>}
where:
cable X/Y is the slot and MAC Domain number of the CMTS module.
ethernet X/Y is the Ethernet module number and 10/100 Mbps port number.
gigaether is the Gigabit Ethernet module number and 1000 Mbps optical port
number.
pos X/Y is the Packet-Over-SONET module number and optical port number.
loopback <1-255> is the loopback interface.
tunnel <0-255> is the tunnel interface.
2. Use the ip rip message-digest-key command, in Interface Configuration mode,
to configure an MD5 key.
MOT:7A(config-if)#ip rip message-digest-key <1-255> md5 {7 <WORD>
| <WORD>}
where:
1-255 is the range of numbers from which an MD5 secret Key ID can be
selected.
7 <WORD> specifies a hidden (encrypted) MD5 password will follow that is
between 1-50 characters.
WORD is the MD5 password that is between 1-16 characters.
3. Repeat Step 2 to configure additional MD5 keys. Up to 10 MD5 keys can be
configured.
Configuring Interpacket Delay
By default, there is no delay inserted between packets in a multiple-packet RIP
update. If you have a high-end router sending to a low-speed router, you might want
to add some inter-packet delay to RIP updates. To do so, use the output-delay
command in Router RIP Configuration mode:
MOT:7A(config-rip)#output-delay <8-50>
where:
8-50 is the delay, in milliseconds, between packets in a multiple-packet RIP
update; the default is no delay.
Use the no output-delay command to return to the default.
Configuring Timers
Routing protocols use timers to regulate performance. To enhance RIP performance,
the default values for the RIP timers can be adjusted with the timers basic command.
1. To determine the current timers, use the show ip protocols command in
Privileged EXEC mode:
MOT:7A#show ip protocols
2. To set the RIP network timers, use the timers basic command in Router RIP
Configuration mode:
MOT:7A(config-rip)#timers basic <update-timer> <invalid> <flush-timer>
where:
update-timer is the value (1-4294967295), in seconds, between periodic
routing updates; default is 30 seconds.
invalid is the interval of time (1-4294967295), in seconds, after which a route
is declared invalid; this interval should be at least three times the
update-timer value. A route becomes invalid when there is an absence of
updates that refresh the route. The route is marked inaccessible and
advertised as unreachable. The route, however, is still used to forward
packets; default is 180 seconds.
flush-timer is the interval value (1-4294967295), in seconds, that elapse
before a route is removed from the routing table.The interval specified must
be greater than the invalid value; default is 300 seconds.
Example
The following example establishes a 60 second routing update timer, a 360 second
route timeout timer, and a 600 second route flush timer:
timers basic 60 360 600
Configuring a Passive Interface for RIP
You can configure a passive interface to prevent other routers on a local network from
learning about routes dynamically. A passive interface does not transmit routing
updates.
Use the passive-interface command, in Router Configuration mode, to create a
passive RIP interface:
MOT:7A(config-rip)#passive-interface {cable <X/Y> | ethernet <X/Y> |
gigaether <X/Y> | pos <X/Y>}
where:
ethernet is the Ethernet/Fast Ethernet interface.
Note: You can adjust basic RIP timers, but they must be the same for all
routers and servers in the RIP network.
gigaether is the Gigabit Ethernet interface.
Each routing protocol uses different metrics to transfer routes. Some protocols use
hop count metrics, while others use bandwidth and delay attributes to define metrics.
When a specific route is redistributed from one routing protocol or domain into
another, a common metric must be applied by the receiving protocol. Routes are
redistributed to advertise networks on another routing protocol.
Follow these steps to redistribute routes into RIP:
1. Enter the RIP Router Configuration mode:
MOT(config)#router rip
2. Choose from one or more of the following options to redistribute routes from a
specified protocol:
Use the redistribute connected command, in Router Configuration mode, to
redistribute connected routes into RIP:
MOT:7A(config-rip)#redistribute connected metric <1-16>
where:
1-16 is the redistribution metric number for connected routes.
Use the redistribute ospf command, in Router Configuration mode, to
redistribute OSPF routes into RIP:
MOT:7A(config-rip)#redistribute ospf [match {internal | external
| external1 | external2}] [metric <1-16>] [route-map <WORD>]
where:
Note: The RIP metric values for applying non-RIP routes are limited to values
from 1 to 16. RIP metrics are established by hop-counts.
match is the criteria by which OSPF routes are redistributed into RIP.
internal is used to redistribute internal OSPF routes.
external is used to redistribute external OSPF routes into RIP.
external1 is used to redistribute OSPF external1 type routes into RIP.
external2 is used to redistribute OSPF external2 type routes into RIP.
1-16 is the redistribution metric assigned to OSPF routes.
WORD is the route-map name.
Use the redistribute bgp command, in Router Configuration mode, to
redistribute BGP routes into RIP:
MOT:7A(config-rip)#redistribute bgp [metric <1-16>] [route-map
<WORD>]
where:
1-16 is the redistribution metric number for BGP routes.
Use the redistribute static command, in Router Configuration mode, to
redistribute static routes into RIP:
MOT:7A(config-rip)#redistribute static [metric <1-16>] [route-map
<WORD>]
where:
1-16 is the redistribution metric number for BGP routes.
Assigning a Default Metric Value for Redistributed Routes
The default metric function is used to eliminate the need for separate metric
definitions for each routing protocol redistribution.
Follow these steps to assign a default metric value for all routes redistributed into
RIP:
1. Use the router rip command to enter the RIP Router Configuration mode:
MOT:7A(config)#router rip
2. Use the default-metric command, in Router Configuration mode, to force a
routing protocol to use the same metric value for all distributed routes from other
routing protocols:
MOT:7A(config-rip)#default-metric <1-16>
where:
1-16 is the default value for all routes that are redistributed into RIP.
Gathering RIP Information
Follow these steps to monitor RIP on the BSR:
1. Use the show ip route rip command in Privileged EXEC mode:
MOT:7A#show ip route rip
2. To display the configured network parameters for RIP, use the show ip protocols
in Privileged EXEC mode. Figure 4-1 gives an example of the show ip protocols
command output:
Figure 4-1 show ip protocols Command Output
Routing Protocol is
"rip
"
Sending updates every 30 seconds
Invalid after 180 seconds, flushed after 300
Outgoing update filter(s) list for all interfaces are:
Incoming update filter(s) list for all interfaces are:
Default redistribution metric is not set
Default version control: send version 2, receive version 1 and 2
Interface SV RV Key KeyId PassIf SplHrz HostRt
-------------------- -- -- ---------------- ----- ------ ------ ------
ethernet 14/0 2 2 **************** N Y Y
Interface pkts recv pkts tx routes new routes tx
--------- --------- ------- ---------- ---------
9.1.1.1 0 650 0 11887
11.1.1.1 0 649 0 11885
13.1.1.1 0 649 0 11885
14.1.1.1 0 649 0 11885
16.1.1.1 0 649 0 11885
17.1.1.1 0 649 0 11885
15.1.1.1 0 649 0 11885
8.1.1.10 661 647 12 11861
Routing for Networks:
8.1.1.0
9.1.1.0
3. To display the entire contents of the private RIP database, use the show ip rip
database command in Privileged EXEC mode. Figure 4-2 gives an example of
the show ip rip database command output:
Figure 4-2 show ip rip database Command Output
4. To view the routing table, enter the show ip route command in Privileged EXEC
mode. Figure 4-3 gives an example of the show ip route command output:
Figure 4-3 show ip route Command Output
172.19.13.0 255.255.255.0 redistributed 172.17.1.1 m:1 t:0
10.10.10.0 255.255.255.0 via 58.58.58.2 m:2 t:12
Codes: C - connected, S - static, R - RIP, B - BGP
i - IS-IS derived L1- IS-IS level-1 route, L2- IS-IS level 2 route
O - OSPF, IA - OSPF inter area, N1 - OSPF NSSA external type 1
N2 - OSPF NSSA external type 2, E1 - OSPF external type 1
E2 - OSPF external type 2, * - candidate default
U - per-user static route, P - periodic downloaded static route
T - traffic engineered route
Gateway of last resort is 172.17.1.1 to network 0.0.0.0

*S 0.0.0.0/0 [1/0] via 172.17.1.1, ethernet 0/0
C 1.1.1.1/32 is directly connected, loopback 32
O IA 2.2.2.0/24 [110/556] via 3.3.3.2, ethernet 0/1
C 3.3.3.0/24 is directly connected, ethernet 0/1
C 4.4.4.0/24 is directly connected, ethernet 0/2
O 7.7.7.0/24 [110/2] via 80.80.80.6, ethernet 0/0
5
Configuring RIP over VRF
Introduction
This chapter describes using the CLI commands that support the RIP over VRF
feature in an MPLS-BGP network. For additional information necessary to
completely configure MPLS-BGP networks on the BSR, refer to the BSR 64000 BGP/
MPLS VPN Configuration Guide.
RIP Over VRF
In an MPLS-VPN environment, the use of a dynamic routing protocol is necessary to
exchange routes between customer site edge routers (CEs) and the providers routers
(PEs). In the current MPLS-BGP-VPN environment on the BSR, all downstream CPE
network information is learned from either connected or static routes. This network
information is then distributed in the MPLS-BGP network.
The RIP over VRF feature implements the RIP dynamic routing protocol in VRFs on
the BSR to manage PE to CE routing. The RIP protocol allows the BSR to
dynamically exchange routes between downstream routers on the cable interfaces.
The received routes are then converted to VPNv4 routes and distributed to the rest of
the MPLS network. RIP over VRF also provides customers with the flexibility to
import and export routing information into their CPE routers.
The BSR adds all RIP routes learned on a per-VRF basis to the corresponding
VRF specific route table.
The BSR performs route delete operations on RIP routes learned on a per-VRF
basis, and must be removed from the corresponding VRF-Specific Route table
only.
The BSR performs route update operations on RIP routes learned on a per-VRF
basis and updates the corresponding VRF specific route table.
The BSR supports the redistribution of static, connected, or BGP routes into RIP
on a per-VRF basis.
The BSR supports the redistribution of RIP routes into BGP on a per-VRF basis.
The BSR supports RIP over VRF on the following hardware modules:
SRM4
2:8 CMTS
TX32
HSIM4
The BSR supports a maximum of 32 non-global RIP VRF address family
instances for the RIP protocol.
Entering/Exiting RIP IPv4 VRF Address Family
Configuration Mode
RIP IPv4 VRF Address Family Configuration mode allows a user to configure
VRF-specific settings for a RIP routing session.
1. Use the address-family ipv4 vrf command, in RIP Router Configuration mode,
to enter RIP IPv4 VRF Address Family Configuration mode:
MOT:7A(config-rip)# address-family ipv4 vrf <word >
where:
word is the VPN Routing/Forwarding name.
Note: All of the following RIP over VRF configuration procedures are initiated
from RIP IPv4 VRF Address Family Configuration mode.
Release 6.3.1 Configuring RIP over VRF
The command line prompt changes to:
MOT:7A(config-rip-af-ipv4-vrf-<VRF name>)#
2. Use the exit-address-family command to return to RIP Router Configuration
mode.
3. Use the end or exit commands to return to Global Configuration mode.
Specifying an MPLS-BGP Network
In order to use RIP over VRF on the BSR, an MPLS-BGP network must be specified.
RIP routing updates are sent and received only through interfaces on the specified
MPLS-BGP network. If the IP address related to the interface is not specified, RIP
updates do not advertise the MPLS-BGP network associated with this interface.
Multiple MPLS-BGP networks can be specified.
Use the network command, in RIP IPv4 VRF Address Family Configuration mode,
to associate an MPLS-BGP network with the RIP routing process:
MOT:7A(config-rip-af-ipv4-vrf-<VRF name>)# network <A.B.C.D>
[<A.B.C.D>]
where:
A.B.C.D is the IP address of an MPLS-BGP network.
Route summarization condenses routing information and reduces the router load and
the perceived network complexity. The larger the network, the more important route
summarization is. Without route summarization, a router retains a route to every
subnet in its network. With summarization, the router can reduce some sets of routes
to a single advertisement. Route propagation and routing information are reduced
significantly.
1. To enable route summarization, use the auto-summary command, in RIP IPv4
VRF Address Family Configuration mode. It is disabled by default.
MOT:7A(config-rip-af-ipv4-vrf-<VRF name>)#auto-summary
2. If you disconnect subnetworks, disable automatic route summarization, using the
no auto-summary command. When route summarization is disabled, the
software transmits subnet and host routing information across network
boundaries.
Select one or more of the following command options to redistribute routes into RIP:
Use the redistribute bgp command, in RIP IPv4 VRF Address Family
Configuration mode, to redistribute BGP routes into RIP:
MOT:7A(config-rip-af-ipv4-vrf-<VRF name>)# redistribute
bgp [metric <1-16>] [route-map <WORD>]
where:
metric 1-16 is the redistribution metric number for BGP routes.
route-map WORD is the route-map name.
Use the redistribute connected command, in RIP IPv4 VRF Address Family
Configuration mode, to redistribute connected routes into RIP:
connected [metric <1-16>] [route-map <WORD>]
where:
metric 1-16 is the redistribution metric number for connected routes.
Note: The RIP metric values for applying non-RIP routes are limited to values
from 1 to 16. RIP metrics are established by hop-counts.
Release 6.3.1 Configuring RIP over VRF
Use the redistribute static command, in RIP IPv4 VRF Address Family
Configuration mode, to redistribute static routes into RIP:
static [metric <1-16>] [route-map <WORD>]
where:
metric 1-16 is the redistribution metric number for BGP routes.
Use the default-metric command, in RIP IPv4 VRF Address Family Configuration
mode, to force a routing protocol to use the same metric value for all distributed
routes from other routing protocols:
MOT:7A(config-rip-af-ipv4-vrf-<VRF name>)# default-metric
<1-16>
where:
1-16 is the default value for all routes that are redistributed into RIP.
Displaying RIP over VRF Information
show ip protocols
The show ip protocols command displays the status of routing protocol processes
currently active on the system.
MOT:7A# show ip protocols [bgp | rip | summary]
where:
bgp displays BGP protocol information.
rip displays RIP protocol information.
summary displays a summary of system routing protocol processes.
Refer to the BSR 64000 Command Reference Guide to see an example of typical
screen output for the show ip protocols command.
show ip rip database vrf
The show ip rip database vrf command displays RIP over VRF database routing
table information.
MOT:7A# show ip rip database vrf
Refer to Chapter 6 to see an example of typical screen output for the show ip rip
database vrf command.
show ip route vrf
The show ip route vrf command displays VPN Routing Forwarding (VRF) table
information.
MOT:7A# show ip route vrf <WORD> [<A.B.C.D> [<A.B.C.D>] | bgp | connected |
hostname | rip | static | summary]
where:
WORD is the specified VRF name.
A.B.C.D is a specific network associated with this VRF.
bgp displays BGP routes
connected displays connected routes
hostname is the Internet DNS hostname of the VRF
rip displays RIP routes
static displays static routes
summary displays a summary of the number of routes per routing protocol.
6
Configuring OSPF
Overview
This chapter describes how to configure Open Shortest Path First (OSPF) on the BSR
64000 system using the Command Line Interface (CLI). For a complete description
of the CLI commands discussed in this chapter, refer to the BSR 64000 Command
Reference Guide.
About OSPF
Enabling OSPF
OSPF Graceful Restart
Configuring OSPF Area Parameters
Managing OSPF on the BSR
Configuring OSPF on an Interface
Gathering OSPF Information
About OSPF
Open Shortest Path First (OSPF) is an Interior Gateway Protocol (IGP) that
implements a link-state routing protocol. OSPF runs within an Autonomous System
(AS). Link-state Advertisements (LSAs) are advertised to all routers in the AS to
ensure that each participating OSPF router has an identical database of the AS
topology. Each router uses the database information to calculate a shortest-path tree
for updating the routing table. It recognizes AS topology changes and calculates new,
loop-free routes.
OSPF requires coordination among many internal routers, Area Border Routers
(ABRs), and Autonomous System Boundary Routers (ASBRs). If you customize your
environment, you must ensure the coordinated configuration of all routers.
To configure OSPF, you must perform the basic tasks of enabling OSPF, defining an
OSPF area and area ID, and assigning an interface to the area. All other configuration
tasks are optional and if not configured, those configuration parameters will assume
default values.
Specifications
RFC 2328, OSPF Version 2
RFC 1587, The OSPF NSSA Option
Enabling OSPF
Follow these steps to enable OSPF, create the OSPF routing process, specify the
range of IP addresses associated with the routing process, and assign the area IDs
associated with that range of IP addresses:
1. Use the router ospf command, in Global Configuration mode, to enable OSPF
routing and enter Router Configuration mode:
MOT:7A(config)#router ospf
2. Use the network area command, in Router Configuration mode, to specify the
OSPF network, wildcard mask, and Area ID:
Release 6.3.1 Configuring OSPF
MOT:7A(config-ospf)#network <A.B.C.D> <A.B.C.D> area
{<0-4294967295> | <A.B.C.D>}
where:
A.B.C.D is the IP address of the OSPF network.
A.B.C.D is the wildcard bit mask (dont care bits).
0-4294967295 is the area ID number.
A.B.C.D is the area ID in IP address format. If areas are associated with IP
subnets, a subnet area may be specified.
Example
The following example enables the OSPF routing process and adds two OSPF ranges
with each range belonging to a different area. Area 0 is configured for network
123.3.4.0 and Area 1 is configured for network 125.6.6.0. The example creates two
OSPF interfaces. One interface is in the backbone area (Area 0) using IP address
123.3.4.17. The other interface is in the non-backbone area (Area 1) using IP address
125.6.6.23.
ip address 123.3.4.17 255.255.255.0
ip address 125.6.6.23 255.255.255.0
router ospf
network 123.3.4.0 0.0.0.255 area 0
network 125.6.6.0 0.0.0.255 area 1
OSPF Graceful Restart
After an SRM switchover, OSPF will normally rediscover neighboring routers, elect
Designated and Backup Designated Routers on broadcast media, synchronize its
database with its neighbors, maintain this synchronization through flooding, rebuild
its link-state database, and perform routing calculations.
If the BSR is able to keep forwarding traffic and the network topology does not
change, OSPF can perform a graceful restart recovery. The graceful restart feature
allows a "restarting" OSPF router to remain on the forwarding path even as its OSPF
software is being restarted.
In order for a graceful restart to take place, the neighboring routers of the BSR must
also cooperate and be in what is referred to as the helper mode. When the BSR is
acting as a neighboring router, helper mode must be enabled for accomplishing a
graceful restart.
This section describes the following:
Enabling OSPF Graceful Restart
Enabling Helper Mode on the BSR
Enabling OSPF Graceful Restart
Use the graceful-restart command, in OSPF Routing Configuration mode, to enable
the OSPF graceful restart, as follows:
MOT:7A(config-ospf)#graceful-restart [restart-interval <1-1800>]
where:
1-1800 the time period, in seconds, for completion of the OSPF graceful restart
following an SRM switchover.
The OSPF graceful restart feature performs the following:
The redundant SRM generates link-local opaque type-9 grace LSAs after a
switchover which advertises its intention to perform a graceful restart within a
certain grace period. The grace period specifies the time period for which the
neighbors should consider the restarting router as part of the topology.
During this grace period, the link-state database remains as is with the BSRs
neighbors remaining fully adjacent to the BSR. Periodic refreshes of the LSAs are
allowed. The neighboring routers act as if the BSR is still within the network
topology and network traffic continues to be forwarded to the restarting BSR.
Assuming that there are no changes to the network topology, the OSPF graceful
restart will complete and traffic forwarding has continued without interruption.
However, if any of the contents of the LSAs change, the OSPF graceful restart
procedure will be aborted and a normal OSPF restart will occur. The BSR
automatically reverts to a normal OSPF restart when such a topology change is
detected in order to avoid possible routing loops. A normal OSPF restart will
cause an interruption in traffic forwarding.
Note: Helper mode and graceful restart are independent. You can disable
graceful restart in the configuration, but still allow the router to cooperate with
a neighbor attempting to restart gracefully.
The helper mode command only enables/disables helper mode on the BSR.
Neighboring routers must support helper mode and have helper mode
enabled locally for graceful restart to be fully operational on the network.
Enabling Helper Mode on the BSR
Use the helper-mode command, in OSPF Routing Configuration mode, to enable
helper mode on the BSR, as follows:
MOT:7A(config-ospf)#helper-mode [<A.B.C.D> | grace-period <1-1800> |
strict-lsa-checking ]
where:
A.B.C.D is the neighbor router ID.
grace-period 1-1800 specifies the helper mode grace period in seconds. A grace
period is set to specify the time period for which the neighbors should consider
the restarting router as part of the topology.
strict-lsa-checking specifies helper mode strict LSA checking. Strict LSA
checking indicates whether or not an OSPF restart helper should terminate
graceful restart when there is a change to an LSA that would be flooded to the
restarting router or when there is a changed LSA on the restarting router's
retransmission list when graceful restart is initiated.
Redistributing Routes into OSPF
Routes from another routing protocol, such as BGP, are redistributed into OSPF.
When redistributing from one routing protocol or domain into another, a common
metric must be applied by the receiving protocol. Each routing protocol uses different
metrics to transfer routes. Some protocols use hop count metrics, while others use
bandwidth and delay attributes to define metrics.
Follow these steps to redistribute routes into OSPF:
1. Enter the OSPF routing process in which the routes are to be redistributed:
specified protocol:
Use the redistribute bgp command, in Router Configuration mode, to
redistribute BGP routes into OSPF:
MOT:7A(config-ospf)#redistribute bgp [metric <1-16777214>]
[route-map <WORD>]
where:
1-16777214 is the redistribution metric assigned to BGP routes.
WORD is the BGP route-map name.
redistribute connected routes into OSPF:
MOT:7A(config-ospf)#redistribute connected [metric <1-16777214>]
[route-map <WORD>]
where:
1-16777214 is the redistribution metric assigned to connected routes.
WORD is the route-map name for the connected route.
Use the redistribute rip command, in Router Configuration mode, to
redistribute RIP routes into OSPF:
MOT:7A(config-ospf)#redistribute rip [metric <1-16777214>]
[metric-type {1 | 2}] [route-map <WORD>] [subnets]
[tag <0-4294967295>]
where:
metric <1-16777214> is the redistribution metric assigned to RIP routes
from 1 to 16.
metric-type 1 redistributes OSPF External Type 1 metrics.
metric-type 2 redistributes OSPF External Type 2 metrics.
WORD is the route-map name for the OSPF route.
subnets allows the consideration of RIP subnets for redistribution into
OSPF.
tag <0-4294967295> sets a tag for routes redistributed into OSPF.
definitions for each redistributed routing protocol.
OSPF:
1. Use the router ospf command to enter the OSPF routing process in Global
Configuration mode:
routing protocol to use the same metric value for all redistributed routes from
other routing protocols:
MOT:7A(config-ospf)#default-metric <1-4294967295>
where:
1-4294967295 is the default metric value assigned to all routes that are
redistributed into OSPF.
Configuring OSPF Area Parameters
Use the following sections to configure OSPF area parameters:
Configuring OSPF Area Authentication Parameters
Configuring OSPF Stub Areas
Configuring OSPF Not-So-Stubby Area
Configuring Route Summarization between OSPF Areas
Configuring Route Summarization into OSPF Areas
Configuring OSPF Area Authentication Parameters
All neighbor routers on the same OSPF network require the same password to
exchange OSPF information. Use the following steps and options to define area
authentication parameters for your network:
1. Select the interface on which the OSPF authentication key password is to be
configured by using the interface command in Global Configuration mode.
2. Use one of the following options to configure authentication:
Use the ip ospf authentication-key command, in Interface Configuration
mode, to enable OSPF simple password authentication and assign a password
on the routing interface:
MOT:7A(config-if)#ip ospf authentication-key <WORD>
where:
WORD is the unencrypted (clear text) password with 1 to 8 characters.
Use the ip ospf message-digest-key command, in Interface Configuration
mode, to enable OSPF MD5 authentication:
MOT:7A(config-if)#ip ospf message-digest-key <1-255> md5 <WORD>
where:
<1-255> is the key identifier.
WORD is the unencrypted OSPF password consisting of
1 to 16 characters.
3. Exit Interface Configuration mode by using the end command.
4. Enter the OSPF router on the BSR, using the router ospf command in Global
Configuration mode.
5. Use one of the following options to configure authentication:
Use the area authentication command, in Router Configuration mode, to
enable OSPF area authentication to protect against unauthorized access to an
area:
MOT:7A(config-ospf)#area {<0-4294967295> | <A.B.C.D>}
authentication
where:
0-4294967295 is the area number.
A.B.C.D is the OSPF area in IP address format.
Use the area authentication message-digest command, in Router
Configuration mode, to enable OSPF area authentication that provides
encrypted MD5 password protection against unauthorized access to an area:
authentication message-digest
where:
0-4294967295 is the area ID.
Configuring OSPF Stub Areas
Stub areas do not receive information on external routes that have been redistributed
into OSPF from another routing protocol. A stub area allows a default route,
intra-area routes, and inter-area routes, but disallows autonomous system (AS)
external routes, virtual links, and autonomous system boundary router (ASBR) routes.
The Area Border Router (ABR) generates a default external route into the stub area
for destinations outside the Autonomous System (AS).
Use the following steps to configure a stub area:
1. Use the router ospf command, in Global Configuration mode, to enter OSPF
Router Configuration mode.
2. Use the area stub command, in Router Configuration mode, to configure an
OSPF area as a stub area
MOT:7A(config-ospf)#area {<0-4294967295> | <A.B.C.D>} stub
where:
0-4294967295 is the OSPF area ID number.
A.B.C.D is the OSPF area in IP address format.:
Use the following options to further define your OSPF stub area:
Use the optional area stub no-summary command, in Router Configuration
mode, to prevent an ABR from sending further Type 3 summary link-state
advertisements (LSAs) into the stub area:
MOT:7A(config-ospf)#area {<0-4294967295> | <A.B.C.D>} stub
no-summary
where:
0-4294967295 is the area number.
Use the area default-cost command, in Router Configuration mode, to assign a
specific cost to the default summary route sent into the stub area by an ABR only:
Note: If there is more than one router within a stub area, ensure that the area
that you are creating as a stub area is defined as a stub area on each of
these routers.
default-cost <0-65535>
where:
0-65535 is the OSPF cost metric, which is an unsigned 16-bit integer.
Configuring OSPF Not-So-Stubby Area
The Not-So-Stubby Area (NSSA) is similar to the OSPF stub area. It can import AS
external routes in a limited fashion within the area. NSSA allows importing of Type 7
AS external routes within NSSA area by redistribution. These Type 7 LSAs are
translated into Type 5 LSAs by NSSA ABRs and are flooded throughout the whole
routing domain. The BSR does not flood Type 5 external LSAs from the backbone
into the NSSA area. Summarization and filtering are supported during the translation.
Use NSSA to simplify administration if you are an Internet Service Provider (ISP) or
a network administrator and must connect a central site that uses OSPF to a remote
site that uses a different routing protocol. With NSSA, you can extend OSPF to cover
the remote connection by defining the area between the corporate router and the
remote router as an NSSA.
To configure an OSPF NSSA, use the area nssa command in Router Configuration
mode:
MOT:7A(config-ospf)#area {<0-4294967295> | <A.B.C.D>} nssa
[default-information-originate] [no-redistribution] [no-summary]
where:
0-4294967295 specifies the NSSA identifier.
A.B.C.D identifies the NSSA in IP address format.
default-information-originate allows Type 7 LSAs to be imported into the
NSSA.
no-redistribution indicates no routes are redistributed to this NSSA.
no summary disallows summary LSAs into the NSSA.
Example
The following commands redistribute RIP routing information into OSPF and define
area 1 as an NSSA:
router ospf
redistribute rip subnets
network 180.21.54.0. 0.0.0.255 area 1
area 1 nssa
Configuring Route Summarization between OSPF Areas
Route summarization causes an ABR to advertise a single summary route to other
areas. If the network numbers in an area have contiguous assignments, you can
configure the ABR to advertise a summary route that covers all the individual
networks within the area that are in the specified range.
Follow these options to configure OSPF route summarization:
Use the area range advertise command, in Router Configuration mode, to
specify an address range for which a single route is advertised:
range <A.B.C.D> <A.B.C.D> advertise
where:
A.B.C.D is the area ID in IP address format.
A.B.C.D is the IP address for a network within the area.
A.B.C.D is the subnet mask for the network.
Use the area range not-advertise command, in Router Configuration mode, to
specify an address range for a single route that is not advertised:
range <A.B.C.D> <A.B.C.D> not-advertise
where:
A.B.C.D is the area ID in IP address format.
A.B.C.D is the IP address for a network within the area.
A.B.C.D is the subnet mask for the network.
Example
These commands configure an ABR to summarize the aggregate range 2.2.0.0/16.
ip address 2.2.10.1 255.255.255.0
ip address 2.2.11.1 255.255.255.0
router ospf
network 2.2.0.0 0.0.255.255 area 1
area 1 range 2.2.0.0 255.255.0.0 advertise
Configuring Route Summarization into OSPF Areas
When redistributing routes from other protocols into OSPF, each route is advertised
individually in an external LSA. However, you can configure an ASBR to advertise a
single route for all the redistributed routes that are covered by a specified network
address and mask. Doing so helps decrease the size of the OSPF link state database
and the routing table.
Use the summary-address command, in Router Configuration mode, on the ASBR
to specify an IP address and mask that covers redistributed routes so that only one
summary route is advertised:
MOT:7A(config-ospf)#summary-address <A.B.C.D> <A.B.C.D> [tag
<0-4294967295>]
where:
A.B.C.D is the summary address in IP address format.
A.B.C.D is the summary IP address subnet mask.
0-4294967295 is the 32-bit tag value. It can be used for filtering externally
derived routing information.
Example
In the following example, summary address 20.1.0.0 and subnet mask 255.255.0.0
includes addresses 20.1.1.0, 20.1.2.0, 20.1.3.0, etc. Only the address 20.1.0.0 is
advertised in an external LSA.
summary-address 20.1.0.0 255.255.0.0
Managing OSPF on the BSR
This section discusses the following optional OSPF tasks:
Establishing a Virtual Link
Assign a Default Route for an ASBR
Controlling OSPF Link Cost Metrics
Allowing Dynamic OSPF Virtual Links
Changing OSPF Administrative Distances
Configuring Route Calculation Timers
Establishing a Virtual Link
In OSPF, all areas must be connected to a backbone area. If there is a break in
backbone continuity or the backbone is purposefully partitioned, you can establish a
virtual link. The two endpoints of a virtual link are Area Border Routers (ABRs). The
virtual link must be configured in both routers. The configuration information in each
router consists of the other virtual endpoint (the other ABR), and the non-backbone
area that the two routers have in common (the transit area).
Choose from the following options to establish a virtual link that connects an OSPF
area to the backbone area (area 0) without being physically connected to the OSPF
backbone area:
Use the area virtual-link command, in Router Configuration mode, if you want
to configure an OSPF virtual link with default parameters for the hello-interval,
retransmit-interval, transmit-delay, dead-interval, authentication-key, and
message-digest-key parameters:
virtual-link <A.B.C.D>
where:
A.B.C.D is the OSPF area ID in IP address format.
Note: Virtual links cannot be configured through stub areas.
A.B.C.D is the IP address of the virtual link ABR neighbor.
Use the area virtual-link hello-interval command, in Router Configuration
mode, to configure the time in seconds between hello packets on an interface for
the OSPF virtual link:
virtual-link <A.B.C.D> hello-interval <1-65535>
where:
1-65535 is the time in seconds between hello packets. It must be the same for
all routers and access servers attached to a common network.
Use the area virtual-link retransmit-interval command, in Router
Configuration mode, to configure the expected round-trip delay between two
routers on the attached network:
virtual-link <A.B.C.D> retransmit-interval <1-65535>
where:
1-65535 is the retransmission time in seconds. The value must be more than
the expected delay.
Use the area virtual-link transmit-delay command, in Router Configuration
mode, if you want to configure the Link-state Advertisement (LSA) transmit
delay between two routers on the attached network:
virtual-link <A.B.C.D> transmit-delay <1-65535>
where:
1-65535 is the approximate time in seconds to transmit an LSA packet.
Use the area virtual-link dead-interval command, in Router Configuration
mode, if you want to configure the interval that determines when the OSPF
virtual link neighbor is down:
MOT:7A(config-ospf)#area {<0-4294967295> | <A.B.C.D>} virtual-link
<A.B.C.D> dead-interval <1-65535>
where:
1-65535 is the number of seconds that the router does not receive hello
packets from its neighbor before declaring that the neighbor is down.
Use the area virtual-link authentication-key command, in Router
Configuration mode, if you want to set an unencrypted cleartext password for the
OSPF virtual link:
virtual-link <A.B.C.D> authentication-key <WORD>
where:
WORD is the password, 1 to 8 characters in length.
Use the area virtual-link message-digest-key command, in Router
Configuration mode, if you want to set an encrypted password for the OSPF
virtual link:
MOT:7A(config-ospf)#area {<0-4294967295> | <A.B.C.D>} virtual-link
<A.B.C.D> message-digest-key <1-255>
where:
1-255 is the OSPF MD5 Authentication Key.
Monitoring OSPF Virtual Links
Use the show ip ospf virtual-links command, in Privileged EXEC mode, to display
information about the established OSPF virtual links:
MOT:7A#show ip ospf virtual-links
Examples
1. The following example establishes a virtual link with default values for all
optional parameters:
router ospf
network 72.0.0.0 0.255.255.255 area 72.0.0.0
area 72.0.0.0 virtual-link 72.4.5.6
2. The following example establishes a virtual link with MD5 authentication:
router ospf
network72.0.0.0 0.255.255.255 area 72.0.0.0
area 72.0.0.0 virtual-link 72.4.5.6 message-digest-key 3
Assign a Default Route for an ASBR
Once routes are redistributed into an OSPF routing domain, the Autonomous System
Border Router (ASBR) must generate a default route into the OSPF routing domain.
Use the default-information originate command, in Router Configuration mode, on
an ASBR to generate a default route into the OSPF routing domain:
MOT:7A(config-ospf)#default-information originate [always]
[metric <0-16777214>] [metric-type <1-2>]
where:
always indicates always create a default route.
0-16777214 is the metric assigned to the default route; default is 10.
1-2 is the OSPF link state metric value.
Example
The following example specifies a metric of 100 for the default route redistributed
into the OSPF routing domain and an external metric type of Type 1:
router ospf
redistribute rip metric 100 subnets
default-information originate always metric 100 metric-type 1
Controlling OSPF Link Cost Metrics
The BSR OSPF routing process calculates the OSPF cost metric for an interface based
on the type of interface and the bandwidth of the interface. The OSPF cost metric is
calculated as the reference bandwidth divided by the bandwidth of the interface.
Use the auto-cost reference-bandwidth command, in Router Configuration mode, to
set the reference bandwidth for calculating the automatic cost metric that OSPF uses
to differentiate the cost of multiple high-bandwidth links:
MOT:7A(config-ospf)#auto-cost reference-bandwidth <1-4294967>
where:
1-4294967 is the reference bandwidth in Mbps.
Allowing Dynamic OSPF Virtual Links
Automatic detection and creation of OSPF links is disabled by default. Use the
auto-virtual-link command, in Router Configuration mode, to allow the OSPF
routing process on the BSR to automatically detect and create OSPF virtual links.
MOT:7A(config-ospf)#auto-virtual-link
Changing OSPF Administrative Distances
The administrative distance, numbered between 0 and 255, rates the credibility of
routing information from one or more routers. A routing source assigned a low
administrative distance is trusted more than a routing source that is assigned a high
administrative distance value.
Note: If the assigned administrative distance for a routing source is 255, it is
not trusted and is ignored.
The default administrative distance for all three OSPF distances (inter-area and
intra-area OSPF routes, and external routes) is 120. Use either of the following
options to change the administrative distance for OSPF routes:
Use the distance command, in Router Configuration mode, to set all three OSPF
distances to the same value:
MOT:7A(config-ospf)#distance <1-255>
where:
1-255 is the administrative distance for all OSPF routes.
Routes within an OSPF area use the intra-area argument; routes to another OSPF
area use the inter-area argument; and routes from another routing domain learned
through the redistribution of a route use the external argument.
Use the distance ospf command, in Router Configuration mode, to set an
individual value for the administrative distance for an intra-area OSPF route,
inter-area OSPF Route, and external route:
MOT:7A(config-ospf)#distance ospf intra-area <1-255> inter-area <1-255>
external <1-255>
where:
1-255 represents the administrative distance number for all routes within an
area.
1-255 represents the administrative distance number for all routes from one
area to another area.
1-255 represents the administrative distance number for routes learned by
redistribution from other routing domains.
Configuring Route Calculation Timers
Timers are used by routing protocols to determine time intervals for when route
information is adjusted.
Use the timers spf command, in Router Configuration mode, to configure the delay
time after OSPF receives a topology change until it starts a shortest path first (SPF)
calculation. The hold time between two consecutive SPF calculations can also be
specified.
MOT:7A(config-ospf)#timers spf <0-65535> <0-65535>
where:
0-65535 is the time delay in seconds between receiving a topology change to the
SPF calculation.
0-65535 is the hold-time in seconds between consecutive SPF calculations.
Configuring OSPF on an Interface
The following sections are used to configure interface-specific parameters for OSPF
and how to set up OSPF on a passive or loopback interface:
Configuring General OSPF Interface Parameters
Blocking OSPF LSA Flooding
Configuring a Passive Interface for OSPF
Configuring General OSPF Interface Parameters
Using the various ip ospf commands, you can change certain interface-specific OSPF
parameters, as shown in Table 5-1. If you change these parameters, ensure that the
configurations for all routers on your network have compatible values.
Table 6-1 OSPF Parameters
Parameter Description Default Values
cost Cost metric value for sending a packet on
an OSPF interface; the higher the
bandwidth, the lower the cost
10 Mbps 1 to 65535
Mbps
retransmit-interval Time interval between LSA
retransmissions
5 seconds 1 to 3600
seconds
transmit-delay Time allowed for LSA transmissions 1 second 1 to 3600
seconds
priority Priority of this router; it is used in
determining the OSPF designated router;
the router with the higher priority takes
precedence
1 0 to 255
hello-interval Time interval between hello packets 10 seconds 1 to 65535
seconds
1. Use the ip ospf cost command, in Interface Configuration mode, to specify the
cost of sending a packet on an OSPF interface:
MOT:7A(config-if)#ip ospf cost <1-65535>
where:
1-65535 is the OSPF path cost in Mbps.
2. Use the ip ospf retransmit-interval command, in Interface Configuration mode,
to specify the number of seconds between Link-state Advertisement (LSA)
retransmissions for adjacencies belonging to an OSPF area:
MOT:7A(config-if)#ip ospf retransmit-interval <1-3600>
where:
1-3600 is the OSPF retransmission interval in seconds.
3. Use the ip ospf transmit-delay command in Interface Configuration mode to set
the estimated number of seconds to transmit an LSA update packet on an OSPF
interface:
MOT:7A(config-if)#ip ospf transmit-delay <1-3600>
where:
1-3600 is the OSPF transmission delay time in seconds.
dead-interval After this time interval is exceeded and
no hello packets have been received by
neighbors during this time, this router is
considered down by its neighbors
40 seconds 1 to 65535
seconds
authentication-key Password for use by neighboring OSPF
routers that use OSPF simple password
authentication
None Character
string up to
8 bytes
message-digest-k
ey md5
Key enabling OSPF MD5 authentication disabled key id:
1-255;
password:
Character
string up to
16 bytes
Table 6-1 OSPF Parameters
Parameter Description Default Values
4. Use the ip ospf priority command, in Interface Configuration mode, to set
priority of this router:
MOT:7A(config-if)#ip ospf priority <1-255>
where:
1-255 is the priority for this router interface.
5. Use the ip ospf hello-interval command, in Interface Configuration mode, to
specify the length of time between the hello packets that the software sends on an
OSPF interface:
MOT:7A(config-if)#ip ospf hello-interval <1-65535>
where:
1-65535 is the number of seconds between hello packets.
6. Use the ip ospf dead-interval command, in Interface Configuration mode, to set
the number of seconds that hello packets must be absent before neighbors declare
the OSPF router down:
MOT:7A(config-if)#ip ospf dead-interval <1-65535>
where:
1-65535 is the number of seconds before the OSPF router is considered
down.
7. Use the ip ospf authentication-key command, in Interface Configuration mode,
to assign a password for neighboring OSPF routers to use on a network segment
that uses OSPF simple password authentication:
MOT:7A(config-if)#ip ospf authentication-key <WORD>
where:
WORD is the unencrypted (clear text) password (1 to 8 characters).
8. Use the ip ospf message-digest-key md5 command, in Interface Configuration
mode, to enable OSPF MD5 authentication:
MOT:7A(config-if)#ip ospf message-digest-key <1-255> md5 <WORD>
where:
1-255 is the MD5 key.
WORD is the encrypted MD5 password (1-16 characters).
Examples
1. The following example sets the cost of sending a packet over an interface to 30:
interface ethernet 7/0
ip ospf cost 30
2. The following example sets the time interval between transmissions of an LSA on
an interface to 20 seconds:
ip ospf retransmit-interval 20
3. The following example sets the time it takes to transmit a link state update on an
interface to 10seconds:
ip ospf transmit-delay 10
4. The following example sets the router priority value on an interface to 10:
ip ospf priority 10
5. The following example sets the interval between hello packets on an interface to
15 seconds:
ip ospf hello-interval 15
Blocking OSPF LSA Flooding
The OSPF LSA age indicates whether the LSA is valid. The LSA is discarded when it
reaches the maximum age of one hour. During the aging process, the originating
router sends a refresh packet every 30 minutes to keep the LSA from expiring,
regardless of network topology changes. The router tracks and refreshes the LSAs it
generates; it tracks and ages the LSAs it receives from other routers.
By default, OSPF floods new LSAs over all interfaces in the same area, except the
interface on which the LSA arrives. Some redundancy is desirable, because it ensures
robust flooding. However, too much redundancy can waste bandwidth and might
destabilize the network due to excessive link and CPU usage in certain topologies.
Use the ip ospf database-filter all out command, in Interface Configuration mode, to
block the flooding of OSPF LSAs on broadcast, non-broadcast, and point-to-point
networks:
MOT:7A(config-if)#ip ospf database-filter all out
Example
The following example prevents flooding of OSPF LSAs to broadcast, non-broadcast,
or point-to-point networks accessible through Ethernet interface 7/0:
ip ospf database-filter all out
Configuring a Passive Interface for OSPF
To prevent OSPF from flooding an interface, you can configure the interface as a
passive interface. This prevents OSPF from sending hello packets and routing updates
through the interface.
Use the passive-interface command, in Router Configuration mode, to create a
passive OSPF interface:
MOT:7A(config-ospf)#passive-interface {cable <X/Y> | ethernet <X/Y> |
gigaether <X/Y> | loopback <1-255> | pos <X/Y>}
where:
ethernet is the Ethernet/Fast Ethernet interface.
loopback <1-255> is the loopback interface number.
Gathering OSPF Information
There are several show commands that can be used to view and gather information
about your OSPF network. These show commands are available in all command
modes except for User EXEC mode, and most user access groups.
Use the following sections to gather information for your OSPF network:
Displaying OSPF Routing Information
Displaying OSPF Memory Information
Displaying OSPF Routing Information
Use the following sections to display OSPF routing information:
Displaying Network Information
Displaying Border Routers
Displaying Neighboring Routers
Displaying Virtual Links
Displaying Network Information
Use the show ip ospf network command to display the IP network addresses,
wildcard masks, and the area numbers for all OSPF area networks:
MOT:7A#show ip ospf network
Figure 5-1 displays typical show ip ospf network command output:
Figure 6-1 show ip ospf network Command Output
Displaying Border Routers
Use the show ip ospf border-routers command to display the Autonomous System
Boundary Router (ASBR) and Area Border Router (ABR) routing tables. Figure 5-2
displays typical show ip ospf border-routers command output:
Figure 6-2 show ip ospf border-routers Command Output
Displaying Neighboring Routers
The show ip ospf neighbor command is used to display OSPF neighbor information.
The command options are described as follows:
network 33.4.2.0 0.0.0.255 area 0
network 33.3.2.0 0.0.0.255 area 0
network 8.1.1.0 0.0.0.255 area 0
Routing Process OSPF internal Routing Table
Destination Next Hop Cost Type Rte Type Area
172.17.1.103 172.17.82.188 0 Both INTRA 0
172.17.111.1 8.1.1.1 22 ASBR INTRA 0
172 17 115 1 8 1 1 1 20 ASBR 0
Use the show ip ospf neighbor command to display information about all OSPF
neighbors. Figure 5-3 displays typical show ip ospf neighbor command output:
Figure 6-3 show ip ospf neighbor Command Output:
Use the show ip ospf neighbor command to display a specific OSPF neighbor by
entering its IP address:
MOT:7A#show ip ospf neighbor <A.B.C.D>
where:
A.B.C.D is the OSPF neighbor IP address.
Use the show ip ospf neighbor detail command to display detailed information
for all OSPF neighbors. Figure 5-4 displays typical show ip ospf neighbor detail
command output:
Figure 6-4 show ip ospf neighbor detail Command Output
Displaying Virtual Links
The show ip ospf virtual-links command displays parameters regarding the current
state of the OSPF virtual links.
MOT:7A#show ip ospf virtual-links
Note: The show ip ospf neighbor can be accessed by the ISP user group.
Neighbor ID Pri State Dead Time Address Interface
172.17.82.152 1 FULL/DR 00:00:38 8.1.1.1 8.1.1.10
Neighbor 172.17.82.152, interface address 8.1.1.1
In the area 0 via interface 8.1.1.10
Neighbor priority is 1, State is FULL
DR is 8.1.1.1 BDR is 8.1.1.10
Displaying OSPF Interface Information
The show ip ospf interface command is used to display OSPF interface information.
The command options are described as follows:
Use the show ip ospf interface command to display information about all
interfaces on which OSPF is configured. Figure 5-5 displays typical show ip ospf
interface command output:
Figure 6-5 show ip ospf interface Command Output
Use the show ip ospf interface command with the known IP address of the OSPF
interface to display information about a specific interface on which OSPF is
configured:
MOT:7A#show ip ospf interface <A.B.C.D>
ethernet 14/0 is up, line protocol is up
Internet Address 8.1.1.10/24, Area 0
Router ID 9.1.1.1, Network Type BROADCAST, Cost: 1
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 172.17.82.152, Interface address 8.1.1.1
Backup Designated Router (ID) 9.1.1.1, Interface address 8.1.1.10
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 172.17.82.152 (Designated Router)

Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 9.1.1.1, Interface address 33.3.2.3
Backup Designated Router (ID) 0.0.0.0, Interface address 0.0.0.0
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Neighbor Count is 0, Adjacent neighbor count is 0

Transmit Delay is 1 sec, State DR, Priority 1
where:
A.B.C.D is the interface IP address.
Use the show ip ospf interface command with modifiers to display information
about individual interfaces on which OSPF is configured:
MOT:7A#show ip ospf interface {cable <X/Y> | ethernet <X/Y> |
gigaether <X/Y> | loopback <1-255> | pos <X/Y> | tunnel <0-255>}
where:
cable is the CMTS interface.
ethernet is the Ethernet/FastEthernet IEEE 802.3 interface.
loopback is the loopback interface.
1-255 is the loopback interface number.
pos is the Packet Over SONET interface.
tunnel is the tunnel interface.
0-255 is the tunnel interface number.
Displaying OSPF Memory Information
Use the show ip ospf memory command to display OSPF memory usage
information. Figure 5-6 displays typical show ip ospf memory command output:
Figure 6-6 show ip ospf memory Command Output
Displaying OSPF Database Information
Use the following options to display OSPF database information:
Use the show ip ospf database command with an IP address of a router to
display information for a specific OSPF router:
MOT:7A#show ip ospf database [<A.B.C.D>]
where:
A.B.C.D is the IP address of the OSPF router.

OSPF Memory Usage
Mem Pool Free In-Used Hi-Water Mark
-----------------------------------------------------------
Gen256 497 3 10
Gen512 500 0 0
Gen1k 500 0 0
Gen2k 497 3 4
Lsd256 481 19 20
Lsa256 489 11 11
Lsa2k 192 8 9
Figure 5-7 displays typical show ip ospf database command output:
Figure 6-7 show ip ospf database Command Output Using an OSPF Router IP Address
Use the show ip ospf database adv-router command to view all the Link State
Advertisements (LSAs) for the advertising router:
MOT:7A#show ip ospf database adv-router <A.B.C.D>
where:
A.B.C.D is the IP address of the advertising router.
Use the show ip ospf database asbr-summary command to view the summary
of a Autonomous System Boundary Router (ASBR):
MOT:7A#show ip ospf database asbr-summary <A.B.C.D>
where:
A.B.C.D is the IP address of an ASBR.
Use the show ip ospf database external command to display external LSAs:
MOT:7A#show ip ospf database external

OSPF Router with ID (9.1.1.1)

Router Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Link count
9.1.1.1 9.1.1.1 1016 0x800000AE 0xDA24 3
172.17.1.103 172.17.1.103 914 0x80000149 0xDCD 1
172.17.82.152 172.17.82.152 1621 0x80000360 0x8CDA 5
172.17.111.1 172.17.111.1 1147 0x8000045E 0xAA0C 3
172.17.115.1 172.17.115.1 1617 0x800003C3 0x41A9 2

Network Link States (Area 0)

Link ID ADV Router Age Seq# Checksum
8.1.1.1 172.17.82.152 121 0x80000085 0x4508
172.17.82.152 172.17.82.152 1621 0x80000252 0x3064
172.17.120.100 172.17.115.1 477 0x8000007F 0x5A54

Summary Link States Type-3 (Area 0)
7
Configuring BGP
Overview
This chapter describes how to configure Border Gateway Protocol (BGP) on the BSR
64000 system using the Command Line Interface (CLI). For a complete description
of the CLI commands discussed in this chapter, refer to the BSR 64000 Command
Reference Guide.
About BGP
BGP Basic Configuration
BGP Peer Groups
BGP Routing Policy
BGP Path Selection and Configuration
Managing BGP
About BGP
Border Gateway Protocol (BGP), an Exterior Gateway Protocol (EGP), allows you to
set up an inter-domain routing system that automatically guarantees the loop-free
exchange of routing information between autonomous systems (ASs). An AS is a set
of routers that use a single routing policy running under a single technical
administration. An AS runs Interior Gateway Protocols (IGPs) such as Routing
Information Protocol (RIP), Open Shortest Path First (OSPF), or internal BGP within
its boundaries.
With BGP, each route comprises of a network number, a list of ASs (AS-path) that
information passed through, and a list of other path attributes. A BGP system
exchanges network reachability information with other BGP systems, including
AS-path information. This information allows routing loops to be pruned and
AS-level policy decisions to be enforced.
Routers that belong to the same AS and exchange BGP updates run IBGP. Routers
that belong to different ASs and exchange BGP updates run external BGP (EBGP).
With few exceptions, the commands for configuring IBGP and EBGP are identical.
BGP uses AS-path information to prevent routing loops. In BGP, each AS examines
the route in the path. This enables routers to look for loops by examining the
information sent to them about the path. Figure 7-1 and the following steps describe
exchanges between IBGP and EBGP in a multiple AS network.
1. Router Boston originates a route to Router NY.
2. Router NY forwards the route to Router LA, after adding its AS to the AS-path.
3. Router LA receives the route and ascertains that it comes from another AS.
Router LA adds its own AS to the AS-path and forwards the route to Router
Miami.
4. Router Miami receives the route and ascertains that it comes from another AS.
Router Miami adds its own AS to the AS-path and forwards the route to Router
Dallas.
5. Router Dallas receives the route, determines that the route is a loop since its own
AS is contained in the AS-path, and discards the route.
Release 6.3.1 Configuring BGP
Figure 7-1 Advertising BGP Routes
BGP minimizes routing traffic between ASs and manages the peer relationship
between border routers that connect ASs within a backbone of the network
infrastructure. IGPs concentrate on finding the shortest or quickest route between
endpoints within an AS; BGP is typically used between ASs.
BGP selects among different routes by comparing specific path attributes or metrics
for each route. The local administrator can manually configure each of these and
assign them different values.
The Multi-Exit Discriminator (MED) metric attribute value is configured using
route-maps. Updates sent to an IBGP peer also include unchanged MED information,
enabling all peers in the same AS to make a consistent path selection.
BGP supports classless inter-domain routing (CIDR). This allows reduction of the
routing table sizes by creating aggregate routes, which result in supernets. CIDR
eliminates the concept of network classes within BGP and supports the advertising of
IP prefixes. CIDR routes are also carried by OSPF and RIP.
AS 100
AS 200
LA
AS 300
Miami
bgp0003
Boston
NY
Dallas
EBGP
EBGP
IBGP
1
2
EBGP
4
3
5
BGP Neighbors
BGP provides a means for BGP neighbors, or peers, to exchange routing information
within an AS (IBGP) and with peers within other ASs (EBGP). The following
information is exchanged between neighbors:
New active routes and their attributes
Inactive routes
Unusual conditions that require connection termination
BGP does not require routing information to be refreshed. Advertised route
information is considered valid until a router explicitly advertises that the information
is no longer valid or until the BGP TCP session is lost.
BGP Updates
BGP routers exchange routing information in the form of BGP updates. BGP updates
contain the following attributes associated with routes that a BGP peer advertises to
its neighbors:
A list of ASs the routing update passed through
The AS routing update origin
Next hop information
Metrics specifying route preference
Note: Set up your router with BGP if your AS or router is dual or multihomed
(if it has two or more backbone connections, either direct or daisy-chained
through another point of presence). Also, use BGP if the BSR provides IP
routing to a downstream site or customer or if you must preserve AS-path
information in your network. If your site is single-homed and you do not
provide IP services or AS-paths, consider using static routes instead.
Because external routing requirements are relatively simple, static routing is
easier to set up and to maintain, and it requires less overhead.
BGP Sessions
After exchanging a series of messages, the BGP peers establish a session over TCP.
BGP session peers rely on TCP to manage the underlying connection. Once a TCP
connection is established, a BGP router uses port 179 to communicate full routing
information with another BGP peer. As long as the connection is up, the BGP partners
can exchange a very simple set of messages with minimal overhead.
The BGP protocol includes the exchange of keep-alive messages between peers. A
keep-alive message is a signal from one endpoint to another, indicating that the first
end point is still active. Keep-alive messages are necessary to keep BGP peers aware
of the health of the connection, because TCP does not provide this service.
Specifications
RFC 1771 A Border Gateway Protocol 4 (BGP-4)
RFC 1745 BGP4/IDRP for IP (OSPF Interaction)
RFC 1965 Autonomous System Confederations for BGP
RFC 1966 BGP Route Reflection, an Alternative to Full Mesh IBGP
RFC 1997 BGP Communities Attributes
RFC 1998 An Application of the BGP Community Attribute in Multi-home
Routing
RFC 2439 BGP Route Flap Damping
RFC 2385 Protection of BGP Sessions via the TCP MD5 Signature Options
BGP Basic Configuration
BGP provides a means to configure the connectivity of BGP neighbors and peer
groups. The following basic BGP configuration tasks are described:
Enabling BGP
Configuring a BGP Neighbor
Advertising Networks in an AS
Enabling BGP
Use the router bgp command, in Global Configuration mode, to enable BGP and
enter Router Configuration mode:
MOT:7A(config)#router bgp <1-65535>
where:
1-65535 is the Autonomous System (AS) to which the router belongs.
Configuring a BGP Neighbor
Follow these steps to configure a BGP neighbor:
1. Use the router bgp command, in Global Configuration mode, to enter Router
Configuration mode:
where:
1-65535 is the Autonomous System (AS) to which the router belongs. If the
BGP router is enabled, the AS can be found using the show running-config
command.
2. Use the neighbor remote-as command, in Router Configuration mode, to add an
entry to the BGP neighbor table. The BGP neighbor table identifies a router as a
BGP peer and maps its IP address to a specific AS.
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} remote-as
<1-65535>
where:
A.B.C.D is the neighbor IP address.
WORD is the name of the BGP peer group already configured.
1-65535 is the AS to which the neighbor belongs.
3. Use the neighbor description command, in Router Configuration mode, to
associate a textual description with a BGP neighbor.
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} description
<LINE>
where:
A.B.C.D is the IP address of the neighbor.
WORD is the name of the BGP peer group.
LINE is up to 80 characters of text that describes the neighbor.
Example
The following commands configure Routers Miami with Routers Chicago, Boston,
and NY as neighbors (as shown in Figure 7-2):
MOT:7A(config-bgp)#router bgp 100
MOT:7A(config-bgp)#neighbor 172.30.20.2 remote-as 100
MOT:7A(config-bgp)#neighbor 172.30.20.2 description peer_NY
MOT:7A(config-bgp)#neighbor 172.40.20.2 description peer_Chicago
MOT:7A(config-bgp)#neighbor 192.50.30.2 description peer_Boston
Figure 7-2 Configuring BGP Neighbors
AS 100 AS 300
Boston
bgp0004
NY
192.50.30.1
192.50.30.2
172.30.20.2
172.30.20.1
172.40.20.2
172.40.20.1
Chicago
Miami
Advertising Networks in an AS
Use the network command, in Router Configuration mode, to advertise to BGP peers
in other ASs about the networks in your AS:
MOT:7A(config-bgp)#network <A.B.C.D> [mask <A.B.C.D>]
where:
A.B.C.D is the network IP address that BGP advertises.
mask is the keyword for specifying the network mask.
Example
Refer to Figure 7-3 to configure Routers Miami, Chicago, and LA for advertising
networks in their ASs.
The following commands configure Router Miami:
MOT:7A(config-bgp)#network 126.60.0.0
The next commands configure Router Chicago:
These commands configure Router LA:
Figure 7-3 Advertising Networks in an AS
BGP Peer Groups
A BGP peer group assigns the same set of routing policies to a group of BGP
neighbors or peers. Peer groups help to reduce the configuration effort. They are
configured on one router associated with the peer group. You can also use peer groups
to override configuration options for incoming updates.
The following sections describe various BGP peer group configuration topics:
Configuring BGP Peer Groups
Enabling EBGP Multihop for Neighbor and Peer Groups
Shutting Down a Neighbor or Peer Group
3.3.3.2 AS 400
162.56.0.0
2.2.2.2
Miami
LA
Chicago
bgp0005
AS 300
162.24.0.0
AS 100
126.60.0.0
3.3.3.1
2.2.2.1
4.4.4.1
4.4.4.2
Configuring BGP Peer Groups
You can create a BGP peer group or you can configure a BGP neighbor to be a
member of a BGP peer group using the neighbor peer-group command.
1. Use the neighbor peer-group command, in Router Configuration mode, to
create a BGP peer group:
MOT:7A(config-bgp)#neighbor <WORD> peer-group
where:
WORD is the name you assign to the peer group.
2. Use the neighbor peer-group command, in Router Configuration mode, to
assign a BGP neighbor as a member of a BGP peer group:
MOT:7A(config-bgp)#neighbor <A.B.C.D> peer-group <WORD>
where:
A.B.C.D is the IP address of the neighbor to be assigned to the peer group.
WORD is the name of the peer group.
Example
In Figure 7-4, the first peer group contains the routers in AS 100. The second peer
group contains Routers Chicago, Philadelphia, Trenton, and Boston.
Figure 7-4 BGP Peer Groups
The following commands configure the BGP peer group, PACIFIC, on Router
Chicago and apply it to Routers SF, Dallas, and Seattle (as shown in Figure 7-4):
MOT:7A(config)#router bgp 100
MOT:7A(config-bgp)#neighbor PACIFIC peer-group
MOT:7A(config-bgp)#neighbor PACIFIC remote-as 100
MOT:7A(config-bgp)#neighbor 2.2.2.2 peer-group PACIFIC
The following commands configure the BGP peer group, ATLANTIC, on Router
Chicago and apply it to Routers Philadelphia, Trenton, and Boston:
MOT:7A(config-bgp)#neighbor ATLANTIC peer-group
MOT:7A(config-bgp)#neighbor 5.5.5.5 peer-group ATLANTIC
AS 100
AS 200
Philadelphia
AS 300
Trenton
AS 400
Boston
bgp0006
5.5.5.5
6.6.6.6
4.4.4.4
2.2.2.2
3.3.3.3
3.3.3.1
4.4.4.1
2.2.2.1
5.5.5.1
7.7.7.1
6.6.6.1
7.7.7.7
Chicago Seattle
Dallas
SF
Enabling EBGP Multihop for Neighbor and Peer Groups
Normally, EBGP neighbors are directly connected. When EBGP neighbors do not
connect directly, use the neighbor ebgp-multihop command to specify that the
neighbor is more than one hop away.
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} ebgp-multihop
[<1-255>]
where:
A.B.C.D is the IP address of the BGP neighbor.
1-255 is the time-to-live in the range 1 to 255 hops.
Example
The commands in this example configure Router Miami, as shown in Figure 7-5:
MOT:7A(config-bgp)#neighbor 1.1.1.1 ebgp-multihop
Figure 7-5 shows Router Miami is configured with Router Washington as an external
peer. Because Router Miami and Router Washington are connected together via
Router Boston, rather than by a direct link, the neighbor ebgp-multihop command is
used.
Figure 7-5 Using EBGP-Multihop
Shutting Down a Neighbor or Peer Group
Follow these steps to disable a BGP neighbor or peer group:
1. Use the show ip bgp summary command, in Privileged EXEC mode, to view a
summary of BGP neighbors and peer-group connections:
MOT:7A(config-bgp)#show ip bgp summary
Note: Disabled neighbors have an Idle status and Admin entry.
1.1.1.1
AS 200

Washington
bgp0031
AS 200
AS 100
3.3.3.1
3.3.3.3
1.1.1.2
Miami
Boston
2. Use the neighbor shutdown command, in Router Configuration mode, to
terminate any active session for a specified BGP neighbor or peer group and
remove all associated routing information:
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} shutdown
where:
Examples
The following example terminates the active session for the neighbor 156.40.20.23:
MOT:7A(config-bgp)#neighbor 156.40.20.23 shutdown
The following example terminates all peering sessions for the peer group PACIFIC:
MOT:7A(config-bgp)#neighbor PACIFIC shutdown
BGP Routing Policy
Routing policies are usually defined by route-maps, filter lists, and distribution lists.
Route-maps define the conditions for advertising and learning routes from one router
to another and for redistributing routes from one routing protocol to another (for
example, between BGP and OSPF).
The following topics are discussed:
Configuring the Community Attribute
Creating Community Lists
Note: In the case of a peer group, use of the neighbor shutdown command
may suddenly terminate a large number of peering sessions.
A route-map consists of a set of route-map commands, match statements defining
conditions that a route must meet, and set statements defining the conditions that
apply to a route.
To define a route-map, use the route-map command in Global Configuration mode:
MOT:7A(config)#route-map <WORD> [permit | deny] [<0-65535>]
where:
WORD uniquely identifies a route-map.
permit specifies the route is considered for further operation.
deny specifies the route is not considered for further operation.
0-65535 uniquely identifies an instance of the route-map. Instances with lower
sequence numbers are parsed first.
Match and Set Statements
Match statements define the conditions that must be met by a route. Each instance
may contain multiple match statements. If all match statements within a given
instance match for a given route, the route meets the conditions of the instance.
Therefore, the ordering of match statements within an instance does not matter. If an
instance has no match statements, all routes meet the conditions of the instance
(unless they are denied by an instance with a lower sequence-number).
Set statements define the conditions that are applied to the route. If the match
conditions of a given instance are met by a route, all set statements within the instance
are applied to the route. Therefore, the ordering of set statements within an instance
does not matter since either all or none are applied.
If an instance has no set statements and all the match statements in the instance match,
nothing is set for the route. The route is simply redistributed, advertised, or learned as
is (depending on where the route-map is applied).
Table 7-1 lists the match commands for creating route-maps.
Table 7-1 match Commands
Command Description
match as-path Matches a BGP AS-path access list.
match community Matches a BGP community list.
Table 7-2 lists the set commands for creating route-maps.
Example
The commands in the following example, executed from Global Configuration
mode, create the route-map, locpref, and apply the route-map to a BGP neighbor.
The route-map, locpref, sets the local preference to 50 for BGP updates. The
route-map also uses AS-path access list 1 to permit any update whose AS-path
attribute begins and ends with 400.
MOT:7A(config)#route-map locpref permit 10
MOT:7A(config)#match as-path 1
MOT:7A(config)#set local-preference 50
MOT:7A(config)#route-map locpref permit 20
MOT:7A(config)#exit
match ip address Matches an IP access list.
match ip next-hop Matches the next-hop ip address.
match metric Matches a routing metric value. For BGP,
this is the MED.
match ip route-src Matches neighbor IP address.
Table 7-2 set Commands
Command Description
set as-path prepend Modifies an AS-path.
set comm_list Removes selected communities.
set community Sets the BGP community attribute.
set ip next-hop Sets the next-hop attribute of a route.
set local-preference Set the local preference value.
set metric Set the metric. For BGP, this is the MED.
set origin Set the BGP origin.
set weight Set weight of the route.
Table 7-1 match Commands
Command Description
These commands, also executed from Global Configuration mode, create
AS-path access list 1:
MOT:7A(config-bgp)#ip as-path access-list 1 permit ^400
These commands, also executed from Global Configuration mode, apply the
route-map to a BGP neighbor:
MOT:7A(config-bgp)#neighbor 160.20.30.4 route-map locpref in
MOT:7A(config-bgp)#exit
An access list is a sequential collection of permit and deny conditions. The BSR tests
conditions one-by-one against conditions in an access list. The following types of
access-lists are described:
standard access list
AS-path access list
Configuring a Standard Access List
Use the access-list command, in Global Configuration mode, to define access list
entry:
MOT:7A(config)#access-list <1-99> {permit | deny} {<A.B.C.D> [<A.B.C.D>] |
any | host <A.B.C.D>}
where:
A.B.C.D is the source IP address.
A.B.C.D is the network wildcard bits of the source address.
any match against any IP address.
host A.B.C.D is a single source host.
Permit and deny conditions in an IP access list apply to IP addresses. Use the
neighbor distribute-list command to apply an access list to a BGP neighbor.
Example
This sample configuration filters BGP updates from a BGP neighbor. The
following commands, executed in Global Configuration mode, configure standard
Access List 4 by specifying its permit and deny conditions. Access list 4 prohibits the
propagation of networks specified in the deny statements (10.0.0.0, 162.15.0.0, and
180.10.0.0) and permits all others.
MOT:7A(config)#access-list 4 deny 10.0.0.0 0.255.255.255
MOT:7A(config)#access-list 4 permit any
The following commands, also executed in Global Configuration mode, enable BGP,
specify an AS, and apply Access List 4 to a neighbor. The example instructs the router
to pass all network information received from the BGP neighbor 156.30.10.22
through access list 4.
MOT:7A(config-bgp)#neighbor 156.30.10.22 distribute-list 4 in
Configuring an AS-Path Access List
Autonomous System (AS) paths can be applied to an AS-path access list by using
permit and deny arguments. The neighbor filter-list command applies an AS-path
access list for inbound and outbound updates to a BGP neighbor. The match AS-path
command adds a match clause to a route-map.
Use the ip as-path access-list command, in Global Configuration mode, to define an
AS-path access list:
MOT:7A(config)#ip as-path access-list <1-199> {permit | deny} <LINE>
where:
permit specifies the packets to forward from the specified access list.
deny specifies the packets to reject from the specified access list.
LINE is a valid AS-path regular expression.
Note: Any type of list always has an assumed deny all entry as the last
statement. If there are no matches at the end, the route or match (depending
on the type of list and/or how it is used) is denied.
Example
The commands in the example below configure a router with two AS-path access
lists. Routes that pass AS-path access list 1 are sent to one destination. Routes that
pass AS-path access list 2 are accepted from another destination. The commands,
executed in Global Configuration mode, specify permit and deny conditions for
AS-path access lists 1 and 2.
MOT:7A(config)#ip as-path access-list 1 permit _200
MOT:7A(config)#ip as-path access-list 1 permit ^100
MOT:7A(config)#ip as-path access-list 2 deny _690
MOT:7A(config)#ip as-path access-list 2 permit .*
The next command, executed in Global Configuration mode, enables BGP, specifies
an AS, and enters Router Configuration mode.
The following commands, executed in Router Configuration mode, define two
neighbor peers and assign AS-path access lists.
MOT:7A(config-bgp)#neighbor 156.30.10.22 filter-list 1 out
MOT:7A(config-bgp)#neighbor 160.25.15.10 filter-list 2 in
Configuring the Community Attribute
A community is a group of routers that share a common policy. BGP defines the
following well-known community attributes which determine how routes are
advertised:
no-export advertises a route to IBGP peers only (peers within the local AS).
no advertise does not advertise a route to any peer.
local-AS advertises a route only to peers in the same local confederation.
internet is the default community to which all destinations belong.
Members of a community can be on different networks and in different ASs. A router
can belong to more than one community. Community attributes are sent in BGP
updates. Create a route-map and use the set community command to set the
community attributes. Use the neighbor send-community command to send the
community attributes to a neighbor.
Examples
The following commands set the value of the community attribute:
MOT:7A(config)#route-map 20 permit 10
MOT:7A(config-bgp)#match ip address 1
MOT:7A(config-bgp)#set community no-advertise
MOT:7A(config-bgp)#match as-path 2
MOT:7A(config-bgp)#set community 300 additive
The following commands use the neighbor send-community command to send the
community attribute to a neighbor:
MOT:7A(config-bgp)#neighbor 5.5.5.5 send-community
MOT:7A(config-bgp)#neighbor 5.5.5.5 route-map 20 out
Creating Community Lists
Community lists are sequential collections of conditions consisting of permit and
deny statements. Each condition specifies the community number to be matched.
The order of the conditions is important as the router stops testing conditions after the
first matched condition. If no conditions match, the router drops the route.
The ip community-list command is used to create a BGP community access list. The
following describes options with the ip community-list command:
1. To create a community list that globally accepts or rejects all advertisements, use
the ip community-list command in Global Configuration mode:
MOT:7A(config)#ip community-list <1-99> {permit | deny} <1-4294967295>
where:
1-99 is a standard number that identifies a community list.
permit indicates accept the advertisements.
deny indicates reject the advertisements.
1-4294967295 is one or more community numbers.
2. To create a community list that accepts or rejects advertisements within the local
AS community, use the ip community-list local-as command in Global
Configuration mode, as shown below:
MOT:7A(config)#ip community-list <1-99> {permit | deny} local-as
where:
local-as indicates the well-known community Local-AS.
3. To create a community list that accepts or rejects advertisements within the
well-known community Internet, use the ip community-list internet command
in Global Configuration mode, as shown below:
MOT:7A(config)#ip community-list <1-99> {permit | deny} internet
where:
internet is the name of the Internet community.
4. To create a community list that does not advertise to any internal and external
peers, use the ip community-list no-advertise command in Global Configuration
mode, as shown below:
MOT:7A(config)#ip community-list <1-99> {permit | deny} no-advertise
where:
no-advertise indicates do not advertise to any peer internal or external.
5. To create a community list that accepts or rejects advertisements from an AS, or
to advertise a route to IBGP peers only, use the ip community-list no-export
command in Global Configuration mode, as shown below:
MOT:7A(config)#ip community-list <1-99> {permit | deny} no-export
where:
no-export indicates routes are advertised to peers in other sub-autonomous
systems within a confederation.
Example
This example uses a community list to filter routes based on the local preference. The
following commands, executed in Global Configuration mode, define a community
list. Specify community list 1 to permit routes from AS 100 and community list 2 to
permit routes from AS 200, as shown in Figure 7-6.
MOT:7A(config)#ip community-list 1 permit 100
MOT:7A(config)#ip community-list 2 permit 200
The next commands, also executed in Global Configuration mode, define the first
instance of the route-map with the appropriate match and set clauses and specify
route-map 10, instance 10. This permits the route to be accepted and its local
preference to be set to 50. The last command indicates that the route is part of the
communities defined in Community List 1.
MOT:7A(config)#match community 1
MOT:7A(config)#set local preference 50
The following commands define the second instance of the route-map, route-map 10
to permit the route to be accepted and its local preference to be set to 25 if the route is
part of the communities defined in Community List 2.
MOT:7A(config)#match community 2
MOT:7A(config)#set local preference 25
The following commands, executed from Global Configuration mode, enable BGP
and specify an AS. As indicated in Figure 7-6, they specify the AS for Router Boston
in AS 100. The AS of the BGP neighbors, New York and Miami, is specified. Finally,
the route-map 10 is applied for all incoming routes from router New York and Miami.
MOT:7A(config-bgp)#neighbor 3.3.3.1 route-map 10 in
It is assumed that the NY and Miami routers set their outgoing routes (to Boston) to
belong to communities 200 and 300, respectively.
Figure 7-6 Using a Community List
3.3.3.2
AS 100
160.20.0.0
2.2.2.2
Miami
Boston
NY
bgp0002
AS 200
160.30.0.0
AS 300
160.40.0.0
3.3.3.1
2.2.2.1
BGP Path Selection and Configuration
BGP selects the best possible path for a route and installs it in its route table. If only
one route exists for a specific destination, BGP selects that route, because, by
definition, it is the best route. If multiple routes exist, BGP uses the BGP Path
Selection Algorithm to select the best path.
The following topics are discussed:
BGP Path Selection Algorithm
Configuring Next Hop Processing
Configuring Aggregate Addresses
Configuring BGP Administrative Weights
Configuring the Local Preference
Understanding the Origin Attribute
Understanding the AS-path Attribute
Configuring the MED Attribute
BGP Path Selection Algorithm
The BGP path selection process uses the following sequential criteria to select a path:
1. If the next hop is inaccessible, BGP does not consider the route. To configure the
next hop, use the neighbor remote-as command or the neighbor next-hop-self
command.
2. If IGP synchronization is enabled and the route is not in an IGP, BGP ignores the
route.
3. BGP uses the route that was locally originated, using either the network or
aggregate-address command, or through redistribution from an IGP.
4. BGP uses the path with the largest weight, a value ranging from 0 to 65535. The
administrative weight is local to the router. BSR originating paths have a weight
of 32768 by default; other paths, from peers, have a default weight of 0. To
configure specific neighbors as preferred for most traffic, use the neighbor
weight command to assign a higher weight to all routes learned from that
neighbor. You can also assign weights based on AS-path access lists. A given
weight becomes the weight of the route, if the AS-path is permitted by the access
list. Any number of weight filters are allowed.
5. BGP uses the route with the largest local preference. Define a particular path as
more preferable or less preferable than other paths by changing the default local
preference value of 100. To assign a different default local preference value, use
the bgp default local-preference command.
6. BGP uses the route with the shortest AS-path.
7. BGP uses the route with the lowest origin type. IGP is lower than EGP, and EGP
is lower than INCOMPLETE.
8. BGP uses the route with the lowest MED. The comparison is made only if the
neighboring AS is the same, except when the bgp always-compare-med
command is enabled.
9. BGP uses the route with the lowest IGP metric to the BGP next hop.
10. BGP prefers EBGP over IBGP. All confederation paths are considered IBGP.
11. If the best route and a new route are both external and maximum-paths is
enabled, BGP inserts the new route into the IP routing table as an alternate path.
EBGP multipath load sharing can occur at this point. The forwarding table holds
1 to 2 paths.
12. BGP prefers the path with the lowest IP address specified by the BGP router ID.
Configuring Next Hop Processing
The BGP next hop attribute is the IP address of the next hop. It can be specified with
the neighbor remote-as command. You can also use the neighbor next-hop-self
command to specify the router itself.
neighbor remote-as Command
Use the neighbor remote-as command, in Router Configuration mode, to configure
next hop processing:
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} remote-as <1-65535>
where:
1-65535 is the AS number of the neighbor AS.
In the network shown in Figure 7-7, Router SF advertises network 172.56.0.0 to
Router Miami with a next hop attribute of 172.56.20.1. Router Miami advertises
network 120.80.0.0 to Router SF with a next hop attribute of 172.56.20.2.
In BGP, the next hop of EBGP-learned routes is carried without modification in
IBGP. Because of this BGP rule, Router Miami advertises 172.56.0.0 to its IBGP peer
(Router NY) with a next hop attribute of 172.56.20.1. As a result, according to Router
NY, the next hop to reach 172.56.0.0 is 172.56.20.1 instead of 120.80.20.1 via an
IGP. Router NY drops packets destined for 172.56.0.0, if the next hop 172.56.20.1 is
not reachable via IGP.
Figure 7-7 Configuring Next Hop Processing
The following commands configure Router Miami:
AS 100
120.80.0.0
AS 300
172.56.0.0
SF
bgp0012
NY
EBGP
IBGP
Miami
172.56.20.1
172.56.20.2
120.80.30.2
120.80.30.1
The following commands configure Router NY:
The following commands configure Router SF:
neighbor next-hop-self Command
Use the neighbor next-hop-self command, in Router Configuration mode, to
configure next hop processing for routers not on the same IP subnet or in a Frame
Relay environment:
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} next-hop-self
where:
WORD is the name of the neighbor peer group.
Example
The following commands configure Router SF as shown in Figure 7-8:
MOT:7A(config-bgp)#neighbor 172.56.10.1 next-hop-self
Figure 7-8 Using the neighbor next-hop-self Command
Configuring Aggregate Addresses
Using Classless Inter-Domain Routing (CIDR) addressing, you can combine routes so
that multiple routes are advertised as a single route. CIDR replaces the concept of
classes (such as Class A, Class B, and Class C) with the concept of IP prefixes. An IP
prefix is a network address that indicates the number of bits that comprise the network
number.
Use the following options to configure aggregate addresses:
Use the aggregate-address command, in Router Configuration mode, to combine
multiple routes:
MOT:7A(config-bgp)#aggregate-address <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the aggregate IP address.
A.B.C.D is the aggregate IP subnetwork mask.
AS 100
172.24.0.0
bgp0013
172.24.50.1
172.56.10.1
172.24.30.1
Miami
NY
AS 200
172.30.0.0
172.56.10.3
172.56.10.2
SF
Frame Relay
Network
Washington
Use the aggregate-address advertise-map command, in Router Configuration
mode, to identify the route-map for selecting routes to be aggregated:
advertise-map <WORD>
where:
Use the aggregate-address as-set command, in Router Configuration mode, to
generate autonomous system path information for the aggregate IP address based
on the routes selected for aggregation:
MOT:7A(config-bgp)#aggregate-address <A.B.C.D> <A.B.C.D> as-set
where:
A.B.C.D is the aggregate IP mask.
Use the aggregate-address attribute-map command, in Router Configuration
mode, to identify the route-map for manipulating the attributes of the aggregate
route:
attribute-map <WORD>
where:
Use the aggregate-address summary-only command, in Router Configuration
mode, to filter all more specific routes from updates:
summary-only
where:
Use the aggregate-address suppress-map command, in Router Configuration
mode, to specify the route-map for selectively blocking routes:
suppress-map <WORD>
where:
A.B.C.D is the aggregate IP mask.
Example
Network 200.10.0.0 is an illegal Class C network address. This address becomes legal
when it is represented in CIDR notation as 200.10.0.0/16. The /16 specifies that the
subnet mask consists of 16 bits (counting from left to right). Thus, the CIDR address,
200.10.0.0/16, is the same as 200.10.0.0 with a network mask of 255.255.0.0.
MOT:7A(config-bgp)#aggregate-address 200.10.0.0 255.255.0.0
Configuring BGP Administrative Weights
You can assign a weight to a neighbor connection if more than one route exists for the
same destination. A weight indicates a preference for a particular route; a higher
weight indicates a preferred route. Initially, all routes learned from the neighbor have
the assigned weight. The BSR chooses the route with the highest weight as the
preferred route if multiple routes exist for a particular network.
In Figure 7-9, Routers Boston and NY learn about network 160.80.0.0 from AS200.
Router Boston and NY propagate the update to Router LA. Router LA has two routes
for reaching 160.80.0.0 and must determine the appropriate route. On Router LA, if
you set the weight of updates coming from Router Boston to be higher than the
updates coming from Router NY, then Router LA uses Router Boston as the next hop
to reach network 160.80.0.0.
Figure 7-9 Assigning a Weight to a Neighbor Connection
Use the following commands to assign a weight to a neighbor connection:
neighbor weight
neighbor filter-list
neighbor route-map
The weights assigned with the route-map commands, match as-path and set weight,
override the weights assigned using the neighbor weight and neighbor filter-list
commands.
Using the neighbor weight Command
Use the neighbor weight command, in Router Configuration mode, to change the
weight attribute of all route updates received from a specific AS:
AS 400
192.56.0.0
Boston
LA
AS 200
160.80.0.0
Albany
NY
bgp0030
AS 300
192.24.0.0
AS 100
150.60.0.0
4.4.4.1
3.3.3.1
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} weight <0-65535>
where:
0-65535 is the assigned weight.
Example
For example, the commands in the following example configure Router LA (as shown
in Figure 7-9) using the neighbor weight command. This configuration assigns the
weight attribute of 1000 to all route updates received from AS 100 and assigns 500 to
the weight attribute of all route updates from AS 300. This causes Router LA to send
traffic through Router Boston to destinations reachable via both the ASs.
MOT:7A(config-bgp)#neighbor 3.3.3.1 weight 1000
MOT:7A(config-bgp)#neighbor 4.4.4.1 weight 500
Using Filter-lists and AS-Path Access Lists
The commands in the following example configure Router LA using an AS-path
access list. Filter List 1 assigns a weight attribute of 1000 to updates received from
neighbors in AS 100. Access List 1 permits any update whose AS-path attribute
begins with 100 (specified by ^). The same is true for Access List 2 regarding AS
300. Filter List 2 assigns a weight attribute of 500 to updates received from AS 300.
Example
MOT:7A(config-bgp)#neighbor 3.3.3.1 filter-list 1 weight 1000
MOT:7A(config-bgp)#neighbor 4.4.4.1 filter-list 2 weight 500
Using a Route-map and Access Lists
The commands in the following example configure Router LA using a route-map. In
the commands to configure Router LA, Instance 10 of route-map 10 assigns a weight
of 1000 to any updates from AS 100. Instance 20 assigns a weight of 500 to updates
from any other AS.
Example
MOT:7A(config)#match as-path 1
MOT:7A(config)#set weight 1000
MOT:7A(config)#set weight 500
Configuring the Local Preference
When multiple paths exist to the same destination, the local preference specifies the
preferred path. The preferred path is the one with the higher preference value. To
configure the local preference of a BGP path, perform one of the following steps.
1. Use the bgp default local-preference command, in Router Configuration mode,
to set the default local preference attribute in BGP updates:
MOT:7A(config-bgp)#bgp default local-preference <04294967295>
where:
04294967295 is the local preference number.
2. Use a route-map to set the local preference attribute.
Example: Setting the Local Preference
This example configures Routers NY and Boston so that AS 100 receives updates for
network 156.10.0.0 from AS 200 and AS 400 (as shown in Figure 7-10).
Figure 7-10 Configuring the Local Preference Attribute
Router NY sets the local preference for all updates from AS 200 to 125. Router
Boston sets the local preference for all updates from AS 400 to 200. Because Router
NY and Router Boston exchange local preference information within AS 100, they
recognize that updates regarding network 156.10.0.0 have higher local preference
when they come to AS 100 from AS 400 than from AS 200.
MOT:7A(config-bgp)#bgp default local-preference 125
The following commands configure Router Boston:
MOT:7A(config-bgp)#bgp default local-preference 200
AS 200
AS 300
Chicago
AS 400
LA
bgp0019
AS 100
IBGP
Boston
NY
AS 500
Washington
192.56.10.2
192.30.10.1
192.30.10.2
192.56.10.1
156.10.0.0
140.20.30.2
140.20.30.1
Example: Using a Route-map to Set the Local Preference
A route-map setting the local preference allows more flexibility in determining
updates from a specific AS. In the previous example, all updates received by Router
Boston are set to a local preference of 200 (including updates from AS 500).
Use a route-map to specifically assign a local preference for updates from AS 400.
The following commands specify that the local preference attribute is set to 200 for
updates specifically coming from AS 300 through AS 400:
MOT:7A(config-bgp)#ip as-path access-list 1 permit ^400 300$
MOT:7A(config-bgp)#route-map 10 permit 10
MOT:7A(config-bgp)#match as-path 1
MOT:7A(config-bgp)#set local-preference 200
Understanding the Origin Attribute
The Origin attribute indicates the route origin and is one of the following values:
IGP indicates that the route was learned via an Interior Gateway Protocol (IGP)
and, therefore, is interior to the originating AS.
EGP indicates that the route was learned via Exterior Gateway Protocol (EGP).
Incomplete indicates that the origin of the route is unknown. It was learned
from something other than IGP or EGP. Incomplete origin occurs when a route is
redistributed into BGP. This value most often appears for static routes.
Example
Figure 7-11 shows a BGP network consisting of two ASs, AS 100 and AS 300. AS
100 is configured to run IBGP between Routers NY and Boston. Routers Boston and
LA are configured to run EBGP.
Figure 7-11 Origin Attribute Network Example
Table 7-3 gives the origin attributes of various routes with respect to Routers NY,
Boston, and LA.
Table 7-3 Origin Atrributes
Router Route Origin Attribute
Boston 150.20.0.0 Incomplete
Boston 175.40.30.0 IGP
Boston 192.56.0.0 EGP
NY 150.20.0.0 IGP
NY 192.56.0.0 IGP
LA 175.40.30.0 EGP
LA 150.20.0.0 EGP
AS 100
AS 300
192.56.0.0
LA
bgp0020
Albany
NY
IGP
Boston
EGP
1.1.1.2
1.1.1.1
175.40.30.1
150.20.20.1
150.20.30.1
MOT:7A(config-bgp)#redistribute static
The following commands configure Router LA:
Understanding the AS-path Attribute
When a BGP route passes through an Autonomous System (AS), BGP prepends its
AS number to the route. The AS-path attribute contains the list of ASs that a route has
gone through.
In Figure 7-12, Router Boston advertises network 150.60.0.0 to AS 400 with an
AS-path of 100. When the BGP route arrives in AS 400, Router LA adds its AS
number. When the BGP route arrives at Router NY, its AS-path attribute contains AS
numbers 400 and 100.
Figure 7-12 The AS-path Attribute
Boston
NY
bgp0021
AS 300
192.55.0.0
AS 100
150.60.0.0
3.3.3.2
AS 400
192.56.0.0
LA
Configuring the MED Attribute
The Multi-exit Discriminator (MED) attribute is a metric that expresses a degree of
preference for a particular route. By default, the BSR compares MED attributes only
among paths from the same AS.
Use the bgp always-compare-med command on the receiving router to enable
comparison of MED attributes from different neighbors in different ASs. On the
sending routers, configure a route-map with a set metric command to set a MED
attribute. Routes with lower MED values are preferred.
Example
In Figure 7-13, Routers LA, NY, and Boston send updates regarding network
155.30.0.0 to Router Chicago. They are configured with MED attributes. Router
Chicago is also configured to compare MED attributes of routes coming from external
neighbors. Router Chicago prefers the route from Router LA since the MED attribute
coming from Router LA has the lowest MED value.
Figure 7-13 Configuring the MED
AS 100
155.30.0.0
AS 200
192.56.0.0
AS 300
LA
bgp0022
NY
3.3.3.2
6.6.6.1
155.30.0.0
MED=25
155.30.0.0
MED=150
155.30.0.0
MED=100
3.3.3.1
Boston
Chicago
7.7.7.2
4.4.4.1
5.5.5.1
5.5.5.2
7.7.7.1
4.4.4.2
6.6.6.2
The following commands configure Router LA:
MOT:7A(config)#set metric 25
In the following commands, the bgp always-compare-med command enables MED
comparison in Router Chicago:
MOT:7A(config-bgp)#bgp always-compare-med
Managing BGP
Beyond basic BGP and routing policy configuration, there are additional
configuration tasks that may be required to maintain and manage BGP. The following
configuration topics are described:
Configuring a Default Route
Assigning a Loopback Interface to a BGP Session
Enabling Message Digest 5 Authentication Between Peers
Adjusting BGP Timers
Setting the Routing Updates Interval
Controlling the Number of Prefixes
Setting the Administrative Distance for a Route
Disabling Route Summarization
Enabling and Disabling Synchronization
Redistributing Routes into BGP
Configuring Route Flap Dampening
Reconfiguring BGP
Large Scale Asynchronous Systems
Configuring a Confederation
Configuring a Route Reflector
Configuring a Default Route
A default route in a router IP forwarding table is used by the router if a routing entry
for a destination does not exist. Any AS advertising the default route represents itself
as the gateway of last resort to other systems.
Use the neighbor default-originate route-map command, in Router Configuration
mode, to target the default route to a specific BGP neighbor so that only that router
receives the default advertisement:
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} default-originate
route-map [<WORD>]
where:
WORD is name of the route-map. The route-map allows route 0.0.0.0 to be
injected conditionally.
It is important to control defaults in BGP, because a BGP neighbor, in an attempt to
advertise a default route to a specific peer, may send the default to all of its neighbors.
Example
In Figure 7-14, Router Boston originates the default route 0.0.0.0 toward Router
Miami only. Router Chicago does not receive the default route.
MOT:7A(config-bgp)#network 150.20.30.0 255.255.255.0
MOT:7A(config-bgp)#neighbor 150.20.20.1 default-originate
Figure 7-14 Dynamically Configuring a Default Route
AS 100
AS 200
Miami
bgp0018
Chicago
EBGP
IBGP
Boston
150.20.20.1
150.20.20.2
150.20.30.1
Assigning a Loopback Interface to a BGP Session
Loopback interfaces are often used by IBGP peers. The advantage of using loopback
interfaces is that they eliminate operational status and negotiated address
dependencies that result from using the IP address of a physical interface on the router
to configure BGP. Loopback interfaces are rarely used between EBGP peers because
they are usually directly connected and depend on a specific interface for
connectivity. The neighbor update-source loopback command is used to allow a
BGP session to use any operational interface for TCP connections by specifying an IP
address or peer-group and the proper interface. This feature is often used in
conjunction with loopback interfaces.
Use the neighbor update-source loopback command, in Router Configuration
mode, to assign a loopback interface to the BGP session:
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} update-source loopback
<1-255>
where:
loopback indicates the interface type.
1-255 is the loopback interface number.
Example
Figure 7-15 shows a network that can benefit from the use of a loopback interface,
because an alternate path exists. Routers NY and Albany are running IBGP within
AS 100. Router NY specifies the IP address of the loopback interface (160.10.0.1) of
Router Albany in the neighbor remote-as command. Router Albany is configured
with the neighbor update-source loopback command so that the source of BGP TCP
connections for the specified neighbor (NY) is the IP address of the loopback
interface instead of the IP address of a physical interface. This eliminates the
dependency on the physical interface. If a cable break occurs on S0, the connection
can still be maintained via S1, provided IP connectivity still exists to the loopback.
Note: The loopback interface is unrelated to the IP loopback address
127.x.x.x.
Figure 7-15 Using a Loopback Interface
The following commands configure a loopback interface for Router Albany:
MOT:7A(config)#interface loopback 0
MOT:7A(config-if)#ip address 160.10.0.1 255.255.255.255
MOT:7A(config-if)#exit
MOT:7A(config-bgp)#neighbor 192.56.42.10 update-source loopback
0
Enabling Message Digest 5 Authentication Between Peers
You can enable Message Digest 5 (MD5) authentication between two BGP peers,
causing each segment sent on the TCP connection between them to be verified. You
must configure the same password on both BGP peers; otherwise, the connection
between them is not made. The authentication feature uses the MD5 algorithm
command that causes the generation and checking of the MD5 digest on every
segment sent on the TCP connection. Configuring a password for a neighbor
terminates an existing session and establishes a new one. If you specify a BGP peer
group using the name argument, all the members of the peer group inherit the
characteristic configured with this command.
Albany
Boston
S0
S1 Loopback interface 0: 160.10.0.1
NY
Use the neighbor password command, in Router Configuration mode, to enable
MD5 authentication:
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} password {0 | 7}
<string>
where:
0 specifies that an UNENCRYPTED password follows.
7 specifies that an ENCRYPTED password follows.
string is a case-sensitive password of up to 32 alphanumeric characters. The first
character cannot be a number.
Example
The commands in the following example enable the authentication feature between a
router and the BGP neighbor at 122.35.3.1. The password that must also be
configured for the neighbor is mypassword.
MOT:7A(config-bgp)#neighbor 122.35.3.1 password 0 mypassword
Adjusting BGP Timers
Keepalive messages are exchanged between BGP neighbors or peer groups to monitor
the health of the link between them. If a BGP peer does not receive a keepalive
message, it waits for a configured holdtime before the ailing BGP peer is declared
dead by its waiting peer.
BGP supports the following two commands that set the frequency of keepalive and
holdtime timers:
timers bgp globally sets the keepalive timers for BGP
neighbor timers sets the keepalive timers for a BGP peer or peer group
Use the timers bgp command, in Router Configuration mode, to configure the
keepalive frequency and holdtime interval globally for BGP:
MOT:7A(config-bgp)#timers bgp <0-21845> [<0-65535>]
where:
0-21845 is the frequency in seconds that the BSR sends keepalive messages to its
peers. The default is 60 seconds.
0-65535 is the optional holdtime, which is the interval in seconds, after which,
not receiving a keepalive or any other BGP message, the BSR declares a BGP
peer dead.
Use the neighbor timers command, in Router Configuration mode, to configure the
keepalive frequency and holdtime interval for a BGP peer or peer-group:
MOT:7A(config-bgp)#neighbor [<A.B.C.D> | <WORD>] timers <0-21845>
[<0-65535>]
where:
0-21845 is the frequency, in seconds, that the BSR sends keepalive messages to
its peers. The default is 60 seconds.
0-65535 is the interval a BSR waits to receive a keepalive message before it
declares a BGP peer dead. The default is 180 seconds.
Example
The commands in the following example, configure the keepalive frequency and
holdtime interval for BGP on a BSR and configure the keepalive frequency and
holdtime interval for a BGP peer:
MOT:7A(config-bgp)#timers bgp 80 200
MOT:7A(config-bgp)#neighbor 192.56.20.2 timers 80 200
Setting the Routing Updates Interval
Use the neighbor advertisement-interval command, in Router Configuration mode,
to set the minimum interval between the sending of BGP routing updates to neighbors
or peer groups. Lower values for the advertisement interval cause route changes to be
reported more quickly. However, use caution because this action may cause the
routers to use more bandwidth.
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} advertisement-interval
<0-600>
where:
0-600 is the advertisement interval time in seconds, default = 30 sec. for
external peers and default = 5 sec. for internal peers.
Example
The commands in the following example set the minimum time between sending BGP
routing updates to 4 seconds:
MOT:7A(config-bgp)#neighbor 3.3.3.3 advertisement-interval 4
Controlling the Number of Prefixes
Use the neighbor maximum-prefix command, in Router Configuration mode, to
control the number of prefixes received from a neighbor router:
MOT:7A(config-bgp)#neighbor {<A.B.C.D> | <WORD>} maximum-prefix
[<1-65536> [<1-100 > | warning-only ]
where:
1-65536 is the maximum number of prefixes allowed from this neighbor.
1-100 is the percent of the maximum at which the router generates a warning
message. The default is 75 percent.
warning-only gives a warning message when the limit is exceeded instead of
shutting down the peer.
Example
The commands in the following example set the maximum prefix to 900:
MOT:7A(config-bgp)#neighbor 1.1.1.1 maximum-prefix 900
Setting the Administrative Distance for a Route
An administrative distance is a rating of the trustworthiness of a routing information
source, such as a router or group of routers. The administrative distance is an integer
between 0 and 255 with a higher value indicating a lower trust rating. An
administrative distance of 255 denotes a routing information source that cannot be
trusted and should be ignored. Routes with distances of 255 are not installed in the
routing table.
You can change an administrative distance if you know that another protocol provides
a better route than that learned via EBGP or if you want IBGP to show preference for
internal routes.
Three administrative distance types can be configured with the distance bgp
command:
external for BGP external routes learned from a neighbor external to the AS.
internal for BGP internal routes learned from another BGP router within the
same AS.
local for local networks configured with the network command, often as back
doors for that router or for networks that are redistributed from another process.
Use the distance bgp command, in Router Configuration mode, to set the external,
internal, and local administrative distances for a BGP router:
MOT:7A(config-bgp)#distance bgp [<1-255> <1-255> <1-255>]
where:
1-255 is the administrative distance for BGP routes external to the AS. The
default is 20.
1-255 is the administrative distance for BGP routes internal to the AS. The
default is 200.
1-255 is the administrative distance for local routes. The default is 200.
Note: Changing the administrative distance of BGP internal routes is
dangerous and is not recommended. It can cause the accumulation of routing
table inconsistencies that can break routing within an AS and between ASs.
Example
In the following example, BGP routes are preferable to local routes. The
administrative distance values are set accordingly: 20 for BGP routes external and
internal (to AS 100), and 200 for local routes.
MOT:7A(config-bgp)#distance bgp 20 20 200
Disabling Route Summarization
Route summarization condenses routing information. Without summarization, each
router in a network must retain a route to every subnet in the network. With
summarization, routers can reduce some sets of routes to a single advertisement,
reducing both the load on the router and the perceived complexity of the network. The
importance of route summarization increases with network size. Automatic network
summarization of routes is enabled on the BSR by default.
The reduction in route propagation and routing information overhead is significant.
For example, without summarization, each router in a network with 1,000 subnets
must contain 1,000 routes. With summarization in a Class B network with eight bits
of subnet address space, each router must know all of the routes for each subnet in its
network number. This is 250 routes, assuming that 1,000 subnets fall into four major
networks of 250 routes each. In addition, the router must know one route for each of
the other three networks for a total of 253 routes. This represents a nearly 75 percent
reduction in the size of the routing table.
In Figure 7-16, Router Albany maintains one route for all destination networks
beginning with B, and Router Chicago maintains one route for all destination
networks beginning with A. This is the essence of route summarization. Router New
York tracks all routes because it exists on the boundary between A and B.
Figure 7-16 Route Summarization
Boston
Albany
B1
B2
B4
A1
A5
Destination
A1
A2
A3
A4
A5
B1
B2
B3
B4
A3
A2
A4
B3
Router New York's routing table
Chicago
bgp0016
Next hop
Direct
Direct
Boston
Albany
Boston
Direct
Chicago
Chicago
Chicago
Destination
A1
A2
A3
A4
A5
B
Router Albany's routing table
Next hop
Direct
Direct
NY
Direct
Boston
NY
Destination
B1
B2
B3
B4
A
Router Chicago's routing table
Next hop
Direct
Direct
Direct
Direct
NY
New
York
To disable automatic network summarization of routes, use the no auto-summary
command in Router Configuration mode:
MOT:7A(config-bgp)#no auto-summary
Example
The commands, in the following example, disable automatic network summarization
for AS 100:
MOT:7A(config-bgp)#no auto-summary
Enabling and Disabling Synchronization
Synchronization is a feature of BGP that prevents a BGP speaker from advertising a
route before all routers within an AS have learned the route. Without synchronization,
traffic may be dropped as a result of intermediate non-BGP routers not having learned
routes when the AS provides transit service to other ASs.
Usually, a BGP speaker does not advertise a route to an external neighbor unless that
route is local or exists in the IGP. This feature allows routers within an AS to learn the
route before BGP makes it available to other ASs. The no synchronization command
disables synchronization and allows the BGP router to advertise a network route
without waiting to learn it via IGP.
Figure 7-17 shows a situation that demonstrates the value of synchronization. Router
LA sends updates about network 192.56.0.0 to Router Boston. Router NY receives
updates about network 192.56.0.0 from Router Boston via IBGP. Router NY wants to
reach network 192.56.0.0 and sends traffic to Router Albany. If Router Boston does
not distribute network 192.56.0.0. into an IGP, IBGP in this case, Router Albany
cannot know that network 192.56.0.0 exists. Router Albany drops the packets from
Router NY destined for network 192.56.0.0. In addition, Router NY advertises to AS
200 that it can reach 192.56.0.0 before Router Albany learns about the network via
IBGP. This means that traffic coming from Router Chicago to Router Albany through
Router NY with a destination of 192.56.0.0 is dropped.
Synchronization solves this problem by not allowing BGP to advertise a route before
all routers within the same AS have learned about the route. In Figure 7-17, Router
NY waits to hear about network 192.56.0.0 before it sends an update to Router
Chicago.
Figure 7-17 Synchronization
If your AS does not pass traffic from one AS to another or if all the transit routers in
your AS run BGP, use the no synchronization command, in Router Configuration
mode, to disable synchronization:
MOT:7A(config-bgp)#no synchronization
Example
The commands in the following example configure a router with synchronization
disabled:
MOT:7A(config-bgp)#no synchronization
AS 100
AS 300
192.56.0.0
LA
bgp0014
Albany
NY
IBGP
Boston
AS 200
Chicago
Redistributing Routes into BGP
redistributed to advertise networks on another routing protocol. Figure 7-18 shows
Router NY redistributes the routes learned through OSPF protocol from Routers
Boston and LA into BGP.
Figure 7-18 Redistributing Routes Learned from OSPF
Follow these steps to redistribute routes into BGP:
1. Enter the BGP routing process in which the routes are to be redistributed:
where:
1-65535 is the Autonomous System (AS) number.
specified protocol:
AS 100
AS 200
SF
bgp0001
LA
Boston
OSPF
OSPF
EBGP
OSPF
NY
180.40.20.1
180.40.20.2
Use the redistribute ospf command, in Router Configuration mode, to
redistribute OSPF routes into BGP:
MOT:7A(config-bgp)#redistribute ospf [match {internal | external |
external 1 | external 2}] [metric <0-4294967295>] [route-map <WORD>]
[weight <0-65535>]
where:
internal is used to redistribute internal OSPF routes.
external is used to redistribute external OSPF routes.
external 1 is used to redistribute routes that are external to an AS, but are
imported into OSPF as Type 1 external routes.
external 2 is used to redistribute routes that are external to an AS, but are
imported into OSPF as Type 2 external routes.
metric <0-4294967295> is the redistribution metric number for OSPF
routes.
route-map <WORD> is the OSPF route-map name.
weight <0-65535> sets the network weight value from 0 to 65535 for
redistributing OSPF routes into BGP.
redistribute connected routes into BGP:
MOT:7A(config-bgp)#redistribute connected [metric <0-4294967295>]
[route-map <WORD>] [weight <0-65535>]
where:
metric <0-4294967295> is the redistribution metric number for
connected routes.
route-map <WORD> is the route-map name for the connected route.
redistributing connected routes into BGP
Use the redistribute rip command, in Router Configuration mode, to
redistribute RIP routes into BGP:
MOT:7A(config-bgp)#redistribute rip [metric <0-4294967295>]
[route-map <WORD>] [ weight <0-65535>]
where:
metric <0-4294967295> is the redistribution metric number for RIP
routes.
route-map <WORD> is the route-map name for the RIP route.
redistributing RIP routes into BGP.
BGP:
1. Use the router bgp command to enter the BGP routing process in Global
Configuration mode:
where:
1-65535 is the AS number.
routing protocol to use the same metric value for all distributed routes from other
routing protocols:
MOT:7A(config-bgp)#default-metric <0-4294967295>
where:
0-4294967295 is the default metric value for all routes that are redistributed
into BGP.
Configuring Route Flap Dampening
Route flapping occurs when a link constantly fluctuates between being available and
unavailable. When a link changes its availability, the upstream neighbor sends an
update message to all its neighbors and in turn, these routes are advertised globally.
This process continues until the underlying problem is fixed.
Route flap dampening is a mechanism for minimizing instability caused by route
flapping. When the BSR is configured with the default dampening values, a penalty
value for a route is increased by 1000 if the route flaps and is decreased by half after
15 minutes. Once the penalty exceeds the suppress limit of 2000, the route is no
longer advertised to neighbors. (The route is dampened.) When the penalty for a
dampened route falls below the reuse limit of 750, the route is again available.
The BSR supports two types of route flap dampening.
Global
Policy-based
Global Route Flap Dampening
Use the bgp dampening command, in Router Configuration mode, to globally enable
the default route flap dampening parameters for all BGP routes:
MOT:7A(config-bgp)#bgp dampening
Policy-based Route Flap Dampening
Use the bgp dampening command, in Router Configuration mode, to configure or
change route flap dampening parameters for all BGP routes or specific BGP routes
specified in a route-map:
MOT:7A(config-bgp)#bgp dampening [<1-45> <1-2000> <1-2000> <1-255> |
route-map <WORD>]
where:
1-45 is the half-life period for the penalty enabling route flap dampening in
minutes. The default is 15 minutes.
1-2000 is the number of seconds to start reusing dampened routes. The default is
750 seconds.
1-20000 is the number of seconds to start suppressing a route. The default is 2000
seconds.
1-255 is the maximum number of minutes to suppress a stable route. The default
is four times the half-life.
Example
The following commands create a route-map and apply route flap dampening:
MOT:7A(config-bgp)#route-map dallas permit 10
MOT:7A(config-bgp)#ip as-path access-list 1
MOT:7A(config-bgp)#bgp dampening route-map dallas
These commands specify AS-path access list 1 as the filter to determine the permitted
ASs.
MOT:7A(config)#ip as-path access-list 1 deny ^300
MOT:7A(config)#ip as-path access-list 1 permit any
Clearing Route Flap Dampening
Follow these steps to clear route flap dampening and flap-statistics:
1. Use the clear ip bgp dampening command, in Privileged EXEC mode, to clear
all route dampening information:
MOT:7A#clear ip bgp dampening
2. Use the clear ip bgp dampening command, in Router Configuration mode, to
unsuppress a suppressed route:
MOT:7A(config-bgp)#clear ip bgp dampening <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the network IP address.
A.B.C.D is the network mask applied to the address.
3. Use the clear ip bgp flap-statistics command, in Privileged EXEC mode, to reset
flap statistics information for a BGP neighbor:
MOT:7A#clear ip bgp flap-statistics <A.B.C.D>
where:
A.B.C.D is the BGP neighbor IP address.
Example
The following example clears route dampening information about the route to
network 170.0.0.0 and unsuppresses its suppressed routes. If you do not specify the
address and mask arguments, the clear ip bgp dampening command clears route
dampening information for the entire BGP routing table.
MOT:7A(config-bgp)#clear ip bgp dampening 170.0.0.0 255.255.0.0
Reconfiguring BGP
Once you define two routers to be BGP neighbors, they form a BGP connection and
exchange routing information. If you subsequently change a BGP filter, weight,
route-map, distance, timer, or make a similar configuration change, you must reset
BGP connections for the configuration change to take effect.
The following usage of the clear ip bgp command, in Privileged EXEC mode, forces
a hard clear of BGP sessions:
MOT#clear ip bgp {* | <A.B.C.D> | <WORD>}
where:
* resets all BGP sessions.
A.B.C.D is the BGP neighbor address to clear.
WORD is the BGP neighbor peer group name to clear.
Soft Reconfiguration
To minimize network disruptions, a soft reconfiguration with the clear ip bgp soft
command will enable policy changes without clearing BGP sessions. Inbound soft
reconfiguration needs inbound updates from a neighbor and enables the new inbound
policy to take effect. Outbound soft reconfiguration sends a new set of updates to a
neighbor and causes the new local outbound policy to take effect without resetting the
BGP session. You can configure the BSR to store received updates, a requirement for
inbound BGP soft reconfiguration. Outbound reconfiguration does not require
enabling of inbound soft reconfiguration.
1. Use the clear ip bgp soft in command, in Privileged EXEC mode, to reset a BGP
neighbor or peer group using a software reconfiguration of the inbound route
update:
MOT:7A(config-bgp)#clear ip bgp {* | <A.B.C.D> | <WORD>} soft in
where:
Note: Using the clear ip bgp command to force a hard clear causes cache
invalidation and may cause major disruptions in the network.
2. Use the clear ip bgp soft out command, in Privileged EXEC mode, to reset a
BGP neighbor IP address or peer group using a software reconfiguration of the
outbound route update:
MOT:7A(config-bgp)#clear ip bgp {* | <A.B.C.D> | <WORD>} soft out
where:
Large Scale Asynchronous Systems
Within an Asynchronous Systems (ASs), BGP requires that IBGP peers be fully
meshed. This creates significant routing overhead for each router in the AS as the
number of peers increases.
To simplify the mesh in large ASs, BGP provides two configuration alternatives:
Confederations
Route Reflectors
Configuring a Confederation
You can reduce the IBGP mesh inside an AS by creating a BGP confederation. In
Figure 7-19, AS 400 consists of ten BGP neighbors that, without confederations,
require that the routers be fully meshed. Each of the ten routers runs IBGP with the
other nine routers and connects to an external AS.
Using a confederation, you reduce the number of peers required within AS 400. Each
AS within AS 400 (AS 100, AS 200, and AS 300) must be fully meshed with IBGP
running between its member routers. The ASs within the confederation run a modified
version of EBGP, similar to IGBP. Specifically, the next-hop and local preference
information is preserved. This lets you retain a single IGP for all the ASs in the
confederation. To external ASs, the confederation looks like a single AS, AS 400.
Figure 7-19 Configuring a Routing Domain Confederation
The following commands are used to configure a confederation within an AS:
1. Use the bgp confederation identifier command, in Router Configuration mode,
to specify a BGP confederation identifier:
AS 100
AS 400
AS 500
Salem
bgp0007
7.7.7.2
7.7.7.1
AS 600
Providence
6.6.6.6
Boston
Concord
Hartford
140.100.40.1
160.21.10.1
Denver
Chicago
Seattle
SF
San Diego
Portland
Houston
139.100.20.1
139.100.30.1
140.100.30.1
140.100.20.1
AS 200 AS 300
MOT:7A(config-bgp)#bgp confederation identifier <1-65535>
where:
1-65535 is the AS number that identifies the confederation as one AS that
internally includes multiple ASs.
2. Use the bgp confederation peers command, in Router Configuration mode, to
identify peer ASs that are members of the confederation:
MOT:7A(config-bgp)#bgp confederation peers <1-65535> [<1-65535>]
where:
1-65535 specifies the AS that is a member of the confederation.
Example
The commands in this example configure Routers Hartford, Chicago, and Salem (as
shown in Figure 7-19).
The following commands configure Router Hartford. Router Hartford belongs to
confederation 400 containing AS 200 and AS 300 as its peer ASs. They also specify
neighbor connections with peers in AS 100 and AS 200, and specify an external peer
in AS 500.
MOT:7A(config-bgp)#bgp confederation identifier 400
MOT:7A(config-bgp)#bgp confederation peers 200 300
The following commands configure Router Chicago:
MOT:7A(config-bgp)#bgp confederation identifier 400
MOT:7A(config-bgp)#bgp confederation peers 100 300
The following commands configure Router Salem:
Configuring a Route Reflector
A BGP speaker cannot advertise a route to an IBGP neighbor if that BGP speaker
originally heard the route from another IBGP neighbor. The result of the this rule
requires a full mesh of IBGP sessions within an AS to fully distribute routes via
IBGP. If an AS has many BGP speakers, the number of peer connections can become
very large.
A route reflector alleviates this problem. A route reflector is a BGP speaker that
learns routes from an IBGP neighbor and advertises the routes to other IBGP
neighbors. A route reflector client is a router within the same AS that depends on a
router reflector to re-advertise its routes to the entire AS and to learn about routes
from the rest of the AS. A cluster consists of one or more route reflectors and all their
clients. Clients peer only with route reflectors while route reflectors and non-client
routers must be fully meshed. Figure 7-20 shows an AS with multiple clusters.
Figure 7-20 Multiple Route Reflectors
AS 100
BGP Cluster
bgp0009
Route
Reflector
client
Route
Reflector
client
Route
Reflector
BGP Cluster
Route
Reflector
client
Route
Reflector
client
Route
Reflector
Use the neighbor route-reflector-client command, in Router Configuration mode, to
specify route-reflector-clients for a route reflector:
MOT:7A(config-bgp)#neighbor [<A.B.C.D> | <WORD>] route-reflector-client
where:
A.B.C.D is the IP address of the BGP neighbor that is the route reflector client.
WORD is the BGP neighbor peer group name that is the route reflector client.
Example
The commands in the following example configures a route reflector with two route
reflector clients:
MOT:7A(config-bgp)#neighbor 1.1.1.1 route-reflector-client
Configuring a Cluster-ID
Usually a cluster of clients has a single route reflector. The cluster is identified by the
router ID of the route reflector.
For each route reflector in a cluster, use the bgp cluster-id command, in Router
Configuration mode, to configure the cluster ID:
MOT:7A(config-bgp)#bgp cluster-id <value>
where:
value is the Route Reflector Cluster ID in IP address format (not 0)
Example
In the following example, the local router is one of the route reflectors serving
the cluster. The example configures the local router with the cluster ID to
identify the cluster.
MOT:7A(config-bgp)#bgp cluster-id 156.80.10.1
Restoring Route Reflection from a Route Reflection Client
By default, the clients of a route reflector are not required to be fully meshed and the
routes from a client are reflected to other clients. However, if the clients are fully
meshed, route reflection with the same set of clients is not required. Also, if
client-to-client reflection is enabled, the clients of a route reflector cannot be members
of a peer group.
In Figure 7-21, the local router is configured as a route reflector. However, the four
neighbors are fully meshed, so client-to-client reflection can be disabled.
Figure 7-21 Disabling Client-to-Client Reflection
To disable client-to-client route reflection, use the no bgp client-to-client reflection
command in Router Configuration mode:
MOT:7A(config-bgp)#no bgp client-to-client reflection
AS 100
140.20.10.3
140.20.10.1
140.20.10.2
140.20.10.4 140.20.10.5
bgp0010
Route
Reflector
client
Route
Reflector
client
Route
Reflector
client
Route
Reflector
client
Route
Reflector
8
Configuring VRRP
Overview
This chapter describes how to configure the Virtual Router Redundancy Protocol
(VRRP) on the BSR 64000 system using the Command Line Interface (CLI). For
further information on the CLI commands described in this chapter, refer to the BSR
64000 Command Reference Guide. This chapter discusses the following topics:
About VRRP
Configuring VRRP
Gathering Virtual Router Information
About VRRP
Virtual Router Redundancy Protocol (VRRP) dynamically assigns packet forwarding
responsibility for one or more virtual routers to VRRP routers on a LAN. This allows
several routers on a multi-access link to use the same virtual IP address.
A group of VRRP routers connected to a LAN are configured to belong to a virtual
router, identified by the virtual router identification (VRID). The VRRP process
elects one router as Master; the others act as Backups in case the Master router fails.
The election process provides dynamic fail-over in the forwarding responsibility if the
master becomes unavailable. This allows any of the virtual router IP addresses on the
LAN to be used as the default first-hop router by hosts. VRRP provides a
higher-availability default path without requiring configuration of dynamic routing or
router discovery protocols on every host.
Configuring VRRP
The following tasks configure VRRP on the BSR:
Enabling VRRP
Creating a Virtual Router
Configuring a Virtual IP Address
Configuring a Primary IP Address
Enabling a Virtual Router
Enabling Authentication
Specifying Priority
Pre-empting a Master
Specifying an Advertisement Interval
Clearing Statistic Counters
Note: If you configure a virtual IP address on a router with the same IP
address on a physical interface, then it is assigned a priority of 255 and will
always be master unless it fails.
Release 6.3.1 Configuring VRRP
Enabling VRRP
To globally enable VRRP on the router, use the ip vrrp command in Global
Configuration mode. This command enables all interfaces so that multiple virtual
routers can be enabled or disabled at one time. Use the no ip vrrp command to
disable VRRP on all interfaces. VRRP is enabled by default.
MOT:7A(config)#ip vrrp
Creating a Virtual Router
To configure this router to participate as a VRRP router in a VRRP virtual router, use
the ip vrrp command in Interface Configuration mode. The VRRP virtual router is
identified by the virtual router identification (VRID). Each virtual router selects its
own Master and Backups from the group of configured VRRP routers in the VRID,
independent of other virtual routers. Each virtual router has a unique virtual MAC
address and virtual IP address. Use the no ip vrrp command to delete a virtual router.
MOT:7A(config-if)#ip vrrp <1-255>
where:
1-255 is the virtual router ID (VRID).
Example
The following example configures a system to participate in two virtual routers, 1 and
2, on the Ethernet interface 7/0:
ip vrrp 1
ip vrrp 2
Configuring a Virtual IP Address
To associate a virtual IP address or addresses with a virtual router, use the ip vrrp
address command in Interface Configuration mode. VRRP is not enabled for the
virtual router until you specify at least one IP address. If you specify one or more IP
addresses, those addresses are used as the designated IP address or addresses for the
VRRP virtual router. Use the no ip vrrp address to remove the virtual IP address or
addresses.
MOT:7A(config-if)#ip vrrp <1-255> address <A.B.C.D> [...<A.B.C.D>]
where:
1-255 is the VRID.
A.B.C.D is the virtual IP address.
Example
The following example configures the system to use 198.112.190.1 and 20.20.20.1 as
the virtual IP addresses of virtual router 1, configured on Ethernet interface slot 1,
port 0:
ip vrrp 1 address 198.112.190.1 20.20.20.1
Configuring a Primary IP Address
To configure the primary IP address for the VRRP router that has multiple addresses
on an interface, use the ip vrrp primary-ip command in Interface Configuration
mode. Use the no ip vrrp primary-ip command to reset the primary IP address to the
lowest IP address among all real interface addresses for the interface.
MOT:7A(config-if)#ip vrrp <1-255> primary-ip <A.B.C.D>
where:
1-255 is the VRID.
A.B.C.D is the primary source IP address of outgoing IP packets on the interface.
Example
This example sets the primary IP address to 10.10.20.100.
ip address 10.10.10.100 255.255.255.0
ip address 10.10.20.100 255.255.255.0 secondary
ip vrrp 1 primary-ip 10.10.20.100
Enabling a Virtual Router
To enable a VRRP router on a configured interface, use the ip vrrp enable command
in Interface Configuration mode. This brings up a specific VRRP router on the
interface when the router is enabled. The router becomes either a Backup or Master
VRRP router, if at least one IP address is configured for the VRRP virtual router. Use
the no vrrp enable command to disable a VRRP router on a configured interface.
MOT:7A(config-if)#ip vrrp <1-255> enable
where:
1-255 is the VRID.
Example
This example disables the configured VRRP router, VRID 1, on the interface Ethernet
slot 1, port 0.
no ip vrrp 1 enable
Enabling Authentication
To enable authentication of packets received from other routers in the VRRP router
group, use the ip vrrp authentication type and ip vrrp authentication key
commands in Interface Configuration mode. This sets a simple text key in VRRP
messages. The unencrypted authentication string is transmitted for authentication
type, simple text, in all VRRP protocol messages.
The following steps enable and configure authentication:
1. Use the ip vrrp authentication type command to set the authentication type to
text. The default is no authentication.
MOT:7A(config-if)#ip vrrp <1-255> authentication type text
where:
1-255 the VRID of a configured virtual router.
2. Use the ip vrrp authentication type command to specify the authentication key.
Use the no ip vrrp authentication key command to remove the specified
authentication key.
MOT:7A(config-if)#ip vrrp <1-255> authentication key <WORD>
where:
1-255 the VRID of a configured virtual router.
WORD a string of up to 8 characters.
Note: You must configure the same authentication string on all routers
associated with a virtual router, identified by the VRID. An authentication
mismatch does not prevent a router from taking over as the designated
Master, however, it may cause VRRP to work incorrectly. This can result in
lack of communication between VRRP routers.
Example
The following example shows how to specify the authentication string, text only. The
system is configured to use mot as the authentication key to operate between other
VRRP routers for virtual router 1 on the configured interface.
ip vrrp 1 authentication type text
ip vrrp 1 authentication key mot
Specifying Priority
To specify the priority of the router used by VRRP when electing a Master for a
virtual router, use the ip vrrp priority command in Interface Configuration mode. If
two routers have the same priority, VRRP compares their primary IP addresses. The
router with the higher IP address takes precedence. A priority of 255 is reserved for
VRRP routers that own the virtual IP address. During configuration, the system
automatically sets the priority to 255 for the router owning that IP address. This value
cannot be changed. The system reserves the value 0 for the master to indicate the
relinquishing of its responsibility as Master in the virtual router. This value cannot be
changed. The default value is 100.
Use the no form of this command to restore the default priority value of the router.
MOT:7A(config-if)#ip vrrp <1-255> priority <1-254>
where:
1-255 is the VRID.
1-254 is the priority value for the VRRP router.
Example
This example configures the VRRP router with a priority of 150 for virtual router 1 on
the Ethernet interface 1/0.
ip vrrp 1 priority 150
Note: If you set up a virtual IP address on a router with the same IP address
on a physical interface, it receives priority 255 and is always master, unless it
fails.
Pre-empting a Master
To configure the VRRP router to take over as the master VRRP router if the router has
a higher priority than the current master VRRP router, use the ip vrrp preempt
command in Interface Configuration mode. Use the no ip vrrp preempt command to
disable the pre-emption feature on the configured interface.
MOT:7A(config-if)#ip vrrp <1-255> preempt
where:
1-255 is the VRID.
Example
This example configures the system to pre-empt the current master. VRRP, VRID 1,
is configured on interface Ethernet slot 1, port 0, with a higher priority than the
master. This command assumes the current master does not own the IP addresses of
virtual router 1.
ip vrrp 1 preempt
Specifying an Advertisement Interval
To specify the time interval between VRRP advertisement messages sent by the
Master VRRP router, use the ip vrrp timer command in Interface Configuration
mode. Use the no ip vrrp timer command to restore the default to 1 second.
MOT:7A(config-if)#ip vrrp <1-255> timer <1-255>
where:
1-255 is the VRID.
1-255 is the advertisement time interval in seconds.
Note: If the router owns the IP address or addresses associated with the
virtual router, the master always pre-empts, regardless of this command
setting.
Example
This example configures the system to send VRRP advertisements every three
seconds for the virtual router on the configured interface Ethernet 1/0, if the router is
is selected as the master for the virtual router 1. If not the Master, the Backup router
uses this interval to determine if the Master is down.
interface 1/0
ip vrrp 1 timer 3
Clearing Statistic Counters
To reset all VRRP statistic counters for all virtual routers configured on a router, use
the clear ip vrrp command in any mode, except User EXEC mode. A specific
interface or a specific Virtual Router ID (VRID) can be identified for more specific
resetting of statistic counters.
MOT:7A(config)#clear ip vrrp {* | ethernet <X/Y> | gigaether <X/Y>} [<1-255>]
where:
* resets all VRRP statistics counters for all virtual routers on this router.
ethernet resets VRRP statistics counter on the Ethernet interface.
gigaether resets VRRP statistics counter on the Gigabit Ethernet interface.
X is the slot number.
1-255 resets VRRP statistics counter for this VRID.
Examples
1. The following example resets all VRRP statistic counters for all virtual routers on
all interfaces for this router:
clear ip vrrp *
Note: The advertisement interval must be configured the same on all VRRP
routers of the same virtual router, identified by the VRID.
2. This example resets VRRP statistic counters for all virtual routers on the Ethernet
interface on slot 7, port 0:
clear ip vrrp ethernet 7/0
3. This example resets VRRP statistic counters for the virtual router with the
VRID 5 on the Ethernet interface in slot 7, port 0:
clear ip vrrp ethernet 7/0 vrid 5
Gathering Virtual Router Information
Monitoring Critical Link States
Monitoring Virtual Router Information
Monitoring Critical Link States
To configure the VRRP router to monitor one or more VRRP router IP addresses of a
virtual router, use the ip vrrp verify-availability command in Interface
Configuration mode. Use this command to configure a virtual router to monitor the
link states of other VRRP routers interfaces. If one or more IP addresses are
configured for monitoring and all monitored links are down, the VRRP process on the
router is brought down automatically. The Master relinquishes responsibility by
sending an advertisement 0. If at least one monitored link comes back up, the VRRP
process is brought back up automatically. Use the no ip vrrp verify-availability
command to stop monitoring of the specified VRRP IP addresses from the virtual
router, specified by the VRID.
MOT:7A(config-if)#ip vrrp <1-255> verify-availability <A.B.C.D>
[...<A.B.C.D>]
where:
1-255 is the VRID.
A.B.C.D is a VRRP IP address from the virtual router, identified by VRID.
Example
In this example, the system is configured to monitor VRRP IP addresses,
198.112.190.11 and 20.20.20.11, for their availability.
ip vrrp 1 verify-availability 198.112.190.11 20.20.20.11
Monitoring Virtual Router Information
To display detailed information on VRRP virtual routers that are configured on this
router, use the show ip vrrp command in all modes, except User EXEC mode. This
command verifies router virtual status.
MOT:7A(config-if)#show ip vrrp
Example:
The show ip vrrp command results in the following display:
VRRP Global Statistic:
Recv: 0 checksum errors, 0 bad version
60621 bad vrid, 0 bad packet size
Interface ethernet 7/0, VRID 1:
Status: vrrp is enabled, in state backup, priority is
100
advert interval is 1 sec, preempt mode is on
use no authentication, up since 16:46:27 ago
last state change 3:13:14 ago
primary ip is 10.10.10.202, total virtual ip
address(es) is 1
virtual ip address(es): 10.10.10.19
Advertisement Recv: 56615 total, 0 mismatched interval
0 bad vrrp type, 0 bad packet len, 0 as master
0 mismatched ip ttl, 0 mismatched addrlist
0 bad authentication type, 0 mismatched authentication
type
0 failed authentication, 0 zero priority
Advertisement Sent: 4 total, 0 zero priority
Become master: 3 times
Status: vrrp is enabled, in state master, priority is 255
address(es) is 1
0 bad authentication type, 0 mismatched authentication
type
Monitoring Ethernet Virtual Routers
To display detailed information on all of the VRRP virtual routers configured on an
Ethernet interface, use the show ip vrrp ethernet command in User EXEC mode.
MOT:7A#show ip vrrp [ethernet <X/Y> | gigaether <X/Y>] [<1-255>]
where:
ethernet is the Ethernet interface.
X is the slot number.
1-255 is the VRID.
Examples
The following are examples of the show ip vrrp ethernet command and their
displays.
1. MOT:7A(config-if)# show ip vrrp ethernet 7/0
Status: vrrp is enabled, in state backup, priority is
100
address(es) is 1
0 bad authentication type, 0 mismatched
authentication type
Interface ethernet 7/0, VRID 3 :
Status: vrrp is enabled, in state master, priority is
255
address(es) is 1
authentication type
2. MOT:7A(config-if)#show ip vrrp ethernet 7/0 vrid 3
Status: vrrp is enabled, in state master, priority is 255
address(es) is 1
0 bad vrrp type, 0 bad packet len, 126 as
master
authentication type
Obtaining Summary Information
To show summary information on all VRRP virtual routers configured on all
interfaces on the router, use the show ip vrrp summary command in User EXEC
mode.
MOT:7A#show ip vrrp summary
Example
The example below displays typical show ip vrrp summary command output:
MOT:7A(config-if)# show ip vrrp summary
Global vrrp configuration is enabled, total vrrp configured:
2
Interface VRID Enable State Pri Tmr Primary IP Addr Virtual
IP Addr StateChg ----------- ------ -------- ------- --- ----- ---------------------
---------------------------
ethernet 7/0 1 true backup 100 1 10.10.10.202 10.10.10.19
13:15:46
ethernet 7/0 3 true master 255 1 10.10.20.20
10.10.20.20 16:48:38
9
Configuring MPLS
Overview
This chapter describes how to configure Multiprotocol Label Switching (MPLS) on
the BSR 64000 system using the Command Line Interface (CLI). For a complete
description of the CLI commands discussed in this chapter, refer to the BSR 64000
Command Reference Guide.
About MPLS
Enabling MPLS and Basic Configuration Tasks
Creating a Static LSP
Configuring MPLS with RSVP
Accessing MPLS and RSVP Information
About MPLS
Multiprotocol Label Switching (MPLS) provides a mechanism for engineering
network traffic patterns that is independent of routing tables. In a standard routed
network (without MPLS), as a packet travels from a source to a destination, an
independent forwarding decision must be made at each router along the path. As a
packet travels through the network, each router analyzes the packet and determines
the next hop router that the packet must be sent to in order for the packet to arrive at
its final destination.
With MPLS, a packet only has to be analyzed once it enters the network. As the
packet is received at the first router in the network, the router assigns a short label to
the packet. When the packet is forwarded to the next router, the label is included in
the packet. At subsequent routers, there is no further analysis of the packets layer 3
address. Instead, the label is used to instruct the router how to forward the packet.
An MPLS network consists of Label Edge Routers (LERs) and Label Switch Routers
(LSRs).
The LER is responsible for classifying each packet based on some
user-configurable policy (source, destination, port, QoS class, etc.) and assigning
a label to the packet.
The LSRs are responsible for forwarding the packet along the correct Label
Switched Path (LSP) based upon the label. LSPs are configured from end-to-end
across the network. In order for a packet to properly travel across the network, all
routers in the path must be aware of the label for each packet and which LSP to
send the packet on. LSPs are configured statically at each router along the path or
dynamically using the Resource Reservation Protocol (RSVP).
MPLS supports a variety routing protocols by creating end-to-end links across a
network that serve as tunnels for all packets that need to travel to the same
destination.
About RSVP
Resource Reservation Protocol (RSVP) data transfer occurs between a router that
serves as the links entrance point and another router that serves as the links exit
point. RSVP is used in conjunction with MPLS to distribute MPLS labels.
Release 6.3.1 Configuring MPLS
RSVP is a resource reservation setup protocol that is used by both network hosts and
routers. Hosts use RSVP to request a specific quality of service (QoS) from the
network for particular application flows. Routers use RSVP to deliver QoS requests to
all routers along the data path. RSVP also can maintain and refresh states for a
requested QoS application flow.
RSVP is not a routing protocol, but rather is designed to inter-operate with current and
future unicast and multicast routing protocols. The routing protocols are responsible
for choosing the routes to use to forward packets, and RSVP consults local routing
tables to obtain routes. RSVP is responsible only for ensuring the QoS of packets
traveling along a data path.
Configurable MPLS Entries
The BSR 64000 currently allows for approximately 65,000 Fastpath entries. Of these
entries, 10,000 entries are set aside for MPLS label entries (BGP-VPN, etc.). This
leaves 55,000 remaining Fastpath entries that can be used for IP forwarding entries.
When the BSR is configured as a cable-bundle, every cable, CM, or CPE also requires
a Fastpath entry to resolve which CMTS slot to forward a received packet toward
since the IP subnet exists across several or all the CMTS slots. The BSR cable-bundle
allows up to 45,000 of these cable forwarding entries. This leaves 10,000 forwarding
entries for IP destinations.
If a user carries greater-than 10,000 IP destinations (routes) in a full 45,000 cable
entry configuration, then some of the IP destinations are forwarded via the Slowpath
by the SRM. This results in SRM instability and loss of services (e.g., COPS
connection timeouts, OSPF neighbor loss, etc). The configurable MPLS entries
feature allows a user to increase the number of IP forwarding entries by setting a
maximum number for MPLS forwarding entries and thus prevent IP destinations from
being forwarded via the Slowpath.
The following commands are used for this feature:
mpls fp max
show fast-path ranges
Enabling MPLS and Basic Configuration Tasks
This section describes globally enabling MPLS and various basic configuration tasks:
1. Enable the MPLS Protocol with the mpls ip command, in Global Configuration
mode, as follows:
MOT:7A(config)#mpls ip
2. Check to see that the MPLS is running with the show running-config command,
in Global Configuration mode, as follows:
MOT:7A(config)#show running-config | begin mpls
"mpls ip" should appear as an entry in the running configuration file.
3. Use the mpls label range, in Global Configuration mode, to specify an MPLS
minimum and maximum label range for static or dynamic Label Switched Paths
(LSPs), as follows:
MOT:7A(config)#mpls label range {dynamic-lsp | static-lsp}{<16-1048575>
<16-1048575>}
where:
dynamic-lsp is the label range for a dynamic LSP.
static-lsp is the label range for a static LSP.
16-1048575 is the minimum label value in the label range.
16-1048575 is the maximum label value in the label range.
4. Check the label range with the show mpls label range command, in all modes
except User EXEC. This command displays the specified minimum and
maximum label range for both static and dynamic LSPs.
MOT:7A(config)#show mpls label range
Note: A dynamic-lsp range can not overlap a static-lsp range.
5. Propagate the time-to-live value (default 64 hops) with the mpls ip propagate-ttl
command in Global Configuration mode. The mpls ip propagate-ttl command
enables the traceroute command to show all the hops traversed by the MPLS
packet in the network. If the no mpls ip propagate-ttl command is used, then the
traceroute command will not display the hops traversed by the MPLS packet in
the network.
MOT:7A(config)#mpls ip propagate-ttl
6. Optionally, you can change the default MPLS time-to-live value with the mpls ttl
command in Global Configuration mode.
MOT:7A(config)#mpls ttl <1-255>
where:
1-255 is the time-to-live value.
Creating a Static LSP
To configure a static LSP route, you configure an ingress router and each transit
router along the path up to and including the egress router.
The ingress router checks the IP address in the incoming packets destination
address field and, if it finds a match in the Forwarding Equivalence Class (FEC)
table, applies the label associated with that address to the packets.
Transit and egress routers modify the label that has been applied to a packet. A
transit (intermediate) router can change the label. An egress router removes the
label (if the packet still contains a label) and continues forwarding the packet to
its destination.
Follow these steps to create a static MPLS LSP route:
1. Configure the Ingress Router:
Configuring an ingress router involves specifying the tag to apply to the packet,
the next hop router in the LSP, and optional QoS value, as follows:
MOT:7A(config)#mpls create-lsp static <lsp-path-name> {ip-to-mpls-push |
mpls-to-mpls-push} <16-1048575> <A.B.C.D>
where:
lsp-path-name is the user-defined LSP name.
ip-to-mpls-push the Ingress router uses the ip-to-mpls-push label operation.
Push label adds a new label to the packet.
mpls-to-mpls-push the Ingress router uses the mpls-to-mpls-push label
operation. Push label adds a new label to the packet.
16-1048575 is the MPLS label to push on the packet.
A.B.C.D is the IP address of the next hop router.
2. Configure the Transit Router(s):
Configuring a transit router involves specifying the tag to apply to the packet, the
next hop router in the LSP, and an optional QoS value, as follows:
MOT:7A(config)#mpls create-lsp static <lsp-path-name> swap-label
<16-1048575> <16-1048575> <A.B.C.D> queue <0-3>
where:
swap-label the transit router uses the swap-label operation.
16-1048575 is the MPLS label to swap out from the packet.
16-1048575 is the MPLS label to swap in to the packet.
queue <0-3> is QoS queue identifier.
3. Configure the Egress Router:
Configuring the egress router involves removing the label and continue
forwarding the packet to the next hop based on the destination IP address, as
follows:
MOT:7A(config)#mpls create-lsp static <lsp-path-name> pop-label
<16-1048575>
where:
pop-label the egress router uses the pop-label operation.
16-1048575 is the MPLS label to pop out of the packet.
4. Use the show mpls lsp command to display the static LSP, as follows:
MOT:7A(config)#show mpls lsp
Refer to the MPLS Commands chapter in the BSR 64000 Command Reference
Guide for a detailed command output description.
Deleting a Static LSP
Use the no mpls create-lsp static command, in Global Configuration mode, to delete
an existing LSP, as follows:
MOT:7A(config)#no mpls create-lsp static <lsp-path-name>
Configuring MPLS with RSVP
The following sections describe how to dynamically configure MPLS on an interface
using the Resource Reservation Protocol (RSVP).
Enabling RSVP on an Interface
Follow these steps to enable RSVP on an interface:
1. Use the interface command, in Global Configuration mode, to enter Interface
Configuration mode, as follows:
MOT:7A(config)#interface {ethernet <X/Y> | gigaether <X/Y>| pos <X/Y>}
where:
ethernet <X/Y> is any 10 or 10/100 Ethernet interface slot and port number.
gigaether <X/Y> is the Gigabit Ethernet interface slot and port number.
pos <X/Y> is the Packet over SONET interface slot and port number.
2. Use the ip rsvp command, in Interface Configuration mode, to enable the RSVP
protocol on the interface, as follows:
MOT:7A(config-if)#ip rsvp
3. Check to see that RSVP is running with the show running-config command, in
Global Configuration mode, as follows:
MOT:7A(config)#show running-config | begin rsvp
"ip rsvp" should appear as an entry in the running configuration file.
Disabling RSVP on an Interface
Use the no ip rsvp command, in Interface Configuration mode, to disable the RSVP
protocol on an interface:
MOT:7A(config-if)#no ip rsvp
Creating a Dynamic LSP Using RSVP
To configure a dynamic LSP, you only need to configure the ingress router; you do
not have to configure any other routers. You specify the source and destination
address for the path. The LSP is then set up by RSVP, through RSVP signaling
messages.
You use the mpls create-lsp rsvp command, in Global Configuration mode, to create
a dynamic LSP using RSVP, as follows:
MOT:7A(config)#mpls create-lsp rsvp <string> <A.B.C.D> [<A.B.C.D>]
where:
string is the LSP name.
A.B.C.D is the destination IP address for the dynamic LSP.
A.B.C.D is the source IP address for the dynamic LSP.
Refer to the MPLS Commands chapter in the BSR 64000 Command Reference Guide
for detailed syntax descriptions.
Configuring an Explicit Route Using RSVP
Optionally, you can configure an LSP using the explicit route option. This involves
specifying each transit router on the LSP all the way to the destination. Refer to the
MPLS Commands chapter in the BSR 64000 Command Reference Guide for detailed
syntax descriptions.
1. Use the mpls create-lsp rsvp explicit-route command, in Global Configuration
mode, to create one or more named paths on the ingress router.
MOT:7A(config-if)#mpls create-lsp rsvp explicit-route identifier <string>
[hops [<1-20>]]
where:
Note: To configure dynamic LSPs on all the MPLS routers that participate in
MPLS, you need to enable MPLS and RSVP on these routers,
1-20 is the number of hops; if not specified, the default is 10.
2. Use the mpls create-lsp rsvp next-hop command to specify one or more MPLS
transit router addresses. You can specify the address of each transit router if its
type is specified as "strict". You specify the addresses in their order along the
path, starting with the first transit router, and continuing sequentially along the
path. You can specify only one address per router hop.
MOT:7A(config)#mpls create-lsp rsvp <string> next-hop <A.B.C.D>
{Loose | Strict} [Last-Hop]
where:
Loose specifies that the route taken from the previous router to this router
does not need to be a direct path.
Strict specifies that the route taken from the previous router to this router is a
direct path. The IP address of the next hop router should be directly
connected and should be one of the interface addresses in the LSP path.
Last-Hop is the keyword that signifies that this is the last hop in the LSP
configuration.
Configuring RSVP Routing Messages
Use the following commands to configure RSVP routing messages. Refer to the
MPLS Commands chapter in the BSR 64000 Command Reference Guide for detailed
syntax descriptions.
Use the ip rsvp aggregate command, in Interface Configuration mode, to enable
the bundling of multiple RSVP messages into a single RSVP transmission. The
network resources needed for running RSVP on a router increases with the
number of sessions. Aggregation provides a mechanism to efficiently handle the
large number of refresh messages that are transmitted between RSVP neighbors,
reduce message flooding, and efficiently transmit RSVP messages.
MOT(config-if)#ip rsvp aggregate
Use the ip rsvp bundle-time command, in Interface Configuration mode, to
specify the maximum interval in seconds between the generation of bundle
messages. The default bundle time interval is 10 seconds.
MOT:7A(config-if)#ip rsvp bundle-time <1-30>
where:
Use the ip rsvp msgack-time command, in Interface Configuration mode, to
specify the maximum interval in seconds between the acknowledgement of
bundle messages. The default msgack time is 2 seconds.
MOT:7A(config-if)#ip rsvp msgack-time <1-65535>
where:
Hello packets are used to update an MPLS router on the active status of other
MPLS routers on the link. Use the ip rsvp hello-interval command, in Interface
Configuration mode, to specify how often this MPLS enabled interface generates
hello packets. By default, hello packets are disabled.
MOT:7A(config-if)#ip rsvp hello-interval <0-65535>
where:
0-65535 is the interval, in seconds, between the generation of Hello packets;
0 disables the generation of hello packets.
Use the ip rsvp refresh-time command, in Interface Configuration mode, to
specify how often refresh messages are generated on an MPLS link. Refresh
messages are sent periodically so that reservation states in neighboring nodes do
not time out and include Path and Resv messages. Path and Resv messages carry
the refresh timer value. The receiving node extracts this value from the messages.
The default refresh time interval is 30 seconds.
MOT:7A(config-if)#ip rsvp refresh-time <1-65535>
where:
1-65535 is the interval in seconds between the successive generation of
refresh messages.
Accessing MPLS and RSVP Information
Use the commands in Table 9-1 to clear, debug, and access MPLS and RSVP
information. Refer to the MPLS Commands chapter in the BSR 64000 Command
Reference Guide for detailed syntax descriptions.
Table 9-1 Clearing, Debugging, and Accessing MPLS and RSVP Information
clear ip rsvp statistics Use the clear ip rsvp statistics command to clear
RSVP packet and error counters.
clear mpls traffic Use the clear mpls traffic command to reset MPLS
traffic counters.
debug mpls forwarding
debug mpls rsvp
Use the debug mpls forwarding and debug mpls
rsvp commands to enable MPLS debugging output.
show ip rsvp
explicit-routed-lsps
Use the show ip rsvp explicit-routed-lsps command
to display RSVP explicit route LSPs.
show ip rsvp interface Use the show ip rsvp interface command to display
information about the status of interfaces on which
RSVP is running either for a specified interface or all
interfaces on the BSR.
show ip rsvp neighbor Use the show ip rsvp neighbor command to display
information about current RSVP neighbors, on a
specified interface or all interfaces on the BSR.
show ip rsvp reservation Use the show ip rsvp reservation to view
RSVP-related receiver information for the specified
interface or all interfaces on the BSR.
show ip rsvp sender Use the show ip rsvp sender command to view
RSVP-related sender information for the specified
interface or all interfaces on the BSR.
show ip rsvp lsp Use the show mpls lsp command to display all
configured LSPs on this router, as well as all ingress,
intermediate, and egress LSPs.
show ip rsvp statistics Use the show mpls rsvp statistics command to
access statistical information for all or individual
MPLS RSVP-enabled interfaces.
show mpls filters Use the show mpls filters command to display MPLS
filter table entries.
show mpls forwarding-table Use the show mpls forwarding-table command to
display the LSP forwarding table.
show mpls label range Use the show mpls label range to display the
configured minimum and maximum label range for
both static and dynamic LSPs.
show mpls lsp Use the show mpls lsp command to display all
configured LSPs on this router, as well as all ingress,
transit, and egress LSPs.
show mpls lsp interface Use the show mpls lsp interface command to
display configured LSPs on a specific interface, as
well as all ingress, transit, and egress LSPs.
show mpls rsvp refresh-time Use the show mpls rsvp refresh-time command to
display the global refresh time.
show mpls traffic Use the show mpls traffic command to display
MPLS network traffic statistics.
Table 9-1 Clearing, Debugging, and Accessing MPLS and RSVP Information
10
Configuring Packet Over
SONET
Overview
This chapter describes how to configure the Packet Over SONET (POS) interface on
the BSR 64000 using the Command Line Interface (CLI). For further information
on the CLI commands described in this chapter, refer to the BSR 64000 Command
Reference Guide.
About SONET/SDH
POS Interface Configuration Tasks
Configuring SONET
Configuring SONET Alarms
Changing the POS Signal Rate
Specifying the POS Loopback Mode Type
Configuring POS Automatic Protection Switching
Gathering POS Network Information
Table 10-1 describes the SONET transmission types and rates that are available for
the BSR 64000.
About SONET/SDH
The Synchronous Optical Network (SONET) standard provides for data transmission
over fiber optic cable, and high-bandwidth utilization and efficiency over Internet
links. The SONET standard defines industry interface standards at the physical layer
of the OSI seven-layer model. This standard defines a hierarchy of interface rates that
allow data streams at different rates to be multiplexed. SONET establishes Optical
Carrier (OC) levels from 51.8 Mbps to 2.48 Gbps. Prior rate standards used by
different countries specified rates that were not compatible for multiplexing.
Synchronous Digital Hierarchy (SDH), the international equivalent of SONET,
defines a standard rate of transmission at 155.52 Mbps. With the implementation of
SONET/SDH, communication carriers throughout the world can interconnect existing
digital carrier and fiber optic systems.
Specifications
The BSR POS interface supports the following Request for Comment (RFC)
specifications:
RFC 1619, PPP over SONET/SDH
RFC 1662, PPP in HDLC-like Framing
RFC 2558, SONET/SDH
POS Features
The BSR supports the following POS features:
Payload scrambling
Clock source configuration
Table 10-1 SONET Transmission Types and Rates
Transmission Type Rate
OC-1 51.84 Mbps
OC-3 155.52 Mbps
OC-12 622.08 Mbps
Release 6.3.1 Configuring Packet Over SONET
Maximum transmission unit size configuration
SONET/SDH framing
Cyclic redundancy check
Alarm Reporting
Automatic Protection Switching
POS Interface Configuration Tasks
The following POS module configuration tasks are mandatory:
Configuring the POS Interface
Configuring PPP
Configuring the Network Clock Source for SONET
Configuring the POS Interface
Follow these steps to configure the POS interface:
1. Use the interface pos command, in Global Configuration mode, to configure the
physical POS interface:
MOT:7A(config)#interface pos <X/Y>
where:
X is the POS module slot on the BSR 64000 chassis.
Y is the POS port on the POS module.
2. Use the ip address command, in Interface Configuration mode, to enter the IP
address and subnet mask for the POS interface:
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the IP address of the POS interface.
A.B.C.D is the subnet mask for the IP address.
3. Optionally, use the ip address secondary command, in Interface Configuration
mode, to set a secondary IP address and subnet mask for the POS interface:
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D> secondary
where:
A.B.C.D is the IP address of the POS interface.
A.B.C.D is the subnet mask.
Configuring PPP
Table 10-2 describes the Point-to-Point Protocol (PPP) features and commands that
are available on the POS module:
Follow these options to configure PPP on the POS interface:
The Magic-Number option is used to detect loops on the link either in the
negotiation or traffic phase. Use the ppp magic-number command, in Interface
Configuration mode, to periodically send a magic number in the PPP negotiation
request:
MOT:7A(config-if)#ppp magic-number
Table 10-2 PPP Commands
Command Description Default Value
ip mtu Maximum transmission
unit packet size allowed on
the POS interface
1496 bytes 68 to 4000 bytes
peer default ip
address
Specifies a IP address for
the remote peer.
none IP address
ppp magic-number Enable sending of a magic
number in a negotiation
request
none none
ppp
negotiation-count
Number of attempts before
the PPP connection is
dropped
Continuous 1 to 100 attempts
ppp timeout ncp Maximum wait time for the
network layer to negotiate
before the PPP connection
is dropped
10 seconds 1 to 2147483
seconds
ppp timeout retry Maximum wait time for the
link layer to receive a
negotiation response
before the PPP connection
is dropped
10 seconds 0 to 2147483
seconds
Use the ip mtu command, in Interface Configuration mode, to set the size of the
MTU packet allowed on the POS interface:
MOT:7A(config-if)#ip mtu <68-4000>
where:
68-4000 is the number of bytes permitted for the MTU; the default is 1496
bytes.
Use the peer default ip address command, in Interface Configuration mode, to
specify the default IP address assigned to the remote peer connecting to this
interface:
MOT:7A(config-if)#peer default ip address <A.B.C.D>
where:
A.B.C.D is the IP address assigned to a remote peer connected to the POS
interface.
Use the ppp negotiation-count command, in Interface configuration mode, to set
the number of attempts for successful negotiation before terminating the PPP link
on the POS interface:
MOT:7A(config-if)#ppp negotiation-count <1-100>
where:
1-100 is the number of permitted negotiation attempts.
Use the ppp timeout ncp command, in Interface Configuration mode, to set the
maximum PPP wait time for the network layer to negotiate before disconnecting
the PPP link on the POS interface when there is no activity on the link.
MOT:7A(config-if)#ppp timeout ncp <1-2147483>
where:
1-2147483 is the number of seconds of inactivity before the PPP link is
disconnected; the default is 10 seconds.
Use the ppp timeout retry command, in Interface Configuration mode, to set the
maximum PPP wait time for a negotiation response at the link layer before
disconnecting the PPP link on the POS interface when there is no activity on the
link.
MOT:7A(config-if)#ppp timeout retry <1-2147483>
where:
1-2147483 is the number of seconds of inactivity before the PPP link is
disconnected; the default is 10 seconds.
Configuring the Network Clock Source for SONET
The network clock source is set for the SONET link to avoid undesirable conditions
related to timing synchronization such as jitter and wander. Jitter refers to the
short-term instabilities in network signal timing. Wander refers to long-term random
variations of the significant instances of a digital signal from their ideal position in
time. The internal clock on the POS module is enabled by default so that it references
the network clock source for the BSR 64000.
Table 10-3 describes the network clocking commands that are available on the BSR
and the POS module:
Table 10-3 Network Clocking Commands
network-clock-select
{1 | 2} bits e1 {a | b}
Enables the E1 Building
Integrated Timing Supply
(BITS) network clocking to
be derived from the central
office (CO) BITS source.
none 1 sets the priority of the
clocking source to
primary or 2 sets the
priority of the clocking
source to secondary.
Specify a or b port on
SRM I/O module.
{1 | 2} bits t1 {a | b}
Enables the T1 Building
Integrated Timing Supply
(BITS) network clocking to
be derived from the central
office (CO) BITS source.
clocking source to
Specify a or b port on
SRM I/O module.
Setting the Primary BITS Network Clocking Source
Follow these steps to set the primary network clocking source:
1. Use the network-clock-select 1 bits command, in Global Configuration mode, to
identify the primary network clock and define the network clocking port on the
SRM I/O module from which the T1 or E1 BITS signal is derived:
MOT:7A(config)#network-clock-select 1 bits [t1 {esf-b8zs | sf-d4 | slc96 |
t1dm} | e1 {pcm31-crc | pcm31-hdb3 | pcm31-nocrc}] [a | b]
where:
1 is the priority assigned to the primary network clock.
t1 specifies a T1 BITS signal.
esf-b8zs is ESF framing with B8ZS line coding.
sf-d4 is SF-D4 framing with AMI line coding.
slc96 is SLC96 framing with AMI line coding.
t1dm is T1DM framing with AMI line coding
e1 specifies an E1 BITS signal.
pcm31-crc is PCM-31 framing with AMI line coding and CRC Multiframe
support.
pcm31-hdb3 is PCM-31 framing with HDB3 line coding and CRC
Multiframe support.
{1 | 2} pos <X/Y>
Enables the network
clocking to be derived from
a specific POS module
and interface.
clocking source to
Specify slot and
interface number
pos internal-clock Set the clock source on
the POS interface
internal internal or recovered
Table 10-3 Network Clocking Commands
pcm31-nocrc is PCM-31 framing with AMI line coding and no CRC
Multiframe support.
a specifies the Input A port on the SRM I/O module.
b specifies the Input B port on the SRM I/O module.
2. Use the show network-clocks command, in Global Configuration mode, to
verify the primary network clock source information that you have configured:
MOT:7A(config)#show network-clocks
Figure 10-1 show network-clocks Command Output
Setting the Secondary BITS Network Clocking Source
Follow these steps to set the secondary network clocking source:
1. Use the network-clock-select 2 bits command, in Global Configuration mode, to
identify the secondary network clock and define the network clocking port on the
SRM I/O module from which the T1 or E1 BITS signal is derived:
MOT:7A(config)#network-clock-select 2 bits [t1 {esf-b8zs | sf-d4 | slc96 |
t1dm} | e1 {pcm31-crc | pcm31-hdb3 | pcm31-nocrc}] [a | b]
where:
2 is the priority assigned to the secondary network clock.
t1 specifies a T1 BITS signal.
esf-b8zs is ESF framing with B8ZS line coding.
sf-d4 is SF-D4 framing with AMI line coding.
slc96 is SLC96 framing with AMI line coding.
t1dm is T1DM framing with AMI line coding
e1 specifies an E1 BITS signal.
pcm31-crc is PCM-31 framing with AMI line coding and CRC Multiframe
support.
Priority 1 clock source: T1 Device A
Current Alarms: None
Priority 2 clock source: Sonet Slot 3 Port 0
Current Alarms: None
pcm31-hdb3 is PCM-31 framing with HDB3 line coding and CRC
Multiframe support.
pcm31-nocrc is PCM-31 framing with AMI line coding and no CRC
Multiframe support.
a specifies the Input A port on the SRM I/O module.
b specifies the Input B port on the SRM I/O module.
verify the secondary network clock source information that you have configured:
Deriving the Network Clocking Source from a POS Interface
Follow these steps to derive network clocking from a POS interface:
1. Use the network-clock-select pos command, in Global Configuration mode, to
enable the network timing to be derived from the clocking recovered from a
specified POS module interface, as shown below:
MOT:7A(config)#network-clock-select [1 | 2] pos <X/Y>
where:
1 is the priority assigned to the primary network clock.
2 is the priority assigned to the secondary network clock.
X is the POS slot on the BSR.
Y is the POS port from which the clocking is recovered.
verify the network clock source information that you have configured:
Setting Clock Recovery from the Received SONET Signal
Follow these steps to set clock recovery from the received SONET signal:
1. Use the interface pos command, in Global Configuration mode, to enter the POS
interface from which the clock is to be recovered:
where:
Y is the line POS port on the POS module.
2. Use the no pos internal-clock command, in Interface Configuration mode, to use
the recovered clock from the received SONET signal:
MOT:7A(config-if)#no pos internal-clock
Use the pos internal-clock command, in Interface Configuration mode, if the
timing source must be returned to internal clock mode:
MOT:7A(config-if)#pos internal-clock
Configuring SONET
The following sections describe how to set a variety of SONET parameters:
Optionally Disabling SONET Payload Scrambling
Changing the SONET Framing Type
Changing the CRC Function on the POS Interface
Defining SONET Frame Overhead Bytes
Table 10-4 describes the SONET features and commands that are available for the
POS module:
Note: Internal clock mode is enabled by default for the POS module to gather
its timing from the network clocks that are configured on the SRM. If the
internal clocking function is disabled, clock recovery is taken from the
received SONET signal.
Table 10-4 SONET Commands
pos scramble Enables scrambling
algorithm used for the
SONET payload
enabled none
pos framing Sets the POS interface
framing type
sonet sdh or sonet
crc Number of bits used for
CRC checking
16 bits 16 or 32 bits per
frame. Also the crc
can be optionally set
for big-endian byte
order.
pos flag c2 The c2 byte in the SONET
frame is the path signal
identifier.
0xCF 0xCF for PPP without
scrambling; 0x16 for
PPP with scrambling.
pos flag c2-exp Path signal identifier
expected from the far end
SONET equipment.
0xCF Hexadecimal value
for the protocol
encapsulation.
pos flag j0 Defines section trace byte
message
0xCC Hexadecimal value;
0x01is used for some
SDH devices in
Japan.
pos flag j0 16byte Defines 16 byte section
trace message
undefined 15 character text
string containing the
trace sequence.
pos flag j1 Defines hexadecimal path
trace byte
0x0 Hexadecimal value.
pos flag j1 16byte Defines 16 byte path trace
message
byte sequence.
pos flag j1 64byte Defines 64 byte path trace
message
byte sequence.
pos flag s1 Used for synchronous
status messaging
0x0 Hexadecimal value.
Table 10-4 SONET Commands
Optionally Disabling SONET Payload Scrambling
SONET optical interface signals use binary line encoding, and therefore must be
scrambled to assure an adequate number of transitions of zeros to ones, and ones to
zeros.
If the remote SONET device does not support scrambling, payload scrambling may
need to be disabled.
Payload scrambling is enabled by default on the POS interface. Use the no pos
scramble command, in Interface Configuration mode, to disable payload scrambling:
MOT:7A(config-if)#no pos scramble
Use the pos scramble command, in Interface Configuration mode, to return to the
default, which is payload scrambling:
MOT:7A(config-if)#pos scramble
Changing the SONET Framing Type
The BSR framing type default is SONET. Use the following options to change the
framing type:
Use the pos framing sdh command, in Interface Configuration mode, to set the
framing type to SDH.
MOT:7A(config-if)#pos framing sdh
Use the pos framing sonet command, in Interface Configuration mode, to set the
framing type back to SONET:
MOT:7A(config-if)#pos framing sonet
Note: When payload scrambling is enabled, both sides of the connection
must be using the same scrambling algorithm.
Changing the CRC Function on the POS Interface
Cyclic Redundancy Check (CRC) error-checking uses a calculated numeric value to
detect errors in transmitted data. The values 16 and 32 indicate the number of check
bits per frame for calculating the frame check sequence (FCS). Both the sender and
receiver must use the same setting. The default is 16. Use the crc command, in
Interface Configuration mode, to set the number of bits used for CRC on the POS
interface:
MOT:7A(config-if)#crc [16 | 32] [big-endian]
where:
16 is the number of check bits.
32 is the number of check bits.
big-endian byte ordering is to be used.
Defining SONET Frame Overhead Bytes
SONET overhead bytes identify information in the SONET frame. Refer to the
GR-253-CORE document for STS Path Signal Label Assignments and the
hexadecimal values required for the SONET frame overhead bytes.
Follow these steps to specify flags for the SONET frame overhead bytes:
1. The c2 byte of the SONET frame is a path signal identifier. Use the pos flag c2
command, in Interface Configuration mode, to set the hexadecimal value for the
c2 byte:
MOT:7A(config-if)#pos flag c2 <hexnum>
where:
hexnum is the hexadecimal value for the c2 byte.
For example:
- PPP encapsulation is 0xCF
- HDLC encapsulation is 0x16
- ATM encapsulation is 0x13
- Unequipped is 0x00
- Equipped non-specific is 0x01
2. The c2-exp byte is the path signal label expected from the far end SONET
equipment. Use the pos flag c2-exp command, in Interface Configuration mode,
to set the hexadecimal value for the c2-exp byte for the SONET frame payload
for the PPP or HDLC protocols:
MOT:7A(config-if)#pos flag c2-exp <hexnum>
where:
hexnum is the hexadecimal value for the c2 byte.
3. If the received c2 byte differs from the expected c2 byte, a payload mismatch
occurs. Use the show controllers pos command, in Interface Configuration
mode, to view a payload mismatch for the c2 byte:
MOT:7A(config-if)#show controllers pos
4. Use the pos flag j0 command, in Interface Configuration mode, to configure the
j0 section trace byte:
MOT:7A(config-if)#pos flag j0 <hexnum>
where:
hexnum is the hexadecimal value for the j0 byte.
5. Use the pos flag j0 16byte command, in Interface Configuration mode, to
configure the section trace message:
MOT:7A(config-if)#pos flag j0 16byte <string>
where:
string is 15 character text string containing the byte sequence.
6. Use the pos flag j1 command, in Interface Configuration mode, to configure the
path trace byte:
MOT:7A(config-if)#pos flag j1 <hexnum>
where:
hexnum is the hexadecimal value for the j1 byte.
Note: The first byte from the 16 byte section trace message contains an
automatically generated CRC, the remaining 15 bytes are user defined.
configure the 16 byte path message:
where:
string is a 15 character text string containing the byte sequence.
configure the 64 byte path message:
where:
string is a 62 character text string containing the byte sequence.
9. The s1 byte identifies the timing source for SONET frame synchronization. Use
the pos flag s1 command, in Interface Configuration mode, to set the
hexadecimal value for the s1 byte:
MOT:7A(config-if)#pos flag s1 <hexnum>
where:
hexnum is the hexadecimal value for the s1 byte.
Note: The first byte from the 16 byte path message contains an automatically
generated CRC; the remaining 15 bytes are the user defined 15 character
text string.
Note: 2 bytes from the 64 byte path message are automatically set to CR/LF
for framing purposes; the remaining 62 bytes are the user defined 62
character text string.
Note: Only the lower four bits of the s1 byte are actually configured.
Configuring SONET Alarms
The following sections discuss SONET alarm thresholds, alarm reports, and alarm
indicators:
Setting Alarm Thresholds
Setting Alarm Reporting
Setting the Line Alarm Indication Signal
Table 10-5 describes the SONET alarms that can be configured on the POS module:
Table 10-5 SONET Alarm Commands
pos threshold
b1-tca
The BER threshold for the
b1 threshold crossing
alarm (TCA)
3 (10E-3
Rate)
3 - 9 (10E-3 to 10E-9
Rate)
pos threshold
b2-tca
alarm (TCA)
3 (10E-3
Rate)
3 - 9 (10E-3 to 10E-9
Rate)
pos threshold
b3-tca
alarm (TCA)
3 (10E-3
Rate)
3 - 9 (10E-3 to 10E-9
Rate)
pos report SONET alarm reporting to
the console
Reporting
disabled
all, b1-tca, b2-tca,
b3-tca, lais, lrdi,
pais, plop, prdi,
rdool, sd-ber, sf-ber,
slof, slos
pos ais-shut Controls whether an Alarm
Indication Signal - Line
(AIS-L) is sent to the far
end SONET device when
the POS interface is
placed in an
administratively shutdown
state
disabled none
Setting Alarm Thresholds
Use the SONET alarm thresholds discussed in this section to evaluate network
performance. Alarm thresholds define the Bit Error Rate (BER) threshold values for
specific control bits in SONET frames. The default SONET alarm thresholds are
adequate for most POS installations. Refer to Table 10-11 for more information on
each alarm threshold. Refer to Setting APS Alarm Thresholds on page 10-36 for more
information on setting APS thresholds.
Follow these steps to set SONET alarm thresholds:
1. Use the pos threshold b1-tca command, in Interface Configuration mode, to
configure the BER threshold for the b1 threshold crossing alarm (TCA):
MOT:7A(config-if)#pos threshold b1-tca <3-9>
where:
<3-9> is the numeric rate of error indicating from 10E-3 to 10E-9.
configure the BER threshold for the b2 TCA:
where:
configure the BER threshold for the b3 TCA:
where:
4. Use the no pos threshold command, in Interface Configuration mode, to return
to the default setting:
MOT:7A(config-if)#no pos threshold [b1-tca | b2-tca | b3-tca]
Setting Alarm Reporting
Reporting of SONET alarms is disabled by default. Use the pos report command, in
Interface Configuration mode, to select SONET alarms to be logged to the POS
interface console:
MOT:7A(config-if)#pos report [all | b1-tca | b2-tca | b3-tca | lais | lrdi | pais | plop |
prdi | rdool | sd-ber | sf-ber | slof | slos]
Use the no pos report command, in Interface Configuration mode, to disable logging
of selected SONET alarms:
MOT:7A(config-if)#no pos report [all | b1-tca | b2-tca | b3-tca | lais | lrdi | pais |
plop | prdi | rdool | sd-ber | sf-ber | slof | slos]
Table 10-6 describes the SONET alarms that can be configured for reporting:
Table 10-6 SONET Alarm Report Selections and Descriptions
Alarm Report Description
all All possible alarm reporting
b1-tca B1 BER TCA errors
lais Line alarm indication signal
lrdi Line remote defect indicator
pais Path alarm indication signal
plop Path loss of pointer
prdi Path remote defect indicator
rdool Remote data out of lock
sd-ber Signal degradation BER exceed (for APS)
sf-ber Signal fail BER exceeded (for APS)
slof Section loss of frame error
slos Section loss of signal error
Setting the Line Alarm Indication Signal
The pos ais-shut command controls whether an Alarm Indication Signal - Line
(AIS-L) is sent to the far end SONET device when the POS interface is placed in an
administrative shutdown state. Use the pos ais-shut command, in Interface
Configuration mode, to enable sending an Alarm Indication Signal-Line (AIS-L):
MOT:7A(config-if)#pos ais-shut
Use the no pos ais-shut command, in Interface Configuration mode, to disable
sending the AIS-L on an administrative shutdown:
MOT:7A(config-if)#no pos ais-shut
Changing the POS Signal Rate
Table 10-7 describes the SONET signal mode command:
The following commands are used to switch the SONET signal mode to either OC12
or OC3:
Use the pos signal mode oc12 command, in Interface Configuration mode, to
optionally change the POS module SONET signal rate for OC12:
MOT:7A(config-if)#pos signal mode oc12
where:
oc12 is 622 Mbps signal rate.
Note: If the far end SONET device has Automatic Protection Switching (APS)
configured, an APS switch can be forced by using the pos ais-shut
command.
Table 10-7 SONET Signal Mode Command
pos signal mode Use to change the POS
module SONET signal
oc3 oc12 or oc3
Use the pos signal mode oc3 command, in Interface Configuration mode, to
return to the default signal rate of 155 Mbps:
MOT:7A(config-if)#pos signal mode oc3
where:
oc3 is signal rate 155 Mbps.
Specifying the POS Loopback Mode Type
You can use POS loopback commands to isolate the fault on an end-to-end circuit,
especially when the circuit is down.
Table 10-8 describes the POS loopback mode command:
Follow these steps to specify the POS loopback mode:
1. Use the pos loop internal command, in Interface Configuration mode, to specify
that the data transmitted out of the SONET framer device is directly looped to the
receive side of the SONET framer device:
MOT:7A(config-if)#pos loop internal
2. Use the pos loop line command, in Interface Configuration mode, to specify the
line loopback mode, which is used to connect the received SONET network
signal directly to the transmitted SONET network signal:
MOT:7A(config-if)#pos loop line
Table 10-8 SONET Signal Mode Command
pos loop Used to specify the POS
loopback mode type
none internal, line,
txrx-line,
txpos-rxpos
Note: When configured in line loop mode, the BSR never receives data from
the network. Use the no pos loop command to clear any loopbacks.
3. Use the pos loop txrx-line command, in Interface Configuration mode, to specify
that the data transmitted out of the SONET transceiver device is directly looped
to the receive side of the SONET transceiver device:
MOT:7A(config-if)#pos loop txrx-line
4. Use the pos loop txpos-rxpos command, in Interface Configuration mode, to
specify that any packets sent from the transmit packet FIFO are looped back to
the receive packet FIFO:
MOT:7A(config-if)#pos loop txpos-rxpos
Configuring POS Automatic Protection Switching
Both the POS module on the BSR and the far end device must support APS and be
configured for APS in order for APS to function. APS is configured on the BSR for
either a single POS module having redundant interfaces called Port APS or for a
redundant POS module. If APS is implemented on a single POS module on the BSR
only, a working interface and protection interface scheme is used. If APS is
implemented using two POS modules on the BSR, a working module and protection
module scheme is used.
Use the following sections if you are implementing interface-based redundancy:
Defining APS Groups for Working and Protection Interfaces
Managing APS Interface-based Redundancy
Use the following sections if you are implementing module-based redundancy:
Defining APS Groups for Working and Protection Modules
Managing APS Module-based Redundancy
APS Alarm Thresholds are set for both working and protection interfaces. The
following section applies to either module or interface-based redundancy:
Setting APS Alarm Thresholds
Table 10-9 describes the APS features and commands that are available on the POS
module:
Table 10-9 APS Commands
aps force Unconditionally switch the
working POS interface or
module to the protection
POS interface or module.
none Number of the
working or protection
POS interface or
module.
aps group Set the APS group number
for an interface or module.
none 0 - 3
aps lockout Lock the protection POS
interface or module.
none Number of the
protection POS
aps manual Manually switch from the
working interface or
module to the protection
none Interface number or
module.
aps protect Designate an interface or
module as protection.
none none
aps revert Set the wait to restore time
for the protection interface
or module to switch back
to the working interface or
module after it becomes
available.
none Time from 1 to 255
minutes and the
group number
containing the
working and
protection interfaces
or modules.
aps signal-degrade
ber threshold
Set the BER threshold for
b2 signal degrade alarms.
disabled 5 to 9 (10E-5 to 10E-9
Rate)
aps signal-fail ber
threshold
Set the BER threshold for
b2 signal fail alarms.
disabled 3 to 5 (10E-3 to 10E-5
Rate)
aps working Designate an interface or
module as working.
none none
Defining APS Groups for Working and Protection Interfaces
The working POS interface on the BSR and the working interface on the far end
SONET equipment carries all traffic, while the protection interface is in standby.
The BSR supports 1+1 unidirectional APS or bi-directional APS operation.
Uni-directional APS operation is the default. The 1+1 architecture has the head-end
signal continuously bridged to working and protection equipment so that the same
payloads are transmitted identically to the tail-end working and protection equipment.
At the tail end, the working and protection signals are monitored independently and
identically for failures. The receiving equipment chooses either the working or the
protection signal as the one from which to select the traffic.
When 1+1 unidirectional or bi-directional APS is used, the protection POS interface
on the BSR sends packets over the SONET link to the far end device, but the packets
are dropped by the receive port. Also, the protection interface on the far end device
can send packets over the SONET link to the POS interface on the BSR, where the
packets are dropped by the receive port.
The protection interface protects the working channel. The purpose of having both
working and protection interfaces on the BSR POS module and the far end device is
to ensure that packets can be transferred to the protection interface when a critical
alarms occur, or the fiber optic cable is physically cut or damaged.
APS groups are used to define a port pair, where one interface is configured as
working and the other is configured as protection. Up to two groups can be configured
on the BSR POS module.
Your APS configuration may vary slightly from the procedure identified below, but
the process is the same. The following steps show how to configure a group
containing a working interface and a protection interface:
1. Use the interface pos command, in Global Configuration mode, to designate the
working interface (POS interface 0):
Caution: Both ends of the SONET link must be configured for APS in order
for APS to work properly. If you have BSRs on both ends, then follow this
procedure. If there is different equipment involved, then the fiber optic
connection must be set up and physically connected in such a way that both
working POS interfaces are connected and both protection POS interfaces
are connected.
where:
X is the POS module slot on the BSR.
Y is POS interface which is either 0 or 1.
For example, the POS module is in slot 9 and the working port is 0:
MOT:7A(config)#interface pos 9/0
2. Use the aps group command, in Interface Configuration mode, to define a group
number for POS interface:
MOT:7A(config-if)#aps group <0-3>
where:
0-3 is the working group number.
For example, the following command adds interface 0 to port group 0:
MOT:7A(config-if)#aps group 0
3. Use the aps working command, in Interface Configuration mode, to define the
interface as working:
MOT:7A(config-if)#aps working <1-15>
where:
1-15 is the APS switching priority number.
4. Use the end command, in Interface Configuration mode, to exit the working POS
interface:
MOT:7A(config-if)#end
5. Use the interface pos command, in Global Configuration mode, to enter the POS
protection interface:
where:
Y is POS port which is either 0 or 1.
For example, the POS module is in slot 9 and the working interface is 1:
MOT:7A(config)#interface pos 9/1
6. Use the aps group command, in Interface Configuration mode, to define the
group number for the protection POS interface, so that it is in the same group as
the working interface:
MOT:7A(config-if)#aps group <0-3>
where:
<0-3> is the same group number as the working interface.
For example, the following command adds interface 1 to group 0:
MOT:7A(config-if)#aps group 0
7. Use the aps protect command, in Interface Configuration mode, to define this
POS interface as the protection interface:
MOT:7A(config-if)#aps protect
8. Use the show aps command, in Interface Configuration mode, to view the APS
configuration:
MOT:7A(config-if)#show aps
Configuring an APS Interface for Bi-directional Operation
APS is configured for uni-directional operation, by default, to work with far end
SONET equipment that uses uni-directional operation. If you need to configure APS
for bi-directional operation because the far end SONET device supports bi-directional
operation, use the no aps unidirectional command on the protection interface, in
Note: APS does not work until a group containing both a working and a
protection interface is configured.
Note: When the protect interface is configured as bi-directional, the working
interfaces and protect interfaces must cooperate to switch the working
interface to the protection interface. This happens automatically when the
SONET network equipment is in bi-directional mode.
MOT:7A(config-if)#no aps unidirectional <0-3>
where:
0-3 is the associated group number to which this interface belongs.
If you need to return the protection interface to uni-directional operation, use the
aps unidirectional command in Interface Configuration mode:
MOT:7A(config-if)#aps unidirectional <0-3>
where:
0-3 is the associated group number to which this interface belongs.
Defining APS Groups for Working and Protection Modules
APS module redundancy feature works only between two BSR 64000 systems. The
working POS module on the BSR and the working module on the far end BSR POS
carries all traffic, while the protection POS module is in standby.
The BSR supports 1:1 unidirectional APS or bi-directional APS operation.
Uni-directional APS operation is the default. The protection module protects the
working channel.
APS groups are used to define a module pair, where one module is configured as
working and the other is configured as protection. Up to four board groups can be
configured on the BSR. APS module redundancy has all SONET interfaces on the
working module protected by the corresponding interfaces on the protection module.
Your APS configuration may vary slightly from the procedure identified below, but
the process is the same. The following steps show how to configure a group
containing a working module and a protection module:
Caution: Both ends of the SONET link must be configured for APS in order
for APS to work properly.
1. Use the slot command, in Global Configuration mode, to enter Slot Configuration
mode and designate the working POS module slot:
MOT:7A(config)#slot <NUM>
where:
NUM is the POS module slot number on the BSR.
For example, the working POS module is in slot 9:
MOT:7A(config)#slot 9
2. Use the aps group command, in Slot Configuration mode, to define a group
number for a POS module:
MOT:7A(config-slot9)#aps group <0-3>
where:
0-3 is the working group number.
For example, the following command adds working POS module 9 to group 0:
MOT:7A(config-slot9)#aps group 0
3. Use the aps working command, in Slot Configuration mode, to define the POS
module as working:
MOT:7A(config-slot9)#aps working
4. Use the end command, in Slot Configuration mode, to exit the working POS
module:
MOT:7A(config-slot9)#end
5. Use the slot command, in Global Configuration mode, to enter the POS
protection module:
where:
NUM is the POS module slot on the BSR.
6. Use the aps group command, in Interface Configuration mode, to define the
group number for the protection POS module, so that it is in the same group as the
working POS module:
MOT:7A(config-slot11)#aps group <0-3>
where:
<0-3> is the group number.
For example, the following command adds POS module 11 to group 0:
MOT:7A(config-slot11)#aps group 0
7. Use the aps protect command, in Slot Configuration mode, to define this POS
interface as the protection interface:
MOT:7A(config-slot11)#aps protect
8. Use the show aps command, in Slot Configuration mode, to view the APS
configuration:
Configuring an APS Module for Bi-directional Operation
APS is configured for uni-directional operation, by default, to work with far end
SONET equipment that uses uni-directional operation. If you need to configure APS
for bi-directional operation because the far end SONET device supports bi-directional
operation, issue the no aps unidirectional command on the protection module in Slot
Configuration mode:
MOT:7A(config-slot11)#no aps unidirectional <0-3>
where:
0-3 is the associated group number to which this module belongs.
Note: APS does not work until a group containing both a working and a
protection module is configured.
Note: When the protection POS module is configured as bi-directional, the
working POS modules and protect POS modules must cooperate to switch
the transmit and receive SONET channel in a bi-directional way. This
happens automatically when the SONET network equipment is in
bi-directional mode.
If you need to return the protection module to uni-directional operation, use the aps
unidirectional command in Interface Configuration mode:
MOT:7A(config-slot11)#aps unidirectional <0-3>
where:
0-3 is the associated group number to which this module belongs.
Managing APS Interface-based Redundancy
The following sections describe the available APS management options:
Manually Switching a Module
Setting the Revert Timer
Forcing a Module to Switch
Locking Out a Protection APS Module
Manually Switching an Interface
The aps manual command can be used to manually switch the working interface to
the protection interface when maintenance must be performed on the working
interface. It is similar to the aps force command except that it has a lower priority for
performing the same task. For example, if the protection interface is in a fail
condition, the aps manual command does not execute and all traffic remains on the
working interface.
Follow these steps to transfer traffic from the working interface to the protection
interface:
1. To enter the working interface, use the interface pos command in Global
Configuration mode:
where:
Y is the number of the working POS port.
2. To switch to the protection interface, use the aps manual command:
MOT:7A(config-if)#aps manual <0-1>
where:
0-1 is the number of the protection POS interface.
3. To manually switch traffic back to the working POS interface after maintenance
is performed or before the wait to restore (WTR) time has expired, use the aps
manual command:
MOT:7A(config-if)#aps manual <0-1>
where:
0-1 is the number of the working POS interface.
Follow these steps to enable the automatic transfer of traffic from the protection
interface to the working interface, in a specified group, after a switch has occurred
and the failure condition is cleared on the working interface:
1. To enter the protection interface, use the interface pos command in Global
Configuration mode:
where:
Y is the number of the protect POS port.
2. To set the amount of time to wait to restore traffic from a protection interface
back to the working interface, use the aps revert command in Interface
Configuration mode:
MOT:7A(config-if)#aps revert <1-255> <0-3>
where:
1-255 is the revert time in minutes.
0-3 is the group number assigned to the working interface and protection
interface.
Note: The WTR time period is defined using the aps revert command.
Forcing an Interface to Switch
The aps force command is used to manually switch the working POS interface to the
protect POS interface or to switch the protection interface to the working interface in
instances when the aps revert command is not used. The aps force command differs
from the aps manual command because it unconditionally switches traffic regardless
of the condition of the other POS interface.
1. Use the interface pos command, in Global Configuration mode, to enter a
protection or working interface on the POS module:
where:
Y is the number of the protect or working POS port.
2. Use the aps force command, in Interface Configuration mode, to manually
switch the working POS interface to the protect POS interface or to switch the
protect POS interface to the working POS interface:
MOT:7A(config-if)#aps force <0-3>
where:
0-3 is the number of a working or protection POS interface.
Locking Out a Protection APS Interface
Follow these steps to lock out a protection POS interface.
1. Use the interface pos command, in Global Configuration mode, to enter the
protection interface that needs to be locked out:
where:
Y is the number of the protect or working POS interface.
2. Use the aps lockout command, in Interface Configuration mode, to lock the
protection POS interface:
MOT:7A(config-if)#aps lockout
3. Use the show aps command, in Interface Configuration mode, to verify the
protection POS interface is locked:
Managing APS Module-based Redundancy
The following sections describe the available APS management options:
The aps manual command can be used to manually switch the working POS module
to the protection POS module when maintenance must be performed on the working
interface. It is similar to the aps force command except that it has a lower priority for
performing the same task. For example, if the protection POS module is in a fail
condition, the aps manual command does not execute and all traffic remains on the
working POS module.
Follow these steps to transfer traffic from the working POS module to the protection
POS module:
1. Use the slot command, in Global Configuration mode, to enter the working POS
module:
where:
NUM is the working POS module slot number on the BSR.
Note: When the protection POS interface is locked, the protection channel
will never be used for traffic. It is locked out from protecting the working
interface.
2. Use the aps manual command to transfer to the protection POS module:
MOT:7A(config-slot9)#aps manual <0-15>
where:
0-15 is the protection POS module slot number.
3. Use the end command, in Slot Configuration mode, to exit the working POS
module:
MOT:7A(config-slot9)#end
4. When you need to switch traffic back to the working POS module after
maintenance is performed or before the wait to restore (WTR) time has expired,
enter the protection POS module:
where:
NUM is the protection POS module slot number on the BSR.
For example, the protection POS module is in slot 11:
MOT(config)#slot 11
5. Use the aps manual command, in Slot Configuration mode, to switch POS traffic
back to the working POS module:
MOT:7A(config-slot11)#aps manual <0-15>
where:
0-15 is the protection POS module slot number.
MOT:7A(config)#aps manual 9
Note: The WTR time period is defined using the aps revert command.
Follow these steps to enable the automatic transfer of traffic from the protection
module to the working module, in a specified group, after a switch has occurred and
the failure condition is cleared on the working module:
1. Use the slot command, in Global Configuration mode, to enter the protection
POS module:
where:
2. Use the aps revert command, in Slot Configuration mode, to set the amount of
time to wait to restore traffic from a protection POS module back to the working
POS module:
MOT:7A(config-slot11)#aps revert <1-255> <0-3>
where:
1-255 is the number of revert time in minutes.
0-3 is the group number assigned to the working POS module and protection
POS module.
The aps force command is used to manually switch the working POS module to the
protection POS module or to switch the protection POS module to the working POS
module in instances when the aps revert command is not used. The aps force
command differs from the aps manual command because it unconditionally switches
traffic regardless of the condition of the other POS module.
1. Use the slot command, in Global Configuration mode, to enter a protection or
working module:
where:
NUM is the working or protection POS module slot number on the BSR.
2. Use the aps force command, in Slot Configuration mode, to manually switch the
working POS module to the protect POS module or to switch the protect POS
module to the working POS module:
MOT:7A(config-slot9)#aps force <0-15>
where:
0-15 is the number of a working or protection POS interface.
For example, the working POS module in slot 9 must be forced to protection POS
module 11:
MOT:7A(config-slot9)#aps force 11
Follow these steps to lock out a protection POS module:
1. Use the slot command, in Global Configuration mode, to enter the protection
POS module that needs to be locked out:
where:
For example, the protection POS module is in slot 11:
2. Use the aps lockout command, in Slot Configuration mode, to lock the protection
POS module:
MOT:7A(config-slot11)#aps lockout
Note: When the protection POS interface is locked, the protection module is
never used for traffic. It is locked out from protecting the working module.
3. Use the show aps command, in Slot Configuration mode, to verify the protection
POS interface is locked:
Setting APS Alarm Thresholds
APS Alarm thresholds are used as one of the triggers to switch to a protection POS
interface when a b2 signal degrade or b2 signal fail condition occurs on the interface.
For example, when the APS threshold for B2 errors is exceeded on the working POS
interface 0, the POS link switches to the protection POS interface 1.
Follow these steps to set APS alarm thresholds:
1. Use the aps signal-degrade ber threshold command, in Interface Configuration
mode, to configure the BER threshold for the b2 signal degrade alarm:
MOT:7A(config-if)#aps signal-degrade ber threshold <5-9>
where:
<5-9> is the 10E-5 to 10E-9 rate.
To disable the setting, use the no aps signal-degrade ber threshold command,
in Interface Configuration mode, as shown below:
MOT:7A(config-if)#no aps signal-degrade ber threshold <5-9>
2. To configure the BER threshold for the b2 signal failure alarm, use the aps
signal-fail ber threshold command, in Interface Configuration mode, as shown
below:
MOT:7A(config-if)#aps signal-fail ber threshold <3-5>
where:
<3-5> is the 10E-3 to 10E-5 rate.
3. Use the show controllers pos command, in Interface Configuration mode, to
verify APS BER thresholds:
MOT:7A(config-if)#show controllers pos
Note: APS alarm thresholds apply to both APS interface redundancy and
APS POS module redundancy.
Gathering POS Network Information
The following sections describe how to use show commands to gather POS
information for the PPP link, SONET interface, and the physical SONET link:
Displaying PPP Link and Statistics Information
Displaying POS Interface Information
Displaying Physical SONET Link and Alarm Information
Displaying APS Information
Displaying PPP Link and Statistics Information
1. To display PPP link information, use the show ppp info command in Interface
Configuration mod. Figure 10-2 displays typical show ppp info command
output: :
Figure 10-2 show ppp info Command Output
pos 11/0
LCP Stats
LCP phase DEAD
LCP state INITIAL
passive ON
silent OFF
restart OFF
lcp echo timer ON
lcp echos pending 0
lcp echo number 0
lcp echo interval 10
lcp echo fails 5
IPCP Stats
IPCP state INITIAL

pos 11/1
LCP Stats
LCP phase DEAD
LCP state INITIAL
passive ON
silent OFF
restart OFF
lcp echo timer ON
2. To display PPP statistics, use the show ppp statistics command in Interface
Configuration mode. Figure 10-3 displays typical show ppp statistics command
output:
Figure 10-3 show ppp statistics Command Output
Displaying POS Interface Information
To display configuration information for the POS interface, use the show interfaces
pos command in Interface Configuration mode:
MOT:7A(config-if)#show interfaces pos <X/Y>
where:
pos 11/0
Input
total bytes 0
total packets 44371
ip packets 0
Output
total bytes 0
total packets 0
ip packets 0
pos 11/1
Input
total bytes 0
total packets 0
ip packets 0
Output
total bytes 0
total packets 0
ip packets 0
Figure 10-4 displays typical show interfaces pos command output:
Figure 10-4 show interfaces pos Command Output
Table 10-10 describes the show interfaces pos command output fields.
Table 10-10 show interfaces pos Output Fields and Descriptions
Field Description
POS1/0 is up/down Indicates whether the physical link is currently up or down.
line protocol is up/down Indicates whether the PPP link or protocol is currently up
or down.
Hardware is Hardware type.
Internet address is IP address and subnet mask.
MTU Maximum Transmission Unit of the interface.
BW Bandwidth of the interface in KBIT/S per second.
pos 11/0 is up, line protocol is up
Hardware is pos
Internet address is 192.168.16.66/24
MTU 1500 bytes, BW 155000 Kbits
MPLS MTU 1500 bytes
Encapsulation PPP, crc 16
Keepalive set (10 sec)
Scramble enabled
LCP Initial, IPCP Initial, OSICP Initial, MPLSCP Initial
Last input 3d18h, output 3d18h
Last clearing of
"show interfaces
" counters never
Last state change 3d18h, 0 interface resets
Queueing strategy: FIFO
Output queue 0/100, 0 drops; input queue 0/0, 0 drops
27240 packets input, 2395832 bytes
0 input errors, 2 CRC, 21 overruns
0 runts, 1 giants, 36 aborts
27241 packets output, 2286960 bytes
0 output errors, 44 underruns
14 carrier transitions
Encapsulation Encapsulation method assigned to the interface which in
this instance is PPP with the CRC sequence is set to 16
bytes.
loopback Indicates whether loopbacks are set.
keepalive Indicates whether keepalives are set.
scramble Indicates whether payload scrambling is enabled or
disabled.
LCP Indicates if the Link Control Protocol is open or closed.
LCP is used to negotiate PPP configuration parameters.
IPCP Indicates if the Internet Protocol Control Protocol is open
or closed. IPCP is used for transporting IP traffic over a
PPP connection.
Last input Number of hours, minutes, and seconds since the last
packet was successfully received by an interface.
Indicates a dead interface failure.
(Last) output Number of hours, minutes, and seconds since the last
packet was successfully transmitted by an interface.
Last clearing of show
interfaces counters
Describes the last time that the counters were cleared for
the show interfaces command statistics.
Last state change Number of hours, minutes, and seconds since the last
state change of the POS interface.
Queueing strategy First-in, first-out queuing strategy (other queueing
strategies are priority-list, custom-list, and weighted fair).
Output queue, drops
input queue, drops
Number of packets in output and input queues. Each
number is followed by a slash, the maximum size of the
queue, and the number of packets dropped because a
queue was full.
packets input Total number of error-free packets received by the system.
bytes (input) Total number of bytes, including data and MAC
encapsulation, in the error-free packets received by the
system.
no buffer Number of received packets discarded because there was
no buffer space in the main system. Compare with ignored
count. Broadcast storms on Ethernets and bursts of noise
on serial lines can cause no input buffer events.
Field Description
Received <n> broadcasts Where n is the total number of broadcast or multicast
packets received by the interface.
multicasts Indicates the number of multicast packets received by the
interface.
runts Number of packets that are discarded because they are
smaller than the medium's minimum packet size.
giants Number of packets discarded because they exceed the
medium's maximum packet size.
input errors Total number of no buffer, runts, giants, CRCs, frame,
overrun, ignored, and abort counts. Other input-related
errors can also increment the count, so that this sum might
not balance with the other counts.
CRC Cyclic redundancy checksum generated by the originating
LAN station or far-end device does not match the
checksum calculated from the data received.
overruns Number of times the serial receiver hardware was unable
to transfer received data to a hardware buffer because the
input rate exceeded the receiver ability to handle the data.
aborts Illegal sequence of one bits on the interface.
parity Report of the parity errors on the interface.
packets output Total number of messages transmitted by the system.
bytes (output) Total number of bytes, including data and MAC
encapsulation, transmitted by the system.
underruns Number of times that the far-end transmitter has been
running faster than the near-end router's receiver can
handle.
output errors Sum of all errors that prevented the final transmission of
datagrams out of the interface being examined.
collisions Number of collisions on the interface.
interface resets Number of times an interface has been completely reset.
carrier transitions Number of times the carrier detect signal of the interface
has changed state.
Field Description
Displaying Physical SONET Link and Alarm Information
SONET alarm hierarchy rules mandate that only the most severe alarm of an alarm
group is reported. Reported alarms are logged to the console.
To display information about the POS module hardware, SONET alarms and BER
thresholds, use the show controllers pos command, in Privileged EXEC mode, as
follows:
MOT:7A#show controllers pos <X/Y>
where:
Figure 10-5 displays a portion of the show controllers pos command output.
Figure 10-5 show controllers pos Command Output
Note: The Active Defect field in the show controllers pos command output
shows all alarms currently present on the interface.

Interface HSIM (2-port POS (OC3/12)) on slot 11
State (UpTime): RUN ( 0w1d1h)
Boot ROM: RDN ROM Version: 3.1.0.01 Creation Date: Thu Sep 18 16:51:16 EDT
Image: 3.1.0T00P20.KRAU
Date Built: Thu Oct 23 12:04:43 EDT 2003
CPU: RDN Inc. HSIM8260 -- MPC8260 PowerQUICC II HSIM
Memory Size: 64 MB
Format Version: 0
Assembly Type : 3
Part Number : PCA-0071-01
HW Revision : TR
Serial Number : 027000471
Product Number: BSR 64000
FPFE FPGA Version: 0060
BufMgr FPGA Version: 00E4
BufMgr Chip Version: F5
Table 10-11 defines the SONET Alarms and BER threshold information that is
reported on the POS interface console:
Table 10-11 SONET Alarms and Identifications
Alarm Identification
POS X/Y POS slot X and interface Y.
SECTION Errors that occur in the SONET Section. A section may be between
Customer Premises Equipment (CPE) and SONET Service Provider
Equipment (SPE).
SLOS Section Los Of Signal errors.
SLOS is detected when an all-zeros pattern on the incoming SONET
signal lasts 19(+-3) microseconds or longer.
SLOF Section loss of frame errors.
SLOF is detected when a severely errored frame (SEF) defect on the
incoming SONET signal persists for 3 milliseconds.
b1-tca B1 BER TCA (crossing threshold).
For B1, the bit interleaved parity error report is calculated by
comparing the BIP-8 code with the BIP-8 code extracted from the B1
byte of the next frame. Differences indicate that section level bit
errors have occurred.
LINE Errors that occur in the SONET Line. A line may be between a
SONET SPE, regenerators, and another SONET SPE.
L-AIS Line-alarm Indication Signal. L-AIS is sent by the section terminating
equipment (STE) to alert the downstream LTE that a LOS or LOF
defect has been detected on the incoming SONET section.
L-RDI Line-remote Defect Indication. L-RDI is reported by the downstream
LTE when it detects LOF, LOS, or AIS.
L-REI Line-remote Error Indicator. L-REI conveys a B2 error count detected
by the LTE.
sf-ber The line is considered in failure.
sd-ber B2 errors have exceeded the threshold and the line is considered
degraded.
b2-tca B2 BER TCA (crossing threshold)
comparing the BIP-8/24 code with the BIP-8 code extracted from the
B2 byte of the next frame. Differences indicate that line level bit
errors have occurred.
PATH Errors that occur in the SONET Path. A path may be between a CPE,
SONET SPE, regenerators, and another SONET SPE and CPE.
PLOP Path Loss Of Pointer. PLOP is reported as a result of an invalid
pointer (H1, H2) or an excess number of new data flag (NDF)
enabled indications.
P-AIS Path-Alarm Indication Signal errors.
PAIS is sent by line terminating equipment (LTE) to alert the
downstream path terminating equipment (PTE) that it has detected a
defect on its incoming line signal.
P-RDI Path Remote Defect Indication errors. P-RDI is reported by the
downstream PTE when it detects a defect on the incoming signal.
b3-tca B3 BER TCA (crossing threshold).
comparing the BIP-8 code with the BIP-8 code extracted from the B3
byte of the next frame. Differences indicate that path level bit errors
have occurred.
Active Defects All currently active SONET defects.
Active Alarms Current Alarms as enforced by SONET Alarm Hierarchy.
Alarm reporting
enabled for
Alarms that were enabled through the use of the pos report
command in Interface Configuration mode.
APS Describes the working and protect interfaces for the group(s).
Path Signal Label The value extracted from the SONET path signal label byte (C2).
Synchronous
Status Message
Bits 5 through 8 of the S1 Byte which describe the synchronization
status of the Near End device.
CLOCK
RECOVERY
Displays that the recovered clock is from the received SONET signal.
RDOOL Receive Data Out Of Lock Errors. RDOOL describes the status of the
clock recovery. If a RDOOL alarm has been detected, this indicates
that the clock recovery phased lock loop is unable to lock to the
receive stream.
PATH TRACE
BUFFER
SONET path trace buffer is used to communicate information
regarding the remote hostname, interface name/number and IP
address or other user designated parameters. J0 indicates a section
and J1indicates a path message.
Displaying APS Information
To view APS configuration and statistics information for groups containing working
and protection interfaces, use the show aps command in Interface Configuration
mode. Figure 10-6 displays typical show aps command output:
Figure 10-6 show aps Command Output
APS BER
thresholds
List of APS BER thresholds configured with the aps signal-degrade
ber threshold and aps signal-fail ber threshold commands. The
signal degrade bit error rate (sd-ber) threshold is from 5 to 9 (10E-5
to 10E-9). The signal fail bit error rate (sf-ber) threshold is 3 to 5
(10E-3 to 10E-5).
TCA thresholds List of TCAs configured with the pos threshold command in
Interface Configuration mode.
APS: Slot 11 : Interface 0 assigned to Port Group 0
APS: 1+1, Bidirectional, Revertive : revert time = 1 min
Group Status = Group OK
Info = Valid Protection Port Valid Working Port
Minor = 0x0
Major = 0x0
APS: Working Channel Slot 11 : interface 0
Port Status = Port Active
APS: Slot 11 : interface 1 assigned to Port Group 0
APS: 1+1, Bidirectional, Revertive : revert time = 1 min
Group Status = Group OK
Info = Valid Protection Port Valid Working Port
Minor = 0x0
Major = 0x0
APS: Protection Channel Slot 11 : interface 1
Port Status = OK
TX K1 0x00 : BITS 1-4 -> None : BITS 5-8 -> Channel 0
TX K2 0x05 : BITS 1-4 -> Channel 0 : BIT 5 -> 1+1 : BITS 6-8 -> BI-D
RX K1 0x00 : BITS 1-4 -> None : BITS 5-8 -> Channel 0
RX K2 0x05 : BITS 1-4 -> Channel 0 : BIT 5 -> 1+1 : BITS 6-8 -> BI-D
11
Configuring IS-IS
Introduction
The integrated Intermediate System to Intermediate System (IS-IS) is a link state
based intra-domain routing protocol used to build a complete and consistent picture of
a networks topology by sharing link state information across all network
Intermediate System (IS) devices. IS-IS is based on an Shortest Path First (SPF)
routing algorithm and shares all the advantages common to other link-state protocols.
It also routes both IP packets and pure OSI packets with no extra encapsulation by
design. IS-IS supports type of service (TOS) identifiers, IP subnetting, variable subnet
masks, external routing, and authentication.
IS-IS routing decisions are made on two levels. Level 1 routers know the topology of
their network within an area and level 2 routers are used to route between different
areas within a routing domain. If a level 1 router has no knowledge of a specific
destination address, it passes the traffic to a level 2 router. Level 2 routers know
which addresses are reachable through each Level 2 router, and they do not need to
know the topology within Level 1 areas. Level 2 routers can also exchange
information with external routers outside their routing domain.
IS-IS support for IPv6 implements single-topology IPv6 IS-IS functionality. A single
shortest path first (SPF) per IS-IS level is used to determine IPv4 and IPv6 routes. The
use of a single SPF means that both IPv4 IS-IS and IPv6 IS-IS routing protocols must
share a common network topology. All routers within an IS-IS area (Level 1 routing)
or domain (Level 2 routing) must also support the same set of address families: IPv4
only, IPv6 only, or both IPv4 and IPv6.
IS-IS as an Interior Gateway Protocol (IGP) is mostly analogous to Open Shortest
Path First (OSPF) in principle and operation. The one major difference between IS-IS
and OSPF is that IS-IS operates directly on top of Layer-2 and mostly oblivious to the
Layer-3 addressing scheme for topology and route computation (at-least within an
area). This feature of IS-IS allows it to be a successful integrated routing protocol
supporting multiple Layer-3 networking protocols like Connection-less Network
Service (CLNS), IPv4, and IPv6 with a common routing protocol engine and
framework. IS-IS protocol PDUs are extensible to support various Layer-3 specific
(and other Layer-3 independent) extensions required to support multiple network
layer protocols.
The following tasks are required to implement IS-IS on your network:
n Enabling IS-IS
n Entering/Exiting IPv6 Address Family Configuration Mode (if applicable)
n Redistributing Routes into IS-IS
The following optional tasks are used to manage IS-IS on your network:
n IS-IS Authentication
n Managing IS-IS on the BSR
n Configuring IS-IS on an Interface
n Displaying IS-IS Information
Enabling IS-IS
You must enable the IS-IS process and assign IS-IS to a specific interface in order to
implement IS-IS on your network.
Follow these steps to enable IS-IS on the router:
1. Use the router isis command, in Global Configuration mode, to enable IS-IS
routing, specify an IS-IS process for IP communication, and enter IS-IS Router
Configuration mode:
MOT:7A(config)#router isis [WORD]
where:
WORD is the name for the routing process. If the tag is not specified, a null
tag is assumed. This keyword is not supported at this time.
Release 6.3.1 Configuring IS-IS
Network Entity Titles (NETs) define the area address and the system ID for an IS-IS
router. Most end systems and intermediate systems have one NET. Intermediate
systems that participate in multiple areas can have multiple NETs.
2. Use the net command, in IS-IS Router Configuration mode, to define a Network
Entity Title (NET):
MOT:7A(config-isis)#net <XX.XXXX.XXXX. ... .XXXX.XX>
where:
XX.XXXX.XXXX. ... .XXXX.XX is an area ID, a system ID, and an n-selector. The
Area ID, System ID and the n-selector are concatenated together with a period
between them each.
The following example configures IS-IS for IP routing, with an area ID of
01.0001, a system ID of 0000.0000.0002, and an n-selector of 00. The Area
ID, System ID and the n-selector are concatenated together with a period
between them each.
MOT:7A(config-isis)#net 01.0001.0000.0000.0002.00
Use the following criteria to interpret the IS-IS NET address format:
n The first portion of the NET address is the area number, which is a variable
number from 1 through 13 bytes. The first byte of the area number (01) is the
authority and format indicator (AFI). The next bytes are the assigned domain
(area) identifier, which can be from 0 through 12 bytes. In the example above, the
area identifier is 0001.
n The next six bytes form the system identifier (SYSID). The SYSID can be any six
bytes that are unique throughout the entire domain. The system identifier
commonly is either the Media Access Control (MAC) address or the IP address
expressed in binary-coded decimal (BCD).
n The last byte (00) is the n-selector.
3. Use the interface command, in Global Configuration mode, to select the
interface on which you plan to configure IS-IS.
Note: Under most circumstances, one NET is configured.
MOT:7A(config)#interface {ethernet <X/Y> | gigaether <X/Y> | loopback
<1-255> }
where:
ethernet X/Y is the Ethernet interface slot and port number.
gigaether X/Y is the Gigabit Ethernet interface slot and port number.
loopback 1-255 is the loopback interface number.
4. Use the ip router isis or the ipv6 router isis command, in Interface
Configuration mode, to enable IS-IS routing on the interface. See Setting the
IS-IS Operational Mode below.
- or -
Use the passive-interface command, in IS-IS Router Configuration mode, to
allow the IS-IS interface to receive IS-IS network information, but not send IS-IS
network information:
MOT:7A(config-isis)#passive-interface {cable <X/Y> | ethernet <X/Y> |
gigaether <X/Y> | loopback <1-255>}
where:
cable X/Y is the cable interface slot and MAC domain number.:
Note: IS-IS is not supported on cable or tunnel interfaces.
Note: IS-IS is not supported on a loopback interface that is a cable bundle
master.
Setting the IS-IS Operational Mode
The BSR supports three IS-IS operating modes in a single topology. Use the ip router
isis and ipv6 router isis command, in Interface Configuration Mode for Ethernet or
Gigabit Ethernet interfaces, to set the IS-IS operational mode, as follows:
IPv4 Only
MOT:7A(config-if)#ip router isis
IPv6 Only
MOT:7A(config-if)#ipv6 router isis
IPv4 and IPv6 Together
MOT:7A(config-if)#ip router isis
MOT:7A(config-if)#ipv6 router isis
Note: For IPv6-only operation, the BSR does not check any IPv4 conditions
and all IPv4 information is dropped.
Note: To use IS-IS for both IPv4 and IPv6 routing (IPv4/IPv6 mode), any
interface configured for IPv4 IS-IS must also be configured for IPv6 IS-IS and
vice versa.
Entering/Exiting IPv6 Address Family
Configuration Mode
IS-IS Address Family Configuration mode allows a user to configure IPv6-specific
settings for an IS-IS routing session.
1. Use the address-family ipv6 command, in IS-IS Router Configuration mode, to
enter IPv6 Address Family Configuration mode:
MOT:7A(config-isis)# address-family ipv6
The command line prompt changes to:
MOT:7A(config-isis-af)#
2. Use the exit-address-family command to return to IS-IS Router Configuration
mode.
3. Use the end or exit commands to return to Global Configuration mode.
Redistributing Routes into IS-IS
Follow these steps to redistribute routes into IS-IS:
1. Enter the IS-IS routing process in which the routes are to be redistributed:
MOT:7A(config)#router isis
2. Select one or more of the following options to redistribute routes from a specified
protocol:

Note: The distance and maximum-paths commands used in IS-IS Address
Family Configuration mode apply to IPv6 only while the matching distance
and maximum-paths commands in IS-IS Router Configuration mode are
specific to IPv4.
Use the redistribute ospf command in Router Configuration mode to
redistribute OSPF routes into IS-IS:
MOT:7A(config-isis)#redistribute ospf [level-1 | level-1-2 | level-2 |
match {external | internal} | metric {<0-63> |<0-16777214>} |
metric-type [external | internal] | route-map <WORD>}
level-1 indicates a Level 1 IS-IS router.
level-1-2 indicates a Level 1 and 2 IS-IS router.
match is the criteria by which OSPF routes are redistributed into IS-IS.
internal are routes that are internal to an autonomous system.
external are routes external to an autonomous system, but are imported into
OSPF as either Type 1 or Type 2 external route.
metric 0-63 is the assigned narrow metric style value for OSPF routes.
metric 0-16777214 is the assigned wide metric style value for OSPF routes.
metric-type external is used to redistribute external IS-IS metric-types.
metric-type internal is used to redistribute internal IS-IS metric-types.
route-map <WORD> is the OSPF route-map name.
Use the redistribute connected command in Router Configuration mode to
redistribute connected routes into IS-IS:
MOT:7A(config-isis)#redistribute connected [level-1 | level-1-2 |
level-2 | metric {<0-63> |<0-16777214>} | metric-type [external | internal]
| route-map <WORD>}
where:
Note: Metric styles are specified with the metric-style command.
metric 0-63 is the assigned narrow metric style value for connected route.
metric 0-16777214 is the assigned wide metric style value for the connected
route.
route-map <WORD> is the connected route-map name.
Use the redistribute bgp command in Router Configuration mode to
redistribute BGP routes into IS-IS:
MOT:7A(config-isis)#redistribute bgp [level-1 | level-1-2 | level-2 |
metric {<0-63> |<0-16777214>} | metric-type [external | internal] |
route-map <WORD>}
where:
metric 0-63 is the assigned narrow metric style value for BGP routes.
metric 0-16777214 is the assigned wide metric style value for BGP routes.
route-map <WORD> is the BGP route-map name.
Use the redistribute rip command in Router Configuration mode to
redistribute RIP routes into IS-IS:
MOT:7A(config-isis)#redistribute rip level-1 | level-1-2 | level-2 |
route-map <WORD>}
where:
metric 0-63 is the assigned narrow metric style value for RIP routes.
metric 0-16777214 is the assigned wide metric style value for RIP routes.
route-map <WORD> is the RIP route-map name.
Use the redistribute static command in Router Configuration mode to
redistribute static routes into ISIS:
MOT:7A(config-isis)#redistribute static level-1 | level-1-2 | level-2 |
route-map <WORD>}
where:
metric 0-63 is the assigned narrow metric style value for static routes.
metric 0-16777214 is the assigned wide metric style value for static routes.
route-map <WORD> is the static route-map name.
IS-IS Authentication
Motorolas IS-IS security implementation offers an authentication mechanism to
prevent unauthorized routers from forming adjacencies or injecting TLVs. Both clear
text and MD5 authentication are available where the configured password is
transmitted inside IS-IS PDUs as unencrypted in plain text or encrypted with MD5.
Authentication mode control can be enabled globally or on a per-interface basis.
Passwords can be specified for area, domain, or interface authentication.
IS-IS global authentication mode control (MD5 or clear text) applies to Link-state
PDUs (LSPs), Complete Sequence Number PDUs (CSNPs) and Partial Sequence
Number PDUs (PSNPs).
n area authentication passwords are set for Level 1 LSPs, CSNPs and PSNPs.
n domain authentication passwords are set for Level 2 LSPs, CSNPs and PSNPs.
IS-IS interface authentication mode control applies to Hello packets. An interface
IS-IS password is set for Hello packets.
This section describes the following IS-IS security configuration tasks:
n Specifying IS-IS Global Authentication Mode
n Assigning IS-IS Area or Domain Passwords
n Specifying IS-IS Interface Authentication Mode
n Configuring an Interface Message Digest Key
n Assigning a Password to an IS-IS Interface
Specifying IS-IS Global Authentication Mode
Use the authentication mode command, in IS-IS router configuration mode, to
specifiy global IS-IS authentication mode control, as shown below:
MOT:7A(config-isis)#authentication mode [md5 | text ]
where:
md5 enables MD5 based authentication.
text enables clear text authentication.
Assigning IS-IS Area or Domain Passwords
Passwords can be assigned to IS-IS areas and domains.
Domain and area password authentication can be configured separately. It is also
possible to configure either one or both types of this password authentication.
The area authentication password is inserted and checked for Level 1 LSPs, CSNPs,
and Partial Sequence Number PDUs (PSNPs).
The domain authentication password is inserted and checked for Level 2 LSP, CSNP,
and PSNPs.
Follow these steps to configure either area or domain authentication passwords:
n Use the area-password command, in IS-IS Router Configuration mode, to
configure an IS-IS area authentication password:
MOT:7A(config-isis)#area-password <WORD>
where:
WORD is the unencrypted text password, 1-8 characters in length.
n Use the domain-password command, in IS-IS Router Configuration mode, to
configure an IS-IS routing domain authentication password:
MOT:7A(config-isis)#domain-password <WORD>
where:
Specifying IS-IS Interface Authentication Mode
Use the authentication mode command, in IS-IS router configuration mode, to
specifiy global IS-IS authentication mode control for an interface, as shown below:
MOT:7A(config-if)#isis authentication mode {md5 | text }
where:
md5 enables MD5 based authentication.
text enables clear text authentication.
Configuring an Interface Message Digest Key
Use the isis message-digest-key md5 command is used to configure a Message
Digest 5 (MD5) Authentication key for an IS-IS interface, as shown below:
MOT:7A(config-if)#isis message-digest-key md5 <1-255> md5 {7
<password> | <password>} [level-1 | level-2 ]
where:
1-255 is the range of numbers from which an MD5 secret Key ID can be selected.
7 <password> specifies a hidden (encrypted) MD5 password between 18-50
characters.
password specifies an MD5 cleartext password between 1-16 characters.
level-1 configures MD5 for Level 1 IS-IS routing.
level-2 configures MD5 for Level 2 IS-IS routing.
Assigning a Password to an IS-IS Interface
You can assign a password to insert authentication TLVs onto hello packets
transmitted from an IS-IS enabled interface. This authentication can be used to make
sure that only authorized neighbors form an IS-IS adjacency over a given interface.
The password is configured on a per-interface base and must be specified for Level 1
and Level 2 independently.
Specifying Level 1 or Level 2 configures the password for only Level 1 or Level 2
routing, respectively.
By default, authentication is disabled.
Use the isis password command, in Interface Configuration mode, to configure the
authentication password for the specified interface:
MOT:7A(config-if)#isis password <WORD> [level-1 | level-2]
where:
Managing IS-IS on the BSR
The following sections are used to manage IS-IS on the BSR:
n Specifying Router-Level Support
n Configuring a Default Route into an IS-IS Domain
n Configuring the Administrative Distance for IS-IS
n Summarizing IP Address Ranges
n Enabling the LSP Overload Bit
n Configuring the SPF Hold Time
n Configuring a Passive Interface for IS-IS
Specifying Router-Level Support
Use the is-type command, in IS-IS Router Configuration mode, to specify that the
BSR acts as a Level 1 (intra-area) router, as both a Level 1 router and a Level 2
(inter-area) router, or as a Level-2 router only:
MOT:7A(config-isis)#is-type {level-1 | level-1-2 | level-2-only}
level-2-only indicates a Level 2 IS-IS router.
Configuring a Default Route into an IS-IS Domain
The BSR can be configured to force a default route into the IS-IS routing domain:
Use the default-information originate command, in IS-IS Router Configuration
mode, to configure a default route into the IS-IS routing domain:
MOT:7A(config-isis)#default-information originate [level-1 | level-1-2 |
level-2-only]
where:
level-2-only indicates a Level 2 IS-IS router. This is the default summary.
Configuring the Administrative Distance for IS-IS
An administrative distance is a rating of the trustworthiness of a routing information
source, such as an individual router or a group of routers. Numerically, an
administrative distance is an integer between 1 and 255. The higher the value, the
lower the trust rating. For example, an administrative distance of 255 means the
routing information source cannot be trusted and should be ignored. The default
administrative distance for IS-IS is 115.
Use the distance command, in IS-IS Router Configuration mode (for IPv4), or in
IS-IS Address Family Configuration mode (for IPv6), to set the administrative
distance for the IS-IS router:
MOT:7A(config-isis)#distance <1-254>
- or -
MOT:7A(config-isis-af)#distance <1-254>
where:
1-254 is the IS-IS routing administrative distance. The default is 115.
Configuring Maximum Paths for IS-IS IPv6
To configure the maximum number of parallel routes that an IS-IS IPv6 routing
process can support, use the maximum-paths command in IS-IS Address Family
Configuration mode.
MOT:7A(config-isis-af)#maximum-paths <1-2>
where:
1-2 is the maximum number of parallel routes.
The no maximum-paths command cancels the number of maximum paths.
Summarizing IP Address Ranges
A range of IP addresses listed in an LSP can be represented by a summary address.
Routes learned from other routing protocols also can be summarized. The metric used
to advertise the summary is the smallest metric of all the more specific routes.
Use the summary-address command, in IS-IS Router Configuration mode, to create
a summary address for a range of IP addresses:
MOT:7A(config-isis)#summary-address <A.B.C.D> <A.B.C.D> [level-1 |
level-1-2 | level-2 | metric <1-4294967295>]
where:
A.B.C.D is the summary IP address.
A.B.C.D is the subnetwork mask for the summary IP address.
level-2 indicates a Level 2 IS-IS router. This is the default summary.
metric 1-4294967295 sets a metric for the summary route.
Enabling the LSP Overload Bit
The LSP overload bit is enabled for the IS-IS routing process to ensure that no paths
through the BSR are seen by other routers in the IS-IS area when the Link State
routing table on the BSR is incomplete or inaccurate. However, IP prefixes directly
connected to the BSR continue to be reachable.
Use the set-overload-bit command, in IS-IS Router Configuration mode, to allow
other routers on the network to ignore IS-IS routing problems on the BSR in their SPF
calculations until the IS-IS routing process on the BSR has recovered from its
problems:
MOT:7A(config-isis)#set-overload-bit
Configuring the SPF Hold Time
The spf-hold-time command is used to configure the shortest path first (SPF) hold
interval. The SPF hold interval is the minimum hold time between two consecutive
SPF calculations in seconds. The no spf-hold-time command restores the default hold
interval value of two seconds.
Use the spf-hold-time command, in IS-IS Router Configuration mode, to configure
the hold time between two consecutive SPF calculations.
MOT:7A(config-isis)#spf-hold-time <1-120>
where:
1-120 is the hold-time in seconds between consecutive SPF calculations.
Configuring a Passive Interface for IS-IS
You can configure a passive interface to learn an interface prefix without forming
adjacencies. A passive interface does not transmit routing updates.
Use the passive-interface command, in IS-IS Router Configuration mode, to create a
passive IS-IS interface, as shown in the following example:
MOT:7A(config-isis)#passive-interface {cable <X/Y> | ethernet <X/Y> |
gigaether <X/Y> | loopback <1-255>}
where:
cable X/Y is the cable interface slot and MAC domain number.
Note: You must use the no set-overload-bit command to re-enable the LSP
overload bit.
Configuring IS-IS on an Interface
The following configuration tasks performed on the designated IS-IS interface are
optional. They are used to adapt IS-IS to your network. When you configure IS-IS
parameters on a BSR interface, ensure that they are consistent with other routers on
your network.
n Specifying the Interface Circuit Type
n Configuring IS-IS Link-State Cost Metrics
n Setting the Advertised Hello Interval
n Specifying the Advertised Hello Multiplier
n Setting the Advertised CSNP Interval
n Setting the LSP Interval
n Setting the LSP Retransmission Interval
n Setting the LSP Retransmit Throttle Interval
n Setting the Designated Router Priority
Note: IS-IS is not supported on a loopback interface that is a cable bundle
master.
Specifying the Interface Circuit Type
The default IS-IS interface circuit type is for Level 1 and Level 2. Use the isis
circuit-type command, in Interface Configuration mode, to select the IS-IS interface
circuit type of adjacency desired for neighbors on the BSR interface (IS-IS interface
circuit type):
MOT:7A(config-if)#isis circuit-type {level-1 | level-1-2 | level-2-only}
where:
level-1 indicates that a Level 1 adjacency may be established if there is at least
one area address in common between this system and its neighbors.
level-1-2 indicates that a Level 1 and 2 adjacency is established if the neighbor is
also configured as level-1-2 and there is at least one area in common. If there is
no area in common, a Level 2 adjacency is established.
level-2-only indicates that a Level 2 adjacency is established only if the neighbor
is configured exclusively to be a Level 2 router.
Configuring IS-IS Link-State Cost Metrics
You can configure a cost for a specified interface. A cost is an arbitrary routing metric
value assigned for crossing or intersecting networks. This metric can be applied to
both Level 1 and/or Level 2 routing.
Use the isis metric command, in Interface Configuration mode, to configure the
metric cost for the specified IS-IS interface:
MOT:7A(config-if)#isis metric {<0-63> |<0-16777214>} [level-1 | level-2]
where:
0-63 is the assigned narrow metric style value for the interface.
0-16777214 is the assigned wide metric style value for the interface.
level-1 is for Level 1 IS-IS routing.
Setting the Advertised Hello Interval
IS-IS hello packets are broadcast to discover the identity of neighboring IS-IS systems
and to determine whether the neighbors are Level 1 or Level 2 intermediate systems.
The hello-interval is the amount of time between sending hello packets.
Use the isis hello-interval command, in Interface Configuration mode, to specify the
length of time between hello packets that the BSR sends on either the Level 1 or Level
2 IS-IS router interface:
MOT:7A(config-if)#isis hello-interval <1-65535> [level-1 | level-2]
where:
1-65535 is the ISIS hello interval in seconds.
The hello interval can be configured independently for Level 1 and Level 2.
Specifying the Advertised Hello Multiplier
Use the isis hello-multiplier command in Interface Configuration mode to specify the
the number of Intermediate System-to-Intermediate System (IS-IS) hello packets a
neighbor can miss before the BSR determines the adjacency between the BSR
interface and the neighbor is down:
MOT:7A(config-if)#isis hello-multiplier <3-1000> [level-1 | level-2]
where:
3-1000 is the number of missing hello packets.
Setting the Advertised CSNP Interval
Complete Sequence Number PDUs (CSNPs) hold a complete list of all LSPs in the
IS-IS routing database. CSNPs are sent periodically on all links, and the receiving
systems use the information in the CSNP to update and synchronize their LSP
databases. The designated router multicasts CSNPs on broadcast links in place of
sending explicit acknowledgments for each LSP.
By default, IS-IS sends CSN packets periodically. If the BSR is the designated router
on a LAN, IS-IS sends CSN packets every 10 seconds. Depending on your network
topology you may want to modify the default interval to protect against LSP flooding.
Use the isis csnp-interval command in Interface Configuration mode to adjust the
IS-IS CSNP interval for intranet connections if the intranet is a part of a multiaccess
meshed network on the interface:
MOT:7A(config-if)#isis csnp-interval <1-65535> [level-1 | level-2]
where:
1-65535 is the ISIS CSNP interval in seconds.
level-1 indicates that the interface is a Level 1 IS-IS interface.
level-2 indicates that the interface is a Level 2 IS-IS interface.
Setting the LSP Interval
IS-IS Link-state PDUs (LSPs) hold information about the state of adjacencies to
neighboring IS-IS systems. LSPs are flooded periodically throughout an area.
Use the isis lsp-interval command, in Interface Configuration mode, to configure the
time delay between successive link state packet (LSP) transmissions:
MOT:7A(config-if)#isis lsp-interval <1-65535>
where:
1-65535 is the time delay in milliseconds between successive LSPs.
Setting the LSP Retransmission Interval
When LSPs are dropped, LSPs are retransmitted. Use the isis retransmit-interval
command, in Interface Configuration mode, to set the number of seconds between
retransmission of the same LSP.
MOT:7A(config-if)#isis retransmit-interval <1-65535>
where:
1-65535 is the number of seconds between LSP retransmissions.
Setting the LSP Retransmit Throttle Interval
To configure the amount of time between any LSP retransmissions, use the isis
retransmit-throttle-interval interface configuration command in Interface
Configuration mode as shown below:
MOT:7A(config-if)#isis retransmit-throttle-interval <1-65535>
where:
1-65535 is the minimum delay in milliseconds between LSP retransmissions on
the interface.
A BSR uses hello packets to advertise its priority to become a designated router. IS-IS
uses the advertised priorities on all multiaccess networks to elect a designated router
for the network. This router is responsible for sending network LSP advertisements,
which describe all the routers attached to the network. These advertisements are
flooded throughout a single area. The priority value is meaningful only on a
multiaccess network.
A routers priority for becoming the designated router is indicated by an arbitrary
number. Routers with a higher value are more likely to become the designated router.
By default, the BSR has a priority value of 32.
Note: The number of seconds should be greater than the expected round-trip
delay between any two routers on the attached network. Set this parameter
conservatively by increasing the interval to avoid unnecessary
retransmission. Increase the number of seconds for networks that have serial
lines and virtual links.
Use the isis priority command, in Interface Configuration mode, to select the
designated router priority:
MOT:7A(config-if)#isis priority <0-127> [level-1 | level-2]
where:
0-127 is a number that gives a priority value to the designated router.
Displaying IS-IS Information
show clns interface
The show clns interface command displays the CLNS interface status and
configuration.
MOT:7A# show clns interface [ ethernet <X/Y> | gigaether <X/Y> | loopback
<1-255> ]
where:
Note: Priorities can be configured for Level 1 and Level 2 individually.
show clns is-neighbors
The show clns is-neighbors command displays IS-IS information for IS-IS router
adjacencies.
MOT:7A# show clns is-neighbors [ethernet <X/Y> | gigaether <X/Y> | loopback
<1-255>]
where:
show clns neighbors
The show clns neighbors command displays IS-IS neighbor information.
MOT:7A# show clns neighbors [detail] [ethernet <X/Y> | gigaether <X/Y> |
loopback <1-255>]
where:
detail displays detailed neighbor information.
show clns protocols
The show clns protocols command displays protocol-specific information for each
IS-IS routing process in the BSR.
MOT:7A# show clns protocols
show clns traffic
The show clns traffic command lists the CLNS packets that the BSR has processed.
MOT:7A# show clns traffic
show ip redistribute
The show ip redistribute command displays which routing processes are being
redistributed to other routing domains.
MOT:7A# show ip redistribute [ bgp | isis | ospf | rip ]
where:
bgp displays routing domains redistributed into BGP.
isis displays routing domains redistributed into ISIS.
ospf displays routing domains redistributed into OSPF.
rip displays routing domains redistributed into RIP.
show ipv6 protocols
The show ipv6 protocols command is used for debugging routing activity and
processes by displaying the status of routing protocol processes currently on the
system.
MOT:7A# show ipv6 protocols [summary]
where:
summary displays a summary of system routing protocol processes.
show ipv6 route isis
The show ipv6 route isis command displays active IS-IS entries in the IPv6 routing
table.
MOT:7A# show ipv6 route isis
show isis database
The show isis database command is used to display all or specific IS-IS database
information.
MOT:7A# show isis database [detail <WORD> | l1 | l2 | level-1 | level-2] [<WORD>
| detail <WORD>]
where:
detail displays the contents of each LSP.
WORD is the LSPID in the form xxxx.xxxx.xxxx.xx-xx or name.xx-xx.
l1 is the abbreviation for the level-1 option.
level-1 displays the Level 1 IS-IS routing link state database.
show isis hostname
The show isis hostname command displays IS-IS hostname information.
MOT:7A# show isis hostname
show isis neighbors
The show isis neighbors command displays IS-IS neighbor information.
MOT:7A# show isis neighbors [ethernet <X/Y> | gigaether <X/Y> | loopback
<1-255>]
where:
show isis spf-log
The show isis spf-log command displays how often and why the router has run a full
SPF calculation for the Level 1 and Level 2 IS-IS routers.
MOT:7A# show isis spf-log
show isis topology
The show isis topology command displays the IS-IS paths to Intermediate Systems.
MOT:7A# show isis topology [ l1| l2 | level-1 | level-2 ]
where:
Compass ID: 389959760 Version 4 Index-1
A
ABR, 6-2, 6-9
access list
displaying, 2-9
name, 4-6
number, 4-6
address range
specifying, 6-11
addressing
multicast, 4-3
advertising
network, 6-11
route, 2-2, 6-12
APS, 10-21
show commands, 10-45
area border router, 6-2
AS, 7-2
and stub area, 6-9
boundary router in, 4-2
AS-path access lists
displaying, 2-9
authentication
IS-IS, 11-10
OSPF MD5, 6-21
RIP, 4-7
VRRP, 8-5
B
backbone
network, 1-1
OSPF, 6-13
BGP, 5-1, 7-1
external, 7-2
internal, 7-2
neighbors, 7-4
sessions, 7-5
updates, 7-4
Bootstrap Routers (BSRs), 3-9, 3-11
broadcast message, 4-3
C
cable plant, 1-1
Candidate Bootstrap Routers, 3-9
checksum
PIM, 3-13
CIDR, 7-3
community access lists
displaying, 2-9
configured route maps
displaying, 2-10
configuring
OSPF, 6-2, 6-7
RIP, 4-4
router
OSPF-based, 6-2
single route advertisement, 6-12
stub area, 6-9
VRRP, 8-1
D
default metric, 4-12, 5-5, 6-6
Index
Index-2 Compass ID: 389959760 Version 4
defining
route map, 2-4
route maps, 2-2, 2-4
Digital Set-top Gateway (DSG), 3-14
displaying
access lists, 2-9
AS-path access lists, 2-9
community access lists, 2-9
configured route maps, 2-10
IP traffic, 2-9
redistributed domains, 2-10
routing tables, 2-9
virtual link information, 6-16
Distance Vector Multicast Routing Protocol
(DVMRP), 3-16 to 3-22
information, 3-33
parent-child links, 3-18
summary address, 3-22
distance-vector routing, 3-16, 4-2
distribution hub, 1-1
E
EBGP, 7-2
EGP, 4-2
enabling
MPLS, 9-4
OSPF MD5 authentication, 6-21
F
fastpath, 3-3
forwarding
centralized, 1-1
H
hello packet, 6-21
hop count, 4-2
host route, 4-2
I
IBGP, 7-2
IGMP, 3-23 to 3-27
clearing statistics, 3-30
host-query messages, 3-24, 3-26
information, 3-34
querier timeout interval, 3-26
static group, 3-27
Version 3, 3-15, 3-24
versions, 3-25
incoming metrics, 4-6
interface
setting default, 2-6
setting forwarding, 2-6
type, 4-6
interface number, 4-6
interpacket delay
RIP update, 4-9
IP
address, 4-3
IP multicast routing, 3-1
group access, 3-24
information, 3-31
managing, 3-28
static routes, 3-28
IP traffic
displaying, 2-9
ip vrrp address, 8-3
IPv6 with IS-IS, 11-5
IS-IS, 11-1
authentication, 11-10
enabling, 11-2
IPv6, 11-5
redistributing routes, 11-6
K
keep-alive messages, 7-5
L
Label Edge Routers, 9-2
Label Switch Router, 9-2
learning
route, 2-2
Release 6.3.1 Index
LERs, 9-2
line, 10-43
link state database size, 6-12
LSA
age, 6-22
blocking flooding, 6-22
refreshing, 6-22
retransmission, 6-20
transmission interval, 6-22
Type 5
flooding, 6-10
translating from Type 7, 6-10
Type 7
importing, 6-10
translating into Type 5, 6-10
LSP
configuring route, 9-5
deleting route, 9-7
dynamic, 9-8
explicit route, 9-8
LSRs, 9-2
M
matching
next hop IP address, 2-5
monitoring
routing policy, 2-9
MPLS, 5-1, 9-1
enabling, 9-4
label range, 9-4
LSP route, 9-5
messages, 9-9
show commands, 9-11
TTL, 9-5
multicast, 3-1
addressing, 4-3
fastpath, 3-3
group, 3-2
hardware assisted, 3-3
information, 3-31
managing, 3-28
static routes, 3-28
Multicast Backbone (MBONE), 3-19
multiple-packet RIP update, 4-9
N
next hop
field, 4-3
IP address matching, 2-5
nonbackbone area, 6-13
Not So Stubby Area See NSSA
NSSA
ABR, 6-10
O
offset list, 4-6
OSPF, 6-1
area, 6-2, 6-7
configuring, 6-2, 6-19
cost metric, 6-17
distance value, 6-17
graceful restart, 6-3, 6-4
hello packet, 6-21
helper mode, 6-5
interface-specific parameter
changing, 6-19
link state database size, 6-12
LSA flood blocking, 6-22
managing, 6-13
NSSA, 6-10
packet cost, 6-20
passive interface, 6-23
password, 6-21
redistributing routes, 6-5, 6-12
route summarization, 6-11
stub area, 6-9
outgoing interfaces (OIs), 3-32
outgoing metrics, 4-6
P
PIM, 3-4 to 3-9
border, 3-11
checksum, 3-13
information, 3-33
sparse mode, 3-5
SSM, 3-14
unicast routes, 3-13
Policy-Based Routing
enabling
interface, 2-8
local, 2-8
POS, 10-1
APS, 10-21
CRC, 10-13
interface configuration, 10-3
loopback, 10-20
show commands, 10-37
signal rate, 10-19
PPP
POS configuration, 10-4
priority (VRRP), 8-6
R
redistributed domains
displaying, 2-10
redistributing routes
default metric, 4-12, 5-5
into IS-IS, 11-6
into OSPF, 6-5, 6-12
into RIP, 4-11, 5-4
specifying address, 6-12
specifying mask, 6-12
regional fiber network, 1-1
rendezvous point (RP), 3-5 to 3-12
configuration of, 3-7
Reverse Path Forwarding (RPF), 3-5, 3-28
information, 3-35
RIP
authentication, 4-7
configuring, 4-1, 5-2
distance vector routing, 4-2
enabling, 4-3
information, 4-13
over VRF, 5-1
passive interface, 4-10
redistributing routes, 4-11, 5-4
timers, 4-9
update
interpacket delay, 4-9
multiple-packet, 4-9
version, 4-4
route
advertising, 2-2
default external, 6-9
host, 4-2
learning, 2-2
next-hop attribute
setting, 2-6
next-hop default
setting, 2-7
redistributed, 6-12
summarization, 4-6, 5-3, 6-11
supernet, 4-2
tag, 4-2
route maps
content, 2-4
defining, 2-2, 2-4
router
internal, 6-2
routing
centralized, 1-1
distance-vector, 3-16, 4-2
update timers, 4-9
Routing Information Protocol See RIP
routing policy
monitoring, 2-9
routing tables
displaying, 2-9
RSVP, 9-2
disabling, 9-7
enabling, 9-7
messages, 9-9
show commands, 9-11
S
SDH, 10-2
set statements, 2-6
setting
default interface, 2-6
forwarding interface, 2-6
route
Release 6.3.1 Index
next-hop attribute, 2-6
next-hop default, 2-7
Shortest Path Tree (SPT), 3-12
show ip vrrp ethernet num, 8-11
SONET, 10-1
alarms, 10-16
b1-tca, 10-43
b2-tca, 10-43
b3-tca, 10-44
framing, 10-12
network clock, 10-6
payload scrambling, 10-12
specifying
address range, 6-11
packet cost, 6-20
split horizon, 4-5
static routes
multicast, 3-28
stub area
configuring, 6-9
default summary route cost
assigning, 6-9
subnet mask, 4-2
advertisement, 4-2
rules, 4-2
summary route
advertisement, 6-11
supernet route, 4-2
T
timers
OSPF, 6-18
RIP, 4-9
VRRP, 8-7
time-to-live (TTL), 3-26, 9-5
U
UDP, 4-2
unicast routes
PIM, 3-13
V
virtual endpoint, 6-13
virtual links, 6-16, 6-17
virtual router, 8-3
information, 8-9
VRF
and RIP, 5-1
VRRP
authentication, 8-5
configuring, 8-1
enabling, 8-3
priority, 8-6
timers, 8-7
12/11
Visit our website at:
www.motorola.com

BSR64K-R6 3 1-RoutingGuide

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

BSR64K-R6 3 1-RoutingGuide

Загружено:

Авторское право:

Доступные форматы

BSR 64000 Routing

Вам также может понравиться