here u go
in my config:
protocols {
bgp {
metric-out 10;
local-as 7671;
group to-linux {
type external;
metric-out 10;
import damping-policy;
export into-ebgp;
peer-as 7673;
local-as 7671;
neighbor 192.2.200.158;
}
}
policy-options {
policy-statement into-eb
from protocol [ dire
then {
metric 20;
next-hop self;
accept;
}
}
gives on remote peer:
bgpd# show ip bgp
BGP table version is 0, local router ID is 192.2.200.158
Status codes: s suppressed, d damped, h history, * valid, > best, i - i
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 0.0.0.0 192.2.200.190 20 0 7671 i
*> 192.2.200.0 192.2.200.190 20 0 7671 i
*> 192.168.1.1/32 192.2.200.190 20 0 7671 i
*> 192.168.1.2/32 0.0.0.0 0 32768 i
*> 202.54.0.0/16 0.0.0.0 0 32768 i
on remote peer
also:
protocols {
bgp {
metric-out 10;
local-as 7671;
group to-linux {
type external;
import damping-policy;
export into-ebgp;
peer-as 7673;
local-as 7671;
neighbor 192.2.200.158;
}
}
policy-options {
policy-statement into-eb
from protocol [ dire
then {
metric 20;
next-hop self;
accept;
}
}
gives the same...
and:
protocols {
bgp {
local-as 7671;
group to-linux {
type external;
metric-out 10;
import damping-policy;
export into-ebgp;
peer-as 7673;
local-as 7671;
neighbor 192.2.200.158;
}
}
GIVES SAME.
however in my config , the metric statement preceed the export
statement......in show config
how did it work out the reverse in ur case?
by the way:
bgp {
local-as 7671;
group to-linux {
type external;
import damping-policy;
export into-ebgp;
peer-as 7673;
local-as 7671;
neighbor 192.2.200.158
metric-out 10;
}
}
}
also shows:
bgpd# show ip bgp
BGP table version is 0, local router ID is 192.2.200.158
Status codes: s suppressed, d damped, h history, * valid, > best
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Pat
*> 0.0.0.0 192.2.200.190 20 0 767
*> 192.2.200.0 192.2.200.190 20 0 767
*> 192.168.1.1/32 192.2.200.190 20 0 767
* 192.168.1.2/32 192.2.200.190 20 0 767
*> 0.0.0.0 0 32768 i
*> 202.54.0.0/16 0.0.0.0 0 32768 i
so policy takes precedence....
-rgds
Alok
----- Original Message -----
From: Yiheng Ngan
To:
Sent: Thursday, September 26, 2002 9:14 PM
Subject: BGP MEDs [9:2120]
Hi,
Given this configuration, I have a static route for 172.16.0.0/16 with
"metric out 5". Now I also a neighbor statement which I have set a med of
10. Using a policy to match all static route, and setting the meds for 20
and then export them under the bgp group, what will the out come of med for
route 172.16.0.0/16 will my ebgp neighbor 10.10.10.2 see?
Will the meds set on the static statement, or neighbor statement or using
policy will be the "prefer" meds be used.
Below is the config out put.
------------
[edit routing-options]
autonomous-system 23;
{
static{
route 172.16.0.0/16;
metric 5;
{
protocols{
bgp{
group ebgp{
type external;
export set-meds;
peer-as 701;
metric-out 10
neighbor 10.10.10.2;{
traceoptions{
file bgp-logs;
flag packets;
}
log-updown;
[edit policy-options]
policy-statement set-meds{
term seq1{
from {
protocol static;
}
then metric 20;
http://www.groupstudy.com/list/juniper.html
Message Posted at:
http://www.groupstudy.com/form/read.php?f=9&i=2123&t=2120
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/juniper.html
