-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
The problem is that neither neighbor has a local-address or
update-source defined. The bgp updates will, by default, be
"sourced" from the physical interface from which the packets are
transmitted. Since the neighbor is defined as the loopback of the
cisco, the Juniper doesn't have a defined neighbor so it will fail.
Regards,
Guy
> -----Original Message-----
> From: Julian Eccli [mailto:je@juniper.net]
> Sent: Tuesday, January 22, 2002 7:00 AM
> To: Raymond Leung; juniper-nsp@puck.nether.net
> Subject: RE: [j-nsp] how to form an IBGP neighbor between juniper
> and cisco ?
>
>
> > why my 7206 said : " 2w0d: %BGP-3-NOTIFICATION: sent to neighbor
> > 203.129.80.36 2/3 (BGP identifier wrong) 4 bytes 0A0A1802 "
>
> The cisco is whining that the BGP ident it's receiving is
> 10.10.24.2, and is wrong. Is 10.10.24.2 the Juniper's lo0 or
> router-id or used anywhere else in the network? The cisco should
> not care what the
> identifier is, as long as it's unique. What does the Juniper's log
> messages file say as well as traceoptions, that would give
> you even more
> information.
>
> Turn off the multihop stuff, not needed. The only time you
> usually see
> multihop for IBGP is in a confederated setup if recursion is
> needed for
> CEBGP.
>
>
> -Julian
>
> >
> > any idea ? Thx!!!!!!
> >
> >
> > group zonaza {
> > type internal;
> > description iBGP-peer-to-7206;
> > multihop ttl 3;
> > peer-as 4841;
> > neighbor 203.129.64.60;
> > }
> >
> > neighbor 203.129.80.36 remote-as 4841
> > neighbor 203.129.80.36 description iBGP peer to Juniper
> > neighbor 203.129.80.36 ebgp-multihop 3
> > neighbor 203.129.80.36 version 4
> > neighbor 203.129.80.36 next-hop-self
> > neighbor 203.129.80.36 soft-reconfiguration inbound
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.1
iQA/AwUBPE1zwo3dwu/Ss2PCEQLyIwCbBePJqJ0pndblm/wHZx77aZIrBh0AnRh5
R09VaiMd0hJNfrm2OWhGhDqM
=MTOZ
-----END PGP SIGNATURE-----
.
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:38 EDT