Hi,
We are quite new with Juniper so excuse me if these exists and i haven't been
able to find them.
We have rolled out several networks with EX series chassis and switches(82xx,
42xx). Currently all logging ends up in /var/log/messages which becomes a
terrible mess, especially when you try
I'm doing some RPM tests using two J2350 [1], both are connected to an
M10. Before any RPM configuration (or even any configuration or any
packet forwarding) the memory utilization of the router was around 86%
of 512 MB. I'm blaming this on the stateful firewall that is
preconfigured but I cannot
Hi,
Not sure if I understood the question...
Anyway, here it goes. On our M10's we have:
syslog {
archive size 128k;
user * {
any emergency;
}
host x.x.x.x {
any notice;
facility-override local7;
}
file messages {
any notice;
authorization info;
}
file updown {
any info;
match LINK_DOWN|LINK_UP;
Quick way is to set mpls to packet-based which essentially makes the router
packet-based as well (so you'll need to go back to standard firewall filters
for router protection). I have about 60 or so RPM probes running on this J2350:
j...@rpm01. show configuration security
forwarding-options
The memory utilization in Show chassis routing-engine is misleading. Run a
Show system process extensive look to see how much is free, Inact and Buf.(I
think) Juniper has KB on this too.
Sample from M10:
Mem: 448M Active, 110M Inact, 117M Wired, 38M Cache, 69M Buf, 27M Free
Jensen Tyler
On Wed, Jun 23, 2010 at 12:18:32PM +0200, Wouter van den Bergh wrote:
Hi,
We are quite new with Juniper so excuse me if these exists and i
haven't been able to find them.
We have rolled out several networks with EX series chassis and
switches(82xx, 42xx). Currently all logging ends up in
2) I disagree with a huge number of the default prioties for a lot of
events. For example, an IGP DOWN event is a priority 5 / notice, while
an IGP UP is a priority 6 / info. If you actually want to match up your
igp flaps and know if a circuit has come back up you'll need to monitor
all the
I'd recommend you not rely on Juniper to do this but instead do it yourself.
If you output the entire contents of syslog to a syslog-ng server, you can
do all of the intelligent filtering you need on the server end.
Personally, I'd rather Juniper focus on fixing bugs for my SRX. :)
Scott
On
Hi all,
I am in my lab trying to test out ISIS between a J2320 running 9.5R2.7 and an
MRV Optiswitch 9000 and I'm having an incredibly difficult time getting routes
to show up in either device. The config is so simple, I'm confused as to why
it's not working and thinking there's a bug. The
But Juniper - pretty please: We *really* need a simple method to be
able to match UP and DOWN events and not drown in useless trash.
Seconded. My current workaround is to use two IP addresses on each syslog
receiver, with one getting notice logs and the other filtered info logs.
The abridged
But Juniper - pretty please: We *really* need a simple method to be
able to match UP and DOWN events and not drown in useless trash.
Seconded.
It is possible to re-log syslog messages at a different severity level using an
event script. For an example see pages 73-75 of this PDF:
The MRV is treating the adjacency like it's a P2P link and you're thereby not
getting a bidirectional adjacency. Perhaps the MRV is being 'smart' about
having a /30 on the link.
Tony
On Jun 23, 2010, at 11:08 AM, Eric Van Tol wrote:
Hi all,
I am in my lab trying to test out ISIS between
On Wed, Jun 23, 2010 at 12:57:17PM -0700, Curtis Call wrote:
But Juniper - pretty please: We *really* need a simple method to be
able to match UP and DOWN events and not drown in useless trash.
Seconded.
It is possible to re-log syslog messages at a different severity level
On Wed, Jun 23, 2010 at 01:43:30PM -0400, Scott T. Cameron wrote:
I'd recommend you not rely on Juniper to do this but instead do it
yourself. If you output the entire contents of syslog to a syslog-ng
server, you can do all of the intelligent filtering you need on the
server end.
I did it
On Wed, Jun 23, 2010 at 03:26:06PM -0500, Richard A Steenbergen wrote:
Managing priorities is pretty dynamic, and uploading/managing/syncing
revisions of slax scripts is a giant pain in the ass already.
Is there any software to help with this task? Common group config has
some of the same
Ross Vandegrift writes:
Is there any software to help with this task? Common group config has
some of the same issues. Should be like the inverse of RANCID -
manage versions of JUNOS groups and scripts with options to push out
approved new versions.
Take a look at the share-data script:
16 matches
Mail list logo
