Discussion

IP router id: 192.168.19.1
IP address: 192.168.19.1
Hostname: RouterG
IP prefix: 10.0.1.0/24, Internal, Metric: default 10, Up
IP prefix: 10.0.16.0/24, Internal, Metric: default 10, Up
IP prefix: 192.168.19.1/32, Internal, Metric: default 0, Up
IP extended prefix: 10.0.1.0/24 metric 10 up
IP extended prefix: 10.0.16.0/24 metric 10 up
IP extended prefix: 192.168.19.1/32 metric 0 up
IP external prefix: 192.168.12.1/32, Internal, Metric: default 0, Up
IP extended prefix: 192.168.12.1/32 metric 0 up
Authentication data: 17 bytes
No queued transmissions
...
The show isis database extensive command output shows that the metric for the
static route redistributed into IS-IS is 0. To lower the preference for the route, change
the metric in the routing policy to increase the cost. Here, we increase the metric to
500:
[edit policy-options]
aviva@RouterG# set policy-statement export-statics term 1 then metric 500
The policy now looks like this:
aviva@RouterG# show
policy-statement export-statics {
term 1 {
from protocol static;
then {
metric 500;
accept;
}
}
}
Looking in the IS-IS link-state database shows that the metric value has changed
from 0:
aviva@RouterG> show isis database extensive
IS-IS level 1 link-state database:
RouterG.00-00 Sequence: 0xe5, Checksum: 0x912c, Lifetime: 492 secs
IP prefix: 10.0.1.0/24 Metric: 10 Internal Up
IP prefix: 10.0.16.0/24 Metric: 10 Internal Up
IP prefix: 192.168.12.1/32 Metric: 63 External Up
IP prefix: 192.168.19.1/32 Metric: 0 Internal Up
It’s true that the metric has changed, but instead of being 500, it’s 63. Looking in the
routing table on the neighboring router shows that it has learned the static route:
aviva@RouterA> show route
inet.0: 6 destinations, 7 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.12.1/32 *[IS-IS/160] 00:14:56, metric 73
> via se-0/0/3.0
370 | Chapter 11: IS-IS
This is the Title of the Book, eMatter Edition
Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.