in cisco 7206:
neighbor 202.140.162.7 remote-as 65000
neighbor 202.140.162.7 description juniper
neighbor 202.140.162.7 ebgp-multihop 255
in juniper :
routing-options {
static {
route 0.0.0.0/0 next-hop 202.140.162.1;
}
autonomous-system 65000;
}
protocols {
bgp {
group test {
type external;
local-address 202.140.162.7;
peer-as 4841;
local-as 65000;
neighbor 203.129.64.60 {
peer-as 4841;
}
}
}
}
Do I need to do anything with the routing-instance in juniper ?
At 10:10 AM 1/7/2002 +0100, you wrote:
>On Mon, Jan 07, 2002 at 04:35:24PM +0800, Raymond Leung wrote:
> > Jan 7 16:31:52 juniper-m20 rpd[330]: bgp_pp_recv: NOTIFICATION sent to
> > 203.129.64.60+16923 (proto):
> > code 2 (Open Message Error) subcode 5 (authentication failure), Reason:
> > no group for 203.129.64.60+
> > 16923 (proto) from AS 4841 found (peer idled), dropping him
> >
> > any idea?
>
>On the Juniper, configure a BGP neighbor to 203.129.64.60, as it
>clearly says to you.
>
>If it is configured, verify the AS number.
>
>/Jesper
>
>--
>Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
>Work: Network manager @ AS3292 (Tele Danmark DataNetworks)
>Private: FreeBSD committer @ AS2109 (A much smaller network ;-)
>
>One Unix to rule them all, One Resolver to find them,
>One IP to bring them all and in the zone to bind them.
--With Regards,
Raymond Leung Network Analyst Zonasa Network Limited
Suite 903,Technology Plaza 651 King's Road Quarry Bay Hong Kong
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:38 EDT