To deal with such a situation, the summary-metric command was implemented. If there are many component routes to be summarized and the component routes are frequently updated, the metrics are also updated frequently, and thus a high CPU state may be caused depending on the configuration. Via Summary ( 2611200/0), Null0 <- 2611200, the smallest value among the component routes If a component route is updated and the smallest metric is changed, the summary route metric is also updated. Via Summary ( 307200/0), Null0 <- 307200, the smallest value among the component routes How the summary route metric is determinedįor EIGRP, the smallest metric among the component routes (routes contained in the summary) will be employed as the summary route metric.ĮIGRP-IPv4 Topology Table for AS(1)/ID(172.20.1.2)Ĭodes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, (※ 15.1(4)M3 is used for all the output examples below)Ģ. (All setting examples are described at the end of this document) On R2, configure settings to summarize routes to 10.1.0.0/16 on the interface which connected to the R3 How the summary route metric is determined. There is a need to provide information on how the summary route metrics, which is created by the ip summary-address eigrp command, is determined and details of the summary-metric command implemented in association with the command. This document describes how the eigrp summary route metrics is determined.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |