Answer: 1.
(w/ 9.6R1.13)
|[edit protocols bgp group E]
|# show
|apply-groups g1;
|neighbor 10.0.0.1 {
|apply-groups g2;
|import p03;
|peer-as 102;
|}
|
|[edit protocols bgp group E]
|# show | display inheritance
|neighbor 10.0.0.1 {
|##
|## 'p02' was inherited from group 'g2'
|
Hello,
According to Release Note, both SRC_AS and DST_AS fields are supported
in JUNOS 9.2.
http://www.juniper.net/techpubs/software/junos/junos92/rn-sw-92/changes-in-default-behavior-and-syntax.html
The following fields are sent when specifying "ipv4-template" with JUNOS
9.2R1.10.
Template (Id
Hello Daniel,
I see the same message whenever issuing 'show vrrp' from CLI. I heard
that this can be ignored because this is a meaningless message.
Regards,
--
Tomohiko Kurahashi <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
Date: Wed Jun 25 2008 18:04:48 JST
>
> Hi,
>
> [EMAIL PROTECTED]> show
From: [EMAIL PROTECTED]
Date: Sat May 17 2008 04:31:56 JST
>
> Hello,
>
> 'asdot' representation isn't supported.
>
> http://www.juniper.net/techpubs/software/junos/junos91/swconfig-policy/defining-as-path-regular-expressions.html
> "Beginning with JUNOS Release 9.1, the range for AS numbers has
Hello,
'asdot' representation isn't supported.
http://www.juniper.net/techpubs/software/junos/junos91/swconfig-policy/defining-as-path-regular-expressions.html
"Beginning with JUNOS Release 9.1, the range for AS numbers has been
extended to provide BGP support for 4-byte AS numbers as defined in
Hello,
I had seen the same message when receiving an UPDATE message including
NEXT_HOP attribute which is the same address as self.
The output of 'show route advertising-protocol bgp ...' and configuration
on the sender will be the beginning to resolve it.
Regards,
--
Tomohiko Kurahashi <[EMAIL
Hello,
I think 'rename' command in configuration mode will match for your case.
ex.# rename interfaces ge-0/0/0 to ge-0/1/0
Regards,
--
Tomohiko Kurahashi <[EMAIL PROTECTED]>
Internet Initiative Japan Inc.
From: [EMAIL PROTECTED]
Date: Wed Feb 20 2008 07:14:58 JST
>
> I have a facility(3, act
Hello,
I think "event-options" will match for your purpose.
For example,
[edit event-options]
generate-event {
EVERY-NIGHT time-of-day "02:30:00 -2000";
}
policy UPLOAD-CONFIG {
events EVERY-NIGHT;
then {
upload filename committed destination FTP-SERVER;
}
}
destinations {
8 matches
Mail list logo
