[nsp] BGP metric?
mohacsi at niif.hu
Wed Jun 2 02:04:43 EDT 2004
We have IPv6 setup with 6PE and also with IBGP. We are using 6PE for
backup now, since we could upgrade only one path only to support IPv6.
We experienced a problem, that 6PE routes are preferred to native routes.
cntrl.6net.hbone.hu#show bgp ipv6 unicast 2001:738:6001::/48
BGP routing table entry for 2001:738:6001::/48, version 525
Paths: (2 available, best #1, table Global-IPv6-Table)
Advertised to update-groups:
1 5 8
Local, (Received from a RR-client), (received & used)
::FFFF:220.127.116.11 (metric 116) from 18.104.22.168
Origin IGP, metric 0, localpref 100, valid, internal, best
Originator: 22.214.171.124, Cluster list: 126.96.36.199
2001:738:6000:1::1 (metric 340) from 2001:738:0:3::1 (188.8.131.52)
Origin IGP, metric 0, localpref 100, valid, internal
Originator: 184.108.40.206, Cluster list: 220.127.116.11, 18.104.22.168
As far as I can see the metric difference is in the metric in
parentheses (116 and 340). Where these metrics come from? This is the
only attribute that makes the decision? How can I change these
attributes to make 6PE backup only.
Network Engineer, Research Associate
Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98
More information about the cisco-nsp