3.5 EIGRP [for IPv4 and IPv6]

the three criteria that must match for eigrp neighborship are AS number, network (subnet) and K values… the default metrics are:

r1(config-router)#do sh ip proto | i EIGRP met
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0

if you wanted to affect the delay for an AS you adjust the third value… for bw you adjust the first value… in production you would probably never have a good reason to do this but who claims that for purposes of testing there is any reality involved… this is basic eigrp stuff… of course when you actually adjust these values using the metric weight command for the process, the first value is the TOS, which is always zero, making a total of six…

r1(config-router)#metric weight ?
<0-8>  Type Of Service (Only TOS 0 supported)

it borders on trivia…

r7(config-router)#do sh run | b router
router eigrp 100
network 7.7.7.0 0.0.0.255
network 192.168.27.0
network 192.168.67.0
no auto-summary
!
router eigrp 200
network 192.168.78.0
 metric weights 0 0 0 1 0 0
no auto-summary

r7(config-router)#do sh ip proto | i EIGRP met
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP metric weight K1=0, K2=0, K3=1, K4=0, K5=0

in this multi AS system the value for K1 has been set to other than the default for AS 200…

r7(config-router)#do sh ip eigrp neigh
IP-EIGRP neighbors for process 100
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
(sec)         (ms)       Cnt Num
1   192.168.67.6            Se2/0             13 00:37:25   28   200  0  61
0   192.168.27.2            Fa0/0             12 00:37:45   24   200  0  71
IP-EIGRP neighbors for process 200
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
(sec)         (ms)       Cnt Num
0   192.168.78.8            Fa1/0             11 00:24:58   47   282  0  8