Configuring Juniper Networks Routers

Module 3: Protocol-Independent
Routing Properties

Copyright © 2006, Juniper Networks, Inc. CJNR-M-7.a.7.6.1

 Module Objectives
 After successfully completing this module, you will be
able to:
– Create static routes
– Create aggregate routes
– Create generated routes
– Describe JUNOS software routing tables
– Describe the JUNOS software route selection process
– Explain load-balancing options

Copyright © 2006, Juniper Networks, Inc.

 Protocol-Independent Routing
 Where we are going…
– Static, aggregate, generated, and martian routes
– Routing tables and route preferences
– Configure routing protocol process system logging
– Load balancing

Copyright © 2006, Juniper Networks, Inc.

 Static Routes
 Manually configured routes added to the routing table
 Once active, routes remain in the routing table until deleted
 Route configured at the routing-options hierarchy level

[edit]
routing-options {
static {
defaults {
static-options;
}
route destination-prefix{
next-hop;
static-options;
}

Copyright © 2006, Juniper Networks, Inc.

 Static Route Configuration
 Static routes require the configuration of a next hop
– Valid options are IP address, discard, and reject
 Defaults section affects all static routes
 Qualified next-hop option allows independent
preference for static routes to the same destination
 Recursive static routes allow you to configure a route
to an IP address that is not connected directly to the
router
routing-options {
static {
defaults {
preference 250;
}
route 192.168.20.0/24 next-hop 10.0.0.1;
route 192.168.21.0/24 discard;
route 192.168.22.0/24 reject;
}
}
Copyright © 2006, Juniper Networks, Inc.
 Aggregate Routes
 Route prefixes in the network can be combined into a
single entry in the routing table
 Aggregate routes become active once one or more
contributing routes are active
 You configure aggregate routes at the routing-
options hierarchy level
[edit]
routing-options {
aggregate {
defaults {
aggregate-options;
}
route destination-prefix {
policy policy-name;
aggregate-options;
}
Copyright © 2006, Juniper Networks, Inc.
 Aggregate Route Configuration
 The default next hop for an aggregate is reject
– discard is also a valid option
 Defaults section affects all aggregate routes

routing-options {
aggregate {
defaults {
community 1:888;
}
route 192.168.16.0/21;
route 192.168.24.0/21 discard;
}
}

Copyright © 2006, Juniper Networks, Inc.

 Generated Routes
 Similar to aggregate routes
– Become active once one or more contributing routes are
active
 Often used as the route of last resort or floating static
 Configured at the routing-options hierarchy level

[edit]
routing-options {
generate {
defaults {
generate-options;
}
route destination-prefix {
policy policy-name;
generate-options;
}

Copyright © 2006, Juniper Networks, Inc.

 Generated Route Configuration
 The default next hop is the next hop of the primary
contributing route
– Discard is also a valid option
 Defaults section affects all generated routes

routing-options {
generate {
defaults {
metric 5;
}
route 172.16.64.0/20;
route 172.16.80.0/20 discard;
}
}

Copyright © 2006, Juniper Networks, Inc.

 Contributing Routes
 All routes that fall within a prefix defined for an aggregate or
generated route
 Only active routes with a valid forwarding next hop can
contribute to a generated route
 A given route can only contribute to one summary
 View contributing routes with show route protocol
aggregate extensive command
lab@London> show route protocol aggregate detail
inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden) A generated route
172.16.64.0/20 (1 entry, 1 announced)
*Aggregate Preference: 130
Next hop: 10.0.22.1 via so-0/1/1.0, selected
State: <Active Int Ext>
Age: 8:37
Task: Aggregate
Announcement bits (1): 0-KRT
AS path: I The contributing route
Flags: Generate Depth: 0 Active
Contributing Routes (1):
172.16.65.0/24 proto Static
__juniper_private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

Copyright © 2006, Juniper Networks, Inc.

 Generated Route Example
 ISP wants to send a default route to its customer
– What’s the best way to get 0/0 to appear on the edge router?

Core prefix

10.10/1
6

10.10/1 Edge router

6
(only generates 0/0 if
10.10/16 is present)

Tier 1/2 ISP

0/0

Regional ISP

Copyright © 2006, Juniper Networks, Inc.

 Martian Addresses
 Address prefixes for which the routers ignore all
associated routing information
 Martians are not installed into the routing table
 In JUNOS software, the default martian addresses are:
– 0.0.0.0/8 orlonger
– 127.0.0.0/8 orlonger
– 128.0.0.0/16 orlonger
– 191.255.0.0/16 orlonger
– 192.0.0.0/24 orlonger
– 223.255.255.0/24 orlonger
– 240.0.0.0/4 orlonger

Copyright © 2006, Juniper Networks, Inc.

 Adding Martian Addresses
 Additional prefixes can be added to the martian list
 Configured at the routing-options hierarchy level

routing-options {
martians {
destination-prefix match-type;
}
}

[edit]
routing-options {
martians {
10.0.0.0/8 orlonger;
172.16.0.0/12 orlonger;
192.168.0.0/16 orlonger;
}
}

Copyright © 2006, Juniper Networks, Inc.

 Routing Tables
 Juniper Networks M-series and T-series platforms have
eight predefined routing tables:
– inet.0 for unicast routes
– inet.1 for the multicast forwarding cache
– inet.2 for MBGP routes to provide reverse path forwarding
(RPF) checks
– inet.3 for MPLS path information
– inet6.0 for IPv6 routes
– mpls.0 for MPLS next hops
– __juniper_private1__.inet.0
– __juniper_private1__.inet6.0

Copyright © 2006, Juniper Networks, Inc.

 Routing Table Protocols
 Within JUNOS software, many sources of routing
information exist
– Referred to as protocols in the routing table
 Default protocols:
– Direct
– Local
– Static
– RSVP
– LDP
– OSPF
– IS-IS
– RIP
– Aggregate
– BGP

Copyright © 2006, Juniper Networks, Inc.

 Protocol Preference
 Each protocol has a default preference value
– Preference is a measure of desirability
 Used as a tiebreaker when the same prefix is learned through multiple
sources; protocols with a lower preference are preferred
 Selected default preference values circa release 6.0:

Direct/Local: 0 ...
Static: 5 PIM: 105
RSVP: 7 DVMRP: 110
LDP: 9 Aggregate routes: 130
OSPF internal route: 10 OSPF AS external routes: 150
IS-IS Level 1 internal route: 15 IS-IS Level 1 external route: 160
IS-IS Level 2 internal route: 18 IS-IS Level 2 external route: 165
RIP: 100 BGP: 170
RIPng: 100 MSDP: 175
...

Copyright © 2006, Juniper Networks, Inc.

 The Main Routing Table: inet.0
Sample inet.0 routing table for unicast routes:
user@host> show route

inet.0: 49 destinations, 49 routes (49 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.11.0/24 *[Direct/0] 1d 08:19:20

> via at-0/1/0.100
10.0.11.1/32 *[Local/0] 1d 08:19:20
Local
192.168.1.0/24 *[BGP/170] 00:06:08, localpref 100
AS path: 1 I
> to 10.0.11.2 via at-0/1/0.100
192.168.16.0/21 *[Static/5] 00:02:40
Discard
[Aggregate/130] 00:36:17
Reject
192.168.20.0/24 *[Static/5] 00:06:12
Reject

Copyright © 2006, Juniper Networks, Inc.

 Load Balancing
 Default is to randomly choose from multiple equal-cost
paths on a per-prefix basis
– You can change this default to allow multiple next-hop
addresses into the forwarding table with a per-packet
configuration
 Load-balancing characteristics vary according to
Internet Processor version
– Internet Processor I: traffic is balanced according to prefix
among up to eight next hops
 Per-packet behavior when per-packet is configured
– Internet Processor II: traffic is balanced according to prefix
among up to sixteen next hops
 Per-flow balancing when per-packet is configured; packets for
individual flows are forwarded to a common next hop

Copyright © 2006, Juniper Networks, Inc.

 Review Questions
1. What is the difference between a static and an
aggregate route?
2. What is the purpose of the martian table?
3. Describe the JUNOS software route selection process.
4. List and describe three or more standard JUNOS
software routing tables.
5. How would you create multiple static routes to the
same destination with independent next-hop
preference?

Copyright © 2006, Juniper Networks, Inc.