7210 SAS M, X OS Routing Protocols Guide

7210 SAS M, X OS
Routing Protocols Guide
Software Version: 7210 SAS M OS 5.0 Rev. 01
October 2012
Document Part Number: 93-0422-01-01
93-0422-01-01
This document is protected by copyright. Except as specifically permitted herein, no portion of the provided information can be
reproduced in any form, or by any means, without prior written permission from Alcatel-Lucent.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of
their respective owners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2011 Alcatel-Lucent. All rights reserved.
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Getting Started
Alcatel-Lucent 7210 SAS M-Series Router Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
OSPF
Configuring OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Backbone Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Stub Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Not-So-Stubby Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
OSPFv3 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Virtual Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Neighbors and Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Link-State Advertisements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
IP Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Preconfiguration Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
OSPF Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
OSPF Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Configuring OSPF with CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
OSPF Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Basic OSPF Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Configuring the Router ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Configuring OSPF Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Configuring OSPF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Configuring an OSPF Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Configuring a Stub Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Configuring a Not-So-Stubby Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Configuring a Virtual Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Configuring an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Configuring Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Assigning a Designated Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Configuring Route Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Configuring Route Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
OSPF Configuration Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Modifying a Router ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Deleting a Router ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Modifying OSPF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
OSPF Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Generic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
7210 SAS M, X OS Routing Protocols Guide
Page 3
Table of Contents
OSPF Global Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
OSPF Area Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Interface/Virtual Link Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Clear Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
OSPF Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
IS-IS
Configuring IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
IS-IS Frequently Used Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
ISO Network Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
IS-IS PDU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
IS-IS Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
IS-IS Route Summarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
IS-IS Administrative Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Setting Route Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Using Route Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
IS-IS Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Configuring IS-IS with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
IS-IS Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Router Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Area Address Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Interface Level Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Route Leaking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Basic IS-IS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
Configuring IS-IS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Enabling IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Modifying Router-Level Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Configuring ISO Area Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Configuring Global IS-IS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Configuring Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
IS-IS Configuration Management Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
Disabling IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
Removing IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
Modifying Global IS-IS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
Modifying IS-IS Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Configuring Leaking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Redistributing External IS-IS Routers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Specifying MAC Addresses for All IS-IS Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
IS-IS Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
IS-IS Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Generic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
Clear Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
Debug Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238
Page 4
7210 SAS M, X OS Routing Protocols Guide
Table of Contents
BGP
BGP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
BGP Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
Message Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
Group Configuration and Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244
Hierarchical Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245
Route Reflection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245
Fast External Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249
Sending of BGP Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249
Route Selection Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250
IP-VPNs MSE Direct Route Comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
Enabling Best External . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
BGP Decision Process with Best External . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
Advertisement Rules with Best External . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
Displaying Best-External Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
Command Interactions and Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
Changing the Autonomous System Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254
Changing the Local AS Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255
Changing the Router ID at the Configuration Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
Hold Time and Keep Alive Timer Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
Import and Export Route Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
Route Damping and Route Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
AS Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
TTL Security for BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
BGP Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
BGP Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
BGP MIB Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
Configuring BGP with CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263
BGP Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
Preconfiguration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
BGP Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
Internal and External BGP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
Basic BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266
Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268
Creating an Autonomous System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269
Configuring a Router ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
BGP Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271
Configuring BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271
Configuring Group Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
Configuring Neighbor Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274
BGP Configuration Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Modifying an AS Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Modifying the BGP Router ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276
Modifying the Router-Level Router ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
Deleting a Neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Deleting Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279
Editing BGP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
7210 SAS M, X OS Routing Protocols Guide
Page 5
Table of Contents
BGP Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281
Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289
Other BGP-Related Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312
Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313
Clear Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350
Debug Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352
Route Policies
Configuring Route Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358
Policy Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359
Default Action Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360
Denied IP Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360
Controlling Route Flapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361
Regular Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363
BGP and OSPF Route Policy Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368
BGP Route Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368
Re-advertised Route Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370
When to Use Route Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371
Route Policy Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373
Configuring Route Policies with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375
Route Policy Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376
When to Create Routing Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376
Default Route Policy Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377
Policy Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378
Damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381
Basic Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .382
Configuring Route Policy Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .383
Beginning the Policy Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384
Creating a Route Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385
Configuring a Default Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .386
Configuring an Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .387
Configuring Damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388
Configuring a Prefix List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389
Route Policy Configuration Management Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390
Editing Policy Statements and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390
Deleting an Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392
Deleting a Policy Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392
Use of Route Policies for IGMP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393
Route Policy Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395
Route Policy Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .399
Generic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .399
Route Policy Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401
Route Policy Damping Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404
Route Policy Prefix Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407
Route Policy Entry Match Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .409
Route Policy Action Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .417
Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425
Page 6
7210 SAS M, X OS Routing Protocols Guide
Table of Contents
Standards and Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .433
7210 SAS M, X OS Routing Protocols Guide
Page 7
Table of Contents
Page 8
7210 SAS M, X OS Routing Protocols Guide
List of Tables
Getting Started
Table 1:
Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
OSPF
Table 2:
Table 3:
Table 4:
Route Preference Defaults by Route Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Route Preference Defaults by Route Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Route Preference Defaults by Route Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
IS-IS
Table 5:
Table 6:
Potential Adjacency Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Potential Adjacency Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
BGP
Table 7:
Table 8:
7210 SAS and IETF MIB Variations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
MIB Variable with SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
Route Policies
Table 9:
Table 10:
Table 11:
Regular Expression Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364
AS Path and Community Regular Expression Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365
Default Route Policy Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377
7210 SAS M, X OS Routing Protocols Guide
Page 9
Page 10
7210 SAS M, X OS Routing Protocols Guide
LIST
OF
FIGURES
OSPF
Figure 1:
Figure 2:
Backbone Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
OSPF Configuration and Implementation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
IS-IS
Figure 3:
Figure 4:
Figure 5:
Figure 6:
Figure 7:
IS-IS Routing Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Using Area Addresses to Form Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
IS-IS Configuration and Implementation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Configuring a Level 1 Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Configuring a Level 1/2 Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
BGP
Figure 8:
Figure 9:
Figure 10:
Figure 11:
BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244
Fully Meshed BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246
BGP Configuration with Route Reflectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
BGP Configuration and Implementation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
Route Policies
Figure 12:
Figure 13:
Figure 14:
Figure 15:
Figure 16:
Figure 17:
Figure 18:
BGP Route Policy Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368
BGP Route Policy Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369
OSPF Route Policy Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369
Route Policy Configuration and Implementation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
Route Policy Process Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379
Next Policy Logic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380
Damping Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381
7210 SAS M, X OS Routing Protocols Guide
Page 11
Page 12
7210 SAS M, X OS Routing Protocols Guide
Preface
About This Guide
This guide describes routing protocols including multicast, OSPF, IS-IS, and route policies
provided by the 7210 SAS M OS and presents configuration and implementation examples.
All the variants of 7210 SAS-M can be configured in two modes, that is in network mode and in
access-uplink mode. In network mode configuration 7210 SAS-M uses IP/MPLS to provide
service transport. In access-uplink mode configuration 7210 SAS-M uses Ethernet QinQ
technology to provide service transport. The mode can be selected by configuring the BOF
appropriately.
NOTE: In either mode, it is expected that the user will only configure the required CLI parameters
appropriate for the mode he intends to use. Unless otherwise noted, most of the configuration is
similar in both the Network mode and access uplink mode.
Note :Only 7210 SAS-M supports access-uplink mode. 7210 SAS-X does not support accessuplink mode.
This document is organized into functional chapters and provides concepts and descriptions of the
implementation flow, as well as Command Line Interface (CLI) syntax and command usage.
Audience
This manual is intended for network administrators who are responsible for configuring the 7210
SAS M-Series routers. It is assumed that the network administrators have an understanding of
networking principles and configurations. Protocols, standards, and services described in this
manual include the following:
•
Open Shortest Path First (OSPF)
•
Intermediate System to Intermediate System (IS-IS)
•
Route policies
Page 13
Preface
List of Technical Publications
The 7210-SAS M, X OS documentation set is composed of the following books:
•
7210-SAS M, X OS Basic System Configuration Guide
This guide describes basic system configurations and operations.
•
7210-SAS M, X OS System Management Guide
This guide describes system security and access configurations as well as event
logging and accounting logs.
•
7210-SAS M, X OS Interface Configuration Guide
This guide describes card, Media Dependent Adapter (MDA), and port provisioning.
•
7210-SAS M, X OS Router Configuration Guide
This guide describes logical IP routing interfaces and associated attributes such as an
IP address, port, link aggregation group (LAG) as well as IP and MAC-based filtering.
•
7210-SAS M, X OS Routing Protocols Guide
This guide provides an overview configuration examples for route policies.
•
7210-SAS M, X OS MPLS Guide
This guide describes how to configure Multiprotocol Label Switching (MPLS) and
Label Distribution Protocol (LDP).
•
7210 SAS M OS Services Guide
This guide describes how to configure service parameters such as customer
information and user services.
•
7210-SAS M, X OS OAM and Diagnostic Guide
This guide describes how to configure features such as service mirroring and
Operations, Administration and Management (OAM) tools.
•
7210 SAS M OS Quality of Service Guide
This guide describes how to configure Quality of Service (QoS) policy management.
Page 14
7210 SAS M, X OS Routing Protocols Guide
Preface
Technical Support
If you purchased a service agreement for your 7210 SAS router and related products from a
distributor or authorized reseller, contact the technical support staff for that distributor or reseller
for assistance. If you purchased an Alcatel-Lucent service agreement, contact your welcome center
at:
Web:
http://www1.alcatel-lucent.com/comps/pages/carrier_support.jhtml
7210 SAS M, X OS Routing Protocols Guide
Page 15
Preface
Page 16
7210 SAS M, X OS Routing Protocols Guide
Getting Started
In This Chapter
This chapter provides process flow information to configure IP routing protocols.
Alcatel-Lucent 7210 SAS M-Series Router Configuration Process
Table 1 lists the tasks necessary to configure RIP, OSPF, and IS-IS, BGP, and multicast protocols,
and route policies. This guide is presented in an overall logical configuration flow. Each section
describes a software area and provides CLI syntax and command usage to configure parameters
for a functional area.
Table 1: Configuration Process
Area
Protocol configuration
Task
Chapter
Configure routing protocols:
• Multicast
Multicast on page 21
• RIP
RIP on page 231
• OSPF
OSPF on page 19
• IS-IS
IS-IS on page 151
• BGP
BGP on page 241
Policy configuration
• Configure route policies
Route Policies on page 357
Reference
List of IEEE, IETF, and other
proprietary entities.
Standards and Protocol Support on page 429
7210 SAS M, X OS Routing Protocols Guide
Page 17
Getting Started
Page 18
7210 SAS M, X OS Routing Protocols Guide
OSPF
In This Chapter
This chapter provides information about configuring the Open Shortest Path First (OSPF)
protocol.
NOTE: OSPF and OSPFv3 is not supported in 7210 SAS-M access-uplink mode.
Topics in this chapter include:
•
Configuring OSPF on page 20
→ OSPF Areas on page 21
−
Backbone Area on page 21
−
Stub Area on page 22
−
Not-So-Stubby Area on page 23
→ OSPFv3 Authentication on page 23
→ Virtual Links on page 24
→ Neighbors and Adjacencies on page 25
→ Link-State Advertisements on page 26
→ Metrics on page 26
→ Authentication on page 26
→ IP Subnets on page 28
→ Preconfiguration Recommendations on page 28
•
OSPF Configuration Process Overview on page 29
•
Configuration Notes on page 30
7210 SAS M, X OS Routing Protocols Guide
Page 19
Configuring OSPF
Configuring OSPF
OSPF (Open Shortest Path First) is a hierarchical link state protocol. OSPF is an interior gateway
protocol (IGP) used within large autonomous systems (ASs). OSPF routers exchange state, cost,
and other relevant interface information with neighbors. The information exchange enables all
participating routers to establish a network topology map. Each router applies the Dijkstra
algorithm to calculate the shortest path to each destination in the network. The resulting OSPF
forwarding table is submitted to the routing table manager to calculate the routing table.
When a router is started with OSPF configured, OSPF, along with the routing-protocol data
structures, is initialized and waits for indications from lower-layer protocols that its interfaces are
functional. Alcatel-Lucent’s implementation of OSPF conforms to OSPF Version 2 specifications
presented in RFC 2328, OSPF Version 2 and OSPF Version 3 specifications presented in RFC
2740, OSPF for IPv6. Routers running OSPF can be enabled with minimal configuration. All
default and command parameters can be modified.
Changes between OSPF for IPv4 and OSPF3 for IPv6 include the following:
•
Addressing semantics have been removed from OSPF packets and the basic link-state
advertisements (LSAs). New LSAs have been created to carry IPv6 addresses and
prefixes.
•
OSPF3 runs on a per-link basis, instead of on a per-IP-subnet basis.
•
Flooding scope for LSAs has been generalized.
•
Unlike OSPFv2, OSPFv3 authentication relies on IPV6's authentication header and
encapsulating security payload.
•
Most packets in OSPF for IPv6 are almost as compact as those in OSPF for IPv4, even
with the larger IPv6 addresses.
•
Most field and packet-size limitations present in OSPF for IPv4 have been relaxed.
•
Option handling has been made more flexible.
Key OSPF features are:
Page 20
•
Backbone areas
•
Stub areas
•
Not-So-Stubby areas (NSSAs)
•
Virtual links
•
Authentication
•
Route redistribution
•
Routing interface parameters
•
OSPF-TE extensions (Alcatel-Lucent’s implementation allows MPLS fast reroute)
7210 SAS M, X OS Routing Protocols Guide
OSPF
OSPF Areas
The hierarchical design of OSPF allows a collection of networks to be grouped into a logical area.
An area’s topology is concealed from the rest of the AS which significantly reduces OSPF protocol
traffic. With the proper network design and area route aggregation, the size of the route-table can
be drastically reduced which results in decreased OSPF route calculation time and topological
database size.
Routing in the AS takes place on two levels, depending on whether the source and destination of a
packet reside in the same area (intra-area routing) or different areas (inter-area routing). In intraarea routing, the packet is routed solely on information obtained within the area; no routing
information obtained from outside the area is used.
Routers that belong to more than one area are called area border routers (ABRs). An ABR
maintains a separate topological database for each area it is connected to. Every router that belongs
to the same area has an identical topological database for that area.
Backbone Area
The OSPF backbone area, area 0.0.0.0, must be contiguous and all other areas must be connected
to the backbone area. The backbone distributes routing information between areas. If it is not
practical to connect an area to the backbone (see area 0.0.0.5 in Figure 1) then the ABRs (such as
routers Y and Z) must be connected via a virtual link. The two ABRs form a point-to-point-like
adjacency across the transit area (see area 0.0.0.4).
7210 SAS M, X OS Routing Protocols Guide
Page 21
Configuring OSPF
Area 0.0.0.0
Area 0.0.0.1
Area 0.0.0.2
Y
Area 0.0.0.3
Area 0.0.0.4
OSPF Domain
Z
Area 0.0.0.5
RIP Domain
OSRG035
Figure 1: Backbone Area
Stub Area
A stub area is a designated area that does not allow external route advertisements. Routers in a stub
area do not maintain external routes. A single default route to an ABR replaces all external routes.
This OSPF implementation supports the optional summary route (type-3) advertisement
suppression from other areas into a stub area. This feature further reduces topological database
sizes and OSPF protocol traffic, memory usage, and CPU route calculation time.
In Figure 1, areas 0.0.0.1, 0.0.0.2 and 0.0.0.5 could be configured as stub areas. A stub area cannot
be designated as the transit area of a virtual link and a stub area cannot contain an AS boundary
router. An AS boundary router exchanges routing information with routers in other ASs.
Page 22
7210 SAS M, X OS Routing Protocols Guide
OSPF
Not-So-Stubby Area
Another OSPF area type is called a Not-So-Stubby area (NSSA). NSSAs are similar to stub areas
in that no external routes are imported into the area from other OSPF areas. External routes learned
by OSPF routers in the NSSA area are advertised as type-7 LSAs within the NSSA area and are
translated by ABRs into type-5 external route advertisements for distribution into other areas of
the OSPF domain. An NSSA area cannot be designated as the transit area of a virtual link.
In Figure 1, area 0.0.0.3 could be configured as a NSSA area.
OSPFv3 Authentication
OSPFv3 authentication requires IPv6 IPsec and supports the following:
•
IPsec transport mode
•
AH and ESP
•
Manual keyed IPsec Security Association (SA)
•
Authentication Algorithms MD5 and SHA1
To pass OSPFv3 authentication, OSPFv3 peers must have matching inbound and outbound SAs
configured using the same SA parameters such as SPI, keys and related parameters. The
implementation must allow the use of one SA for both inbound and outbound directions.
This feature is supported on IES and VPRN interfaces as well as on virtual links.
The re-keying procedure defined in RFC 4552 supports the following:
•
For every router on the link, create an additional inbound SA for the interface being rekeyed using a new SPI and the new key.
•
For every router on the link, replace the original outbound SA with one using the new SPI
and key values. The SA replacement operation must be atomic with respect to sending
OSPFv3 packet on the link, so that no OSPFv3 packets are sent without authentication or
encryption.
•
For every router on the link, remove the original inbound SA.
The key rollover procedure automatically starts when the operator changes the configuration of the
inbound static-SA or bi-directional static-SA under an interface or virtual link. Within the
KeyRolloverInterval time period, OSPF3 accepts packets with both the previous inbound staticSA and the new inbound static-SA, and the previous outbound static-SA should continue to be
used. When the timer expires, OSPF3 only accepts packets with the new inbound static-SA and for
outgoing OSPF3 packets, the new outbound static-SA is used instead.
7210 SAS M, X OS Routing Protocols Guide
Page 23
Configuring OSPF
Virtual Links
The backbone area in an OSPF AS must be contiguous and all other areas must be connected to the
backbone area. Sometimes, this is not possible. You can use virtual links to connect to the
backbone through a non-backbone area.
Figure 1 depicts routers Y and Z as the start and end points of the virtual link while area 0.0.0.4 is
the transit area. In order to configure virtual links, the router must be an ABR. Virtual links are
identified by the router ID of the other endpoint, another ABR. These two endpoint routers must be
attached to a common area, called the transit area. The area through which you configure the
virtual link must have full routing information.
Transit areas pass traffic from an area adjacent to the backbone or to another area. The traffic does
not originate in, nor is it destined for, the transit area. The transit area cannot be a stub area or a
NSSA area.
Virtual links are part of the backbone, and behave as if they were unnumbered point-to-point
networks between the two routers. A virtual link uses the intra-area routing of its transit area to
forward packets. Virtual links are brought up and down through the building of the shortest-path
trees for the transit area.
Page 24
7210 SAS M, X OS Routing Protocols Guide
OSPF
Neighbors and Adjacencies
A router uses the OSPF Hello protocol to discover neighbors. A neighbor is a router configured
with an interface to a common network. The router sends hello packets to a multicast address and
receives hello packets in return.
In broadcast networks, a designated router and a backup designated router are elected. The
designated router is responsible for sending link-state advertisements (LSAs) describing the
network, which reduces the amount of network traffic.
The routers attempt to form adjacencies. An adjacency is a relationship formed between a router
and the designated or backup designated router. For point-to-point networks, no designated or
backup designated router is elected. An adjacency must be formed with the neighbor.
To significantly improve adjacency forming and network convergence, a network should be
configured as point-to-point if only two routers are connected, even if the network is a broadcast
media such as Ethernet.
When the link-state databases of two neighbors are synchronized, the routers are considered to be
fully adjacent. When adjacencies are established, pairs of adjacent routers synchronize their
topological databases. Not every neighboring router forms an adjacency. Routing protocol updates
are only sent to and received from adjacencies. Routers that do not become fully adjacent remain
in the two-way neighbor state.
7210 SAS M, X OS Routing Protocols Guide
Page 25
Configuring OSPF
Link-State Advertisements
Link-state advertisements (LSAs) describe the state of a router or network, including router
interfaces and adjacency states. Each LSA is flooded throughout an area. The collection of LSAs
from all routers and networks form the protocol's topological database.
The distribution of topology database updates take place along adjacencies. A router sends LSAs
to advertise its state according to the configured interval and when the router's state changes. These
packets include information about the router's adjacencies, which allows detection of nonoperational routers.
When a router discovers a routing table change or detects a change in the network, link state
information is advertised to other routers to maintain identical routing tables. Router adjacencies
are reflected in the contents of its link state advertisements. The relationship between adjacencies
and the link states allow the protocol to detect non-operating routers. Link state advertisements
flood the area. The flooding mechanism ensures that all routers in an area have the same
topological database. The database consists of the collection of LSAs received from each router
belonging to the area.
OSPF sends only the part that has changed and only when a change has taken place. From the
topological database, each router constructs a tree of shortest paths with itself as root. OSPF
distributes routing information between routers belonging to a single AS.
Metrics
In OSPF, all interfaces have a cost value or routing metric used in the OSPF link-state calculation.
OSPF uses cost values to determine the best path to a particular destination: the lower the cost
value, the more likely the interface will be used to forward data traffic.
Authentication
All OSPF protocol exchanges can be authenticated. This means that only trusted routers can
participate in autonomous system routing. Alcatel-Lucent’s implementation of OSPF supports
plain text and Message Digest 5 (MD5) authentication (also called simple password).
MD5 allows an authentication key to be configured per network. Routers in the same routing
domain must be configured with the same key. When the MD5 hashing algorithm is used for
authentication, MD5 is used to verify data integrity by creating a 128-bit message digest from the
data input. It is unique to that data. Alcatel-Lucent’s implementation of MD5 allows the migration
of an MD5 key by using a key ID for each unique key.
Page 26
7210 SAS M, X OS Routing Protocols Guide
OSPF
By default, authentication is not enabled on an interface.
7210 SAS M, X OS Routing Protocols Guide
Page 27
Configuring OSPF
IP Subnets
OSPF enables the flexible configuration of IP subnets. Each distributed OSPF route has a
destination and mask. A network mask is a 32-bit number that indicates the range of IP addresses
residing on a single IP network/subnet. This specification displays network masks as hexadecimal
numbers; for example, the network mask for a class C IP network is displayed as 0xffffff00. Such
a mask is often displayed as 255.255.255.0.
Two different subnets with same IP network number have different masks, called variable length
subnets. A packet is routed to the longest or most specific match. Host routes are considered to be
subnets whose masks are all ones (0xffffffff).
Preconfiguration Recommendations
Prior to configuring OSPF, the router ID must be available. The router ID is a 32-bit number
assigned to each router running OSPF. This number uniquely identifies the router within an AS.
OSPF routers use the router IDs of the neighbor routers to establish adjacencies. Neighbor IDs are
learned when Hello packets are received from the neighbor.
Before configuring OSPF parameters, ensure that the router ID is derived by one of the following
methods:
•
Define the value in the config>router router-id context.
•
Define the system interface in the config>router>interface ip-int-name context (used if
the router ID is not specified in the config>router router-id context).
A system interface must have an IP address with a 32-bit subnet mask. The system
interface is used as the router identifier by higher-level protocols such as OSPF and IS-IS.
The system interface is assigned during the primary router configuration process when the
interface is created in the logical IP interface context.
•
Page 28
If you do not specify a router ID, then the last four bytes of the MAC address are used.
7210 SAS M, X OS Routing Protocols Guide
OSPF
OSPF Configuration Process Overview
Figure 2 displays the process to provision basic OSPF parameters.
START
CONFIGURE THE ROUTER ID
DEFINE ONE OR MORE AREAS
DEFINE INTERFACES
DEFINE STUB AREA
OPTIONAL
DEFINE NSSA
CONFIGURE VIRTUAL LINKS
TURN UP
Figure 2: OSPF Configuration and Implementation Flow
7210 SAS M, X OS Routing Protocols Guide
Page 29
Configuration Notes
Configuration Notes
This section describes OSPF configuration caveats.
General
•
Before OSPF can be configured, the router ID must be configured.
•
The basic OSPF configuration includes at least one area and an associated interface.
•
All default and command parameters can be modified.
OSPF Defaults
The following list summarizes the OSPF configuration defaults:
Page 30
•
By default, a router has no configured areas.
•
An OSPF instance is created in the administratively enabled state.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Configuring OSPF with CLI
This section provides information to configure Open Shortest Path First (OSPF) using the
command line interface.
Topics in this section include:
•
OSPF Configuration Guidelines on page 32
•
Basic OSPF Configuration on page 33
•
Configuring the Router ID on page 33
•
Configuring OSPF Components on page 35
→ Configuring the Router ID on page 33
→ Configuring an OSPF Area on page 36
→ Configuring a Stub Area on page 37
→ Configuring a Not-So-Stubby Area on page 38
→ Configuring a Virtual Link on page 39
→ Configuring an Interface on page 40
→ Configuring Authentication on page 41
→ Assigning a Designated Router on page 45
→ Configuring Route Summaries on page 47
→ Configuring Route Preferences on page 48
•
OSPF Configuration Management Tasks on page 51
→ Modifying a Router ID on page 51
→ Deleting a Router ID on page 51
→ Modifying OSPF Parameters on page 53
7210 SAS M, X OS Routing Protocols Guide
Page 31
OSPF Configuration Guidelines
OSPF Configuration Guidelines
Configuration planning is essential to organize routers, backbone, non-backbone, stub, NSSA
areas, and transit links. OSPF provides essential defaults for basic protocol operability. You can
configure or modify commands and parameters. OSPF is not enabled by default.
The minimal OSPF parameters which should be configured to deploy OSPF are:
•
Router ID
Each router running OSPF must be configured with a unique router ID. The router ID is
used by OSPF routing protocols in the routing table manager.
When configuring a new router ID, protocols will not automatically be restarted with the
new router ID. Shut down and restart the protocol to initialize the new router ID.
•
An area
At least one OSPF area must be created. An interface must be assigned to each OSPF area.
•
Interfaces
An interface is the connection between a router and one of its attached networks. An
interface has state information associated with it, which is obtained from the underlying
lower level protocols and the routing protocol itself. An interface to a network has
associated with it a single IP address and mask (unless the network is an unnumbered
point-to-point network). An interface is sometimes also referred to as a link.
Page 32
7210 SAS M, X OS Routing Protocols Guide
OSPF
Basic OSPF Configuration
This section provides information to configure OSPF as well as configuration examples of
common configuration tasks.
The minimal OSPF parameters that need to be configured are:
•
A router ID - If a router-id is not configured in the config>router context, the router’s
system interface IP address is used.
•
One or more areas.
•
Interfaces (interface "system").
Following is an example of a basic OSPF configuration:
ALA-A>config>router>ospf# info
---------------------------------------------area 0.0.0.0
interface "system"
exit
exit
area 0.0.0.20
nssa
exit
interface "to-104"
priority 10
exit
exit
area 0.0.1.1
exit
---------------------------------------------ALA-A>config>router>ospf#
Configuring the Router ID
The router ID uniquely identifies the router within an AS. In OSPF, routing information is
exchanged between autonomous systems, groups of networks that share routing information. It can
be set to be the same as the loopback (system interface) address. Subscriber services also use this
address as far-end router identifiers when service distribution paths (SDPs) are created. The router
ID is used by both OSPF and BGP routing protocols. A router ID can be derived by:
•
Defining the value in the config>router router-id context.
•
Defining the system interface in the config>router>interface ip-int-name
context (used if the router ID is not specified in the config>router router-id
context).
•
Inheriting the last four bytes of the MAC address.
•
On the BGP protocol level. A BGP router ID can be defined in the config>router>bgp
router-id context and is only used within BGP.
7210 SAS M, X OS Routing Protocols Guide
Page 33
Basic OSPF Configuration
When configuring a new router ID, protocols are not automatically restarted with the new router
ID. The next time a protocol is (re) initialized the new router ID is used. An interim period of time
can occur when different protocols use different router IDs. To force the new router ID, issue the
shutdown and no shutdown commands for each protocol that uses the router ID or restart the
entire router.
The following displays a router ID configuration example:
A:ALA-B>config>router# info
#-----------------------------------------# IP Configuration
#-----------------------------------------interface "system"
address 10.10.10.104/32
exit
interface "to-103"
address 10.0.0.104/24
port 1/1/1
exit
router-id 10.10.10.104
...
#-----------------------------------------A:ALA-B>config>router#
Page 34
7210 SAS M, X OS Routing Protocols Guide
OSPF
Configuring OSPF Components
Use the CLI syntax displayed below for:
•
Configuring OSPF Parameters on page 35
•
Configuring a Stub Area on page 37
•
Configuring a Not-So-Stubby Area on page 38
•
Configuring a Virtual Link on page 39
•
Configuring an Interface on page 40
•
Configuring Authentication on page 41
•
Assigning a Designated Router on page 45
•
Configuring Route Summaries on page 47
Configuring OSPF Parameters
The following displays a basic OSPF configuration example:
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
export "OSPF-Export"
graceful-restart
helper-disable
exit
---------------------------------------------A:ALA-49>config>router>ospf# ex
7210 SAS M, X OS Routing Protocols Guide
Page 35
Configuring OSPF Components
Configuring an OSPF Area
An OSPF area consists of routers configured with the same area ID. To include a router in a
specific area, the common area ID must be assigned and an interface identified.
If your network consists of multiple areas you must also configure a backbone area (0.0.0.0) on at
least one router. The backbone is comprised of the area border routers and other routers not
included in other areas. The backbone distributes routing information between areas. The
backbone is considered to be a participating area within the autonomous system. To maintain
backbone connectivity, there must be at least one interface in the backbone area or have a virtual
link configured to another router in the backbone area.
The minimal configuration must include an area ID and an interface. Modifying other command
parameters are optional.
Use the following CLI syntax to configure an OSPF area:
CLI Syntax: ospf ospf-instance
area area-id
area-range ip-prefix/mask [advertise|not-advertise]
blackhole-aggregate
The following displays an OSPF area configuration example:
A:ALA-A>config>router>ospf# info
---------------------------------------------area 0.0.0.0
exit
area 0.0.0.20
exit
---------------------------------------------ALA-A>config>router>ospf#A:
Page 36
7210 SAS M, X OS Routing Protocols Guide
OSPF
Configuring a Stub Area
Configure stub areas to control external advertisements flooding and to minimize the size of the
topological databases on an area's routers. A stub area cannot also be configured as an NSSA.
By default, summary route advertisements are sent into stub areas. The no form of the summary
command disables sending summary route advertisements and only the default route is advertised
by the ABR. This example retains the default so the command is not entered.
If this area is configured as a transit area for a virtual link, then existing virtual links of a non-stub
or NSSA area are removed when its designation is changed to NSSA or stub.
Use the following CLI syntax to configure virtual links:
CLI Syntax: ospf
area area-id
stub
default-metric metric
summaries
The following displays a stub configuration example:
ALA-A>config>router>ospf>area># info
---------------------------------------------...
area 0.0.0.0
exit
area 0.0.0.20
stub
exit
exit
...
---------------------------------------------ALA-A>config>router>ospf#
The following displays a stub configuration example:
ALA-A>config>router>ospf>area># info
---------------------------------------------...
area 0.0.0.0
exit
area 0.0.0.20
stub
exit
exit
...
---------------------------------------------ALA-A>config>router>ospf#
7210 SAS M, X OS Routing Protocols Guide
Page 37
Configuring OSPF Components
Configuring a Not-So-Stubby Area
You must explicitly configure an area to be a Not-So-Stubby Area (NSSA) area. NSSAs are
similar to stub areas in that no external routes are imported into the area from other OSPF areas.
The major difference between a stub area and an NSSA is an NSSA has the capability to flood
external routes it learns throughout its area and by an area border router to the entire OSPF domain.
An area cannot be both a stub area and an NSSA.
If this area is configured as a transit area for a virtual link, then existing virtual links of a non-stub
or NSSA area are removed when its designation is changed to NSSA or stub.
Use the following CLI syntax to configure stub areas:
CLI Syntax: ospf ospf-instance
area area-id
nssa
area-range ip-prefix/mask [advertise|not-advertise]
originate-default-route [type-7]
redistribute-external
summaries
The following displays an NSSA configuration example:
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
exit
area 0.0.0.20
stub
exit
exit
area 0.0.0.25
nssa
exit
exit
---------------------------------------------A:ALA-49>config>router>ospf#
Page 38
7210 SAS M, X OS Routing Protocols Guide
OSPF
Configuring a Virtual Link
The backbone area (area 0.0.0.0) must be contiguous and all other areas must be connected to the
backbone area. If it is not practical to connect an area to the backbone then the area border routers
must be connected via a virtual link. The two area border routers will form a point-to-point-like
adjacency across the transit area. A virtual link can only be configured while in the area 0.0.0.0
context.
The router-id parameter specified in the virtual-link command must be associated with
the virtual neighbor, that is, enter the virtual neighbor’s router ID, not the local router ID. The
transit area cannot be a stub area or an NSSA.
Use the following CLI syntax to configure stub areas:
CLI Syntax: ospf ospf-instance
area area-id
virtual-link router-id transit-area area-id
authentication-key [authentication-key|hash-key]
[hash]
authentication-type [password|message-digest]
dead-interval seconds
hello-interval seconds
message-digest-key key-id md5 [key|hash-key]
[hash|hash2]
retransmit-interval seconds
transit-delay
no shutdown
The following displays a virtual link configuration example:
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
virtual-link 1.2.3.4 transit-area 1.2.3.4
hello-interval 9
dead-interval 40
exit
exit
area 0.0.0.20
stub
exit
exit
area 0.0.0.25
7210 SAS M, X OS Routing Protocols Guide
Page 39
Configuring OSPF Components
nssa
exit
exit
area 1.2.3.4
exit
---------------------------------------------A:ALA-49>config>router>ospf#
Configuring an Interface
In OSPF, an interface can be configured to act as a connection between a router and one of its
attached networks. An interface includes state information that was obtained from underlying
lower level protocols and from the routing protocol itself. An interface to a network is associated
with a single IP address and mask. If the address is merely changed, then the OSPF configuration
is preserved.
The passive command enables the passive property to and from the OSPF interface where
passive interfaces are advertised as OSPF interfaces but do not run the OSPF protocol. By default,
only interface addresses that are configured for OSPF are advertised as OSPF interfaces. The
passive parameter allows an interface to be advertised as an OSPF interface without running the
OSPF protocol. When enabled, the interface will ignore ingress OSPF protocol packets and not
transmit any OSPF protocol packets.
An interface can be part of more than one area, as specified in RFC5185. To do this, add the
keyword secondary when creating the interface.
Use the following CLI syntax to configure an OSPF interface:
CLI Syntax: ospf ospf-instance
area area-id
interface ip-int-name
advertise-subnet
authentication-key [authentication-key|hash-key]
[hash|hash2]
authentication-type [password|message-digest]
dead-interval seconds
hello-interval seconds
interface-type {broadcast|point-to-point}
message-digest-key key-id md5 [key|hashkey][hash|hash2]
metric metric
mtu bytes
passive
priority number
retransmit-interval seconds
no shutdown
Page 40
7210 SAS M, X OS Routing Protocols Guide
OSPF
transit-delay seconds
The following displays an interface configuration example:
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
virtual-link 1.2.3.4 transit-area 1.2.3.4
hello-interval 9
dead-interval 40
exit
interface "system"
exit
exit
area 0.0.0.20
stub
exit
interface "to-103"
exit
exit
area 0.0.0.25
nssa
exit
exit
area 1.2.3.4
exit
area 4.3.2.1
interface "SR1-3"
exit
exit
area 4.3.2.1
interface "SR1-3" secondary
exit
exit
---------------------------------------------A:ALA-49>config>router>ospf# area 0.0.0.20
Configuring Authentication
Authentication must be explicitly configured. The following authentication commands can be
configured on the interface level or the virtual link level:
7210 SAS M, X OS Routing Protocols Guide
Page 41
Configuring OSPF Components
•
authentication-key — Configures the password used by the OSPF interface or
virtual-link to send and receive OSPF protocol packets on the interface when simple
password authentication is configured.
•
authentication-type — Enables authentication and specifies the type of
authentication to be used on the OSPF interface, either password or message digest.
•
message-digest-key — Use this command when message-digest keyword is
selected in the authentication-type command. The Message Digest 5 (MD5)
hashing algorithm is used for authentication. MD5 is used to verify data integrity by
creating a 128-bit message digest from the data input. It is unique to that specific data.
An special checksum is included in transmitted packets and are used by the far-end router to verify
the packet by using an authentication key (a password). Routers on both ends must use the same
MD5 key.
MD5 can be configured on each interface and each virtual link. If MD5 is enabled on an interface,
then that interface accepts routing updates only if the MD5 authentication is accepted. Updates that
are not authenticated are rejected. A router accepts only OSPF packets sent with the same key-id
value defined for the interface.
When the hash parameter is not used, non-encrypted characters can be entered. Once configured
using the message-digest-key command, then all keys specified in the command are stored in
encrypted format in the configuration file using the hash keyword. When using the hash keyword
the password must be entered in encrypted form. Hashing cannot be reversed. Issue the no
message-digest-key key-id command and then re-enter the command without the hash
parameter to configure an unhashed key.
The following CLI commands are displayed to illustrate the key authentication features. These
command parameters can be defined at the same time interfaces and virtual-links are being
configured. See Configuring an Interface on page 40 and Configuring a Virtual Link on page 39.
Use the following CLI syntax to configure authentication:
CLI Syntax: ospf ospf-instance
area area-id
interface ip-int-name
authentication-key [authentication-key|hash-key]
[hash]
authentication-type [password|message-digest]
message-digest-key key-id md5 key [hash]
virtual-link router-id transit-area area-id
authentication-key [authentication-key|hash-key]
[hash]
authentication-type [password|message-digest]
message-digest-key key-id md5 key [hash]
The following displays authentication configuration examples:
Page 42
7210 SAS M, X OS Routing Protocols Guide
OSPF
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
virtual-link 1.2.3.4 transit-area 1.2.3.4
hello-interval 9
dead-interval 40
exit
interface "system"
exit
exit
area 0.0.0.20
stub
exit
interface "to-103"
exit
exit
area 0.0.0.25
nssa
exit
exit
area 0.0.0.40
interface "test1"
authentication-type password
authentication-key "3WErEDozxyQ" hash
exit
exit
area 1.2.3.4
exit
---------------------------------------------A:ALA-49>config>router>ospf#
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
virtual-link 10.0.0.1 transit-area 0.0.0.1
authentication-type message-digest
message-digest-key 2 md5 "Mi6BQAFi3MI" hash
exit
virtual-link 1.2.3.4 transit-area 1.2.3.4
hello-interval 9
dead-interval 40
7210 SAS M, X OS Routing Protocols Guide
Page 43
Configuring OSPF Components
exit
interface "system"
exit
exit
area 0.0.0.1
exit
area 0.0.0.20
stub
exit
interface "to-103"
exit
exit
area 0.0.0.25
nssa
exit
exit
area 0.0.0.40
interface "test1"
authentication-type password
authentication-key "3WErEDozxyQ" hash
exit
exit
area 1.2.3.4
exit
---------------------------------------------A:ALA-49>config>router>ospf#
Page 44
7210 SAS M, X OS Routing Protocols Guide
OSPF
Assigning a Designated Router
A designated router is elected according to the priority number advertised by the routers. When a
router starts up, it checks for a current designated router. If a designated router is present, then the
router accepts that designated router, regardless of its own priority designation. When a router
fails, then new designated and backup routers are elected according their priority numbers.
The priority command is only used if the interface is a broadcast type. The designated router is
responsible for flooding network link advertisements on a broadcast network to describe the
routers attached to the network. A router uses hello packets to advertise its priority. The router
with the highest priority interface becomes the designated router. A router with priority 0 is not
eligible to be a designated router or a backup designated router. At least one router on each logical
IP network or subnet must be eligible to be the designated router. By default, routers have a
priority value of 1.
Use the following CLI syntax to configure the designated router:
CLI Syntax: ospf ospf-instance
area area-id
interface ip-int-name
priority number
The following displays a priority designation example:
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
virtual-link 10.0.0.1 transit-area 0.0.0.1
authentication-type message-digest
message-digest-key 2 md5 "Mi6BQAFi3MI" hash
exit
virtual-link 1.2.3.4 transit-area 1.2.3.4
hello-interval 9
dead-interval 40
exit
interface "system"
exit
exit
area 0.0.0.1
exit
area 0.0.0.20
stub
exit
interface "to-103"
7210 SAS M, X OS Routing Protocols Guide
Page 45
Configuring OSPF Components
exit
exit
area 0.0.0.25
nssa
exit
interface "if2"
priority 100
exit
exit
area 0.0.0.40
interface "test1"
authentication-type password
authentication-key "3WErEDozxyQ" hash
exit
exit
area 1.2.3.4
exit
---------------------------------------------A:ALA-49>config>router>ospf#
Page 46
7210 SAS M, X OS Routing Protocols Guide
OSPF
Configuring Route Summaries
Area border routers send summary (type 3) advertisements into a stub area or NSSA to describe
the routes to other areas. This command is particularly useful to reduce the size of the routing and
Link State Database (LSDB) tables within the stub or NSSA.
By default, summary route advertisements are sent into the stub area or NSSA. The no form of the
summaries command disables sending summary route advertisements and, in stub areas, the
default route is advertised by the area border router.
The following CLI commands are displayed to illustrate route summary features. These command
parameters can be defined at the same time stub areas and NSSAs are being configured. See
Configuring a Stub Area on page 37 and Configuring a Not-So-Stubby Area on page 38.
Use the following CLI syntax to configure a route summary:
CLI Syntax: ospf ospf-instance
area area-id
stub
summaries
nssa
summaries
The following displays a stub route summary configuration example:
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
virtual-link 10.0.0.1 transit-area 0.0.0.1
authentication-type message-digest
message-digest-key 2 md5 "Mi6BQAFi3MI" hash
exit
virtual-link 1.2.3.4 transit-area 1.2.3.4
hello-interval 9
dead-interval 40
exit
interface "system"
exit
exit
area 0.0.0.1
exit
area 0.0.0.20
stub
7210 SAS M, X OS Routing Protocols Guide
Page 47
Configuring OSPF Components
exit
interface "to-103"
exit
exit
area 0.0.0.25
nssa
exit
interface "if2"
priority 100
exit
exit
area 0.0.0.40
interface "test1"
authentication-type password
authentication-key "3WErEDozxyQ" hash
exit
exit
area 1.2.3.4
exit
---------------------------------------------A:ALA-49>config>router>ospf#
Configuring Route Preferences
A route can be learned by the router from different protocols, in which case, the costs are not
comparable. When this occurs the preference value is used to decide which route is installed in the
forwarding table if several protocols calculate routes to the same destination. The route with the
lowest preference value is selected
Different protocols should not be configured with the same preference, if this occurs the tiebreaker
is per the default preference table as defined in Table 2. If multiple routes are learned with an
identical preference using the same protocol, the lowest cost route is used.
Table 2: Route Preference Defaults by Route Type
Route Type
Page 48
Preference
Configurable
Direct attached
0
No
Static routes
5
Yes
OSPF internal
10
Yesa
IS-IS level 1 internal
15
Yes
IS-IS level 2 internal
18
Yes
OSPF external
150
Yes
IS-IS level 1 external
160
Yes
7210 SAS M, X OS Routing Protocols Guide
OSPF
Table 2: Route Preference Defaults by Route Type
Route Type
Preference
Configurable
IS-IS level 2 external
165
Yes
BGP
170
Yes
a. Preference for OSPF internal routes is configured with the preference command.
The following CLI commands are displayed to illustrate route preference features. The command
parameters can be defined at the same time you are configuring OSPF. See Configuring OSPF
Components on page 35.
7210 SAS M, X OS Routing Protocols Guide
Page 49
Configuring OSPF Components
Use the following CLI syntax to configure a route preference:
CLI Syntax: ospf ospf-instance
preference preference
external-preference preference
The following displays a route preference configuration example:
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
preference 9
external-preference 140
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
virtual-link 10.0.0.1 transit-area 0.0.0.1
authentication-type message-digest
message-digest-key 2 md5 "Mi6BQAFi3MI" hash
exit
virtual-link 1.2.3.4 transit-area 1.2.3.4
hello-interval 9
dead-interval 40
exit
interface "system"
exit
exit
area 0.0.0.1
exit
area 0.0.0.20
stub
exit
interface "to-103"
exit
exit
area 0.0.0.25
nssa
exit
interface "if2"
priority 100
exit
exit
area 0.0.0.40
interface "test1"
authentication-type password
authentication-key "3WErEDozxyQ" hash
exit
exit
area 1.2.3.4
exit
----------------------------------------------
Page 50
7210 SAS M, X OS Routing Protocols Guide
OSPF
OSPF Configuration Management Tasks
This section discusses the following OSPF configuration management tasks:
•
Modifying a Router ID on page 51
•
Deleting a Router ID on page 51
•
Modifying OSPF Parameters on page 53
Modifying a Router ID
Since the router ID is defined in the config>router context, not in the OSPF configuration
context, the protocol instance is not aware of the change. Re-examine the plan detailing the router
ID. Changing the router ID on a device could cause configuration inconsistencies if associated
values are not also modified.
After you have changed a router ID, manually shut down and restart the protocol using the
shutdown and no shutdown commands in order for the changes to be incorporated.
Use the following CLI syntax to change a router ID number:
CLI Syntax: config>router# router-id router-id
The following displays a NSSA router ID modification example:
A:ALA-49>config>router# info
-----------------------------------------IP Configuration
-----------------------------------------interface "system"
address 10.10.10.104/32
exit
interface "to-103"
address 10.0.0.103/24
port 1/1/1
exit
router-id 10.10.10.104
-----------------------------------------A:ALA-49>config>router#
Deleting a Router ID
You can modify a router ID, but you cannot delete the parameter. When the no router
router-id command is issued, the router ID reverts to the default value, the system interface
7210 SAS M, X OS Routing Protocols Guide
Page 51
OSPF Configuration Management Tasks
address (which is also the loopback address). If a system interface address is not configured, then
the last 32 bits of the chassis MAC address is used as the router ID.
Page 52
7210 SAS M, X OS Routing Protocols Guide
OSPF
Modifying OSPF Parameters
You can change or remove existing OSPF parameters in the CLI or NMS. The changes are applied
immediately.
The following example displays an OSPF modification in which an interface is removed and
another interface added.
Example:
config>router# ospf 1
config>router>ospf# area 0.0.0.20
config>router>ospf>area# no interface "to-103"
config>router>ospf>area# interface "to-HQ
config>router>ospf>area>if$ priority 50
config>router>ospf>area>if# exit
config>router>ospf>area# exit
The following example displays the OSPF configuration with the modifications entered in the
previous example:
A:ALA-49>config>router>ospf# info
---------------------------------------------asbr
overload
overload-on-boot timeout 60
traffic-engineering
preference 9
external-preference 140
export "OSPF-Export"
graceful-restart
helper-disable
exit
area 0.0.0.0
virtual-link 10.0.0.1 transit-area 0.0.0.1
authentication-type message-digest
message-digest-key 2 md5 "Mi6BQAFi3MI" hash
exit
virtual-link 1.2.3.4 transit-area 1.2.3.4
hello-interval 9
dead-interval 40
exit
interface "system"
exit
exit
area 0.0.0.1
exit
area 0.0.0.20
stub
exit
interface "to-HQ"
priority 50
exit
exit
area 0.0.0.25
7210 SAS M, X OS Routing Protocols Guide
Page 53
OSPF Configuration Management Tasks
nssa
exit
interface "if2"
priority 100
exit
exit
area 0.0.0.40
interface "test1"
authentication-type password
authentication-key "3WErEDozxyQ" hash
exit
exit
area 1.2.3.4
exit
---------------------------------------------A:ALA-49>config>router>ospf#
Page 54
7210 SAS M, X OS Routing Protocols Guide
OSPF
OSPF Command Reference
Command Hierarchies
• Configuration Commands. on page 55
• Show Commands on page 57
• Clear Commands on page 57
• Debug Commands on page 57
Configuration Commands.
config
— router
— [no] ospf
— [no] ospf3
— [no] area area-id
— area-range ip-prefix/mask [advertise | not-advertise]
— no area-range ip-prefix/mask
— [no] blackhole-aggregate
— [no] interface ip-int-name [secondary]
—
— authentication bidirectional sa-name
— authentication inbound sa-name outbound sa-name
— no authentication
— bfd-enable [remain-down-on-failure]
— no bfd-enable
— dead-interval seconds
— no dead-interval
— export policy-name [.. policy-name]
— no export
— export-limit number [log percentage]
— no export-limit
— hello-interval seconds
— no hello-interval
— interface-type {broadcast | point-to-point}
— no interface-type
— metric metric
— no metric
— mtu bytes
— no mtu
— [no] passive
— priority number
— no priority
— retransmit-interval seconds
— no retransmit-interval
— [no] shutdown
7210 SAS M, X OS Routing Protocols Guide
Page 55
Configuration Commands.
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
Page 56
— transit-delay seconds
— no transit-delay
— key-rollover-interval key-rollover-interval
— [no] nssa
— area-range ip-prefix/ipv6 [advertise | not-advertise]
— no area-range ip-prefix/ipv6
— originate-default-route [type-nssa]
— no originate-default-route
— [no] redistribute-external
— [no] summaries
— [no] stub
— default-metric metric
— no default-metric
— [no] summaries
— [no] virtual-link router-id transit-area area-id
— authentication bidirectional sa-name
— authentication inbound sa-name outbound sa-name
— no authentication
— dead-interval seconds
— no dead-interval
— hello-interval seconds
— no hello-interval
— retransmit-interval seconds
— no retransmit-interval
— [no] shutdown
— transit-delay seconds
— no transit-delay
[no] asbr [trace-path domain-id]
[no] disable-ldp-sync
export policy-name [ policy-name...(up to 5 max)]
no export
export-limit number [log percentage]
no export-limit
external-db-overflow limit seconds
no external-db-overflow
external-preference preference
no external-preference
[no] graceful-restart
— [no] helper-disable
[no] ldp-over-rsvp
overload [timeout seconds]
no overload
[no] overload-include-stub
overload-on-boot [timeout seconds]
no overload-on-boot
preference preference
no preference
reference-bandwidth bandwidth-in-kbps
no reference-bandwidth
router-id ip-address
no router-id
[no] shutdown
timers
— [no] lsa-arrival lsa-arrival-time
7210 SAS M, X OS Routing Protocols Guide
OSPF
— [no] lsa-generate max-lsa-wait [lsa-initial-wait [lsa-second-wait]]
— [no] spf-wait max-spf-wait [spf-initial-wait [spf-second-wait]]
—
Show Commands
show
— router
— ospf
— ospf3
— area [area-id] [detail]
— database [type {router | network | summary | asbr-summary | external | nssa | all}
[area area-id] [adv-router router-id] [link-state-id] [detail]
— interface [ip-int-name|ip-address|ipv6-address] [detail]]
— interface [area area-id] [detail]
— interface [ip-int-name|ip-address|ipv6-address] database [detail]
— neighbor [remote ip-address] [detail]
— neighbor [ip-int-name] [router-id] [detail]
— opaque-database area area-id | as] [adv-router router-id][ls-id] [detail]
— range [area-id]
— spf
— statistics
— status
— virtual-link [detail]
— virtual-neighbor [remote ip-address] [detail]
Clear Commands
clear
— router
— ospf
—
—
—
—
database [purge]
export
neighbor [ip-int-name | ip-address]
statistics
—
—
—
—
—
—
—
—
—
—
area [area-id]
no area
area-range [ip-address]
no area-range
cspf [ip-addr]
no cspf
[no] graceful-restart
interface [ip-int-name | ip-address]
no interface
leak [ip-address]
Debug Commands
debug
— router
— ospf
— ospf3
7210 SAS M, X OS Routing Protocols Guide
Page 57
Debug Commands
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
Page 58
no leak
lsdb [type] [ls-id] [adv-rtr-id] [area area-id]
no lsdb
[no] misc
neighbor [ip-int-name | router-id]
no neighbor
nssa-range [ip-address]
no nssa-range
packet [packet-type] [interface-name] [ingress | egress] [detail]
no packet
rtm [ip-addr]
no rtm
spf [type] [dest-addr]
no spf
virtual-neighbor [ip-address]
no virtual-neighbor
7210 SAS M, X OS Routing Protocols Guide
OSPF
Configuration Commands
Generic Commands
shutdown
Syntax
Context
Description
[no] shutdown
config>router>ospf
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
The shutdown command administratively disables the entity. When disabled, an entity does not change,
reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the
no shutdown command.
The shutdown command administratively disables an entity. The operational state of the entity is disabled as
well as the operational state of any entities contained within. Many objects must be shut down before they
may be deleted.
Unlike other commands and parameters where the default state is not indicated in the configuration file,
shutdown and no shutdown are always indicated in system generated configuration files.
The no form of the command puts an entity into the administratively enabled state.
Default
OSPF Protocol — The Open Shortest Path First (OSPF) protocol is created in the no shutdown state.
OSPF Interface — When an IP interface is configured as an OSPF interface, OSPF on the interface is in
the no shutdown state by default.
7210 SAS M, X OS Routing Protocols Guide
Page 59
OSPF Global Commands
OSPF Global Commands
ospf
Syntax
Context
Description
[no] ospf
config>router
This command configures the router ID for OSPF.
The router ID configured in the base instance of OSPF overrides the router ID configured in the
config>router context.
The default value for the base instance is inherited from the configuration in the config>router context.
When that is not configured the following applies:
1.
The system uses the system interface address (which is also the loopback address).
2.
If a system interface address is not configured, use the last 32 bits of the chassis MAC address.
When configuring a new router ID, the instance is not automatically restarted with the new router ID. The
next time the instance is initialized, the new router ID is used.
Issue the shutdown and no shutdown commands for the instance for the new router ID to be used, or reboot
the entire router.
The no form of the command to reverts to the default value.
Default
no ospf
ospf3
Syntax
Context
Description
[no] ospf3
config>router
This command enables the context to configure OSPF to support version 6 of the Internet Protocol (IPv6).
When an OSPF instance is created, the protocol is enabled. To start or suspend execution of the OSPF
protocol without affecting the configuration, use the no shutdown command.
The no form of the command deletes the OSPF protocol instance removing all associated configuration
parameters.
Default
Page 60
no ospf — The OSPF protocol is not enabled.
7210 SAS M, X OS Routing Protocols Guide
OSPF
asbr
Syntax
Context
Description
[no] asbr [trace-path domain-id]
config>router>ospf
config>router>ospf3
This command configures the router as a Autonomous System Boundary Router (ASBR) if the router is to
be used to export routes from the Routing Table Manager (RTM) into this instance of OSPF. Once a router is
configured as an ASBR, the export policies into this OSPF domain take effect. If no policies are configured
no external routes are redistributed into the OSPF domain.
The no form of the command removes the ASBR status and withdraws the routes redistributed from the
Routing Table Manager into this instance of OSPF from the link state database.
no asbr — The router is not an ASBR.
compatible-rfc1583
Syntax
Context
Description
[no] compatible-rfc1583
config>router>ospf
This command enables OSPF summary and external route calculations in compliance with RFC1583 and
earlier RFCs.
RFC1583 and earlier RFCs use a different method to calculate summary and external route costs. To avoid
routing loops, all routers in an OSPF domain should perform the same calculation method.
Although it would be favorable to require all routers to run a more current compliancy level, this command
allows the router to use obsolete methods of calculation.
The no form of the command enables the post-RFC1583 method of summary and external route calculation.
Default
compatible-rfc1583 — RFC1583 compliance is enabled.
disable-ldp-sync
Syntax
Context
Description
[no] disable-ldp-sync
config>router>ospf
This command disables the IGP-LDP synchronization feature on all interfaces participating in the OSPF
routing protocol. When this command is executed, IGP immediately advertises the actual value of the link
cost for all interfaces which have the IGP-LDP synchronization enabled if the currently advertized cost is
different. It will then disable IGP-LDP synchornization for all interfaces. This command does not delete the
interface configuration. The no form of this command has to be entered to re-enable IGP-LDP
synchronization for this routing protocol.
7210 SAS M, X OS Routing Protocols Guide
Page 61
OSPF Global Commands
The no form of this command restores the default settings and re-enables IGP-LDP synchronization on all
interfaces participating in the OSPF routing protocol and for which the ldp-sync-timer is configured.
Default
no disable-ldp-sync
export
Syntax
Context
Description
export policy-name [policy-name…]
no export
config>router>ospf
config>router>ospf3
This command associates export route policies to determine which routes are exported from the route table
to OSPF. Export polices are only in effect if OSPF is configured as an ASBR.
If no export policy is specified, non-OSPF routes are not exported from the routing table manager to OSPF.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first
policy that matches is applied. If multiple export commands are issued, the last command entered will
override the previous command. A maximum of five policy names can be specified.
The no form of the command removes all policies from the configuration.
Default
Parameters
no export — No export route policies specified.
policy-name — The export route policy name. Allowed values are any string up to 32 characters long
composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces,
etc.), the entire string must be enclosed within double quotes.
The specified name(s) must already be defined.
export-limit
Syntax
Context
Description
export-limit number [log percentage]
no export-limit
config>router>ospf
config>router>ospf3
This command configures the maximum number of routes (prefixes) that can be exported into OSPF from
the route table.
The no form of the command removes the parameters from the configuration.
Default
Parameters
no export-limit, the export limit for routes or prefixes is disabled..
number — Specifies the maximum number of routes (prefixes) that can be exported into OSPF from the
route table.
Values
Page 62
1 — 4294967295
7210 SAS M, X OS Routing Protocols Guide
OSPF
log percentage — Specifies the percentage of the export-limit, at which a warning log message and SNMP
notification would be sent.
Values
1 — 100
external-db-overflow
Syntax
Context
Description
external-db-overflow limit interval
no external-db-overflow
config>router>ospf
config>router>ospf3
This command enables limits on the number of non-default AS-external-LSA entries that can be stored in
the LSDB and specifies a wait timer before processing these after the limit is exceeded.
The limit value specifies the maximum number of non-default AS-external-LSA entries that can be stored in
the link-state database (LSDB). Placing a limit on the non-default AS-external-LSAs in the LSDB protects
the router from receiving an excessive number of external routes that consume excessive memory or CPU
resources. If the number of routes reach or exceed the limit, the table is in an overflow state. When in an
overflow state, the router will not originate any new AS-external-LSAs. In fact, it withdraws all the selforiginated non-default external LSAs.
The interval specifies the amount of time to wait after an overflow state before regenerating and processing
non-default AS-external-LSAs. The waiting period acts like a dampening period preventing the router from
continuously running Shortest Path First (SPF) calculations caused by the excessive number of non-default
AS-external LSAs.
The external-db-overflow must be set identically on all routers attached to any regular OSPF area. OSPF
stub areas and not-so-stubby areas (NSSAs) are excluded.
The no form of the command disables limiting the number of non-default AS-external-LSA entries.
Default
Parameters
no external-db-overflow — No limit on non-default AS-external-LSA entries.
limit — The maximum number of non-default AS-external-LSA entries that can be stored in the LSDB
before going into an overflow state expressed as a decimal integer.
Values
-1 — 2147483674
interval — The number of seconds after entering an overflow state before attempting to process non-default
AS-external-LSAs expressed as a decimal integer.
Values
0 — 2147483674
7210 SAS M, X OS Routing Protocols Guide
Page 63
OSPF Global Commands
external-preference
Syntax
Context
Description
external-preference preference
no external-preference
config>router>ospf
config>router>ospf3
This command configures the preference for OSPF external routes.
A route can be learned by the router from different protocols, in which case, the costs are not comparable.
When this occurs the preference is used to decide which route will be used.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is per the
default preference table as defined in the Table 3, “Route Preference Defaults by Route Type,” on page 64. If
multiple routes are learned with an identical preference using the same protocol, the lowest cost route is
used.
If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are
equal, then the decision of what route to use is determined by the configuration of the ecmp in the
config>router context.
The no form of the command reverts to the default value.
Default
Parameters
external-preference 150 — OSPF external routes have a default preference of 150.
preference — The preference for external routes expressed as a decimal integer. Defaults for different route
types are listed in Table 3.
Table 3: Route Preference Defaults by Route Type
Route Type
Preference
Configurable
Direct attached
0
No
Static routes
5
Yes
OSPF internal
10
Yes*
IS-IS level 1 internal
15
Yes
IS-IS level 2 internal
18
Yes
RIP
100
Yes
OSPF external
150
Yes
IS-IS level 1 external
160
Yes
IS-IS level 2 external
165
Yes
BGP
170
Yes
*. Preference for OSPF internal routes is configured with the preference
command.
Values
Page 64
1 — 255
7210 SAS M, X OS Routing Protocols Guide
OSPF
graceful-restart
Syntax
Context
Description
[no] graceful-restart
config>router>ospf
This command enables graceful-restart for OSPF. When the control plane of a GR-capable router fails, the
neighboring routers (GR helpers) temporarily preserve adjacency information, so packets continue to be
forwarded through the failed GR router using the last known routes. If the control plane of the GR router
comes back up within the GR timer, then the routing protocols would re-converge to minimize service
interruption.
Note: This command is not support for OSPFv3
The no form of the command disables graceful restart and removes all graceful restart configurations in the
OSPF instance.
Default
no graceful-restart
helper-disable
Syntax
Context
Description
[no] helper-disable
config>router>ospf>graceful-restart
This command disables the helper support for graceful restart.
When graceful-restart is enabled, the router can be a helper (meaning that the router is helping a neighbor
to restart) or be a restarting router or both. The 7210 SAS M OS supports only helper mode. This facilitates
the graceful restart of neighbors but will not act as a restarting router (meaning that the 7210 SAS M OS will
not help the neighbors to restart).
Note: This command is not support for OSPFv3
The no helper-disable command enables helper support and is the default when graceful-restart is enabled.
Default
disabled
ldp-over-rsvp
Syntax
[no] ldp-over-rsvp
Context
config>router>ospf
Description
This command allows LDP-over-RSVP processing in this OSPF instance.
7210 SAS M, X OS Routing Protocols Guide
Page 65
OSPF Global Commands
overload
Syntax
Context
Description
overload [timeout seconds]
no overload
config>router>ospf
config>router>ospf3
This command changes the overload state of the local router so that it appears to be overloaded. When
overload is enabled, the router can participate in OSPF routing, but is not used for transit traffic. Traffic
destined to directly attached interfaces continues to reach the router.
To put the IGP in an overload state enter a timeout value. The IGP will enter the overload state until the
timeout timer expires or a no overload command is executed.
If the overload command is encountered during the execution of an overload-on-boot command then this
command takes precedence. This could occur as a result of a saved configuration file where both parameters
are saved. When the file is saved by the system the overload-on-boot command is saved after the overload
command. However, when overload-on-boot is configured under OSPF with no timeout value configured,
the router will remain in overload state indefinitely after a reboot.
Use the no form of this command to return to the default. When the no overload command is executed, the
overload state is terminated regardless of the reason the protocol entered overload state.
Default
Parameters
no overload
timeout seconds — Specifies the number of seconds to reset overloading.
Values
1 — 1800
Default
60
overload-include-stub
Syntax
Context
Description
Default
Page 66
[no] overload-include-stub
config>router>ospf
config>router>ospf3
This command is used to to determine if the OSPF stub networks should be advertised with a maximum
metric value when the system goes into overload state for any reason. When enabled, the system uses the
maximum metric value. When this command is enabled and the router is in overload, all stub interfaces,
including loopback and system interfaces, will be advertised at the maximum metric.
no overload-include-stub
7210 SAS M, X OS Routing Protocols Guide
OSPF
overload-on-boot
Syntax
Context
Description
overload-on-boot [timeout seconds]
no overload
config>router>ospf
config>router>ospf3
When the router is in an overload state, the router is used only if there is no other router to reach the
destination. This command configures the IGP upon bootup in the overload state until one of the following
events occur:
• The timeout timer expires.
• A manual override of the current overload state is entered with the no overload command.
The no overload command does not affect the overload-on-boot function.
The no form of the command removes the overload-on-boot functionality from the configuration.
The default timeout value is 60 seconds, which means after 60 seconds overload status the SR will recover
(change back to non-overload status). However, when overload-on-boot is configured under OSPF with no
timeout value the router will remain in overload state indefinitely after a reboot.
Parameters
timeout seconds — Specifies the number of seconds to reset overloading.
Values
1 — 1800
Default
indefinitely in overload.
preference
Syntax
Context
Description
preference preference
no preference
config>router>ospf
config>router>ospf3
This command configures the preference for OSPF internal routes.
A route can be learned by the router from different protocols, in which case, the costs are not comparable.
When this occurs the preference is used to decide which route will be used.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is per the
default preference table as defined in Table 4. If multiple routes are learned with an identical preference
using the same protocol, the lowest cost route is used.
The no form of the command reverts to the default value.
Default
Parameters
preference 10 — OSPF internal routes have a preference of 10.
preference — The preference for internal routes expressed as a decimal integer. Defaults for different route
types are listed in Table 4.
7210 SAS M, X OS Routing Protocols Guide
Page 67
OSPF Global Commands
Table 4: Route Preference Defaults by Route Type
Route Type
Preference
Configurable
Direct attached
0
No
Static routes
5
Yes
OSPF internal
10
Yes*
IS-IS level 1 internal
15
Yes
IS-IS level 2 internal
18
Yes
RIP
100
Yes
OSPF external
150
Yes
IS-IS level 1 external
160
Yes
IS-IS level 2 external
165
Yes
BGP
170
Yes
*. Preference for OSPF internal routes is configured with the preference
command.
Values
1 — 255
reference-bandwidth
Syntax
Context
Description
reference-bandwidth reference-bandwidth
no reference-bandwidth
config>router>ospf
config>router>ospf3
This command configures the reference bandwidth in kilobits per second (Kbps) that provides the reference
for the default costing of interfaces based on their underlying link speed.
The default interface cost is calculated as follows:
cost = reference-bandwidth ÷ bandwidth
The default reference-bandwidth is 100,000,000 Kbps or 100 Gbps, so the default auto-cost metrics for various
link speeds are as as follows:
• 10 Mbs link default cost of 10000
• 100 Mbs link default cost of 1000
• 1 Gbps link default cost of 100
• 10 Gbps link default cost of 10
Page 68
7210 SAS M, X OS Routing Protocols Guide
OSPF
The reference-bandwidth command assigns a default cost to the interface based on the interface speed. To
override this default cost on a particular interface, use the metric metric command in the
config>router>ospf>area>interface ip-int-name context.
The no form of the command reverts the reference-bandwidth to the default value.
Default
Parameters
reference-bandwidth 100000000 — Reference bandwidth of 100 Gbps.
reference-bandwidth — The reference bandwidth in kilobits per second expressed as a decimal integer.
Values
1 — 100000000
router-id
Syntax
router-id ip-address
no router-id
Context
config>router>ospf
config>router>ospf3
Description
This command configures the router ID for the OSPF instance. This command configures the router ID for
the OSPF instance.
When configuring the router ID in the base instance of OSPF it overrides the router ID configured in the
config>router context.
The default value for the base instance is inherited from the configuration in the config>router context. If
the router ID in the tconfig>router context is not configured, the following applies:
• The system uses the system interface address (which is also the loopback address).
• If a system interface address is not configured, use the last 32 bits of the chassis MAC address.
This is a required command when configuring multiple instances and the instance being configured is not
the base instance.
When configuring a new router ID, the instance is not automatically restarted with the new router ID. The
next time the instance is initialized, the new router ID is used.
To force the new router ID to be used, issue the shutdown and no shutdown commands for the instance, or
reboot the entire router.
The no form of the command to reverts to the default value.
Default
Parameters
The default value for non-base instances is 0.0.0.0 and is invalid, in this case the instance of OSPF will not
start and when doing a show command an error condition will be displayed.
ip-address — Specifies a 32-bit, unsigned integer uniquely identifying the router in the Autonomous
System.
7210 SAS M, X OS Routing Protocols Guide
Page 69
OSPF Global Commands
timers
Syntax
Context
Description
timers
config>router>ospf
config>router>ospf3
This command enables the context that allows for the configuration of OSPF timers. Timers control the
delay between receipt of a link state advertisement (LSA) requiring a Dijkstra (Shortest Path First (SPF))
calculation and the minimum time between successive SPF calculations.
Changing the timers affects CPU utilization and network reconvergence times. Lower values reduce
convergence time but increase CPU utilization. Higher values reduce CPU utilization but increase
reconvergence time.
Default
none
lsa-arrival
Syntax
lsa-arrival lsa-arrival-time
no lsa-arrival
Context
config>router>ospf>timers
config>router>ospf3
Description
This parameter defines the minimum delay that must pass between receipt of the same Link State
Advertisements (LSAs) arriving from neighbors.
It is recommended that the neighbors configured (lsa-generate) lsa-second-wait interval is equal or greater
then the lsa-arrival timer configured here.
Use the no form of this command to return to the default.
Default
Parameters
no lsa-arrival
lsa-arrival-time — Specifies the timer in milliseconds. Values entered that do not match this requirement
will be rejected.
Values
0 — 600000
lsa-generate
Syntax
Context
Description
Page 70
lsa-generate max-lsa-wait [lsa-initial-wait [lsa-second-wait]]
no lsa-generate-interval
config>router>ospf>timers
config>router>ospf3
This parameter customizes the throttling of OSPF LSA-generation. Timers that determine when to generate
the first, second, and subsequent LSAs can be controlled with this command. Subsequent LSAs are
generated at increasing intervals of the lsa-second-wait timer until a maximum value is reached.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Configuring the lsa-arrival interval to equal or less than the lsa-second-wait interval configured in the lsagenerate command is recommended.
Use the no form of this command to return to the default.
Default
Parameters
no lsa-generate
max-lsa-wait — Specifies the maximum interval, in milliseconds, between two consecutive ocurrences of an
LSA being generated.
Values
10 — 600,000
Default
5,000 milliseconds
lsa-initial-wait — Specifies the first waiting period between link-state advertisements (LSA) originate(s), in
milliseconds. When the LSA exceeds the lsa-initial-wait timer value and the topology changes, there is
no wait period and the LSA is immediately generated.
When an LSA is generated, the initial wait period commences. If, within the specified lsa-initial-wait
period and another topology change occurs, then the lsa-initial-wait timer applies.
Values
10 — 600000
Default
5,000 milliseconds
lsa-second-wait — Specifies the hold time in milliseconds between the first and second LSA generation. The
next topology change is subject to this second wait period. With each subsequent topology change, the
wait time doubles (this is 2x the previous wait time.). This assumes that each failure occurs within the
relevant wait period.
Values
10 — 600000
Default
5,000 milliseconds
spf-wait
Syntax
Context
Description
spf-wait max-spf-wait [spf-initial-wait [spf-second-wait]]
no spf-wait
config>router>ospf>timers
config>router>ospf3
This command defines the maximum interval between two consecutive SPF calculations in milliseconds.
Timers that determine when to initiate the first, second, and subsequent SPF calculations after a topology
change occurs can be controlled with this command. Subsequent SPF runs (if required) will occur at
exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait
interval is 1000, then the next SPF will run after 2000 milliseconds, and then next SPF will run after 4000
milliseconds, etc., until it reaches the spf-wait value. The SPF interval will stay at the spf-wait value until
there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF
interval will drop back to spf-initial-wait.
The timer must be entered in increments of 100 milliseconds. Values entered that do not match this
requirement will be rejected.
Use the no form of this command to return to the default.
7210 SAS M, X OS Routing Protocols Guide
Page 71
OSPF Global Commands
Default
Parameters
no spf-wait
max-spf-wait — Specifies the maximum interval in milliseconds between two consecutive SPF calculations.
Values
10 — 120000
Default
1000
spf-initial-wait — Specifies the initial SPF calculation delay in milliseconds after a topology change.
Values
10 — 100000
Default
1000
spf-second-wait — Specifies the hold time in milliseconds between the first and second SPF calculation.
Values
10 — 100000
Default
1000
traffic-engineering
Syntax
Context
Description
[no] traffic-engineering
config>router>ospf
This command enables traffic engineering route calculations constrained by nodes or links.
Traffic engineering enables the router to perform route calculations constrained by nodes or links. The traffic
engineering capabilities of this router are limited to calculations based on link and nodal constraints.
The no form of the command disables traffic engineered route calculations.
Default
Page 72
no traffic-engineering — Traffic engineered route calculations is disabled.
7210 SAS M, X OS Routing Protocols Guide
OSPF
OSPF Area Commands
area
Syntax
Context
Description
[no] area area-id
config>router>ospf
config>router>ospf3
This command creates the context to configure an OSPF or OSPF3 area. An area is a collection of network
segments within an AS that have been administratively grouped together. The area ID can be specified in
dotted decimal notation or as a 32-bit decimal integer.
The no form of the command deletes the specified area from the configuration. Deleting the area also
removes the OSPF configuration of all the interfaces, virtual-links, and address-ranges etc., that are currently
assigned to this area.
Default
Parameters
no area — No OSPF areas are defined.
area-id — The OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
Values
0.0.0.0 — 255.255.255.255 (dotted decimal), 0 — 4294967295 (decimal integer)
area-range
Syntax
Context
Description
area-range ip-prefix/mask [advertise | not-advertise]
no area-range ip-prefix/mask
config>router>ospf3>area
config>router>ospf3>area>nssa
This command creates ranges of addresses on an Area Border Router (ABR) for the purpose of route
summarization or suppression. When a range is created, the range is configured to be advertised or not
advertised into other areas. Multiple range commands may be used to summarize or hide different ranges. In
the case of overlapping ranges, the most specific range command applies.
ABRs send summary link advertisements to describe routes to other areas. To minimize the number of
advertisements that are flooded, you can summarize a range of IP addresses and send reachability
information about these addresses in an LSA.
The no form of the command deletes the range (non) advertisement.
Default
Special Cases
no area-range — No range of addresses are defined.
NSSA Context — In the NSSA context, the option specifies that the range applies to external routes (via
type-7 LSAs) learned within the NSSA when the routes are advertised to other areas as type-5 LSAs.
Area Context — If this command is not entered under the NSSA context, the range applies to summary
LSAs even if the area is an NSSA.
7210 SAS M, X OS Routing Protocols Guide
Page 73
OSPF Area Commands
Parameters
ip-prefix — The IP prefix in dotted decimal notation for the range used by the ABR to advertise that
summarizes the area into another area.
Values
ip-prefix/mask:
ipv6-prefix:
ip-prefix a.b.c.d (host bits must be 0)
x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x: [0 — FFFF]H
d: [0 — 255]D
prefix-length:0 — 128
mask — The subnet mask for the range expressed as a decimal integer mask length or in dotted decimal
notation.
Values
0 — 32 (mask length), 0.0.0.0 — 255.255.255.255 (dotted decimal)
advertise | not-advertise — Specifies whether or not to advertise the summarized range of addresses into
other areas. The advertise keyword indicates the range will be advertised, and the keyword notadvertise indicates the range will not be advertised.
The default is advertise.
blackhole-aggregate
Syntax
[no] blackhole-aggregate
Context
config>router>ospf>area
config>router>ospf3>area
Description
This command installs a low priority blackhole route for the entire aggregate. Exisiting routes that make up
the aggregate will have a higher priority and only the components of the range for which no route exists are
blackholed.
It is possible that when performing area aggregation, addresses may be included in the range for which no
actual route exists. This can cause routing loops. To avoid this problem configure the blackhole aggregate
option.
The no form of this command removes this option.
Default
blackhole-aggregate
default-metric
Syntax
Context
Description
default-metric metric
no default-metric
config>router>ospf>area>stub
config>router>ospf3>area
This command configures the metric used by the area border router (ABR) for the default route into a stub
area.
The default metric should only be configured on an ABR of a stub area.
Page 74
7210 SAS M, X OS Routing Protocols Guide
OSPF
An ABR generates a default route if the area is a stub area.
The no form of the command reverts to the default value.
Default
Parameters
default-metric 1
metric — The metric expressed as a decimal integer for the default route cost to be advertised into the stub
area.
Values
1 — 16777215
nssa
Syntax
Context
Description
[no] nssa
config>router>ospf>area
config>router>ospf3>area
This command creates the context to configure an OSPF or OSPF3 Not So Stubby Area (NSSA) and adds/
removes the NSSA designation from the area.
NSSAs are similar to stub areas in that no external routes are imported into the area from other OSPF areas.
The major difference between a stub area and an NSSA is an NSSA has the capability to flood external
routes that it learns throughout its area and via an ABR to the entire OSPF or OSPF3 domain.
Existing virtual links of a non-stub or NSSA area will be removed when the designation is changed to NSSA
or stub.
An area can be designated as stub or NSSA but never both at the same time.
By default, an area is not configured as an NSSA area.
The no form of the command removes the NSSA designation and configuration context from the area.
Default
no nssa — The OSPF or OSPF3 area is not an NSSA.
originate-default-route
Syntax
originate-default-route [type-7]
no originate-default-route
Context
config>router>ospf>area>nssa
config>router>ospf3>area>nssa
Description
This command enables the generation of a default route and its LSA type (3 or 7) into a Not So Stubby Area
(NSSA) by an NSSA Area Border Router (ABR) or Autonomous System Border Router (ASBR).
When configuring an NSSA with no summaries, the ABR will inject a type 3 LSA default route into the
NSSA area. Some older implementations expect a type 7 LSA default route.
The no form of the command disables origination of a default route.
Default
no originate-default-route — A default route is not originated.
7210 SAS M, X OS Routing Protocols Guide
Page 75
OSPF Area Commands
Parameters
type-7 — Specifies a type 7 LSA should be used for the default route.
Configure this parameter to inject a type-7 LSA default route instead the type 3 LSA into the NSSA
configured with no summaries.
To revert to a type 3 LSA, enter originate-default-route without the type-7 parameter.
Default
Type 3 LSA for the default route.
redistribute-external
Syntax
Context
Description
[no] redistribute-external
config>router>ospf>area>nssa
config>router>ospf3>area>nssa
This command enables the redistribution of external routes into the Not So Stubby Area (NSSA) or an NSSA
area border router (ABR) that is exporting the routes into non-NSSA areas.
NSSA or Not So Stubby Areas are similar to stub areas in that no external routes are imported into the area
from other OSPF or OSPF3 areas. The major difference between a stub area and an NSSA is that the NSSA
has the capability to flood external routes that it learns (providing it is an ASBR) throughout its area and via
an Area Border Router to the entire OSPF or OSPF3 domain.
The no form of the command disables the default behavior to automatically redistribute external routes into
the NSSA area from the NSSA ABR.
Default
redistribute-external — External routes are redistributed into the NSSA.
stub
Syntax
Context
Description
[no] stub
config>router>ospf>area
config>router>ospf3>area
This command enables access to the context to configure an OSPF or OSPF3 stub area and adds/removes the
stub designation from the area.
External routing information is not flooded into stub areas. All routers in the stub area must be configured
with the stub command. An OSPF or OSPF3 area cannot be both an NSSA and a stub area.
Existing virtual links of a non STUB or NSSA area will be removed when its designation is changed to
NSSA or STUB.
By default, an area is not a stub area.
The no form of the command removes the stub designation and configuration context from the area.
Default
Page 76
no stub — The area is not configured as a stub area.
7210 SAS M, X OS Routing Protocols Guide
OSPF
summaries
Syntax
Context
Description
[no] summaries
config>router>ospf>area>stub
config>router>ospf>area>nssa
config>router>ospf3>area>stub
config>router>ospf3>area>nssa
This command enables sending summary (type 3) advertisements into a stub area or Not So Stubby Area
(NSSA) on an Area Border Router (ABR).
This parameter is particularly useful to reduce the size of the routing and Link State Database (LSDB) tables
within the stub or NSSA area. (Default: summary)
By default, summary route advertisements are sent into the stub area or NSSA.
The no form of the command disables sending summary route advertisements and, for stub areas, only the
default route is advertised by the ABR.
Default
summaries — Summary routes are advertised by the ABR into the stub area or NSSA.
7210 SAS M, X OS Routing Protocols Guide
Page 77
Interface/Virtual Link Commands
Interface/Virtual Link Commands
advertise-subnet
Syntax
Context
Description
[no] advertise-subnet
config>router>ospf>area>interface ip-int-name
This command enables advertising point-to-point interfaces as subnet routes (network number and mask).
When disabled, point-to-point interfaces are advertised as host routes.
The no form of the command disables advertising point-to-point interfaces as subnet routes meaning they are
advertised as host routes.
Default
advertise-subnet — Advertises point-to-point interfaces as subnet routes.
authentication
Syntax
Context
Description
authentication [inbound sa-name outbound sa-name]
authentication bidirectional sa-name
no authentication
config>router>ospf3>area>interface ip-int-name
config>router>ospf3>area>virtual-link >if
This command configures the password used by the OSPF3 interface or virtual-link to send and receive
OSPF3 protocol packets on the interface when simple password authentication is configured.
All neighboring routers must use the same type of authentication and password for proper protocol
communication.
By default, no authentication key is configured.
The no form of the command removes the authentication.
Default
Parameters
no authentication — No authentication is defined.
inbound sa-name — Specifies the inbound sa-name for OSPF3 authentication.
outbound sa-name — Specifies the outbound sa-name for OSPF3 authentication.
bidirectional sa-name — Specifies bidirectional OSPF3 authentication.
Page 78
7210 SAS M, X OS Routing Protocols Guide
OSPF
authentication-key
Syntax
Context
Description
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
config>router>ospf>area>interface ip-int-name
config>router>ospf>area>virtual-link >if>
This command configures the password used by the OSPF interface or virtual-link to send and receive OSPF
protocol packets on the interface when simple password authentication is configured.
All neighboring routers must use the same type of authentication and password for proper protocol
communication. If the authentication-type is configured as password, then this key must be configured.
By default, no authentication key is configured.
The no form of the command removes the authentication key.
Default
Parameters
no authentication-key — No authentication key is defined.
authentication-key — The authentication key. The key can be any combination of ASCII characters up to 8
characters in length (unencrypted). If spaces are used in the string, enclose the entire string in quotation
marks (“ ”).
hash-key — The hash key. The key can be any combination of ASCII characters up to 22 characters in length
(encrypted). If spaces are used in the string, enclose the entire string in quotation marks
(“ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual
unencrypted key value is not provided.
hash — Specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is
assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in
the configuration file with the hash parameter specified.
hash2 — Specifies the key is entered in a more complex encrypted form. If the hash2 parameter is
not used, the less encrypted hash form is assumed.
authentication-type
Syntax
Context
Description
authentication-type {password | message-digest}
no authentication-type
config>router>ospf>area>interface ip-int-name
config>router>ospf>area>virtual-link router-id
This command enables authentication and specifies the type of authentication to be used on the OSPF
interface.
Both simple password and message-digest authentication are supported.
By default, authentication is not enabled on an interface.
The no form of the command disables authentication on the interface.
7210 SAS M, X OS Routing Protocols Guide
Page 79
Interface/Virtual Link Commands
Default
Parameters
no authentication — No authentication is enabled on an interface.
password — This keyword enables simple password (plain text) authentication. If authentication is enabled
and no authentication type is specified in the command, simple password authentication is enabled.
message-digest — This keyword enables message digest MD5 authentication in accordance with RFC1321.
If this option is configured, then at least one message-digest-key must be configured.
bfd-enable
Syntax
Context
Description
[no] bfd-enable [remain-down-on-failure]
config>router>ospf>area>interface
This command enables the use of bi-directional forwarding (BFD) to control the state of the associated
protocol interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied
to the state of the BFD session between the local node and the remote node. The parameters used for the
BFD are set via the BFD command under the IP interface.
NOTE: BFD is not supported for IPv6 interfaces.
The no form of this command removes BFD from the associated IGP protocol adjacency.
Default
Parameters
no bfd-enable
remain-down-on-failure — Forces adjacency down on BFD failure.
dead-interval
Syntax
Context
Description
dead-interval seconds
no dead-interval
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
This command configures the time, in seconds, that OSPF waits before declaring a neighbor router down. If
no hello packets are received from a neighbor for the duration of the dead interval, the router is assumed to
be down. The minimum interval must be two times the hello interval.
The no form of the command reverts to the default value.
Default
Special Cases
40 seconds
OSPF Interface — If the dead-interval configured applies to an interface, then all nodes on the subnet
must have the same dead interval.
Virtual Link — If the dead-interval configured applies to a virtual link, then the interval on both
termination points of the virtual link must have the same dead interval.
Page 80
7210 SAS M, X OS Routing Protocols Guide
OSPF
Parameters
seconds — The dead interval expressed in seconds.
Values
1 — 65535
export
Syntax
Context
Description
[no] export policy-name [policy-name...up to 5 max]
config>router>ospf
This command configures export routing policies that determine the routes exported from the routing table
to OSPF.
If no export policy is defined, non OSPF routes are not exported from the routing table manager to IS-IS.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first
policy that matches is applied. If multiple export commands are issued, the last command entered overrides
the previous command. A maximum of five policy names can be specified.
If an aggregate command is also configured in the config>router context, then the aggregation is applied
before the export policy is applied.
Routing policies are created in the config>router>policy-options context.
The no form of the command removes the specified policy-name or all policies from the configuration if no
policy-name is specified.
Default
Parameters
no export — No export policy name is specified.
policy-name — The export policy name. Up to five policy-name arguments can be specified.
export-limit
Syntax
Context
Description
export-limit number [log percentage]
no export-limit
config>router>ospf
This command configures the maximum number of routes (prefixes) that can be exported into OSPFfrom
the route table.
The no form of the command removes the parameters from the configuration.
Default
Parameters
no export-limit, the export limit for routes or prefixes is disabled.
number — Specifies the maximum number of routes (prefixes) that can be exported into OSPF from the
route table.
Values
1 — 4294967295
log percentage — Specifies the percentage of the export-limit, at which a warning log message and SNMP
notification would be sent.
Values
1 — 100
7210 SAS M, X OS Routing Protocols Guide
Page 81
Interface/Virtual Link Commands
hello-interval
Syntax
Context
Description
hello-interval seconds
no hello-interval
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
This command configures the interval between OSPF hellos issued on the interface or virtual link.
The hello interval, in combination with the dead-interval, is used to establish and maintain the adjacency.
Use this parameter to edit the frequency that hello packets are sent.
Reducing the interval, in combination with an appropriate reduction in the associated dead-interval, allows
for faster detection of link and/or router failures at the cost of higher processing costs.
The no form of this command reverts to the default value.
Default
Special Cases
hello-interval 10 — A 10-second hello interval.
OSPF Interface — If the hello-interval configured applies to an interface, then all nodes on the subnet
must have the same hello interval.
Virtual Link — If the hello-interval configured applies to a virtual link, then the interval on both
termination points of the virtual link must have the same hello interval.
Parameters
seconds — The hello interval in seconds expressed as a decimal integer.
Values
1 — 65535
interface
Syntax
Context
Description
[no] interface ip-int-name [secondary]
config>router>ospf>area
config>router>ospf3>area
This command creates a context to configure an OSPF interface.
By default, interfaces are not activated in any interior gateway protocol, such as OSPF, unless explicitly
configured.
The no form of the command deletes the OSPF interface configuration for this interface. The shutdown
command in the config>router>ospf>interface context can be used to disable an interface without removing
the configuration for the interface.
Default
Parameters
Page 82
no interface — No OSPF interfaces are defined.
ip-int-name — The IP interface name. Interface names must be unique within the group of defined IP
interfaces for config router interface and config service ies interface commands. An interface name
cannot be in the form of an IP address. Interface names can be any string up to 32 characters long
7210 SAS M, X OS Routing Protocols Guide
OSPF
composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces,
etc.), the entire string must be enclosed within double quotes.
If the IP interface name does not exist or does not have an IP address configured an error message will
be returned.
If the IP interface exists in a different area it will be moved to this area.
secondary — Allows multiple secondary adjacencies to be established over a single IP interface.
interface-type
Syntax
Context
Description
interface-type {broadcast | point-to-point}
no interface-type
config>router>ospf>area>interface
config>router>ospf3>area>interface
This command configures the interface type to be either broadcast or point-to-point.
Use this command to set the interface type of an Ethernet link to point-to-point to avoid having to carry the
broadcast adjacency maintenance overhead of the Ethernet link provided the link is used as a point-to-point.
If the interface type is not known at the time the interface is added to OSPF and subsequently the IP interface
is bound (or moved) to a different interface type, this command must be entered manually.
The no form of the command reverts to the default value.
Default
point-to-point if the physical interface is SONET.
broadcast if the physical interface is Ethernet or unknown.
Special Cases
Virtual-Link — A virtual link is always regarded as a point-to-point interface and not configurable.
Parameters
broadcast — Configures the interface to maintain this link as a broadcast network. To significantly improve
adjacency forming and network convergence, a network should be configured as point-to-point if only
two routers are connected, even if the network is a broadcast media such as Ethernet.
point-to-point — Configures the interface to maintain this link as a point-to-point link.
metric
Syntax
Context
Description
metric metric
no metric
config>router>ospf>area>interface
config>router>ospf3>area>interface
This command configures an explicit route cost metric for the OSPF interface that overrides the metrics
calculated based on the speed of the underlying link.
The no form of the command deletes the manually configured interface metric, so the interface uses the
computed metric based on the reference-bandwidth command setting and the speed of the underlying link.
7210 SAS M, X OS Routing Protocols Guide
Page 83
Interface/Virtual Link Commands
Default
Parameters
no metric — The metric is based on reference-bandwidth setting and the link speed.
metric — The metric to be applied to the interface expressed as a decimal integer.
Values
1 — 65535
mtu
Syntax
Context
Description
mtu bytes
no mtu
config>router>ospf>area>interface
config>router>ospf3>area>interface
This command configures the OSPF packet size used on this interface. If this parameter is not configured
OSPF derives the MTU value from the MTU configured (default or explicitly) in the following contexts:
config>port>ethernet
config>port>sonet-sdh>path
config>port>tdm>t3-e3
config>port>tdm>t1-e1>channel-group
If this parameter is configured, the smaller value between the value configured here and the MTU configured (default or explicitly) in an above-mentioned context is used.
To determine the actual packet size add 14 bytes for an Ethernet packet and 18 bytes for a tagged Ethernet
packet to the size of the OSPF (IP) packet MTU configured in this command.
Use the no form of this command to revert to default.
Default
Parameters
no mtu — Uses the value derived from the MTU configured in the config>port context.
bytes — The MTU to be used by OSPF for this logical interface in bytes.
Values
512 — 9198
passive
Syntax
Context
Description
[no] passive
config>router>ospf>area>interface
config>router>ospf3>area>interface
This command adds the passive property to the OSPF interface where passive interfaces are advertised as
OSPF interfaces but do not run the OSPF protocol.
By default, only interface addresses that are configured for OSPF will be advertised as OSPF interfaces. The
passive parameter allows an interface to be advertised as an OSPF interface without running the OSPF
protocol.
While in passive mode, the interface will ignore ingress OSPF protocol packets and not transmit any OSPF
protocol packets.
Page 84
7210 SAS M, X OS Routing Protocols Guide
OSPF
The no form of the command removes the passive property from the OSPF interface.
Default
Service interfaces defined in config>router>service-prefix are passive.
All other interfaces are not passive.
priority
Syntax
Context
Description
priority number
no priority
config>router>ospf>area>interface
config>router>ospf3>area>interface
This command configures the priority of the OSPF interface that is used in an election of the designated
router on the subnet.
This parameter is only used if the interface is of type broadcast. The router with the highest priority interface
becomes the designated router. A router with priority 0 is not eligible to be Designated Router or Backup
Designated Router.
The no form of the command reverts the interface priority to the default value.
Default
Parameters
priority 1
number — The interface priority expressed as a decimal integer. A value of 0 indicates the router is not
eligible to be the Designated Router or Backup Designated Router on the interface subnet.
Values
0 — 255
retransmit-interval
Syntax
Context
Description
retransmit-interval seconds
no retransmit-interval
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
This command specifies the length of time, in seconds, that OSPF will wait before retransmitting an
unacknowledged link state advertisement (LSA) to an OSPF neighbor.
The value should be longer than the expected round trip delay between any two routers on the attached
network. Once the retransmit-interval expires and no acknowledgement has been received, the LSA will be
retransmitted.
The no form of this command reverts to the default interval.
Default
retransmit-interval 5
7210 SAS M, X OS Routing Protocols Guide
Page 85
Interface/Virtual Link Commands
Parameters
seconds — The retransmit interval in seconds expressed as a decimal integer.
Values
1 — 1800
transit-delay
Syntax
Context
Description
transit-delay seconds
no transit-delay
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
This command configures the estimated time, in seconds, that it takes to transmit a link state advertisement
(LSA) on the interface or virtual link.
The no form of this command reverts to the default delay time
Default
Parameters
transit-delay 1
seconds — The transit delay in seconds expressed as a decimal integer.
Values
1 — 1800
virtual-link
Syntax
Context
Description
[no] virtual-link router-id transit-area area-id
config>router>ospf>area
config>router>ospf3>area
This command configures a virtual link to connect area border routers to the backbone via a virtual link.
The backbone area (area 0.0.0.0) must be contiguous and all other areas must be connected to the backbone
area. If it is not practical to connect an area to the backbone (see area 0.0.0.2 in the picture below) then the
area border routers (routers 1 and 2 in the picture below) must be connected via a virtual link. The two area
border routers will form a point-to-point like adjacency across the transit area. (area 0.0.0.1 in the picture
below). A virtual link can only be configured while in the area 0.0.0.0 context.
The router-id specified in this command must be associated with the virtual neighbor. The transit area cannot
be a stub area or a Not So Stubby Area (NSSA).
The no form of the command deletes the virtual link. (Default: none specified)
Default
Parameters
No virtual link is defined.
router-id — The router ID of the virtual neighbor in IP address dotted decimal notation.
transit-area area-id — The area-id specified identifies the transit area that links the backbone area with the
area that has no physical connection with the backbone.
Page 86
7210 SAS M, X OS Routing Protocols Guide
OSPF
The OSPF backbone area, area 0.0.0.0, must be contiguous and all other areas must be connected to the
backbone area. The backbone distributes routing information between areas. If it is not practical to
connect an area to the backbone then the area border routers (such as routers Y and Z) must be
connected via a virtual link. The two area border routers form a point-to-point-like adjacency across the
transit area (see Area 0.0.0.4).
7210 SAS M, X OS Routing Protocols Guide
Page 87
Interface/Virtual Link Commands
Page 88
7210 SAS M, X OS Routing Protocols Guide
OSPF
Show Commands
ospf
Syntax
Context
Description
ospf
show>router
This command enables the context to display OSPF information.
area
Syntax
Context
area [area-id] [detail]
show>router>ospf
show>router>ospf3
Description
Displays configuration information about all areas or the specified area. When detail is specified operational
and statistical information will be displayed.
Parameters
area-id — The OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
detail — Displays detailed information on the area.
Output
OSPF Area Output — The following table describes the standard and detailed command output fields for
an OSPF area.
Label
Description
Area Id
A 32 bit integer uniquely identifying an area.
Type
NSSA — This area is configured as an NSSA area.
Standard — This area is configured as a standard area (not NSSA
or Stub).
Stub — This area is configured as a stub area.
SPF Runs
The number of times that the intra-area route table has been calculated
using this area’s link state database.
LSA Count
The total number of link-state advertisements in this area’s link state
database, excluding AS External LSA’s.
LSA Cksum Sum
The 32-bit unsigned sum of the link-state database advertisements LS
checksums contained in this area’s link state database. This checksum
excludes AS External LSAs (type-5).
No. of OSPF Areas
The number of areas configured on the router.
7210 SAS M, X OS Routing Protocols Guide
Page 89
Show Commands
Label
Description (Continued)
Virtual Links
The number of virtual links configured through this transit area.
Active IFs
The active number of interfaces configured in this area.
Area Bdr Rtrs
The total number of ABRs reachable within this area.
AS Bdr Rtrs
The total number of ASBRs reachable within this area.
Last SPF Run
The time when the last intra-area SPF was run on this area.
Router LSAs
The total number of router LSAs in this area.
Network LSAs
The total number of network LSAs in this area.
Summary LSAs
The summary of LSAs in this area.
Asbr-summ LSAs
The summary of ASBR LSAs in this area.
Nssa-ext LSAs
The total number of NSSA-EXT LSAs in this area.
Area opaque LSAs
The total number of opaque LSAs in this area.
Total Nbrs
The total number of neighbors in this area.
Total IFs
The total number of interfaces configured in this area.
Total LSAs
The sum of LSAs in this area excluding autonomous system external
LSAs.
Blackhole Range
False — No blackhole route is installed for aggregates configured
in this area.
True — A lowest priority blackhole route is installed for aggregates
configured in this area.
Sample Output
A:SR# show router ospf area detail
===============================================================================
OSPF Areas (Detailed)
===============================================================================
------------------------------------------------------------------------------Area Id: 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Type
: Standard
Virtual Links
: 0
Total Nbrs
: 2
Active IFs
: 3
Total IFs
: 3
Area Bdr Rtrs
: 0
AS Bdr Rtrs
: 0
SPF Runs
: 7
Last SPF Run
: 10/26/2006 10:09:18
Router LSAs
: 3
Network LSAs
: 3
Summary LSAs
: 0
Asbr-summ LSAs
: 0
Nssa ext LSAs
: 0
Area opaque LSAs : 3
Total LSAs
: 9
LSA Cksum Sum
: 0x28b62
Blackhole Range : True
Unknown LSAs
: 0
Page 90
7210 SAS M, X OS Routing Protocols Guide
OSPF
===============================================================================
*A:Bombadil# show router ospf area 0.0.0.0 detail
===============================================================================
OSPF Area (Detailed) : 0.0.0.0
===============================================================================
------------------------------------------------------------------------------Configuration
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Type
: Standard
------------------------------------------------------------------------------Statistics
------------------------------------------------------------------------------Virtual Links
: 0
Total Nbrs
: 2
Active IFs
: 3
Total IFs
: 3
Area Bdr Rtrs
: 0
AS Bdr Rtrs
: 0
SPF Runs
: 7
Last SPF Run
: 10/26/2006 10:09:18
Router LSAs
: 3
Network LSAs
: 3
Summary LSAs
: 0
Asbr-summ LSAs
: 0
Nssa ext LSAs
: 0
Area opaque LSAs : 3
Total LSAs
: 9
LSA Cksum Sum
: 0x28b62
Blackhole Range : True
Unknown LSAs
: 0
===============================================================================
*A:ALU_SIM11>show>router>ospf# area detail
===============================================================================
OSPF Areas (Detailed)
===============================================================================
------------------------------------------------------------------------------Area Id: 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Type
: Standard
Virtual Links
: 0
Total Nbrs
: 1
Active IFs
: 2
Total IFs
: 2
Area Bdr Rtrs
: 1
AS Bdr Rtrs
: 0
SPF Runs
: 5
Last SPF Run
: 07/06/2010 10:36:45
Router LSAs
: 2
Network LSAs
: 0
Summary LSAs
: 1
Asbr-summ LSAs
: 0
Nssa ext LSAs
: 0
Area opaque LSAs : 0
Total LSAs
: 3
LSA Cksum Sum
: 0x15668
Blackhole Range : True
Unknown LSAs
: 0
===============================================================================
Sample Output for OSPF3
*A:Dut-A# show router ospf3 area detail
===============================================================================
OSPF Areas (Detailed)
===============================================================================
------------------------------------------------------------------------------Area Id: 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Type
: Standard
Key Rollover Int.: 10
Virtual Links
: 0
Total Nbrs
: 2
Active IFs
: 3
Total IFs
: 3
7210 SAS M, X OS Routing Protocols Guide
Page 91
Show Commands
Area Bdr Rtrs
: 0
AS Bdr Rtrs
: 0
SPF Runs
: 8
Last SPF Run
: 10/09/2012 13:54:11
Router LSAs
: 3
Network LSAs
: 3
IE Pfx LSAs
: 0
IE Rtr LSAs
: 0
Nssa ext LSAs
: 0
IA Pfx LSAs
: 6
Total LSAs
: 12
LSA Cksum Sum
: 0x67bc8
Blackhole Range : True
Unknown LSAs
: 0
===============================================================================
*A:Dut-A# show router ospf3 area 0.0.0.0 detail
===============================================================================
OSPF Area (Detailed) : 0.0.0.0
===============================================================================
------------------------------------------------------------------------------Configuration
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Type
: Standard
Key Rollover Int.: 10
------------------------------------------------------------------------------Statistics
------------------------------------------------------------------------------Virtual Links
: 0
Total Nbrs
: 2
Active IFs
: 3
Total IFs
: 3
Area Bdr Rtrs
: 0
AS Bdr Rtrs
: 0
SPF Runs
: 8
Last SPF Run
: 10/09/2012 13:54:11
Router LSAs
: 3
Network LSAs
: 3
IE Pfx LSAs
: 0
IE Rtr LSAs
: 0
Nssa ext LSAs
: 0
IA Pfx LSAs
: 6
Total LSAs
: 12
LSA Cksum Sum
: 0x67bc8
Blackhole Range : True
Unknown LSAs
: 0
===============================================================================
*A:Dut-A#
database
Syntax
Context
Description
database [type {router | network | summary | asbr-summary | external | nssa | all}] [area
area-id] [adv-router router-id] [link-state-id] [detail]
show>router>ospf
show>router>ospf3
show>router>ospf3
This command displays information about the OSPF link state database (LSDB).
When no command line options are specified, the command displays brief output for all database entries
Parameters
type keyword — Specifies to filter the OSPF LSDB information based on the type specified by keyword.
type router — Display only router (Type 1) LSAs in the LSDB.
type network — Display only network (Type 2) LSAs in the LSDB.
type summary — Display only summary (Type 3) LSAs in the LSDB.
type asbr-summary — Display only ASBR summary (Type 4) LSAs in the LSDB.
Page 92
7210 SAS M, X OS Routing Protocols Guide
OSPF
type external — Display only AS external (Type 5) LSAs in the LSDB. External LSAs are maintained
globally and not per area. If the display of external links is requested, the area parameter, if present, is
ignored.
type nssa — Displays only NSSA area-specific AS external (Type 7) LSAs in the LSDB.
type all — Display all LSAs in the LSDB. The all keyword is intended to be used with either the area areaid or the adv-router router-id [link-state-id] parameters.
area area-id — Display LSDB information associated with the specified OSPF area-id.
adv-router router-id [link-state-id] — Display LSDB information associated with the specified advertising
router. To further narrow the number of items displayed, the link-state-id can optionally be specified.
detail — Displays detailed information on the LSDB entries.
Output
OSPF Database Ouput — The following table describes the standard and detailed command output
fields for an OSPF database.
Label
Description
Area Id
The OSPF area identifier.
Type
LSA Type
Router — LSA type of router (OSPF)
Network — LSA type of network (OSPF)
Summary — LSA type of summary (OSPF)
ASBR Summary — LSA type of ASBR summary (OSPF)
Nssa-ext — LSA area-specific, NSSA external (OSPF)
Area opaque — LSA type of area opaque (OSPF)
router — LSA type of router (OSPF3)
Network — LSA type of network (OSPF3)
IE Pfx — LSA type of IE Pfx (OSPF3)IE Rtr — LSA type of
IE Rtr (OSPF3)
IA Pfx — LSA type of IA Pfx (OSPF3)
Nssa-ext — NSSA area-specific AS external (OSPF3)
Link State Id
The link state Id is an LSA type specific field containing either a number to distinguish several LSAs from the same router, an interface ID,
or a router-id; it identifies the piece of the routing domain being
described by the advertisement.
Adv Rtr Id
Adv Router Id
The router identifier of the router advertising the LSA.
Age
The age of the link state advertisement in seconds.
7210 SAS M, X OS Routing Protocols Guide
Page 93
Show Commands
Label
Description (Continued)
Sequence
Sequence No
The signed 32-bit integer sequence number.
Cksum
Checksum
The 32-bit unsigned sum of the link-state advertisements' LS checksums.
No. of LSAs
The number of LSAs displayed.
Options
EA — External Attribute LSA Support
DC — Demand Circuit Support
R — If clear, a node can participates in OSPF topology distribution
without being used to forward transit traffic.
N — Type 7 LSA Support
MC — Multicast Support
E — External Routes Support
Prefix Options
P — Propagate NSSA LSA.
MC — Multicast support.
Flags
None — No flags set
V — The router is an endpoint for one or more fully adjacent Virtual
Links having the described area as the transit area
E — The router is an AS Boundary Router
B — The router is an Area Border Router
Link Count
The number of links advertised in the LSA.
Link Type (n)
The link type of the nth link in the LSA.
Network (n)
The network address of the nth link in the LSA.
Metric-0 (n)
The cost metric of the nth link in the LSA.
Sample Output
A:ALA-A# show router ospf database
===============================================================================
OSPF Link State Database (Type : All)
===============================================================================
Area Id
Type
Link State Id
Adv Rtr Id
Age Sequence
Cksum
------------------------------------------------------------------------------0.0.0.0
Router 180.0.0.2
180.0.0.2
1800 0x800000b6 0xf54
0.0.0.0
Router 180.0.0.5
180.0.0.5
1902 0x8000009d 0xcb7c
0.0.0.0
Router 180.0.0.8
180.0.0.8
1815 0x8000009a 0x529b
0.0.0.0
Router 180.0.0.9
180.0.0.9
1156 0x80000085 0xd00f
0.0.0.0
Router 180.0.0.10
180.0.0.10
533 0x8000009d 0x3f1f
0.0.0.0
Router 180.0.0.11
180.0.0.11
137 0x80000086 0xc58f
0.0.0.0
Router 180.0.0.12
180.0.0.12
918 0x8000009d 0x4cf3
Page 94
7210 SAS M, X OS Routing Protocols Guide
OSPF
0.0.0.0
Router 180.0.0.13
180.0.0.13
1401 0x800000a2 0x879c
0.0.0.0
Network 180.0.53.28
180.0.0.28
149 0x80000083 0xe5cd
0.0.0.0
Network 180.0.54.28
180.0.0.28
1259 0x80000083 0xdad7
0.0.0.0
Summary 180.0.0.15
180.0.0.10
378 0x80000084 0xeba1
0.0.0.0
Summary 180.0.0.15
180.0.0.12
73
0x80000084 0xdfab
0.0.0.0
Summary 180.0.0.18
180.0.0.10
1177 0x80000083 0xcfbb
0.0.0.1
Summary 180.100.25.4
180.0.0.12
208 0x80000091 0x3049
0.0.0.1
AS Summ 180.0.0.8
180.0.0.10
824 0x80000084 0x3d07
0.0.0.1
AS Summ 180.0.0.8
180.0.0.12
1183 0x80000095 0x4bdf
0.0.0.1
AS Summ 180.0.0.9
180.0.0.10
244 0x80000082 0x73cb
n/a
AS Ext 7.1.0.0
180.0.0.23
1312 0x80000083 0x45e7
n/a
AS Ext 7.2.0.0
180.0.0.23
997 0x80000082 0x45e6
n/a
AS Ext 10.20.0.0
180.0.0.23
238 0x80000081 0x2d81
...
------------------------------------------------------------------------------No. of LSAs: 339
===============================================================================
A:ALA-A#
A:ALA-A# show router ospf database detail
===============================================================================
OSPF Link State Database (Type : All) (Detailed)
------------------------------------------------------------------------------Router LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 180.0.0.2
Link State Id
: 180.0.0.2
LSA Type
: Router
Sequence No
: 0x800000b7
Checksum
: 0xd55
Age
: 155
Length
: 192
Options
: E
Flags
: None
Link Count
: 14
Link Type (1)
: Point To Point
Nbr Rtr Id (1)
: 180.0.0.13
I/F Address (1) : 180.0.22.2
No of TOS (1)
: 0
Metric-0 (1)
: 25
Link Type (2)
: Stub Network
Network (2)
: 180.0.22.0
Mask (2)
: 255.255.255.0
No of TOS (2)
: 0
Metric-0 (2)
: 25
Link Type (3)
: Point To Point
Nbr Rtr Id (3)
: 180.0.0.12
I/F Address (3) : 180.0.5.2
No of TOS (3)
: 0
Metric-0 (3)
: 25
Link Type (4)
: Stub Network
Network (4)
: 180.0.5.0
Mask (4)
: 255.255.255.0
No of TOS (4)
: 0
Metric-0 (4)
: 25
Link Type (5)
: Point To Point
Nbr Rtr Id (5)
: 180.0.0.8
I/F Address (5) : 180.0.13.2
No of TOS (5)
: 0
Metric-0 (5)
: 6
Link Type (6)
: Stub Network
Network (6)
: 180.0.13.0
Mask (6)
: 255.255.255.0
No of TOS (6)
: 0
Metric-0 (6)
: 6
Link Type (7)
: Point To Point
Nbr Rtr Id (7)
: 180.0.0.5
I/F Address (7) : 180.0.14.2
No of TOS (7)
: 0
Metric-0 (7)
: 6
Link Type (8)
: Stub Network
Network (8)
: 180.0.14.0
Mask (8)
: 255.255.255.0
No of TOS (8)
: 0
Metric-0 (8)
: 6
Link Type (9)
: Point To Point
Nbr Rtr Id (9)
: 180.0.0.11
I/F Address (9) : 180.0.17.2
No of TOS (9)
: 0
Metric-0 (9)
: 25
7210 SAS M, X OS Routing Protocols Guide
Page 95
Show Commands
Link Type (10)
: Stub Network
Network (10)
: 180.0.17.0
Mask (10)
: 255.255.255.0
No of TOS (10)
: 0
Metric-0 (10)
: 25
Link Type (11)
: Stub Network
Network (11)
: 180.0.0.2
Mask (11)
: 255.255.255.255
No of TOS (11)
: 0
Metric-0 (11)
: 1
Link Type (12)
: Stub Network
Network (12)
: 180.0.18.0
Mask (12)
: 255.255.255.0
No of TOS (12)
: 0
Metric-0 (12)
: 24
Link Type (13)
: Point To Point
Nbr Rtr Id (13) : 180.0.0.10
I/F Address (13) : 180.0.3.2
No of TOS (13)
: 0
Metric-0 (13)
: 25
Link Type (14)
: Stub Network
Network (14)
: 180.0.3.0
Mask (14)
: 255.255.255.0
No of TOS (14)
: 0
Metric-0 (14)
: 25
------------------------------------------------------------------------------AS Ext LSA for Network 180.0.0.14
------------------------------------------------------------------------------Area Id
: N/A
Adv Router Id
: 180.0.0.10
Link State Id
: 180.0.0.14
LSA Type
: AS Ext
Sequence No
: 0x80000083
Checksum
: 0xa659
Age
: 2033
Length
: 36
Options
: E
Network Mask
: 255.255.255.255
Fwding Address
: 180.1.6.15
Metric Type
: Type 2
Metric-0
: 4
Ext Route Tag
: 0
------------------------------------------------------------------------------...
A:ALA-A#
Sample Output for OSPF3
*A:Dut-A# show router ospf3 database
===============================================================================
OSPF Link State Database (Type : All)
===============================================================================
Type
Area Id
Link State Id
Adv Rtr Id
Age Sequence
Cksum
------------------------------------------------------------------------------Router 0.0.0.0
0.0.0.0
1.1.1.1
116 0x8000006c 0x555a
Router 0.0.0.0
0.0.0.0
3.3.3.3
78
0x80000003 0x3fd0
Router 0.0.0.0
0.0.0.0
6.6.6.6
115 0x80000004 0x6c83
Network 0.0.0.0
0.0.0.3
1.1.1.1
116 0x80000001 0xac65
Network 0.0.0.0
0.0.0.2
6.6.6.6
768 0x80000001 0x668c
Network 0.0.0.0
0.0.0.3
6.6.6.6
118 0x80000001 0xc029
IA Pfx 0.0.0.0
0.0.0.0
1.1.1.1
116 0x80000075 0x6885
IA Pfx 0.0.0.0
0.0.117.51
1.1.1.1
116 0x80000001 0xedf0
IA Pfx 0.0.0.0
0.0.0.0
3.3.3.3
78
0x80000003 0xb994
IA Pfx 0.0.0.0
0.0.0.0
6.6.6.6
115 0x80000009 0xc769
IA Pfx 0.0.0.0
0.0.117.50
6.6.6.6
769 0x80000001 0x3e7b
IA Pfx 0.0.0.0
0.0.117.51
6.6.6.6
118 0x80000002 0x9114
------------------------------------------------------------------------------No. of LSAs: 12
===============================================================================
*A:Dut-A#
Page 96
7210 SAS M, X OS Routing Protocols Guide
OSPF
*A:Dut-A# show router ospf3 database detail
===============================================================================
OSPF Link State Database (Type : All) (Detailed)
===============================================================================
------------------------------------------------------------------------------Router LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 1.1.1.1
Link State Id
: 0.0.0.0 (0)
LSA Type
: Router
Sequence No
: 0x8000006c
Checksum
: 0x555a
Age
: 147
Length
: 56
Options
: --R--EV6
Flags
:
Link Count
: 2
Link Type (1)
: Transit Network
DR Rtr ID (1)
: 6.6.6.6
I/F Index (1)
: 2
DR I/F Index (1) : 2
Metric (1)
: 100
Link Type (2)
: Transit Network
DR Rtr ID (2)
: 1.1.1.1
I/F Index (2)
: 3
DR I/F Index (2) : 3
Metric (2)
: 100
------------------------------------------------------------------------------Router LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 3.3.3.3
Link State Id
: 0.0.0.0 (0)
LSA Type
: Router
Sequence No
: 0x80000003
Checksum
: 0x3fd0
Age
: 109
Length
: 56
Options
: --R--EV6
Flags
:
Link Count
: 2
Link Type (1)
: Transit Network
DR Rtr ID (1)
: 1.1.1.1
I/F Index (1)
: 2
DR I/F Index (1) : 3
Metric (1)
: 100
Link Type (2)
: Transit Network
DR Rtr ID (2)
: 6.6.6.6
I/F Index (2)
: 3
DR I/F Index (2) : 3
Metric (2)
: 100
------------------------------------------------------------------------------Router LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 6.6.6.6
Link State Id
: 0.0.0.0 (0)
LSA Type
: Router
Sequence No
: 0x80000004
Checksum
: 0x6c83
Age
: 146
Length
: 56
Options
: --R--EV6
Flags
:
Link Count
: 2
Link Type (1)
: Transit Network
DR Rtr ID (1)
: 6.6.6.6
I/F Index (1)
: 2
DR I/F Index (1) : 2
Metric (1)
: 100
Link Type (2)
: Transit Network
DR Rtr ID (2)
: 6.6.6.6
I/F Index (2)
: 3
DR I/F Index (2) : 3
Metric (2)
: 100
------------------------------------------------------------------------------Network LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 1.1.1.1
Link State Id
: 0.0.0.3 (3)
LSA Type
: Network
7210 SAS M, X OS Routing Protocols Guide
Page 97
Show Commands
Sequence No
: 0x80000001
Checksum
: 0xac65
Age
: 148
Length
: 32
Options
: --R--EV6
No of Adj Rtrs
: 2
Router Id (1)
: 1.1.1.1
Router Id (2)
: 3.3.3.3
------------------------------------------------------------------------------Network LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 6.6.6.6
Link State Id
: 0.0.0.2 (2)
LSA Type
: Network
Sequence No
: 0x80000001
Checksum
: 0x668c
Age
: 801
Length
: 32
Options
: --R--EV6
No of Adj Rtrs
: 2
Router Id (1)
: 6.6.6.6
Router Id (2)
: 1.1.1.1
------------------------------------------------------------------------------Network LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 6.6.6.6
Link State Id
: 0.0.0.3 (3)
LSA Type
: Network
Sequence No
: 0x80000001
Checksum
: 0xc029
Age
: 150
Length
: 32
Options
: --R--EV6
No of Adj Rtrs
: 2
Router Id (1)
: 6.6.6.6
Router Id (2)
: 3.3.3.3
------------------------------------------------------------------------------IA Pfx LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 1.1.1.1
Link State Id
: 0.0.0.0 (0)
LSA Type
: IA Pfx
Sequence No
: 0x80000075
Checksum
: 0x6885
Age
: 148
Length
: 52
Ref Ls Type
: 2001
Ref Ls Id
: 0
Ref Adv Rtr
: 1.1.1.1
No of Pfxs
: 1
Prefix (1)
: 1001::1/128
Options (1)
: LA
Metric (1)
: 0
------------------------------------------------------------------------------IA Pfx LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 1.1.1.1
Link State Id
: 0.0.117.51 (30003)
LSA Type
: IA Pfx
Sequence No
: 0x80000001
Checksum
: 0xedf0
Age
: 148
Length
: 44
Ref Ls Type
: 2002
Ref Ls Id
: 3
Ref Adv Rtr
: 1.1.1.1
No of Pfxs
: 1
Prefix (1)
: 2013::/64
Options (1)
:
Metric (1)
: 0
------------------------------------------------------------------------------IA Pfx LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 3.3.3.3
Link State Id
: 0.0.0.0 (0)
LSA Type
: IA Pfx
Sequence No
: 0x80000003
Checksum
: 0xb994
Age
: 110
Length
: 52
Ref Ls Type
: 2001
Ref Ls Id
: 0
Ref Adv Rtr
: 3.3.3.3
No of Pfxs
: 1
Prefix (1)
: 1001::3/128
Page 98
7210 SAS M, X OS Routing Protocols Guide
OSPF
Options (1)
: LA
Metric (1)
: 0
------------------------------------------------------------------------------IA Pfx LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 6.6.6.6
Link State Id
: 0.0.0.0 (0)
LSA Type
: IA Pfx
Sequence No
: 0x80000009
Checksum
: 0xc769
Age
: 148
Length
: 52
Ref Ls Type
: 2001
Ref Ls Id
: 0
Ref Adv Rtr
: 6.6.6.6
No of Pfxs
: 1
Prefix (1)
: 1001::2/128
Options (1)
: LA
Metric (1)
: 0
------------------------------------------------------------------------------IA Pfx LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 6.6.6.6
Link State Id
: 0.0.117.50 (30002)
LSA Type
: IA Pfx
Sequence No
: 0x80000001
Checksum
: 0x3e7b
Age
: 801
Length
: 44
Ref Ls Type
: 2002
Ref Ls Id
: 2
Ref Adv Rtr
: 6.6.6.6
No of Pfxs
: 1
Prefix (1)
: 2012::/64
Options (1)
:
Metric (1)
: 0
------------------------------------------------------------------------------IA Pfx LSA for Area 0.0.0.0
------------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 6.6.6.6
Link State Id
: 0.0.117.51 (30003)
LSA Type
: IA Pfx
Sequence No
: 0x80000002
Checksum
: 0x9114
Age
: 151
Length
: 44
Ref Ls Type
: 2002
Ref Ls Id
: 3
Ref Adv Rtr
: 6.6.6.6
No of Pfxs
: 1
Prefix (1)
: 2023::/64
Options (1)
:
Metric (1)
: 0
===============================================================================
*A:Dut-A#
interface
Syntax
Context
Description
interface [ip-int-name|ip-address|ipv6-address] [detail]
interface [area area-id] [detail]
interface [ip-int-name|ip-address|ipv6-address database [detail]]
show>router>ospf
show>router>ospf3
Displays the details of the OSPF interface, this interface can be identified by ip-address or ip interface name.
When neither is specified, all in-service interfaces are displayed.
The detail option produces a great amount of data. It is recommended to detail only when requesting a
specific interface.
7210 SAS M, X OS Routing Protocols Guide
Page 99
Show Commands
Parameters
ip-addr — Display only the interface identified by this IP address.
ip-int-name — Display only the interface identified by this interface name.
ipv6-address —
area area-id — Display all interfaces configured in this area.
database — — Keyword to display database information.
detail — Displays detailed information on the interface.
Output
Standard OSPF Interface Output — The following table describes the standard command output fields
for an OSPF interface.
Label
Description
If Name
The interface name.
Area Id
A 32-bit integer uniquely identifying the area to which this interface is
connected. Area ID 0.0.0.0 is used for the OSPF backbone.
D Rtr Id
The IP Interface address of the router identified as the Designated
Router for the network in which this interface is configured. Set to
0.0.0.0 if there is no Designated router.
BD Rtr Id
The IP Interface address of the router identified as the Backup Designated Router for the network in which this interface is configured. Set
to 0.0.0.0 if there is no Backup Designated router.
Adm
Dn — OSPF on this interface is administratively shut down.
Up — OSPF on this interface is administratively enabled.
Opr
Down — This is the initial interface state. In this state, the lower-level
protocols have indicated that the interface is unusable.
Wait — The router is trying to determine the identity of the (Backup)
Designated router for the network.
PToP — The interface is operational, and connects either to a physical point-to-point network or to a virtual link.
DR — This router is the Designated Router for this network.
BDR — This router is the backup Designated Router for this network.
ODR — The interface is operational and part of a broadcast or NBMA
network on which another router has been selected to be the Designated Router.
Page 100
No. of OSPF Interfaces
The number of interfaces listed.
Bfd Enabled
Indicates if BFD is enabled.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Sample Output
A:SetupCLI# show router ospf interface detail
===============================================================================
OSPF Interfaces (Detailed)
------------------------------------------------------------------------------Interface : system
------------------------------------------------------------------------------IP Address
: 9.1.255.255
Area Id
: 0.0.0.0
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: True
Cfg MTU
: 0
Admin Status
: Enabled
Oper State
: Designated Rtr
Designated Rtr
: 2.2.2.2
Backup Desig Rtr : 0.0.0.0
IF Type
: Broadcast
Network Type
: Transit
Oper MTU
: 1500
Last Enabled
: 05/14/2006 09:16:26
Oper Metric
: 0
Nbr Count
: 0
If Events
: 5
Tot Rx Packets
: 0
Tot Tx Packets
: 0
Rx Hellos
: 0
Tx Hellos
: 0
Rx DBDs
: 0
Tx DBDs
: 0
Rx LSRs
: 0
Tx LSRs
: 0
Rx LSUs
: 0
Tx LSUs
: 0
Rx LS Acks
: 0
Tx LS Acks
: 0
Retransmits
: 0
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
------------------------------------------------------------------------------Interface : sender
------------------------------------------------------------------------------IP Address
: 11.1.1.1
Area Id
: 0.0.0.0
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
===============================================================================
A:SetupCLI#
*A:ALU_SIM11>show>router>ospf# interface 6.6.6.2 detail
===============================================================================
OSPF Interface (Detailed) : 6.6.6.2
===============================================================================
------------------------------------------------------------------------------Configuration
------------------------------------------------------------------------------IP Address
: 6.6.6.2
Area Id
: 0.0.0.0
Priority
: 1
7210 SAS M, X OS Routing Protocols Guide
Page 101
Show Commands
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
------------------------------------------------------------------------------State
------------------------------------------------------------------------------Admin Status
: Enabled
Oper State
: Point To Point
Designated Rtr
: 0.0.0.0
Backup Desig Rtr : 0.0.0.0
IF Type
: Point To Point
Network Type
: Transit
Oper MTU
: 1564
Last Enabled
: 07/06/2010 10:34:11
Oper Metric
: 100
Bfd Enabled
: No
Te Metric
: 100
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
------------------------------------------------------------------------------Statistics
------------------------------------------------------------------------------Nbr Count
: 1
If Events
: 7
Tot Rx Packets
: 353
Tot Tx Packets
: 348
Rx Hellos
: 314
Tx Hellos
: 309
Rx DBDs
: 31
Tx DBDs
: 30
Rx LSRs
: 1
Tx LSRs
: 1
Rx LSUs
: 4
Tx LSUs
: 4
Rx LS Acks
: 3
Tx LS Acks
: 4
Retransmits
: 1
Discards
: 6
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 6
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
===============================================================================
*A:7210-SAS>show>router>ospf#
interface C_Port detail
===============================================================================
OSPF Interface (Detailed) : C_Port
===============================================================================
------------------------------------------------------------------------------Configuration
------------------------------------------------------------------------------IP Address
: 26.26.26.2
Area Id
: 0.0.0.2
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
------------------------------------------------------------------------------State
------------------------------------------------------------------------------Admin Status
: Enabled
Oper State
: Point To Point
Designated Rtr
: 0.0.0.0
Backup Desig Rtr : 0.0.0.0
IF Type
: Point To Point
Network Type
: Transit
Page 102
7210 SAS M, X OS Routing Protocols Guide
OSPF
Oper MTU
: 9198
Last Enabled
: 12/14/2010 09:48:30
Oper Metric
: 100
Bfd Enabled
: No
Te Metric
: 100
Te State
: Up
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
------------------------------------------------------------------------------Statistics
------------------------------------------------------------------------------Nbr Count
: 1
If Events
: 1
Tot Rx Packets
: 22391
Tot Tx Packets
: 22273
Rx Hellos
: 8641
Tx Hellos
: 8640
Rx DBDs
: 20
Tx DBDs
: 19
Rx LSRs
: 0
Tx LSRs
: 0
Rx LSUs
: 13531
Tx LSUs
: 13611
Rx LS Acks
: 199
Tx LS Acks
: 3
Retransmits
: 26
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
===============================================================================
*A:7210-SAS>show>router>ospf#
Sample Output for OSPF3
*A:Dut-A# show router ospf3 interface detail
===============================================================================
OSPF Interfaces (Detailed)
===============================================================================
------------------------------------------------------------------------------Interface : system
------------------------------------------------------------------------------IP Address
: 1001::1
Area Id
: 0.0.0.0
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: True
Cfg MTU
: 0
IPsec InStatSA
:
IPsec OutStatSA :
IPsec InStatSATmp:
Admin Status
: Enabled
Oper State
: Designated Rtr
Designated Rtr
: 1.1.1.1
Backup Desig Rtr : 0.0.0.0
IF Type
: Broadcast
Network Type
: Stub
Oper MTU
: 1500
Last Enabled
: 10/09/2012 13:41:23
Oper Metric
: 0
Bfd Enabled
: No
Te Metric
: 0
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 0
If Events
: 2
Tot Rx Packets
: 0
Tot Tx Packets
: 0
Rx Hellos
: 0
Tx Hellos
: 0
7210 SAS M, X OS Routing Protocols Guide
Page 103
Show Commands
Rx DBDs
Rx LSRs
Rx LSUs
Rx LS Acks
Retransmits
Bad Networks
Bad Areas
Bad Auth Types
Bad Neighbors
Bad Lengths
Bad Dead Int.
Bad Versions
LSA Count
:
:
:
:
:
:
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
0
0
0
0
Tx DBDs
Tx LSRs
Tx LSUs
Tx LS Acks
Discards
Bad Virt Links
Bad Dest Addrs
Auth Failures
Bad Pkt Types
Bad Hello Int.
Bad Options
Bad Checksums
LSA Checksum
:
:
:
:
:
:
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
0
0
0
0x0
------------------------------------------------------------------------------Interface : to_b
------------------------------------------------------------------------------IP Address
: FE80::8E90:D3FF:FEBE:8F5A-"to_b"
Area Id
: 0.0.0.0
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
IPsec InStatSA
:
IPsec OutStatSA :
IPsec InStatSATmp:
Admin Status
: Enabled
Oper State
: Backup Desig Rtr
Designated Rtr
: 6.6.6.6
Backup Desig Rtr : 1.1.1.1
IF Type
: Broadcast
Network Type
: Transit
Oper MTU
: 9198
Last Enabled
: 10/09/2012 13:42:16
Oper Metric
: 100
Bfd Enabled
: No
Te Metric
: 100
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 1
If Events
: 4
Tot Rx Packets
: 449
Tot Tx Packets
: 339
Rx Hellos
: 96
Tx Hellos
: 96
Rx DBDs
: 5
Tx DBDs
: 3
Rx LSRs
: 1
Tx LSRs
: 1
Rx LSUs
: 235
Tx LSUs
: 230
Rx LS Acks
: 112
Tx LS Acks
: 9
Retransmits
: 1
Discards
: 1
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 2
LSA Checksum
: 0x16aa9
------------------------------------------------------------------------------Interface : to_c
------------------------------------------------------------------------------IP Address
: FE80::8E90:D3FF:FEBE:8F5A-"to_c"
Area Id
: 0.0.0.0
Priority
: 1
Page 104
7210 SAS M, X OS Routing Protocols Guide
OSPF
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
IPsec InStatSA
:
IPsec OutStatSA :
IPsec InStatSATmp:
Admin Status
: Enabled
Oper State
: Designated Rtr
Designated Rtr
: 1.1.1.1
Backup Desig Rtr : 3.3.3.3
IF Type
: Broadcast
Network Type
: Transit
Oper MTU
: 9198
Last Enabled
: 10/09/2012 13:42:14
Oper Metric
: 100
Bfd Enabled
: No
Te Metric
: 100
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 1
If Events
: 77
Tot Rx Packets
: 117
Tot Tx Packets
: 118
Rx Hellos
: 97
Tx Hellos
: 97
Rx DBDs
: 2
Tx DBDs
: 3
Rx LSRs
: 1
Tx LSRs
: 1
Rx LSUs
: 13
Tx LSUs
: 10
Rx LS Acks
: 4
Tx LS Acks
: 7
Retransmits
: 0
Discards
: 75
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 2
LSA Checksum
: 0x17644
===============================================================================
*A:Dut-A#
Detailed OSPF Interface Output — The following table describes the detailed command output fields
for an OSPF interface.
Label
Description
Interface
The IP address of this OSPF interface.
IP Address
The IP address and mask of this OSPF interface.
Interface Name
The interface name.
Area Id
A 32-bit integer uniquely identifying the area to which this interface is
connected. Area ID 0.0.0.0 is used for the OSPF backbone.
Priority
The priority of this interface. Used in multi-access networks, this field
is used in the designated router election algorithm.
Hello Intrvl
The length of time, in seconds, between the Hello packets that the
router sends on the interface. This value must be the same for all routers attached to a common network.
7210 SAS M, X OS Routing Protocols Guide
Page 105
Show Commands
Label
Description (Continued)
Rtr Dead Intrvl
The number of seconds that a router's Hello packets have not been seen
before it's neighbors declare the router down. This should be some
multiple of the Hello interval. This value must be the same for all routers attached to a common network.
Retrans Intrvl
The number of seconds between link-state advertisement retransmissions, for adjacencies belonging to this interface. This value is also
used when retransmitting database description and link-state request
packets.
Poll Intrvl
The larger time interval, in seconds, between the Hello packets sent to
an inactive non-broadcast multi-access neighbor.
Metric
The metric to be advertised for this interface.
Advert Subnet
False — When a point-to-point interface is configured as false, then
the subnet is not advertised and the endpoints are advertised as host
routes.
True — When a point-to-point interface is configured to true, then
the subnet is advertised.
Transit Delay
The estimated number of seconds it takes to transmit a link state update
packet over this interface.
Auth Type
Identifies the authentication procedure to be used for the packet.
None — Routing exchanges over the network/subnet are not authenticated.
Simple — A 64-bit field is configured on a per-network basis. All
packets sent on a particular network must have this configured value in
their OSPF header 64-bit authentication field. This essentially serves
as a “clear” 64-bit password.
MD5 — A shared secret key is configured in all routers attached to a
common network/subnet. For each OSPF protocol packet, the key is
used to generate/verify a “message digest” that is appended to the end
of the OSPF packet.
Passive
False — This interfaces operates as a normal OSPF interface with
regard to adjacency forming and network/link behavior.
True — no OSPF HELLOs will be sent out on this interface and the
router advertises this interface as a stub network/link in its router
LSAs.
MTU
Page 106
The desired size of the largest packet which can be sent/received on
this OSPF interface, specified in octets. This size DOES include the
underlying IP header length, but not the underlying layer headers/trailers.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Label
Admin Status
Description (Continued)
Disabled — OSPF on this interface is administratively shut down.
Enabled — OSPF on this interface is administratively enabled.
Oper State
Down — This is the initial interface state. In this state, the lower-level
protocols have indicated that the interface is unusable.
Waiting — The router is trying to determine the identity of the
(Backup) Designated router for the network.
Point To Point — The interface is operational, and connects
either to a physical point-to-point network or to a virtual link.
Designated Rtr — This router is the Designated Router for this
network.
Other Desig Rtr — The interface is operational and part of a
broadcast or NBMA network on which another router has been
selected to be the Designated Router.
Backup Desig Rtr — This router is the Backup Designated
Router for this network.
DR-Id
The IP Interface address of the router identified as the Designated
Router for the network in which this interface is configured. Set to
0.0.0.0 if there is no Designated router
BDR-Id
The IP Interface address of the router identified as the Backup Designated Router for the network in which this interface is configured. Set
to 0.0.0.0 if there is no Backup Designated router.
IF Type
Broadcast — LANs, such as Ethernet.
NBMA — X.25 and similar technologies.
Point-To-Point — Links that are definitively point to point.
Network Type
Stub — OPSF has not established a neighbor relationship with any
other OSPF router on this network as such only traffic sourced or destined to this network will be routed to this network.
Transit — OPSF has established at least one neighbor relationship
with any other OSPF router on this network as such traffic en route to
other networks may be routed via this network.
Oper MTU
The operational size of the largest packet which can be sent/received
on this OSPF interface, specified in octets. This size DOES include the
underlying IP header length, but not the underlying layer headers/trailers.
Last Enabled
The time that this interface was last enabled to run OSPF on this interface.
7210 SAS M, X OS Routing Protocols Guide
Page 107
Show Commands
Label
Page 108
Description (Continued)
Nbr Count
The number of OSPF neighbors on the network for this interface.
If Events
The number of times this OSPF interface has changed its state, or an
error has occurred since this interface was last enabled.
Tot Rx Packets
The total number of OSPF packets received on this interface since this
interface was last enabled.
Tot Tx Packets
The total number of OSPF packets transmitted on this interface since
this interface was last enabled.
Rx Hellos
The total number of OSPF Hello packets received on this interface
since this interface was last enabled.
Tx Hellos
The total number of OSPF Hello packets transmitted on this interface
since this interface was last enabled.
Rx DBDs
The total number of OSPF database description packets received on
this interface since this interface was last enabled.
Tx DBDs
The total number of OSPF database description packets transmitted on
this interface since this interface was last enabled.
Rx LSRs
The total number of Link State Requests (LSRs) received on this interface since this interface was last enabled.
Tx LSRs
The total number of Link State Requests (LSRs) transmitted on this
interface since this interface was last enabled.
Rx LSUs
The total number of Link State Updates (LSUs) received on this interface since this interface was last enabled.
Tx LSUs
The total number of Link State Updates (LSUs) transmitted on this
interface since this interface was last enabled.
Rx LS Acks
The total number of Link State Acknowledgements received on this
interface since this interface was last enabled.
Tx LS Acks
The total number of Link State Acknowledgements transmitted on this
interface since this interface was last enabled.
Retransmits
The total number of OSPF Retransmits sent on this interface since this
interface was last enabled.
Discards
The total number of OSPF packets discarded on this interface since
this interface was last enabled.
Bad Networks
The total number of OSPF packets received with invalid network or
mask since this interface was last enabled.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Label
Description (Continued)
Bad Virt Links
The total number of OSPF packets received on this interface that are
destined to a virtual link that does not exist since this interface was last
enabled.
Bad Areas
The total number of OSPF packets received with an area mismatch
since this interface was last enabled.
Bad Dest Addrs
The total number of OSPF packets received with the incorrect IP destination address since this interface was last enabled.
Bad Auth Types
The total number of OSPF packets received with an invalid authorization type since this interface was last enabled.
Auth Failures
The total number of OSPF packets received with an invalid authorization key since this interface was last enabled.
Bad Neighbors
The total number of OSPF packets received where the neighbor information does not match the information this router has for the neighbor
since this interface was last enabled.
Bad Pkt Types
The total number of OSPF packets received with an invalid OSPF
packet type since this interface was last enabled
Bad Lengths
The total number of OSPF packets received on this interface with a
total length not equal to the length given in the packet itself since this
interface was last enabled.
Bad Hello int.
The total number of OSPF packets received where the hello interval
given in packet was not equal to that configured on this interface since
this interface was last enabled.
Bad Dead Int.
The total number of OSPF packets received where the dead interval
given in the packet was not equal to that configured on this interface
since this interface was last enabled.
Bad Options
The total number of OSPF packets received with an option that does
not match those configured for this interface or area since this interface
was last enabled.
Bad Versions
The total number of OSPF packets received with bad OSPF version
numbers since this interface was last enabled.
Te Metric
Indicates the TE metric configured for this interface. This metric is
flooded out in the TE metric sub-tlv in the OSPF TE LSAs. Depending
on the configuration, either the TE metric value or the native OSPF
metric value is used in CSPF computations.
Te State
Indicates the MPLS interface TE status from OSPF standpoint.
Admin Groups
Indicates the bit-map inherited from MPLS interface that identifies the
admin groups to which this interface belongs.
7210 SAS M, X OS Routing Protocols Guide
Page 109
Show Commands
Sample Output
*A:JC-NodeA# show router ospf interface area detail
===============================================================================
OSPF Interfaces in Area (Detailed) : 1
===============================================================================
Interface : ip-10.10.1.1
------------------------------------------------------------------------------IP Address
: 10.10.1.1
Area Id
: 0.0.0.1
Priority
: 1
Hello Intrvl
: 5 sec
Rtr Dead Intrvl : 15 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
Admin Status
: Enabled
Oper State
: Designated Rtr
Designated Rtr
: 10.20.1.1
Backup Desig Rtr : 0.0.0.0
IF Type
: Broadcast
Network Type
: Transit
Oper MTU
: 1500
Last Enabled
: 04/11/2007 16:06:27
Oper Metric
: 1000
Nbr Count
: 0
If Events
: 5
Tot Rx Packets
: 0
Tot Tx Packets
: 1116
Rx Hellos
: 0
Tx Hellos
: 1116
Rx DBDs
: 0
Tx DBDs
: 0
Rx LSRs
: 0
Tx LSRs
: 0
Rx LSUs
: 0
Tx LSUs
: 0
Rx LS Acks
: 0
Tx LS Acks
: 0
Retransmits
: 0
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
TE Metric
: 678
===============================================================================
*A:JC-NodeA#
*A:7210-SAS>show>router>ospf# interface detail
===============================================================================
OSPF Interfaces (Detailed)
===============================================================================
------------------------------------------------------------------------------Interface : system
------------------------------------------------------------------------------IP Address
: 1.1.1.4
Area Id
: 0.0.0.2
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: True
Cfg MTU
: 0
Admin Status
: Enabled
Oper State
: Point To Point
Page 110
7210 SAS M, X OS Routing Protocols Guide
OSPF
Designated Rtr
: 0.0.0.0
Backup Desig Rtr : 0.0.0.0
IF Type
: Point To Point
Network Type
: Stub
Oper MTU
: 1500
Last Enabled
: 12/14/2010 09:47:33
Oper Metric
: 0
Bfd Enabled
: No
Te Metric
: 0
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 0
If Events
: 1
Tot Rx Packets
: 0
Tot Tx Packets
: 0
Rx Hellos
: 0
Tx Hellos
: 0
Rx DBDs
: 0
Tx DBDs
: 0
Rx LSRs
: 0
Tx LSRs
: 0
Rx LSUs
: 0
Tx LSUs
: 0
Rx LS Acks
: 0
Tx LS Acks
: 0
Retransmits
: 0
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
------------------------------------------------------------------------------Interface : F_Port
------------------------------------------------------------------------------IP Address
: 22.1.1.2
Area Id
: 0.0.0.2
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
Admin Status
: Enabled
Oper State
: Point To Point
Designated Rtr
: 0.0.0.0
Backup Desig Rtr : 0.0.0.0
IF Type
: Point To Point
Network Type
: Transit
Oper MTU
: 9198
Last Enabled
: 12/14/2010 09:48:07
Oper Metric
: 100
Bfd Enabled
: Yes
Te Metric
: 100
Te State
: Up
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 1
If Events
: 1
Tot Rx Packets
: 21739
Tot Tx Packets
: 20709
Rx Hellos
: 8630
Tx Hellos
: 8629
Rx DBDs
: 19
Tx DBDs
: 20
Rx LSRs
: 0
Tx LSRs
: 11
Rx LSUs
: 12782
Tx LSUs
: 1872
Rx LS Acks
: 308
Tx LS Acks
: 10177
Retransmits
: 13
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
7210 SAS M, X OS Routing Protocols Guide
Page 111
Show Commands
------------------------------------------------------------------------------Interface : F_Lag
------------------------------------------------------------------------------IP Address
: 23.1.1.2
Area Id
: 0.0.0.2
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
Admin Status
: Enabled
Oper State
: Point To Point
Designated Rtr
: 0.0.0.0
Backup Desig Rtr : 0.0.0.0
IF Type
: Point To Point
Network Type
: Transit
Oper MTU
: 9198
Last Enabled
: 12/14/2010 09:48:09
Oper Metric
: 50
Bfd Enabled
: Yes
Te Metric
: 50
Te State
: Up
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 1
If Events
: 1
Tot Rx Packets
: 21885
Tot Tx Packets
: 22347
Rx Hellos
: 8629
Tx Hellos
: 8634
Rx DBDs
: 19
Tx DBDs
: 20
Rx LSRs
: 0
Tx LSRs
: 5
Rx LSUs
: 13221
Tx LSUs
: 13152
Rx LS Acks
: 16
Tx LS Acks
: 536
Retransmits
: 16
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
------------------------------------------------------------------------------Interface : C_Lag
------------------------------------------------------------------------------IP Address
: 25.1.1.1
Area Id
: 0.0.0.2
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
Admin Status
: Enabled
Oper State
: Point To Point
Designated Rtr
: 0.0.0.0
Backup Desig Rtr : 0.0.0.0
IF Type
: Point To Point
Network Type
: Transit
Oper MTU
: 9198
Last Enabled
: 12/14/2010 09:48:33
Oper Metric
: 50
Bfd Enabled
: Yes
Te Metric
: 50
Te State
: Up
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 1
If Events
: 1
Tot Rx Packets
: 22578
Tot Tx Packets
: 21802
Rx Hellos
: 8628
Tx Hellos
: 8634
Rx DBDs
: 20
Tx DBDs
: 19
Rx LSRs
: 12
Tx LSRs
: 1
Page 112
7210 SAS M, X OS Routing Protocols Guide
OSPF
Rx LSUs
: 13883
Tx LSUs
: 12831
Rx LS Acks
: 35
Tx LS Acks
: 317
Retransmits
: 23
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
------------------------------------------------------------------------------Interface : C_Port
------------------------------------------------------------------------------IP Address
: 26.26.26.2
Area Id
: 0.0.0.2
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
Admin Status
: Enabled
Oper State
: Point To Point
Designated Rtr
: 0.0.0.0
Backup Desig Rtr : 0.0.0.0
IF Type
: Point To Point
Network Type
: Transit
Oper MTU
: 9198
Last Enabled
: 12/14/2010 09:48:30
Oper Metric
: 100
Bfd Enabled
: No
Te Metric
: 100
Te State
: Up
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 1
If Events
: 1
Tot Rx Packets
: 22380
Tot Tx Packets
: 22262
Rx Hellos
: 8632
Tx Hellos
: 8631
Rx DBDs
: 20
Tx DBDs
: 19
Rx LSRs
: 0
Tx LSRs
: 0
Rx LSUs
: 13531
Tx LSUs
: 13609
Rx LS Acks
: 197
Tx LS Acks
: 3
Retransmits
: 26
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 0
LSA Checksum
: 0x0
===============================================================================
Sample Output for OSPF3
A:Dut-A# show router ospf3 interface area 0 detail
===============================================================================
OSPF Interfaces in Area (Detailed) : 0
===============================================================================
------------------------------------------------------------------------------Interface : system
-------------------------------------------------------------------------------
7210 SAS M, X OS Routing Protocols Guide
Page 113
Show Commands
IP Address
:
Area Id
:
Hello Intrvl
:
Retrans Intrvl
:
Cfg Metric
:
Transit Delay
:
Passive
:
IPsec InStatSA
:
IPsec InStatSATmp:
Admin Status
:
Designated Rtr
:
IF Type
:
Oper MTU
:
Oper Metric
:
Te Metric
:
Admin Groups
:
Ldp Sync
:
Ldp Timer State :
Nbr Count
:
Tot Rx Packets
:
Rx Hellos
:
Rx DBDs
:
Rx LSRs
:
Rx LSUs
:
Rx LS Acks
:
Retransmits
:
Bad Networks
:
Bad Areas
:
Bad Auth Types
:
Bad Neighbors
:
Bad Lengths
:
Bad Dead Int.
:
Bad Versions
:
LSA Count
:
1001::1
0.0.0.0
10 sec
5 sec
0
1
True
Enabled
1.1.1.1
Broadcast
1500
0
0
None
outOfService
Disabled
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Priority
Rtr Dead Intrvl
Poll Intrvl
Advert Subnet
Auth Type
Cfg MTU
IPsec OutStatSA
:
:
:
:
:
:
:
1
40 sec
120 sec
True
None
0
Oper State
: Designated Rtr
Backup Desig Rtr : 0.0.0.0
Network Type
: Stub
Last Enabled
: 10/09/2012 13:41:23
Bfd Enabled
: No
Te State
: Down
Ldp Sync Wait
Ldp Tm Left
If Events
Tot Tx Packets
Tx Hellos
Tx DBDs
Tx LSRs
Tx LSUs
Tx LS Acks
Discards
Bad Virt Links
Bad Dest Addrs
Auth Failures
Bad Pkt Types
Bad Hello Int.
Bad Options
Bad Checksums
LSA Checksum
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Disabled
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0x0
------------------------------------------------------------------------------Interface : to_b
------------------------------------------------------------------------------IP Address
: FE80::8E90:D3FF:FEBE:8F5A-"to_b"
Area Id
: 0.0.0.0
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
IPsec InStatSA
:
IPsec OutStatSA :
IPsec InStatSATmp:
Admin Status
: Enabled
Oper State
: Backup Desig Rtr
Designated Rtr
: 6.6.6.6
Backup Desig Rtr : 1.1.1.1
IF Type
: Broadcast
Network Type
: Transit
Oper MTU
: 9198
Last Enabled
: 10/09/2012 13:42:16
Oper Metric
: 100
Bfd Enabled
: No
Te Metric
: 100
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 1
If Events
: 4
Tot Rx Packets
: 456
Tot Tx Packets
: 346
Page 114
7210 SAS M, X OS Routing Protocols Guide
OSPF
Rx Hellos
Rx DBDs
Rx LSRs
Rx LSUs
Rx LS Acks
Retransmits
Bad Networks
Bad Areas
Bad Auth Types
Bad Neighbors
Bad Lengths
Bad Dead Int.
Bad Versions
LSA Count
:
:
:
:
:
:
:
:
:
:
:
:
:
:
103
5
1
235
112
1
0
0
0
0
0
0
0
2
Tx Hellos
Tx DBDs
Tx LSRs
Tx LSUs
Tx LS Acks
Discards
Bad Virt Links
Bad Dest Addrs
Auth Failures
Bad Pkt Types
Bad Hello Int.
Bad Options
Bad Checksums
LSA Checksum
:
:
:
:
:
:
:
:
:
:
:
:
:
:
103
3
1
230
9
1
0
0
0
0
0
0
0
0x16aa9
------------------------------------------------------------------------------Interface : to_c
------------------------------------------------------------------------------IP Address
: FE80::8E90:D3FF:FEBE:8F5A-"to_c"
Area Id
: 0.0.0.0
Priority
: 1
Hello Intrvl
: 10 sec
Rtr Dead Intrvl : 40 sec
Retrans Intrvl
: 5 sec
Poll Intrvl
: 120 sec
Cfg Metric
: 0
Advert Subnet
: True
Transit Delay
: 1
Auth Type
: None
Passive
: False
Cfg MTU
: 0
IPsec InStatSA
:
IPsec OutStatSA :
IPsec InStatSATmp:
Admin Status
: Enabled
Oper State
: Designated Rtr
Designated Rtr
: 1.1.1.1
Backup Desig Rtr : 3.3.3.3
IF Type
: Broadcast
Network Type
: Transit
Oper MTU
: 9198
Last Enabled
: 10/09/2012 13:42:14
Oper Metric
: 100
Bfd Enabled
: No
Te Metric
: 100
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State : Disabled
Ldp Tm Left
: 0
Nbr Count
: 1
If Events
: 77
Tot Rx Packets
: 124
Tot Tx Packets
: 125
Rx Hellos
: 104
Tx Hellos
: 104
Rx DBDs
: 2
Tx DBDs
: 3
Rx LSRs
: 1
Tx LSRs
: 1
Rx LSUs
: 13
Tx LSUs
: 10
Rx LS Acks
: 4
Tx LS Acks
: 7
Retransmits
: 0
Discards
: 75
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
LSA Count
: 2
LSA Checksum
: 0x17644
===============================================================================
*A:Dut-A#
7210 SAS M, X OS Routing Protocols Guide
Page 115
Show Commands
neighbor
Syntax
Context
Description
neighbor [ip-int-name | ip-address] [detail]
neighbor [remote | ip-address] [detail]
show>router>ospf
show>router>ospf3
This command will display all neighbor information. To reduce the amount of output the user may opt to
select the neighbors on a given interface by address or name.
The detail option produces a large amount of data. It is recommended to use detail only when requesting a
specific neighbor.
Parameters
remote — This keyword is used to specify the remote ospf neighbour.
ip-address — Display neighbor information for the neighbor identified by the the specified IP address.
ip-int-name — Display neighbor information only for neighbors of the interface identified by the interface
name
Output
Standard OSPF Neighbor Output — The following table describes the standard command output fields
for an OSPF neighbor.
Label
Description
Nbr IP Addr
The IP address this neighbor is using in its IP Source Address. Note
that, on addressless links, this will not be 0.0.0.0, but the address of
another of the neighbor's interfaces.
Nbr Rtr Id
A 32-bit integer uniquely identifying the neighboring router in the
Autonomous System.
Nbr State
Down — This is the initial state of a neighbor conversation. It indicates that there has been no recent information received from the
neighbor.
Attempt — This state is only valid for neighbors attached to NBMA
networks. It indicates that no recent information has been received
from the neighbor, but that a more concerted effort should be made to
contact the neighbor.
Init — In this state, an Hello packet has recently been seen from the
neighbor. However, bidirectional communication has not yet been
established with the neighbor (i.e., the router itself did not appear in the
neighbor's Hello packet).
Two Way — In this state, communication between the two routers is
bidirectional.
ExchStart — This is the first step in creating an adjacency
between the two neighboring routers. The goal of this step is to decide
which router is the master, and to decide upon the initial Database
Descriptor sequence number.
Page 116
7210 SAS M, X OS Routing Protocols Guide
OSPF
Label
Description (Continued)
Exchange — In this state the router is describing its entire link state
database by sending Database Description packets to the neighbor.
Loading — In this state, Link State Request packets are sent to the
neighbor asking for the more recent LSAs that have been discovered
(but not yet received) in the Exchange state.
Full — In this state, the neighboring routers are fully adjacent.
These adjacencies will now appear in router-LSAs and network-LSAs.
Priority
The priority of this neighbor in the designated router election algorithm. The value 0 signifies that the neighbor is not eligible to become
the designated router on this particular network.
RetxQ Len
The current length of the retransmission queue.
Dead Time
The time until this neighbor is declared down, this timer is set to the
dead router interval when a valid hello packet is received from the
neighbor.
No. of Neighbors
The number of adjacent OSPF neighbors on this interface.
Sample Output
A:ALA-A# show router ospf neighbor
===============================================================================
OSPF Neighbors
===============================================================================
Interface-Name
Rtr Id
State
Pri RetxQ
TTL
------------------------------------------------------------------------------pc157-2/1
10.13.8.158
Full
1
0
37
pc157-2/2
10.13.7.165
Full
100 0
33
pc157-2/3
10.13.6.188
Full
1
0
38
------------------------------------------------------------------------------No. of Neighbors: 3
===============================================================================
A:ALA-A#
Sample Output for OSPF3
*A:Dut-A# show router ospf3 neighbor
===============================================================================
OSPF Neighbors
===============================================================================
Interface-Name
Rtr Id
State
Pri RetxQ
TTL
Area-Id
------------------------------------------------------------------------------to_b
6.6.6.6
Full
1
0
33
0.0.0.0
to_c
3.3.3.3
Full
1
0
35
0.0.0.0
7210 SAS M, X OS Routing Protocols Guide
Page 117
Show Commands
------------------------------------------------------------------------------No. of Neighbors: 2
===============================================================================
*A:Dut-A#
Detailed OSPF Neighbor Output — The following table describes the detailed command output fields
for an OSPF neighbor.
Label
Description
Neighbor IP Addr
The IP address this neighbor is using in its IP source address. Note
that, on addressless links, this will not be 0.0.0.0, but the address of
another of the neighbor's interfaces.
Local IF IP Addr
The IP address of this OSPF interface.
Area Id
A 32-bit integer uniquely identifying the area to which this interface is
connected. Area ID 0.0.0.0 is used for the OSPF backbone
Designated Rtr
The IP Interface address of the router identified as the Designated
Router for the network in which this interface is configured. Set to
0.0.0.0 if there is no Designated router.
Neighbor Rtr Id
A 32-bit integer uniquely identifying the neighboring router in the AS.
Neighbor State
Down — This is the initial state of a neighbor conversation. It indicates that there has been no recent information received from the
neighbor
Attempt — This state is only valid for neighbors attached to NBMA
networks. It indicates that no recent information has been received
from the neighbor, but that a more concerted effort should be made to
contact the neighbor.
Init — In this state, an Hello packet has recently been seen from the
neighbor. However, bidirectional communication has not yet been
established with the neighbor (i.e., the router itself did not appear in the
neighbor's Hello packet).
Two Way — In this state, communication between the two routers is
bidirectional.
Exchange start — This is the first step in creating an adjacency
between the two neighboring routers. The goal of this step is to decide
which router is the master, and to decide upon the initial Database
Descriptor sequence number.
Exchange — In this state the router is describing its entire link state
database by sending Database Description packets to the neighbor
Loading — In this state, Link State Request packets are sent to the
neighbor asking for the more recent LSAs that have been discovered
(but not yet received) in the Exchange state.
Page 118
7210 SAS M, X OS Routing Protocols Guide
OSPF
Label
Description (Continued)
Full — In this state, the neighboring routers are fully adjacent.
These adjacencies will now appear in router-LSAs and network-LSAs.
Priority
The priority of this neighbor in the designated router election algorithm. The value 0 signifies that the neighbor is not eligible to become
the designated router on this particular network.
Retrans Q Length
The current length of the retransmission queue.
Options
E — External Routes Support
MC — Multicast Support
N/P — Type 7 LSA Support
EA — External Attribute LSA Support
DC — Demand Circuit Support
O — Opaque LSA Support
Backup Desig Rtr
The IP Interface address of the router identified as the Backup Designated Router for the network in which this interface is configured. Set
to 0.0.0.0 if there is no backup designated router.
Events
The number of times this neighbor relationship has changed state, or an
error has occurred.
Last Event Time
The time when the last event occurred that affected the adjacency to
the neighbor.
Up Time
This value represents the uninterrupted time, in hundredths of seconds,
the adjacency to this neighbor has been up. To evaluate when the last
state change occurred see last event time.
Time Before Dead
The time until this neighbor is declared down, this timer is set to the
dead router interval when a valid hello packet is received from the
neighbor.
Bad Nbr States
The total number of OSPF packets received when the neighbor state
was not expecting to receive this packet type since this interface was
last enabled.
LSA Inst fails
The total number of times an LSA could not be installed into the LSDB
due to a resource allocation issue since this interface was last enabled.
Bad Seq Nums
The total number of times when a database description packet was
received with a sequence number mismatch since this interface was
last enabled.
Bad MTUs
The total number of times when the MTU in a received database
description packet was larger than the MTU of the receiving interface
since this interface was last enabled.
7210 SAS M, X OS Routing Protocols Guide
Page 119
Show Commands
Label
Description (Continued)
Bad Packets
The total number of times when an LS update was received with an
illegal LS type or an option mismatch since this interface was last
enabled.
LSA not in LSDB
The total number of times when an LS request was received for an
LSA not installed in the LSDB of this router since this interface was
last enabled.
Option Mismatches
The total number of times when a LS update was received with an
option mismatch since this interface was last enabled.
Nbr Duplicates
The total number of times when a duplicate database description
packet was received during the exchange state since this interface was
last enabled.
Sample Output
A:ALA-A# show router ospf neighbor detail
===============================================================================
OSPF Neighbors
------------------------------------------------------------------------------Neighbor Rtr Id : 10.13.8.158
Interface: pc157-2/1
------------------------------------------------------------------------------Neighbor IP Addr : 10.16.1.8
Local IF IP Addr : 10.16.1.7
Area Id
: 0.0.0.0
Designated Rtr
: 0.0.0.0
Backup Desig Rtr : 0.0.0.0
Neighbor State
: Full
Priority
: 1
Retrans Q Length : 0
Options
: -E--OEvents
: 4
Last Event Time : 05/06/2006 00:11:16
Up Time
: 1d 18:20:20
Time Before Dead : 38 sec
GR Helper
: Not Helping
GR Helper Age
: 0 sec
GR Exit Reason
: None
GR Restart Reason: Unknown
Bad Nbr States
: 1
LSA Inst fails
: 0
Bad Seq Nums
: 0
Bad MTUs
: 0
Bad Packets
: 0
LSA not in LSDB : 0
Option Mismatches: 0
Nbr Duplicates
: 0
Num Restarts
: 0
Last Restart at : Never
------------------------------------------------------------------------------Neighbor Rtr Id : 10.13.7.165
Interface: pc157-2/2
------------------------------------------------------------------------------Neighbor IP Addr : 10.12.1.3
Local IF IP Addr : 10.12.1.7
Area Id
: 0.0.0.0
Designated Rtr
: 10.13.9.157
Backup Desig Rtr : 10.13.7.165
Neighbor State
: Full
Priority
: 100
Retrans Q Length : 0
Options
: -E--OEvents
: 4
Last Event Time : 05/05/2006 01:39:13
Up Time
: 0d 16:52:27
Time Before Dead : 33 sec
GR Helper
: Not Helping
GR Helper Age
: 0 sec
GR Exit Reason
: None
GR Restart Reason: Unknown
Bad Nbr States
: 0
LSA Inst fails
: 0
Bad Seq Nums
: 0
Bad MTUs
: 0
Bad Packets
: 0
LSA not in LSDB : 0
Page 120
7210 SAS M, X OS Routing Protocols Guide
OSPF
Option Mismatches: 0
Nbr Duplicates
: 0
Num Restarts
: 0
Last Restart at : Never
------------------------------------------------------------------------------Neighbor Rtr Id : 10.13.6.188
Interface: pc157-2/3
------------------------------------------------------------------------------Neighbor IP Addr : 10.14.1.4
Local IF IP Addr : 10.14.1.7
Area Id
: 0.0.0.0
Designated Rtr
: 10.13.9.157
Backup Desig Rtr : 10.13.6.188
Neighbor State
: Full
Priority
: 1
Retrans Q Length : 0
Options
: -E--OEvents
: 4
Last Event Time : 05/05/2006 08:35:18
Up Time
: 0d 09:56:25
Time Before Dead : 38 sec
GR Helper
: Not Helping
GR Helper Age
: 0 sec
GR Exit Reason
: None
GR Restart Reason: Unknown
Bad Nbr States
: 1
LSA Inst fails
: 0
Bad Seq Nums
: 0
Bad MTUs
: 0
Bad Packets
: 0
LSA not in LSDB : 0
Option Mismatches: 0
Nbr Duplicates
: 0
Num Restarts
: 0
Last Restart at : Never
===============================================================================
A:ALA-A#
Sample Output for OSPF3
*A:Dut-A# show router ospf3 neighbor detail
===============================================================================
OSPF Neighbors
===============================================================================
------------------------------------------------------------------------------Neighbor Rtr Id : 6.6.6.6 Interface: to_b
------------------------------------------------------------------------------Neighbor IP Addr : FE80::225:BAFF:FE0D:1E90-"to_b"
Local IF IP Addr : FE80::8E90:D3FF:FEBE:8F5A-"to_b"
Area Id
: 0.0.0.0
Designated Rtr
: 6.6.6.6
Backup Desig Rtr : 1.1.1.1
Neighbor State
: Full
Priority
: 1
Retrans Q Length : 0
Options
: --R--EV6
Events
: 6
Last Event Time : 10/09/2012 13:43:08
Up Time
: 0d 00:17:21
Time Before Dead : 34 sec
GR Helper
: Not Helping
GR Helper Age
: 0 sec
GR Exit Reason
: None
GR Restart Reason: Unknown
Bad Nbr States
: 3
LSA Inst fails
: 0
Bad Seq Nums
: 0
Bad MTUs
: 0
Bad Packets
: 0
LSA not in LSDB : 0
Option Mismatches: 0
Nbr Duplicates
: 0
Num Restarts
: 0
Last Restart at : Never
------------------------------------------------------------------------------Neighbor Rtr Id : 3.3.3.3 Interface: to_c
------------------------------------------------------------------------------Neighbor IP Addr : FE80::8E90:D3FF:FEAA:35F-"to_c"
Local IF IP Addr : FE80::8E90:D3FF:FEBE:8F5A-"to_c"
Area Id
: 0.0.0.0
Designated Rtr
: 1.1.1.1
Backup Desig Rtr : 3.3.3.3
Neighbor State
: Full
Priority
: 1
Retrans Q Length : 0
Options
: --R--EV6
Events
: 5
Last Event Time : 10/09/2012 13:53:59
Up Time
: 0d 00:05:41
Time Before Dead : 36 sec
7210 SAS M, X OS Routing Protocols Guide
Page 121
Show Commands
GR Helper
: Not Helping
GR Helper Age
: 0 sec
GR Exit Reason
: None
GR Restart Reason: Unknown
Bad Nbr States
: 0
LSA Inst fails
: 0
Bad Seq Nums
: 0
Bad MTUs
: 0
Bad Packets
: 0
LSA not in LSDB : 0
Option Mismatches: 0
Nbr Duplicates
: 0
Num Restarts
: 0
Last Restart at : Never
===============================================================================
*A:Dut-A#
opaque-database
Syntax
Context
Description
Output
opaque-database [link link-id | area area-id |as] [adv-router router-id] [ls-id] [detail]
show>router>ospf
This command displays OSPF opaque database information.
OSPF Opaque Database Output — The following table describes the OSPF opaque database output
fields.
Label
Description
Area Id
A 32-bit integer uniquely identifying an area. Area ID 0.0.0.0 is used
for the OSPF backbone.
Type
NSSA — This area is configured as a NSSA area.
Area — This area is configured as a standard area (not NSSA or
stub).
Stub — This area is configured as a NSSA area.
Link State Id
The link state ID is an LSA type specific field containing either a
Router-Id or an IP Address; it identifies the piece of the routing
domain being described by the advertisement.
Adv Rtr Id
The router identifier of the router advertising the LSA.
Age
The age of the link state advertisement in seconds.
Sequence
The signed 32-bit integer sequence number.
Cksum
The 32-bit unsigned sum of the link-state advertisements' LS checksums.
Sample Output
A:ALA-A#
show router ospf opaque-database
===============================================================================
OSPF Opaque Link State Database (Type : All)
===============================================================================
Page 122
7210 SAS M, X OS Routing Protocols Guide
OSPF
Area Id
Type Link State Id
Adv Rtr Id
Age Sequence
Cksum
------------------------------------------------------------------------------0.0.0.0
Area 1.0.0.1
180.0.0.2
205 0x8000007e 0xb1b2
0.0.0.0
Area 1.0.0.1
180.0.0.5
617 0x80000084 0xb1a6
0.0.0.0
Area 1.0.0.1
180.0.0.8
1635 0x80000081 0xc391
0.0.0.0
Area 1.0.0.1
180.0.0.9
1306 0x80000082 0xc58c
0.0.0.0
Area 1.0.0.1
180.0.0.10
53
0x80000082 0xc986
0.0.0.0
Area 1.0.0.1
180.0.0.11
577 0x8000007e 0xd57c
0.0.0.0
Area 1.0.0.1
180.0.0.12
1628 0x80000080 0xd578
0.0.0.0
Area 1.0.0.1
180.0.0.13
581 0x80000080 0xd972
0.0.0.0
Area 1.0.0.1
180.0.0.22
1006 0x80000080 0xfd3c
0.0.0.0
Area 1.0.0.1
180.0.0.23
1238 0x80000083 0xfb39
0.0.0.0
Area 1.0.0.1
180.0.0.27
55
0x80000083 0xc21
0.0.0.0
Area 1.0.0.1
180.0.0.28
389 0x80000083 0x101b
0.0.0.0
Area 1.0.0.1
180.0.0.29
1658 0x80000082 0x1614
0.0.0.0
Area 1.0.0.1
180.0.0.30
976 0x80000083 0x180f
0.0.0.0
Area 1.0.0.2
180.0.0.2
45
0x800000a0 0x2f60
0.0.0.0
Area 1.0.0.2
180.0.0.5
1357 0x80000084 0x7038
0.0.0.0
Area 1.0.0.2
180.0.0.8
1960 0x80000084 0x3472
...
------------------------------------------------------------------------------No. of Opaque LSAs: 88
===============================================================================
A:ALA-A#
*A:Dut-A# show router ospf opaque-database adv-router 10.20.1.1 detail
==============================================================================
OSPF Opaque Link State Database (Type : All) (Detailed)
==============================================================================
-----------------------------------------------------------------------------Opaque LSA
-----------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 10.20.1.1
Link State Id
: 1.0.0.1
LSA Type
: Area Opaque
Sequence No
: 0x80000028
Checksum
: 0xb136
Age
: 192
Length
: 28
Options
: E
Advertisement
:
ROUTER-ID TLV (0001) Len
4 : 10.20.1.1
-----------------------------------------------------------------------------Opaque LSA
-----------------------------------------------------------------------------Area Id
: 0.0.0.0
Adv Router Id
: 10.20.1.1
Link State Id
: 1.0.0.2
LSA Type
: Area Opaque
Sequence No
: 0x8000000d
Checksum
: 0x17f3
Age
: 678
Length
: 164
Options
: E
Advertisement
:
LINK INFO TLV (0002) Len 140 :
Sub-TLV: 1
Len: 1
LINK_TYPE
: 2
Sub-TLV: 2
Len: 4
LINK_ID
: 10.10.1.2
Sub-TLV: 3
Len: 4
LOC_IP_ADDR : 10.10.1.1
Sub-TLV: 4
Len: 4
REM_IP_ADDR : 0.0.0.0
Sub-TLV: 5
Len: 4
TE_METRIC
: 1000
Sub-TLV: 6
Len: 4
MAX_BDWTH
: 100000 Kbps
Sub-TLV: 7
Len: 4
RSRVBL_BDWTH : 800000 Kbps
Sub-TLV: 8
Len: 32
UNRSRVD_CLS0 :
P0:
80000 Kbps P1: 320000 Kbps P2: 320000 Kbps P3: 320000 Kbps
7210 SAS M, X OS Routing Protocols Guide
Page 123
Show Commands
P4: 400000 Kbps P5: 400000 Kbps P6: 400000 Kbps P7:
80000 Kbps
Sub-TLV: 9
Len: 4
ADMIN_GROUP : 0 None
Sub-TLV: 17
Len: 36
TELK_BW_CONST:
BW Model : MAM
BC0:
80000 Kbps BC1:
0 Kbps BC2: 320000 Kbps BC3:
0 Kbps
BC4:
0 Kbps BC5: 400000 Kbps BC6:
0 Kbps BC7:
0 Kbps
==============================================================================
*A:Dut-A#
range
Syntax
Context
range [area-id]
show>router>ospf
show>router>ospf3
Description
This command displays ranges of addresses on an Area Border Router (ABR) for the purpose of route
summarization or suppression.
Parameters
area-id — Display the configured ranges for the specified area.
Output
OSPF Range Output — The following table describes the OSPF range output fields.
Label
Description
Area Id
A 32-bit integer uniquely identifying an area. Area ID 0.0.0.0 is used
for the OSPF backbone.
Address/Mask
The mask for the range expressed as a decimal integer mask length or
in dotted decimal notation.
Advertise
False — The specified address/mask is not advertised outside the
area.
True — The specified address/mask is advertised outside the area.
LSDB Type
NSSA — This range was specified in the NSSA context, and specifies
that the range applies to external routes (via type-7 LSAs) learned
within the NSSA when the routes are advertised to other areas as type5 LSAs.
Summary — This range was not specified in the NSSA context, the
range applies to summary LSAs even if the area is an NSSA.
Sample Output
A:ALA-A# show router ospf range
==========================================================
OSPF Ranges
==========================================================
Area Id
Address/Mask
Advertise
LSDB Type
Page 124
7210 SAS M, X OS Routing Protocols Guide
OSPF
---------------------------------------------------------No. of Ranges: 0
==========================================================
A:ALA-A#
A:ALA-A# show router ospf range 180.0.7.9
==========================================================
OSPF Ranges for Area Id : 180.0.7.9
==========================================================
Area Id
Address/Mask
Advertise
LSDB Type
---------------------------------------------------------No. of Ranges: 0
==========================================================
A:ALA-A#
7210 SAS M, X OS Routing Protocols Guide
Page 125
Show Commands
spf
Syntax
Context
spf
show>router>ospf
show>router>ospf3
Description
This command displays statistics of shortest-path-first (SPF) calculations.
Output
SPF Output Fields — The following table describes SPF output fields.
Label
Description
Total SPF Runs
The total number of incremental SPF runs triggered by new or updated
LSAs.
Last Full SPF run @
The date and time when the external OSPF Dijkstra (SPF) was last run.
Last Full SPF Time
The length of time, in seconds, when the last full SPF was run.
Intra SPF Time
The time when intra-area SPF was last run on this area.
Inter SPF Time
The total number of incremental SPF runs triggered by new or updated
type-3 and type-4 summary LSAs.
Extern SPF Time
The total number of incremental SPF runs triggered by new or updated
type-5 external LSAs.
RTM Updt Time
The time, in hundredths of seconds, used to perform a total SPF calculation.
Min/Avg/Max Full SPF
Time
Min — The minimum time, in hundredths of seconds, used to perform a total SPF calculation.
Avg — The average time, in hundredths of seconds, of all the total
SPF calculations performed by this OSPF router.
Max — The maximum time, in hundredths of seconds, used to perform a total SPF calculation.
Total Sum Incr SPF
Runs
The total number of incremental SPF runs triggered by new or updated
type-3 and type-4 summary LSAs.
Total Ext Incr SPF
Runs
The total number of incremental SPF runs triggered by new or updated
type-5 external LSAs.
Sample Output
A:ALA-A# show router ospf spf
===============================================================================
OSPF SPF Statistics
===============================================================================
Total SPF Runs
: 109
Last Full SPF run @
: 11/07/2006 18:43:07
Page 126
7210 SAS M, X OS Routing Protocols Guide
OSPF
Last Full SPF Time
Intra SPF Time
Inter SPF Time
Extern SPF Time
RTM Updt Time
:
:
:
:
:
Min/Avg/Max Full SPF Times
Min/Avg/Max RTM Updt Times
Total Sum Incr SPF Runs :
Last Sum Incr SPF run @ :
Last Sum Incr Calc Time :
<
<
<
<
<
0.01
0.01
0.01
0.01
0.01
:
:
secs
secs
secs
secs
secs
0.02/0.00/0.06 secs
0.02/0.00/0.06 secs
333
11/07/2006 18:43:09
< 0.01 secs
Total Ext Incr SPF Runs : 0
===============================================================================
A:ALA-A#
7210 SAS M, X OS Routing Protocols Guide
Page 127
Show Commands
statistics
Syntax
Context
Description
Output
statistics
show>router>ospf
show>router>ospf3
This command displays the global OSPF statistics.
OSPF Statistics Output Fields — The following table describes the command output fields for OSPF
statistics.
Label
Page 128
Description
Rx Packets
The total number of OSPF packets received on all OSPF enabled interfaces.
Tx Packets
The total number of OSPF packets transmitted on all OSPF enabled
interfaces.
Rx Hellos
The total number of OSPF Hello packets received on all OSPF enabled
interfaces.
Tx Hellos
The total number of OSPF Hello packets transmitted on all OSPF
enabled interfaces.
Rx DBDs
The total number of OSPF database description packets received on all
OSPF enabled interfaces.
Tx DBDs
The total number of OSPF database description packets transmitted on
all OSPF enabled interfaces
Rx LSRs
The total number of OSPF Link State Requests (LSRs) received on all
OSPF enabled interfaces.
Tx LSRs
The total number of OSPF Link State Requests (LSRs) transmitted on
all OSPF enabled interfaces.
Rx LSUs
The total number of OSPF Link State Update (LSUs) received on all
OSPF enabled interfaces.
Tx LSUs
The total number of OSPF Link State Update (LSUs) transmitted on all
OSPF enabled interfaces.
Rx LS Acks
The total number of OSPF Link State Acknowledgements (LSAs)
received on all OSPF enabled interfaces.
New LSAs Recvd
The total number of new OSPF Link State Advertisements received on
all OSPF enabled interfaces.
New LSAs Orig
The total number of new OSPF Link State Advertisements originated
on all OSPF enabled interfaces.
Ext LSAs Count
The total number of OSPF External Link State Advertisements.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Label
Description
No of Areas
The number of areas configured for this OSPF instance.
Total SPF Runs
The total number of incremental SPF runs triggered by new or updated
LSAs.
Ext SPF Runs
The total number of incremental SPF runs triggered by new or updated
type-5 external LSAs.
Retransmits
The total number of OSPF Retransmits transmitted on all OSPF
enabled interfaces.
Discards
The total number of OSPF packets discarded on all OSPF enabled
interfaces.
Bad Networks
The total number of OSPF packets received on all OSPF enabled interfaces with invalid network or mask.
Bad Virt Links
The total number of OSPF packets received on all OSPF enabled interfaces that are destined to a virtual link that does not exist.
Bad Areas
The total number of OSPF packets received on all OSPF enabled interfaces with an area mismatch
Bad Dest Addrs
The total number of OSPF packets received on all OSPF enabled interfaces with the incorrect IP destination address.
Bad Auth Types
The total number of OSPF packets received on all OSPF enabled interfaces with an invalid authorization type.
Auth Failures
The total number of OSPF packets received on all OSPF enabled interfaces with an invalid authorization key.
Bad Neighbors
The total number of OSPF packets received on all OSPF enabled interfaces where the neighbor information does not match the information
this router has for the neighbor.
Bad Pkt Types
The total number of OSPF packets received on all OSPF enabled interfaces with an invalid OSPF packet type.
Bad Lengths
The total number of OSPF packets received on all OSPF enabled interfaces with a total length not equal to the length given in the packet
itself.
Bad Hello Int.
The total number of OSPF packets received on all OSPF enabled interfaces where the hello interval given in packet was not equal to that
configured for the respective interface.
Bad Dead Int.
The total number of OSPF packets received on all OSPF enabled interfaces where the dead interval given in the packet was not equal to that
configured for the respective interface.
7210 SAS M, X OS Routing Protocols Guide
Page 129
Show Commands
Label
Description
Bad Options
The total number of OSPF packets received on all OSPF enabled interfaces with an option that does not match those configured for the
respective interface or area.
Bad Versions
The total number of OSPF packets received on all OSPF enabled interfaces with bad OSPF version numbers.
Sample Output
A:ALA-A# show router ospf statistics
===============================================================================
OSPF Statistics
===============================================================================
Rx Packets
: 308462
Tx Packets
: 246800
Rx Hellos
: 173796
Tx Hellos
: 149062
Rx DBDs
: 67
Tx DBDs
: 48
Rx LSRs
: 21
Tx LSRs
: 19
Rx LSUs
: 105672
Tx LSUs
: 65530
Rx LS Acks
: 28906
Tx LS Acks
: 32141
New LSAs Recvd
: 38113
New LSAs Orig
: 21067
Ext LSAs Count
: 17
No of Areas
: 3
Total SPF Runs
: 327
Ext SPF Runs
: 0
Retransmits
: 46
Discards
: 0
Bad Networks
: 0
Bad Virt Links
: 0
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
Failed SPF Attempts: 0
CSPF Requests
: 0
CSPF Request Drops : 0
CSPF Path Found
: 0
CSPF Path Not Found: 0
===============================================================================
A:ALA-A#
Sample Output for OSPF3
*A:Dut-A# show router ospf3 statistics
===============================================================================
OSPF Statistics
===============================================================================
Rx Packets
: 606
Tx Packets
: 497
Rx Hellos
: 233
Tx Hellos
: 233
Rx DBDs
: 7
Tx DBDs
: 6
Rx LSRs
: 2
Tx LSRs
: 2
Rx LSUs
: 248
Tx LSUs
: 240
Rx LS Acks
: 116
Tx LS Acks
: 16
New LSAs Recvd
: 0
New LSAs Orig
: 30
Ext LSAs Count
: 0
No of Areas
: 1
No of Interfaces
: 3
No of Neighbors
: 2
Retransmits
: 1
Discards
: 76
Bad Networks
: 0
Bad Virt Links
: 0
Page 130
7210 SAS M, X OS Routing Protocols Guide
OSPF
Bad Areas
: 0
Bad Dest Addrs
: 0
Bad Auth Types
: 0
Auth Failures
: 0
Bad Neighbors
: 0
Bad Pkt Types
: 0
Bad Lengths
: 0
Bad Hello Int.
: 0
Bad Dead Int.
: 0
Bad Options
: 0
Bad Versions
: 0
Bad Checksums
: 0
Failed SPF Attempts: 0
CSPF Requests
: 0
CSPF Request Drops : 0
CSPF Path Found
: 0
CSPF Path Not Found: 0
===============================================================================
*A:Dut-A#
7210 SAS M, X OS Routing Protocols Guide
Page 131
Show Commands
status
Syntax
Context
Description
Output
status
show>router>ospf
show>router>ospf3
Displays the general status of OSPF.
OSPF Status Output Fields — The following table describes the command output fields for OSPF
status.
Label
Description
OSPF Router Id
A 32-bit integer uniquely identifying the router in the Autonomous System. The defaults to the System IP address or if not configured the 32
least significant bits of the system MAC address.
OSPF Version
The current version number of the OSPF protocol is 2.
OSPF Admin Status
Disabled — Denotes that the OSPF process is disabled on all interfaces.
Enabled — Denotes that the OSPF process is active on at least one
interface.
OSPF Oper Status
Disabled — Denotes that the OSPF process is not operational on all
interfaces.
Enabled — Denotes that the OSPF process is operational on at least
one interface.
Preference
The route preference for OSPF internal routes.
External Preference
The route preference for OSPF external routes.
Backbone Router
False — This variable indicates that this router is not configured as
an OSPF back bone router.
True — This variable indicates that this router is configured as an
OSPF back bone router.
Area Border Router
False — This router is not an area border router.
True — This router is an area border router.
AS Border Router
False — This router is not configured as an Autonomous System
border router.
True — This router is configured as an Autonomous System border
router.
OSPF Ldp Sync
Admin Status
Page 132
Indicates whether the IGP-LDP synchronization feature is enabled or
disabled on all interfaces participating in the OSPF routing protocol.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Sample Output
A:ALA-A# show router ospf status
===============================================================================
OSPF Status
===============================================================================
OSPF Router Id
: 10.13.7.165
OSPF Version
: 2
OSPF Admin Status
: Enabled
OSPF Oper Status
: Enabled
Graceful Restart
: Enabled
GR Helper Mode
: Disabled
Preference
: 10
External Preference
: 150
Backbone Router
: True
Area Border Router
: True
AS Border Router
: True
Opaque LSA Support
: True
Traffic Engineering Support : True
RFC 1583 Compatible
: True
TOS Routing Support
: False
Demand Exts Support
: False
In Overload State
: False
In External Overflow State
: False
Exit Overflow Interval
: 0
Last Overflow Entered
: Never
Last Overflow Exit
: Never
External LSA Limit
: -1
Reference Bandwidth
: 100,000,000 Kbps
Init SPF Delay
: 500 msec
Sec SPF Delay
: 2000 msec
Max SPF Delay
: 15000 msec
Min LS Arrival Interval
: 500 msec
Max LSA Gen Delay
: 5000 msec
Last Ext SPF Run
: Never
Ext LSA Cksum Sum
: 0x2afce
OSPF Last Enabled
: 05/23/2006 23:34:36
Export Policies
: export-static
===============================================================================
A:ALA-A#
*A:ALU_SIM11>show>router>ospf# status
===============================================================================
OSPF Status
===============================================================================
OSPF Cfg Router Id
: 0.0.0.0
OSPF Oper Router Id
: 1.1.1.2
OSPF Version
: 2
OSPF Admin Status
: Enabled
OSPF Oper Status
: Enabled
Graceful Restart
: Disabled
GR Helper Mode
: Disabled
Preference
: 10
External Preference
: 150
Backbone Router
: True
Area Border Router
: False
AS Border Router
: False
Opaque LSA Support
: True
7210 SAS M, X OS Routing Protocols Guide
Page 133
Show Commands
Traffic Engineering Support : False
RFC 1583 Compatible
: True
Demand Exts Support
: False
In Overload State
: False
In External Overflow State
: False
Exit Overflow Interval
: 0
Last Overflow Entered
: Never
Last Overflow Exit
: Never
External LSA Limit
: -1
Reference Bandwidth
: 100,000,000 Kbps
Init SPF Delay
: 1000 msec
Sec SPF Delay
: 1000 msec
Max SPF Delay
: 10000 msec
Min LS Arrival Interval
: 1000 msec
Init LSA Gen Delay
: 5000 msec
Sec LSA Gen Delay
: 5000 msec
Max LSA Gen Delay
: 5000 msec
Last Ext SPF Run
: Never
Ext LSA Cksum Sum
: 0x0
OSPF Last Enabled
: 07/06/2010 10:34:11
Multicast Import
: False
Export Policies
: None
OSPF Ldp Sync Admin Status
: Enabled
LDP-over-RSVP
: Disabled
===============================================================================
Sample Output for OSPF3
*A:Dut-A# show router ospf3 status
===============================================================================
OSPF Status
===============================================================================
OSPF Cfg Router Id
: 0.0.0.0
OSPF Oper Router Id
: 1.1.1.1
OSPF Version
: 3
OSPF Admin Status
: Enabled
OSPF Oper Status
: Enabled
Graceful Restart
: Disabled
GR Helper Mode
: Disabled
Preference
: 10
External Preference
: 150
Backbone Router
: True
Area Border Router
: False
AS Border Router
: False
Traffic Engineering Support : False
Demand Exts Support
: False
In Overload State
: False
In External Overflow State
: False
Exit Overflow Interval
: 0
Last Overflow Entered
: Never
Last Overflow Exit
: Never
External LSA Limit
: -1
Reference Bandwidth
: 100,000,000 Kbps
Init SPF Delay
: 1000 msec
Sec SPF Delay
: 1000 msec
Max SPF Delay
: 10000 msec
Min LS Arrival Interval
: 1000 msec
Init LSA Gen Delay
: 5000 msec
Page 134
7210 SAS M, X OS Routing Protocols Guide
OSPF
Sec LSA Gen Delay
Max LSA Gen Delay
Last Ext SPF Run
Ext LSA Cksum Sum
OSPF Last Enabled
Multicast Import
Export Policies
OSPF Ldp Sync Admin Status
LDP-over-RSVP
RSVP-Shortcut
Advertise-Tunnel-Link
Export Limit
Export Limit Log Percent
Total Exp Routes
:
:
:
:
:
:
:
:
:
:
:
:
:
:
5000 msec
5000 msec
Never
0x0
10/09/2012 13:41:23
False
None
Enabled
Disabled
Disabled
Disabled
0
0
0
7210 SAS M, X OS Routing Protocols Guide
Page 135
Show Commands
virtual-link
Syntax
virtual-link [detail]
Context
show>router>ospf
show>router>ospf3
Description
This command displays information for OSPF virtual links.
Parameters
detail — Provides operational and statistical information about virtual links associated with this router.
Output
OSPF Virtual Link Output — The following table describes OSPF virtual-link output fields.
Label
Page 136
Description
Nbr Rtr ID
The router ID(s) of neighboring routers.
Area Id
A 32-bit integer which identifies an area.
Local Interface
The IP address of the local egress interface used to maintain the adjacency to reach this virtual neighbor.
Metric
The metric value associated with the route. This value is used when
importing this static route into other protocols. When the metric is configured as zero then the metric configured in OSPF, default-importmetric, applies. This value is also used to determine which static route
to install in the forwarding table.
State
The operational state of the virtual link to the neighboring router.
Authentication
Specifies whether authentication is enabled for the interface or virtual
link.
Hello Intrval
Specifies the length of time, in seconds, between the Hello packets that
the router sends on the interface.
Rtr Dead Intrvl
Specifies the total number of OSPF packets received where the dead
interval given in the packet was not equal to that configured on this
interface since the OSPF admin status was enabled.
Tot Rx Packets
Specifies the total number of OSPF packets received on this interface
since the OSPF admin status was enabled.
Rx Hellos
Specifies the total number of OSPF Hello packets received on this
interface since the OSPF admin status was enabled.
Rx DBDs
Specifies the total number of OSPF DataBase Description packets
received on this interface since the OSPF administrative status was
enabled.
Rx LSRs
Specifies the total number of Link State Requests (LSRs) received on
this interface since the OSPF admin status was enabled.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Label
Description (Continued)
Rx LSUs
Specifies the total number of Link State Updates (LSUs) received on
this interface since the OSPF admin status was enabled.
Rx LS Acks
Specifies the total number of Link State Acknowledgements received
on this interface since the OSPF admin status was enabled.
Tot Tx Packets
Specifies the total number of OSPF packets transmitted on this virtual
interface since it was created.
Tx Hellos
Specifies the total number of OSPF Hello packets transmitted on this
virtual interface since it was created.
Tx DBDs
Specifies the total number of OSPF database description packets transmitted on this virtual interface.
Tx LSRs
Specifies the total number of OSPF Link State Requests (LSRs) transmitted on this virtual interface.
Tx LSUs
Specifies the total number of OSPF Hello packets transmitted on this
interface since the OSPF admin status was enabled.
Tx LS Acks
Specifies the total number of OSPF Link State Acknowledgements
(LSA) transmitted on this virtual interface.
Retransmits
Specifies the total number of OSPF retransmits sent on this interface
since the OSPF admin status was last enabled.
Discards
Specifies the total number of OSPF packets discarded on this interface
since the OSPF admin status was last enabled.
Bad Networks
Specifies the total number of OSPF packets received with invalid network or mask since the OSPF admin status was last enabled.
Bad Versions
Specifies the total number of OSPF packets received with bad OSPF
version numbers since the OSPF admin status was last enabled.
Bad Areas
Specifies the total number of OSPF packets received with an area mismatch since the OSPF admin status was last enabled.
Bad Dest Addrs
Specifies the total number of OSPF packets received with the incorrect
IP destination address since the OSPF admin status was last enabled.
Bad Auth Types
Specifies the total number of OSPF packets received with an invalid
authorization type since the OSPF admin status was last enabled.
Auth Failures
Specifies the total number of OSPF packets received with an invalid
authorization key since the OSPF admin status was last enabled.
Bad Neighbors
Specifies the total number of OSPF packets received where the neighbor information does not match the information this router has for the
neighbor since the OSPF admin status was last enabled.
7210 SAS M, X OS Routing Protocols Guide
Page 137
Show Commands
Label
Description (Continued)
Bad Pkt Types
Specifies the total number of OSPF packets received with an invalid
OSPF packet type since the OSPF admin status was last enabled.
Bad Lengths
Specifies the total number of OSPF packets received on this interface
with a total length not equal to the length given in the packet itself
since the OSPF admin status was last enabled.
Bad Hello Int.
Specifies the total number of OSPF packets received where the hello
interval given in packet was not equal to that configured on this interface since the OSPF admin status was last enabled.
Bad Dead Int.
Specifies the total number of OSPF packets received where the dead
interval given in the packet was not equal to that configured on this
interface since the OSPF admin status was last enabled.
Bad Options
Specifies the total number of OSPF packets received with an option
that does not match those configured for this interface or area since the
OSPF admin status was last enabled.
Retrans Intrvl
Specifies the length of time, in seconds, that OSPF waits before
retransmitting an unacknowledged link state advertisement (LSA) to
an OSPF neighbor.
Transit Delay
Specifies the time, in seconds, that it takes to transmit a link state
advertisement (LSA) on the interface or virtual link.
Last Event
Specifies the date and time when an event was last associated with this
OSPF interface.
Sample Output
A:ALA-A# show router ospf virtual-link
=================================================================
OSPF Virtual Links
=================================================================
Nbr Rtr Id
Area Id
Local Interface
Metric State
----------------------------------------------------------------180.0.0.10
0.0.0.1
180.1.7.12
300
PToP
180.0.0.10
0.0.0.2
180.2.7.12
300
PToP
----------------------------------------------------------------No. of OSPF Virtual Links: 2
=================================================================
A:ALA-A#
A:ALA-A# show router ospf virtual-link detail
===============================================================================
OSPF Virtual Links (detailed)
===============================================================================
Neighbor Router Id : 180.0.0.10
Page 138
7210 SAS M, X OS Routing Protocols Guide
OSPF
------------------------------------------------------------------------------Nbr Router Id : 180.0.0.10
Area Id
: 0.0.0.1
Local Interface: 180.1.7.12
Metric
: 300
State
: Point To Point
Admin State
: Up
Hello Intrvl
: 10 sec
Rtr Dead Intrvl: 60 sec
Tot Rx Packets : 43022
Tot Tx Packets : 42964
Rx Hellos
: 24834
Tx Hellos
: 24853
Rx DBDs
: 3
Tx DBDs
: 2
Rx LSRs
: 0
Tx LSRs
: 0
Rx LSUs
: 15966
Tx LSUs
: 16352
Rx LS Acks
: 2219
Tx LS Acks
: 1757
Retransmits
: 0
Discards
: 0
Bad Networks
: 0
Bad Versions
: 0
Bad Areas
: 0
Bad Dest Addrs : 0
Bad Auth Types : 0
Auth Failures : 0
Bad Neighbors : 0
Bad Pkt Types : 0
Bad Lengths
: 0
Bad Hello Int. : 0
Bad Dead Int. : 0
Bad Options
: 0
Retrans Intrvl : 5 sec
Transit Delay : 1 sec
Last Event
: 11/07/2006 17:11:56
Authentication : None
------------------------------------------------------------------------------Neighbor Router Id : 180.0.0.10
------------------------------------------------------------------------------Nbr Router Id : 180.0.0.10
Area Id
: 0.0.0.2
Local Interface: 180.2.7.12
Metric
: 300
State
: Point To Point
Admin State
: Up
Hello Intrvl
: 10 sec
Rtr Dead Intrvl: 60 sec
Tot Rx Packets : 43073
Tot Tx Packets : 43034
Rx Hellos
: 24851
Tx Hellos
: 24844
Rx DBDs
: 3
Tx DBDs
: 2
Rx LSRs
: 1
Tx LSRs
: 1
Rx LSUs
: 18071
Tx LSUs
: 17853
Rx LS Acks
: 147
Tx LS Acks
: 334
Retransmits
: 0
Discards
: 0
Bad Networks
: 0
Bad Versions
: 0
Bad Areas
: 0
Bad Dest Addrs : 0
Bad Auth Types : 0
Auth Failures : 0
Bad Neighbors : 0
Bad Pkt Types : 0
Bad Lengths
: 0
Bad Hello Int. : 0
Bad Dead Int. : 0
Bad Options
: 0
Retrans Intrvl : 5 sec
Transit Delay : 1 sec
Last Event
: 11/07/2006 17:12:00
Authentication : MD5
===============================================================================
A:ALA-A#
7210 SAS M, X OS Routing Protocols Guide
Page 139
Show Commands
virtual-neighbor
Syntax
Context
virtual-neighbor [remote router-id] [detail]
show>router>ospf
show>router>ospf3
Description
This command displays virtual neighbor information.
Parameters
remote router-id — Displays the specified router ID. This reduces the amount of output displayed.
detail — Produces detailed information on the virtual neighbor. This option produces a large amount of data.
It is recommended to use detail only when requesting information for a specific neighbor.
Output
OSPF Virtual Neighbor Output — The following table describes OSPF virtual neighbor output fields.
Label
Page 140
Description
Nbr IP Addr
The IP address this neighbor is using in its IP source address. Note
that, on addressless links, this will not be 0.0.0.0, but the address of
another of the neighbor's interfaces.
Nbr Rtr ID
Specifies the router ID(s) of neighboring routers.
Transit Area
Specifies the transit area ID that links the backbone area with the area
that has no physical connection with the backbone.
Retrans Q Length
The current length of the retransmission queue.
No. of Neighbors
Specifies the total number of OSPF neighbors adjacent on this interface, in a state of INIT or greater, since the OSPF admin status was
enabled.
Nbr State
Specifies the operational state of the virtual link to the neighboring
router.
Options
Specifies the total number of OSPF packets received with an option
that does not match those configured for this virtual interface or transit
area since the OSPF admin status was enabled.
Events
Specifies the total number of events that have occurred since the OSPF
admin status was enabled.
Last Event Time
Specifies the date and time when an event was last associated with this
OSPF interface.
Up Time
Specifies the uninterrupted time, in hundredths of seconds, the adjacency to this neighbor has been up.
Time Before Dead
Specifies the amount of time, in seconds, until the dead router interval
expires.
Bad Nbr States
Specifies the total number of OSPF packets received where the neighbor information does not match the information this router has for the
neighbor since the OSPF admin status was last enabled.
7210 SAS M, X OS Routing Protocols Guide
OSPF
Label
Description (Continued)
LSA Inst fails
Specifies the total number of times an LSA could not be installed into
the LSDB due to a resource allocation issue since the OSPF admin status was last enabled.
Bad Seq Nums
Specifies the total number of times when a database description packet
was received with a sequence number mismatch since the OSPF admin
status was last enabled.
Bad MTUs
Specifies the total number of times when the MTU in a received database description packet was larger than the MTU of the receiving interface since the OSPF admin status was enabled.
Bad Packets
Specifies the total number of times when an LS update was received
with an illegal LS type or an option mismatch since the OSPF admin
status was enabled.
LSA not in LSDB
Specifies the total number of times when an LS request was received
for an LSA not installed in the LSDB of this router since the OSPF
admin status was enabled.
Option Mismatches
Specifies the total number of times when a LS update was received
with an option mismatch since the OSPF admin status was enabled.
Nbr Duplicates
Specifies the total number of times when a duplicate database description packet was received during the Exchange state since the OSPF
admin status was enabled.
Sample Output
A:ALA-A# show router ospf virtual-neighbor
===============================================================================
OSPF Virtual Neighbors
===============================================================================
Nbr IP Addr
Nbr Rtr Id
Nbr State Transit Area
RetxQ Len Dead Time
------------------------------------------------------------------------------180.1.6.10
180.0.0.10
Full
0.0.0.1
0
58
180.2.9.10
180.0.0.10
Full
0.0.0.2
0
52
------------------------------------------------------------------------------No. of Neighbors: 2
===============================================================================
A:ALA-A#
A:ALA-A# show router ospf virtual-neighbor detail
===============================================================================
OSPF Virtual Neighbors
===============================================================================
Virtual Neighbor Router Id : 180.0.0.10
------------------------------------------------------------------------------Neighbor IP Addr : 180.1.6.10
Neighbor Rtr Id : 180.0.0.10
Neighbor State
: Full
Transit Area
: 0.0.0.1
Retrans Q Length : 0
Options
: -E--
7210 SAS M, X OS Routing Protocols Guide
Page 141
Show Commands
Events
: 4
Last Event Time : 11/07/2006 17:11:56
Up Time
: 2d 17:47:17
Time Before Dead : 57 sec
Bad Nbr States
: 1
LSA Inst fails
: 0
Bad Seq Nums
: 0
Bad MTUs
: 0
Bad Packets
: 0
LSA not in LSDB : 0
Option Mismatches: 0
Nbr Duplicates
: 0
------------------------------------------------------------------------------Virtual Neighbor Router Id : 180.0.0.10
------------------------------------------------------------------------------Neighbor IP Addr : 180.2.9.10
Neighbor Rtr Id : 180.0.0.10
Neighbor State
: Full
Transit Area
: 0.0.0.2
Retrans Q Length : 0
Options
: -E-Events
: 4
Last Event Time : 11/07/2006 17:11:59
Up Time
: 2d 17:47:14
Time Before Dead : 59 sec
Bad Nbr States
: 1
LSA Inst fails
: 0
Bad Seq Nums
: 0
Bad MTUs
: 0
Bad Packets
: 0
LSA not in LSDB : 0
Option Mismatches: 0
Nbr Duplicates
: 0
===============================================================================
A:ALA-A#
Page 142
7210 SAS M, X OS Routing Protocols Guide
OSPF
Clear Commands
ospf
Syntax
Context
Description
ospf
clear>router
This command clears and resets OSPF protocol entities.
database
Syntax
database [purge]
Context
clear>router>ospf
clear>router>ospf3
Description
This command clears all LSAs received from other nodes.
Sets all adjacencies better then two way to one way.
Refreshes all self originated LSAs
Parameters
purge — The purge parameter also clears all self-originated LSAs and re-originates all self-originated LSAs
export
Syntax
Context
Description
export
clear>router>ospf
clear>router>ospf3
Re-evaluates all effective export policies
neighbor
Syntax
Context
neighbor [ip-int-name | ip-address]
clear>router>ospf
clear>router>ospf3
Description
Marks the neighbor as dead and re-initiates the affected adjacencies.
Parameters
ip-int-name — Clear all neighbors for the interface specified by this interface name.
ip-address — Clear all neighbors for the interface specified by this IP-address
7210 SAS M, X OS Routing Protocols Guide
Page 143
Clear Commands
statistics
Syntax
Context
Description
Page 144
statistics
clear>router>ospf
clear>router>ospf3
Clears all neighbor, router, interface, SPF and global statistics of this OSPF instance.
7210 SAS M, X OS Routing Protocols Guide
OSPF
OSPF Debug Commands
ospf
Syntax
Context
Description
ospf
debug>router
Indicates the OSPF instance for debugging purposes.
area
Syntax
Context
area [area-id]
no area
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for an OSPF area.
Parameters
area-id — Specify the OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
Values
0 — 4294967295
area-range
Syntax
Context
area-range [ip-address]
no area-range
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for an OSPF area range.
Parameters
ip-address — Specify the IP address for the range used by the ABR to advertise the area into another area.
cspf
Syntax
Context
Description
cspf [ip-address]
no cspf
debug>router>ospf
debug>router>ospf3
This command enables debugging for an OSPF constraint-based shortest path first (CSPF).
7210 SAS M, X OS Routing Protocols Guide
Page 145
OSPF Debug Commands
Parameters
ip-address — Specify the IP address for the range used for CSPF.
graceful-restart
Syntax
Context
Description
[no] graceful-restart
debug>router>ospf
ebug>router>ospf3
This command enables debugging for OSPF and OSPF3 graceful-restart.
interface
Syntax
Context
interface [ip-int-name | ip-address]
no interface
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for an OSPF and OSPF3interface.
Parameters
ip-int-name — Specify the IP interface name. An interface name cannot be in the form of an IP address.
Interface names can be any string up to 32 characters long composed of printable, 7-bit ASCII
characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed
within double quotes.
ip-address — Specify the interface’s IP address.
leak
Syntax
Context
leak [ip-address]
no leak
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for OSPF leaks.
Parameters
ip-address — Specify the IP address to debug OSPF leaks.
Page 146
7210 SAS M, X OS Routing Protocols Guide
OSPF
lsdb
Syntax
Context
lsdb [type] [ls-id] [adv-rtr-id] [area area-id]
no lsdb
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for an OSPF link-state database (LSDB).
Parameters
type — Specifies the OSPF link-state database (LSDB) type.
Values
router, network, summary, asbr, extern, nssa, area-opaque, as-opaque, link-opaque
ls-id — Specifies an LSA type specific field containing either a router ID or an IP address. It identifies the
piece of the routing domain being described by the advertisement.
adv-rtr-id — Specifies the router identifier of the router advertising the LSA.
area-id — Specifies a 32-bit integer uniquely identifying an area.
misc
Syntax
Context
Description
[no] misc
debug>router>ospf
debug>router>ospf3
This command enables debugging for miscellaneous OSPF events.
neighbor
Syntax
Context
neighbor [ip-int-name | ip-address]
no neighbor
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for an OSPF or OSPF3 neighbor.
Parameters
ip-int-name — Specifies the neighbor interface name.
ip-address — Specifies neighbor information for the neighbor identified by the the specified router ID.
7210 SAS M, X OS Routing Protocols Guide
Page 147
OSPF Debug Commands
nssa-range
Syntax
Context
nssa-range [ip-address]
no nssa-range
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for an NSSA range.
Parameters
ip-address — Specifies the IP address range to debug.
packet
Syntax
Context
packet [packet-type] [interface-name] [ingress|egress] [detail]
no packet
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for OSPF packets.
Parameters
detail — Displays detail packet information.
egress — This keyword specifies an egress packet.
ingress — This keyword specifies ingress packet.
interface-name — Specifies the interface name to debug.
Values
ipv6-address:
x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x: [0 — FFFF]H
d: [0 — 255]D
packet-type — Specifies the OSPF packet type to debug.
Values
hello, dbdescr, lsrequest, lsupdate, lsack
rtm
Syntax
Context
rtm [ip-address]
no rtm
debug>router>ospf
debug>router>ospf3
Description
This command enables debugging for OSPF RTM.
Parameters
ip-address — Specifies the IP address to debug.
Values
Page 148
ipv4-address:
a.b.c.d
7210 SAS M, X OS Routing Protocols Guide
OSPF
spf
Syntax
Context
spf [type] [dest-addr]
no spf
debug>router>ospf
Description
This command enables debugging for OSPF SPF. Information regarding overall SPF start and stop times
will be shown. To see detailed information regarding the SPF calculation of a given route, the route must be
specified as an optional argument.
Parameters
type — Specifies the area to debug
Values
intra-area, inter-area, external
dest-addr — Specifies the destination IP address to debug.
virtual-neighbor
Syntax
Context
virtual-neighbor [ip-address]
no virtual-neighbor
debug>router>ospf
Description
This command enables debugging for an OSPF virtual neighbor.
Parameters
ip-address — Specifies the IP address of the virtual neighbor.
7210 SAS M, X OS Routing Protocols Guide
Page 149
OSPF Debug Commands
Page 150
7210 SAS M, X OS Routing Protocols Guide
IS-IS
In This Chapter
This chapter provides information to configure Intermediate System to Intermediate System
(IS-IS).
NOTE: IS-IS is not supported in 7210 SAS-M access-uplink mode.
Topics in this chapter include:
•
Configuring IS-IS on page 152
→ Routing on page 153
−
IS-IS Frequently Used Terms on page 155
−
ISO Network Addressing on page 156
−
IS-IS PDU Configuration on page 158
−
IS-IS Operations on page 158
−
IS-IS Route Summarization on page 159
−
IS-IS Administrative Tags on page 160
•
IS-IS Configuration Process Overview on page 162
•
Configuration Notes on page 163
7210 SAS M, X OS Routing Protocols Guide
Page 151
Configuring IS-IS
Configuring IS-IS
Intermediate-system-to-intermediate-system (IS-IS) is a link-state interior gateway protocol (IGP)
which uses the Shortest Path First (SPF) algorithm to determine routes. Routing decisions are
made using the link-state information. IS-IS evaluates topology changes and, if necessary,
performs SPF recalculations.
Entities within IS-IS include networks, intermediate systems, and end systems. In IS-IS, a network
is an autonomous system (AS), or routing domain, with end systems and intermediate systems. A
router is an intermediate system. End systems are network devices which send and receive protocol
data units (PDUs), the OSI term for packets. Intermediate systems send, receive, and forward
PDUs.
End system and intermediate system protocols allow routers and nodes to identify each other. IS-IS
sends out link-state updates periodically throughout the network, so each router can maintain
current network topology information.
IS-IS supports large ASs by using a two-level hierarchy. A large AS can be administratively
divided into smaller, more manageable areas. A system logically belongs to one area. Level 1
routing is performed within an area. Level 2 routing is performed between areas. Routers can be
configured as Level 1, Level 2, or both Level 1/2.
Figure 3 displays an example of an IS-IS routing domain.
Level 2
Backbone
Area A
Area B
L1
L1
L1/2
L1/2
L1
L1
L2
L1/2
L1/2
Area C
L1
L1
OSRG033
Figure 3: IS-IS Routing Domain
Page 152
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Routing
OSI IS-IS routing uses two-level hierarchical routing. A routing domain can be partitioned into
areas. Level 1 routers know the topology in their area, including all routers and end systems in
their area but do not know the identity of routers or destinations outside of their area. Level 1
routers forward traffic with destinations outside of their area to a Level 2 router in their area.
Level 2 routers know the Level 2 topology, and know which addresses are reachable by each Level
2 router. Level 2 routers do not need to know the topology within any Level 1 area, except to the
extent that a Level 2 router can also be a Level 1 router within a single area. By default, only Level
2 routers can exchange PDUs or routing information directly with external routers located outside
the routing domain.
In IS-IS, there are two types of routers:
•
Level 1 intermediate systems — Routing is performed based on the area ID portion of the
ISO address called the network entity title (NET). Level 1 systems route within an area.
They recognize, based on the destination address, whether the destination is within the
area. If so, they route toward the destination. If not, they route to the nearest Level 2
router.
•
Level 2 intermediate systems — Routing is performed based on the area address. They
route toward other areas, disregarding other area’s internal structure. A Level 2
intermediate system can also be configured as a Level 1 intermediate system in the same
area.
The Level 1 router’s area address portion is manually configured (see ISO Network Addressing on
page 156). A Level 1 router will not become a neighbor with a node that does not have a common
area address. However, if a Level 1 router has area addresses A, B, and C, and a neighbor has area
addresses B and D, then the Level 1 router will accept the other node as a neighbor, as address B is
common to both routers. Level 2 adjacencies are formed with other Level 2 nodes whose area
addresses do not overlap. If the area addresses do not overlap, the link is considered by both
routers to be Level 2 only and only Level 2 LSPDUs flow on the link.
Within an area, Level 1 routers exchange LSPs which identify the IP addresses reachable by each
router. Specifically, zero or more IP address, subnet mask, and metric combinations can be
included in each LSP. Each Level 1 router is manually configured with the IP address, subnet
mask, and metric combinations, which are reachable on each interface. A Level 1 router routes as
follows:
•
If a specified destination address matches an IP address, subnet mask, or metric reachable
within the area, the PDU is routed via Level 1 routing.
•
If a specified destination address does not match any IP address, subnet mask, or metric
combinations listed as reachable within the area, the PDU is routed towards the nearest
Level 2 router.
7210 SAS M, X OS Routing Protocols Guide
Page 153
Configuring IS-IS
Level 2 routers include in their LSPs, a complete list of IP address, subnet mask, and metrics
specifying all the IP addresses which reachable in their area. This information can be obtained
from a combination of the Level 1 LSPs (by Level 1 routers in the same area). Level 2 routers can
also report external reachability information, corresponding to addresses reachable by routers in
other routing domains or autonomous systems.
Page 154
7210 SAS M, X OS Routing Protocols Guide
IS-IS
IS-IS Frequently Used Terms
•
Area — An area is a routing sub-domain which maintains detailed routing information
about its own internal composition, and also maintains routing information which allows it
to reach other routing sub-domains. Areas correspond to the Level 1 sub-domain.
•
End system — End systems send NPDUs to other systems and receive NPDUs from other
systems, but do not relay NPDUs. This International Standard does not specify any
additional end system functions beyond those supplied by ISO 8473 and ISO 9542.
•
Neighbor — A neighbor is an adjacent system reachable by traversing a single subnetwork by a PDU.
•
Adjacency — An adjacency is a portion of the local routing information which pertains to
the reachability of a single neighboring end or intermediate system over a single circuit.
Adjacencies are used as input to the decision process to form paths through the routing
domain. A separate adjacency is created for each neighbor on a circuit and for each level
of routing (Level 1 and Level 2) on a broadcast circuit.
•
Circuit — The subset of the local routing information base pertinent to a single local
Subnetwork Point of Attachments (SNPAs).
•
Link — The communication path between two neighbors. A link is up when
communication is possible between the two SNPAs.
•
Designated IS — The intermediate system on a LAN which is designated to perform
additional duties. In particular, the designated IS generates link-state PDUs on behalf of
the LAN, treating the LAN as a pseudonode.
•
Pseudonode — Where a broadcast sub-network has n connected intermediate systems, the
broadcast sub-network itself is considered to be a pseudonode. The pseudonode has links
to each of the n intermediate systems and each of the ISs has a single link to the
pseudonode (rather than n-1 links to each of the other intermediate systems). Link-state
PDUs are generated on behalf of the pseudonode by the designated IS.
•
Broadcast sub-network — A multi-access subnetwork that supports the capability of
addressing a group of attached systems with a single PDU.
•
General topology sub-network — A topology that is modeled as a set of point-to-point
links, each of which connects two systems. There are several generic types of general
topology subnetworks, multipoint links, permanent point-to-point links, dynamic and
static point-to-point links.
•
Routing sub-domain — A routing sub-domain consists of a set of intermediate systems
and end systems located within the same routing domain.
•
Level 2 sub-domain — Level 2 sub-domain is the set of all Level 2 intermediate systems
in a routing domain.
7210 SAS M, X OS Routing Protocols Guide
Page 155
Configuring IS-IS
ISO Network Addressing
IS-IS uses ISO network addresses. Each address identifies a point of connection to the
network, such as a router interface, and is called a Network Service Access Point (NSAP).
An end system can have multiple NSAP addresses, in which case the addresses differ only
by the last byte (called the n-selector). Each NSAP represents a service that is available at
that node. In addition to having multiple services, a single node can belong to multiple
areas.
Each network entity has a special network address called a Network Entity Title (NET).
Structurally, an NET is identical to an NSAP address but has an n-selector of 00. Most end
systems have one NET. Intermediate systems can have up to three area IDs (area
addresses).
NSAP addresses are divided into three parts. Only the area ID portion is configurable.
•
Area ID — A variable length field between 1 and 13 bytes long. This includes the
Authority and Format Identifier (AFI) as the most significant byte and the area ID.
•
System ID — A six-byte system identification. This value is not configurable. The
system ID is derived from the system or router ID.
•
Selector ID — A one-byte selector identification that must contain zeros when
configuring a NET. This value is not configurable. The selector ID is always 00.
Of the total 20 bytes comprising the NET, only the first 13 bytes, the area ID portion, can
be manually configured. As few as one byte can be entered or, at most, 13 bytes. If less
than 13 bytes are entered, the rest is padded with zeros.
Routers with common area addresses form Level 1 adjacencies. Routers with no common
NET addresses form Level 2 adjacencies, if they are capable (Figure 4).
Page 156
7210 SAS M, X OS Routing Protocols Guide
IS-IS
L1
L 1/2
L 1/2
area 47.0001
area 48.0001
area 49.0001
area 45.0001
area 46.0001
area 95.0001
L 1/2
area 47.0001
area 32.0001
area 34.0001
area 45.0001
area 28.0001
area 29.0001
L1
area 29.0001
area 50.0001
area 51.0001
L 1/2
area 80.0001
area 79.0001
area 78.0001
L 1/2
area 49.0001
area 80.0001
area 51.0001
L 1/2
area 30.0001
area 31.0001
area 32.0001
L 1/2
area 49.0001
area 87.0001
area 86.0001
OSRG034
Figure 4: Using Area Addresses to Form Adjacencies
7210 SAS M, X OS Routing Protocols Guide
Page 157
Configuring IS-IS
IS-IS PDU Configuration
The following PDUs are used by IS-IS to exchange protocol information:
•
IS-IS hello PDU — Routers with IS-IS enabled send hello PDUs to IS-IS-enabled
interfaces to discover neighbors and establish adjacencies.
•
Link-state PDUs — Contain information about the state of adjacencies to neighboring ISIS systems. LSPs are flooded periodically throughout an area.
•
Complete sequence number PDUs — In order for all routers to maintain the same
information, CSNPs inform other routers that some LSPs can be outdated or missing from
their database. CSNPs contain a complete list of all LSPs in the current IS-IS database.
•
Partial sequence number PDUs (PSNPs) — PSNPs are used to request missing LSPs and
acknowledge that an LSP was received.
IS-IS Operations
Routers perform IS-IS routing as follows:
Page 158
•
Hello PDUs are sent to the IS-IS-enabled interfaces to discover neighbors and establish
adjacencies.
•
IS-IS neighbor relationships are formed if the hello PDUs contain information that meets
the criteria for forming an adjacency.
•
Routers can build a link-state PDU based upon their local interfaces that are configured for
IS-IS and prefixes learned from other adjacent routers.
•
Routers flood LSPs to the adjacent neighbors except the neighbor from which they
received the same LSP. The link-state database is constructed from these LSPs.
•
A Shortest Path Tree (SPT) is calculated by each IS, and from this SPT the routing table is
built.
7210 SAS M, X OS Routing Protocols Guide
IS-IS
IS-IS Route Summarization
IS-IS IPv4 route summarization allows users to create aggregate IPv4 addresses that include
multiple groups of IPv4 addresses for a given IS-IS level. IPv4 Routes redistributed from other
routing protocols also can be summarized. It is similar to the OSPF area-range command. IS-IS
IPv4 route summarization helps to reduce the size of the LSDB and the IPv4 routing table, and it
also helps to reduce the chance of route flapping.
IPv4 route summarization supports:
•
Level 1, Level 1-2, and Level 2
•
Route summarization for the IPv4 routes redistributed from other protocols
•
Metric used to advertise the summary address will be the smallest metric of all the more
specific IPv4 routes.
7210 SAS M, X OS Routing Protocols Guide
Page 159
Configuring IS-IS
IS-IS Administrative Tags
IS-IS admin tags enable a network administrator to configure route tags to tag IS-IS route prefixes.
These tags can subsequently be used to control Intermediate System-to-Intermediate System (ISIS) route redistribution or route leaking.
The IS-IS support for route tags allows the tagging of IP addresses of an interface and use the tag
to apply administrative policy with a route map. A network administrator can also tag a summary
route and then use a route policy to match the tag and set one or more attributes for the route.
Using these administrative policies allow the operator to control how a router handles the routes it
receives from and sends to its IS-IS neighboring routers. Administrative policies are also used to
govern the installation of routes in the routing table.
Route tags allow:
•
Policies to redistribute routes received from other protocols in the routing table to IS-IS.
•
Policies to redistribute routes between levels in an IS-IS routing hierarchy.
•
Policies to summarize routes redistributed into IS-IS or within IS-IS by creating aggregate
(summary) addresses.
Setting Route Tags
IS-IS route tags are configurable in the following ways:
Page 160
•
Setting a route tag for an IS-IS interface.
•
Setting a route tag on an IS-IS passive interface.
•
Setting a route tag for a route redistributed from another protocol to IS-IS.
•
Setting a route tag for a route redistributed from one IS-IS level to another IS-IS level.
•
Setting a route tag for an IS-IS default route.
•
Setting a route tag for an IS-IS summary address.
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Using Route Tags
Although an operator on this or another (neighboring) IS-IS router has configured setting of the ISIS administrative tags it will not have any effect unless policies are configure to instruct how to
process the given tag value.
Policies can process tags where ISIS is either the origin, destination or both origin and destination
protocol.
config>router>policy-options>policy-statement>entry>from
config>router>policy-options>policy-statement>entry>action tag tag-value
config>router>policy-options>policy-statement# default-action tag tag-value
7210 SAS M, X OS Routing Protocols Guide
Page 161
IS-IS Configuration Process Overview
IS-IS Configuration Process Overview
Figure 5 displays the process to provision basic IS-IS parameters.
START
ENABLE IS-IS
CONFIGURE GLOBAL PARAMETERS
SPECIFY AREA ADDRESSES
MODIFY LEVEL-CAPABILITY (OPTIONAL)
CONFIGURE INTERFACE PARAMETERS
ENABLE
Figure 5: IS-IS Configuration and Implementation Flow
Page 162
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Configuration Notes
This section describes IS-IS configuration caveats.
General
•
IS-IS must be enabled on each participating routers.
•
There are no default network entity titles.
•
There are no default interfaces.
•
By default, routers are assigned a Level 1/Level 2 level capability.
7210 SAS M, X OS Routing Protocols Guide
Page 163
Configuration Notes
Page 164
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Configuring IS-IS with CLI
This section provides information to configure intermediate-system-to-intermediate-system (ISIS) using the command line interface.
Topics in this section include:
•
IS-IS Configuration Overview on page 166
→ Router Levels on page 166
→ Area Address Attributes on page 166
→ Interface Level Capability on page 167
→ Route Leaking on page 168
•
Basic IS-IS Configuration on page 169
•
Common Configuration Tasks on page 171
→ Enabling IS-IS on page 172
→ Modifying Router-Level Parameters on page 172
→ Configuring ISO Area Addresses on page 174
→ Configuring Global IS-IS Parameters on page 175
→ Configuring Interface Parameters on page 176
•
IS-IS Configuration Management Tasks on page 181
→ Disabling IS-IS on page 181
→ Modifying Global IS-IS Parameters on page 182
→ Modifying IS-IS Interface Parameters on page 183
→ Example: Configuring a Level 1 Area on page 178
→ Example: Modifying a Router’s Level Capability on page 180
→ Configuring Leaking on page 185
→ Redistributing External IS-IS Routers on page 188
→ Specifying MAC Addresses for All IS-IS Routers on page 189
7210 SAS M, X OS Routing Protocols Guide
Page 165
IS-IS Configuration Overview
IS-IS Configuration Overview
Router Levels
The router’s level capability can be configured globally and on a per-interface basis. The interfacelevel parameters specify the interface’s routing level. The neighbor capability and parameters
define the adjacencies that are established.
IS-IS is not enabled by default. When IS-IS is enabled, the global default level capability is Level
1/2 which enables the router to operate as either a Level 1 and/or a Level 2 router with the
associated databases. The router runs separate shortest path first (SPF) calculations for the Level 1
area routing and for the Level 2 multi-area routing to create the IS-IS routing table.
The level value can be modified on both or either of the global and interface levels to be only Level
1-capable, only Level 2-capable or Level 1 and Level 2-capable.
If the default value is not modified on any routers in the area, then the routers try to form both
Level 1 and Level 2 adjacencies on all IS-IS interfaces. If the default values are modified to Level
1 or Level 2, then the number of adjacencies formed are limited to that level only.
Area Address Attributes
The area-id command specifies the area address portion of the NET which is used to define the
IS-IS area to which the router will belong. At least one area-id command should be configured
on each router participating in IS-IS. A maximum of three area-id commands can be configured
per router.
The area address identifies a point of connection to the network, such as a router interface, and is
called a network service access point (NSAP). The routers in an area manage routing tables about
destinations within the area. The Network Entity Title (NET) value is used to identify the IS-IS
area to which the router belongs.
NSAP addresses are divided into three parts. Only the Area ID portion is configurable.
1. Area ID — A variable length field between 1 and 13 bytes long. This includes the Authority
and Format Identifier (AFI) as the most significant byte and the area ID.
2. System ID — A six-byte system identification. This value is not configurable. The system
ID is derived from the system or router ID.
3. Selector ID — A one-byte selector identification that must contain zeros when configuring
a NET. This value is not configurable. The selector ID is always 00.
Page 166
7210 SAS M, X OS Routing Protocols Guide
IS-IS
The following example displays ISO addresses in IS-IS address format:
MAC address 00:a5:c7:6b:c4:90
IP address: 218.112.14.5
49.0011.00a5.c76b.c490.00
49.0011.2181.1201.4005.00
Interface Level Capability
The level capability value configured on the interface level is compared to the level capability
value configured on the global level to determine the type of adjacencies that can be established.
The default level capability for routers and interfaces is Level 1/2.
Table 5 displays configuration combinations and the potential adjacencies that can be formed.
Table 5: Potential Adjacency Capabilities
Global Level
Interface Level
Potential Adjacency
L 1/2
L 1/2
Level 1 and/or Level 2
L 1/2
L1
Level 1 only
L 1/2
L2
Level 2 only
L2
L 1/2
Level 2 only
L2
L2
Level 2 only
L2
L1
none
L1
L 1/2
Level 1 only
L1
L2
none
L1
L1
Level 1 only
7210 SAS M, X OS Routing Protocols Guide
Page 167
IS-IS Configuration Overview
Route Leaking
Alcatel-Lucent’s implementation of IS-IS route leaking is performed in compliance with RFC
2966, Domain-wide Prefix Distribution with Two-Level IS-IS. As previously stated, IS-IS is a
routing domain (an autonomous system running IS-IS) which can be divided into Level 1 areas
with a Level 2-connected subset (backbone) of the topology that interconnects all of the Level 1
areas. Within each Level 1 area, the routers exchange link state information. Level 2 routers also
exchange Level 2 link state information to compute routes between areas.
Routers in a Level 1 area typically only exchange information within the Level 1 area. For IP
destinations not found in the prefixes in the Level 1 database, the Level 1 router forwards PDUs to
the nearest router that is in both Level 1/Level 2 with the attached bit set in its Level 1 link-state
PDU.
There are many reasons to implement domain-wide prefix distribution. The goal of domain-wide
prefix distribution is to increase the granularity of the routing information within the domain. The
routing mechanisms specified in RFC 1195 are appropriate in many situations and account for
excellent scalability properties. However, in certain circumstances, the amount of scalability can
be adjusted which can distribute more specific information than described by RFC 1195.
Distributing more prefix information can improve the quality of the resulting routes. A well known
property of default routing is that loss of information can occur. This loss of information affects the
computation of a route based upon less information which can result in sub-optimal routes.
Page 168
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Basic IS-IS Configuration
For IS-IS to operate on routers, IS-IS must be explicitly enabled, and at least one area address and
interface must be configured. If IS-IS is enabled but no area address or interface is defined, the
protocol is enabled but no routes are exchanged. When at least one area address and interface are
configured, then adjacencies can be formed and routes exchanged.
To configure IS-IS, perform the following tasks:
•
Enable IS-IS.
•
If necessary, modify the level capability on the global level (default is level-1/2).
•
Define area address(es)
•
Configure IS-IS interfaces.
The following output displays IS-IS default values.
A:Dut-A>config>router>isis$ info detail
---------------------------------------------level-capability level-1/2
no graceful-restart
area-id 01
no authentication-key
no authentication-type
authentication-check
csnp-authentication
lsp-lifetime 1200
no export
hello-authentication
psnp-authentication
traffic-engineering
no reference-bandwidth
no disable-ldp-sync
ipv4-routing
spf-wait 10 1000 1000
lsp-wait 5 0 1
level 1
no authentication-key
no authentication-type
csnp-authentication
external-preference 160
hello-authentication
preference 15
psnp-authentication
no wide-metrics-only
exit
level 2
no authentication-key
no authentication-type
csnp-authentication
external-preference 165
hello-authentication
preference 18
7210 SAS M, X OS Routing Protocols Guide
Page 169
Basic IS-IS Configuration
psnp-authentication
no wide-metrics-only
exit
no shutdown
---------------------------------------------A:Dut-A>config>router>isis$
Page 170
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Common Configuration Tasks
To implement IS-IS in your network, you must enable IS-IS on each participating routers.
To assign different level capabilities to the routers and organize your network into areas, modify
the level capability defaults on end systems from Level 1/2 to Level 1. Routers communicating to
other areas can retain the Level 1/2 default.
On each router, at least one area ID also called the area address should be configured as well as at
least one IS-IS interface.
•
Enable IS-IS.
•
Configure global IS-IS parameters.
→ Configure area address(es).
•
Configure IS-IS interface-specific parameters.
7210 SAS M, X OS Routing Protocols Guide
Page 171
Configuring IS-IS Components
Configuring IS-IS Components
Use the CLI syntax displayed below for:
•
Enabling IS-IS on page 172
•
Modifying Router-Level Parameters on page 172
•
Configuring ISO Area Addresses on page 174
•
Configuring Global IS-IS Parameters on page 175
•
Configuring Interface Parameters on page 176
•
Example: Configuring a Level 1 Area on page 178
•
Example: Modifying a Router’s Level Capability on page 180
Enabling IS-IS
IS-IS must be enabled in order for the protocol to be active.
NOTE: Careful planning is essential to implement commands that can affect the behavior of
global and interface levels.
To configure IS-IS on a router, enter the following command:
CLI Syntax: isis
Example:
config>router# isis
Modifying Router-Level Parameters
When IS-IS is enabled, the default level-capability is Level 1/2. This means that the router
operates with both Level 1 and Level 2 routing capabilities. To change the default value in order
for the router to operate as a Level 1 router or a Level 2 router, you must explicitly modify the
level value.
If the level is modified, the protocol shuts down and restarts. Doing this can affect adjacencies and
routes.
The level-capability value can be configured on the global level and also on the interface
level. The level-capability value determines which level values can be assigned on the router
level or on an interface-basis.
Page 172
7210 SAS M, X OS Routing Protocols Guide
IS-IS
In order for the router to operate as a Level 1 only router or as a Level 2 only router, you must
explicitly specify the level-number value.
•
Select level-1 to route only within an area.
•
Select level-2 to route to destinations outside an area, toward other eligible Level 2
routers.
To configure the router level, enter the following commands:
CLI Syntax: config>router# isis
level-capability {level-1|level-2|level-1/2}
level {1|2}
Example:
config>router# isis
config>router>isis# level-capability 1/2
config>router>isis# level 2
The following example displays the configuration:
A:ALA-A>config>router>isis# info
#-----------------------------------------echo "ISIS"
#-----------------------------------------level-capability level-1/2
level 2
---------------------------------------------A:ALA-A>config>router>isis#
7210 SAS M, X OS Routing Protocols Guide
Page 173
Configuring IS-IS Components
Configuring ISO Area Addresses
Use the following CLI syntax to configure an area ID also called an address. A maximum of 3
area-id can be configured.
CLI Syntax: config>router# isis
area-id area-address
The following example configures the router’s area ID:
Example:config>router>isis#
config>router>isis# area-id 49.0180.0001
config>router>isis# area-id 49.0180.0002
config>router>isis# area-id 49.0180.0003
The following example displays the area ID configuration:
A:ALA-A>config>router>isis# info
---------------------------------------------area-id 49.0180.0001
area-id 49.0180.0002
area-id 49.0180.0003
---------------------------------------------A:ALA-A>config>router>isis#
Page 174
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Configuring Global IS-IS Parameters
Commands and parameters configured on the global level are inherited to the interface levels.
Parameters specified in the interface and interface-level configurations take precedence over
global configurations.
The following example displays global-level IS-IS configuration command usage:
Example: config>router# isis
config>router>isis#
config>router>isis#
config>router>isis#
config>router>isis#
config>router>isis#
config>router>isis#
config>router>isis#
level-capability level-2
authentication-check
authentication-type password
authentication-key test
overload timeout 90
traffic-engineering
The following example displays the modified global-level configuration.
A:ALA-A>config>router>isis# info
---------------------------------------------level-capability level-2
area-id 49.0180.0001
area-id 49.0180.0002
area-id 49.0180.0003
authentication-key "H5KBAWrAAQU" hash
authentication-type password
overload timeout 90
traffic-engineering
---------------------------------------------A:ALA-A>config>router>isis#
7210 SAS M, X OS Routing Protocols Guide
Page 175
Configuring IS-IS Components
Configuring Interface Parameters
There are no interfaces associated with IS-IS by default. An interface belongs to all areas
configured on a router. Interfaces cannot belong to separate areas. There are no default interfaces
applied to the router’s IS-IS instance. You must configure at least one IS-IS interface in order for
IS-IS to work.
To enable IS-IS on an interface, first configure an IP interface in the config>router>
interface context. Then, apply the interface in the config>router>isis>interface
context.
You can configure both the Level 1 parameters and the Level 2 parameters on an interface. The
level-capability value determines which level values are used.
NOTE: For point-to-point interfaces, only the values configured under Level 1 are used regardless
of the operational level of the interface.
The following example displays the modified interface parameters:
Example: config>router# isis
config>router>isis# level 1
config>router>isis>level# wide-metrics-only
config>router>isis>level# exit
config>router>isis# level 2
config>router>isis>level# wide-metrics-only
config>router>isis>level# exit
config>router>isis# interface ALA-1-2
config>router>isis>if# level-capability level-2
config>router>isis>if# mesh-group 85
config>router>isis>if# exit
config>router>isis# interface ALA-1-3
config>router>isis>if# level-capability level-1
config>router>isis>if# interface-type point-to-point
config>router>isis>if# mesh-group 101
config>router>isis>if# exit
config>router>isis# interface ALA-1-5
config>router>isis>if# level-capability level-1
config>router>isis>if# interface-type point-to-point
config>router>isis>if# mesh-group 85
config>router>isis>if# exit
config>router>isis# interface to-103
config>router>isis>if# level-capability level-1/2
>router>isis>if# mesh-group 101
config>router>isis>if# exit
config>router>isis#
Page 176
7210 SAS M, X OS Routing Protocols Guide
IS-IS
The following example displays the global and interface-level configurations.
A:ALA-A>config>router>isis# info
---------------------------------------------level-capability level-2
area-id 49.0180.0001
area-id 49.0180.0002
area-id 49.0180.0003
authentication-key "H5KBAWrAAQU" hash
authentication-type password
traffic-engineering
level 1
wide-metrics-only
exit
level 2
wide-metrics-only
exit
interface "system"
exit
interface "ALA-1-2"
level-capability level-2
mesh-group 85
exit
interface "ALA-1-3"
level-capability level-1
interface-type point-to-point
mesh-group 101
exit
interface "ALA-1-5"
level-capability level-1
interface-type point-to-point
mesh-group 85
exit
interface "to-103"
mesh-group 101
exit
---------------------------------------------A:ALA-A>config>router>isis#
7210 SAS M, X OS Routing Protocols Guide
Page 177
Configuring IS-IS Components
Example: Configuring a Level 1 Area
NOTE: Interfaces are configured in the config>router>interface context.
Area A (ALA-A)
Area B (ALA-B)
Area-ID 49.0180.0001
Area-ID 49.0180.0001
L1
L1
Area C (ALA-C)
Area-ID 49.0180.0001
L1
OSRG031
Figure 6: Configuring a Level 1 Area
The following example displays the command usage to configure a Level 1 area.
A:ALA-A>config>router# isis
A:ALA-A>config>router>isis# area-id 47.0001
A:ALA-A>config>router>isis# level-capability level-1
A:ALA-A>config>router>isis# interface system
A:ALA-A>config>router>isis>if# exit
A:ALA-A>config>router>isis# interface A-B
A:ALA-A>config>router>isis>if# exit
A:ALA-A>config>router>isis# interface A-C
A:ALA-A>config>router>isis>if# exit
A:ALA-A>config>router>isis#
A:ALA-B>config>router# isis
A:ALA-B>config>router>isis# area-id 47.0001
A:ALA-B>config>router>isis# level-capability level-1
A:ALA-B>config>router>isis# interface system
A:ALA-B>config>router>isis>if# exit
A:ALA-B>config>router>isis# interface B-A
A:ALA-B>config>router>isis>if# exit
A:ALA-B>config>router>isis# interface B-C
A:ALA-B>config>router>isis>if# exit
A:ALA-B>config>router>isis#
A:ALA-C>config>router# isis
A:ALA-C>config>router>isis# area-id 47.0001
A:ALA-C>config>router>isis# level-capability level-1
A:ALA-C>config>router>isis# interface system
Page 178
7210 SAS M, X OS Routing Protocols Guide
IS-IS
A:ALA-C>config>router>isis>if# exit
A:ALA-C>config>router>isis# interface "C-A"
A:ALA-C>config>router>isis>if# exit
A:ALA-C>config>router>isis# interface "C-B"
A:ALA-C>config>router>isis>if# exit
A:ALA-A>config>router>isis# info
---------------------------------------------level-capability level-1
area-id 49.0180.0001
interface "system"
exit
interface "A-B"
exit
interface "A-C"
exit
---------------------------------------------A:ALA-A>config>router>isis#
A:ALA-B>config>router>isis# info
---------------------------------------------level-capability level-1
area-id 49.0180.0001
interface "system"
exit
interface "B-A"
exit
interface "B-C"
exit
---------------------------------------------A:ALA-B>config>router>isis#
A:ALA-C>config>router>isis# info
#-----------------------------------------echo "ISIS"
---------------------------------------------level-capability level-1
area-id 49.0180.0001
interface "system"
exit
interface "C-A"
exit
interface "C-B"
exit
---------------------------------------------A:ALA-C>config>router>isis#
7210 SAS M, X OS Routing Protocols Guide
Page 179
Configuring IS-IS Components
Example: Modifying a Router’s Level Capability
In the previous example, ALA-A, ALA-B, and ALA-C are configured as Level 1 systems. Level 1
systems communicate with other Level 1 systems in the same area. In this example, ALA-A is
modified to set the level capability to Level 1/2. Now, the Level 1 systems in the area with NET
47.0001 forward PDUs to ALA-A for destinations that are not in the local area.
L2
L1/2
Area A (ALA-A)
Area B (ALA-B)
Area-ID 49.0180.0001
Area-ID 49.0180.0001
L1/2
L1
Area C (ALA-C)
Area-ID 49.0180.0001
L1
OSRG036
Figure 7: Configuring a Level 1/2 Area
The following example displays the command usage to configure a Level 1/2 system.
A:ALA-A>config>router# isis
A:ALA-A>config>router>isis# level-capability level-1/2
Page 180
7210 SAS M, X OS Routing Protocols Guide
IS-IS
IS-IS Configuration Management Tasks
This section discusses the following IS-IS configuration management tasks:
•
Disabling IS-IS on page 181
•
Removing IS-IS on page 181
•
Modifying Global IS-IS Parameters on page 182
•
Modifying IS-IS Interface Parameters on page 183
→ Example: Configuring a Level 1 Area on page 178
→ Example: Modifying a Router’s Level Capability on page 180
•
Configuring Leaking on page 185
•
Redistributing External IS-IS Routers on page 188
•
Specifying MAC Addresses for All IS-IS Routers on page 189
Disabling IS-IS
The shutdown command disables the IS-IS protocol instance on the router. The configuration
settings are not changed, reset, or removed.
To disable IS-IS on a router, enter the following commands:
CLI Syntax: config>router# isis
shutdown
Removing IS-IS
The no isis command deletes the IS-IS protocol instance. The IS-IS configuration reverts to the
default settings.
To remove the IS-IS configuration enter the following commands:
CLI Syntax: config>router#
no isis
7210 SAS M, X OS Routing Protocols Guide
Page 181
IS-IS Configuration Management Tasks
Modifying Global IS-IS Parameters
You can modify, disable, or remove global IS-IS parameters without shutting down entities.
Changes take effect immediately. Modifying the level capability on the global level causes the ISIS protocol to restart.
The following example displays command usage to modify various parameters:
Example:
config>router>isis# overload timeout 500
config>router>isis# level-capability level-1/2
config>router>isis# no authentication-check
config>router>isis# authentication-key raiderslost
The following example displays the global modifications
A:ALA-A>config>router>isis# info
---------------------------------------------area-id 49.0180.0001
area-id 49.0180.0002
area-id 49.0180.0003
authentication-key "//oZrvtvFPn06S42lRIJsE" hash
authentication-type password
no authentication-check
overload timeout 500 on-boot
level 1
wide-metrics-only
exit
level 2
wide-metrics-only
exit
interface "system"
exit
interface "ALA-1-2"
level-capability level-2
mesh-group 85
exit
interface "ALA-1-3"
level-capability level-1
interface-type point-to-point
mesh-group 101
exit
interface "ALA-1-5"
level-capability level-1
interface-type point-to-point
mesh-group 85
exit
interface "to-103"
mesh-group 101
exit
interface "A-B"
exit
interface "A-C"
exit
---------------------------------------------A:ALA-A>config>router>isis#
Page 182
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Modifying IS-IS Interface Parameters
You can modify, disable, or remove interface-level IS-IS parameters without shutting down
entities. Changes take effect immediately. Modifying the level capability on the interface causes
the IS-IS protocol on the interface to restart.
To remove an interface, issue the no interface ip-int-name command.
To disable an interface, issue the shutdown command in the interface context.
The following example displays interface IS-IS modification command usage:
Example:config>router# isis
config>router>isis# interface ALA-1-3
config>router>isis>if# mesh-group 85
config>router>isis>if# passive
config>router>isis>if# lsp-pacing-interval 5000
config>router>isis>if# exit
config>router>isis# interface to-103
config>router>isis>if# hello-authentication-type message-digest
config>router>isis>if# hello-authentication-key 49ersrule
config>router>isis>if# exit
The following example displays the modified interface parameters.
A:ALA-A>config>router>isis# info
---------------------------------------------area-id 49.0180.0001
area-id 49.0180.0002
area-id 49.0180.0003
authentication-key "//oZrvtvFPn06S42lRIJsE" hash
authentication-type password
no authentication-check
overload timeout 500 on-boot
level 1
wide-metrics-only
exit
level 2
wide-metrics-only
exit
interface "system"
exit
interface "ALA-1-2"
level-capability level-2
mesh-group 85
exit
interface "ALA-1-3"
level-capability level-1
interface-type point-to-point
lsp-pacing-interval 5000
mesh-group 85
passive
exit
interface "ALA-1-5"
7210 SAS M, X OS Routing Protocols Guide
Page 183
IS-IS Configuration Management Tasks
level-capability level-1
interface-type point-to-point
mesh-group 85
exit
interface "to-103"
hello-authentication-key "DvR3l264KQ6vXMTvbAZ1mE" hash
hello-authentication-type message-digest
mesh-group 101
exit
interface "A-B"
exit
---------------------------------------------A:ALA-A>config>router>isis#
Page 184
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Configuring Leaking
IS-IS allows a two-level hierarchy to route PDUs. Level 1 areas can be interconnected by a
contiguous Level 2 backbone.
The Level 1 link-state database contains information only about that area. The Level 2 link-state
database contains information about the Level 2 system and each of the Level 1 systems in the
area. A Level 1/2 router contains information about both Level 1 and Level 2 databases. A Level 1/
2 router advertises information about its Level 1 area toward the other Level 1/2 or Level 2 (only)
routers.
Packets with destinations outside the Level 1 area are forwarded toward the closest Level 1/2
router which, in turn, forwards the packets to the destination area.
Sometimes, the shortest path to an outside destination is not through the closest Level 1/2 router,
or, the only Level 1/2 system to forward packets out of an area is not operational. Route leaking
provides a mechanism to leak Level 2 information to Level 1 systems to provide routing
information regarding inter-area routes. Then, a Level 1 router has more options to forward
packets.
Configure a route policy to leak routers from Level 2 into Level 1 areas in the
config>router>policy-options>policy-statement context.
The following example shows the command usage to configure prefix list and policy statement
parameters in the config>router context.
config>router>policy-options# prefix-list loops
..>policy-options>prefix-list# prefix 10.1.1.0/24 longer
..>policy-options>prefix-list# exit
..>policy-options# policy-statement leak
..>policy-options>policy-statement# entry 10
..>policy-options>policy-statement>entry# from
..>policy-options>policy-statement>entry>from# prefix-list loops
..>policy-options>policy-statement>entry>from# level 2
..>policy-options>policy-statement>entry>from# exit
..>policy-options>policy-statement>entry# to
..>policy-options>policy-statement>entry>to# level 1
..>policy-options>policy-statement>entry>to# exit
..>policy-options>policy-statement>entry# action accept
..>policy-options>policy-statement>entry>action# exit
..>policy-options>policy-statement>entry# exit
..>policy-options>policy-statement#exit
..>policy-options# commit
..>policy-options#
7210 SAS M, X OS Routing Protocols Guide
Page 185
IS-IS Configuration Management Tasks
A:ALA-A>config>router>policy-options# info
---------------------------------------------prefix-list "loops"
prefix 10.1.1.0/24 longer
exit
policy-statement "leak"
entry 10
from
prefix-list "loop"
level 2
exit
to
level 1
exit
action accept
exit
exit
exit
---------------------------------------------A:ALA-A>config>router>policy-options#
Next, apply the policy to leak routes from Level 2 info Level 1 systems on ALA-A.
config>router#isis
config>router>isis# export leak
A:ALA-A>config>router>isis# info
---------------------------------------------area-id 49.0180.0001
area-id 49.0180.0002
area-id 49.0180.0003
authentication-key "//oZrvtvFPn06S42lRIJsE" hash
authentication-type password
no authentication-check
export "leak"
...
---------------------------------------------A:ALA-A>config>router>isis#
Page 186
7210 SAS M, X OS Routing Protocols Guide
IS-IS
After the policy is applied, create a policy to redistribute external IS-IS routes from Level 1
systems into the Level 2 backbone (see Redistributing External IS-IS Routers on page 188). In the
config>router context, configure the following policy statement parameters:
config>router>policy-options# begin
..>policy-options# policy-statement "isis-ext"
..>policy-options>policy-statement# entry 10
..>policy-options>policy-statement>entry$ from
..>policy-options>policy-statement>entry>from$ external
..>policy-options>policy-statement>entry>from# exit
..>policy-options>policy-statement>entry# to
..>policy-options>policy-statement>entry>to$ level 2
..>policy-options>policy-statement>entry>to# exit
..>policy-options>policy-statement>entry# action accept
..>policy-options>policy-statement>entry>action# exit
..>policy-options>policy-statement>entry# exit
..>policy-options>policy-statement# exit
..>policy-options# commit
A:ALA-A>config>router>policy-options# info
---------------------------------------------prefix-list "loops"
prefix 10.1.1.0/24 longer
exit
policy-statement "leak"
entry 10
from
prefix-list "loop"
level 2
exit
to
level 1
exit
action accept
exit
exit
exit
policy-statement "isis-ext"
entry 10
from
external
exit
to
level 2
exit
action accept
exit
exit
exit
---------------------------------------------A:ALA-A>config>router>policy-options#
7210 SAS M, X OS Routing Protocols Guide
Page 187
IS-IS Configuration Management Tasks
Redistributing External IS-IS Routers
IS-IS does not redistribute Level 1 external routes into Level 2 by default. You must explicitly
apply the policy to redistribute external IS-IS routes. Policies are created in the
config>router>policy-options context. Refer to the Route Policy section of this manual for
more information.
The following example displays the policy statement configuration.
config>router>policy-options# info
---------------------------------------------prefix-list "loops"
prefix 10.1.1.0/24 longer
exit
policy-statement "leak"
entry 10
from
prefix-list "loop"
level 2
exit
to
level 1
exit
action accept
exit
exit
exit
policy-statement "isis-ext"
entry 10
from
external
exit
to
level 2
exit
action accept
exit
exit
exit
---------------------------------------------config>router>policy-options#
Page 188
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Specifying MAC Addresses for All IS-IS Routers
Specify the MAC address to use for all L1 or L2 IS-IS routers. The following example shows how
to specify all L1 routers:
Example: all-l1isis 01-80-C2-00-00-14
You can also specify the MAC address for all L2 IS-IS routers by using the all-l2isis command.
7210 SAS M, X OS Routing Protocols Guide
Page 189
IS-IS Configuration Management Tasks
Page 190
7210 SAS M, X OS Routing Protocols Guide
IS-IS
IS-IS Command Reference
Command Hierarchies
Configuration Commands
• Global Commands on page 191
• Interface Commands on page 192
• Show Commands on page 193
• Clear Commands on page 193
• Debug Commands on page 193
—Global Commands
config
— router
— [no] isis [instance-id]
— [no] area-id area-address
— [no] authentication-check
— authentication-key [authentication-key | hash-key] [hash | hash2]
— no authentication-key
— authentication-type {password | message-digest}
— no authentication-type
— [no] csnp-authentication
— [no] disable-ldp-sync
— export policy-name [.. policy-name]
— no export
— [no] graceful-restart
— [no] helper-disable
— [no] hello-authentication
— level {1 | 2}
— authentication-key [authentication-key | hash-key] [hash | hash2]
— no authentication-key
— authentication-type {password | message-digest}
— no authentication-type
— [no] csnp-authentication
— external-preference external-preference
— no external-preference
— [no] hello-authentication
— preference preference
— no preference
— [no] psnp-authentication
— [no] wide-metrics-only
— level-capability {level-1 | level-2 | level-1/2}
— lsp-lifetime seconds
— no lsp-lifetime
— [no] lsp-wait lsp-wait [lsp-initial-wait [lsp-second-wait]]
— overload [timeout seconds]
7210 SAS M, X OS Routing Protocols Guide
Page 191
Configuration Commands
—Interface Commands
Page 192
—
—
—
—
—
—
—
—
—
—
—
—
—
no overload
overload-on-boot [timeout seconds]
no overload-on-boot
[no] psnp-authentication
reference-bandwidth reference-bandwidth
no reference-bandwidth
[no] shutdown
[no] spf-wait spf-wait [spf-initial-wait [spf-second-wait]]
[no] suppress-default
summary-address {ip-prefix/mask | ip-prefix [netmask]} level
no summary-address {ip-prefix/mask | ip-prefix [netmask]}
[no] traffic-engineering
[no] interface ip-int-name
— [no] bfd-enable {ipv4}
— csnp-interval seconds
— no csnp-interval
— hello-authentication-key [authentication-key | hash-key][hash | hash2]
— no hello-authentication-key
— hello-authentication-type {password | message-digest}
— no hello-authentication-type
— interface-type {broadcast | point-to-point}
— no interface-type
— level {1 | 2}
— hello-authentication-key [authentication-key | hash-key] [hash |
hash2]
— no hello-authentication-key
— hello-authentication-type [password | message-digest]
— no hello-authentication-type
— hello-interval seconds
— no hello-interval
— hello-multiplier multiplier
— no hello-multiplier
— metric ipv4-metric
— no metric
— [no] passive
— priority number
— no priority
— level-capability {level-1 | level-2 | level-1/2}
— lsp-pacing-interval milli-seconds
— no lsp-pacing-interval
— mesh-group [value | blocked]
— no mesh-group
— [no] passive
— retransmit-interval seconds
— no retransmit-interval
— [no] shutdown
7210 SAS M, X OS Routing Protocols Guide
IS-IS
—Show Commands
Show Commands
show
— router
— isis
—
—
—
—
—
—
—
—
—
—
adjacency [ip-address | ip-int-name | nbr-system-id] [detail]
database [system-id | lsp-id ] [detail] [level level]
hostname
interface [ip-int-name | ip-address] [detail]
routes [ipv4-unicast]
spf [detail]
spf-log [detail]
statistics
status
summary-address [ip-prefix[/prefix-length]]
—
—
—
—
—
adjacency [system-id]
database [system-id]
export
spf-log
statistics
—
—
—
—
—
—
—
—
—
—
—
—
—
[no] adjacency [ip-int-name | ip-address | nbr-system-id]
[no] cspf
[no] graceful-restart
interface [ip-int-name | ip-address]
no interface
leak [ip-address]
no leak
[no] lsdb [level-number] [system-id | lsp-id]
[no] misc
packet [packet-type] [ip-int-name | ip-address] [detail]
rtm [ip-address]
no rtm
[no] spf [level-number] [system-id]
Clear Commands
—Clear Commands
clear
— router
— isis ]
Debug Commands
debug
— router
— isis
7210 SAS M, X OS Routing Protocols Guide
Page 193
Debug Commands
Page 194
7210 SAS M, X OS Routing Protocols Guide
IS-IS
IS-IS Configuration Commands
Generic Commands
isis
Syntax
Context
Description
isis
no isis
config>router
This command creates the context to configure the Intermediate-System-to-Intermediate-System (IS-IS)
protocol instance.
The IS-IS protocol instance is enabled with the no shutdown command in the config>router>isis context.
Alternatively, the IS-IS protocol instance is disabled with the shutdown command in the config>router>isis
context.
The no form of the command deletes the IS-IS protocol instance. Deleting the protocol instance removes all
configuration parameters for this IS-IS instance.
shutdown
Syntax
Context
Description
[no] shutdown
config>router>isis
config>router>isis>interface ip-int-name
config>router>isis>if>level level-number
This command administratively disables an entity. When disabled, an entity does not change, reset, or
remove any configuration settings or statistics.
The operational state of the entity is disabled as well as the operational state of any entities contained within.
Many objects must be shut down before they may be deleted.
The no form of this command administratively enables an entity.
Special Cases
IS-IS Global — In the config>router>isis context, the shutdown command disables the IS-IS protocol
instance. By default, the protocol is enabled, no shutdown.
IS-IS Interface — In the config>router>isis>interface context, the command disables the IS-IS interface.
By default, the IS-IS interface is enabled, no shutdown.
IS-IS Interface and Level — In the config>router>isis>interface ip-int-name>level context, the command disables the IS-IS interface for the level. By default, the IS-IS interface at the level is enabled, no
shutdown.
Default
no shutdown — IS-IS entity is administratively enabled.
7210 SAS M, X OS Routing Protocols Guide
Page 195
Generic Commands
authentication-check
Syntax
Context
Description
[no] authentication-check
config>router>isis
This command sets an authentication check to reject PDUs that do not match the type or key requirements.
The default behavior when authentication is configured is to reject all IS-IS protocol PDUs that have a mismatch in either the authentication type or authentication key.
When no authentication-check is configured, authentication PDUs are generated and IS-IS PDUs are
authenticated on receipt. However, mismatches cause an event to be generated and will not be rejected.
The no form of this command allows authentication mismatches to be accepted and generate a log event.
Default
authentication-check — Rejects authentication mismatches.
authentication-key
Syntax
Context
Description
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
config>router>isis
config>router>isis>level level-number
This command sets the authentication key used to verify PDUs sent by neighboring routers on the interface.
Neighboring routers use passwords to authenticate PDUs sent from an interface. For authentication to work,
both the authentication key and the authentication type on a segment must match. The authentication-type
statement must also be included.
To configure authentication on the global level, configure this command in the config>router>isis context.
When this parameter is configured on the global level, all PDUs are authenticated including the hello PDU.
To override the global setting for a specific level, configure the authentication-key command in the config>router>isis>level context. When configured within the specific level, hello PDUs are not authenticated.
The no form of the command removes the authentication key.
Default
Parameters
no authentication-key — No authentication key is configured.
authentication-key — The authentication key. The key can be any combination of ASCII characters up to
255 characters in length (un-encrypted). If spaces are used in the string, enclose the entire string in quotation marks (“ ”).
hash-key — The hash key. The key can be any combination of ASCII characters up to 342 characters in
length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (“ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual
unencrypted key value is not provided.
hash — Specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is
assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in
the configuration file with the hash parameter specified.
Page 196
7210 SAS M, X OS Routing Protocols Guide
IS-IS
hash2 — Specifies the key is entered in a more complex encrypted form. If the hash2 parameter is not
used, the less encrypted hash form is assumed.
authentication-type
Syntax
Context
Description
authentication-type {password | message-digest}
no authentication
config>router>isis
config>router>isis>level level-number
This command enables either simple password or message digest authentication or must go in either the
global IS-IS or IS-IS level context.
Both the authentication key and the authentication type on a segment must match. The authentication-key
statement must also be included.
Configure the authentication type on the global level in the config>router>isis context.
Configure or override the global setting by configuring the authentication type in the config>router>isis>level context.
The no form of the command disables authentication.
Default
Parameters
no authentication-type — No authentication type is configured and authentication is disabled.
password — Specifies that simple password (plain text) authentication is required.
message-digest — Specifies that MD5 authentication in accordance with RFC2104 is required.
bfd-enable
Syntax
Context
Description
[no] bfd-enable {ipv4}
config>router>isis>interface
This command enables the use of bi-directional forwarding (BFD) to control IPv4 adjacencies. By enabling
BFD on an IPv4 or IPv6 protocol interface, the state of the protocol interface is tied to the state of the BFD
session between the local node and the remote node. The parameters used for the BFD are set by the BFD
command under the IP interface. This command must be given separately to enable/disable BFD for both
IPv4 and IPv6.
The no form of this command removes BFD from the associated adjacency.
Default
no bfd-enable ipv4
7210 SAS M, X OS Routing Protocols Guide
Page 197
Generic Commands
csnp-authentication
Syntax
Context
Description
[no] csnp-authentication
config>router>isis
config>router>isis>level level-number
This command enables authentication of individual ISIS packets of complete sequence number PDUs
(CSNP) type.
The no form of the command suppresses authentication of CSNP packets.
csnp-interval
Syntax
Context
Description
csnp-interval seconds
no csnp-interval
config>router>isis>interface ip-int-name
This command configures the time interval, in seconds, to send complete sequence number (CSN) PDUs
from the interface. IS-IS must send CSN PDUs periodically.
The no form of the command reverts to the default value.
Default
csnp-interval 10 — CSN PDUs are sent every 10 seconds for LAN interfaces.
csnp-interval 5 — CSN PDUs are sent every 5 seconds for point-to-point interfaces.
Parameters
seconds — The time interval, in seconds between successive CSN PDUs sent from this interface expressed
as a decimal integer.
Values
1 — 65535
disable-ldp-sync
Syntax
Context
Description
[no] disable-ldp-sync
config>router>isis
This command disables the IGP-LDP synchronization feature on all interfaces participating in the
OSPF or IS-IS routing protocol. When this command is executed, IGP immediately advertises the
actual value of the link cost for all interfaces which have the IGP-LDP synchronization enabled if
the currently advertized cost is different. It will then disable IGP-LDP synchornization for all
interfaces. This command does not delete the interface configuration. The no form of this
command has to be entered to re-enable IGP-LDP synchronization for this routing protocol.
The no form of this command restores the default settings and re-enables IGP-LDP
synchronization on all interfaces participating in the OSPF or IS-IS routing protocol and for which
the ldp-sync-timer is configured.
Page 198
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Default
no disable-ldp-sync
export
Syntax
Context
Description
[no] export policy-name [policy-name...up to 32 max]
config>router>isis
This command configures export routing policies that determine the routes exported from the routing table
to IS-IS.
If no export policy is defined, non IS-IS routes are not exported from the routing table manager to IS-IS.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first
policy that matches is applied. If multiple export commands are issued, the last command entered overrides
the previous command. A maximum of five policy names can be specified.
If an aggregate command is also configured in the config>router context, then the aggregation is applied
before the export policy is applied.
Routing policies are created in the config>router>policy-options context.
The no form of the command removes the specified policy-name or all policies from the configuration if no
policy-name is specified.
Default
Parameters
no export — No export policy name is specified.
policy-name — The export policy name. Up to five policy-name arguments can be specified.
external-preference
Syntax
Context
Description
external-preference external-preference
no external-preference
config>router>isis>level level-number
This command configures the external route preference for the IS-IS level.
The external-preference command configures the preference level of either IS-IS level 1 or IS-IS level 2
external routes. By default, the preferences are as listed in the table below.
A route can be learned by the router by different protocols, in which case, the costs are not comparable.
When this occurs, the preference decides the route to use.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is dependent on the default preference table. If multiple routes are learned with an identical preference using the
same protocol, the lowest cost route is used. If multiple routes are learned with an identical preference using
the same protocol and the costs (metrics) are equal, then the decision of the route to use is determined by the
configuration of the ecmp in the config>router context.
Default
Default preferences are listed in the following table:
7210 SAS M, X OS Routing Protocols Guide
Page 199
Generic Commands
Route Type
Preference
Configurable
Direct attached
0
No
Static-route
5
Yes
OSPF internal routes
10
No
IS-IS Level 1 internal
15
Yes*
IS-IS Level 2 internal
18
Yes*
OSPF external
150
Yes
IS-IS Level 1 external
160
Yes
IS-IS Level 2 external
165
Yes
BGP
170
Yes
BGP
170
Yes
*. Internal preferences are changed using the preference command in the config>router>isis>level level-number
context
Parameters
external-preference — The preference for external routes at this level as expressed.
Values
1 — 255
graceful-restart
Syntax
Context
Description
[no] graceful-restart
config>router>isis
This command enables graceful-restart helper support for ISIS. The router will act as a helper to neighbors
who are graceful-restart-capable and are restarting.
When the control plane of a graceful-restart-capable router fails, the neighboring routers (graceful-restart
helpers) temporarily preserve adjacency information so packets continue to be forwarded through the failed
graceful-restart router using the last known routes. If the control plane of the graceful-restart router comes
back up within the timer limits, then the routing protocols re-converge to minimize service interruption.
The no form of the command disables graceful restart and removes all graceful restart configurations in the
ISIS instance.
Default
Page 200
disabled
7210 SAS M, X OS Routing Protocols Guide
IS-IS
helper-disable
Syntax
Context
Description
[no] helper-disable
config>router>isis>graceful-restart
This command disables the helper support for graceful restart.
When graceful-restart is enabled, the router can be a helper (meaning that the router is helping a neighbor
to restart) or be a restarting router or both. The router supports only helper mode. This facilitates the graceful
restart of neighbors but will not act as a restarting router (meaning that the router will not help the neighbors
to restart).
The no helper-disable command enables helper support and is the default when graceful-restart is enabled.
Default
disabled
hello-authentication
Syntax
Context
Description
[no] hello-authentication
config>router>isis
config>router>isis>level level-number
This command enables authentication of individual ISIS packets of HELLO type.
The no form of the command suppresses authentication of HELLO packets.
hello-authentication-key
Syntax
Context
Description
hello-authentication-key [authentication-key | hash-key] [hash | hash2]
no hello-authentication-key
config>router>isis>interface ip-int-name
config>router>isis>if>level level-number
This command configures the authentication key (password) for hello PDUs. Neighboring routers use the
password to verify the authenticity of hello PDUs sent from this interface. Both the hello authentication key
and the hello authentication type on a segment must match. The hello-authentication-type must be specified.
To configure the hello authentication key in the interface context use the hello-authentication-key in the
config>router>isis>interface context.
To configure or override the hello authentication key for a specific level, configure the hello-authentication-key in the config>router>isis>interface>level context.
If both IS-IS and hello-authentication are configured, hello messages are validated using hello authentication. If only IS-IS authentication is configured, it will be used to authenticate all IS-IS (including hello) protocol PDUs.
7210 SAS M, X OS Routing Protocols Guide
Page 201
Generic Commands
When the hello authentication key is configured in the config>router>isis>interface context, it applies to
all levels configured for the interface.
The no form of the command removes the authentication-key from the configuration.
Default
Parameters
no hello-authentication-key — No hello authentication key is configured.
authentication-key — The hello authentication key (password). The key can be any combination of ASCII
characters up to 254 characters in length (un-encrypted). If spaces are used in the string, enclose the
entire string in quotation marks (“ ”).
hash-key — The hash key. The key can be any combination of ASCII characters up to 352 characters in
length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (“ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual
unencrypted key value is not provided.
hash — Specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is
assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in
the configuration file with the hash parameter specified.
hash2 — Specifies the key is entered in a more complex encrypted form. If the hash2 parameter is not used,
the less encrypted hash form is assumed.
hello-authentication-type
Syntax
Context
Description
hello-authentication-type {password | message-digest}
no hello-authentication-type
config>router>isis>interface ip-int-name
config>router>isis>if>level level-number
This command enables hello authentication at either the interface or level context. Both the hello authentication key and the hello authentication type on a segment must match. The hello authentication-key statement
must also be included.
To configure the hello authentication type at the interface context, use hello-authentication-type in the config>router>isis>interface context.
To configure or override the hello authentication setting for a given level, configure the hello-authentication-type in the config>router>isis>interface>level context.
The no form of the command disables hello authentication.
Default
Parameters
Page 202
no hello-authentication-type — Hello authentication is disabled.
password — Specifies simple password (plain text) authentication is required.
7210 SAS M, X OS Routing Protocols Guide
IS-IS
message-digest — Specifies MD5 authentication in accordance with RFC2104 (HMAC: Keyed-Hashing
for Message Authentication) is required.
hello-interval
Syntax
Context
Description
hello-interval seconds
no hello-interval
config>router>isis>if>level level-number
This command configures the interval in seconds between hello messages issued on this interface at this
level.
The no form of the command to reverts to the default value.
Default
3 — Hello interval default for the designated intersystem.
9 — Hello interval default for non-designated intersystems.
Parameters
seconds — The hello interval in seconds expressed as a decimal integer.
Values
1 — 20000
hello-multiplier
Syntax
Context
Description
hello-multiplier multiplier
no hello-multiplier
config>router>isis>if>level level-number
This command configures the number of missing hello PDUs from a neighbor after the router declares the
adjacency down.
The no form of the command reverts to the default value.
Default
Parameters
3 — The router can miss up to 3 hello messages before declaring the adjacency down.
multiplier — The multiplier for the hello interval expressed as a decimal integer.
Values
2 — 100
interface
Syntax
Context
Description
[no] interface ip-int-name
config>router>isis
This command creates the context to configure an IS-IS interface.
When an area is defined, the interfaces belong to that area. Interfaces cannot belong to separate areas.
7210 SAS M, X OS Routing Protocols Guide
Page 203
Generic Commands
When the interface is a POS channel, the OSINCP is enabled when the interface is created and removed
when the interface is deleted.
The no form of the command removes IS-IS from the interface.
The shutdown command in the config>router>isis>interface context administratively disables IS-IS on the
interface without affecting the IS-IS configuration.
Default
Parameters
no interface — No IS-IS interfaces are defined.
ip-int-name — Identify the IP interface name created in the config>router>interface context. The IP interface name must already exist.
interface-type
Syntax
Context
Description
interface-type {broadcast | point-to-point}
no interface-type
config>router>isis>interface ip-int-name
This command configures the IS-IS interface type as either broadcast or point-to-point.
Use this command to set the interface type of an Ethernet link to point-to-point to avoid having to carry the
designated IS-IS overhead if the link is used as a point-to-point.
If the interface type is not known at the time the interface is added to IS-IS and subsequently the IP interface
is bound (or moved) to a different interface type, then this command must be entered manually.
The no form of the command reverts to the default value.
Special Cases
SONET — Interfaces on SONET channels default to the point-to-point type.
Ethernet or Unknown — Physical interfaces that are Ethernet or unknown default to the broadcast type.
Default
point-to-point — For IP interfaces on SONET channels.
broadcast — For IP interfaces on Ethernet or unknown type physical interfaces.
Parameters
broadcast — Configures the interface to maintain this link as a broadcast network.
point-to-point — Configures the interface to maintain this link as a point-to-point link.
level
Syntax
Context
Description
level level-number
config>router>isis
config>router>isis>interface ip-int-name
This command creates the context to configure IS-IS Level 1 or Level 2 area attributes.
A router can be configured as a Level 1, Level 2, or Level 1-2 system. A Level 1 adjacency can be established if there is at least one area address shared by this router and a neighbor. A Level 2 adjacency cannot be
established over this interface.
Page 204
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Level 1/2 adjacency is created if the neighbor is also configured as Level 1/2 router and has at least one area
address in common. A Level 2 adjacency is established if there are no common area IDs.
A Level 2 adjacency is established if another router is configured as Level 2 or a Level 1/2 router with interfaces configured as Level 1/2 or Level 2. Level 1 adjacencies will not established over this interface.
To reset global and/or interface level parameters to the default, the following commands must be entered
independently:
level> no hello-authentication-key
level> no hello-authentication-type
level> no hello-interval
level> no hello-multiplier
level> no metric
level> no passive
level> no priority
Special Cases
Global IS-IS Level — The config>router>isis context configures default global parameters for both
Level 1 and Level 2 interfaces.
IS-IS Interface Level — The config>router>isis>interface context configures IS-IS operational characteristics of the interface at Level 1 and/or Level 2. A logical interface can be configured on one Level 1 and
one Level 2. In this case, each level can be configured independently and parameters must be removed independently.
By default an interface operates in both Level 1 and Level 2 modes.
Default
Parameters
level 1 or level 2
level-number — The IS-IS level number.
Values
1, 2
level-capability
Syntax
Context
Description
level-capability {level-1 | level-2 | level-1/2}
no level-capability
config>router>isis
This command configures the routing level for an instance of the IS-IS routing process.
An IS-IS router and an IS-IS interface can operate at Level 1, Level 2 or both Level 1 and 2.
Table 6 displays configuration combinations and the potential adjacencies that can be formed.
Table 6: Potential Adjacency Capabilities
Global Level
Interface Level
Potential Adjacency
L 1/2
L 1/2
Level 1 and/or Level 2
L 1/2
L1
Level 1 only
L 1/2
L2
Level 2 only
7210 SAS M, X OS Routing Protocols Guide
Page 205
Generic Commands
Table 6: Potential Adjacency Capabilities (Continued)
Global Level
Interface Level
Potential Adjacency
L2
L 1/2
Level 2 only
L2
L2
Level 2 only
L2
L1
none
L1
L 1/2
Level 1 only
L1
L2
none
L1
L1
Level 1 only
The no form of the command removes the level capability from the configuration.
Special Cases
IS-IS Router — In the config>router>isis context, changing the level-capability performs a restart on the
IS-IS protocol instance.
IS-IS Interface — In the config>router>isis>interface context, changing the level-capability performs a
restart of IS-IS on the interface.
Default
Parameters
level-1/2
level-1 — Specifies the router/interface can operate at Level 1only.
level-2 — Specifies the router/interface can operate at Level 2 only.
level-1/2 — Specifies the router/interface can operate at both Level 1 and Level 2.
lsp-pacing-interval
Syntax
Context
Description
lsp-pacing-interval milliseconds
no lsp-pacing-interval
config>router>isis>interface ip-int-name
This command configures the interval between LSP PDUs sent from this interface.
To avoid bombarding adjacent neighbors with excessive data, pace the Link State Protocol Data Units
(LSP’s). If a value of zero is configured, no LSP’s are sent from the interface.
The no form of the command reverts to the default value.
Default
Parameters
100 — LSPs are sent in 100 millisecond intervals.
milliseconds — The interval in milliseconds that IS-IS LSP’s can be sent from the interface expressed as a
decimal integer.
Values
Page 206
0 — 65535
7210 SAS M, X OS Routing Protocols Guide
IS-IS
lsp-lifetime
Syntax
Context
Description
lsp-lifetime seconds
no lsp-lifetime
config>router>isis
This command sets the time, in seconds, the router wants the LSPs it originates to be considered valid by
other routers in the domain.
Each LSP received is maintained in an LSP database until the lsp-lifetime expires unless the originating
router refreshes the LSP. By default, each router refreshes its LSP’s every 20 minutes (1200 seconds) so
other routers will not age out the LSP.
The LSP refresh timer is derived from this formula: lsp-lifetime/2
The no form of the command reverts to the default value.
Default
Parameters
1200 — LSPs originated by the router should be valid for 1200 seconds (20 minutes).
seconds — The time, in seconds, that the router wants the LSPs it originates to be considered valid by other
routers in the domain.
Values
350 — 65535
lsp-wait
Syntax
Context
lsp-wait lsp-wait [lsp-initial-wait [lsp-second-wait]]
config>router>isis
Description
This command is used to customize the throttling of IS-IS LSP-generation. Timers that determine when to
generate the first, second and subsequent LSPs can be controlled with this command. Subsequent LSPs are
generated at increasing intervals of the second lsp-wait timer until a maximum value is reached.
Parameters
lsp-max-wait — Specifies the maximum interval in seconds between two consecutive ocurrences of an LSP
being generated.
Values
1 — 120
Default
5
lsp-initial-wait — Specifies the initial LSP generation delay in seconds.
Values
0 — 100
Default
0
lsp-second-wait — Specifies the hold time in seconds between the first and second LSP generation.
Values
1 — 100
Default
1
7210 SAS M, X OS Routing Protocols Guide
Page 207
Generic Commands
mesh-group
Syntax
Context
Description
mesh-group {value | blocked}
no mesh-group
config>router>isis>interface ip-int-name
This command assigns an interface to a mesh group. Mesh groups limit the amount of flooding that occurs
when a new or changed LSP is advertised throughout an area.
All routers in a mesh group should be fully meshed. When LSPs need to be flooded, only a single copy is
received rather than a copy per neighbor.
To create a mesh group, configure the same mesh group value for each interface that is part of the mesh
group. All routers must have the same mesh group value configured for all interfaces that are part of the
mesh group.
To prevent an interface from flooding LSPs, the optional blocked parameter can be specified. Configure
mesh groups carefully. It is easy to created isolated islands that do not receive updates as (other) links fail.
The no form of the command removes the interface from the mesh group.
Default
Parameters
no mesh-group — The interface does not belong to a mesh group.
value — The unique decimal integer value distinguishes this mesh group from other mesh groups on this or
any other router that is part of this mesh group.
Values
1 — 2000000000
blocked — Prevents an interface from flooding LSPs.
metric
Syntax
Context
Description
metric ipv4-metric
no metric
config>router>isis>if>level level-number
This command configures the metric used for the level on the interface.
In order to calculate the lowest cost to reach a given destination, each configured level on each interface
must have a cost. The costs for each level on an interface may be different.
If the metric is not configured, the default of 10 is used unless reference bandwidth is configured.
The no form of the command reverts to the default value.
Default
Parameters
10 — A metric of 10 for the level on the interface is used.
ipv4-metric — The metric assigned for this level on this interface.
Values
Page 208
1 — 16777215
7210 SAS M, X OS Routing Protocols Guide
IS-IS
area-id
Syntax
Context
Description
[no] area-id area-address
config>router>isis
This command was previously named the net network-entity-title command. The area-id command allows
you to configure the area ID portion of NSAP addresses which identifies a point of connection to the network, such as a router interface, and is called a Network Service Access Point (NSAP). Addresses in the ISIS protocol are based on the ISO NSAP addresses and Network Entity Titles (NETs), not IP addresses.
A maximum of 3 area addresses can be configured.
NSAP addresses are divided into three parts. Only the area ID portion is configurable.
• Area ID — A variable length field between 1 and 13 bytes long. This includes the Authority and Format
Identifier (AFI) as the most significant byte and the area ID.
• System ID — A six-byte system identification. This value is not configurable. The system ID is derived
from the system or router ID.
• Selector ID — A one-byte selector identification that must contain zeros when configuring a NET. This
value is not configurable. The selector ID is always 00.
The NET is constructed like an NSAP but the selector byte contains a 00 value. NET addresses are
exchanged in hello and LSP PDUs. All net addresses configured on the node are advertised to its neighbors.
For Level 1 interfaces, neighbors can have different area IDs, but, they must have at least one area ID (AFI +
area) in common. Sharing a common area ID, they become neighbors and area merging between the potentially different areas can occur.
For Level 2 (only) interfaces, neighbors can have different area IDs. However, if they have no area IDs in
common, they become only Level 2 neighbors and Level 2 LSPs are exchanged.
For Level 1 and Level 2 interfaces, neighbors can have different area IDs. If they have at least one area ID
(AFI + area) in common, they become neighbors. In addition to exchanging Level 2 LSPs, area merging
between potentially different areas can occur.
If multiple area-id commands are entered, the system ID of all subsequent entries must match the first area
address.
The no form of the command removes the area address.
Default
Parameters
none — No area address is assigned.
area-address — The 1 — 13-byte address. Of the total 20 bytes comprising the NET, only the first 13 bytes
can be manually configured. As few as one byte can be entered or, at most, 13 bytes. If less than 13 bytes are
entered, the rest is padded with zeros.
7210 SAS M, X OS Routing Protocols Guide
Page 209
Generic Commands
overload
Syntax
Context
Description
overload [timeout seconds]
no overload
config>router>isis
This command administratively sets the IS-IS router to operate in the overload state for a specific time
period, in seconds, or indefinitely.
During normal operation, the router may be forced to enter an overload state due to a lack of resources.
When in the overload state, the router is only used if the destination is reachable by the router and will not
used for other transit traffic.
If a time period is specified, the overload state persists for the configured length of time. If no time is specified, the overload state operation is maintained indefinitely.
The overload command can be useful in circumstances where the router is overloaded or used prior to executing a shutdown command to divert traffic around the router.
The no form of the command causes the router to exit the overload state.
Default
Parameters
no overload
seconds — The time, in seconds, that this router must operate in overload state.
Default
infinity (overload state maintained indefinitely)
Values
60 — 1800
overload-on-boot
Syntax
Context
Description
overload-on-boot [timeoutseconds]
no overload-on-boot
config>router>isis
When the router is in an overload state, the router is used only if there is no other router to reach the
destination. This command configures the IGP upon bootup in the overload state until one of the following
events occur:
1. The timeout timer expires.
2. A manual override of the current overload state is entered with the config>router>isis>no overload
command.
The no overload command does not affect the overload-on-boot function.
If no timeout is specified, IS-IS will go into overload indefinitely after a reboot. After the reboot, the IS-IS
status will display a permanent overload state:
L1 LSDB Overload : Manual on boot (Indefinitely in overload)
L2 LSDB Overload : Manual on boot (Indefinitely in overload)
This state can be cleared with the config>router>isis>no overload command.
Page 210
7210 SAS M, X OS Routing Protocols Guide
IS-IS
When specifying a timeout value, IS-IS will go into overload for the configured timeout after a reboot. After
the reboot, the IS-IS status will display the remaining time the system stays in overload:
L1 LSDB Overload : Manual on boot (Overload Time Left : 17)
L2 LSDB Overload : Manual on boot (Overload Time Left : 17)
The overload state can be cleared before the timeout expires with the config>router>isis>no overload command.
The no form of the command removes the overload-on-boot functionality from the configuration.
Default
no overload-on-boot
Use show router ospf status and/or show router isis status commands to display the administrative and
operational state as well as all timers.
Parameters
timeout seconds — Configure the timeout timer for overload-on-boot in seconds.
Values
60 — 1800
passive
Syntax
Context
Description
[no] passive
config>router>isis>interface ip-int-name
config>router>isis>if>level level-number
This command adds the passive attribute which causes the interface to be advertised as an IS-IS interface
without running the IS-IS protocol. Normally, only interface addresses that are configured for IS-IS are
advertised as IS-IS interfaces at the level that they are configured.
When the passive mode is enabled, the interface or the interface at the level ignores ingress IS-IS protocol
PDUs and will not transmit IS-IS protocol PDUs.
The no form of the command removes the passive attribute.
Special Cases
Service Interfaces — Service interfaces (defined using the service-prefix command in config>router)
are passive by default.
All other Interfaces — All other interfaces are not passive by default.
Default
passive — Service interfaces are passive.
no passive — All other interfaces are not passive.
preference
Syntax
Context
Description
preference preference
no preference
config>router>isis>level level-number
This command configures the preference level of either IS-IS Level 1 or IS-IS Level 2 internal routes. By
default, the preferences are listed in the table below.
7210 SAS M, X OS Routing Protocols Guide
Page 211
Generic Commands
A route can be learned by the router by different protocols, in which case, the costs are not comparable.
When this occurs, the preference is used to decide to which route will be used.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is per the
default preference table as defined in the table below. If multiple routes are learned with an identical preference using the same protocol, the lowest cost route is used. If multiple routes are learned with an identical
preference using the same protocol and the costs (metrics) are equal, then the decision what route to use is
determined by the configuration of the ecmp in the config>router context.
Default
Default preferences are listed in the following table:
Route Type
Preference
Configurable
Direct attached
0
No
Static-route
5
Yes
OSPF internal routes
10
No
IS-IS level 1 internal
15
Yes
IS-IS level 2 internal
18
Yes
OSPF external
150
Yes
IS-IS level 1 external
160
Yes*
IS-IS level 2 external
165
Yes*
BGP
170
Yes
*. External preferences are changed using the external-preference command in the config>router>isis>level
level-number context.
Parameters
preference — The preference for external routes at this level expressed as a decimal integer.
Values
1 — 255
priority
Syntax
Context
Description
priority number
no priority
config>router>isis>if>level level-number
This command configures the priority of the IS-IS router interface for designated router election on a multiaccess network.
This priority is included in hello PDUs transmitted by the interface on a multi-access network. The router
with the highest priority is the preferred designated router. The designated router is responsible for sending
LSPs with regard to this network and the routers that are attached to it.
The no form of the command reverts to the default value.
Page 212
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Default
Parameters
64
number — The priority for this interface at this level.
Values
0 — 127
psnp-authentication
Syntax
Context
Description
[no] psnp-authentication
config>router>isis
config>router>isis>level
This command enables authentication of individual ISIS packets of partial sequence number PDU (PSNP)
type.
The no form of the command suppresses authentication of PSNP packets.
reference-bandwidth
Syntax
Context
Description
reference-bandwidth reference-bandwidth
no reference-bandwidth
config>router>isis
This command configures the reference bandwidth that provides the basis of bandwidth relative costing.
In order to calculate the lowest cost to reach a specific destination, each configured level on each interface
must have a cost. If the reference bandwidth is defined, then the cost is calculated using the following formula:
cost = reference-bandwidth ÷ bandwidth
If the reference bandwidth is configured as 10 Gigabits (10,000,000,000), a 100 M/bps interface has a default
metric of 100. In order for metrics in excess of 63 to be configured, wide metrics must be deployed. (See
wide-metrics-only in the config>router>isis context.)
If the reference bandwidth is not configured, then all interfaces have a default metric of 10.
The no form of the command reverts to the default value.
Default
Parameters
no reference-bandwidth — No reference bandwidth is defined. All interfaces have a metric of 10.
reference-bandwidth — The reference bandwidth in kilobits per second expressed as a decimal integer.
Values
0 - 100000000
7210 SAS M, X OS Routing Protocols Guide
Page 213
Generic Commands
retransmit-interval
Syntax
Context
Description
retransmit-interval seconds
no retransmit-interval
config>router>isis>interface ip-int-name
This command configures the minimum time between LSP PDU retransmissions on a point-to-point interface.
The no form of the command reverts to the default value.
Default
Parameters
100
seconds — The interval in seconds that IS-IS LSPs can be sent on the interface.
Values
1 — 65535
spf-wait
Syntax
Context
Description
Default
Parameters
[no] spf-wait spf-wait [spf-initial-wait [spf-second-wait]]
config>router>isis
This command defines the maximum interval between two consecutive SPF calculations in seconds. Timers
that determine when to initiate the first, second and subsequent SPF calculations after a topology change
occurs can be controlled with this command. Subsequent SPF runs (if required) will occur at exponentially
increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, then
the next SPF will run after 2000 milliseconds, and then next SPF will run after 4000 milliseconds, etc., until
it reaches the spf-wait value. The SPF interval will stay at spf-wait value until there are no more SPF runs
scheduled in that interval. After a full interval without any SPF runs, the SPF interval will drop back to spfinitial-wait.
no spf-wait
spf-wait — Specifies the maximum interval in seconds between two consecutive spf calculations.
Values
1 — 120
Default
10
spf-initial-wait — Specifies the initial SPF calculation delay in milliseconds after a topology change.
Values
10 — 100000
Default
1000
spf-second-wait — Specifies the hold time in milliseconds between the first and second SPF calculation.
Page 214
Values
0 — 100000
Default
1000
7210 SAS M, X OS Routing Protocols Guide
IS-IS
summary-address
Syntax
Context
Description
Default
Parameters
summary-address {ip-prefix/mask | ip-prefix [netmask]} level
no summary-address {ip-prefix/mask | ip-prefix [netmask]}
config>router>isis
This command creates summary-addresses.
none
ip-prefix/mask — Specifies information for the specified IP prefix and mask length.
Values
ipv4-address:
ipv4-prefix-length:
a.b.c.d (host bits must be 0)
0 — 32
netmask — The subnet mask in dotted decimal notation.
Values
0.0.0.0 — 255.255.255.255 (network bits all 1 and host bits all 0)
level — Specifies IS-IS level area attributes.
Values
level-1, level-2, level-1/2
suppress-default
Syntax
Context
Description
[no] suppress-default
config>router>isis
This command enables or disables IS-IS to suppress the installation of default routes.
traffic-engineering
Syntax
Context
Description
Default
[no] traffic-engineering
config>router>isis
This command configures traffic-engineering and determines if IGP shortcuts are required.
disabled
wide-metrics-only
Syntax
Context
Description
[no] wide-metrics-only
config>router>isis>level level-number
This command enables the exclusive use of wide metrics in the LSPs for the level number.. Narrow metrics
can have values between 1 and 63. IS-IS can generate two TLVs, one for the adjacency and one for the IP
7210 SAS M, X OS Routing Protocols Guide
Page 215
Generic Commands
prefix. In order to support traffic engineering, wider metrics are required. When wide metrics are used, a second pair of TLVs are added, again, one for the adjacency and one for the IP prefix.
By default, both sets of TLVs are generated. When wide-metrics-only is configured, IS-IS only generates the
pair of TLVs with wide metrics for that level.
The no form of the command reverts to the default value.
Page 216
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Show Commands
isis
Syntax
Context
Description
isis
show>router
This command displays information for a specified IS-IS instance.
adjacency
Syntax
Context
adjacency [ip-address | ip-int-name | nbr-system-id] [detail]
show>router>isis
Description
This command displays information regarding IS-IS neighbors. When no ip-address, ip-int-name, or nbrsystem-id are specified, then all adjacencies display.
Parameters
ip-address — When specified, only adjacencies with that interface display.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
ip-int-name — When specified, only adjacencies with that interface display.
nbr-system-id — When pecified, only the adjacency with that ID displays.
detail — All output displays in the detailed format.
Output
Standard and Detailed IS-IS Adjacency Output — The following table describes the standard and
detailed command output fields for an IS-IS adjacency.
Label
Description
Interface
Interface name associated with the neighbor.
System-id
Neighbor’s system ID.
Level
1-L1 only, 2-L2 only, 3-L1 and L2.
State
Up, down, new, one-way, initializing, or rejected.
Hold
Hold time remaining for the adjacency.
SNPA
Subnetwork point of attachment, MAC address of the next hop.
Circuit type
Level on the interface L1, L2, or both.
Expires In
Number of seconds until adjacency expires.
Priority
Priority to become designated router.
7210 SAS M, X OS Routing Protocols Guide
Page 217
Show Commands
Label
Description (Continued)
Up/down transitions
Number of times neighbor state has changed.
Event
Event causing last transition.
Last transition
Time since last transition change.
Speaks
Supported protocols (only IP).
IP address
IP address of neighbor.
MT enab
Yes — The neighbor is advertising at least 1 non MTID#0.
Topology
Derived from the MT TLV in the IIH
• MT#0, MT#2 => “Topology : Unicast”
• Native IPv4
Not supported MTID's => Topology line suppressed
Sample Output
*A:Dut-A# show router isis adjacency
===============================================================================
ISIS Adjacency
===============================================================================
System ID
Usage State Hold Interface
MT Enab
------------------------------------------------------------------------------Dut-B
L1
Up
2
ip-3FFE::A0A:101
Yes
Dut-B
L2
Up
2
ip-3FFE::A0A:101
Yes
Dut-F
L1L2 Up
5
ies-1-3FFE::A0A:1501
Yes
------------------------------------------------------------------------------Adjacencies : 3
===============================================================================
*A:Dut-A#
*A:ALA-A# show router isis adjacency 180.0.7.12
===============================================================================
ISIS Adjacency
===============================================================================
System ID
Usage State Hold Interface
------------------------------------------------------------------------------asbr_east
L2
Up
25
if2/5
------------------------------------------------------------------------------Adjacencies : 1
===============================================================================
*A:ALA-A#
*A:ALA-A# show router isis adjacency if2/5
===============================================================================
ISIS Adjacency
===============================================================================
System ID
Usage State Hold Interface
------------------------------------------------------------------------------asbr_east
L2
Up
20
if2/5
Page 218
7210 SAS M, X OS Routing Protocols Guide
IS-IS
------------------------------------------------------------------------------Adjacencies : 1
===============================================================================
*A:ALA-A#
*A:Dut-A# show router isis adjacency detail
===============================================================================
ISIS Adjacency
===============================================================================
SystemID
: Dut-B
SNPA
: 20:81:01:01:00:01
Interface
: ip-3FFE::A0A:101
Up Time
: 0d 00:56:10
State
: Up
Priority
: 64
Nbr Sys Typ : L1
L. Circ Typ : L1
Hold Time
: 2
Max Hold
: 2
Adj Level
: L1
MT Enabled : Yes
IPv4 Neighbor
:
Restart Support
:
Restart Status
:
Restart Supressed :
Number of Restarts:
Last Restart at
:
SystemID
Interface
State
Nbr Sys Typ
Hold Time
Adj Level
Topology
:
:
:
:
:
:
:
Dut-B
ip-3FFE::A0A:101
Up
L2
2
L2
Unicast
IPv4 Neighbor
:
Restart Support
:
Restart Status
:
Restart Supressed :
Number of Restarts:
Last Restart at
:
SystemID
Interface
State
Nbr Sys Typ
Hold Time
Adj Level
Topology
:
:
:
:
:
:
:
10.10.1.2
Disabled
Not currently being helped
Disabled
0
Never
SNPA
Up Time
Priority
L. Circ Typ
Max Hold
MT Enabled
:
:
:
:
:
:
20:81:01:01:00:01
0d 00:56:10
64
L2
2
Yes
SNPA
Up Time
Priority
L. Circ Typ
Max Hold
MT Enabled
:
:
:
:
:
:
00:00:00:00:00:00
0d 01:18:34
0
L1L2
6
Yes
10.10.1.2
Disabled
Not currently being helped
Disabled
0
Never
Dut-F
ies-1-3FFE::A0A:1501
Up
L1L2
5
L1L2
Unicast
IPv4 Neighbor
: 10.10.21.6
Restart Support
: Disabled
Restart Status
: Not currently being helped
Restart Supressed : Disabled
Number of Restarts: 0
Last Restart at
: Never
===============================================================================
*A:Dut-A#
A:Dut-A# show router isis status
===============================================================================
7210 SAS M, X OS Routing Protocols Guide
Page 219
Show Commands
ISIS Status
===============================================================================
System Id
: 0100.2000.1001
Admin State
: Up
Ipv4 Routing
: Enabled
Last Enabled
: 08/28/2006 10:22:17
Level Capability
: L2
Authentication Check : True
Authentication Type : None
CSNP-Authentication : Enabled
HELLO-Authentication : Enabled
PSNP-Authentication : Enabled
Traffic Engineering : Enabled
Graceful Restart
: Disabled
GR Helper Mode
: Disabled
LSP Lifetime
: 1200
LSP Wait
: 1 sec (Max)
1 sec (Initial)
1 sec (Second)
Adjacency Check
: loose
L1 Auth Type
: none
L2 Auth Type
: none
L1 CSNP-Authenticati*: Enabled
L1 HELLO-Authenticat*: Enabled
L1 PSNP-Authenticati*: Enabled
L1 Preference
: 15
L2 Preference
: 18
L1 Ext. Preference
: 160
L2 Ext. Preference
: 165
L1 Wide Metrics
: Disabled
L2 Wide Metrics
: Enabled
L1 LSDB Overload
: Disabled
L2 LSDB Overload
: Disabled
L1 LSPs
: 0
L2 LSPs
: 15
Last SPF
: 08/28/2006 10:22:25
SPF Wait
: 1 sec (Max)
10 ms (Initial)
10 ms (Second)
Export Policies
: None
Area Addresses
: 49.0001
===============================================================================
* indicates that the corresponding row element may have been truncated.
A:Dut-A#
database
Syntax
Context
database [system-id | lsp-id] [detail] [level level]
show>router>isis
Description
This command displays the entries in the IS-IS link state database.
Parameters
system-id — Only the LSPs related to that system-id are listed. If no system-id or lsp-id are specified, all
database entries are listed.
lsp-id — Only the specified LSP (hostname) is listed. If no system-id or lsp-id are specified, all database
entries are listed.
detail — All output is displayed in the detailed format.
Page 220
7210 SAS M, X OS Routing Protocols Guide
IS-IS
level level — Only the specified IS-IS protocol level attributes are displayed.
Output
IS-IS Database Output — The following table describes the IS-IS database output.
Label
Description
LSP ID
LSP IDs are auto-assigned by the originating IS-IS node. The LSP ID
is comprised of three sections. The first 6 bytes is the system ID for
that node, followed by a single byte value for the pseudonode generated by that router, then finally, a fragment byte which starts at zero.
For example, if a router’s system ID is 1800.0000.0029, the first LSP
ID is 1800.0000.0029.00-00. If there are too many routes, LSP ID
1800.0000.0029.00-01 is created to contain the excess routes. If the
router is the Designated Intermediate System (DIS) on a broadcast network, a pseudo-node LSP is created. Usually the internal circuit ID is
used to determine the ID assigned to the pseudonode. For instance, for
circuit 4, a LSP pseudonode with ID 1800.0000.0029.04-00 is created.
The router learns hostnames and uses the hostname in place of the system ID. An example of LDP IDs are:
acc_arl.00-00
acc_arl.00-01
acc_arl.04-00
Sequence
The sequence number of the LSP that allows other systems to determine if they have received the latest information from the source.
Checksum
The checksum of the entire LSP packet.
Lifetime
Amount of time, in seconds, that the LSP remains valid.
Attributes
OV — The overload bit is set.
L1 — Specifies a Level 1 IS type.
L2 — Specifies a Level 2 IS type.
The attach bit is set. When this bit is set, the router
can also act as a Level 2 router and can reach other areas.
ATT —
LSP Count
A sum of all the configured Level 1 and Level 2 LSPs.
LSP ID
Displays a unique identifier for each LSP composed of SysID,
Pseudonode ID and LSP name.
Lifetime
Displays the remaining time until the LSP expires.
Version
Displays the version/protocol ID extension. This value is always set to
1.
Pkt Type
Displays the PDU type number.
Pkt Ver
Displays the version/protocol ID extension. This value is always set to
1.
7210 SAS M, X OS Routing Protocols Guide
Page 221
Show Commands
Label
Description (Continued)
Max Area
Displays the maximum number of area addresses supported.
Sys ID Len
Displays the length of the system ID field (0 or 6 for 6 digits).
Use Len
The actual length of the PDU.
Alloc Len
The amount of memory space allocated for the LSP.
Area Address
Displays the area addresses to which the router is connected.
Supp Protocols
Displays the data protocols that are supported.
IS-Hostname
The name of the router originating the LSP.
Virtual Flag
0 — Level 1 intermediate systems report this octet as 0 to all neighbors.
1 — Indicates that the path to a neighbor is a Level 2 virtual path used
to repair an area partition.
Neighbor
Displays the routers running interfaces to which the router is connected.
Internal Reach
Displays a 32-bit metric. A bit is added for the ups and downs resulting
from Level 2 to Level 1 route-leaking.
IP Prefix
Displays the IP addresses that the router knows about by externallyoriginated interfaces.
Metrics
Displays a routing metric used in the IS-IS link-state calculation.
Sample Output
*A:ALA-A# show router isis database
===============================================================================
ISIS Database
===============================================================================
LSP ID
Sequence Checksum Lifetime Attributes
------------------------------------------------------------------------------Displaying Level 1 database
------------------------------------------------------------------------------abr_dfw.00-00
0x50
0x164f
603
L1L2
Level (1) LSP Count : 1
Displaying Level 2 database
------------------------------------------------------------------------------asbr_east.00-00
0x53
0xe3f5
753
L1L2
abr_dfw.00-00
0x57
0x94ff
978
L1L2
abr_dfw.03-00
0x50
0x14f1
614
L1L2
Level (2) LSP Count : 3
===============================================================================
*A:ALA-A#
*A:Dut-B# show router isis database Dut-A.00-00 detail
Page 222
7210 SAS M, X OS Routing Protocols Guide
IS-IS
==============================================================================
ISIS Database
==============================================================================
Displaying Level 1 database
-----------------------------------------------------------------------------Level (1) LSP Count : 0
Displaying Level 2 database
-----------------------------------------------------------------------------LSP ID
: Dut-A.00-00
Level
: L2
Sequence : 0x6
Checksum : 0xb7c4
Lifetime : 1153
Version
: 1
Pkt Type : 20
Pkt Ver
: 1
Attributes: L1L2
Max Area : 3
SysID Len : 6
Used Len : 311
Alloc Len : 311
TLVs :
Area Addresses:
Area Address : (2) 30.31
Supp Protocols:
Protocols
: IPv4
IS-Hostname
: Dut-A
Router ID
:
Router ID
: 10.20.1.1
I/F Addresses :
I/F Address
: 10.20.1.1
I/F Address
: 10.10.1.1
I/F Address
: 10.10.2.1
TE IS Nbrs
:
Nbr
: Dut-B.01
Default Metric : 1000
Sub TLV Len
: 98
IF Addr
: 10.10.1.1
MaxLink BW: 100000 kbps
Resvble BW: 100000 kbps
Unresvd BW:
BW[0] : 10000 kbps
BW[1] : 40000 kbps
BW[2] : 40000 kbps
BW[3] : 40000 kbps
BW[4] : 50000 kbps
BW[5] : 50000 kbps
BW[6] : 50000 kbps
BW[7] : 10000 kbps
Admin Grp : 0x0
TE Metric : 1000
SUBTLV BW CONSTS
: 8
BW Model : 1
BC[0]: 10000 kbps
BC[1]: 0 kbps
BC[2]: 40000 kbps
BC[3]: 0 kbps
BC[4]: 0 kbps
BC[5]: 50000 kbps
BC[6]: 0 kbps
BC[7]: 0 kbps
TE IP Reach
:
Default Metric : 0
Control Info:
, prefLen 32
Prefix
: 10.20.1.1
7210 SAS M, X OS Routing Protocols Guide
Page 223
Show Commands
Default
Control
Prefix
Default
Control
Prefix
Metric : 1000
Info:
, prefLen 24
: 10.10.1.0
Metric : 1000
Info:
, prefLen 24
: 10.10.2.0
Level (2) LSP Count : 1
==============================================================================
*A:Dut-B#
hostname
Syntax
Context
Description
Output
hostname
show>router>isis
This command displays the hostname database. There are no options or parameters.
IS-IS Hostname Output — The following table describes output fields for IS-IS hostname output.
Label
Description
System-id
System identifier mapped to hostname.
Hostname
Hostname for the specific system-id.
Type
The type of entry (static or dynamic).
Sample Output
A:ALA-A# show router isis hostname
=========================================================================
Hosts
=========================================================================
System Id
Hostname
------------------------------------------------------------------------1800.0000.0002
core_west
1800.0000.0005
core_east
1800.0000.0008
asbr_west
1800.0000.0009
asbr_east
1800.0000.0010
abr_sjc
1800.0000.0011
abr_lax
1800.0000.0012
abr_nyc
1800.0000.0013
abr_dfw
1800.0000.0015
dist_oak
1800.0000.0018
dist_nj
1800.0000.0020
acc_nj
1800.0000.0021
acc_ri
1800.0000.0027
dist_arl
1800.0000.0028
dist_msq
1800.0000.0029
acc_arl
1800.0000.0030
acc_msq
=========================================================================
A:ALA-A#
Page 224
7210 SAS M, X OS Routing Protocols Guide
IS-IS
interface
Syntax
Context
interface [ip-int-name | ip-address] [detail]
show>router>isis
Description
This command shows IS-IS interface information. When no ip-addr or the ip-int-name is specified, all interfaces are listed.
Parameters
ip-address — Only displays the interface information associated with the specified IP address.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
ip-int-name — Only displays the interface information associated with the specified IP interface name.
detail — All output is given in the detailed format.
Output
IS-IS Interface Output — The following table describes IS-IS interface output fields.
Label
Description
Interface
The interface name.
Level
Specifies the interface level (1, 2, or 1 and 2).
CirID
Specifies the circuit identifier.
Oper State
Up — The interface is operationally up.
Down — The interface is operationally down.
L1/L2 Metric
Interface metric for Level 1 and Level 2, if none are set to 0.
Sample Output
A:ALA-A# show router isis interface
===============================================================================
ISIS Interfaces
===============================================================================
Interface
Level CircID Oper State
L1/L2 Metric
------------------------------------------------------------------------------system
L1L2 1
Up
10/10
if2/1
L2
8
Up
-/10
if2/2
L1
5
Up
10/if2/3
L1
6
Up
10/if2/4
L1
7
Up
10/if2/5
L2
2
Up
-/10
lag-1
L2
3
Up
-/10
if2/8
L2
4
Up
-/10
------------------------------------------------------------------------------Interfaces : 8
===============================================================================
A:ALA-A#
*A:7210-SAS>show>router>isis# interface detail
===============================================================================
7210 SAS M, X OS Routing Protocols Guide
Page 225
Show Commands
ISIS Interfaces
===============================================================================
------------------------------------------------------------------------------Interface
: abcd
Level Capability: L1L2
Oper State
: Down
Admin State
: Up
Auth Type
: None
Circuit Id
: 7
Retransmit Int. : 5
Type
: Broadcast
LSP Pacing Int. : 100
Mesh Group
: Inactive
CSNP Int.
: 10
Bfd Enabled
: No
Te Metric
: 0
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State: Disabled
Ldp Tm Left
: 0
Route Tag
: None
Level
Desg. IS
Auth Type
Hello Timer
Priority
:
:
:
:
:
1
0000.0000.0000
None
9
64
Adjacencies
: 0
Metric
Hello Mult.
Passive
: 10
: 3
: No
Level
Desg. IS
Auth Type
Hello Timer
Priority
:
:
:
:
:
2
0000.0000.0000
None
9
64
Adjacencies
: 0
Metric
Hello Mult.
Passive
: 10
: 3
: No
===============================================================================
*A:7210-SAS>show>router>isis#
*A:7210-SAS>show>router>isis# interface abcd detail
===============================================================================
ISIS Interfaces
===============================================================================
------------------------------------------------------------------------------Interface
: abcd
Level Capability: L1L2
Oper State
: Down
Admin State
: Up
Auth Type
: None
Circuit Id
: 7
Retransmit Int. : 5
Type
: Broadcast
LSP Pacing Int. : 100
Mesh Group
: Inactive
CSNP Int.
: 10
Bfd Enabled
: No
Te Metric
: 0
Te State
: Down
Admin Groups
: None
Ldp Sync
: outOfService
Ldp Sync Wait
: Disabled
Ldp Timer State: Disabled
Ldp Tm Left
: 0
Route Tag
: None
Page 226
Level
Desg. IS
Auth Type
Hello Timer
Priority
:
:
:
:
:
1
0000.0000.0000
None
9
64
Adjacencies
: 0
Metric
Hello Mult.
Passive
: 10
: 3
: No
Level
Desg. IS
Auth Type
: 2
: 0000.0000.0000
: None
Adjacencies
: 0
Metric
: 10
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Hello Timer
Priority
: 9
: 64
Hello Mult.
Passive
: 3
: No
===============================================================================
*A:7210-SAS>show>router>isis#
routes
Syntax
Context
routes [ipv4-unicast]
show>router>isis
Description
This command displays the routes in the IS-IS route table.
Parameters
ipv4-unicast — Displays IPv4 unicast parameters.
Output
IS-IS Route Output — The following table describes IS-IS route output fields.
Label
Description
Prefix
The route prefix and mask.
Metric MT
The route’s metric.
Lvl/Type
Specifies the level (1 or 2) and the route type, Internal (Int) or External
(Ext).
Version
SPF version that generated route.
Nexthop
System ID of nexthop, give hostname if possible.
Hostname
Hostname for the specific system-id.
Sample Output
*A:Dut-A# show router isis routes
===============================================================================
Route Table
===============================================================================
Prefix
Metric
Lvl/Typ Ver.
SysID/Hostname
NextHop
MT
------------------------------------------------------------------------------10.10.1.0/24
10
1/Int. 5
Dut-A
0.0.0.0
0
10.10.3.0/24
20
1/Int. 137
Dut-B
10.10.1.2
0
10.10.4.0/24
20
1/Int. 137
Dut-B
10.10.1.2
0
10.10.5.0/24
30
1/Int. 137
Dut-B
10.10.1.2
0
10.10.9.0/24
60
1/Int. 52
Dut-F
10.10.21.6
0
10.10.10.0/24
70
1/Int. 52
Dut-F
7210 SAS M, X OS Routing Protocols Guide
Page 227
Show Commands
10.10.21.6
0
10.10.12.0/24
20
1/Int.
10.10.1.2
0
10.10.13.0/24
10
1/Int.
0.0.0.0
0
10.10.14.0/24
20
1/Int.
10.10.21.6
0
10.10.15.0/24
30
1/Int.
10.10.1.2
0
10.10.16.0/24
30
1/Int.
10.10.1.2
0
10.10.21.0/24
10
1/Int.
0.0.0.0
0
10.10.22.0/24
30
1/Int.
10.10.1.2
0
10.20.1.1/32
0
1/Int.
0.0.0.0
0
10.20.1.2/32
10
1/Int.
10.10.1.2
0
10.20.1.3/32
20
1/Int.
10.10.1.2
0
10.20.1.4/32
20
1/Int.
10.10.1.2
0
10.20.1.5/32
30
1/Int.
10.10.1.2
0
10.20.1.6/32
10
1/Int.
10.10.21.6
0
3FFE::A0A:100/120
10
1/Int.
::
0
10.10.1.0/24
10
1/Int.
0.0.0.0
2
10.10.13.0/24
10
1/Int.
0.0.0.0
2
10.10.21.0/24
10
1/Int.
0.0.0.0
2
10.20.1.1/32
0
1/Int.
0.0.0.0
2
3FFE::A0A:100/120
10
1/Int.
::
2
3FFE::A0A:300/120
20
1/Int.
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A0A:400/120
20
1/Int.
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A0A:500/120
30
1/Int.
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A0A:900/120
60
1/Int.
FE80::2285:FFFF:FE00:0-"ies-1-3FFE::A0A:1501" 2
3FFE::A0A:A00/120
70
1/Int.
FE80::2285:FFFF:FE00:0-"ies-1-3FFE::A0A:1501" 2
3FFE::A0A:C00/120
20
1/Int.
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A0A:D00/120
10
1/Int.
::
2
3FFE::A0A:E00/120
20
1/Int.
FE80::2285:FFFF:FE00:0-"ies-1-3FFE::A0A:1501" 2
3FFE::A0A:F00/120
30
1/Int.
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A0A:1000/120
30
1/Int.
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
Page 228
137
Dut-B
7
Dut-A
52
Dut-F
137
Dut-B
137
Dut-B
48
Dut-A
137
Dut-B
10
Dut-A
137
Dut-B
137
Dut-B
137
Dut-B
137
Dut-B
52
Dut-F
5
Dut-A
65
Dut-A
65
Dut-A
65
Dut-A
65
Dut-A
65
Dut-A
116
Dut-B
116
Dut-B
130
Dut-B
71
Dut-F
71
Dut-F
116
Dut-B
65
Dut-A
71
Dut-F
130
Dut-B
130
Dut-B
7210 SAS M, X OS Routing Protocols Guide
IS-IS
3FFE::A0A:1500/120
10
1/Int. 65
Dut-A
::
2
3FFE::A0A:1600/120
30
1/Int. 127
Dut-B
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A14:101/128
0
1/Int. 65
Dut-A
::
2
3FFE::A14:102/128
10
1/Int. 116
Dut-B
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A14:103/128
20
1/Int. 130
Dut-B
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A14:104/128
20
1/Int. 127
Dut-B
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A14:105/128
30
1/Int. 130
Dut-B
FE80::2281:1FF:FE01:1-"ip-3FFE::A0A:101" 2
3FFE::A14:106/128
10
1/Int. 71
Dut-F
FE80::2285:FFFF:FE00:0-"ies-1-3FFE::A0A:1501" 2
------------------------------------------------------------------------------Routes : 43
===============================================================================
*A:Dut-A#
spf
Syntax
Context
Description
Output
spf [detail]
show>router>isis
This command displays information regarding SPF calculation.
Router ISIS Output — The following table describes the output fields for ISIS SPF.
Label
Description
Node
The route node and mask.
Interface
The outgoing interface name for the route.
Metric
The route’s metric.
Nexthop
The system ID of nexthop or hostname.
SNPA
The Subnetwork Points of Attachment (SNPA) where a router is physically attached to a subnetwork.
Sample Output
A:ALA-A# show router isis spf
===============================================================================
Path Table
===============================================================================
Node
Interface
Nexthop
------------------------------------------------------------------------------abr_sjc.00
if2/2
dist_oak
abr_sjc.00
if2/3
dist_nj
7210 SAS M, X OS Routing Protocols Guide
Page 229
Show Commands
dist_oak.00
if2/2
dist_oak
dist_nj.00
if2/3
dist_nj
acc_nj.00
if2/3
dist_nj
acc_ri.00
if2/3
dist_nj
core_west.00
if2/8
core_west
core_east.00
lag-1
core_east
asbr_west.00
if2/8
core_west
asbr_east.00
if2/5
asbr_east
abr_sjc.00
lag-1
core_east
abr_sjc.00
if2/8
core_west
abr_lax.00
lag-1
core_east
abr_lax.00
if2/8
core_west
abr_dfw.00
if2/5
asbr_east
abr_dfw.00
lag-1
core_east
abr_dfw.00
if2/8
core_west
dist_arl.00
if2/5
asbr_east
dist_arl.00
lag-1
core_east
dist_arl.00
if2/8
core_west
dist_msq.00
if2/5
asbr_east
dist_msq.00
lag-1
core_east
dist_msq.00
if2/8
core_west
acc_arl.00
if2/5
asbr_east
acc_arl.00
lag-1
core_east
acc_arl.00
if2/8
core_west
acc_msq.00
if2/5
asbr_east
acc_msq.00
lag-1
core_east
acc_msq.00
if2/8
core_west
acc_msq.03
if2/5
asbr_east
acc_msq.03
lag-1
core_east
acc_msq.03
if2/8
core_west
acc_msq.04
if2/5
asbr_east
acc_msq.04
lag-1
core_east
acc_msq.04
if2/8
core_west
===============================================================================
A:ALA-A#
A:ALA-A# show router isis spf detail
===============================================================================
Path Table
===============================================================================
Node
: abr_sjc.00
Metric : 20
Interface : if2/2
SNPA
: 00:00:00:00:00:00
Nexthop
: dist_oak
Page 230
Node
: abr_sjc.00
Interface : if2/3
Nexthop
: dist_nj
Metric : 20
SNPA
: 00:00:00:00:00:00
Node
: dist_oak.00
Interface : if2/2
Nexthop
: dist_oak
Metric : 10
SNPA
: 00:00:00:00:00:00
Node
: dist_nj.00
Interface : if2/3
Nexthop
: dist_nj
Metric : 10
SNPA
: 00:00:00:00:00:00
Node
: acc_nj.00
Interface : if2/3
Metric : 20
SNPA
: 00:00:00:00:00:00
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Nexthop
: dist_nj
Node
: acc_ri.00
Interface : if2/3
Nexthop
: dist_nj
Metric : 20
SNPA
: 00:00:00:00:00:00
Node
: core_west.00
Interface : if2/8
Nexthop
: core_west
Metric : 10
SNPA
: 00:00:00:00:00:00
...
===============================================================================
A:ALA-A#
statistics
Syntax
Context
Description
Output
statistics
show>router>isis
This command displays information regarding IS-IS traffic statistics.
IS-IS Statistics Output — This table describes IS-IS statistics output fields.
Label
Description
Purge Initiated
The number of times purges have been initiated.
SPF Runs
The number of times shortest path first calculations have been made.
LSP Regens
The count of LSP regenerations.
Requests
The number of CSPF requests made to the protocol.
Paths Found
The number of responses to CSPF requests for which paths satisfying
the constraints were found.
PDU Type
The PDU type.
Received
The count of link state PDUs received by this instance of the
protocol.
Processed
The count of link state PDUs processed by this instance of the protocol.
Dropped
The count of link state PDUs dropped by this instance of the
protocol.
Sent
The count of link state PDUs sent out by this instance of the
protocol.
7210 SAS M, X OS Routing Protocols Guide
Page 231
Show Commands
Label
Retransmitted
Description (Continued)
The count of link state PDUs that had to be retransmitted by this
instance of the protocol.
Sample Output
A:ALA-A>config>router# show router isis statistics
===============================================================================
ISIS Statistics
===============================================================================
ISIS Instance
: 1
SPF Runs
: 44
Purge Initiated
: 0
LSP Regens.
: 54
CSPF Statistics
Requests
: 0
Request Drops : 0
Paths Found
: 0
Paths Not Found: 0
------------------------------------------------------------------------------PDU Type
Received
Processed Dropped
Sent
Retransmitted
------------------------------------------------------------------------------LSP
185
184
1
54
0
IIH
8382
8382
0
2796
0
CSNP
3352
3352
0
0
0
PSNP
0
0
0
4
0
Unknown
0
0
0
0
0
===============================================================================
A:ALA-A>config>router#
status
Syntax
Context
Description
Output
status
show>router>isis
This command displays information regarding IS-IS status.
IS-IS Status Output — The following table describes IS-IS status output fields.
Label
Description
System-id
Neighbor system ID.
Admin State
Up — IS-IS is administratively up.
Down — IS-IS is administratively down.
Ipv4 Routing
Enabled — IPv4 routing is enabled.
Disabled — IPv4 routing is disabled.
Ipv6 Routing
Page 232
Disabled — IPv6 routing is disabled.
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Label
Description (Continued)
Enabled, Native — IPv6 routing is enabled.
Enabled, Multi-topology — Multi-topology TLVs for IPv6
routing is enabled.
Multi-topology
Disabled — Multi-topology TLVs for IPv6 routing is disabled.
Enabled — Multi-topology TLVs for IPv6 routing is enabled.
Last Enabled
The date/time when IS-IS was last enabled in the router.
Level Capability
The routing level for the IS-IS routing process.
Authentication
Check
True — All IS-IS mismatched protocol packets are rejected.
False — Authentication is performed on received IS-IS protocol
packets but mismatched packets are not rejected.
Authentication
Type
The method of authentication used to verify the authenticity of packets
sent by neighboring routers on an IS-IS interface.
Traffic Engineering
Enabled — TE is enabled for the router.
Disabled — TE is disabled so that TE metrics are not generated
and are ignored when received by this node.
Graceful Restart
Enabled — Graceful restart is enabled for this instance of IS-IS on
the router.
Disabled — Graceful restart capability is disabled for this instance
of IS-IS on the router.
Ldp Sync Admin
State
Indicates whether the IGP-LDP synchronization feature is enabled or
disabled on all interfaces participating in the OSPF routing protocol.
Sample Output
*A:Dut-A>config>router>isis# show router isis status
===============================================================================
ISIS Status
===============================================================================
System Id
: 0100.2000.1001
Admin State
: Up
Ipv4 Routing
: Enabled
Last Enabled
: 02/13/2008 02:22:38
Level Capability
: L1L2
Authentication Check : True
Authentication Type : None
CSNP-Authentication : Enabled
HELLO-Authentication : Enabled
PSNP-Authentication : Enabled
Traffic Engineering : Enabled
7210 SAS M, X OS Routing Protocols Guide
Page 233
Show Commands
Graceful Restart
: Disabled
GR Helper Mode
: Disabled
LSP Lifetime
: 1200
LSP Wait
: 1 sec (Max)
1 sec (Initial)
1 sec (Second)
Adjacency Check
: loose
L1 Auth Type
: none
L2 Auth Type
: none
L1 CSNP-Authenticati*: Enabled
L1 HELLO-Authenticat*: Enabled
L1 PSNP-Authenticati*: Enabled
L1 Preference
: 15
L2 Preference
: 18
L1 Ext. Preference
: 160
L2 Ext. Preference
: 165
L1 Wide Metrics
: Enabled
L2 Wide Metrics
: Enabled
L1 LSDB Overload
: Disabled
L2 LSDB Overload
: Disabled
L1 LSPs
: 6
L2 LSPs
: 6
Last SPF
: 02/13/2008 19:32:16
SPF Wait
: 10 sec (Max)
1000 ms (Initial)
1000 ms (Second)
Export Policies
: None
Multicast Import
: None
Multi-topology
: Disabled
Area Addresses
: 01
Ldp Sync Admin State : Up
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Dut-A>config>router>isis#
*A:ALU_SIM11>show>router>isis# status
===============================================================================
ISIS Status
===============================================================================
System Id
: 0010.0100.1002
Admin State
: Up
Ipv4 Routing
: Enabled
Last Enabled
: 07/06/2010 12:28:12
Level Capability
: L1L2
Authentication Check : True
Authentication Type : None
CSNP-Authentication : Enabled
HELLO-Authentication : Enabled
PSNP-Authentication : Enabled
Traffic Engineering : Disabled
Graceful Restart
: Disabled
GR Helper Mode
: Disabled
LSP Lifetime
: 1200
LSP Wait
: 5 sec (Max)
0 sec (Initial)
1 sec (Second)
Adjacency Check
: loose
L1 Auth Type
: none
L2 Auth Type
: none
L1 CSNP-Authenticati*: Enabled
L1 HELLO-Authenticat*: Enabled
L1 PSNP-Authenticati*: Enabled
L1 Preference
: 15
L2 Preference
: 18
Page 234
7210 SAS M, X OS Routing Protocols Guide
IS-IS
L1 Ext. Preference
: 160
L2 Ext. Preference
: 165
L1 Wide Metrics
: Disabled
L2 Wide Metrics
: Disabled
L1 LSDB Overload
: Disabled
L2 LSDB Overload
: Disabled
L1 LSPs
: 3
L2 LSPs
: 3
Last SPF
: 07/06/2010 12:28:17
SPF Wait
: 10 sec (Max)
1000 ms (Initial)
1000 ms (Second)
Export Policies
: None
Multicast Import
: None
Multi-topology
: Disabled
Advertise-Passive-On*: Disabled
Suppress Default
: Disabled
Default Route Tag
: None
Area Addresses
: 01
Ldp Sync Admin State : Up
LDP-over-RSVP
: Disabled
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:ALU_SIM11>show>router>isis#
summary-address
Syntax
Context
Description
Output
summary-address [ip-prefix[/prefix-length]]
show>router>isis
Displays ISIS summary addresses.
Router ISIS Summary Address Output — The following table describes the ISIS summary address
output fields.
Label
Description
Address
The IP address.
Level
Specifies the IS-IS level from which the prefix should be summarized.
Sample Output
A:ALA-48# show router isis summary-address
===============================================================================
ISIS Summary Address
===============================================================================
Address
Level
------------------------------------------------------------------------------1.0.0.0/8
L1
2.1.0.0/24
L1L2
3.1.2.3/32
L2
-------------------------------------------------------------------------------
7210 SAS M, X OS Routing Protocols Guide
Page 235
Clear Commands
Summary Addresses : 3
===============================================================================
A:ALA-48#
Clear Commands
isis
Syntax
Context
Description
isis
clear>router>isis
This command enables the context to clear and reset ISIS protocol entities.
adjacency
Syntax
Context
adjacency [system-id]
clear>router>isis
Description
This command clears and resets the entries from the IS-IS adjacency database.
Parameters
system-id — When the system ID is entered, only the specified entries are removed from the IS-IS adjacency
database.
Values
6 octets system identifier (xxxx.xxxx.xxxx)
database
Syntax
Context
database [system-id]
clear>router>isis
Description
This command removes the entries from the IS-IS link-state database which contains information about
PDUs.
Parameters
system-id — When the system ID is entered, only the specified entries are removed from the IS-IS link-state
database.
Values
Page 236
6 octets system identifier (xxxx.xxxx.xxxx)
7210 SAS M, X OS Routing Protocols Guide
IS-IS
export
Syntax
Context
Description
export
clear>router>isis
This command re-evaluates route policies participating in the export mechanism, either as importers or
exporters of routes.
spf-log
Syntax
Context
Description
spf-log
clear>router>isis
This command clears the SPF log.
statistics
Syntax
Context
Description
statistics
clear>router>isis
This command clears and resets IS-IS statistics.
7210 SAS M, X OS Routing Protocols Guide
Page 237
Debug Commands
Debug Commands
adjacency
Syntax
Context
Description
[no] adjacency [ip-int-name | ip-address | nbr-system-id]
debug>router>isis
This command enables debugging for IS-IS adjacency.
The no form of the command disables debugging.
Parameters
ip-address — Only displays the interface information associated with the specified IP address.
Values
ipv4-address:
a.b.c.d
cspf
Syntax
Context
Description
[no] cspf
debug>router>isis
This command enables debugging for IS-IS cspf.
The no form of the command disables debugging.
graceful-restart
Syntax
Context
Description
[no] graceful-restart
debug>router>isis
This command enables debugging for IS-IS graceful-restart.
The no form of the command disables debugging.
interface
Syntax
Context
Description
interface [ip-int-name | ip-address]
no interface
debug>router>isis
This command enables debugging for IS-IS interface.
The no form of the command disables debugging.
Page 238
7210 SAS M, X OS Routing Protocols Guide
IS-IS
Parameters
ip-address — Only displays the interface information associated with the specified IP address.
Values
ipv4-address:
a.b.c.d
leak
Syntax
leak [ip-address]
no leak
Context
debug>router>isis
Description
This command enables debugging for IS-IS leaks.
The no form of the command disables debugging.
Parameters
ip-address — Only displays the interface information associated with the specified IP address.
Values
ipv4-address:
a.b.c.d
lsdb
Syntax
Context
Description
[no] lsdb [level-number] [system-id | lsp-id]
debug>router>isis
This command enables debugging for Link State DataBase (LSDB).
The no form of the command disables debugging.
misc
Syntax
Context
Description
[no] misc
debug>router>isis
This command enables debugging for IS-IS misc.
The no form of the command disables debugging.
packet
Syntax
Context
Description
packet [packet-type] [ip-int-name | ip-address] [detail]
debug>router>isis
This command enables debugging for IS-IS packets.
The no form of the command disables debugging.
7210 SAS M, X OS Routing Protocols Guide
Page 239
Debug Commands
Parameters
ip-address — Only displays the interface information associated with the specified IP address.
Values
ipv4-address:
a.b.c.d
rtm
Syntax
Context
Description
rtm [ip-address]
no rtm
debug>router>isis
This command enables debugging for IS-IS route table manager (RTM).
The no form of the command disables debugging.
Parameters
ip-address — Only displays the interface information associated with the specified IP address.
Values
ipv4-address:
a.b.c.d ipv6-address:
x:x:x:x:x:x:x:x [-interface]
x:x:x:x:x:x:d.d.d.d [-interface]
x: [0 — FFFF]H
d: [0 — 255]D
spf
Syntax
Context
Description
[no] spf [level-number] [system-id]
debug>router>isis
This command enables debugging for IS-IS SFP.
The no form of the command disables debugging.
Page 240
7210 SAS M, X OS Routing Protocols Guide
BGP
In This Chapter
This chapter provides information to configure BGP.
NOTE: BGP is not supported in 7210 SAS-M access-uplink mode.
Topics in this chapter include:
•
BGP Overview on page 242
→ BGP Communication on page 242
→ Group Configuration and Peers on page 244
→ Hierarchical Levels on page 245
→ Route Reflection on page 245
→ BGP Route Tunnel on page 244
→ RSVP-TE LSP Shortcut for BGP Next-Hop Resolution on page 238
→ BGP Confederations on page 240
→ BGP Add-Path (R9.0 R4) on page 245
→ Command Interactions and Dependencies on page 254
−
Changing the Autonomous System Number on page 254
−
Changing the Router ID at the Configuration Level on page 256
−
Changing the Local AS Number on page 255
−
Hold Time and Keep Alive Timer Dependencies on page 256
−
Import and Export Route Policies on page 256
−
Route Damping and Route Policies on page 257
−
AS Override on page 257
−
TTL Security for BGP on page 258
•
BGP Configuration Process Overview on page 259
•
Configuration Notes on page 260
7210 SAS M, X OS Routing Protocols Guide
Page 241
BGP Overview
BGP Overview
Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol. An autonomous
system is a network or a group of routers logically organized and controlled by a common network
administration. BGP enables routers to exchange network reachability information, including
information about other ASs that traffic must traverse to reach other routers in other ASs. In order
to implement BGP, the AS number must be specified in the config>router context. A 7210 SAS
BGP configuration must contain at least one group and include information about at least one SAS
neighbor (peer).
AS paths are the routes to each destination. Other attributes, such as the path’s origin, the multiple
exit discriminator (MED), the local preference and communities included with the route are called
path attributes. When BGP interprets routing and topology information, loops can be detected and
eliminated. Route preference for routes learned from the configured peer(s) can be enabled among
groups of routes to enforce administrative preferences and routing policy decisions.
Note: In 7210, MP-BGP (family vpn-ipv4) is supported for use in L3 VPN services (aka VPRN
services). BGP (family ipv4) is not available for use in the 'base' routing instance. It is only
available for use as PE-CE routing protocol.
BGP Communication
There are two types of BGP peers, internal BGP (IBGP) and external BGP (EBGP) (Figure 8).
•
IBGP is used to communicate with peers in the same autonomous system. Routes received
from an IBGP peer in the same autonomous system are not advertised to other IBGP peers
(unless the router is a route reflector) but can be advertised to an EBGP peer.
•
EBGP is used to communicate with peers in different autonomous systems. Routes
received from an router in a different AS can be advertised to both EBGP and IBGP peers.
Autonomous systems share routing information, such as routes to each destination and information
about the route or AS path, with other ASs using BGP. Routing tables contain lists of known
routers, reachable addresses, and associated path cost metrics to each router. BGP uses the
information and path attributes to compile a network topology.
Message Types
Four message types are used by BGP to negotiate parameters, exchange routing information and
indicate errors. They are:
•
Page 242
Open Message — After a transport protocol connection is established, the first message
sent by each side is an Open message. If the Open message is acceptable, a Keepalive
7210 SAS M, X OS Routing Protocols Guide
BGP
message confirming the Open is sent back. Once the Open is confirmed, Update,
Keepalive, and Notification messages can be exchanged.
Open messages consist of the BGP header and the following fields:
→ Version — The current BGP version number is 4.
→ Local AS number — The autonomous system number is configured in the
config>router context.
→ Hold time — Configure the maximum time BGP will wait between successive
messages (either keep alive or update) from its peer, before closing the connection.
Configure the local hold time with in the config>router>bgp context.
→ BGP identifier — IP address of the BGP system or the router ID. The router ID must
be a valid host address.
•
Update Message — Update messages are used to transfer routing information between
BGP peers. The information contained in the packet can be used to construct a graph
describing the relationships of the various autonomous systems. By applying rules, routing
information loops and some other anomalies can be detected and removed from the interAS routing,
The update messages consist of a BGP header and the following optional fields:
→ Unfeasible routes length — The field length which lists the routes being withdrawn
from service because they are considered unreachable.
→ Withdrawn routes — The associated IP address prefixes for the routes withdrawn from
service.
→ Total path attribute length — The total length of the path field that provides the
attributes for a possible route to a destination.
→
Path attributes — The path attributes presented in variable length TLV
format.
→ Network layer reachability information (NLRI) — IP address prefixes of reachability
information.
•
Keepalive Message — Keepalive messages, consisting of only a 19 octet message header,
are exchanged between peers frequently so hold timers do not expire. The keepalive
messages determine if a link is unavailable.
•
Notification — A Notification message is sent when an error condition is detected. The
peering session is terminated and the BGP connection (TCP connection) is closed
immediately after sending it.
7210 SAS M, X OS Routing Protocols Guide
Page 243
BGP Overview
AS 100
AS 200
ALA-E
ALA-B
IBGP
EBGP
ALA-D
IBGP
ALA-F
IBGP
ALA-A
IBGP
IBGP
IBGP
ALA-C
Figure 8: BGP Configuration
Group Configuration and Peers
To enable BGP routing, participating routers must have BGP enabled and be assigned to an
autonomous system and the neighbor (peer) relationships must be specified. A router typically
belongs to only one AS. TCP connections must be established in order for neighbors to exchange
routing information and updates. Neighbors exchange BGP open messages that includes
information such as AS numbers, BGP versions, router IDs, and hold-time values. Keepalive
messages determine if a connection is established and operational. The hold-time value specifies
the maximum time BGP will wait between successive messages (either keep alive or update) from
its peer, before closing the connection.
In BGP, peers are arranged into groups. A group must contain at least one neighbor. A neighbor
must belong to a group. Groups allow multiple peers to share similar configuration attributes.
Although neighbors do not have to belong to the same AS, they must be able to communicate with
each other. If TCP connections are not established between two neighbors, the BGP peering will
not be established and updates will not be exchanged.
Peer relationships are defined by configuring the IP address of the routers that are peers of the local
BGP system. When neighbor and peer relationships are configured, the BGP peers exchange
update messages to advertise network reachability information.
Page 244
7210 SAS M, X OS Routing Protocols Guide
BGP
Hierarchical Levels
BGP parameters are initially applied on the global level. These parameters are inherited by the
group and neighbor (peer) levels. Parameters can be modified and overridden on a level-specific
basis. BGP command hierarchy consists of three levels:
•
Global level
•
Group level
•
Neighbor level
Many of the hierarchical BGP commands can be modified on different levels. The most specific
value is used. That is, a BGP group-specific command takes precedence over a global BGP
command. A neighbor-specific statement takes precedence over a global BGP and group-specific
command; for example, if you modify a BGP neighbor-level command default, the new value
takes precedence over group- and global- level settings.
NOTE: Careful planning is essential to implement commands that can affect the behavior of
global, group, and neighbor-levels. Because the BGP commands are hierarchical, analyze the
values that can disable features on the global or group levels that must be enabled at the neighbor
level. For example, if you enable the damping command on the global level but want it disabled
only for a specific neighbor (not for all neighbors within the group), you cannot configure a
double-no command (no no damping) to enable the feature.
Route Reflection
In a standard BGP configuration, all BGP speakers within an AS, must have full BGP mesh to
ensure that all externally learned routes are redistributed through the entire AS. IBGP speakers do
not re-advertise routes learned from one IBGP peer to another IBGP peer. If a network grows,
scaling issues could emerge because of the full mesh configuration requirement. Instead of peering
with all other IBGP routers in the network, each IBGP router only peers with a router configured
as a route reflector.
Route reflection circumvents the full mesh requirement but maintains the full distribution of
external routing information within an AS. Route reflection is effective in large networks because
it is manageable, scalable, and easy to implement. Route reflection is implemented in autonomous
systems with a large internal BGP mesh to reduce the number of IBGP sessions required within an
AS.
Note: 7210 devices can be configured only as route reflector clients. Only the client functionality
of a route reflector described here is available for use with 7210. The route reflector "server-side"
functionality cannot be used on 7210.
7210 SAS M, X OS Routing Protocols Guide
Page 245
BGP Overview
A large AS can be sub-divided into one or more clusters. Each cluster contains at least one
route reflector which is responsible for redistributing route updates to all clients. Route
reflector clients do not need to maintain a full peering mesh between each other. They
only require a peering to the route reflector(s) in their cluster. The route reflectors must
maintain a full peering mesh between all non-clients within the AS.
Each route reflector must be assigned a cluster ID and specify which neighbors are clients
and which are non-clients to determine which neighbors should receive reflected routes
and which should be treated as a standard IBGP peer. Additional configuration is not
required for the route reflector besides the typical BGP neighbor parameters.
Figure 9 displays a simple full-mesh configuration with several BGP routers. When SR-A
receives a route from SR-1 (an external neighbor), it must advertise route information to
all of its IBGP peers (SR-B, SR-C, SR-D, etc). To prevent loops, IBGP learned routes are
not re-advertised to other IBGP peers.
Figure 9: Fully Meshed BGP Configuration
Page 246
7210 SAS M, X OS Routing Protocols Guide
BGP
When route reflectors are configured, the routers within a cluster do not need to be fully meshed.
Figure 9 depicts a fully meshed network and Figure 10 depicts the same network but with route
reflectors configured to minimize the IBGP mesh between SR-A, SR-B, SR-C, and SR-D. SR-A,
configured as the route reflector, is responsible for redistributing route updates to clients SR-B,
SR-C, and SR-D. IBGP peering between SR-B, SR-C and SR-D is not necessary because even
IBGP learned routes are reflected to the route reflector’s clients.
In Figure 10, SR-E and SR-F are shown as non-clients of the route reflector. As a result, a full
mesh of IBGP peerings must be maintained between, SR-A, SR-E and SR-F.
SR-1
EBGP Peering
SR-A
Route
Reflector
SR-F
(Non-client)
SR-B
SR-E
(Client)
(Non-client)
Route Reflector
Cluster 0.0.0.1
SR-C
SR-D
(Client)
(Client)
OSRG055
Figure 10: BGP Configuration with Route Reflectors
A route reflector enables communication between the clients and non-client peers. Clients of a
route reflector do not need to be fully meshed but non-client peers need to be fully meshed within
an AS.
A grouping, called a cluster, is composed of a route reflector (or a redundant pair of route
reflectors configured with the same cluster-id) and its client peers. Each route reflector is assigned
a cluster ID and this defines the cluster that it and its clients belong to. Multiple route reflectors can
be configured within a cluster for redundancy. A router assumes the role as a route reflector by
configuring the cluster cluster-id command. No other command is required unless you
want to disable reflection to specific clients.
7210 SAS M, X OS Routing Protocols Guide
Page 247
BGP Overview
When a route reflector receives an advertised route, it selects the best path. If the best path was
received from an EBGP peer then it is typically advertised, with next hop unchanged, to all clients
and non-client peers of the route reflector. If the best path was received from a non-client peer then
it is advertised to all clients of the route reflector. If the best path was received from a client then it
is advertised to all clients and non-client peers.
Page 248
7210 SAS M, X OS Routing Protocols Guide
BGP
Fast External Failover
Fast external failover on a group and neighbor basis is supported. For eBGP neighbors, this feature
controls whether the router should drop an eBGP session immediately upon an interface-down
event, or whether the BGP session should be kept up until the hold-time expires.
When fast external failover is disabled, the eBGP session stays up until the hold-time expires or
the interface comes back up. If the BGP routes become unreachable as a result of the down IP
interface, BGP withdraws the unavailable route immediately from other peers.
Sending of BGP Communities
The capability to explicitly enable or disable the sending of the BGP community attribute to BGP
neighbors, other than through the use of policy statements, is supported.
This feature allows an administrator to enable or disable the sending of BGP communities to an
associated peer. This feature overrides communities that are already associated with a given route
or that may have been added via an export route policy. In other words, even if the export policies
leave BGP communities attached to a given route, when the disable-communities feature is
enabled, no BGP communities are advertised to the associated BGP peers.
7210 SAS M, X OS Routing Protocols Guide
Page 249
BGP Overview
Route Selection Criteria
For each prefix in the routing table, the routing protocol selects the best path. Then, the best path is
compared to the next path in the list until all paths in the list are exhausted. The following
parameters are used to determine the best path:
1. Routes are not considered if they are unreachable.
2. An RTM’s preference is lowered as well as the hierarchy of routes from a different
protocol. The lower the preference the higher the chance of the route being the active
route.
3. Routes with higher local preference have preference.
4. Routes with the shorter AS path have preference.
5. Routes with the lower origin have preference. IGP = 0 EGP = 1 INCOMPLETE = 2
6. Routes with the lowest MED metric have preference. Routes with no MED value are
exempted from this step unless always-compare-med is configured.
7. Routes learned by an EBGP peer rather than those learned from an IBGP peer are
preferred.
8. Routes with the lowest IGP cost to the next-hop path attribute are preferred.
9. Routes with the lowest BGP-ID are preferred.
10. Routes with shortest cluster list are preferred.
11. Routes with lowest next-hop IP address are preferred.
Notes:
1. For BGP-VPN routes with the same prefix but a different Route Distinguisher (RD) that
are imported in a VRF, if ECMP is not enabled in that VRF, the above selection criteria
are used until parameter point 8. If all selection criteria are still the same after that point,
the last updated route will be selected.
2. For BGP-VPN routes with the same prefix but a different Route Distinguisher (RD) that
reach parameter point 8 in the selection criteria, all routes will be flagged as BEST and
USED although the actual number of used routes will depend on the ECMP value
configured in the VRF.
3. For BGP-VPN routes with the same prefix and same Route Distinguisher (RD) that reach
parameter point 8 in the selection criteria, such routes will be flagged as BEST but
parameter points 9-11 will determine which routes are submitted to the VRF and marked
as USED in accordance to the ECMP value configured in the VRF.
Page 250
7210 SAS M, X OS Routing Protocols Guide
BGP
IP-VPNs MSE Direct Route Comparison
IP-VPNs MSE direct route comparison of BGP and MP-BGP learned routes provides the ability to
compare a route received from a CE peer (inside the VPRN context) to the same route prefix
received as a BGP VPN-IPv4 update from a PE peer. This is required when a CE router is dual
homed and advertises the same customer route prefix to two (or more) PE peers. Each PE router
needs to choose one of the prefixes, which was done previously, based on the Route Table
Preference as opposed to comparing the BGP attributes. The BGP route decision process takes into
account the following attribute values of the two routes to decide the best route to install in the
VRF table:
1. Routes are not considered if they are unreachable.
2. Routes of the protocol with the lowest preference value are selected.
3. BGP routes with higher local preference have preference.
4. BGP routes with the shorter AS path have preference. (This is checked independent of the
as-path-ignore parameter.)
5. Routes with the lowest origin type have preference (where IGP is lower than EGP and
EGP is lower than INCOMPLETE).
6. BGP routes with the lowest MED metric have preference. (If MED values are present,
they are checked independent of the always-compare-med parameter.)
7. BGP CE-PE learned routes are preferred over MP-BGP learned routes.
7210 SAS M, X OS Routing Protocols Guide
Page 251
BGP Overview
Enabling Best External
Enabling the best-external feature is supported only at the config>router>bgp level. This feature
can be enabled/disabled on a per address family basis, with IPv4 and IPv6 as the only options
supported initially. Enabling best-external for IPv4 causes the new advertisement rules to apply to
both regular IPv4 unicast routes as well as labeled-IPv4 (SAFI4) routes. Similarly, enabling bestexternal for IPv6 causes the new advertisement rules to apply to both regular IPv6 unicast routes as
well as labeled-IPv6 (SAFI4) routes.
The advertise-external command cannot be applied to a route reflector unless client-to-client
reflection is disabled (disable-client-reflect in the CLI).
BGP Decision Process with Best External
When best-external is enabled for an address family, all routes belonging to that address family
must be classified internally as either “internal” or “external”. A route is “internal” if:
•
It was received from an IBGP peer in the same AS.
•
It was originated by a router in the same or a different RR cluster of the same AS.
•
It was received from an IBGP peer in the same member AS of a confederation.
A route is external if:
•
It was received from an EBGP peer in a different AS.
•
Itwas received from a confed-EBGP peer in a different member AS of a confederation.
The tie-breaking steps of the decision process are run as usual on all of the routes (both “internal”
and “external”) for a particular destination until only one path, the best path, is left. If this is an
external route then the decision process must be rerun on only the “internal” routes to find the
single best path in that subset. This “best internal” route is advertised to confed-EBGP peers, as
described in Advertisement Rules with Best External on page 253.
If the overall best path found by the first run of the decision process is an internal route with
NEXT_HOP n the decision process must be rerun on only the “external” routes with NEXT_HOP
not equal to n to find the single best path in that subset. This “best external” route is advertised to
IBGP peers, as described in Advertisement Rules with Best External on page 253.
Page 252
7210 SAS M, X OS Routing Protocols Guide
BGP
Advertisement Rules with Best External
The advertisement rules when advertise-external is enabled can be summari zed as follows:
1. If a router has advertise-external enabled and its best overall route is an internal route
then this best route should be advertised to:
→ All IBGP RR clients (if the route came from a non-client peer) or all IBGP non-clients
(if the route came from a client peer).
→ And all EBGP peers
→ And all confed-EBGP peers
→ But if there is a best external route it should be sent to IBGP client and non-client
peers instead of the best overall route
2. If a router has advertise-external enabled and its best overall route is an external route
then this best route should be advertised to:
→ All IBGP peers
→ And all EBGP peers
→ And all confed-EBGP peers
→ But if there is a best internal route (see section 5.2) it should be sent to all confedEBGP peers instead of the best overall route
Displaying Best-External Routes
BGP show commands display the following information for this feature:
•
For each RIB-IN entry in the output of the show router bgp routes prefix hunt command
there is a Flags field that indicates the origin of the route and whether it is valid, best, used,
etc. This feature reflects an “Advertised” value in the Flags field. This indicatse that the
route was advertised to one or more peers. If the “Advertised” flag is present but the
“Best” flag is not the operator can determine that the route was probably a best-external.
•
The show router bgp neighbor advertised-routes command display sall advertised
routes to that peer, including routes that were overall best, best-external and best-internal.
•
The advertise-external configuration (specifically the address families for which it is
enabled) is displayed as part of the show router bgp output.
Note that the overall best, best-external and best-internal routes for a prefix can be determined
from the output of the show router bgp routes prefix command. The first external route to be
displayed in the output is always be the best-external route and the first internal route to be
displayed in the output is always be the best-internal route. Only one of these routes will have the
“Best” flag set, and this will be the overall best route.
7210 SAS M, X OS Routing Protocols Guide
Page 253
BGP Overview
Command Interactions and Dependencies
This section highlights the BGP command interactions and dependencies which are important for
configuration or operational maintenance of 7210 SAS routers. Topics covered in this section are:
•
Changing the Autonomous System Number on page 254
•
Changing a Confederation Number on page 254
•
Changing the Router ID at the Configuration Level on page 256
•
Changing the Local AS Number on page 255
•
Hold Time and Keep Alive Timer Dependencies on page 256
•
Import and Export Route Policies on page 256
•
Route Damping and Route Policies on page 257
Note that this information can be found in the BGP Command Reference on page 281 which
provides detailed descriptions of the configuration commands.
Changing the Autonomous System Number
If the AS number is changed on a router with an active BGP instance, the new AS number will not
be used until the BGP instance is restarted either by administratively disabling or enabling the
BGP instance or by rebooting the system with the new configuration.
Page 254
7210 SAS M, X OS Routing Protocols Guide
BGP
Changing the Local AS Number
Changing the local AS of an active BGP instance:
•
At the global level causes the BGP instance to restart with the new local AS number.
•
At the group level causes BGP to re-establish the peer relationships with all peers in the
group with the new local AS number.
•
At the neighbor level causes BGP to re-establish the peer relationship with the new local
AS number.
7210 SAS M, X OS Routing Protocols Guide
Page 255
BGP Overview
Changing the Router ID at the Configuration Level
If you configure a new router ID in the config>router context, protocols are not
automatically restarted with the new router ID. The next time a protocol is (re) initialized the new
router ID is used. An interim period of time can occur when different protocols use different router
IDs.
Hold Time and Keep Alive Timer Dependencies
The BGP hold time specifies the maximum time BGP will wait between successive messages
(either keep alive or update) from its peer, before closing the connection. This configuration
parameter can be set at three levels. The most specific value is used.
•
Global level — applies to all peers
•
Group level — applies to all peers in group
•
Neighbor level — only applies to specified peer
Although the keep alive time can be user specified, the configured keep alive timer is overridden
by the value of hold time under the following circumstances:
•
If the hold time specified is less than the configured keep alive time, then the operational
keep alive time is set to one third of the specified hold time; the configured keep alive time
is unchanged.
•
If the hold time is set to zero, then the operational value of the keep alive time is set to
zero; the configured keep alive time is unchanged. This means that the connection with the
peer will be up permanently and no keep alive packets are sent to the peer.
If the hold time or keep alive values are changed, the changed timer values take effect when the
new peering relationship is established. Changing the values cause the peerings to restart. The
changed timer values are used when re-negotiating the peer relationship.
Import and Export Route Policies
Import and export route policy statements are specified for BGP on the global, group, and neighbor
level. Up to five unique policy statement names can be specified in the command line per level.
The most specific command is applied to the peer. Defining the policy statement name is not
required before being applied. Policy statements are evaluated in the order in which they are
specified within the command context.
The import and export policies configured on different levels are not cumulative. The most specific
value is used. An import or export policy command specified on the neighbor level takes
Page 256
7210 SAS M, X OS Routing Protocols Guide
BGP
precedence over the same command specified on the group or global level. An import or
export policy command specified on the group level takes precedence over the same command
specified on the global level.
Route Damping and Route Policies
To prevent BGP systems from sending excessive route changes to peers, BGP route damping can
be implemented. Damping can reduce the number of update messages sent between BGP peers, to
reduce the load on peers, without adversely affecting the route convergence time for stable routes.
The damping profile defined in the policy statement is applied to control route damping
parameters. Route damping characteristics are specified in a route damping profile and are
referenced in the action for the policy statement or in the action for a policy entry. Damping can be
specified at the global, group, or neighbor level with the most specific command applied to the
peer.
AS Override
The BGP-4 Explicit AS Override simplifies the use of the same AS number (ASN) across multiple
RFC 2547 VPRN sites.
The Explicit AS Override feature can be used in VPRN scenarios where a customer is running
BGP as the PE-CE protocol and some or all of the CE locations are in the same Autonomous
System (AS). With normal BGP, two sites in the same AS would not be able to reach each other
directly since there is an apparent loop in the ASPATH.
With AS Override enabled on an egress eBGP session, the Service Provider network can rewrite
the customer ASN in the ASPATH with its own ASN as the route is advertised to the other sites
within the same VPRN.
7210 SAS M, X OS Routing Protocols Guide
Page 257
BGP Overview
TTL Security for BGP
The BGP TTL Security Hack (BTSH) was originally designed to protect the BGP infrastructure
from CPU utilization-based attacks. It is derived on the fact that the vast majority of ISP eBGP
peerings are established between adjacent routers. Since TTL spoofing is considered nearly
impossible, a mechanism based on an expected TTL value can provide a simple and reasonably
robust defense from infrastructure attacks based on forged BGP packets.
While TSH is most effective in protecting directly connected peers, it can also provide a lower
level of protection to multi-hop sessions. When a multi-hop BGP session is required, the expected
TTL value can be set to 255 minus the configured range-of-hops. This approach can provide a
qualitatively lower degree of security for BGP (such as a DoS attack could, theoretically, be
launched by compromising a box in the path). However, BTSH will catch a vast majority of
observed distributed DoS (DDoS) attacks against eBGP. For further information, refer to draft-gillbtsh-xx.txt, The BGP TTL Security Hack (BTSH).
TSH can be used to protect LDP peering sessions as well. For details, see draft-chen-ldp-ttl-xx.txt,
TTL-Based Security Option for LDP Hello Message.
The TSH implementation supports the ability to configure TTL security per BGP peer and evaluate
(in hardware) the incoming TTL value against the configured TTL value. If the incoming TTL
value is less than the configured TTL value, the packets are discarded and a log is generated.
Page 258
7210 SAS M, X OS Routing Protocols Guide
BGP
BGP Configuration Process Overview
Figure 11 displays the process to provision basic BGP parameters.
START
CONFIGURE GLOBAL ROUTER PARAMETERS
- CONFIGURE ROUTER ID
- ASSIGN AUTONOMOUS SYSTEM NUMBER
- CONFIGURE CONFEDERATIONS (optional)
CONFIGURE BGP GROUP PARAMETERS
CONFIGURE BGP NEIGHBOR PARAMETERS
TURN UP
Figure 11: BGP Configuration and Implementation Flow
7210 SAS M, X OS Routing Protocols Guide
Page 259
Configuration Notes
Configuration Notes
This section describes BGP configuration caveats.
General
•
Before BGP can be configured, the router ID (a valid host address, not the MAC address
default) and autonomous system global parameters must be configured.
•
BGP instances must be explicitly created on each BGP peer. There are no default BGP
instances on a 7210 SAS.
BGP Defaults
The following list summarizes the BGP configuration defaults:
Page 260
•
By default, the 7210 SAS is not assigned to an AS.
•
A BGP instance is created in the administratively enabled state.
•
A BGP group is created in the administratively enabled state.
•
A BGP neighbor is created in the administratively enabled state.
•
No BGP router ID is specified. If no BGP router ID is specified, BGP uses the router
system interface address.
•
The 7210 SAS BGP timer defaults are the values recommended in IETF drafts and RFCs
(see BGP MIB Notes on page 261)
•
If no import route policy statements are specified, then all BGP routes are accepted.
•
If no export route policy statements specified, then all best and used BGP routes are
advertised and non-BGP routes are not advertised.
7210 SAS M, X OS Routing Protocols Guide
BGP
BGP MIB Notes
The 7210 SAS implementation of the RFC 1657 MIB variables listed in Table 7 differs from the
IETF MIB specification.
Table 7: 7210 SAS and IETF MIB Variations
Description
RFC 1657
Allowed
Values
Allowed
Values
bgpPeerMinASOriginationInterval
Time interval in seconds for the
MinASOriginationInterval timer.
The suggested value for this timer
is 15 seconds.
1 — 65535
2 — 255
bgpPeerMinRouteAdvertisementInterval
Time interval in seconds for the
MinRouteAdvertisementInterval
timer. The suggested value for this
timer is 30.
1 — 65535
MIB Variable
a
1 — 255
a.A value of 0 is supported when the rapid-update command is applied to an address family that
supports it.
If SNMP is used to set a value of X to the MIB variable in Table 8, there are three possible results:
Table 8: MIB Variable with SNMP
Condition
Result
X is within IETF MIB values
and
X is within 7210 SAS values
SNMP set operation does not return an error
MIB variable set to X
X is within IETF MIB values
and
X is outside 7210 SAS values
SNMP set operation does not return an error
MIB variable set to “nearest” 7210 SAS supported
value (e.g. 7210 SAS range is 2 - 255 and X = 65535,
MIB variable will be set to 255)
Log message generated
X is outside IETF MIB values
and
X is outside 7210 SAS values
SNMP set operation returns an error
7210 SAS M, X OS Routing Protocols Guide
Page 261
Configuration Notes
When the value set using SNMP is within the IETF allowed values and outside the 7210 SAS
values as specified in Table 7 and Table 8, a log message is generated.
The log messages that display are similar to the following log messages:
Sample Log Message for setting bgpPeerMinASOriginationInterval to 65535
576 2006/11/12 19:45:48 [Snmpd] BGP-4-bgpVariableRangeViolation: Trying
to set bgpPeerMinASOrigInt to 65535 - valid range is [2-255] - setting to
255
Sample Log Message for setting bgpPeerMinASOriginationInterval to 1
594 2006/11/12 19:48:05 [Snmpd] BGP-4-bgpVariableRangeViolation: Trying
to set bgpPeerMinASOrigInt to 1 - valid range is [2-255] - setting to 2
Sample Log Message for setting bgpPeerMinRouteAdvertisementInterval to 256
535 2006/11/12 19:40:53 [Snmpd] BGP-4-bgpVariableRangeViolation: Trying
to set bgpPeerMinRouteAdvInt to 256 - valid range is [2-255] - setting to
255
Sample Log Message for setting bgpPeerMinRouteAdvertisementInterval to 1
566 2006/11/12 19:44:41 [Snmpd] BGP-4-bgpVariableRangeViolation: Trying
to set bgpPeerMinRouteAdvInt to 1 - valid range is [2-255] - setting to 2
Page 262
7210 SAS M, X OS Routing Protocols Guide
BGP
Configuring BGP with CLI
This section provides information to configure BGP using the command line interface.
Topics in this section include:
•
BGP Configuration Overview on page 264
→ Preconfiguration Requirements on page 264
→ BGP Hierarchy on page 264
→ Internal and External BGP Configurations on page 264
→ BGP Confederations on page 253
→ BGP Route Reflectors on page 256
•
Basic BGP Configuration on page 266
•
Common Configuration Tasks on page 268
→ Creating an Autonomous System on page 269
→ Configuring a Router ID on page 270
→ BGP Components on page 271
→ Configuring Group Attributes on page 273
→ Configuring Neighbor Attributes on page 274
→ Configuring Route Reflection on page 267
→ Configuring a Confederation on page 268
•
BGP Configuration Management Tasks on page 275
→ Modifying an AS Number on page 275
→ Modifying the BGP Router ID on page 276
→ Deleting a Neighbor on page 278
→ Deleting Groups on page 279
→ Editing BGP Parameters on page 280
7210 SAS M OS Routing Protocols Guide
Page 263
BGP Configuration Overview
BGP Configuration Overview
Preconfiguration Requirements
Before BGP can be implemented, the following entities must be configured:
•
The autonomous system (AS) number for the router.
An AS number is a globally unique value which associates a router to a specific
autonomous system. This number is used to exchange exterior routing information with
neighboring ASs and as an identifier of the AS itself. Each router participating in BGP
must have an AS number specified.
In order to implement BGP, the AS number must be specified in the config>router
context.
•
Router ID — The router ID is the IP address of the local router. The router ID identifies a
packet’s origin. The router ID must be a valid host address.
BGP Hierarchy
BGP is configured in the config>router>bgp context. Three hierarchical levels are included in
BGP configurations:
•
Global level
•
Group level
•
Neighbor level
Commands and parameters configured on the global level are inherited to the group and neighbor
levels although parameters configured on the group and neighbor levels take precedence over
global configurations.
Internal and External BGP Configurations
A BGP system is comprised of ASs which share network reachability information. Network
reachability information is shared with adjacent BGP systems neighbors. Further logical groupings
are established within BGP systems within ASs. BGP supports two types of routing information
exchanges:
•
Page 264
External BGP (EBGP) is used between ASs.
7210 SAS M OS Routing Protocols Guide
BGP
EBGP speakers peer to different ASs and typically share a subnet. In an external group,
the next hop is dependent upon the interface shared between the external peer and the
specific neighbor. The multihop command must be specified if an EBGP peer is more
than one hop away from the local router. The next hop to the peer must be configured so
that the two systems can establish a BGP session.
•
Internal BGP (IBGP) is used within an AS.
An IBGP speaker peers to the same AS and typically does not share a subnet. Neighbors
do not have to be directly connected to each other. Since IBGP peers are not required to be
directly connected, IBGP uses the IGP path (the IP next-hop learned from the IGP) to
reach an IBGP peer for its peering connection.
7210 SAS M OS Routing Protocols Guide
Page 265
Basic BGP Configuration
Basic BGP Configuration
This section provides information to configure BGP and configuration examples of common
configuration tasks. The minimal BGP parameters that need to be configured are:
•
An autonomous system number for the router.
•
A router ID - Note that if a new or different router ID value is entered in the BGP context,
then the new valued takes precedence and overwrites the router-level router ID.
•
A BGP peer group.
•
A BGP neighbor with which to peer.
•
A BGP peer-AS that is associated with the above peer.
The BGP configuration commands have three primary configuration levels: bgp for global
configurations, group name for BGP group configuration, and neighbor ip-address for BGP
neighbor configuration. Within the different levels, many of the configuration commands are
repeated. For the repeated commands, the command that is most specific to the neighboring router
is in effect, that is, neighbor settings have precedence over group settings which have precedence
over BGP global settings.
Following is a sample configuration that includes the above parameters. The other parameters
shown below are optional:
info
#-------------------------------------------------echo "IP Configuration"
#-------------------------------------------------...
autonomous-system 200
confederation 300 members 200 400 500 600
router-id 10.10.10.103
#-------------------------------------------------...
#-------------------------------------------------echo "BGP Configuration"
#-------------------------------------------------bgp
graceful-restart
exit
cluster 0.0.0.100
export "direct2bgp"
router-id 10.0.0.12
group "To_AS_10000"
connect-retry 20
hold-time 90
keepalive 30
local-preference 100
remove-private
peer-as 10000
neighbor 10.0.0.8
description "To_Router B - EBGP Peer"
Page 266
7210 SAS M OS Routing Protocols Guide
BGP
connect-retry 20
hold-time 90
keepalive 30
local-address 10.0.0.12
passive
preference 99
peer-as 10000
exit
exit
group "To_AS_30000"
connect-retry 20
hold-time 90
keepalive 30
local-preference 100
remove-private
peer-as 30000
neighbor 10.0.3.10
description "To_Router C - EBGP Peer"
connect-retry 20
hold-time 90
keepalive 30
peer-as 30000
exit
exit
group "To_AS_40000"
connect-retry 20
hold-time 30
keepalive 30
local-preference 100
peer-as 65206
neighbor 10.0.0.15
description "To_Router E - Sub Confederation AS 65205"
connect-retry 20
hold-time 90
keepalive 30
local-address 10.0.0.12
peer-as 65205
exit
exit
exit
#-------------------------------------------------....
A:ALA-48>config>router#
7210 SAS M OS Routing Protocols Guide
Page 267
Common Configuration Tasks
Common Configuration Tasks
This section provides a brief overview of the tasks that must be performed to configure BGP and
provides the CLI commands. In order to enable BGP, one AS must be configured and at least one
group must be configured which includes neighbor (system or IP address) and peering information
(AS number).
Configure BGP hierarchically, the global level (applies to all peers), the group level (applies to all
peers in peer-group), or the neighbor level (only applies to specified peer). By default, group
members inherit the group’s configuration parameters although a parameter can be modified on a
per-member basis without affecting the group-level parameters.
Many of the hierarchical BGP commands can be used on different levels. The most specific value
is used. That is, a BGP group-specific command takes precedence over a global BGP command. A
neighbor-specific statement takes precedence over a global BGP or group-specific command.
All BGP instances must be explicitly created on each node. Once created, BGP is administratively
enabled.
Configuration planning is essential to organize ASs and the 7210 nodes within the ASs, and
determine the internal and external BGP peering.
To configure a basic autonomous system, perform the following tasks:
1. Prepare a plan detailing the autonomous sytem(s), the 7210 SAS node belonging to each
group, group names, and peering connections.
2. Associate each 7210 SAS node with an autonomous system number.
3. Configure each 7210 SAS node with a router ID.
4. Associate each 7210 SAS node with a peer group name.
5. Specify the local IP address that will be used by the group or neighbor when communicating
with BGP peers.
6. Specify neighbors.
7. Specify the autonomous system number associated with each neighbor.
Page 268
7210 SAS M OS Routing Protocols Guide
BGP
Creating an Autonomous System
Before BGP can be configured, the autonomous system must be configured first. In BGP, routing
reachability information is exchanged between autonomous systems (ASs). An AS is a group of
networks that share routing information. The autonomous-system command associates an
autonomous system number to the router being configured. A 7210 SAS device can only belong to
one AS. The autonomous-system command is configured in the config>router context.
Use the following CLI syntax to associate a 7210 SAS device to an autonomous system:
CLI Syntax: config>router# autonomous-system autonomous-system
The 7210 SAS devise supports 4 bytes AS numbers by default. This means autonomous-system
can have any value from 1 to 4294967295. The following example displays autonomous system
configuration command usage:
Example: config>router# autonomous-system 100
The following example displays the autonomous system configuration:
ALA-B>config>router# info
#-----------------------------------------# IP Configuration
#-----------------------------------------interface "system"
address 10.10.10.104/32
exit
interface "to-103"
address 10.0.0.104/24
port 1/1/1
exit
autonomous-system 100
#-----------------------------------------ALA-B>config>router#
7210 SAS M OS Routing Protocols Guide
Page 269
Common Configuration Tasks
Configuring a Router ID
In BGP, routing information is exchanged between autonomous systems. The BGP router ID,
expressed like an IP address, uniquely identifies the router. It can be set to be the same as the
loopback address.
Note that if a new or different router ID value is entered in the BGP context, then the new router ID
value is used instead of the router ID configured on the router level, system interface level, or
inherited from the MAC address. The router-level router ID value remains intact. A router ID can
be derived by:
•
Defining the value in the config>router router-id context.
•
Defining the system interface in the config>router>interface ip-int-name context.
•
Inheriting the last four bytes of the MAC address.
•
The BGP protocol level. The router ID can be defined in the config>router>bgp router-id
context and is only used within BGP.
When configuring a new router ID, protocols are not automatically restarted with the new router
ID. The next time a protocol is (re) initialized the new router ID is used. An interim period of time
can occur when different protocols use different router IDs. To force the new router ID, issue the
shutdown and no shutdown commands for each protocol that uses the router ID or restart the
entire router. Use the following CLI syntax to configure the router ID:
CLI Syntax: config>router# router-id router-id
The following example displays router ID configuration command usage:
Example: config>router# router-id 10.10.10.104
The following example displays the router ID configuration:
ALA-B>config>router# info
---------------------------------------------# IP Configuration
#-----------------------------------------interface "system"
address 10.10.10.104/32
exit
interface "to-103"
address 10.0.0.104/24
port 1/1/1
exit
autonomous-system 100
router-id 10.10.10.104
#-----------------------------------------...
ALA-B>config>router#
Page 270
7210 SAS M OS Routing Protocols Guide
BGP
BGP Components
Use the CLI syntax displayed below to configure the following BGP attributes:
•
BGP Components on page 271
•
Configuring Group Attributes on page 273
•
Configuring Neighbor Attributes on page 274
•
Configuring Route Reflection on page 267
•
Configuring a Confederation on page 268
Configuring BGP
Once the BGP protocol instance is created, the no shutdown command is not required since BGP
is administratively enabled upon creation. Minimally, to enable BGP on a router, you must
associate an autonomous system number for the router, have a pre-configured router ID or system
interface, create a peer group, neighbor, and associate a peer AS number. There are no default
groups or neighbors. Each group and neighbor must be explicitly configured.
All parameters configured for BGP are applied to the group and are inherited by each peer, but a
group parameter can be overridden on a specific basis. BGP command hierarchy consists of three
levels:
•
The global level
•
The group level
•
The neighbor level
For example:
CLI Syntax: config>router# bgp
group
neighbor
(global level)
(group level)
(neighbor level)
NOTE: Careful planning is essential to implement commands that can affect the behavior of
global, group, and neighbor levels. Because the BGP commands are hierarchical, analyze the
values that can disable features on a particular level.
7210 SAS M OS Routing Protocols Guide
Page 271
Common Configuration Tasks
The following example displays the basic BGP configuration:
ALA-B>config>router# info
#-----------------------------------------# BGP Configuration
#-----------------------------------------#-----------------------------------------# BGP
#-----------------------------------------bgp
exit
#-----------------------------------------ALA-B>config>router#
Page 272
7210 SAS M OS Routing Protocols Guide
BGP
Configuring Group Attributes
A group is a collection of related BGP peers. The group name should be a descriptive name for the
group. Follow your group, name, and ID naming conventions for consistency and to help when
troubleshooting faults.
All parameters configured for a peer group are applied to the group and are inherited by each peer
(neighbor), but a group parameter can be overridden on a specific neighbor-level basis.
The following example displays the BGP group configuration:
ALA-B>config>router>bgp# info
---------------------------------------------...
group "headquarters1"
description "HQ execs"
local-address 10.0.0.104
disable-communities standard extended
ttl-security 255
exit
exit
...
---------------------------------------------ALA-B>config>router>bgp#
7210 SAS M OS Routing Protocols Guide
Page 273
Common Configuration Tasks
Configuring Neighbor Attributes
After you create a group name and assign options, add neighbors within the same autonomous
system to create IBGP connections and/or neighbors in different autonomous systems to create
EBGP peers. All parameters configured for the peer group level are applied to each neighbor, but a
group parameter can be overridden on a specific neighbor basis.
The following example displays neighbors configured in group “headquarters1”.
ALA-B>config>router>bgp# info
---------------------------------------------...
group "headquarters1"
description "HQ execs"
local-address 10.0.0.104
disable-communities standard extended
ttl-security 255
neighbor 10.0.0.5
passive
peer-as 300
exit
neighbor 10.0.0.106
peer-as 100
exit
neighbor 17.5.0.2
hold-time 90
keepalive 30
min-as-origination 15
local-preference 170
peer-as 10701
exit
neighbor 17.5.1.2
hold-time 90
keepalive 30
min-as-origination 15
local-preference 100
min-route-advertisement 30
preference 170
peer-as 10702
exit
exit
...
---------------------------------------------ALA-B>config>router>bgp#
Page 274
7210 SAS M OS Routing Protocols Guide
BGP
BGP Configuration Management Tasks
This section discusses the following BGP configuration management tasks:
•
Modifying an AS Number on page 275
•
Modifying a Confederation Number on page 270
•
Modifying the BGP Router ID on page 276
•
Modifying the Router-Level Router ID on page 277
•
Deleting a Neighbor on page 278
•
Deleting Groups on page 279
•
Editing BGP Parameters on page 280
Modifying an AS Number
You can modify an AS number on a 7210 SAS but the new AS number will not be used until the
BGP instance is restarted either by administratively disabling or enabling the BGP instance or by
rebooting the system with the new configuration.
Since the AS number is defined in the config>router context, not in the BGP configuration
context, the BGP instance is not aware of the change. Re-examine the plan detailing the
autonomous sytem(s), the SRs belonging to each group, group names, and peering connections.
Changing an AS number on a 7210 SAS could cause configuration inconsistencies if associated
peer-as values are not also modified as required. At the group and neighbor levels, BGP will reestablish the peer relationships with all peers in the group with the new AS number.
Use the following CLI syntax to change an autonomous system number:
CLI Syntax: config>router# autonomous-system autonomous-system
CLI Syntax: config>router# bgp
group name
neighbor ip-addr
peer-as asn
Example: config>router# autonomous-system 400
config>router# bgp
config>router>bgp# group headquarters1
config>router>bgp>group# neighbor 10.10.10.103
config>router>bgp>group# peer-as 400
config>router>bgp>group# exit
7210 SAS M OS Routing Protocols Guide
Page 275
Common Configuration Tasks
Modifying the BGP Router ID
Changing the router ID number in the BGP context causes the new value to overwrite the router ID
configured on the router level, system interface level, or the value inherited from the MAC
address. Changing the router ID on a router could cause configuration inconsistencies if associated
values are not also modified.
When configuring a new router ID, protocols are not automatically restarted with the new router
ID. The next time BGP is (re) initialized the new router ID is used. To force the new router ID,
issue the shutdown and no shutdown commands for BGP or restart the entire router.
Example: config>router>bgp#
config>router>bgp#
config>router>bgp#
config>router>bgp#
router-id 10.0.0.104
shutdown
router-id 10.0.0.123
no shutdown
This example displays the BGP configuration with the BGP router ID specified:
ALA-B>config>router>bgp# info detail
---------------------------------------------no shutdown
no description
no always-compare-med
ibgp-multipath load-balance
. . .
router-id 10.0.0.123
---------------------------------------------ALA-B>config>router>bgp#
Page 276
7210 SAS M OS Routing Protocols Guide
BGP
Modifying the Router-Level Router ID
Changing the router ID number in the config>router context causes the new value to
overwrite the router ID configured on the protocol level, system interface level, or the value
inherited from the MAC address. Changing the router ID on a router could cause configuration
inconsistencies if associated values are not also modified.
When configuring a new router ID, protocols are not automatically restarted with the new router
ID. The next time a protocol is (re) initialized the new router ID is used. An interim period of time
can occur when different protocols use different router IDs. To force the new router ID, issue the
shutdown and no shutdown commands for each protocol that uses the router ID or restart the
entire router.
Use the following CLI syntax to change a router ID:
CLI Syntax: config>router# router-id router-id
Example: config>router# router-id 10.10.10.104
config>router# no shutdown
config>router>bgp# shutdown
config>router>bgp# no shutdown
The following example displays the router ID configuration:
ALA-A>config>router# info
#-----------------------------------------# IP Configuration
#-----------------------------------------interface "system"
address 10.10.10.104/32
exit
interface "to-103"
address 10.0.0.104/24
port 1/1/1
exit
autonomous-system 100
router-id 10.10.10.104
#-----------------------------------------ALA-B>config>router#
7210 SAS M OS Routing Protocols Guide
Page 277
Common Configuration Tasks
Deleting a Neighbor
In order to delete a neighbor, you must shut down the neighbor before issuing the no neighbor
ip-addr command.
Use the following CLI syntax to delete a neighbor:
CLI Syntax: config>router# bgp
group name
no neighbor ip-address
shutdown
no peer-as asn
shutdown
Example: config>router# bgp
config>router>bgp# group headquarters1
config>router>bgp>group# neighbor 10.0.0.103
config>router>bgp>group>neighbor# shutdown
config>router>bgp>group>neighbor# exit
config>router>bgp>group# no neighbor 10.0.0.103
The following example displays the “headquarters1” configuration with the neighbor
10.0.0.103 removed.
ALA-B>config>router>bgp# info
---------------------------------------------group "headquarters1"
description “HQ execs”
local-address 10.0.0.104
neighbor 10.0.0.5
passive
peer-as 300
exit
exit
---------------------------------------------ALA-B>config>router>bgp#
Page 278
7210 SAS M OS Routing Protocols Guide
BGP
Deleting Groups
In order to delete a group, the neighbor configurations must be shut down first. After each
neighbor is shut down, you must shut down the group before issuing the no group name
command.
Use the following CLI syntax to shut down a peer and neighbor and then delete a group:
CLI Syntax: config>router# bgp
no group name
shutdown
no neighbor ip-address
shutdown
shutdown
Example: config>router# bgp
config>router>bgp# group headquarters1
config>router>bgp>group# neighbor 10.0.0.105
config>router>bgp>group>neighbor# shutdown
config>router>bgp>group>neighbor# exit
config>router>bgp>group# neighbor 10.0.0.103
config>router>bgp>group# shutdown
config>router>bgp>group# exit
config>router>bgp# no headquarters1
If you try to delete the group without shutting down the peer-group, the following message
appears:
ALA-B>config>router>bgp# no group headquarters1
MINOR: CLI BGP Peer Group should be shutdown before deleted. BGP Peer
Group not deleted.
7210 SAS M OS Routing Protocols Guide
Page 279
Common Configuration Tasks
Editing BGP Parameters
You can change existing BGP parameters in the CLI. The changes are applied immediately.
CLI Syntax: config>router# bgp
group name
. . .
neighbor ip-address
. . .
Example:
config>router# bgp
Refer to BGP Components on page 271 for a complete list of BGP parameters.
Page 280
7210 SAS M OS Routing Protocols Guide
BGP
BGP Command Reference
Command Hierarchies
Configuration Commands
• Global BGP Commands on page 281
• Group BGP Commands on page 283
• Neighbor BGP Commands on page 285
• Show Commands on page 287
• Clear Commands on page 287
• Debug Commands on page 287
—Global BGP Commands
config
— router [router-name]
— [no] bgp
— [no] advertise-inactive
— [no] aggregator-id-zero
— always-compare-med {zero | infinity}
— no always-compare-med
— as-path-ignore [ipv4] [vpn-ipv4] [l2-vpn]
— no as-path-ignore
— authentication-key [authentication-key | hash-key] [hash | hash2]
— no authentication-key
— auth-keychain name
— connect-retry seconds
— no connect-retry
— [no] damping
— description description-string
— no description
— [no] disable-4byte-asn
— disable-communities [standard] [extended]
— no disable-communities
— [no] disable-fast-external-failover
— [no] enable-peer-tracking
— export policy-name [policy-name…(up to 5 max)]
— no export
— family [ipv4] [vpn-ipv4] [l2-vpn]
— no family
— hold-time seconds [strict]
— no hold-time
— [no] import
— import policy-name [policy-name …(up to 5 max)]
— no import
— keepalive seconds
— no keepalive
7210 SAS M OS Routing Protocols Guide
Page 281
BGP Command Reference
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
Page 282
local-as as-number [private]
no local-as
local-preference local-preference
no local-preference
loop-detect {drop-peer | discard-route | ignore-loop | off}
no loop-detect
med-out {number | igp-cost}
no med-out
min-as-origination seconds
no min-as-origination
min-route-advertisement seconds
no min-route-advertisement
multihop ttl-value
no multihop
[no] outbound-route-filtering
— [no] extended-community
— [no] accept-orf
— send-orf [comm-id...(up to 32 max)]
— no send-orf comm-id
[no] path-mtu-discovery
preference preference
purge-timer
no purge-timer
no preference
[no] rapid-update[l2-vpn][no] rapid-withdrawal
[no] remove-private
router-id (bgp) ip-address
no router-id (bgp)
[no] shutdown
[no] vpn-apply-export
[no] vpn-apply-import
7210 SAS M OS Routing Protocols Guide
BGP
—Group BGP Commands
config
— router [router-name]
— [no] bgp
— [no] group name
— [no] advertise-inactive
— [no] aggregator-id-zero
— authentication-key [authentication-key | hash-key] [hash | hash2]
— no authentication-key
— auth-keychain name
— [no] bfd-enable
— connect-retry seconds
— no connect-retry
— [no] damping
— description description-string
— no description
— [no] disable-4byte-asn
— [no] disable-capability-negotiation
— disable-communities [standard] [extended]
— no disable-communities
— [no] disable-fast-external-failover
— [no] enable-peer-tracking
— export policy-name [policy-name…(up to 5 max)]
— no export
— family [ipv4] [vpn-ipv4] [l2-vpn]
— no family
— [no] flowspec-validate
— hold-time seconds [strict]
— no hold-time
— import policy-name [policy-name …(up to 5 max)]
— no import
— keepalive seconds
— no keepalive
— local-address ip-address
— no local-address
— local-as as-number [private]
— no local-as
— local-preference local preference
— no local-preference
— loop-detect {drop-peer | discard-route | ignore-loop | off}
— no loop-detect
— med-out {number | igp-cost}
— no med-out
— min-as-origination seconds
— no min-as-origination
— min-route-advertisement seconds
— no min-route-advertisement
— multihop ttl-value
— no multihop
— [no] next-hop-self {[ipv4] [l2-vpn]}]
— [no] outbound-route-filtering
— [no] extended-community
— [no] accept-orf
— send-orf [comm-id...(up to 32 max)]
7210 SAS M OS Routing Protocols Guide
Page 283
BGP Command Reference
— no send-orf [comm-id]
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
Page 284
[no] path-mtu-discovery
peer-as as-number
no peer-as
preference preference
no preference
prefix-limit limit
no prefix-limit
[no] remove-private
[no] shutdown
ttl-security min-ttl-value
no ttl-security
type {internal | external}
no type
[no] vpn-apply-export
[no] vpn-apply-import
7210 SAS M OS Routing Protocols Guide
BGP
—Neighbor BGP Commands
config
— router [router-name]
— [no] bgp
— [no] group name
— [no] neighbor ip-address
— [no] advertise-inactive
— [no] aggregator-id-zero
— auth-keychain name
— authentication-key [authentication-key | hash-key] [hash | hash2]
— no authentication-key
— connect-retry seconds
— no connect-retry
— [no] damping
— description description-string
— no description
— [no] disable-4byte-asn
— [no] disable-capability-negotiation
—
— disable-communities [standard] [extended]
— no disable-communities
— [no] disable-fast-external-failover
— [no] enable-peer-tracking
— export policy-name [policy-name…(up to 5 max)]
— no export
— family [ipv4] [vpn-ipv4] [l2-vpn]
— no family
— hold-time seconds [strict]
— no hold-time
— import policy-name [policy-name …(up to 5 max)]
— no import
— keepalive seconds
— no keepalive
— local-address ip-address
— no local-address
— local-as as-number [private]
— no local-as
— local-preference local-preference
— no local-preference
— loop-detect {drop-peer | discard-route | ignore-loop | off}
— no loop-detect
— med-out {number | igp-cost}
— no med-out
— min-as-origination seconds
— no min-as-origination
— min-route-advertisement seconds
— no min-route-advertisement
— multihop ttl-value
— no multihop
— [no] next-hop-self
— [no] outbound-route-filtering
— [no] extended-community
— [no] accept-orf
— send-orf [comm-id...(up to 32 max)]
7210 SAS M OS Routing Protocols Guide
Page 285
BGP Command Reference
— no send-orf [comm-id]
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
peer-as as-number
no peer-as
preference preference
no preference
prefix-limit limit
no prefix-limit
[no] remove-private {limited}
[no] shutdown
ttl-security min-ttl-value
no ttl-security
type {internal | external}
no type
[no] vpn-apply-export
[no] vpn-apply-import
Other BGP-Related Commands
config
— router [router-name]
— autonomous-system as-number
— no autonomous-system
— router-id ip-address
— no router-id
Page 286
7210 SAS M OS Routing Protocols Guide
BGP
Show Commands
show
— router [router-instance]
— bgp
— auth-keychain keychain-name
— damping [ip-prefix[/prefix-length]] [decayed|history|suppressed] [detail] [ipv4]
—
— damping [ip-prefix | prefix-length] [detail]
— group [name] [detail]
— neighbor [ip-address [detail]]
— neighbor [as-number [detail]]
— neighbor ip-address [family [type mvpn-type]] filter1 [brief]
— neighbor ip-address [family] filter2
— neighbor as-address [family] filter2
— neighbor orf [filter3]
— neighbor ip-address graceful-restart
— next-hop [ family] [ip-address] [detail]
— paths
— routes [family] [brief]
— routes [family] prefix [detail | longer | hunt [brief]]
— routes [family [type mvpn-type]] community comm-id
— routes [family [type mvpn-type]] aspath-regex reg-ex
— routes mvpn-ipv4 type mvpn-type {originator-ip ip-address | source-ip ip-address |
group-ip ip-address | source-as as-number} [hunt | detail]
— routes l2-vpn l2vpn-type {[rd rd] | [siteid site-id] | [veid veid] [offset vpls-base-offset]}
— summary [all]
— summary [family family] [neighbor ip-address]
Clear Commands
clear
— router
— bgp
— damping [{prefix/ip-prefix-length] [neighbor ip-address]} | {group name}]
— flap-statistics [{prefix/mask [neighbor ip-address] | [group group-name] | [regex reg-exp
| policy policy-name}]
— neighbor {ip-address | as as-number | external | all} [soft | soft-inbound]
— neighbor {ip-address | as as-number | external | all} statistics
— neighbor ip-address end-of-rib
— protocol
Debug Commands
debug
7210 SAS M OS Routing Protocols Guide
Page 287
BGP Command Reference
— router
— bgp
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
Page 288
events [neighbor ip-address | group name]
no events
graceful-restart [neighbor ip-address | group name]
no graceful-restart
keepalive [neighbor ip-address | group name]
no keepalive
notification [neighbor ip-address | group name]
no notification
open [neighbor ip-address | group name]
no open
[no] outbound-route-filtering
packets [neighbor ip-address | group name]
no packets
route-refresh [neighbor ip-address | group name]
no route-refresh
rtm [neighbor ip-address | group name]
no rtm
socket [neighbor ip-address | group name]
no socket
timers [neighbor ip-address | group name]\
no timers
update [neighbor ip-address | group name]
no update
7210 SAS M OS Routing Protocols Guide
BGP
Configuration Commands
bgp
Syntax
Context
Description
[no] bgp
config>router
This command creates the BGP protocol instance and BGP configuration context. BGP is administratively
enabled upon creation.
The no form of the command deletes the BGP protocol instance and removes all configuration parameters
for the BGP instance. BGP must be shutdown before deleting the BGP instance. An error occurs if BGP is
not shutdown first.
advertise-inactive
Syntax
Context
Description
[no] advertise-inactive
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command enables the advertising of inactive BGP routes to other BGP peers. By default, BGP only
advertises BGP routes to other BGP peers if a given BGP route is chosen by the route table manager as the
most preferred route within the system and is active in the forwarding plane. This command allows system
administrators to advertise a BGP route even though it is not the most preferred route within the system for a
given destination.
The no form of the command disables the advertising of inactive BGP routers to other BGP peers.
Default
no advertise-inactive
aggregator-id-zero
Syntax
Context
Description
[no] aggregator-id-zero
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command is used to set the router ID in the BGP aggregator path attribute to zero when BGP aggregates
routes. This prevents different routers within an AS from creating aggregate routes that contain different AS
paths.
When BGP is aggregating routes, it adds the aggregator path attribute to the BGP update messages. By
default, BGP adds the AS number and router ID to the aggregator path attribute.
7210 SAS M OS Routing Protocols Guide
Page 289
Configuration Commands
When this command is enabled, BGP adds the router ID to the aggregator path attribute. This command is
used at the group level to revert to the value defined under the global level, while this command is used at the
neighbor level to revert to the value defined under the group level.
The no form of the command used at the global level reverts to default where BGP adds the AS number and
router ID to the aggregator path attribute.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
no aggregator-id-zero — BGP adds the AS number and router ID to the aggregator path attribute.
always-compare-med
Syntax
Context
Description
always-compare-med {zero | infinity}
no always-compare-med
config>router>bgp
This command specifies how the Multi-Exit Discriminator (MED) path attribute is used in the BGP route
selection process. The MED attribute is always used in the route selection process regardless of the peer AS
that advertised the route. This parameter determines what MED value is inserted in the RIB-IN.
If this parameter is not configured, only the MEDs of routes that have the same peer ASs are compared.
The no form of the command removes the parameter from the configuration.
Default
Parameters
no always-compare-med — Only compare MEDs of routes that have the same peer AS.
zero — Specifies that for routes learned without a MED attribute that a zero (0) value is used in the MED
comparison. The routes with the lowest metric are the most preferred.
infinity — Specifies for routes learned without a MED attribute that a value of infinity (2^32-1) is used in
the MED comparison. This in effect makes these routes the least desirable.
as-path-ignore
Syntax
Context
Description
as-path-ignore [ipv4] [vpn-ipv4] [l2-vpn]
no as-path-ignore
config>router>bgp
This command determines whether the AS path is used to determine the best BGP route.
If this option is present, the AS paths of incoming routes are not used in the route selection process.
The no form of the command removes the parameter from the configuration.
Default
Parameters
no as-path-ignore
ipv4 — Specifies that the AS-path length will be ignored for all IPv4 routes.
vpn-ipv4 — Specifies that the lengthAS-path will be ignored for all IPv4 VPRN routes.
l2-vpn — The AS-path length will be ignored for all L2-VPN NLRIs.
Page 290
7210 SAS M OS Routing Protocols Guide
BGP
auth-keychain
Syntax
Context
Description
Default
Parameters
auth-keychain name
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures a TCP authentication keychain to use for the session. The keychain allows the
rollover of authentication keys during the lifetime of a session.
no auth-keychain
name — Specifies the name of the keychain, up to 32 characters, to use for the specified TCP session or sessions.
authentication-key
Syntax
Context
Description
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the BGP authentication key.
Authentication is performed between neighboring routers before setting up the BGP session by verifying the
password. Authentication is performed using the MD-5 message based digest.
The authentication key can be any combination of ASCII characters up to 255 characters long.
The no form of the command reverts to the default value.
Default
Parameters
MD5 Authentication is disabled by default.
authentication-key — The authentication key. The key can be any combination of ASCII characters up to
255 characters in length (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (“ ”).
hash-key — The hash key. The key can be any combination of ASCII characters up to 342 characters in
length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (“ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
hash — Specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is
assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in
the configuration file with the hash parameter specified.
hash2 — Specifies the key is entered in a more complex encrypted form. If the hash2 parameter is not
used, the less encrypted hash form is assumed.
7210 SAS M OS Routing Protocols Guide
Page 291
Configuration Commands
bfd-enable
Syntax
Context
Description
[no] bfd-enable
config>router>bgp>group
config>router>bgp>group>neighbor
This command enables the use of bi-directional forwarding (BFD) to control the state of the associated
protocol interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied to
the state of the BFD session between the local node and the remote node. The parameters used for the BFD
are set via the BFD command under the IP interface.
The no form of this command removes BFD from the associated IGP/BGP protocol adjacency.
Default
no bfd-enable
connect-retry
Syntax
Context
Description
connect-retry seconds
no connect-retry
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the BGP connect retry timer value in seconds.
When this timer expires, BGP tries to reconnect to the configured peer. This configuration parameter can be
set at three levels: global level (applies to all peers), peer-group level (applies to all peers in group) or
neighbor level (only applies to specified peer). The most specific value is used.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
120 seconds
seconds — The BGP Connect Retry timer value in seconds expressed as a decimal integer.
Values
1 — 65535
damping
Syntax
Context
Description
Page 292
[no] damping
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command enables BGP route damping for learned routes which are defined within the route policy. Use
damping to reduce the number of update messages sent between BGP peers and reduce the load on peers
7210 SAS M OS Routing Protocols Guide
BGP
without affecting the route convergence time for stable routes. Damping parameters are set via route policy
definition.
The no form of the command used at the global level reverts route damping.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
When damping is enabled and the route policy does not specify a damping profile, the default damping
profile is used. This profile is always present and consists of the following parameters:
Half-life:
Max-suppress:
Suppress-threshold:
Reuse-threshold:
Default
15 minutes
60 minutes
3000
750
no damping — Learned route damping is disabled.
description
Syntax
Context
Description
description description-string
no description
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command creates a text description stored in the configuration file for a configuration context.
The no form of the command removes the description string from the context.
Default
Parameters
No description is associated with the configuration context.
string — The description character string. Allowed values are any string up to 80 characters long composed
of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the
entire string must be enclosed within double quotes.
disable-4byte-asn
Syntax
Context
Description
[no] disable-4byte-asn
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command disables the use of 4-byte ASNs. It can be configured at all 3 level of the hierarchy so it can
be specified down to the per peer basis.
If this command is enabled 4-btye ASN support should not be negotiated with the associated remote peer(s).
The no form of the command resets the behavior to the default which is to enable the use of 4-byte ASN.
7210 SAS M OS Routing Protocols Guide
Page 293
Configuration Commands
disable-communities
Syntax
Context
disable-communities [standard] [extended]
no disable-communities
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Description
This command configures BGP to disable sending communities.
Parameters
standard — Specifies standard communities that existed before VPRNs or 2547.
extended — Specifies BGP communities used were expanded after the concept of 2547 was introduced, to
include handling the VRF target.
disable-fast-external-failover
Syntax
[no] disable-fast-external-failover
Context
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Description
This command configures BGP fast external failover.
disallow-igp
Syntax
[no] disallow-igp
Context
config>router>bgp
Description
This command allows or disallows the use of the IGP next-hop to the BGP next-hop as the next-hop of the
last resort.
enable-peer-tracking
Syntax
Context
Description
Page 294
[no] enable-peer-tracking
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command enables BGP peer tracking. BGP peer tracking allows a BGP peer to be dropped immediately
if the route used to resolve the BGP peer address is removed from the IP routing table and there is no
alternative available. The BGP peer will not wait for the holdtimer to expire; therefore, the BGP
reconvergance process is accelerated.
7210 SAS M OS Routing Protocols Guide
BGP
The no form of the command disables peer tracking.
Default
no enable-peer-tracking
export
Syntax
export policy-name [policy-name…]
no export [policy-name]
Context
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Description
This command specifies the export route policy used to determine which routes are advertised to peers.
This configuration parameter can be set at three levels: global level (applies to all peers), group level
(applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific level
is used.
When multiple policy names are specified, the policies are evaluated in the order they are specified. A
maximum of five (5) policy names can be configured. The first policy that matches is applied.
When multiple export commands are issued, the last command entered overrides the previous command.
When no export policies are specified, BGP routes are advertised and non-BGP routes are not advertised by
default.
The no form of the command removes the policy association with the BGP instance. To remove association
of all policies, use the no export command without arguments.
Default
Parameters
no export — No export policy is specified. BGP routes are advertised and non-BGP routes are not
advertised.
policy-name — The route policy name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes. Route policies are configured in the config>router>policy-options context.
family
Syntax
family [ipv4] [vpn-ipv4] [l2-vpn] ]
no family
Context
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Description
This command specifies the address family or families to be supported over BGP peerings in the base router.
This command is additive so issuing the family command adds the specified address family to the list.
The no form of the command removes the specified address family from the associated BGP peerings. If an
address family is not specified, then reset the supported address family back to the default.
7210 SAS M OS Routing Protocols Guide
Page 295
Configuration Commands
Default
Parameters
ipv4
ipv4 — Provisions support for IPv4 routing information.
vpn-ipv4 — Exchanges IPv4 VPN routing information.
l2-vpn — Exchanges Layer 2 VPN information.
vpn-apply-export
Syntax
Context
Description
[no] vpn-apply-export
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command causes the base instance BGP export route policies to be applied to VPN-IPv4 routes.
The no form of the command disables the application of the base instance BGP route policies to VPN-IPv4
routes.
Default
no vpn-apply-export
vpn-apply-import
Syntax
Context
Description
[no] vpn-apply-import
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command causes the base instance BGP import route policies to be applied to VPN-IPv4 routes.
The no form of the command disables the application of the base instance BGP import route policies to
VPN-IPv4 routes.
Default
no vpn-apply-import
Values
Page 296
7210 SAS M OS Routing Protocols Guide
BGP
group
Syntax
[no] group name
Context
config>router>bgp
Description
This command creates a context to configure a BGP peer group.
The no form of the command deletes the specified peer group and all configurations associated with the peer
group. The group must be shutdown before it can be deleted.
Default
Parameters
No peer groups are defined.
name — The peer group name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string
must be enclosed within double quotes.
hold-time
Syntax
Context
Description
hold-time seconds [strict]
no hold-time
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the BGP hold time, expressed in seconds.
The BGP hold time specifies the maximum time BGP waits between successive messages (either keepalive
or update) from its peer, before closing the connection. This configuration parameter can be set at three
levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only
applies to specified peer). The most specific value is used.
Even though the 7210 SAS implementation allows setting the keepalive time separately, the configured
keepalive timer is overridden by the hold-time value under the following circumstances:
1. If the specified hold-time is less than the configured keepalive time, then the operational keepalive
time is set to a third of the hold-time; the configured keepalive time is not changed.
2. If the hold-time is set to zero, then the operational value of the keepalive time is set to zero; the configured keepalive time is not changed. This means that the connection with the peer is up permanently
and no keepalive packets are sent to the peer.
The no form of the command used at the global level reverts to the default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
90 seconds
seconds — The hold-time, in seconds, expressed as a decimal integer. A value of 0 indicates the connection
to the peer is up permanently.
Values
0, 3 — 65535
7210 SAS M OS Routing Protocols Guide
Page 297
Configuration Commands
strict — When this parameter is specified, the advertised BGP hold-time from the far-end BGP peer must
be greater than or equal to the specified value.
import
Syntax
import policy-name [policy-name…]
no import [policy-name]
Context
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Description
This command specifies the import route policy to be used to determine which routes are accepted from
peers. Route policies are configured in the config>router>policy-options context.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies
to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific level is used.
When multiple policy names are specified, the policies are evaluated in the order they are specified. A
maximum of five (5) policy names can be specified. The first policy that matches is applied.
When multiple import commands are issued, the last command entered will override the previous
command.
When an import policy is not specified, BGP routes are accepted by default.
The no form of the command removes the policy association with the BGP instance. To remove association
of all policies, use no import without arguments.
Default
Parameters
no import — No import policy specified (BGP routes are accepted).
policy-name — The route policy name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes. Route policies are configured in the config>router>policy-options context.
keepalive
Syntax
Context
Description
keepalive seconds
no keepalive
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the BGP keepalive timer. A keepalive message is sent every time this timer
expires.
The keepalive parameter can be set at three levels: global level (applies to all peers), group level (applies to
all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
Page 298
7210 SAS M OS Routing Protocols Guide
BGP
The keepalive value is generally one-third of the hold-time interval. Even though the 7210 SAS
implementation allows the keepalive value and the hold-time interval to be independently set, under the
following circumstances, the configured keepalive value is overridden by the hold-time value:
1. If the specified keepalive value is greater than the configured hold-time, then the specified value is
ignored, and the keepalive is set to one third of the current hold-time value.
2. If the specified hold-time interval is less than the configured keepalive value, then the keepalive
value is reset to one third of the specified hold-time interval.
3. If the hold-time interval is set to zero, then the configured value of the keepalive value is ignored.
This means that the connection with the peer is up permanently and no keepalive packets are sent to
the peer.
The no form of the command used at the global level reverts to the default value
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
30 seconds
seconds — The keepalive timer in seconds expressed as a decimal integer.
Values
0 — 21845
local-address
Syntax
Context
Description
local-address ip-address
no local-address
config>router>bgp>group
config>router>bgp>group>neighbor
Configures the local IP address used by the group or neighbor when communicating with BGP peers.
Outgoing connections use the local-address as the source of the TCP connection when initiating
connections with a peer.
When a local address is not specified, 7210 SAS uses the system IP address when communicating with
IBGP peers and uses the interface address for directly connected EBGP peers. This command is used at the
neighbor level to revert to the value defined under the group level.
The no form of the command removes the configured local-address for BGP.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
no local-address - The router ID is used when communicating with IBGP peers and the interface address is
used for directly connected EBGP peers.
ip-address — The local address expressed in dotted decimal notation. Allowed value is a valid routable IP
address on the router, either an interface or system IP address.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
7210 SAS M OS Routing Protocols Guide
Page 299
Configuration Commands
local-as
Syntax
Context
Description
local-as as-number [private]
no local-as
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures a BGP virtual autonomous system (AS) number.
In addition to the AS number configured for BGP in the config>router>autonomous-system context, a
virtual (local) AS number is configured.The virtual AS number is added to the as-path message before the
router’s AS number makes the virtual AS the second AS in the as-path.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies
to all peers in peer-group) or neighbor level (only applies to specified peer). Thus, by specifying this at each
neighbor level, it is possible to have a separate as-number per EBGP session.
When a command is entered multiple times for the same AS, the last command entered is used in the
configuration. The private attribute can be added or removed dynamically by reissuing the command.
Changing the local AS at the global level in an active BGP instance causes the BGP instance to restart with
the new local AS number. Changing the local AS at the global level in an active BGP instance causes BGP to
re-establish the peer relationships with all peers in the group with the new local AS number. Changing the
local AS at the neighbor level in an active BGP instance causes BGP to re-establish the peer relationship
with the new local AS number.
This is an optional command and can be used in the following circumstance:
Provider router P is moved from AS1 to AS2. The customer router that is connected to P, however, is
configured to belong to AS1. To avoid reconfiguring the customer router, the local-as value on router P can
be set to AS1. Thus, router P adds AS1 to the as-path message for routes it advertises to the customer router.
The no form of the command used at the global level will remove any virtual AS number configured.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
no local-as
as-number — The virtual autonomous system number expressed as a decimal integer.
Values
1 — 65535
private — Specifies the local-as is hidden in paths learned from the peering.
Page 300
7210 SAS M OS Routing Protocols Guide
BGP
local-preference
Syntax
local-preference local-preference
no local-preference
Context
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Description
This command enables setting the BGP local-preference attribute in incoming routes if not specified and
configures the default value for the attribute.
This value is used if the BGP route arrives from a BGP peer without the local-preference integer set.
The specified value can be overridden by any value set via a route policy. This configuration parameter can
be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or
neighbor level (only applies to specified peer). The most specific value is used.
The no form of the command at the global level specifies that incoming routes with local-preference set are
not overridden and routes arriving without local-preference set are interpreted as if the route had localpreference value of 100.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
no local-preference — Does not override the local-preference value set in arriving routes and analyze
routes without local preference with value of 100.
local-preference — The local preference value to be used as the override value expressed as a decimal integer.
Values
0 — 4294967295
loop-detect
Syntax
Context
Description
loop-detect {drop-peer | discard-route | ignore-loop | off}
no loop-detect
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures how the BGP peer session handles loop detection in the AS path.
This configuration parameter can be set at three levels: global level (applies to all peers), group level
(applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value
is used.
Note that dynamic configuration changes of loop-detect are not recognized.
The no form of the command used at the global level reverts to default, which is loop-detect ignore-loop.
The no form of the command used at the group level reverts to the value defined at the global level.
7210 SAS M OS Routing Protocols Guide
Page 301
Configuration Commands
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
loop-detect ignore-loop
drop-peer — Sends a notification to the remote peer and drops the session.
discard-route — Discards routes received from a peer with the same AS number as the router itself. This
option prevents routes looped back to the router from being added to the routing information base and
consuming memory. When this option is changed, the change will not be active for an established peer
until the connection is re-established for the peer.
ignore-loop — Ignores routes with loops in the AS path but maintains peering.
off — Disables loop detection.
med-out
Syntax
Context
Description
med-out {number | igp-cost}
no med-out
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command enables advertising the Multi-Exit Discriminator (MED) and assigns the value used for the
path attribute for the MED advertised to BGP peers if the MED is not already set.
The specified value can be overridden by any value set via a route policy.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies
to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of the command used at the global level reverts to default where the MED is not advertised.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
no med-out
number — The MED path attribute value expressed as a decimal integer.
Values
0 — 4294967295
igp-cost — The MED is set to the IGP cost of the given IP prefix.
Page 302
7210 SAS M OS Routing Protocols Guide
BGP
min-as-origination
Syntax
Context
Description
min-as-origination seconds
no min-as-origination
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the minimum interval, in seconds, at which a path attribute, originated by the
local router, can be advertised to a peer.
This configuration parameter can be set at three levels: global level (applies to all peers), group level
(applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value
is used.
The no form of the command used at the global level reverts to default.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
15 seconds
seconds — The minimum path attribute advertising interval in seconds expressed as a decimal integer.
Values
2 — 255
min-route-advertisement
Syntax
min-route-advertisement seconds
no min-route-advertisement
Context
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
Description
This command configures the minimum interval, in seconds, at which a prefix can be advertised to a peer.
This configuration parameter can be set at three levels: global level (applies to all peers), group level
(applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value
is used.
The no form of the command used at the global level reverts to default.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
30 seconds
seconds — The minimum route advertising interval, in seconds, expressed as a decimal integer.
Values
1— 255
7210 SAS M OS Routing Protocols Guide
Page 303
Configuration Commands
multihop
Syntax
Context
Description
multihop ttl-value
no multihop
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the time to live (TTL) value entered in the IP header of packets sent to an EBGP
peer multiple hops away.
The no form of the command is used to convey to the BGP instance that the EBGP peers are directly
connected.
The no form of the command used at the global level reverts to default.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
1 — EBGP peers are directly connected.
64 — IBGP
Parameters
ttl-value — The TTL value expressed as a decimal integer.
Values
1 — 255
outbound-route-filtering
Syntax
Context
Description
Default
[no] outbound-route-filtering
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command opens the configuration tree for sending or accepting BGP filter lists from peers (outbound
route filtering).
no outbound-route-filtering
extended-community
Syntax
Context
Description
Page 304
[no] extended-community
config>router>bgp>orf
config>router>bgp>group>orf
config>router>bgp>group>neighbor>orf
The extended-community command opens the configuration tree for sending or accepting extendedcommunity based BGP filters.
7210 SAS M OS Routing Protocols Guide
BGP
In order for the no version of the command to work, all sub-commands (send-orf, accept-orf) must be
removed first.
Default
Community filtering is not enabled by default.
accept-orf
Syntax
Context
Description
[no] accept-orf
config>router>bgp>orf>ext-comm
config>router>bgp>group>orf>ext-comm
config>router>bgp>group>neighbor>orf>ext-comm
This command instructs the router to negotiate the receive capability in the BGP ORF negotiation with a
peer, and to accept filters that the peer wishes to send.
The no form of the command causes the router to remove the accept capability in the BGP ORF negotiation
with a peer, and to clear any existing ORF filters that are currently in place.
Default
Accepting ORFs is not enabled by default.
send-orf
Syntax
Context
Description
send-orf [comm-id...(up to 32 max)]
no send-orf [comm-id]
config>router>bgp>orf>ext-comm
config>router>bgp>group>orf>ext-comm
config>router>bgp>group>neighbor>orf>ext-comm
This command instructs the router to negotiate the send capability in the BGP outbound route filtering
(ORF) negotiation with a peer.
This command also causes the router to send a community filter, prefix filter, or AS path filter configured as
an inbound filter on the BGP session to its peer as an ORF Action ADD.
The no form of this command causes the router to remove the send capability in the BGP ORF negotiation
with a peer.
The no form also causes the router to send an ORF remove action for a community filter, prefix filter, or AS
path filter configured as an inbound filter on the BGP session to its peer.
If the comm-id parameter(s) are not exclusively route target communities then the router will extract
appropriate route targets and use those. If, for some reason, the comm-id parameter(s) specified contain no
route targets, then the router will not send an ORF.
Default
Parameters
no send-orf — Sending ORF is not enabled by default.
comm-id — Any community policy which consists exclusively of route target extended communities. If it is
not specified, then the ORF policy is automatically generated from configured route target lists,
accepted client route target ORFs and locally configured route targets.
7210 SAS M OS Routing Protocols Guide
Page 305
Configuration Commands
neighbor
Syntax
[no] neighbor ip-address
Context
config>router>bgp>group
Description
This command creates a BGP peer/neighbor instance within the context of the BGP group.
This command can be issued repeatedly to create multiple peers and their associated configuration.
The no form of the command is used to remove the specified neighbor and the entire configuration
associated with the neighbor. The neighbor must be administratively shutdown before attempting to delete
it. If the neighbor is not shutdown, the command will not result in any action except a warning message on
the console indicating that neighbor is still administratively up.
Default
Parameters
No neighbors are defined.
ip-address — The IP address of the BGP peer router in dotted decimal notation.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
next-hop-self
Syntax
[no] next-hop-self{[ipv4] [l2-vpn]}
Context
config>router>bgp>group
config>router>bgp>group>neighbor
Description
This command configures the group or neighbor to always set the NEXTHOP path attribute to its own
physical interface when advertising to a peer.
This is primarily used to avoid third-party route advertisements when connected to a multi-access network.
In addition, this command can be used to enable and configure the multi-homing resiliency mechanism
replacing the usual BGP nexthop with a configured anycast address.
The no form of the command used at the group level allows third-party route advertisements in a multiaccess network.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
no next-hop-self — Third-party route advertisements are allowed.
ipv4 — Provisions support for IPv4 routing information.
l2-vpn — Exchanges Layer 2 VPN information.
Page 306
7210 SAS M OS Routing Protocols Guide
BGP
peer-as
Syntax
Context
Description
peer-as as-number
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the autonomous system number for the remote peer. The peer AS number must be
configured for each configured peer.
For EBGP peers, the peer AS number configured must be different from the autonomous system number
configured for this router under the global level since the peer will be in a different autonomous system than
this router
For IBGP peers, the peer AS number must be the same as the autonomous system number of this router
configured under the global level.
This is required command for each configured peer. This may be configured under the group level for all
neighbors in a particular group.
Default
Parameters
No AS numbers are defined.
as-number — The autonomous system number expressed as a decimal integer.
Values
1 — 4294967295
path-mtu-discovery
Syntax
Context
Description
[no] path-mtu-discovery
config>router>bgp
This command enables path MTU discovery for the associated TCP connections. In doing so, the MTU for
the associated TCP session will be initially set to the egress interface MTU. The DF bit will also be set so
that if a router along the path of the TCP connection cannot handle a packet of a particular size without
fragmenting, it will send back and ICMP message to set the path MTU for the given session to a lower value
that can be forwarded without fragmenting.
The no form of the command disables path MTU discovery.
Default
no path-mtu-discovery
preference
Syntax
Context
Description
[no] preference preference
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the route preference for routes learned from the configured peer(s).
7210 SAS M OS Routing Protocols Guide
Page 307
Configuration Commands
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies
to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The lower the preference the higher the chance of the route being the active route. The 7210 SAS assigns
BGP routes highest default preference compared to routes that are direct, static or learned via MPLS or
OSPF.
The no form of the command used at the global level reverts to default value.
The no form of the command used at the group level reverts to the value defined at the global level.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
170
preference — The route preference expressed as a decimal integer.
Values
1 — 255
purge-timer
Syntax
Context
[no] purge-timer minutes
config>router>bgp
Description
This command configures the maximum time before stale routes are purged.
Parameters
minutes — Specifies the duration of purge timer in minutes.
Values
1 — 60 minutes
rapid-update
Syntax
Context
Description
Default
Page 308
rapid-update { [l2-vpn] }
no rapid-update
config>router>bgp
This command enables and disables BGP rapid update for specified address-families. When no parameter is
given for the no rapid-update statement, rapid update is disabled for all address-families.
no rapid-update
7210 SAS M OS Routing Protocols Guide
BGP
rapid-withdrawal
Syntax
Context
Description
[no] rapid-withdrawal
config>router>bgp
This command disables the delay (Minimum Route Advertisement) on sending BGP withdrawals. Normal
route withdrawals may be delayed up to the minimum route advertisement to allow for efficient packing of
BGP updates.
The no form of the command removes this command from the configuration and returns withdrawal
processing to the normal behavior.
Default
no rapid-withdrawal
prefix-limit
Syntax
Context
Description
prefix-limit limit
no prefix-limit
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures the maximum number of routes BGP can learn from a peer.
When the number of routes reaches 90% of this limit, an SNMP trap is sent. When the limit is exceeded, the
BGP peering is dropped and disabled.
The no form of the command removes the prefix-limit.
Default
Parameters
no prefix-limit
limit — The number of routes that can be learned from a peer expressed as a decimal integer.
Values
1 — 4294967295
remove-private
Syntax
Context
Description
[no] remove-private {limited}
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command allows private AS numbers to be removed from the AS path before advertising them to BGP
peers.
When the remove-private parameter is set at the global level, it applies to all peers regardless of group or
neighbor configuration. When the parameter is set at the group level, it applies to all peers in the group
regardless of the neighbor configuration.
7210 SAS M OS Routing Protocols Guide
Page 309
Configuration Commands
7210 SAS software recognizes the set of AS numbers that are defined by IANA as private. These are AS
numbers in the range 64512 through 65535, inclusive.
The no form of the command used at the global level reverts to default value. The no form of the command
used at the group level reverts to the value defined at the global level. The no form of the command used at
the neighbor level reverts to the value defined at the group level.
Default
no remove-private — Private AS numbers will be included in the AS path attribute.
limited — This optional keyword removes private ASNs up to the first public ASN encountered. It then
stops removing private ASNs.
router-id (bgp)
Syntax
Context
Description
router-id ip-address
no router-id
config>router>bgp
This command specifies the router ID to be used with this BGP instance.
Changing the BGP router ID on an active BGP instance causes the BGP instance to restart with the new
router ID. The router ID must be set to a valid host address.
Default
Parameters
No router-id is configured for BGP by default. The system interface IP address is used.
ip-address — The router ID expressed in dotted decimal notation. Allowed value is a valid routable IP
address on the router, either an interface or system IP address. It is highly recommended that this
address be the system IP address.
shutdown
Syntax
Context
Description
[no] shutdown
config>router>bgp
config>router>bgp>group
config>router>bgp>group>neighbor
This command administratively disables an entity. When disabled, an entity does not change, reset, or
remove any configuration settings or statistics.
The operational state of the entity is disabled as well as the operational state of any entities contained within.
Many objects must be shut down before they may be deleted.
The no form of this command administratively enables an entity.
Unlike other commands and parameters where the default state is not indicated in the configuration file, the
shutdown and no shutdown states are always indicated in system generated configuration files.
Default administrative states for services and service entities are described in Special Cases.
The no form of the command places an entity in an administratively enabled state.
Page 310
7210 SAS M OS Routing Protocols Guide
BGP
Special Cases
BGP Global — The BGP protocol is created in the no shutdown state.
BGP Group — BGP groups are created in the no shutdown state.
BGP Neighbor — BGP neighbors/peers are created in the no shutdown state.
ttl-security
Syntax
Context
Description
ttl-security min-ttl-value
no ttl-security
config>router>bgp>group
config>router>bgp>group>neighbor
This command configures TTL security parameters for incoming packets. When the feature is enabled,
BGP/LDP will accept incoming IP packets from a peer only if the TTL value in the packet is greater than or
equal to the minimum TTL value configured for that peer.
The no form of the command disables TTL security.
Parameters
min-ttl-value — Specify the minimum TTL value for an incoming packet.
Values
1 — 255
Default
1
type
Syntax
Context
Description
[no] type {internal | external}
config>router>bgp>group
config>router>bgp>group>neighbor
This command designates the BGP peer as type internal or external.
The type of internal indicates the peer is an IBGP peer while the type of external indicates that the peer is an
EBGP peer.
By default, 7210 SAS derives the type of neighbor based on the local AS specified. If the local AS specified
is the same as the AS of the router, the peer is considered internal. If the local AS is different, then the peer
is considered external.
The no form of the command used at the group level reverts to the default value.
The no form of the command used at the neighbor level reverts to the value defined at the group level.
Default
Parameters
no type — Type of neighbor is derived on the local AS specified.
internal — Configures the peer as internal.
external — Configures the peer as external.
7210 SAS M OS Routing Protocols Guide
Page 311
Other BGP-Related Commands
Other BGP-Related Commands
autonomous-system
Syntax
Context
Description
autonomous-system autonomous-system
no autonomous-system
config>router
This command configures the autonomous system (AS) number for the router. A router can only belong to
one AS. An AS number is a globally unique number with an AS. This number is used to exchange exterior
routing information with neighboring ASs and as an identifier of the AS itself.
If the AS number is changed on a router with an active BGP instance, the new AS number is not used until
the BGP instance is restarted either by administratively disabling/enabling (shutdown/no shutdown) the
BGP instance or rebooting the system with the new configuration.
Default
Parameters
No autonomous system number is defined.
as-number — The autonomous system number expressed as a decimal integer.
Values
1 — 4294967295
router-id
Syntax
Context
Description
router-id ip-address
no router-id
config>router
This command configures the router ID for the router instance.
The router ID is used by both OSPF and BGP and BGP routing protocols in this instance of the routing table
manager.
When configuring a new router ID, protocols are not automatically restarted with the new router ID. The
next time a protocol is initialized, the new router ID is used. This can result in an interim period of time when
different protocols use different router IDs.
To force the new router ID to be used, issue the shutdown and no shutdown commands for each protocol
that uses the router ID, or restart the entire router.
The no form of the command to reverts to the default value.
Default
Parameters
Page 312
The system uses the system interface address (which is also the loopback address).
If a system interface address is not configured, use the last 32 bits of the chassis MAC address.
router-id — The 32 bit router ID expressed in dotted decimal notation or as a decimal value.
7210 SAS M OS Routing Protocols Guide
BGP
Show Commands
router
Syntax
Context
router [router-instance]
show
Description
Displays router instance information.
Parameters
router-instance — Specify either the router-name or service-id
Values
router-instance: Base, management
Default
Base, Management
bgp
Syntax
Context
Description
bgp
show>router
Enables the context to display BGP related information.
auth-keychain
Syntax
Context
auth-keychain [keychain]
show>router>bgp
Description
This command displays BGP sessions using particular authentication key-chain.
Parameters
keychain — Specifies an existing keychain name.
Sample Output
*A:ALA-48# show router 2 bgp auth-keychain
===============================================================================
Sessions using key chains
===============================================================================
Peer address
Group
Keychain name
------------------------------------------------------------------------------10.20.1.3
1
eta_keychain1
30.1.0.2
1
eta_keychain1
===============================================================================
*A:ALA-48#
*A:ALA-48>config>router>bgp# show router bgp group "To_AS_10000"
===============================================================================
7210 SAS M OS Routing Protocols Guide
Page 313
Show Commands
BGP Group : To_AS_10000
------------------------------------------------------------------------------Group
: To_AS_10000
------------------------------------------------------------------------------Group Type
: No Type
State
: Up
Peer AS
: 10000
Local AS
: 200
Local Address
: n/a
Loop Detect
: Ignore
Import Policy
: None Specified / Inherited
Hold Time
: 90
Keep Alive
: 30
Cluster Id
: 0.0.0.100
Client Reflect
: Enabled
NLRI
: Unicast
Preference
: 170
TTL Security
: Disabled
Min TTL Value
: n/a
Graceful Restart : Enabled
Stale Routes Time: 360
Auth key chain
: testname
List of Peers
- 10.0.0.8 :
To_Router B - EBGP Peer
Total Peers
: 1
Established
: 0
------------------------------------------------------------------------------Peer Groups : 1
===============================================================================
*A:ALA-48>config>router>bgp#
*A:ALA-48>config>router>bgp# show router bgp neighbor 10.0.0.8
===============================================================================
BGP Neighbor
------------------------------------------------------------------------------Peer : 10.0.0.8
Group : To_AS_10000
------------------------------------------------------------------------------Peer AS
: 10000
Peer Port
: 0
Peer Address
: 10.0.0.8
Local AS
: 200
Local Port
: 0
Local Address
: 0.0.0.0
Peer Type
: External
State
: Active
Last State
: Idle
Last Event
: stop
Last Error
: Cease
Local Family
: IPv4
Remote Family
: Unused
Hold Time
: 90
Keep Alive
: 30
Active Hold Time
: 0
Active Keep Alive
: 0
Cluster Id
: 0.0.0.100
Preference
: 99
Num of Flaps
: 0
Recd. Paths
: 0
IPv4 Recd. Prefixes : 0
IPv4 Active Prefixes : 0
IPv4 Suppressed Pfxs : 0
VPN-IPv4 Suppr. Pfxs : 0
VPN-IPv4 Recd. Pfxs : 0
VPN-IPv4 Active Pfxs : 0
Mc IPv4 Recd. Pfxs. : 0
Mc IPv4 Active Pfxs. : 0
Mc IPv4 Suppr. Pfxs : 0
Input Queue
: 0
Output Queue
: 0
i/p Messages
: 0
o/p Messages
: 0
i/p Octets
: 0
o/p Octets
: 0
i/p Updates
: 0
o/p Updates
: 0
TTL Security
: Disabled
Min TTL Value
: n/a
Graceful Restart
: Enabled
Stale Routes Time
: 360
Advertise Inactive
: Disabled
Peer Tracking
: Disabled
Page 314
7210 SAS M OS Routing Protocols Guide
BGP
Advertise Label
: None
Auth key chain
: testname
Local Capability
: RouteRefresh MP-BGP
Remote Capability
:
Import Policy
: None Specified / Inherited
------------------------------------------------------------------------------Neighbors : 1
===============================================================================
*A:ALA-48>config>router>bgp#
*A:ALA-48>config>router>bgp# show router bgp auth-keychain testname
=========================================================================
Sessions using key chain: keychain
=========================================================================
Peer address
Group
Keychain name
------------------------------------------------------------------------10.0.0.8
To_AS_10000
testname
=========================================================================
*A:ALA-48>config>router>bgp#
damping
Syntax
Context
Description
damping
damping
show>router>bgp
This command displays BGP routes which have been dampened due to route flapping. This command can be
entered with or without a route parameter.
When the keyword detail is included, more detailed information displays.
When only the command is entered (without any parameters included except detail), then all dampened
routes are listed.
When a parameter is specified, then the matching route or routes are listed.
When a decayed, history, or suppressed keyword is specified, only those types of dampened routes are
listed.
Parameters
ip-prefix — Displays damping information for the specified IP prefix and length.
Values
ipv4-prefix
ipv4-prefix-length
a.b.c.d (host bits must be 0)
0 — 32
damp-type — Specifies the type of damping to display.
Values
decayed — Displays damping entries that are decayed but are not suppressed.
history — Displays damping entries that are withdrawn but have history.
suppressed — Displays damping entries suppressed because of route damping.
detail — Displays detailed information.
7210 SAS M OS Routing Protocols Guide
Page 315
Show Commands
Output
Damping Output Fields — The following table describes BGP damping output fields.
Label
Page 316
Description
BGP Router ID
The local BGP router ID.
The local BGP router
ID.
The configured autonomous system number.
Local AS
The configured or inherited local AS for the specified peer group. If
not configured, then it is the same value as the AS.
Network
Route IP prefix and mask length for the route.
Flag(s)
Legend:
Status codes: u- used, s-suppressed, h-history, d-decayed,
*-valid. If a * is not present, then the status is invalid.
Origin codes: i-IGP, e-EGP, ?-incomplete, >-best
From
The originator ID path attribute value.
Reuse time
The time when a suppressed route can be used again.
From
The originator ID path attribute value.
Reuse time
The time when a suppressed route can be used again.
AS Path
The BGP AS path for the route.
Peer
The router ID of the advertising router.
NextHop
BGP nexthop for the route.
Peer AS
The autonomous system number of the advertising router.
Peer Router-Id
The router ID of the advertising router.
Local Pref
BGP local preference path attribute for the route.
Age
The length of time in hour/minute/second (HH:MM:SS) format.
Last update
The time when BGP was updated last in day/hour/minute
(DD:HH:MM) format.
FOM Present
The current Figure of Merit (FOM) value.
Number of Flaps
The number of route flaps in the neighbor connection.
Reuse time
The time when the route can be reused.
Path
The BGP AS path for the route.
Applied Policy
The applied route policy name.
7210 SAS M OS Routing Protocols Guide
BGP
Sample Output
A:ALA-12# show router bgp damping
===============================================================================
BGP Router ID : 10.0.0.14
AS : 65206
Local AS : 65206
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, - best
===============================================================================
BGP Damped Routes
===============================================================================
Flag Network
From
Reuse
AS-Path
------------------------------------------------------------------------------ud*i 12.149.7.0/24
10.0.28.1
00h00m00s
60203 65001 19855 3356
1239 22406
si
24.155.6.0/23
10.0.28.1
00h43m41s
60203 65001 19855 3356
2914 7459
si
24.155.8.0/22
10.0.28.1
00h38m31s
60203 65001 19855 3356
2914 7459
si
24.155.12.0/22
10.0.28.1
00h35m41s
60203 65001 19855 3356
2914 7459
si
24.155.22.0/23
10.0.28.1
00h35m41s
60203 65001 19855 3356
2914 7459
si
24.155.24.0/22
10.0.28.1
00h35m41s
60203 65001 19855 3356
2914 7459
si
24.155.28.0/22
10.0.28.1
00h34m31s
60203 65001 19855 3356
2914 7459
si
24.155.40.0/21
10.0.28.1
00h28m24s
60203 65001 19855 3356
7911 7459
si
24.155.48.0/20
10.0.28.1
00h28m24s
60203 65001 19855 3356
7911 7459
ud*i 61.8.140.0/24
10.0.28.1
00h00m00s
60203 65001 19855 3356
4637 17447
ud*i 61.8.141.0/24
10.0.28.1
00h00m00s
60203 65001 19855 3356
4637 17447
ud*i 61.9.0.0/18
10.0.28.1
00h00m00s
60203 65001 19855 3356
3561 9658 6163
. . .
ud*i 62.213.184.0/23
10.0.28.1
00h00m00s
60203 65001 19855 3356
6774 6774 9154
------------------------------------------------------------------------------A:ALA-12#
7210 SAS M OS Routing Protocols Guide
Page 317
Show Commands
A:ALA-12# show router bgp damping detail
===============================================================================
BGP Router ID : 10.0.0.14
AS : 65206
Local AS : 65206
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * valid
Origin codes : i - IGP, e - EGP, ? - incomplete, - best
===============================================================================
BGP Damped Routes
===============================================================================
------------------------------------------------------------------------------Network : 12.149.7.0/24
------------------------------------------------------------------------------Network
: 12.149.7.0/24
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h00m00s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
Age
: 00h22m09s
Last update
: 02d00h58m
FOM Present
: 738
FOM Last upd.
: 2039
Number of Flaps : 2
Flags
: ud*i
Path
: 60203 65001 19855 3356 1239 22406
Applied Policy
: default-damping-profile
------------------------------------------------------------------------------Network : 15.142.48.0/20
------------------------------------------------------------------------------Network
: 15.142.48.0/20
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h00m00s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
Age
: 00h00m38s
Last update
: 02d01h20m
FOM Present
: 2011
FOM Last upd.
: 2023
Number of Flaps : 2
Flags
: ud*i
Path
: 60203 65001 19855 3356 3561 5551 1889
Applied Policy
: default-damping-profile
------------------------------------------------------------------------------Network : 15.200.128.0/19
------------------------------------------------------------------------------Network
: 15.200.128.0/19
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h00m00s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
Age
: 00h00m38s
Last update
: 02d01h20m
FOM Present
: 2011
FOM Last upd.
: 2023
Number of Flaps : 2
Flags
: ud*i
Path
: 60203 65001 19855 1299 702
1889
Applied Policy
: default-damping-profile
------------------------------------------------------------------------------Network : 15.203.192.0/18
------------------------------------------------------------------------------Network
: 15.203.192.0/18
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h00m00s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
Age
: 00h00m07s
Last update
: 02d01h20m
FOM Present
: 1018
FOM Last upd.
: 1024
Number of Flaps : 1
Flags
: ud*i
Path
: 60203 65001 19855 1299 702
1889
Applied Policy
: default-damping-profile
Page 318
7210 SAS M OS Routing Protocols Guide
BGP
------------------------------------------------------------------------------A:ALA-12#
A:ALA-12# show router bgp damping 15.203.192.0/18 detail
===============================================================================
BGP Router ID : 10.0.0.14
AS : 65206
Local AS : 65206
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, - best
===============================================================================
BGP Damped Routes 15.203.192.0/18
===============================================================================
------------------------------------------------------------------------------Network : 15.203.192.0/18
------------------------------------------------------------------------------Network
: 15.203.192.0/18
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h00m00s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
Age
: 00h00m42s
Last update
: 02d01h20m
FOM Present
: 2003
FOM Last upd.
: 2025
Number of Flaps : 2
Flags
: ud*i
Path
: 60203 65001 19855 3356 702
1889
Applied Policy
: default-damping-profile
------------------------------------------------------------------------------Paths : 1
===============================================================================
A:ALA-12#
A:ALA-12# show router bgp damping suppressed detail
===============================================================================
BGP Router ID : 10.0.0.14
AS : 65206
Local AS : 65206
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, - best
===============================================================================
BGP Damped Routes (Suppressed)
===============================================================================
------------------------------------------------------------------------------Network : 15.142.48.0/20
------------------------------------------------------------------------------Network
: 15.142.48.0/20
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h29m22s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
Age
: 00h01m28s
Last update
: 02d01h20m
FOM Present
: 2936
FOM Last upd.
: 3001
Number of Flaps : 3
Flags
: si
Path
: 60203 65001 19855 3356 702
1889
Applied Policy
: default-damping-profile
------------------------------------------------------------------------------Network : 15.200.128.0/19
------------------------------------------------------------------------------Network
: 15.200.128.0/19
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h29m22s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
7210 SAS M OS Routing Protocols Guide
Page 319
Show Commands
Age
: 00h01m28s
Last update
: 02d01h20m
FOM Present
: 2936
FOM Last upd.
: 3001
Number of Flaps : 3
Flags
: si
Path
: 60203 65001 19855 3356 702
1889
Applied Policy
: default-damping-profile
------------------------------------------------------------------------------Network : 15.203.240.0/20
------------------------------------------------------------------------------Network
: 15.203.240.0/20
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h29m22s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
Age
: 00h01m28s
Last update
: 02d01h20m
FOM Present
: 2936
FOM Last upd.
: 3001
Number of Flaps : 3
Flags
: si
Path
: 60203 65001 19855 3356 702
1889
Applied Policy
: default-damping-profile
------------------------------------------------------------------------------Network : 15.206.0.0/17
------------------------------------------------------------------------------Network
: 15.206.0.0/17
Peer
: 10.0.28.1
NextHop
: 10.0.28.1
Reuse time
: 00h29m22s
Peer AS
: 60203
Peer Router-Id
: 32.32.27.203
Local Pref
: none
Age
: 00h01m28s
Last update
: 02d01h20m
FOM Present
: 2936
FOM Last upd.
: 3001
Number of Flaps : 3
Flags
: si
Path
: 60203 65001 19855 3356 702
1889
Applied Policy
: default-damping-profile
------------------------------------------------------------------------------A:ALA-12#
group
Syntax
Context
Description
group [name] [detail]
show>router>bgp
This command displays group information for a BGP peer group. This command can be entered with or
without parameters.
When this command is entered without a group name, information about all peer groups displays.
When the command is issued with a specific group name, information only pertaining to that specific peer
group displays.
The ‘State’ field displays the BGP group’s operational state. Valid states are:
Up — BGP global process is configured and running.
Down — BGP global process is administratively shutdown and not running.
Disabled — BGP global process is operationally disabled. The process must be restarted by the operator.
Parameters
name — Displays information for the BGP group specified.
detail — Displays detailed information.
Page 320
7210 SAS M OS Routing Protocols Guide
BGP
Output
Standard and Detailed Group Output — The following table describes the standard and detailed
command output fields for a BGP group.
Label
Description
Group
Displays the BGP group name.
Group Type
No Type — Peer type not configured.
External — Peer type configured as external BGP peers.
Internal — Peer type configured as internal BGP peers.
State
Disabled — The BGP peer group has been operationally disabled.
Down — The BGP peer group is operationally inactive.
Up — The BGP peer group is operationally active.
Peer AS
The configured or inherited peer AS for the specified peer group.
Local AS
The configured or inherited local AS for the specified peer group.
Local Address
The configured or inherited local address for originating peering for
the specified peer group.
Loop Detect
The configured or inherited loop detect setting for the specified peer
group.
Connect Retry
The configured or inherited connect retry timer value.
Authentication
None — No authentication is configured.
MD5 — MD5 authentication is configured.
Bfd
Yes — BFD is enabled.
No — BFD is disabled.
Local Pref
The configured or inherited local preference value.
MED Out
The configured or inherited MED value assigned to advertised routes
without a MED attribute.
Min Route Advt.
The minimum amount of time that must pass between route updates for
the same IP prefix.
Min AS Originate
The minimum amount of time that must pass between updates for a
route originated by the local router.
Multihop
The maximum number of router hops a BGP connection can traverse.
Prefix Limit
No Limit — No route limit assigned to the BGP peer group.
1 — 4294967295 — The maximum number of routes BGP can learn
from a peer.
7210 SAS M OS Routing Protocols Guide
Page 321
Show Commands
Label
Passive
Description (Continued)
Disabled — BGP attempts to establish a BGP connection with
neighbor in the specified peer group.
Enabled — BGP will not actively attempt to establish a BGP connection with neighbor in the specified peer group.
Next Hop Self
Disabled — BGP is not configured to send only its own IP address
as the BGP nexthop in route updates to neighbors in the peer group.
Enabled — BGP sends only its own IP address as the BGP nexthop
in route updates to neighbors in the specified peer group.
Aggregator ID 0
Disabled — BGP is not configured to set the aggregator ID to
0.0.0.0 in all originated route aggregates sent to the neighbor in the
peer group.
Enabled — BGP is configured to set the aggregator ID to 0.0.0.0 in
all originated route aggregates sent to the neighbor in the peer group.
Remove Private
Disabled — BGP will not remove all private AS numbers from the
AS path attribute in updates sent to the neighbor in the peer group.
Enabled — BGP removes all private AS numbers from the AS path
attribute in updates sent to the neighbor in the peer group.
Damping
Disabled — The peer group is configured not to dampen route
flaps.
Enabled — The peer group is configured to dampen route flaps.
Export Policy
The configured export policies for the peer group.
Import Policy
The configured import policies for the peer group.
Hold Time
The configured hold time setting.
Keep Alive
The configured keepalive setting.
Cluster Id
The configured route reflector cluster ID.
None — No cluster ID has been configured
Client Reflect
Disabled — The BGP route reflector will not reflect routes to this
neighbor.
Enabled — The BGP route reflector is configured to reflect routes
to this neighbor.
NLRI
The type of NLRI information that the specified peer group can accept.
Unicast — IPv4 unicast routing information can be carried.
Preference
Page 322
The configured route preference value for the peer group.
7210 SAS M OS Routing Protocols Guide
BGP
Label
Description (Continued)
List of Peers
A list of BGP peers configured under the peer group.
Total Peers
The total number of peers configured under the peer group.
Established
The total number of peers that are in an established state.
Sample Output
A:ALA-12# show router bgp group
===============================================================================
BGP Groups
------------------------------------------------------------------------------Group
: To_AS_40000
------------------------------------------------------------------------------Description
: Not Available
Group Type
: No Type
State
: Up
Peer AS
: 40000
Local AS
: 65206
Local Address
: n/a
Loop Detect
: Ignore
Export Policy
: direct2bgp
Hold Time
: 90
Keep Alive
: 30
Cluster Id
: None
Client Reflect
: Enabled
NLRI
: Unicast
Preference
: 170
List of Peers
- 10.0.0.1
- 10.0.0.12
- 10.0.0.13
- 10.0.0.14
- 10.0.0.15
:
:
:
:
:
To_Jukebox
Not Available
Not Available
To_SR1
To_H-215
Total Peers
: 5
Established
: 2
===============================================================================
A:ALA-12#
Sample Detailed Output
A:ALA-12# show router bgp group detail
===============================================================================
BGP Groups (detail)
------------------------------------------------------------------------------Group
: To_AS_40000
------------------------------------------------------------------------------Description
: Not Available
Group Type
: No Type
State
: Up
Peer AS
: 40000
Local AS
: 65206
Local Address
: n/a
Loop Detect
: Ignore
Connect Retry
: 20
Authentication
: None
Local Pref
: 100
MED Out
: 0
Multihop
: 0 (Default)
Min Route Advt. : 30
Min AS Originate : 15
Prefix Limit
: No Limit
Passive
: Disabled
Next Hop Self
: Disabled
Aggregator ID 0 : Disabled
Remove Private
: Disabled
Damping
: Disabled
Export Policy
: direct2bgp
7210 SAS M OS Routing Protocols Guide
Page 323
Show Commands
Hold Time
Cluster Id
NLRI
: 90
: None
: Unicast
List of Peers
- 10.0.0.1
- 10.0.0.12
- 10.0.0.13
- 10.0.0.14
- 10.0.0.15
:
:
:
:
:
Keep Alive
Client Reflect
Preference
: 30
: Enabled
: 170
To_Jukebox
Not Available
Not Available
To_SR1
To_H-215
Total Peers
: 5
Established
: 2
===============================================================================
A:ALA-12#
A:SetupCLI>show>router>bgp# group
===============================================================================
BGP Group
------------------------------------------------------------------------------Group
: bgp_group_1 34567890123456789012
------------------------------------------------------------------------------Description
: Testing the length of the group value for the DESCRIPTION
parameter of BGP
Group Type
: No Type
State
: Up
Peer AS
: n/a
Local AS
: 100
Local Address
: n/a
Loop Detect
: Ignore
Import Policy
: test i1
: test i2
: test i3
: test i4
: test i5 890123456789012345678901
Export Policy
: test e1
: test e2
: test e3
: test e4
: test e5 890123456789012345678901
Hold Time
: 120
Keep Alive
: 30
Cluster Id
: None
Client Reflect
: Disabled
NLRI
: Unicast
Preference
: 101
TTL Security
: Disabled
Min TTL Value
: n/a
Graceful Restart : Disabled
Stale Routes Time: n/a
Auth key chain
: n/a
Bfd Enabled
: Yes
List of Peers
- 3.3.3.3 :
Testing the length of the neighbor value for the DESCRIPTION parameter of
BGP
Total Peers
: 1
Established
: 0
------------------------------------------------------------------------------Peer Groups : 1
===============================================================================
A:SetupCLI>show>router>bgp#
Page 324
7210 SAS M OS Routing Protocols Guide
BGP
neighbor
Syntax
Context
Description
neighbor [ip-address [detail]]
neighbor [as-address [detail]]
neighbor [as-number [ detail ] filter2]
neighbor ip-address [family [type mvpn-type]] filter1 [brief]
neighbor ip-number [ family ] filter2
neighbor as-number [ family ] filter2
neighbor ip-address orf [filter3]
neighbor ip-address graceful-restart
show>router>bgp
This command displays BGP neighbor information. This command can be entered with or without any
parameters.
When this command is issued without any parameters, information about all BGP peers displays.
When the command is issued with a specific IP address or ASN, information regarding only that specific
peer or peers with the same AS displays.
When either received-routes or advertised-routes is specified, then the routes received from or sent to the
specified peer is listed (see second output example).
Note: This information is not available by SNMP.
When either history or suppressed is specified, then the routes learned from those peers that either have a
history or are suppressed (respectively) are listed.
The ‘State’ field displays the BGP peer’s protocol state. In additional to the standard protocol states, this
field can also display the ‘Disabled’ operational state which indicates the peer is operationally disabled and
must be restarted by the opeartor.
Parameters
ip-address — Display information for the specified IP address.
ipv4-address:
a.b.c.d (host bits must be 0)
as-number — Display information for the specified AS number.
Values
1 — 65535
family — Specify the type of routing information to be distributed by this peer group.
ipv4 — Displays only those BGP peers that have the IPv4 family enable and not those capable of
exchanging IP-VPN routes.
filter1 — Display information for the specified IP address.
Values
received-routes — Displays the number of routes received from this peer.
advertised-routes — Displays the number of routes advertised by this peer.
history — Displays statistics for dampened routes.
suppressed — Displays the number of paths from this peer that have been suppressed by
damping.
detail — Displays detailed information pertaining to filter1.
filter2 — Display information for the specified AS number.
Values
history — Display statistics for dampened routes.
suppressed — Display the number of paths from this peer that have been suppressed by
7210 SAS M OS Routing Protocols Guide
Page 325
Show Commands
damping.
detail — Displays detailed information pertaining to filter2
brief — Displays information in a brief format. This parameter is only supported with received-routes and
advertised-routes.
orf — Displays outbound route filtering for the BGP instance. ORF (Outbound Route Filtering) is used to
inform a neighbor of targets (using target-list) that it is willing to receive. This mechanism helps lessen
the update exchanges between neighbors and saves CPU cycles to process routes that could have been
received from the neighbor only to be dropped/ignored.
filter3 — Displays path information for the specified IP address.
Values
send — Displays the number of paths sent to this peer.
receive — Displays the number of paths received from this peer.
graceful-restart — Displays neighbors configured for graceful restart.
Output
Standard and Detailed Neighbor — The following table describes the standard and detailed command
output fields for a BGP neighbor.
Label
Description
Peer
The IP address of the configured BGP peer.
Group
The BGP peer group to which this peer is assigned.
Peer AS
The configured or inherited peer AS for the peer group.
Peer Address
The configured address for the BGP peer.
Peer Port
The TCP port number used on the far-end system.
Local AS
The configured or inherited local AS for the peer group.
Local Address
The configured or inherited local address for originating peering for
the peer group.
Local Port
The TCP port number used on the local system.
Peer Type
External — Peer type configured as external BGP peers.
Internal — Peer type configured as internal BGP peers.
Bfd
Yes — BFD is enabled.
No — BFD is disabled.
State
Idle — The BGP peer is not accepting connections.
Active — BGP is listening for and accepting TCP connections from
this peer.
Connect — BGP is attempting to establish a TCP connections from
this peer.
Page 326
7210 SAS M OS Routing Protocols Guide
BGP
Label
Description (Continued)
Open Sent — BGP has sent an OPEN message to the peer and is
waiting for an OPEN message from the peer.
Open Confirm — BGP has received a valid OPEN message from
the peer and is awaiting a KEEPALIVE or NOTIFICATION.
Established — BGP has successfully established a peering and is
exchanging routing information.
Last State
Idle — The BGP peer is not accepting connections.
Active — BGP is listening for and accepting TCP connections from
this peer.
Connect — BGP is attempting to establish a TCP connections from
this peer.
Open Sent — BGP has sent an OPEN message to the peer and is
waiting for an OPEN message from the peer.
Open Confirm — BGP has received a valid OPEN message from
the peer and is awaiting a KEEPALIVE or NOTIFICATION.
Last Event
start — BGP has initialized the BGP neighbor.
stop — BGP has disabled the BGP neighbor.
open — BGP transport connection opened.
close — BGP transport connection closed.
openFail — BGP transport connection failed to open.
error — BGP transport connection error.
connectRetry — Connect retry timer expired.
holdTime — Hold time timer expired.
keepAlive — Keepalive timer expired.
recvOpen — Receive an OPEN message.
revKeepalive — Receive a KEEPALIVE message.
recvUpdate — Receive an UPDATE message.
recvNotify — Receive a NOTIFICATION message.
None — No events have occurred.
Last Error
Displays the last BGP error and subcode to occur on the BGP neighbor.
7210 SAS M OS Routing Protocols Guide
Page 327
Show Commands
Label
Description (Continued)
Connect Retry
The configured or inherited connect retry timer value.
Local Pref.
The configured or inherited local preference value.
Min Route Advt.
The minimum amount of time that must pass between route updates for
the same IP prefix.
Min AS Originate
The minimum amount of time that must pass between updates for a
route originated by the local router.
Multihop
The maximum number of router hops a BGP connection can traverse.
Damping
Disabled — BGP neighbor is configured not to dampen route
flaps.
Enabled — BGP neighbor is configured to dampen route flaps.
Loop Detect
Ignore — The BGP neighbor is configured to ignore routes with an
AS loop.
Drop — The BGP neighbor is configured to drop the BGP peering if
an AS loop is detected.
Off — AS loop detection is disabled for the neighbor.
MED Out
The configured or inherited MED value assigned to advertised routes
without a MED attribute.
Authentication
None — No authentication is configured.
MD5 — MD5 authentication is configured.
Next Hop Self
Disabled — BGP is not configured to send only its own IP address
as the BGP nexthop in route updates to the specified neighbor.
Enabled — BGP will send only its own IP address as the BGP
nexthop in route updates to the neighbor.
AggregatorID Zero
Disabled — The BGP Neighbor is not configured to set the aggregator ID to 0.0.0.0 in all originated route aggregates.
Enabled — The BGP Neighbor is configured to set the aggregator
ID to 0.0.0.0 in all originated route aggregates.
Remove Private
Disabled — BGP will not remove all private AS numbers from the
AS path attribute, in updates sent to the specified neighbor.
Enabled — BGP will remove all private AS numbers from the AS
path attribute, in updates sent to the specified neighbor.
Passive
Page 328
Disabled — BGP will actively attempt to establish a BGP connection with the specified neighbor.
7210 SAS M OS Routing Protocols Guide
BGP
Label
Description (Continued)
Enabled — BGP will not actively attempt to establish a BGP connection with the specified neighbor.
Prefix Limit
No Limit — No route limit assigned to the BGP peer group.
1 — 4294967295 — The maximum number of routes BGP can learn
from a peer.
Hold Time
The configured hold time setting.
Keep Alive
The configured keepalive setting.
Active Hold Time
The negotiated hold time, if the BGP neighbor is in an established
state.
Active Keep Alive
The negotiated keepalive time, if the BGP neighbor is in an established
state.
Cluster Id
The configured route reflector cluster ID.
None — No cluster ID has been configured.
Client Reflect
Disabled — The BGP route reflector is configured not to reflect
routes to this neighbor.
Enabled — The BGP route reflector is configured to reflect routes
to this neighbor.
Preference
The configured route preference value for the peer group.
Num of Flaps
The number of route flaps in the neighbor connection..
Recd. Prefixes
The number of routes received from the BGP neighbor.
Active Prefixes
The number of routes received from the BGP neighbor and active in
the forwarding table.
Recd. Paths
The number of unique sets of path attributes received from the BGP
neighbor.
Suppressed Paths
The number of unique sets of path attributes received from the BGP
neighbor and suppressed due to route damping.
Input Queue
The number of BGP messages to be processed.
Output Queue
The number of BGP messages to be transmitted.
i/p Messages
Total number of packets received from the BGP neighbor.
o/p Messages
Total number of packets sent to the BGP neighbor.
i/p Octets
Total number of octets received from the BGP neighbor.
o/p Octets
Total number of octets sent to the BGP neighbor.
7210 SAS M OS Routing Protocols Guide
Page 329
Show Commands
Label
Description (Continued)
Export Policy
The configured export policies for the peer group.
Import Policy
The configured import policies for the peer group.
Sample Output
*A:7210-SAS>show>router>bgp# neighbor
===============================================================================
BGP Neighbor
===============================================================================
------------------------------------------------------------------------------Peer : 1.1.1.1
Group : sample
------------------------------------------------------------------------------Peer AS
: 12345
Peer Port
: 0
Peer Address
: 1.1.1.1
Local AS
: 143
Local Port
: 0
Local Address
: 0.0.0.0
Peer Type
: External
State
: Active
Last State
: Connect
Last Event
: openFail
Last Error
: Cease
Local Family
: IPv4 VPN-IPv4
Remote Family
: Unused
Hold Time
: 10000 (strict)
Keep Alive
: 21845
Active Hold Time
: 0
Active Keep Alive
: 0
Cluster Id
: None
Preference
: 10
Num of Flaps
: 0
Recd. Paths
: 0
IPv4 Recd. Prefixes : 0
IPv4 Active Prefixes : 0
IPv4 Suppressed Pfxs : 0
VPN-IPv4 Suppr. Pfxs : 0
VPN-IPv4 Recd. Pfxs : 0
VPN-IPv4 Active Pfxs : 0
Mc IPv4 Recd. Pfxs. : 0
Mc IPv4 Active Pfxs. : 0
Mc IPv4 Suppr. Pfxs : 0
IPv6 Suppressed Pfxs : 0
IPv6 Recd. Prefixes : 0
IPv6 Active Prefixes : 0
VPN-IPv6 Recd. Pfxs : 0
VPN-IPv6 Active Pfxs : 0
VPN-IPv6 Suppr. Pfxs : 0
MVPN-IPv4 Suppr. Pfxs: 0
MVPN-IPv4 Recd. Pfxs : 0
MVPN-IPv4 Active Pfxs: 0
Input Queue
: 0
Output Queue
: 0
i/p Messages
: 0
o/p Messages
: 1
i/p Octets
: 0
o/p Octets
: 0
i/p Updates
: 0
o/p Updates
: 0
TTL Security
: Disabled
Min TTL Value
: n/a
Graceful Restart
: Enabled
Stale Routes Time
: 3600
Advertise Inactive
: Enabled
Peer Tracking
: Enabled
Advertise Label
: None
Auth key chain
: keychain-one
Bfd Enabled
: Disabled
L2 VPN Cisco Interop : Disabled
Local Capability
: RtRefresh MPBGP ORFSendExComm ORFRecvExComm
Remote Capability
:
Import Policy
: abcd
Page 330
7210 SAS M OS Routing Protocols Guide
BGP
Export Policy
: abcd
------------------------------------------------------------------------------Peer : 1.1.3.4
Group : test
------------------------------------------------------------------------------Peer AS
: 0
Peer Port
: 0
Peer Address
: 1.1.3.4
Local AS
: 12345
Local Port
: 0
Local Address
: 0.0.0.0
Peer Type
: External
State
: Idle
Last State
: Idle
Last Event
: none
Last Error
: Unrecognized Error
Local Family
: VPN-IPv4
Remote Family
: Unused
Hold Time
: 0 (strict)
Keep Alive
: 0
Active Hold Time
: 0
Active Keep Alive
: 0
Cluster Id
: None
Preference
: 10
Num of Flaps
: 0
Recd. Paths
: 0
IPv4 Recd. Prefixes : 0
IPv4 Active Prefixes : 0
IPv4 Suppressed Pfxs : 0
VPN-IPv4 Suppr. Pfxs : 0
VPN-IPv4 Recd. Pfxs : 0
VPN-IPv4 Active Pfxs : 0
Mc IPv4 Recd. Pfxs. : 0
Mc IPv4 Active Pfxs. : 0
Mc IPv4 Suppr. Pfxs : 0
IPv6 Suppressed Pfxs : 0
IPv6 Recd. Prefixes : 0
IPv6 Active Prefixes : 0
VPN-IPv6 Recd. Pfxs : 0
VPN-IPv6 Active Pfxs : 0
VPN-IPv6 Suppr. Pfxs : 0
MVPN-IPv4 Suppr. Pfxs: 0
MVPN-IPv4 Recd. Pfxs : 0
MVPN-IPv4 Active Pfxs: 0
Input Queue
: 0
Output Queue
: 0
i/p Messages
: 0
o/p Messages
: 0
i/p Octets
: 0
o/p Octets
: 0
i/p Updates
: 0
o/p Updates
: 0
TTL Security
: Disabled
Min TTL Value
: n/a
Graceful Restart
: Enabled
Stale Routes Time
: 100
Advertise Inactive
: Enabled
Peer Tracking
: Enabled
Advertise Label
: None
Auth key chain
: n/a
Bfd Enabled
: Enabled
L2 VPN Cisco Interop : Disabled
Local Capability
: RtRefresh MPBGP
Remote Capability
:
Import Policy
: abcd
Export Policy
: abcd
------------------------------------------------------------------------------*A:7210-SAS>
A:ALA-48# show router 2 bgp neighbor 10.20.1.3
===============================================================================
BGP Neighbor
===============================================================================
Peer : 10.20.1.3
Group : 1
------------------------------------------------------------------------------Peer AS
: 100
Peer Port
: 49725
Peer Address
: 10.20.1.3
Local AS
: 100
Local Port
: 179
Local Address
: 10.20.1.2
7210 SAS M OS Routing Protocols Guide
Page 331
Show Commands
Peer Type
: Internal
State
: Established
Last State
: Established
Last Event
: recvKeepAlive
Last Error
: Cease
Local Family
: IPv4
Remote Family
: IPv4
Hold Time
: 3
Keep Alive
: 1
Active Hold Time
: 3
Active Keep Alive
: 1
Cluster Id
: None
Preference
: 170
Num of Flaps
: 0
Recd. Paths
: 1
IPv4 Recd. Prefixes : 11
IPv4 Active Prefixes : 10
IPv4 Suppressed Pfxs : 0
VPN-IPv4 Suppr. Pfxs : 0
VPN-IPv4 Recd. Pfxs : 0
VPN-IPv4 Active Pfxs : 0
Mc IPv4 Recd. Pfxs. : 0
Mc IPv4 Active Pfxs. : 0
Mc IPv4 Suppr. Pfxs : 0
Input Queue
: 0
Output Queue
: 0
i/p Messages
: 471
o/p Messages
: 473
i/p Octets
: 3241
o/p Octets
: 3241
i/p Updates
: 4
o/p Updates
: 4
TTL Security
: Disabled
Min TTL Value
: n/a
Advertise Inactive
: Disabled
Peer Tracking
: Disabled
Advertise Label
: None
Auth key chain
: eta_keychain1
Local Capability
: RouteRefresh MP-BGP
Remote Capability
: RouteRefresh MP-BGP
Import Policy
: None Specified / Inherited
Export Policy
: static2bgp
------------------------------------------------------------------------------Neighbors : 1
===============================================================================
A:ALA-48#
A:ALA-12# show router bgp neighbor 10.0.0.11 orf
===============================================================================
BGP Neighbor 10.0.0.11 ORF
===============================================================================
Send List (Automatic)
------------------------------------------------------------------------------target:65535:10
target:65535:20
===============================================================================
A:ALA-12
A:ALA-22 show router bgp neighbor 10.0.0.1 orf
===============================================================================
BGP Neighbor 10.0.0.1 ORF
===============================================================================
Receive List
------------------------------------------------------------------------------target:65535:10
target:65535:20
===============================================================================
A:ALA-22
Page 332
7210 SAS M OS Routing Protocols Guide
BGP
Sample Detailed Output
A:ALA-12# show router bgp neighbor detail
===============================================================================
BGP Neighbor (detail)
------------------------------------------------------------------------------Peer : 10.0.0.15
Group : To_AS_40000
------------------------------------------------------------------------------Peer AS
: 65205
Peer Port
: 0
Peer Address
: 10.0.0.15
Local AS
: 65206
Local Port
: 0
Local Address
: 10.0.0.16
Peer Type
: External
State
: Active
Last State
: Connect
Last Event
: openFail
Last Error
: Hold Timer Expire
Connect Retry
: 20
Local Pref.
: 100
Min Route Advt. : 30
Min AS Orig.
: 15
Damping
: Disabled
Loop Detect
: Ignore
MED Out
: No MED Out
Authentication
: None
Next Hop Self
: Disabled
AggregatorID Zero: Disabled
Remove Private
: Disabled
Passive
: Disabled
Prefix Limit
: No Limit
Hold Time
: 90
Keep Alive
: 30
Active Hold Time : 0
Active Keep Alive: 0
Cluster Id
: None
Client Reflect
: Enabled
Preference
: 170
Num of Flaps
: 0
Recd. Prefixes
: 0
Active Prefixes : 0
Recd. Paths
: 0
Suppressed Paths : 0
Input Queue
: 0
Output Queue
: 0
i/p Messages
: 0
o/p Messages
: 0
i/p Octets
: 0
o/p Octets
: 0
i/p Updates
: 0
o/p Updates
: 0
Export Policy
: direct2bgp
===============================================================================
A:ALA-12#
*A:SetupCLI>show>router>bgp# neighbor
===============================================================================
BGP Neighbor
===============================================================================
Peer : 3.3.3.3
Group : bgp_group_1 34567890123456789012
------------------------------------------------------------------------------Peer AS
: 20
Peer Port
: 0
Peer Address
: 3.3.3.3
Local AS
: 100
Local Port
: 0
Local Address
: 0.0.0.0
Peer Type
: Internal
State
: Active
Last State
: Idle
Last Event
: stop
Last Error
: Cease
Local Family
: IPv4
Remote Family
: Unused
Hold Time
: 10
Keep Alive
: 30
Active Hold Time
: 0
Active Keep Alive
: 0
Cluster Id
: 2.2.3.4
Preference
: 101
Num of Flaps
: 0
7210 SAS M OS Routing Protocols Guide
Page 333
Show Commands
Recd. Paths
IPv4 Recd. Prefixes
IPv4 Suppressed Pfxs
VPN-IPv4 Recd. Pfxs
Mc IPv4 Recd. Pfxs.
Mc IPv4 Suppr. Pfxs
Input Queue
i/p Messages
i/p Octets
i/p Updates
TTL Security
Graceful Restart
Advertise Inactive
Advertise Label
Auth key chain
Local Capability
Remote Capability
Import Policy
: 0
: 0
IPv4 Active Prefixes : 0
: 0
VPN-IPv4 Suppr. Pfxs : 0
: 0
VPN-IPv4 Active Pfxs : 0
: 0
Mc IPv4 Active Pfxs. : 0
: 0
: 0
Output Queue
: 0
: 0
o/p Messages
: 0
: 0
o/p Octets
: 0
: 0
o/p Updates
: 0
: Disabled
Min TTL Value
: n/a
: Enabled
Stale Routes Time
: 360
: Disabled
Peer Tracking
: Enabled
: None
Bfd Enabled
: Yes
: n/a
: RouteRefresh MP-BGP
:
: test i1
: test i2
: test i3
: test i4
: test i5 890123456789012345678901
Export Policy
: test e1
: test e2
: test e3
: test e4
: test e5 890123456789012345678901
------------------------------------------------------------------------------Neighbors : 1
===============================================================================
Advertised and Received Routes Ouptut — The following table describes the command output for
both the standard and detailed information for a neighor.
Label
Description
BGP Router ID
The local BGP router ID.
AS
The configured autonomous system number.
Local AS
The configured local AS setting. If not configured, then it is the same
value as the AS.
Flag
u — used
s — suppressed
h — history
d — decayed
* — valid
i — igp
e — egp
Page 334
7210 SAS M OS Routing Protocols Guide
BGP
Label
Description (Continued)
? — incomplete
> — best
Network
Route IP prefix and mask length for the route.
Next Hop
BGP nexthop for the route.
LocalPref
BGP local preference path attribute for the route.
MED
BGP Multi-Exit Discriminator (MED) path attribute for the route.
AS Path
The BGP AS path for the route.
Sample Output
A:ALA-12# show router bgp neighbor 10.0.0.16 received-routes
===============================================================================
BGP Router ID : 10.0.0.16
AS : 65206
Local AS : 65206
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
BGP IPv4 Routes
===============================================================================
Flag Network
Nexthop
LocalPref MED
As-Path
------------------------------------------------------------------------------?
10.0.0.16/32
10.0.0.16
100
none
No As-Path
?
10.0.6.0/24
10.0.0.16
100
none
No As-Path
?
10.0.8.0/24
10.0.0.16
100
none
No As-Path
?
10.0.12.0/24
10.0.0.16
100
none
No As-Path
?
10.0.13.0/24
10.0.0.16
100
none
No As-Path
?
10.0.204.0/24
10.0.0.16
100
none
No As-Path
===============================================================================
A:ALA-12#
A:core_east# show router bgp neighbor 10.193.0.10 graceful-restart
============================================================================
BGP Neighbor 10.193.0.10 Graceful Restart
============================================================================
Graceful Restart locally configured for peer: Enabled
Peer's Graceful Restart feature
: Enabled
NLRI(s) that peer supports restart for
: IPv4-Unicast IPv4-MPLS IPv4-VPN
NLRI(s) that peer saved forwarding for
: IPv4-Unicast IPv4-MPLS IPv4-VPN
NLRI(s) that restart is negotiated for
: None
NLRI(s) of received end-of-rib markers
: IPv4-Unicast
NLRI(s) of all end-of-rib markers sent
: IPv4-Unicast
Restart time locally configured for peer
: 120 seconds
Restart time requested by the peer
: 390 seconds
Time stale routes from peer are kept for
: 360 seconds
Graceful restart status on the peer
: Not currently being helped
Number of Restarts
: 328
Last Restart at
: 08/20/2006 12:22:06
7210 SAS M OS Routing Protocols Guide
Page 335
Show Commands
============================================================================
A:core_east#
next-hop
Syntax
Context
next-hop [ family] [ip-address] [detail]
show>router>bgp
Description
Displays BGP next-hop information.
Parameters
family — Specify the type of routing information to be distributed by the BGP instance.
Values
ipv4 — Displays only those BGP peers that have the IPv4 family enable and not those
capable of exchanging IP-VPN routes.
vpn-ipv4 — Displays the BGP peers that are IP-VPN capable.
mcast-ipv4 — Displays the BGP peers that are mcast-ipv4 capable.
ip-address — Displays the next hop information for the specified IP address.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
detail — Display the longer, more detailed version of the output.
Output
Show Next-Hop Output — The following table describes the command output fields for a BGP next hop.
Label
Description
BGP ID
The local BGP router ID.
AS
The configured autonomous system number.
Local AS
The configured local AS setting. If not configured, then the value is the
same as the AS.
Next Hop
The next-hop address.
Resolving Prefix
Displays the prefix of the best next hop.
Owner
Displays the routing protocol used to derive the best next hop.
Preference
Displays the BGP preference attribute for the routes.
Reference Count
Displays the number of routes using the resolving prefix.
Resolved Next Hop
The IP address of the next hop.
Sample Output
*A:Dut-C# show router bgp next-hop
===============================================================================
BGP Router ID:10.20.1.3
AS:5000
Local AS:5000
===============================================================================
===============================================================================
Page 336
7210 SAS M OS Routing Protocols Guide
BGP
BGP Next Hop
===============================================================================
Next Hop
Pref Owner
Resolving Prefix
Metric
Resolved Next Hop
Ref. Count
------------------------------------------------------------------------------10.20.1.1
7
RSVP
10.20.1.1/32
1000
10.10.2.1
2
10.20.1.2
7
RSVP
10.20.1.2/32
1000
10.10.3.2
2
10.20.1.4
7
RSVP
10.20.1.4/32
1000
10.10.11.4
2
------------------------------------------------------------------------------Next Hops : 3
A:ALA-49>show>router>bgp# next-hop 192.168.2.194
------------------------------------------------------------------------------BGP Router ID : 10.10.10.104
AS : 200
Local AS : 200
===============================================================================
BGP Next Hop
===============================================================================
Next Hop
Resolving
Owner Preference Reference Resolved
Prefix
Count
Next Hop
------------------------------------------------------------------------------A:ALA-49>show>router>bgp# next-hop 10.10.10.104
paths
Syntax
Context
Description
Output
paths
show>router>bgp
This command displays a summary of BGP path attributes.
Show Path Output — The following table describes the command output fields for a BGP path.
Label
Description
BGP Router ID
The local BGP router ID.
AS
The configured autonomous system number.
Local AS
The configured local AS setting. If not configured, then the value is the
same as the AS.
Path
The AS path attribute.
Origin
EGP — The NLRI is learned by an EGP protocol.
IGP — The NLRI is interior to the originating AS.
7210 SAS M OS Routing Protocols Guide
Page 337
Show Commands
Label
Description (Continued)
INCOMPLETE — NLRI was learned another way.
Next Hop
The advertised BGP nexthop.
MED
The Multi-Exit Discriminator value.
Local Preference
The local preference value. This value is used if the BGP route arrives
from a BGP peer without the Local Pref attribute set. It is overridden
by any value set via a route policy.
Refs
The number of routes using a specified set of path attributes.
ASes
The number of autonomous system numbers in the AS path attribute.
Segments
The number of segments in the AS path attribute.
Flags
EBGP-learned — Path attributes learned by an EBGP peering.
IBGP-Learned — Path attributes learned by an IBGP peering.
Aggregator
The route aggregator ID.
Community
The BGP community attribute list.
Originator ID
The originator ID path attribute value.
Cluster List
The route reflector cluster list.
Sample Output
===============================================================================
BGP Router ID : 10.0.0.14
AS : 65206
Local AS : 65206
===============================================================================
BGP Paths
===============================================================================
Path: 60203 65001 19855 3356 15412
------------------------------------------------------------------------------Origin
: IGP
Next Hop
: 10.0.28.1
MED
: 60203
Local Preference : none
Refs
: 4
ASes
: 5
Segments
: 1
Flags
: EBGP-learned
Aggregator
: 15412 62.216.140.1
------------------------------------------------------------------------------Path: 60203 65001 19855 3356 1
1236 1236 1236 1236
------------------------------------------------------------------------------Origin
: IGP
Next Hop
: 10.0.28.1
MED
: 60203
Local Preference : none
Refs
: 2
ASes
: 9
Segments
: 1
Flags
: EBGP-learned
Page 338
7210 SAS M OS Routing Protocols Guide
BGP
routes
Syntax
Context
Description
routes [family] [received] [url file-url]
routes [family [type mvpn-type]] [brief]
routes [family] prefix [detail | longer | hunt [brief]]
routes [family [type mvpn-type]] community comm-id
routes [family [type mvpn-type]] aspath-regex reg-ex
routes mvpn-ipv4 type mvpn-type {originator-ip ip-address | source-ip ip-address | group-ip
ip-address | source-as as-number} [hunt | detail]
routes l2-vpn l2vpn-type {[rd rd] | [siteid site-id] | [veid veid]
[offset vpls-base-offset ]}
show>router>bgp
This command displays BGP route information.
When this command is issued without any parameters, then the entire BGP routing table displays.
When this command is issued with an IP prefix/mask or IP address, then the best match for the parameter
displays.
Parameters
family — Specify the type of routing information to be distributed by the BGP instance.
Values
ipv4 — Displays only those BGP peers that have the IPv4 family enable and not those
capable of exchanging IP-VPN routes.
vpn-ipv4 — Displays the BGP peers that are IP-VPN capable.
ipv6 — Displays the BGP peers that are IPv6 capable.
mcast-ipv4 — Displays the BGP peers that are mcast-ipv4 capable.
received — Specifies to show the BGP routes received from the neighbor,
prefix — Specifies the type of routing information to display.
Values
rd:[ip-address[/mask]]
rd
ip-address:number1
as-number1:number2
as-number2:number3
number1
1 — 65535
as-number1
1 — 65535
number2
0 — 4294967295
as-number2
1 — 4294967295
number3
0 — 65535
ip-addres
a.b.c.d
mask
0 — 32
filter — Specifies route criteria.
Values
hunt
Displays entries for the specified route in the RIB-In, RIB-Out, and RTM.
longer Displays the specified route and subsets of the route.
detail Display the longer, more detailed version of the output.
aspath-regex “reg-exp” — Displays all routes with an AS path matching the specified regular expression
reg-exp.
community comm.-id — Displays all routes with the specified BGP community.
7210 SAS M OS Routing Protocols Guide
Page 339
Show Commands
Values
[as-number1:comm-val1 | ext-comm | well-known-comm]
ext-comm
type:{ip-address:comm-val1 | as-number1:comm-val2 | asnumber2:comm-val1}
as-number1
0 — 65535
comm-val1
0 — 65535
type
target, origin
ip-address
a.b.c.d
comm-val2
0 — 4294967295
as-number2
0 — 4294967295
well-known-comm no-export, no-export-subconfed, no-advertise
brief — Provides a summarized display of the set of peers to which a BGP route is advertised.
rd — Pip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val}
veid — [0..4294967295
vpls-base-offset — 0..4294967295
site-id — 0..4294967295
l2vpn-type — bgp-ad | bgp-vpls | multi-homing
Output
BGP Route — The following table describes the command output fields for BGP routes.
Label
Description
BGP Router ID
The local BGP router ID.
AS
The configured autonomous system number.
Local AS
The configured local AS setting. If not configured, then the value is the
same as the AS.
Route Dist.
Displays the route distinguisher identifier attached to routes that
distinguishes the VPN it belongs.
VPN Label
Displays the label generated by the PE's label manager.
Network
The IP prefix and mask length.
Nexthop
The BGP nexthop.
From
The advertising BGP neighbor’s IP address.
Res. Nexthop
The resolved nexthop.
Local Pref.
The local preference value. This value is used if the BGP route arrives
from a BGP peer without the Local Pref attribute set. It is overridden
by any value set via a route policy.
Flag
u — used
s — suppressed
h — history
Page 340
7210 SAS M OS Routing Protocols Guide
BGP
Label
Description (Continued)
d — decayed
* — valid
i — igp
e — egp
? — incomplete
> — best
Aggregator AS
The aggregator AS value.
none — Aggregator AS attributes are not present.
Aggregator
The aggregator attribute value.
none — Aggregator attributes are not present.
Atomic Aggr.
Atomic — The atomic aggregator flag is set.
Not Atomic — The atomic aggregator flag is not set.
MED
The MED metric value.
none — MED metrics are present.
Community
The BGP community attribute list.
Cluster
The route reflector cluster list.
Originator Id
The originator ID path attribute value.
none — The originator ID attribute is not present.
Peer Router Id
The router ID of the advertising router.
AS-Path
The BGP AS path attribute.
VPRN Imported
Displays the VPRNs where a particular BGP-VPN received route has
been imported and installed.
Sample Output
*A:Dut-C# show router bgp routes hunt 1.1.1.1/32
===============================================================================
BGP Router ID:10.20.1.3
AS:5000
Local AS:5000
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid Origin codes
: i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
7210 SAS M OS Routing Protocols Guide
Page 341
Show Commands
BGP IPv4 Routes
===============================================================================
------------------------------------------------------------------------------RIB In Entries
------------------------------------------------------------------------------Network
: 1.1.1.1/32
Nexthop
: 10.20.1.1
From
: 10.20.1.1
Res. Nexthop
: 10.20.1.1 (RSVP LSP: 1)
Local Pref.
: 100
Interface Name : ip-10.10.2.3
Aggregator AS : None
Aggregator
: None
Atomic Aggr.
: Not Atomic
MED
: None
Community
: No Community Members
Cluster
: No Cluster Members
Originator Id : None
Peer Router Id : 10.20.1.1
Flags
: Used Valid Best Incomplete
AS-Path
: No As-Path
------------------------------------------------------------------------------RIB Out Entries
------------------------------------------------------------------------------------------------------------------------------------------------------------Routes : 1
===============================================================================
A:ALA-12>config>router>bgp# show router bgp routes family ipv4
===============================================================================
BGP Router ID : 10.10.10.103
AS : 200
Local AS : 200
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
BGP Routes
===============================================================================
Flag Network
Nexthop
LocalPref MED
VPN Label
As-Path
------------------------------------------------------------------------------No Matching Entries Found
===============================================================================
A:ALA-12>config>router>bgp#
A:ALA-12>config>router>bgp# show router bgp routes 13.1.0.0/24 de
===============================================================================
BGP Router ID : 10.128.0.161 AS : 65535 Local AS : 65535
===============================================================================
Legend - Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid Origin
codes : i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
BGP Routes ===============================================================================
Original Attributes
Network
: 13.1.0.0/24
Nexthop
: 10.20.1.20
Route Dist. : 10070:100
VPN Label
: 152784
From
: 10.20.1.20
Res. Nexthop
: 10.130.0.2
Local Pref. : 100
Aggregator AS: none
Aggregator
: none
Atomic Aggr. : Not Atomic
MED
: none
Page 342
7210 SAS M OS Routing Protocols Guide
BGP
Community
: target:10070:1
Cluster
: No Cluster Members
Originator Id: None
Flags
: Used Valid Best IGP
AS-Path
: 10070 {14730}
Peer Router Id : 10.20.1.20
Modified Attributes
Network
: 13.1.0.0/24
Nexthop
: 10.20.1.20
Route Dist. : 10001:100
VPN Label
: 152560
From
: 10.20.1.20
Res. Nexthop
: 10.130.0.2
Local Pref. : 100
Aggregator AS: none
Aggregator
: none
Atomic Aggr. : Not Atomic
MED
: none
Community
: target:10001:1
Cluster
: No Cluster Members
Originator Id: None
Peer Router Id : 10.20.1.20
Flags
: Used Valid Best IGP
AS-Path
: No As-Path
------------------------------------------------------------------------------...
===============================================================================
A:ALA-12>config>router>bgp#
A:SR-12# show router bgp routes 100.0.0.0/30 hunt
===============================================================================
BGP Router ID : 10.20.1.1
AS : 100Local AS : 100
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
BGP Routes
===============================================================================
RIB In Entries
------------------------------------------------------------------------------Network
: 100.0.0.0/30
Nexthop
: 10.20.1.2
Route Dist.
: 10.20.1.2:1
VPN Label
: 131070
From
: 10.20.1.2
Res. Nexthop
: 10.10.1.2
Local Pref.
: 100
Interface Name: to-sr7
Aggregator AS : none
Aggregator
: none
Atomic Aggr.
: Not Atomic
MED
: none
Community
: target:10.20.1.2:1
Cluster
: No Cluster Members
Originator Id : None
Peer Router Id: 10.20.1.2
Flags
: Used Valid Best IGP
AS-Path
: No As-Path
VPRN Imported : 1 2 10 12
------------------------------------------------------------------------------RIB Out Entries
------------------------------------------------------------------------------Routes : 1
===============================================================================
A:SR-12#
7210 SAS M OS Routing Protocols Guide
Page 343
Show Commands
*A:praragon-sim1# show router bgp routes mvpn-ipv4 brief
===============================================================================
BGP Router ID:10.20.1.3
AS:200
Local AS:200
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
BGP MVPN-IPv4 Routes
===============================================================================
Flag RouteType
OriginatorIP
SourceIP
RD
SourceAS
GroupIP
------------------------------------------------------------------------------u*>i Intra-Ad
10.20.1.4
1:1
u*>i Source-Ad
130.100.1.2
1:1
227.0.0.0
u* >i Source-Join
150.100.1.2
1:1
200
226.0.0.0
------------------------------------------------------------------------------Routes : 3
===============================================================================
*A:praragon-sim1#
*A:praragon-sim1# show router bgp routes mvpn-ipv4 type source-join source-as 200 source-ip
150.100.1.2 group-ip 226.0.0.0 detail
===============================================================================
BGP Router ID:10.20.1.3
AS:200
Local AS:200
===============================================================================
Legend Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
BGP MVPN-IPv4 Routes
===============================================================================
Route Type
: Source-Join
Route Dist.
: 1:1
Source AS
: 200
Source IP
: 150.100.1.2
Group IP
: 226.0.0.0
Nexthop
: 10.20.1.4
From
: 10.20.1.4
Res. Nexthop
: 0.0.0.0
Local Pref.
: 100
Interface Name : NotAvailable
Aggregator AS : None
Aggregator
: None
Atomic Aggr.
: Not Atomic
MED
: 0
Community
: target:10.20.1.3:2
Cluster
: No Cluster Members
Originator Id : None
Peer Router Id : 10.20.1.4
Flags
: Used Valid Best IGP
AS-Path
: No As-Path
------------------------------------------------------------------------------Routes : 1
===============================================================================
*A:praragon-sim1#
Page 344
7210 SAS M OS Routing Protocols Guide
BGP
summary
Syntax
Context
Description
summary [all]
summary [family family] [neighbor ip-address]
show>router>bgp
This command displays a summary of BGP neighbor information.
If confederations are not configured, that portion of the output will not display.
The “State” field displays the global BGP operational state. The valid values are:
Up — BGP global process is configured and running.
Down — BGP global process is administratively shutdown and not running.
Disabled — BGP global process is operationally disabled. The process must be restarted by the operator.
For example, if a BGP peer is operationally disabled, then the state in the summary table shows the state
‘Disabled’
Parameters
family — Specify the type of routing information to be distributed by the BGP instance.
ipv4 — Displays only those BGP peers that have the IPv4 family enabled.
vpn-ipv4 — Displays the BGP peers that are IP-VPN capable.
neighbor ip-address — Clears damping information for entries received from the BGP neighbor.
Values
Output
ipv4-address:
a.b.c.d
BGP Summary Output — The following table describes the command output fields for a BGP summary.
Label
Description
BGP Router ID
The local BGP router ID.
AS
The configured autonomous system number.
Local AS
The configured local AS setting. If not configured, then the value is the
same as the AS.
BGP Admin State
Down — BGP is administratively disabled.
Up — BGP is administratively enabled.
BGP Oper State
Down — BGP is operationally disabled.
Up — BGP is operationally enabled.
Bfd
Yes — BFD is enabled.
No — BFD is disabled.
Confederation AS
The configured confederation AS.
Member Confederations
The configured members of the BGP confederation.
7210 SAS M OS Routing Protocols Guide
Page 345
Show Commands
Label
Description (Continued)
Number of Peer
Groups
The total number of configured BGP peer groups.
Number of Peers
The total number of configured BGP peers.
Total BGP Active
Routes
The total number of BGP routes used in the forwarding table.
Total BGP Routes
The total number of BGP routes learned from BGP peers.
Total BGP Paths
The total number of unique sets of BGP path attributes learned from
BGP peers.
Total Path Memory
Total amount of memory used to store the path attributes.
Total Suppressed
Routes
Total number of suppressed routes due to route damping.
Total History
Routes
Total number of routes with history due to route damping.
Total Decayed
Routes
Total number of decayed routes due to route damping.
Total VPN Peer
Groups
The total number of configured VPN peer groups.
Total VPN Peers
The total number of configured VPN peers.
Total VPN Local
Rts
The total number of configured local VPN routes.
Total VPN Remote
Rts
The total number of configured remote VPN routes.
Total VPN Remote
Active Rts.
The total number of active remote VPN routes used in the forwarding
table.
Total VPN
Supp.Rts.
Total number of suppressed VPN routes due to route damping.
Total VPN Hist.
Rts.
Total number of VPN routes with history due to route damping.
Total VPN Decay
Rts.
Total number of decayed routes due to route damping.
Neighbor
BGP neighbor address.
AS
BGP neighbor autonomous system number.
(Neighbor)
Page 346
PktRcvd
Total number of packets received from the BGP neighbor.
PktSent
Total number of packets sent to the BGP neighbor.
InQ
The number of BGP messages to be processed.
7210 SAS M OS Routing Protocols Guide
BGP
Label
Description (Continued)
OutQ
The number of BGP messages to be transmitted.
Up/Down
The amount of time that the BGP neighbor has either been established
or not established depending on its current state.
State|Recv/Actv/
Sent
The BGP neighbor’s current state (if not established) or the number of
received routes, active routes and sent routes (if established).
Sample Output
A:Dut-C# show router bgp summary neighbor 3FFE::A0A:1064
===============================================================================
BGP Router ID : 10.20.1.3
AS : 100
Local AS : 100
===============================================================================
BGP Admin State
: Up
BGP Oper State
: Up
Number of Peer Groups
: 4
Number of Peers
: 5
Total BGP Paths
: 8
Total Path Memory
: 1212
Total BGP Active Rts.
: 0
Total BGP Rts.
: 0
Total Supressed Rts.
: 0
Total Hist. Rts.
: 0
Total Decay Rts.
: 0
Total
Total
Total
Total
Total
VPN
VPN
VPN
VPN
VPN
Peer Groups
Local Rts.
Remote Rts.
Supp. Rts.
Decay Rts.
:
:
:
:
:
0
0
0
0
0
Total VPN Peers
: 0
Total VPN Remote Active Rts.: 0
Total VPN Hist. Rts.
: 0
Total IPv6 Remote Rts. : 5
Total IPv6 Rem. Active Rts. : 4
===============================================================================
BGP Summary
===============================================================================
Neighbor
AS
PktRcvd InQ Up/Down
State|Rcv/Act/Sent (IPv4)
PktSent OutQ
Rcv/Act/Sent (VpnIPv4)
Rcv/Act/Sent (IPv6)
Rcv/Act/Sent (MCastIPv4)
------------------------------------------------------------------------------3FFE::A0A:1064
103
489
0 00h40m28s IPv4 Incapable
569
0
VPN-IPv4 Incapable
1/1/3
MCAST-IPv4 Incapable
===============================================================================
A:Dut-C#
A:SetupCLI>show>router# bgp summary
===============================================================================
BGP Router ID : 21.3.4.5
AS : 35012
Local AS : 100
===============================================================================
BGP Admin State
: Up
BGP Oper State
: Up
Confederation AS
: 40000
Member Confederations
: 35012 65205 65206 65207 65208
Rapid Withdrawal
: Disabled
7210 SAS M OS Routing Protocols Guide
Page 347
Show Commands
Bfd Enabled
: Yes
Number of Peer Groups
Total BGP Paths
Total BGP Active Rts.
Total Supressed Rts.
Total Decay Rts.
:
:
:
:
:
1
3
0
0
0
Number of Peers
Total Path Memory
Total BGP Rts.
Total Hist. Rts.
:
:
:
:
Total
Total
Total
Total
Total
:
:
:
:
:
1
0
0
0
0
Total VPN Peers
: 1
VPN
VPN
VPN
VPN
VPN
Peer Groups
Local Rts.
Remote Rts.
Supp. Rts.
Decay Rts.
1
396
0
0
Total VPN Remote Active Rts.: 0
Total VPN Hist. Rts.
: 0
===============================================================================
BGP Summary
===============================================================================
Neighbor
AS
PktRcvd InQ Up/Down
State|Rcv/Act/Sent (IPv4)
PktSent OutQ
Rcv/Act/Sent (VpnIPv4)
Rcv/Act/Sent (MCastIPv4)
------------------------------------------------------------------------------3.3.3.3
20
0
0
01h55m56s Active
0
0
===============================================================================
A:SetupCLI>show>router#
Page 348
7210 SAS M OS Routing Protocols Guide
BGP
Clear Commands
damping
Syntax
Context
damping [[ip-prefix/ip-prefix-length] [neighbor ip-address]] | [group name]
clear>router>bgp
Description
This command clears or resets the route damping information for received routes.
Parameters
ip-prefix/ip-prefix-length — Clears damping information for entries that match the IP prefix and prefix
length.
Values
ipv4-prefix:
ipv4-prefix-length:
a.b.c.d (host bits must be 0)
0 — 32
neighbor ip-address — Clears damping information for entries received from the BGP neighbor.
Values
ipv4-address:
a.b.c.d
group name — Clears damping information for entries received from any BGP neighbors in the peer group.
Values
32 characters maximum
flap-statistics
Syntax
Context
flap-statistics [[ip-prefix/mask] [neighbor ip-address]] | [group group-name] | [regex reg-exp] |
[policy policy-name]
clear>router>bgp
Description
This command clears route flap statistics.
Parameters
ip-prefix/mask — Clears route flap statistics for entries that match the specified IP prefix and mask length.
Values
ip-prefix:
mask:
a.b.c.d (host bits must be 0)
0 — 32
neighbor ip-address — Clears route flap statistics for entries received from the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d
group group-name — Clears route flap statistics for entries received from any BGP neighbors in the
specified peer group.
regex reg-exp — Clears route flap statistics for all entries which have the regular expression and the AS path
that matches the regular expression.
policy policy-name — Clears route flap statistics for entries that match the specified route policy.
7210 SAS M OS Routing Protocols Guide
Page 349
Clear Commands
neighbor
Syntax
Context
neighbor {ip-address | as as-number | external | all} [soft | soft-inbound]
neighbor{ip-address | as as-number | external | all} statistics
neighbor ip-address end-of-rib
clear>router>bgp
Description
This command resets the specified BGP peer or peers. This can cause existing BGP connections to be
shutdown and restarted.
Parameters
ip-address — Resets the BGP neighbor with the specified IP address.
Values
ipv4-address:
a.b.c.d
as as-number — Resets all BGP neighbors with the specified peer AS.
Values
1 — 65535
external — Resets all EBGP neighbors.
all — Resets all BGP neighbors.
soft — The specified BGP neighbor(s) re-evaluates all routes in the Local-RIB against the configured export
policies.
soft-inbound — The specified BGP neighbor(s) re-evaluates all routes in the RIB-In against the configures
import policies.
statistics — The BGP neighbor statistics.
end-of-rib — Clears the routing information base (RIB).
protocol
Syntax
Context
Description
Page 350
protocol
clear>router>bgp
Resets the entire BGP protocol.
7210 SAS M OS Routing Protocols Guide
BGP
Debug Commands
events
Syntax
Context
events [neighbor ip-address | group name]
no events
debug>router>bgp
Description
This command logs all events changing the state of a BGP peer.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
graceful-restart
Syntax
Context
Description
graceful-restart [neighbor ip-address | group name]
no graceful-restart
debug>router>bgp
This command enables debugging for BGP graceful-restart.
The no form of the command disables the debugging.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
keepalive
Syntax
Context
keepalive [neighbor ip-addr | group name]
no keepalive
debug>router>bgp
Description
This command decodes and logs all sent and received keepalive messages in the debug log.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
7210 SAS M OS Routing Protocols Guide
Page 351
Debug Commands
notification
Syntax
Context
notification [neighbor ip-address | group name]
no notification
debug>router>bgp
Description
This command decodes and logs all sent and received notification messages in the debug log.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
open
Syntax
Context
open [neighbor ip-address | group name]
no open
debug>router>bgp
Description
This command decodes and logs all sent and received open messages in the debug log.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
outbound-route-filtering
Syntax
Context
Description
[no] outbound-route-filtering
debug>router>bgp
This command enables debugging for for all BGP outbound route filtering (ORF) packets. ORF is used to
inform a neighbor of targets (using target-list) that it is willing to receive.
packets
Syntax
Context
Description
Page 352
packets [neighbor ip-address | group name]
packets
debug>router>bgp
This command decodes and logs all sent and received BGP packets in the debug log.
7210 SAS M OS Routing Protocols Guide
BGP
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
route-refresh
Syntax
Context
route-refresh [neighbor ip-address | group name]
no route-refresh
debug>router>bgp
Description
Thic command enables and disables debugging for BGP route-refresh.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
rtm
Syntax
Context
rtm [neighbor ip-address | group name]
no rtm
debug>router>bgp
Description
This command logs RTM changes in the debug log.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
socket
Syntax
Context
socket [neighbor ip-address | group name]
no socket
debug>router>bgp
Description
This command logs all TCP socket events to the debug log.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
7210 SAS M OS Routing Protocols Guide
Page 353
Debug Commands
timers
Syntax
Context
timers [neighbor ip-address | group name]
no timers
debug>router>bgp
Description
This command logs all BGP timer events to the debug log.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
update
Syntax
Context
update [neighbor ip-address | group name]
no update
debug>router>bgp
Description
This command decodes and logs all sent and received update messages in the debug log.
Parameters
neighbor ip-address — Debugs only events affecting the specified BGP neighbor.
Values
ipv4-address:
a.b.c.d (host bits must be 0)
group name — Debugs only events affecting the specified peer group and associated neighbors.
Page 354
7210 SAS M OS Routing Protocols Guide
BGP
7210 SAS M OS Routing Protocols Guide
Page 355
Debug Commands
Page 356
7210 SAS M OS Routing Protocols Guide
Route Policies
In This Chapter
This chapter provides information about configuring route policies.
Topics in this chapter include:
•
Configuring Route Policies on page 358
→ Policy Statements on page 359
−
•
Default Action Behavior on page 360
BGP and OSPF Route Policy Support on page 368
−
BGP Route Policies on page 368
−
Re-advertised Route Policies on page 370
→ When to Use Route Policies on page 371
•
Route Policy Configuration Process Overview on page 372
•
Configuration Notes on page 373
7210 SAS M, X OS Routing Protocols Guide
Page 357
Configuring Route Policies
Configuring Route Policies
Alcatel-Lucent’s 7210 SAS M, X supports two databases for routing information. The routing
database is composed of the routing information learned by the routing protocols. The forwarding
database is composed of the routes actually used to forward traffic through a router. In addition,
link state databases are maintained by interior gateway protocols (IGPs) such as IS-IS and OSPF.
Routing protocols calculate the best route to each destination and place these routes in a
forwarding table. The routes in the forwarding table are used to forward routing protocol traffic,
sending advertisements to neighbors and peers.
A routing policy can be configured that will not place routes associated with a specific origin in the
routing table. Those routes will not be used to forward data packets to the intended destinations
and the routes are not advertised by the routing protocol to neighbors and peers.
Routing policies control the size and content of the routing tables, the routes that are advertised,
and the best route to take to reach a destination. Careful planning is essential to implement route
policies that can affect the flow of routing information or packets in and traversing through the
router. Before configuring and applying a route policy, develop an overall plan and strategy to
accomplish your intended routing actions.
There are no default route policies. Each policy must be created explicitly and applied to a routing
protocol or to the forwarding table. Policy parameters are modifiable.
Page 358
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Policy Statements
Route policies contain policy statements containing ordered entries containing match conditions
and actions you specify. The entries should be sequenced from the most explicit to least explicit.
Packet forwarding and routing can be implemented according to your defined policies. Policybased routing allows you to dictate where traffic can be routed, through specific paths, or whether
to forward or drop the traffic. Route policies can match a given route policy entry and continue
searching for other matches within either the same route policy or the next route policy.
The process can stop when the first complete match is found and executes the action defined in the
entry, either to accept or reject packets that match the criteria or proceed to the next entry or the
next policy. You can specify matching criteria based on source, destination, or particular
properties of a route. Route policies can be constructed to support multiple stages to the evaluation
and setting various route attributes. You can also provide more matching conditions by specifying
criteria such as:
•
•
Prefix list — A named list of prefixes.
To and From criteria — A route’s source and destination.
7210 SAS M, X OS Routing Protocols Guide
Page 359
Configuring Route Policies
Default Action Behavior
The default action specifies how packets are to be processed when a policy related to the route is
not explicitly configured. The following default actions are applied in the event that:
•
A route policy does not specify a matching condition, all the routes being compared with
the route policy are considered to be matches.
•
A packet does not match any policy entries, then the next policy is evaluated.
If a match does not occur then the last entry in the last policy is evaluated.
•
If no default action is specified, the default behavior of the protocol controls whether the
routes match or not.
If a default action is defined for one or more of the configured route policies, then the default
action is handled as follows:
•
The default action can be set to all available action states including accept, reject, nextentry, and next-policy.
•
If the action states accept or reject, then the policy evaluation terminates and the
appropriate result is returned.
•
If a default action is defined and no matches occurred with the entries in the policy, then
the default action is used.
•
If a default action is defined and one or more matches occurred with the entries of the
policy, then the default action is not used.
Denied IP Prefixes
The following IP address prefixes are not allowed by the routing protocols and the Route Table
Manager and are not be populated within the forwarding table:
•
0.0.0.0/8 or longer
•
127.0.0.0/8 or longer
•
224.0.0.0/4 or longer
•
240.0.0.0/4 or longer
Any other prefixes that need to be filtered can be filtered explicitly using route policies.
Page 360
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Controlling Route Flapping
Route damping is a controlled acceptance of unstable routes from BGP peers so that any ripple
effect caused by route flapping across BGP AS border routers is minimized. The motive is to delay
the use of unstable routes (flapping routes) to forward data and advertisements until the route
stabilizes.
Alcatel-Lucent’s implementation of route damping is based on the following parameters:
•
Figure of Merit — A route is assigned a Figure of Merit (FoM), which is proportional to
the frequency of flaps. FoM should be able to characterize a route’s behavior over a period
of time.
•
Route flap — A route flap is not limited to the withdrawn route. It also applies to any
change in the AS path or the next hop of a reachable route. A change in AS path or next
hop indicates that the intermediate AS or the route-advertising peer is not suppressing
flapping routes at the source or during the propagation. Even if the route is accepted as a
stable route, the data packets destined to the route could experience unstable routing due to
the unstable AS path or next hop.
•
Suppress threshold — The threshold is a configured value that, when exceeded, the route
is suppressed and not advertised to other peers. The state is considered to be down from
the perspective of the routing protocol.
•
Reuse threshold — When FoM value falls below a configured reuse threshold and the
route is still reachable, the route is advertised to other peers.
The FoM value decays exponentially after a route is suppressed. This requires the BGP
implementation to decay thousands of routes from a misbehaving peer.
The two events that could trigger the route flapping algorithm are:
•
Route flapping — If a route flap is detected within a configured maximum route flap
history time, the route’s FoM is initialized and the route is marked as a potentially unstable
route. Every time a route flaps, the FoM is increased and the route is suppressed if the
FoM crosses the suppress threshold.
•
Route reuse timer trigger — A suppressed route’s FoM decays exponentially. When it
crosses the reuse threshold, the route is eligible for advertisement if it is still reachable.
If the route continues to flap, the FoM, with respect to time scale, looks like a sawtooth waveform
with the exponential rise and decay of FoM. To control flapping, the following parameters can be
configured:
•
half-life — The half life value is the time, expressed in minutes, required for a route
to remain stable in order for one half of the FoM value to be reduced. For example, if the
half life value is 6 (minutes) and the route remains stable for 6 minutes, then the new FoM
7210 SAS M, X OS Routing Protocols Guide
Page 361
Configuring Route Policies
value is 3. After another 6 minutes passes and the route remains stable, the new FoM value
is 1.5.
•
max-suppress — The maximum suppression time, expressed in minutes, is the
maximum amount of time that a route can remain suppressed.
•
suppress — If the FoM value exceeds the configured integer value, the route is
suppressed for use or inclusion in advertisements.
•
Page 362
reuse — If the suppress value falls below the configured reuse value, then the route can
be reused.
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Regular Expressions
The ability to perform a filter match on confederations in the AS-PATH is supported. This feature
allows customers to configure match criteria for specific confederation sets and sequences within
the AS path so that they can be filtered out before cluttering the service provider’s routing
information base (RIB).
7210 SAS uses regular expression strings to specify match criteria for:
•
An AS path string; for example, “100 200 300”
•
A community string; for example, “100:200” where 100 is the AS number, and 200 is the
community-value.
•
Any AS path beginning with a confederation SET or SEQ containing 65001 and 65002
only: for example “< 65001 65002 >.*”
•
Any AS path containing a confederation SET or SEQ, regardless of the contents: for
example, “.* <.*> .*”
A regular expression is expressed in terms of terms and operators. A term for an AS path regular
expression is:
1. Regular expressions should always be enclosed in quotes.
2. An elementary term; for example, an AS number “200”
3. A range term composed of two elementary terms separated by the ‘-’ character like “200300”.
4. The '.' dot wild-card character which matches any elementary term.
5. A regular expression enclosed in parenthesis “( )”.
6. A regular expression enclosed in square brackets used to specify a set of choices of elementary or range terms; for example. [100-300 400] matches any AS number between 100
and 300 or the AS number 400.
A term for a community string regular expression is a string that is evaluated character by
character and is composed of:
1. An elementary term which for a community string is any single digit like “4”.
2. A range term composed of two elementary terms separated by the ‘-’ character like “2-3”.
3. A colon ':' to delimit the AS number from the community value
4. The '.' dot wild-card character which matches any elementary term or ':'.
5. A regular expression enclosed in parenthesis “( )”.
7210 SAS M, X OS Routing Protocols Guide
Page 363
Regular Expressions
6. A regular expression enclosed in square brackets used to specify a set of choices of elementary or range terms; for example, [1-37] matches any single digit between 1 and 3 or
the digit 7.
The regular expression OPERATORS are listed in Table 9.
Table 9: Regular Expression Operators
Operator
|
Matches the term on alternate sides of the pipe.
*
Matches multiple occurrences of the term.
?
Matches 0 or 1 occurrence of the term.
+
Matches 1 or more occurrence of the term.
( )
Used to parenthesize so a regular expression is considered as one term.
[ ]
Used to demarcate a set of elementary or range terms.
{m,n}
Used between the start and end of a range.
Matches least m and at most n repetitions of the term.
{m}
Matches exactly m repetitions of the term.
{m,}
Matches m or more repetitions of the term.
^
Matches the beginning of the string - only allowed for communities.
$
Matches the end of the string - only allowed for communities.
\
An escape character to indicate that the following character is a match criteria and
not a grouping delimiter.
<>
Page 364
Description
Matches any AS path numbers containing a confederation SET or SEQ.
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Examples of AS path and community string regular expressions are listed in Table 10.
Table 10: AS Path and Community Regular Expression Examples
AS Path to Match Criteria
Regular Expression
Example Matches
Null AS path
nulla
Null AS path
AS path is 11
11
11
AS path is 11 22 33
11 22 33
11 22 33
Zero or more occurrences of AS number 11
11*
Null AS path
11
11 11
11 11 11
11 … 11
Path of any length that begins with AS numbers 11, 22,
33
11 22 33 .*
11 22 33
11 22 33 400 500 600
Path of any length that ends with AS numbers 44, 55, 66
.* 44 55 66
44 55 66
100 44 55 66
100 200 44 55 66
100 200 300 44 55 66
100 200 300 … 44 55 66
One occurrence of the AS numbers 100 and 200,
followed by one or more occurrences of the number 33
100 200 33+
100 200 33
100 200 33 33
100 200 33 33 33
100 200 33 33 33 … 33
One or more occurrences of AS number 11, followed by
one or more occurrences of AS number 22, followed by
one or more occurrences of AS number 33
11+ 22+ 33+
11 22 33
11 11 22 33
11 11 22 22 33
11 11 22 22 33 33
11 … 11 22 … 22 33 …33
Path whose second AS number must be 11 or 22
(. 11) | (. 22)
.*
or
. (11 | 22) .*
100 11
200 22 300 400
…
Path of length one or two whose second AS number
might be 11 or 22
. (11 | 22)?
100
200 11
300 22
7210 SAS M, X OS Routing Protocols Guide
Page 365
Regular Expressions
Table 10: AS Path and Community Regular Expression Examples (Continued)
AS Path to Match Criteria
Regular Expression
Example Matches
Path whose first AS number is 100 and second AS
number is either 11 or 22
100 (11 | 22) .*
100 11
100 22 200 300
Either AS path 11, 22, or 33
[11 22 33]
11
22
33
Range of AS numbers to match a single AS number
10-14
10 or 11 or 12 or 13 or 14
[10-12]*
Null AS path
10 or 11 or 12
10 10 or 10 11 or 10 12
11 10 or 11 11 or 11 12
12 10 or 12 11 or 12 12
…
Zero or one occurrence of AS number 11
11? or 11{0,1}
Null AS path
11
One through four occurrences of AS number 11
11{1,4}
11
11 11
11 11 11
11 11 11 11
One through four occurrences of AS number 11 followed
by one occurrence of AS number 22
11{1,4} 22
11 22
11 11 22
11 11 11 22
11 11 11 11 22
Path of any length, except nonexistent, whose second AS
number can be anything, including nonexistent
. .* or . .{0,}
100
100 200
11 22 33 44 55
AS number is 100. Community value is 200.
^100:200$
100:200
AS number is 11 or 22. Community value is any number.
^((11)|(22)):(.
*)$
11:100
22:100
11:200
…
AS number is 11. Community value is any number that
starts with 1.
^11:(1.*)$
11:1
11:100
11:1100
…
Page 366
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Table 10: AS Path and Community Regular Expression Examples (Continued)
AS Path to Match Criteria
Regular Expression
Example Matches
AS number is any number. Community value is any
number that ends with 1, 2, or 3.
^(.*):(.*[13])$
11:1
100:2002
333:55553
…
AS number is 11 or 22. Community value is any number
that starts with 3 and ends with 4, 5 or 9.
^((11)|(22)):(3
.*[459])$
11:34
22:3335
11:3777779
…
AS number is 11 or 22. Community value ends in 33 or
44.
[^((11|22)):(.*
((33)|(44)))$
11:33
22:99944
22:555533
…
a.The null keyword matches an empty AS path.
7210 SAS M, X OS Routing Protocols Guide
Page 367
Regular Expressions
BGP and OSPF Route Policy Support
OSPF and BGP requires route policy support. Figure 12 and Figure 14 display where route policies
are evaluated in the protocol. Figure 12 depicts BGP which applies a route policy as an internal
part of the BGP route selection process. Figure 14 depicts OSPF which applies routing policies at
the edge of the protocol, to control only the routes that are announced to or accepted from the
Route Table Manager (RTM).
RIB-Out
BGP Export
Route Policy
RIB-In
BGP Import
Route Policy
Route
Selection
Loc-RIB
Learned BGP Routes
from Peers
Submit BEST
BGP Routes
Reject
RTM
RTM signals
Which routes
are Used
Non-BGP
routes are
taken
from RTM
and
Exported
to BGP
Figure 12: BGP Route Policy Diagram
BGP Route Policies
Alcatel-Lucent’s implementation of BGP uses route policies extensively. The implied or default
route policies can be overridden by customized route policies. The default BGP properties, with no
route policies configured, behave as follows:
•
Page 368
Accept all BGP routes into the RTM for consideration.
7210 SAS M, X OS Routing Protocols Guide
Route Policies
•
Announce all used BGP learned routes to other BGP peers
•
Announce none of the IGP, static or local routes to BGP peers.
RIB-Out
BGP Export
Route Policy
Route
Selection
BGP Import
Route Policy
RIB-In
Loc-RIB
Learned BGP Routes
from Peers
Submit BEST
BGP Routes
Reject
RTM signals
Which routes
are Used
Non-BGP
routes are
taken
from RTM
and
Exported
to BGP
RTM
Figure 13: BGP Route Policy Diagram
Inject External
OSPF LSAs
SPF
LSDB
OSPF Export
Route Policy
OSPF Route
Table
RTM
Figure 14: OSPF Route Policy Diagram
7210 SAS M, X OS Routing Protocols Guide
Page 369
Regular Expressions
Re-advertised Route Policies
Occasionally, BGP routes may be readvertised from BGP into OSPF, IS-IS, and RIP. OSPF export
policies (policies control which routes are exported to OSPF) are not handled by the main OSPF
task but are handled by a separate task or an RTM task that filters the routes before they are
presented to the main OSPF task.
Page 370
7210 SAS M, X OS Routing Protocols Guide
Route Policies
When to Use Route Policies
The following are examples of circumstances of when to configure and apply unique route
policies.
•
When you want to control the protocol to allow all routes to be imported into the routing
table. This enables the routing table to learn about particular routes to enable packet
forwarding and redistributing packets into other routing protocols.
•
When you want to control the exporting of a protocol’s learned active routes.
•
When you want a routing protocol to announce active routes learned from another routing
protocol, which is sometimes called route redistribution.
•
Route policies can be used to filter IGMP membership reports from specific hosts and/or
specific multicast groups.
•
When you want unique behaviors to control route characteristics. For example, change the
route preference, AS path, or community values to manipulate the control the route
selection.
•
When you want to control BGP route flapping (damping).
7210 SAS M, X OS Routing Protocols Guide
Page 371
Route Policy Configuration Process Overview
Route Policy Configuration Process Overview
Figure 15 displays the process to provision basic route policy parameters.
START
CONFIGURE AS-PATH EXPRESSIONS
CONFIGURE COMMUNITY LISTS
CONFIGURE DAMPING PARAMETERS
CONFIGURE PREFIX LISTs
CONFIGURE ROUTE POLICY
APPLY ROUTE POLICIES
ENABLE
Figure 15: Route Policy Configuration and Implementation Flow
Page 372
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Configuration Notes
This section describes route policy configuration caveats.
General
•
When configuring policy statements, the policy statement name must be unique.
7210 SAS M, X OS Routing Protocols Guide
Page 373
Configuration Notes
Page 374
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Configuring Route Policies with CLI
This section provides information to configure route policies using the command line interface.
Topics in this section include:
•
Route Policy Configuration Overview on page 376
→ When to Create Routing Policies on page 376
→ Policy Evaluation on page 378
•
Configuring Route Policy Components on page 383
→ Creating a Route Policy on page 385
→ Beginning the Policy Statement on page 384
→ Configuring an Entry on page 387
→ Configuring a Prefix List on page 389
•
Route Policy Configuration Management Tasks on page 390
7210 SAS M, X OS Routing Protocols Guide
Page 375
Route Policies
Route Policy Configuration Overview
Route policies allow you to configure routing according to specifically defined policies. You can
create policies and entries to allow or deny paths based on various parameters such as destination
address.
Policies can be as simple or complex as required. A simple policy can block routes for a specific
location or IP address. More complex policies can be configured using numerous policy statement
entries containing matching conditions to specify whether to accept or reject the route, control how
a series of policies are evaluated, and manipulate the characteristics associated with a route.
When to Create Routing Policies
Route policies are created in the config>router context. There are no default route policies. Each
route policy must be explicitly created and applied. Applying route policies can introduce more
efficiency as well as more complexity to 7210 SAS routers’ capabilities.
A route policy impacts the flow of routing information or packets within and through the router. A
routing policy can be specified to prevent a particular customer’s routes to be placed in the route
table which causes those routes to not forward traffic to various destinations and the routes are not
advertised by the routing protocol to neighbors.
Route policies can be created to control:
•
A protocol to export all the active routes learned by that protocol.
•
Route characteristics to control which route is selected to act as the active route to reach a
destination and advertise the route to neighbors.
•
Protocol to import all routes into the routing table. A routing table must learn about
particular routes to be able to forward packets and redistribute to other routing protocols.
•
Damping.
Before a route policy is applied, analyze the policy’s purpose and be aware of the results (and
consequences) when packets match the specified criteria and the associated actions and default
actions, if specified, are executed. Membership reports can be filtered based on a specific source
address.
Page 376
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Default Route Policy Actions
Each routing protocol has default behaviors for the import and export of routing information.
Table 11 shows the default behavior for each routing protocol.
Table 11: Default Route Policy Actions
Protocol
Import
Export
OSPF
Not applicable. All OSPF routes are
accepted from OSPF neighbors and
cannot be controlled via route policies.
• Internal routes: All OSPF routes are automatically
advertised to all neighbors.
• External routes: By default all non-OSPF learned
routes are not advertised to OSPF neighbors
IS-IS
Not applicable. All IS-IS routes are
accepted from IS-IS neighbors and can
not be controlled via route policies
• Internal routes: All IS-IS routes are automatically
advertised to all neighbors.
• External routes: By default all non-IS-IS learned routes
are not advertised to IS-IS peers.
BGP
By default, all routes from BGP.
• Internal routes: By default all active BGP routes are
advertised to BGP peers
• External routes: By default all non-BGP learned routes
are not advertised to BGP peers.
7210 SAS M, X OS Routing Protocols Guide
Page 377
Route Policies
Policy Evaluation
Routing policy statements can consist of as few as one or several entries. The entries specify the
matching criteria. A route is compared to the first entry in the policy statement. If it matches, the
specified entry action is taken, either accepted or rejected. If the action is to accept or reject the
route, that action is taken and the evaluation of the route ends.
If the route does not match the first entry, the route is compared to the next entry (if more than one
is configured) in the policy statement. If there is a match with the second entry, the specified action
is taken. If the action is to accept or reject the route, that action is taken and the evaluation of the
route ends, and so on.
Each route policy statement can have a default-action clause defined. If a default-action is defined
for one or more of the configured route policies, then the default actions should be handled in the
following ways:
•
The process stops when the first complete match is found and executes the action defined
in the entry.
•
If the packet does not match any of the entries, the system executes the default action
specified in the policy statement.
Figure 16 depicts an example of the route policy process.
Route policies can also match a given route policy entry and continue to search for other entries
within either the same route policy or the next route policy by specifying the next-entry or nextpolicy option in the entry’s action command. Policies can be constructed to support multiple states
to the evaluation and setting of various route attributes.
Figure 17 depicts the next-policy and next-entry route processes.
Page 378
7210 SAS M, X OS Routing Protocols Guide
Route Policies
ROUTE
POLICY-STATEMENT 274
DEFAULT ACTION
ENTRY 1
ENTRY 20
ENTRY 30
ENTRY ACTION:
matches
ACCEPT
OR REJECT
matches
ACCEPT
OR REJECT
matches
ACCEPT
OR REJECT
no match
POLICY-STATEMENT 275
DEFAULT ACTION
ENTRY 1
ENTRY 2
ENTRY 3
ENTRY ACTION:
matches
ACCEPT
OR REJECT
matches
ACCEPT
OR REJECT
matches
ACCEPT
OR REJECT
no match
DEFAULT ACTION
SPECIFIED ?
yes
PERFORM DEFAULT
ACTION
no
PERFORM ACTION SPECIFIED
BY PROTOCOL
See Table 11, Default Route Policy
Actions, on page 377
Figure 16: Route Policy Process Example
7210 SAS M, X OS Routing Protocols Guide
Page 379
Route Policies
Policy Statement
POL1
Entry 10
Match Criteria
Entry 20
Match Criteria
Entry 30
Match Criteria
Entry nn
Match Criteria
Policy Statement
POL2
Action:
next-policy
METRIC: 100
Entry 10
Match Criteria
Action:
next-policy
METRIC: 200
Entry 20
Match Criteria
Action:
next-policy
METRIC: 300
Entry 30
Match Criteria
Action:
next-policy
METRIC: nn
Policy Statement
POL3
Action:
next-policy
Entry 10
Match Criteria
Community:
A:B
Action:
next-policy
Local-Pref:
100
Entry 20
Match Criteria
Community:
C:D
Entry nn
Match Criteria
Action:
next-policy
Community:
E:F
Action:
next-policy
Community:
Y-Z
Action:
next-policy
Entry 30
Match Criteria
Entry nn
Match Criteria
Action:
next-policy
Local-Pref:
200
Action:
next-policy
Local-Pref:
300
Action:
next-policy
Local-Pref:
nn
Figure 17: Next Policy Logic Example
Page 380
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Damping
Damping initiates controls when routes flap. Route flapping can occur when an advertised route
between nodes alternates (flaps) back and forth between two paths due to network problems which
cause intermittent route failures. It is necessary to reduce the amount of routing state change
updates propagated in order to limit processing requirements. Thus, when a route flaps beyond a
configured value (the suppress value), then that route is removed from the routing tables and
routing protocols until the value falls below the reuse value.
A route can be suppressed according to the Figure of Merit (FoM) value. The FoM is a value that
is added to a route each time it flaps. A new route begins with an FoM value of 0.
Damping is optional. If damping is configured, the following parameter values must be explicitly
specified as there are no default values:
•
suppress
•
half-life
•
reuse
•
max-suppress
When a route's FoM value exceeds the suppress value, then the route is removed from the routing
table. The route is considered to be stable when the FoM drops below the reuse value by means
of the specified half life parameter. The route is returned to the routing tables. When routes have
higher FoM and half life values, they are suppressed for longer periods of time. Figure 18 depicts
an example of a flapping route, the suppress threshold, the half life decay (time), and reuse
threshold. The peaks represent route flaps, the slopes represent half life decay.
SUPPRESS THRESHOLD
FoM
REUSE THRESHOLD
TIME
Figure 18: Damping Example
7210 SAS M, X OS Routing Protocols Guide
Page 381
Route Policies
Basic Configurations
This section provides information to configure route policies and configuration examples of
common tasks. The minimal route policy parameters that need to be configured are:
•
Policy statement with the following parameters specified:
→ At least one entry
→ Entry action
Following is a sample route policy configuration:
A:ALA-B>config>router>policy-options# info
---------------------------------------------. . .
policy-statement "aggregate-customer-peer-only"
entry 1
from
community "all-customer-announce"
exit
action accept
exit
exit
default-action reject
exit
exit
---------------------------------------------A:ALA-B>config>router>policy-options#
Page 382
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Configuring Route Policy Components
Use the CLI syntax displayed below to configure:
•
Creating a Route Policy on page 385
•
Beginning the Policy Statement on page 384
•
Configuring an Entry on page 387
•
Configuring a Prefix List on page 389
7210 SAS M, X OS Routing Protocols Guide
Page 383
Route Policies
Beginning the Policy Statement
Use the following CLI syntax to begin a policy statement configuration. In order for a policy
statement to be complete an entry must be specified (see Configuring an Entry on page 387).
CLI Syntax: config>router>policy-options
begin
policy-statement name
description text
The following error message displays when the you try to modify a policy options command
without entering begin first.
A:ALA-B>config>router>policy-options# policy-statement “allow all”
MINOR: CLI The policy-options must be in edit mode by calling begin before any changes can
be made.
The following example displays policy statement configuration command usage. These commands
are configured in the config>router context.
Example: config>router# policy-options
policy-options# begin
There are no default policy statement options. All parameters must be explicitly configured.
Page 384
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Creating a Route Policy
To enter the mode to create or edit route policies, you must enter the begin keyword at the
config>router>policy-options prompt. Other editing commands include:
•
The commit command saves changes made to route policies during a session.
•
The abort command discards changes that have been made to route policies during a
session.
The following error message displays when the you try to modify a policy options command
without entering begin first.
A:ALA-B>config>router>policy-options# policy-statement “allow all”
MINOR: CLI The policy-options must be in edit mode by calling begin before any changes can
be made.
A:ALA-B>config>router>policy-options# info
#-----------------------------------------# Policy
#-----------------------------------------policy-options
begin
policy-statement "allow all"
description "General Policy"
...
exit
exit
---------------------------------------------A:ALA-B>config>router>policy-options#
7210 SAS M, X OS Routing Protocols Guide
Page 385
Route Policies
Configuring a Default Action
Specifying a default action is optional. The default action controls those packets not matching any
policy statement entries. If no default action is specified for the policy, then the action associated
with the protocol to which the routing policy was applied is performed. The default action is
applied only to those routes that do not match any policy entries.
A policy statement must include at least one entry (see Configuring an Entry on page 387).
To enter the mode to create or edit route policies, you must enter the begin keyword at the
config>router>policy-options prompt. Other editing commands include:
•
The commit command saves changes made to route policies during a session.
•
The abort command discards changes that have been made to route policies during a
session.
The following example displays the default action configuration:
A:ALU-7210>config>router>policy-options# info
---------------------------------------------policy-statement "1"
default-action accept
metric set 10
exit
exit
---------------------------------------------A:ALU-7210>config>router>policy-options#
Page 386
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Configuring an Entry
An entry action must be specified. The other parameters in the entry action context are optional.
Refer to the Route Policy Command Reference on page 395 for the commands and syntax.
The following example displays entry parameters and includes the default action parameters which
were displayed in the previous section.
A:ALA-B>config>router>policy-options# info
---------------------------------------------policy-statement "1"
entry 1
to
neighbor 10.10.10.104
exit
action accept
exit
exit
entry 2
from
protocol ospf 1
exit
to
protocol ospf
neighbor 10.10.0.91
exit
action accept
exit
exit
default-action accept
. . .
exit
exit
---------------------------------------------A:ALA-B>config>router>policy-options#
7210 SAS M, X OS Routing Protocols Guide
Page 387
Route Policies
Configuring Damping
NOTES:
•
For each damping profile, all parameters must be configured.
•
The suppress value must be greater than the reuse value (see Figure 18 on page 381).
•
Damping can be enabled in the config>router>bgp context on the BGP global, group,
and neighbor levels. If damping is enabled, but route policy does not specify a damping
profile, the default damping profile will be used. This profile is always present and
consists of the following parameters:
half-life:
15 minutes
max-suppress:
60 minutes
suppress:
3000
reuse:
750
The following example displays a damping configuration:
*A:cses-A13>config>router>policy-options# info
---------------------------------------------damping "damptest123"
half-life 15
max-suppress 60
reuse 750
suppress 1000
exit
---------------------------------------------*A:cses-A13>config>router>policy-options#
Page 388
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Configuring a Prefix List
The following example displays a prefix list configuration:
A:ALA-B>config>router>policy-options# info
---------------------------------------------prefix-list "western"
prefix 10.10.0.1/32 exact
prefix 10.10.0.2/32 exact
prefix 10.10.0.3/32 exact
prefix 10.10.0.4/32 exact
exit
---------------------------------------------A:ALA-B>config>router>policy-options#
7210 SAS M, X OS Routing Protocols Guide
Page 389
Route Policies
Route Policy Configuration Management Tasks
This section discusses the following route policy configuration management tasks:
•
Editing Policy Statements and Parameters on page 390
•
Deleting an Entry on page 392
•
Deleting a Policy Statement on page 392
Editing Policy Statements and Parameters
Route policy statements can be edited to modify, add, or delete parameters. To enter the mode to
edit route policies, you must enter the begin keyword at the config>router> policyoptions prompt. Other editing commands include:
•
The commit command saves changes made to route policies during a session.
•
The abort command discards changes that have been made to route policies during a
session.
The following example displays a changed configuration:
A:ALA-B>config>router>policy-options>policy-statement# info
---------------------------------------------description "Level 1"
entry 1
to
neighbor 10.10.10.104
exit
action accept
exit
exit
entry 2
from
protocol ospf
exit
to
protocol ospf
neighbor 10.10.0.91
exit
action accept
exit
exit
entry 4
description "new entry"
from
protocol isis
area 0.0.0.20
exit
action reject
exit
Page 390
7210 SAS M, X OS Routing Protocols Guide
Route Policies
default-action accept
metric set 10
exit
----------------------------------------------
7210 SAS M, X OS Routing Protocols Guide
Page 391
Route Policies
Deleting an Entry
Use the following CLI syntax to delete a policy statement entry:
CLI Syntax: config>router>policy-options
begin
commit
abort
policy-statement name
no entry entry-id
The following example displays the commands required to delete a policy statement entry.
Example: config>router>policy-options# begin
policy-options# policy-statement "1"
policy-options>policy-statement# no entry 4
policy-options>policy-statement# commit
Deleting a Policy Statement
Use the following CLI syntax to delete a policy statement:
CLI Syntax: config>router>policy-options
begin
commit
abort
no policy-statement name
The following example displays the commands required to delete a policy statement.
Example: config>router>policy-options# begin
policy-options# no policy-statement 1
policy-options# commit
Page 392
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Use of Route Policies for IGMP Filtering
The following output is a sample route policy configuration that can be used for IGMP filtering.
This policy needs to be configured with a SAP for filtering to take effect.
---------------------------------------------A:ALA-B>config>router>policy-options#info
---------------------------------------------prefix-list "host"
prefix 11.0.0.0/8 longer
exit
prefix-list "group"
prefix 226.6.6.6/32 exact
exit
policy-statement "block-igmp"
description "Reject-Reports-From-Specific-Group-And-Host"
entry 1
from
host-ip "host"
exit
action next-entry
exit
exit
entry 2
from
group-address "group"
exit
action reject
exit
default-action accept
exit
exit
policy-statement "permit-igmp"
description "Accept-Reports-From-Specific-Group-And-Host"
entry 1
from
host-ip "host3"
group-address "group3"
exit
action accept
exit
exit
default-action reject
exit
---------------------------------------------A:ALA-B>config>router>policy-options#
7210 SAS M, X OS Routing Protocols Guide
Page 393
Route Policies
Page 394
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Route Policy Command Reference
Command Hierarchies
• Route Policy Configuration Commands on page 395
• Show Commands on page 397
Route Policy Configuration Commands
config
— [no] router
— [no] triggered-policy
— [no] policy-options
— begin
— commit
— abort
— as-path name {regular-expression | null}
— no as-path name
— community name members comm-id [comm-id … (up to 15 max)]
— no community name [members comm-id]
— [no] damping name
— half-life minutes
— no half-life
— max-suppress minutes
— no max-suppress
— reuse integer
— no reuse
— suppress integer
— no suppress
— [no] policy-statement name
— default-action {accept | next-entry | reject}
— no default-action
— as-path {add | replace} name
— no as-path
— as-path-prepend as-number [ repeat]
— no as-path-prepend
— community {{add name [remove name]} | {remove name [add
name]} | {replace name}}
— no community
— damping {name | none}
— no damping
— local-preference local-preference
— no local-preference
— metric {add | subtract | set} metric
— no metric
— next-hop ip-address
— no next-hop
— [no] next-hop-self
7210 SAS M, X OS Routing Protocols Guide7750 SR OS Routing Protocols Guide7450
Route Policy Command Reference
— origin {igp | egp | incomplete}
— no origin
— preference preference
— description description-string
— no description
— [no] entry entry-id
— action {accept| next-entry | reject}
— no action
— as-path {add | replace} name
— no as-path
— as-path-prepend as-number [ repeat]
— no as-path-prepend
— community {{add name [remove name]} | {remove name
[add name]} | {replace name}}
— no community
— damping {name | none}
— no damping
— local-preference local-preference
— no local-preference
— metric {add | subtract | set} metric
— no metric
— next-hop ip-address
— no next-hop
— [no] next-hop-self
— origin {igp | egp | incomplete}
— no origin
— preference preference
— description description-string
— no description
— [no] from
— community name
— no community
— [no] external
— family [ipv4] [vpn-ipv4] [l2-vpn]
— no family
— group-address prefix-list-name
— no group-address
— host-ip prefix-list-name
— prefix-list name [name...(up to 5 max)]
— no prefix-list
— source-address ip-address
— no source-address
— tag tag
— no tag
— type type
— no type
— [no] to
— level {1 | 2}
— no level
— neighbor {ip-address | prefix-list name}
— no neighbor
— [no] prefix-list name [name...(up to 5 max)]
— protocol protocol
— no protocol
Page 396
7210 SAS M, X OS Routing Protocols Guide
Route Policies
config
— [no] router
— [no] policy-options
— [no] prefix-list name
— prefix ip-prefix/prefix-length [exact | longer | through length | prefix-lengthrange length1-length2]
— no prefix [ipv-prefix/prefix-length] [exact | longer | through length | prefixlength-range length1-length2]
Show Commands
show
— router router-name
— policy [name | prefix-list name | admin]
7210 SAS M, X OS Routing Protocols Guide7750 SR OS Routing Protocols Guide7450
Route Policy Command Reference
Page 398
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Route Policy Command Reference
Generic Commands
abort
Syntax
Context
Description
Default
abort
config>router>policy-options
This command is required to discard changes made to a route policy.
none
begin
Syntax
Context
Description
Default
begin
config>router>policy-options
This command is required in order to enter the mode to create or edit route policies.
none
commit
Syntax
Context
Description
Default
commit
config>router>policy-options
This command is required to save changes made to a route policy.
none
7210 SAS M, X OS Routing Protocols Guide
Page 399
Generic Commands
description
Syntax
Context
Description
description string
no description
config>router>policy-options>policy-statement
config>router>policy-options>policy-statement>entry
This command creates a text description which is stored in the configuration file to help identify the content
of the entity.
The no form of the command removes the string from the configuration.
Default
Parameters
Page 400
none
string — The description character string. Allowed values are any string up to 80 characters long composed
of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the
entire string must be enclosed within double quotes.
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Route Policy Options
as-path
Syntax
as-path name {reg-exp | null}
no as-path name
Context
config>router>policy-options
Description
This command creates a route policy AS path regular expression statement to use in route policy entries.
The no form of the command deletes the AS path regular expression statement.
Default
Parameters
No AS path regular expression statement is defined.
name — The AS path regular expression name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.),
the entire string must be enclosed within double quotes.
reg-exp — The AS path regular expression. Allowed values are any string up to 256 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.),
the entire string must be enclosed within double quotes.
null — The AS path expressed as an empty regular expression string.
community
Syntax
Context
Description
community name members comm-id [comm-id...up to 15 max]
no community name [members comm-id ]
config>router>policy-options
This command creates a route policy community list to use in route policy entries.
The no form of the command deletes the community list or the provided community ID.
Default
Parameters
no community — No community names or members are specified.
name — The community list name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes.
comm-id — The community ID. Note that up to 15 community ID strings can be specified up to a total maximum of 72 characters.
Values
72 chars max
2byte-asnumber:comm-val | reg-ex | ext-comm | well-known-comm
ext-comm
type:{ip-address:comm-val | reg-ex1&reg-ex2 | ip-address&regex2 | 2byte-asnumber:ext-comm-val |4byte-asnumber:comm-val}
2byte-asnumber 0..65535
7210 SAS M, X OS Routing Protocols Guide
Page 401
Route Policy Options
comm-val
0..65535
reg-ex
72 chars max
type
target, origin
ip-address
a.b.c.d
ext-comm-val
0..4294967295
4byte-asnumber 0..4294967295
reg-ex1
63 chars max
reg-ex2
63 chars max
well-known-comm null, no-export,no-export-subconfed, no-advertise
A community ID can be specified in different forms:
• as-num:comm.-value — The as-num is the Autonomous System Number (ASN)
Values
as-num:
comm-value:
1 — 65535
0 — 65535
• type {target | origin} :as-num:comm.-value – The keywords target or origin denote the community as
an extended community of type route target or route origin respectively. The as-num and comm.-value
allow the same values as described above for regular community values.
• reg-ex1 reg-ex2— A regular expression string. Allowed values are any string up to 63 characters long
composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces,
etc.), the entire string must be enclosed within double quotes.
• well-known-comm — keywords null, no-export, no-export-subconfed, no-advertise
policy-options
Syntax
Context
Description
[no] policy-options
config>router
This command enables the context to configure route policies. Route policies are applied to the routing protocol.
The no form of the command deletes the route policy configuration.
Default
none
triggered-policy
Syntax
Context
Description
[no] triggered-policy
config>router
This command triggers route policy re-evaluation.
By default, when a change is made to a policy in the config router policy options context and then
committed, the change is effective immediately. There may be circumstances when the changes should or
must be delayed; for example, if a policy change is implemented that would effect every BGP peer on a 7210
Page 402
7210 SAS M, X OS Routing Protocols Guide
Route Policies
SAS router, the consequences could be dramatic. It is more effective to control changes on a peer by peer
basis.
If the triggered-policy command is enabled, and a given peer is established, and you want the peer to
remain up, then, in order for a change to a route policy to take effect, a clear command with the soft or softinbound option must be used. In other words, when a triggered-policy is enabled, any routine policy change
or policy assignment change within the protocol will not take effect until the protocol is reset or a clear command is issued to re-evaluate route policies; for example, clear router bgp neighbor x.x.x.x soft. This
keeps the peer up and the change made to a route policy is applied only to that peer, or group of peers.
Default
Non-dynamic route policy is disabled.
7210 SAS M, X OS Routing Protocols Guide
Page 403
Route Policy Damping Commands
Route Policy Damping Commands
damping
Syntax
Context
Description
[no] damping name
config>router>policy-options
This command creates a context to configure a route damping profile to use in route policy entries.
The no form of the command deletes the named route damping profile.
Default
Parameters
No damping profiles are defined.
name — The damping profile name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes.
half-life
Syntax
Context
Description
half-life minutes
no half-life
config>router>policy-options>damping
This command configures the half-life parameter for the route damping profile.
The half life value is the time, expressed in minutes, required for a route to remain stable in order for the Figure of Merit (FoM) value to be reduced by one half; for example, if the half life value is 6 (minutes) and the
route remains stable for 6 minutes, then the new FoM value is 3 (minutes). After another 3 minutes pass and
the route remains stable, the new FoM value is 1.5 (minutes).
When the FoM value falls below the reuse threshold, the route is once again considered valid and can be
reused or included in route advertisements.
The no form of the command removes the half life parameter from the damping profile.
Default
Parameters
No half life value is specified. The half life value must be explicitly configured.
minutes — The half life in minutes expressed as a decimal integer.
Values
Page 404
1 — 45
7210 SAS M, X OS Routing Protocols Guide
Route Policies
max-suppress
Syntax
Context
Description
max-suppress minutes
no max-suppress
config>router>policy-options>damping
This command configures the maximum suppression parameter for the route damping profile.
This value indicates the maximum time, expressed in minutes, that a route can remain suppressed.
The no form of the command removes the maximum suppression parameter from the damping profile.
Default
Parameters
No maximum suppression time is configured.
minutes — The maximum suppression time, in minutes, expressed as a decimal integer.
Values
1 — 720
reuse
Syntax
Context
Description
reuse integer
no reuse
config>router>policy-options>damping
This command configures the reuse parameter for the route damping profile.
When the Figure of Merit (FoM) value falls below the reuse threshold, the route is once again considered
valid and can be reused or included in route advertisements.
The no form of the command removes the reuse parameter from the damping profile.
Default
Parameters
No reuse parameter is configured.
integer — The reuse value expressed as a decimal integer.
Values
1 — 20000
suppress
Syntax
Context
Description
suppress integer
no suppress
config>router>policy-options>damping
This command configures the suppression parameter for the route policy damping profile.
A route is suppressed when it has flapped frequently enough to increase the Figure of Merit (FoM) value to
exceed the suppress threshold limit. When the FoM value exceeds the suppress threshold limit, the route is
removed from the route table or inclusion in advertisements.
The no form of the command removes the suppress parameter from the damping profile.
7210 SAS M, X OS Routing Protocols Guide
Page 405
Route Policy Damping Commands
Default
Parameters
No suppress parameter is configured.
integer — The suppress value expressed as a decimal integer.
Values
Page 406
1 — 20000
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Route Policy Prefix Commands
prefix-list
Syntax
Context
Description
[no] prefix-list name
config>router>policy-options
This command creates a context to configure a prefix list to use in route policy entries.
The no form of the command deletes the named prefix list.
Default
Parameters
none
name — The prefix list name. Allowed values are any string up to 32 characters long composed of printable,
7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must
be enclosed within double quotes.
prefix
Syntax
Context
Description
[no] prefix [ipv-prefix/prefix-length] [exact | longer | through length | prefix-length-range
length1-length2]
no prefix [ipv-prefix/prefix-length] [exact | longer | through length | prefix-length-range
length1-length2]
config>router>policy-options>prefix-list
This command creates a prefix entry in the route policy prefix list.
The no form of the command deletes the prefix entry from the prefix list.
Parameters
ip-prefix — The IP prefix for prefix list entry in dotted decimal notation.
Values
ipv4-prefix:
a.b.c.d (host bits must be 0)
ipv4-prefix-length:
0 — 32
ipv6-prefix - x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x - [0..FFFF]H
d - [0..255]D
ipv6-prefix-le - [0..128]
<exact|longer|thro*> : keyword
<length>
: [0..128] (prefix-length <= length)
<length1-length2> : length1/length - [0..128] (prefix-length <= length1 <=length2)
exact — Specifies the prefix list entry only matches the route with the specified ip-prefix and prefix mask
(length) values.
longer — Specifies the prefix list entry matches any route that matches the specified ip-prefix and prefix
mask length values greater than the specified mask.
7210 SAS M, X OS Routing Protocols Guide
Page 407
Route Policy Prefix Commands
through length — Specifies the prefix list entry matches any route that matches the specified ip-prefix and
has a prefix length between the specified length values inclusive.
Values
0 — 32
prefix-length-range length1 - length2 — Specifies a route must match the most significant bits and have a
prefix length with the given range. The range is inclusive of start and end values.
Values
Page 408
0 — 32, length2 > length1
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Route Policy Entry Match Commands
entry
Syntax
Context
Description
entry entry-id
no entry
config>router>policy-options>policy-statement
This command creates the context to edit route policy entries within the route policy statement.
Multiple entries can be created using unique entries. The 7210 SAS OSexits the filter when the first match is
found and executes the action specified. For this reason, entries must be sequenced correctly from most to
least explicit.
An entry does not require matching criteria defined (in which case, everything matches) but must have at
least define an action in order to be considered complete. Entries without an action are considered incomplete and will be rendered inactive.
The no form of the command removes the specified entry from the route policy statement.
Default
Parameters
none
entry-id — The entry ID expressed as a decimal integer. An entry-id uniquely identifies match criteria and
the corresponding action. It is recommended that multiple entries be given entry-ids in staggered increments. This allows users to insert a new entry in an existing policy without requiring renumbering of all
the existing entries.
Values
1 — 4294967295
from
Syntax
Context
Description
[no] from
config>router>policy-options>policy-statement>entry
This command creates the context to configure policy match criteria based on a route’s source or the protocol from which the route is received.
If no condition is specified, all route sources are considered to match.
The no form of the command deletes the source match criteria for the route policy statement entry.
7210 SAS M, X OS Routing Protocols Guide
Page 409
Route Policy Entry Match Commands
family
Syntax
Context
family [ipv4] [vpn-ipv4] [l2-vpn]
no family
config>router>policy-options>policy-statement>entry>from
Description
This command specifies address families as matching conditions.
Parameters
ipv4 — Specifies IPv4 routing information.
vpn-ipv4 — Specifies IPv4 VPN routing information.
l2-vpn — Exchanges Layer 2 VPN information.
area
Syntax
Context
Description
area area-id
no area
config>router>policy-options>policy-statement>entry>from
This command configures an OSPF area as a route policy match criterion.
This match criterion is only used in export policies.
All OSPF routes (internal and external) are matched using this criterion if the best path for the route is by the
specified area.
The no form of the command removes the OSPF area match criterion.
Default
Parameters
none
area-id — The OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
Values
0.0.0.0 — 255.255.255.255 (dotted decimal), 0 — 4294967295 (decimal)
community
Syntax
Context
Description
community name
no community
config>router>policy-options>policy-statement>entry>from
This command configures a community list as a match criterion for the route policy entry.
If no community list is specified, any community is considered a match.
The no form of the command removes the community list match criterion.
Default
Page 410
no community — Matches any community.
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Parameters
name — The community list name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes.
The name specified must already be defined.
external
Syntax
Context
Description
Default
[no] external
config>router>policy-options>policy-statement>entry>from
This command specifies the external route matching criteria for the entry.
no external
family
Syntax
Context
family [ipv4] [vpn-ipv4] [l2-vpn]
no family
config>router>policy-options>policy-statement>entry>from
Description
This command specifies address families as matching conditions.
Parameters
ipv4 — Specifies IPv4 routing information.
vpn-ipv4 — Specifies IPv4 VPN routing information.
l2-vpn — Exchanges Layer 2 VPN information.
group-address
Syntax
Context
Description
group-address prefix-list-name
no group-address
config>router>policy-options>policy-statement>entry>from
This command specifies the multicast group-address prefix list containing multicast group-addresses that are
imbedded in the join or prune packet as a filter criterion. The prefix list must be configured prior to entering
this command. Prefix lists are configured in the config>router>policy-options>prefix-list context.
The no form of the command removes the criterion from the configuration.
Default
Parameters
no group-address
prefix-list-name — The prefix-list name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes.
7210 SAS M, X OS Routing Protocols Guide
Page 411
Route Policy Entry Match Commands
The prefix-list-name is defined in the config>router>policy-options>prefix-list context.
host-ip
Syntax
Context
Description
Default
Parameters
host-ip prefix-list-name
config>router>policy-options>policy-statement>entry>from
This command specifies a prefix list host IP address as a match criterion for the route policy-statement entry.
no host-ip
prefix-list-name — The prefix-list name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes.
The prefix-list-name is defined in the config>router>policy-options>prefix-list context.
interface
Syntax
Context
Description
interface interface-name
no interface
config>router>policy-options>policy-statement>entry>from
This command specifies the router interface, specified either by name or address, as a filter criterion.
The no form of the command removes the criterion from the configuration.
Default
Parameters
no interface
ip-int-name — Specify the name of the interface as a match criterion for this entry. If the string contains
special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
level
Syntax
Context
Description
Default
Parameters
Page 412
level {1 | 2}
no level
config>router>policy-options>policy-statement>entry>from
config>router>policy-options>policy-statement>entry>to
This command specifies the ISIS route level as a match criterion for the entry.
no level
1 | 2 — Matches the IS-IS route learned from level 1 or level 2.
7210 SAS M, X OS Routing Protocols Guide
Route Policies
neighbor
Syntax
Context
Description
neighbor {ip-address | prefix-list name}
no neighbor
config>router>policy-options>policy-statement>entry>to
config>router>policy-options>policy-statement>entry>from
This command specifies the neighbor address as found in the source address of the actual join and prune
message as a filter criterion. If no neighbor is specified, any neighbor is considered a match.
The no form of the of the command removes the neighbor IP match criterion from the configuration.
Default
Parameters
no neighbor — Matches any neighbor.
ip-addr — The neighbor IP address in dotted decimal notation.
Values
ipv4-address:
a.b.c.d
ipv6-address - x:x:x:x:x:x:x:x[-interface]
x:x:x:x:x:x:d.d.d.d[-interface]
x - [0..FFFF]H
d - [0..255]D
interface - 32 chars max, mandatory for link local addresses
name : [32 chars max]
prefix-list name — The prefix-list name. Allowed values are any string up to 32 characters long composed
of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the
entire string must be enclosed within double quotes.
The name specified must already be defined.
origin
Syntax
Context
Description
origin {igp | egp | incomplete | any}
no origin
config>router>policy-options>policy-statement>entry>from
This command configures a BGP origin attribute as a match criterion for a route policy statement entry.
If no origin attribute is specified, any BGP origin attribute is considered a match.
The no form of the command removes the BGP origin attribute match criterion.
Default
Parameters
no origin — Matches any BGP origin attribute
igp — Configures matching path information originating within the local AS.
egp — Configures matching path information originating in another AS.
incomplete — Configures matching path information learned by another method.
any — Specifies to ignore this criteria.
7210 SAS M, X OS Routing Protocols Guide
Page 413
Route Policy Entry Match Commands
policy-statement
Syntax
[no] policy-statement name
Context
config>router>policy-options
Description
This command creates the context to configure a route policy statement.
The policy-statement is a logical grouping of match and action criteria.
The no form of the command deletes the policy statement.
Default
Parameters
no policy-statement — No route policy statements are defined.
name — The route policy statement name. Allowed values are any string up to 32 characters long composed
of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the
entire string must be enclosed within double quotes.
prefix-list
Syntax
Context
Description
prefix-list name [name...up to 5 max]
no prefix-list
config>router>policy-options>policy-statement>entry>from
config>router>policy-options>policy-statement>entry>to
This command configures a prefix list as a match criterion for a route policy statement entry.
If no prefix list is specified, any network prefix is considered a match.
The prefix lists specify the network prefix (this includes the prefix and length) a specific policy entry
applies.
A maximum of five prefix names can be specified.
The no form of the command removes the prefix list match criterion.
Default
Parameters
Page 414
no prefix-list — Matches any network prefix.
name — The prefix list name. Allowed values are any string up to 32 characters long composed of printable,
7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must
be enclosed within double quotes.
7210 SAS M, X OS Routing Protocols Guide
Route Policies
protocol
Syntax
Context
Description
protocol {protocol} [all | instance instance]
no protocol
config>router>policy-options>policy-statement>entry>from
config>router>policy-options>policy-statement>entry>to
This command configures a routing protocol as a match criterion for a route policy statement entry. This
command is used for both import and export policies depending how it is used.
If no protocol criterion is specified, any protocol is considered a match.
The no form of the command removes the protocol match criterion.
Default
Parameters
no protocol — Matches any protocol.
protocol — The protocol name to match on.
Values
bgp|isis|ospf|bgp-vpn|ospf3|vpn-leak|ldp
instance — The OSPF or IS-IS instance.
Values
[1..31]
all — OSPF- or ISIS-only keyword.
source-address
Syntax
Context
Description
source-address ip-address
no source-address
config>router>policy-options>policy-statement>entry>from
This command specifies the source address that is embedded in the join or prune packet as a filter criterion.
The no form of the command removes the criterion from the configuration.
Default
none
Description
This command specifies a multicast data source address as a match criterion for this entry.
Parameters
ip-address — The IP prefix for the IP match criterion in dotted decimal notation.
Values
ipv4-address - a.b.c.d
ipv6-address - x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x - [0..FFFF]H
d - [0..255]D
7210 SAS M, X OS Routing Protocols Guide
Page 415
Route Policy Entry Match Commands
tag
Syntax
Context
Description
tag tag
no tag
config>router>policy-options>policy-statement>entry>from
This command adds an integer tag to the static route. These tags are then matched on to control route redistribution.
The no form of the command removes the tag field match criterion.
Default
Parameters
no tag — Matches any external LSA tag field.
tag — Matches a specific external LSA tag field.
Values
no-tag, 1 — 4294967295
to
Syntax
Context
Description
[no] to
config>router>policy-options>policy-statement>entry
This command creates the context to configure export policy match criteria based on a route’s destination or
the protocol into which the route is being advertised.
If no condition is specified, all route destinations are considered to match.
The to command context only applies to export policies. If it is used for an import policy, match criteria is
ignored.
The no form of the command deletes export match criteria for the route policy statement entry.
type
Syntax
Context
Description
type type
no type
config>router>policy-options>policy-statement>entry>from
This command configures an OSPF type metric as a match criterion in the route policy statement entry.
If no type is specified, any OSPF type is considered a match.
The no form of the command removes the OSPF type match criterion.
Parameters
1 — Matches OSPF routes with type 1 LSAs.
2 — Matches OSPF routes with type 2 LSAs.
Page 416
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Route Policy Action Commands
action
Syntax
Context
Description
action {accept | next-entry | reject}
no action
config>router>policy-options>policy-statement>entry
This command creates the context to configure actions to take for routes matching a route policy statement
entry.
This command is required and must be entered for the entry to be active.
Any route policy entry without the action command will be considered incomplete and will be inactive.
The no form of the command deletes the action context from the entry.
Default
Parameters
no action — No action is defined.
accept — Specifies routes matching the entry match criteria will be accepted and propagated.
next-entry — Specifies that the actions specified would be made to the route attributes and then policy evaluation would continue with next policy entry (if any others are specified).
reject — Specifies routes matching the entry match criteria would be rejected.
as-path
Syntax
Context
Description
as-path {add | replace} name
no as-path
config>router>policy-options>policy-statement>default-action
config>router>policy-options>policy-statement>entry>action
This command assigns a BGP AS path list to routes matching the route policy statement entry.
If no AS path list is specified, the AS path attribute is not changed.
The no form of the command disables the AS path list editing action from the route policy entry.
Default
Parameters
no as-path — The AS path attribute is not changed.
add — Specifies that the AS path list is to be prepended to an existing AS list.
replace — Specifies AS path list replaces any existing as path attribute.
name — The AS path list name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string
must be enclosed within double quotes.
7210 SAS M, X OS Routing Protocols Guide
Page 417
Route Policy Action Commands
The name specified must already be defined.
as-path-prepend
Syntax
Context
Description
as-path-prepend as-num [repeat]
no as-path-prepend
config>router>policy-options>policy-statement>default-action
config>router>policy-options>policy-statement>entry>action
The command prepends a BGP AS number once or numerous times to the AS path attribute of routes matching the route policy statement entry.
If an AS number is not configured, the AS path is not changed.
If the optional number is specified, then the AS number is prepended as many times as indicated by the number.
The no form of the command disables the AS path prepend action from the route policy entry.
Default
Parameters
no as-path-prepend — no AS number prepending configured.
as-num — The AS number to prepend expressed as a decimal integer.
Values
1 — 4294967295
repeat — The number of times to prepend the specified AS number expressed as a decimal integer.
Values
1 — 50
community
Syntax
Context
Description
community {{add name [remove name]} | {remove name [add name]} | {replace name}}
no community
config>router>policy-options>policy-statement>default-action
config>router>policy-options>policy-statement>entry>action
This command adds or removes a BGP community list to or from routes matching the route policy statement
entry.
If no community list is specified, the community path attribute is not changed.
The community list changes the community path attribute according to the add and remove keywords.
The no form of the command disables the action to edit the community path attribute for the route policy
entry.
Default
Parameters
no community — The community path attribute is not changed.
add — The specified community list is added to any existing list of communities.
remove — The specified community list is removed from the existing list of communities.
replace — The specified community list replaces any existing community attribute.
Page 418
7210 SAS M, X OS Routing Protocols Guide
Route Policies
name — The community list name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes.
damping
Syntax
Context
Description
damping {name | none}
no damping
config>router>policy-options>policy-statement >default-action
config>router>policy-options>policy-statement>entry>action
This command configures a damping profile used for routes matching the route policy statement entry.
If no damping criteria is specified, the default damping profile is used.
The no form of the command removes the damping profile associated with the route policy entry.
Default
Parameters
no damping — Use the default damping profile.
name — The damping profile name. Allowed values are any string up to 32 characters long composed of
printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes.
The name specified must already be defined.
none — Disables route damping for the route policy.
default-action
Syntax
Context
Description
default-action {accept | next-entry | reject}
no default-action
config>router>policy-options>policy-statement
This command enables the context to configure actions for routes that do not match any route policy statement entries when the accept parameter is specified.
The default action clause can be set to all available action states including: accept, reject, next-entry and
next-policy. If the action states accept or reject then the policy evaluation terminates and the appropriate
result is returned.
If a default action is defined and no match(es) occurred with the entries in the policy then the default action
clause is used.
If a default action is defined and one or more matches occurred with the entries of the policy then the default
action is not used.
The no form of the command deletes the default-action context for the policy statement.
Default
Parameters
no default-action — No default action is specified.
accept — Specifies routes matching the entry match criteria will be accepted and propagated.
7210 SAS M, X OS Routing Protocols Guide
Page 419
Route Policy Action Commands
next-entry — Specifies that the actions specified would be made to the route attributes and then policy evaluation would continue with next policy entry (if any others are specified).
reject — Specifies routes matching the entry match criteria would be rejected.a
local-preference
Syntax
Context
Description
local-preference preference
no local-preference
config>router>policy-options>policy-statement>default-action
config>router>policy-options>policy-statement>entry
This command assigns a BGP local preference to routes matching a route policy statement entry.
If no local preference is specified, the BGP configured local preference is used.
The no form of the command disables assigning a local preference in the route policy entry.
Default
Parameters
No local-preference — BGP default preference is assigned.
preference — The local preference expressed as a decimal integer.
Values
0 — 4294967295
metric
Syntax
Context
Description
metric {add | subtract | set} metric
no metric
config>router>policy-options>policy-statement>default-action
config>router>policy-options>policy-statement>entry>action
This command assigns a metric to routes matching the policy statement entry.
If no metric is specified, the configured metric is used. If neither is defined, no metric will be advertised.
The value assigned for the metric by the route policy is controlled by the required keywords.
The no form of the command disables assigning a metric in the route policy entry.
Default
Parameters
no metric — Uses the configured metric (if defined) or do not advertise a metric.
add — Specified integer is added to any existing metric. If the result of the addition results in a number
greater than 4294967295, the value 4294967295 is used.
subtract — Specified integer is subtracted from any existing metric. If the result of the subtraction results in
a number less than 0, the value of 0 is used.
set — Specified integer replaces any existing metric.
metric — The metric modifier expressed as a decimal integer.
Values
Page 420
0 — 4294967295
7210 SAS M, X OS Routing Protocols Guide
Route Policies
next-hop
Syntax
Context
Description
next-hop ip-address
no next-hop
config>router>policy-options>policy-statement>default-action
config>router>policy-options>policy-statement>entry>action
This command assigns the specified next hop IP address to routes matching the policy statement entry.
If a next-hop IP address is not specified, the next-hop attribute is not changed.
The no form of the command disables assigning a next hop address in the route policy entry.
Default
Parameters
no next-hop — The next hop attribute is not changed.
ip-address — The next hop IP address in dotted decimal notation.
Values
ipv4-prefix:
ipv4-prefix-length:
a.b.c.d (host bits must be 0)
0 — 32
next-hop-self
Syntax
Context
Description
[no] next-hop-self
config>router>policy-options>policy-statement name>default-action
config>router>policy-options>policy-statement>entry>action
This command advertises a next hop IP address belonging to this router even if a third-party next hop is
available to routes matching the policy statement entry.
The no form of the command disables advertising the next-hop-self option for the route policy entry.
Default
no next-hop-self — The next hop IP address is not changed.
origin
Syntax
Context
Description
origin {igp | egp | incomplete}
no origin
config>router>policy-options>policy-statement name>default-action
config>router>policy-options>policy-statement>entry>action
This command sets the BGP origin assigned to routes exported into BGP.
If the routes are exported into protocols other than BGP, this option is ignored.
The no form of the command disables setting the BGP origin for the route policy entry.
Default
Parameters
no origin
igp — Sets the path information as originating within the local AS.
7210 SAS M, X OS Routing Protocols Guide
Page 421
Route Policy Action Commands
egp — Sets the path information as originating in another AS.
incomplete — Sets the path information as learned by some other means.
preference
Syntax
Context
Description
preference preference
no preference
config>router>policy-options>policy-statement name>default-action
config>router>policy-options>policy-statement>entry>action>action
This command assigns a route preference to routes matching the route policy statement entry.
If no preference is specified, the default Route Table Manager (RTM) preference for the protocol is used.
The no form of the command disables setting an RTM preference in the route policy entry.
Default
Parameters
no preference — No route preference is assigned by the policy entry. The protocol default preference is
used.
preference — The route preference expressed as a decimal integer.
Values
1 — 255 (0 represents unset - MIB only)
tag
Syntax
Context
Description
tag tag
no tag
config>router>policy-options>policy-statement>default-action
config>router>policy-options>policy-statement>entry>action
This command assigns an OSPF tag to routes matching the entry. The tag value is used to apply a tag to a
route for either an OSPF or RIP route. A hexadecimal value of 4 octets can be entered.
For OSPF, all four octets can be used.
For RIP, only the two most significant octets are used if more than two octets are configured.
The no form of the command removes the tag.
Default
Parameters
no tag
tag — Assigns an OSPF, RIP or ISIS tag to routes matching the entry.
Values
Page 422
Accepts decimal or hex formats:
OSPF and ISIS:
[0x0..0xFFFFFFFF]H
RIP:
[0x0..0xFFFF]H
7210 SAS M, X OS Routing Protocols Guide
Route Policies
type
Syntax
Context
Description
type {type}
no type
config>router>policy-options>policy-statement name>default-action
config>router>policy-options>policy-statement>entry>action
This command assigns an OSPF type metric to routes matching the route policy statement entry and being
exported into OSPF.
The no form of the command disables assigning an OSPF type in the route policy entry.
Default
Parameters
no type
type — Specifies the OSPF type metric.
Values
1 — Set as OSPF routes with type 1 LSAs
2 — Set as OSPF routes with type 2 LSAs.
7210 SAS M, X OS Routing Protocols Guide
Page 423
Route Policy Action Commands
Page 424
7210 SAS M, X OS Routing Protocols Guide
Route Policies
Show Commands
policy
Syntax
Context
policy [name | damping | prefix-list name |as-path name |community name | admin]
show>router
Description
This command displays configured policy statement information.
Parameters
policy name — Displays information similar to the info command for a specific policy-statement. If a name
is provided, the matching policy-statement displays.
If no statement name is specified, a list of all policies statements and descriptions display.
damping — Displays the damping profile for use in the route policy.
prefix-list name — Displays the prefix lists configured in the route policy.
as-path — Displays AS path regular expression statements used in the route policy.
community — Displays community lists used in the route policy.
admin — If the keyword admin is included, the entire policy option configuration displays, including any
un-committed configuration changes. This command is similar to the info command.
Output
Route Policy Output — The following table describes route policy output fields.
Label
Description
Policy
Displays a list of route policy names.
Description
Displays the description of each route policy.
Policies
The total number of policies configured.
Damping
Displays the damping profile name.
half-life
Displays the half-life parameter for the route damping profile.
max-suppress
Displays the maximum suppression parameter configured for the route
damping profile.
Prefix List
Displays the prefix list name and IP address/mask and whether the prefix list entry only matches (exact) the route with the specified ip-prefix
and prefix mask (length) values or values greater (longer) than the
specified mask.
AS Path Name
Displays a list of AS path names.
AS Paths
Displays the total number of AS paths configured.
Community Name
Displays a list of community names.
Communities
Displays the total number of communities configured.
7210 SAS M, X OS Routing Protocols Guide
Page 425
Show Commands
The following route policy commands are displayed with different command parameter options:
• show router policy on page 426
• show router policy admin on page 426
Sample Output
The show router policy command displays all configured route policies.
show router policy
A:ALA-1# show router policy
===============================================================================
Route Policies
===============================================================================
Policy
Description
------------------------------------------------------------------------------OSPF to OSPF
Policy Statement for 'OSPF to OSPF'
Direct And Aggregate
Policy Statement ABC
------------------------------------------------------------------------------Policies : 2
===============================================================================
A:ALA-1#
The show router policy admin command is similar to the info command which displays information about
the route policies and parameters.
show router policy admin
*A:7210-SAS>show>router# policy admin
prefix-list "abc"
prefix 10.1.1.0/24 longer
prefix 10.1.1.1/32 exact
prefix 20.1.0.0/16 prefix-length-range 16-24
exit
community "SOO" members "origin:12345:1"
community "sample" members "target:12345:10"
as-path "null" "null"
as-path "test" "1234"
as-path "prevent loop" "null"
damping "re"
reuse 100
exit
damping "max"
max-suppress 20
exit
damping "sup"
suppress 20000
exit
damping "half"
half-life 10
exit
damping "test"
exit
policy-statement "abcd"
description "Test for policy statements"
entry 1
from
area 0.0.0.0
exit
Page 426
7210 SAS M, X OS Routing Protocols Guide
Route Policies
to
protocol bgp
exit
action accept
exit
exit
entry 2
from
community "sample"
exit
to
neighbor 2.2.2.2
exit
action accept
exit
exit
entry 3
from
external
exit
to
level 2
exit
action accept
exit
exit
entry 4
from
family vpn-ipv4
exit
to
protocol bgp-vpn
exit
action accept
exit
exit
entry 5
from
protocol bgp
exit
action accept
next-hop 10.1.1.1
exit
exit
entry 6
from
protocol bgp
exit
action accept
as-path add "null"
exit
exit
entry 7
from
protocol bgp
exit
action accept
as-path replace "sample"
exit
7210 SAS M, X OS Routing Protocols Guide
Page 427
Show Commands
exit
default-action accept
exit
exit
policy-statement "test"
entry 2
from
exit
to
exit
action accept
exit
exit
default-action accept
exit
exit
*A:7210-SAS>show>router#
The show router policy name command displays information about a specific route policy.
A:ALA-1# show router policy "OSPF To OSPF"
entry 10
description "Entry For Policy Statement OSPF To OSPF"
from
protocol ospf
exit
to
protocol ospf
exit
action accept
tag 100
exit
exit
default-action reject
ALA-1#
Page 428
7210 SAS M, X OS Routing Protocols Guide
Standards and Protocol Support
Standards Compliance
IEEE 802.1ab-REV/D3 Station and
Media Access Control Connectivity
Discovery
IEEE 802.1D Bridging
IEEE 802.1p/Q VLAN Tagging
IEEE 802.1s Multiple Spanning Tree
IEEE 802.1w Rapid Spanning Tree
Protocol
IEEE 802.1X Port Based Network
Access Control
IEEE 802.1ad Provider Bridges
IEEE 802.1ah Provider Backbone
Bridges
IEEE 802.1ag Service Layer OAM
IEEE 802.3ah Ethernet in the First Mile
IEEE 802.3 10BaseT
IEEE 802.3ad Link Aggregation
IEEE 802.3ae 10Gbps Ethernet
IEEE 802.3ah Ethernet OAM
IEEE 802.3u 100BaseTX
IEEE 802.3z 1000BaseSX/LX ITU-T
Y.1731 OAM functions and
mechanisms for Ethernet based
networks draft-ietf-disman-alarmmib-04.txt IANA-IFType-MIB
IEEE8023-LAG-MIB ITU-T G.8032
Ethernet Ring Protection Switching
(version 2)
Protocol Support
BGP
RFC 1397 BGP Default Route
Advertisement
RFC 1772 Application of BGP in the
Internet
RFC 1997 BGP Communities Attribute
RFC 2385 Protection of BGP Sessions
via MD5
RFC 2439 BGP Route Flap Dampening
RFC 2547 bis BGP/MPLS VPNs draftietf-idr-rfc2858bis-09.txt.
RFC 2918 Route Refresh Capability for
BGP-4
RFC 3107 Carrying Label Information in
BGP-4
Standards and Protocols
RFC 3392 Capabilities Advertisement
with BGP4
RFC 4271 BGP-4 (previously RFC 1771)
RFC 4360 BGP Extended Communities
Attribute
RFC 4364 BGP/MPLS IP Virtual Private
Networks (VPNs)(previously RFC
2547bis BGP/MPLS VPNs)
RFC 4760 Multi-protocol Extensions for
BGP
RFC 4893 BGP Support for Four-octet
AS Number Space
CIRCUIT EMULATION
RFC 4553 Structure-Agnostic Time
Division Multiplexing (TDM) over
Packet (SAToP)
RFC 5086 Structure-Aware Time
Division Multiplexed (TDM) Circuit
Emulation Service over Packet
Switched Network (CESoPSN)
RFC 5287 Control Protocol Extensions
for the Setup of Time-Division
Multiplexing (TDM) Pseudowires in
MPLS Networks
DHCP
RFC 2131 Dynamic Host Configuration
Protocol (REV)
DIFFERENTIATED SERVICES
RFC 2474 Definition of the DS Field the
IPv4 and IPv6 Headers (Rev)
RFC 2597 Assured Forwarding PHB
Group (rev3260)
RFC 2598 An Expedited Forwarding
PHB
RFC 2697 A Single Rate Three Color
Marker
RFC 2698 A Two Rate Three Color
Marker
RFC 4115 A Differentiated Service TwoRate, Three-Color Marker with
Efficient Handling of in-Profile
Traffic
IPv6
RFC 2460 Internet Protocol, Version 6
(IPv6) Specification
RFC 2461 Neighbor Discovery for IPv6
RFC 2462 IPv6 Stateless Address Auto
configuration
RFC 2463 Internet Control Message
Protocol (ICMPv6) for the Internet
Protocol Version 6 Specification
RFC 2464 Transmission of IPv6 Packets
over Ethernet Networks
RFC 2740 OSPF for IPv6
RFC 3587 IPv6 Global Unicast Address
Format
RFC 4007 IPv6 Scoped Address
Architecture
RFC 4193 Unique Local IPv6 Unicast
Addresses
RFC 4291 IPv6 Addressing Architecture
RFC 4552 Authentication/Confidentiality
for OSPFv3
RFC 5095 Deprecation of Type 0 Routing
Headers in IPv6
IS-IS
RFC 1142 OSI IS-IS Intra-domain
Routing Protocol (ISO 10589)
RFC 1195 Use of OSI IS-IS for routing in
TCP/IP & dual environments
RFC 2763 Dynamic Hostname Exchange
for IS-IS
RFC 2966 Domain-wide Prefix
Distribution with Two-Level IS-IS
RFC 2973 IS-IS Mesh Groups
RFC 3373 Three-Way Handshake for
Intermediate System to Intermediate
System (IS-IS) Point-to-Point
Adjacencies
RFC 3567 Intermediate System to
Intermediate System (ISIS)
Cryptographic Authentication
RFC 3719 Recommendations for
Interoperable Networks using IS-IS
RFC 3784 Intermediate System to
Intermediate System (IS-IS)
Extensions for Traffic Engineering
(TE)
RFC 3787 Recommendations for
Interoperable IP Networks
RFC 3847 Restart Signaling for IS-IS –
GR helper
MPLS - LDP
RFC 3036 LDP Specification
Page 429
Standards and Protocols
RFC 3037 LDP Applicability
RFC 3478 Graceful Restart Mechanism
for LDP — GR helper
RFC 5283 LDP extension for Inter-Area
LSP
RFC 5443 LDP IGP Synchronization
MPLS - General
RFC 3031 MPLS Architecture
RFC 3032 MPLS Label Stack Encoding
RFC 4379 Detecting Multi-Protocol
Label Switched (MPLS) Data Plane
Failures
RFC 4182 Removing a Restriction on the
use of MPLS Explicit NULL
Multicast
RFC 1112 Host Extensions for IP
Multicasting (Snooping)
RFC 2236 Internet Group Management
Protocol, (Snooping)
RFC 3376 Internet Group Management
Protocol, Version 3 (Snooping) [
Only in 7210 SAS-M access-uplink
mode ]
NETWORK MANAGEMENT
ITU-T X.721: Information technologyOSI-Structure of Management
Information
ITU-T X.734: Information technologyOSI-Systems Management: Event
Report Management Function
M.3100/3120 Equipment and Connection
Models
TMF 509/613 Network Connectivity
Model
RFC 1157 SNMPv1
RFC 1215 A Convention for Defining
Traps for use with the SNMP
RFC 1907 SNMPv2-MIB
RFC 2011 IP-MIB
RFC 2012 TCP-MIB
RFC 2013 UDP-MIB
RFC 2096 IP-FORWARD-MIB
RFC 2138 RADIUS
RFC 2206 RSVP-MIB
RFC 2571 SNMP-FRAMEWORKMIB
RFC 2572 SNMP-MPD-MIB
RFC 2573 SNMP-TARGET-&NOTIFICATION-MIB
RFC 2574 SNMP-USERBASEDSMMIB
Page 430
RFC 2575 SNMP-VIEW-BASEDACMMIB
RFC 2576 SNMP-COMMUNITY-MIB
RFC 2665 EtherLike-MIB
RFC 2819 RMON-MIB
RFC 2863 IF-MIB
RFC 2864 INVERTED-STACK-MIB
RFC 3014 NOTIFICATION-LOGMIB
RFC 3164 Syslog
RFC 3273 HCRMON-MI
RFC 3411 An Architecture for
Describing Simple Network
Management Protocol (SNMP)
Management Frameworks
RFC 3412 - Message Processing and
Dispatching for the Simple Network
Management Protocol (SNMP)
RFC 3413 - Simple Network
Management Protocol (SNMP)
Applications
RFC 3414 - User-based Security Model
(USM) for version 3 of the Simple
Network Management Protocol
(SNMPv3)
RFC 3418 - SNMP MIB
draft-ietf-mpls-lsr-mib-06.txt
draft-ietf-mpls-te-mib-04.txt
draft-ietf-mpls-ldp-mib-07.txt
OSPF
RFC 1765 OSPF Database Overflow
RFC 2328 OSPF Version 2
RFC 2370 Opaque LSA Support
RFC 3101 OSPF NSSA Option
RFC 3137 OSPF Stub Router
Advertisement
RFC 3623 Graceful OSPF Restart – GR
helper
RFC 3630 Traffic Engineering (TE)
Extensions to OSPF Version 2
MPLS - RSVP-TE
RFC 2430 A Provider Architecture
DiffServ & TE
RFC 2702 Requirements for Traffic
Engineering over MPLS
RFC2747 RSVP Cryptographic
Authentication
RFC3097 RSVP Cryptographic
Authentication
RFC 3209 Extensions to RSVP for
Tunnels
RFC 4090 Fast reroute Extensions to
RSVP-TE for LSP Tunnels
RFC 5817 Graceful Shutdown in MPLS
and GMPLS Traffic Engineering
Networks
PSEUDO-WIRE
RFC 3985 Pseudo Wire Emulation Edgeto-Edge (PWE3)
RFC 4385 Pseudo Wire Emulation Edgeto-Edge (PWE3) Control Word for
Use over an MPLS PSN
RFC 3916 Requirements for PseudoWire Emulation Edge-to-Edge
(PWE3)
RFC 4448 Encapsulation Methods for
Transport of Ethernet over MPLS
Networks (draft-ietf-pwe3-ethernetencap-11.txt)
RFC 4446 IANA Allocations for PWE3
RFC 4447 Pseudowire Setup and
Maintenance Using LDP (draft-ietfpwe3-control-protocol-17.txt)
RFC 5085, Pseudowire Virtual Circuit
Connectivity Verification (VCCV):
A Control Channel for Pseudowires
RFC 5659 An Architecture for MultiSegment Pseudowire Emulation
Edge-to-Edge
RFC6073, Segmented Pseudowire (draftietf-pwe3-segmented-pw-18.txt)
draft-ietf-l2vpn-vpws-iw-oam-02.txt
OAM Procedures for VPWS
Interworking
draft-ietf-pwe3-oam-msg-map-14-txt,
Pseudowire (PW) OAM Message
Mapping
Pseudowire Preferential Forwarding
Status bit definition
draft-pwe3-redundancy-02.txt
Pseudowire (PW) Redundancy
RADIUS
RFC 2865 Remote Authentication Dial In
User Service
RFC 2866 RADIUS Accounting
SSH
draft-ietf-secsh-architecture.txt SSH
Protocol Architecture
draft-ietf-secsh-userauth.txt SSH
Authentication Protocol
Standards and Protocols
Standards and Protocols
draft-ietf-secsh-transport.txt SSH
Transport Layer Protocol
draft-ietf-secsh-connection.txt SSH
Connection Protocol
draft-ietf-secsh- newmodes.txt SSH
Transport Layer Encryption Modes
TACACS+
draft-grant-tacacs-02.txt
TCP/IP
RFC 768 UDP
RFC 1350 The TFTP Protocol
RFC 791 IP
RFC 792 ICMP
RFC 793 TCP
RFC 826 ARP
RFC 854 Telnet
RFC 1519 CIDR
RFC 1812 Requirements for IPv4
Routers
RFC 2347 TFTP option Extension
RFC 2328 TFTP Blocksize Option
RFC 2349 TFTP Timeout Interval and
Transfer Size option
Timing
ITU-T G.781 Telecommunication
Standardization Section of ITU,
Synchronization layer functions,
issued 09/2008
ITU-T G.813 Telecommunication
Standardization Section of ITU,
Timing characteristics of SDH
equipment slave clocks (SEC),
issued 03/2003.
GR-1244-CORE Clocks for the
Synchronized Network: Common
Generic Criteria, Issue 3,May 2005
ITU-T G.8261 Telecommunication
Standardization Section of ITU,
Timing and synchronization aspects
in packet networks, issued 04/2008.
ITU-T G.8262 Telecommunication
Standardization Section of ITU,
Timing characteristics of
synchronous Ethernet equipment
slave clock (EEC), issued 08/2007.
ITU-T G.8264 Telecommunication
Standardization Section of ITU,
Distribution of timing information
through packet networks, issued 10/
2008.
Standards and Protocols
VPLS
RFC 4762 Virtual Private LAN Services
Using LDP (previously draft-ietfl2vpn-vpls-ldp-08.txt)
VRRP
RFC 2787 Definitions of Managed
Objects for the Virtual Router
Redundancy Protocol
RFC 3768 Virtual Router Redundancy
Protocol
TIMETRA-SECURITY-MIB.mib
TIMETRA-SERV-MIB.mib
TIMETRA-SYSTEM-MIB.mib
TIMETRA-TC-MIB.mib
TIMETRA-ISIS-MIB.mib
TIMETRA-ROUTE-POLICY-MIB.mib
TIMETRA-MPLS-MIB.mib
TIMETRA-RSVP-MIB.mib
TIMETRA-LDP-MIB.mib
TIMETRA-VRRP-MIB.mib
TIMETRA-VRTR-MIB.mib
Proprietary MIBs
ALCATEL-IGMP-SNOOPINGMIB.mib
TIMETRA-CAPABILITY-7210-SAS-MV5v0.mib
(7210 SAS-M Only)
TIMETRA-CAPABILITY-7210-SAS-XV5v0.mib (7210 SAS-X Only)
TIMETRA-CHASSIS-MIB.mib
TIMETRA-CLEAR-MIB.mib
TIMETRA-DOT3-OAM-MIB.mib
TIMETRA-FILTER-MIB.mib
TIMETRA-GLOBAL-MIB.mib
TIMETRA-IEEE8021-CFM-MIB.mib
TIMETRA-LAG-MIB.mib
TIMETRA-LOG-MIB.mib
TIMETRA-MIRROR-MIB.mib
TIMETRA-NTP-MIB.mib
TIMETRA-OAM-TEST-MIB.mib
TIMETRA-PORT-MIB.mib
TIMETRA-QOS-MIB.mib
TIMETRA-SAS-ALARM-INPUTMIB.mib
TIMETRA-SAS-FILTER-MIB.mib
TIMETRA-SAS-IEEE8021-CFMMIB.mib
TIMETRA-SAS-IEEE8021-PAEMIB.mib
TIMETRA-SAS-GLOBAL-MIB.mib
TIMETRA-SAS-LOG-MIB.mib.mib
TIMETRA-SAS-MIRROR-MIB.mib
TIMETRA-SAS-MPOINT-MGMTMIB.mib (Only for 7210 SAS-X)
TIMETRA-SAS-PORT-MIB.mib
TIMETRA-SAS-QOS-MIB.mib
TIMETRA-SAS-SDP-MIB.mib
TIMETRA-SAS-SYSTEM-MIB.mib
TIMETRA-SAS-SERV-MIB.mib
TIMETRA-SAS-VRTR-MIB.mib
TIMETRA-SCHEDULER-MIB.mib
Page 431
Standards and Protocols
Page 432
Standards and Protocols
Index
B
AS areas 21
backbone 21
NSSA 23
stub 22
authentication 26
IP subnets 28
LSAs 26
metrics 26
neighbors and adjacencies 25
virtual links 24
configuring 33
area interface 40, 41
basic 33
command reference 55
designated router 45
management tasks 51
NSSA 38
OSPF area 36
overview 32
route preferences 48, 47, 33
stub area 37
virtual link 39
BGP
overview 242
group configuration and peers 244
hierarchical levels 245
interactions and dependencies 254
message types 242
route damping 257, 245, 250
configuring 266
autonomous system 269
basic 266
BGP parameters 271
group 273
neighbor 274
command reference 281
overview 264
router ID 270
management tasks 275
I
IS-IS
overview 152
ISO network addressing 156
PDU configuration 158
routing 153
terminology 155
configuring
area address attributes 166
basic 169
command reference 191
enabling IS-IS 172
global parameters 175
interface level capabilities 167, 176
ISO area addresses 174
level parameters 172
management tasks 181
overview 166
router levels 166
R
Route policies
overview 358
damping 381, 377
policy evaluation 378, 359
regular expressions 363
when to use 371
configuring
beginning 384
command reference 395, 385
damping 388, 386
entry 387
management tasks 390
overview 376
prefix list 389
O
OSPF
overview 20
7210 SAS M, X OS Routing Protocols Guide
Page 433
Page 434
7210 SAS M, X OS Routing Protocols Guide