Forgive me if this is a known bugI seem unable to mask the fxp0 management
port down alarm for the Redundant RE - host 1. (works fine for the primary RE -
host 0).
Platform: MX480, JunOS 10.3R3.7
groups {
re0 {
chassis {
alarm {
management-ethernet {
Hi Paul..!
Yeah - I tried that as well initially with no luck (and just tried again
just now...)
me@wowter show configuration chassis
alarm {
management-ethernet {
link-down ignore;
}
}
user@wowter show chassis alarms
1 alarms currently active
Alarm time Class
Silly question... You did use commit sync, correct?
Will O'Brien
On May 1, 2011, at 7:51 PM, Chris Kawchuk juniperd...@gmail.com wrote:
Hi Paul..!
Yeah - I tried that as well initially with no luck (and just tried again
just now...)
me@wowter show configuration chassis
alarm {
Heh. Good question! I just had to double check:
show config system
commit synchronize;
Thats in there.. OK let's try it manually.
ckawchuk@jmx480# commit synchronize and-quit
re0:
configuration check succeeds
re1:
commit complete
re0:
commit complete
Exiting configuration
On Sat, Apr 30, 2011 at 08:48:59AM -0700, Bill Blackford wrote:
So if what you are saying is that the EX, only being capable of 16k
routes, will only Receive and Accept a random smattering of a full
table being sent up to 16k and any filters beyond that filter on the
16k Received and
Thanks Richard. Great comments on and off list. Thank you.
This just happened to be the first time I tested this scenario. I had
a fundamental misunderstanding of the behavior of the RIB/FIB on the
EX. In production, my EX's only get IGP and local AS.
As a side note, when I filter by upto /19
6 matches
Mail list logo
