Original Message:
Sent: 03-13-2024 06:18
From: ashvino
Subject: IS-IS and external route
Hi,
This is a side effect of enabling wide-metrics-only which suppresses TLV130.
TLV130 used to carry IP External Reachability prefixes and could distinguish whether a prefix is external.
When wide-metrics-only is enabled, the external prefix is carried over TLV135 and cannot distinguish between internal & external.
Hope this helps.
Cheers,
------------------------------
Ashvin
Original Message:
Sent: 03-12-2024 01:22
From: AfroAmestigon
Subject: IS-IS and external route
Hello colleagues .
I have this configuration
show configuration protocols isis
|
traffic-engineering { |
family inet { |
shortcuts; |
} |
} |
level 1 disable; |
level 2 { |
wide-metrics-only; |
} |
interface ae0.116 { |
point-to-point; |
family inet { |
bfd-liveness-detection { |
minimum-interval 300; |
multiplier 3; |
} |
} |
} |
interface lo0.0 { |
passive; |
} |
export EXPORT-TO-ISIS; |
reference-bandwidth 10g;
lsp-lifetime 65535;
show configuration policy-options policy-statement EXPORT-TO-ISIS
term 1 {
from {
protocol static;
route-filter 0.0.0.0/0 exact;
}
to level 2;
then accept;
}
term 200 {
to level 2;
then reject;
}
show configuration routing-options static
route 0.0.0.0/0 discard;
The default route is advertised, but it is visible as an internal route
Destination/Mask Proto Pre Cost Flags NextHop Interface
0.0.0.0/0 ISIS-L2 15 301 D 10.0.10.123 Vlanif124
Please tell me how to make the default route visible as IS-IS Level 2 external route and had preference 160 ?