yep, it is after.
1.you can also try this command, it works sometime.
test policy <your import policy> <prefix in question>
2.or as Guy said, try show route receive-protocol bgp <bgp peer ip address>
hidden |match <prefix in question>
3. last resort, try the traceoptions:
protocols {
bgp {
traceoptions {
file bgp.log size 10m files 10 world-readable;
flag update receive detail;
}
}
}
you may need to withdraw the prefix and then send it to juniper again to see
the something like the following:
Jan 11 14:28:50 bgp_read_v4_update: receiving packet(s) from 10.1.1.1
(External AS y)
Jan 11 14:28:50
Jan 11 14:28:50 BGP RECV 10.1.1.1+1024 -> 10.1.1.2+179
Jan 11 14:28:50 BGP RECV message type 2 (Update) length 59
Jan 11 14:28:50 BGP RECV flags 0x40 code Origin(1): IGP
Jan 11 14:28:50 BGP RECV flags 0x40 code ASPath(2): y
Jan 11 14:28:50 BGP RECV flags 0x40 code NextHop(3): 10.1.1.1
Jan 11 14:28:50 BGP RECV flags 0x80 code MultiExitDisc(4): 5
Jan 11 14:28:50 BGP RECV <prefix in question>
good luck,
-dave
-----Original Message-----
From: Guy Davies [mailto:Guy.Davies@telindus.co.uk]
Sent: Friday, January 11, 2002 12:39 PM
To: 'Borchers, Mark'; 'juniper-nsp@puck.nether.net'
Cc: 'Dave Qi'
Subject: RE: Private ASN's
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
It's after policy. Therefore, to see the prefix, you may need to add
the "hidden" keyword.
Regards,
Guy
> -----Original Message-----
> From: Borchers, Mark [mailto:mborchers@splitrock.net]
> Sent: Friday, January 11, 2002 5:32 PM
> To: 'juniper-nsp@puck.nether.net'
> Cc: 'Dave Qi'
> Subject: RE: Private ASN's
>
>
> Done that and more. I can verify the advertisement on
> the Cisco sending the route (sh ip bgp nei <M160> adv).
> But I don't see it on the M160, even after removing all
> policy from my IBGP group and clearing the session.
>
> Can you tell me: does sh route received-prot bgp output
> all of the neighbor's advertisements, or only those which
> were put in the table after policy was applied?
>
> TIA,
> Mark
>
> > -----Original Message-----
> > From: Dave Qi [mailto:dqi@bloomberg.com]
> > Sent: Friday, January 11, 2002 11:26 AM
> > To: Guy Davies; Borchers, Mark; juniper-nsp@puck.nether.net
> > Subject: RE: Private ASN's
> >
> >
> > also , do show route receive-protocol bgp <bgp peer ip
> > address> <prefix in
> > question> to see if you are indeed received the prefix on
> the juniper
> > router.
> >
> > -dave
> >
> > -----Original Message-----
> > From: Guy Davies [mailto:Guy.Davies@telindus.co.uk]
> > Sent: Friday, January 11, 2002 12:16 PM
> > To: 'Borchers, Mark'; 'juniper-nsp@puck.nether.net'
> > Subject: RE: Private ASN's
> >
> >
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > What's the prefix? By default, the Junipers won't discard
> > prefixes just because they're using private ASNs. However, there
> > is
> a list of
> > martian prefixes which automatically get discarded. Try "show
> > route martians" to get a list.
> >
> > Regards,
> >
> > Guy
> >
> > > -----Original Message-----
> > > From: Borchers, Mark [mailto:mborchers@splitrock.net]
> > > Sent: Friday, January 11, 2002 5:12 PM
> > > To: 'juniper-nsp@puck.nether.net'
> > > Subject: Private ASN's
> > >
> > >
> > > We have an IBGP mesh consisting of a mixture of Ciscos and
> > > Junipers. A prefix from a downstream to whom we assigned a
> > > private ASN is being accepted by the Cisco routers but appears
> > > to be getting discarded by the Junipers. Can anybody confirm
> > > if this is the default *IBGP* behavior for prefixes containing
> > > private ASNs in the path? I'm not finding anything helpful
> > > on www.juniper.net.
> > >
> > > --
> > > Mark Borchers McLeodUSA Data Services
> > > IP Engineering 9012 New Trails Dr.
> > > mborchers@splitrock.net The Woodlands, TX 77381
> > > (281) 465-1931 http://www.mcleod.net/
> > >
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: PGP 7.0.1
> >
> > iQA/AwUBPD8dzY3dwu/Ss2PCEQKJbACgz3awCwg57Tu56nah/ue5Ut0XcWcAoLRj
> > UhLZr5E8dmyGIGHRYk/sa6D/
> > =51TS
> > -----END PGP SIGNATURE-----
> >
> >
> > .
> >
> >
> >
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.1
iQA/AwUBPD8jBo3dwu/Ss2PCEQIZlACcD9SYuF+BkF/9Tygou8zr4DXn42IAoKBF
/vLQnvSnEOlrImXwjpJtvyCS
=UHu5
-----END PGP SIGNATURE-----
.
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:38 EDT