This is just a bug right now. They have a PR(Problems Report) opened on it.
So, if you just put in a any peer-as or a dummy AS, say one of your
neighbors this will work. Ex.
group external-neighbor {
type external;
family inet {
any;
}
export something-out;
peer-as 65108; <<< This peer-as is what allows the cli to compile and
not give you that error. If you do not have this then the commit will fail.
It is just the CLI parser complaining about
missing peer-as when you are configuring eBGP peering.>>>
neighbor 1.1.1.1 {
description to-neighbor1;
peer-as 65108;
}
neighbor 2.2.2.2 {
description to-neighbor2;
peer-as 64803;
}
-----Original Message-----
From: Arnd Vehling [mailto:av@nethead.de]
Sent: Thursday, March 22, 2001 6:26 AM
To: dave.humphrey@telindusk.net
Cc: Bauer Kurt; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] AW: Juniper Config for Peering-points
Hi,
Dave Humphrey wrote:
>
> Arnd,
>
> What you want to do looks like this
Hu? I havent any problems with configuration and i am
doing peering-setup with groups which works fine as long
as u r using the dummy-as on group level.
regards,
Arnd
-- NetHead Network Design and Security Arnd Vehling av@nethead.De Gummersbacherstr. 27 Phone: +49 221 8809210 50679 Köln Fax : +49 221 8809212
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:41 EDT