[j-nsp] dsc interface destination unusable as next-hop?
José Esteves
Jose.Esteves at cabovisao.pt
Fri Mar 12 09:26:10 EST 2004
Hi,
You must use a policy next-hop self.
Something like this:
policy-options {
policy-statement next_hop_self {
from protocol bgp;
then {
next-hop self;
}
Then you must export into your bgp connection.
Hope that helps.
Regards,
JE
-----Original Message-----
From: Daniel Roesen [mailto:dr at cluenet.de]
Sent: sexta-feira, 12 de Março de 2004 11:49
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] dsc interface destination unusable as next-hop?
Hi,
interfaces {
dsc {
unit 0 {
family inet {
address 10.66.66.65/32 {
destination 10.66.66.66;
}
}
}
}
}
policy-options {
policy-statement ingress-processing {
term blackholing {
from community blackhole-route;
then {
community add no-export;
next-hop 10.66.66.66;
accept;
}
}
}
community blackhole-route members 1:666;
community no-export members no-export;
}
dr at A1> show route 10.10.10.10 extensive hidden
inet.0: 28 destinations, 32 routes (26 active, 0 holddown, 2 hidden)
10.10.10.10/32 (1 entry, 0 announced)
BGP Preference: 170/-101
====> Next hop type: Unusable
State: <Hidden Ext>
Local AS: 1 Peer AS: 64949
Age: 1:41:26
Task: BGP_64949.192.168.0.66+179
AS path: 64949 I
Communities: 1:666 no-export
Localpref: 100
dr at A1> show route 10.66.66.66
inet.0: 28 destinations, 32 routes (26 active, 0 holddown, 2 hidden)
+ = Active Route, - = Last Active, * = Both
10.66.66.66/32 *[Direct/0] 00:27:50
> via dsc.0
Any clues why the next-hop is considered unusable? JunOS 6.2R1.5 here.
Best regards,
Daniel
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list